Since 31 August 2026, apps that target Android 14 or lower are hidden from new users on newer phones. One example app, walked through from the warning to the fixed release.
If your app targets Android 14 (API level 34) or lower, Google Play stopped offering it to new users on newer phones on 31 August 2026. Someone on Android 15 or 16 who finds your listing is told the app was made for an older version of Android and can't be installed. Getting back in front of them takes an update that targets Android 16 (API level 36), because that has been the minimum for any update since the same day. People who already have the app keep it.
The rest of this post follows one illustrative app from the warning to the fixed release.
The example app
Picture a home workout app with a monthly subscription. It's made up for this post, not a client. It was built in Flutter in early 2024, last updated in March 2025, and its Android build targets API level 34. Subscriptions run through Google Play Billing Library 6. Nobody has opened the code since, because nothing broke.
In September, sign-ups from Play drop while existing subscribers carry on.
What changed on 31 August 2026
Google's target API level requirements for Google Play apps set two separate bars on that date, and it's the gap between them that catches people out:
- To stay visible: existing apps must target Android 15 (API level 35) or higher, or they stop being offered to new users whose phones run a newer Android than the app targets.
- To ship anything: new apps and every update must target Android 16 (API level 36) or higher. Wear OS and Android Automotive OS apps need API 35, and Android TV and Android XR apps need API 34.
Our example targets 34, so it fails the first bar. Owners could ask for an extension to 1 November 2026 through a form linked from the warning on the Policy status page in Play Console. That date has passed too, so the only way back is a compliant update.
The bar rises every year. Google's table shows the update minimum at API 35 from 31 August 2025 and API 36 from 31 August 2026, so expect the same exercise again next summer.
Who can still find the app
The cut-off follows the app's own target. Google hides it only from phones running a newer Android than the one it was built for. For an app targeting API 34, that works out like this:
| Phone runs | New user can install? | Existing user can reinstall? |
|---|---|---|
| Android 13 (API 33) | Yes | Yes |
| Android 14 (API 34) | Yes | Yes |
| Android 15 (API 35) | No | Yes |
| Android 16 (API 36) | No | Yes |
Google's FAQ admits this may cut downloads. That's an understatement: the phones that can still see the listing are the older ones, and there are fewer of them each month.
The reason is simple. Each Android release changes how apps behave, and the target level tells the system which rules an app was written for. The minimum SDK version still decides how old a phone can run it, so raising the target doesn't drop older devices.
Why the update jumps two levels, not one
API 35 is enough to be visible again, so moving from 34 to 35 sounds like the small job. But you can't upload a build that targets 35 any more, because every update now has to target 36. The workout app has to go from 34 to 36 in one release, and it picks up two years of behaviour changes at once.
In Flutter the target is one value in the Android build file, so the job looks like five minutes. The next section explains why it isn't.
What the jump to API 36 breaks in this app
Three of the behaviour changes for apps targeting Android 16 hit the example directly.
Screens now run edge to edge. Android 15 forced edge-to-edge drawing on apps targeting API 35 but let them opt out with a flag. For apps targeting 36, that opt-out is disabled on Android 16 phones. The workout app's header assumed the status bar sat above it. Now the timer slides under the clock and the camera cutout, and every screen needs its insets handled.
The back gesture works differently. On Android 16 devices, apps targeting 36 get the predictive back animations by default, and the old onBackPressed callback is no longer called. The app's "quit this workout?" prompt was built on that callback, so swiping back now skips it and throws away the session. That prompt has to be rebuilt on the newer back handling.
Portrait lock stops working on tablets. On any display whose smallest width is 600dp or more, Android 16 ignores orientation, resizability and aspect ratio restrictions for apps targeting 36. The app was locked to portrait. On a tablet or an unfolded foldable it now turns sideways and fills the screen, and a one-column layout stretches across it.

Two other deadlines that land on the same update
The target level is rarely the only thing out of date in an app that has sat still for 20 months.
Billing. Every Play Billing Library version gets a two-year life. The deprecation table put version 7's deadline at 31 August 2026, so new apps and updates must now use version 8 or later. Our example is on version 6. Its first update has to move the subscription code forward two major versions. Version 8 itself runs out on 31 August 2027.
16 KB memory pages. Apps targeting Android 15 and higher must support 16 KB page sizes on 64-bit devices, and from 1 February 2027 Play won't let you release an update that doesn't. This bites when the app or a plugin ships compiled native libraries. A newer version of that plugin tends to fix it.
The update, step by step
For the workout app, the order of work is:
- Open the warning on the Policy status page and confirm which requirement it names. Sometimes it's billing, not the target level.
- Raise the compile and target SDK to 36, then update Flutter, the Android Gradle plugin and every plugin to match.
- Move to Billing Library 8 and test a purchase, a renewal and a restore with test accounts.
- Check the build for 16 KB support and replace any plugin that fails it.
- Fix the insets, the back prompt and the tablet layout, testing on Android 15 and 16 and on a tablet-sized screen.
- Check the Data safety form against the SDKs now in the build.
- Upload, get through review, then watch the crash reports for a few days.
If you're seeing the same drop in installs, we handle this as a fixed-price fix for apps Google Play has hidden. For warnings that come as a rejection rather than a quiet drop, what a Google Play policy email means covers the other half.
When unpublishing is the better call
Google's own FAQ points owners who won't update towards unpublishing, and sometimes that's right. An app with a few dozen users, no revenue and nobody to maintain it isn't worth a two-level jump plus a billing migration. Our workout app has paying subscribers, so it gets the update.
Either way, look at Policy status in Play Console a few times a year. The warning shows up there long before installs fall.
Questions owners ask when the warning arrives
Will people who already installed my app lose it?
No. Google says users who installed it from Play before can still find it, reinstall it and use it on any Android version the app supports. Only new users on newer phones are shut out.
Our app is only used inside our company. Does the rule apply?
Google exempts permanently private apps, meaning apps restricted to users in one organization and meant for internal distribution only. A public listing that happens to have few users doesn't count.
What does it cost to have the update done?
It's a fixed-price Google Play update, $450 per app: the current target API level, the current Play Billing Library, 16 KB page size support, a Data safety check against your SDKs, and the release with one round of review replies. That price is for Flutter and native Kotlin or Java apps. React Native, Unity and other builds are quoted.