VVidra Labs ◐

"Your app doesn't meet Google Play's target API level requirements" — what it actually means, and your honest options

Updated June 2026 · every claim links to Google's own documentation

If Google emailed you that warning, or you found it on the Policy status page of your Play Console: your app isn't about to be deleted, and you're not in trouble. But something real is happening to it, on a schedule, and ignoring it quietly costs you installs and customers. Here's the whole picture.

The rule, in one paragraph

Every Android app declares which Android version it "targets" (its targetSdkVersion). Google requires apps on the Play Store to keep that target reasonably current, and raises the bar every year, around August 31. The current requirements (in force since August 31, 2025): new apps and app updates must target Android 15 (API level 35) or higher, and existing apps must target at least Android 14 (API level 34) to remain available to new users on current devices. The authoritative, always-current version is on Google's policy page — don't take our word for it.

What actually happens if you do nothing

• Your app disappears for new users. In Google's own words, apps below the bar "will only be available on devices running Android OS that are the same or lower than your apps' target API level." A potential customer with a recent phone searches for your app — it simply isn't there. Existing users keep it; growth stops.
• You can't ship updates. Any update must meet the current target — so the longer you wait, the bigger the jump (and the work) becomes.
• It compounds annually. Every August the bar rises again, and your app falls one more year behind. Apps three or four years behind often need permission-model changes, library upgrades and build-system surgery — not a one-line fix anymore.

Check where your app stands (2 minutes, no tools)

1. Open your app's Google Play page → About this app → App info → Updated on. If the last update is older than ~18 months, you're at or past the visibility cliff.
2. Search for your app from a recent Android phone that never had it installed. Not there? That's the problem, live.
3. In Play Console: Policy → Policy status shows the exact finding and deadline for your app.

Your options, honestly

Option 1 — do it in-house. If you have an active Android developer: bump targetSdkVersion, walk through the behavior changes for each Android version you're jumping across (permissions, background limits, exported components…), upgrade the libraries that demand it, test on a current device, ship. For a well-maintained app this is days; for an app untouched since 2021-22, it's usually a small project.

Option 2 — file the extension (Play Console → Policy status) and buy yourself until November. Real option, often sensible — as long as the work actually gets scheduled.

Option 3 — have it done fixed-price. This is what we do, all day:

FAQ

Will Google delete my app? No — this policy hides it from new users and blocks updates. (Separate policies can remove long-abandoned apps, but the target-API rule itself doesn't delete anything.)

Do my existing users lose the app? No. Installed apps keep working and stay in those users' libraries.

We lost the source code — now what? Then no one can update the app, including us, until it's rebuilt. Anyone who claims otherwise is guessing. We'll tell you honestly what a rebuild involves if you ask.

More free checks: is your Google Analytics collecting anything? · can your email be spoofed? · all Vidra Labs services