There's a deadline most Android developers aren't thinking about yet: August 31, 2026. That's when Google Play requires all new app submissions and updates to target Android 16, API level 36.
If you miss it, new users on Android 16+ devices won't see your app in search results. Existing users who already have your app installed keep it — but you disappear for anyone installing fresh. That's not a deprecation warning. That's a quiet, invisible cut in your acquisition funnel.
what "targeting API 36" actually requires#
Bumping targetSdkVersion to 36 isn't always just changing a number. Android 16 includes behavior changes that activate the moment your app opts in — and some of them will break things if you're not prepared.
Notification and full-screen intent enforcement. Apps targeting Android 16 that use full-screen intents — alarm apps, call apps, delivery tracking, rideshare — must explicitly request the USE_FULL_SCREEN_INTENT permission. If you're showing notifications that pop over a locked screen and haven't updated your permission handling, expect breakage.
Photo and media picker changes. Android 16 tightens the media access model further. If you're still using deprecated file picker patterns or the old READ_EXTERNAL_STORAGE flow, this is the upgrade that finally forces you off them.
Predictive back gesture compliance. Android 16 enforces the predictive back gesture more aggressively against apps that still use onBackPressed(). If you haven't migrated to OnBackPressedDispatcher, you'll start seeing issues. This migration takes longer than developers expect — especially in apps with complex navigation or deep back stacks.
None of these changes are catastrophic. But they're also not the kind of thing you want to discover two weeks before the deadline, especially when a regression in notification behavior can tank your ratings overnight.
why indie devs always get caught by this#
Enterprise apps have release managers and compliance trackers. Indie developers have shipping features. The pattern is predictable: you see the announcement in February, think "six months, plenty of time," ship a feature update in June, and suddenly it's August 20th with ten days left to do a compliance pass you assumed would be quick.
The other trap is dependency debt. Your third-party SDKs also need to support targeting API 36. If a library you depend on hasn't released a compatible version, you're blocked — and you have limited options: wait for them, fork and patch, or find a replacement. Starting now gives you time to file issues and wait for official releases rather than scrambling. Starting in August does not.
Run this check today in your build.gradle:
android {
defaultConfig {
targetSdk = 36 // does this number exist without breaking your build?
}
}Bump it and run your test suite. The output will tell you exactly what's broken. Better to find out now.
what else changes at the same deadline#
August 31, 2026 also brings an important change for existing apps: any app that doesn't target at least Android 15 (API 34) becomes invisible to new users on devices running newer Android versions. If you have older apps in your portfolio that you haven't touched in a while, they could quietly drop off the radar for anyone on a recent device.
This is worth auditing across your whole catalog, not just your active apps. A dormant app that still generates a few hundred installs a month is worth a one-day SDK bump — losing that visibility is harder to recover than preventing it.
the Play Store submission piece#
Once you've done the work — updated your target SDK, migrated any breaking API usages, tested on Android 16 devices and emulators — you still need to get the update through Play Console review cleanly.
That means updated screenshots if your UI changed with the predictive back gesture migration, updated description if you've added features, and clean metadata across every locale you support. This is the part of a compliance release that always takes longer than expected. Stora handles the submission packaging — screenshots, store listing updates, multi-locale metadata — so once your build is ready, the submission side doesn't become its own project at the worst possible time.
the bottom line#
August 31 is far enough away that there's no reason to panic. It's close enough that if you start now, you can do this without rushing. Check your targetSdkVersion, audit your notification and permission usage, check your key dependencies for Android 16 support, and file the issues you find.
The developers who treat this as a Q2 task will be fine. The ones who treat it as a Q3 task will be scrambling.