Google Play's Android 16 requirement: what app owners need to do
New apps and updates on Google Play must now target Android 16 (API level 36). What that means, the extension window, and what usually breaks.
Every year Google raises the minimum Android version that apps on Play must be built for. For 2026 the rule is: from 31 August 2026, new apps and app updates must target Android 16 (API level 36). Google allows developers to request an extension to 1 November 2026 through Play Console.
Existing apps that don't move aren't deleted — but they must target at least Android 15 (API 35) to stay visible to new users on newer Android versions, and you can't publish an update (including a bug fix) until the target is raised.
Why this is more than changing one number
Raising the target opts your app into every behaviour change Android made for that version at once. Typical things that need work:
- Layouts that assumed the old status and navigation bars (edge-to-edge display is enforced).
- Background work, notifications and foreground-service rules.
- Permissions and media access changes.
- Third-party SDKs that haven't been updated — often the real blocker.
A sensible plan
- Upgrade build tools and SDKs on a branch; list what fails.
- Test on real devices across Android versions, not just the emulator.
- Release to an internal or closed testing track first.
- Book this as a yearly maintenance task — the requirement moves every year.
Apps built with React Native or Flutter need the framework upgraded too, which is usually the bigger part of the job.
Sources
Planning something like this?
Tell us what you're building. A product lead replies within one business day with questions and a first take.
Get a free consultationThe product planning checklist
42 questions to answer before you hire a team or write a line of code.
Get the checklistGet the next article by email
One practical email a month. No spam, unsubscribe any time.
