You have completed your 14 days of closed testing with 12 or more opt-in testers. When you click the "Apply for production" button in your Google Play Console dashboard, you are not immediately approved. Instead, you are greeted by an extensive questionnaire asking you to justify your testing process, detail user feedback, and explain why your app is ready for global release.
Google's review team uses these written responses—combined with telemetry from your closed testing track—to decide whether to grant production access or require further testing. In this guide, we provide proven, field-tested answer templates and explain exactly what Google reviewers are looking for in each response.
The Anatomy of the Production Questionnaire
The questionnaire consists of three primary sections:
- About your testers: How you recruited them and who they are.
- Feedback received: What bugs, UX flaws, and device issues were discovered.
- Changes made & readiness: What code updates were released and why the app is production-grade.
⚠️ The #1 Rejection Mistake
Writing vague, one-sentence answers such as "Recruited friends and fixed all bugs." Reviewers reject these immediately because they look automated or unverified.
Section 1: How Did You Recruit Your Testers?
What Google Wants to See:
Google wants to verify that your testers are real human beings with diverse Android devices, not automated bot accounts. Mentioning developer communities, peer beta testing groups, or early access newsletters works best.
Winning Template:
We recruited a cohort of 15 verified Android developers and beta testers through dedicated Android developer communities, developer testing exchanges (including Testers Hub), and early access sign-up lists. All testers were onboarded through a managed Google Group and opted in via the official Google Play closed testing track link. Testers represented a diverse mix of physical Android devices (ranging from Android 11 to Android 15 across Samsung, Google Pixel, Xiaomi, and Motorola hardware) to ensure real-world compatibility across varying screen sizes and processor architectures.
Section 2: What Feedback Did You Receive During Testing?
What Google Wants to See:
No first beta build is flawless. Google wants authentic technical details: UI overflow issues, performance latency, navigation confusion, or locale formatting glitches.
Winning Template (Customize with Your App's Specifics):
During the 14-day closed testing period, our testers provided actionable feedback across three key areas: 1. UI & Layout Adjustments: Testers on smaller screen devices (e.g. 5.5-inch displays) noticed that the primary submit button overlapped with the bottom navigation bar on certain form screens. 2. Network Error Handling: Two testers encountered an unhandled timeout error when switching between Wi-Fi and mobile data during background sync. 3. Dark Mode Contrast: Testers reported that secondary metadata text had low contrast against dark backgrounds in the settings panel.
Section 3: What Changes Did You Make Based on Tester Feedback?
What Google Wants to See:
Google cross-references this answer against the App Bundles (AABs) you uploaded to the Closed Testing track. Always mention your version codes.
Winning Template:
In response to the feedback gathered, we implemented the following technical iterations during the closed testing track: • Version 1.0.1 (Build 2 - Released Day 6): Refactored the layout constraints using dynamic safe area insets to eliminate button clipping on compact devices. • Version 1.0.2 (Build 3 - Released Day 11): Implemented an exponential backoff retry mechanism for API requests to resolve network disconnects, and updated color tokens to meet WCAG AA contrast standards. All crash logs on Android Vitals are currently at 0.00% crash rate with zero ANRs reported over the final 7 days of testing.
Section 4: Why Is Your App Ready for Production?
Winning Template:
The application has undergone 14 continuous days of real-world testing with 15 active developers. We have resolved all identified edge cases, verified memory consumption under 80MB on mid-range devices, and confirmed that our backend architecture handles peak concurrent traffic seamlessly. The app is fully compliant with Google Play Developer Program policies and ready for public users.
Summary: Honesty + Specifics = Guaranteed Approval
By following these structured templates and backing them up with genuine telemetry gathered through peer testing on Testers Hub, your production track application will pass human review without unnecessary delay.
Get Real Feedback from Real Developers
Join a 15-developer testing Squad on Testers Hub and gather real bug reports to include in your questionnaire.
Download Testers Hub App ➔