Developing a cross-platform WebRTC API using Rust and WebAssembly
Daily is rewriting its client-side stack using Rust and WebAssembly in order to support both web and native platforms. Why on earth would someone… (cough) I mean, what are the expected benefits? What does such a stack look like? What technical fjords were crossed along the way? How does it affect the design of the user-facing API?
Speakers:
Mattie Ruth Backman, Senior Product Engineer, Daily
Thank you to our sponsors!
Google - https://webrtc.org
Agora - https://www.agora.io
Daily - https://www.daily.co/
Dolby - https://bit.ly/3vgy7qy
Element - https://ems.element.io/
Intel - https://bit.ly/31AtHRy
RingCentral - https://developers.ringcentral.com/
SUBSCRIBE TO OUR WEEKLY: https://webrtcweekly.com/
00:00 - Intro
03:40 - Requirements and alternatives
06:20 - Going cross-platform
10:47 - Challenges
15:55 - Benefits