RUST APPLICATION PLATFORM
One model.
Every surface.
Build, test, package, and release production apps in Rust—from native windows and mobile devices to the web, terminal, and server.
A
Android
◎
Web
●
iOS
L
Linux
M
macOS
⊞
Windows
RUST APPLICATION PLATFORM
One model.
Every surface.
Build, test, package, and release production apps in Rust—from native windows and mobile devices to the web, terminal, and server.
A
Android
◎
Web
●
iOS
L
Linux
M
macOS
⊞
Windows
One framework. Nine targets.
Build the product once. Let every surface feel at home.
Fission keeps the product model shared while each target owns the details that make it belong: windows, input, packaging, accessibility, lifecycle, and distribution.
Build
One product model
State, reducers, widgets, services, and design systems stay together in Rust.
Learn the model →
Render
A real UI pipeline
Deterministic layout, semantics, input, paint, and GPU rendering stay inspectable.
See the pipeline →
Reach
Every surface
Native desktop, mobile, Web, Terminal, Static site, and SSR are first-class targets.
Browse targets →
Ship
A complete release path
Test, package, sign, publish, roll out, and keep the receipts from one toolchain.
See the release path →
Visual proof
A UI framework should be able to show, not merely tell.
Fission Charts exercises the same renderer, layout system, themes, interaction model, and screenshot tooling as the rest of the framework—across analytical dashboards, live data, maps, networks, finance, and 3D-ready scenes.
Why the model stays stable
The important boundaries stay visible.
Fission is strict about where state changes happen, where host work starts, and how rendering is produced.
fn reduce(state: &mut GlobalState, action: Action) {
match action {
Action::Inc => state.count += 1,
Action::Reset => state.count = 0,
}
}
01
Plain Rust data stays in charge.
Product truth is not hidden inside widgets or host callbacks.
State
02
Every durable change has a named cause.
Typed actions and reducers keep behavior reviewable and testable.
Reducers
03
Outside work has an explicit path.
Files, timers, authentication, and services do not leak through rendering.
Host work
04
Layout and paint stay inspectable.
Tests and diagnostics can inspect structure, semantics, and paint order directly.
Render
Next
Start with one screen. Ship it everywhere.
Build your first Fission app, inspect the architecture, or explore the crates extending the framework.