The second part of the production access form is called About your app or game. Google says your answers here are not shown publicly and do not affect your app's visibility, your access to Play Console features, or your eligibility for developer programs. So there is no reason to exaggerate, and a good reason to answer carefully. The questions are described on Google's testing requirements page.
The three questions
- Target audience. Google asks you to be as specific as possible.
- Value proposition. For an app: how it provides value to users. For a game: what makes it unique.
- Estimated installs in the first year. You pick an install range.
Target audience: weak and strong
| Weak | Strong |
|---|---|
| "Everyone" | "People who commute by train and want to track delays" |
| "Young adults" | "University students who share flat costs" |
| "Anyone who likes games" | "Adults who play short puzzle games on their phones while waiting" |
A strong answer names who they are and when or why they use the app. If you cannot say it in one sentence, your target is still too wide.
Value proposition: say the benefit, not the features
- Weak: "It has charts, categories and reminders."
- Strong: "It lets two people see, in ten seconds, who owes whom after a shared month, without a spreadsheet."
For a game, say what is different: "Each level changes the rules of the board, so players cannot rely on one strategy."
The install estimate: be honest and use arithmetic
Google asks for a range for your first year. A simple way to choose:
- List your channels. For example: your followers, a community you belong to, the Play Store search.
- Estimate reach for each. For example: 2,000 followers.
- Apply a modest conversion. For example: 5% of reach installs it.
- Add up, and pick the range that contains it.
Example (invented): 2,000 followers × 5% = 100, a community post reaching 3,000 × 3% = 90, and search adding a few. A total of about 200 means you choose the lowest range, not a hopeful one.
Overestimating does not help you, and Google says the answer does not affect your visibility. Pick the range you honestly expect.
Keep it consistent
Your audience, your value proposition and your test feedback should tell one story. If your target audience is "students" but all your testers were retired friends, say so, and explain the difference. See the tester engagement guide.
Where it fits
This is part 2 of 3. For parts 1 and 3, see the questionnaire guide and example answers for five app types. Before you apply, check the production access checklist.
ClosedTest is an independent service and is not affiliated with Google.