How to Apply for Production Access on Google Play

Before you apply

Personal developer accounts created after November 13, 2023 must complete a closed test before they can publish to production. Check these points first:

• At least 12 testers are opted in, and each stayed opted in for 14 days in a row. If your count looks low, read why testers sometimes do not count.
• Your app's closed testing track is still active.
• You have written down tester feedback and the changes you made. You will need them for the questionnaire.

If you are not sure about the requirement itself, our guide to the 14-day closed testing requirement explains it in plain language. You can also read Google's page: testing requirements for new personal developer accounts.

How do you apply for production access?

1. Open Play Console and select your appUse the account that owns the app.
2. Go to the DashboardThis is the home page of your app in Play Console.
3. Click Apply for productionThis starts the questionnaire. It is available once your closed test meets the requirements.
4. Complete the three-part formEach section has a Next button. Answer every question carefully.
5. Click Apply at the endDo not leave a page before saving. Clicking Discard or leaving early loses your changes.

The three parts of the questionnaire

Part 1: About your closed test

• How easy it was to recruit testers.
• Whether testers used all the available features of your app.
• Whether tester usage matched what you expect from production users, and any differences you saw.
• A summary of the feedback you collected and how you collected it.

Part 2: About your app or game

• Your target audience.
• The value your app gives users (or, for a game, what makes it unique).
• An estimate of installs in the first year.

Google says Part 2 is not displayed publicly.

Part 3: About your production readiness

• The changes you made based on what you learned in the closed test.
• How you decided the app was ready for production.

Tips for strong answers

• Be specific. "Testers reported the login button was hidden on small screens, and we fixed it in version 1.0.3" is better than "we fixed bugs".
• Be honest. Say how you really found testers and how they used the app. Do not invent numbers.
• Mention real changes. Release at least one update during the test, so Part 3 has something concrete to describe.
• Draft first. Write your answers in a document, read them once, and paste them into the form.

What happens after you apply?

Google says the review usually takes seven days or less, but it can occasionally take longer. The account owner receives an email when the review is complete. If more testing is needed, keep your closed test running and fix the points Google names.

While you wait, you can prepare your store listing and your production release, so you are ready to publish when you get approval.

Example answers you can adapt

These examples show the level of detail that works well. Replace them with your own real information.

• Recruiting testers: "We invited 15 testers through our own network and a testing service. Most joined within two days, and we replaced two who left."
• Feature use: "Testers used sign-up, the main dashboard and settings. Reports showed the reminder feature was used less, so we made it easier to find."
• Feedback summary: "We collected feedback through a shared form every three days. The most common issues were a slow first load and a hidden button on small screens."
• Changes made: "We fixed both issues and released version 1.0.2 to the closed track."
• Readiness: "After 14 days with no crashes reported, we decided the app was ready for production."

Prepare your notes before you click Apply

The questionnaire is easy when you keep notes during the test. Start a simple document with these headings on day 1:

Mistakes that cost an extra week

• Applying on day 14 when the count dropped below 12 on day 13.
• Copy-pasting generic answers. See the strong-vs-weak examples in the rejection guide.
• Changing your app's purpose between test and application.
• Skipping the Data safety form. See the Data safety guide.

For the timeline after you apply, read how long production access takes.

Frequently asked questions

Where is the Apply for production button?

Open the Dashboard of your app in Play Console and click Apply for production. It appears when your closed test meets the requirements.

How long does the review take?

Google says it usually takes seven days or less, but it can occasionally take longer. The account owner receives an email when the review is complete.

What if I leave the form halfway?

Clicking Discard or leaving a page before saving loses your changes. Write your answers in a separate document first, then paste them in.

Do I need to apply if my account is old?

The closed testing requirement applies to personal developer accounts created after November 13, 2023. Other accounts may not need this step, so check what your Dashboard shows.