ııı motion.mdVideo style specification
Perplexity / V259

Perplexity Computer now works in email

Use email as both task entry and result exit. One send begins the work; one reply returns an openable file.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 41.51 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>Perplexity Computer now works in email · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#08332e}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 elementsMailbox windowEmail draftAttachmentExecution stepsReplySpreadsheet output
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Explain the task and attachment in the draft

8.01s · Composition reference

Establish the mailbox context before opening a new email. Show request and attachment together, keeping send near the focus; subject and attachment names should directly explain the task.

02

Allow processing time after sending

Allow processing time after sendingRule example
0.00 / 11.00 seconds
11–22 seconds · Motion 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>Perplexity Computer now works in email · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#08332e}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="11" data-end="22"><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>

Close the draft after send, then show attachment processing and execution. Do not show completed outputs before sending; processing may be brief but needs at least one state change.

03

Return along the same task chain in the reply

Bring execution results back by email, open the deliverable, then return to the workspace. Keep a recognizable link between reply subject, filename, and initial attachment so it does not feel unrelated.

04

Set the familiar mailbox against deep green

Use deep green and pale outer text while keeping the email body bright and compact. Serif may serve branding statements, with sans serif subjects, addresses, and body; reserve accents for send, status, and result entry.

05

Replace the whole email, not just its subject

Change recipient, request, input attachment, and returned file. Budgeting, design checks, and data cleanup fit this flow; the email must explain why the later output is produced.

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 8.01 seconds
8.01s
Composition reference at 15.02 seconds
15.02s
Composition reference at 18.02 seconds
18.02s
Composition reference at 29.03 seconds
29.03s
Composition reference at 37.04 seconds
37.04s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace email tasks and deliverable files; preserve send→execute→reply.

Production constraints

Mailbox window / email draft / attachment / execution steps / reply / spreadsheet output

  • Trigger the task by email and return results to the same thread; attachments are input dependencies.
  • Show processing only after sending, and open outputs only after the reply.