How to answer Google Play's production access questions
Updated October 2026
When your closed test is done, Play Console asks you to apply for production and fill in a short questionnaire. Your answers, together with the test data Google can see, decide whether you get access. Good answers are specific: real numbers, real feedback and real changes.
Questions about your closed test
- How easy was it to recruit testers? Say where they came from (friends, a developer community, a tester exchange) and how many joined, installed and stayed.
- Describe the engagement you received. Give numbers: testers active per day, total tester-days, and how long the test ran. Mention how you kept testers active.
- Summarize the feedback. Name two or three concrete themes ("sign-up was confusing", "crash when rotating the screen") and say how you collected it.
Questions about your app
- Who is the intended audience? Be specific: who they are and what problem they have.
- How does your app provide value? One or two sentences on what users can do that they couldn't before.
- How many installs do you expect in the first year? Pick an honest range. Nobody expects a big number from a new developer.
Questions about production readiness
- What changes did you make based on the test? List the fixes and improvements, and mention the builds you uploaded during the test.
- How did you decide your app is ready? Use criteria: key flows work, reported crashes are fixed, testers used it for the full period.
Example answer (engagement)
"14 testers installed the app from the closed track and used it over 15 days. On average 12 testers were active each day, for 186 tester-days in total, with around 4 minutes per session. We sent testers a short task list each week and asked them to report anything confusing. 13 testers completed the full period."
Frequently asked questions
Can I answer in my own language?
Yes, but clear, simple English is safest, because reviewers may not read your language.
How long are the answers?
Two to five sentences each is enough. Specific beats long.
What if I don't have numbers?
Then you probably need more testing. Track daily active testers and feedback before you apply.