Capiche is a secret society for SaaS power users, building a new community of people who care about software to make the SaaS industry more transparent, together. This article was written by Matthew Guay, Capiche‘s founding editor and former senior writer at Zapier.
The problems with email were there from the beginning.
You’d be reading documentation, see something to improve, and wish you could tell the author.
For MIT’s programming staff in 1965, that idea led to the invention of email. “A new command should be written to allow a user to send a private message to another user which may be delivered at the receiver’s convenience,” wrote the team. “This will be useful for the system to notify a user that … files have been backed-up,” presciently imagining email as a notifications inbox.
More fatefully, they continued: “It will also be useful for users to send authors any criticisms.”
We’ve been trying to escape those automated notifications and unsolicited feedback letters ever since.
Email was a simple enough concept, with a file name (what became the email subject), a user (what became email addresses), and the message. The MIT team’s proposal assumed “The proposed MAIL command can be written,” which proved true. Writing the MAIL command only took the summer of 1965.
Decades have passed, though, and email still hasn’t been perfected.
It’s not for lack of trying.
An email app