Webreakstuff blog

Archive
August, 2006 Monthly archive

Gmail and content findability

Google Mail (or Gmail) is a great service. Enough storage to keep a hefty amount of email, and what you might call a cleverly developed fast user interface. But it has its shortcomings – shortcomings that annoy the hell out of me as a user, and that no one seems to care enough about to implement.

Content findability

Email re-findability:

Storage is granted, so people tend to archive email (or just keep it for a very long time) in services like Gmail. This constitutes a problem when it comes to re-findability. Here’s a practical example:

I subscribe to the Ruby on Rails mailing list, which is pretty high traffic. Due to time constraints, I don’t read all the list’s emails – I archive them for reference. However, when I do search for something and find an email I know I’m going to be interested in the future, I can only “Star” it. That’s a start, but there’s no way for me to organize it in a way that conveys contextual meaning to me (in the middle of 20.000 other email messages).

So I’d like to be able to tag that email with keywords that mean something to me (e.g: rails, caching, bug) so that I can traverse a tree of tags and find that particular email fast if I need it. The usual search model for finding content just doesn’t cut it in this sort of situation.

The need for better solutions

Email solutions (like Gmail) aren’t the only products with content findability issues, but developers haven’t really woken up to that problem – even though they will have to sooner or later. We’re being overrun by increasing levels of information each day (in our email, in our RSS feeds, in our news), and haven’t found ways to properly deal with that.

There’s a larger version of the illustration in this story on our Flickr page.

Click here to read the full post!

Reading on a screen is a lousy experience

Reading a computer screen sucks. More often than not, the designer behind the interface we’re using (web pages, news readers, browsers, applications) didn’t think about content readability or accessibility during the design process – which makes many of us give up. There’s so much great content being written (in the blogosphere and elsewhere) that its a shame so little is being done to fix this.

There are few solutions for the problem of combining short attention span (that the web is causing in all of us) versus online content readability. I believe it is up to us designers and developers, those of us who care about user experience, to tackle the problem in new ways. It will take rethinking layouts, font sizes, color schemes and contrasts. It will take serious advances in web standards (CSS 3 will help). But more importantly, it’ll take a mentality change – in all of us. We need to realize that people want to (but can’t) read.

Readability

If the web is to become the de facto medium for the publishing of knowledge, we need to get much better at using it. And by that I mean we definitely need to get better at displaying text on a screen – or else, we’ll just keep giving up.

Click here to read the full post!