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.
What the rules say
- Since August 31, 2026, new apps and app updates must target Android 16 (API level 36). Extensions ran out on November 1, 2026.
- Existing apps must target Android 15 (API level 35) or higher to stay available to new users. Below that, the app stops being available to new users whose devices run a newer Android version.
- Apps targeting Android 15 and higher must support 16 KB memory pages on 64-bit devices. From February 1, 2027, updates without 16 KB support can't be released.
1. Raise the target and the build tools
- 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.
- Set
compileSdk and targetSdk to 36.
- Update AndroidX, Google Play services, Firebase and Play Billing libraries: old versions are often what blocks the build or the review.
- 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
- Edge-to-edge. Apps that target Android 15 draw under the status and navigation bars by default; toolbars and bottom buttons can slide under them. The temporary opt-out stops working once you target Android 16, so fix the insets properly.
- Back navigation. With target API 36, predictive back is on by default; code that relies on
onBackPressed() should move to the OnBackPressedCallback API.
- Read Android's behaviour-change pages for API 35 and 36 against your own screens and services.
3. Make every native library 16 KB-ready
- Only apps with native code (
.so files, often pulled in by SDKs) are affected; pure Java and Kotlin apps already work.
- Check the APK in Android Studio's APK Analyzer: the Alignment column flags libraries that aren't 16 KB-aligned.
- From the command line:
zipalign -c -P 16 -v 4 your-app.apk should end with "Verification successful".
- Rebuild your own native code with NDK r28 or later (16 KB-aligned by default) or add the 16 KB linker flags on older NDKs; replace prebuilt SDK libraries with 16 KB-compatible versions.
- Test on a 16 KB emulator image:
adb shell getconf PAGE_SIZE should print 16384.
4. Ship it
- Build a signed App Bundle, upload it to internal testing and fix what the pre-launch report finds.
- 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