The journey map

Navigation is how people experience a product, so it is the first reading of the map. The journey map starts from a top-level flow and lets you drill all the way down to a single screen.

Each flow is a playlist: an ordered list of views and sub-flows, with conditions and junctions where the path forks. Sub-flows show up as collapsed cards you can expand, so a big product reads like chapters until you want the pages.

The composition links are generated from the playlist itself. That means a flow cannot lie about its own screens: reorder the playlist and the map follows.

Screens also carry what they talk to. API calls appear right on the view card, with an arrow telling you whether the screen sends the request or the server pushes to it, and the detail panel lists the data it displays.