Google Play's yearly target API deadline: keeping your app listed

Short answer: Every year Google Play raises the minimum Android version that apps must "target". As of November 2026, new apps and updates must target Android 16 (API level 36), and existing apps must target at least Android 15 (API level 35) to stay visible to new users on newer phones. The deadline was August 31, 2026, with extensions running to November 1, 2026, so if your app has not been updated this year, it may already be hidden from many new users.

Many small business apps are built once and then left alone because they "still work". On Android, they keep working for people who already installed them, but Google Play quietly stops offering them to new customers with recent phones. This guide explains the rule, the timeline and what an update involves.

What "target API level" means

Every Android app declares a target API level, a number that tells Android which version's behavior the app was built and tested for. Each new Android version adds security, privacy and performance changes, and apps that target an older level can skip some of them. Google's target SDK page explains that targeting a recent level ensures users get those improvements, which is why Play enforces a moving minimum.

The target level is different from the minimum Android version your app supports. You can target the newest level and still run on older phones.

The 2026 timeline

According to Google's developer page and the Play Console help article, as of November 2026:

From August 31, 2026, for new apps and app updates

Phone and tablet apps must target Android 16 (API level 36) or higher to be submitted.
Wear OS and Android Automotive OS apps must target Android 15 (API 35) or higher.
Android TV and Android XR apps must target Android 14 (API 34) or higher.

From August 31, 2026, for existing apps (availability)

Existing apps must target Android 15 (API level 35) or higher to remain available to new users on devices running newer Android versions.
Apps targeting Android 14 (API 34) or lower are only offered on devices running the same or an older Android version than their target. Different thresholds apply to Wear OS, TV, XR and Automotive.

Extension

Developers could request an extension to November 1, 2026 through a form linked from the policy warning in Play Console.

Exceptions exist for permanently private apps distributed only inside one organization.

What happens if you missed it

Google's help article spells out the effects:

Existing users are not affected. People who already installed the app can still find it, reinstall it and use it on any Android version it supports.
New users on newer phones cannot install it. If someone with a recent device follows a link to your store page, Google Play tells them the app is not available for their device because it was made for an older version of Android.
Downloads may drop, since a growing share of phones run newer Android versions.
You cannot ship updates that do not meet the current target level, which matters the moment you need to fix a bug.

The app does not disappear from the store entirely. That is what makes this easy to miss: the business owner, on an older phone or with the app already installed, sees nothing wrong.

What an update involves

Raising the target level is sometimes a small change and sometimes a project. It depends on how far behind the app is and how it was built.

Typical work:

Changing the target version in the build configuration and updating the build tools.
Updating libraries and SDKs (maps, payments, analytics, push notifications, login), which often need newer versions to support the new target.
Handling behavior changes introduced in the Android versions you are jumping over. Google publishes these per version; they can affect permissions, background work, notifications, and how the app draws on screen.
Updating cross-platform frameworks such as Flutter or React Native first, if the app uses one, because the framework version determines which target levels are supported.
Testing on real devices running recent Android versions, plus at least one older device you still support.
Uploading through the normal release process, ideally via a testing track first.

An app that skipped several years of updates may need significant library upgrades before the target level can move. That is the expensive case, and the reason to plan the bump every year.

Checklist: what your developer needs to do

Hand this list to whoever maintains the app:

[ ] Check the app's current target level and the Policy status page in Play Console for warnings
[ ] Confirm the current year's requirement on Google's target SDK page
[ ] Update the framework (if any), build tools and Android Gradle setup
[ ] Update third-party SDKs to versions that support the new target
[ ] Review Google's behavior-change list for each skipped Android version
[ ] Test sign-in, payments, notifications, location, camera and file uploads on a recent device
[ ] Release to an internal or closed test track, then production
[ ] Note the next deadline in the calendar

Planning the yearly maintenance

Treat the target level as an annual service, like renewing your domain:

Spring: check Google's target SDK page for the coming requirement and whether it has changed.
Early summer: schedule the update with your developer, combined with any small fixes.
Before the deadline: release, and confirm no warning remains in Play Console.

The Apple side, briefly

Apple has its own rolling minimums. Apple's upcoming requirements page states that since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK (or the matching SDK for other Apple platforms), and since September 9, 2026, iOS and iPadOS apps must target iOS 13 or later. Apple's rules apply when you upload a new build; they do not hide existing apps in the same way. If you maintain both versions, plan them together.

FAQ

My app works fine on my phone. Is it really affected?

Possibly. Existing installs keep working, and your phone may run an older Android version. Check the Play Console for policy warnings, or ask your developer for the app's target level.

Can I still request an extension?

Google's pages describe the extension as running to November 1, 2026. After that, the practical path is to update the app.

Will updating change how the app looks?

Usually not much, but newer Android versions can change layout and notification behavior, so test the main screens carefully.

How long does the update take?

It ranges from a short job for a recently maintained app to a larger project for one that has not been touched in years. Ask for an estimate after your developer has checked library versions.

If your Android app has fallen behind Google Play's target level, we can check what it needs.