futurice/android-best-practices ? reverse-engineered prompt

Build me a simple Android best practices guide that reads like a friendly handbook for developers.

I want it to cover the main do’s and don’ts of Android work, like how to set up Gradle, keep secrets out of source control, choose libraries wisely, organize layouts, handle testing, avoid leaks, and keep builds stable. Make it easy to skim, with clear section headings and short explanations people can actually use.

It should feel like a polished reference document, not a tutorial or a big app. If it makes sense, include translated versions in a separate translations area so it can be reused by teams in different languages. Use current Android advice where needed, and if anything is outdated, update it to something modern and practical.