The Watchmaker's Insistent Tick: On the Virtue of a Predictable Rerender

We are taught, from our earliest days wrestling with the browser's pixel-painted canvas, that motion is the enemy of stability. The core tenet of performant design is often this: minimize layout shifts. Eliminate jank. The page should load like a photograph developing in a chemical bath, emerging complete and undisturbed. Any movement after the initial paint is treated as a failure, a flaw in the craft. The ultimate goal, we whisper to each other in hushed tones, is to build a statue.

But a statue, for all its perfect stillness, is dead. It cannot respond. We build for the web, a medium defined by interaction, not for a marble gallery. The relentless pursuit of a perfectly stable Core Web Vital can, paradoxically, lead us to create interfaces that feel sluggish and unresponsive, where a user’s action is met with a perceptible delay as the page works up the courage to finally, cautiously, change. We smooth over the inherent reactivity of the web in the name of a metric, mistaking the lack of visible turbulence for a quality experience.

Consider instead the inner workings of a fine mechanical watch. Its beauty is not in silence, but in its constant, reliable motion. The balance wheel oscillates; gears engage and disengage with a soft, persistent tick. This movement is not a flaw; it is the entire purpose of the mechanism. It is the visible, audible proof that the system is alive and working as intended. The user winds the crown (an interaction), and the hands move predictably across the face (a rerender). This is the contract.

Our obsession with Cumulative Layout Shift (CLS) has pushed us toward techniques that batten down the hatches, pre-allocating space for every conceivable element, sometimes pre-rendering entire sections off-screen. We build fortresses of predictability. But in doing so, we sacrifice the watch’s tick. We delay the essential, informative feedback of a layout adjustment in response to a deliberate user command. A filter applied to a product list, a sidebar toggled open, a comment section expanded—these should not be events we fear. They are the point.

The true craft, then, is not in the eradication of movement, but in its mastery. It is the difference between an unpredictable shudder—the true jank of an image loading late and pushing content down—and the deliberate, timely, and smooth animation of an element shifting in direct, immediate response to a user’s will. The former is a bug; the latter is a feature. The former breaks the user’s trust; the latter confirms it. We should strive not for the silence of a statue, but for the confident, purposeful tick of a well-oiled timepiece, where every user-driven rerender is not a metric to be suppressed, but a promise being kept.

Notes & further reading

A few pages I came back to while writing this: