Google Play Closed Testing Before Production

Streak is a habit app on a personal Google Play account created after November 13, 2023. The check-in works on your phone. Production is still disabled, and so is pre-registration. Play will not let that account publish to the public store until a closed test has at least 12 testers who have been opted in continuously for the 14 days before you apply. This is not a suggestion. It is the gate on the dashboard.

The rule is in Play’s testing requirements for new personal accounts . How you build the tester list is in the closed test setup article . iOS does not use this 12-person clock. The parallel private beta there is TestFlight external testing. Do not paste one store’s caps into the other.

Who the 14-day rule applies to

The article is about personal developer accounts created after November 13, 2023. Those accounts must run a closed test before the app can be eligible for production. At least 12 testers must be opted in when you apply, and they must have been opted in continuously for the preceding 14 days. When you apply, you answer questions about the app, the test, and whether you are ready for production. Play says review usually takes seven days or less, and can take longer.

Until you meet the requirement, Production and Pre-registration stay disabled. Open testing becomes available after you have production access. An organization account or an older personal account is not this article’s mandatory clock, but Play still tells everyone to test before a public release. If Streak’s account is the new personal kind, do not announce a store URL. The console will not let you complete the announcement.

Opt-out resets the person, not the idea

Play is explicit. Testers who opt in, stay fewer than 14 days, and opt out do not count. If they opt out and later opt in again, the 14 days must be consecutive. A tester who misses day 9 and rejoins on day 10 starts that personal clock over. Your other testers keep the days they already earned. The requirement is 12 people who each have an unbroken 14 days at the moment you apply, not an average and not a pile of weekend installs.

Tell them that before they opt in. Play’s own testing guidance says to inform testers they need to stay opted in continuously for at least 14 days. A habit app is a decent fit for that sentence: the test is the product. Ask them to check in on the days they would actually use Streak. If they only install and vanish, you may meet a headcount and still get sent back for weak engagement. The apply form asks how testing went. “Twelve friends installed” is a thin answer.

Email lists and Google Groups

Closed tests target people by email list or Google Group. The production rule is still 12 testers opted in for 14 consecutive days, which an internal track does not satisfy.

Internal testing feels faster and does not count

An internal test can go out quickly, including before the app is fully configured, to up to 100 testers. Play recommends it before a closed test. It is the wrong track for the production application. The dashboard wants a closed test. If you only ever publish internal builds, the 14-day counter you care about never starts. Run internal until the check-in does not crash, then move the same people, if they agree, onto the closed track and restart the conversation about staying opted in.

The first time you publish a test, the opt-in link can take several hours to work. Warn the 12. A tester who cannot opt in on night one is not failing you. A tester who opts in, gets bored, and leaves on day 6 is resetting their own clock. Keep a simple record of who is still in. You will summarize feedback when you apply. Play says that summary is part of the application.

What you apply with

When the 12 people have stayed in, open the dashboard and apply for production. The form has sections about the closed test, the app, and production readiness. You describe what testers did and whether that looked like real use. If Play says you need more testing, the usual reasons include fewer than 12 opted-in testers or weak engagement. Keep the closed test running while you fix what they reported. Play also says you are responsible for policy compliance before you apply. Review is not a debugging service.

After approval you can open Production and, if you want it, open testing. Pre-registration becomes possible too. That campaign is a different job, with a 90-day limit, covered in the pre-registration guide. A staged rollout is how you release a production bundle gradually. It comes after this gate, not instead of it. The launch checklist is the listing work you should not skip while the 14 days run.

Use the 14 days as the product test

Streak’s whole point is showing up on ordinary days. Ask each tester to check in the way a stranger would: one habit, a reminder, a miss, a return. Write down what confused them. You need that story for the application, and you need it because a habit app that only the developer can operate will collect bad ratings the week production opens. Fix the reminder during the closed test. The listing screenshots should be the check-in they used, not a concept frame.

AppGrowthKit can frame that check-in once the screen is stable. Do not spend the 14 days on screenshot concepts while testers are dropping out. Data safety and the content rating still have to be true before the public listing. Closed testing does not waive them. A feedback URL or email on the opt-in page is required so testers know where notes go. Put a real inbox there.