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.
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>Motion and composition
Local motion · Composition rules
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.
Use the preview to explain what the app does
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.
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 publication | After publication |
|---|---|
| Preview content | The same app opens in its published form |
| Audience | Corresponding sharing scope |
| App address | Clear result link |
| Confirmation action | Explicit completion feedback |
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.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
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