When can you apply for production access?
For the personal accounts covered by the requirement, you need at least 12 continuously opted-in testers for the preceding 14 days. Check eligibility in Play Console before you apply.
Open your app’s Dashboard and choose “Apply for production” when available. The application covers your closed test, your app or game, and production readiness. This guide helps you organize your own evidence; it does not provide answers to copy.
What evidence should you gather?
| Keep a record of | Write down | Avoid |
|---|---|---|
| Recruitment | Where you found people and how they joined | Inventing a target-audience match |
| Engagement | Tasks attempted and features actually used | Turning installation counts into usage claims |
| Feedback | An issue, its impact and how you collected it | Calling a sample report your evidence |
| Changes | What you fixed and the follow-up result | Saying every problem is fixed without checking |
| Readiness | Remaining issues and your release decision | Treating time elapsed as proof of quality |
How do you describe your closed test?
Summarize what participants actually did. If a feature was not tested, say so and decide whether to test it before applying. Keep the difference between your intended test plan and observed activity clear.
An evidence note can follow this structure: task attempted; feedback received; change made; follow-up result. Leave a field blank until you have evidence instead of inventing a result.
How do you describe your app?
Explain who your app serves and the task it helps them complete. Use the actual audience and working features of the submitted build. If the application asks for an estimate, label your own estimate honestly.
Review your store listing against the current build. Remove claims for unfinished features and check that your access instructions still work.
How do you decide whether it is ready?
Use your own readiness judgment and actual fixes in the application. A service can help with testing coordination; it cannot take responsibility for your app’s compliance or answer truthfully on your behalf.
- Try the main journey with a fresh test account.
- Recheck the problems that blocked testers.
- Review remaining issues and document why they do or do not block release.
- Check your app’s disclosures, permissions and store information.
- Keep access instructions for Google’s reviewers current in Play Console.
What if Google requests more testing?
Read the explanation before deciding what to change. Google identifies insufficient tester count and engagement as reasons it may require continued testing. Resolve access problems, recruit where needed and collect evidence from the additional test.
Keep a separate note of what changed after the request. Do not submit the same generic description if the underlying test has not improved. TestPogo’s proposed campaign is time-bounded; any extension needs an agreed scope.
Common questions
Can TestPogo submit the application for me?
No. You apply from your own Play Console and remain responsible for your app and answers. TestPogo does not need administrator access.
Should I copy questionnaire answers from another app?
No. Your answers must reflect your app, testers, feedback and changes. Use a worksheet to collect facts instead of copying claims.
Is the sample feedback report usable as evidence?
No. The sample report is fictional and only illustrates a useful format. Your application needs evidence from your actual test.
Will production access be approved when the time is up?
No. Meeting the testing requirement makes you eligible to apply for production access. Google reviews your application and may ask for more testing.
Does a rejection automatically mean a refund?
No active refund promise exists while TestPogo is in prelaunch. The draft terms distinguish service delivery from Google’s independent decision.
Where can I check the official steps?
Read Google’s app testing requirements page and follow the prompts in your app’s Play Console. Its current instructions take precedence over this guide.