Game feel: what 60 seconds of Domino Peak taught us about UX

Sixty seconds is the budget. That is roughly how long a new player gives a game before deciding whether it is worth a second session, and no feature list survives losing that minute.

In Domino Peak the minute is spent on three things. A turn timer, so a table never stalls on a player who walked away. Tile feedback — weight, snap, sound — so placing a domino feels like putting something down rather than submitting a form. And connection state you never have to guess about: if the other player is reconnecting, the table says so, instead of leaving you staring at a board wondering whether the game is over.

None of that is visible in a feature comparison. All of it is visible in the first sixty seconds.

We apply the same budget thinking to business software: every action that succeeds must feel finished. A saved setting that gives no acknowledgement gets saved again, then a third time, then reported as a bug. Micro-copy, button states and empty states carry as much weight as the data model — they are the parts of the system a user actually touches.