Another conference/seminar/meeting, another reference to netflix.com.
Many web eons ago, back in 2001 or so, amazon.com was brought up in every conversation of “what a website should look like.” Build tabs! Tabs are neat. They’re like file folders. People understand them. Just keep adding more tabs as you get or define new content areas. If you have more tabs than fit across one row? No problem! Add a second row. And a third. Amazon continued with the tab metaphor to the point where, because of the multiple rows of tabs, the structure became increasingly clumsy. So at some point the amazon.com designers scaled back to one row of tabs and had one of the tabs show, on hover, a big list of all categories. This felt like progress. Recently amazon.com was reborn with no tabs at all. This felt like an important moment in the trajectory of designing for the web.
In any case, my web-oriented discussions in meetings in 2001 focused on “What should a website look like? What is good navigation? What is amazon.com doing, and how can do learn from it?”
Fast forward, sort of, to a couple years later. Thanks to the efforts of Tantek and other smart people, the possibilities for page structuring using CSS were beginning to be understood, and navigation issues took the backseat to convincing Powers That Be that CSS was worth ripping apart and reassembling many thousands (in my case) of HTML documents.
Around this time a showy and fabulous grouping of sites known as csszengarden.com came on the scene. The CSS Zen Garden project was a chance for designers and CSS aficionados to prove to the world that CSS sites could be even more lovely than table layouts. From this point, in every meeting, in every discussion, in every utterance of web strategy-ness there came the inevitable “look at csszengarden.com! Look at what we can do with CSS!”
Somewhere along the way we, the CSS converts, won the battle over tabled layouts. CSS and XHTML are now standard. I’m not sure what role csszengarden.com played in this, but in my experience it was certainly significant in helping convince designers and business managers that CSS could help make stuff beautiful (as well as, of course, more easily maintainable). This started around 2002 and lasted until around 2005.
The discussion, particularly around 2002-03, was centered around “How should we build websites? What can we do with CSS?”
Since that time, web interactions have gotten more complicated and more important than ever for business operations — and the discussion has shifted to be more about ROI and customer experience. My conversations are less about how websites should be built, and more about what they should do.
And now, people bring up netflix.com to me on an almost daily basis, as the site does an exemplary job of explaining a complicated business process at the same time as offering a compelling and easy sign-up process; we are all thinking about the user experience in ways that we weren’t before.
I would say this is progress.
And I would say that the luster of the netflix.com experience will wear off fast. Until you sign up and provide personal information, the experience feels flat and disconnected. I predict that the next “brought up in every meeting” site will provide a rich and contextual experience before the sign up process is completed. (Maybe along the lines of upcoming.org?)
