Android Best Practices - Sean Katz's blog

Seeking to be an advanced Android developer? Leading a team to a better work process? We'll aim to cover a bunch of development process steps and best practices. Providing a "cook book" for successful, agile, clean process. Area we'll talk about: REST, Android studio, Gradle, Maven, ProGuard, Intellij Inspections, Lint, Build variants, Flavours, Strict mode, MAT, Google play beta and rollouts, Graphical design, Performance, Automation, Unit testing, Git workflow, Jenkins... And much more!

Thursday, May 7, 2015

Gradle tip - Read the changelog of the Android Build Tools

›
Read the change log of the  Android Build Tools  - This line in the build.gradle: buildToolsVersion " x.y.z " Controls the a...
Monday, April 20, 2015

Gradle tip - Always choose dependencies explicitly

›
For the sake of your CI process and versioning (the ability to go back in time in your SCM and get the same result) - always use explicit ...
Sunday, April 5, 2015

Gradle tip - Prefer a remote maven dependency

›
Prefer a remote maven dependency over a local jar. Just because it makes your build easier keeps your SCM lighter, and lets you easily chan...
Monday, March 30, 2015

Gradle tip - Set names to your modules

›
Set names to your modules/sub-projects. The name for your module/sub-project will be defined according to the filesystem directory it'...
Tuesday, March 10, 2015

Gradle tip - Leverage a top-level build.gradle

›
Usually a project contains more than one sub project or module. In that case you will want to have common settings that will be shared amon...
Thursday, February 19, 2015

Gradle tip - Always use a gradle wrapper

›
The wrapper sits in your project and defines a common build behaviour for all your team and CI tools.  Why  not use  a local gradle inst...
›
Home
View web version
Sean Katz
View my complete profile
Powered by Blogger.