android studio development versus production

Your default option should be Gradle using the Android Gradle plugin.

This can be bad when you need to upgrade (or reinstall) the IDE, as you may lose your SDK installation, forcing a long and tedious redownload.Īlso avoid putting the SDK in a system-level directory that might need root permissions, to avoid permissions issues. Some distributions of IDEs include the SDK when installed, and may place it under the same directory as the IDE.

Place your Android SDK somewhere in your home directory or some other application-independent location. Summary Use Gradle and its default project structure Put passwords and sensitive data in gradle.properties Use the Jackson library to parse JSON data Don't write your own HTTP client, use OkHttp libraries Avoid Guava and use only a few libraries due to the 65k method limit Sail carefully when choosing between Activities and Fragments Layout XMLs are code, organize them well Use styles to avoid duplicate attributes in layout XMLs Use multiple style files to avoid a single huge one Keep your colors.xml short and DRY, just define the palette Also keep dimens.xml DRY, define generic constants Do not make a deep hierarchy of ViewGroups Avoid client-side processing for WebViews, and beware of leaks Use JUnit for unit tests, Espresso for connected (UI) tests, and AssertJ-Android for easier assertions in your Android tests Always use ProGuard or DexGuard Use SharedPreferences for simple persistence, otherwise ContentProviders Use Stetho to debug your application Use Leak Canary to find memory leaks Use continuous integration If you are interested in iOS or Windows Phone development, be sure to check also our iOS Good Practices and Windows App Development Best Practices documents. Lessons learned from Android developers in Futurice. Avoid reinventing the wheel by following these guidelines.

Android studio development versus production