Google Play target API 36: what the August 2026 rule means for your app

Since August 31, 2026, new apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher. Wear OS and Automotive apps need API 35; TV and XR apps need API 34. The extension Google offered ran until November 1, 2026, and is over.

If you're starting a closed test now, your first build should already target 36.

The rule, exactly

From Google's target API level requirements:

• "New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play; except for Wear OS, and Android Automotive OS apps, which must target Android 15 (API level 35) or higher, and Android TV and Android XR apps, which must target Android 14 (API level 34) or higher."
• "Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running Android OS higher than your app's target API level."

Google's definitions: a new app is one not yet published on Google Play; an app update is a new version submitted to replace an existing one. The only listed exception is permanently private apps restricted to one organization.

The extension is over

Google allowed developers to request more time, until November 1, 2026, through a form in Play Console (Play Console Help). As of November 8, 2026, that date has passed. Plan as if there is no extension.

Why it matters during closed testing

New personal accounts publish their first builds on the closed track, and those builds have to follow the same submission rules. Google's page doesn't exempt testing tracks. Practically:

• Build the closed test release with targetSdk = 36. The same bundle can then be promoted to production after Google grants access.
• Don't change the target API in the middle of the test if you can avoid it. A target bump changes app behavior (see below). It's better to ship that change before day 1 than to discover problems on day 12.
• Updates during the test are fine. Google encourages updating your app during closed testing (Play Console Help). Each update must also target 36.

How to set the target API

In your app module's Gradle file (Android Developers):

// build.gradle.kts
android {
    compileSdk = 36
    defaultConfig {
        applicationId = "com.example.myapp"
        minSdk = 24
        targetSdk = 36
        versionCode = 12
        versionName = "1.2"
    }
}

// build.gradle (Groovy)
android {
    compileSdkVersion 36
    defaultConfig {
        targetSdkVersion 36
    }
}

Google says you can set it in the Gradle file or with the android:targetSdkVersion attribute of the manifest's <uses-sdk> element (Android Developers). Most projects set it in Gradle, so check there first.

Cross-platform frameworks often set the value through their own variables or SDK versions. See the framework notes for Flutter and React Native and Expo.

Also check your SDKs and libraries. Google's migration guide says to verify that third-party SDKs support the API level you target, and to work with the provider if they don't (Android Developers).

What changes when you target Android 16

Targeting 36 turns on behavior changes that only apply to apps targeting it. From Google's Android 16 behavior changes:

Edge-to-edge, no opt-out. Android 15 let apps opt out of edge-to-edge with windowOptOutEdgeToEdgeEnforcement. For apps targeting 36 on Android 16, that attribute is "deprecated and disabled". Check that toolbars, bottom bars and buttons don't sit under the status or navigation bar.

Predictive back. For apps targeting 36 on Android 16 devices, the predictive back animations are on by default, "onBackPressed is not called and KeyEvent.KEYCODE_BACK is not dispatched anymore." If your app intercepts back, migrate to the supported back APIs, or temporarily opt out with android:enableOnBackInvokedCallback="false" in the manifest.

Large screens ignore orientation and resizability locks. On displays with a smallest width of 600dp or more, "orientation, resizability, and aspect ratio restrictions no longer apply." A portrait-locked app fills a tablet in landscape. Games (declared with android:appCategory) are excepted. There's a temporary opt-out property, android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY, which Google says won't apply once you target API 37.

elegantTextHeight is ignored. Check text layout if your app shows Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu or Thai.

Fixed-rate scheduling. With scheduleAtFixedRate, at most one missed execution runs when the app comes back to a valid lifecycle, instead of all of them.

The page lists more changes, including health and fitness permissions, Bluetooth bond handling, and opt-in stricter intent resolution. Read the sections that touch your features.

A test plan for the target bump

Google's migration guide suggests testing core flows after changing the target, including denied permissions, Doze and App Standby, and file sharing with other apps (Android Developers). For API 36, add:

1. Back navigation on an Android 16 device or emulator, with gesture navigation on.
2. Every screen edge to edge: status bar, navigation bar, keyboard open.
3. A tablet or foldable emulator in both orientations, if your app locks orientation.
4. Text rendering in any of the scripts listed above, if you support them.

Your closed test is a good place to catch the rest. Ask testers which device and Android version they use, and look for patterns in bug reports from tablets and Android 16 phones.

Checklist

• compileSdk and targetSdk set to 36 (35 for Wear OS and Automotive, 34 for TV and XR).
• Third-party SDKs updated to versions that support API 36.
• Back handling migrated, or the temporary opt-out set on purpose.
• Edge-to-edge layouts checked on Android 16.
• Large-screen behavior checked if you lock orientation.
• versionCode increased for every new upload.

Then set up the track: How to set up a closed test. For the whole process, see the Google Play closed testing guide.