Mobile App Manual Testing: Android and iOS Checklist

Mobile apps fail in ways web QA rarely catches: OS permissions, background refresh, keyboard overlap, push notifications, and the thousand variations of Android devices. Mobile app manual testing is still essential for most startups, even when you have some automation.

This checklist covers what to verify on Android app testing and iOS app testing before release. Use it as a sign-off sheet on real devices, not simulators alone.

For how manual testing fits your overall strategy, see manual vs automated testing for startups.

Before you start: test environment

Document device list: at minimum one recent iPhone, one older iPhone, one Pixel-class Android, one Samsung or OEM-skinned Android.

1. Install and first launch

• Fresh install from TestFlight, Play Internal Testing, or APK/IPA
• App opens without crash on cold start
• Onboarding screens render; skip and complete paths both work
• Permission prompts appear at the right moment (not all at once on launch unless required)
• Deep link opens app to correct screen when installed

First launch is high churn. Test it every release.

2. Authentication

• Sign up, login, logout
• Biometric login (Face ID, Touch ID, fingerprint) if supported
• Session persists after app kill and reopen
• Session expires or refreshes as designed
• "Forgot password" flow completes on device (email/SMS)
• OAuth (Google, Apple Sign In) works on both platforms

Compare with web auth if you share accounts. Token sync bugs are common.

3. Core user journeys

Repeat your product's money paths on mobile:

• Create, view, edit, delete primary content
• Search and filters return correct results
• Pagination or infinite scroll loads without duplicates
• Pull-to-refresh updates data
• Offline or slow network: graceful message, retry, no silent data loss
• Upload photos, files, or camera capture if applicable

Our manual testing service often maps these paths from a web regression suite and adapts them for mobile.

4. Navigation and gestures

• Tab bar or drawer navigation reaches every main section
• Back gesture (iOS swipe, Android back) behaves predictably
• Modals and bottom sheets dismiss correctly
• Landscape orientation (if supported) does not break layout
• Safe areas respected on notched devices (no buttons under home indicator)

5. Keyboard and input

• Text fields scroll into view when keyboard opens
• Return key moves focus or submits as expected
• Numeric keyboards for phone, PIN, amount fields
• Autofill and password managers work (iOS Keychain, Google Autofill)
• Copy, paste, and undo behave on long text fields
• Emoji and non-Latin input do not crash or truncate silently

6. Notifications and background behavior

• Push notification received when app backgrounded and killed
• Tapping notification opens correct screen
• In-app notification center marks items read
• Badge count updates on home screen icon
• Background sync completes (e.g. message delivery) without draining battery abnormally

Test with Do Not Disturb, low power mode, and restricted background data on Android.

7. Permissions and OS settings

Walk through each permission your app requests:

After deny or revoke, app shows helpful explanation and recovery path, not a blank screen.

8. Android-specific checks

• Back button from every major screen exits or navigates logically
• App survives configuration change (rotation if supported)
• Test on Android 13+ notification permission prompt
• Picture-in-picture or split screen if supported
• Different screen densities (small phone vs tablet)
• OEM quirks: Samsung, Xiaomi battery optimization killing background work

Android app testing without a Samsung or popular OEM device misses a real user segment.

9. iOS-specific checks

• Test on latest iOS and one older supported version
• Apple Sign In works if offered alongside other login methods
• App Tracking Transparency prompt if applicable
• Dynamic Type: larger accessibility text sizes do not break layout
• Dark mode and light mode (if supported)
• App Store review guidelines: no broken links, login demo account ready

iOS app testing on simulator plus one physical device minimum before App Store submission.

10. Performance and stability

• Cold start under acceptable threshold (team-defined, often under 3 seconds on mid-range device)
• No memory warnings during 15-minute session
• Lists with 500+ items scroll smoothly or virtualize correctly
• No ANR on Android (app not responding) during network calls
• Airplane mode toggle: app recovers when connectivity returns

For load and backend stress, pair manual checks with performance testing on APIs.

11. Payments and external apps

• In-app purchase or Stripe mobile flow completes
• Return from Safari/Chrome custom tab or WebView after 3DS
• Share sheet exports content correctly
• Open maps, mail, phone links in system apps
• PDF or document preview opens

12. Upgrade path

• Install previous public version, then upgrade to release candidate
• User data and login persist after upgrade
• New permissions handled on first launch after upgrade
• Migrations complete without crash on large local databases

Skipping upgrade testing causes bad App Store reviews from loyal users.

13. Accessibility (quick pass)

• VoiceOver (iOS) and TalkBack (Android) reach primary actions
• Buttons have accessible labels (not icon-only without labels)
• Color contrast readable outdoors
• Tap targets large enough for touch (roughly 44pt minimum)

Full WCAG audits go deeper. This pass catches blockers before release.

14. Release sign-off

Sign-off name, date, build number. Keep records for App Store / Play Console submissions.

When to add automation

Manual checklist first. Add mobile automation when:

• Core flows are stable for 4+ weeks
• You release weekly and manual full pass takes too long
• Same regression appears twice on one platform

Until then, disciplined mobile app manual testing beats flaky Appium suites nobody maintains.

Practical takeaway

1. Test on real devices: recent + one older phone per platform
2. Run auth, core journeys, notifications, and upgrade every release
3. Cover Android OEM and iOS accessibility quirks explicitly
4. Sign off in writing before store submission

Need help building a mobile test plan for your next release? Get a free QA audit or explore our manual testing services.