Scoop: Microsoft bets on WebRTC for Skype’s browser future

Skype (s MSFT) is taking first steps towards a browser-based future, and it is doing so by embracing a key technology open sourced by Google (s GOOG) last year: New job postings on Microsoft’s website suggest that WebRTC will be at the core of Skype’s next generation messaging architecture. This is a big step for Skype. Not only would it allow to facilitate voice and video calls in the browser without the need for any plugins, it could also lead to Skype finally opening up its walled garden and becoming interoperable with the next generation of Google Talk and other voice and video chat services.

Microsoft has been working on bringing Skype to the browser for some time. First job offers searching for relevant talent popped up earlier this year, but a number of new postings published in June reveal that WebRTC will play a key role in these efforts. Take the recent offering for a Senior Software Development Engineer, WebRTC, for example. It reads, in part:

Advertisement

“As a member of the Media Signaling and Gateway Technologies Team, you will impact (hundreds of) millions, and help us reach billions. You will do this by being part of a talented group of engineers defining Skype’s next generation calling architecture. You will help create an architecture that allows WebRTC enabled endpoints to directly interoperate with other endpoints on the Skype network, without the need of gateways.”

Here’s what this means in plain English: Skype wants to build a browser-based app that will be able to connect to legacy Skype clients. It wants to transition to a new architecture, but not invest heavily into gateways to keep all those hundreds of millions of users of Skype’s legacy software connected. And it wants to do so using WebRTC.

But Google doesn’t want to do this alone, and there are active efforts to advance WebRTC as a web standard under way both at the IETF as well as the W3C. These efforts are being supported by Mozilla and Opera, both of which have been adding WebRTC to their own browsers. WebRTC has also gotten some support from Microsoft, and the company’s principal architect Matthew Kaufman has been attending the IETF’s WebRTC meetings. It’s unclear however when Internet Explorer will gain WebRTC capabilities.

What does all of this mean for Skype?

Asked about its efforts to adopt WebRTC, Skype didn’t offer up any details for this story. Instead, the company’s head of global communications Brian O’Shaughnessy sent me the following statement via email:

“Skype is an active member of a number of standards groups focusing on real time communications and we continually experiment with both standards based and proprietary technologies that may improve the reach, quality or functionality that we can offer to our users. We keep these technologies under close review, but don’t comment on future product or technology plans as these are subject to constant change and evolution.”

That’s typical corporate non-denial, but the job ads itself are quite specific, and offer us some ideas on where the company is going with this. Microsoft is currently looking for four people working on WebRTC integration out of Skype’s London and Palo Alto offices, and all of them include the following phrase: “You will impact (hundreds of) millions, and help us reach billions.”

Obviously, Skype has always been striving to reach billions. It offers traditional phone calls, after all. But the language also suggests another possibility: As Skype moves towards open standards, it opens itself up to interoperability with other real-time communication networks.

Skype’s technology has been highly proprietary, until now. It has been using P2P tech based on work its founders Janus Friis and Niklas Zennstrom did for their file sharing outlet KaZaA, which has made it hard to take the leap towards a web- and cloud-centric future. Case in point: Facebook’s video chats, which are powered by Skype, required a lot of heavy lifting from the company’s engineers – and still leave users with a 3 megabyte runtime download necessary to chat away.

At the same time, Skype has been taking steps towards open source in standards-based solutions over the years. For example, its group video chats are now based on VP8, the open source codec at the core of Google’s WebM video format. And now it seems like it’s getting ready to take the next big step towards an open, standards-based platform.

The Dev Channel isn’t “a kind of beta version of Googleâ€™s browser”, that’s the Beta Channel. Dev Channel is more like an alpha build; it’s whatever code they’ve got checked in on trunk that may or may not be working in any given build. Beta is much more stable.

First of all this is a very interesting, great find. Only thing is, I don’t think you can conclude that their whole next gen platform will be built on WebRTC based on what it says in the job posting. It says:
1. They are building a next gen platform
2. Skype endpoints will interoperate with WebRTC endpoints without a gateway

This actually makes it sound like Skype and WebRTC will remain two different things, except they won’t need a gateway to talk to each other.

Aside from that it would be uncharacteristic of both Microsoft and Skype to do this. They are most likely to build something of their own and then let it interoperate with other platforms such as WebRTC, Lync, etc. This is the future of telephony, nothing less. Finally the closed gardens will open on that point I think you’re right.

Janko,
Skype isn’t a Microsoft play at openness – simply one of necessity. Browser based video calling was a Flash thing – or a plugin thing. Now it is a native thing. They have to be there to stay relevant in the long run.
I’ve written about it here: http://bloggeek.me/skype-webrtc/
It is a part of a long series of posts I’ve done about WebRTC.