Zune 80

Last but certainly not least we have Microsoft's second-generation Zune, the Zune 80. If the iPod Classic is the old guard and the iPod Touch the new guard, then the Zune is the missing link, as its feature set includes items from both generations of products, with interesting results.

As the successor to the original Zune (30) which was developed prior to the Touch, the Zune 80 is best described as an attempt to build a bigger, better iPod Classic; AKA the proverbial iPod killer. The original Zune launched with fairly tepid reviews thanks to a combination of poor design choices with both the hardware and the software. Since then Microsoft has gone back to the drawing board and heavily revised the Zune's hardware for the Zune 80, and taken out many of the kinks in the Zune software, which has also been pushed out to the original Zune as an update. The result is that their second generation Zune is immediately a much stronger contender than the original Zune was.

At $249 for the Zune 80, the Zune 80 is clearly targeted against the 80GB iPod Classic which retails at the same price and features the same 80GB 1.8" hard drive. Microsoft seems content to leave Apple alone at the $349 price point for the 160GB iPod Classic.

One of the biggest complaints with the original Zune was the controls, and that's where we'll start. The original Zune used a d-pad in the shape of a circle along with buttons on the left and right sides, something that would seem to be more at home on a Windows Mobile PDA than a MP3 player. The d-pad's successor in the Zune 80 is a touch-sensitive pad (the Zune Pad) in the shape of a squircle. Notably, the Zune Pad is only a single button, emulating the previous Zune's d-pad by reading the location of the thumb when the Zune Pad is pressed.

On the whole the Zune Pad is a mixed bag. The lack of touch controls on the original Zune were a massive mistake and this makes up for it greatly, as it's now far easier to quickly navigate through lists thanks to the ability to flick your finger along the Zune Pad to launch the list up or down. The biggest shortcoming in its design however is the Zune Pad just isn't very accurate. Because the Zune Pad uses touch loaction to figure out what d-pad action it should be emulating (or if it should be emulating a centered button press), we continue to have periodic issues accidentally scrolling up/down as we press the button because the Zune Pad reads our thumb actions as a flick while we're pressing the button. Through a month's practice we've learned how to better work with the Zune Pad to try to avoid such accidents, but we haven't been able to stop them completely. This particularly manifests itself during blind navigation, making that task harder than it should be.

Less significant is the fact that Zune Pad is hard to get a read on in terms of sensitivity; every now and then the Zune Pad is reading small motions as bigger than they are meant to be. Much of this has to do with the fact that the Zune Pad is fairly small (1" diameter) and requires repeated motions to use, so the device has brief 1" motions to decide what's going on. In all fairness to Microsoft, this is a case where they're between a rock and a hard place with what Apple has done. The iPod scroll wheel is simply a fantastic design, it's very comfortable and easy to use, with no significant problems in our opinion and none of the issues we've had with the Zune Pad. But we believe Microsoft can't outright copy the scroll wheel both because Apple's legal team probably won't let the idea go without a fight and because there's a certain level of harm that would come to Microsoft's reputation if it was such an obvious copy.

So what we get is the Zune Pad, to the detriment of the Zune 80. Don't get us wrong, it's not terrible (if you want terrible ask us about a Rio, any of them), it's just not great either; it's better than the first Zune and still not as good as the competition. Ultimately it's not possible to avoid fighting with the Zune Pad at least once, which is a tough sell in the iPod age. We should note that you can turn the touch-sensitive features of the Zune Pad off, which would solve some of our problems, but then we'd just be back to a d-pad.

Moving on, we come to the UI of the Zune. In all honesty we don't have much to say about the UI because we're largely content with it. Its anti-iPod design is rather obvious at times, starting with the white-on-black design compared to the iPod's black-on-white design, but at the end of the day it accomplishes the same things and works out rather well. Hierarchies are very solid designs for a MP3 player interface, and this is what Microsoft sticks to. If you've used any other MP3 player then you're not going to immediately know where everything is, but once you've used one hierarchical design you've basically used them all and will quickly adapt to the Zune.

The only thing keeping us from calling the Zune UI a draw with the iPod Classic's (it's basically incomparable to the Touch) are two nagging issues with it that we're having. First is a matter of design, Microsoft decided to shorten the hierarchy some by making song groupings a horizontal list across the top with the elements appearing below, skipping the need to actually traverse deeper. In practice this saves a short amount of time traversing the UI, but it also has the side effect of not making all of the groupings visible at once. What are the grouping methods and how many clicks/flicks do we need to make to get to the one we want? Because they're not all on the screen at once, you can't tell without going through them all. It's only a problem for new users, but it's a problem none the less.

The other issue we have is with the responsiveness of the UI. Most of the time it's fast, but not always; certain actions such as traversing through the song grouping methods too quickly will result in a UI that feels sluggish - never slow but sluggish. It's not enough to significantly impact the usability of the Zune, but it is enough to be annoying. Who ever heard of a MP3 player being sluggish? It just shouldn't be happening.

ncG1vNJzZmivp6x7orrAp5utnZOde6S7zGiKoaenZJavsMSxZmtsYmiMpJzAoJx2bFaWua2JpZqjrJ1WqLyzwJxpXamZl5qKdnLSpaygdQ%3D%3D