The 14-day closed test is done. The button is finally there. Now what?
The production-access application is not a victory lap. It is a short review of whether your test was real, what you learned, and whether the app is ready for a wider audience.
Where to find it
In Play Console, go to Production → Apply for access. The page shows a checklist. The closed-testing item should be complete before you can apply.
If the button is still locked, check:
- the tester count;
- the continuous 14-day window;
- any policy or account warnings;
- whether the app is on the correct track.
What Google asks
The exact questions can change, but the themes are consistent:
- What did you test? The core flows, the target audience, and the scope of the closed test.
- Who were your testers? How many, how they were recruited, and how they were engaged.
- What did you learn? The feedback you received and what you changed.
- Is the app ready? Whether the app is functional, compliant, and prepared for production.
You do not need to write an essay. You need to be specific and honest.
How to answer well
Describe the test, not the app's feature list
“We tested onboarding, account creation, the main dashboard, and the payment flow with 14 testers over 14 days” is more useful than “we tested the app.”
Mention the feedback loop
Google wants to see that testing led to change. For example:
- testers found a confusing permission prompt, so we moved it later in onboarding;
- three testers hit a crash on a specific device, so we fixed it in build 1.4;
- testers said the empty state was unclear, so we added guidance.
Be honest about what you did not test
If you did not test a feature, say so. A believable answer is better than a perfect-sounding one.
Do not overclaim
Do not say you had 50 testers if you had 14. Do not say every tester used the app daily if they did not. Reviewers can see the test data.
A simple structure
You can use this as a starting point:
We ran a closed test with 14 testers from [countries] between [dates]. Testers installed the app from the closed track and were asked to complete onboarding, the main workflow, and the settings flow. We collected feedback through a short form and a WhatsApp group. The main issues were [issue 1], [issue 2], and [issue 3]. We fixed [fixes] in builds [versions]. The remaining known limitation is [limitation]. We believe the app is ready for production because [reason].
That is specific, readable, and easy to verify.
What if the button is still locked?
The most common reasons:
- fewer than 12 testers are opted in;
- the testers have not been opted in for 14 continuous days;
- the test has not been active long enough;
- the Console has not updated yet;
- the app has a policy or account issue.
If the Console shows the requirement as complete but the button is still locked, wait a day and check again. If it remains locked, contact Google Play developer support with your package name and the dates.
After you apply
Google reviews the application. The response can take time. Do not submit duplicate applications or create a new app to get around the wait.
If you are approved, you can create a production release. If you are rejected, read production access rejected before you change anything.
The short version
- Apply from the Production page after the closed-test requirement is complete.
- Describe the test, the testers, the feedback, and the changes.
- Be specific and honest.
- Do not submit duplicates.
- Google reviews the application; the 14 days do not grant access automatically.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.