The Rust desktop GUI ecosystem, measured

The ecosystem is consolidating from the bottom of the stack upward — faster than its reputation suggests. In the last 12 months: the principal reusable pure-Rust text stacks converged on HarfRust, Zed dropped its custom Linux GPU layer for wgpu, and Slint/Bevy/floem migrated to parley/fontique. AccessKit is now the de-facto native accessibility abstraction; iced and floem remain unintegrated, while gpui support is unreleased and currently disabled in Zed. What remains fragmented is the top: text layout, 2D renderers, widgets, and windowing forks.

A GUI framework is a tower of layers: window (winit opens the window and feeds you input) → GPU (wgpu turns one API into Metal/Vulkan/DX12) → 2D renderer (turns “rounded rect with shadow” into GPU work or pixels) → text (find fonts → shape glyphs → lay out lines) → layout (taffy computes flexbox math) → a11y (AccessKit feeds screen readers) → widgets. Several lower-layer abstractions are increasingly shared; these four stories are where sharing still breaks down.

The shared infrastructure under the sampled frameworks, ranked by an explicitly interpretive sustainability assessment. The table contains 21 entries; 15 are rated amber/red. “Author concentration” is a heuristic derived from dated public commit attribution, not a measured probability of collapse, and “none found” means no public direct funding source was identified—not proof that a contributor is unpaid. Exact reverse-dependency, sponsor, and search-result counts are dated snapshot observations whose raw query responses were not retained. Full sourced table: report/data/load-bearing-crates.md.

A todo app (text input, Enter shortcut, per-row delete, live counter, scrolling) built idiomatically in each framework, versions pinned. All seven compiled and survived the launch check; later inspection observed their windows, and the implementations cover the source-level spec (GPUI exposes low-level elements and a hand-built input example but no reusable first-party high-level input widget, so this app approximated text input). On this M4 Pro, these seven small apps each clean-built in under a minute from a warm registry and empty target directory; that is not a general large-application ranking.

Round 2 tested what production apps are made of: drag-and-drop, live data, custom charts, hover interactions, inline editing, animation. Two more apps per framework — “Pulse” (live metrics dashboard: draggable card grid, 10–60 Hz data, hover-tooltip chart) and “Board” (kanban: cross-column DnD, drop indicators, double-click edit). All 14 built and survived the scripted launch check, and later inspection observed their windows; interaction evidence ranges from source/API paths through retained app tests as marked per capability. Full data: report/11-interactive-results.md + per-app FRICTION.md.

¹ The sample has no shared automatic FLIP/position-transition abstraction: stock iced/xilem layouts snap, while the implementations used egui tweens, hand-built CSS FLIP, or explicit Slint x/y animation. ² iced’s time::every needs a non-default executor feature; the compile error gives no hint.

One quick-note app per framework exercising everything AROUND the window: tray, global hotkey, native menubar, dialogs, clipboard (text + image), Finder file-drop, notifications, live dark mode, multi-window, close-to-tray. Zero implementation-level not-achievable cells on tested macOS — every framework exposed a viable path, although Finder drops and some notification results were source/API-level rather than real end-to-end observations. Full matrix + evidence notes: report/12-shell-integration-results.md.

¹ A trap reproduced in these 3 integrations: muda’s predefined Edit items silently swallow ⌘X/⌘C/⌘V before the framework’s own bindings — the standard Edit menu breaks paste app-wide. ² notify-rust was rejected after a reproducible frame-scheduling freeze in this egui/macOS configuration; delegate replacement is the leading inferred cause. ³ eframe never runs App::ui for hidden viewports — reopen logic must live elsewhere or the window can’t come back. Round upset: dioxus quietly matches Tauri here (tray, hotkey, menubar, multi-window, close-to-tray all built-in). Scope note: this is macOS; the Linux GTK fault line (muda menubars cannot attach to plain winit windows; global-hotkey is X11-only) stands as documented in the fragmentation stories.

The same multilingual corpus (Latin ligatures, Arabic/Hebrew BiDi, Chinese/Japanese/Korean, Devanagari, Thai, ZWJ emoji, one all-scripts line) rendered by every framework — the text-stack fragmentation made visible. Verification used screenshots plus OCR/glyph/caret diagnostics described in each FRICTION file. The seven screenshots are retained, but not every raw diagnostic output is; exact caret/OCR/mark counts and caption-specific interpretations therefore remain local observations rather than independently reproducible results. Full matrices incl. evidence levels and editing behavior: report/13-text-i18n-results.md.

