Games follow the same closed testing rule as any other app: if you publish from a personal developer account created after November 13, 2023, you need a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. What's different is the detail around it. Games tend to have heavier builds, more varied device demands, different rating questions and a slightly different question in the production access form.
The rule is the same
Google's requirement doesn't separate games from apps. Its help page refers to "apps" throughout, and the production form explicitly mentions games, which tells you they're covered (App testing requirements). Internal testing doesn't count, and nothing shortens the 14 days. If you're new to the rule, start with what closed testing is.
1. The production form asks what makes your game unique
The second section of the production access form, About your app/game, asks about your target audience, your value proposition and your estimated installs in the first year. For games, Google words the value question as what makes the game unique.
That's harder than it sounds for a game. "A fun puzzle game" doesn't say much. A good answer names the mechanic, theme or format that sets it apart, and it should match the build testers actually played. Google says these answers "are not displayed publicly" and "do not affect app visibility". Our production access guide has example answers you can adapt.
2. Paid games cost testers money
Google's help says closed and open testers "must purchase paid apps"; only internal testers install them for free. If your game has an upfront price, your closed testers will see that price. Note that a game offered for free can't later be changed to paid on the same package, so decide your pricing model before the closed test. If the game will be paid, plan how testers will cover the price, for example with promo codes (a community workaround, not official guidance).
In-app purchases are a separate topic. Test purchases need their own setup, and it's worth checking Google's billing documentation before your test so testers aren't charged by accident.
3. The content rating questionnaire is game-specific
When you fill in the content rating questionnaire, you choose a category, and games get questions suited to games, often about violence, fear, language and gambling-like features. Answer for the whole game, including later levels. If you add content during the test that changes your answers, you must submit a new questionnaire. The details are in the content rating questionnaire, explained.
4. Devices matter even more
Games usually push hardware harder than typical apps: graphics, memory, storage and battery. A closed test on varied real phones is your chance to see:
- how the game performs on lower-end or older devices
- whether it overheats or drains battery quickly
- whether the screen layout works on tall, small and tablet screens
- whether the first download is too large for people on mobile data
Android vitals after launch uses user-perceived crash and ANR rates, with thresholds that also apply per phone model. See Android vitals for new apps. The free pre-launch report also runs your build on test devices, though an automated crawler may not get far into gameplay; read it anyway (pre-launch report explained).
Keep in mind the AAB format: new apps must publish with the Android App Bundle, and the compressed download limit is 4 GB.
5. Engagement looks different in a game
For an app, engagement often means "used every feature". For a game, it's more about whether testers keep coming back and how far they get. The form still asks whether testers used all features and whether usage matched what you expect in production. Think about:
- Progression. Fourteen days may not be long enough for testers to see late content. Tell testers which modes or levels to try, so your answer covers them honestly.
- First session. Tutorials and the first few minutes decide whether players stay. Ask testers specifically about them.
- Session patterns. Note whether testers play in short bursts or long sessions, and whether that matches your expectations.
Keeping the game installed and playing it regularly is strongly advised. Google may require more testing for "insufficient tester engagement during the testing period". Practical tactics are in keeping testers engaged.
6. Feedback for games needs structure
"It's fun" isn't actionable. Ask testers targeted questions: where they got stuck, which level felt unfair, whether controls felt responsive on their device, and whether anything crashed. Then act on it and record what you changed. Google encourages you to keep testing "while resolving user-reported issues and bugs", and the form asks what you changed. Collecting useful feedback has a log template.
7. Store listing and assets
Games often rely heavily on screenshots and the feature graphic. Make sure they show the real game, not concept art the build doesn't contain, since store listing accuracy is one of the areas Google says to check before applying. Specs are in app icon, screenshots and feature graphic.
What not to do
- Don't reward testers for ratings or reviews. Testers can't leave public reviews on test versions, and incentivized reviews are prohibited.
- Don't use bots or emulators to "play" the game for 14 days. The requirement is about real players.
- Don't change monetization in a way that contradicts your declarations without updating them.
Key takeaways
- Games follow the same 12-tester, 14-day rule as apps.
- The form asks what makes your game unique; answer specifically.
- Paid games cost closed testers money, and a free game can't become paid later, so settle pricing before you test.
- Device variety, progression and structured feedback matter more for games.
GoPlayTester supplies 12+ real testers who install your game on their own Android devices for the full 14 days. It helps you meet the testing requirement, and Google makes the final decision. You can order here.
