Android 17: First since 3.x to add APIs outside AOSP
Original: Android 17 is the first since 3.x to add new APIs without releasing to the AOSP
Why This Matters
AOSP openness underpins OEM customization, security research, and Android forks like GrapheneOS.
GrapheneOS flagged that Android 17 QPR1 is the first Android release since the 3.x era to introduce new APIs without a corresponding public AOSP release, raising transparency concerns about Google's development process.
GrapheneOS posted on Mastodon that Android 17 QPR1 marks a significant departure from Google's long-standing practice: it is the first Android release since the 3.x era (over a decade ago) to add new APIs without publishing the corresponding source code to the Android Open Source Project (AOSP). This breaks the expectation — held by OEMs, developers, and privacy-focused projects alike — that Android's public API surface is backed by openly available source code. GrapheneOS, which builds a hardened Android fork, flagged this as a notable regression in Google's transparency around Android development. The post does not specify which APIs were added or why they were withheld from AOSP, but the comparison to Android 3.x (Honeycomb), which was briefly kept closed due to tablet-focused features Google wasn't ready to open-source, is pointed. That episode was widely criticized at the time and Google subsequently committed to keeping Android open. Whether this represents a temporary delay or a deliberate shift in policy is not yet clear.