Microsoft says that it wants to push rapid updates to users; but there are issues…
I saw an interesting update on the Supersite for Windows this morning, and I answered a comment asking what the issues were on this in the US. I wanted to expound a bit more, so I thought I’d gather what I wrote and then start shooting my mouth off.
The original article deals with Microsoft taking control of OS related updates from the mobile carriers – in the States, that’s basically, AT&T, Verizon, T-Mobile and Sprint, but may also include a number of larger regional or budget carriers like US Cellular, Cricket and Boost Mobile – and making updates available roughly four to six (4 – 6) weeks after the updates go RTM. Based on a report from Ed Bott, Microsoft is serious about it. According to Terry Myerson,
“Here at Microsoft, we take our responsibility to keep Windows secure seriously. We follow up on all reported security issues, continuously probe our software with leading edge techniques, and proactively update supported devices with necessary updates to address issues. And today, we’re announcing this continuous update process applies to all Windows 10 devices, including phones.”
The only way that Windows as a Service (WaaS) REALLY works, is if Microsoft can release updates to users as they are ready.
The problem is that mobile broadband carriers in the US don’t allow just anything to ride their networks and don’t allow hardware manufacturers or OEM’s to release just any device update without that update going through a testing and certification process. Well, at least everyone but Apple; users of any cellular capable iDevice get iOS updates all the time…as soon as they’re released, in fact. I’ll deal with Apple in just a bit. However, every other device and device manufacturer/ OEM has to jump through a lot of hoops.
There are two parts to this issue: Control of the (enterprise) network and control of support. The second one is easy to understand. The first one is a PITA.
Control of Support
Many users don’t know much of anything about their smartphone past how to make and take calls, send and receive text messages, and change a status update on Facebook (or other social network). Most carriers like these types of users, because they generally accept what they are given, even if they don’t like it (which leads to the first thing, but I’ll get to that in a minute).
Because most users aren’t very tech savvy, they don’t know how to trouble shoot issues when they bump into problems, so they call their mobile carrier for support. The mobile carrier knows that support is a big issue, and don’t want to HAVE to support each and every problem that can arise, especially with exotic or little/unknown 3rd party software. So, they offer crapware that may have much the same functionality that most users are looking for and do their best to push users that way. They pay their support people to troubleshoot the crapware, and to try to get users to use it instead of a similar, and likely much more popular app that does the same thing. They can’t pay their people to know everything about every chat client, social network, photo enhancer, etc. it costs too much money to train and support them.
Control of the (Enterprise) Network
(Most) Mobile carriers don’t allow just ANY smartphone on their network. Unknown or rogue mobile devices can eat up bandwidth; and as much as they want to charge you for the bandwidth you use, mobile carriers certify devices and updates because if it rides on their network, users are going to demand support, so… they limit what can actually get on the network… or they at least try to.
Historically, this is why mobile carriers take so long to test individual devices before they actually offer them for sale; or take so long to test and certify updates before they actually go out to users of devices that use the mobile network.
Think of this the same way you think of your work computer. Your office’s IT department doesn’t let you install everything from any and every download site on the internet. Many sites are blocked to protect the network from viruses and other malware. It’s the same thing here.
All you do is use the network. You don’t own it, so the mobile carrier doesn’t allow you to do any and everything you want…. just like the office. The purpose is public communication. Your use effects the public, and the carrier has an obligation to insure that its available to all that pay to use it.
Now, all of this is SOMEWHAT based on older information. I really ran into this face first when I was a Verizon customer, living in Nashville, TN back in 2003/ 2004. I had two separate talks with a VzW store manager and a Tier 2 install technician (I had a car kit installed for my then, state of the art new, Samsung i700). The install tech who put the car kit in my Honda CRV laughed at me when I asked him why the store staff wouldn’t talk to me. I have to admit, it was kinda funny. However, he explained that I gave them fits because I knew more than they did, and had issues they couldn’t support (smartphones were new back then…). I later confirmed this with the store manager, who apologized, but didn’t offer any helpful suggestions, either.
However, the general principals here are the same now as they were then. Control… at least until you pay me (me, being the mobile carrier). Apple cut a lot of deals to get the iPhone on AT&T (and eventually VzW and T-Mo). Part of that was specifically that Apple has control of OS updates. It worked, and continues to work because Apple sells a BOAT load of iPhones. Mobile carriers make a lot of money via mobile accounts, upgrades, and other add-on related iDevice purchases.
…and volume. Let’s not forget the amount of sales volume they get. The carriers tolerate it because they make a lot of money based on iDevice sales volume.
Microsoft has a huge issue here. They simply don’t – and won’t – have the device sales volume to help them convince mobile carriers not to relinquish they’re control of their networks so Microsoft can deliver both software and firmware updates as needed. I have no idea what incentive Microsoft thinks it’s going to come up with to convince the carriers to allow this to happen. However, you would have to think that it may involve a bit of that ol’ happy cabbage… We’ll have to wait and see what and how MS does to make this happen.
What do you think about all of this? Will Microsoft be able to release updates to Windows 10 Mobile device owners as they want to; or will the US mobile carriers put a halt to it? Would these OS and firmware updates attract you to a Windows 10 Mobile device over, say, an Android device or iDevice?
I’d really like to hear from you on this, so why don’t you join me in the discussion area, below, and give me your thoughts on it all.