[DanielHB]

I think the critical failure of the windows phone was that app development was not open. You can't compete with established walled gardens by building your own, you can only compete if you make a huge amazing park free to use just outside the walls of the competitors.

Translating this to windows phones, it would have only succeeded if it either:

1) Made browser applications first-class and pushed phone-specific APIs (gyro, bluetooth, etc) to be open. Then pick a fight with google and apple about supporting PWAs better. This would probably keep windows phones as a "low cost, crappy feeling" systems forever.

2) Made the windows phone native-apps trivial to port to run on browsers with a convenient and easy way to deploy those apps on ios/android (hopefully without feeling too much not-native on those platforms). Would require a lot more engineering resources and time, so much harder to pull off.

[shortrounddev2]

Well they did do something like that; Windows Phone apps were written in the same .Net UWP SDK as desktop apps, so the idea was that you could target both platforms at once (and Xbox as well). I think MS overestimated how much people cared about native PC apps by that point (basically not at all). Additionally, snapchat was the hot new app at the time, and there was no first party Snapchat app (and if you used the 3rd party one, you risked being banned from snapchat).

The Lumia remains my favorite phone of all time

[DanielHB]

I would argue that windows desktop development using .net is a walled garden in itself as well.

They finally realized what I was saying when they acquired Xamarin in 2016. I never used Xamarin myself, but I hear it is not that great and kinda dying. So like I said the native open platform approach was a lot harder to pull off.