Google Takes Full Control: All Android Developments Move In-House

Google has decided to handle all Android operating system developments internally, aiming to simplify and speed up the process. This shift implies that Android's primary branch for development will no longer be AOSP, which has been the platform of choice for over 16 years.

Currently, Android has two places where it’s developed — AOSP, which is open to anyone using, modifying, and sharing; and Google’s private internal branch that partners using Google Mobile Services (GMS) can access. However, this dual system often has gaps. Since Google’s internal version tends to have features ahead of AOSP, it is difficult to keep the two versions in sync.

Technical challenges like conflicts when merging updates have occurred due to managing two branches. An example of that is syncing screen magnifier settings and storage access that were necessary for changes across both versions. In the hope of avoiding such problems and simplifying the workflow, Google is shifting its work over to a single internal branch.

Google does indeed say it is committed to keeping Android open source. It will keep publishing its source code for new Android versions, including its Linux kernel — the whole thing must be in the public domain under open source rules.

Now that the Android AOSP build system, Bluetooth stack, and security settings are a thing of the past, it isn’t always in the cards to patch these frequently updated parts of the OS. Instead, attention will be paid to core system improvements that are already taking place in Google’s own branch.

Google said the change will streamline Android development by enabling phone makers and developers to work with one fixed version instead of chasing constant revisions.

Android 16’s source code is planned to be released in 2025, with more details expected soon.