Google Play API 36 and Android 16: What WebView App Owners Must Do Before August 31

Apps that don't target API level 36 (Android 16) will be blocked from publishing updates on Google Play after August 31, 2026. If you run a WebView app for your business, this deadline applies to you — regardless of whether you built the app yourself or had someone else do it.

What Is Google Play API 36 and Why Does It Matter?

Every Android app targets a specific API level — a number that tells Android which version of the operating system your app is designed to run on. Google Play requires all apps to target a minimum API level, and it raises that bar each year.

For 2026, Google is requiring all apps to target API level 36, which corresponds to Android 16. Apps that haven't been updated to meet this requirement by August 31, 2026 will be blocked from submitting new updates on the Play Store.

This doesn't immediately remove your app from search results — existing installs continue working. But it does mean you won't be able to push any updates (bug fixes, new features, or compliance changes) until the target API level issue is resolved.

Who Is Affected by the August 31 Deadline?

The August 31 deadline applies to apps being updated or newly submitted:

Existing apps on Google Play that haven't been updated to target API 36 cannot submit new versions after this date.
New apps submitted for the first time after this date must target API 36 from the start.

If your app was published and has never been updated, it stays on the Play Store — but you lose the ability to update it. That's a bigger problem than it sounds. If a bug or policy issue surfaces, you have no path to fix it until the API level is resolved first.

WebView apps are fully subject to this rule. While WebView apps load web content rather than running native Android code, the app wrapper itself must still target the required API level. There are no exceptions for webview-based apps.

What Actually Changes When You Target Android 16?

For most WebView apps, targeting API 36 doesn't require changes to your website or web content at all. The changes happen at the Android wrapper level — the native shell that packages your website into an app.

Three areas to verify:

WebView rendering: Android 16 includes updates to the WebView engine. Most modern responsive websites render correctly without any adjustments. The main risk is apps loading legacy pages with outdated JavaScript APIs or old CSS properties that behave differently in the updated renderer.

Permission declarations: Android 13 and later introduced granular media permissions. Apps targeting API 36 must update how they declare storage or media access permissions in the Android manifest. This is a wrapper-level change, not a website change.

Splash screen handling: Android 12 enforced the SplashScreen API. Apps targeting API 36 must handle this correctly — otherwise the launch experience breaks on newer devices. Again, this is a wrapper fix, not a content change.

If you're using a managed app service like Webvify, these wrapper-level compliance updates are handled for you. You don't touch Gradle or Android Studio, and your app gets rebuilt to the new API target as part of ongoing app management.

How to Check if Your App Is Already Compliant

Open Google Play Console and navigate to your app. Under App content → Android vitals, you'll see the current target SDK version for your published build.

If it shows 36, you're already compliant. If it shows anything lower, you need to act before August 31.

You can also check directly on a phone: open the Play Store page for your app, scroll to "About this app," and look at the Android version requirement listed there.

A practical rule of thumb: if your app hasn't been updated since before late 2025, assume it needs a compliance rebuild. It's faster to confirm in Play Console than to guess.

For more background on how Google Play enforces API level requirements for webview-based apps, see our Google Play Android API Target Level guide.

What to Do If Your App Hasn't Been Updated Yet

Option 1: Update it yourself. If you built the app in Android Studio, update the targetSdkVersion in your build.gradle file to 36, rebuild the AAB (Android App Bundle), test on an Android 16 device or emulator, and submit the new version through Play Console. This is a straightforward change for someone comfortable with Android development.

Option 2: Contact your app provider. If you're using a WebView app service, reach out now. A compliance rebuild is a standard wrapper update — it doesn't require changes to your website. The question to ask: "Has my app been updated to target API 36 for the August 31 Google Play deadline?"

Option 3: If your app has no active support path. If the developer who built your app is unreachable, or you're using a tool that doesn't include ongoing compliance support, this deadline is a clear signal to re-evaluate. An app that can't be updated after August 31 is effectively frozen — you lose the ability to respond to any Play Store policy changes, fix crashes, or add features.

Services like Webvify handle Google Play API 36 compliance as part of managed app maintenance — you're not tracking annual deadlines yourself, and you're not waiting on a freelancer to respond. If you're also wondering about App Store compliance, our app store rejection prevention guide covers the equivalent requirements on the Apple side.

What Happens If You Miss the Deadline?

Missing August 31 doesn't immediately delete your app from the Play Store. Users who have it installed can still open and use it. But:

You cannot submit any new version to Google Play until the API level is resolved.
Google has previously removed non-compliant apps from search visibility in past API deadline cycles.
You lose any ability to respond to future policy changes, security issues, or crashes.

If you're already past the deadline, submit the compliance update immediately. Google's enforcement tends to prioritize completely inactive apps over those actively working to comply. Play Console will show you the exact blocking reason when you try to submit.

The window is short. If your app needs an update, this week is the time to act.

Frequently Asked Questions

Does the August 31 deadline apply to my WebView app if I haven't published any changes recently?

Yes. The deadline applies to any app attempting to submit a new version after August 31. Even if your app hasn't changed in years, you must target API 36 before Google Play will accept any future update from you.

Will my app stop working for existing users if I miss the August 31 deadline?

No. Apps already installed on user devices continue to work normally. The restriction is on submitting new versions to the Play Store — not on the app running on devices where it's already installed.

How long does it take to update a WebView app to target API 36?

For a WebView app, updating the target API level is a wrapper rebuild — no changes to your website are needed. A rebuild and submission typically takes 2–5 days once initiated. Google Play review for a compliance update usually completes within 1–3 days.

August 31 is close. If you're not sure whether your app is compliant — or you'd rather not track Google Play API deadlines yourself — Webvify handles compliance updates, wrapper rebuilds, and Play Store submissions end-to-end.