BestPaid guides · Android · Google Play

Google Play now requires target API 36, and 16 KB pages from February 1, 2027. Here is how to update an old Android app.

If your app was last updated in 2025 or earlier, chances are you can't publish anything on Google Play today, not even a one-line bug fix. And if it targets below Android 15, new users on newer devices can't find it.

Sources: Google Play's target API level requirements and Android's 16 KB page size guide. This page is our own summary; follow the official documentation for every detail.

What the rules say

1. Raise the target and the build tools

  1. Update Android Studio, the Gradle wrapper and the Android Gradle Plugin; AGP 8.5.1 or later also handles 16 KB packaging of native libraries.
  2. Set compileSdk and targetSdk to 36.
  3. Update AndroidX, Google Play services, Firebase and Play Billing libraries: old versions are often what blocks the build or the review.
  4. Flutter, React Native and Xamarin apps: move to a framework version that targets API 36 and ships 16 KB-aligned engine libraries, then rebuild. For Xamarin the move is to .NET MAUI.

2. Handle the behaviour changes that come with the new target

3. Make every native library 16 KB-ready

4. Ship it

  1. Build a signed App Bundle, upload it to internal testing and fix what the pre-launch report finds.
  2. Roll out in stages and watch Android vitals for new crashes.

On iOS the matching rule is that App Store builds must come from Xcode 26 with the iOS 26 SDK (since April 28, 2026), so an app that hasn't been rebuilt needs the same treatment there.

No one left who knows the app? We bring native, Flutter, React Native and Xamarin apps up to the current Google Play and App Store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer