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.

  • 11
    Feb
    2011

    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]

    VisionMobile blog - The Android Monopoly and how to harness it

    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).

    Android as the centre of a 5-sided network

    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.

    OEM + Android - Winners & Losers

    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,

    - Andreas
    you should follow me on Twitter: @andreascon

    Andreas Constantinou

    Andreas Constantinou

    As Managing Director, Andreas oversees the growth and strategy of VisionMobile. He has twelve years experience in mobile, having worked with the top brand names in the mobile industry including Telefonica, AT&T, Telenor, Vodafone, Deutsche Telekom, MTS, Nokia, Sony, RIM, HTC, Qualcomm, Ericsson and Microsoft. Over the last five years, Andreas has grown VisionMobile into the leading, most respected research firm on telco economics and developer economics, with a client base and reputation that out rivals companies many times the size.

Troed Sångberg

With industrial design being one of the main differentiators when selecting from an otherwise equal feature set, wouldn't that create the opportunity for bigger margins as well?

It seems to be true in other industries with cut throat competition – clothing, cars etc.

 
11Feb
Jonas Hermansson

I'm not sure about virtualisation.

How would an end user use a handset with virtualisation? Wouldn't it always be confusing and cumbersome to move between different environments.

I agree with Troed that industrial design could be an option for differentiation but also:

-HW features such as camera(s)

-superset of APIs adressing a specific vertical

-gaming

-enterprise services

-formfactors

-unique cloud services

 
11Feb
Michael

"Google’s control of Android compliance means that it deprives OEMs of all points of differentiation: user interface"

Sigh. If only this were true. Sense, TouchWiz, Motoblur: you can all DIAF. I don't want "differentiation". It is not good for me as an end-user. It means updates to my devices are delayed, or missing entirely. It means I have to deal with ugly, buggy replacements for stock android functionality (e.g., the HTC Sense "People" app that replaces the dialer/contacts).

"Differentiation" like that means, simply, "making Android worse".

 
12Feb
Jonas Morän

To me the virtualisation conclusion is completely up side down. My conclusion is; take advantage of the fact that "bread and butter features" are done by Android and build your own "hyper targeted" additions. But make it smart, not to create your own, internal fragmentation! (Differentiation in "phone book design" is waste. Fully agree!)

