←back to thread

Transition to using 16 KB page sizes for Android apps and games

(android-developers.googleblog.com)
95 points ingve | 1 comments | 11 Jul 25 07:04 UTC | HN request time: 0s | source
Show context
AnonC ◴[15 Jul 25 04:13 UTC] No.44567762[source]▶
> Starting November 1st, 2025, all new apps and app updates that use native C/C++ code targeting Android 15+ devices submitted to Google Play must support 16 KB page sizes.

I realize that most apps wouldn’t need to make changes and that a recompilation would suffice, but is this time frame enough for the apps that do need code changes?

replies(2): >>44567986 #>>44569068 #
extraduder_ire ◴[15 Jul 25 05:07 UTC] No.44567986[source]▶
They've mentioned this requirement before, last hn post I see is from early may.

They only added support in android 15, in august 2024. https://android-developers.googleblog.com/2024/08/adding-16-...

I don't know what "targetting Android 15+" means specifically. Does that include anything with a lower API level?

replies(2): >>44568296 #>>44569215 #
1. izacus ◴[15 Jul 25 08:44 UTC] No.44569215[source]▶
Android apps have a flag in their manifest which tells the OS "this app was built with Android X (API level X) in mind".

This allows the OS to selectively enable backwards compatibility and change certain behaviors (e.g. selectively enforce new permissions so old apps aren't broken).

Play Store requires apps to target new OSes and port APIs within certain time of an OS launching (usually ~2 years).

This avoids apps targeting older OSes to avoid new security and privacy enhancements (e.g. asking for permisisons to show notifications, asking for permisisons to access microphone, being allowed to show a fullscreen popup ad, etc. Those restrictions were all gated behind the target check.)