On cinematic UI
What does it mean for an interface to be cinematic? A short defense of slowness, framing, and the long fade.
A working definition
I keep using the word cinematic to describe interfaces I admire, and people keep asking me what I mean. So: a working definition.
A cinematic interface is one that:
- Frames its content. It chooses what to show and what to crop, the way a shot composition does. It is willing to leave things out.
- Paces its reveal. It treats time as a material. Information arrives in beats, not all at once.
- Has a point of view. It looks like someone made it. Someone with taste, not a committee with consensus.
That’s the whole list. It is not about animation, dark mode, or movie-poster hero images.
Why it’s worth defending
The default interface today is infinite. Infinite scroll, infinite settings, infinite tabs. The cinematic interface refuses this. It says: here is the shot. Look at it. Now we cut.
This is not nostalgia. It is editorial discipline applied to a medium that desperately needs more of it.
A few examples
- [App or product you admire] does this well. [What specifically.]
- [Second example.] The first thing it shows you is a single frame, not a feed.
- [Third example.] The animation is restrained. The product trusts you to wait.
A few it isn’t
- Anything described as “filmic” by its own marketing copy.
- “Cinematic” backgrounds that play stock footage behind a login form.
- A still photograph, no matter how moody.
What I’m working on
A reading mode that paces scroll like dialogue. More on that later.