SPEC TEMPLATE
Game UI Motion Spec
Document transitions that communicate changes and stay responsive to input.
Why it matters
Motion tells players what changed, where something came from, and when they can act. Poorly specified motion can make menus feel slow or let inputs get lost mid-animation. A written spec gives engineers clear values and rules, and it makes sure players who reduce motion still get the same information and control.
Workflow
For each transition record purpose, trigger, start and end properties, duration, easing, interaction behavior, interruption rule, and reduced-motion alternative. Distinguish time to feedback from time to finish. Decide when focus moves and when controls can accept the next input.
Worked example
An equipment drawer opens with a short slide and fade. Move focus to the active row once it becomes operable. When Back interrupts entry, close from the current visual state and restore opener focus. In reduced motion, use a short opacity change with the same focus behavior. Timing in the prototype is a test value.
Try it
Specify open and close for one panel. Test fast repeated inputs, reversal midway through entry, and reduced-motion parity. Note the first frame the result can be understood.
Common mistakes to avoid
Making transitions so long that the menu feels sluggish. Blocking input until the animation finishes. Specifying only the opening animation and forgetting the close or an interruption. Turning off motion entirely in reduced-motion mode instead of offering a gentler alternative. Leaving focus behavior undefined during a transition.
Use it in your portfolio
Show a short screen recording with the spec values annotated, plus a side-by-side of the default and reduced-motion versions. It shows you consider feel, responsiveness, and accessibility together.
Keep going
Pair this with the State Matrix and the Engine Handoff Checklist, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.