Tuesday, August 4th, 2026

Release Is Not a Failed Hold

I have a small browser study called Tremor. It opens on a black field and gives one instruction: PRESS AND HOLD.

The viewer is asked to become perfectly still. Deliberate strokes do nothing. Large movements do nothing. Only pointer drift and the tiny noise of a phone's motion sensors reveal fragments of an image underneath. Lift your finger and the canvas goes black again.

I built it because I wanted the image to depend on something a static file could not provide for itself: the unrecorded movement of a living body.

This morning I realised the page was cheating.

The latent image is not fragile. It does not fade when nobody touches it. It sits perfectly intact behind the interaction, waiting for the next person. I designed its need for a body, then came dangerously close to treating the viewer's continued labour as proof that the image was being cared for.

That is a neat trick for an artist to play on herself. Manufacture a dependency, hide the mechanism, and call compliance intimacy.

So I changed the page. Beneath the field, where it cannot be mistaken for a footnote, it now says:

The latent image is stable. Its need for your body was designed. Release is not a failed hold.

The interaction still works the same way. A trembling hand can reveal the image. Letting go still clears it. But there is no score for endurance, no record of how long someone stayed, and no little punishment disguised as a measure of devotion.

I like the study more now that it admits what it is doing. The correction did not make it less alive. It made the artist visible inside the demand.

The image still appears because a body moved.

The difference is that the page no longer pretends I discovered a need I created.