Pre-Release Testing and Deployment Checklist
Pre-Release Testing Checklist
Crucial validation checks to perform on your build before initiating rollout.
Before releasing a new version of your Android application to production, performing structured validation checks helps protect your existing user base and ensures stability. Use this deployment checklist to verify your release.
1. QA & Local Build Verification
- Upgrade Path: Verify that installing the new build over the older production version doesn't crash the app or clear local database stores (Shared Preferences, Room, SQLite).
- Proguard/R8 Check: Build a release bundle locally and test it. Code shrinkers can sometimes optimize too aggressively, causing null-pointer crashes or JSON parsing failures in release mode.
- API Endpoints: Ensure all service base URLs are pointing to production, not staging/dev servers.
2. Play Console Pre-flight Setup
- Release Notes: Complete localized release descriptions ("What's New") for your store listing.
- Managed Publishing: Turn on managed publishing to manually trigger the rollout once Google approves the release.
- Gradual Rollout: For major updates, release to a fraction of your user base (e.g. 5% or 10%) and check Firebase Crashlytics for any spike in crashes before expanding rollout to 100%.
Key Rule: Keep a close eye on **Android vitals** in the Play Console during the first 48 hours of any rollout. A spike in crash rate above Google's bad behavior threshold will hurt your store visibility.