4 ms·

I am not in any position to give advice to Microsoft, but it seems to me that they are trying to apply the winning strategies they used in one game to all the o

I am not in any position to give advice to Microsoft, but it seems to me that they are trying to apply the winning strategies they used in one game to all the others. Example: WP7. What is expected: They ship fast and they update fast and agile, they don't have giant compatibility legacy to maintain. What actually happens: WP7 took forever to ship and never got updated. My speculation why it happened: they've got some lengthy and fairly bureaucratic process of approving new features, new versions, etc. They apply the same methodic they used with windows to their WP7, like, always maintain backward compatibility, be very reliable (well, you all know what happened) and predictable. They're, like, four years late and they keep wasting time. Not to mention that WinMo wasn't too great either. I had an iPaq, which was sort of okay, but it didn't rock. It wasn't "cool" in any sense. And they probably vastly underestimate the coolness factor. My $0.02.

mattmanser 16y ago
I don't think that's their strategy generally. Their current development strategy for things like MVC and Silverlight is to pre-release new functionality as an unsupported project, full source and iterate fast. They're quite agile in areas. WP7 feels like some one has suddenly put the breaks on it.
- smiler 16y ago
  It's one thing to ship MVC & Silverlight as unsupported projects and iterate fast, but quite another to iterate phone software quickly where you could potentially brick millions of phones with one small software update. As noted in this blog post, an update applied to the phone broke it and the user had to get a brand new phone. This added a customer service burden to the mobile provider / network - which in turn means they will moan to Microsoft when they do this and give them less enthuiasm for WP7 devices in future if it keeps happening.

mattmanser 16y ago

I don't think that's their strategy generally. Their current development strategy for things like MVC and Silverlight is to pre-release new functionality as an unsupported project, full source and iterate fast. They're quite agile in areas. WP7 feels like some one has suddenly put the breaks on it.

smiler 16y ago
It's one thing to ship MVC & Silverlight as unsupported projects and iterate fast, but quite another to iterate phone software quickly where you could potentially brick millions of phones with one small software update. As noted in this blog post, an update applied to the phone broke it and the user had to get a brand new phone. This added a customer service burden to the mobile provider / network - which in turn means they will moan to Microsoft when they do this and give them less enthuiasm for WP7 devices in future if it keeps happening.