Skip to content
Go back

Foodie

From recipe to receipt, optimised.

Foodie product shot
Status
In progress
Stage
In development
First shipped
29 Apr 2026
Stack
Golang, Postgres, NextJS, Typescript, React, Tailwind, Wrangler

Why I built this

I was throwing out food every week and spending too much on impulse groceries. I wanted a tool that treated the kitchen like a system — inventory in, recipes through, nutrition out — and I couldn’t find one that respected my time and my budget. So I built it.

Foodie treats your pantry as a database, your recipes as queries, and your week as a constraint. The goal isn’t another recipe app. It’s to make “what should I eat” a solved problem so the rest of life gets a little quieter.

What it does today

What’s next

The immediate focus is the basket optimisation engine — taking the per-ingredient price data already collected and solving for the cheapest store, or cheapest split across stores, for a full week’s meal plan. That’s the core of what Foodie is for.

After that: promotions as a first-class input so a Clubcard deal or multi-buy can actually flip which store wins, a household model for budget and dietary constraints, and the mobile app so the optimised list is in your pocket before you leave.

Iteration log

  1. 25 May 2026
    v1.22.0 — Asda, Waitrose, Morrisons; basket pricing
  2. 10 May 2026
    v1.10.0 — Sainsbury's collector; Jaccard product clustering
  3. 29 Apr 2026
    v1.0.0 — ingredient taxonomy + scoring engine
  4. 21 Mar 2026
    prototype — Tesco + PostgreSQL end-to-end pipeline

See all products →