Seven Rust GUI Libraries, Two Questions: Who Draws and What Changes When Data Moves
Rust's ownership rules force every GUI framework to pick an architecture for handling shared state, so the library you choose locks in your app's structure. Picking wrong means a rewrite once an app grows beyond a few screens; the article gives a checklist to avoid that.
Choosing a Rust GUI framework comes down to two questions: who draws the pixels and what happens when data changes. That's the framing here, as a developer evaluates Egui, Iced, Tauri, GPUI, Slint, Dioxus, Xilem, and GTK-rs/Relm4 for a log viewer tool. Each library picks a different answer, and those answers determine bundle size, rendering speed, and how much boilerplate you'll write.
Egui uses immediate mode: the whole UI is a function that runs every frame, reads state on the way, and releases borrows. Iced borrows Elm's architecture, with state, messages, and a single update function. Tauri hands rendering to the OS WebView and keeps Rust for heavy lifting. GPUI comes from the Zed editor and targets 120 fps with a game-like render pipeline.
Trade-offs are concrete. Egui is fast to build but looks like dev tools. Iced is structured but still pre-1.0; its last release is nearly a year old. Tauri ships small installers but depends on different web engines per OS. GPUI is built for speed but its API tracks Zed's roadmap and has thin docs. The author's own tool chooses GPUI because speed is the priority.
The two-question framing (who draws pixels, what happens on data change) explains why Rust GUI libraries look so different: each is a coherent answer to the borrow checker's demands, not just a style preference.
The shared infrastructure across libraries (Winit, WGPU, Taffy, AccessKit) means the ecosystem is consolidating on lower-level components; a fix in one can lift all the frameworks built on it.
GPUI's tie to Zed is a double-edged bet: you get speed, but your API follows Zed's needs rather than the broader community's, and docs are sparse enough that you end up reading Zed's source.
Iced's near-year without a release, despite active source updates, shows that pre-1.0 Rust GUI libraries can stall in version bumps; teams should factor release cadence into adoption decisions.
makePad development speed is also quite fast.