A Microsoft made Android is something often referred to as ‘forking’, something that would take the existing Android and build on top of it, or ‘fork’ it. 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 make for a true ‘three-horse’ race, and an Android smartphone by Nokia (or Microsoft) would leverage a much larger app and developer ecosystem, and finally, since parts of Android are open source, it’s not risking too much.
On the flipside 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
2013 is long over, and with its passing, we can safely say that the mobile space continues to be a duopoly ...
via PhoneArena - News http://ift.tt/1ehNFuu
0 comments:
Post a Comment