ııı motion.mdVideo style specification
xAI / Grok / V314

Grok Bot | Android launch

Complete a question and answer through two lock-screen notifications: a person requests something, and the assistant returns the result.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 9.97 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>Grok Bot|Android launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#c9e6cc}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 lock screenTimeRequest notificationResult notificationLaunch phrase
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Let the lock screen contain the entire scene

Surround the phone with pale green and distinguish time from notification hierarchy. Use simple sans serif on white notification cards, differentiating sender, time, and body through weight; keep each body to roughly two lines.

02

Push in on the request before showing the reply

Push in on the request before showing the replyRule example
0.00 / 4.70 seconds
0.6–5.3 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>Grok Bot|Android launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#c9e6cc}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="0.6" data-end="5.3"><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>

The first notification establishes the task; the second delivers its result. Move closer to aid reading, then pull back to the full phone before cutting to the platform launch phrase.

03

Adapt to another system-level reminder

Change the team, task, and result summary while retaining the same subject and sequence. Briefly state what is ready in the result notification; show branding after the phone.

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 0.60 seconds
0.60s
Composition reference at 1.80 seconds
1.80s
Composition reference at 3.00 seconds
3.00s
Composition reference at 5.30 seconds
5.30s
Composition reference at 8.00 seconds
8.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • When adapting to status reminders, preserve request→result notifications; avoid inventing in-app pages.
  • Keep notification summaries under two lines.

Production constraints

Phone lock screen / time / request notification / result notification / launch phrase

  • Show the human request first, followed by the assistant's prepared result, using timing to express a response.
  • Push in on notifications, then pull back from the phone to emphasize system-level reach.
  • Condense the workflow into two notifications, directly comparing request and result.