← All Workshops
MudEngine Part 10: Desktop with Blitz
Step 11 / 12
What the future looks like
The Blitz renderer represents the long-term vision for Dioxus native rendering: a pure-Rust HTML/CSS engine with no browser dependencies.
Roadmap
From the Blitz project page, the team's priorities are:
- Near term — complete CSS support (animations, transitions, filters), improve text shaping and layout, fix accessibility
- Medium term — custom widget system (canvas, WebGL-like rendering via WGPU), embeddable Blitz in other Rust apps
- Long term — replace the system WebView as the default Dioxus desktop renderer
Why this matters for the MUD
A pure-Rust renderer means:
- No system dependencies — no
libwebkit2gtk, no WebKit framework. Your MUD binary runs on any platform with GPU support. - Faster startup — no browser engine to spin up; the window opens as fast as winit creates it.
- Full control — you can render custom 2D graphics (maps, effects) directly on the GPU through the same rendering pipeline.
- Smaller bundles — no Chromium/WebKit embedded in your app.
Try it alongside the web version
The same codebase now runs in three modes:
All three share the same game world through the server. Players in the browser, the wry desktop app, and the Blitz native app can explore the MUD together.
🔍 Renderer modes
| Mode | Command | Renderer |
|---|---|---|
| Web (browser) | dx serve | Browser DOM (WASM) |
| Desktop (wry) | dx serve --desktop | System WebView |
| Desktop (Blitz) | cargo run | WGPU/Vello (this part) |
Step 11 / 12