Google Play's Android 16 (API 36) deadline: what app owners must do in 2026

From 31 August 2026 new Google Play apps and updates must target Android 16 (API 36). What it means for owners with many apps, extensions and a checklist.

Checked on 16 October 2026 against Google’s public documentation and secondary reports. Always read the current rules on developer.android.com before acting.

The rule in plain language

Google Play requires apps to target a recent Android version so they use current security and privacy behaviour. According to Google’s documentation:

From 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted.
Some device types have lower thresholds, for example Wear OS and Android TV.
Existing apps that do not meet the lower requirement may stay available to current users but may not be offered to new users on devices running newer Android versions.
Developers could ask for an extension to 1 November 2026.

If your extension date has passed, check your Play Console messages for the status of each app.

Why it matters if you manage many apps

An owner with 20 or 30 apps faces a pipeline problem: every app that needs an update must be rebuilt, tested and reviewed. If one app stays behind, you can lose the ability to update it, to fix a crash or to change a store listing.

Checklist for each app

List every app with its current targetSdk, version and last update date.
Prioritise apps with traffic and revenue.
Raise targetSdk to 36 and compile with the matching SDK.
Test the Android 16 behaviour changes: edge-to-edge layouts, back navigation, large-screen and orientation behaviour, background work and permission changes.
Fix ad and SDK versions. Old ad or analytics libraries can break the build. Update them.
Update the Data safety form if libraries or behaviour changed.
Roll out gradually and watch crash rates in Android vitals.
Keep a record so that the next target-level change is easier.

What if an app is abandoned?

Decide whether to update it or retire it. Keeping dozens of untouched apps on the store can harm trust and expose you to policy risk. Unpublishing is better than leaving a broken app.

Update deadlines are one part of keeping apps healthy. Another is how people find them: see ASO and organic growth for app owners. For new sideloading rules, read Android developer verification.

Frequently asked questions

What does targeting API 36 mean?

Your app declares that it was built and tested for Android 16 behaviour, through the targetSdkVersion setting in its build.

What is the deadline?

Per Google's documentation, from 31 August 2026 new apps and updates must target Android 16 (API level 36) or higher. Developers could request an extension to 1 November 2026.

Does my old app disappear from Google Play?

Google's documentation says existing apps that do not meet the lower requirement stay available to users on older Android versions but may not be offered to new users on newer devices. Read the official page for exact consequences.

Is changing the number enough?

Often it is a small change, but Android 16 behaviour changes, such as edge-to-edge display and large-screen rules, need real testing.