At work we have an interactive guided process/wizard that is currently implemented with an unwieldy low-code engine. I've been replacing this with a Node API that uses XState to encode process states. The API endpoints wait for XState to enter a 'ready' state (calling out to external services in the process), then pass meta properties of the current state back to the client.
One nice thing about this is that I can translate the existing low-code model into XState more or less directly. And the state machine can be rendered as a process flow diagram using viz tools in the Xstate ecosystem or some straightforward custom tooling.
I love that use-case. We have plenty of developers & companies using XState on the backend, and one of our main goals for XState v5 was to enable more backend use-cases, with custom & composable actor logic, deep persistence, inspection APIs, and actor-first statechart features for modeling more complex actor-actor interaction.
Ultimately, we'd love to be an open-source alternative to AWS Step Functions.
At work we have an interactive guided process/wizard that is currently implemented with an unwieldy low-code engine. I've been replacing this with a Node API that uses XState to encode process states. The API endpoints wait for XState to enter a 'ready' state (calling out to external services in the process), then pass meta properties of the current state back to the client.
One nice thing about this is that I can translate the existing low-code model into XState more or less directly. And the state machine can be rendered as a process flow diagram using viz tools in the Xstate ecosystem or some straightforward custom tooling.