Receipt Roll
A phone-camera receipt scanner that files expenses into categories. Built for Receipts — build something that makes a messy pile of documents answerable. Camera capture and category assignment. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Receipt Roll — main view
Receipt Roll — result state
On the clock
What shipped, what didn't
Completed in time
Camera capture and category assignment.
Unfinished / faked
Categories are fixed and can't be edited.
Obstacles
A dependency version mismatch cost six minutes. Pinned it and moved on.
Lessons learned
Test the demo path once at minute 25. I didn't, and it showed.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Receipt Roll 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.
Elena Voss
VP of Engineering, Harbor Compute
Ambitious in a way that worked against you. Half of a large idea scores lower than all of a small one.
Claudia Reyes
Staff Engineer, Vantage Analytics
This needed a working demo path. I could not verify the core claim from what was submitted.
Hana Kobayashi
Principal Research Engineer, Independent
Ambitious in a way that worked against you. Half of a large idea scores lower than all of a small one.
Discussion
0 comments
No comments yet.