What Is Time to First Motion?
Short answer: Time to first motion is the interval from a declared speech-input boundary to the first usable or visible avatar motion.
Time to First Motion belongs to the performance & quality layer of a real-time avatar system. Audio may begin quickly while the avatar remains visibly frozen if motion startup is slower. The useful engineering question is not merely whether the feature exists, but which component owns it and which event proves it worked.
| Quick reference | Answer |
|---|---|
| Category | Performance & quality |
| Stack boundary | Quality telemetry |
| Primary concern | Audio may begin quickly while the avatar remains visibly frozen if motion startup is slower. |
| Example | A demo team measures why the voice begins before the avatar’s mouth starts moving. |
Time to First Motion definition
Time to first motion is the interval from a declared speech-input boundary to the first usable or visible avatar motion. Here the term is scoped to a live AI avatar: a system that listens, generates a response, produces speech and motion, and presents the result while the user remains in the interaction. In that setting, time to first motion must coexist with conversation state, interruption, synchronization, and device constraints.
An implementation definition should name the input, output, owner, and lifecycle. That prevents one team from using “time to first motion” for a local operation while another uses it for the user-visible outcome. Audio may begin quickly while the avatar remains visibly frozen if motion startup is slower.
Why Time to First Motion matters in a real-time AI avatar
Audio may begin quickly while the avatar remains visibly frozen if motion startup is slower. A healthy average can conceal a slow tail, repeated stalls, or a device-specific regression that users experience as an unreliable conversation. In practice, this makes time to first motion part of the product experience rather than an invisible implementation detail.
The risk is easiest to see in the article’s example: a demo team measures why the voice begins before the avatar’s mouth starts moving. The behavior needs to remain correct across the whole turn, including queued work and late events, not only at the instant the primary decision is made.
Where Time to First Motion sits in the avatar stack
The measures that reveal startup speed, tail latency, stalls, bandwidth, and sync quality. Telemetry converts visible avatar behavior into defined events and distributions. Startup, sustained production, network delivery, playback, and rendering are measured separately before they are combined into an end-to-end view.
For time to first motion, the upstream boundary is a precisely named start event. The downstream boundary is an observable user-facing result such as audible speech, visible motion, a presented frame, or a completed recovery. Maintain a shared event dictionary so product, client, and backend teams measure the same boundaries and can reproduce a regression. Any later component should consume the resulting state or data without silently redefining what the term means.
How Time to First Motion works
1. Define the input and configuration boundary.
Specify whether the endpoint is first motion received, decoded, or presented. Document the chosen value or rule alongside the environment in which it was tested; otherwise a change can alter time to first motion without a clear baseline.
2. Make runtime ownership explicit.
Separate asset and shader readiness from motion-inference delay. Make the responsible component visible in logs and cancellation paths so two services do not make conflicting decisions about the same turn.
3. Turn the behavior into an observable contract.
Correlate it with first-audio timing to detect startup desynchronization. Capture the corresponding event or state in telemetry and test both the expected path and a failure path. This turns time to first motion from an assumption into a verifiable behavior.
Practical example
A demo team measures why the voice begins before the avatar’s mouth starts moving. A useful test recreates that moment and follows the term-specific controls in order:
- Specify whether the endpoint is first motion received, decoded, or presented.
- Separate asset and shader readiness from motion-inference delay.
- Correlate it with first-audio timing to detect startup desynchronization.
How to test or measure Time to First Motion
Declare start and end events before comparing results. Use distributions rather than averages alone, retain sample counts, and correlate outliers with pipeline stages so a high-level metric remains actionable.
For time to first motion, track P50/P95/P99 latency, startup milestones, queue depth, stalls, frame deadlines, sustained throughput, bandwidth, and synchronization error. Review distributions and failure counts rather than relying on one successful demo. Segment the result by region, device, network type, browser or runtime, provider, model, utterance length, load level, and session phase; a global average can conceal a failure limited to one environment.
Minimum test checklist
- Boundary: Specify whether the endpoint is first motion received, decoded, or presented.
- Ownership: Separate asset and shader readiness from motion-inference delay.
- Verification: Correlate it with first-audio timing to detect startup desynchronization.
- Run the same test once on the primary environment and once on a constrained or failure-prone segment.
- Keep start and end events unchanged when comparing releases.
Tradeoffs and failure modes
- Boundary mismatch: If the implementation violates the rule “Specify whether the endpoint is first motion received, decoded, or presented”, the observed behavior can vary by environment without a trustworthy baseline.
- Ownership conflict: If it violates “Separate asset and shader readiness from motion-inference delay”, two components may act on different assumptions or leave stale work active.
- Invisible regression: If it violates “Correlate it with first-audio timing to detect startup desynchronization”, a release can change time to first motion without leaving enough evidence to isolate the cause.
Common misconception
A single average hides the shape of realtime performance; always define event boundaries and inspect distributions by device and network. For time to first motion, the reliable claim is the definition and test boundary documented on this page—not a broader promise about every stage of the avatar pipeline.
Frequently asked questions
Is Time to First Motion the same as Time to First Audio?
No. The concepts interact, but they describe different boundaries. For time to first motion, the relevant definition is: Time to first motion is the interval from a declared speech-input boundary to the first usable or visible avatar motion. For time to first audio, it is: Time to first audio is the interval from a defined request boundary to the first audible sample of the avatar’s response. Instrumenting them separately makes the root cause of a failure easier to isolate.
What should a team define first for Time to First Motion?
Start with the event or data boundary: specify whether the endpoint is first motion received, decoded, or presented. Then name the component that owns the rule and the observable result that proves it worked. This prevents two implementations from using the same term for different behavior.
How does Time to First Motion connect to Shader Warmup and Time to First Audio?
Shader Warmup covers a neighboring concern: Shader warmup compiles and links graphics programs before their first visible use. Time to First Audio covers another: Time to first audio is the interval from a defined request boundary to the first audible sample of the avatar’s response. Read the three definitions together, but keep their events and ownership separate in telemetry so one metric does not mask another.
Related glossary terms
- Motion Inference Window — A motion inference window is a buffered interval of speech analyzed together to generate the next segment of avatar movement.
- Shader Warmup — Shader warmup compiles and links graphics programs before their first visible use.
- Time to First Audio — Time to first audio is the interval from a defined request boundary to the first audible sample of the avatar’s response.
Continue to implementation and evaluation
- Implementation path: PostHog observability integration
- Evaluation path: Best low-bandwidth AI avatar platforms
- Browse the complete real-time AI avatar glossary
References
Last reviewed: 2026-08-19. Review the linked specifications and current Spatius documentation before using this article as an implementation contract.