Ninety
Onboarding for a finance tool, designed for someone who is nervous about finance tools. Built for The First Ninety Seconds — design the opening 90 seconds of a product a stranger has never seen. Progressive disclosure flow with a reassurance pattern throughout. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Ninety — main view
Ninety — result state
On the clock
What shipped, what didn't
Completed in time
Progressive disclosure flow with a reassurance pattern throughout.
Unfinished / faked
Copy is placeholder in two of six steps.
Obstacles
Underestimated the parsing work. Cut a whole feature to protect the demo.
Lessons learned
Hardcode the thing you can hardcode. Nobody is scoring your config system.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Ninety 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.
Tomas Eriksen
Developer Advocate, Independent
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.
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.