Here's the video from the WebRTC session at Google I/O 2013, which gives a good look at the current state of the WebRTC universe.
All of the WebRTC code is now enabled by default in Firefox Nightly. Previously, you needed to go to about:config in Firefox and set the
Today, Chrome and Firefox jointly announced interoperability for WebRTC. This website has been updated with information for developers wanting to build interoperable web apps.
1. We've added a Firefox section that lists status and useful resources.
2. We've added a Demo section that details how interop is achieved through running code.
3. We'e added a Interop Notes section which call out the main differences.
We'll keep the site updated as changes are expected to be frequent.
In case you missed it, Google will be hosting a new protothon event at the end of the month. The last day to apply is this Friday (the 9th of November).
WebRTC is now live in Chrome version 23, which is now rolling out to the public. No flag needed, no special Chrome build required.
It's the biggest milestone yet. Our journey started with the open sourcing of key technologies in June 2011 and with the help of community driven workgroups at the W3C and IETF, we made these technologies available through a web API and ensured standardized protocols. We also iterated heavily based on your feedback.
18 short months later, web developers can now offer Chrome users the ability to have live, high quality audio and video communication as part of their web experience.
If you are a developer, join our mailing list and take a look at some demos and start thinking today how letting people talk and see each other could change how they experience your services / applications!
Read more about other Chrome 23 features here.
We are getting closer to having WebRTC reach stable. As I mentioned a while back, we are trying to make the last big changes before this happens.
As such, we are now hiding the PeerConnection00 class behind a flag (--enable-deprecated-peer-connection) both for Canary and M23 beta.
This won't be visible in the chrome://flags page and therefore can't be made to stick; you have to launch chrome/chromium with the flag every time if you require the old API.
This is a hassle and having you switch APIs is no fun. Rest assured that changes going forward will be smaller and smaller... and thanks for all the amazing feedback so far!
Chrome M23 Beta now serves PeerConnection API without a Flag.
Blog post by+Justin Uberti here: http://blog.chromium.org/2012/10/supporting-new-media-experiences-on-web.html
Cullen Jennings, co-chair of the IETF RTCWeb working group, posted this intro to WebRTC on Vimeo. It's a good primer.
If you have been following the W3C WebRTC spec and looking at the Chrome implementation, you will have noticed that our implementation was not spec compliant.
With this week’s patches to Chromium and Webkit, Chrome is now a editor’s-draft-compliant WebRTC implementation.
RTCPeerConnection is replacing PeerConnection00. RTCPeerConnection is the API you will find in the upcoming stable version of Chrome, and the last major API change before we go to a public stable release.
These changes signify breaking current applications. We do not take this lightly. It is the unfortunate consequence of being at the forefront and of using the Chrome Canary and Dev channels to help the community iterate on the WebRTC API.
As Chrome 23 hits the beta channel, we will move the older, deprecated PeerConnection00 behind a flag, --enable-deprecated-peerconnection, and remove it completely thereafter.
Once WebRTC goes into the stable channel of Chrome, API changes will be done with a longer, smoother transition period.
1-10 of 34