Dioxus is a portable, performant, and ergonomic framework for building cross-platform user interfaces in Rust.
fn app(cx: Scope) -> 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.
- Desktop apps running natively (no Electron!) in less than 10 lines of code.
- Incredibly ergonomic and powerful state management.
- Comprehensive inline documentation - hover and guides for all HTML elements, listeners, and events.
- Extremely memory efficient - 0 global allocations for steady-state components.
- Multi-channel asynchronous scheduler for first-class async support.
- And more! Read the full release post here.
All examples in this repo are desktop apps. To run an example, simply clone this repo and use cargo run --example XYZ
cargo run --example EXAMPLE
Tutorial | Web | Desktop | SSR | Mobile | State |
---|---|---|---|---|---|
File Navigator (Desktop) | WiFi scanner (Desktop) | TodoMVC (All platforms) | E-commerce w/ Tailwind (SSR/LiveView) |
---|---|---|---|
![]() |
![]() |
![]() |
![]() |
See the awesome-dioxus page for a curated list of content in the Dioxus Ecosystem.
TypeScript is a fantastic addition to JavaScript, but it's still fundamentally JavaScript. TS code runs slightly slower, has tons of configuration options, and not every package is properly typed.
In contrast, Dioxus is written in Rust - which is almost like "TypeScript on steroids".
By using Rust, we gain:
- Static types for every library
- Immutability by default
- A simple and intuitive module system
- Integrated documentation (
go to source
actually goes to source) - Advanced pattern matching
- Clean, efficient, composable iterators
- Inline built-in unit/integration testing
- Best-in-class error handling
- Powerful and sane standard library
- Flexible macro system
- Access to
crates.io
Specifically, Dioxus provides us many other assurances:
- Proper use of immutable datastructures
- Guaranteed error handling (so you can sleep easy at night not worrying about
cannot read property of undefined
) - Native performance on mobile
- Direct access to system IO
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.
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.
- You need a Send+Sync UI solution (Dioxus is not currently ThreadSafe)
Dioxus primarily emphasizes developer experience and familiarity with React principles.
- Yew: prefers the elm pattern instead of React-hooks, no borrowed props, supports SSR (no hydration).
- Percy: Supports SSR but less emphasis on state management and event handling.
- Sycamore: VDOM-less using fine-grained reactivity, but lacking in ergonomics.
- Dominator: Signal-based zero-cost alternative, less emphasis on community and docs.
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 |
Effects | β | β | Run effects after a component has been committed to render |
Portals | π | β | Render nodes outside of the traditional tree structure |
Cooperative Scheduling | π | β | Prioritize important events over non-important events |
Server Components | π | β | Hybrid components for SPA and Server |
Bundle Splitting | π | β | Efficiently and asynchronously load the app |
Lazy Components | π | β | Dynamically load the new components as the page is loaded |
1st class global state | β | β | redux/recoil/mobx on top of context |
Runs natively | β | β | runs as a portable binary w/o a runtime (Node) |
Subtree Memoization | β | β | skip diffing static element subtrees |
High-efficiency templates | π | β | rsx! calls are translated to templates on the DOM's side |
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 |
- β = implemented and working
- π = actively being worked on
- π = not yet implemented or being worked on
- β = not sure if will or can implement
This project is licensed under the MIT license.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Dioxus by you, shall be licensed as MIT, without any additional terms or conditions.