(Push the Button)

(with apologies to Toffler for the title – Third Wave has other connotations these days)

In the early days of personal digital computing things were pretty wild.  After all it was the 70’s and California (where much of the [computing] action was going down) was probably a pretty sweet place to be.  Unfortunately, I only know this second-hand – my parents lived near the Morningstar Commune in Sebastapol.  I digress.  So, maybe it was the drugs, maybe it was the spirit of the time.  But, nevertheless, ideas were – flowing!

Among those ideas are just about everything that we currently use to interact with our computers.  Take a look at Brad Myers’ “A Brief History of Human Computer Interaction Technology” for a retrospective.  Eventually, the drugs wore off.  The experimental 70’s came to an end.

Time to get real and sell, sell, sell – enter the corporate 80’s.  The “Office of the Future” was first sold commercially in 1981 as the Xerox Star.  It used a desktop-metaphor to help make these alien computing devices called PCs comprehensible to the humans.  Yup, just like your desk… sorta.  And then this company you’ve probably never heard of came along and made a product called the Macintosh in 1984.

Ok, so that’s pretty much the entire history of personal computing.  Well, not quite.  There was this sorta major event in 1995 that we still haven’t really recovered from.  Windows 95 / AOL / Netscape brought the internet to the world.  But somewhat surprisingly personal computers didn’t change much.

While the PC operating system world hasn’t really changed, the rest of the industry certainly has.  For example, my new phone (a Palm Pre) is a powerful computer, is a powerful Linux-based operating system – and it is beautiful, fun, functional, and damn near an entirely desktop-metaphor-free computing experience.  And I get it.

Well, what about this UNIX and Linux thing they talk about on the TV?  Yeah well, remember that wild and crazy time in the 70’s?  Some of those guys were droppin’ ‘C’-tabs and the trip lasted right up until June 2002.  At that point, Linux began to have a fairly viable desktop-metaphor-based environment.  Just like the rest of the PC gang… sorta.  Don’t get me wrong though.  The people who brought us GNOME 2.0 were heroes and visionaries.  Only it was very, very, long overdue and ushered in a new set of challenges.  Seth Nickell discusses this very eloquently in his GNOME Journal opinion piece “Experimental Culture”.  Check it out.

So, what do we do now?  Will GNOME 3.0 be the beginning of our third age, where we move beyond the desktop-metaphor?  Will a new crop of heroes emerge?  So far, things are looking good.  We’re already seeing some great contributions and exciting new ideas from people who are thinking about and working on GNOME Shell.  People who just get it and know that often a great design is anything but conservative.  Interested?  Stop by and say hey.

Join irc.gnome.org:#gnome-shell to participate in daily discussions or get help with running, developing, or designing for the GNOME Shell.

–

PS. Many new technologies go through very similar growth stages before they realize their own “language” or establish their own idioms.  Somewhat canonical and well-studied examples include film, automobiles, and television that initially used metaphors of theater, carriage, and the hearth respectively.  I’d also suggest that it is very human: childhood (play), adolescence (mimicry), adulthood (expression).  There is a fourth age as well – but once again, I digress.

Risk

And then the day came,
when the risk
to remain tight
in a bud
was more painful
than the risk
it took
to Blossom.

– Anaïs Nin

For the last couple of weeks I’ve been working pretty much non-stop to pick up where we left off after the GNOME UX Hackfest and drive the GNOME Shell / 3.0 designs forward.

I’ve been approaching the problem in a way that, I like to think, is consistent with the very strong goal-oriented design heritage of Owen’s team at Red Hat.

No matter what design process you use (personally I like to blend Design Thinking with the OODA Loop) you really ought to carefully observe the environment and history of the problem – both the failures and partial successes, and perhaps most importantly empathize with the innocent victims of related “designs”.

I’ve posted to the wiki a selection of some of the material I’ve been reading.

If you are new to the subject, I highly recommend the first book listed, “Beyond the Desktop Metaphor: Designing Integrated Digital Work Environments.”  Which is basically a collection and summary of a number of the papers that I list below it – but it adds a lot of context that you may find helpful.

The papers are all really interesting.  I encourage you to read as many as you can.  Doing so will almost certainly help you understand some of the design decisions that will come later.  And with any luck motivate you to get involved!

I should also note that I haven’t made any attempt to categorize the papers.  I’ll leave it as an exercise for the reader to determine why.  Hint: read Lansdale.

Something I may have missed?  If you have any suggestions please leave a comment.  Thanks.