Compact Interfaces Are Not Virtuous

I work in Cursor every day. I open a repo before breakfast, accept agent diffs between calls, and keep three files visible on a thirteen-inch screen. I am supposed to be the audience for its condensed UI layout. I am not convinced. The agent panel type got smaller until I lean forward to read a diff summary. Apple recommends a minimum of eleven points for legible body text at typical viewing distance. apple-design-tips Accept, Reject, and Apply sit in a row of touch targets sized for a precise trackpad click, not a tired thumb on a laptop hinge. Mice offer high precision; fingers offer low precision and obscure the screen. nngroup-mouse-vs-fingers The sidebar icon strip is a guessing game unless you already memorised the glyph. After each compact refresh I bump the zoom back up. That is not mastery. That is tax.

Last month a client sent a screenshot of that same editor and three words in the subject line: Make it look like this. Not the model. Not the retrieval. The chrome. Tighter panels. Flatter buttons. The kind of interface that says we ship software before anyone has read a line of copy.

They wanted virtue by association. If their dashboard resembled an IDE, the AI workflow would inherit the seriousness of a compiler. Their product was a clinician review queue, not a codebase. That is a category error, and it is spreading faster than component libraries can ship new variants.

Why does every new AI dashboard look like a cramped IDE when most users are not shipping code? Because we have confused two different ideas. Information density is more useful signal per glance for someone who already knows the schema. Column headers, keyboard shortcuts, status colours that repeat all day: those earn their pixels. Visual compression is what happens when you shrink padding, type size, and hit targets to look efficient without adding signal. One helps experts move. The other helps demos photograph well on a sixteen-inch MacBook. Screen size is a communication channel with finite capacity, not a licence to shrink everything. nngroup-scaling-ui Extraneous visual clutter strains working memory without adding capability. nngroup-cognitive-load Conflating the two is how we ended up with approval queues that look like terminals and behave like traps.

Density Is a Skill IDE Users Earned

Visual Studio Code did not become the default developer surface because someone hated whitespace. It earned density over years of iteration, not a sprint labelled polish. The activity bar packs dozens of extensions into a strip you learn once. The side panel holds file trees and search results you summon by muscle memory. The command palette is the escape hatch: you do not hunt tiny icons when you can type `> refactor`. vscode-command-palette Cursor inherits that lineage. I jump to definition, review a diff inline, and accept a suggestion without treating every pixel as a new decision. When I need a refactor, I type a command instead of hunting a menu. That keyboard contract is half the density story. Expert interfaces need accelerators invisible to novices. nngroup-accelerators The other half is repetition: the same file tree, the same status colours, the same panel layout until my hands know where everything lives.

That is information density with training wheels built in — and I am still on those wheels more often than I want to admit. Novice developers struggle in IDEs too, myself included, because the schema is not written on the glass. Icons arrive without labels. The palette only helps after someone else mentions it. Panels stay closed until you know the incantation. You are not stupid; the interface is betting you will repeat the same workflow until the bet pays off. nngroup-novice-vs-expert The difference is still the audience: people who opted into a profession that pays that tuition over years. Dashboards for clinicians, recruiters, and compliance officers are not that audience. The hype still rewards the look anyway. Founders pitch on laptops where every extra panel suggests feature depth. Registries like shadcn's Maia theme make tight padding the default aesthetic. Earned complexity arrives through progressive disclosure, not default compression. nngroup-progressive-disclosure On a gallery page, compact reads as modern. In a patient record, it reads as hurry up. I have sat in steering meetings and nodded when a CTO said compact felt serious. I knew better in the moment. I said nothing because the mock already matched the registry screenshot everyone had bookmarked. I had shipped my own site with the same Maia defaults the week before. That complicity is part of why I am writing this.

Cargo Cult Compression Looks Pro and Acts Amateur

There is an honest version of dense UI and a cosplay version. The honest version adds signal. Another sortable column when analysts compare cohorts. A second pane when lawyers redline contracts. A filter chip row when operators manage hundreds of incidents. The cosplay version subtracts space and calls it focus. I have watched teams import IDE spacing into surfaces that are mostly reading and consent. An AI suggestion list with Accept and Dismiss buttons the size of favicons. A chat transcript beside a settings drawer so narrow the scrollbar eats the prose. A review queue where each row is forty pixels tall. The mock used the compact table variant. Nobody asked what happens when someone taps with a gloved hand or reads on a cracked phone in a corridor.

This is not information density. Nothing new is visible. You have moved the same text closer together and hoped expertise would appear by osmosis. Jakob Nielsen has argued for decades that most interfaces should use available screen space rather than cram content into peepholes. nngroup-utilize-screen-space Maximising content-to-chrome ratio is not the same as maximising content on screen. nngroup-content-chrome-ratio Comprehension and tap accuracy degrade when we confuse smaller with clearer. Minimalist design means removing irrelevant elements, not shrinking relevant ones. nngroup-complex-heuristics Mobile-first responsive patterns do not generalise to desktop without task analysis. nngroup-mobile-first-not-mobile-only The shadcn Maia pattern is not the villain. In this repo we use `radix-maia` from the registry. Pill-shaped triggers carry `rounded-4xl`. Dropdown panels share the same radius. Popovers use `sideOffset={-4}` so the menu overlaps the button by four pixels instead of leaving a polite gap. Material Design 3 warns against applying density by default. material-density-default On a component gallery, that overlap reads as craft. On a consent screen, it reads as impatience. The harm is cargo culting: copying the visual rhythm of keyboard-heavy tools onto flows where the primary action is read, then decide. I have pasted Maia spacing into admin dashboards myself because the alternative looked dated in a Figma review. The date on the ticket mattered more than the task on the screen.

