How to answer Google Play’s production access questions

Part 1: About your closed test

• How easy was it to recruit testers? Say where they came from, for example a developer community, your Google Group or friends.
• Did testers use all the features? Name the main features and which ones got the most use.
• Did usage match what you expect in production? Note any differences, such as testers using it less often than real users would.
• Summarize the feedback and how you collected it. List the top themes, like onboarding confusion or a crash on one device.

Part 2: About your app

• Who is the intended audience? Be specific, not “everyone”.
• How does the app provide value? One or two sentences about the problem it solves.
• How many installs do you expect in the first year? Pick a realistic range.

Part 3: About your production readiness

• What changes did you make based on testing? List the real fixes from your updates during the test. This is why shipping updates during the 14 days matters.
• How did you decide the app is ready? Mention that the main flows work without blocking bugs and the feedback themes were addressed.

Tips for a strong application

• Keep notes during the test: who joined, what they said, what you fixed and when.
• Ship at least two small updates during the test.
• Run the pre-launch report and fix crashes before applying.
• If your app needs a login, give Google working test credentials in App access.

Dozenship keeps your testers, feedback and timeline in one place, so these answers are easy to write from real data.