☰
Home
IdealystOne codebase, native everywhere.
FeaturesOverviewCross-platformHigh performanceType safetyServer-side renderingServer functionsCode splittingInstructionsInstall the CLIQuickstartCore conceptsWhy RustReferenceDemoBackendsRobot & MCPRoadmapFurther reading
Dark mode
One codebase, native everywhere.Idealyst is a reactive UI framework that runs natively on every target. The platform implementations are extensible by design: use the ones we ship, or write your own to target anything else.
Install the CLI →Quickstart
Build an iOS, Web, and Android app in five commands.The same `app()` function runs unchanged on web, iOS, and Android. The CLI handles the build pipeline and the per-target wrappers — your code stays platform-agnostic.
# Install the CLI from the GitHub repo
cargo install --git https://github.com/IdealystIO/idealyst-native idealyst-cli

# Scaffold a project and run it
idealyst new my-app
cd my-app
idealyst dev          # hot-reload web preview at http://localhost:8080
idealyst run ios      # build + boot in the iOS simulator
idealyst run android  # build + install on emulator or device
What makes it different
Truly cross-platformIdealyst comes with premade platform implementations and is designed to extend to any platform through the Backend Interface.Read more →
Reactive without a virtual DOMFine-grained signals mutate exactly the primitives that depend on them. No tree-diffing, no reconciliation, no re-render cycle.Read more →
Native-class performanceOn every target, idealyst drives the platform's own toolkit directly — not a re-rendered abstraction over the top.Read more →
No bundled runtimeWASM for the web, native binaries everywhere else. No JavaScript engine, no platform VM, no embedded runtime to ship.Read more →
AI-forwardDocumentation generators and MCP support are built in. As you define components, your LLMs can read live metadata to enrich their context.Read more →
How idealyst comparesIf you've shipped real apps in Electron, React Native, Dioxus, Flutter, or a JS framework, you've probably hit some of the same friction that motivated this project. Honest framework-by-framework comparisons (including "when not to use Idealyst") live on their own page.See the comparisons →
IdealystOne codebase, native everywhere.
ProjectGitHubIssuesDiscussions
ResourcesQuickstartCore conceptsWhy RustBackends
© Idealyst 2026