Google Play’s target API level deadline lands on 31 August 2026. From that date, new apps and app updates must target Android 16 (API level 36) or higher to be published. Existing apps that don’t meet at least Android 15 (API level 35) don’t get pulled outright, but they stop being discoverable to new users on any device running an Android version newer than the app’s target — a quiet, ongoing loss of App Store reach rather than a dramatic takedown. Developers who need more time can request an extension, but only until 1 November 2026, and only by demonstrating an active plan to update.
This is a routine-looking policy update that’s easy to miss if nobody on the commissioning side is watching the Play Console. It’s also entirely predictable: Google raises the target API bar on a near-annual cycle to force adoption of current security, privacy, and performance baselines, and every previous cycle has followed the same pattern — a compliance window, an extension option, then reduced visibility for apps that never move.
So what
If your business has an Android app that hasn’t shipped an update in the last year, this is worth a direct question to whoever maintains it: does it currently target API level 35 or higher, and is there a plan in place before 31 August? For apps built on frameworks like React Native or Flutter this is usually a low-effort SDK bump rather than a rewrite, but “usually low-effort” and “actually done before the deadline” are different things, and the cost of missing it compounds quietly — fewer new installs, not a visible outage, which makes it easy to overlook until acquisition numbers dip and nobody can say why. If you need someone to check your app’s current target level and handle the update, that’s exactly the kind of maintenance work covered under our iOS & Android development, or get in touch if you’d rather hand the whole thing off.