The OS and even the eco-system attached to it will seize to be (have already?) differentiators. Android is a blessing for the big old OEMs. True, newcomers that are used to 3% margin will take the bottom layer of the cake, but at least there is now a vehicle to address the icing layer (read challange Apple's margins), which none of them could have done on their own.

 
13Feb
Vas Rastinen

Jonas: "My conclusion is; take advantage of the fact that “bread and butter features” are done by Android and build your own “hyper targeted” additions"

How, pray tell, do you imagine low-margin handset makers to differentiate smartly, when they can't:

– differentiate with services

– compete with Google's services

But can only change icons, launchers and built-in apps and industrial design?

Where's is the value added pricing power and margins?

Care to elaborate?

 
15Feb
Jonas Morän

@Vas Ratinen. Absolutely! I'd say OEM's are ill equipped to compete on services. It's not in their DNA. And eventually the consumer won't select their device based on services it brings. They'll like to use the best ones out there; Spotify for music, Netflix for movies&TV, Dropbox for cloud storage…

So, it's in the hands of the OEM's to find other means of differentiation that is truly valuable to the consumer. What that is is the Billion dollar question. If you ask me I'd say that at least partially it lies within traditional differentiators: Industrial Design, HW innovation & integration etc.

But I agree it won't be enough to make a quantumn leap, because it's obvious and all will go there.

What will the Golden Feature be 2012…?!

 
15Feb
Andreas Constantinou

@Troed,

If industrial design alone can secure margins, then why aren't PC manufacturers (-Apple) having differentiated pricing? I think mobile is comparable more to PC than clothing/car examples you mention as mobile is utilitarian (like PC) whereas cars and clothing is more aspirational than utilitarian.

@Jonas,

Virtualised cells can be presented through a single menu interface (e.g. widget-like or WP7-like). Clicking an app switches to the virtualisation cell that hosts that app. It's transparent to the user.

@Michael: agreed that OEM UI differentiation is self-serving. OEMs customise the UI so that they can argue to their operator customers (and the OEM management) that the device offers something above the competition and therefore worth more $cents per handset.

 
15Feb
Ankur Jalota

@Andreas Even if an OEM did virtualize Android, and make running Android apps transparent to the user, it wouldn't be – the look-and-feel of an Android app would then be different than the OEM's OS.

 
16Feb
Nachi Junankar

Andreas, great entry! As you may know, my company OpenMobile is in the business of giving power back to OEM's so they can differentiate at any level they'd like. We think it's an elegant way to handle dellification/commodification.

Thanks again!

Nachi

 
22Feb
Tsahi Levent-Levi

Andreas,

I think there are two other approaches as well, each targeting a different decision made by a handset vendor.
If a handset vendor wants to get out of Google's control, it can use other markets – especially the Amazon one, once it opens up. If the Amazon market will have enough applications in it, it might become a viable alternative to Google's Android Market.
For handset vendors who still want the Android trademark and Google's Android Market, the differentiation I see today is by moving towards cloud services for their handsets. The leading vendors today are investing heavily in such services – either by inhouse development, acquisitions or placing money on startups in this area.
Virtualization might be another viable option, but I don't see it materializing in 2011.

Regards,
Tsahi

 
26Feb
Pedro

"I think mobile is comparable more to PC than clothing/car examples you mention as mobile is utilitarian (like PC) whereas cars and clothing is more aspirational than utilitarian."

Have to disagree with that one. A mobile phone is like a wristwatch. When you meet friends at a cafe and everyone puts their mobile phone on the table, it's a fashion statement. And in an all-Android world – without other significant differentiators – it's by that metric that a lot of people will choose their device. Case in point: Motorola Razor…

 
20Mar
Vishruth

Andreas

The article is well written with the way you have summarized the overall eco-system.

I have a few comments:

1. You have referred to the CDD and CTS specifications of Android. I should say they have eased up some of the hardware requirements in Gingerbread, which will now enable OEMs to make lower cost Android devices. Please see my article related to this at http://mobiletopics.wordpress.com/2011/01/02/ging

2. This comment is related to the topic of virtualization that you have mentioned. At our company we provide Android software services. As part of these Android services we have also undertaken Android projects on virtualized platforms. One of the big challenges faced is the performance of Android on a virtualized platform. For e.g. the UI response become sluggish. Further, R&D costs increase not-only in creating such a virtualized platform but also maintaining the same. For e.g. various tweaks need to be done in Android to have a decent if not the best performance on a virtualized platform. But as you have mentioned Google makes new Android release every 4 to 6 months. So this becomes so much more harder for an OEM to quickly upgrade to the newer version of Android. Further, it is very important for any OEM to keep their devices updated to the latest release of Android to avoid their customers wrath. So I believe, the virtualized platform will be primarily good to drive down BOM costs targeted specifically at emerging markets.

 
21Mar

Vision Mobile Blog

Distilling market noise into market sense

The Mediatek Phenomenon: the new smartphone disruption shutterstock_106186655

[The next disruption in smartphones comes not from the power struggle between Apple, Google and Amazon, but from silicon. Guest…

Continue Reading
[Infographic] Developer Economics 2013: Dev tools are the foundation of the app economy DE13_preview

We’d like to present our latest infographic, based on the latest Developer Economics report – themed around dev tools. This…

Continue Reading
Connecting the next 5 billion users: Emerging markets and the need for new business models Business model innovations for connecting the next 5B users

[With so much excitement about smartphone growth, we often forget that the biggest opportunity still lies ahead, in connecting the…

Continue Reading

Vision Mobile Research

Analytical reports on emerging solution markets

Developer Outreach dev_outreach

Developers are fast becoming the de-facto engine for innovation in the mobile industry. But how can you approach the right…

Developer Economics 2013: The tools report DE13_flagF

This is the fourth in the series of Developer Economics reports, our highly acclaimed developer research series. Besides benchmarking developer mindshare,…

Mobile Insider Oil pump on the sunset sky

Mobile Insider is a monthly publication that examines under-the-radar and forward-looking trends in mobile. Each issue focuses on a specific…

Vision Mobile Strategy

Market Sonar MarketSonar_ill

Market Sonar is a customisable reporting service, based on Big Data from all major app stores. We deliver monthly, quarterly…

Report: Telco Innovation Toolbox Telco_web

Telco Innovation Toolbox showcases 10 economic models on how Telcos can manage disruption and reinvent themselves. This report, produced in…

Telco Innovation Toolbox VM029 - SEBroc_V0.5_HR-1 copy

“Telco Innovation Toolbox” is a strategy workshop introducing the new economic thinking necessary for successful innovation by telcos. Aimed at…

Privacy Policy

1. Introduction

VisionMobile Limited (referred to as “VisionMobile”, “we, or “our”) is committed to protecting the privacy of visitors to the VisionMobile web site(s) together with all related surveys, discussion forums, directories and databases. This privacy policy explains how we collect and use the information we collect about you.
By accessing and using this web site, you agree to the terms of this privacy policy.
As used in this Privacy Policy, the term “Personal Data” means data such as: your name, mailing address, e-mail address or other personal information that may be supplied by you or collected about you. We hope that this Privacy Policy helps you understand what kind of Personal Data, if any, we collect at this site and how we handle and use any such personal data after collection. Please note that we may provide aggregate statistics about our surveys, sales, traffic patterns, and related site information to reputable third parties, but these statistics will not include personally identifiable information (such as name and email address). VisionMobile is committed to protecting your privacy and does not engage in the practice of selling or trading Personal Data to other companies for promotional purposes.

2. Personal Data Provided by You

To respond to your questions, fulfill your requests or manage our online Surveys, it may be necessary to ask for or obtain Personal Data. If you provide us with any Personal Data, we may use it to respond to your requests or manage our surveys. By providing information to VisionMobile through this Site, you acknowledge and consent to the collection, use and disclosure of personally identifying information of the type and for the limited purposes described in this Privacy Policy.
If you place an order for a product, request a service or submit content to this site, we may need to contact you for additional information required to process or fulfill your order and/or request. Unless compelled by applicable law or administrative or judicial order, we will not provide this information to a third party without your permission, except as necessary to process your order, fulfill your requests, manage interactive customer programs or, if you are a corporate user, enable administration of access and usage of this Site by authorized personnel in your organization.

3. What type of information is collected?

To provide you with our Services and/or Products and to collect your views via our online surveys, we collect certain personal information about you. The information we collect may include, but is not limited to, your name, address, email address and work details.
We do not store credit card or debit card details. If you have given us your credit card or debit card details, we will only use this information to process your order and we will delete this information once your order has been completed.
We do not collect any sensitive personal information such as information on your racial or ethnic origins, political opinions, religious beliefs, trade union affiliations, sexual life, health or criminal history.

4. How is information collected?

We may collect personal information about you from the following sources:
4.1 Personal details registered by yourself in relation to VisionMobile online surveys.
4.2 Personal details registered by yourself in other ways e.g. via our website feedback forum or our Blog
4.3 Information about your visits to our web site(s);

5. How long is the information retained by us?

We only collect information which is necessary for the operation of our web site(s) and for the provision of our Services. We will not keep your personal information for longer than necessary to provide the Services or as required by law.

6. External Web Sites

This privacy policy only applies to our web site(s). Our web site(s) may contain links to external web sites. Please note that we are not responsible for the privacy practices of other web sites. We recommend that you check the privacy policy of any other web sites you may visit through the web sites.

7. Changes to Privacy Policy

We may amend this privacy policy from time to time. If we make any changes we will post them on the web site, so that you will always be aware of the way we use your personal information.
terms of use.
The contents of the VisionMobile Forum are licensed under a Creative Commons Attribution 2.5 License. The contents of the downloadable papers published through this website are licensed under the terms specified within each paper. The remaining contents of this website are licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License.

8. Cookie Policy

Cookie Name Info URL Info
_vm1 VisionMobile The purpose of this cookie is ensure that a user is authorized to download the report . Vision Mobile does use the data stored in this cookie in any other way.
_prli_click_? Pretty Permaling The purpose of this cookie is to log information from the Pretty Links Lite Plugin in order for the plugin to know that the user has clicked in the pretty link of the (id=?) to go to the VisionMobile website.
mp_2dccbf28670dda1c8b77def198be2f89_mixpanel MixPanel The purpose of this cookie to use mixpanel to identify the mixpanel user to track the flow of the visitors from page to page. No personal or any other private information is captured.
(a)_utma
(b)_utmz
(c)_utmb
(d)_utmc
Google Analytics (a)This cookie tracks the number of times a visitor has come to www.visionmobile.com including their first and last visits.
(b)This cookie tells VisionMobile from where you, the visitor, were referred to www.visionmobile.com
(c)This cookie is used to determine the length and time of your visit to www.visionmobile.com
(d)This cookie works with _utmb to determine the length of your visiting session to www.visionmobile.com and when that session has ended.
VisionMobile does not use the data stored in these cookies in any other way.
(a)__qca
(b)mc
Quantserve (a)The _qca cookie may use your computer’s IP address, pixel code, referring HTTP location, current HTTP location, search string, time of the access, browser’s time, any searches made on the applicable website, and other statistics” in order to “analyze Log Data from different websites and combine it with other non Personally Identifiable Information to produce the Reports that are made available on the Quantcast.com Site, to enable web publishers and advertisers to deliver audience segments that are appropriate for their products or services.
(b)The mc cookie set by Quantserve is related to advertising, and may track your behaviour on the VisionMobile website.
PREF Google cookie This cookie remembers users basic search preferences. The Google “PREF cookie” is used to remember our users’ basic preferences, such as the fact that a user wants search results in English, no more than 10 results on a given page etc. Expiry is set to 2038 in order to preserve user preference information. See here for more information.
Please enter your email to receive weekly updates from the VisionMobile blog
I also want to subscribe to the monthly newsletter, with updates on VisionMobile news and research (you will receive a separate email for this list, please subscribe to both to receive the newsletter and blog updates)