How to Test a Mobile Application: Practical QA Checklist

Use production analytics or target-market data to select representative operating-system versions, manufacturers, screen sizes and performance levels. Include the oldest supported configuration and at least one common current device.

A small purposeful matrix produces more useful confidence than a large random collection of devices.

Cover clean installation, first launch, update from the previous supported version, backgrounding, process termination and relaunch. Verify whether user state, sessions and locally stored data are restored or cleared according to policy.

Include low-storage conditions and interrupted updates when the platform and test environment allow safe simulation.

Test first request, allow, deny, permanent denial and later changes through operating-system settings. Optional permissions should not block unrelated features.

Interrupt important flows with calls, notifications, app switching, screen lock and orientation changes. Confirm that work is preserved safely and actions are not duplicated.

Test online, offline, slow and changing connectivity. Submit important actions during a connection loss and verify clear feedback, safe retry and duplicate prevention.

Observe startup, scrolling, battery use and memory on representative devices. Performance that is acceptable on a flagship phone may fail on a common lower-end device.

Check touch targets, keyboard overlap, system Back behaviour, large text, dark mode, screen-reader labels and reduced motion. Perform important journeys with one hand and on the smallest supported screen.

Verify secure local storage, logout, deep links, screenshots or app-switcher privacy and protection of API credentials. Mobile security must also be enforced by backend authorisation.