Signal Flare
An onboarding sequence that adapts its pace to how fast you're clicking. Built for The First Ninety Seconds — design the opening 90 seconds of a product a stranger has never seen. Pace detection and three adaptive tracks. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Signal Flare — main view
Signal Flare — result state
On the clock
What shipped, what didn't
Completed in time
Pace detection and three adaptive tracks.
Unfinished / faked
Pace heuristic is crude and misfires on slow connections.
Obstacles
Lost four minutes to an auth redirect loop that turned out to be a trailing slash.
Lessons learned
Boring, well-understood tools beat interesting ones when there's no time to debug.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Signal Flare 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
Good instinct on the problem. I would have liked to see the model doing more of the reasoning rather than formatting output.
Tomas Eriksen
Developer Advocate, Independent
Solid build with a clear user in mind. The interface is doing less than it could — a second pass on hierarchy would lift this considerably.
Marcus Bell
Founder, Bellwether Studio
The idea is strong and the execution is most of the way there. The demo path broke once, which is what separates this from the top three today.
Discussion
0 comments
No comments yet.