If you're a Windows 10 Mobile fan, you may have received a bit of a shock last week when Microsoft announced the first wave of devices that would be officially getting their Windows 10 Mobile update. Actually, that wasn't the shocking part. The shocking part was that there wasn't going to be a second wave. That's right Microsoft fans, what you see is what you get. There were some notable exceptions left off this list, including the Lumia 1020, the Lumia 920, and the Lumia 930. Interestingly enough, the Lumia Icon, which is basically the Lumia 930 in a bright red Verizon candy shell is still "being considered." But then Microsoft did say no second wave, so maybe for wave 1.5? Anyway.
Bottom line, due to performance issues and user feedback, it was decided that many older devices that technically meet the specifications would not be getting the latest and greatest Windows operating system. Whiskey to the Tango to the Foxtrot?
History repeats itselfSo, Microsoft is doing it again. The great beta test in the sky is coming back to bite us in the keysters one more time. Anyone out there running Windows Phone 7.8 and wondering why they can't just have 8? This is a similar situation. Yes, the jump from Windows 7 to Windows 8 had some hardware complications, but that didn't change the fact that if you were holding a Lumia 900, you were going to be on the wrong side of that divide.
Microsoft is building a reputation of essentially screwing its own customers out of upgrades. We're wandering into "fool me once" territory here. You can put iOS 9 onto an iPad 2. If a phone is technically capable of running the software and the user has a choice of whether or not to update the software, then where is the harm? Even if a user experiences some performance issues, isn't that to be expected on older hardware? Any user going into that upgrade should be well aware of the risks, considering they'll know they're holding older hardware.
And yet…On the other hand, this is understandable. Microsoft should not be expected to deliver a product that will run badly on your phone. Remember, this is not a beta product. This is an official release. You'd be going all in with an operating system that had a higher percentage of performance issues on your phone. This is arguably your most important piece of technology in your life. You don't want it getting bogged down, laggy, or otherwise suboptimal if you're going to be using it on the daily.
Also, consider that it's not just Pocketnow readers who will be potentially installing this upgrade. It'll also be Joe consumer who went out and bought a phone with a great camera and really digs it to this day. This consumer isn't going to know that an operating system behaved badly in a beta. Heck, they're probably only vaguely aware of what a "beta test" is. All they know is their 1020 takes great stills at Bobby's soccer games. If Microsoft decides to release this upgrade to Joe, he's going to install it, and he probably won't even read the Terms of Service (because, really, who does?). So now Microsoft has broken Joe's phone through no fault of his own – except perhaps not reading the Terms of Service.
Nothing wrong with oldBecause at the end of the day, you should buy and use a phone based on what it does today, not based on what it might do tomorrow. If Microsoft isn't upgrading your Windows Phone, you're welcome to be a little miffed about that fact, but honestly, it makes sense when you really stop and think about it. Especially in the context of Joe, just some poor schlep who bought a great phone three years ago, and now can't even get Angry Birds to run because it's laggy as hell now.
But that's just how I see it. The true nature of the debate is what happens down below. Is Microsoft screwing over its fans with this move? Or it Microsoft hedging its bets by not releasing a potential disaster to the average citizen? There are compelling arguments on both sides, and I might've even missed some, so sound off below and let's see if we can figure this out.
Source: Windows 10 Mobile update: Is Microsoft screwing some of its users out of it, or is it making the right call?
No comments:
Post a Comment