Twiliocon 2012

Last week, part of the VerbalizeIt team jetted off to San Francisco to attend Twiliocon 2012. As you can imagine, connecting our customers to live human translators across the world involves quite a bit of telephony, and we were eager to hear from Twilio about their latest offerings. We were also very excited to connect with developers to discuss ways in which the VerbalizeIt API can intergrate with Twilio.

Zach, one VerbalizeIt’s awesome developers, had this to say about the conference:

“Twilio is all about making their services available to everyone, and this was very apparent. They had a great crowd. Developers mostly stuck to workshops on how to use Twilio, ranging from basic calls to advanced features and new tools. Other talks and workshops were more fun (Hustling for Hackers), generally technical (API-driven development from Heroku), or startup focused (closing keynote from Dave McClure).

The keynotes were awesome. On Wednesday, the opened some garage bay doors to a giant auditorium with sexy lighting and huge red/white posters of people who’ve contributed to society via Twilio along the walls. The CEO Jeff came on to Smashing Pumpkins, and dropped a whole bunch of new features (call stats, SIP, WebRTC) and some usage metrics graphs that had a pretty close resemblance to a hockey stick.

A lot of the people that stopped by the VerbalizeIt booth were nontechnical, and many expressed a real need for live interpretation (customer support was a big one) or accurate transcription.

The Hackathon was pretty cool- played around for a bit (started a phone-based Reddit reader) but didn’t stay until the end. Met some cool developers from around the country.

Twilio definitely demonstrates how to have a ‘developer platform’- unbelievably easy and fun.”

We can’t thank Twilio enough for hosting their Twiliocon Conference this year; our team learned so much & we’re excited to implement our findings into the VerbalizeIt platform. Until next year’s conference!

Leave a Reply

Your email address will not be published. Required fields are marked *