Is Android Moving to a Closed Source Model?
In an interesting analysis on Ars Technica, Ron Amadeo argues that Google is progressively shifting Android towards a closed source model. Google's strategy would aim at making Android suitable to be freely customised and used "for little hobbies", while hampering the choices of "anyone trying to use Android without Google’s blessing".
According to Amadeo, Google's strategy about Android has changed from its initial stage. At first, indeed, Google aimed at providing a full open source mobile platform, complete with all the necessary apps and services to make it usable and a thorough competitor in the mobile market. This approach had its goal in having as many manufacturers as possible engage with the Android Open Source Platform (AOSP).
In a second phase, continues Amadeo, after Android became dominant, Google stopped actively developing a few parts of AOSP, including apps like Search, Music, and Calendar. The Ars Technica piece goes into details describing how those open source apps came to a development standstill after Google rebranded them, enhanced them, and made them available as closed source apps in Play Store. “While you can't kill an open source app, you can turn it into abandonware by moving all continuing development to a closed source model", according to Amadeo. It can be also noted that, after the Ars Technica piece was written, Chrome was removed from Android 4.4 as well.
Another pillar of Google's Android strategy aims at locking-in manufacturers through the Open Handset Alliance (OHA), whose members "are contractually prohibited from building non-Google approved devices". What this means is that any OEM trying to build a mobile phone based on an incompatible fork of Android, will lose its rights within the OHA, namely the possibility to use Google Apps in any other product they develop. This contractual obligation has been leveraged by Google against Acer when it tried to ship a mobile phone based on Aliyun OS, a cloud-based Chinese Android fork. More famously, as Amadeo remarks, “no major OEM is allowed to produce the Kindle Fire for Amazon” if it wants to remain in the Android family.
The third pillar of Google's strategy as described in the Ars Technica article is locking-in third party apps through proprietary cloud APIs for Google maps, push notifications, location, in-app purchases, games. Such APIs are not part of AOSP and are not available on non-Google approved devices. In short, according to Amadeo:
Google's strategy with Google Play Services is to turn the 'Android App Ecosystem' into the 'Google Play Ecosystem' by making a developer's life as easy as possible on a Google-approved device—and as difficult as possible on a non-Google-approved device.
A few of the comments to the article pointed out that:
- Google's strategy "is defragging Android [...] Google is doing this because they have to.” (idealego)
- “From the standpoint of the individual user, Google is what brings value to Android devices and makes them useful...” (batmanuel), “Google is entirely justified in keeping a tight lid on those things.” (karlsvec)
- “Even with all these tie-ins turning closed-source, Android as a base is still open-source.”(walkop)
On the other hand, commenters also stressed that:
- “Google's PR face of 'open source android' is, essentially, a lie.” (dbright)
- this strategy, specifically OHA obligations, could hamper innovation from mobile startups. (ChrisSD)
The discussion has extended beyond Ars Technica. In a debate hosted on Android Authority, Robert Triggs states that Google “necessitates the production of some proprietary software and services. It’s impossible for Google to open up all of its software to the open-source crowd”. Adam Koueider observes that Google gaining more control over Android is ultimately a good thing for users, since “you can’t have one pie being pulled in 14 completely different directions”. A poll held on Android Authority website shows that 72% of respondents believe that Google's increased control is good for users, while 13% believe it will be eventually bad.
Stijn Schuermans in the post 'The Naked Android' summarizes Google's strategy about its proprietary APIs:
The operating system had been forked by Amazon and too many Asian handset makers. Worse, it had become too easy to replace Google Play with a proprietary app store yet leverage existing Android apps; too easy to replace Google’s services (Maps) with 3rd party alternatives (Nokia’s HERE). Even the Android brand wasn’t the king of the hill anymore, being eclipsed by Samsung’s Galaxy.
According to Schuermans, Google's response to this has been stripping down Android to its essentials, so that it could let go of it, while consolidating its proprietary Google Play Services and Google Apps.
Another dimension of this issue is represented by OEMs, their relationship with Google, and how they will react to Google's increasing control over Android.
In the context of an investigation about a patent infringement case, The Verge's Nilay Patel reported about Google's practices towards OEMs, stating that there was evidence of Google "using compatibility as a club to make [OEMs] do what we want" and the OEMs were aware of it; furthermore Google would have “a major role in Android device development, to the point where Andy Rubin himself approves and denies requests from OEMs”.
With Samsung selling about 63% of all mobile handsets and with five Samsung models among the ten most successful handsets (Localytics data), it becomes understandable why not controlling its own software is becoming a limit to break for Samsung and why the South Korean company is trying to give more and more relevance to its Tizen OS to move beyond Android, according to an Associated Press story.
Parmy Olson, writing for Forbes, also establishes a relation between the latest efforts done by Samsung in order to get the developer community more engaged with its growing software platform and Google's increasing control over Android and remarks that “future growth depends on keeping customers loyal through unique software services.”
Android is open, Google is closed (which is more than fair)
It's probably not really about software, but about brand. Control, also, but control over Google's products, not the Android operating system.
If you want to build a high-end consumer phone, you probably want the Google brand, services and software, since they are... awesome? Just pay the costs!
But if you want to build a GPS device, or a dedicated home automation device, or a car sound system, or an Internet-enabled dishwasher, or whatever, based on the Android operational system, you can, and you won't worry about Google's anything. And no, Android is not just Linux.
Shane Hastie on Distributed Agile Teams, Product Ownership and the Agile Manifesto Translation Program
Shane Hastie Apr 17, 2015