The problem
Recording meals asks people to repeat a task throughout the day: remember what they ate, find a matching item, and enter a portion. A digital food receipt already contains part of that record. ReceiptCal starts from that existing information and turns supported receipts into a food log.
My contribution
My work spans the product experience, the application, receipt processing, and the supporting nutrition infrastructure. The product connects a private receipt address with a reviewable daily log. That puts the user workflow and the treatment of incomplete information in the same design problem.
A smaller input, a useful result
A user can provide their private ReceiptCal address at checkout or forward a chosen receipt. The workflow begins with that receipt rather than access to a personal inbox. It reduces the information the user needs to share and keeps the action tied to a specific purchase.
- 01A chosen receipt
Use a private receipt address or forward a supported receipt.
- 02A daily food log
Bring the receipt’s food information into one reviewable place.
- 03Room to correct
Adjust portions, ignore items, and inspect supporting details.
Automation with room for correction
Automatic logging is useful only if the result stays understandable. The log lets a user adjust portions or ignore items, while supporting details explain nutrition sources. Estimates remain estimates. A receipt can describe a purchase without fully describing the portion eaten, so the interface needs room for the user to correct that difference.
What the product demonstrates
ReceiptCal brings receipt intake and nutrition logging into one product experience. The public product site provides the current app link, supported-receipt information, and an explanation of its nutrition methodology. The daily log is the point where those supporting systems become useful to the person using the app.
The boundary that matters
The approach depends on the quality and completeness of the receipt and the available food information. Some details can be resolved; others remain uncertain. The central product challenge is to remove repetitive entry while keeping the user able to understand and correct the result.