MacroDuo, nutrition tracking
A nutrition-tracking app for a family or a couple: each person picks the day's foods or recipes and sees how many kcal and macros they have left against their own targets.
Demo data: everything in the demo is fictional and generated by a script. It uses no real people, no server and no real data.
Problem
I was using a popular calorie-counting app, but it kept moving basic features behind its paid plan. I moved my records to a spreadsheet, which was not very visual and hard to use on a phone.
Approach
- One profile per person with their own kcal and macro targets, and a simple view of what is left or exceeded.
- A catalogue of more than 320 foods and ready-made recipes to pick from quickly.
- Adding new foods by taking a photo of the label.
- A shared shopping list: everyone in the household adds items and ticks them off in the shop.
- Password-protected access validated on the server with signed sessions; the API only answers to a valid session, and the data lives in a private repository.
- Serverless functions, one per endpoint; data lives as versioned JSON in the repository itself (every write is a commit), a pragmatic zero-cost choice for a handful of users.
- A basic threat model; next step: per-user identity instead of a shared password.
Result (qualitative)
It is used at home every day.
Skills demonstrated
Product design from a real need, APIs, persistence trade-offs, basic threat modelling and mitigation.
Publishable material
A demo with fictional data (invented profiles, a reduced catalogue, shopping list included; no label-photo reading and no password sign-in).
Stack
- Serverless
- API design
- JavaScript
- Security
- Vercel
- Computer vision