Comment by ianbutler 2 days ago
MetroUI in Windows 8 was pretty universally panned. I thought it was pretty good on tablets and such, but it left a lot to be desired on desktops and hid a lot of functionality, it went too mobile for a lot of people's tastes.
Disclaimer: I was one of the dozens who used a windows phone. The Nokia Lumia 920 was great, you can fight me.
Wrong. There was full app compat of WP7 apps in WP8 and Win10 Mobile, and for WP8 apps in W10M. The only full backward app compat break was from WM6.5/WP6.5 to WP7.
I'll give you the benefit of the doubt and assume you're thinking of the lack of device OS upgrades: from WP6.5 to WP7, from WP7 to WP8, and from older WP8 devices to W10M. So no forward compat, but absolutely yes to backward compat.
That's not what they mean. As a developer, the API you used to develop your app was now deprecated with no migration path. That meant your app was deprecated, with no migration path.
For an app platform already a distant third place and struggling to attract developers, pissing off the few devs you do have TWICE was not a smart move.
You joke, but I honestly wonder if this period and projects didn't involve a bunch of Microsoft employees who got a little overexcited when they were told that they didn't need to maintain the insane, sometimes bug-for-bug, compatibility layers with 20-40 year old software that they had had to deal with their entire career there.
Must have felt incredibly liberating, and maybe they got a little too into the whole idea of "fresh start"(s).
See also Windows RT.
I think a lot of people liked the Windows mobile experience. Shame it didn't quite get enough market share.