We're using Xstate for state management instead of Redux and the like and it fits well for this purpose - chiefly I have an idiomatic way of defining which inputs are appropriate in different contexts.
The visualizer is a major selling point - especially if I need to explain something to non-dev people or someone new to the concept.
The one downside is that building state machines is an art in and of itself and I had to throw away my first implementation in favour of something simpler once I got the hang of it.
The visualizer is a major selling point - especially if I need to explain something to non-dev people or someone new to the concept.
The one downside is that building state machines is an art in and of itself and I had to throw away my first implementation in favour of something simpler once I got the hang of it.