Tauri's WebKit engine proved disastrous for Hopp's low-latency screensharing app, plagued by blurry SVGs, audio glitches, and missing AV1 support. Safari's WebKit crashes on simple GIFs, forcing hacky viewport-based rendering. The user agent's stagnant version (605.1.15) broke feature detection, while WebRTC support in WebKitGTK required custom builds, blocking Linux. After evaluating Electron's update complexity and Tauri's stalled CEF integration, Hopp pivoted to Rust with iced for direct backend control.

The move eliminates browser restrictions, enabling LiveKit's Rust SDK to handle WebRTC across all participants in a single token. Rust's access to hardware codecs (like Apple's AV1 decoder) and neural upscaling via M1 chips addresses Tauri's codec limitations. This backend-centric approach simplifies code, reduces duplicated tokens, and unlocks features impossible in WebKit.

Hopp's technical debt with Tauri—design compromises, crash-prone pages, and platform fragmentation—outweighed short-term Electron gains. By centralizing streaming logic in Rust, the team gains codec flexibility, lower latency, and macOS-specific optimizations. The decision prioritizes performance and maintainability over framework trends.

Hopp's Rust migration exemplifies how native tooling trumps cross-platform convenience when core features demand precision. WebKit's stagnation and Tauri's dependency risks made Rust's learning curve a necessary investment for scalable, performant collaboration tools.