Re:Open-source client scaffolds and API pricing
by grinich on Wednesday October 01, 2014 @01:27PM
(#8396158)
(I work at Inbox.)
IMAP libraries are good enough to not have to pay for
a wrapper when using most email providers
I found this actually not to be true when building my own stuff. Although IMAP is a "standard," the various different extensions and quirks mean you need to essentially build for each provider initially.There's also a lot of stuff in Inbox API does that's not available in IMAP. Like the files endpoint[0], or threads as a first-class object[1].
Plus, you don't need to worry about MIME or character encodings with Inbox. The reason we don't great email tools is that they're hard to build.
Re:Open-source client scaffolds and API pricing
by toomuchtodo on Wednesday October 01, 2014 @12:57PM
(#8395947)
Or Use Gmail's REST API if you use Gmail/Google Apps:
Re:Open-source client scaffolds and API pricing
by grinich on Wednesday October 01, 2014 @01:35PM
(#8396234)
The Gmail API is great, but if you're building a real app that needs more compatibility, Inbox is a much better fit.
https://www.inboxapp.com/features
Plus, the Inbox sync engine is open source.
Having said that, IMAP libraries are good enough to not have to pay for a wrapper when using most email providers.