The flow
Flows, not screenshots.
Screens wired together in the order somebody actually walked them — recorded from the session rather than drawn afterwards from memory.
01
From the thing you clicked
Each wire leaves the exact element that was pressed, so a flow is a record of what happened rather than a diagram of what was intended.
- The real element — a wire starts at the button that was actually clicked, not at the edge of a box.
- Not a sketch — the order comes out of the recording, so it cannot drift from what the app does.
- Screens in sequence — laid out in the order they were walked, not in the order somebody filed them.
02
Signposts, not lines
When a flow forks, it renders as a signpost with one wire per choice — so a branch is never quietly flattened into a straight line.
- One wire per choice — each branch gets its own route out of the fork.
- Nothing implied — a path that was never taken does not appear as though it was.
03
Pass beside pass
The next iteration lands next to the last one, so what changed between two rounds of testing is visible rather than remembered.
- Side by side — round two sits beside round one instead of replacing it.
- What changed — the difference is something you can see, not something you have to reconstruct.
- Tests out of it — a recorded journey can be turned into a runner-backed end-to-end suite.