In this guide
A beta without a plan drifts. This four-week plan gives each week one purpose and ends with a decision gate: a question you answer with "go", "fix first" or "stop". It is a suggested structure; shorten or stretch it to fit your app.
Week 1: Prepare and start
Goal: a build testers can actually use.
- Test the build yourself on a clean install.
- Write short test instructions: what to try, how long it takes, how to report.
- Invite your first group and set up a way to collect feedback.
Gate 1: can testers install and reach the main screen? If more than a few cannot, fix that before anything else.
Week 2: Find the big problems
Goal: crashes, blockers and confusing first steps.
- Read feedback daily and group it by area.
- Fix blockers quickly and release a new build.
- Ask testers to confirm the fixes.
Gate 2: are there open blockers or crashes on the main path? If yes, repeat this week.
Week 3: Widen and refine
Goal: variety and polish.
- Add testers on different devices, OS versions and languages.
- Look at usability: where do people hesitate or misread things?
- Sort findings by severity: blocks use, annoys, nice to have.
Gate 3: do new testers report mostly things you already know? When findings repeat and no new serious ones appear, you are approaching saturation.
Week 4: Verify and decide
Goal: confidence in the release candidate.
- Freeze features. Only fix bugs.
- Run a final pass on the release build, not a debug build.
- Check store listing, privacy information and permissions.
- Go through your release checklist.
Gate 4, the release decision: - No open blockers or crashes on the main path. - Remaining issues are known, rated and acceptable. - You can describe the app in the store without overpromising.
If all three hold: go. If not: fix first and run another short round.
If you target Google Play
Personal developer accounts created after November 13, 2023 need a closed test with at least 12 testers who stay opted in for 14 consecutive days; testers who opt out earlier do not count (Play Console Help, retrieved 2026-10-24). Start that period early and plan the weeks above around it. Check the current Play Console Help page for details.
Printable gate sheet
| Week | Question | Go / fix / stop |
|---|---|---|
| 1 | Can testers install and reach the main screen? | |
| 2 | Any open blocker or crash on the main path? | |
| 3 | Are findings mostly repeats? | |
| 4 | Blockers closed, known issues acceptable? |
With AppReviewX
Developers exchange private, structured feedback: 1 feedback = 1 credit, new accounts start at 0 credits. Android apps get Google Play test groups (12 testers, 14 days in a row); published apps get test packages.
Start with AppReviewX and run week 1.
Related: App testing for developers · Feedback on your app idea · Feedback on a mobile game