The plain-English version
An arrangement where state drives the interface and user events request state changes through a defined path.
Why it matters
It makes ownership and transitions easier to inspect and test.
Let’s make it click
The screen displays task state, emits a CompleteTask event, and later receives the resulting state.
Vibe Bro’s heads-up
Multiple unrelated components mutating the same state directly can undermine the pattern even if the project uses its terminology.
The docs behind it
Documentation links checked .
Editorial review · October 28, 2026
Supported: Android explicitly describes state flowing down and events flowing up. The example is an application of that pattern.