Quick answer
Before launch, test installation and first launch, signup and login, your core user flows, payments, permissions and notifications, behaviour on slow or no network, performance on low-end devices, a spread of screen sizes and OS versions, and your store listing and privacy details. Test with real users on real devices, not just emulators.
1. Install and first launch
- Installs cleanly from the store or test track.
- Opens without crashing on first launch.
- Splash and loading screens don't hang.
- App size is reasonable for users on limited data.
2. Signup, login and onboarding
- OTP arrives and auto-fills; resend works; wrong OTP shows a clear message.
- Google or social login works on fresh devices.
- Password reset works end to end.
- Onboarding can be skipped or completed without confusion.
3. Core flows
List the three to five things users must be able to do, then test each from start to finish: search, add to cart, book, post, pay, upload. Ask testers to describe where they hesitated — that is where users drop off. Usability testing finds these moments.
4. Devices, screens and OS versions
| Check | Why |
|---|---|
| Budget and older phones | Memory and performance issues hide on flagship devices |
| Several manufacturers | Custom Android skins handle permissions, battery and notifications differently |
| Small and large screens | Buttons off-screen, cut-off text, keyboard covering fields |
| Supported OS versions | APIs and permission flows differ by version |
| Dark mode and large font | Unreadable text and broken layouts |
5. Network, permissions and notifications
- Slow 3G/4G, switching networks, going offline mid-task.
- Denying a permission, then allowing it later from settings.
- Push notifications arrive and open the right screen.
- Background battery restrictions don't break key features.
6. Payments and data
- Successful, failed and cancelled payments all show the right result.
- Refund and retry flows work.
- Data survives app restart, update and logout/login.
7. Store and policy readiness
- Store listing screenshots and description match the app.
- Privacy policy link works; data safety answers are accurate.
- Content rating completed.
- For new personal Google Play accounts: the closed test requirement is planned — see the 12-tester rule.
Frequently asked questions
Are emulators enough for testing?
Emulators are useful during development, but real devices reveal problems with manufacturers' Android versions, performance, cameras, notifications and networks that emulators miss.
How long should pre-launch testing take?
It depends on your app. Many teams run a focused multi-day test so testers use different features across several sessions.
Who should do the testing?
Your team for obvious checks, and real users who match your audience for everything else. See our guide on crowdtesting vs in-house QA.