The use of design metaphors was one of the first things Web designers explored in the mid-90’s on the early commercial Web sites. A Southwest Airlines site used the airport ticket counter as a design metaphor, for example, and the mall metaphor itself was widely used by early eCommerce developers.
I did it, too. I designed a site for the RI Teacher’s union that used a ruled-paper background, and the homepage navigation was designed to look like stuff that was left on top of a notebook. I even had a coffee ring on there.
In the mid-90’s , most of the first Web designers were coming over from print. As Marshall Mcluhan pointed out, we tend to use a new medium the way we used the old one, so a lot of early Web design was driven by what designers knew from print, including the use of metaphor.
While you can make the argument, as Brian has, that a design metaphor can be used to make people feel comfortable with a user experience by basing it on something they already know, there are good reasons why Southwest and the RI Teachers no longer have metaphor-driven Web site designs.
If you really want to get into this, check out Jacob Nielsen’s book Designing Web Usability (where he dissects the Southwest ticket counter site), but it boils down to this: The Web has essentially become an operating system, and successful Web sites are basically apps that run on it. The reason your users come to your site is to complete a task using your app.
That means that Web design has morphed from print-based design principles to software user interface design principles, and the problem with metaphors in UI design is that they don’t scale well as you add functions to your app to enhance your audience’s ability to complete primary and related tasks.
You end up stretching the metaphor until it breaks, and something that started off giving you a fresh and interesting way to look at a hierarchy of information becomes a drag on your ability to extend that hierarchy. Already on Shawna’s site, you have to Read more