Download as PDF, PPTX
Uploaded byDan Jenkins
WebRTC Reborn SignalConf 2016
WebRTC has come a long way in 5 years. It now has strong browser support, open source signaling servers, modules to simplify implementation, and production-ready platforms. While early adoption was challenging due to complexity, the WebRTC community has addressed issues through documentation, code samples, and plugins. WebRTC is now ready for developers to build real-time communication into web and mobile apps.
More Related Content
Similar to WebRTC Reborn SignalConf 2016
WebRTC Reborn SignalConf 2016
- 1. WebRTC Reborn Dan Jenkins@dan_jenkins
- 2.
- 3. Node.js Developer Love Lego& Technic General Geek Founder of Nimble Ape Ltd ❤ open source
- 5.
- 6.
- 7.
- 8. Node.js / IoT/ VoIP/WebRTC Consulting (Anything real-time)
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. Peer to PeerTechnology
- 18. Media Channel for Audio& Video
- 19. Data Channel for almostany kind of Data
- 20. 3 Core JavaScriptAPIs getUserMedia RTCPeerConnection RTCDataChannel
- 21.
- 22. Signalling Server /Protocol
- 23.
- 24. Signalling Server /Protocol
- 25. Signalling Server /Protocol
- 26.
- 27.
- 28. *n peers (Mesh) (Not Recommendedfor all situations)
- 29. No plugins (Browser extensionsare required for screensharing)
- 30. Opens the doorfor Awesome
- 31.
- 32. Browsers, Mobiles and OtherDevices
- 34.
- 35. Little Dependence on MediaServers
- 36. Easier on thewallet
- 37. Awesome apps arebeing launched
- 38.
- 39.
- 40. Cystic Fibrosis TelehealthIn Australia http://www.webrtcworld.com/topics/webrtc-world/articles/334242-australian-cystic-fibrosis-telehealth-project-relies-webrtc.htm
- 41. Cancer Telehealth inTexas https://developer.ibm.com/bluemix/2015/09/16/bluemix-and-twilio-at-krankygeek-2015/
- 42. Developers are building Appsthat help humanity
- 43.
- 44. A brief historyof time WebRTC…
- 45. Its 5 yearsold!
- 46. You always mess upthe first child
- 47.
- 48. At the start, everyonewas so excited
- 49.
- 50.
- 51.
- 52. Developers went andtried it
- 53.
- 54. We didn’t tellDevelopers about the complicated stuff
- 55. Heard of STUNor TURN?
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73. Apple Put AnEngineer on the WebRTC-in-webkit Project
- 74.
- 75.
- 76.
- 77. Microsoft Edge Currently supportsORTC What about WebRTC?
- 78. Edge will soonsupport WebRTC!
- 79.
- 80. All those Supportedbrowsers… Their support and progress is awesome
- 81.
- 82. And we haveplugins for IE and Safari
- 83.
- 84. API & Browser StatusCheck iswebrtcreadyyet.com
- 85.
- 86. You need aSignalling Server
- 87.
- 88.
- 89.
- 90.
- 91.
- 92.
- 93. And many manyothers
- 94.
- 95.
- 96.
- 97.
- 98. STUN & TURNServers
- 99. You still don’tknow what they do. Do you?
- 100. STUN Siri, What’s myIP Address? Here’s your address: James R. Herman Cruise Terminal at Pier 27 Pier 27 The Embarcadero San Francisco CA 94111 Siri wouldn’t make a good STUN Server
- 101.
- 102.
- 103.
- 104. Don’t Forget!… You needto address a STUN server in your App!
- 105. Google give yousome! stun.l.google.com:19302 stun1.l.google.com:19302 stun2.l.google.com:19302 stun3.l.google.com:19302 stun4.l.google.com:19302 There are many others!
- 106. Don’t repeat History Usea STUN Server!
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116. Xura … (Forge)… (Acision) Kandy Tokbox Respoke Cisco … (Tropo) Plus many others…
- 117.
- 118. 2 Billion+ WebRTC EnabledBrowsers https://docs.google.com/presentation/d/1JwnW6v3OM0RfoDYrPPTJrDNeIpidgh7hF_k5E1j2oKM/pub
- 119. 1 Billion+ Transmitted audio/videominutes per week in Chrome https://docs.google.com/presentation/d/1JwnW6v3OM0RfoDYrPPTJrDNeIpidgh7hF_k5E1j2oKM/pub
- 120. And a wholehost of internal improvements
- 121.
- 122.
- 123.
- 124. And finally... a specificationsoon (hopefully)
- 125. Currently a workingdraft https://www.w3.org/TR/webrtc/
- 126.
- 127.
- 128. Trusted Origins = Localhost+ HTTPS (But not Self Signed Certs)
- 129.
- 130. Don't get caughtout in wondering why your app doesn't work...
- 131. It’s time togive WebRTC another go
- 132.
- 133.
- 134.
- 135.
- 136.