ashrust

We've noticed the same price differential but if you include the cost of paying someone to manage the db and be on call in the event of an issue - it seems to even out.

We've moved some stuff off Heroku but not because of cost, most recently we discovered they have a tight max on scala apps and it was cheaper for us to put it on aws directly, rather than code around it on Heroku.

We do try - and btw, we're hiring if you know any iOS engineers...

Let us know if you're in the unfortunate position of having to use it. We'd love to know if it works out for you.

Thanks - we appreciate the feedback.

It's one of our most requested features. Just like email, if it's not easy manage, it's difficult to keep track.

For example, we have use our own product to provide text based support and it receives hundreds of msgs a day - difficult to manage without a way to focus on what you need to deal with right now.

Yes - http://sendhub.com/developer

There doesn't seem to be many similarities at all.

Agreed on Khaled, although I'm at best unsure on James.

People told us we were crazy for months. During our YC interview PG told us it was one of worst ideas he'd heard. Thus, I believe founder conviction is one of the most important parts of building a company.

As an aside, SendHub isn't really focused on SMS marketing, there are lots of services out there for that - people use SendHub for both interactions within their business as well as communication with customers.

These rounds can be called anything you wish. Remember when onswipe raised a 'Series Awesome"?

We're planning on expanding to europe soon, likely the UK first.

We use hackpad at sendhub all day, everyday. It's invaluable. I've used other wiki systems like atlassian and wiki media but this is the only that's stuck. Easy to use, updates in realtime and the founders have always been available to listen to and respond to our feedback.

We truncate longer msgs, and the link leads to the full msg. The link allows you to get realtime feedback on your msgs which a lot of ours users find extremely valuable. We'll also be adding some more features to the landing page, which you can brand, so SendHub is largely invisible in the process.

We do this for a few reasons: 1. you can send msgs longer than 160. 2. You get realtime feedback on the msgs. 3. It helps to prevent spam.

We don't allow the removal of the links but you can control the landing page with your name and avatar and our paid plans include complete branding of the page.

You can ping us at support [at] sendhub.com and we'd be happy to talk through your options.

Thanks for the feedback.

1. You have to build an endpoint and process the inbound requests, that takes a good deal more engineering time than making an api call to check for them.

2. This gets complex when you're sending messages to users in the context of groups an individuals. it's not a big problem but you'd still have to code it.

3. That sounds simple but doesn't account for things like timezones.

Thanks for the questions, I'll do my best...

1. The API is certainly one of our suite of features, you can also use SendHub via the web or any sms enabled cell phone. We expect to see more competition in the space and will be doing our best to contribute to open source ourselves.

2. A lot of our users have tried other SMS products and found them to be a poor experience - based on the feedback we get. We try to spend our time focused on building the best possible product and let that, rather than our backgrounds, do the talking.

3. We believe so, and our initial sales are reflective of that.

We think the Twilio API is great but there's lot of features you might need for your app that aren't built in and that SendHub's api provides, for example: we have an inbox with threads so you don't need to build an endpoint to receive messages and they can be kept in context.

Actually, a few people have now asked about this, if you'd like us to add it: please send an email to support [at] sendhub.com or text us: (650) 830-5662.

I think the same could be argued for Heroku and EC2 - no?

Thanks, great feedback. We're definitely focused on developers not yet using Twilio for their apps or don't have the time to manage in and outbound messaging on their current apps.

Thanks, we didn't build the API with CORS in mind but if you have suggestions or use cases, we're always open to making it easier for developers.

Thanks, that's great feedback, the developer page is definitely in v1. You can see the send and receive functions on our getting started guide: http://apidocs.sendhub.com/GettingStarted.html#viewing-the-i...

We're built on the Twilio API, we add a lot of features that you'd need to build yourself otherwise, like: sending and receiving messages, contact management, scheduled messages etc.

We give you 1 number per plan, but always happy to talk through individual needs: sales [at] sendhub.com or feel free to ping us on live chat on our site.

We love the Twilio api too, but you still have to write a lot of code to make it fully functional for your app, our api takes a lot of that need away. For example, what happens if someone calls the number you send your text from? We have settings and options for that.

or platform as a service?

We add a lot of extra features on top of the twilio api, like: send and receive messages, context for conversations, scheduled messages and contact management.

The main issue is what happens when you want to receive a reply to your message - you're going to have to build an inbound endpoint and process those requests. Then how do you know what you sent that contact in the past or what they sent you? We fix those kind of problems and it's just one call for each of them.

Groupme is like instant messaging for a group. SendHub is much more like email.

Nice work guys. I already control my TV via my iPhone, no reason why shouldn't be able to do the same with games. Love it.