David T Phung · Grok in the Timeline
Workflow · animated walkthrough

The product, in motion.

Each step below is a real interaction firing in context — the kind of moment a user has six times an hour without thinking about it. Watch it auto-play, or step through manually. The annotations to the right of the phone explain what just happened and, more importantly, why it was designed that way.

9:41 ●●● 100%
For you
Following
Auto-advance in 8s

How the system decides what to do.

Every post that enters the viewport triggers a small decision tree. Most of the time, the answer is "do nothing." That's the most important branch in the whole system — and the one most AI products forget to draw.

TRIGGER Post enters viewport DECISION Does Grok have anything to add? NO Render nothing "lol", "gm", short posts DECISION What type of post is this? RENDER Ask Grok Inline affordance RENDER Context chip Sources cited RENDER Thread Synth ≥8 replies, sampled SURFACE Compose RENDER Co-Writer SURFACE Feed header RENDER Tune (steer) CONSTRAINT (APPLIES TO ALL) First token: 400ms · Full answer: 1.5s · Every answer cites sources · Every answer shows confidence If we can't hit budget on a surface, we don't ship that surface. No exceptions. always no yes general factual thread

The decision tree is the spec. The visual board is the rendering. The prototype is the implementation. Three views of the same idea.