By Will McCullough, DigiRune Studios ·
What is a target API level?
Each Android version has a number, called its API level. Your app declares a targetSdkVersion in its manifest file: the Android version you built and tested it for. A higher target turns on newer Android privacy and security behavior, which is why Google keeps raising the minimum.
If you wrapped a web app for Google Play, the wrapper tool sets this number for you. It still counts, so rebuild with an up-to-date version of the tool when the requirement rises.
What is the current requirement?
For phone and tablet apps, Google's page says new apps and app updates must target Android 16 (API level 36) or higher to be submitted. That rule took effect on August 31, 2026. A year earlier, the floor was Android 15 (API level 35).
Other device types have their own floors. For example, Wear OS apps need Android 15 (API level 35) and Android XR apps need Android 14 (API level 34) for new apps and updates from August 31, 2026. Check Google's table for your device type.
What happens to an app that does not update?
Your app is not deleted, but it slowly disappears for new users:
- Existing phone apps must target at least Android 15 (API level 35) to stay available to new users on newer Android versions.
- An app below that line is only offered on devices running an Android version at or below its target.
- People who already installed it keep it and can reinstall it.
- Google warns that apps that stop meeting the requirement may see fewer downloads.
Can I get more time?
For the 2026 deadline, Google offered an extension request in Play Console that gave apps until November 1, 2026 to update and kept them available to all users until then. That date has passed, so apps still behind need an update now. Affected developers get the extension form through Play Console notifications and the Policy status page when one is offered.
The only standing exception Google lists is permanently private apps restricted to users in one organization for internal distribution.
How do I stay ahead of it?
- Put the end of August in your calendar every year. Google has raised the requirement around August 31 in recent years.
- Watch Play Console's Policy status page and inbox. Google flags affected apps there.
- Raise the target on your schedule, not Google's: change it, test on a real phone running the newest Android, then release.
- Read Android's behavior-change notes for the new version before you raise the number. Some features, such as permissions and background work, change behavior when you do.
How do I check my app's current target?
Look for targetSdkVersion in your app's build settings or manifest. For a wrapped web app, check the settings in the wrapper tool or its generated project. In our experience, Play Console's app bundle explorer also shows the target API level of each bundle you upload, which is a good final check.
Taking your app to the stores?
The DigiRune Studios Store Launch Kit is a step-by-step guide and checklist for getting through Apple App Store and Google Play review, built from the process we use for our own apps. Apple and Google make every approval decision; the kit helps you submit ready.
See the Store Launch KitSources
Store rules change. Check the official pages on the day you submit. Checked November 19, 2026.