twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Google Play blocks app updates without 16 KB page support on February 1, 2027. Inventory your native SDKs now

From February 1, 2027, Play will refuse updates for apps that target Android 15 or higher and still lack 16 KB page-size support on 64-bit devices. Pure Kotlin apps are fine. Native libraries and old SDKs are the trap.

Editorial engraving of a sunny mobile lab where an SDK engineer reviews a native-library inventory on a laptop while a tech lead circles a week on a blank wall calendar.

Google Play requires apps targeting Android 15 (API 35) and higher to support 16 KB memory page sizes on 64-bit devices. Starting February 1, 2027, updates that do not support 16 KB cannot ship. Inventory every native .so in your APK and every third-party SDK that ships one, rebuild with a current NDK or AGP, and test on a 16 KB emulator before the gate. Java/Kotlin-only apps already comply, but most production apps pull at least one native dependency through analytics, payments, maps or a game engine.

The gate on the calendar

Google's Android Developers documentation, updated November 4, 2026, is blunt. Apps that target Android 15 (API level 35) and higher must support 16 KB memory page sizes on 64-bit devices on Google Play. Starting February 1, 2027, if your app updates do not support 16 KB page sizes, you will not be able to release those updates.

This is not a soft warning in a blog post. It is a store gate. Devices with more RAM are moving to 16 KB pages; Android 15 already supports them. Apps with native code that still assume 4 KB pages will not run correctly on those devices, and Play will stop taking your updates until you rebuild.

If your app is pure Java or Kotlin with no native libraries, you already support 16 KB. Most shipping apps are not that clean. Analytics kits, payment SDKs, maps, camera pipelines, React Native / Flutter engines and game engines all ship .so files. The February gate fails the dependency you forgot, not the Activity you wrote.

Decision guide

Who is actually affected

ConsiderationApp shapeFebruary 1, 2027
Pure Kotlin/JavaAlready supports 16 KB.Still test on a 16 KB image
App + native SDKsMust rebuild or replace.Inventory every .so
Game / RN / FlutterEngine + plugins matter.Confirm engine version notes
Builder / white-labelArtifact may hide natives.Get a written vendor statement
Decision framework from Android Developers 16 KB guidance, updated November 4, 2026.

Build the SDK inventory before you touch Gradle

Spend a morning on evidence, not optimism.

1. Analyze a release APK. In Android Studio, use Analyze APK and open the lib folder. Every .so is native code. Note the ABI folders and which libraries show alignment warnings.

2. Map each .so to a dependency. Match file names to Gradle coordinates or vendor SDKs. Anything you cannot name is a priority—orphans are what break release week.

3. Check vendors for a 16 KB-ready version. Payment, identity, crash reporting and mediation partners publish notes at different speeds. Put "16 KB supported as of version X" in a sheet with a link. If a vendor has no answer, start the replacement conversation now, not in January.

4. Note your AGP and NDK. Android's guidance: AGP 8.5.1 or higher with uncompressed shared libraries, and NDK r28 or higher which aligns to 16 KB by default. Older NDKs need linker flags for max-page-size and common-page-size at 16384.

5. Hunt hard-coded 4096. Search for PAGE_SIZE, 4096, and custom allocators that assume 4 KB pages. Runtime crashes on 16 KB devices often come from those assumptions even after ELF alignment looks fine.

Write the inventory as a one-page table: library, owner, version, 16 KB status, action. That table is what you bring to sprint planning. It is also what you show leadership when someone asks why a "simple Play update" needs three sprints.

The February gate fails the dependency you forgot, not the Activity you wrote.

Rebuild, then prove it on a 16 KB image

Alignment on disk is necessary and not sufficient. After you bump AGP/NDK and swap SDKs:

  • Rebuild release and re-run APK Analyzer until arm64-v8a libraries show clean alignment.
  • Use zipalign / bundletool checks so Play's packaging does not undo your work.
  • Boot an Android 15+ emulator image configured for 16 KB pages (Google publishes experimental 16 KB system images). Confirm adb shell getconf PAGE_SIZE returns 16384.
  • Smoke the paths that touch native code: login, pay, map, camera, push, any on-device ML.

Pixel devices with developer options can boot in 16 KB mode on certain builds; use that for a final pass if you have hardware. Emulator evidence is enough to start; hardware evidence is what you want before the freeze.

Backcompat modes exist and will tempt someone to ship "for now." Treat them as diagnostic, not a release strategy. Play's February rule is about what you upload, not about whether a device can limp along.

How this collides with the rest of the mobile calendar

February 1, 2027 sits near other mobile deadlines teams already track—SDK version floors, privacy label refreshes, store questionnaire changes. Fold 16 KB into the same pre-mortem you use for Apple's SDK deadlines. If your last native dependency will not be ready until late January, you do not have a mobile plan; you have a hope.

Also check white-label and "we use a builder" apps. Third-party app builders that embed native libraries can leave you compliant in source and broken in the artifact you upload. Demand a 16 KB statement from the builder in writing.

Related reading inside the journal: keep the same ownership discipline you use when someone holds the Android signing key—named owner, named artifact, no folklore.

A twelve-week shape that usually works

Weeks 1–2: Inventory and vendor tickets.
Weeks 3–6: AGP/NDK bump on a branch; replace or upgrade blockers; fix PAGE_SIZE assumptions.
Weeks 7–9: 16 KB emulator QA on payment and media paths; fix crashes.
Weeks 10–11: Staged rollout to internal and percentage production.
Week 12 buffer: Vendor slip and holiday freezes.

If you are already inside that window, compress honestly. Cut feature work that touches native layers. Do not schedule a major SDK upgrade the same week as the 16 KB cut unless one upgrade delivers both.

Sequence of work

Twelve-week shape

  1. Weeks 1–2

    APK inventory + vendor tickets.

  2. Weeks 3–6

    AGP/NDK bump; replace blockers.

  3. Weeks 7–9

    16 KB emulator QA on native paths.

  4. Weeks 10–12

    Staged rollout + buffer for slips.

Illustrative decision framework; compress if vendors are already ready.

If you own the Android app

Open the APK this week. Name every .so. File vendor tickets with the February 1, 2027 date in the subject line. Put the inventory in the same place you keep store listing credentials. When the rebuild needs product time, our mobile applications team can run the inventory, the AGP migration and the 16 KB test plan with your engineers. Get in touch and send the APK Analyzer screenshot.

One more practical note. Put the February 1, 2027 date on the shared mobile calendar next to your usual Play policy reminders, and assign a single owner who can say "we are green" or "we are blocked on vendor X." Committees do not ship APKs. If that owner needs outside help to finish the inventory, the rebuild and the 16 KB test matrix, bring them into the first conversation with our mobile applications team rather than waiting for a red Play Console banner in late January. Waiting turns a scheduled migration into an emergency change freeze you did not plan to have.

Take the extra hour this week to write the decision down where the next person will find it—not in a chat thread that scrolls away. Named owners, named dates and a short "what good looks like" line prevent the same argument from restarting every Monday.

If a vendor demo skips the failure path, ask them to show it before you renew. Happy-path screenshots are easy. The recover path is what your team will live inside when something ships wrong at 5 p.m. on a Friday.

Related work: Sutton Place.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