Play Store publishing
Managed Google Play closed testing and production-access support
A managed closed test from a studio that already ships on Play. Not twelve Gmail sign-ups, and not a promise that Google will approve production.
Personal Google Play developer accounts created after 13 November 2023 cannot apply for production until a closed test has at least 12 testers opted in continuously for the preceding 14 days. The clock is per app, not once per account. Testers who never use the official opt-in link, drop out early, or only install a sideloaded APK do not count. Meeting that bar unlocks Google’s production-access questionnaire — it does not guarantee approval. Organization accounts registered with a D-U-N-S number, and personal accounts created before that cutoff, skip this gate. We run a boutique in-house panel: 15 to 18 distinct Google accounts on physical Android devices, daily engagement, replacements if someone opts out, written notes you can act on, and honest answers for the questionnaire. We also review the listing, privacy URL, and Data safety form so the test is not the only thing standing between you and review. If you need a cheap opt-in mill, we are not it. If you need a closed test that will stand up when Google asks how testers were recruited and what you fixed, we are.
What the closed-testing pass includes
- Closed testing track setup: tester emails or Google Group, countries enabled, official opt-in link
- 15 to 18 in-house testers on physical Android devices — a buffer above Google’s 12 so one dropout does not reset the 14 days
- Daily engagement on real Play Store test installs, not emulators or sideloaded APKs
- Replacement testers if someone opts out before day 14
- Written feedback notes: crashes, broken flows, and what we actually used
- Draft answers for Google’s production-access questionnaire, based on the test that ran
- Store listing, privacy policy URL, and Data safety review before you apply
- Included as a publishing milestone when we build the app — or as a standalone pass if the build already exists
How we run the 14 days
- 1
Confirm the account and the build
We check whether the 12-tester rule applies (new personal account vs organization or a pre-November 2023 personal account), then confirm the closed track, listing, privacy URL, and Data safety answers are ready before anyone opts in.
- 2
Opt the in-house panel in
Fifteen to eighteen testers — each a distinct Google account on a physical device — join through your official closed-testing link. Sideloaded APKs and internal testing do not start the clock.
- 3
Hold 14 consecutive days
Testers stay opted in and open the app on a daily protocol. If anyone drops, we replace them so the count does not fall below 12 and restart the window.
- 4
Notes, fixes, then the form
You get written notes from the test. After issues that would fail review are addressed, we draft the production-access questionnaire from what actually happened. Google still decides.
What we will not sell
- Fake installs, bots, emulator farms, or recycled accounts dressed up as testers
- A guarantee that Google will grant production access
- Advice to mis-register as an organization to skip the test
- Self-serve checkout or a live tester dashboard — we quote after a short brief, same as every other engagement
Related services
Closed testing is one step in app development and Play Store publishing. If the product is still being built, start there.
Frequently asked questions
Who has to run Google Play’s 12-tester, 14-day closed test?
Personal Play Console accounts created after 13 November 2023. You need at least 12 testers opted in to a closed test continuously for the last 14 days before you can apply for production. Organization accounts (D-U-N-S) and personal accounts created on or before that date are exempt. The requirement is per app, not once per account.
Does finishing 14 days mean Google will put the app in production?
No. It only unlocks the production-access application. Google still reviews the app, the test, and your answers. We keep testers opted in, collect real notes, and draft honest form answers. We do not sell approval.
Why 15 to 18 testers if Google asks for 12?
If a tester opts out before day 14, that person no longer counts and the consecutive window can reset. A buffer above 12 is how we keep the count stable without restarting the fortnight.
Are your testers real people on real devices?
Yes. An in-house panel of distinct Google accounts on physical Android devices, opted in through the official closed-test link. We do not use emulators, bot installs, or a high-volume farm of the same accounts across dozens of unrelated apps.
I already have a build. Can I hire only the closed test?
Yes. The standalone pass is for founders stuck on the 12-tester wall. Send the opt-in link and a short brief. If we also built the app, closed testing is a publishing milestone rather than a surprise after “the app is done.”
What does this cost?
One-time per app, quoted after we see the account type and how ready the listing is — not a public $15 checkout. Cheap mill prices buy opt-ins; this is QA labour across 14 days plus the questionnaire and listing review. We invoice as professional services, typically 50% to start the panel and 50% when the window is complete and the draft answers are delivered.
Can I skip testers by registering as an organization?
Organization Play accounts with a D-U-N-S number are exempt from this closed-testing gate. That is a real registration status for a legal entity, not a shortcut we sell. If you already have a company and the documents to match, we can tell you whether the exemption applies. We will not coach anyone to fake it.
Stuck on the 12-tester wall?
Send the closed-test opt-in link and a short brief. We usually reply within one business day with whether we can take the panel and what the pass would cover.
Talk to us