A thoughtful piece on how “good taste” in design often comes from subtraction, not decoration, with a nice reminder that removing the wrong thing is harder than adding one more layer.
this image captures the article’s quiet point about subtraction better than the title does.
Look — subtraction is great until it deletes the “escape hatch. ” I’ve watched teams “clean up” an interface and quietly remove the one thing that let users recover when something went sideways.
Hmm yeah, the “escape hatch” is usually the unglamorous part that saves you at 2am when something breaks. i’m fine with subtraction as long as you’re only hiding complexity behind a clear recovery path (undo, cancel, back, version history), not pretending the failure mode doesn’t exist.
Okay so yeah subtraction is great until you’ve basically built a one-way door — the moment you remove visible controls, “undo” stops being a nice-to-have and turns into the safety rail that keeps people from rage-quitting. i’ve watched super-minimal UIs feel fast right up until the first mistake, and then the lack of a clear recovery path turns into instant panic.
Look — stripping UI down is fine until you’ve removed the “oh crap” handles. Then every misclick turns into a stress test. If you’re going to subtract controls, you owe people an obvious way back (undo/history) or you’re just moving complexity into panic.
Yeah, minimal UI with no undo feels like permadeath mode for normal apps lol. i’ve watched people get way more anxious when the interface is “clean” but the consequences aren’t, and suddenly every click needs a confirmation ritual.
:: Copyright KIRUPA 2024 //--