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

> When can you publish on Google Play? Count down the 12-tester, 14-day closed test, get a calendar reminder, and draft your production access answers.

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.

- Tool: 12-tester countdown. Input: Enter a date. Free, no signup. Runs entirely in the browser; nothing is uploaded.
- Interactive version: https://capwr.app/free-tools/google-play-12-testers
- All free tools: https://capwr.app/free-tools
- Last updated: 2026-10-14

## The rule in short

| | Google Play’s requirement |
| --- | --- |
| Who | Personal developer accounts created after 13 November 2023. Organization accounts and older personal accounts are exempt. |
| What | A **closed** test with at least 12 testers opted in. Internal testing doesn’t count. |
| How long | 14 consecutive days, with the same testers staying in. |
| Then | Apply 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](https://support.google.com/googleplay/android-developer/answer/14151465).

## 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](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied).

## 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](https://capwr.app/guides/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](https://capwr.app/login).

## FAQ

### 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.

## Related free tools

- [Is your Lovable app ready for the App Store?](https://capwr.app/free-tools/lovable-capacitor-checker) — Paste package.json. See what is set up, what is missing, and get a prompt to paste back into Lovable.
- [Is your Bolt app ready for the App Store?](https://capwr.app/free-tools/bolt-capacitor-checker) — Same checks as the Lovable checker, tuned for Bolt’s Vite projects and Next.js templates.
- [Is your Base44 app ready for the App Store?](https://capwr.app/free-tools/base44-capacitor-checker) — Check a Base44 export: the frontend Capacitor wraps, the backend that stays hosted, and common setup mistakes.
- [Can this GitHub repo become an iPhone and Android app?](https://capwr.app/free-tools/github-repo-checker) — Paste a public repo URL. The same checks as the builder checkers, read straight from GitHub.
- [Capacitor appId and bundle ID validator](https://capwr.app/free-tools/capacitor-config-validator) — Check an appId against Apple and Android rules at once, plus webDir and server.url in capacitor.config.
- [Do you need a Mac to publish an iPhone app?](https://capwr.app/free-tools/do-i-need-a-mac) — Three questions. What you need for TestFlight and Google Play — accounts, costs, and whether a Mac is one of them.
- [Will Apple reject your app as just a website?](https://capwr.app/free-tools/apple-guideline-4-2) — Six questions on Apple’s Minimum Functionality rule — the usual reason wrapped web apps get rejected.
- [Why was my app rejected by Apple or Google Play?](https://capwr.app/free-tools/app-store-rejection-explainer) — Paste the rejection. Get the guideline in plain English, the fix, a reply for App Review, and a prompt for Lovable or Cursor.
- [App icon generator for iPhone and Android](https://capwr.app/free-tools/app-icon-generator) — Drop a logo or type an emoji. Get the iOS 1024 icon, Android adaptive and round icons, and both store icons — in Capacitor’s folders.
- [Why did my iOS or Android build fail?](https://capwr.app/free-tools/build-error-explainer) — Paste a failed build or upload log. Get the known error, what it means, and how to fix it — signing, versions, Gradle, uploads.
- [App Store and Google Play screenshot sizes](https://capwr.app/free-tools/app-store-screenshot-sizes) — Drop screenshots, see which store slots they fit, and export the missing sizes as PNGs both stores accept.

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)