Putting WebRTC to Work: Using the Standard in the Real World

19
Putting WebRTC to Work: Using the Standard in the Real World Ian Small, CEO

Transcript of Putting WebRTC to Work: Using the Standard in the Real World

Putting WebRTC to Work:

Using the Standard in the Real WorldIan Small, CEO

What’s a TokBox?

Founded in 2007

Silicon Valley venture-backed startup

Introduced OpenTok live video platform in 2010

Transitioned to WebRTC in 2012

Acquired by Telefónica Digital in 2012

Making it easy

to add face-to-face WebRTC video

to any web or mobile app

apprtc.appspot.com:

In OpenTok:

500+ lines

17 lines

What do customers want?• Not WhatsApp, Skype or BitTorrent...

• They want to have business impact

• Customer service

• Brand engagement

• Remote diagnosis

• Distance education

• They don’t want to become real-time communications experts

Moving beyond the ordinary

Real world not limited to WebRTC standard use cases

1:1+

Group

conferencing

Broadcast

Routing &

scaling traffic

Crossing

firewalls

Low-bandwidth

devices

Recordingconversations

PSTN interop and more...

Three applications

Drawn from real-world experience

1. Robots• There’s more than “Web” to WebRTC

• All about device support

• All about connectivity

2. Insurance claims adjustment• “See what I see” use case

• Also requires device support

• Camera manipulation presents challenges

3. Remote classroom• Multi-point scalable traffic

• Speaker support

• Bandwidth adaptation to avoid LCD challenges

0"

50"

100"

150"

200"

250"

300"

350"

400"

Video&Bit&Rate&for&Streams&Encountering&Level&2&Conges:on&Events&

3. Remote classroom• Multi-party

• Bandwidth adaptation

• Speaker support

0"

50"

100"

150"

200"

250"

300"

350"

400"

Video&Bit&Rate&for&Streams&Encountering&Level&2&Conges:on&Events&

Congestion event

Time leading up to congestion Time following congestion

Robots

Insurance claims

Remote classroom

More than “web”

Camera manipulation

Multi-point traffic shaping

Implementation gaps1. TCP transport fallback (uneven implementation)

2. H.264 support for improved mobile performance

3. Incomplete browser support

4. Quality management for multi-point streaming

5. Refence impl. lacks VP8 temporal scalability support

6. Archiving (regulatory)

But there’s good news• Chrome + Firefox + OpenTok -> commercial applications

• Cloud solutions to browser gaps

• Implementations moving forward

• Enterprises can have business impact today

Breaking the rules with WebRTC• First real-time comms standard moving at Internet speed

• Grown from 0 to 1B+ endpoints in less than a year

• Spawning opportunities for new applications and new use

cases

• Enabled by a powerful standard, widely available browser

implementations, and easy-to-use platforms like OpenTok

Enterprise-grade WebRTC

for commercial apps