ııı motion.mdVideo style specification
Cursor / V284

Build Live Apps

Turn a temporarily generated tool into an app the team can access. Continue beyond preview to permissions, address, and the actually opened result.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 24.27 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>Build Live Apps · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}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 elementsRequest fieldCheck stepsApp previewSeating chartPublishing-permissions dialogLinkOnline app
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

One request brings a full preparation process

After specific tool requirements, show app, database, access control, hosting, and checks. Run and complete each in order; do not show the finished product before adding decorative checkmarks.

Use white explanatory pages with simple sans serif; checks may use dark backgrounds and clear state symbols. Retain the app's own dark spatial layout when entering its preview.

02

Use the preview to explain what the app does

Use the preview to explain what the app doesRule example
0.00 / 5.00 seconds
10–15 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>Build Live Apps · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="10" data-end="15"><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>

Once the full tool appears, choose a function directly matching the request, such as assigning seats to new colleagues. Keep preview objects aligned with task results so the published content has a clear purpose.

03

Make address and permissions visible in the publishing dialog

After clicking publish, show address, audience, and confirmation together in one readable dialog. Reveal the link after confirmation, then open the online app with the same name and content throughout.

Before publicationAfter publication
Preview contentThe same app opens in its published form
AudienceCorresponding sharing scope
App addressClear result link
Confirmation actionExplicit completion feedback
04

Adapt to another team tool

Replace requirements, app data, and usage actions, updating address and permissions text. Preserve the full preparation→preview→authorized publication→link-opening path, rather than substituting a success message for the final result.

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 5.00 seconds
5.00s
Composition reference at 10.00 seconds
10.00s
Composition reference at 15.00 seconds
15.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 22.00 seconds
22.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • For team-tool publishing, preserve checks→preview→permissions→link→use
  • App content may change, but permissions confirmation must not become a decorative button

Production constraints

Request box / check steps / app preview / seating chart / publishing-permissions dialog / link / online app

  • Complete infrastructure-building steps one by one before revealing the app preview
  • the publishing dialog specifies the address and access scope, with an openable link appearing only after confirmation
  • carry the same seating chart from preview into the live app, preserving content identity