Google confirms that Android development will soon become fully private

Google will privately develop Android but keep it open source.

: Google announced plans to conduct Android development privately, marking a shift from its 16-year practice of public contribution. However, the company reassured that Android OS would remain open source, continuing to share its source code with external developers. This change aims to streamline processes and resolve delays between AOSP and Google's internal branches. Developers might face reduced public code releases, but end users should not notice any significant differences.

Google recently confirmed its decision to transition Android development to private internal branches starting next week. This shift will conclude nearly 16 years of a mixed development approach, where public contributions occurred via the Android Open Source Project (AOSP) Gerrit. While Google aims to streamline its development process, this new policy arises from the challenges of maintaining dual development tracks that comprise public AOSP code alongside private internal work. Historically, the lag in AOSP has led to delays and inconsistencies, affecting timely fixes and feature rollouts.

AOSP remains a fundamental part of Android as an open-source platform, accessible to everyone, and will continue accepting external contributions. However, Google's internal branch will be available only to companies with a Google Mobile Services (GMS) licensing agreement. Some prominent companies with such agreements include Samsung, Xiaomi, and OnePlus. GMS itself is not open source, but Google licenses it freely to manufacturers compliant with its conditions.

One notable change is that significant components of the Android stack, including the build system, update engine, Bluetooth stack, virtualization framework, and SELinux configuration, will transfer exclusively to Google's internal development channels. Consequently, the community will only see these changes when Google releases new Android versions incorporating them. This management strategy should alleviate existing sync and integration errors between the dual branches.

Despite the shift, end users are unlikely to experience any discernible differences in Android updates or functionality as core manufacturers with GMS licenses will continue receiving timely developments from Google's internal processes. However, developers might encounter more limited access to specific Android components, translating to fewer opportunities for public access and instant feedback.

In summary, while Google's decision to move Android's development privately underscores its intent to enhance efficiency and control, it reassures that openness remains a priority. By maintaining AOSP contributions and transparent updates, Google aims to balance innovation with the community-driven ethos defining Android. The tech world awaits to observe if this transition will maintain Android's vitality and flexibility once new policies are fully implemented.

Sources: TechSpot, Android Authority

MobileSoftwareSecurity