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 - webrtc.org
Agora - www.agora.io
Daily - www.daily.co/
Dolby - bit.ly/3vgy7qy
Element - ems.element.io/
Intel - bit.ly/31AtHRy
RingCentral - developers.ringcentral.com/
SUBSCRIBE TO OUR WEEKLY: webrtcweekly.com/
00:00 - Intro
03:40 - Requirements and alternatives
06:20 - Going cross-platform
10:47 - Challenges
15:55 - Benefits

[@fabracht]

That was a seriously good presentation. Bravo.

[@mattieruthbackman6793]

Thank you! 😊

[@ceddymuhoza]

Share please whenever out, thank you very much

[@mattieruthbackman6793]

So excited to say: They are out! www.daily.co/blog/introducing-dailys-native-mobile-libraries/