Google Play Target API 36: What App Owners Must Do

TL;DR

Since 31 August 2026, new apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS need API 35, and Android TV and Android XR need API 34. Existing apps that do not update still stay on the store, but they become unavailable to new users on newer Android versions. Check the current rules in Google Play Console before acting, because dates and extensions change.

The requirement in one table

This is a summary of the Android developer documentation on target API level requirements, as we read it on 26 October 2026 (page last updated 16 October 2026). Re-check it before you act, because Google updates the page.

App type	Required target API level for new apps and updates
Phone and tablet apps	Android 16 (API 36) or higher
Wear OS and Android Automotive OS	Android 15 (API 35) or higher
Android TV and Android XR	Android 14 (API 34) or higher

Effective date: 31 August 2026.
Extension: the documentation said developers could request an extension to 1 November 2026, with the request form to appear in Play Console. If that date has passed or the form is gone, treat the requirement as in force.
Exempt: permanently private apps restricted to one organisation and distributed internally.

Source: Target API level requirements for Google Play apps.

Who is affected and what happens if you miss it

You publish an update: the update must target API 36 (or the level above for your device type) to be accepted.
You do not update: the app stays on Google Play. According to the documentation, apps whose target is below the required level for existing apps (API 35 for phones) are only available to users on devices running the same or an older Android version than the app’s target. In practice, people with newer phones may not see or install the app.
You have a new app: you cannot submit it without meeting the target level.

So the real risk is not a sudden removal but gradual loss of reach and the inability to ship fixes.

Requesting an extension

If you are still inside an extension window, request it in Play Console. If the date has passed, the practical path is to update and test now. Do not plan around an extension that may no longer exist.

Behaviour changes to test on Android 16

Raising the target level opts the app in to new platform behaviour. Before you ship, review the behaviour changes for apps that target Android 16 on developer.android.com and test the flows that are most likely to break: permissions, background work, notifications, media access, edge-to-edge layouts and any library that wraps platform APIs. We do not list each change here because the official list is the reliable source and it changes between releases.

Upgrade checklist

Read the official Android 16 behaviour changes for apps that target it.
Update the build: targetSdk and compileSdk to 36, plus Android Gradle Plugin and Gradle to compatible versions.
Update dependencies that wrap platform APIs (push, maps, billing, analytics, ad SDKs).
Test on a real Android 16 device or emulator, including install, upgrade from the previous version, login, payments and push.
Staged rollout rather than 100% on day one, and watch crash reports.
React Native: upgrade React Native or the Android template to a version that supports API 36 and check native modules.
Flutter: upgrade Flutter and plugins, then rebuild the Android project with the new target.
Native (Kotlin/Java): fix deprecation warnings and run your UI and instrumentation tests.

When to hire help and when to do it in-house

An app with a small, recent codebase and good tests can usually be upgraded in-house. Bring in help when the code is old, when key libraries are unmaintained, when there is no test coverage, or when you do not have the people to test on real devices. We offer a mobile app development service that includes updates and store-compliance reviews.

Plan for next year’s cycle

Google has repeatedly raised the target level on a regular cycle, so plan a yearly maintenance slot rather than treating this as a one-off. For a broader view of tooling choices, see the best technologies for your startup and vibe coding vs agentic engineering.

Frequently asked questions

What is the Google Play target API requirement for 2026? New apps and updates must target Android 16 (API 36) or higher from 31 August 2026, with lower levels for Wear OS, Automotive OS, TV and XR, as shown in the table above.

Can I still request an extension after the extension date? The documentation mentioned an extension to 1 November 2026. After that date, do not count on one. Check Play Console for the current options.

What happens to my app if I do not update the target API level? It stays on Google Play, but it becomes unavailable to users on newer Android versions than the app’s target, and you cannot publish new updates that do not meet the requirement.

Does a Flutter or React Native app need extra steps for API 36? Yes. Upgrade the framework and plugins or native modules to versions that support API 36, then rebuild and test the Android project.

How often does Google raise the target API requirement? Google has raised it on a regular cycle in recent years, so plan for it as part of yearly maintenance.

Need an app update or a compliance check?

Tell us about the app and we will scope the upgrade, testing and rollout. See our mobile app development service or contact us.