Bring Back Idiomatic Design
This essay champions a return to "idiomatic design" and homogeneous interfaces, arguing that modern web development has sacrificed user consistency for innovation. It contrasts the predictable user experience of classic desktop applications with the fragmented, often frustrating, landscape of today's web apps. The piece resonates on Hacker News by critiquing contemporary UI/UX trends and advocating for principles that prioritize intuitive, familiar interactions.
The Lowdown
The author, from the "desktop software generation," expresses a longing for the consistent design patterns prevalent in older operating systems like Windows 95 to 7. This consistency, termed "idiomatic design" and "homogeneous interfaces," made software intuitive and easy to use without much thought.
- Idiomatic Design Defined: An "idiom" is a common design pattern (like a checkbox for a yes/no question) that users understand instinctively, and developers implement without much deliberation.
- Homogeneous Interfaces: These provide consistent experiences, where familiar actions (e.g., 'Ctrl+C' for copy) work universally across different applications, minimizing cognitive load.
- The Modern Web's Failing: Today, web applications lack this homogeneity. Tasks like date picking or credit card entry vary wildly across sites, even within the same company's product suite (e.g., Google's ecosystem).
- Reasons for Heterogeneity: The shift to touchscreens forced a reinvention of design patterns, leading to awkward compromises (e.g., desktop hamburger menus). Furthermore, modern front-end development, focused on modular components and rapid innovation, often prioritizes "what is possible" over established usability. Advanced technologies like WebAssembly (used by Figma) allow for custom interfaces that completely bypass traditional HTML idioms.
- Apple as a Counter-Example: The author cites Apple as a company that successfully maintains strong, opinionated design idioms across its ecosystem, creating an "it-just-works" effect that benefits users and influences third-party developers.
- Author's Recommendations for Builders: The article concludes with practical advice for developers, including studying and following HTML/CSS and browser idioms, avoiding JavaScript re-implementations of basic elements, prioritizing words over universally understood icons, making visual elements obvious, and choosing understandability over visual aesthetics. When in doubt, consult well-designed websites or historical interface design books.
The author dreams of a future where web interfaces converge on universally agreed-upon best practices, making common interactions predictably consistent and user-friendly, much like the best of the desktop era.