The same outcome, felt two different ways — and the argument that "juice" is doing real design work, not decoration
Nothing about a block breaking requires a screen shake. The logic is identical with or without one: the block existed, you acted on it, it stopped existing. “Juice” — the shake, the flash, the momentary pause — changes nothing about what happened and everything about whether it registered.
Try it#
Try it: two blocks, identical outcome, one button
No juice
▮
Felt impact
Juice on
▮
Felt impact
Press Break both blocks — same outcome on each, watch how differently it registers.
Both blocks break on the same click, with the identical outcome. Watch how differently the two announce it.
Notice:
- the meter on the juiced block moves further even though the same one thing happened
- how much of “juice” is actually just timing — a beat of hesitation before the burst
- whether you can point to the exact frame it stopped feeling like feedback and started feeling like an event
Outline#
- juice as feedback design, separated from the mechanic it’s attached to
- why the moment of failure is where juice usually matters most
- what this course has actually been arguing for twelve weeks: that failure is designed, at every layer, on purpose
- the final project brief and what a strong fail state needs to demonstrate
Teaching team
- Marisol Quayeconvenor
