The Windows Phone 7 Review

Updates

At Microsoft’s reviewer’s workshop for Windows Phone 7 the subject of software updates caused a bit of unrest among the press in attendance. To understand how Microsoft handles update delivery let’s look at how Apple and Google do it first.

When Apple updates iOS it first puts the software update through its own validation tests. These tests include regression testing to make sure that previously fixed bugs are not re-broken by the new update. The tests also include basic functionality as well as usage model tests to try and simulate real world use. AT&T also gets to test these updates, after all it is AT&T’s network. The final update is placed on Apple’s servers and delivered to you by Apple. Updates have to be installed over USB.

Google is very different. Android releases go through the same testing and validation process within Google, however given the wide variety of hardware on the market the testing isn’t done on every device. Google’s partners are provided with final code which they have to bring in and implement their customizations on top of (e.g. HTC Sense) before they’re released to customers. The OEMs and carriers have the final say on what Android versions come to their devices and when. This creates a bit of frustration as not all Android devices will get equal treatment when it comes to updates. It’s the downside to doing extensive UI customization, when Google delivers an update the OEMs have a lot of work to do in order to implement the update. Android updates can be installed by copying the update package directly to the device or downloaded over the cellular/WiFi network.

Microsoft’s update approach closely mimics Apple’s. Microsoft has its own validation that all updates must go through before release. Microsoft has even mirrored AT&T’s testing labs on its campus so that whenever an update rolls out, Microsoft already knows how it will fare on AT&T’s tests. The update code is then handed off to AT&T with a test report showing how the update did in Microsoft’s internal testing. AT&T then takes the update, does its own validation (which should mirror what Microsoft has already done) and finally pushes it out to end users.

Microsoft physically hosts the update, however it is the carrier’s call whether or not to release it to customers. Given the ban on UI customizations and the unified hardware support, there should be no technical reason for a carrier to prevent an update from going out. The fact that Microsoft will deliver, with every update, a list of how the carrier’s own validation tests will run should guarantee that any failure to push out said update would be negligence on the carrier’s part. Microsoft went on to say that while it’s possible for a carrier to prevent a Windows Phone update from going out, it doesn’t believe it’s a likely scenario. While Microsoft didn’t say it explicitly, the implication is that Windows Phone won’t have the update issues that have plagued certain Android customers.

Microsoft did state that it wouldn’t offer a direct download of updates. Similar to updating iOS, you can only update Windows Phones over USB. Updates over WiFi and the cellular network aren’t supported.