Beta testing is a series of small, controlled tests with a wider group each time. Each phase answers one question and ends when you have the answer.
The phases
1. Alpha: does it work at all? - Who: you and your team, maybe a few friendly developers. - Where: builds you install directly, or an internal track. - Exit criteria: the core action works, no crash on start, you can describe the app in one sentence.
2. Closed beta: does it work for other people? - Who: a limited group you invite. - What they do: follow a short brief, report device, steps and results. - Exit criteria: no open crash or blocker, repeated confusions are fixed or explained.
3. Open beta (optional): does it hold up at a larger scale? - Who: anyone who can find and join. - Exit criteria: no new serious problems for a set period, feedback becomes mostly small items.
4. Release candidate: is this the build? - Who: you, plus a final check by a few testers. - Exit criteria: store listing, privacy details and build are ready; you have no known blocker.
5. Release. Then keep reading feedback.
Use the exit criteria as gates. Do not move on just because time has passed.
How this maps to the stores
Google Play. The Play Console offers internal, closed and open testing. According to Play Console Help (retrieved 2026-10-24): an internal test can have up to 100 testers per app; closed testing is for pre-release versions with a wider audience, using email lists or Google Groups; open testing makes the test version visible on Google Play so anyone can join. Personal developer accounts created after November 13, 2023 must meet specific testing requirements before the app becomes available on Google Play. According to the linked Play Console Help article (retrieved 2026-10-24), that means a closed test with at least 12 testers who stay opted in for 14 consecutive days, and a summary of your testing feedback when you apply for production access.
Apple TestFlight. Per Apple's App Store Connect Help (retrieved 2026-10-24): you can invite up to 10,000 external testers per app, by email or a public link. External builds go through TestFlight App Review; the first build of a version needs a full review.
| Phase | Google Play | TestFlight |
|---|---|---|
| Alpha | Internal testing | Internal testers (see Apple's docs) |
| Closed beta | Closed testing | External group with invited testers |
| Open beta | Open testing | External group with a public link |
| Release candidate | Production release prepared | Final build submitted for App Review |
Who does what
- You: write the brief, send the build, read and sort the feedback, decide.
- Testers: follow the brief and report in the format you ask for.
- The platform or store: distributes the build and sets limits.
Where AppReviewX fits
AppReviewX provides private, structured feedback from other developers; one feedback you write earns one credit, and one credit buys feedback on your app. New accounts start with 0 credits. For Android apps, test groups are built around 12 testers for 14 days in a row. For apps already published, there are test packs. Nothing is traded for store reviews or installs.
Start with AppReviewX and set up your first closed round.
Related: Beta testing timeline: a 4-week plan before release, How many beta testers do you need?. Back to the overview.