Google Play's API 36 Deadline: What Small Business Android Apps Need to Do Before November 1, 2026

If your business has an Android app on Google Play, there's a compliance deadline you need to know about right now. Google has raised the minimum "target API level" every Android app must meet, and the grace period for late apps runs out on November 1, 2026. Miss it, and your app doesn't get rejected outright — it just quietly stops showing up for new customers on newer phones.

This isn't a rare, obscure policy update. It affects every app currently live on Google Play, whether you built it in-house, hired an agency, or had a freelancer ship it two years ago and haven't touched it since. Here's what's actually happening, who it affects, and what to do about it before the extension window closes.

What's Actually Changing

Every Android app declares a "target API level" in its build configuration — essentially a statement of which version of Android the app was built and tested against. Google requires that number to move forward periodically so apps keep up with current platform security, privacy, and permission standards instead of running against rules from years ago.

For the 2026 cycle, Google set two thresholds:

• New apps and app updates submitted after August 31, 2026 must target Android 16 (API level 36).
• Existing apps that aren't being updated still need to target at least Android 15 (API level 35) to stay fully visible on the Play Store.
• Google is allowing developers to request an extension until November 1, 2026 for apps that need a little more time to get compliant.

A few device categories have their own timelines — Wear OS and Android Automotive apps only need to hit API level 35, while Android TV and Android XR apps are held to API level 34. But if you're running a typical phone app for customers, employees, or field staff, the API 35/36 rules apply to you.

What Happens If You Miss the Deadline

This is the part that catches business owners off guard: nothing dramatic happens on day one. Your app doesn't get pulled from the store, and the people who already have it installed can keep using it without interruption.

What changes is discoverability. Once the deadline passes, an app that doesn't meet the minimum target API level becomes invisible in Play Store search and browsing for anyone using a newer Android device — specifically, devices running an Android version newer than what your app targets. New customers searching for your app, or arriving from a link, simply won't be able to find or install it on modern phones. Existing users are unaffected, but your ability to bring on new users from current-generation devices is effectively cut off until you update.

For a restaurant, service business, or retailer that depends on new customers discovering and downloading the app, this is a slow leak, not an explosion — and that's exactly why it's dangerous. Nobody notices a spike in errors or a wave of complaints. Download numbers just start drifting down, and it's easy to blame marketing before anyone checks the actual cause.

Who This Applies To

The requirement applies to any app distributed through Google Play, regardless of how it was built:

• Native Android apps built with Kotlin or Java
• Cross-platform apps built with React Native, Flutter, or similar frameworks
• Hybrid or WebView-based apps wrapped for the Play Store
• Apps built through no-code or low-code app builders, if the builder hasn't already handled the update on your behalf

It doesn't matter whether the app was last updated last month or three years ago. If it's live on Google Play and being distributed to new users, it's in scope. This is also worth checking even if you think your developer "handles all that" — if the relationship with whoever built the app has lapsed, no one may be actively watching for this.

What "Targeting a New API Level" Actually Requires

It's worth clearing up a common misconception here: targeting a newer API level is not the same as rebuilding your app or redesigning it. It's a configuration change in the app's build settings, paired with testing to confirm the app still behaves correctly under the newer platform rules.

In practice, that usually means:

• Updating the development environment (Android Studio, build tools, and the Android SDK) to a version that supports the new API level
• Changing the targetSdkVersion value in the app's build configuration
• Reviewing Android's behavior-change notes for the new version, since permission handling, background process limits, and notification behavior can shift between releases
• Re-testing core flows — login, checkout, notifications, camera or location permissions — on a device or emulator running the new Android version
• Checking that any third-party SDKs in the app (payment processors, analytics, ad networks, crash reporting) are compatible with the new target level, since outdated SDKs are the most common source of last-minute breakage
• Submitting the updated build through Google Play Console and confirming it passes the automated pre-launch checks

For a well-maintained app with reasonably current dependencies, this is often a matter of days, not weeks. For an app that hasn't been touched in a long time, outdated third-party libraries are usually the bottleneck, not the code you actually wrote.

A Straightforward Compliance Checklist

If you're not sure where your app stands, here's the order to work through this in:

1. Check your current target API level. This is visible in Play Console under your app's release details, or in the build configuration file if you have access to the source.
2. Confirm who has access to the source code and Play Console account. This sounds basic, but it's the single most common holdup — businesses that switched developers or agencies sometimes discover no one currently has login access or the original project files.
3. Update your build environment and target SDK version, then rebuild.
4. Test the update on a real device or emulator running the current Android version, focusing on permissions, notifications, and any payment or checkout flow.
5. Audit third-party SDKs for compatibility issues before you submit.
6. Submit the update through Play Console well before November 1, 2026 to leave room for review and any unexpected fixes.
7. If you can't make the date, use Play Console's extension request option rather than letting the deadline pass silently.

The businesses most at risk here aren't the ones actively building new features — they're the ones with a "finished" app from a couple of years ago that nobody has opened the project files on since launch.

If You Don't Have a Developer on Call Anymore

A surprising number of small business apps are orphaned in a very specific way: the app works, it's live, it made sense to build a few years ago, and the original developer or agency relationship has since ended. If that's your situation, you have a few practical paths:

• Reach out to the original developer or agency to see if a maintenance update is something they can still handle
• Bring in a developer or agency to do a one-time compliance update, even without an ongoing retainer
• Use this deadline as a natural checkpoint to evaluate whether the app still fits how your business operates today, rather than just patching it to survive another cycle

That last option is worth taking seriously. If your app was built years ago on an older framework, a compliance update is a reasonable moment to also ask whether the app still reflects your current menu, services, booking flow, or loyalty program — or whether it's due for a more substantial refresh.

The Bigger Picture

Google's target API level requirement isn't new, and it isn't going away — it updates on a roughly annual cycle, and this pattern will repeat again next year with a new API level and a new deadline. The businesses that handle this smoothly are usually the ones with someone — internal or outsourced — who treats "keep the app current" as an ongoing responsibility rather than a one-time project that ended at launch.

If your Android app hasn't been touched in a while and you're not sure where it stands on this deadline, it's worth finding out now rather than after new customers start quietly failing to find it in the Play Store.

Not sure whether your app is compliant, or need someone to handle the update for you? Get in touch with our team and we'll take a look.