Target API level: when an app quietly disappears

How does the rule work?

Play maintains a floor for the Android version an app targets and moves that floor up one release each year. An app below the floor is not removed from the store; it simply is not listed on devices running Android newer than its target. The app does not disappear — the reachable audience quietly narrows.

As of 31 August 2026 the target for new apps and updates is Android 16 — API level 36. There are exceptions by device class: Android 15 for Wear OS and Android Automotive apps, Android 14 for Android TV and XR apps.

Why does nobody notice?

Because nothing breaks. The app runs, existing users use it, updates flow, the store page is intact. The only change is that someone with a new device cannot find it in search — and that person does not tell you, they download something else.

So the symptom is commercial rather than technical: new installs fall, conversion degrades, campaign results stop making sense. If an app has not been updated for three years, the device pool it can reach today is a fraction of the one it launched into.

When should the upgrade be planned?

Ahead of the date, not against it. Raising the target is not only a configuration change; each Android release alters behaviour in permissions, background execution and storage access, and the app has to comply. Testing that compliance takes time.

The rhythm that works: start testing when the new Android version ships, raise the target a few months before the deadline, and get that build into the field. Then a regression leaves you time to fix it. Left to the final week, the fix and the deadline compress into the same calendar.