UI&us is about User Interface Design, User Experience design and the cognitive psychology behind design in general. It's written by Keith Lang, co-founder of Skitch; now a part of Evernote.  His views and opinions are his own and do not represent in any way the views or opinions of any company. 

Navigation
Categories
External Articles

Entries in time (2)

Sunday
Mar082009

Time as Interface Element

Time. Software is increasingly focussed on helping us understand and manage it. For a great example, see the unreleased Palm Pre; it's diary view shows spare time in a beautifully simple 'crumpled' concertina UI. So, how do other UIs handle time?

Temporal Interfaces
Lukas Mathis' blog, ignore the code, recently covered some mockups of current, and possible temporal interfaces. Including one from this blog :-) One of the examples showed how the file 'list view' could better serve temporal thinking.

My Take
Lukas' approach inspired some thoughts of my own on the problem of representing time visully. I've put Lukas' original example topmost with my iterations below; if an item is separated in time from the other items — and since we seem to think about time in a spatial way, how could we show this spatially? (click for fullsize)

I like the 3rd, 'peaks' iteration as it reminds me of something I saw in Norway — a 'Give Way' line evoking a steep slope, big bear teeth, or sharp spikes. "Slow Down!" It seems a nice visual metaphor for time.

How else could time be shown spatially in this context?

Another conversation for another day: missing UI metaphors for working with (as opposed to simply understanding) elements which travel through time. We can tell it's a problem because people are going to the effort of devising complex workarounds. For example, the 37signals crowd has a nifty solution for throwing emails forward in time.


Click to read more ...

Thursday
Feb052009

Amazon: Milliseconds means Money

John Gruber resurfaces interesting stuff:

A Google researcher saw a 1/2 second page delay cause a 20% drop in traffic and revenue.

On this post, an Amazon.com employee concurred; In A/B tests, we tried delaying the page in increments of 100 milliseconds and found that even very small delays would result in substantial and costly drops in revenue.

Based on the above quote let's simplify and say revenue drops off linearly with the delay of the appearance of page, with a delta based on the Google research. Taking into account Amazon.com's Revenue for 2007 was USD $14.835 Billion…

500ms = 20% loss = USD$ 2.967 Billion loss 100ms = 4% loss = USD$ 593,400,000 1ms = 0.04% loss = USD$ 5,934,000

By this logic, every extra millisecond the page takes to load costs Amazon.com almost six million lost dollars in revenue.

(btw, I know UI&us is currently loading slowly and realize the hypocrisy! I'm working on this problem with someone already. Any tips are welcome.)


Click to read more ...