Put a clj-statechart somewhere in my mobile app! Learn from the process.
Certainly better for orchestrating interesting behaviour when compared with simple re-frame handlers. The registration process has lots of corner cases. More of those are covered. The code is by rights more maintainable. I was able to refactor as I expanded it with confidence. So lots of wins there.
Actions tend to be hardcoded to a specific use case. Primarily because they have to dispatch an event which the fsm expects.