Sparse layouts levy a paging and scrolling tax
Aliases: scrolling tax · paging cost · sparse UI
What it is
Each setting is a card with one field and 48 px of padding; twelve settings is a long slide. “Notifications” and “Privacy” never share the screen, so whether two switches interact is a memory problem. Sparse layouts bill you in pages and scrolls — a comparison task chopped into recall.
This leaf does not ask whether the air pleased someone. It only keeps the books: every empty region is an object that left the viewport.
Why it happens
Working memory will not hold the items that rolled off. Comparing, pairing, finding extrema all want candidates co-present; one scroll turns the last item into a token to be recalled. Scrolling also costs pointing and settling, and those times grow linearly on a long list. Marketing pages buy rhythm with air; that is narrative, not comparison. Move narrative density into a tool, and every option change is a re-orientation.
Cards, large illustrations, repeated block titles all cut how many items can stand side by side. Cut the count, and a table that should have been a glance becomes a sequence of separate scenes.
Where it stops holding
Story, brand, first-run coaching: scrolling is cadence, sparse is a device. Long-form reading needs measure and paragraph breaks; that is type, not a “sparse UI.” Small screens physically hold less, and some air is readability; even then, making one setting a full-screen hero is still a scroll tax.
If the task was never comparison (look at one image, press one button), holding fewer objects is free. The tax appears when things that must be seen together are split across screens.
Applying it
- List fields that must be co-visible to get the task right (two switches, price and stock, filters and the result count). Keep them on-screen at the target width.
- Prefer list rhythm on tool surfaces, not hero-card rhythm. Spend air between groups, not around every row.
- How to check: pick a five-way comparison (cheapest row, three most overdue). From the top of the page to an answer, count scrolls and whether an item had to be held in mind. More than one scroll and a memory load: pack or switch to a table until the five fit in one view. Do not veto the packing because it “feels less premium.”