PlayTestersby Alpha MF

Guide 4 of 7 · Updated October 2026

Production access application: what Google asks and how to answer (with sample answers)

Short answer: The form asks about your closed test — how easy recruiting was, how many testers engaged and how, the feedback you received and what you changed because of it — and about your app: who it is for, whether it is ready for production and how you know, and a confirmation that it follows the Developer Program Policies and is complete. Answer with numbers, quotes and version numbers from the test; Google reads the answers against what actually happened on the track and usually answers within 7 days.

After 12 testers have been opted in to your closed test for 14 days, Play Console shows an Apply for production access button. Behind it is a short form about your test and your app. Google reads the answers, looks at what happened on the track, and decides whether a new personal account may publish. This guide goes through every question, how to answer it, and what to avoid.

Last updated: · About 8 minutes · Google adjusts the form's wording from time to time; the questions below are the ones it has asked throughout 2025–2026, in plain words.

When the button appears

Open the app's Dashboard in Play Console. The closed-testing requirement card shows "x of 12 testers" and the days remaining. When both are satisfied, the card turns into Apply for production access. If the count is 12 but the button is not there yet, the 14 days are not complete for 12 of the currently opted-in testers — a tester who dropped out and was replaced restarts the count for that slot. The 14-day calculator gives you the earliest date.

The questions, one by one

About your closed test

  1. How easy was it to recruit testers? A scale, sometimes with a text field. Answer honestly; "hard" is not held against you. If you used a community or a service, say so — recruiting is not what is being judged.
  2. How many testers engaged with your app, and how? Give numbers you can stand behind: how many of the 12 installed, how many opened it more than once, what they did (completed onboarding, created an account, finished a level, exported a file). Play Console's statistics for the closed track give you installs and sessions; your feedback form gives you the rest.
  3. Describe the feedback you received. Quote or paraphrase real feedback, good and bad. Two or three concrete items beat a paragraph of adjectives. "Three testers could not find the settings screen; two asked for a dark theme; one reported a crash when rotating the phone on the map screen."
  4. What changes did you make based on the feedback? List builds and what changed: "1.0.2 moved Settings to the main menu and fixed the rotation crash; 1.0.3 added a dark theme." If you shipped an update to the closed track during the test, say it here — Google can see the release history.

About your app

  1. Who is the app for? / What is its purpose? One or two sentences, the same way you would describe it to a stranger. Be consistent with the store listing.
  2. Is the app ready for production, and how do you know? Tie it to the test: crash-free sessions, the pre-launch report, the feedback items you closed, what remains on your roadmap.
  3. Confirmation that the app follows the Developer Program Policies and is complete (no placeholder screens, no "coming soon" features).

Three sample answers

Adapt the structure, not the words. Each example answers questions 2–4 together, the way most developers write them.

A utility app (a unit converter)

Testers: 13 opted in, 12 installed, 10 opened the app on at least three different days (closed-track stats). Testers were colleagues (5), members of a Flutter Discord server (5) and a tester service (3).

Feedback: four testers said the currency tab needed a "last updated" time; two reported that the history list lost entries after the app was killed; one asked for a widget; one found the font too small on a 5" phone.

Changes: 1.0.1 (day 4) fixed the history persistence bug and added the "rates updated at" line. 1.0.2 (day 9) raised the base font size and added a system-font-size option. The widget is on the roadmap for 1.1. Crash-free sessions in the closed track: 99.6%. The pre-launch report shows no crashes or accessibility errors.

A game (a word puzzle)

12 testers from a word-game subreddit and friends; all 12 installed; 9 completed the tutorial and played more than 20 levels; the average session was 6 minutes.

Feedback: the tutorial was too long (5 testers), the hint button was easy to tap by mistake (3), two testers wanted a daily puzzle, one reported the game freezing when the phone went to sleep mid-animation.

Changes: 1.0.3 cut the tutorial from 8 steps to 3, moved the hint button and added a confirmation; 1.0.4 fixed the sleep/freeze bug. The daily puzzle shipped in 1.0.5 on day 12 and 7 testers played it the next day. We believe the game is ready: no open crash reports, and the remaining requests are new content.

A niche business app (an invoice generator for freelancers)

Testers: 14 opted in (12 freelancers from an Indie Hackers thread, 2 accountants I know); 12 installed and created at least one invoice; 6 sent an invoice to a real client during the test.

Feedback: VAT handling was wrong for two countries; PDF export used the wrong paper size for US testers; three testers asked to save client details for reuse; one asked for Dutch translation.

Changes: 1.1.0 fixed the VAT rules and added Letter/A4 selection; 1.1.1 added saved clients. Dutch is planned. The app has a privacy policy, the data safety form matches what we collect (email and invoice data, stored on-device), and the only permission requested is storage for the PDF export.

What not to write

  • One-word answers. "Yes", "Easy", "None" and "Nothing" are the single most common reason an application is turned down.
  • "Testers were my family and gave no feedback." Even if true, that sentence tells Google the test did not happen. If the feedback was thin, run a short questionnaire now, before applying.
  • Claims that do not match the track. Google can see installs, sessions, crashes and releases. "All testers used it daily" with two installs on record hurts more than a modest, true number.
  • Marketing copy. The form is not a store listing. Facts, numbers, versions.
  • Blaming testers or Google. It is not read by a sympathetic human looking for context; it is read by a reviewer looking for evidence of a real test.

Before you press Apply

  • Installs on the closed track are close to the opt-in count (if not, nudge testers today and wait a day).
  • At least one update was released to the track during the 14 days, with release notes.
  • You have written feedback from at least three testers, saved somewhere you can quote.
  • The pre-launch report (Play Console → Testing → Pre-launch report) has no crashes you have not fixed.
  • The store listing, privacy policy, data safety form and content rating are complete — Google reviews the app against policy at this stage too.
  • Your answers are drafted in a document, not typed live into the form.

After you submit

Google says the review takes up to 7 days; one to three days is common. You get an email and a message in the Play Console inbox. Approved: the production track unlocks and you create a production release the usual way (it still goes through app review). Not approved: the message says the app is not ready for production and gives general reasons; there is no appeal, you keep the closed test running, improve, and apply again after a further 14 days. The rejection guide covers the six reasons and the fix for each.

Keep your testers opted in after you apply. If the application is turned down, a test that is still running means your second 14 days start immediately instead of after a new recruiting round.

Short answers

When does the "Apply for production access" button appear?

On the app's dashboard in Play Console, once at least 12 testers have been opted in to your closed test for the last 14 days continuously. Until then the dashboard card shows the current count and the remaining days.

How long does Google take to review the application?

Google says up to 7 days. Many developers get an answer within one to three days.

What if the application is rejected?

There is no appeal form. You improve the app and the test, keep the closed test running, and apply again after a further 14 days. Rejections usually come from thin answers or a test with little real usage, both of which you can fix.