2 hours and not a single comment yet?! At one point, Statecharts seemed to be getting traction in the frontend/UI ecosystem, albeit tiny traction. Leveraging state machines (and particular Statecharts, which is basically compositions of state machines) for UI interactions makes complex flows so much easier to reason about! However, seems the traction eventually disappeared for unknown reasons, sadly.

If this is the first time you're hearing about Statecharts, I highly recommend the book "Constructing the user interface with statecharts" by Ian Horrucks (https://archive.org/details/isbn_9780201342789/mode/2up) which yes, is from 1999, but probably the best introduction for how to actually apply and use Statecharts.

▲

davidkpiano 2 hours ago | parent | next [-]

Statecharts are still getting some traction! XState has over 4 million weekly npm downloads. Animation tools like Rive & LottieFiles heavily advertise state machine capabilities. AI tools like LangGraph are built on state machine foundations.

It'll take some time for those apps/tools to realize the full potential of statecharts, but it's a good start.

	▲	embedding-shape an hour ago \| parent [-]
		No doubt state machines are as popular as they've always been :) I was talking about statecharts specifically, not just state machines in general.

▲

sph 2 hours ago | parent | prev [-]

> Statecharts seemed to be getting traction in the frontend/UI ecosystem

Yes, I stumbled upon statecharts checking out this Godot plugin: https://github.com/derkork/godot-statecharts

▲

brandensilva 2 hours ago | parent [-]

I've been wanting to code up an AI flavor wrapper around state machines that will be visible as an AI generated image in PRs.

I often have my AI code output one just to make sure my logic feels more sound. Along with mermaid charts if I need to toy around or drop into stately for more power.

	▲	ZihangZ an hour ago \| parent [-]
		Small caution from using agents here: the useful chart is the one generated from code, tests, or traces, not the one the model draws from its own explanation. I've had models produce very reasonable Mermaid diagrams that matched the intended design but not the actual program. It felt helpful until I realized I was reviewing the plan twice and the implementation zero times. For PRs I'd rather render the diagram from the executable state machine itself — at least then drift in the chart means drift in behavior, and you can't review one without the other.