Sanding UI

Original Article ↗ Hacker News Discussion ↗

Label/Input Patterns and Accessibility

  • Large subthread on radio/checkbox labels. Many advocate wrapping the input inside the label to eliminate “dead space” and simplify click behavior.
  • Others point out accessibility guidance favors explicit for/id associations; a common compromise: wrap input in label and still use for.
  • Some assistive and voice-control software reportedly has trouble with implicit labels; debate over whether to accommodate buggy tools vs. keeping markup minimal.
  • Frameworks often choose input + label for styling via sibling selectors; :has() is mentioned as a modern alternative.

“Sanding” / Ad-hoc QA as Craft

  • Many describe deliberately “clicking around” (a.k.a. monkey testing, fuzzing, puttering) as a powerful way to find papercuts and edge bugs that formal tests miss.
  • This is compared to woodworking: repeated passes remove small splinters and improve “feel.”
  • Some stress that this complements, not replaces, unit/integration tests.

UI Papercuts in Real Products

  • Numerous examples across Safari, Spotify, Tesla, Facebook, Discord, Teams, etc.: tiny hitboxes, lost text, layout shifts, broken keyboard behavior, janky animations.
  • These are seen as cumulatively frustrating, especially at scale.

Frameworks, HTML/CSS, and Control Design

  • Frustration that basic widgets still require a lot of brittle CSS (flex, gaps, padding) and are easy to get subtly wrong.
  • Some lament the lack of a robust “native UI toolkit for the web” comparable to classic desktop toolkits.
  • Others argue these issues should be solved in design systems/component libraries, not reinvented per screen.

Process, Agile, and Incentives

  • Repeated complaint: ticket-driven Agile/Scrum, PM incentives, and “ship features fast” culture leave little room for sanding.
  • Disagreement over whether this is Agile’s fault or misuse of it; some argue any methodology could prioritize polish if leadership cared.
  • Several note that end-users rarely have power to demand fixes for small UX issues, especially in B2B/enterprise contexts.

Examples of Polished or “Sanded” UIs

  • Praised: certain email services, issue trackers, internal tools, niche shopping sites, well-crafted iOS apps, some games.
  • Others counter that even highly funded products (big clouds, social networks, Steam, etc.) often feel janky despite resources.