ııı motion.mdVideo style specification
Meta / V164

Introducing Muse | Personal AI assistant launch

Connect assistant capabilities through three everyday tasks: understand requirements from messages, show ongoing work, and pause separately at decisions that require the user.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 82.54 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Introducing Muse|Personal AI assistant launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f8}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsAssistant avatarChat bubblesEmail cardOrder confirmationRegistration formFlight cardCalendar cell
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Let tasks arise from everyday messages first

Pair a pale gray-white background with pale blue chat bubbles. Place avatars and states near the current task; center input, email, and forms in turn rather than crowding them together.

02

Give confirmation its own beat in the order process

Give confirmation its own beat in the order processRule example
0.00 / 7.00 seconds
22–29 seconds · Motion example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Introducing Muse|Personal AI assistant launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f8}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="22" data-end="29"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>

Show allow and deny only after the list becomes an order; advance status after the user's response. Keep buttons and total price on one card, using black text and a blue primary button for clear hierarchy.

03

Carry one assistant across different tasks

Use lists for shopping, forms for registration, and itinerary cards for flights. Interleave brief capability statements, closing with calendar completion and checks without reintroducing the assistant for each task.

04

Adapt to other services

Preserve message→information organization→confirmation→completion. When replacing avatars, business cards, and phrases, substitute payment or registration decisions with choices the new service actually requires.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 17.00 seconds
17.00s
Composition reference at 26.00 seconds
26.00s
Composition reference at 33.00 seconds
33.00s
Composition reference at 55.00 seconds
55.00s
Composition reference at 72.00 seconds
72.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace brand, avatar, and three related tasks; confirm before executing.

Production constraints

Assistant avatar / chat bubble / email card / order confirmation / registration form / flight card / calendar cell

  • Pair a pale gray-white background with pale blue chat bubbles. Place avatars and states near the current task; center input, email, and forms in turn rather than crowding them together.
  • Show allow and deny only after the list becomes an order; advance status after the user's response. Keep buttons and total price on one card, using black text and a blue primary button for clear hierarchy.
  • Use lists for shopping, forms for registration, and itinerary cards for flights. Interleave brief capability statements, closing with calendar completion and checks without reintroducing the assistant for each task.
  • Preserve message→information organization→confirmation→completion. When replacing avatars, business cards, and phrases, substitute payment or registration decisions with choices the new service actually requires.