I develop and ship a notarized macOS app, and the part I’d be most interested in hearing about is permission handling. Screen sharing plus remote keyboard/mouse crosses Screen Recording and Accessibility permissions, and the difficult part is often getting users through TCC state changes and required relaunches without leaving the app in a confusing half-authorized state. How are you handling onboarding and permission revocation on macOS? Does everything run in the main app process, or do you use a helper? Also, kudos for distinguishing WebRTC’s DTLS-SRTP transport encryption from actual end-to-end encryption and documenting the MLS + SFrame layers. Many products describe any encrypted WebRTC connection as E2EE even when an intermediary could access the media.