How to get 12 testers for Google Play closed testing
Every method developers actually use, what each one costs in money and risk, and which ones survive contact with the 14-consecutive-day rule.
Google will not grant production access to a personal developer account created after 13 November 2023 until it has run a closed test with at least 12 testers opted in continuously for 14 days. There are six ways people meet that bar. Here is what each one actually costs, including the costs nobody quotes.
1. Friends and family
Free, and the default first attempt. It fails for a specific reason: 12 is more people than most developers can reliably ask, and the requirement is not a one-time favour. Every one of them has to stay opted in for 14 consecutive days, and Google also looks at engagement when reviewing the application. Enthusiasm lasts about four days.
Use it for: the first three or four seats. Do not rely on it for: the last eight.
2. Reddit, Discord and forum swap threads
Free, genuinely popular, and the most common route. r/androiddev and several Discords run standing threads where developers test each other’s apps.
The catch is that it is unenforced. Nobody tracks whether the person you tested for stayed opted in, and there is no consequence when they drop out on day six. You will spend real hours recruiting, and you will discover a broken streak weeks later when the application is rejected. Budget for doing it twice.
3. Paid gigs on freelance marketplaces
Typically $5–$40 per run. Immediate, which is the honest advantage of paying a stranger.
Two problems. The first is that you cannot see what you are buying: a seller with twelve accounts on twelve devices in one flat is a different risk profile from twelve real people, and the listing looks identical. The second is churn — a single install followed by fourteen days of silence satisfies the letter of the count and fails the engagement question Google asks in the application.
4. Review-swap and install-exchange services
Avoid. These trade public store reviews and installs for points or money, which is an incentivised review under Google’s policy regardless of how genuine the opinion is. They also do not solve the problem you have: closed-track testers and store ratings are different requirements, and a five-star review does nothing for your 12-tester count.
The policy detail and what enforcement looks like is worth reading before you sign up to one of these.
5. Recruiting real users directly
Landing page, waitlist, a post in a community where your actual audience already is. Slow — usually weeks — but these are the only testers on this list whose feedback tells you whether the product works for the people it is for.
Use it for: the long game, always. Do not rely on it for: a deadline four weeks out.
6. Closed-test pods
A fixed cohort of developers who all run the same 14-day window together, testing each other. Everyone in the group needs the same thing at the same time, which is what makes the commitment stick where a swap thread’s does not.
What to check before joining one: whether it tracks daily engagement or only the opt-in, whether it replaces someone who drops out mid-cycle, whether it seats more than 12 so a dropout is not fatal, and whether it touches the public store surface at all. If it offers you store reviews, it is item 4 wearing a different name.
What to actually do
Stack them. Take the three or four seats you can get from people you know, get the rest from a cohort that has a buffer and a dropout policy, and start the slow work of recruiting real users in parallel because that is the only one that compounds.
The thing to optimise is not reaching 12. It is reaching 12 and not losing one on day nine, because the clock resets when you do and you will not be told.