A better life with your iPhone.

RSS   Advertise with us ↗

Discover. Download. Do more.

iPhoneDigg: what an early mobile interface chose to leave out

David Cann’s 2007 Digg experiment illustrates the shift from fitting a desktop site onto a phone to organizing a task around touch.

Original photo illustration for iPhoneDigg: what an early mobile interface chose to leave out

iPhoneDigg was one of the interface experiments appearing before the first iPhone reached customers. June 2007 coverage attributes it to David Cann, while another contemporary report describes a Digg API interface arranged for the phone. The historical interest is in the adaptation: a busy news website was being reconsidered as a touch-oriented experience.

Begin with the next decision

A reader encountering a list of stories usually needs to decide which one to open. Headline, source and a little context support that decision. Everything else competes for limited space. On a small display, reducing clutter can change not just appearance but the order in which a person understands the page.

After opening a story, the next useful actions differ: read it, reach the original publisher, return to the list or share the reference. Treating those as separate stages is often clearer than surrounding every headline with the full set of possible controls.

The browser was the application platform

Apple’s original web-application announcement explains the setting in which these experiments appeared. Developers were exploring how web services could inhabit the new screen. An interface demonstration from that period should not be mistaken for a currently supported native app or an official Digg release.

A useful exercise for evaluating mobile news

Choose one article in a news tool you use today. Notice how many steps it takes to identify the publisher, open the original story and return to your place. Then repeat with a second story. The sequence will reveal more about everyday usability than a screenshot alone.

iPhoneDigg’s lasting relevance is this attention to the reading path. A compact interface succeeds when it keeps the next useful action obvious while preserving enough context to understand what you are reading.