Less Is More, Until It Is Not

Less is more when it removes competition from a difficult task. Less is a bore when it removes the character the task could afford. That is my argument, not a universal law. A tax form, a registration flow and a timer used with cold hands need focus. Removing necessary instructions can make them harder, so counting elements is not the test. The skill is deciding, screen by screen, what the moment calls for.

Key Takeaways

• Remove distractions without hiding useful information.
• Give expression a deliberate place in the product.
• Measure the implementation cost of effects.
• Treat the project examples as design rationale, not comparative conversion evidence.

A style slogan is not a product requirement

“Less is more” and “less is a bore” are useful provocations. Neither tells you what a person needs from a payment form, a campaign or a share card. Start from that question instead of treating a preferred style as the answer to every screen.

The case for less: cognitive load is real

For design purposes, inspect what the person has to notice, remember and decide. Unrelated motion or competing actions can make that job harder. But information visible on screen can also spare the person from remembering it, which is why fewer elements do not automatically mean a simpler task.

That is the honest case for minimalism, and it is a strong one. Online banking, a government form, a medical intake flow, a checkout: these are tasks with real stakes, unfamiliar fields and a cost for getting it wrong. Strip them down. Show one decision at a time. Remove anything that does not help the person finish.

There is a caveat that minimalists sometimes skip. In complex domains you can only simplify so far before you are hiding things people need. A minimal interface for a hard problem is not one with fewer features. It is one where the features appear when they are needed and stay out of the way when they are not.

The case against less everywhere

The problem started when minimalism stopped being a response to load and became a default. The early web had personality to spare, from loud colour to skeuomorphic textures to layouts nobody had seen before. Some of it was bad. A lot of it was memorable.

Then the industry converged. Open a handful of SaaS sites and apps from the last decade and the pattern is hard to miss: the same hero layout, the same rounded cards, the same sans-serif, very often the same blue. Swap the logos and ask someone which company is which. This is the bland era, and it persists because it is cheap to reproduce and hard to get fired for.

Sameness is not neutral. When everything looks the same, looking different is one of the few ways left to be remembered. That is where maximalism comes back in: loud colour combinations, contrasting patterns, unexpected type pairings, interaction models that feel made rather than assembled.

A design that is hard to use is neither

Here is the line I would hold in any argument about style. Maximalism is not clutter, and minimalism is not emptiness. If a design is hard to use, it has failed, and the style label is irrelevant. A maximalist screen still needs hierarchy, a clear primary action and a structure underneath the decoration. If minimalism is a plain white T-shirt, good maximalism is a patterned jacket that still fits.

Maximalism also has a bill, and it is worth knowing the amount before you choose it. When we measured a WebGL background effect on our own site, on a machine forced onto a software renderer with the CPU throttled four times, the call that merely asks for a graphics context took 2,531 milliseconds before a single pixel was drawn. We wrote up the measurement and the fix in Three.js vs WebGL. The lesson was not "never do expressive work". It was: pay for it off the critical path, after the page is usable.

Both, in one product

The most useful version of this argument is not minimalism versus maximalism across products. It is both, inside one product, assigned by moment.

TrackCold, a cold plunge timer we designed and built, is the clearest example we have. Around the session, it is unapologetically maximal: plunge presets named Frostbite and Ginnungagap, an oath and rune system that treats habit-building like a Norse saga, a records screen kept "like a ledger of kept promises". That is where personality belongs, because nobody is under load while browsing rituals.

During the session, the app goes almost silent. The design scenario is a person in 39°F water. The timer emphasizes one ring, one number and the current phase, with pause and skip reachable. This describes an interface decision, not a recommendation about cold exposure.

PaceCalc splits the same way. The calculator itself is restrained: the pace, set enormous in serif numerals, with very little around it. The share cards are where it lets go, a poster layout with the race name in serif italic and a receipt layout that prints every split like a till slip, because a share card's job is to be noticed in a group chat.

Neither app is minimalist or maximalist. Each one asks, per screen, how much load the person is under, and spends its personality where the load is low.

The short answer

Whatever the style, check contrast, keyboard behavior and reflow. Expression does not remove those requirements.

Use less when the task is hard, the stakes are real or the user's hands and attention are busy. Use more when the task is light and the goal is to be remembered. Never use either as a house style applied to every screen, and never accept a design that is hard to use because it fits a style. If you are not sure which of your screens are carrying too much, a product UX audit is the fastest way to find out where users stall and where your product could afford to be louder.