Buggy updates. Delayed updates. More buggy updates. No clear sales figures. Has Microsoft dropped the ball with Windows Phone 7?
I'll be honest with you, I was expecting that Microsoft's handling of the Windows Phone 7 launch and subsequent updates would be as smooth as silk. It needed to be. Microsoft faces an uphill battle in the face of iOS and Android. Microsoft is making a billion dollar gamble with Windows Phone (as are the OEMs involved), the risks are high so it's better to keep the foul-ups and fumbles to a minimum.
But the past few months have been a catalog of foul-ups and fumbles. Let's go through a list:
The silence (not to mention absence) of updates is really starting to annoy users. Paul Thurrott wrote a scathing piece on Windows Phone Secrets the other day criticizing Microsoft and holding Apple up as a positive example of how to handle updates:
I’ve already written about how frequently Apple updated its original iPhone during the same time frame under which Microsoft and its partner ecosystem are now ignoring the needs of their own Windows Phone customers. (And, please, don’t be idiotic. These really are needs: Windows Phone shipped in an incomplete and buggy state that has never once been updated. This isn’t just “wrong” morally: Shipping a known-buggy product to consumers is arguably wrong legally as well.)
...
Well, here’s an inconvenient truth for you: When Microsoft launched Windows Phone in October/November 2010, the then-current version of iOS was 4.1, released back in September of that year. And since then, Apple has released:
He then goes on to list every iOS update, from 4.2 to 4.3 (five in all). Yeah, five in the time it has taken Microsoft to release one buggy update that failed to installed on 10% of handsets.
Come on Microsoft, you can do better than this. Right now you're just handing more market share to iOS and Android.
[poll id="604"]