Actually, if you lay things out properly and use the appropriate wrappers to manage @State, you don't need a state machine.

Take for instance if you're gonna have a Form, with 2 buttons, with that Form, are you gonna have "State" mechanics for when the buttons on just that form are clicked or edited?

Hell no, well at least not with some funky home made StateMachine class, and one that's an Actor especially.

You go as deep and as far as you can and put the Form in it's own View, and if you can you put the buttons in their own "Content View" of applicable type you do that.

Then at the last minute you add @State or @StateObject etc, to variables you want to use to monitor JUST the STATE of "THAT" View, and get the hell out of there...

Geesh