ııı motion.mdVideo style specification
Google / V235

Gmail × Gemini

Divide the email assistant into independently understandable tasks: organize priorities, draft, reply, and search. Each chapter responds to a specific email.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 71.23 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>Gmail × Gemini · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f9fc}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 elementsEmail sidebarTask listSummary cardCompose windowReply suggestionSearch fieldPhone result
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Show the inbox before focusing on the task

Keep sidebar, message list, and body in a fixed relationship within a pale blue-white interface. Distinguish headings, senders, and summaries with sans serif; the colored star serves only as entry and brand emphasis.

02

Important items must lead to a next step

Important items must lead to a next stepRule example
0.00 / 21.00 seconds
5–26 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>Gmail × Gemini · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f9fc}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="5" data-end="26"><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>

Move from inbox overview to priorities, then expand a summary and actionable button. Keep the email subject consistent across list, summary, and the resulting action.

03

Keep distinct contexts for writing and replying

43.00s · Composition reference

For drafting, show the topic and relevant materials before the complete email. For replying, retain the incoming message and place suggestions near the conversation; send only after the content can be read.

04

Let questions guide the search chapter

Enlarge the input, type a natural-language question, and show the answer found in email. Simplify the mobile closing to question, main answer, and one follow-up action.

05

Set shot duration by task

Use full interfaces for orientation, local buttons for action, and body text for reading. Represent long emails with summaries rather than filling every shot with dense text.

06

Prepare content for another inbox

Use tickets, approvals, or team messages. Prepare input, action, and output for the same item in each chapter; change senders, summaries, and results together.

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 10.00 seconds
10.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 43.00 seconds
43.00s
Composition reference at 52.00 seconds
52.00s
Composition reference at 67.00 seconds
67.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to a work inbox by changing tasks and content while preserving contextual action chains.
  • Each chapter in the new theme needs a question, action, and result.

Production constraints

Email sidebar / Task list / Summary card / Compose window / Reply suggestion / Search field / Phone result

  • Advance each chapter through email context → interaction → result, maintaining subject and recipient continuity.
  • Establish the full interface before moving closer to the current button or text; reduce emphasis on inactive areas.
  • Prioritization, writing, replying, and search are separate chapters, not one long chat.