In this guide
If you built your app by describing it to a coding tool, you have a working product and a smaller mental map of the code than someone who typed every line. That is fine. It just means your testing should rely on what the app does, not on what you remember writing.
This plan takes about an afternoon. Write down every failure; fix after you finish a pass, not during it.
1. Start from a clean install
Uninstall the app, then install the build you plan to publish (not a debug run from your computer). Open it as a brand-new user.
- Does first launch work with no account, no data, no saved settings?
- Are all permission prompts understandable, and does the app still work if you tap "Don't allow"?
Why: the version on your phone while building has leftover data and permissions that a new user does not have.
2. Walk every screen, then break the order
Make a list of screens and actions. Go through them once as intended. Then go through them badly:
- Tap buttons twice quickly.
- Go back in the middle of a flow.
- Rotate the phone, change font size, switch to dark mode.
- Leave the app for five minutes and return.
Why: generated screens are often tested only along the happy path you described. Order and timing are where surprises sit.
3. Feed it awkward input
Empty fields, a very long name, emoji, a number where text is expected, spaces only. More on this: see the mobile testing checklist.
Why: forms rarely say what they do with input you did not describe. You find out by trying.
4. Switch the network off
Turn on airplane mode at different points: before opening, mid-load, mid-save. Then turn it back on.
- Is there an understandable message, or an endless spinner?
- Is anything lost that the user typed?
Details in test the offline behavior of your app.
5. Test on a real phone, ideally two
An emulator is a start, not a finish. Use one recent phone and, if you can, an older or smaller one. See which Android devices to test on.
6. Check what you cannot see
Read through the project for anything that should not ship: keys, test accounts, debug screens, placeholder text. See API keys and secrets in AI-generated apps.
7. Let someone else try
You know how the app should be used, so you will avoid the problems. Hand it to a person who has never seen it and watch without helping. Then collect crashes and rank them: how to prioritize crash reports.
Keep a simple log
For each failure write: what you did, what you expected, what happened, device. That is also the format you can paste into your coding tool later. See bugs testers find in AI-built apps.
Next step
AppReviewX gives you private, structured feedback from other developers on a build you are about to ship. One feedback you write earns one credit; new accounts start at 0. Start free.
Related: Vibe coding hub, launch checklist, API keys and secrets.