AI & TechnologyGoogle Play Requires Target API 36: The Android 16 Update

Since August 31, 2026, Google Play only accepts new apps and updates that target Android 16 (API level 36), and Google says you'll be able to request an extension to November 1, 2026. Raising targetSdkVersion is one line, but it turns on Android 16 behavior: no edge-to-edge opt-out, predictive back by default, and no orientation lock on tablets. Test those three before you ship. In a Flutter app, the quickest path is usually Flutter 3.35 or later, which targets 36 by default.

The requirements below come from Google's target API page and its Android 16 behavior changes, and the Flutter defaults from Flutter's source code, as listed in the sources. I checked each one on October 18, 2026.

Disclosure: App369 is my studio. I build and fix Android and iOS apps, mostly in Flutter, and the last section mentions what I sell. Google doesn't pay me for anything on this page.

The requirement

Source: Google Play target API level requirement, last updated October 16, 2026.

Google's page also says:

• Extension: if you need more time, you'll be able to request an extension to November 1, 2026. Google says the extension forms will be in Play Console "later this year", so check there for the form.
• Existing apps: to stay available to new users on devices running a newer Android version than the app targets, an existing app must target API 35 or higher. An app that targets API 34 or lower is only available on devices running that Android version or lower.
• Exception: permanently private apps for one organization's internal use.

What changes when you target API 36

Google's Android 16 behavior changes apply to apps that target API 36 and run on Android 16 or higher. These are the three I'd test first:

The large-screen rule doesn't apply to games (based on android:appCategory), to screens smaller than 600dp, or when users opt in to the app's default behavior in the device's aspect ratio settings.

Flutter apps

Flutter's project template sets the target from the Flutter version: targetSdk = flutter.targetSdkVersion in android/app/build.gradle.kts in Flutter 3.35's template, and targetSdkVersion flutter.targetSdkVersion in older Groovy templates such as Flutter 3.10's. Flutter's FlutterExtension source sets it to:

Release dates from Flutter's release archive.

What that means for a Flutter app:

1. Check android/app/build.gradle or build.gradle.kts. If it uses flutter.targetSdkVersion, Flutter 3.35 or later gives you 36. If it has a hard-coded number, change it to 36 yourself (targetSdk = 36 in a build.gradle.kts file).
2. Edge-to-edge. My advice: Flutter draws its own UI, so the visible risk is content under the status or navigation bar. Check every screen with SafeArea or padding from MediaQuery, including bottom sheets and screens with a bottom bar.
3. Back navigation. If the app or a plugin overrides onBackPressed in Android code, that override won't be called on Android 16. My advice: use PopScope on the Flutter side for back handling, and check plugins that intercept back.
4. Tablets. If the app locks orientation with SystemChrome.setPreferredOrientations or the manifest, test it on a tablet or a large emulator, because Google says that lock is ignored on screens 600dp or wider.

If an older app can't move to Flutter 3.35 because the Android build breaks first, the v1 embedding fix and the Gradle plugin fix cover the two errors Flutter 3.29 introduced. If the app sells in-app purchases, the Billing Library 8 deadline is due at the same time.

What to do now

This section is my advice, not Google's.

1. Check the target your last release used. Look at targetSdk in the build file for that release, or the app bundle details in Play Console.
2. Request the extension if the change won't ship in time, once the form appears in Play Console. As of October 18, 2026, the November 1 extension date is two weeks away.
3. Raise the target, then test on an Android 16 device or emulator. Go through every screen for edge-to-edge, try the back gesture everywhere, and rotate on a tablet-sized emulator.
4. Ship to a closed testing track first. Catch layout and back-gesture issues before your users do.

Need a hand?

If an app can't ship an update because of the target API requirement, or something broke after raising it, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. Or send me a short description.