ııı motion.mdVideo style specification
Anthropic / V241

Claude mobile tool connections

Introduce a problem through a notification, show change in a chart, explain its cause through a process, and organize conclusions into shareable materials. Each card has a different informational role.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 52.25 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>Claude mobile tool connections · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}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 elementsPhone conversation containerExternal notificationAnalytics chart cardDesign-process cardSlide-result cardUser follow-up
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Charts, processes, and pages have distinct roles

20.00s · Composition reference

Warm gray-beige background, lightly bordered phone, data and process cards, and serif explanations.

Carry a business question through multiple tool calls: data explains what happened, workflows explain why, and slides support sharing.

02

Expand cards to inspect, then return to the conversation

Expand cards to inspect, then return to the conversationRule example
0.00 / 10.00 seconds
14–24 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>Claude mobile tool connections · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="14" data-end="24"><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>

Tool outputs first appear as embedded cards, expand for inspection, and return to the same conversation when closed.

Card form changes with information needs: curve→process→page. Do not replace them all with the same result-card type.

03

Build each follow-up on the existing conclusion

A notification raises the question, charts show change, processes explain causes, and conclusions become shareable materials. Each new question builds on the preceding card.

04

Change tools and content, preserve the evidence chain

Adapt to design review: feedback data→cause analysis→proposal comparison→reporting materials.

When changing brands, also replace tool content and preserve the causal chain from evidence to conclusion.

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 8.00 seconds
8.00s
Composition reference at 20.00 seconds
20.00s
Composition reference at 27.00 seconds
27.00s
Composition reference at 38.00 seconds
38.00s
Composition reference at 46.00 seconds
46.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to design review: feedback data→cause analysis→proposal comparison→reporting materials.
  • When changing brands, also replace tool content and preserve the causal chain from evidence to conclusion.

Production constraints

Phone conversation container / External notification / Analytics chart card / Design-process card / Slide-result card / User follow-up

  • Carry a business question through multiple tool calls: data explains what happened, workflows explain why, and slides support sharing.
  • Tool outputs first appear as embedded cards, expand for inspection, and return to the same conversation when closed.
  • Card form changes with information needs: curve→process→page. Do not replace them all with the same result-card type.