The Windows Phone 7 Review
by Anand Lal Shimpi & Brian Klug on October 20, 2010 7:00 PM EST- Posted in
- Smartphones
- Windows Phone 7
- Microsoft
- Mobile
OEM/Carrier Customization: One Part Apple, One Part Google
For the past couple of years we’ve had two options at the forefront of the smartphone race. If you want the ability to choose your own device, customize your OS and run virtually anything you want to: Android has you covered. If you want more of an appliance experience and don’t mind giving up freedom in hardware choice or OS customization, there’s always the iPhone. Apple will never sell iOS on non-Apple hardware, and until Android 3.0 Google won’t enforce a consistent UI across all partners. Microsoft falls smack in the middle. If you weren’t totally happy with either option, Windows Phone may be what you’ve been looking for.
The OS and user experience are pretty much off limits for carriers and OEMs to customize. Microsoft will not allow any custom skinning or replacement of default apps. While Android lets you switch out the virtual keyboard software, Microsoft takes a more Apple-like approach and instead delivers what it believes is the only keyboard software you will need. Microsoft wants all Windows Phones to look and feel the same from a UI standpoint, so custom UIs are out. Don’t expect to see HTC’s Sense or Samsung’s TouchWiz permeate Microsoft’s latest OS.
Even hardware specs are pretty well dictated by Microsoft. All first generation Windows Phone 7 devices must use a Qualcomm Snapdragon SoC with Adreno 200 GPU, they must feature at least a 5MP camera and an 800 x 480 screen. A physical keyboard may be optional but all must implement Microsoft’s virtual keyboard via a capacitive multitouch screen.
There are three buttons that must be present along the bottom of the face of any Windows Phone: Back, Start and Search. The buttons must be present in that order, avoiding the confusion of reordered buttons we sometimes see on Android devices. The type of button is up to the OEM to decide: either capacitive touch or physical buttons can be used.
At the top left of any Windows Phone there must be a volume rocker. The top right has to have a power/lock button. The lower right has to have a physical camera button capable of waking the phone up from sleep and putting it directly into the camera app. Microsoft views the smartphone as the replacement for the point and shoot camera and thus Windows Phone needs to be able to function just as quickly as a P&S. Finally, all Windows Phones must have a 3.5” stereo audio out jack and support for headsets with three button integration. These are headsets similar to what Apple ships with the iPhone with button(s) on the cable itself.
Microsoft wants OEMs to compete based on hardware design. Windows Phones can take any shape and size, but they must meet these basic requirements. It’s Microsoft’s way of saying: feel free to differentiate, but don’t ruin what we’ve built.
With this approach Microsoft hopes to avoid the mistakes Google has made with Android, where there’s an inconsistent user experience going from HTC to Samsung to Motorola Android phones. It’s almost as if Microsoft is taking Apple’s approach and simply letting everyone build iPhones.
The OEMs are understandably nervous of what Microsoft is proposing. From what I’ve heard, Google is putting a lot of pressure on its partners to remain pro-Google. That combined with Microsoft’s unproven track record in this new smartphone world resulted in many OEMs shipping very conservative designs for their first Windows Phones. Many of these designs are recycled from previous phones. The Samsung Focus is a lot like the Samsung Captivate, and the HTC HD7 is very similar to the HD2. If Windows Phone gets enough traction, then (and only then) will we see riskier designs from Microsoft’s partners. If you’re wondering why there aren’t any truly sexy WP7 phones out at launch it’s just a matter of OEMs wanting to see if Microsoft really has a chance before committing to a more impressive design.
There’s also no carrier exclusivity here (although I suspect the Apple/AT&T deal is close to being over at this point). Microsoft is launching first in the US with AT&T, however T-Mobile and Sprint phones are forthcoming. Verizon is curiously absent, but if you paid attention to my Google pressure line above it’s not too surprising.
125 Comments
View All Comments
wharris1 - Wednesday, October 20, 2010 - link
Web site is great; now I need to read articledeputc26 - Thursday, October 21, 2010 - link
Where are the actual load times (in seconds) for web pages? Synthetics never tell the whole picture... seems like you might be embarrassed for WP7 on this front ;)GoSharks - Wednesday, October 20, 2010 - link
Are there supposed to be images in this article?jimhsu - Wednesday, October 20, 2010 - link
Article seems to be half done as Anand makes a huge number of edits. Guess that's normal.SelesGames - Wednesday, October 20, 2010 - link
I see images just fine.Btw, I don't know whether any app reviews will be done, but for anyone who has access to a phone, check out some of our apps. Search for "Seles Games" to see all our apps, or check out any of the apps we have demoed here:
http://www.youtube.com/user/aemami99
Mumrik - Saturday, October 23, 2010 - link
So you decided to advertise in the Anandtech comments... Classy move.Termie - Wednesday, October 20, 2010 - link
The HTC Surround page seems to be missing, or at least it's not coming up when I click on the link to that page.Anand Lal Shimpi - Wednesday, October 20, 2010 - link
Images are incoming, please bare with us :)atmartens - Wednesday, October 20, 2010 - link
"please bare with us :)"Skinny dipping? Or just streaking?
Zstream - Wednesday, October 20, 2010 - link
Do you know what the talk time is for the LG? It's not showing on the graph.