Looking for more? Check out the resources at .īuild an app to get video and take snapshots with your webcam and share them peer-to-peer via WebRTC.

Signaling mechanisms aren't defined by WebRTC standards, so it's up to you make sure to use secure protocols. ( WebRTC in the real world explains in more detail.) Is WebRTC secure?Įncryption is mandatory for all WebRTC components, and its JavaScript APIs can only be used from secure origins (HTTPS or localhost). As part of this process, the WebRTC APIs use STUN servers to get the IP address of your computer, and TURN servers to function as relay servers in case peer-to-peer communication fails. However, WebRTC is built to cope with real-world networking: client applications need to traverse NAT gateways and firewalls, and peer to peer networking needs fallbacks in case direct connection fails. WebRTC is designed to work peer-to-peer, so users can connect by the most direct route possible. In this codelab you will use Socket.IO for messaging, but there are many alternatives. Signaling methods and protocols are not specified by WebRTC. WebRTC uses RTCPeerConnection to communicate streaming data between browsers, but also needs a mechanism to coordinate communication and to send control messages, a process known as signaling. WebRTC is also available for native apps on iOS and Android. In Firefox, Opera and in Chrome on desktop and Android.

RTCDataChannel: stream data between users.

RTCPeerConnection: stream audio and video between users.

getUserMedia(): capture audio and video.

WebRTC has several JavaScript APIs - click the links to see demos. WebRTC is an open source project to enable realtime communication of audio, video and data in Web and native apps.

Fluid app peer exchange