Today, August 31, 2026, is the enforcement date for Google Play's updated target API level requirement. According to the official Play Console requirements, new apps and app updates must target Android 16 (API level 36) or higher — and if your app does not, it cannot be submitted to production. Existing apps that target a lower API level remain available only on devices running Android versions equal to or lower than their target, which means their reach quietly shrinks as users upgrade their phones.

If you have an app in active development, work through this checklist before your next release.

Check 1 — Find your current targetSdkVersion

Your target API level is declared in the module's build file: targetSdk = 36 in app/build.gradle.kts (or targetSdkVersion 36 in the Groovy build.gradle). If the value is missing, Gradle falls back to the compileSdk — which makes it easy to ship a target you did not intend. Play Console also shows the target API level for each release on the app's Release page, so you can confirm what actually went out, not just what sits in your source tree.

Check 2 — Bump compileSdk and targetSdk to 36

Setting targetSdk = 36 usually starts with your build toolchain: the Android Gradle Plugin and Gradle itself need versions that support API 36, then compileSdk = 36 and targetSdk = 36 go in together. After the bump, rebuild and resolve what breaks. Third-party SDKs matter here too — ad networks, analytics, payments, and maps libraries must each ship an API 36-compatible version; check their release notes before raising your target, or an outdated dependency can fail at runtime on Android 16 devices.

Check 3 — Review the Android 16 behavior changes

Raising your target opts your app into Android 16's new default behaviors — this is where most migration pain comes from. The areas that bite most apps are edge-to-edge rendering, 16 KB page-size support for apps with native code, the photo picker becoming the default, and the new task-and-identity permission model. Walk the official Android 16 behavior changes list on developer.android.com and test every item that touches a screen your users actually use.

Check 4 — Know the exception tiers

The API 36 requirement does not apply to every form factor. Per Google's requirements page: Wear OS and Automotive apps must target API level 35 or higher, and Android TV and XR apps must target API level 34 or higher — all on the same August 31 timeline. Check which tier your app's form factors fall into before you rush a bump.

Check 5 — Existing apps: the API 35 floor

For apps already on the store, the requirement is one level more forgiving: they must target API level 35 (Android 15) or higher to remain available to new users on devices running a higher Android version. An app stuck at API 34 or lower stays installable only on devices whose Android version matches or is below its target — a shrinking pool in 2026. If a legacy app genuinely cannot be updated, treat this as a product decision about its remaining reach, not a technical footnote.

Check 6 — Test on the right devices

Add Android 16 devices to your test matrix alongside a couple of Android 15 units, and use the device catalog in Play Console to see which devices your APK/AAB actually supports after the bump. Pre-launch reports run your app on a broad device set and surface crashes you will not catch on a single emulator.

Check 7 — Not ready? Request the extension

Google provides an extension path: developers who need more time can request an extension to November 1, 2026 through forms in Play Console. The requirement page says the forms become available later this year — so if your migration is at risk, plan the request now instead of hoping the deadline disappears.

Check 8 — Don't forget the account-level gate

While you are in Play Console: personal developer accounts created after November 13, 2023 still need a closed test with at least 12 testers for 14 consecutive days before they can access production — a separate, verified requirement that also sits on the release path. If your release is blocked at the account level, this checklist will not help you.

The one-line version

Today's deadline: new apps and updates must target Android 16 (API 36)+, existing apps must target API 35+, and Wear OS/Automotive (35) and TV/XR (34) have their own tiers — so find your targetSdkVersion, bump compileSdk and targetSdk together, review the Android 16 behavior changes, test on Android 16 hardware, and if you cannot make it, request the extension to November 1, 2026.

Sources

Shipping an app that must meet Google Play's target API level requirements — or managing a Play Console account that needs compliance work? KappS handles API migrations, release compliance, and Play Console account operations for app developers.

Talk to KappS →