What UI density means and how to design for it

What “UI density” should capture

• Many argue density is not just “more stuff,” but maximizing useful information while preserving visual salience and boundaries.
• Frames, whitespace, and grouping all increase salience; 90s-style framed UIs can be both dense and scannable.
• Tufte’s “data-ink ratio” is frequently referenced, but some note his examples in the article were mis-labeled.

Pro tools vs consumer apps

• Strong consensus: tools used daily for focused work (trading, DAWs, IDEs, ERPs) should be dense to minimize clicks and context switches.
• For infrequent or casual use, sparse, guided flows can be better.
• Disagreement on novices: some say low density helps, others say high-context, well-organized dense screens are actually easier to learn.
• Several note that over-optimizing for “new users” harms power users and can trap everyone as perpetual beginners.

Mobile, desktop, and responsive design

• Many blame low-density desktop UIs on “mobile-first” designs stretched to large screens.
• One camp: web and mobile paradigms are fundamentally different and need separate designs.
• Another: responsive design can work well, but is usually done superficially (hamburgering sidebars, stacking columns, stripping features).
• Touch targets and small screens legitimately cap density on mobile, but people resent when those constraints are blindly applied to desktops.

Customization and “dense modes”

• Recurrent proposal: user-selectable compact / dense modes or basic vs advanced views.
• Others warn that multiple UIs add significant design, dev, and maintenance cost and can fragment learning.

Temporal density & performance

• Thread extends “density” into time: how many steps and how long to complete a task.
• Streaming LLM responses feel faster than delayed full responses; clever loaders can make long waits feel shorter or market “work done.”
• Many users find artificial or padded delays deceptive and infuriating; performance is seen by some as table stakes, not a “nice-to-have.”

Examples and cultural contrasts

• Physical restaurant menus, Bloomberg Terminal, Craigslist, FINVIZ, and some East Asian / Chinese apps are cited as dense but effective (with caveats about clutter and dark patterns).
• Vanguard’s and banking sites’ “beautiful but low-density” designs are criticized as hiding needed detail and wasting space.

Why UIs got sparse (speculated in thread)

• Hypotheses: optimize for lowest-common-denominator users, mobile-first fashion, copying big platforms, engagement metrics that reward time-waste over efficiency, and designers prioritizing aesthetic trends over domain understanding.