Google Play Closed Testing: The 12 Testers, 14 Days Rule Explained (2026)

If you opened a personal Google Play developer account after November 13, 2023, you can't publish your first app straight to the Play Store. Google first requires a closed test: at least 12 testers who stay opted in for at least 14 days in a row. Only then can you apply for production access, and Google reviews that application before your app can go live for everyone. This guide explains exactly who the rule applies to, how to set up the test correctly, and how to write an application that gets approved the first time.

Who has to do closed testing?

The rule is about your developer account, not the app. Once an account has been granted production access, you don't repeat the 14-day test for every future app. Organization accounts are exempt, but they need a D-U-N-S number for the business, which can take days or weeks to obtain. If you're a registered company, it's worth weighing that trade before you sign up; if you're a solo creator or freelancer, the personal account and the closed test are usually the faster path.

The requirement used to be 20 testers. Google lowered it to 12 in December 2024. The 14-day duration has not changed.

The rules, exactly as Google applies them

• At least 12 testers must be opted in to your closed test at the same time. Inviting 12 people is not enough; each one has to accept the invitation.
• Those testers must stay opted in for at least 14 consecutive days. Google's own help page is explicit: testers who opt in, test for fewer than 14 days, and then opt out don't count, and if someone leaves and rejoins, their earlier days are lost.
• Each tester is a separate Google account that joins through your opt-in link and installs the app from Google Play on a real device.
• Only after the 14 days can you click Apply for production on the Play Console dashboard.

Because the clock depends on testers staying in, recruit more than 12. Fifteen to twenty is a sensible buffer: if two people leave on day ten, you still clear the bar without restarting.

How to set up a closed test, step by step

1. 1

   Finish your store listing and app content first

   Play Console won't let you roll out a closed test until the basics are in place: app name, descriptions, icon, screenshots, privacy policy, Data safety form, content rating and target audience. Our Google Play publishing guide walks through each one.

2. 2

   Create a closed testing track

   In Play Console, go to Test and release, then Testing, then Closed testing. Use the default track (often called Alpha) or create a new one.

3. 3

   Add your testers

   Add testers either as an email list or as a Google Group. A Google Group is easier to manage: anyone who joins the group is included, and you don't have to edit the list by hand.

4. 4

   Upload your app bundle and roll out

   Create a release, upload your signed AAB, add release notes and send it for review. Closed test releases are reviewed too, so allow some time before testers can install.

5. 5

   Share the opt-in link

   Once the release is available, copy the opt-in URL from the track and send it to your testers. Each person has to open it, accept, and then install the app from Google Play.

6. 6

   Keep testers active for 14 days, then apply

   Check the Testers count in Play Console regularly. When it has shown 12 or more for 14 consecutive days, the Apply for production button becomes available on your dashboard.

Where to find 12 testers

• Friends, family and colleagues with Android phones. They're the most reliable because you can remind them to actually use the app.
• Your existing customers or email list. If your app is a version of your website, the people already using the site are ideal testers and give the most useful feedback.
• Your social media followers or a community you're part of, such as a local business group or a Discord server.
• Tester exchange communities, where developers test each other's apps. Paid tester services also exist; if you use one, make sure the testers genuinely use the app, because installs alone are not what Google is looking for.

Remember that testers need an Android device. iPhone users can't install from Google Play, so they can't count toward the 12.

What Google checks besides the numbers

Hitting 12 testers for 14 days makes you eligible to apply. It does not guarantee approval. Google's help page says it may ask for more testing if an application shows fewer than 12 opted-in testers or insufficient engagement. In practice, the applications that get sent back usually share the same problems: testers who joined on day one and never opened the app again, no updates released during the test, and vague answers on the application form.

1. 1Ask testers to use the app several times across the 14 days, not just once. Give them something specific to try: sign up, place a test order, submit a form.
2. 2Collect feedback in writing. A short form or a shared document works. You'll need concrete examples for the application.
3. 3Ship at least one or two updates during the test that respond to that feedback. If you build with Capsule, content changes on your website appear instantly, and a new build with an updated icon, splash screen or settings takes a few minutes.
4. 4Keep a simple log of what testers reported and what you changed. It makes the application easy to write.

How to answer the production access application

The form has three sections. Answer every question in full sentences with specifics; one-line answers are the most common reason applications come back.

Google says the review usually takes seven days or less, though it can take longer. You'll get an email when it's done. If Google asks for more testing, you don't lose your account or your app: keep the test running, address the feedback, and apply again.

Mistakes that reset the clock or get you rejected

• Counting invitations instead of opted-in testers. Only people who accepted the invite count.
• Removing testers or deleting the Google Group mid-test, which drops the count below 12 and breaks the 14-day streak.
• Testers who only use iPhones, emulators or duplicate accounts.
• Letting the test sit untouched for two weeks with no updates.
• Applying with short, generic answers such as "testers liked it".
• Asking for permissions the app doesn't need. Only turn on the camera, location, microphone or storage access your site actually uses.

Closed testing for an app made from your website

The rules are the same for a website app as for any other app, and in some ways a website app has it easier: your testers can be the customers who already use your site, and feedback about content or layout can be fixed on the website itself without waiting for a new build. Make sure the app feels like an app rather than a bookmark, though. A proper icon and splash screen, brand-coloured status bar, and features like a bottom tab bar or push notifications help both your testers and Google's reviewers. We cover this in detail in how to convert a website to an Android app.