A Mobile Release Testing Checklist
A practical pre-release checklist for mobile apps — the device, network, lifecycle, and store-readiness checks that catch the bugs desktop testing never will.
Mobile apps fail in ways web apps never do: interrupted by a call, killed in the background, resumed after three days, on a two-year-old phone with a full disk. This checklist covers the release-blocking checks that only matter on mobile.
Device & OS coverage
Test on what your users actually carry, not just the newest flagship.
- Top device models from your analytics (not just the latest)
- Oldest OS version you officially support
- Newest OS version (including the upcoming beta if near release)
- At least one low-end / low-memory device
- Both smallest and largest supported screen sizes
Network conditions
The happy path on office wifi is not the real world.
- Slow / unstable connection (3G, throttled)
- Offline behavior and the transition back online
- Wifi ↔ cellular handoff mid-action
- Airplane mode during a network request
App lifecycle
The lifecycle is where mobile-specific bugs hide.
- Backgrounding and resuming mid-task keeps state
- App killed by the OS and relaunched restores correctly
- Deep links open the right screen from a cold start
- Interruptions handled: incoming call, notification, alarm
- Rotation / split-screen (where supported) doesn’t lose data
Permissions
Permission flows are a common source of crashes and dead ends.
- First-time permission request flows correctly
- App degrades gracefully when a permission is denied
- Permission revoked in settings while app is running is handled
- No feature hard-crashes on a missing permission
Platform integrations
- Push notifications deliver and deep-link correctly
- Biometric / passcode auth works and falls back properly
- Payments / in-app purchases in sandbox
- Share sheet, camera, and file pickers return correctly
Store readiness
The last mile before submission:
- App icon, splash, and screenshots correct for all sizes
- Version and build number bumped
- Release build tested (not just debug) — obfuscation/minification can break things
- Crash reporting and analytics wired up in the release build
- Store metadata and privacy declarations up to date
The takeaway
A mobile release checklist is not bureaucracy — it is a map of the failure modes that never appear on a developer’s clean, high-end device on fast wifi. Run it every release, and the bugs your users would have found become bugs you found first.