android-template 🤖

A simple collection of Android templates that lets you create an Android/Kotlin project.

This template is focused on delivering a project with static analysis and continuous integration already in place.

This project is inspired by https://github.com/cortinico/kotlin-android-template

How to use

tl;dr: start from https://github.com/omarmiatello/start-android

Just click on button to create a new repo starting from https://github.com/omarmiatello/start-android.

Once created, GitHub Actions should initialize your repository (usually takes less than 30 seconds).

Todo list

Create a new template project from .
Edit newmodule.kt configuration.
- Need help? Try it on Kotlin Playground or our samples here.
Run workflow Build Modules
Choose a LICENSE.
Set your ORG_GRADLE_PROJECT_NEXUS_USERNAME, ORG_GRADLE_PROJECT_NEXUS_PASSWORD, ORG_GRADLE_PROJECT_SIGNING_KEY and ORG_GRADLE_PROJECT_SIGNING_PWD secrets in Settings.
Code some cool apps and libraries 🚀.

Features

100% Kotlin-only template.
3 Sample modules (Android app, Android library, Kotlin library).
Sample Espresso, Instrumentation & JUnit tests.
100% Gradle Kotlin DSL setup.
CI Setup with GitHub Actions.
Publish to Maven Central with Github Actions.
Dependency versions managed via buildSrc.
Kotlin Static Analysis via ktlint and detekt.
Issues Template (bug report + feature request).
Pull Request Template.

Gradle Setup

This template is using Gradle Kotlin DSL as well as the Plugin DSL to setup the build.

Dependencies are centralized inside the Dependencies.kt file in the buildSrc folder. This provides convenient auto-completion when writing your gradle files.

Static Analysis

This template is using ktlint with the ktlint-gradle plugin to format your code. To reformat all the source code as well as the buildscript you can run the ktlintFormat gradle task.

This template is also using detekt to analyze the source code, with the configuration that is stored in the detekt.yml file (the file has been generated with the detektGenerateConfig task).

Powered by GitHub Actions

This template is using GitHub Actions as CI. You don't need to setup any external service and you should have a running CI once you start using this template.

There are currently the following workflows available:

Build Modules - Will build gradle modules based on newmodule.kt configuration.
Validate Gradle Wrapper - Will check that the gradle wrapper has a valid checksum.
Pre Merge Checks - Will run the build, check and publishToMavenLocal tasks.
Publish Snapshot - Will publish a -SNAPSHOT of the libraries to Sonatype.
Publish Release - Will publish a new release version of the libraries to Maven Central on tag pushes.

Publishing

The template is setup to be ready to publish a library/artifact on a Maven Repository.

For every module you want to publish you simply have to add the publish plugin:

plugins {
    publish
}

To Maven Central

In order to use this template to publish on Maven Central, you need to configure some secrets on your repository:

Secret name	Value
`ORG_GRADLE_PROJECT_NEXUS_USERNAME`	The username you use to access Sonatype's services (such as Nexus and Jira)
`ORG_GRADLE_PROJECT_NEXUS_PASSWORD`	The password you use to access Sonatype's services (such as Nexus and Jira)
`ORG_GRADLE_PROJECT_SIGNING_KEY`	The GPG Private key to sign your artifacts. You can obtain it with `gpg --armor --export-secret-keys <your@email.here>` or you can create one key online on pgpkeygen.com. The key starts with a `-----BEGIN PGP PRIVATE KEY BLOCK-----`.
`ORG_GRADLE_PROJECT_SIGNING_PWD`	The passphrase to unlock your private key (you picked it when creating the key).

The template already sets up Dokka for project documentation and attaches -sources.jar to your publications.

Once set up, the following workflows will take care of publishing:

Publish Snapshot - To publish -SNAPSHOT versions to Sonatype. The workflow is setup to run either manually (with workflow_dispatch) or on every merge.
Publish Release - Will publish a new release version of the libraries to Maven Central on tag pushes. You can trigger the workflow also manually if needed.

To Jitpack

If you're using JitPack, you don't need any further configuration and you can just configure the repo on JitPack.

You probably want to disable the [Publish Snapshot] and Publish Release workflows (delete the files), as Jitpack will take care of that for you.

Contributing 🤝

Feel free to open a issue or submit a pull request for any bugs/improvements.

omarmiatello / android-template