[toomuchtodo]

Only if its easy to migrate. Now that Elasticsearch has come a long way, I could see someone writing something similar to Graylog (which sits on top of ES, for app/ops logging data), but for email (frontend interface, ingester for mail through SMTP and new REST mail protocols).

[tomashertus]

What about something like this: https://pistats.io/

This is my side project, basically I think that there is space for analytic tool on the top of email(GMail in this case). Because our emails contains much more useful data than we use. The stripe is one of examples.

[davidu]

Without the gmail API limiting inbox search access to a particular filter (eg, "any email from uber.com"), there's no way people should be building a business this way...

opening your inbox up to random third parties is a disaster.

and frankly, I expect google to cut this form of access off, or severely limit it in the future.

[tomashertus]

Well I can't other than agree with you. When I was doing research on this particular use case I was surprised that GMail APIs are open like this.

It was my priority to ensure that we are looking just for specific filter and I touch only emails from Uber and Lyft.

GMail API developers should definitely consider adding this kind of granularity to the system. I think it would allow to build much more sophisticated and trustworthy application.

[davidu]

Yep. I tried to write my comment in a way that wasn't calling you out at all -- but really google for allowing this kind of unfettered or controlled access. :-)

I've no doubt you would do great things and get much greater adoption in a better API-enabled inbox. :-)

[jlees]

Well, we've built the ingester/REST part and we're working on the frontend :) Our sync engine is open source: https://github.com/inboxapp/inbox