All work

Xbox · 2026

A mobile prototype for Game Assist, built in Rive and handed to engineering ready to build.

Bringing Game Assist to Mobile

Game Assist helps players with whatever they’re playing. I helped shape the experience and designed and built its motion: the home screen where help shows up, the composer for typing or talking to the assistant, and the transitions that tie the whole flow together.

Rather than hand engineering a flat redline, I built the motion as one interactive prototype, so every transition, state, and microinteraction could be felt and tested before anyone wrote production code.

The Live Prototype

This is the actual prototype, running live in the browser. It runs the real flow: the home, opening the composer, typing a message, switching to voice, and the assistant thinking and then responding.

Building it this way meant the team could see the whole product, not a stack of disconnected screens.

This is the live prototype. Try moving through the flow yourself.

Handing It to Engineering

A prototype is only half the job. The deliverables were a mix of Rive elements and coded motion, so I pulled them together in a custom specs site I built: one place for engineering, with live previews, state-machine flows, view-model contracts, and frame-by-frame timing for every animation.

That let the team implement the motion exactly as designed, with no guesswork about timing, easing, or state, and no back-and-forth chasing how a transition was supposed to feel.

Loading Animation spec — phases, Figma link, and orb construction values.
General Guidelines — the easing-curve library, each spring with amplitude, period, and keyframe shape.
Animation Breakdown — live preview over a frame-by-frame timeline of opacity and Y-position.
Transition spec — trigger, from/to states, animated properties, and a scrubbable timeline.

The custom handoff site: specs, an easing library, per-frame timing, and live previews of every component

What Engineering Received

Rive Elements and Coded Motion

A mix of self-contained Rive files and coded animations, pulled together into one experience.

View-Model Contracts

A named trigger, boolean, and value API for every interaction, so engineering wires behavior to events without reverse-engineering the animation.

Phased Keyframe Specs

Frame-by-frame breakdowns, easing curves, and Figma references for the loading animation, conversation starters, and text-glow reveal.

One Custom Handoff Site

Live previews and complete specs for every deliverable, in a single site I built and kept current as the work evolved.

Why I Work This Way

Motion only matters if it ships the way it was designed. Building it as a live prototype, then handing it over as named states, triggers, and specs, is how I make sure the motion makes it all the way to the shipped product, exactly as intended.