Meet the published tester requirement, run a useful closed test, and prepare truthful answers about engagement, feedback, app changes, and production readiness.
Policy source: Google Play Console Help
Google states that personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for the preceding 14 days before applying for production access.
Meeting that minimum makes you eligible to apply; it does not guarantee approval. The application also asks about your closed test, app or game, and production readiness.
Google recommends clear test instructions, broad feature coverage, a feedback channel, regular feedback review, and action on relevant findings. Its public guidance does not specify mandatory daily opens, session lengths, or a hidden engagement score.
Google may require continued testing when the tester minimum or engagement is insufficient. These checks help you present a clearer testing record.
For affected personal accounts, at least 12 testers must be opted in continuously for the 14 days immediately before you apply.
Action: Check the opted-in count and continuity before applying. If a tester opts out, that tester's qualifying period is no longer continuous.
Google asks whether testers used the app's features and whether their behavior resembled expected production use.
Action: Give testers clear workflows, cover important features, and provide a simple channel for specific feedback.
The application asks you to summarize tester feedback and explain how you collected it.
Action: Keep a testing log with the affected feature, app version, observation, severity, and follow-up decision.
Google asks what changed because of the test and how you determined that the app was ready for production.
Action: Describe real fixes, retesting, stability checks, policy review, and remaining known limitations without exaggeration.
Google's published requirement applies to personal developer accounts created after November 13, 2023. Check the Dashboard in your own Play Console for the current requirement.
List the app's core journeys, important permissions, account states, error paths, and device conditions that testers should cover.
Give testers a clear feedback channel, review recurring themes, fix relevant defects, and record why each change was or was not made.
Use your real tester count, workflows, feedback, app changes, and readiness checks. Do not copy metrics or examples you did not observe.
12Testers coordinates assigned testers, practical workflows, feedback, and production-access guidance. Google makes the final decision on every application.
