Changing the email client

We’re in the thick of hiring and next week is Thanksgiving, so blogging is going to be very light for the next two weeks.
One thing I have noticed is that lately there are attempts to “change how people interact with email.” Google released their Inbox product. And today I saw a post about an IBM attempt to change email and how people use it as a tool.
I find as I juggle more and more incoming email that most email clients just don’t cope with the whole process well. For a long time I could use my inbox as a todo list and manage what needed to be done. With the company growing and changing, an inbox todo list is just not as workable as it used to be. Maybe the Verse client from IBM is one solution.
I’m glad people are looking at how to improve the email client. Fundamentally, the client I’m using now is not that much different than the GUI client I was using at MAPS back in 2000 and 2001. Sure, it’s visually different, but the functionality isn’t much different.
A few years ago I blogged that people should look at building new email interfaces. I’m glad that some companies are actually looking at the interface and rethinking how people interact with email. Who knows, maybe we’ll end up with some specialized clients that are featured around getting work done by email and other clients focused around a more casual use of email, like shopping and networking.
 
 

Related Posts

A new way of reading email

Fastcompany reports that AOL has a new webmail client “Alto” that changes how email is read and received.

Read More

Asynchronous Bounces

There are three ways that an email can fail to be delivered:

Read More

Email History through RFCs

Many aspects of email are a lot older than you may think.
There were quite a few people in the early 1970s working out how to provide useful services using ARPANET, the network that evolved over the next 10 or 15 years into the modern Internet.
arpanet3
They used Requests for Comment (RFCs) to document protocol and research, much as is still done today. Here are some of the interesting milestones.
April 1971 [rfc 114]RFC 114 A File Transfer Protocol.[/rfc] One of the earliest services that was deployed so as to be useful to people, rather than a required part of the network infrastructure, was a way to transfer files from one computer to another. In the [rfc 114]earliest versions[/rfc] of the service I can find it could already append text to an existing file. This was soon used for sending short messages, initially to a remote printer from where it would be sent by internal mail, but soon also to a mailbox where they could be read online.
August 1971 [rfc 221]RFC 221 A Mail Box Protocol, Version-2[/rfc] had this prescient paragraph:

Read More