The whole film lives in a terminal, and Pulse’s only body is a kaomoji — a face made of type. It dozes (-_-), watches (•_•), gasps (°o°;) and relaxes (^_^)b while the log stream scrolls; the human answers the prompt with one keystroke.
$ open dash/signups ok
$ open dash/latency-p95 ok
$ open dash/errors ok
$ open dash/checkout skipped
$ open dash/active-users ok
… 38 tabs open · 17:58 fri
Log lines scroll up one per 8th note as dashboards open; the prompt types the hook at 20 chars/s and the cursor blinks on the beat; the sleeping face fades in on the 0:06 snare.
Screen clears on the drop (one frame of black) and the face slams in at 230 px; the command types on beat 2 and the lockup appears on beat 3 with a 1-frame glow flash.
09:40 signups ok
09:41 p95 latency 212 ms ok
09:41 error rate 0.4 % ok
09:42 deploy #2231 shipped
09:42 checkout conversion −18%
The stream freezes on beat 1 and the anomaly line flashes coral; the face swaps (•_•) → (°o°;) on the next beat. The prompt box draws in and the human types R on the bar downbeat — [R] fills coral.
The face swaps to (^_^)b on beat 1, the [ok] line prints, the tagline types line by line and [ Start free ] inverts on the final hit.
Why: Nothing is cheaper to produce and nothing is more native for developer tools: type is the character, emotion reads instantly from a kaomoji, and the prompt makes the human decision explicit. Risk: Terminal aesthetics exclude non-technical buyers and dense logs are hard to read at feed size; keep only 5 log lines and one giant face per frame.
Adapt to your product: Replace the log lines with your own CLI or event stream, pick 4 kaomoji for your idle/watching/alert/done states, and turn your primary action into a single-key prompt.
References: https://en.wikipedia.org/wiki/Kaomoji (Japanese text faces read upright, emphasising the eyes) · https://en.wikipedia.org/wiki/Emoticon (the 1982 origin of text faces in plain-text messaging)