FKA twigs: The Body Is an Interface

FKA twigs doesn’t just sing — she is in the music in a way most artists never manage. Trained as a dancer, she treats her body as the primary instrument: every gesture precise, every vocal take physically present. When she performs, you don’t watch a singer; you watch someone inhabit sound like an interface.

I keep coming back to this because it’s the exact quality missing from most software: presence.

The interface argument

We build interfaces for a living, and most of them are haunted by absence. The button that doesn’t say what it does. The loading spinner that pretends. The error message written by someone who was thinking about a meeting, not about the person who would read it.

Twigs’s work is the opposite. Every detail is loaded — the choreography, the set design, the way a breath lands on a beat. Nothing is decorative; everything is intentional. The interface is the artist. The body is the message.

Cellophane

Cellophane is the clearest example. The song is almost nothing: a loop, a voice, a confession. And it’s devastating, because the restraint is total. She doesn’t over-explain the feeling — she just is in it, and the transparency of the container makes the content unmissable.

That’s the lesson for building: the best interfaces are transparent containers. The user should feel the thing itself — the content, the function, the idea — not the framework wrapping it. If your user notices your tech stack, you’ve wrapped the cellophane too thick.

Presence as a practice

I’ve started asking one question during code review: is this feature present, or is it just shipped? A feature is present when the person who built it was in the room while making it — when the edge cases were felt, not filed. A feature is just shipped when it passes tests and no one thinks about it again.

Twigs performs like her life depends on the next three minutes. I want to write code like that — rare, but when I do, fully there.