One of the main focuses of AT&T's Developer Summit at CES in Las Vegas this year was WebRTC.
The AT&T WebRTC API truly untethers user phone numbers from their mobile device. When your phone number on your mobile rings, so can your browser and your tablet. It's the kind of thing that could make answering your phone or making a phone call from anywhere as easy as checking your email is today.
&yet was privileged to play a central role in AT&T's work with WebRTC this year, alongside other partners like Ericsson and Voxeo Labs.
&yet has teamed up with the AT&T Foundry in Palo Alto to deliver several projects this past year. Some were shared at CES and most of those are featured at js.att.io and on AT&T's GitHub account. (Note that at this time, you have to be a registered AT&T Alpha Developer in order to use the API.)
Aside from the various sample apps and tools we contributed, a key highlight was att.js, a JavaScript SDK for the AT&T WebRTC API. (See the code on GitHub.)
You might expect the largest telecom in the US to be fighting against a new and disruptive technology like WebRTC, but that's not been our experience with AT&T—just the opposite, in fact. AT&T wants to see WebRTC take off.
The people involved in the developer programs at AT&T are serious about WebRTC and building APIs that expose the power of AT&T's existing infrastructure to developers. It's refreshing to see and rewarding to be part of.
Our team at &yet is happy to continue to be involved with AT&T in 2013—and not just cos we ampersands gotta stick together ;)
As an aside, we've also really enjoyed collaborating this year with the amazing team at the AT&T Foundry and the great people at Voxeo Labs, who are behind Tropo and Phono, which both play a significant role in AT&T's call control APIs.