3 ms·
So what's new Twilio can offer here? Twilio lets a modestly competent web developer program a telecommunications company from their kitchen table in about, oh,
by patio11 16y ago
So what's new Twilio can offer here?
Twilio lets a modestly competent web developer program a telecommunications company from their kitchen table in about, oh, six weeks or so. Alternatively, Twlio lets a modestly competent web developer take an existing app and add voice/SMS features to it in about a day. (Have a social site? Want to do SMS notifications when something important happens? You can implement that in four hours.)
- steveklabnik 16y agoI implemented "text me when someone orders" in about 25 minutes of time, from clicking "sign up" to "cap deploy." Super awesome.
- mahmud 16y agoI am far from being modestly competent as a web developer[1] and I was able to hack a voice menu in 30 minutes, in Lisp, before I knew XML. -- [1] infrastructure jockey != web developer.
- akalsey 16y agoWith Tropo, you can implement that in less than four minutes - it's two lines of code. Ruby: message "something important happened", {:to => '14155551212', :network => 'SMS'} And then one line of code to hit our session API over http and run the code.
- stanleydrew 16y agoThis is pretty disingenuous. It's the same exact two lines of code to do this in Twilio. Yes if you know ahead of time what those two lines are then you can type them in less than four minutes. Same goes for Twilio. I think what patio11 is referring to is the amount of time it would take for a new developer who's never seen the Twilio API before to get up and running. This includes things like the time to understand the API and documentation. The actual writing of the code is always the easiest part of implementing something.
- visionik 16y agoYou make a great point, but it's also somewhat disingenuous ;) It takes some time to learn how to use a platform. It takes some time to code on a platform. The actual writing of code is easiest when you are doing small applications. However, when you are writing larger applications the coding becomes the larger portion of time. Today it's easier to learn Twilio than Tropo - largely because Tropo needs better documentation (that's coming very soon). However, I will contend that once you know the platform, Tropo is easier - and much more powerful. I think that's what others are saying in this thread. We've also heard that from customers who have switched from Twilio to Tropo. None of this should be surprising to anyone. Voxeo has been doing developer-centric telephony for ten years. Voxeo knows all the little problems and challenges that can come up over time and we've built a platform to address them. Twilio is new to the industry, they came at things with a fresh set of eyes and were able to "re-factor" the simplicity and usability yet again with that fresh perspective. I say "re-factor" because it's exactly what we did at Voxeo when we started in 1999. The experience reminds me of Battlestar Galactica: All this has happened before, and all this will happen again.
- akalsey 16y agoFair enough. But if it takes 4 hours to figure out how to write these two lines of code, something's wrong. Documentation, complicated and confusing API, hard onramp to get started... Our goal is to get a developer who knows nothing about telephony from signup to making their first phone calls and text messages in under 5 minutes.
- visionik 16y agoI'm Voxeo's CEO. Thanks for the summary of what Twilio makes possible. What nivertech (who you responded to) knows and was trying to say is this: With Voxeo (and others) a competent web developer has been able to create a telecom company in six weeks - or add voice features in less than a day - for ten years now. Voxeo delivered and has grown a completely free web-based telephony developer program since 2000. And since 2000 over 200,000 developers have used Voxeo to do just that. This is the Voxeo developer site in the wayback machine archive from August 19, 2000: http://bit.ly/voxeo-dev-2000 http://bit.ly/voxeo-dev-2000 Quoting that site: "our mission at voxeo community is to make it as easy as possible for web developers, service providers, and enterprises to create and deploy applications for an existing market of 1.5 billion telephone users. existing web developers & services use technologies like Perl, PHP, Cold Fusion, Microsoft ASP and Java Servlets to create web applications for traditional web browsers via HTML. we make it just as easy to use those technologies to create web applications for telephones, using phone markup languages such as VoiceXML, Microsoft WTE, and CallXML." Here's the juicy part: "if you have experience creating web applications, this site will help you create and test your first phone application in less than an hour -- without any new hardware or software." Sound familiar? :) What Twilio has done that's new is use marketing and hype to convince developers they invented something that was invented by others and available for a decade now. The power of hype never ceases to amaze me. To be fair, Twilio also did a great job creating more modern developer documentation and refocusing on simplicity. These are things Voxeo had drifted away from as we grew into "the man". In short, we got distracted by million dollar deals with enterprises and carriers. We've continued to invest in our developer community but things got increasingly complex as we added more and more features and options over time. Our new Voxeo Labs group - and it's Tropo.com service - was created to fix that. We're behind on the evangelism but way ahead on the technology. And I dare say we're getting better at evangelism every week. ;) -Jonathan
- mgkimsal 16y agoIf it was really that easy a decade ago why was there no marketing done to reach people like me? Show me pricing lists and contracts from 10 years ago indicating it was cheap as Twilio was 2 years ago. I can't see anything at http://web.archive.org/web/*/http://voxeo.com http://web.archive.org/web/*/http://voxeo.com :( I suspect the infrastructure was there for the 'big boys' and that indie devs and 2-3 man shops who wanted this sort of functionality were ignored in favor of 'enterprise' development shops and projects. OK - rereading your post here - yes, you got 'distracted' by big deals. But it's the focus on getting the basic fundamentals as easy for people to use as possible which has created the Twilio loyalty and fandom they have relative to voxeo/tropo. Twilio has (imo) about a year to add some more features that people are asking for before people jump ship. They should not waste that goodwill and rest on their laurels. But it's going to be easier for them to grow their success with smaller shops and indies in to something larger as those smaller shops and projects grow to larger needs than it is for 'enterprise'-focused groups to prove to the smaller players that they 'get' the independent developer market. You can suggest that this is 'just' marketing/evangelism. I suspect it's a bit more - a focused simplicity on getting a few core things down first rather than trying to offer multiple services on day one. That doesn't appeal to everyone, but I think it's helped more than hurt in Twilio's case. Simply by having more options up front you're forcing people to have to learn a lot more about stuff on your terms when making an evaluation. For example, Tropo's APIs - 'webapi' vs 'scripting'. Huh? What are the differences? I don't find an adequate explanation of the strengths/weaknesses of each model. Both services have their place, but developing a rabid fanbase will serve Twilio better longer term as opposed to pure technical superiority.