The Row She Meant to Dismiss

Leila was six months out of design school when she inherited the clinician review screen. Smart, meticulous, tired. The backlog said ship the compact variant before the conference demo. Marketing had already cut a screen recording with the tight layout. I reviewed the file and suggested one more pass on spacing. The launch date did not move. I signed off the tighter layout because the steering meeting already loved the compact screenshots. I told myself we could fix spacing in a later sprint. That is on me.

On the first remote user test, a nurse practitioner scrolled a list of AI-drafted notes. Each row showed a summary line and two actions: Accept and Edit. The compact table put those actions fourteen pixels tall. Touchscreen research recommends roughly one centimetre by one centimetre as a minimum physical target. nngroup-touch-target-size Microsoft guidance scales target size by how often a control is touched and how costly a miss would be. microsoft-target-consequence She meant to tap Edit. The row highlighted green. The note entered the chart. Leila went still on the call. The facilitator asked if she wanted to pause. She said no and kept watching. After the session she asked me, quietly, whether the compact variant was still mandatory for launch. I did not have a good answer. Nobody trained the model wrong. We trained the thumb wrong. FDA human-factors guidance treats use-related errors in device interfaces as design hazards to minimise. fda-hfe-guidance The agency frames human factors in medical device UI as a hazard-reduction discipline. fda-human-factors A 2024 systematic review links electronic health record interface design to clinician usability and medication safety. ehr-ui-safety-review A mis-click in an IDE might delete a local file with undo waiting. A mis-click in a clinical queue can enter text another human will treat as ground truth. I will not invent a prevalence statistic. One session is enough to see the stakes.

The Shoe That Looked Fast on the Shelf

Try buying running shoes half a size too small. The sleek profile looks faster in the shop mirror. The first kilometre feels fine. Your stride looks economical. By the third, your toes bruise against the cap. You shorten your gait. You lose the very speed the shoe promised on the shelf. You do not notice the trade until the task lasts longer than the fitting room.

Compact UI hype does the same thing to the eye. Tighter rows look decisive on a portfolio shot. Under real tasks, people squint, mis-tap, and double-check because the interface stopped feeling trustworthy. More visible options increase crowding and the chance of selecting the wrong one. nngroup-simplicity-vs-choice A recruiter approving a batch of AI summaries does not get faster because the table lost twelve pixels of row height. She gets slower because she no longer trusts the first tap. Trust is not a brand colour. It is whether the Accept button is larger than your uncertainty.

The Strongest Case for Cramped Pixels

Give the counterargument its full weight. Expert users stare at these tools eight hours a day. Whitespace is not neutral for them. It is rent. Traders learned to read Bloomberg terminals because every extra line of bids was money. Developers live in terminals where `git status` returns forty lines and they want to see them all without scrolling. Neither group approves patient notes between ward rounds. Fitts's law is real: movement time rises with distance and falls with target width. fitts-1954 For a skilled pointer user, shorter travel between generous targets is faster than wandering a sparse page. The W3C mobile accessibility task force proposed forty-eight pixels for coarse pointers and twenty-four for fine ones. w3c-proposed-target-size Screen estate on a train is scarce. A founder on a thirteen-inch laptop has every reason to reclaim pixels. I am that founder on some days. I am also the consultant who signed a compact clinician screen because the demo date was fixed. If your users are power users, the calculus changes. They repeat the same actions hundreds of times a week. Respecting their time can mean tightening the grid, hiding chrome, and trusting shortcuts. Calling every compact layout lazy would insult the craft that built the command palette in the first place.

I used to think the disagreement was taste. It is not. It is task taxonomy.

When Density Is Earned, Not Borrowed

The pro-density case wins inside its fence. IDEs earn tight layouts with keyboards, training, and undo stacks. Terminals assume fluency. Bloomberg assumes apprenticeship. None of those contracts transfer automatically to a nurse between appointments or a manager approving an expense report on a phone. Chat admin UIs rarely ship a command palette. They ship a suggestion row with two tiny buttons and no undo for a chart entry. The keyboard escape hatch does not exist there. For most desktop work, larger targets and clearer separation beat heroic cramming. The cost of a miss exceeds the cost of a scroll. WCAG 2.2 draws two lines. Success Criterion 2.5.8 at Level AA allows twenty-four by twenty-four CSS pixels with spacing exceptions. wcag-target-size-minimum Success Criterion 2.5.5 at Level AAA recommends forty-four by forty-four. wcag-target-size-enhanced WebAIM's checklist separates the AA floor from the AAA enhanced bar. webaim-wcag-checklist GOV.UK's implementation guide recommends forty-four pixels for important controls at the enhanced tier. govuk-target-size W3C advises aiming at the stricter bar for important controls. Apple recommends forty-four by forty-four points. apple-design-tips Android and Material recommend forty-eight by forty-eight density-independent pixels. android-accessible-targets web.dev maps that to roughly a finger pad on the web. webdev-tap-targets Microsoft specifies forty by forty effective pixels minimum and forty-four for touch-optimised UI. microsoft-touch-interactions Accessibility practitioners crosswalk these tiers because legal conformance and comfortable acquisition are not the same thing. adrianroselli-target-size Fingers are not mouse pointers. nngroup-mouse-vs-fingers Density becomes virtuous when it adds signal for a known expert doing a repeat task. It becomes vice when it subtracts space to signal expertise the user never agreed to perform. Audit surfaces by risk, not by aesthetic cousinship to Cursor.

Compression is a context decision, not a moral signal about how serious your company is. The next time a dashboard imports IDE spacing, ask which rows carry consent and which carry speed. Leila still sits in user tests watching clinicians tap twice on a suggestion row that should never have been that narrow.