Guide
Why a card beats a recipe page at the stove
Recipe pages are written for reading. Cooking is not reading — it’s keeping state with wet hands. That mismatch is the whole argument.
The scroll tax
A standard recipe page separates what you need from what you do: ingredients at the top, instructions below, and a thumb-scroll between them every time a step says “add the sugar mixture” and you need to remember which sugars those were. Every scroll is a chance to lose your line; every lost line is a re-read with flour on the screen.
The state problem
Mid-recipe, the question is rarely “what does step six say.” It’s “did the vanilla already go in?” Prose can’t answer that at a glance because prose has no geometry. A tabular card does: if the vanilla’s row has already merged into the cell you’re working from, it’s in. If its row is still running clean, it isn’t. The card is the state.
One glance, whole dish
Because every ingredient is a row and every action is a cell placed where its inputs meet, the entire dish assembles left to right in a single view — the dry bowl forming below the wet, the merge, the fold, the bake at the far edge. Tap any cell and its full lineage lights up. No page can do that, because pages encode order, not structure.
Where pages still win
Honesty requires the other column: pages carry headnotes, photos, technique asides, and the writer’s voice — things a card deliberately compresses away. The card doesn’t replace the page; it’s the page’s stove-side translation. Read the page once on the couch; cook from the card at the counter, with cook mode running the timers.
Try the argument yourself
Convert something you’ve cooked twenty times at the generator. The test isn’t whether the card looks clever — it’s whether, at minute twelve with the onions going, you stop scrolling.