What Games Know About Interfaces

A good game teaches its deepest mechanic without a single tooltip. Mario's first screen makes you walk right by putting empty space to the right; the first Goomba teaches jumping by approaching slowly with a gap behind it. Now open a typical SaaS onboarding: nine tooltips, a progress checklist, and a video nobody watches. The game industry's term for this is 'failure of level design'.

Feedback loops, not features

Games obsess over the loop: input → response → new state → desire to input again. Every satisfying game closes this loop in under 100ms with layered feedback — visual, audio, haptic. When I built Voidrunner's collision feedback, stacking a 40ms hit-stop under the particle burst changed the game's perceived fairness more than any difficulty tuning. Interfaces have the same physics: a button that acknowledges the press instantly can afford a slow server; a button that waits for the server feels broken at any speed.

The deeper lesson is about difficulty. Games ramp challenge against a model of the player's current skill — that's the flow channel. Products dump their full complexity on day one and call the resulting churn a 'marketing problem'. Progressive disclosure is just level design with worse tools.

Every interface is a game whose only mechanic is confidence. You are either building the player's confidence or spending it.

Juice, rationed

Game feel researchers call it juice: the cluster of exaggerated feedback that makes actions feel physical. Interfaces need perhaps a tenth of a game's dosage — but zero is the wrong number. A file that drops into a folder with 60ms of settle, a toggle with a real spring — these are the moments users describe as 'expensive-feeling' without knowing why.