Quick answer: Test across the fragmented Android device range, verify the app bundle and signing, check permissions and policy compliance, use the Play pre-launch report, and capture crashes and ANRs with device context. A Google Play launch must pass policy review and run across thousands of devices, so test fragmentation and compliance deliberately.
Launching an Android game on Google Play means navigating two big challenges at once: the extreme device fragmentation of Android, where your game must run across thousands of device models and many OS versions, and Google Play own requirements, the app bundle format, signing, permissions, policy compliance, and review. A game that runs on your test phone can fail certification or crash on a quarter of devices for reasons your testing never surfaced. This checklist covers the Google Play-specific QA that gets you to a successful Android launch.
Android fragmentation is the core challenge
The defining QA challenge of Google Play is Android fragmentation: thousands of device models, many OS versions in active use, a wide range of hardware tiers and GPUs. Your game must run across this enormous matrix, and a bug or performance problem specific to a device family, OS version, or memory tier can affect a large share of players while never appearing on your development device.
This means you cannot test on one phone and call it done. You need to test across a representative range of devices and OS versions, and crucially, capture crashes from the field with device context so the device-specific failures you could not test surface in your data. Fragmentation makes Android the hardest platform to fully test, so a Google Play launch combines testing a representative range with capturing the long tail through crash reporting.
Verify the app bundle and signing
Google Play uses the Android App Bundle format, from which Google generates optimized APKs per device, and signing is handled through Play App Signing. Verify that your app bundle builds correctly, that signing is set up properly, and that the optimized APKs Google generates actually install and run on devices, since a signing or bundle configuration problem can block installation or cause crashes on specific device configurations.
Test the actual installed result on devices, not just your local build, because the per-device APK generation means what installs on a player phone is derived from your bundle, and configuration issues, missing resources for a density or architecture, only show up in the installed app. Verifying the bundle and signing produce working installs across device configurations is a Google Play-specific step that your local testing does not cover.
Check permissions and policy compliance
Google Play enforces detailed policies, and your game must comply or face rejection or removal. Review the permissions your game requests, since Play scrutinizes permissions and requires justification for sensitive ones, and a game requesting permissions it does not need or cannot justify can be rejected. Request only the permissions you genuinely use, and verify the game handles permission denials gracefully.
Check compliance with Play policies relevant to games: data safety and privacy disclosures, content ratings, target API level requirements that Play enforces and updates, and any monetization policies if you have in-app purchases or ads. Policy compliance is a hard requirement, not a suggestion, and a policy violation can block your launch or get your game pulled, so verifying compliance is as essential as verifying the game runs.
Use the pre-launch report and capture ANRs
Google Play provides a pre-launch report that runs your game on a range of real devices and surfaces crashes, performance issues, and other problems before you launch, which is a valuable free test across devices you do not own. Review the pre-launch report and address the issues it finds, since it exercises the fragmentation you cannot test manually.
Set up your own crash and ANR capture too, because Application Not Responding errors, where your game freezes the main thread, hurt your Play standing and need fixing. While the Play Console reports crashes and ANRs, its data is delayed and lacks in-game context, so capture your own crashes and ANRs with full device context for real-time, contextual diagnosis. The pre-launch report catches issues before launch, and your own capture handles the live long tail across the fragmented device base.
A Google Play launch checklist
Use this checklist for your Google Play launch alongside normal mobile QA, focusing on the fragmentation and policy requirements specific to the platform. Test on real devices across tiers and capture crashes with device context throughout. The two themes that run through it are coverage and compliance: coverage because the device matrix is too large to test on one phone, so you lean on a representative range plus captured field data, and compliance because Play enforces its policies strictly and a violation can block your launch regardless of how well the game runs, so verifying both is essential before you ship.
Google Play launch QA checklist:
[ ] Tested across a representative range of devices and OS versions
[ ] App bundle builds and the generated APKs install and run
[ ] Play App Signing configured correctly
[ ] Only necessary permissions requested, with graceful denial handling
[ ] Data safety and privacy disclosures complete and accurate
[ ] Content rating obtained and accurate
[ ] Target API level meets Play requirements
[ ] Monetization complies with Play policies (IAP, ads)
[ ] Pre-launch report reviewed and issues addressed
[ ] Crash and ANR capture with device context enabled
[ ] Performance acceptable on mid-range and low-end devices
[ ] Saves survive backgrounding and OS kills