Case study · 2023

Relay

An email client that respects your morning — a working prototype exploring what triage feels like when the inbox has a finish line.

Client
Concept
Year
2023
Role
Design + Prototype
Stack
React · Electron · IMAP
Layered envelope lines composition for the Relay case study

Relay started with a question: what would email feel like if the inbox had a finish line? The answer became a working Electron prototype, a small essay in interface form, and eventually the design language I carried into everything since.

The finish line

Relay's inbox is a queue, not a list. Each message fills the screen one at a time, and every message gets exactly one of four verbs: reply, delegate, defer, or done. There is no mark as unread — that's a decision deferred, and Relay makes deferring explicit instead of ambient. When the queue is empty, you get a full-screen sunrise and today's date in 96-point type. People screenshot that screen and send it to each other, which is the only growth loop the prototype ever had.

Keyboard-first, mouse-polite

The four verbs live on J K L and semicolon, home-row adjacent, and every action shows its key inline until you've used it ten times — then the hint quietly retires. Full triage of a forty-message morning takes about six minutes, and the interface animates just enough to make progress feel physical: each handled message slides onto a visible done stack that thickens as you work.

The inbox is a to-do list other people write for you. Relay's job is to hand it back.

What survived

Relay never shipped — IMAP's edge cases and one person's evenings are a bad match — but the prototype did its real job. The one-decision-per-screen pattern, the retiring keyboard hints, and the earned celebration all reappeared in later client work. Some projects are products; this one was a thesis.