Archive

Thanks for following along here over the past two years as we’ve shared news and updates related to WebRTC. Going forward, we’ll start to share this content on the more up-to-date Chromium Blog, so we thought it was time to officially say goodbye here.

Real-time communication with WebRTC: Google I/O 2013

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
media.peerconnection.enabled option to true
to use the feature, but now it’s enabled by default.

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!

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.