Published in


Android App Release Checklist For The Production Launch

Android App Release Checklist For The Production Launch

Add analytics to your Android application

Apply proguard in your Android application

  • Do not forget to add the Proguard rules in proguard-rules.pro file for any library that you have included in your project.
-dontwarn okio.**
  • Add the rule for the classes on which you do not want to apply Proguard using keep class.
-keep class com.mindorks.AmitShekhar**
  • Do not use something like AwesomeFragment.class.getSimpleName() as a fragment TAG. Proguard may assign the same name (A.class) to two different fragments in different packages while obfuscating. In this case, two fragments will have the same TAG. It will lead to the bug in your application.
  • Keep your mapping file of the Proguard to trace back to the original code. You may have to upload it at different places like PlayStore Console for seeing the original stack-trace of the crashes.

Recommended Reading

Check your application size

Add crash reporting library


Upgrade testing for your application

Turn off logging and debugging

Be ready with WHAT’S NEW in your application

Be ready with the updated screenshot

Check your application version name and version code

Measure the metrics around the application performance

  • Frames Per Second
  • CPU Usage
  • Memory Usage
  • Network Traffic
  • Disk

Check for app localization


Test your device on various OS versions and different screen sizes


Look through your application from the security perspective

Follow up on the PlayStore feedback



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Amit Shekhar

A mentor helping developers in getting high-paying tech jobs | Open Source Contributor | IIT 2010–14 | Get Mentorship: amitshekhar.me