Taking existing Android and building on top of it, or ‘forking’ it, is exactly the option that Microsoft has when it comes to Android. There are plenty of reasons in favor of a Microsoft fork of Android, a Microsoft/Nokia Kindle of sorts, and probably as many or more against, but we can sum up the argument down to this: Windows Phone has not been capable of attracting sufficient sales to break the Android/iOS monopoly and create a true ‘three-horse’ race, so that's why an Android smartphone by Nokia (or Microsoft) would leverage a much larger app and developer ecosystem. Finally, since parts of Android are open source, it's not risking too much.
On the flip side of things, it would be an admission of failure of the Windows Phone platform, something that we doubt Microsoft would be willing to do despite the sales situation. Also, it would require some effort and a cloud back-end infrastructure. Let’s be theoretical for a minute and try to step in both Microsoft’s and Google’s shoes to see what it would take for a Microsoft ‘Droid’ to become a reality.
The one argument in favor of a Microsoft ‘Droid’: market share
analysts like the Microsoft-focused Paul Thurott and the AdDuplex network estimate the total platform user base at around 50 million. In stark contrast, Android has an estimated total installed user base of some 1.9 billion, while iOS and Mac combined have around 680 million, so while Microsoft is indeed the third-largest platform, it is so far behind Android and iOS that we cannot seriously consider it a ‘three-horse’ race just yet.
Even worse, the latest statistics show that Windows Phone grows to be more and more dependent on a single phone maker - Nokia. Windows Phone devices by the Finnish company account for more than 90% of all Windows Phone sales. We are all hoping that Microsoft will announce new partners soon, but the reality of the situation at the moment is that its platform has not been met with enthusiasm by phone makers other than Nokia, and the huge sales are not there to give more people reason to buy in.
Additionally, statistics also show that the dynamics of Windows Phone are actually moving down, with diminishing interest in Windows Phone smartphones, and low sales for the platform’s top-shelf smartphones like the Nokia Lumia 1020. What happens instead is that low-end devices like the Lumia 520 that bring low profitability for phone makers are growing their relevant share of the Windows Phone market. That cannot be a good thing for the manufacturer’s revenue sheets.
All in all, the first 'app argument' in favor of an Android-based Microsoft/Nokia could be the strongest, as the Windows Phone ecosystem seems to have been ‘too little, too late’.
Why Android: because of open source, or because of developers, developers, developers?
Google continues updating the AOSP
With over 1 billion applications in its catalog, and a strong developer ecosystem, Android can provide Microsoft with a base that it’s currently missing with Windows Phone. Moreover, Android has largely maintained the principle of providing a level playing field for third-party manufacturers, so that it has the APIs and all other needed tools for Microsoft services. And a quick look at Microsoft’s revenue sheet will tell you in perfect clarity that services like Office are the exact reason why Microsoft wants to be on mobile.
It’s important to note that Android’s openness allowed even starting this discussion about a Microsoft ‘Droid’. Google started with the Android Open Source Project (AOSP)’s huge codebase launched in the early days of Android around October 2008, and has been updating it since then. AOSP is basically the bread and butter of Android, something that a third-party phone maker can virtually take and slap on a device, and have a fully functioning smartphone. It has literally all that’s needed - the launcher, the dialer, phone and contacts apps, the calendar, camera, gallery and so on.
It’s also equally important to make it clear that while the AOSP provides the backbone of Android, it does not include things like Google’s excellent suite of applications including the Google Play Store, Maps, Drive, Gmail, Chrome and so on. All of that is packaged in a separate entity that’s often called Google Mobile Service (GMS), or Google Play services. GMS - unlike AOSP - is proprietary, and has been so from the start, designed to provide access to Google’s cloud services on top of Android. Making use of it is something that requires a paid validation that is rumored to vary in cost, but average at around $0.75 per device.
One key feature of the GMS is that it cannot be divided, you cannot have just a part of it - it is a buy-all, get-all solution. In practical terms, this translates into the fact that all GMS Android phones have not just say Google Play on them, but also the full suite of Google apps.
Here is where the big question for Microsoft appears. If - purely theoretically - the company was to build an Android fork, would it want one that is based on AOSP only or one with AOSP and with GMS?
Or like Samsung?
Building the custom apps seems to be the lesser effort, though, especially for a company the size and expertise of Microsoft. We also ought to mention that a lot of the core apps are available as part of the AOSP already. Chromium is available as an open-source base for everyone to build upon, and in cases where the apps (like the music player) are not well maintained, there are plenty of developers with powerful solutions that can be licensed.
This way, a Microsoft ‘Droid’ would be able to leverage the Android ecosystem fully, but still deliver a unique experience, and most importantly, become a window to Microsoft’s strong cloud services. This has also been done before, and still is - it’s what Samsung is doing to Android, where it keeps the Google core apps, but also offers a competing Samsung app store with competing Samsung applications. Samsung’s explosive growth has been a testament to the viability of such an approach, but we should admit that the business model of Samsung and Microsoft are considerably different.
Will it happen?
We have already seen that companies like Amazon and Samsung have successfully forked Android, and done so in different ways. The big question, however, remains whether Microsoft will actually do such a fundamental change and depart from its Windows Phone platform.
Quite clearly, a Microsoft-made Android device would be a business decision, and sure enough, it will require significant amounts of time and effort. We are not saying in any way that it would be the wiser decision, what we have tried to expose here is whether or not it is possible, and whether or not it’s a viable prospect. To us, it seems like the answer is yes. What do you think?
reference: The Guardian, Ars Technica, Dianne Hackborn