Closed Testing (12 testers, 14 days)

This is the single step that stops most first-time Android developers from ever launching. It's not a coding problem — it's a Google Play rule. Understand it, start it early, and it's easy.

The rule: every new personal Google Play Developer account must run a closed test with at least 12 testers opted in for 14 continuous days before it can apply for production access. The clock only counts days where you have 12+ opted-in testers. There's no way around it — but there's an easy way through it.

This page is the how-to. For where it sits in the whole timeline, see the Launch Roadmap.

Why it exists

Google added this in late 2023 to cut spam and low-quality apps from new accounts. It applies to personal developer accounts (organisation accounts skip it but need a harder-to-get D-U-N-S number). For a first app, personal is normal — you just budget ~3 weeks: build → closed test → 14-day wait → apply for production → review → live.

Step 1 — Upload a build to the closed track

When the command asks which track, choose Closed testing (not Internal, not Production). This is the build your testers will install. You can keep pushing updates to this track during the 14 days — the clock doesn't reset.

Step 2 — Make a testers list (use a Google Group)

Don't add 12 emails by hand and re-edit them forever. Use one Google Group as your tester list — add/remove people in the group, and Play always sees the current members.

1. Create a Google Group at groups.google.com (e.g. myapp-testers@googlegroups.com). Set "Who can join" so your testers can join easily.
2. In Play Console → your app → Testing → Closed testing → your track → Testers, add the Google Group email as the tester list.
3. Anyone in that group is now a tester. Manage testers by managing the group.

Step 3 — Get your 12 testers (the actual hard part)

You need 12 real Google accounts that opt in and install. Options, best first:

• A cohort / tester pool (easiest). If you're in the ShipKaro Weekend cohort, everyone shares one tester Google Group — each person adds that group, so all 12+ are instant. Any group of builders can do this: pool into one shared group and you all clear the requirement together.
• Friends + family. 12 people with Android phones (or even just Google accounts) who'll tap one link. Make it dead simple for them (Step 4).
• Tester-exchange communities. Subreddits like r/androidtesting, Google's tester community groups, and "I'll test yours if you test mine" threads. Be a good citizen — test others' apps too.

They must be real, distinct Google accounts, opted in via the link, with the app installed. Your own developer account doesn't count.

Step 4 — Testers opt in + install

Each tester does this once:

1. You share the opt-in URL (Play Console → Closed testing track → Testers → Copy link).
2. They open it on their phone (signed into the Google account that's in the group), tap Become a tester, then Download it on Google Play → install.

Tell them exactly that in one message — most "lost testers" are people who joined the group but never opened the opt-in link or never installed.

Step 5 — The 14-day clock

• The clock counts continuous days with 12+ opted-in testers. Get all 12 opted in on day 1 so the clock starts immediately — not day 8 when the last person finally installs.
• Testers must stay opted in for the whole window. If someone leaves the group or uninstalls and you drop below 12, you can fall out of the eligible window.
• Keep the build live on the track the whole time.

Step 6 — Apply for production

After 14 continuous days with 12+ testers, Play Console shows a prompt to apply for production access (Testing → Closed testing, or the Dashboard). Fill the short form (who tested, what feedback you got). Google reviews it — usually a few days — then you can publish to Production.

Don't idle during the 14 days

The wait is free build time. Use it (see Launch Roadmap → Phase 4): /kit-generate-screenshots, /kit-generate-aso, /kit-generate-legal, /kit-generate-landing, /kit-plan-release-analytics — and fix the top issues your testers report.

Common mistakes

• ❌ Uploading to Internal testing and expecting it to count — it must be Closed.
• ❌ Counting your own account or duplicate accounts as testers.
• ❌ Adding testers late, so the 14-day clock starts a week behind.
• ❌ Letting testers drop below 12 mid-window.
• ❌ Re-uploading a build without bumping versionCode — Play rejects a version code already used on any track, including this one. /kit-publish-to-play bumps it for you before each build; if you build by hand, increment versionCode in app/build.gradle.kts every time.
• ❌ Forgetting to actually apply for production after 14 days — it's not automatic.

Next: Launch Roadmap · Upload to Google Play.