In light of the $5 billion EU antitrust ruling against Google this week, we started noticing a certain classic Ars story circulating around social media. Google’s methods of controlling the open source Android code and discouraging Android forks is exactly the kind of behavior the EU has a problem with, and many of the techniques outlined in this 2013 article are still in use today.
The idea of a sequel to this piece has come up a few times, but Google’s Android strategy of an open source base paired with key proprietary apps and services hasn’t really changed in the last five or so years. There have been updates to Google’s proprietary apps so that they look different from the screenshots in this article, but the base strategy outlined here is still very relevant. So in light of the latest EU development, we’re resurfacing this story for the weekend. It first ran on October 20, 2013 and appears largely unchanged—but we did toss in a few “In 2018” updates anywhere they felt particularly relevant.
Six years ago, in November 2007, the Android Open Source Project (AOSP) was announced. The original iPhone came out just a few months earlier, capturing people’s imaginations and ushering in the modern smartphone era. While Google was an app partner for the original iPhone, it could see what a future of unchecked iPhone competition would be like. Vic Gundotra, recalling Andy Rubin’s initial pitch for Android, stated:
He argued that if Google did not act, we faced a Draconian future, a future where one man, one company, one device, one carrier would be our only choice.
Google was terrified that Apple would end up ruling the mobile space. So, to help in the fight against the iPhone at a time when Google had no mobile foothold whatsoever, Android was launched as an open source project.
Powered by WPeMatico