https://arstechnica.com/gadgets/2025/03/google-makes-android-development-private-will-continue-open-source-releases/ Skip to content Ars Technica home Sections Forum Subscribe * AI * Biz & IT * Cars * Culture * Gaming * Health * Policy * Science * Security * Space * Tech * Feature * Reviews * Store * AI * Biz & IT * Cars * Culture * Gaming * Health * Policy * Science * Security * Space * Tech Forum Subscribe Story text Size [Standard] Width * [Standard] Links [Standard] * Subscribers only Learn more Pin to story Theme * HyperLight * Day & Night * Dark * System Search dialog... Sign In Sign in dialog... Sign in A private affair Google makes Android development private, will continue open source releases Google says this change will simplify things for developers and OEMs. Ryan Whitwam - Mar 26, 2025 3:20 pm | 39 Android 15 on Pixel screen Android 15 on Pixel screen Credit: Ryan Whitwam Credit: Ryan Whitwam Text settings Story text Size [Standard] Width * [Standard] Links [Standard] * Subscribers only Learn more Minimize to nav Google is planning a major change to the way it develops new versions of the Android operating system. Since the beginning, large swaths of the software have been developed in public-facing channels, but that will no longer be the case. This does not mean Android is shedding its open source roots, but the process won't be as transparent. Google has confirmed to Android Authority that all Android development work going forward will take place in Google's internal branch. This is a shift from the way Google has worked on Android in the past, which featured frequent updates to the public AOSP branch. Anyone can access AOSP, but the internal branches are only available to Google and companies with a Google Mobile Services (GMS) license, like Samsung, Motorola, and others. According to the company, it is making this change to simplify things, building on a recent change to trunk-based development. As Google works on both public and private branches of Android, the two fall out of sync with respect to features and API support. This forces Google to tediously merge the branches for every release. By focusing on the internal branch, Google claims it can streamline releases and make life easier for everyone. When new versions of Android are done, Google says it will continue to publish the source code in AOSP as always. Supposedly, this will allow developers to focus on supporting their apps without keeping track of pending changes to the platform in AOSP. Licensed OEMs, meanwhile, can just focus on the lively internal branch as they work on devices that can take a year or more to launch. This change to private development doesn't come out of the blue--Android feels less open today than it did in the early days. For example, Google has been moving Android features from AOSP into closed source packages for years. This gives Google greater control over the platform while also making it easier to update core components without a full OS update. Currently, most Android development takes place in the internal branch, but a handful of components, like Bluetooth and the kernel, are developed in the open. They'll be moving to internal under the new system. This change will undoubtedly make development easier for Google's team, but it could limit how much we know about Android before new versions are official. Sometimes, the tidbits that appear in AOSP can point to upcoming devices, feature removals, or changes to app support. We may not get those insights anymore, and consequently, there won't be as many opportunities for devs and users to challenge Google before it rolls out an unpopular change. Even if there are some negative consequences, the average Android phone user probably won't know anything about the structural change. Google will reportedly have more details on the shift to private development later this week, and the change could go into effect as soon as next week. Photo of Ryan Whitwam Ryan Whitwam Senior Technology Reporter Ryan Whitwam Senior Technology Reporter Ryan Whitwam is a senior technology reporter at Ars Technica, covering the ways Google, AI, and mobile technology continue to change the world. Over his 20-year career, he's written for Android Police, ExtremeTech, Wirecutter, NY Times, and more. He has reviewed more phones than most people will ever own. You can follow him on Bluesky, where you will see photos of his dozens of mechanical keyboards. 39 Comments Staff Picks m mad77again I guess this may create some problems for developers of open source Android images, like LineageOS: having to deal with a huge set of changes in a single moment is worse than having to deal with (or at least know about) them as they are introduced. On the other end, to be honest, this won't probably change much for people that are developing systems based on Android for a living (as I had the pleasure to): unfortunately in this industry you already are at the wrong end of the food chain, well after the SoC, ODM and OEM repositories. And most of them are not famous for their timely updates. Yes, you could always peek at the AOSP sources, but a lot of the important stuff is often quite difficult to integrate into a codebase that was touched by so many actors. March 26, 2025 at 8:03 pm Comments Forum view Loading Loading comments... Prev story Next story Most Read 1. Listing image for first story in Most Read: Firm wins Space Force funding to provide an "aircraft carrier" in orbit 1. Firm wins Space Force funding to provide an "aircraft carrier" in orbit 2. 2. Open Source devs say AI crawlers dominate traffic, forcing blocks on entire countries 3. 3. As preps continue, it's looking more likely that NASA will fly the Artemis II mission 4. 4. After DDOS attacks, Blizzard rolls back Hardcore WoW deaths for the first time 5. 5. RFK Jr. claws back $11.4B in CDC funding amid wave of top-level departures Customize Ars Technica has been separating the signal from the noise for over 25 years. With our unique combination of technical savvy and wide-ranging interest in the technological arts and sciences, Ars is the trusted source in a sea of information. After all, you don't need to know everything, only what's important. More from Ars * About Us * Staff Directory * Newsletters * Ars Videos * General FAQ * RSS Feeds Contact * Contact us * Advertise with us * Reprints Do Not Sell My Personal Information (c) 2025 Conde Nast. All rights reserved. Use of and/or registration on any portion of this site constitutes acceptance of our User Agreement and Privacy Policy and Cookie Statement and Ars Technica Addendum and Your California Privacy Rights. Ars Technica may earn compensation on sales from links on this site. Read our affiliate link policy. The material on this site may not be reproduced, distributed, transmitted, cached or otherwise used, except with the prior written permission of Conde Nast. Ad Choices