How to answer Google Play's production access questions

After 14 days with 12+ opted-in testers, Play Console lets you apply for production. The form asks about your closed test, your app and whether it is ready. Short, vague answers are a common reason for rejection. Here is how to write good ones.

1. About your closed test

Google wants to know how you recruited testers and how easy it was. Be concrete.

Example: "We recruited 17 testers through TestPass, a community of Android users who test apps daily. Testers joined our Google Group and installed from the Play opt-in link. Recruitment took two days."

2. How testers engaged with your app

Describe what testers actually did, with numbers if you have them.

Example: "Testers used the app on 11 different phone models (Android 11–15) for an average of 6 minutes a day. We received 180 written feedback entries and 9 bug reports with screenshots."

3. Feedback you received and what you changed

This is the most important part. List 2–4 specific issues and the fix.

Example: "Testers reported the back button closed the app from Settings (fixed in v1.0.3), that the sign-up form was confusing on small screens (redesigned in v1.0.4) and requested a dark theme (added in v1.0.5)."

4. About your app

Explain who it is for and what makes it useful. Mention the target audience and the main features in two or three sentences.

5. Production readiness

Say what you did to get ready: crash fixes, performance work, store listing, privacy policy, data safety form. If you plan more updates, say so.

Common reasons for rejection

• Testers did not really use the app (very few sessions).
• No changes made during the test.
• Answers that are copied, generic or one line long.

If you are rejected, Google lets you keep testing and apply again. Use the extra time to collect more feedback and ship another update.

TestPass's dashboard includes an answer helper that fills these sections with your real numbers and feedback — you edit, then paste.