The requirement, what actually counts, the two mistakes almost everyone makes — and a free, genuine way through it.
If you created a personal Play Console developer account after 13 November 2023, you can't publish your app publicly until you've run a closed test with at least 12 opted-in testers over 14 consecutive days, then applied for production access. (The requirement launched at 20 testers and was reduced to 12 in late 2024. Organisation accounts are exempt.)
Once an app has been granted production access, its updates don't repeat the test — it's the launch gate, not a recurring one. Google's own guidance is in the Play Console community guide.
What counts: testers must opt in through your closed-testing link and the test must run 14 consecutive days. Google looks for genuine testing — people who keep the app installed and actually use it — not opt-in-and-vanish installs.
In Play Console → Testing → Closed testing → Testers, there are two "Copy link" buttons that look identical:
· "Join on Android" copies your store listing URL
(play.google.com/store/apps/details?id=…) — useless for opting in.
· "Join on the web" copies the real opt-in URL
(play.google.com/apps/testing/…) — this is the one your
testers need.
If your testers say the link "doesn't work" or just shows the store page, this is almost always why.
The opt-in link only works for people already on your tester list. If you chose an email list in Play Console, you have to collect every tester's Google email and paste it in by hand — which is why you see developers asking strangers to drop their Gmail addresses into public comments. Slow, error-prone, and a privacy mess.
The clean fix: create a Google Group that anyone can join, and select it as your tester list in Play Console. Now the flow is self-serve: a tester joins the group (one click), which puts them on your list, then opens your opt-in link and installs. No email collecting at all.
Friends and family — free, but finding 12 people who'll genuinely keep an app for 14 consecutive days is harder than it sounds, and a dropout can undermine your window.
Developer communities — the "test my app, I'll test yours" groups are full of devs in the same boat, but they're chaotic: ghost testers who opt in and vanish, no way to hold anyone to the 14 days, and many are run by people selling testing services.
Paid testing services — typically $15+ per app. Aside from the cost, bought testers get you into the grey zone Google's policy warns about: the programme wants genuine feedback, not purchased opt-ins.
A reciprocal exchange — developers test each other's apps, for real. Genuine use, genuine feedback, no money. This is what the closed-testing programme is actually designed to produce — the only hard part is running it properly. That's the part we automated.
1 · Post your closed test — your opt-in link, your Google Group, and a few
proof-of-use questions only someone who really used your app can answer.
2 · Members opt in until your roster of 12 is full. You can see it filling.
3 · You press Start testing — one shared 14-day countdown
begins for the whole cohort, so everyone covers the same consecutive window Google
requires. Every tester sees the days remaining on their dashboard.
4 · Testers submit structured feedback which is machine-scored — the app
owner never rates testers, so honest criticism can't be punished. Scores build a public
tester reputation.
5 · Reciprocity is enforced: you test to get tested. No install farms — anyone gaming it
is expelled for good.
It's free for founding members (the first 50 — three of the founder's own live apps are members #1–3, same rules as everyone). And once you launch, the same membership gets you into the promo exchange: members show each other's apps inside their own apps and trade verified clicks instead of paying for ads.
Is 12-for-14-days still the rule? Yes — for personal accounts created after 13 November 2023. It was 20 testers at launch, reduced to 12 in late 2024.
Do testers have to open the app daily? Google doesn't publish an exact threshold; the safe pattern is keeping the app installed for the full 14 days and genuinely using it a few times.
What if someone drops out mid-window? Recruit a spare or two above 12, and only start the clock when the roster is full — the Exchange enforces exactly this.
Is a reciprocal exchange allowed? Genuine mutual testing with real feedback is what the programme intends. What's prohibited is fake or incentivised testing — farms and bought opt-ins.