Guide
Apply for production access
Do this after the 14 days of testing — we recommend day 15.
02After 14 days
Ten questions, answered honestly.
In Play Console, open Dashboard and choose Apply for production. Google asks about your closed test, your app and its readiness. Use these examples as a starting point — replace the [highlighted] parts and keep every answer true.
- 01Written answer
How did you recruit users for your closed test?
Describe how you actually recruited testers. Only mention friends or colleagues if you really invited them.
Example answer
We used a closed-testing service that provides 12+ testers on real Android devices. We added their Google Group to our closed testing track and kept the build available for 14 continuous days. [Optional: We also invited a few colleagues and friends to try the app.]
- 02Multiple choice
How easy or difficult was it to recruit testers?
Choose the option that honestly matches your experience.
Select the option in Play Console — no text to write. - 03Written answer
Describe the engagement you received from testers during your closed test.
Name your app's real features so the answer is specific.
Example answer
Testers installed the app on their own devices and kept it installed for the 14-day test. [Describe what you saw, e.g. sessions in your analytics or Play Console statistics]. They used features such as [feature 1] and [feature 2]. [Feedback they shared, if any].
- 04Written answer
Provide a summary of the feedback you received from testers.
If testers found bugs, mention them and say what you did about them.
Example answer
[Summary of the feedback you actually received, or: We received little written feedback.] [Issues testers reported, if any.] We reviewed [Android vitals / the pre-launch report / crash reports] during testing and found [your findings].
- 05Written answer
Who is the intended audience of your app?
Describe your real target users — not the testers' country.
Example answer
[Age group, e.g. adults 18+] in [countries or 'worldwide'] who want to [problem your app solves].
- 06Written answer
Describe how your app provides value to users.
Two or three clear sentences are enough.
Example answer
[App name] helps users [main goal] by [how it works]. Key features include [feature 1], [feature 2] and [feature 3].
- 07Multiple choice
How many installs do you expect your app to have in its first year?
Pick a realistic range. A modest estimate is fine for a new app.
Select the option in Play Console — no text to write. - 08Written answer
What changes did you make to your app based on what you learned during your closed test?
Small, concrete changes are better than 'none'.
Example answer
Based on tester feedback we [fixed / improved / adjusted] [specific change]. [If nothing major: Testers did not report blocking issues, so we made minor polish to (screen or feature).]
- 09Written answer
How did you decide that your app is ready for production?
Refer to what you actually checked.
Example answer
The app completed a 14-day closed test with 12+ testers on real devices. [What you checked, e.g. Android vitals, the pre-launch report, crash reports] showed [your findings], and we addressed [feedback or fixes].
- 10Written answer
What did you do differently this time? (only shown after a rejection)
Only appears if a previous application was not approved.
Example answer
We ran a full 14-day closed test with active testers on real devices, addressed the feedback from the previous review — [what you changed] — and re-checked the app's stability before applying again.
Got Google's decision?
Report it on your tracking page by day 20. No decision yet? Report “Not approved yet” before the deadline to keep your guarantee — you can change it later.