The story
Why it exists
Food logging fails when recording a meal takes longer than the habit can tolerate.
My role
Independent product designer and engineer. I defined the logging model, designed the native experience, and rebuilt the product in SwiftUI.
Product move
Unify barcode, voice, text, and nutrition-label capture behind one short review flow, then move recognition onto the phone wherever possible.
What shipped
A native iPhone app with four input modes, on-device Apple Intelligence, macro and weight trends, optional HealthKit integration, and no account or analytics.
See the product
Product judgment
Key decisions
- 01
Optimize for the moment of logging
Every input method ends in the same compact confirmation flow instead of becoming a separate feature journey.
- 02
Put intelligence on the device
Typed, spoken, and photographed foods are interpreted locally. Only barcode and brand lookups leave the phone.
- 03
Make privacy the default
Food history and goals stay on-device with no account, tracking, or analytics. HealthKit remains explicitly optional.
Build notes
The original Progressive Web App was rebuilt as a native SwiftUI application with Apple Intelligence handling food recognition on-device.
Open Food Facts is used only for barcode and brand lookup. Face ID protection and HealthKit integration are optional system capabilities.
Built withSwift, SwiftUI, Apple Intelligence, HealthKit, Open Food Facts, Claude Code
