Mobile App Release Checklist
20 items · Technical · Hard difficulty · 2 hours
A practical checklist to get your iOS and Android app safely published and monitored.
-
Bump app version and build number
Update semantic version and build code for both iOS and Android.
-
Archive signed release builds for iOS and Android
Create signed .ipa (iOS) and AAB/APK (Android) with release keys.
-
Install and test release builds on supported devices
Test on a sample of device models, OS versions, and network conditions.
- Prepare store listing metadata
-
Create high-res screenshots and device previews
Follow platform size guidelines and show key flows.
-
Write concise short and long descriptions highlighting features
Lead with top benefit and include keywords for discoverability.
-
Select keywords, category, and age rating
Use targeted keywords and set the correct content rating.
-
Create or update privacy policy and host URL
Include data collection, usage, and third-party services.
-
Document and justify sensitive permissions
Provide clear reasons for camera, location, contacts, and other sensitive access.
-
Write clear release notes and changelog
List bug fixes, improvements, and notable changes for users.
-
Verify in-app purchases and entitlements
Test purchase flows and sandbox subscriptions before publishing.
-
Enable analytics, crash reporting, and alerting
Set up crash alerts and dashboards before release.
-
Configure feature flags and remote config for rollout
Prepare flags to control gradual rollout and quick fixes.
-
Upload builds to App Store Connect and Play Console
Attach correct build, dSYM/mapping files, and release notes.
-
Configure store release settings (pricing, countries, staged rollout)
Choose release date, region availability, and rollout percentage.
-
Run pre-release validations and fix metadata errors
Use store validators to catch missing icons, links, or screenshots.
-
Submit app for review and schedule release
Select manual or automatic release after approval.
-
Monitor review status and respond to reviewer requests
Check review notes daily and provide requested info promptly.
-
Run post-publish smoke tests and verify key user flows
Test login, purchase, onboarding, and deep links on the live build.
-
Monitor analytics, crashes, and be ready to rollback or hotfix
Watch KPIs for 24–72 hours and have rollback steps documented.
Printed from TickYouOff — the interactive version tracks your progress and can be shared with others.