How to Apply for Production Access on Google Play

Production access on Google Play is what turns a tested app into a published one. For personal developer accounts created after November 13, 2023, you apply for it in Play Console once your closed test has met Google's criteria. This guide covers when you can apply, the three parts of the application, what happens during review, and what to do if Google asks for more testing.

All of the steps and questions here come from Google's Help Center article App testing requirements for new personal developer accounts.

When can you apply?

You can apply once your closed test meets Google's criteria: at least 12 testers opted in to your closed test when you apply, who have been opted in continuously for the preceding 14 days. Testers who left before completing 14 days do not count, and a tester who opts out and back in needs 14 consecutive days again.

If you are still building toward that point, our guides to 12 testers for 14 days and setting up closed testing cover the earlier steps.

How do you apply?

Google's steps are short:

1. Open the Dashboard in Play Console.
2. Click Apply for production.
3. Answer the required questions about your closed test, your app and its production readiness.

The application form has three sections: 'About your closed test', 'About your app/game' and 'About your production readiness'. The rest of this guide explains what Google asks in each one.

Part 1: About your closed test

Google says this section helps verify that apps have been thoroughly tested before publication, which protects users from low-quality apps, prevents malware distribution and reduces fraud. You are asked to:

• Select an option indicating how easy it was to recruit testers for your app.
• Give details about tester engagement during the closed test, including whether testers used all available app features, and whether tester usage matched expected production user behavior, with details of any differences you observed.
• Summarize the feedback you received from testers and describe how you collected it.

Then click Next. This is where notes kept during the test pay off. A specific summary of what testers found and how you gathered it is much easier to write from records than from memory.

Part 2: About your app or game

This section gives Google context about what you are publishing. Google states that these answers are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access or eligibility for developer programs. You are asked to:

• Specify the target audience for your app or game, as specifically as possible.
• Describe its value proposition. For apps, describe how the app provides value to users. For games, describe what makes the game unique.
• Select an estimated install range for the first year.

Then click Next.

Part 3: About your production readiness

The final section helps Google evaluate whether your app or game is ready for a production release. You are asked to:

• Describe any changes you made to your app or game based on what you learned from the closed test.
• Describe how you determined that your app or game was ready for production.

Then click Apply.

One practical warning appears in Google's instructions for every section: if you click Discard or leave the page without clicking Next (or Apply, on the last section), your changes are not saved. Drafting your answers somewhere else first avoids losing them.

What happens after you apply?

After you submit, Google reviews the application. When the review is complete, Google sends an email notification to the account owner. Google says review usually takes seven days or less, but can occasionally take longer.

If the application is approved, you get access to your app's Production page (Test and release > Production) and can distribute your app to users on Google Play. Open testing (Test and release > Testing > Open testing) also becomes available. Google recommends that you keep testing thoroughly before publishing production updates.

What if Google asks for more testing?

An application may not be approved on the first attempt. Google states that if your app needs additional testing, you may need to continue running your closed test. It names two reasons for required continued testing: having fewer than 12 opted-in testers, and insufficient tester engagement during the testing period.

Both point to the same fixes. Check that your count is truly 12 or more opted-in testers with an unbroken 14 days, not 12 invited email addresses. And look at engagement: Google's best-practice advice is to give testers clear instructions on how to test and report bugs, say what kind of feedback you want, and encourage them to use as many features as possible.

Policy compliance matters just as much. Google is explicit that ensuring policy compliance is your responsibility before you submit, and that review is not a troubleshooting step. Submitting an app that does not comply, expecting reviewers to find the issues, leads to rejections, review delays and lengthier appeal processes. Before applying again, check the areas Google highlights: app content and features, targeting and content rating, functional reliability, and working test credentials if your app needs a login.

Use the 14 days to prepare your answers

Almost everything the form asks about happens during the test, so the best preparation is to work on it while the test runs:

• Record feedback as it arrives. Google recommends keeping a record and reviewing it regularly to spot recurring themes.
• Act on what testers report. Google says responding to feedback and fixing bugs during testing improves user experience and increases the likelihood of a successful production access application.
• Note what you changed and why. Part 3 asks for exactly this.
• Run through a checklist before you apply. Our production access checklist collects every point from this guide in one tick-box list.
• Use Play Console's own tools. Google suggests running a pre-launch report to find warnings, errors and performance issues before reaching users.

Frequently asked questions