From August 31, 2026, Google Play requires new mobile apps and app updates to target Android 16, API level 36. Existing mobile apps must target Android 15, API level 35, to remain available to new users on devices running newer Android versions. This is a release gate, not a store-listing edit.

The rule in one table

  • New mobile apps and updates: target API 36 or higher.
  • Existing mobile apps: target API 35 or higher to stay available to new users on newer Android versions.
  • Deadline: August 31, 2026.
  • Extension: eligible apps can request additional time until November 1, 2026 in Play Console.

Wear OS, Android Automotive OS, Android TV, and Android XR have different thresholds. Check the current platform table in Google's target API level requirements before submitting.

Check every active release track

Open Play Console and record the target API of the artifacts serving production, open testing, and closed testing. Then check the candidate bundle your CI is about to upload. A local project setting is not proof that the signed artifact uses the same value.

Do not confuse target SDK with minimum SDK

Raising targetSdkVersion opts the app into newer platform behavior. It does not automatically drop support for older devices; that is controlled separately by minSdkVersion.

Test the behavior changes, not only the build

  1. Update the compile and target SDK with a compatible Android Gradle Plugin and toolchain.
  2. Review Android 16 behavior changes that apply when targeting API 36.
  3. Update SDKs that are incompatible with the new target.
  4. Run permission, background work, notifications, deep links, edge-to-edge, and billing flows on a current Android device.
  5. Ship to an internal track and inspect the artifact details in Play Console.

Release ticket checklist

Target API in signed AAB: 36
      Production artifact checked: yes
      Android 16 behavior tests: passed
      Third-party SDK audit: complete
      Internal-track install: verified
      Extension needed: no

What happens if you miss it

A non-compliant update cannot be submitted after the deadline. An older existing app can also lose discovery for new users on newer Android versions. Current users may still have access, but that is not a safe distribution strategy. Treat target API compliance as a standing release check rather than an annual emergency.

Was this article helpful?