Selected work Case study
Shipped product · iOS · 2025 to now
BabyEats AI: shipping a consumer AI app, then keeping it shipped
A parent starting solids asks the same question several times a day: what can I safely feed them from what's in the kitchen? BabyEats AI answers it from a photo, a voice note or a typed list.
- My role
- Built and launched it
- First release
- 24 September 2025
- Latest release
- Version 1.6, 7 June 2026
- Published by
- NewSpace Ventures LLC
App Store screenshots for BabyEats AI, as published on the listing.
The problem
Starting solids comes with rules that change month by month. Honey is off the table before twelve months. Whole nuts are a choking hazard for years. Allergens need introducing on purpose. General recipe apps don't carry those rules, and searching for each meal is slow when a hungry baby is in the high chair.
The useful product was narrow: take the ingredients already in the house and return a few meals that suit the child's age.
My contribution
I built and launched the app. That covered the React Native client, the recipe generation service behind it, the onboarding quiz that captures feeding stage, subscriptions, App Store submission and the releases since.
The Create screen takes three kinds of input: a photo of ingredients, a voice note, or text. It can also import a recipe from a pasted link and reformat it into the same card.
One decision
Every recipe comes back in one fixed structure, whatever the input was. The card always carries an age range, prep time, difficulty and a short nutrition note, and the generation step applies the same feeding rules every time: no honey or added salt under twelve months, no whole nuts for young children, textures matched to the age group, common allergens flagged.
The alternative was a free-text answer, which is quicker to build and reads nicely. I chose the fixed card because a parent scanning a result one-handed needs the age range in the same place every time, and because a fixed structure can be checked. A recipe that arrives without an age group is detectably wrong. In prose, the same omission is easy to miss.
Evidence
The App Store listing is public. Version 1.0 went live on 24 September 2025 and the listing shows six further releases through version 1.6 on 7 June 2026, including onboarding and paywall changes in the first month and recipe updates in January.
The store screenshots on this page are the ones on the listing. They show the fixed card described above: the age badge, time, difficulty and nutrition note on a generated recipe. I haven't published usage or revenue figures here.