For some time now, many have followed their friends and interests online. Since people tend to publish in different places, subscribing via an RSS feed at least allows us to not have to go to their website to watch/view/read their content, but many sources make for an unwieldy list.
Google Reader’s endless (continously loading) page makes it a bit easier to churn through all those newsfeeds. When you get to the bottom of the page, items are dynamically added to the list so you can keep on scrolling. Usability-wise, this tweak increases the users’ efficiency.
Even if you are using Google Reader or a similar tool, you’re still dealing with multiple silos of content. Chugging down to the bottom of one writer’s pile leads to no other reward than having to start digging through the next pile. In this respect, merging the different piles into one long list gives you a method for ignoring items of equal old age so you can pay attention to newer stuff.
Reverse chronology doesn’t lead to a “newer is better” way of thinking but it does affect interfaces. We do best what we do most often, so I’m not surprised to see the blogging, flickrer, tubing, twittering crowd of tool-makers bring reverse chronology into the tools and interfaces they make. Indeed, reverse chronology is becoming an interface paradigm in its own right.
If newsfeeds – which offer just one axis of navigation – are preferred format for chewing through the Daily Me things, timelines are a smart way to get an overview.
We didn’t have Twitter or Friendfeed in 2001, but we did have a prototype of Grasshopper. Later known as Rememble, the service lets you share images, comments, text messages and more and places all of them on a timeline that you can easily navigate. You can then comment, label, edit and share any of those items.
Rememble didn’t take off like Twitter did. It didn’t have a social network to begin with, but more importantly, I think we the users just weren’t ready for the idea that we should be sharing intentions and experiences with each other (and possibly strangers). Interestingly, though, Rememble offered much of the same functionality as Twitter and Twinkle in 2001 (as did the now-defunct Nokia Lifeblog) but framed itself as a mostly personal memory keeper. But I digress…
Timelines are an interesting way to visualize data, and are useful tools when we make them interactive. The Simile Timeline (see a demo at the original site) lets you explore a timeline on the macro and local level simultaneously. In my view, the dialog in the image below is the micro level, but unfortunately it’s hard to explore two items at the same time. The main benefit of this timeline is that its easy to spot what’s a/synchronous and easy to measure the distance between two events.
Yugop‘s interface for the MoMA exhibit entitled Design and the Elastic Mind combines splendid non-dynamic poster design with an overlay that shows which items have similarities or are somehow related to one another. Although IntenseDebate and other comment-enabled developers embed pointers to what a debater is saying elsewhere, there are no tools for easily surfacing relationships between entities, whether in a feed or a timeline. You have to dig, search and make your own situational knowledge tools to uncover them.
Dipity is, perhaps a new version of Rememble that takes a “yes, and” approach to the interface, offering timeline, list, flipbook (akin to a carousel/coverflow slideshow) and map views of items. As with every other social application on the planet, you can import your friends, link to your services, etc. but more interestingly you can follow (newspeak for “subscribe to posts from/on”) topics of interest to you, and view them as you prefer.
I’m still looking for a tool that visualizes relationships between entities. Imagine a timeline, list or any sort of representation that can be transformed to a relational view where a node’s network and the valence/strength/direction of ties, reader volume, link freshness/decay, etc are easy to spot and work with. If you’re aware of a tool that does this (well) please let me know.