O Danny Blog Entries  

SXSW 2007: The Death of the Desktop

Aza Raskin (Humanized)

Not using his computer with the desktop running. So then how do I actually get to applications?

There are certain fundamental truths about how people work: it's called cognetics. And they apply to interfaces. If you design against human frailties, your interface won't work very well.

Cognetics: the ergonomics of the brain. Magical number 7 rule. Can't actively think about more than one thing at a time. Etc.

If you don't do this, you are asking users to push two buttons ten feet apart.

Forgotten Tools:
GOMs modeling: how long it takes the average user to use an interface.
Information efficiency: how much information you put in vs. what is minimally needed.

The death of the desktop is near. Why? Is this a good thing?

What is an interface? The way that you accomplish tasks with a product--what you do and how it responds. The interface is the product (to the user). A beautiful back-end isn't useful for people without the interface. Don't focus on the technology, not the user.

Keep simple things simple. A litmus test: how long the manual is. If it is difficult to explain how to use your interface, there is something wrong. When you set out to make an interface, write the manual first.

The problem is that applications are like isolated cities. Computing models could be different. There is a lot of overlap (waste) between applications. We get a lot of system bloat this way. You have to keep learning basic applications again and again. This is a fundamental problem with applications--they want to hoard functionality.

What does an interface do?
Create content (typing)
Navigate content
Select content
Transform content
(Share content?)

When designing, always return to these fundamental building blocks.

Raskin's Rules of Interfaces:
1. An interface shall not harm your content or through inaction allow your content to come to harm.
2. An interface shall not waste your time or require you to do more work than is strictly necessary.
3. An interface shall not allow itself to get into a state where it cannot manipulate content.

Content is Everything. You always acting upon some content.

What dooms the desktop? It's not about content. The desktop is a flawed metaphor to start with.

What does a desktop do?
Let's you get your computer into state where you can enter content. Let's you categorize your content. Let's you navigate your content.

There are better, faster, more humane ways. The web is treasure trove of examples.

Language has an untapped power. This is the future. It lets you describe things very quickly and very succinctly. If you can just type what you want, it works better.

Command line interfaces: great way to enter commands. URL bar can be a form of a command line.

The death of forced hierarchy. Tags don't force a hierarchy on users. Desktop needs to learn this lesson. We don't need to think the way our hard drive does. Going up and down trees isn't good. You also just need a really good search.

Navigation: Let content be content. Let search be search. Let 2D content be 2D content. Let the user's structure be.

The web as a maze: you go through a door and you can't see where you came from.

People don't work well in 3D, so don't force them too.

The desktop of the future is a zooming interface where you could put content wherever you want (not forced). Things are related geographically. It's visceral. Easy to navigate.

The desktop is doomed. Why the stagnation? The toolkit straightjacket. Programmers are writing for users, but don't want to interact with users. The people who write toolkits are one step removed from that. The system makes making mediocre interfaces easy. This is why the web matters. But it is dangerous to make the web like the desktop. We're free to make something better. And you cannot be better without being different. We have a unique opportunity to step away from the desktop. We can invent new paradigms.

How can we overcome applications? Services and Universal Access Interface. How do we get all these Ajax apps to work together?

Design the big picture: think above the apps.

Originally posted at Monday, March 12, 2007 | Comments (2) | Trackback (0)

 
Previous Entry
SXSW 2007: Mobile Application Design Challenges and Tips
Panel: Kevin Cheng (Yahoo!), Matt Jones (Nokia), Simon King (Yahoo! Research Berkeley), John Poisson (Tiny Pictures Inc/RADAR.NET), Anita Wilhelm (Caterpillar Mobile). MJ: User research and prototyping for mobile is incredibly important and difficult. The mobile experience is difference when... ...

Recent Entries
New Book: Designing Gestural Interfaces

An Interaction Designer's Thanksgiving

Missing Britpop

Presentation: Gaming the Web: Using the Structure of Games to Design Better Web Apps

Connecting07: Rethinking Product Design: Why We Can't Wait

Connecting07: Medical Device Design: 10 Things You Need to Know

Connecting07: Brand, Design, and the Brain

An Open Letter to the Producers of the new Bionic Woman

Review: The Reflective Practitioner (Part IV)

Presentations on Slideshare

Archives
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
 
 
  O Danny Boy is About Me, Dan Saffer, and has my Portfolio, Resumé, Blog, and some Extras. It also has the blog I kept of my graduate studies and ways to Contact Me.  
 
 
 
  Blog RSS Feeds
Blog Excerpts
Full Entries
Design Entries Only
Atom Feed
 
 
 
 
  Search