Seems weird. You stopped "updates" while you're pressing the button? What "updates" could have occurred during the 1/10 of a second button press?

Second, in SwiftUI state is the source of truth for the app (or a piece of UI). Change state, and that triggers an update cycle where SwiftUI diffs the view changes and then the app updates to reflect those changes.

All in all it feels a bit more nailed down than Flutter, which always seemed like it couldn't really figure out how it wanted to manage things and so ended up with dozens of state management packages, each one proclaiming to be the way,

And, honestly, the problem sounds like a fundamental lack of understanding of how a given mechanism was supposed to work, which in turn lead to the creation of yet another state management package.

Cue the appropriate XKCD comic...