What does this update require?

Starting November 1, 2025, all new apps and updates targeting Android 15 or higher must support 16 KB page sizes in order to be published on Google Play.

Existing apps that do not comply may have their updates or new versions blocked from release on the store.

Why is Google enforcing this change?

This is not an arbitrary update — it’s based on performance improvements and the evolution of mobile hardware. Some of the benefits highlighted by Google include:

• Faster app launch times (average improvements of around 3%, in some cases up to 30%).

• Lower battery consumption during app startup.

• Faster camera initialization and more optimized system startup.

• Future readiness for devices with more RAM and modern architectures, where the traditional 4 KB page size is becoming a limitation.

In short, Google wants apps to be ready for the next generation of Android hardware and take full advantage of memory, mapping, and processing efficiencies.

What is the timeline and what does it mean for your company?

Although the initial deadline announced was November 1, 2025 for new apps and updates targeting Android 15+, some communications indicate that certain apps may receive extensions or phased rollout periods.

The key takeaway: don’t postpone it. The longer you delay, the higher the risk of updates being rejected or of encountering errors or incompatibilities on devices that use 16 KB page sizes.

For software companies, now is the time to review all mobile projects, especially those that use native code, plugins, external libraries, or integrate specialized SDKs.

What are we doing at Avance Software?

At Avance Software, we are proactively preparing for this change and guiding our clients through the transition. Specifically, we:

• Perform a technical audit of each app to identify whether it uses native libraries or dependencies that require rebuilding.

• Update and configure build tools (AGP, NDK, Gradle) to ensure they are aligned with 16 KB requirements.

• Review and refactor code (and third-party libraries) to remove assumptions about fixed 4 KB page sizes.

• Run compatibility tests in 16 KB environments (emulators and physical devices) before publishing.

• Manage production builds in Google Play to ensure smooth publication without blocking issues.

• Inform and update our clients on the migration progress, incorporating this work into their maintenance or app-upgrade plans.

In short, we take care of making the transition as smooth as possible — ensuring your applications are ready for the future of Android, with no surprises.