Another Nokia Flop: The New Music Store

I got excited when I received an email from Nokia announcing the new Nokia Music Store. OK, I didn’t get excited at all, Nokia has been sending me promises of good service for a long time. Without success.

I have been an unhappy Nokia E61 user for a year or so (they are still selling that model). The interface is horrible and the whole telephone is very slow. I managed to load music into my phone only once, I never did it again. OK, OK, Nokia is the number one phone maker but that might be because they are making a good business in the third world selling cheap phones.

The new Music Store

Designing with standards and for everybody should be something that customers and designers themselves should fight for. When I tried to see the new Nokia Music Store a beautiful "Unsupported Browser" message was displayed. GREAT. The only system combination that works with it is the Windows-Internet Explorer one.    

"Nokia Music does not currently support the Mozilla Firefox (Mac OS X) browser on your operating system"

Nokia Music Store Screenshot

My point

This is not what customers want, specially here in Europe where Firefox has a 30% market share, in some EU countries with market share higher then 40% (as reported by Ars Technica in January 2008). In a perfect world we would design for standard browsers, but the world is not perfect. Making a service available for different browsers is something that it’s going to affect the usability of it.

We are not talking about a startup, we are talking a huge company. So why not spending some more money to make products available for all?

Careless Design From Google and Apple?

Today two of my favorite companies decided to tell me how little they care about me and other customers. In my opinion, not bothering users with useless information is highly related to the general design of a website and usability. Keep in mind that a good website should make users’ life easier trying to make processes simple and short and without disturbing users when they are doing other activities. In another example of how design, usability and marketing mix each other I will show you the emails I got from Google and Apple. 

The first mail came from Google, it was actually coming from "noreplay" and the subject was "New Optional Benchmarking Feature Available in Google Analytics". That was it, no link to get farther information, no content in the email. At all. Then I went to my Analytics account, there was an item for the new feature in the menu but nothing inside. OK, this could be a new feature that is coming but the way they announced it was a little bit careless (maybe arrogant?).

Don’t get me wrong, I do really admire Google. They usually make good marketing, they design good processes and they care about usability. And that’s why the following email makes me angry:

Google Mail Example

 

The second email making me angry today comes from the Apple iTunes Store (Germany). Yeah, I love my iPod and I love Apple products but lets have a look at the following email. Apple decided today that they wanted to send me spam, OK, it was not unsolicited email because I signed up for the newsletter, but the information on it was as useless and aggressive as spam could be.

The "iTunes alert me" newsletter should recommend me music I might like. Today, Apple sent me an email offering me an album I already have, one that I listen to very often and one that has been released 4 years ago. I am sure Apple already knows all that, so why bothering me with so useless information?

iTunes Alert Me Mail Example

 

Designing a Checkout Process: 8 Rules, 7 Examples

Users usually need to be guided in order to finish a task. Designing a process funnel right will keep your visitors in the process and will make them finish the task they want to commit. This tasks could be as important as the Checkout Process, I will focus on this particular one.

Here there are 8 tips to improve usability during a checkout process:

1. Keep it short. If the process has too many steps users will be scared and will probably leave without finishing it.

2. Keep it long. If the process is too short, well, it’s not a process. Sometimes it’s better to divide tasks that could be presented in one page into smaller steps. Keeping every step short gives a sense of simplicity.

3. Progress bar. It is very important for the user to have information about how long the process it will be. Maybe your process is not that long, but if you don’t show that to the user, she might decide that is not worth enough to finish with it.

4. Back button. Give users the possibility to go backwards to check what they filled in the previous step.

5. Unnecessary steps. Give users the chance to skip steps they don’t need (e.g. the Amazon "Gift-Wrap" step).

6. Online help. Use floating windows or other online help to solve problems without taking users out of the process. Remember not to distract users.

7. Next step button. Make this button or link highly visible.

8. Make clear that the process is finished, if not you could have a lot of users contacting your customer service, which could become extremely expensive.

I would like to show you 7 examples I took from different websites. I focus on the information the user should get to make important decisions just before or during a checkout process funnel:

 

Amazon’s design shows a shopping cart that seems to be rolling through the whole process. Users know what to expect as the steps have clear names, displayed from the beginning.

Amazon Process Funel Design

 

The Starbucks Store shows very clear steps and the name of each one in a prominent position (e.g. Sign In). Some usability tests show that users might prefer a longer process with smaller steps. Good naming for each step should represent the user mental model, something like what the people are used to when they buy off-line.

Starbucks Checkout Process Design

 

Buy.com has a sleek checkout process status information design. I like the red arrow clearly showing the actual step. Steps are clearly indicated and the end is also coherently indicated with an "Order Complete".

Buy.com Checkout Process Design 

 

Toy"R"Us checkout process is not going to prevent users to finish the purchase but it could create some confusion. Notice that the difference between the step "Addresses" and "Shipping" could be misunderstood and users have to go inside the step and read instructions in order to understand what are they about. Using "payments", the plural form, is not standard and could add even more worries.

Toyrus Checkout Process Design

 

The beginning of the checkout process at Petco adds some extra complexity. They require an extra decision to be made by the user: "check out", "Google Checkout" or "International Checkout"… I would avoid so many options.

Petco Checkout Process Design

 

Google Checkout has a special design. Coming from an online music store I landed at the Google Checkout page, at this point is not possible to delete products or change quantities. The whole information is displayed in a single page, including product to be paid, payment information, shipping address and term of service. Maybe the aim of this was to try to make the process short but in my opinion this design fires back and scare people, making users think that the whole form is too long (this happens to the first-time Google Checkout users).

Google Checkout Process Design

 

The PayPal process does not offer any information about how long the process it will be.

Paypal Checkout Process Design

 

At the end, once the user logins, the process is very short (if the user has an account and bought before with Paypal). Unfortunately, before the login the user could not guess how long the process could be. Something like

1. Login, 2. Confirm and Finish

in the login page wold give users the feeling that the process is really short and easy.

Paypal Process Funel Design