Windows Phone 7 Update Strategy And Specs Leaked

Although much of Microsoft’s strategy for Windows Phone 7 was discussed at MIX last month, the company left a handful of key details hazy – portions of the hardware specifications and software update strategy were included amongst those. Much of this seems to be revealed due to a leaked “architecture guide” slide deck where we see that retail devices will be required to feature cameras (that could be a problem for corporate environments), FM radio tuners, compasses, and proximity sensors, among other obvious features like a capacitive touchscreen display. Of course, these are all requirements for the initial volley of launch devices at the end of 2010, it’s probably reasonable to assume that future iterations will be tweaked.

Moving on to software, the deck confirms that a Windows Live ID will be required to set up the handset, much like the same way that Android strongly encourages the use of a Google account. Application purchases will also be tied to this ID. The update mechanism, which has all but failed Microsoft in Windows Mobile thus far, looks to be well controlled this time around. For example, the Kin will release small updates over the air, while larger updates will require tethering and management through the Zune software on the PC. Microsoft will manage the process, not the manufacturer or carrier, though device or carrier specific customizations can be pushed through the same mechanism. Speaking of OEM customizations, the deck emphasizes just how tightly Redmond will be controlling them, IE’s default search engine can be changed, but everything else on the phone will go through Bing, for example. OEMs can add no more than six (or 60MB) worth of custom apps, and while custom home screen tiles can be added, none of the standard Microsoft ones can be changed or removed. It’s pretty old-fashioned, but considering how desperately these guys are in need of a fresh, different mobile strategy, it’s probably a good thing.