Distilling market noise into market sense
The VisionMobile blog is a space where VisionMobile analysts and industry insiders exchange views on the fast-changing mobile market and the trends that define the future direction of telecoms.
The Android Monopoly and how to harness it
[Behind Android's stellar success is a love and hate relationship with handset vendors. Android is a critical launchpad for PC-borne OEMs like Dell and Acer, but a short-term life support for mobile vendor incumbents like Sony Ericsson and Motorola. Research Director Andreas Constantinou looks at how OEMs can leverage on virtualisation to get the best of both worlds with Android; the burgeoning app ecosystem, but without Google's lock down of experience differentiation]
From an underdog to ubiquitous manufacturer support, the Android platform has come a long way since its introduction in 2008. Almost every single device vendor (except for Apple and Nokia) has launched Android devices, while Sony Ericsson and Motorola are betting their margins and future on it. The phenomenal rally behind Android is – in a nutshell – due to 4 factors: the operator demand for a cheaper iPhone, the burgeoning Android developer community, Android’s market readiness (3 months to launch a new handset) and the ability to differentiate on top of the platform.
A monopolist on the rise?
Year after year, Android keeps on surprising industry pundits. Google’s software platform saw 100% quarter-on-quarter increase in the first 3 quarters of 2010. The last quarter of 2010 saw Android go chest-to-chest with Nokia in terms of smartphone shipments, in what CEO Stephen Elop called â€˜unbelievable’. With such meteoric rise, analysts are beginning to talk about a potential Android monopoly in the future market of smartphones, contested only by the Nokia-backed Windows Phone.
The Google commoditization endgame
Is Google the biggest benefactor the industry has seen? Not by a long way.
Google runs a hugely successful advertising business and needs to bring as many eyeballs as it can onto its ad network. To this end, Google’s agenda is to commoditise handsets by forcing smartphone prices down (see our analysis on the $100 Android phone) and having its ad network deployed on the broadest possible number of smartphones (via closed apps like GMaps and Gmail).
Moreover, Google’s agenda is to commoditise mobile networks by flattening the mobile termination barriers and removing volume-based price plans that telcos have traditionally built.
At a 10,000 ft level, Google’s strategy is based on deceptively simple microeconomics principle; to drive up the value of its core business (ad network) it needs to commoditise the complements (devices, networks and browsers).
Naturally Google is hermetically closed in all aspects of its core business. The Android Market, GMaps, Gmail, GTalk are â€˜closed source’ and the Android trademark is commercially licensed. This means that while Android is open source, Google uses the Android Market and trademark to enforce strict compliance of Android handsets to Google’s CDD and CTS specifications. See our earlier analysis on Android’s hidden control points for how Google runs the show.
So Google is by no means a benevolent benefactor. Like any other company out there, it’s in it for the money; a rationally-driven business of the platform era, out to commoditise the mobile handset business with a free-for-all carrot.
Winners and losers of the Android game
For handset manufacturers, Android is both a blessing and a curse. A blessing because it offers OEMs a low-cost-base, rapid time-to-market platform from which to build differentiated designs. This is manna from heaven for PC-borne assemblers who use Android as the pier from where they can gain firstly a foothold in mobile and secondly global reach.
At the same time it’s a curse; Google’s control of Android compliance means that it deprives OEMs of all points of differentiation: user interface, hardware features and industrial design – except for (you guessed it!) price. Which means that with Google defining the Android experience, there’s little differentiating a Sony Ericsson handset from an Acer handset. With Acer happily operating at 3% profit margins, Android is to Motorola and Sony Ericsson just a short-term life support.
Nokia too evaluated Android before hoping on an strategic partnership with Microsoft on Windows Phone 7. As Stephen Elop said during the press conference with Steve Ballmer, “we assessed Android [...] but the commoditisation risk is very high”. In sight a potential Android monopoly threat operators, too and getting wary of over-supporting Android.
Best of both worlds
Confronted with Android’s two-faced agenda, major handset vendors have been apparently plotting how can they get the best of both worlds; the burgeoning apps ecosystem but without the Google’s control of the user experience. Three approaches have emerged.
1. The Do-it-yourself approach: By virtue of the open source (APL2) license, any handset vendor can take the public Android codebase, branch it, tweak it and deploy it on handsets. China Mobile has commissioned Borqs to develop the oPhone spin-off while Sharp has released handsets based on the Tapas spin-off also for the Chinese market. However, branching Android means that you miss out on the 130,000+ Android apps as Google won’t give you access to their app distribution system – which is ok if you â€˜re targeting China, but unacceptable if you â€˜re targeting any other region. Moreover, the Google Android codebase moves faster than any other platform (5 new versions within the space of 12 months) meaning that it’s near impossible to maintain feature parity in Android spin-offs – the same reason why Nokia publically regretted forking WebKit in the past. Lack of feature parity means that an Android spin-off would breaks the developer story and stays behind the competition of Android Experience and Partner phones.
2. The virtual machine approach: Myriad announced Alien Dalvik , a solution it claims can run Android apps on non-Android handsets, including on Maemo. Alien Dalvik is a Java SE virtual machine designed in Zurich and China by the same ex-Esmertec guys who started off the OHA consortium. Myriad has released a demo of Alien which however hides the real issues behind a pure virtual machine approach: the lack of 100% API compatibility and most importantly access to the distribution of 130,000 apps available through Google’s Android Market.
3. The Virtualisation approach: the third and most promising approach is to run a complete replica of the Android platform within an isolated, â€˜virtual’ container using mobile virtualisation technology (from Red Bend, OK Labs or VMWare – see our earlier analysis of virtualisation technologies). The virtualisation approach offers a sandboxed, complete version of Android (including the apps ecosystem) which co-habits the same handset as the OEM-specific core UI and applications. Virtualisation technology is mainstream in cloud and enterprise, but applied only in a limited context in mobile to reduce hardware costs or run enterprise micro-environments (the type Barack Obama enjoys in his virtualized BlackBerry cellphone).
The real opportunity with virtualisation is to deliver the best of both worlds for handset OEMs who want to leverage the 130,000+ apps ecosystem, but maintain their own apps experience and signature user interface. A virtualized Android co-inhabiting with the native app experience (think S40, Symbian, QNX, BlackBerry OS 6, Web OS, or Bada) would allow OEMs to resist commoditization while having ample degrees of freedom to differentiate.
The question is: will Google allow OEMs access to the Android Market and the Android trademark when the platform is run within a virtualized shell?
Such an approach would allow Sony Ericsson, Motorola, RIM, HP and the others not to compete against Android and neither to surrender to Android – but to leverage Google’s network effects and harness the Android innovation wave.
Comments welcome as always,
you should follow me on Twitter: @andreascon