🌗🚀 Dioxus

Frontend that scales.

API Docs | Website | Examples

Dioxus is a portable, performant, and ergonomic framework for building cross-platform user experiences in Rust.

fn App((cx, props): Component<()>) -> Element {
    let mut count = use_state(cx, || 0);

    cx.render(rsx!(
        h1 { "High-Five counter: {count}" }
        button { onclick: move |_| count += 1, "Up high!" }
        button { onclick: move |_| count -= 1, "Down low!" }
    ))
};

Dioxus can be used to deliver webapps, desktop apps, static sites, liveview apps, mobile apps (WIP), and more. At its core, Dioxus is entirely renderer agnostic and has great documentation for creating new renderers for any platform.

If you know React, then you already know Dioxus.

Unique features:

• The most ergonomic and powerful state management of any Rust UI toolkit.
• Desktop apps running natively (no Electron!) in less than 10 lines of code.
• Starting a new app takes zero templates or special tools - get a new app running in just seconds.
• Incredible inline documentation. Supports hover and guides for all HTML elements, listeners, and events.
• Custom bump-allocator backing for all components. Nearly 0 allocations for steady-state components.
• Multithreaded asynchronous coroutine scheduler for powerful async code.
• And more! Read the full release post here.

Get Started with...

Web	Desktop	Mobile	State	Docs	Tools

Examples:

File Navigator (Desktop)	Bluetooth scanner (Desktop)	TodoMVC (All platforms)	Widget Gallery

See the awesome-dioxus page for a curated list of content in the Dioxus Ecosystem.

Why?

TypeScript is a great addition to JavaScript, but comes with a lot of tweaking flags, a slight performance hit, and an uneven ecosystem where some of the most important packages are not properly typed. TypeScript provides a lot of great benefits to JS projects, but comes with its own "tax" that can slow down dev teams. Rust can be seen as a step up from TypeScript, supporting:

• static types for all libraries
• advanced pattern matching
• immutability by default
• clean, composable iterators
• a good module system
• integrated documentation
• inline built-in unit/integration testing
• best-in-class error handling
• simple and fast build system (compared to WebPack!)
• powerful standard library (no need for lodash or underscore)
• include_str! for integrating html/css/svg templates directly
• various macros (html!, rsx!) for fast template iteration

And much more. Dioxus makes Rust apps just as fast to write as React apps, but affords more robustness, giving your frontend team greater confidence in making big changes in shorter time. Dioxus also works on the server, on the web, on mobile, on desktop - and it runs completely natively so performance is never an issue.

Parity with React

Dioxus is heavily inspired by React, but we want your transition to feel like an upgrade. Dioxus is most of the way there, but missing a few key features. This parity table does not necessarily include important ecosystem crates like code blocks, markdown, resizing hooks, etc.

Feature	Dioxus	React	Notes for Dioxus
Conditional Rendering	✅	✅	if/then to hide/show component
Map, Iterator	✅	✅	map/filter/reduce to produce rsx!
Keyed Components	✅	✅	advanced diffing with keys
Web	✅	✅	renderer for web browser
Desktop (webview)	✅	✅	renderer for desktop
Shared State (Context)	✅	✅	share state through the tree
Hooks	✅	✅	memory cells in components
SSR	✅	✅	render directly to string
Component Children	✅	✅	cx.children() as a list of nodes
Headless components	✅	✅	components that don't return real elements
Fragments	✅	✅	multiple elements without a real root
Manual Props	✅	✅	Manually pass in props with spread syntax
Controlled Inputs	✅	✅	stateful wrappers around inputs
CSS/Inline Styles	✅	✅	syntax for inline styles/attribute groups
Custom elements	✅	✅	Define new element primitives
Suspense	✅	✅	schedule future render from future/promise
Integrated error handling	✅	✅	Gracefully handle errors with ? syntax
NodeRef	✅	✅	gain direct access to nodes
Re-hydration	✅	✅	Pre-render to HTML to speed up first contentful paint
Jank-Free Rendering	✅	✅	Large diffs are segmented across frames for silky-smooth transitions
Cooperative Scheduling	✅	✅	Prioritize important events over non-important events
Runs natively	✅	❓	runs as a portable binary w/o a runtime (Node)
1st class global state	✅	❓	redux/recoil/mobx on top of context
Subtree Memoization	✅	❓	skip diffing static element subtrees
Compile-time correct	✅	❓	Throw errors on invalid template layouts
Heuristic Engine	✅	❓	track component memory usage to minimize future allocations
Fine-grained reactivity	🛠	❓	Skip diffing for fine-grain updates
Effects	🛠	✅	Run effects after a component has been committed to render

