# 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.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 59.366667,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 12.2,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Build from your phone",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#67f0b1"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Build from your phone",
"accent": "#67f0b1"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## 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.
## 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.
## 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.
| Time | Section |
|---|---|
| 0.00–6.00s | Brand light form |
| 6.00–11.00s | Revenue milestone |
| 11.00–18.00s | Growth curve |
| 18.00–25.00s | Launch proposition |
| 25.00–28.00s | Laptop |
| 28.00–31.00s | Switch to phone |
| 31.00–38.00s | Phone input |
| 38.00–41.00s | Build status |
| 41.00–44.00s | Two platforms |
| 44.00–48.00s | Deployment success |
| 48.00–52.00s | App collection |
| 52.00–59.37s | Time and brand |
## 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.
## Color and typography
Sans-serif interface text with a clear size hierarchy.
#0b171b · #ffffff · #67f0b1 · #82abdf · #fafbfa
## Elements and production rules
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
## Content replacement
- 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 parameters
[Visuals and objects](style.json) · [Section timing](timeline.json) · [Position data](tracks.json) · [File manifest](manifest.json)
This specification is based on the reference video. The HTML provides editable choreography examples; each file identifies the source, precision and valid interval of its data.
```motion-board
{
"version": 1,
"brand": "Emergent",
"id": "V056",
"palette": [
"#0b171b",
"#ffffff",
"#67f0b1",
"#82abdf",
"#fafbfa"
],
"typography": "Sans-serif interface text with a clear size hierarchy",
"sample": "Build from your phone",
"objects": [
"3D brand form",
"Revenue figure",
"Growth curve",
"Computer",
"Phone",
"Input field",
"Deployment status",
"App wall"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 10.993827222222222,
"frameId": "K0043",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 24.985970959595956,
"frameId": "K0087",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 37.97867585858586,
"frameId": "K0130",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 43.97530888888889,
"frameId": "K0151",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 51.97081959595959,
"frameId": "K0185",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0.0,
"label": "Brand light form",
"end": 6.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 6.0,
"label": "Revenue milestone",
"end": 11.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 11.0,
"label": "Growth curve",
"end": 18.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 18.0,
"label": "Launch proposition",
"end": 25.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 25.0,
"label": "Laptop",
"end": 28.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 28.0,
"label": "Switch to phone",
"end": 31.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 31.0,
"label": "Phone input",
"end": 38.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 38.0,
"label": "Build status",
"end": 41.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 41.0,
"label": "Two platforms",
"end": 44.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 44.0,
"label": "Deployment success",
"end": 48.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 48.0,
"label": "App collection",
"end": 52.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 52.0,
"label": "Time and brand",
"end": 59.366667,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 59.366667,
"fontFamily": "Arial, sans-serif"
}
```