The sharpest cross-stack finding is about editing, not rendering: Backspace over 👨‍👩‍👧‍👦 deletes the whole cluster in WebKit and gpui’s hand-rolled editor, shrinks it through valid smaller emoji in Slint (by design), and splits the cluster or leaves a dangling zero-width joiner in the tested iced, egui, and xilem editing paths. Those integrations lacked whole-cluster deletion out of the box; this does not establish that cosmic-text or Parley themselves lack grapheme editing. Egui also dropped 13 corpus combining marks; Slint showed one notdef mark and clipped tall stacks. macOS AX selected-text queries returned garbled RTL text for egui; actual screen-reader speech was not exercised, so assistive-technology impact remains an inference.

All seven iteration-1 apps were bundled into launching DMGs containing ad-hoc-sealed .app bundles. The “packaging is the hard part” claim splits in two: the mechanical layer is nearly free — a revived cargo-bundle packaged all six non-Tauri frameworks with an identical 4-line stanza, under a minute each (and beat cargo-packager, the ecosystem’s “intended answer,” head-to-head in this run). The trust layer is the real cliff: with no identity configured none of the tested runs produced a distribution signature; cargo-bundle lacks signing while Tauri/cargo-packager support it when configured. The create-dmg flows failed repeatedly on this macOS 26 machine, while a plain hdiutil create fallback was more reliable. In the standard quarantined-distribution path tested here, spctl rejected all seven ad-hoc bundles as expected without Developer ID signing and notarization; Tauri, cargo-packager, and the principal Rust-native cross-platform implementation rcodesign automate parts of that workflow but cannot supply Apple credentials. Bundle sizes: 5.0 MiB (GPUI) → 14.7 MiB (Slint). Reliable app-attributed notification banners and dock behavior also benefit from a bundled, identified .app. Details: report/14-packaging-results.md.

Round 4 tested the last untested dimensions: “Peek” (camera preview ≈30 fps, mic meter, audio, 200-image gallery), “Grid” (100k rows: virtualization, sort, filter, resize, selection), and “Fetcher” (debounce, streamed progress, and cancellation proven by a local server that logs client disconnects). All 21 apps built and ran. Full matrices with per-cell evidence labels: report/15-media-hardware-results.md, report/16-data-grid-results.md, and report/17-async-network-results.md.

The macOS-built apps, rebuilt and run on Linux headlessly (lavapipe software Vulkan + llvmpipe GL, WebKitGTK 2.50.6 — one plausible CI configuration). All 11 tested apps compiled with zero source changes; the differences live entirely in the render path and the shell layer. Verbatim logs, screenshots, and probe sources retained. Full report: report/18-linux-reality-results.md.

Whatever you pick: prototype the riskiest screen first (not hello-world), pin versions exactly (several audited tutorials were stale; this was not universal), test Linux on Wayland + NVIDIA early, and budget real time for packaging, signing, and updates. Tauri has the most integrated first-party chain; other stacks assemble maintained bundlers, platform tools/rcodesign, and Velopack.

1. Finish the accessibility map: fund iced’s AccessKit integration. The tracking issue is iced#552 (open since 2020); the live draft PR #3111 demonstrates VoiceOver on one limited Button/Text example; the most complete community attempt, PR #3281, was closed unmerged in Mar 2026. System76’s fork ships a11y today via pop-os/iced. Upstream integration would close the baseline gap in this sample, but still requires widget semantics, adapter QA, maintenance, and upstream acceptance; Floem and GPUI product readiness remain separate gaps.
2. De-GTK Linux shell integration. Today muda menubars need a GTK window and cannot attach to a plain winit window, tray-icon needs a parallel GTK event loop, and global-hotkey is X11-only; winit has no menu/tray API (winit#403, #3108). Integrating existing Rust portal/SNI/DBusMenu implementations into maintained winit-compatible facades would improve menus/tray/hotkeys for every winit-based framework — and would remove part of the remaining rationale for the tao fork (tao#509, wry#1014).
3. Explore fontique interoperability for cosmic-text. fontdb has had no release since Oct 2024 and this audit found no announced maintainer succession; cosmic-text uses it and is a significant consumer in this sample. Slint already made this exact migration (slint#9564, 1.14) to fontique. A migration or adapter could reduce duplicate font discovery/fallback work, subject to maintainer and compatibility review.
4. Sustainability grants for AccessKit and rcodesign. AccessKit has concentrated recent public authorship, and the 2023–24 Sovereign-Tech-Fund-backed work administered via GNOME was mostly wrapped up (GNOME STF report). This audit identified no later direct institutional AccessKit grant; visible support includes personal GitHub Sponsors. rcodesign — the principal open-source Rust-native cross-platform implementation found — has concentrated maintenance and no release since Nov 2024.
5. Bless a framework-neutral packager. Non-Tauri apps lack one equally integrated bundle + sign + runtime-update chain: cargo-packager had current commits as of June 23, 2026, but its latest release was 0.11.8 from November 2025, cargo-bundle is minimal, dist is CLI-shaped. Improve a shared composition around cargo-packager, or standardize on Velopack (official Rust crate) + rcodesign.