In Defense of Text Labels

Original Article ↗ Hacker News Discussion ↗

Modern software increasingly replaces text labels with minimalist icons, a trend many users say makes interfaces harder to learn, scan, and explain to others. Commenters argue that while a small set of universally recognized symbols (play, pause, close) work well—and icons can save space, aid landmarks, and help advanced users—most app‑specific pictograms are ambiguous, require hovering for tooltips, and vary wildly between products. The emerging consensus favors offering both icons and clear text, with user‑configurable options, especially as complexity, accessibility needs, and internationalization concerns grow.

Text vs. Icons: Which Is “Better”?

  • Many argue text is fundamentally clearer: we’ve spent years learning words; icons are often app-specific, ambiguous, and slower to decode for anything beyond a tiny set of standard symbols (play, pause, close, search, trash).
  • Others push back on “strictly superior”: some users recognize icons faster and they save horizontal space, especially on crowded UIs or mobile.
  • Several note that icons are fine for a handful of common actions; beyond ~5–10 actions, unlabeled pictograms become “mystery meat navigation.”

Discoverability, Learning Curve, and Cognitive Load

  • Users describe hunting through monochrome toolbars (macOS Markup, Pixelmator, Obsidian, JetBrains IDE redesign) and having to hover each icon and wait for a delayed tooltip.
  • This creates ongoing friction, especially across many different apps each with 5–10 unique icons; people forget meanings between sessions.
  • A proposed heuristic: a GUI is “good” if you can easily guide someone verbally (“click ‘Share Screen’”) rather than “the grey thing with an arrow.”
  • Overly “intuitive” icon-only UIs often end up needing more explanation in popups, docs, or videos.

Best Practice: Combine Text and Icons, With Structure

  • Many prefer text + icons: text explains; familiar icons act as visual anchors and speed scanning; both support different cognitive styles.
  • Example praised: older Windows/Word menus using icons only on common commands, giving the menu a distinctive “shape.” Criticized: sidebars where every item has a similar vague icon, producing a blur.
  • Grouping actions by topic and using icons selectively is seen as better than hiding “unimportant” actions or reordering menus, which breaks muscle memory.

Accessibility, Diversity, and Internationalization

  • Visual limitations (low contrast, color blindness, large cursors) and age make icon-only UIs harder; labels also help screen readers.
  • Color can aid recognition but cannot be the sole differentiator.
  • Internationalization is cited for icons, but commenters note: icons themselves are culturally loaded and you need alt text/translations anyway; auto-translation makes simple labels cheap.
  • Analogies to traffic signs: Europe leans icon-heavy due to language diversity; people are trained on those icons—software rarely gets that level of training.

Platform and Design Culture

  • On phones, icon-only nav is sometimes accepted due to limited space; on desktop, commenters see little justification for removing labels and menu bars.
  • Criticism falls on both “devs doing UX” and visually focused designers chasing aesthetics and trends (flat, monochrome, Chrome-style static toolbars) over guidelines and usability.
  • Many want OS- or app-level toggles to choose icon-only, text-only, or both, plus search/command palettes for complex apps.