Applying for Production Access After Closed Testing

Finishing your 14-day closed test doesn't publish your app automatically. You still have to apply for production access and answer a short questionnaire. This guide covers what Google asks, based on its testing requirements help article, and how to answer each part honestly using what your testers told you.

When you can apply

Once at least 12 testers have been opted in continuously for 14 days, Play Console shows an Apply for production option on your dashboard. Keep your closed test running and your testers opted in while you apply and while Google reviews.

The three sections of the application

Google groups its questions into three parts:

1. About your closed test: how you recruited testers and how they used your app.
2. About your app or game: your intended audience, the value your app provides, and how many installs you expect in the first year.
3. About your production readiness: what you changed based on the closed test and how you decided the app is ready.

Answering "About your closed test"

Google asks how easy it was to recruit testers, whether testers used all the app's features, and how their usage compares to what you expect from real users. Good answers are specific:

• Recruitment: say how you found testers (for example, "a developer tester-exchange community where testers check in daily with feedback"). Be truthful. Don't claim they are your target users if they weren't.
• Feature coverage: mention which flows you asked testers to try. On TestersZone, the testing instructions you write appear to every tester.
• Engagement evidence: summarise check-ins and feedback volume. Your app's dashboard shows check-ins per day and lets you export all feedback as CSV.

Answering "About your app or game"

• Intended audience: who the app is for and why ("students preparing for exams who want offline flashcards").
• Value: what problem it solves and how it differs from alternatives.
• Expected installs: pick a realistic range. Overstating it doesn't help.

Answering "About your production readiness"

This is where real feedback pays off. Google asks you to describe changes made because of the closed test. Go through your feedback export and list concrete fixes, for example: "Fixed a crash on rotation reported by 3 testers on Android 14", "Simplified onboarding from 4 screens to 2 after testers found it confusing", "Added dark-mode persistence." Then explain how you decided you're ready: crash-free sessions, resolved bug reports, and positive ratings.

Tip: reply to tester feedback in your TestersZone dashboard as you fix things. It creates a clear record of what changed and when. The Apply tab on your app page then drafts all three sections from your real test data, with placeholders for you to complete honestly.

Review time and what happens next

Google says review "usually takes seven days or less, but can occasionally take longer." If you're approved, the production track unlocks and you can roll out your release. If you're not approved, Google tells you, and you may need to keep testing before applying again. Keep testers engaged (see our engagement guide) so you don't have to start from zero, and follow our rejection recovery plan. Approved? Launch with a staged rollout.

Nobody, including TestersZone or paid services, can guarantee approval. Real usage and honest answers are your best chance.