The mobile app testing checklist for iOS and Android
A phone is not a desktop with a smaller screen. Real devices, flaky networks, and a hundred gestures make mobile testing its own discipline.
By Quality AboveAll · May 25, 2026 · 7 min read
Where this fits in the wider picture.
The mobile app testing checklist for iOS and Android
We work inside your team
Your standups, your repos, your release calls.
Numbers you can audit
Every claim backed by a metric you can check.
Green builds, always
CI/CD that blocks the merge instead of the release.
Built for the traffic you expect next
Capacity modelled against real growth curves.
Ready for the audit
Traceable artefacts for regulated environments.
Test on real devices across networks, interruptions, and OS versions, not just a single simulator, so your app holds up in your users' hands.
Start with device and OS coverage
You cannot test every phone, so test the ones that matter. Pull your analytics, find the top devices and OS versions your users carry, and build a coverage matrix from real data. Cover one older low-memory device, one current flagship, and the newest OS beta.
- Top five devices by active users on each platform
- Oldest OS version you still support
- Smallest and largest screen sizes in your base
- Both light and dark mode
Cloud device labs like BrowserStack let you reach phones you do not own, but keep a few physical devices for the bugs that only appear on real hardware.
Test the conditions phones live in
Desktop apps sit on a stable connection. Phones do not. Throttle the network to 3G, drop it mid-request, and switch from wifi to cellular while a screen is loading. Then fire the interruptions that only happen on mobile.
- Incoming call or alarm during a flow
- App backgrounded and restored after an hour
- Low battery and low storage states
- Permission prompts accepted, denied, and revoked later
Most production mobile crashes we see trace back to an interruption or a permission state, not the main flow.
Cover gestures, layout, and accessibility
Touch targets, swipes, pinch-to-zoom, and the on-screen keyboard all create bugs that functional checks on a web build never surface. Rotate the device, test with large system fonts, and run the screen reader on a few core flows. Our accessibility testing work pairs well here, since mobile and accessibility issues often hide in the same place.
Automate the repeatable parts
Smoke tests, login, and core navigation should run on every build so regressions surface fast. Tools like Appium, Espresso for Android, and XCTest for iOS each have a place depending on how deep you go.
Keep automation for the stable, high-traffic paths and leave the messy edge cases to skilled manual testers. Our test automation framework service builds the suite, and our mobile testing team runs the device work so you can ship a build that works on the phone in your user's pocket. Want a second look at your current coverage? Book a testing audit.
Questions about this topic.
What should a mobile app testing checklist cover?
Device and OS matrix, network conditions including offline, interruptions such as calls and backgrounding, permissions, performance and battery, accessibility, and store compliance before submission.
Do we need to test on real devices?
Yes for performance, battery and camera behaviour, which do not reproduce on simulators. Simulators are fine for functional flows and much cheaper for broad coverage.
How many devices should we test on?
Prioritise by your own analytics, not market share. Cover the top devices your users actually run, plus the oldest OS version you support, where performance problems surface first.
How ready is your product to ship and scale?
Answer 12 questions and get a maturity score across architecture, delivery, quality and security, plus the three things we would fix first. No email required to see your result.
Senior-led QA,embedded in your workflow.
Often less than one full-time hire. Book a free 30-minute testing audit and we'll show you exactly where the risk is hiding.