Why The Greatest Online Tool, Email, Still Needs Disruption
blog.frontapp.com
blog.frontapp.com
I read that and thought "what does that even mean? Yet-another-busted-calendar thing?"
Turns out it's actually multiplayer inboxes. Neat! Are you going to release an API so the diehard Emacs users et al can work with everyone else?
Where has this terrible trend originated?
I've seen it before. The boss doesn't want to defer responsibility. So they have everything go through their approval. Suddenly, you're CCing the boss on every thing you send, leaving behind a train of emails to cover your ass. Soon, other bosses demand the same treatment, and before you know it, everyone's inbox is cluttered with FWDs, and Reply-Alls, making sure nobody is left out of the loop.
Your company should have an email policy.
The one UI improvement I can see: make the reply all button hard to find, so morons don't accidentally click it.
Pretty much the only way to invite someone to a meeting at work is to send invite over email. To figure out the place for your meeting, you use "email" client for that. Because you have not sent emails previously to all participants, you use "email" client to figure out the email address of those persons. And the recipients use their "email" client to update their calendar so they remember to come to the meeting.
So to disrupt email, you need to disrupt calendaring and address books and what ever it is called when you search your co-workers email address by their partial name or some wacky username.
It's a mess and a huge beast.
Why must the client be a web app? Why not a regular app? You just install them on your devices once and have the same interface for every server. Damn Atwood's Law!
It's the reason standards exist, so that you are not at the whims of Google and the like. Just stick Thunderbird on your desktop or K9 on Android.
I use thunderbird too, but it's nice to have a webmail back up. Somethings need to be accessed anywhere, and those things should have web apps.
How else would you propose inviting people to a meeting? Put a paper memo in their mailbox asking for a written reply? Call everyone individually on the phone? Walk around the office and gather everyone together?
If you're thinking about the meeting problem, do you propose a meeting/calendar app/client or protocol that is separate from email? Then the problem becomes saturating your user community with your new client. What do you do if someone doesn't use your new meeting/calendar app/client?
I think what you are describing is a problem with meeting/calendars not email.
Because there isn't any other way to send those invites, figure out the meeting room and the recipients, you need to support those use cases also. Otherwise people will not user your client because then they would have to keep using the old one also.
Edit: Guess I can try to explain. Email messages have become much shorter and back-and-forths are frequent (and not always best solved with a call). IM has almost no spam so the idea would be to strike a better balance between only hearing from people you know against the need for "cold emailing". Google's new tabs sort of address this. IM still suffers from fragmentation so there'd be a benefit from using the universal email protocols (so long as unwanted messages could be contained).