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.
(The only exception I can think of is 'evennn'. e.g. Bob and Sue are at a dinner party with friends. Bob tells everyone that he likes all vegetables. Sue knows he doesn't like broccoli, so she nudges Bob and says "evennn...?". This makes sense if 'even' in fact contains a syllabic nasal consonant rather than schwa: /'ivn=/.)
That said, I don't think it's a big deal!