E-mail didn't really evolve since Gmail. Why is it so hard to innovate?
blog.frontapp.com
blog.frontapp.com
That said, I don't use gmail anymore because I don't want my emails to be directly in the hands of the NSA.
But let's focus on their list for a bit. Because innovating a sector is not a goal. Having a goal and therefore innovating, that is a goal. So, does the list they formulated hold up? I don't think so:
better interfaces: Better than gmail? Good luck. Besides, even old-style programs like claws-mail, sylpheed and thunderbird have really good interfaces, for their purpose.
better email management: Gmail does that. And one has to be really careful with that: It is not something every user need, sure not something every user wants, especially if it even once sorts something the wrong way.
better workflow integration: Emails are not tasks. They don't need task management in general. Emails are a communication medium, and sometimes, they contain or become tasks. but that is not a general requirement for users.
better attachment handling: What does that mean besides searching for attachments, maybe including their title, and browsing through the photos? Like attachments.me tried to do. But all of that is not innovation…
better social integration: The action one might want to do, like tweetbacks, should be linked in the email. Isn't that already the case? Blogs do that (ok, serendipity does, don't know about the others).
better prioritisation and analytic: To general. Besides, Gmail tries that already.
So, hmpf. Though I want to add that their general product idea (shared inboxes for taskmanagement) doesn't look bad, for a very specific usecase.
But sure, if you use emails primarily to collaborate with others, for you the emails are task thinking might very well be true.
Then I hope you don't send any messages in plaintext, and good luck with the headers.
I want the ability to "like" an email, and have the sender know that I "liked" it. I don't want to write "yes, I agree", or even worse, a terse response of "like" as I feel that's a waste of my time, the sender's time, an unnecessary "+1" in their inbox.
I just want a way to say "I read your email and it sounds good to me" without having to actually write anything. Just click the "heart" or whatever symbol, and the sender is notified next time they open their email client with the heart showing next to the thread. Would work out nicely for lists and group emails as well.
I suppose there are clunky workarounds that would allow such a thing dependent upon client implementation, but it's just not that significant of a thing.
As for shared inboxen for task management, I'd recommend Asana (with whom I've no affiliation, besides being a happy customer).
I think there is a lot to do with this idea.
It's the ability to give pure positive reinforcement without actually using words, and it's one of the most powerful ideas to come out of the Web.
At http://www.mailcloudapp.com We're currently working on new ways to use e-mail. Always hungry for feedback and new ideas! ;)
"enobrev has read and 'liked' your message with the LikeMail chrome extension! Download it _here_ so you can do the same with your emails."
Then on the recipient's client, if they have LikeMail, consume that message and hide it, while showing the appropriate signaling in the inbox, etc.
Definitely a clunky workaround, and can easily be considered spammy, I suppose, although if that automated message were customizable, maybe less so. I think the reason for the email (as opposed to skipping it) is to convey the info the action of "liking" is meant to convey. Essentially if I hit "like" button in LikeMail I'm trying to tell the sender "I read and liked your email". Sending nothing would go against that intention.
Few people even know that they can access Gmail anywhere other than at mail.google.com or via the Gmail app. Ditto for hotmail/outlook.com and pretty much every other freemail service out there. And of course ad-supported freemail providers have no incentive to let their users access email with a third-party app.
The distinction between an email service and an email app is so murky in the minds of most people, that Mozilla added a dialog box to Thunderbird where they offer to create a new email account for the user. Seriously, a lot of people were wondering why Thunderbird didn't come with its own email address! Instead of trying to dispel this myth, Mozilla just let people keep believing it.
Google Apps was certainly taking a huge chunk out of enterprise, but I don't know if that's still happening now that you have to pay for it from employee #1.
Outlook usage is so embedded and big enough that Google built a sync app, but moderately funnily, the 'how to integrate google apps with Outlook' video on this page is missing, not sure if that's a reflection of how few people use it?
All that would be required to jumpstart the innovation process is a developer-friendly API and standardised events for extending email:
onReceive(headers, body);
onOpen(...);
onTagged(...);
...
That would allow developers to do creative things with email. It may even give way to niceties such as: npm install email-itinerary-parser
These events could be standardised across the board. A plugin ecosystem would allow emails to operate much like blogging platforms do today. You could have a self-hosted email platform with a plugin dashboard where you would pick and choose your plugins. The UI would be the hard part but is a tractable problem given the state of client-side MVC libraries that didn't exist until a few years ago.A service like Akismet would provide SPAM filtering and other services could be built around it. The trust factor would be an issue but it might be even possible to send these services only extrapolated data instead of the entire contents of the email.
It would even be possible to build atypical interfaces around your email. You could for example build a blogs UI that shows all emails sent to myname+blogs@mydomain.com. The blogs Controller could automatically reply to that email with the published status.
In general, things could move in a progressive direction much faster in the hands of the developer community.
It could be suggested that Wave was a revolution rather than an evolution, and that was its greatest weakness. I'm sad that it's gone.
I think largest email innovation is right now happening at KDE with integration of KMail into rest of the desktop.
Outlook Web Access... yeah that changed the world, gmail was but a shadow in its glory.
But yes, it introduced Ajax and changed the world. Gmail was revolutionary because it offered 1GB when 10MB was the norm. Not because of UI.
Google implemented in both a maps app (completely new UI, and WAY more novel use of Ajax than outlook) and a mail app a standard that worked across all browsers (also something missing in outlook).
Google showed us that you can use a new piece of tech across all browsers. Microsoft showed us you could do something in IE, and only IE.
Your statement is equivalent to saying "ActiveX changed the world". You maybe right, but no one cared about the change, and the change was probably negative.
As to novelty: XMLHttpRequest was invented by Microsoft for Outlook Web Access. "Ajax" was invented by Jesse James Garret as a new name for XMLHttpRequest.
I remember the first time I saw someone use OWA on IE, thinking: HTF does that work? Then I remembered he was using IE and chalked it up to proprietary browser extensions, which was correct. Proprietary but useful enough that the other browsers eventually had to duplicate the feature, with different syntax.
That duplication is what made Google Maps (and later, Gmail) possible.
So, yes. Microsoft gets credit for this one. Not for the generosity of their hearts, but for doing it and making it work and dragging the rest of the world along behind them. That had been the tradition with browser tech since the beginning, with positive and negative effects. This was a positive one.
Definitely not a Microsoft apologist here. And XHR could have been better. But no one else cooked it up, so, they get some credit.
The could do what ajax does before microsoft "invented" XMLHttpRequest...
Or we could admit, that coming up with proprietary crap on the web doesn't mean much, the hard part is making it work for everyone.
Personally I find this quite useful and it definitely improved the way I use email.
That would be my top feature in gmail.
I believe this existed before gmail
> gigabyte storage
was not a tech problem before
> speed
in what way? the ui was and still is as fast as most lightweight desktop clients
> powerful search
maybe, although some clients supported powerful search with regex before
I think gmail was not that innovative, but it did bring everything together very well, in a very user-friendly way, along with some new-ish stuff like tags and the no need to delete anything.
FTFY
Actually what still bugs me is that I use email as my default record of all conversations I've had since 94 or so but I have not found a way for it to include SMS messages. Facebook you can forward to email but not SMS as far as I know. I want to be able to say to the program show me all the conversations with Bob last year and see everything, SMS, WhatsApp etc included. So come on startup dudes, build away! I daresay much of the problem is the likes of Apple being precious about letting you download the SMSs, but anyway.