41–50 of 280 posts
This is great. We've used ContextIO in the past (they've been great) so good to see more ways to access user email data. Any comparisons vs. contextIO? Do you index all the data yourselves, or proxy requests to the actual mail provider?
Clickable link: http://context.io/
What I would really love for someone to fix is how slow email is. Why is it so much slower to send an email than an SMS or FB message with the same contents?
I've routinely used email like an IM system with folks in different companies. GMail will spool email in <30 seconds. Exchange can be near instantaneous.
“Inbox is an email company. Google is an advertising company. This product is our focus, and will not be ‘discontinued’ unexpectedly.” Burn! Very amusing. But for all we know they will be acqui-hired, maybe even by Google, and then shifted to a different project.
I said this in the other thread and I know it sounds cliché, but we're not planning to "go away" or get acquired or something. We've always positioned this company as a long-term play, and made that very clear when hiring, raising money, etc. It's just not possible to go after something big if you plan to "flip" the company quickly.
Your claim that your product will not be discontinued is worthless. If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it. Doesn't sound like a good idea? Then shut up.
I find the angry tone of this message to be misplaced and unnecessary.
Not like they can't shutdown their company irrespective of any promises.
Your claim that your product will not be discontinued is worthless. If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it. Doesn't sound like a good idea? Then shut up.
I find the angry tone of this message to be misplaced and unnecessary.
Your claim that your product will not be discontinued is worthless. If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it. Doesn't sound like a good idea? Then shut up.
'unexpectedly' is the key. Giving people 3-6 months of runway to say "we're shutting down on day X" is still living up to that statement.
Your claim that your product will not be discontinued is worthless. If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it. Doesn't sound like a good idea? Then shut up.
I find the angry tone of this message to be misplaced and unnecessary.
Grinich also points out that developers can build using the Inbox APIs for free, without sending email data to a third-party. Cool! In the future, however, the company will release a hosted version of Inbox that will allow developers to create applications without needing to also scale their own infrastructure. Oh...
You can totally still run it yourself. But we figure most developers won't want to run lots and lots of servers to sync+store terabytes of mail data. (see Heroku, AWS, etc.) ... but you can if you want. And if that sounds interesting, maybe you should work with us? :) jobs@inboxapp.com
Your claim that your product will not be discontinued is worthless. If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it. Doesn't sound like a good idea? Then shut up.
Ouch. We're just a few hackers trying to fix broken developer tools.
Any claim is just a claim, for sure. We know that it's a long road to earn trust of other developers. One of the (many) reasons we made the sync engine open source was so that developers could run it on their own metal without trusting us. Transparency is really important to us.
This is just the beta announcement of our API. I'd love to hear any comments you have on what guaranteed level of support+performance you would need for a hosted product. We're working on a hosted version now (so you don't have to run it yourself), and developer happiness is the #1 priority.