ııı motion.mdVideo style specification
Emergent / V056

Emergent | Build apps on mobile

Use growth context to introduce a new scenario: bringing work previously built on a computer to a phone. Let data open the story and actual mobile interaction carry the second half.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 59.37 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>Emergent|Build apps on mobile · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#0b171b}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 elements3D brand formRevenue figureGrowth curveComputerPhoneInput fieldDeployment statusApp wall
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Clarify time relationships in opening figures

Use two growth milestones and a curve to show change, grouping figures, metric names, and dates together. Emphasize growth with mint green on dark; use large bold sans serif headings with lighter units and times.

02

Keep the same task across the device change

Carry task wording or the app subject from laptop to phone. Once the phone settles, show input, build status, platform support, and deployment completion; do not lose task identity during the device transition.

03

Expand the app collection after completion

Once the individual phone task is complete, unfold multiple results around the phone, moving from focused to rich composition. Add counts and platform marks as secondary information, then return to the brand or release date.

04

Prepare two sets of material for a new theme

Provide new growth context and one task that can be completed on the new device. Update both milestone definitions and product actions, preserving the turn from business context to use case; the app collection must also match the new theme.

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.99 seconds
10.99s
Composition reference at 24.99 seconds
24.99s
Composition reference at 37.98 seconds
37.98s
Composition reference at 43.98 seconds
43.98s
Composition reference at 51.97 seconds
51.97s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Use for a product moving from an old medium to a new one, retaining the same task identity
  • Replace growth figures and launch commitments with verifiable information for the new brand

Production constraints

3D brand form / revenue figures / growth curve / computer / phone / input field / deployment status / app wall

  • Establish context through growth first, then move the building entry point from computer to phone
  • phone input, building and launch occur in sequence, with the app wall appearing only after completion feedback
  • distinguish the dark data section from the bright mobile section