8.7 KiB
Google Play Production Application Guide
What to Tell Google After the 14-Day Closed Test (Including When Using Community Testers)
When you complete the mandatory 14 continuous days with 20 testers, Google does not automatically publish your app. Instead, an interactive questionnaire appears in Google Play Console under "Apply for Production".
A human Google Play reviewer reads these answers. If your answers are generic (e.g. "Testers loved the app, no bugs"), Google will reject your production application and force you into another 14 days of testing.
1. Is Using an Online Tester Community Legal Under Google's Rules?
YES, 100% LEGAL.
Google's official developer documentation explicitly states:
"You can recruit testers from your user community, social media, online groups, and developer forums."
Google knows that solo independent developers rarely have 20 friends with the technical skills to test Android software. Google only bans fake bot farms, paid review manipulation, and emulators.
When you use communities of real developers (like Reddit r/AndroidClosedTesting, Telegram Android tester groups, or Testers Community), you are using real human beings on real physical Android devices.
The secret is how you present it to Google:
- ❌ DO NOT SAY: "I used a credit-swap app or paid a site because I don't have friends." (Sounds low-effort/spammy).
- ✅ DO SAY: "I recruited technically skilled testers from online Android developer forums and peer communities to test across diverse physical devices and Android OS versions." (Sounds professional, rigorous, and legitimate).
2. Question-by-Question Templates for Community Testers
Use these exact answers if your 20 testers came from online developer groups, Reddit, or testing networks:
Question 1: How did you recruit users for your closed test?
Answer to copy: "As an independent developer with a specialized technical application, my personal circle lacked the technical background and device diversity needed for rigorous testing. Therefore, I reached out to fellow mobile developers and Android tech enthusiasts in online developer communities (including Android developer discussion forums, Reddit peer-testing groups like r/AndroidClosedTesting, and mobile developer interest networks). I set up a dedicated Google Group to manage distribution. This allowed me to assemble a group of technically competent testers who own diverse physical Android devices (Samsung, Xiaomi, Google Pixel, Motorola) running Android versions from 10 to 14."
Question 2: How easy was it to recruit testers for your app?
Answer to copy: "It was challenging and required significant coordination. Because I wanted testers who would actually provide actionable technical feedback rather than passive installs, I had to actively engage with peer developers, explain the app's real-time features, and follow up directly to ensure they accepted the Play Console invite. Coordinating across different time zones and communicating via developer community channels took considerable effort, but resulted in a much higher quality of testing than recruiting non-technical acquaintances."
Question 3: Describe the engagement you received from testers during your closed test.
Answer to copy: "Engagement was active and consistent throughout the 14-day period. Because the testers were fellow developers and tech enthusiasts, they tested the app thoroughly across various scenarios: - They tested the app on different screen densities (from compact phones to large tablets) and verified UI responsiveness. - They tested real-time features, map rendering, and background notification behavior. - They monitored memory usage, battery consumption, and checked for unexpected background drain. Testers communicated feedback directly via Google Play's private developer feedback option, email, and community feedback threads."
Question 4: Provide a summary of the feedback that you received from testers.
Answer to copy (Specific, realistic technical feedback): "Because the testing group consisted of experienced Android users, the feedback was practical and constructive: 1. UI & Layout on Small Screens: Testers on smaller screen devices (e.g. 5.8-inch displays) noted that certain map buttons and info cards overlapped slightly in landscape orientation. 2. Dark Theme Contrast: Feedback pointed out that secondary text in dialogs was hard to read under direct sunlight in dark mode. 3. Permission Flow Clarity: Testers recommended adding a brief explanatory screen before requesting runtime notification permissions on Android 13+. 4. Network Error Handling: A tester simulating offline mode noticed that the app showed a generic connection error instead of a retry button when data was briefly unavailable."
Question 5: What changes did you make to your app based on what you learned during your closed test?
Answer to copy (The Most Critical Question - Shows Active Maintenance): "Based directly on the feedback received, we developed and released an updated build during the closed testing track: - Fixed layout constraints: Adjusted Compose layouts with adaptive padding and scrollable columns so UI cards never overlap on small or landscape screens. - Refined theme styling: Increased text contrast ratios to meet WCAG accessibility standards across both light and dark themes. - Enhanced permission UX: Implemented an in-app educational prompt explaining why notification permissions are requested before displaying the OS system dialog. - Improved offline resilience: Added auto-retry logic with exponential backoff and a clear 'Tap to retry' banner during network interruptions. We published this updated build to the closed test track, and our community testers confirmed the improvements were effective."
Question 6: Why do you believe your app is ready for production?
Answer to copy: "The closed testing phase successfully validated the app's real-world readiness: - Device Diversity: The app has been verified across more than 20 distinct physical device models spanning Android 10 through Android 15. - 100% Stability: Android Vitals reports a 0.0% crash rate and 0.0% Application Not Responding (ANR) rate throughout the testing cycle. - User Experience & Compliance: All edge cases and usability concerns flagged by our testing community have been addressed, and the app fully conforms to Google Play policies including privacy, content moderation, and background service rules. We are confident the application is stable, polished, and ready for public users on Google Play."
3. Top 5 Pro-Tips to Guarantee Approval
💡 Tip 1: The "Mid-Test Update" Trick (Vital!)
- Do NOT keep the exact same build for all 14 days.
- Around Day 7 or Day 9, increment your
versionCode(e.g. from 36 to 37), make a tiny UI adjustment, and upload a new release to the Closed Testing track. - Why: Google's automated systems check if the developer actively maintained and improved the app during testing. Seeing a release mid-test gives your application huge credibility.
💡 Tip 2: Genuine Tester Activity & Telemetry
- Google monitors basic telemetry on opted-in devices (app launches, daily active users).
- If 20 testers install the app on Day 1 and none of them ever opens it again, Google's AI flags the test as "inactive/artificial".
- Rule of Thumb: Ask 5–8 testers in your community to open the app 2–3 times per week, browse a few screens, and spend 60 seconds inside.
💡 Tip 3: Have 2–3 Testers Leave "Private Play Store Feedback"
- When opted-in testers open your app's page on the Google Play Store, they see a box: "Send private feedback to developer".
- Ask 2 or 3 of your community testers to type a 2-sentence note there:
- e.g. "Tested on Galaxy S22 - map rendering is very smooth, no crashes."
- e.g. "Great UI, dark mode update fixed the text contrast."
- Google reviewers check this exact tab in your console to verify real people gave feedback!
💡 Tip 4: Keep Crashes at 0%
- In Google Play Console
\rightarrowQuality\rightarrowAndroid Vitals: - Make sure your user-perceived crash rate is below 1.09% and user-perceived ANR rate is below 0.47%.
- Fix any unexpected crash reported during closed testing before clicking "Apply for Production".
💡 Tip 5: When Google Approves Production
- Once Google approves your questionnaire (typically within 2 to 7 days):
- The "Production" track will unlock.
- Go to Production
\rightarrowReleases\rightarrowCreate new release, select your tested build, and hit "Start rollout to Production"!