Juice: The Small Animations That Make a Game Feel Good
There is a layer of motion in good interactive work that carries no information at all. It is the difference between an ad that functions and one a stranger wants to keep touching, and it is almost impossible to argue for in a spec document.
In short
- Juice is the motion that carries no information. Feedback tells the player their input registered; juice tells them nothing, and that is the correct way to think about it.
- It is doing emotional work rather than instructional work, which is why it cannot be defended on clarity grounds and why it disappears first under a file-size cut.
- The effects are mostly borrowed from character animation: anticipation, overshoot, follow-through. They read as alive because they imitate how mass behaves.
- Juice on failure matters more than juice on success, because a miss that feels good is a miss a player will try again.
- There is a ceiling. Past it, the motion starts obscuring the board the player is trying to read, and the ad becomes busy rather than satisfying.
Take a well-made match-three game and strip out everything not strictly necessary. Tiles still swap, matches still clear, the counter still goes up. Every rule survives intact, every input works, and the thing becomes almost unbearable to play.
What was removed was not function. It was the tile lifting slightly before it moves, the cleared pieces scattering rather than vanishing, the counter overshooting and settling back, the board nudging when something big happens. None of that changes the state of the game. All of it changes whether anyone wants to keep touching the screen.
Game developers have called this juice for about twenty years, and the word stuck because no more dignified term captures it. It is the layer of motion sitting on top of a system that already works — and in a format where a stranger decides within seconds whether this is worth their attention, it is not a finishing touch. It is a substantial part of what the ad is selling.
Juice is not feedback, and the distinction matters
These get conflated constantly, and keeping them apart is the thing that makes juice possible to reason about rather than just pile on.
Feedback is informational. Its job is to tell the player that an input was received and what it did. A press state, a highlight, a piece snapping to a slot — each of those answers a question the player was actually asking. Remove it and they are genuinely confused, because a fact they needed has been withheld.
Juice answers no question. When a cleared tile bursts into fragments that arc outward and fade, the player learns nothing they did not already know a frame earlier. The tile was already gone. The burst exists to make its going feel like something.
That sounds like a case for cutting it, and it is the reason juice is always the first casualty of a size budget. But it inverts under a different question. Feedback determines whether the ad is *usable*. Juice determines whether it is *enjoyable* — and enjoyment is not a bonus in an ad a person did not ask to see. It is the entire basis on which they keep watching instead of hunting for the close button.
The same moment, split into its two layers — what the motion is for decides how much of it you can afford to lose:
Feedback — the informational layer
- Answers a question the player is actually asking
- Must begin on contact, before any logic resolves
- Removing it makes the ad read as broken
- Cheap: a scale change, a tint, a press state
- Judged on whether it is legible
Juice — the emotional layer
- Answers nothing; the state was already communicated
- Can run long after the outcome is settled
- Removing it makes the ad read as cheap
- Expensive: particles, easing curves, extra sprite work
- Judged on whether it feels good
Feedback decides whether the player understands the ad. Juice decides whether they like it. Only one of those can be cut without anybody filing a bug.
Where the effects actually come from
Juice looks like a grab bag of tricks until you notice that nearly all of it is doing one thing: pretending the objects on screen have mass.
Nothing on a screen has weight. A rectangle that moves from one place to another at a constant speed and stops dead is what a computer does naturally, and it looks exactly like what it is. Every technique below is a way of faking the behaviour of a physical object, and they come more or less directly from traditional character animation, where the same problem was solved decades earlier with pencils.
That is also why they compose well rather than competing. They are not separate effects; they are parts of one imitation.
The core vocabulary, what each one imitates, and where it earns its place in an ad:
| Technique | What it does and when it is worth the bytes |
|---|---|
| Anticipation | A small movement opposite to the intended one, just before it happens — a piece dipping before it jumps. It makes the main motion readable, because the player's eye is already at the right place when it starts. |
| Squash and stretch | Deforming along the direction of travel: elongating in flight, flattening on impact. The cheapest way to suggest that a thing is made of something rather than drawn. |
| Overshoot and settle | Travelling past the target and easing back. Almost nothing in the physical world stops exactly on its mark, so a movement that does reads as mechanical even to people who cannot say why. |
| Follow-through | Secondary parts arriving slightly late — a tail, a hanging piece, a shadow catching up. One offset element is usually enough to sell it. |
| Particles and debris | Fragments thrown outward on a destructive event. Pure spectacle, no information, and the single most reliable way to make a clear feel like an achievement. |
| Screen shake | A brief displacement of the whole view on impact. Extremely effective in very small amounts and the fastest of these to become unpleasant. |
| Scale punch | A quick pulse in size on a counter, score or badge. The reason a number that grows feels like a reward and a number that simply changes does not. |
Exaggerate more than feels correct
Juice tuned on a desktop monitor with the timeline open is almost always too subtle by the time it is running at a phone's size, in a feed, watched with partial attention by somebody who is not looking for it. The reliable method is to push each effect until it is clearly too much, then pull it back until it stops being distracting. What lands there is usually stronger than what you would have chosen by going straight to tasteful.
One tap, in slow motion
It is worth taking a single interaction apart frame by frame, because juice is invisible at normal speed and that is exactly the point. Here is a player tapping a block that clears — roughly half a second of screen time, with each layer labelled by what it is doing.
A single successful tap, decomposed. Only the first entry is strictly necessary; everything after it is the part that makes the ad worth playing.
0 ms
The block acknowledges contact
It compresses slightly, immediately, before any rule has been evaluated. This is feedback, not juice — it is the only item here the player would miss if it were gone.
~60 ms
It rebounds past its original size
The release overshoots before settling. Nothing has changed about the game state; the block just stopped behaving like a rectangle and started behaving like something with give in it.
~100 ms
The block breaks and scatters
Fragments thrown outward on slightly varied trajectories, fading as they go. The block was already logically removed a frame ago. This is the moment the removal becomes an event.
~120 ms
The view nudges
A displacement of a few pixels, over well under a tenth of a second. Enough to register as force, short enough that nobody consciously notices it happened.
~150 ms
Neighbours react
Adjacent pieces wobble and fall, arriving at staggered intervals rather than together. The stagger is what makes it read as a consequence rather than as a redraw.
~250 ms
The counter punches upward
The score scales up, overshoots the new value, settles. A number that arrives with force is a reward; a number that updates silently is bookkeeping.
~400 ms
Everything is at rest
The board is legible again and ready for the next input. The whole sequence cost under half a second, communicated nothing, and is the difference between an ad that works and one that is satisfying.
Note what is not in that list: a pause. Nothing in the sequence blocks the next input. The player can tap again at 100 ms and the new interaction begins while the previous one is still resolving, layered on top.
That is a hard constraint rather than a nicety. Juice that gates the next action has stopped being juice and become a loading screen with better art, and in a format measured in seconds, a half-second of enforced watching is expensive. Effects must be interruptible, overlappable, and entirely optional to the flow of play.
The failure case deserves the better animation
Most juice budgets go to success, which is intuitive and slightly backwards. A player who succeeds is already having a good time; the animation decorates a moment that was going to feel fine regardless. A player who fails is at the point where they decide whether to try again or close the ad, and that decision is made on feel rather than reasoning.
This is the mechanism behind a pattern anyone who plays games recognises: some games are enjoyable to lose at. The block that does not fit tilts, teeters and topples with visible physics. The stack collapses elaborately, taking a satisfying second to fall. None of that softens the failure — it is still a failure — but it was interesting to watch, and interesting-to-watch is what converts a loss into another attempt.
The inverse is grim and common. A player misses, the piece vanishes, a red flash fires, the board resets instantly. Every fact has been communicated accurately, and the experience is of being told off. In an ad nobody asked for, being told off is the last beat before the close button.
Success
Already rewarding on its own terms; juice amplifies a good moment
Failure
The moment the player decides whether to retry; juice does the persuading
Reset
Instant and unanimated reads as punishment rather than as another go
The point where it turns against you
Juice is unusual among design principles in that applying it enthusiastically fails about as badly as ignoring it, and does so more often in work by people who have just read about it.
The board is information the player is reading in order to decide what to do next, and every effect occupying the screen competes with that reading. One tile bursting is a celebration; six tiles bursting while the view shakes, three counters punch and a banner flies in is a screen where nothing can be located. The player is not delighted — they are waiting for it to end so they can see the board again.
One test resolves most of these arguments. Add the effect, then ask whether a first-time player can still tell, at any moment during it, what the state of the board is and what they can do. If not, the effect is not too flashy in the abstract; it is hiding the game, which is the one thing it can never be worth.
The second limit is budget. The good news is that the expensive-looking techniques are mostly not the expensive ones: squash, overshoot, stagger and scale punch are transformations of assets already in the file and cost almost nothing. Elaborate particle systems consume the budget, and they are what you can most afford to lose.
A rough order of value per byte, if something has to go:
- Keep first: easing and overshoot. Free in file size, applied to assets already present, and responsible for most of the difference between mechanical and alive.
- Keep next: stagger and follow-through. Also free — a matter of offsetting existing motion in time rather than adding anything new to the file.
- Keep, in small doses: screen shake and scale punch. Cheap, high impact, and the two easiest to overdo. A few pixels and a few frames is the whole effect.
- Spend carefully: particles. The most expensive category and the most visually rewarding. Usually worth funding for exactly one moment — the ad's peak — and nowhere else.
- Cut first: ambient motion. Background drift, idle loops, decorative flourishes nobody is looking at. It costs the same as the motion the player is actually watching and earns none of the credit.
The device you tune on is not the device they play on
Juice is frame-rate sensitive in a way that plain feedback is not. A sequence of overlapping effects that reads as buttery on a current flagship can drop frames on the mid-range hardware where a large share of impressions actually land — and a stuttering celebration feels considerably worse than no celebration at all. The number of simultaneous effects is the variable to check on a real, unexceptional phone before a campaign goes anywhere.
Why this is a selling argument, not a polish argument
A playable ad makes an implicit claim: this is what the product is like. The mechanic carries most of that claim, but feel carries a surprising amount of it, because feel is the one thing a player can evaluate in two seconds without knowing anything about the game.
So an under-juiced ad for a well-made game is not a neutral omission. It is an inaccurate description of the product — it says adequate about something better than that, in the first two seconds, to somebody deciding whether to continue. That is the defensible answer to why any of this deserves budget. It is not decoration competing with the mechanic for space; it is the part of the ad showing that the thing on the other end of the install is worth the download.
Five decisions that get most of the benefit without the common failures.
- 1
Separate the two layers before you start
Decide which motion is telling the player something and which is making them feel something. The first is not negotiable under any budget; the second is where every trade-off should be made. Mixing them up is how ads end up both confusing and busy.
- 2
Spend the free techniques first
Easing, overshoot, stagger and squash cost no file size — they are how existing assets move. Exhaust them completely before anything that adds bytes, because most of the perceived difference lives there.
- 3
Fund one peak moment
Pick the single beat the ad is built around — the big clear, the collapse, the win — and put the expensive effects there. Distributing the same budget evenly across every interaction produces an ad that is uniformly noisy and has no high point.
- 4
Animate the failure at least as well as the win
The retry decision happens at the failure, not the success. A miss that is interesting to watch buys another attempt; a miss that is punished with an instant reset buys a close.
- 5
Check legibility with fresh eyes
Hand it to somebody who has not seen it and watch whether they hesitate. Hesitation during an effect means the effect is covering something they needed. That is the only reliable signal, because the person who built it can no longer see the board as new.
The cheapest juice is almost all of the benefit. Easing, overshoot and a well-timed stagger add nothing to the file and account for most of the difference between a demo and a game.
Questions this raises.
How much of an ad's file size should go to juice?
Less than people expect, because the techniques that matter most are free. Easing, overshoot, stagger and squash are properties of motion rather than assets, so they consume no budget at all. The only real allocation needed is particle art, and one well-made sheet at the ad's peak moment is usually the right amount. If juice is eating a meaningful share of the file, the cause is almost always expensive effects spread across every interaction rather than concentrated on one.
Does juice slow the ad down?
Only if it is built to block, and it should never be. Effects need to be interruptible and overlappable — the player taps again while the previous burst is still resolving, and both run at once. A sequence that prevents the next input has become a cutscene, and in a format measured in seconds that is the most expensive thing in the file.
Is juice worth it if the mechanic is very simple?
It matters more, not less. A simple mechanic has little else holding attention, so how it feels is most of what the player is responding to. A complex mechanic can survive being merely functional. A simple one cannot — and a great deal of effective creative in this format is one four-word action carried entirely by the fact that performing it is pleasant.
Should juice be consistent across the whole ad?
Consistent in style, deliberately uneven in intensity. The same physical language should govern everything — if objects have weight in one place they have weight everywhere — but the volume should rise toward the moment the ad is built around. Uniform intensity is why some heavily animated ads still feel flat: nothing stands out, because everything is shouting equally.
Editorial
The Play Ads Maker team
We build the editor behind this site, which means we spend our days inside the format — its constraints, its export limits, and the question of what actually makes someone tap. We write about what we learn doing it.
The fastest way to understand the format is to build one
The editor is free to open, runs in the browser, and needs no code. Start from a template and have something playable within the hour.
Keep reading
Why a Button Needs to Feel Pressed
A response to a tap is not decoration. It is the only proof the player has that they caused something — and if it arrives late enough, they stop believing they did.
8 min readThe Grammar of Interaction
A tap and a drag are not two ways of doing the same thing. Each gesture makes a different claim about what the player is to the thing on screen, and picking the wrong one misdescribes the product.
9 min readDesigning for the Thumb
A phone screen is not a small canvas. It is a surface with a curved reachable region, a blind spot that moves, and a corner almost nobody can comfortably touch.
11 min read