WebRTC: Real Time Video /Audio For Your App

Riaz Virani

Riaz Viranimonokaicode.co

pennyforyourcode.com

attend.zoho.com

How Did We Get Here?

HISTORY! - Part 1Once upon a time, we had slow internet limited to ISDN and dial up.

We used AOL Instant Messenger and RealPlayer.

Hell, Google was still a startup.

But then the gods gave us faster internet.

We started to video chat and watch endless videos of stupid house cats.

Yet the browser was still a fail.

HISTORY! - Part 2We needed Skype and Flash to talk to grandma.

Nope, there was no native HTML5 solution for our nanna.

So…

webRTC baby!

What is WebRTC?

Key Pieces

GetUserMedia (camera and microphone access)

PeerConnection (sending and receiving media)

DataChannel (sending and receiving everything else)

What It’s Not

WebRTC Peer-to-Peer Audio, Video, or Data

WebSockets Bi-Directional Pipe Between Client andServer

Server Side

Peer⇔ Peer =

! Peer⇔ Peer =

Required 20%of the time

This #$@&! can get complicated

Demo

https://www.monokaicode.co/webrtc_demo.html

Real Time Video Chat for Everybody!

Strengths = Weaknesses

Noooooooooooooooooo!

ORTC (Object RTC)

Originally designed by Robin Raymond of HookFlash in 2013

Removes WebRTC’s use of Session Description ProtocolSome think it’s too loose of an API

Google wants to merge both into

“WebRTC NV”

Microsoft is the only vendor who

supports ORTC

No Easy Solutions

Popular Providers

All-in-One Platforms

● OpenTok

● Twilio

Libraries

● PeerJS

● SimpleWebRTC

● Muaz Khan’s Libraries

● EasyRTC

Network Traversal

● Xirsys

● Twilio

● Bit6

Maybe this is the year...

But maybe not...“Just 4% of participants in the Nemertes' 2015-16 Enterprise Technology benchmark saidthey were using WebRTC today”

- NoJitter.com (2/3/16)

The Bottom Line

The End