Links
Badges
Forums
Designing is easy. Translating that design into a state machine is a nightmare.
The absolute worst part of frontend development is trying to animate changing data.
If a WebSocket pushes new data to your dashboard chart while an existing transition is still running... what happens? Usually, it completely breaks the React state, skips a frame, or the numbers just snap abruptly. Writing robust unmount/remount logic and handling interrupted animations (with Framer Motion or GSAP) for an entire dashboard is awful. It turns a "fun UI task" into a multi-day state management nightmare.
That's why we built ExodeUI. Our engine natively understands state machines and data logic.
The designer builds the visual logic in the .exode file. You, the developer, just throw raw JSON at our custom runtime (built natively in WASM). The Engine handles the data parsing, safely cancels old transition states, calculates physics-based interpolation, and renders the new data points autonomously, at 120fps. No React state syncing. No glue code.
What do you use for complex, stateful UI animations? (Lottie/Rive aren't cutting it for us)
Lottie is fantastic for simple loaders, and Rive is great for interactive icons. But when it comes to whole-app screens like a complex credit card entry form with validation logic, 3D-like flips, and dynamic API data these tools often fall short.
We're building ExodeUI to handle "Complex Application Logic" directly in the UI file. It has built-in LogicNodes and StateMachines, meaning the developer just feeds JSON data to the runtime, and the UI handles the entire interaction autonomously.
For the frontend engineers (and technical designers) here: How are you currently handling complex, multi-state UI animations that require logic and data binding? Are you hand-coding all of it in React/Framer Motion, or is there a better workflow we are missing?