Google is gearing up for a significant transformation in the way it develops new versions of the Android operating system. Historically, much of the software development has occurred in public-facing channels, allowing developers and users to engage with the platform transparently. However, this trend is set to change as Google moves to a more private development model.
This transition does not imply that Android is abandoning its open source roots. Instead, the development process will be less transparent moving forward. Google has confirmed to Android Authority that all future Android development will be conducted in its internal branch. This marks a departure from the previous approach, which allowed frequent updates to the public AOSP (Android Open Source Project) branch.
While AOSP remains accessible to anyone interested, the internal branches will be restricted to Google and select companies holding a Google Mobile Services (GMS) license, such as Samsung and Motorola. The primary reason for this shift, according to Google, is to simplify the development process. Recent changes to trunk-based development have contributed to this decision, as maintaining synchronization between public and private branches has proven cumbersome.
By concentrating on the internal branch, Google aims to streamline its release process and alleviate some of the burdens associated with merging branches for each new release. Once new versions of Android are finalized, Google will continue to publish the source code in AOSP, ensuring that developers can still support their applications without needing to track changes in the platform.
This focus on internal development allows licensed OEMs to dedicate their efforts to the vibrant internal branch, which is crucial for devices that may take a year or longer to launch.
This move towards private development isn't entirely unexpected. Over the years, Android has become less open, with Google gradually transitioning features from AOSP into closed-source packages. This shift provides Google with enhanced control over the platform while facilitating updates to core components without necessitating a complete OS overhaul.
Currently, while much of the development occurs within the internal branch, certain components—such as Bluetooth and the kernel—are still developed openly. Under the new system, these elements will also migrate to the internal branch.
While this change is likely to simplify processes for Google's development team, it may limit the amount of information available about Android prior to the official release of new versions. In the past, insights gleaned from AOSP have hinted at upcoming devices, potential feature removals, or changes in app support. The reduction in transparency may hinder developers' and users' ability to engage with Google regarding any unpopular changes before they are implemented.
Nevertheless, the average Android phone user may remain largely unaware of this structural transformation. Google is expected to share more details about the shift to private development later this week, with the change potentially going into effect as soon as next week.
