Perplexity Computer — hybrid cloud and local compute
Explain hybrid execution through one routed task: inspect content, assign it locally or to cloud, then gather results.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Perplexity Computer — hybrid cloud and local compute · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#111611}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
Set execution mode first
Establish device, hybrid settings, and task entry on a dark canvas. Use serif headings for propositions and sans serif for options; teal connections and emphasis form the main thread, with low-contrast gray secondary explanations.
Let checks determine the route
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Perplexity Computer — hybrid cloud and local compute · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#111611}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="24" data-end="42"><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>Show local checks after submission, then sensitive-information notices. Present notices before routing, highlighting the inspected content instead of showing a context-free message.
Two execution locations, two progress states
Keep local and cloud positions and states independent. Route by responsibility, advance separately, then converge on results; keep line direction and progress ownership consistent.
| Stage | Visual relationship |
|---|---|
| Check | Connect task to local inspection area |
| Route | Send distinct content to explicit execution nodes |
| Execute | Give each node its own state |
| Summarize | Completed items enter a shared result area |
End technical explanations with results
Complete results before showing the local-cloud summary diagram. Retain the two key layers and reduce interaction detail, letting the brand ending follow a complete task chain.
Change data types, preserve decision criteria
For another business, define checks and routing rules before changing notices, node names, and result text. Let complexity arise from two actual processing methods, not irrelevant extra nodes.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Preserve check→route→summarize, replacing data types and node names.
Production constraints
Local node / cloud node / task input / sensitive-information notice / parallel state / result
- Inspect sensitive information before choosing a local or cloud path, giving the two execution locations explicit responsibilities.
- do not combine them into an indistinguishable loading bar.