App Store Without a Mac

Google Play’s Closed Testing Rule for New Accounts: 12 Testers, 14 Days, Explained (2026)

Who Google’s 12-tester, 14-day closed test applies to, how to set it up, how to find testers who stay opted in, and what the production access form asks.

Floot ·

Key Takeaways

  • It applies to personal accounts created after November 13, 2023. Organization accounts aren’t covered by Google’s page on this requirement. Personal accounts must meet it before Production is unlocked.
  • The rule is 12 testers, opted in continuously for at least 14 days. A tester who opts out and back in restarts their own count. Testers who leave before 14 days don’t count.
  • Then you apply, and Google reviews. After the test you answer three sets of questions in Play Console. Google says review usually takes seven days or less.
  • Budget about three weeks, so start early. 14 days of testing plus up to 7 days of review is about three weeks by our arithmetic, before your app’s own review.
  • Engagement matters, not just headcount. Google may ask you to keep testing if tester engagement was too low, so give testers real tasks and collect feedback.

Quick-Start Prioritization Framework

StepWhenWhat to do
Recruit 15 to 20 testersWhile you buildFriends, customers, a community; collect Gmail or Google Account addresses
Create a closed testing trackFirst testable buildAdd testers by email list or Google Group; publish the track
Share the opt-in linkOnce the track shows PublishedEach tester opts in and installs from Play
Run the test14 consecutive days minimumSend tasks, collect feedback, ship fixes
Apply for productionDay 15 or laterAnswer the three-part form on the Play Console dashboard
Wait for reviewUsually up to 7 daysThen release to production as normal

If you created a personal Google Play developer account after November 13, 2023, you can’t publish your first Android app straight to the public. Google first asks for a closed test with at least 12 testers who stay opted in for 14 days in a row, followed by an application for production access. For a first-time developer this adds roughly three weeks, and it catches many people by surprise right when they think they’re done. This guide explains exactly what Google requires, how to set the test up, how to recruit testers who count, and how to answer the production access questions.

What the rule says, exactly

Google’s Play Console Help page on testing requirements says that developers with personal accounts created after November 13, 2023 must run a closed test with “a minimum of 12 testers who have been opted in continuously for at least 14 days” before they can apply for production access. Until then, Production and Pre-registration are disabled in Play Console. Open testing also only becomes available after you get production access.

The original requirement was 20 testers. Android Authority reported in December 2024 that Google cut it to 12, with the 14-day period unchanged. Older tutorials still mention 20.

What “continuously” means

Google spells this out. Testers who opt in, test for less than 14 days and then opt out don’t count. If a tester opts out and opts back in, their 14 days must be consecutive. So the safest reading is: at the moment you apply, at least 12 people should have been opted in, without a break, for 14 days or more.

Who it doesn’t apply to

The requirement is scoped to personal accounts. Google’s page doesn’t apply it to organization accounts, which need a D-U-N-S number to create. Accounts created before November 13, 2023 aren’t covered either. Google’s account-type page also says organization accounts are required for some kinds of apps, such as financial services, health, VPN and government apps.

Why Google added it

Google frames the rule as a way to help new developers ship apps that work, and its page is full of testing advice: recruit a diverse group that matches your audience, give clear instructions, ask testers to use as many features as possible, and act on feedback. It also warns that “submitting non-compliant apps expecting reviewers to identify issues leads to rejections.”

Whatever you think of the rule, it rewards the same thing that gets apps approved on both stores: a finished, tested app. Treat the 14 days as real testing time rather than a waiting room, and you’ll get more out of it.

Setting up the closed test

You need a Play developer account (US$25, one time), an app created in Play Console, and an Android App Bundle to upload. Personal accounts also have to verify access to an Android device using the Play Console mobile app before publishing.

1. Create a closed testing track

In Play Console, open your app’s closed testing page and create a track (or use the default one). Upload your build to it and fill in the release notes. You can run several closed tests at once, but for the requirement, keep it simple with one.

2. Add testers by email list or Google Group

Google’s testing page gives two ways. Email lists suit small groups: up to 2,000 testers per list, up to 50 lists per track and 200 per account. Google Groups have no size limit, but testers must join the group before they can opt in. For a 12-to-20-person test, an email list is easiest. Testers need a Google Account, usually the one signed in to Play on their Android phone.

3. Publish the track and share the opt-in link

The opt-in link only appears once the track’s status is Published; drafts and builds pending review have no link. That first publication goes through Google’s review, so allow time for it. Every tester must open the link, accept the invitation and then install the app from Play. Being on the email list alone isn’t opting in.

4. Check the count

Keep your own list of who has confirmed they opted in and installed, and on which day. Ask on day one and again a few days in. If you’re under 12, fix it immediately, because each new tester starts their own 14 days from the day they opt in.

