Android 17 Adds New APIs Without Releasing to AOSP: First Since 3.x

Android 17 just became the first version since Android 3.x to add new APIs without releasing the source code to AOSP, a move that shakes the foundations of Android development as we know it.

Context: A decade of openness

Since Android 4.0 Ice Cream Sandwich, Google kept an implicit promise: every new Android version landed in AOSP (Android Open Source Project) with its source code. This allowed manufacturers like Samsung, Xiaomi, and OnePlus, plus communities like LineageOS, to build custom ROMs based on the latest APIs. The exception was Android 3.x Honeycomb, a tablet version that never saw the light in AOSP due to quality and fragmentation issues. Now, with Android 17, that exception repeats, but for very different reasons.

Details: New APIs, closed code

According to comments on Hacker News, Android 17 includes a set of new APIs that are not available in the public AOSP repository. These APIs, reportedly related to artificial intelligence and power management, are only distributed through Google Play Services and factory images for Pixel devices. Google has not issued an official statement, but developers who inspected the SDK confirm that key classes and methods are missing. The expected release date for Android 17 is late 2025, and voices are already warning about a possible gradual closure of the ecosystem.

Analysis: Strategy or oversight?

My take is that Google is using Android 17 to test a more closed model, similar to iOS, where critical APIs are reserved for its own services. This benefits Google (more control, better integration with Gemini) but hurts manufacturers that rely on AOSP to differentiate and developers of alternative ROMs. If consolidated, fragmentation could increase: Pixel users will get exclusive features while others wait months. It's not a mistake, it's a calculated move.

Implications: The future of open source in Android

In the short term, we'll see more exclusive APIs in Google Play Services and fewer contributions to AOSP. Manufacturers like Samsung may accelerate their own developments (One UI) to avoid depending on Google's cycle. In the long run, this could revitalize projects like /e/OS or GrapheneOS, which already promise total independence. The big question is whether Google will let AOSP remain relevant or turn it into a mere showcase.

If Android 17 marks the end of the golden era of open source, the coming years will define whether the ecosystem unifies under Google or diversifies into alternatives. Which do you prefer: a more controlled Android or a freer one?

Source: Hacker News