5 ms·
>We fix it by building smart clients. I think improving email lies before the client. Email is just a message container and apps generally throw a load of diff
by ed209 15y ago
>We fix it by building smart clients.
I think improving email lies before the client. Email is just a message container and apps generally throw a load of different content into that container, events, to-do's, photos etc.
Some of this stuff should never arrive in my inbox. A to-do email should automatically go to my to-do list, an event should automatically go to my calendar, photos should automatically go to iPhoto (or whatever).
Separately to that I can choose how I'm notified about that content.
For example, for all the marketing emails, I'd much prefer to have a Flipboard type app on my mac that receives all of those messages so that they never arrive in my inbox.
So no, email is not broken, but we haven't kept up with ways to manage the growing number of correspondence email is handling. I think the solution lies on the server where mail is sorted into types i.e. if you have that Flipboard for Marketing app, you get those marketing messages otherwise you don't.
- icebraining 15y agoKDE's system-centralized PIM solution, Akonadi, seems a decent way to solve that problem. It's designed to share data between local application and external services in a standardized way. Of course, considering almost everyone is using webapps for that type of stuff nowadays, you'd probably need an Akonadi-on-the-cloud solution, POSTing stuff to each webapp as messages come in.
- evaneykelen 15y agohttp://pigeonal.com/ http://pigeonal.com/ is my attempt at doing this, we've built this app for email that you can deal with in an "out of band" fashion e.g. while waiting in queue. Disclaimer: I'm one of the creators of this app.
- ed209 15y agothat's a pretty nice start. I guess it's similar to label+rules in Gmail? This creates a series of "inboxes" for the 200 services you recognise - and for client side that's pretty cool. I was thinking more that I'd never actually get these messages via email, that on the mail server, these messages would be interpreted and assigned to whatever app/protocol is relevant. A bit like Tripit do with bookings email. Look forward to see more from your app!
- sjsjsj 14y agoContext.IO provides API access to core resources in IMAP-enabled mailboxes such as messages, contacts, threads and attachments, and provides webhooks to manage all of these. Apps can be notified of specific content as it arrives, instead of constantly polling a mailbox for matching content. Makes development of apps that look for and push important messages much much easier. http://context.io/docs/2.0/accounts/webhooks http://context.io/docs/2.0/accounts/webhooks Full disclosure, I do Community Management/Developer Relations for Context.IO.