Beyond the News
Sign in
Marketing & DistributionMarketplaces & Platforms Active dossier

Google Play’s August 31 target-API deadline can block updates and hide older apps from new users

From August 31, Google Play requires most new apps and updates to target Android 16 / API 36, while older existing apps that miss a lower availability threshold can disappear for new users on newer Android devices.

Reviewed and published by Lars Jansen Updated 6 min read
Comment
First published
Illustration of a Google Play policy deadline showing “Aug 31 Target API Deadline,” a phone displaying compliant and older apps, and a warning that older apps may be hidden from new users if they are not updated to the required target API level.
Google Play’s August 31 target-API deadline can block app updates and reduce visibility for older apps that don’t meet the new requirements.

Key details

  1. The main Google Play cutoff begins August 31, 2026.
  2. Most new Android apps and app updates must target Android 16 / API level 36 or higher.
  3. Most existing apps must target Android 15 / API level 35 or higher to remain available to new users on devices running Android versions newer than the app’s target API level.
  4. Wear OS and Android Automotive OS submissions use an API 35 threshold; Android TV and Android XR use API 34.
  5. Google says developers can request an extension to November 1, 2026 if they need more time.
  6. Permanently private apps restricted to a specific organization are among the documented exceptions.
  7. Raising targetSdkVersion to 36 activates Android 16 target-specific behavior changes that can require application testing and code changes.

What builders should take away

  1. Audit every Play-listed app now and record its current targetSdkVersion, release pipeline owner and whether another update is expected before August 31.
  2. For apps that still need to ship updates, build and test against API 36 before the deadline; do not treat a targetSdkVersion bump as a metadata-only change.
  3. For maintenance-mode apps, check whether missing the API 35 existing-app threshold would materially reduce new-user acquisition on newer devices even if the currently installed user base keeps working.
  4. Test Android 16 target-specific behavior in navigation, edge-to-edge layouts, permissions, background work and third-party SDKs before promoting the build.
  5. Use the Play Console extension to November 1 when a safe migration genuinely needs more time, while keeping a concrete upgrade plan rather than relying on the extension as a permanent exception.
  6. Add the annual Google Play target-API cycle to release-maintenance planning so dormant mobile surfaces do not become surprise distribution liabilities.

What changed

Starting August 31, 2026, Google Play requires most new apps and app updates to target Android 16, API level 36, or higher. The platform also applies a separate availability rule to existing apps: most existing apps must target Android 15, API level 35, or higher to remain available to new users whose devices run an Android version newer than the app’s target API level. Google says developers who need more time can request an extension to November 1, 2026 through Play Console. Wear OS and Android Automotive OS use a lower API 35 submission threshold, while Android TV and Android XR use API 34.

Why it matters

This is not only a build-system maintenance deadline. For teams still shipping an older target SDK, August 31 can stop new releases from being accepted; for neglected or maintenance-mode apps, falling below the existing-app threshold can narrow acquisition by making the app unavailable to new users on newer Android versions. Raising targetSdkVersion can also activate Android 16 behavior changes, so the safe path is a tested migration rather than a last-minute manifest edit. SaaS and independent developers with companion Android apps should treat Play distribution as a versioned platform dependency with an explicit annual maintenance budget.

New apps and updates move to API 36

For ordinary Android phone and tablet apps, Google Play requires new submissions and app updates from August 31 to target Android 16 / API level 36 or higher. The requirement is different for some form factors: Wear OS and Android Automotive OS apps need API 35 or higher, while Android TV and Android XR apps need API 34 or higher. Builders should verify the exact targetSdkVersion in the release artifact rather than assuming a newer compile SDK or Android Studio version satisfies the policy.

Existing apps face a separate discovery rule

An app that is already published does not simply disappear from every device when it misses the newest submission target. Instead, most existing apps need to target API 35 or higher to remain available to new users on devices running an Android version newer than the app’s target API level. Apps below that threshold remain available on devices running an Android version equal to or older than the app’s target. That makes the commercial consequence a distribution restriction rather than an immediate universal shutdown.

API 36 can change runtime behavior

Moving targetSdkVersion forward opts an app into Android 16 target-specific behavior changes. Google’s migration guidance calls out changes that can require code and UX work rather than a configuration-only bump, including edge-to-edge enforcement changes, predictive-back behavior and other platform restrictions. Teams should therefore test core navigation, layouts, permissions, background behavior, SDK dependencies and device compatibility against an API 36-targeting build before submitting it.

There is an extension path, but it should not replace migration work

Google says developers who need additional time can request an extension to November 1, 2026, with extension forms available through Play Console. That gives teams a fallback for a migration that cannot be safely completed by August 31, but it does not remove the underlying target-API requirement. Owners of low-maintenance apps should use the extra window to decide whether the app remains supported, needs a tested target-SDK upgrade, or should be deliberately left with narrower new-user availability.

What to watch next

  • Whether Google changes the August 31 enforcement timing or extension mechanics before the cutoff.
  • Play Console warnings and enforcement behavior for apps close to the existing-app availability threshold.
  • Third-party SDKs that lag API 36 compatibility and become blockers for otherwise simple target-SDK upgrades.
  • The next annual Google Play target-API requirement and how Android’s annual major API cadence affects future deadlines.

Still unclear

  • Google documents the November 1 extension path, but the exact Play Console workflow and approval behavior can depend on the app/account context.
  • The practical revenue or acquisition impact of the existing-app availability rule depends on the share of prospective users running Android versions newer than an app’s target level.
  • Targeting API 36 does not affect every app in the same way; the migration cost depends on which Android 16 behavior changes and third-party SDKs touch the application.

Sources

Direct reading behind this dossier.

3 sources
Meet Google Play's target API level requirement
Android Developers / Google primary

Primary Google documentation for the August 31, 2026 submission and existing-app availability thresholds, form-factor exceptions, and November 1 extension path.

Migrate apps to Android 16
Android Developers / Google primary

Primary migration guidance explaining that targeting Android 16 requires review and testing of target-specific behavior changes.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading