# Will set up a pre-commit hook that will run # reformat the code before a git commit. # Will update IntelliJ/AndroidStudio reformat rules to # match the ktlint style.

I use the ktlint-gradle plugin to integrate it into my build. A formatter can help you ship beautified code and avoid useless discussions.įor Kotlin my preferred formatter is ktlint. Having several comments on your pull-requests about where to place parenthesis or extra white-spaces can be pretty annoying. I generally don’t start writing code without a good formatter to support me. I believe that in 2020 is safe to assume that you can start your new Android project with Kotlin only. The clear choice I made in this template is to have it as a 100% Kotlin template. In this blog-post, I will walk you through the steps I do before starting an Android project and that you can find already applied in the linked template.

Here you can find my Android App/Library template: They’re now available for everyone to use with Github templates with just one click. Recently I’ve spent some time polishing them and open-sourcing some of them. They help me kick off a project if I have a new idea in mind, without having to spend time configuring everything from scratch. That’s why throughout the years I crafted my own project templates. Unfortunately, setting up such tools can be time-consuming, especially if you’re not familiar with a specific tool and how to configure it. They’re generally the first thing I set up before starting a new project. They’re crucial to deliver good quality code, and I can’t imagine working without them. I love developer-tools such as CIs and static-analysis tools. That’s how a lot of side-projects of mine died in the past.

Setup a code formatter to enforce code-style.

Setup a proper CI to build your project.

Have a great idea for a weekend project.

Have you ever experienced something like this:

Detekt android studio plugin