Case Study
A kitchen inventory and recipe manager that figures out what you can actually cook tonight with what you already have. Built native for every screen in the house.
The problem
Every cooking decision is the same broken loop: open the fridge, stare, close the fridge, open the app, get told to make something that needs three things you don’t have, go to the store, come home, find the thing you thought you were out of, repeat.
Recipe apps assume a fantasy pantry. Inventory apps assume you’re tracking boxes, not food that rots. Meal planners assume you’ll cook what you scheduled even when the kids are melting down and the chicken is still frozen. None of them meet you where you actually live — in a real kitchen, on a weeknight, with the clock running.
WhatDo?! was born from that gap. A kitchen inventory that knows how food ages, paired with a recipe engine that only suggests things you can actually make right now.
Our approach
Most cross-platform apps are one iPhone app stretched awkwardly onto every screen. We took the opposite approach: each platform gets its own native layout designed around how people actually use that device.
Our App
A kitchen inventory and recipe manager that figures out what you can actually cook tonight with what you already have. It answers the age-old question: “What Do I make with all this stuff?”
Currently in development. Launching later this year.
WhatDo isn’t a stretched-out phone app — every platform gets its own native layout.
Under the hood
WhatDo is a local-first app with a cloud backbone. Every device keeps its own SwiftData store so the app works offline and launches instantly. A custom delta-log sync engine reconciles changes across devices and households without requiring CloudKit’s assumptions about ownership.
Client
SwiftUI + SwiftData
Platforms
iOS · iPadOS · macOS
Backend
Cloudflare Workers + D1
AI
OpenAI, tuned per kitchen
Sync
Custom delta-log with cursors
Data
Local-first, encrypted at rest
The AI layer runs on Cloudflare Workers, which gives us low-latency inference, tight quota control per user, and the ability to adapt suggestions over time without shipping a new app build. Recipe generation is grounded in the user’s real pantry so the model can’t hallucinate ingredients that aren’t there.
What's next
WhatDo is in active development. Current focus is shipping the iOS + iPadOS + macOS bundle, followed by a community recipe layer and cook-off challenges. Android is next on the roadmap.
Along the way we’ve built patterns that generalize to other apps: the custom sync engine, the quota-aware AI client, the cross-device layout system. If any of that sounds useful for something you’re building, we’re open to talking.
We’re taking on a small number of new projects this year. Drop a note.