- Project Structure
- Java Guidelines
- Resources Guidelines
- Android Manifest Guidelines
- Gradle Best Practices
Our parting thought: BE CONSISTENT. If you're writing/editing code, take a few minutes to look at the code around you and determine it's style. If the code use spaces around if clauses, you should too. If the comments have little boxes of stars around them, make your comments have little boxes of stars around them too.
The point of having style guidelines is to have a common vocabulary of coding, so people can concentrate on what you're saying, rather than on how you're saying it. We present global style rules here so people know the vocabulary. But local style is also important. If the code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they to read it.
- https://github.com/futurice/android-best-practices#gradle-configuration (Prefer to follow this)
- https://github.com/bufferapp/android-guidelines/blob/master/project_style_guidelines.md
- https://google.github.io/styleguide/javaguide.html
- http://source.android.com/source/code-style.html
- https://github.com/ribot/android-guidelines/blob/master/architecture_guidelines/android_architecture.md
- http://tools.android.com/tech-docs/new-build-system/user-guide
- https://developer.android.com/studio/projects/index.html
- https://github.com/ribot/android-guidelines/blob/master/project_and_code_guidelines.md
- https://medium.com/rocknnull/effective-java-for-android-cheatsheet-bf4e3433889a#.2p879tgbo
- https://developer.android.com/studio/publish/app-signing.html