Two months ago, I pushed the first version of Food Pilot to TestFlight. It was rough. The UI was basic, animations were non-existent, and half the features I’d planned were missing.
I shipped it anyway.
Today, Food Pilot is live on the App Store — polished, refined, and actually something I’m proud of. But here’s the thing: I wouldn’t have gotten here without that ugly first version.
What is Food Pilot?
Food Pilot is a simple app that helps people build consistent eating habits. It sends smart meal reminders, tracks streaks, and offers AI-powered meal suggestions. Nothing revolutionary — just a tool that solves a real problem I had.
I kept forgetting to eat. Not because I wasn’t hungry, but because I’d get absorbed in work and suddenly realize it was 4pm and I hadn’t had lunch. I needed something to nudge me, and nothing I found quite fit.
So I built it.
The MVP Mindset
There’s a famous quote from Reid Hoffman: “If you’re not embarrassed by the first version of your product, you’ve launched too late.”
I used to think this was just startup advice — something VCs say to sound wise. But after actually living it, I get it now.
My MVP had:
- Basic meal reminders (the core feature)
- A simple check-in system
- User authentication
That’s it. No streaks. No AI suggestions. No fancy onboarding. The design was functional at best.
But it worked. And more importantly, it existed.
What I Cut (And Why It Mattered)
The hardest part of building an MVP isn’t writing code — it’s deciding what NOT to build.
Here’s what I originally planned but deliberately cut from v1.0.0:
- Streak system: Seemed important, but I needed to validate that people would even use the reminders first
- AI meal suggestions: Cool feature, but complex to implement. Would it actually help people eat more consistently? Unknown.
- Social features: Sharing progress with friends. Nice to have, not need to have.
Every feature you add before launch is a feature you might have to maintain, debug, or remove later. Cutting scope isn’t giving up — it’s being strategic.
The Feedback Loop
Once the MVP was on TestFlight, something interesting happened: I actually started using it. Daily.
And because I was using it, I immediately saw what was missing. Not what I thought was missing before building — what was actually missing from real usage.
Turns out:
- Streaks were more motivating than I expected (added in v1.1.0)
- The notification timing needed to be way more flexible
- People wanted to see their history at a glance
None of this was obvious from planning. It only became clear through use.
From Ugly to Polished
The version I shipped today looks nothing like that first TestFlight build. Side by side, the difference is stark.
But here’s what stayed the same: the core. Meal reminders, check-ins, the basic flow. The foundation I built in week one is still there, just wrapped in better UI and surrounded by features that actually earned their place.
The polish came from:
- Iterating on the design after seeing it in context
- Adding features based on real friction, not imagined needs
- Taking time to refine animations and micro-interactions
What I’d Tell Someone Starting Today
If you’re building something and waiting for it to be “ready” — stop.
- Define your core: What’s the one thing your app absolutely must do? Build that first. Everything else is noise until you validate the core.
- Set a deadline: I gave myself 2 weeks for the MVP. Having a constraint forced me to cut scope ruthlessly.
- Use your own product: If you won’t use it, why would anyone else? Dogfooding reveals more than any amount of planning.
- Ship before you’re comfortable: That discomfort? It’s the feeling of actually putting something into the world. It means you’re doing it right.
- Polish is a reward: You earn the right to polish by shipping first. Make it work, then make it good, then make it great.
The Result
Food Pilot is now live on the App Store. It’s free, it’s polished, and it actually helps people eat more consistently.
But more than that — I have proof that the MVP approach works. Not in theory, in practice. I went from idea to shipped product in 2 months, and the app is better for starting ugly.
If you’re sitting on an idea, waiting for the perfect moment or the perfect design or the perfect feature set — let this be your sign.
Ship the ugly version. You can make it beautiful later.
—
Food Pilot is available now on iOS: https://apps.apple.com/us/app/food-pilot/id6756402994
