Open almost any consumer app released in the last five years and you will find the same visual grammar: white space, thin typography, ghost buttons, icons without labels, navigation hidden behind hamburger menus or swipe gestures. The aesthetic is instantly recognisable and broadly considered sophisticated. It signals that the product is modern, considered, uncluttered by the visual noise of earlier software generations.
It also, in many cases, makes the product harder to use.
This is not a fringe view. Usability research has been documenting the costs of aggressive minimalism for over a decade, and the findings are consistent enough to constitute a pattern. Error rates increase when affordances are removed. Task completion times rise when navigation is hidden. User confidence drops when visual feedback is stripped in the name of elegance. Yet the design industry has been slow to reckon with these findings, in part because the aesthetic reward — the clean screenshot, the design award, the press coverage — comes well before the usage data arrives.
What follows is not an argument against considered visual restraint. Good design often benefits from removing things that serve no purpose. It is an argument against the ideological application of minimalism — the belief that less is always better, that any visible affordance is a failure of design thinking, and that the measure of a good interface is how invisible it appears. That version of minimalism has costs that are rarely acknowledged by the people who create it.
How We Arrived Here: The Aesthetic Genealogy of Emptiness
Minimalism as a design philosophy predates digital interfaces by several decades. Its roots lie in the mid-twentieth century modernist movements — Bauhaus, the International Style, the Swiss grid tradition — all of which shared a rejection of ornament and a belief that form should follow function with nothing left over. Dieter Rams, whose work at Braun became the foundational text for a generation of product designers, articulated it most clearly: good design is as little design as possible.
The problem with applying this principle uncritically to software is that physical and digital products operate under fundamentally different constraints. A Braun radio has a fixed set of functions, a physical form that communicates those functions through its shape and material, and a user interaction model that does not need to be learned because it maps directly to physical affordances — a dial turns, a button depresses. A software application can have hundreds of functions, presents no physical form, and requires users to develop a mental model of a system they cannot touch.
When Apple introduced iOS 7 in 2013, the industry took it as a manifesto. The skeuomorphic textures of the previous era — the leather calendar, the green baize game tables, the linen drawer pulls — were swept away. Flat design arrived, and with it a new aesthetic orthodoxy that spread to Android, to web applications, to enterprise software, to everything. The transition was so rapid and so complete that questioning it felt like defending clipart.
The justification was partly philosophical and partly practical. Skeuomorphism was accused of being patronising — training wheels for users who needed real-world metaphors to understand digital objects. As smartphones became ubiquitous, the argument went, everyone understood that a calendar app was a calendar and did not need to look like a leather notebook to communicate that. Flat design was therefore a mark of maturity, both in the technology and in the audience.
There is something to this argument. Metaphor scaffolding that made sense when smartphones were new became redundant as literacy with digital interfaces spread. But the industry did not just remove the skeuomorphic decoration. It kept going, removing affordances, labels, visual hierarchy, and feedback cues that had nothing to do with skeuomorphism and everything to do with usability.
The Affordance Erosion Problem
An affordance, in the sense Donald Norman introduced in The Design of Everyday Things, is a design element that communicates how an object should be used. A button that looks raised and pressable communicates that it can be pressed. A text field with a visible border communicates that it accepts input. These are not decorative choices. They are the visual language through which users understand what actions are possible and what will happen when they take them.
Modern minimalist design has systematically removed affordances in the name of visual cleanliness. Buttons have become indistinguishable from static text. Form fields have lost their borders. Scrollable areas have no scroll bars. Interactive elements have no hover states on desktop. The visual cues that once told users "this thing does something" have been stripped out, leaving interfaces that are genuinely ambiguous about what is interactive and what is not.
The Nielsen Norman Group, which has been conducting usability research since the 1990s, published a comprehensive study on flat design's effect on usability in 2017 and updated it with further findings in 2022. Their consistent finding: removing or weakening visual affordances increases the time users spend looking for interactive elements and increases the likelihood that they will miss functionality entirely. In one study, participants took 22 percent longer to complete tasks on interfaces with weak affordances than on interfaces with strong ones.
The counter-argument is that users learn. Given sufficient exposure to a product, they develop a mental model that compensates for the missing visual cues. This is true, but it loads the cost of the design decision onto the user rather than the designer. Users have to work harder to learn the system, make more errors during that learning period, and feel less confident while doing so. The learning cost is real even if it is eventually amortised. And for users who encounter the interface infrequently — occasional users, new users, users who are older or less digitally fluent — that learning curve never fully resolves.
What Hiding Navigation Actually Costs
One of the most consequential minimalist decisions in modern app design is the near-universal adoption of hidden navigation. Hamburger menus, bottom sheets, swipe gestures, and long-press interactions have replaced visible navigation structures in the name of giving more screen space to content. The logic is reasonable on its surface: if the navigation is not in the way, the content can breathe.
The cost, however, is discoverability. When navigation is hidden, users cannot see what the product can do. They cannot form an accurate mental model of the application's capabilities because those capabilities are never visible at once. Features that are not in the primary flow of the application — the settings, the preferences, the secondary functions — are effectively invisible to users who have not been explicitly told they exist.
This is not a hypothetical concern. Research from the Nielsen Norman Group and from independent academic usability studies has repeatedly found that hidden navigation reduces feature discovery, increases the proportion of users who rely on a small subset of an application's capabilities, and increases frustration when users know a feature should exist but cannot find it. A study published in the International Journal of Human-Computer Studies found that users exploring apps with hidden navigation discovered 37 percent fewer features than users on the same apps with visible tab-based navigation.
The mobile design community largely acknowledged this in the mid-2010s when tab bars began replacing hamburger menus in major consumer apps. Twitter, Facebook, Spotify, and Google Maps all moved primary navigation to visible tab bars after usability research demonstrated the cost of hiding it. Yet the same pattern continued to be adopted by newer products, and the hamburger menu remains common in web applications where the research case against it is equally strong.
Part of the reason is that designers are not the primary users of their own products. A designer who builds a product from the ground up has a complete mental model of its capabilities. To them, the product is navigable even when the navigation is hidden, because they already know where everything is. The invisibility that frustrates a new user is invisible to the designer precisely because their expertise has made it so. This is a well-documented failure mode in interface design — sometimes called the curse of knowledge — and minimalism makes it worse by removing the external cues that would compensate for it.
Accessibility: The Group Minimalism Fails Most
The usability costs of aggressive minimalism fall unevenly across user populations. For young, digitally fluent users with high visual acuity and no motor impairments, the costs are real but manageable — more effort, more errors, longer learning curves, but ultimately a navigable experience. For users outside that profile, the costs can make a product effectively unusable.
Low-contrast typography is perhaps the most widespread accessibility failure in contemporary minimalist design. The trend toward light grey text on white backgrounds — a combination that appears elegant in a design tool at full brightness on a high-resolution display — fails the WCAG 2.1 contrast ratio requirements at the AA level and is difficult to read for the approximately 8 percent of the male population with some form of colour vision deficiency, as well as for users over 40 whose contrast sensitivity naturally declines with age. Nielsen Norman Group data from 2021 found that 73 percent of websites sampled failed WCAG contrast requirements for body text. The overwhelming driver was low-contrast minimalist typography.
Thin fonts present a related problem. The sub-100 weight typography that became fashionable in the 2010s — beautiful on a retina display in a controlled environment — is genuinely difficult to read on lower-resolution displays, in bright sunlight, or for users with any degree of visual impairment. The choice to use a 200-weight font instead of a 400-weight one is an aesthetic preference that converts into an accessibility failure for a meaningful proportion of the potential audience.
Touch target size is another failure mode. The Web Content Accessibility Guidelines recommend touch targets of at least 44 by 44 CSS pixels. Many minimalist interfaces use targets considerably smaller than this — icon-only buttons at 24 pixels, text links with no padding, tightly spaced list items — in order to preserve visual lightness. The users who pay for this choice are those with motor impairments, tremors, or simply large fingers. For them, a 24-pixel touch target is not an aesthetic preference. It is a barrier.
It is worth noting that accessibility failures are not merely ethical lapses. In most jurisdictions with advanced consumer protection frameworks, digital products used by the public are legally required to meet accessibility standards. The EU Web Accessibility Directive and the US Americans with Disabilities Act have both been applied to private-sector digital products in case law. Designing for visual minimalism at the expense of accessibility is, increasingly, a legal risk as well as a moral one.
The Confidence Problem: When Invisible Design Feels Unreliable
There is a subtler cost to extreme minimalism that is harder to measure but shows up consistently in qualitative user research: users lose confidence in systems they cannot read. When an interface gives no feedback, provides no confirmation, offers no visible indication of state, users are left uncertain whether their actions have registered. That uncertainty compounds into distrust.
Consider the common pattern of ghost buttons — outlined buttons with no fill, often with thin strokes and light text — used as primary call-to-action elements. Research on button design has shown that ghost buttons consistently underperform solid buttons in conversion rates, not because users cannot find them, but because the visual weight of the ghost button signals uncertainty. A solid button communicates: this is a defined thing, pressing it will do something definite. A ghost button communicates: this is a suggestion.
The same logic applies to loading states, error messages, and success confirmations. Minimalist interfaces frequently suppress or minimise these feedback elements in order to maintain visual cleanliness. A form submission might produce a brief toast notification that disappears in two seconds and leaves no persistent evidence of success. A slow network request might show no loading indicator at all, leaving users unsure whether their action was received. These are not corner cases — they are moments when users need the most reassurance that the system is working as expected, and minimalism has trained designers to treat that reassurance as noise.
The result is an irony that the advocates of minimalism rarely acknowledge: the pursuit of clarity through reduction often produces an experience that feels less clear, not more. Ambiguity is not elegance. A design that leaves users uncertain about what happened, what is possible, or what they should do next has not achieved simplicity. It has achieved confusion without ornament.
Emotional Resonance and the Limits of Neutrality
Beyond usability, there is a case to be made about what minimalism costs at the level of emotional engagement. Software exists in a competitive landscape where most functional requirements are met by multiple products. Users make choices between near-equivalent products based on how those products feel to use. Personality, warmth, distinctiveness — these are not trivial considerations. They are often the decisive ones.
Minimalism, applied uniformly, produces sameness. When every application uses the same neutral sans-serif typeface, the same restricted colour palette, the same white space proportions, the same icon style, the resulting landscape is homogenous in a way that makes individual products difficult to distinguish and difficult to feel attached to. This is not hypothetical — it is visually demonstrable if you compare the design of a dozen consumer fintech apps released between 2019 and 2023. They are not merely similar. In many cases, they are visually interchangeable.
Brands that have bucked this trend — that have invested in visual personality, distinctive illustration, unconventional typography, or rich colour work — tend to generate stronger user loyalty and word-of-mouth recommendation even when their functional capabilities are comparable to less distinctive competitors. Mailchimp's Freddie and its illustration system, Monzo's coral card and high-contrast brand identity, Duolingo's aggressive character-driven design — these are not coincidences. They are the result of a deliberate choice to be recognisable rather than merely tasteful.
Visual richness does not mean visual clutter. A design can be organised, purposeful, and usable while also being warm, distinctive, and human. The conflation of minimalism with quality — the assumption that stripped-back equals sophisticated and expressive equals amateurish — is a cultural preference, not a design principle. And it is a preference with costs that the design community has been reluctant to fully account for.
Designing With Complexity: What the Evidence Actually Supports
The research on usability, accessibility, and user confidence does not point toward abandoning restraint in favour of maximalism. It points toward a more nuanced principle: design complexity should match the complexity of the task, the diversity of the user population, and the context in which the product is used.
For a single-function tool used repeatedly by digitally fluent professionals, aggressive minimalism may be entirely appropriate. The user base has the context to compensate for hidden affordances, the task is well-defined, and the learning curve is acceptable given the frequency of use. A code editor, a digital audio workstation, a professional photography application — these are contexts where minimalism serves experts without failing newcomers, because newcomers are not the primary audience.
For consumer-facing products used by a broad and diverse population, including occasional users, older users, and users with varying degrees of digital fluency and physical capability, the equation is different. Here, the research supports making navigation visible, using strong visual affordances, maintaining contrast ratios above WCAG AA thresholds, providing persistent feedback on system state, and ensuring that interactive elements look interactive. These are not concessions to poor taste. They are the implementation of what we actually know about how people use software.
The most useful framing is probably not minimalism versus maximalism but signal versus noise. Every element in an interface either helps users understand what is possible, what has happened, and what to do next — or it does not. Elements that carry no signal should be removed. Elements that carry signal should be retained and made as legible as possible, regardless of whether their presence disturbs the aesthetic of negative space. The measure of a good interface is not how empty it looks. It is how clearly it communicates.
The Industry's Blind Spot: Who Evaluates Design Outcomes
One reason the gap between design aesthetics and design outcomes has persisted for so long is structural. The mechanisms by which design work is evaluated — awards, editorial coverage, portfolio culture, social media — are almost entirely visual. A design award goes to a screenshot. A portfolio piece shows the interface, not the usability data. Design Dribbble shots are assessed by other designers who share the aesthetic norms of the profession. The user who spent 45 seconds trying to find the settings menu is not in the room.
This creates a feedback loop that reinforces the aesthetic preferences of the design community rather than the practical needs of users. Designers who win awards for minimalist work are invited to speak at conferences. Their work is featured as exemplary. Younger designers absorb these examples as the standard to aspire to. The cycle continues, insulated from the usability research that would complicate it.
Breaking this cycle requires changing what the profession treats as success. It requires treating usability metrics, error rates, task completion times, and accessibility audits as design outcomes that matter as much as visual elegance. It requires creating space in portfolio culture for designers to show not just what their work looked like but what it achieved for the people who used it. And it requires a degree of intellectual honesty about the fact that some of the most celebrated design work of the last decade has been celebrated for reasons that have very little to do with how well it served its users.
Toward a More Honest Practice
None of the foregoing requires abandoning the genuine insights that the minimalist tradition has contributed to design. The elimination of purposeless ornament, the discipline of visual hierarchy, the respect for the user's attention — these are durable principles that produce better work. The problem is not the insight that less can be more. The problem is the ideology that insists less is always more, regardless of context, regardless of the evidence, and regardless of which users pay the price for the aesthetic preference.
Good design — the kind that actually serves the people it is made for — requires holding two things simultaneously: the aesthetic impulse to remove what does not serve, and the empirical honesty to recognise when removal has gone too far. It requires testing with real users, including users who are not like you. It requires reading the usability research rather than dismissing it as the concern of engineers who do not understand design. And it requires being willing to add things back when the evidence shows that their absence is causing harm.
The uncomfortable truth about minimalist design is not that it is wrong. It is that it has been applied as doctrine rather than as judgement. Doctrine is comfortable — it tells you what to do without requiring you to think about whether it applies here, to this user, on this device, in this context. Judgement is harder. It demands that you stay curious about outcomes rather than faithful to aesthetics. It demands that you care more about the person using the thing than the person photographing it.
That is, in the end, what design is supposed to be for.