When not to use IdealystIdealyst is a new frontier in app development — rich in potential, with the chance of choppy waters ahead. The framework is worth your time if that trade-off sounds like fun. If you're shipping something on a deadline where every edge case has to be already-solved, the rest of this page is for you.
WASM is still maturing on the edgesBrowser support for WebAssembly is universal and has been for years, but the toolchain around it — wasm-bindgen, wasm-split, the streaming-compile path, source-map fidelity in production builds — is still moving. Idealyst hits the edges of that toolchain more than a typical web app does. Most of the time it works flawlessly; when it doesn't, the failure mode can be obscure (we have a memory in this codebase about a stack-overflow that looked like a wasm-bindgen externref bug for weeks before the real cause turned up).If your team doesn't have appetite for occasionally getting your hands dirty in a wasm trap or a compiler regression, that's a reasonable reason to wait.
Rust is a learning curveMany web developers haven't written Rust before, and the ownership / lifetime model is a real intellectual investment to pick up. The framework has been designed to keep authoring-surface ergonomics close to React's mental model — components, props, signals, JSX-ish syntax — but the language underneath is still Rust, and it will hold you to its rules.If most of your team is more comfortable in TypeScript than in Rust, factor in the ramp time. (The flip side: once they're past it, most of the runtime classes of bug that web frameworks ship with stop existing.)
WASM bundle sizeAn Idealyst web build ships a WASM binary that's heavier than a hand-tuned pure-JS bundle. Even with aggressive code splitting and SSR, the framework's runtime is in the few-hundred-KB range compressed. If your traffic comes in on cold loads over constrained networks and every kilobyte matters, this is a real cost to weigh.WASM bundle size is one of the most active areas of focus right now, and ideas / PRs from the community are welcome — if you have a take on how to shrink it further, the GitHub discussions are open:https://github.com/IdealystIO/idealyst-native/discussions Treat it like new frontier territoryNone of this is meant to talk you out of trying it. The framework already ships real apps to real platforms, and the team behind it (and the issue tracker behind it) is responsive. But the promise of "truly cross-platform native" is a frontier promise, not a settled one. Go in with that framing and the rough edges become interesting instead of frustrating.