Linked by Thom Holwerda on Mon 9th Oct 2017 19:44 UTC

In a series of tweets, Microsoft's Joe Belfiore has revealed that the software giant is no longer developing new features or hardware for Windows 10 Mobile. While Windows Phone fans had hoped Microsoft would update the platform with new features, it's now clear the operating system has been placed into servicing mode, with just bug fixes and security updates for existing users.

I was a first adopter of Windows Phone 7 - so much so I imported a device from the US during launch week. It was an amazing operating system to use, and I loved it. Soon, however, it became clear Microsoft was unable to attract developers to the platform, and even those applications that did make it weren't particularly good - not even the ones written by Microsoft itself, which were often simple HTML-based apps, which simply weren't good advocates for the platform. As a Windows Phone user, you were always scraping the very bottom of the barrel when it came to applications.

To make matters worse, the move to Windows NT with Windows Phone 8 was a disaster. Existing phones weren't updated, and instead, only got an entirely pointless Windows Phone 7.8 update. This didn't do anything to enamour users to the platform, which makes it all the more weird when Microsoft did it again when Windows Phone 10 was released. In any event, Windows Phone 8 did mature over its short lifetime, gaining many features other platforms had had for ages. Sadly, the application situation never improved, and to this day, the Windows Store is a ghost town.

It really sucks that Windows Phone became a victim of blatant mismanagement and market forces, because I still love the operating system and its unique UI. One day, I'll have to sit down and write the counterpart to my Palm retrospective, covering the entire PocketPC/Windows Mobile/Windows Phone era.

It's been a wild ride.

Thread beginning with comment 649718
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Embrace
by judgen on Tue 10th Oct 2017 08:44 UTC in reply to "Embrace"
Member since:

The edge on android is so far just a skin on chrome and does not use their engine.

Reply Parent Score: 3

RE[2]: Embrace
by Morgan on Tue 10th Oct 2017 15:24 in reply to "RE: Embrace"
Morgan Member since:

I find that fascinating, given how many non-Chrome-based browsers exist for Android. I would completely understand it if an iOS version of Edge used Safari, Apple requires it after all. But Google is fairly open about allowing other browser engines to exist on their platform.

Reply Parent Score: 4

RE[3]: Embrace
by modmans2ndcoming on Sat 14th Oct 2017 19:51 in reply to "RE[2]: Embrace"
modmans2ndcoming Member since:

why do the extra work when people just want to integrate their mobile and desktop experiences?

Reply Parent Score: 2

RE[2]: Embrace
by mutantsushi on Wed 11th Oct 2017 01:39 in reply to "RE: Embrace"
mutantsushi Member since:

And that contradicts any MS "need"... how?

Reply Parent Score: 1

RE[2]: Embrace
by modmans2ndcoming on Sat 14th Oct 2017 19:50 in reply to "RE: Embrace"
modmans2ndcoming Member since:

Yes. So that edge users can leverage their bookmarks and other integration features. Who cares about the mobile rendering engine?

Reply Parent Score: 2