The case for liquid interfaces
Why the next decade of software will ditch rigid panels for surfaces that flex, merge, and reform — and what we lost when every screen became a grid of frozen cards.
I spent two weeks last winter rewriting a toolbar that nobody had asked to touch. The brief was simple: make the controls feel less like a control panel and more like a wet surface. By the end of the rewrite I had thrown out the concept of a button entirely, and the product felt, for the first time, alive.
From panels to puddles
The dominant metaphor of the 2010s was the card: a clean rectangle, padded, shadowed, inert. Cards stacked neatly into columns and columns stacked neatly into feeds. The trouble is that cards do not metabolize input — they only hold it. You drop a file onto a card and nothing happens to the card. The interaction is a transfer, not a reaction.
A liquid surface does not hold your input. It is changed by it.
— field note, Liquid Lab, Q4 2025When you press a mercury bead it does not register a click; it deforms, splits, and recoalesces. That physical honesty — the surface telling you it felt you — is what we lost when every interface became a sheet of frozen glass. The chrome of the late nineties understood this instinctively, even if the hardware could not deliver it. We had the aesthetic of liquidity without the mechanics.