A field guide is a search engine with arrows

Take it from someone who annotates screenshots for a living: a field guide is an interface. The plate is a grid view. The arrows are annotations.

In the 1930s, Roger Tory Peterson made the decisive design move: he stopped painting birds beautifully and started painting them distinguishable. His little arrows point at the one mark that separates two similar species. That is a diff view, printed in ink.

Then there's the sort order. Field guides refuse alphabetical and cluster species by relationship instead, so the two sparrows you keep confusing sit on facing pages. Nearest-neighbor search, shipped decades before anyone named it.

Even the failure states are designed. Peterson's warbler section famously ran under the heading "Confusing Fall Warblers" — an error message that admits the system has limits. Most software never says that part out loud.

And credit where due: the format is generous to amateurs. You need zero jargon to use one, because the book carries the taxonomy for you. Those are good defaults.

My quibble with birding apps — opinion, not data — is that they nail lookup and fumble compare. When the side-by-side view is three taps deep, the 1934 book is quietly winning.

The transferable lesson for anyone drawing interfaces: don't annotate the object, annotate the delta. Redlines, review comments, design pins — all of it is Peterson's arrow wearing a different tool belt.

One last plea: look at the range maps again. Small multiples, a legend, a color scale. Nature shipped solid data viz, and we're still doing breathless takes about dashboards.