MacroPilot.
An evolving, coach-first nutrition app designed around a simple question: what should I eat next?
to eat next.
Coach-first. Tracker-second.
I’m designing MacroPilot to move beyond calorie counting. I want Milo to help people understand their nutrition and decide what to eat next without turning every meal into a math problem.
The larger vision includes assisted food logging, personalized recommendations, and context-aware coaching. I’m starting with the core screens and interactions that will support those features.
What I’ve built so far.
Cross-platform foundation
I built the cross-platform foundation with Expo, React Native, and TypeScript, using Expo Router to organize navigation.
Onboarding
I designed and implemented onboarding screens for personal details, goals, activity, and preferences. The animated plan-building sequence previews the experience; personalized calculations still need to be connected.
UI system and Milo
I created a shared interface system for typography, spacing, and reusable controls, along with a dedicated Milo character component to keep the experience consistent as the app grows.
Next: meal logging
I’m working toward a meal logger that saves entries and makes everyday nutrition easy to review. AI coaching, meal-photo recognition, and integrations are planned for later phases.
Designing for a larger system.
I’m organizing the app around reusable components and clear navigation so I can add richer features without rebuilding the interface every time.
What comes next.
My next milestone is to build and test meal logging end to end, including a dependable nutrition-data model. That foundation will give me a starting point for coaching features. I’ll document the design and engineering decisions as the product evolves.
I want the evolution of MacroPilot to be part of the story, from the first interaction designs to working features.