Every year, Google Play raises the bar on how current an Android app has to be. This year’s deadline was August 31. Apps that weren’t ready could request an extension, and that extension runs out on November 1.
If your company has an Android app that works fine and hasn’t been touched in a while, this is the kind of rule that can quietly cut off your growth. Nothing crashes, and no one gets an error. New users just stop finding the app.
What the Rule Actually Says
Every Android app declares a “target API level,” the version of Android it was built and tested against. Google Play sets a minimum each year. Per Google’s Play Console Help, starting August 31, 2026:
- New apps and app updates must target Android 16 (API level 36) to be submitted to Google Play.
- Existing apps must target at least Android 15 (API level 35) to stay available to new users on devices running newer versions of Android.
Developers who needed more time could request an extension to November 1, 2026. After that, the extension’s over.
There are a few exceptions. Wear OS, Android TV, Android Automotive, and Android XR apps have lower minimums, and permanently private apps distributed only inside an organization are exempt. For a typical customer-facing phone app, the rules above apply.
What Happens If You Do Nothing
This is where it gets easy to misread. Your app doesn’t get deleted. Existing users who already installed it can keep using it.
What changes is discovery. An app that targets Android 14 or lower stops being available to new users whose phones run a newer version of Android than the app targets. As people upgrade their phones, that group keeps growing. Your listing reaches fewer people every month, and the drop shows up as “installs are down” long before anyone connects it to a target API setting.
There’s a second, sneakier problem. Even if your app already targets Android 15 and is still visible, you can’t ship any update without targeting Android 16. The day you need an urgent fix, a security patch, or a price change, the target update becomes part of that release whether you planned for it or not.
Is It Just Changing a Number?
Sometimes. Often it isn’t.
The target level is one line in a build file, but raising it opts your app into every behavior change for that version of Android. For Android 16, a few changes stand out:
Edge-to-edge is mandatory. Apps are drawn behind the status bar and navigation bar, and the opt-out that let apps skip that is going away. Apps that never handled it can end up with buttons or headers hidden under system bars.
Large screens get less control from the app. On tablets, foldables, and other displays at least 600dp wide, Android 16 ignores an app’s orientation and resizability restrictions. An app that was locked to portrait can suddenly be stretched sideways on a tablet. There’s a temporary opt-out, but it won’t last.
Your dependencies need updates too. Raising the target usually means updating build tools and third-party libraries. If the app hasn’t been touched in two years, those updates can surface problems that have nothing to do with Android 16 itself.
None of this is unusual. It’s the normal cost of keeping a mobile app current. It’s just easier to absorb when it’s planned than when it lands in the same week as an urgent fix.
What to Do This Month
If you’re not sure where your app stands, start here:
- Check your current target API level. Whoever builds your app can answer in a minute. Play Console also flags apps that fall below the requirement.
- Check your Play Console notifications. Google sends extension request links and policy warnings there. If someone requested an extension, November 1 is your real deadline.
- Get the update scoped. Ask for an estimate that covers the target change, the behavior changes above, and dependency updates, plus testing on a phone and a tablet.
- Put it on a schedule. Even if you miss November 1, the goal is to stop losing new users as soon as possible, not to wait for the next deadline.
This Will Happen Again Next Year
Google raises the target API requirement every year, usually with an August deadline. Apple has its own version: App Store submissions have to be built with recent versions of Xcode and the iOS SDK. A mobile app is never “done.” It needs a small, predictable amount of work every year to stay in the stores.
If that line isn’t in your budget, it’s worth adding. We wrote about this kind of quiet, recurring cost in our 2027 budget post. Annual platform updates are one of the most common examples.
The Bottom Line
The November 1 deadline isn’t a cliff for your existing users, but it is a slow leak for new ones. The fix is usually a few days to a few weeks of work, depending on how long the app has gone without updates.
If you’re not sure where your app stands, or the person who built it isn’t around anymore, we can take a look. We’ll tell you what the update involves and what it’ll take to stay ahead of next year’s deadline, too.