Six Sisters'MealPlanner
A food brand with a fifteen-year recipe library and a large audience had no way for that audience to actually cook from it week to week. This is the app that closed the gap — plan the week, get the list, cook from the phone.
- Role
- Sole developer
- Surface
- iOS, Android & web
- Stack
- Expo · Supabase · WordPress
- Status
- Shipped, in the stores
Two sources of truth, one screen.
The recipes belong to the brand's WordPress library and change constantly — they're fetched live and never copied into the app's database. Everything a household does with them lives in Supabase and syncs between devices in real time.
Keeping those two apart is the whole architecture. Editors publish a recipe and it appears; a partner ticks something off the shopping list in a grocery aisle and it disappears from the other phone.
The parts that were hard.
A recipe library that predates the app
Fifteen years of recipes written for the web, not for a phone. Ingredients, timings and serving sizes had to be read out of an existing taxonomy and made reliable enough to build a shopping list from.
A plan two people edit at once
Households share a plan. Two phones editing the same week is the normal case, not an edge case, so the list and the plan sync live rather than on next open.
Three platforms, one codebase
iOS with tablet support, Android with edge-to-edge display, and a static web build — from one Expo Router codebase, with Apple and Google sign-in on the native targets.