Kitchen Table
A voice assistant for a user with low vision who wants to cook from a recipe hands-free. Built for Say It Back — build a voice interface for someone who cannot comfortably use a screen. Full voice loop with step navigation, timers, and repeat-back. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Kitchen Table — main view
Kitchen Table — result state
On the clock
What shipped, what didn't
Completed in time
Full voice loop with step navigation, timers, and repeat-back.
Unfinished / faked
Only handles recipes from three sites.
Obstacles
A dependency version mismatch cost six minutes. Pinned it and moved on.
Lessons learned
Scope down before the timer starts, not at minute 20 when you're already committed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Kitchen Table 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.
Started from the official framework starter template, unmodified.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Hana Kobayashi
Principal Research Engineer, Independent
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Ravi Anand
Head of Design, Tessellate
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Tomas Eriksen
Developer Advocate, Independent
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Discussion
1 comments
The repeat-back confirmation is the detail everyone else skipped. That's the difference between a demo and something a person could actually rely on.