CapWrapp
Get started

Free tool · 12-tester countdown

Google Play 12 testers, 14 days: when can you publish?

With a personal Google Play developer account created after 13 November 2023, you can apply for production access once at least 12 testers have been opted in to a closed test for 14 days in a row — and Google usually answers within 7 days. Enter your testers and the day the 12th joined: this countdown gives the date, a calendar reminder, a message for testers, and draft answers for the production access request.

  • Free, no signup
  • Runs in your browser
  • Nothing stored
  • Also in the CapWrapp Toolbox
  • Updated
Which Google Play developer account do you have?

Draft answers for the production access request

Google asks these when you apply. Fill in the fields, then edit each draft with what really happened — vague answers are a common reason for a refusal.

  1. About your closed test

    How easy was it to recruit testers for your app?

    [Easy / Neither easy nor difficult / Difficult]. We invited people from [who it is for] who would really use [App name], plus friends and early users of our website. 12 testers joined the closed test.

  2. About your closed test

    Describe the engagement you received from testers during your closed test.

    12 testers stayed opted in for the full 14 days. Most of them used [App name] [several times a week] to [main task], and tried [key features]. Usage matched what we expect in production: [short sessions on weekdays / …].

  3. About your closed test

    Provide a summary of the feedback you received from testers, and how you collected it.

    We collected feedback through a feedback form we shared with every tester. Testers liked [what worked]. They reported [problems, e.g. a crash during sign-up, slow loading] and asked for [requests].

  4. About your app

    Who is the intended audience of your app?

    [App name] is for [who it is for].

  5. About your app

    Describe how your app provides value to users.

    [App name] [what the app does]. Compared with [how they do it today], it [saves time / avoids mistakes / …] because [reason].

  6. About your app

    How many installs do you expect your app to have in your first year?

    [Pick the range in Play Console — a realistic one.]

  7. Your production readiness

    What changes did you make to your app based on what you learned during your closed test?

    Based on tester feedback we [the changes you made]. We shipped these in [n] updates to the closed testing track during the test.

  8. Your production readiness

    How did you decide that your app is ready for production?

    The last builds had no crashes in Android vitals, the issues testers reported are fixed, and testers confirmed that [main task] works end to end. The store listing, Data safety form and content rating are complete.

Copy all answers

How easy was it to recruit testers for your app?
[Easy / Neither easy nor difficult / Difficult]. We invited people from [who it is for] who would really use [App name], plus friends and early users of our website. 12 testers joined the closed test.

Describe the engagement you received from testers during your closed test.
12 testers stayed opted in for the full 14 days. Most of them used [App name] [several times a week] to [main task], and tried [key features]. Usage matched what we expect in production: [short sessions on weekdays / …].

Provide a summary of the feedback you received from testers, and how you collected it.
We collected feedback through a feedback form we shared with every tester. Testers liked [what worked]. They reported [problems, e.g. a crash during sign-up, slow loading] and asked for [requests].

Who is the intended audience of your app?
[App name] is for [who it is for].

Describe how your app provides value to users.
[App name] [what the app does]. Compared with [how they do it today], it [saves time / avoids mistakes / …] because [reason].

How many installs do you expect your app to have in your first year?
[Pick the range in Play Console — a realistic one.]

What changes did you make to your app based on what you learned during your closed test?
Based on tester feedback we [the changes you made]. We shipped these in [n] updates to the closed testing track during the test.

How did you decide that your app is ready for production?
The last builds had no crashes in Android vitals, the issues testers reported are fixed, and testers confirmed that [main task] works end to end. The store listing, Data safety form and content rating are complete.

The rule in short

Google Play’s requirement
WhoPersonal developer accounts created after 13 November 2023. Organization accounts and older personal accounts are exempt.
WhatA closed test with at least 12 testers opted in. Internal testing doesn’t count.
How long14 consecutive days, with the same testers staying in.
ThenApply for production access from the Play Console dashboard. Review usually takes 7 days or less.

Source: Google’s app testing requirements for new personal developer accounts.

The timeline

  1. Day 0 — upload a build to Closed testing, add testers (an email list or a Google Group) and share the opt-in link.
  2. The day the 12th tester opts in — the 14 days start.
  3. During the test — testers use the app; ship fixes to the same track. New builds don’t reset the clock.
  4. Day 14 — apply for production access.
  5. Up to about 7 days later — Google answers. Then create the production release, which has its own review.

From the 12th tester to a live app, plan on three to four weeks.

What Google asks when you apply

The request has three parts:

  • About your closed test — how easy it was to recruit testers, how they engaged with the app, and a summary of their feedback and how you collected it.
  • About your app — who it is for, how it provides value, and how many installs you expect in the first year.
  • Your production readiness — what you changed because of the test, and how you decided the app is ready.

The countdown drafts an answer to each from what you enter. Rewrite them with what really happened: thin answers are a common reason for a refused production access request.

Keep 12 testers in

  • Recruit 15 or 16. If anyone opts out and you fall below 12, the count restarts for their replacement.
  • A tester counts once they open the opt-in link and accept — being on the email list isn’t enough.
  • Testers need a Google account, an Android phone, and to be in a country where the test is available.
  • Ask for feedback in writing, so you can quote it in the request.

The full Play Console path, from signup to production, is the Google Play submission checklist.

Where CapWrapp fits

CapWrapp builds the Android app from your GitHub repo, signs it, bumps the version code and uploads it to Google Play internal testing, so testers always get the latest build once you promote it to the closed track. The test, the request and the production release stay in Play Console, on your account. Get started free.

FAQ

Questions people ask before they ship

Do I need 12 testers to publish on Google Play?

Only with a personal developer account created after 13 November 2023. Those accounts must run a closed test with at least 12 testers opted in for 14 days in a row before they can apply for production access. Organization accounts and older personal accounts are exempt.

Do testers have to use the app every day?

Google counts testers who stay opted in for the 14 days, not daily sessions. But the production access request asks how testers engaged and what they told you, and requests with little real use are often refused. Ask testers to open the app a few times and send feedback.

Does uploading a new build reset the 14 days?

No. New builds on the closed testing track keep the clock running. What resets it is falling below 12 opted-in testers: a replacement tester starts their own 14 days. That is why it is worth recruiting 15 or 16.

Does internal testing count toward the 12 testers?

No. The requirement is a closed test. Internal testing is useful to check that the build installs, but it doesn’t count toward the 14 days.

How long does the production access review take?

Google says usually seven days or less, sometimes longer. Once approved you can create a production release, which has its own review — often a few days for a first release.

Where can I find 12 testers?

Friends, family, early users of your web app, your mailing list or community. Testers need a Google account, an Android phone, and to be in a country where the test is available. Tester-swap groups exist, but Google looks at engagement, so testers who really use the app are worth more.

Free tools

Run the next check

All free tools

From checked to shipped

CapWrapp turns your GitHub repo into iPhone and Android apps, signs every build, and ships it to TestFlight and Google Play — no Mac, no Xcode.

Get started free See how it works
  • Free to start
  • No credit card
  • Sign in with Google or GitHub