Google Play's Android 16 deadline: what if you miss it?

Since 31 August 2026, every new app and every update submitted to Google Play must target Android 16 (API level 36). If your app doesn't, you can't publish updates, so you can't ship bug fixes or security patches until you upgrade. Developers who asked for an extension have until 1 November 2026. Existing apps that don't publish anything stay in the store, but they must target at least Android 15 to remain visible to new users on newer phones.

If you're a business owner and that paragraph was mostly numbers, here's the short version: your Android app has a deadline, and missing it freezes your ability to change the app.

What the rule actually says

Google raises its target API requirement every year, always at the end of August. For 2026 the rules are:

• New apps and app updates must target Android 16 (API level 36) or higher.

• Existing apps must target Android 15 (API level 35) or higher to stay available to new users on devices running newer Android versions.

• Wear OS and Android Automotive apps have a lower bar (Android 15), and Android TV and XR apps lower still (Android 14).

• Eligible developers could request an extension in Play Console, which runs until 1 November 2026.

Targeting a version is different from supporting it. Your app can still run on older phones. Targeting means you've declared that your app follows the newer version's rules and behaviour changes.

Google does this to move the whole store forward on privacy and security. Each Android release tightens something, like how apps access location, photos or background activity, and those protections only apply to apps that target the new version. The yearly deadline is how Google makes sure old apps don't quietly keep old loopholes open.

How to check your app's target version

You don't need to read code to find out where you stand. In Play Console, open your app, go to the App bundle explorer, and look at the target SDK of your latest release. If it says 36, you're done for this year. If it says 35, you need the upgrade before your next update. Anything lower, and you're already losing new users on recent phones.

Play Console also shows a warning on the dashboard when an app falls behind the requirement, so check there if you haven't logged in for a while.

What happens if your app misses it

Nothing dramatic happens to users who already have the app. It keeps working on their phones.

The trouble starts when you need to change something. Play Console will reject the update until the app targets API 36. So the day a payment provider retires an old integration, or a crash appears on a popular phone, you can't ship the fix without doing the upgrade first. A one-hour fix becomes a one-week project at the worst possible moment.

Apps that fall further behind lose reach too. Apps targeting Android 14 or lower are only offered to devices running that version or older, which is a shrinking share of phones.

What upgrading involves

For a well-maintained app, the upgrade can be a small change: raise the target version, update libraries, test. For an app that hasn't been touched in a year or two, it usually means catching up on several framework releases first.

Android 16 also brings behaviour changes that apps targeting it have to handle:

• Edge-to-edge display is enforced. Apps can no longer opt out, so screens need to handle content drawing behind the status and navigation bars.

• Predictive back gestures are on by default, so custom back-button handling needs checking.

• On large screens like tablets and foldables, apps can no longer lock orientation or refuse to resize, so layouts need to adapt.

Each of these can break a screen that looked fine last year. The fix is usually straightforward. Finding every screen it affects takes testing.

If your app is built with React Native or Flutter, the framework itself may need upgrading before you can target API 36. That's often the bulk of the work, because framework upgrades pull library upgrades behind them.

How long it takes

Rough guide, based on the apps we've upgraded:

• Kept up to date within the last year: a few days, most of it testing.

• One or two years behind: one to three weeks, depending on how many libraries need replacing.

• Abandoned for longer, or built on libraries that no longer exist: sometimes a partial rebuild is cheaper than an upgrade.

The only way to know which group you're in is to open the code. A short audit tells you the size of the job before anyone commits to a price.

How to avoid this every August

This deadline comes back every year, so the real fix is a routine, not a rescue.

Put the target API bump on your calendar for June, when Google's new requirement is known and there's no rush. Keep libraries updated in small steps through the year. Maintain a test checklist for your core flows, so each upgrade ends with a quick, reliable check.

That's the maintenance work we cover in our guide to app maintenance costs. It's cheaper than the emergency version by a wide margin.

Questions about the Android 16 target API deadline

Will my app be removed from Google Play if I miss the deadline?

No. Your existing app stays listed, and current users keep it. You just can't publish updates until you target Android 16, and apps targeting old versions become invisible to new users on newer phones.

Can I still get an extension?

Extensions were available through Play Console for eligible developers and run until 1 November 2026. After that date there's no further extension, so the upgrade has to happen before your next release.

Does this affect iPhone apps?

No, this is a Google Play rule. Apple has its own yearly requirement: apps uploaded to the App Store must be built with a recent SDK, which moved to the iOS 26 SDK in April 2026.

My developer is no longer available. What can I do?

Get the source code and store account access first, since you'll need both. Then a new developer can audit the code and tell you how big the upgrade is. If you don't have the source code, that becomes the first problem to solve.

Get your app upgraded before November

If your Android app needs the API 36 upgrade and your old developer isn't around, our web and app development team can audit it and give you a fixed price for the work. Send us the app link and we'll reply within 48 hours.