You've made it through 14 days of closed testing with 12+ testers. Now comes the part most guides skip: the Google Play production access application. This guide covers exactly what Google asks, what they're looking for in your answers, and how to get approved on the first try.
What Is Google Play Production Access?
Production access is Google's permission to make your app publicly available on the Google Play Store. Without it, your app can only be accessed by testers on your internal or closed testing tracks. Google introduced the production access application process to add a manual review layer for new developer accounts.
The process involves:
- Confirming your closed testing is complete (Play Console verifies this automatically)
- Answering three essay questions about your testing experience
- Google's team reviewing your application (3-7 business days)
- Receiving approval (or rejection with feedback) via email and Play Console notification
The Three Production Access Questions
Google asks these three questions in the production access form. You must answer all three with substantive, data-backed responses.
Question 1: What Did You Learn From Your Closed Testing?
Google wants to know that you actually used the testing period to learn something about your app. Generic answers ("it worked fine," "users liked it") will not pass. Strong answers include:
- Specific bugs you discovered and fixed (e.g., "We found that on Android 12 devices, the login button was unresponsive in landscape mode — fixed in v1.2")
- Performance issues identified (e.g., "Loading time on first launch was 4.2 seconds — optimized to 1.8 seconds")
- UI/UX feedback from testers (e.g., "5 of 25 testers found the onboarding confusing — we added a progress indicator")
- Feature gaps (e.g., "Testers requested a dark mode option — we added it in v1.3")
Question 2: How Did You Gather Feedback from Testers?
Explain your feedback collection method. Examples:
- In-app feedback form or rating prompt
- Email surveys sent to opted-in testers
- Google Play Console's built-in review system for testing tracks
- Direct communication via Telegram, Discord, or email group
- Engagement logs and crash analytics (Firebase Crashlytics, Android Vitals)
If you used TestLaunch Pro, your feedback report includes engagement logs, interaction frequency, and session data that you can reference directly.
Question 3: What Changes Did You Make Based on Testing?
List specific changes made as a result of tester feedback. Be concrete:
- Version numbers and what changed in each
- Bugs fixed with before/after context
- Features added or modified
- Performance improvements with metrics
- UI changes based on usability feedback
What Gets Applications Rejected
- Generic answers — "Testers were happy" or "No major issues" without specifics
- Inconsistent tester counts — Claiming 50 testers when Play Console shows 12
- App policy violations — Metadata, permissions, or content issues found during review
- No real testing evidence — Google can see engagement data and will flag applications that don't match
What Happens After You Submit
Google sends a confirmation email that your application was received. Review typically takes 3-7 business days. You'll receive an email notification and a Play Console notification with the decision.
If rejected, Google provides feedback on what needs to change. You can reapply after addressing the issues — there is no limit on reapplication attempts.
After Approval: Going Live
Once approved, you can release to production. In Play Console:
- Go to Production → Create new release
- Upload your production-ready AAB
- Write release notes
- Choose rollout percentage (start at 10-20% if you want a staged rollout, or 100% to go fully live)
- Click Review and rollout
Google Play typically reviews production releases within a few hours to 1 day for apps from newly approved accounts.