Google's Android 16 Deadline Passed: Is Your Store App Now Invisible?
Google quietly closed its extended grace period for targeting Android 16 on 1 November 2026. If your store's Android app hasn't been updated since the summer, it may already be dropping out of search and discovery for anyone on a newer phone.

TL;DR: Google required all Google Play apps to target Android 16 (API level 36) by 31 August 2026, with a one-time extension pushing the real cutoff to 1 November 2026. That extension has now passed. Apps still targeting an older API level don't get pulled from the store, but they quietly stop showing up in search and browse for anyone running a newer Android version, which for a shopping app means fewer new customers finding it. If your store has an Android app and nobody's touched its build settings since summer, this is worth a five-minute check before you lose another week of visibility. For stores without an in-house developer, this is exactly the kind of maintenance an Android development team handles as routine upkeep rather than a once-a-year scramble.
What Actually Happened on 1 November
Google's target API level policy isn't new; it requires every app on Google Play to be built against a recent version of Android, refreshed roughly once a year. For 2026, the rule was that new apps and updates had to target Android 16 (API level 36) starting 31 August. Developers who weren't ready could request a one-time extension through Play Console, pushing their personal deadline to 1 November 2026. That extension window has now closed, and Google isn't granting a second one for this cycle.
Why "Not Removed" Doesn't Mean "Fine"
The penalty here is easy to misread as nothing, because Google doesn't pull a non-compliant app off the store. What it does instead is narrower and easier to miss: the app stops being shown to new users whose phones are running an Android version newer than whatever API level the app still targets. Existing customers who already installed it keep using it as normal. New customers browsing or searching Google Play on a current-generation phone simply won't see it in results. For a store that depends on people discovering the app organically, rather than everyone already having it installed, that's a slow leak in new customers that doesn't show up as an error anywhere, it just shows up later as fewer downloads.
Who This Actually Affects
If your Android app was built or last updated by a developer within the past year, it's very likely already compliant and there's nothing to do. The apps at risk are the ones nobody has touched in a while: a store app built 18 months ago and left alone because "it still works," or an app inherited from a freelancer who's no longer involved. Neither of those is rare for a small, home-run store, and neither one throws up a warning you'd notice while using the app yourself.
How to Check in Five Minutes
- If you have Play Console access: open your app, go to Release > Setup > App integrity (or the "Policy status" panel), and look for any compliance warning about target API level.
- If a developer manages it for you: ask them directly whether the app's current build targets API level 36, and if not, when the update is scheduled. A reputable developer will have this on their radar already.
- If you're not sure who manages it anymore: check the app's Play Store listing page for its "Updated on" date. If it's been more than 12 months, that's reason enough to get someone to look at it this week.
What to Do If Your App Is Behind
The fix itself, updating the target API level, is routine developer work, not a rewrite. It's usually three steps:
- Rebuild the app against the new target API.
- Test it and resolve anything Android 16 changed.
- Ship the update through Play Console.
The harder part for a solo store owner is usually just knowing it needs doing at all, since nothing inside the app itself flags the problem. This is the kind of unglamorous maintenance that's easy to let slide when you're also doing inventory, customer service, and marketing yourself, which is exactly why stores that keep an app long-term tend to put it on a standing schedule with whoever built it, rather than waiting for a deadline headline to notice.
FAQ
Will my app disappear from the Play Store if I miss this?
No, it stays listed and existing users can keep using it. It stops appearing in search and browse results for new users on devices running a newer Android version than the app targets.
How do I know what API level my app currently targets?
Check Play Console's Policy status page under your app, or ask whoever built or maintains the app. There's no way to see this from inside the app itself as a user.
Is there another extension coming?
Google granted one extension to 1 November 2026 for this cycle. There's no public indication of a further extension, and the policy repeats on roughly an annual basis with the next Android version.
Does this affect my store's website or only the Android app?
Only the Android app on Google Play. Your website, iOS app, and any other sales channels aren't affected by this particular policy.
My app was updated recently. Do I still need to check?
If it was built or updated within the last few months, it's almost certainly already compliant, but a quick look at Play Console's Policy status page takes a minute and removes the guesswork.
If this is the first you're hearing that your app needs standing maintenance, not just a launch, that's a normal gap for a one-person store to have, and it's exactly the kind of thing we build into the plan when we set an app up properly from the start.


