As a dev, this sort of marketing tends to push me to your competitor (Twilio, to be clear). I've done a little work with both, though, and Tropo is good enough that your time is better spent on technical merits than this sort of thing. Or, start a series going over the gnarly technical problems and 10,000 ft overview of Tropo's architecture. I'm sure that'd be an interesting read, and if it adds a tool to my toolbox, I'll likely remember Tropo when I need a voice service again.
Though, this all hinges on me being your target market. Quite an assumption on my part!
Comments
As a dev, this sort of marketing tends to push me to your competitor (Twilio, to be clear). I've done a little work with both, though, and Tropo is good enough that your time is better spent on technical merits than this sort of thing. Or, start a series going over the gnarly technical problems and 10,000 ft overview of Tropo's architecture. I'm sure that'd be an interesting read, and if it adds a tool to my toolbox, I'll likely remember Tropo when I need a voice service again.
Though, this all hinges on me being your target market. Quite an assumption on my part!
Not sure if you're our target market, however, if you want some technical merits, I posted some in the comments here: http://www.diggz.org/index.php/2012/10/16/twilio-is-like-the...