Finding testers who actually stay

Getting 12 names is easy. Keeping 12 people opted in for two weeks, on Android phones, with some genuine use, is the hard part. Many people you know will have iPhones, which can’t install a Play test build.

Recruit more than you need

Aim for 15 to 20. Some people never click the link, some uninstall, and some turn out to have an iPhone. A cushion of a few extra testers means one dropout doesn’t restart your clock.

Where testers come from

Google suggests personal and professional networks, communities and social media. The best testers are people who would use the app anyway: existing customers, members of a club the app serves, colleagues in the industry. For a gym app, that’s ten regulars and a couple of trainers. They’ll use it for real, and their feedback will be useful.

There are paid services and tester-swap groups that offer opted-in testers. Google’s page doesn’t mention them. Testers who install and never open the app may satisfy the count but not the engagement Google says it looks at, so treat them as a last resort.

Give them something to do

Send a short message on day one with three or four tasks, such as “create an account, book a class, cancel it, and tell us what was confusing.” Send a new task or a new build every few days. Give testers a single place to reply, such as an email address or a group chat, as Google recommends. Keep a simple log of feedback and what you changed; you’ll need it for the application.

Applying for production access

Once the criteria are met, the Play Console dashboard shows an Apply for production option. The form has three sections, and you need to press Next or Apply to save each one; leaving the page loses your answers.

SectionWhat Google asksHow to answer well
About your closed testHow easy recruiting was, whether testers used all features, whether use matched expected production use, feedback summary and how you collected itBe specific: number of testers, what they tested, two or three real pieces of feedback
About your app or gameTarget audience, value proposition, expected installs in the first yearPlain and honest; Google says these answers aren’t public and don’t affect eligibility
About your production readinessWhat you changed based on testing, how you decided it was readyList the actual fixes and improvements, with the build where each shipped

How long review takes, and what if it fails

Google says review of the application usually takes “seven days or less, but can occasionally take longer.” If Google isn’t satisfied, its page says you may need to keep running the closed test, for example because you had fewer than 12 opted-in testers or engagement was too low. Keep the test running while you wait, so you’re not starting from zero if that happens.

After you’re approved

Production unlocks. You still upload a production release, which goes through Google’s normal app review. Google’s publishing page says some reviews can take up to seven days or longer in exceptional cases. Your store listing, Data safety form, privacy policy and content rating all need to be complete before you can publish.

A realistic timeline

Here is a worked example for a personal account. The dates are illustrative arithmetic, not Google’s guarantees.

DayMilestone
Day 0First build uploaded to closed testing; track submitted for review
Day 1 to 2Track published; opt-in link sent to 18 testers
Day 315 testers opted in; clock starts for each from their own opt-in day
Day 17The 12th tester to opt in reaches 14 days; apply for production
Day 17 to 24Production access review (usually seven days or less)
Day 24 to 31Production release reviewed and live

Common mistakes

These are the patterns that most often add weeks.

  • Starting the closed test after the app is finished, instead of with the first usable build.
  • Recruiting exactly 12 testers, then losing one on day 10.
  • Inviting people who use iPhones.
  • Assuming that adding someone to the email list counts; each tester must open the opt-in link and accept.
  • Letting testers opt out and back in, which restarts their 14 days.
  • Writing one-line, generic answers in the production access form.
  • Stopping the test while the application is under review.
  • Using an organization’s app under a personal account when Google requires an organization account for that category.

If you’d rather not do this yourself

The 14-day test is Google’s rule for your account, so no tool can skip it. A builder can remove the build and upload work around it. Floot, for example, builds the Android app from the same app as your web version and submits it to Google Play with your developer account (connecting Google Play needs a paid Floot plan), so you can spend the two weeks on testers and feedback.

Frequently Asked Questions

Do I need 12 or 20 testers for Google Play?

12. The requirement started at 20 testers and was reduced to 12 in December 2024. Testers must be opted in continuously for at least 14 days.

Does the closed testing rule apply to organization accounts?

Google’s page applies it to personal developer accounts created after November 13, 2023. It doesn’t apply the rule to organization accounts, which require a D-U-N-S number to create.

Can testers use an iPhone?

No. Closed testing installs the app from Google Play, so testers need an Android device signed in with the Google Account you invited.

Do testers have to use the app every day?

Google’s requirement is that they stay opted in for 14 consecutive days. It doesn’t set a daily usage rule, but it says production access may be refused if engagement was too low, so ask testers to use the app for real.

Can I update the app during the closed test?

Yes. Google’s own tips are to fix bugs during the test, and the production access form asks what you changed based on testing. Upload new builds to the same closed track and list those fixes in your application.

How much does a Google Play developer account cost?

US$25, paid once. Google doesn’t accept prepaid cards, and may ask for a government ID and a card in your legal name during verification.

Sources