Skip to content
Technical note· 6 min read
Published: Updated:

Google Play's API 36 requirement: The deadline has passed, now what?

Since August 31, 2026, new apps and updates submitted to Google Play must target Android 16 (API 36). Extensions end on November 1, 2026. What happens to apps with a lower target, and the steps to take now.

Short answer

Since August 31, 2026, Google Play has required new apps and updates to target at least API 36 (Android 16); an extension to November 1, 2026 could be requested in Play Console. Published apps must target at least API 35; apps targeting API 34 or lower are not shown to new users on newer Android versions. Users who already installed the app are not affected.

Free toolApp Store and Google Play deadlines

The August 31, 2026 deadline has passed. Google Play now requires new apps and updates to target Android 16 (API 36). If you received an extension, your time runs out on November 1, 2026. This post summarizes what the rule actually says, what happens to apps with a lower target, and what to do now, based on Google's official pages.

Dates and rules

RuleDateDetails
New apps and updatesAugust 31, 2026At least API 36 (Android 16). Wear OS and Android Automotive OS: API 35. Android TV and Android XR: API 34
ExtensionUntil November 1, 2026Requested in Play Console, from the details of the warning on the Policy status page
Published appsAugust 31, 2026At least API 35 (Android 15) to stay available to new users on newer Android versions
ExceptionPermanentPermanently private apps distributed only to users within one organization

To see this and other store deadlines in one table, use the app store deadlines tool.

What happens to apps with a lower target?

Google's official pages distinguish three cases:

  • New apps and updates: a release that does not target API 36 cannot be submitted to Google Play (apps with an extension have until November 1, 2026).
  • Published apps that are not updated: if the app targets API 34 or lower, it is only available on devices running an Android version equal to or lower than its target. New users on devices with newer Android versions cannot install it.
  • Users who already installed the app: not affected. According to Google, they can still discover, reinstall and use the app on any Android version it supports.

When a new user cannot install the app, Google Play shows a message saying it is not available on their device because it was made for an older version of Android. Users arriving from an ad or a link cannot install it, while your existing user base stays the same.

What to do now

  1. Open your app's Policy status page in Play Console; the target API warning or extension details appear there.
  2. List your dependencies and find the API 36-compatible version of each library.
  3. Set the target to 36 in your Gradle file (or the uses-sdk element in the manifest) and rebuild the app.
  4. Test each Android 16 behavior change that applies to apps targeting API 36 (see below).
  5. Upload the release to the internal testing track in Play Console first, then roll it out.
gradle
android {
    defaultConfig {
        targetSdk = 36
    }
}

What changes when you target API 36

From Google's Android 16 behavior changes page, these are the items that affect only apps targeting API 36 and most often cause problems:

  • Edge-to-edge: the option to opt out of edge-to-edge display is gone; content extends behind the status and navigation bars.
  • Predictive back: system back animations are on by default; onBackPressed() is no longer called.
  • Large screens: on displays with a smallest width of 600dp or more, orientation, resizability and aspect ratio restrictions are ignored.
  • elegantTextHeight: the attribute is deprecated and ignored.
  • Health permissions: BODY_SENSORS is replaced by granular android.permissions.health permissions.

The full list, plus the changes in earlier versions (Android 13, 14, 15), is on the official page. If your app targets API 33 or older, review those versions' changes too.

If you need help keeping your app live and up to date, see our React Native app development service.

Frequently asked questions

My app is simple. Do I still need to update if the behavior changes don't affect me? Yes. The rule looks at the target API level, not at what the app does. To submit a new release, the target must be API 36.

I use React Native or Flutter. Won't the framework handle this? Partly. The target is set in your project's Android configuration; check the targetSdk value in your Gradle file instead of relying on the framework's default. Test third-party packages for API 36 compatibility separately.

If I don't ship an update, will my app be removed from the store? No. According to Google's page, the app stays published and existing users are not affected. But if it targets API 34 or lower, new users on devices with newer Android versions cannot install it.

My app hasn't been updated in a long time. Where do I start? Read the behavior changes page for every version from your current target up to API 36, in order, and test at each step. If the codebase and dependencies are very old, it can make sense to compare the migration cost with a rewrite.

Sources

#güncel#android#google play

Have a project in mind?

A short description is enough; if it isn't clear yet, we can think it through together. We'll write back within one business day.

With your consent, we use analytics cookies to improve the site and measure visits. Cookie policy