Google recently announced some changes in its Android development process. While Android remains open source, there will be less development in the open, and more development in private, with cadenced open source releases. In a large sense, this has always been the case, given that Google has always had paid, pre-release access programs for top Android product developers.
Android has long been one of the most renown and successful COSS business initiatives, developed to challenge Apple’s dominance of mobile devices and drive traffic toward Google’s search and services. Google has always had two Android development branches, one public and one private. Now, Google is streamlining them, to avoid duplication of effort. Google says it expects this move to have little effect on developers. (More details about how the release cadence works here.)
Android’s development was always the poster child for the “embargo” business model, where open source releases were free, but paying customers could get early access. This move may represent a step away from such models–with COSS dividing into open and closed initial development cycles.
For almost all COSS–or all open source for that matter–some development usually takes place in private, before commits to public repositories. The line between public and private development has always been, and will remain, a fuzzy one.


Leave a Reply