Google Play's 31 August deadline: the quiet way an app disappears

A mobile app can pass every test on your own phone and still be quietly going dark for the people you most want to reach: new customers. Nothing crashes. The app just stops showing up for anyone on a recent device, and you lose the ability to update it.

Google Play and the App Store both enforce a floor that moves every year. Apps that fall below it are not pulled down with a bang. They fade. Here is the rule, the difference between new and existing apps, and what to check before the deadline checks it for you.

The rule, and who it hits first

Google Play sets a target API level that apps are measured against, and raises it on a yearly cycle. The distinction that matters most is between an app you are touching and one you are leaving alone.

New apps and any update are held to the current bar. To publish a new app, or to push any update to an app you already have on the store, you must target the latest required level. At the 31 August 2025 deadline that level was Android 15 (API level 35). The moment you want to ship a change, you are measured against today's bar, not the one your app was built to.

Existing apps you do not touch get more runway. An app already published stays available to the people who have it, and Google treats it as compliant as long as it targets Android 14 (API level 34) or higher. That is one level back from the new bar, which buys time, but it is still a floor, and it rises too.

On that yearly cadence, the next deadline is expected on 31 August 2026. Google confirms the exact date and level closer to the time, and the direction only goes one way. Teams that need longer can request an extension, as the 2025 cycle allowed through to 1 November.

The failure is quiet

This is the part that catches people. Nothing breaks on the phones you test on, and existing users carry on as normal. But a new user on a newer Android phone is shown a message that the app is not available to install on their device because it was made for an older version of Android. Your installs from new devices quietly drop, and the dashboard that would explain why is the one nobody is watching.

The second cost is worse. Because every update is held to the current bar, an app you cannot rebuild to that level is an app you cannot patch. Not a feature, not a price change, not a security fix. It freezes at exactly the moment it most needs to move.

Apple runs the same play, on its own clock

Apple's version is a build requirement rather than a store-visibility one, and the dates differ. Since 28 April 2026, any app uploaded to App Store Connect must be built with Xcode 26 and an iOS 26 SDK. Miss it and you cannot upload at all. Same shape: the floor moves every year, and the apps that drift below it lose the ability to ship.

What to check

Three questions answer most of it.

• What API level does your Android app target today, and what iOS SDK was your last build made with? Both sit in the build configuration, and the Play Console and App Store Connect both show them.
• Is either store already flagging the app, or about to? A warning in the Play Console is the polite version of the deadline.
• If there is a gap, how big is the rebuild? An app kept roughly current is a small job. An app two or three years behind, or sitting on an end-of-life framework like Xamarin, is a project.

What to do

Roll forward on a schedule, before the deadline forces it. For a healthy app that means rebuilding to the current target, testing the behaviour changes each new API level brings, and shipping. For a neglected one it means a stabilisation pass first, to get back to a baseline you can build on.

This is the unglamorous, non-negotiable work that keeps an app alive, and it is exactly what App Care exists to do. We run the mobile apps you have already paid to build, so they stay secure, stay current, and never quietly fall out of the App Store or Google Play. Brisbane-based.

Sources

1. Google, "Meet Google Play's target API level requirement", Android Developers. New apps and app updates must target Android 15 (API level 35) or higher from 31 August 2025; existing apps targeting Android 14 (API level 34) or higher are compliant; non-compliant apps stop being available to new users on devices running a newer Android version than the app targets. https://developer.android.com/google/play/requirements/target-sdk
2. Google, "Target API level requirements for Google Play apps", Play Console Help. The same requirement, the new-versus-update-versus- existing distinction, and the extension to 1 November 2025. https://support.google.com/googleplay/android-developer/answer/11926878
3. Apple, "SDK minimum requirements", Upcoming Requirements, Apple Developer. Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26 or later. https://developer.apple.com/news/upcoming-requirements/