Google Play in 2026: the Android 16 deadline and developer verification

Every year Google raises the minimum Android version that apps on Google Play must be built for — the “target API level”. It pushes apps to adopt newer security and privacy protections. This year’s step was the biggest date on the Android calendar:

Your app doesn’t disappear if it misses the date. What changes is that Play Console won’t accept your next update until it targets API 36 — which is usually discovered at the worst moment, when you need to ship an urgent fix.

Raising the target switches on the new platform’s behaviour for your app. For Android 16, that includes:

• Edge-to-edge screens. Apps can no longer opt out of drawing behind the status and navigation bars, so screens that relied on that can show content under the clock or the gesture bar.
• Large screens. On tablets and foldables, Android ignores an app’s request to stay in portrait or not be resized, so layouts must stretch properly.
• Back gesture animations. Apps that support the predictive back gesture get the system animations by default, which can expose odd navigation.

Apps built with React Native, Flutter or Expo usually need a framework update first, then a round of testing on an Android 16 phone and a tablet.

1. 01

   Check the warning in Play Console

   Policy status and the App bundle explorer show your current target and any deadline that applies to you.

2. 02

   Update the framework

   Move to a version of React Native, Flutter or Expo that supports API 36. This is the part that can take a few days on older apps.

3. 03

   Raise the target and test

   Test login, payments, notifications and every main screen on Android 16 — on a phone and on a tablet or foldable.

4. 04

   Release in stages

   Use a staged rollout to a small share of users first, and watch the crash reports before going to 100%.

Separately, Google now requires apps installed on certified Android phones to come from developers whose identity it has verified — including apps installed outside Google Play. It confirms who the developer is, not what the app does.

• Apps on Google Play: developers verify through Play Console. Check your account’s verification status there.
• Apps shared as APK files — a sales team app, a dealer app, a kiosk app — need the developer registered through the Android Developer Console.
• Timing: protections began rolling out on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand. Google says it expands globally in 2027, so India is in that wave.
• Sideloading still works: Google kept an advanced install flow for unregistered apps, but it adds warnings and waiting steps that ordinary staff and customers won’t follow.

If your business hands out an app outside Google Play, get the developer account verified in good time — ideally in the company’s name, not a freelancer’s personal account.