In this guide
It depends on what you want to learn. There is no magic number. Two questions decide it: are you looking for bugs, or for usability problems? And do you need to meet a store requirement?
The one fixed number: Google Play
For personal Android developer accounts created after November 13, 2023, Google Play requires a closed test with at least 12 testers who stay opted in for 14 days in a row; testers who opt out before the 14 days are over do not count (Play Console Help, retrieved 2026-10-24). This is a platform requirement, not a quality target. It tells you nothing about how many testers you need to find problems. Rules change, so check the current Play Console Help page before you plan around it.
Plan for a few more than 12 so that one person opting out early does not leave you below the minimum.
Number by goal
| Goal | Rough size | Why |
|---|---|---|
| Does it start and basically work? | 3 to 5 people | The big, obvious bugs show up fast. |
| Device and OS coverage | As many as it takes to cover your target devices | Count distinct devices and OS versions, not people. |
| Usability and onboarding | A handful, watched or interviewed one by one | The same confusion repeats quickly; depth matters more than count. |
| Google Play closed-test requirement | At least 12, kept active 14 days | Platform rule, see above. |
| Confidence before a wide launch | A mixed group over a longer period | Variety of habits finds what a small group misses. |
These are working guidelines from experience, not statistics. Treat them as a starting point and adjust.
Why more is not always better
- Repeats add little. Once three people report the same crash, a fourth report is not new information.
- You have to read it all. Every tester produces feedback you must triage. Past a point, you cannot act on it.
- Quality beats quantity. Five testers who follow your instructions and write clear findings help more than thirty who open the app once.
- Diversity beats size. Different devices, OS versions, languages and experience levels reveal more than a crowd of identical phones.
How to decide
- Write down the one question you want answered this round.
- Pick the smallest group that can answer it.
- Add testers only where you see a gap (a device, a screen size, a user type).
- Run another round after you fix things; a second small round beats one large one.
With AppReviewX
You get private, structured feedback from other developers. One feedback you give earns 1 credit, and credits buy feedback on your own app. New accounts start with 0 credits. For Android apps on Google Play there are test groups of 12 testers over 14 days at a stretch, and test packages for apps that are already published.
Start with AppReviewX and match the group size to your goal.
Related: App testing for developers · Where to find beta testers · App testing without a QA team