hi, Michael from Inbox here.
just noticed someone posted here :) I'm happy to answer any questions, or your can ping me at email@example.com
I'm going to try and get this to run on my Netgear ReadyNAS this week. If all goes well, would you guys be opposed to me releasing it as a packaged app for other ReadyNAS users?
That sounds awesome! Let me know how it goes. Memory might be a concern, but we can work with you to tune a few things. And it'd be awesome to have a supported package. Feel free to ping me at firstname.lastname@example.org
Hey Mate! Just a recommendation for the site: Add something up front and center about what Inbox is. I thought it was a standalone application (because of the URL and frequent mentions to "app") for like 10 minutes. I had to read the documentation to really understand what you had built. Something as simple as "A simple API for interacting with major email providers" towards the top of the page.
P.S. This is awesome. I had an email app idea and I will definitely be using Inbox to build it :D
Thanks for the feedback— very appreciated.
Agree that the domain is very poorly chosen. Maybe inboxapi.[tld] wasn't sexy enough for the VCs?
Hey Michael, fyi, check the subheadline webfont font-weight at a chrome/windows combo. It's horrible to unreadable. Robot at 100 is to lightweight, give it a 200 weight :)
I'm a bit confused. Could this be a first step towards email moving away from the terrible coding standards that plague it currently? I've been saying for some time that email apps aren't the problem, it's the underlying system.
Yep, that's the idea! Modern JSON+REST APIs instead of clunky and buggy old standards.
With that are we seeing complete encryption standards implemented, because that would be fantastic in a new standard.