Front Door
A landing-to-first-action flow that removes every step that isn't the action. Built for The First Ninety Seconds — design the opening 90 seconds of a product a stranger has never seen. The full flow, plus an instrumented drop-off view. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Front Door — main view
Front Door — result state
On the clock
What shipped, what didn't
Completed in time
The full flow, plus an instrumented drop-off view.
Unfinished / faked
Analytics are local only.
Obstacles
A dependency version mismatch cost six minutes. Pinned it and moved on.
Lessons learned
Writing the submission summary first would have caught the scope problem earlier.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Front Door data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Ravi Anand
Head of Design, Tessellate
Nice work under the clock. The unfinished list is longer than the finished one, but what shipped works and you were straight about it.
Marcus Bell
Founder, Bellwether Studio
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Discussion
0 comments
No comments yet.