X of Y is pretty powerful when it makes sense. In this case it's tough for me to parse.
Edit: For me, I see EC2 as virtualized servers, and Heroku as Application management. I see Twilio as currently on the same playing field/complexity as Heroku (compared to say, hosted Asterisk)
Yeah that was my feeling too. I mean it's great to have a one-click application to get up and going, but Twilio is about the easiest API i've ever seen, so it's not exactly rocket science.
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.
All the best. And I was (and still am for lots of things) and EC2 user who is now heavily using Heroku, but just didn't get it at first. That's where I am with this right now. I love Twilio, I got it and had an entire application (SMS send/receive, call receive, etc) up and running and debugged in an afternoon. I think that you might have that resistance among people who have used Twilio already.
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.
Or am I alone in thinking this?