Testing Tracks
| Track | Who | Use |
|---|---|---|
| Internal testing | Up to 100 testers you list | Quick checks, available within minutes |
| Closed testing | Invited groups or email lists | Beta feedback |
| Open testing | Anyone can join from the store | Public beta |
| Production | Everyone | Full release |
Target API Level
Google Play requires apps to target a recent Android API level. From August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher (Wear OS and Automotive have lower requirements). Existing apps that target below Android 15 (API 35) become hidden from new users on newer devices.
When you raise targetSdk, read the behavior changes page for that Android version and test your app. Typical changes affect permissions, background work, edge-to-edge display and 16 KB memory page size support for native code.
Pre-Release Checklist
- Test the release build on at least two real devices and different Android versions
- Check the Pre-launch report in Play Console (automatic tests on real devices)
- Complete the Data safety form honestly, including SDKs
- Provide a demo account if the app needs login (App access section)
- Remove debug logs, test URLs and hard-coded secrets
- Prepare screenshots, icon (512 x 512) and short and full descriptions
Common Policy Problems
| Problem | How to avoid it |
|---|---|
| Missing or wrong privacy policy | Use a real policy that matches the app's behavior |
| Requesting unnecessary permissions | Request only what a feature really needs |
| Misleading store listing | Screenshots and text must match the real app |
| Crashes and ANRs | Test on real devices, watch Android vitals |
| Using restricted permissions (SMS, call log, background location) | Avoid them, or complete the declaration form with a strong reason |
Staged Rollout
In the production release choose a percentage, for example 10 percent. Watch crashes and ratings, then increase to 100 percent. You can halt a rollout if you find a serious bug.
After Release
- Monitor Android vitals: crash rate, ANR rate and startup time
- Read and answer user reviews
- Ship updates with a higher versionCode and release notes
- Update
targetSdkonce a year
Conclusion
Use internal and closed tracks to test, meet the target API level, follow the policy checklist and release in stages.

