OOmnistu

Blog / Mobile App Development

Mobile App Development

Google Play's target API requirements are now current events: API 36 to ship, 35 to stay visible

Since 31 August 2026 new apps and updates must target Android 16 (API 36); existing apps below API 35 are hidden from new users on newer devices, and the 1 November extension deadline has passed. The per-platform table, what users see, and the remaining options.

OOmnistu
Reviewed 2026-11-19 · 4 min read

Every year Google Play raises the floor under new submissions, and every year a slice of published apps quietly falls below it. The 2026 round is no longer upcoming: it has been in force since 31 August, the extension window closed on 1 November, and the consequences are now visible to users as a store-listing message. If you ship or maintain an Android app, this is a current-state check, not a planning item.

What Play requires now

Since 31 August 2026, new apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher. The bar is lower on the smaller platforms: Wear OS and Android Automotive OS submissions must target Android 15 (API level 35), and Android TV and Android XR submissions must target Android 14 (API level 34).

Existing apps face a separate rule. To stay available to new users on devices running a newer Android version than your app targets, an existing app must target at least Android 15 (API level 35) - Android 14 for Wear OS and Android XR, Android 13 for Android TV, and Android 12L for Android Automotive OS. Drop below that line and the app is not removed from the store; it stops being discoverable and installable for anyone whose device runs a newer OS version than the app targets. People on older devices keep seeing it.

What users actually see

Google's help page spells out the user-facing message: someone on a newer device who finds your listing is told the app "is not available to install on their device because it was made for an older version of Android." That is the whole penalty - no suspension, no strike - but it quietly caps your addressable audience at the devices that existed when you last updated. For an app that relies on a steady inflow of new users, the effect compounds with every Android release cycle you skip.

The extension window has closed

Google offered an extension for teams that needed more time: a request through Play Console would have kept a non-compliant app fully distributed until 1 November 2026. That date has passed. The extension form was reachable through the policy warning on the Policy status page in Play Console, and only apps flagged as non-compliant received it. If your app is below the line today, the remaining options are the blunt ones: ship an update targeting the required API level, or accept the shrinking audience - or unpublish if the app is intentionally retired.

One carve-out exists: permanently private apps, restricted to a specific organization and distributed internally, are excepted from these requirements.

targetSdkVersion is a promise, not a preference

The mechanism behind all of this is a single manifest value. targetSdkVersion declares which Android version's behavior changes your app has been adapted and tested against; minSdkVersion sets the oldest device that can install at all. Raising the target is not a text edit - each new API level brings behavior changes your app inherits, which is why Google ties the requirement to security, privacy and performance improvements and why the migration work is real. But the store's leverage is simple: the target you declare decides who can see your listing.

A short checklist

The honest summary

Play's target API rules are now a present-tense filter on your store presence: target Android 16 to ship anything new, and target at least Android 15 (or the per-platform equivalent) or watch new-device users bounce off a message saying your app is too old for them. The extension deadline passed on 1 November 2026. The fix is the same as it has always been - keep the target current - but the grace period is over.

Sources

Prepared with AI assistance and reviewed before publication. API levels, dates, per-platform thresholds and the extension mechanics are drawn from the Play Console Help page above, checked on 19 November 2026.