Google Play Target API Level Requirement: What App Owners Must Do

The rule in one paragraph

Every year Google raises the minimum target API level for apps on Google Play. Since 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted. Existing apps must target at least Android 15 (API level 35) to stay fully available.

What happens if your app is behind

• You cannot upload updates. Play Console rejects a new version that targets a lower API level.
• Your live app slowly disappears for new users. An app that targets too low a version is only offered to devices on the same or an older Android version, so people with newer phones stop seeing it.
• Small bugs pile up. Apps that fall behind on target level are usually behind on security and compatibility too.

How to check your app's current target level

Open your app's build.gradle (or build.gradle.kts) and look for:

android {
    compileSdk = 36
    defaultConfig {
        minSdk = 24
        targetSdk = 36
    }
}

If targetSdk is below 36, your next update will be blocked. You can also see warnings in Play Console under Policy and programs → App content and in your inbox.

How to update the target API level

1. Back up and branch. Work on a copy of the project, never on your only version.
2. Update the build tools. Newer Android Gradle Plugin, Gradle and Kotlin versions are usually needed before API 36 will compile.
3. Set compileSdk and targetSdk to 36.
4. Update old libraries. Abandoned or outdated dependencies are the most common cause of build errors.
5. Review Android 16 behavior changes and fix what affects your app (see below).
6. Test on an Android 16 emulator and a real device. Check login, payments, notifications, permissions and screen layouts.
7. Build a signed App Bundle (.aab) and upload it to a closed or internal test track first, then roll out to production.

What usually breaks in older apps

Edge-to-edge screens

Newer Android versions draw apps behind the status and navigation bars. Apps that were never designed for this can show buttons hidden under system bars.

Back button behavior

Android is moving to predictive back gestures. Old custom back handling can stop working as expected.

Large screens and rotation

On tablets and foldables, Android increasingly ignores fixed-orientation locks, so layouts that assumed a phone in portrait can look broken.

Permissions, background work and notifications

Each Android release tightens rules about background services, exact alarms, notification permission and file access. Older apps that rely on these often need code changes.

Native code and 16 KB page size

If your app includes native libraries (C/C++ or some game and media SDKs), they must also support 16 KB memory pages. Google's documentation currently says updates that do not will be blocked from 1 February 2027. Apps written only in Java or Kotlin already work. See our 16 KB guide.

Should you fix it yourself or hire someone?

DIY is realistic if the app was built recently, uses current libraries and you have a developer who knows the codebase.

Get help if the original developer is gone, the project no longer builds, the code is several years old, or you are on a tight deadline. In those cases the target level is rarely the only problem, and a stuck update costs you users every week.

Frequently asked questions

Keep reading

• Elaaj: Updating an Urdu and English Health App for Google Play
• Play Billing Library 8: What App Owners Need to Know
• Android Build Failed After an SDK Update? 8 Common Errors and Fixes