Glad to have you here, lets review what happened with WebRTC in 2021 and how is that affecting our event today and the future for all of us.

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?

This session will cover how to add custom media processing to browser-based communications using WebAssembly. Learn the basics of WebAssembly and discover how to use it with WebRTC. Explore some challenges the Dolby.io team ran into when using it for audio processing in their WebRTC-based communications SDK. Finally, learn about how they leveraged this technology to add innovative features to the Dolby.io Communications APIs.

WebTransport and WebCodecs are new API’s that provide powerful, low-level contols over the RTC stack but developers must implement many features of WebRTC themselves. Intel will discuss the benefits and disadvantages of these technologies and their implementation learnings from using these API’s in the open source Open WebRTC Toolkit (OWT) media server project.

Agora has been researching the best ways to manage large numbers of remote video streams and support grids of up to 64 people (8×8) by detecting CPU and network resource limits from within the web browser environment. This is a difficult problem because CPU information is not available to Javascript and network stats can make it hard to distinguish between congestion and transmission error packet loss. In this session, I will look at the available WebRTC stats, some newly derived stats, and how to adapt in real time to both CPU and network constraints of the local device.

Users expect their communications to be as secure as possible. WebRTC has built in encryption for peer-to-peer media, but End to End Encryption (E2EE) gets complicated for multiparty calls with devices like Selective Forwarding Units (SFU). In addition, E2EE must be extended to the signaling layer, across different devices, and deal with current usage. In this talk Matrix will review how they solved these challenges in their open source decentralized communications project.

Google will provide insights on what they have been working on and a roadmap update.

WebRTC runs in browsers, but what if you want to build desktop apps? One of the popular ways to get that done is through Electron. While using Electron is quite straightforward, there’s a lot more you can do with it when it comes to WebRTC. After several years building products with Electron and WebRTC, RingCentral will share their best practices in Electron-based desktop development.