Consent First
An onboarding flow where the privacy explanation is the product, not a footnote. Built for The First Ninety Seconds — design the opening 90 seconds of a product a stranger has never seen. Full consent flow with plain-language data explanations. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Consent First — main view
Consent First — result state
On the clock
What shipped, what didn't
Completed in time
Full consent flow with plain-language data explanations.
Unfinished / faked
Not legally reviewed — this is a design exercise.
Obstacles
The first approach needed a background worker I didn't have time to deploy, so I moved it inline at minute 14.
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 Consent First 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.
Reused a personal utility file for date formatting (~40 lines), linked in the repo README.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
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
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.
Discussion
0 comments
No comments yet.