Blog Post RSS ?

Blogs » JavaScript & CSS » AllMusicGuide: A Web Standards case study
 

AllMusicGuide: A Web Standards case study

by Simon Willison

Yesterday saw the launch of a new design for All Music Guide, the music world’s answer to the Internet Movie Database. AMG has been around since 1995 and has grown to be by far the largest and most useful music resource on the web. It’s a classic example of good content trumping poor design: you will find few people who loved the old design, but it was good enough to provide access to the content, which for most people is good enough period.

I’m calling this entry a case study, because AMG’s new design is a case study in how not to handle a redesign in 2004. Until a few hours ago, the site carried a prominent “This site optimised for Internet Explorer 5.5+ for Windows” message when viewed in alternative browsers (they appear to have removed it now, but the browsers I’ve tested it in still show prominent visual glitches). One of the greatest complaints with the old site was that most of the links required JavaScript to function – a problem so great that a friend of mine wrote a bookmarklet to unsuckify them! Amazingly, these links still feature on the new site.

In fact, the most prominent new “feature” is a flashy navigation widget in the header, implemented in Flash. Navigation links sit in a pretty 3D treee structure and rotate when touched by the mouse. At first glance, it looks like it might be something ultra cool like Music Plasma. Then you realise that it’s the same six links every time, and in fact it’s the exact kind of navigation you would expect to find on some pretentious “cool” site circa 1998. Anyone remember Boo.com?

To their credit, AMG responded to the flood of negative feedback from the relaunch by putting up a page excusing some of the site’s issues (it’s 404ing now – you can read the full text here instead). Here’s my favourite part:

Optimizing a site of allmusic’s complexity and size for all browsers and operating systems is no small feat. This isn’t a simple “brochure-ware” site of static pages. While we would love to optimize the AMG sites for all browsers and all operating systems, we simply don’t have the necessary resources to do so. Despite some users flattering comparison of our site with that of Google, Amazon and Yahoo!, we are a small company with limited resources. So, we had to pick the most widely used browser by our users (over 87%) to optimize the site for and then work on compatibility issues with the other major browsers as we go forward.

Back in the 20th century, this kind of argument would have been excusable. Today, it’s a joke. Aside from the usual arguments for building for standards rather than targetting one browser, one statistic stands out like a sore thumb: they’re deliberately ignoring 13% of their readership! That’s simply insane – on a site with a million page unique visitors a month (and you can bet AMG gets a lot more than that) that means sticking a finger up at 130,000 people!

Thankfully they claim to be working towards fixes for problems in other browsers. I can’t help but think that if only they’d read the little book of orange, or SitePoint’s HTML Utopia, they would have ended up with a lot less bruises.

Fore more commentary, see Waxy.org here and here.

Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Ping.fm
  • Twitthis

Related posts:

  1. Case Study: The difference a web design firm can make
  2. Case study part III
  3. News Wire: The Business Case for Web Standards
  4. Case Study of Startup: Online Subscription-Based Programs
  5. Let’s do a case study comparing five money-making websites

This post has 7 responses so far

Sponsored Links