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.

Notifications Facebook Integration & the People Hub
Comments Locked

125 Comments

View All Comments

  • Crono - Thursday, October 21, 2010 - link

    A lot may not have been taken from the Kin One and Kin Two, but the square, multi page Start is the same concept that was implemented in the Kin phones.

    Looking forward to moving from my Kin One to the Surround. Microsoft is offering 3 months free Zune Pass for those who sign up to be notified about preorders.
  • heelo - Thursday, October 21, 2010 - link

    You might be the only owner of a Surround.

    That thing has a "value proposition" that I'm really struggling to relate to.
  • peter7921 - Thursday, October 21, 2010 - link

    I have to give recognition to Anandtech for another great review. I have been looking for a detailed review on WP7 and you guys delivered. Not only is it extremely informative but it's also very well written. I read through it all, not once feeling bored or skipping ahead.

    These types of articles are the reason Anandtech is my first source for all things tech!

    Keep up the great work guys!
  • Confusador - Thursday, October 21, 2010 - link

    OK, wow. I mean, even by Anandtech's unusually high standards that was intense. Just one thing I'm not clear on, though... am I reading this correctly?

    "WP7 calls presents its browser user agent as “Mozilla/4.0 ...""

    If that's correct we've come a long way from the days I had to have Firefox masquerade as IE to be effective.
  • Guspaz - Thursday, October 21, 2010 - link

    IE has *always* done this, including on the desktop. IE6 reports as as Mozilla/4.0 too. IE2 also did it (a different version of Mozilla, though). A quick search didn't turn up IE1 user agent strings, but I assume it also did.
  • Spivonious - Thursday, October 21, 2010 - link

    Remember back when IE was introduced, Netscape was king. Netscape is based on Mozilla. That's the only reason it's in there - so pages made for Netscape would load correctly in IE.
  • arturnowp - Thursday, October 21, 2010 - link

    IT seems strange that WP7 cannot pass test, has very slow JavaScript engine but still pages are fluid and displayed porperly. Maybe Microsoft renders pages remotely and serves them to the phne?
  • UCLAPat - Thursday, October 21, 2010 - link

    Wow! After reading this review, it makes all the other reviews look like previews. Definitely going to be considering WP7 when it's time to upgrade my phone. Still have time to burn on my current 2 year contract. By the time it's up, LTE should be up and running and Verizon will probably have a WP7 device for us to consider as well.
    Apps will come. But they're not a huge part of my life anyway. I want a rock-solid core experience for a phone. A smartphone has to nail the basic experiences first (calls, messaging, calendar, etc). I never liked the main screen completely filled with app icons. That reminded me too much of my old desktop computer before I cleaned up the desktop.
  • Belard - Thursday, October 21, 2010 - link

    But very detailed... tells us pretty much everything anyone can ask.

    Thanks...

    While I'm not exactly PRO-MS... its good to see good design.
    I still like Google's a bit more and its shortcoming are easy to spot. Hopefully Android 3.0 will improve on its weaknesses.

    The icon / naming is well thought out and is used by others... including Apple, but not on a phone.
  • silverblue - Thursday, October 21, 2010 - link

    "...displays up to 8 tiles of people you’ve either recently communicated with or whose profiles you’ve viewed/stalked."

    LOL.

Log in

Don't have an account? Sign up now