Animation and interaction are not the same thing. They look similar from the outside — both involve things moving on screen — but they come from different design intentions and produce different experiences.
Animation is something you watch. Interaction is something you do.
This sounds obvious. But the majority of websites that call themselves "interactive experiences" are, in practice, animated websites. The visitor scrolls to trigger animations that play out regardless of what the visitor does. The visitor is not interacting with anything. They're advancing a playhead.
There's nothing wrong with that, as long as you know what you're building. The problem is when developers and designers conflate the two concepts and end up with work that has the visual complexity of interaction without any of its actual qualities.
Why the Distinction Matters
Interaction requires the visitor's active participation. The experience responds to what the visitor does — not just that they scrolled, but how they moved, where they looked, what they chose. The visitor's behavior changes what happens.
When an experience genuinely responds to visitor behavior, something interesting occurs: the visitor feels agency. They feel like they're inside the experience rather than watching it. They start to explore, to test the boundaries, to discover things that weren't immediately obvious.
This exploratory quality is what makes interactive experiences memorable in a way that animated experiences often aren't. The visitor has a personal relationship with what they discovered. They did something, and the experience responded.
The deeper benefit is that agency creates investment. A visitor who feels like they're actively participating in an experience will stay longer, engage more deeply, and be more likely to share what they found.
The Scroll Question
Scroll occupies an interesting middle ground. It's not purely passive — the visitor controls the speed and direction. But in most implementations, it's also not genuinely responsive — the experience has been predetermined, and scroll is just the mechanism for revealing it in sequence.
Whether scroll feels like interaction or feels like animation depends almost entirely on pacing and camera behavior.
When scroll produces immediate, proportional, physical-feeling change — when the camera moves in a way that feels like it has mass and momentum, when the world responds with the same physics that real objects would have — scroll starts to feel like something you're doing rather than something you're watching. You feel inside the space.
When scroll produces pre-planned animations that trigger at specific threshold points — when elements fade in on cue, when camera cuts jump to predetermined positions — scroll feels like advancing a slideshow. You're navigating a presentation.
The camera behavior is the key difference. A camera that moves smoothly with slight lag, that has inertia, that carries the visitor through space — that creates a bodily sense of movement. The visitor's hand controls their physical position in a virtual world. That's interaction.
Pointer-Based Interaction
One of the most underused interaction techniques in 3D web experiences is pointer parallax — using the mouse or device orientation to create subtle movement in the scene that suggests depth and presence.
Done well, this is invisible. The visitor doesn't notice they're doing it. They just notice that the scene feels alive, that it responds to their presence. Move slightly to the left and the elements shift a little, revealing slightly different angles. Hold still and the scene settles.
This is biologically resonant. Our eyes have been doing parallax computation their entire lives — it's one of the primary mechanisms through which we perceive depth. When a visual environment responds to small movements of the head in the way a real environment would, our depth perception engages and the scene becomes spatially real in a way that static rendering never achieves.
The implementation is simple. The effect is disproportionate.
When to Animate, When to Interact
Here's a useful heuristic. Animate things that happen to the visitor: the world revealing itself, the camera arriving somewhere, the atmosphere shifting. These are things the experience does for the visitor, transitions and reveals that are authored.
Make interactive the things the visitor does to the world: exploring a product from different angles, hovering on objects to reveal information, physically navigating through space. These are the visitor's actions, and they should produce real responses.
The mistake is animating things that should be interactive — treating pointer movement as a trigger for a pre-planned animation sequence rather than a genuine influence on the scene's behavior. The visitor feels the difference immediately. An animation that plays when you move the mouse is not the same as a scene that moves with you.
The Performance Consideration
Genuine interaction has a performance cost that animation does not. A predetermined animation sequence can be highly optimized because you know exactly what's going to happen and when. Genuine interaction requires the system to respond to unpredictable input, which means more computation per frame.
This is one reason why most "interactive" web experiences are actually animated: it's technically easier, more predictable, and easier to control.
The answer is not to avoid interaction. It's to be precise about what requires genuine responsiveness and what can be pre-planned. Camera movement that follows scroll can be pre-planned. Pointer parallax needs to be genuinely responsive. A product rotation that follows the cursor needs to be responsive. Background particles can be pre-planned.
Knowing the difference — and engineering accordingly — is part of what separates work that feels alive from work that feels like a performance.
The Visitor's Role in the Story
There's a deeper question underneath all of this, which is: what role does the visitor play in the experience you're building?
An animated experience casts the visitor as audience. They watch something that was made for them. It can be beautiful, emotional, even profound — but their role is passive.
An interactive experience can cast the visitor as participant. They're not just watching the story unfold. They're moving through it, making choices, leaving traces.
The most powerful experiences hold both at once. They have a pre-authored emotional arc that the visitor moves through, and they respond genuinely to the visitor's presence — their movement, their attention, their behavior. The story was written, but the visitor is physically present in it.
That combination is what the medium of interactive web experiences is uniquely capable of. Not animation that happens in the browser, and not interaction without direction — but authored story, physically inhabited.
That's the thing worth building.