How to apply for production access on Google Play

After your closed test, production stays locked until you apply and Google says yes. The application is a three-part form on your app's Dashboard. Google uses it to check that you really tested the app, that you know who it's for, and that it's ready (Play Console Help).

Below: when to apply, what to check first, each question with an example answer, and what happens next.

When you can apply

You can apply once "at least 12 testers" are "opted in to your closed test" and "have been opted in continuously for the preceding 14 days". Then:

1. Open your app's Dashboard in Play Console.
2. Click Apply for production.

Don't apply the minute day 14 starts. Wait until 14 full days have passed for your 12th tester. Our own recommendation is day 15. If you're unsure how your days add up, see how the 14 days are counted.

Before you click Apply

Google is direct about this: its review "is not a troubleshooting step". It lists what to double-check before applying (Play Console Help):

• Content and features. Everything, including monetization, follows Google Play policy.
• Target audience and content rating. They match your app and listing.
• Stability. No crashes, broken features or missing screens.
• Test credentials. If the app needs a login, working credentials are in Play Console, under App access (Play Console Help).

Two more checks worth doing:

• Your store listing matches the app. Google may reject apps whose listing promises features the app doesn't have (Play Console Help).
• Your latest bundle targets API 36 or higher, the requirement for new apps since August 31, 2026 (Play Console Help).

Gather your material too: tester feedback (including private feedback under Monitor and improve > "Ratings and reviews" > Testing feedback), your bug list, and the release notes of the versions you shipped during the test.

The example app

To make the answers concrete, the examples below use a fictional app: a habit tracker for university students. Its numbers are invented for illustration. Use your own test's real facts. Don't copy these sentences: a generic answer tells Google nothing about your app.

Part 1: About your closed test

Google says this section "helps verify that apps have been thoroughly tested before publication". It asks four things.

How easy was it to recruit testers?

You select an option. Pick the honest one. There's no bonus for saying it was easy.

Did testers use all the features?

Google asks about tester "engagement": whether testers used all available features. Name the features and say what was used and what wasn't.

Example (fictional): "Most testers used the core features. 14 of 16 testers created at least one habit and checked it off on most days. 9 used the weekly statistics screen. Only 3 found the CSV export, so we moved it from Settings to the statistics screen in version 1.0.3."

Did tester usage match how real users will behave?

Google asks whether usage matched expected production behavior, and to describe any differences.

Example (fictional): "Mostly. We expect students to open the app once or twice a day, in the evening. Testers did the same. One difference: testers rarely used reminders, while we expect real users to rely on them. Several testers were developers who test in short sessions, so we tested reminders ourselves on three devices."

Summarize the feedback and how you collected it

Example (fictional): "We collected feedback through a form linked in the app's settings, Google Play's private feedback, and a group chat with testers. The main themes were: the onboarding had too many screens (fixed: 5 screens down to 2), the dark mode had unreadable charts (fixed), and two testers on Android 12 saw a crash when editing a habit (fixed in 1.0.2)."

Click Next. If you click Discard or leave the page without clicking Next, your answers are lost.

Part 2: About your app/game

Google says these answers "are not displayed publicly on Google Play and do not affect app visibility, Play Console feature access, or eligibility for developer programs".

Target audience

Be as specific as possible.

Example (fictional): "University students aged 18 to 25 who want to build study and sleep habits. English-speaking first, mostly in the United States and India, on mid-range Android phones."

Value proposition

For apps, describe how the app provides value to users. For games, describe what makes the game unique.

Example (fictional): "Students track two or three habits with one tap a day. The app works offline, has no account, and shows weekly progress that fits a semester schedule."

Estimated "install range" for the first year

Choose a range that matches your real plans and marketing. A modest, honest estimate is the safer choice.

Click Next.

Part 3: About your production readiness

Google says this section "helps evaluate whether your app or game is prepared for production release".

What did you change based on the closed test?

List concrete changes, ideally with versions.

Example (fictional): "Version 1.0.1 shortened onboarding. Version 1.0.2 fixed a crash on Android 12 when editing a habit. Version 1.0.3 fixed dark mode charts and moved CSV export to the statistics screen. Each update went to the closed track, and testers confirmed the fixes."

How did you decide the app was ready?

Example (fictional): "No new crash reports in Play Console during the last five days of the test. All bugs marked critical by testers are fixed. Every tester who reached day 14 completed the core flow: create a habit, check it off, read the weekly summary."

Click Apply. Discard or quit before applying, and your changes are not saved.

What makes answers weak

• Generic text that could describe any app.
• Numbers that don't add up, like "50 testers" when your closed test had 14.
• No changes at all. Google's best practices are to fix reported issues and update the app in closed testing before production.
• Promises the listing doesn't keep.

After you apply

"Review usually takes seven days or less, but can occasionally take longer." Google emails the account owner (Play Console Help).

• Approved: the Production page (Test and release > Production) and Open testing unlock.
• More testing needed: Google names two reasons: "fewer than 12 opted-in testers or insufficient tester engagement during the testing period". The next steps are in production access rejected: what to do.

Keep testers opted in until you have the answer. If Google asks for more testing, you'll need them.

To check your setup before you even get here, see how to set up closed testing. The whole process is in the complete guide to Google Play closed testing.