The Ribbit API, and all the REST libraries, require you to submit phone numbers in RFC3966 format. This requires that the Ribbit US sales number (619) 916-2565 is submitted to the API as tel:16199162565
It's not always straightforward to validate phone numbers easily, ensuring that the country code is included. With the help of Javascript, we can make this a lot easier.
You may have seen our Google Wave gadget that uses our Javascript library to create an outbound conference call to lots of people in a Google Wave. You really don't need to write a lot code to accomplish this.
I had to put my augmented reality demo on hold for this week as I have been building out some ultra cool projects here for ( along with the augmented reality ) for the Creativity and Technology conference in New York.
If you are attending, come by and see us do some demos!
We have been working hard to integrate Flash and our RESTful API, generally through a PHP proxy. Why is this so cool to me?
At SXSWi, we launched the yourcall.ribbit.com campaign to ask the community what the next Ribbit API language should be. Well, the community has spoken.
Some of the Ribbit Team went to South By Southwest last week to spread the good word on how a utility should provide its services to an ever increasingly ROI-savvy world. We had great conversations on what the face of telephone service looks like. I had never been to SxSW before, and had no idea what to expect. It was amazing. Never have I been around such a huge group of people who care so much about interaction. So here is my quick recap: My close friends at OrdinaryKids were nominated for an interactive award.
The presentation I did from eComm earlier this month is now online in our YouTube channel, RibbitVoice. The session covered getting started with Ribbit, connecting using the authentication manager, making and recieving phone calls, managing contacts, managing voicemails and sending SMS messages. As you can see, we covered a lot in an hour.
[/caption]