• ✅ = implemented and working
• 🛠 = actively being worked on
• 👀 = not yet implemented or being worked on
• ❓ = not sure if will or can implement

FAQ:

Aren't VDOMs just pure overhead? Why not something like Solid or Svelte?

Remember: Dioxus is a library - not a compiler like Svelte. Plus, the inner VirtualDOM allows Dioxus to easily port into different runtimes, support SSR, and run remotely in the cloud. VDOMs tend to more ergonomic to work with and feel roughly like natural Rust code. The overhead of Dioxus is extraordinarily minimal... sure, there may be some overhead but on an order of magnitude lower than the time required to actually update the page.

Isn't the overhead for interacting with the DOM from Wasm too much?

The overhead layer between Wasm and JS APIs is extremely poorly understood. Rust web benchmarks typically suffer from differences in how Rust and JS cache strings. In Dioxus, we solve most of these issues and our JS Framework Benchmark actually beats the Wasm Bindgen benchmark in many cases. Compared to a "pure vanilla JS" solution, Dioxus adds less than 5% of overhead and takes advantage of batched DOM manipulation.

Aren't Wasm binaries too huge to deploy in production?

Wasm binary sizes are another poorly understood characteristic of Rust web apps. 50kb of Wasm and 50kb of JS are not made equally. In JS, the code must be downloaded first and then JIT-ted. Just-in-time compiling 50kb of JavaScript takes a while which is why 50kb of JavaScript sounds like a lot! However, with Wasm, the code is downloaded and JIT-ted simultaneously through the magic of streaming compilation. By the time the 50kb of Rust is finished downloading, it is already ready to go. Again, Dioxus beats out many benchmarks with time-to-interactivity.

For reference, Dioxus hello-world clocks in at around 70kb gzip or 60kb brotli, and Dioxus supports SSR.

Why hooks? Why not MVC, classes, traits, messages, etc?

There are plenty Rust Elm-like frameworks in the world - we were not interested in making another! Instead, we borrowed hooks from React. JS and Rust share many structural similarities, so if you're comfortable with React, then you'll be plenty comfortable with Dioxus.

Why a custom DSL? Why not just pure function calls?

The RSX DSL is barely a DSL. Rustaceans will find the DSL very similar to simply assembling nested structs, but without the syntactical overhead of "Default" everywhere or having to jump through hoops with the builder pattern. Between RSX, HTML, the Raw Factory API, and the NodeBuilder syntax, there's plenty of options to choose from.

What are the build times like? Why on earth would I choose Rust instead of JS/TS/Elm?

Dioxus builds as roughly as fast as a complex WebPack-TypeScript site. Compile times will be slower than an equivalent TypeScript site, but not unbearably slow. The Wasm compiler backend for Rust is very fast. Iterating on small components is basically instant and larger apps takes a few seconds. In practice, the compiler guarantees of Rust balance out the rebuild times.

What about Yew/Seed/Sycamore/Dominator/Dodrio/Percy?

• Yew and Seed use an Elm-like pattern and don't support SSR or any alternate rendering platforms
• Sycamore and Dominator are more like SolidJS/Svelte, requiring no VDOM but has less naturally-Rusty state management
• Percy isn't quite mature yet
• Dodrio is the spiritual predecessor of Dioxus, but is currently an archived research project without the batteries of Dioxus

How do the mobile and desktop renderers work? Is it Electron?

Currently, Dioxus uses your device's native WebView library to draw the page. None of your app code is actually running in the WebView thread, so you can access system resources instead of having to go through something like NodeJS. This means your app will use Safari on macOS/iOS, Edge (Chromium) on Windows, and whatever is the default Web Browser for Linux and Android. Because your code is compiled and running natively, performance is not a problem. You will have to use the various "Escape Hatches" to use browser-native APIs (like WebGL) and work around visual differences in how Safari and Chrome render the page.

In the future, we are interested in using Webrenderer to provide a fully native renderer without having to go through the system WebView library. In practice, Dioxus mobile and desktop are great for CRUD-style apps, but the ergonomic cross-platform APIs (GPS, Camera, etc) are not there yet.

Why NOT Dioxus?

You shouldn't use Dioxus if:

• You don't like the React Hooks approach to frontend
• You need a no-std renderer
• You want to support browsers where Wasm or asm.js are not supported.

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Pipette by you, shall be licensed as MIT, without any additional terms or conditions.