Miro | Product launch collection
Carry one product project through goals, research, design and development. Preserve its name or key question at every view change so the long video reads as one advancing workflow.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}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>Motion and composition
Local motion · Composition rules
Gather the team's problems first
Cut from yellow branding to a pale canvas, adding business-goal cards and named cursors progressively. Center the main question with surrounding notes responding; do not fill the frame with goals, research, and prototypes together.
Turn goals into schedulable work
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="53" data-end="59"><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>Pass through goal tables, milestone timelines, and boards. Match project colors between table rows and Gantt bars, with the right assistant panel explaining only the current step.
Let user insights actually shape the prototype
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Miro|Product launch collection · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="93" data-end="101"><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>Organize feedback into insight cards, open generation from a card, then show the phone prototype. Sequence question, action choice, and result; do not substitute an unrelated phone page.
Hand design to development at the end
Show product descriptions, entity diagrams, phone interfaces, and code workspaces in turn. Retain a small thumbnail or shared heading from each preceding step, using the overall timeline to explain strategy through delivery.
Replace upstream and downstream content with the project
Prepare business goals, three insights, one prototype, and development notes for one theme. Use note colors only for grouping; keep phones and documents white with dark text, using purple, blue, and pink as secondary colors without a new primary.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Replace the complete project and collaborators, preserving goal→research→prototype→architecture→delivery.
Production constraints
Sticky note / collaborator cursor / goal table / timeline / insight card / phone prototype / document / architecture diagram
- Cut from yellow branding to a pale canvas, adding business-goal cards and named cursors progressively. Center the main question with surrounding notes responding; do not fill the frame with goals, research, and prototypes together.
- Pass through goal tables, milestone timelines, and boards. Match project colors between table rows and Gantt bars, with the right assistant panel explaining only the current step.
- Organize feedback into insight cards, open generation from a card, then show the phone prototype. Sequence question, action choice, and result; do not substitute an unrelated phone page.
- Show product descriptions, entity diagrams, phone interfaces, and code workspaces in turn. Retain a small thumbnail or shared heading from each preceding step, using the overall timeline to explain strategy through delivery.
- Prepare business goals, three insights, one prototype, and development notes for one theme. Use note colors only for grouping; keep phones and documents white with dark text, using purple, blue, and pink as secondary colors without a new primary.