The document discusses how WebRTC is being used in various real-world applications like customer service, distributed workforces, and education. It provides examples of companies like Valspar, Fluke, and Minerva Project using WebRTC to enhance customer service through live video consultations, enable remote collaboration between colleagues, and reinvent the university learning experience. The document also outlines some challenges around performance, hardware acceleration, user experience, and ecosystem fragmentation that need to be addressed for WebRTC to gain wider adoption.

1. WebRTC in the Real-World
Badri Rajasekar CTO, TokBox

2. What consumers use
What businesses need
It’s all about rich experiences that seamlessly tie-in real-time communications to enable and complement an experience.

3. Customer Service Distributed Workforce Education
WebRTC gaining momentum…

4. Customer Service

5. How it works:
• Connect with a Valspar Color Consultant through live video.
• Valspar Color Consultants can overlay recommended paint colors on the video stream.
Valspar

6. 75% of Fire HDX customer questions now come via the Mayday button

7. Distributed Workforce

8. How it works:
•Fluke Connect enables users to connect and collaborate with colleagues via video calls.
•Securely connect and collaborate with others, so they can see what you see.
Fluke

9. Education

10. How it works:
•Reinventing the university experience
• Enable students to interact with one another and with their teachers, share resources and collaborate in real time creating a powerful and productive virtual learning environment.
Minerva Project

11. But what does it take…

12. Mobile is a mess – but getting better!

13. Performance & Hardware acceleration
•Video codecs
•Audio codec – poor stepchild

15. Use-case enablement
•Screen-capture in mobile devices: Quality vs. Contiguous playback
•Programmatically prevent down-scale: access the right APIs

16. Mobile first experience… Sometimes not so much

17. Beyond Mobile

18. UX Improvements – incentivize behavior

19. Multi-party and Media
•Need for custom-built MCUs: What’s the right topology?
•Network Adaptation: Simulcast/Temporal scalability
•SDPs as surface APIs: No, No (ORTC?)
•Scalability – deployment topology
•Telemetry

20. Fragmented/Evolving Ecosystem
•Safari & IE support
•Legacy IE browsers
•Still evolving - Chrome ,FireFox
•Multiple media stream over single peer connection
•WebRTC competing with closed systems – Skype, Facetime, etc

21. Enterprise/Legacy
•NAT Traversal
•Integration with legacy systems
•PSTN/SIP
•Conferencing solutions

22. Up to all of the thought-leaders here to drive adoption … THANK YOU
6+ Billion WebRTC capable devices by 2019*
* WebRTC Market status and Forecast (2014) ~ Dean Bubley