OnTesters blog
Every article cites Google’s own Help Center for the policy and labels any figure that comes from our own campaign data. No invented statistics, no approval guarantees.
33 guides across 7 topics
The lead guide is featured above — the rest of the library follows.
Seven realistic ways to get 12 testers, ranked by dropout risk, plus why 15-16 is the number to target and how to spot a vendor approval guarantee.
What Google requires
Google Play requires 12 testers, not 20, opted in for 14 continuous days. Who the rule covers, what counts as a tester, and why applying is not approval.
Read guideTwelve testers sounds simple until one opts out on day 9. What Google counts, what it does not, and the buffer that stops a dropout costing you two weeks.
Read guideThe 2026 Play Console tester rules: the 13 November 2023 cutoff, the 20-to-12 change, the organization exemption, and eligible versus approved.
Read guideThe 20-tester rule ended on 11 December 2024. How to spot pages still citing it, why the error survives, and what chasing 20 actually costs you.
Read guideClosed testing is the only track that counts toward production access. How internal, closed and open testing differ, and the setup order that avoids delays.
Read guideSetup takes about fifteen minutes. The delays come from the opt-in link that does not exist until your app is Published, and the Google Group prerequisite.
Read guideNo. Internal testing is capped at 100 testers and does not satisfy the closed testing requirement. What each Play Console track is actually for.
Read guideThe decisive difference is not visibility, it is availability: open testing unlocks only after you gain production access, so it cannot qualify you.
Read guideThe rule is 14 consecutive days at 12 or more opted in, not 14 days of testing in total. What breaks continuity, what does not, and why 15-16 beats 12.
Read guideOne opt-out drops your count immediately. How to tell whether you can still apply, when to replace the tester, and how to prevent the next one.
Read guideFourteen days of testing is fixed, and Google says review usually takes seven days or less. What varies is recruitment, and that is where timelines slip.
Read guideFive channels assessed on what decides your outcome: whether testers are still opted in on day 12. Costs, dropout risk, and why the target is 15-16.
Read guideYou are not buying twelve installs, you are buying twelve people still opted in on day 12. Six questions that separate a managed pool from a seat reseller.
Read guideSwap threads are the cheapest route to 12 testers and the least reliable way to stay above 12. What goes wrong, why reciprocity expires, and how to use them.
Read guideCommunities differ enormously in whether anyone is still there on day 12. How to assess one in twenty minutes, plus the signals that predict retention.
Read guideEvery service sells 12 testers for 14 days. The differences live in dropouts, device reality and feedback — plus the three claims to discount on sight.
Read guideEleven questions to ask before paying a closed testing service, with the answers that should give you confidence and the ones that should end the call.
Read guideThe gig delivers twelve installs. The problem is day 8 to day 14. Why the failure is structural rather than a matter of picking a better seller.
Read guideFinishing 12 testers over 14 days unlocks the Apply button — it does not approve your app. What Google still reviews, and how the outcome is decided.
Read guideWhere the button lives, what the three application sections ask, how to write answers that describe a real test, and the policy checks Google expects.
Read guideGoogle names two reasons for this outcome, and both are fixable: fewer than 12 opted-in testers, or insufficient engagement. How to tell which applies.
Read guideYou completed the window and it still did not go through. Four things to check in order, when to contact support, and why the fix is engagement.
Read guideA new personal account has to clear more than the 12-tester rule: device verification, app setup, content rating and policy. The full gate list.
Read guideYes, organization accounts are exempt from closed testing. But becoming one needs a real business, and faking it trades a two-week delay for account risk.
Read guideTwo separate gates that get treated as one. Verification confirms you have an Android device; closed testing needs 12 testers for 14 days. Neither substitutes.
Read guideThe requirement is written per app, so each app needs its own closed test and 14-day window. The testers can be the same people — they opt in again.
Read guideYes, the same people can test every app you publish, but each app needs its own opt-in and its own 14 continuous days. How to run repeat windows.
Read guideFour things make someone count: an opt-in through the link, their own Google account, a real device, 14 continuous days. Everything else is a myth.
Read guideNo. Emulator installs inflate a tester count and cannot produce a genuine closed test. Why the risk is asymmetric, and what to use emulators for instead.
Read guideYes, and Google names personal networks as the most common route. Three constraints to plan around: household clustering, soft feedback, and network size.
Read guideThe rule is identical in India: 12 testers, 14 continuous days, real devices. What differs is device mix, time zones and how you pay for a tester pool.
Read guideThe real-device requirement is global, so the question is how a vendor meets it. Five checks, two common failure modes, and the questions to ask first.
Read guideBrowse by topic
Recruitment, Play Console setup, the 14-day window and the production access application each have their own cluster. Start with the one that is actually blocking you.
Need testers who stay opted in for the full 14 days?
OnTesters provides 12 real testers on physical Android devices, with replacements for dropouts and free retesting if Google asks for more testing. From $14.99.
We do not sell or guarantee production access