(Seriously, who names these products? Microsoft even lampooned themselves on their ludicrously overwrought names with their “Microsoft designs the iPod packaging” video, and yet they keep doing it!)
So, Windows Phone 7 Series. Phones. Yeah. I’ma just call it WP7 for short.
I have to give MS some serious kudos on this, actually. Despite the completely atrocious design-by-committee branding in the name of the product, they’ve taken a pretty damn bold step with WP7. Zero backwards compatibility with Windows Mobile 6.5 and earlier, strong emphasis on the retail consumer (to the point of tying media sync to the Zune software platform… will be interesting to see how this device plays out in corporate IT, given the holy hell that was raised about iTunes), minimal multitasking, and a complete and utter departure from the UI of not only Windows Mobile, but pretty much every other smartphone out there.
Conceptually, there is a great deal about WP7 to like, and I think Microsoft can easily position themselves to become a serious contender again in the mobile market that’s basically left them behind over the last 2.5 years (3.5 by the time Wp7 comes out, actually) since the release of the iPhone. Things like the live-updating, rich-content home screen tiles, the broad and deep integration with social networks like Facebook, and the concept- or task-oriented nature of the device’s software, rather than a strictly application-based usage model are things that are very interesting to me, and it’s good to see Microsoft intentionally differentiate itself from the rest of the market in such substantive ways. I think Windows Phone will live or die on this differentiation, rather than its branding as a Windows device (though as always, such branding is probably more beneficial than not).
I’m more ambivalent about the actual execution of the concepts put forth in the WP7 user experience though. The entire platform is built on the Zune HD interface model, and there’s no possibility of carriers overriding this interface as there was in the past with Windows Mobile (something I’m sure HTC is less than 100% pleased about), so I really, really hope you like the way the Zune HD behaves. I, personally, don’t.
Maybe it’s because I get a little OCD with my digital interfaces (having an uneven number of apps on one screen of my iPod is enough to annoy me until I “fix it”, even at the expense of my application grouping methodology… and don’t even get me started on the elaborate and complex maze of folders I use on the Mac to store everything), but the Zune HD’s UI just strikes me as lazily executed because of all the overflowing text and wasted space in many of the screens. I know large, thin, sans-serif type and bold, flat colors are “in vogue” right now, and they do make the device look very stylish, but I don’t think “hip” and “useful” necessarily converge all that often (I mean, have you seen Lady Gaga’s wardrobe?), and I kind of worry that MS is painting themselves into a corner with this UI being so closely tied to the branding of the platform. Chucker argued back at me that Apple’s Aqua interface has made considerable evolutions since its introduction in 2001 2000 with super-glossy buttons and translucent pinstripes, and I agree that Apple has done a very good job with keeping their OS’s interface fairly fresh and in-line with current trends. However, I think the changes Apple has made to Aqua in the past decade are largely superficial: tweaking gradients and transparencies more than anything else. At its core, Aqua is still very much the same as it was 10 years ago in terms of its appearance and behavior. The Zune UI, I think, faces a larger uphill battle against trendiness because so much of its UI is fundamentally not just trendy-looking, but trendy-feeling (again, overflowing text, large monochromatic iconography, whizzy spinny animations). Revamping that UI to keep up with the times without seriously altering the behavioral characteristics of the UI on a fairly fundamental level will probably be much more difficult for Microsoft than it has been for Apple, though I do wish them the best of luck.
My other gripe is related to the first, and it’s got to do with the design of the “hub” applications. I’m not personally a huge fan of the broad two-dimensional navigation in apps like Windows Media Center, because half the time a number of my options are invisible and inaccessible. Similarly, with the Zune UI, it can be hard to tell what all can be done in an application hub without first exploring it fully, which can take some time. This secretive UI concept also requires the user to maintain a much larger conceptual map of the application, as well as the navigational requirements needed to reach various far-flung regions, which strikes me as far more complex than the model which Apple has adopted for the iPhone. It’s bound to be a great interface for chic geeks, because Microsoft is pretty good at building interfaces that geeks and tech enthusiasts feel very comfortable with. I just wonder if the breadth of the navigational capabilities (and requirements) for some of the task hubs in WP7 will be off-putting to people who are less comfortable with digital devices.
As a furtherance to this point, I think Microsoft has misunderstood the utility of animation in a user interface. The WP7 animations are very slick, very intricate, and very dimensional, but they do very little to aid the user in visually navigating through the device’s software. Tapping a tile on the home screen causes the tile to angle away from your finger (which is a nice touch, assuming it actually responds contextually to where you’re pushing on it), but then everything spins off-screen and new content whizzes in seemingly from nowhere. There’s no real “physical” connection between these two layers of the interface the way there is when navigating through the iPhone. Tapping an application icon causes the program to “float up” to the surface, with the home screen UI proceeding out of the field of view. Movement within the application itself is generally very physical, both vertically (with inertial scrolling) and horizontally (with sliding displays). Exiting an application causes it to recede into the background, and the home screen UI falls back into place. These animations are very basic compared to those in WP7, but they also give the device a more physical and connected feel, whereas the WP7 animations just seem to be there because “everybody likes animation in their UI these days”.
I realize I’m doing a lot of complaining about a device which I said at the beginning of this post was a very good idea. The reason is, I think that it is a very good idea, just that the execution of that idea doesn’t fit my personal tastes.
I would love to see some of the more dynamic capabilities of WP7 come to the iPhone, and I think Apple should focus more on providing platforms for developers to build into, rather than just an operating system to build on top of. For example, the Photos application on the iPhone is very basic, and if you want to get photos from Facebook, Flickr, or MobileMe, you have to go into different applications to access them. Even the Apple TV does this better, with a Photos “category” where you can move between services with comparative ease. Better than even that model, though, is WP7’s, where photos just show up from wherever they’re posted, all collected in one place.
Similarly, the People hub is another great idea, which ideally third parties can build into to expand its functionality without adding full-blown applications to the system. Consolidating Contacts, Twitter, Facebook, etc. into one place is a really cool concept. I don’t think it would work quite as well for geeky folks who have multiple Twitter accounts (unless the UI got really creative and potentially overly-complex), but for the average Joe who may have only just figured out what Twitter even is, it’s a very slick implementation.
I also like the ability to pin pretty much anything to the home screen, from hubs to applications to individual items in a hub (like a person or an album). It gives the home screen much more utility for people than a collection of icons with numeric badges on them.
I think a lot of the initial development for WP7 is going to be oriented towards expanding the functionality of these hubs through plugin-style programs, rather than strictly fully-fledged application-based development. Given that the platform will also run whatever new applications developers create, it will be interesting to see how these two branches of functionality compliment or conflict with each other going forward. I suspect WP7 apps will be held to an even higher standard than iPhone apps because of the increased capacity for integration with the various content hubs, as well as the obviously unique and distinctive Zune-like UI. I just hope Windows Mobile developers are up to the considerable challenge after the past decade-plus reign of Windows Mobile’s often atrociously-designed and now-archaic-looking UI.
I’d also be interested in seeing what exactly Microsoft decides to do with the Zune from here out. Given that the Zune and WP7 share a pretty obvious commonality in their UI department, I wonder if they’re both running the same basic OS, with considerable efforts being made to expand its capabilities for the phone. If that’s the case, I wonder if Microsoft will attempt to do with the Zune HD what Apple has done with the iPod Touch: create a gateway product with a lower barrier-to-entry that people can use and get used to without the risk or expense of a phone contract or data plan. If they do, it will definitely be worth keeping an eye on, because Microsoft always plays to win, and while their efforts thus far in the MP3 player market have been pretty dismal at gaining any traction, coupling the Zune HD with a completely overhauled Windows Mobile Phone 7 to create a new Microsoft-controlled mobile computing platform could start driving greater adoption of both devices.
One last thing that wasn’t discussed at the reveal, is whether updates for the OS will be pushed to all users, either free or for a minor fee. This is something that the iPhone platform does pretty consistently better than anyone else, so hopefully Microsoft is learning a lesson from Apple and pressuring carriers and handset makers to allow OS upgrades without making people buy a new phone or resort to tech-nerd solutions like custom boot ROMs.
It will definitely be interesting to see where this goes from here. Unfortunately, I think the biggest problem Microsoft has now is that they’ve tipped their hand a full 8-10 months before their first product will hit store shelves, which gives the competition (especially the whenever-we-feel-like-updating-it Android platform) a considerable head start on getting their copy machines running.
Update: Chucker tells me I’m wrong about the intro date for Aqua being 2001. While I was going off of OS X’s general availability, it was demoed much earlier.