Your browser is not supported. Please update it.

10 July 2014

Microsoft’s Android moves ‘ desperation, or an Amazon-style plot?

When Nokia launched an Android handset on the eve of Microsoft acquiring its devices business, it seemed like a wicked joke at the expense of the purchaser, a last gesture of independence by the fallen king. Of course, it was also bitterly ironic, given that Nokia had rejected the mass appeal of Google’s operating system in favor of supporting Windows Phone, a decision which probably hastened the once-dominant phonemaker’s decline. Even more ironic is that Microsoft looks set to retain the Nokia Android device family, and reach out to the hated Google ecosystem to rescue Windows Phone itself.

New CEO Satya Nadella has already made significant moves to cut the umbilical cord with Windows and build a developer and services platform based around the cloud, with support for any end-point operating system. His most symbolic gesture since taking the helm from Steve Ballmer was to release the mobile version of Office, the company’s most iconic app, on Android and iOS before Windows.

More recently, the ‘new’ Microsoft introduced Universal Apps, which enables developers to build software that targets any Windows OS, including WP8 and both versions of Windows 8. Given the company’s close cooperation with cross-platform mobile tools provider’Xamarin, with which Microsoft has established an open source .Net foundation, it should not be a big leap to extend this initiative, and allow developers to support iOS, Android and Windows apps from a single code base, rather than forcing them to choose. In yet another irony, this cross-platform approach, now almost a no-brainer, was the way Nokia seemed to be heading before its conversion to Windows, particularly with its 2008 purchase of Trolltech (perhaps the biggest opportunity missed in Nokia’s recent M&A strategy).

For now, Microsoft will release more Android models, and it may allow its Windows Phone products to run Android apps, say reports. According to various online leaks, the next handset sporting the Google OS will not be relegated to the low end of the range, but given the flagship Lumia brand. This makes sense ‘ although it is not yet fully clear how Microsoft will unify its device branding, and whether the ‘Nokia’, ‘Lumia’ or ‘Asha’ names will survive, if it is going to embrace Android in order to bolster the appeal of its own OS, it needs to do that in the mainstream family. This is where most of the marketing and developer effort goes, and Nokia competes most effectively at the smartphone low end. Areas where Windows Phone, as well as the basic Series 40 OS, comes closest to Android and iOS are in emerging markets, where featurephone users may be ripe to upgrade to an affordable Lumia with the breadth of Android apps.

Other reports claim that Microsoft will allow Android apps to run on its Windows Phone products. Credible Russian tech blogger Eldar Murtazin wrote last week: ‘Microsoft has adopted a virtual machine for execution of Android apps on WP. All Lumia devices will support it.’ This would follow in the footsteps of BlackBerry and other minor league mobile platforms ‘ all Android apps run in a VM and some companies have chosen to support Android emulation to boost software choices.

However, the bolder step would clearly be to abandon Windows Phone and acknowledge the victory of Android in handsets ‘ perhaps protecting Windows in large-screen and post-PC devices and the internet of things, but perhaps not. The key will be to defend Microsoft’s control of all these devices and apps, whatever their OS, from the cloud. As Stephen Elop – the Nokia CEO who engineered both Microsoft deals and has now returned to the mother ship as EVP of devices ‘ put it in April, when the Android-based Nokia X launched: “Nokia X uses the Microsoft cloud, not Google’s. This is a great opportunity to connect new customers to Skype, Outlook.com’and Onedrive for the first time. We’ve already seen tens of thousands of new subscribers on Microsoft services.”

Of course, there is also the chance that the old Microsoft, jealously guarding its device-end user experience, is still lurking behind the openness and cloudiness. There are increasing numbers of companies harnessing the Android Open Source Project (AOSP) code to create devices, rather than going through the Open Handset Alliance and having to support Google services and user experiences.

At the end of last year, according to BI Intelligence, about one-quarter of smartphone shipments were running a forked version of Android, or at least an overlay without native Google services support. Some are coming from low end Chinese manufacturers ‘ the hostility to Google in China is a major problem for it in the mobile world ‘ and others are deliberate attempts to tap into Android’s apps base while still controlling a distinctive platform, Amazon and Baidu being the most obvious examples.

Microsoft could try to do the same, creating an Android-based platform which revolved around its own services, particularly the continuing power of Office. It could retain the many strong elements of the Lumia/Windows Phone UI, while giving up the struggle to establish a mobile apps stable after the horse has bolted. And since Microsoft has stopped charging per-device licensing fees to most Windows Phone partners, and owns the largest supporter of the OS anyway, it will not be sacrificing much revenue by shifting its mobile (and embedded) efforts to a platform it did not invent.

The idea is somewhat attractive, but it would still be a mistake. The battle for the mobile OS is won, but only temporarily before the market shifts to new HTML5 platforms suited to cloud-connected devices and the IoT. Microsoft does not need its own OS in this area either. It just needs to embrace whatever gains mass acceptance and deliver its key services to those systems from its own cloud. Nadella understands this, but it remains to be seen whether he can withstand the siren call of trying, one last time, to control the device landscape.