Skip to content
Get startedAdd your app

Production access · Application answers

Weak application answers: what Google asks and how to answer

The production access form is short, but it's where your closed test is judged. Generic one-liners can make a decent test look like nobody used the app. Here's what each section asks, and how to answer with facts.

What Google asks

You apply from the Dashboard with Apply for production. According to Google's help page, the form has three parts:

  • About your closed test: how easy it was to recruit testers, the engagement you got (did testers use all of your features, and did their usage match what you expect in production, with details if not), and a summary of the feedback you received and how you collected it.
  • About your app or game: your intended audience, as specifically as possible; how your app provides value, or what makes your game unique; and an estimate of installs in the first year.
  • About your production readiness: what you changed based on the closed test, and how you decided the app is ready for production.

Changes are only saved when you click Next or Apply: leaving the page loses them. Draft your answers somewhere else first.

What weak answers look like

  • No numbers: “testers liked the app” says nothing. How many testers, for how long, how many bugs, how many updates?
  • No method: Google asks how you collected feedback. “From testers” isn't a method; a form, email or group chat is.
  • Nothing changed: if the answer to “what did you change” is “nothing”, the test looks like it taught you nothing.
  • A generic audience: “everyone” or “all Android users” isn't specific. Google asks for as specific as possible.
  • Copied templates: the same paragraph many other developers pasted from a forum reads like it.
  • Claims the test can't back up: describing heavy daily use when testers barely opened the app. See testers not engaged.

How to fix it

  1. Gather the facts first

    Before writing, collect your numbers: opted-in testers, test period, active days, features covered, bug reports, fixes and versions released.

  2. Answer the closed test section with specifics

    Say how you recruited testers and who they were. Describe which features they used, and where usage differed from what you expect in production. Summarise the main feedback themes and the channel you used.

  3. Be specific about audience and value

    Describe your users the way you'd describe a customer: age range, situation, need. Then say in one or two sentences what your app does for them, or what makes your game different.

  4. Be realistic about installs

    Pick the estimate that matches your plans for the first year. There's no bonus for a big number.

  5. Show what changed

    List concrete changes by version: bugs fixed, flows simplified, crashes resolved. Then explain how you decided it was ready: open critical bugs, retested fixes, feedback addressed.

  6. Write it in your own words

    Use a draft as structure, not as the final text. Our free answer helper turns your notes into a structured draft for each question, in your browser only.

If the test itself was thin, better answers alone won't fix it. Run the extra testing period properly first, then write the answers.

How TestBunny helps

  • The facts, already collected: participation by day, devices and Android versions, scenarios completed, bugs with their status, feedback and builds, in one report. See a sample report.
  • Production access prep: in your panel, the report's records are turned into sentences for each of Google's three sections, each one linked to the data behind it. You write the final answers yourself.
  • Real testers, fast: first testers join within 6 hours of recruiting, and each one tests for 14 days with daily tasks.
  • Free re-test guarantee: if Google rejects production access after a completed campaign, you get one free re-test per campaign. Claim it within 30 days of completion.

We don't write your application and we can't influence Google's review. Nobody can guarantee approval, and we don't.

Frequently asked questions

Can I copy answers from a template?

You can use one for structure, but write the content yourself. Google asks about your test and your app; generic text can't describe either.

How long should each answer be?

Long enough to include the facts: a few sentences with numbers usually beats one line or a page of filler.

Does a higher install estimate help?

No. Give your honest estimate for the first year.

If my answers were the problem, do I need to test again?

Developers usually report being asked for another 14 days of closed testing either way. Use that time to make the test and the answers stronger.

Sources

Technical details were checked against the official documentation below. Menus and defaults change between versions; when in doubt, the official page wins.

Draft your application answers

A free, private helper that walks you through Google's three sections and turns your notes into well-structured drafts. Nothing leaves your browser.

Open the free helper

See what a well-documented test looks like

Daily participation, devices, scenarios, bugs and feedback, in the same report a TestBunny campaign produces. Demo data from a fictional app.

See a sample report

Other rejection reasons

Run a closed test that holds up.

Real testers, every day on record, first testers within 6 hours of recruiting. If Google still says no after a completed campaign, you get one free re-test (claim within 30 days of completion).

Start your testSee the plans

TestBunny isn't affiliated with Google. Testers earn credits, never cash. Google alone decides on production access: nobody can guarantee approval, and we don't.