M0VE shipped this week. I want to do the thing most apps don't do on launch day, which is tell you what's actually going on inside the product.
What I learned shipping
The thing that surprised me most was how much of building M0VE was not nutrition. It was the boring infrastructure under it. Getting workouts to come in from five different sources and look like one workout. Getting your sweat rate to round the same way on every screen. Getting an offline meal to sync to the right slot when the phone comes back online. Months of work nobody ever notices, which is exactly how I want it.
The second thing I learned is that the food-logging method matters more than the macro engine. The best macro maths in the world doesn't help if logging takes 90 seconds. So most of the last six months went into making the photo, voice and barcode paths fast. That's why opening the app and logging a meal takes about as long as taking a photo of it.
What's broken on day one that I already know about
The Android waitlist is open but the Android app isn't here yet. Soon.
A handful of recipes still need better photos.
If you find something I didn't list, tell me. Bugs in M0VE get fixed faster when an athlete describes them than when the analytics flags them.
What's coming in the next 90 days
More integrations are coming.
A redesigned Fuel tier for better UX
Tighter coach-to-athlete pairing so the dashboard reflects what's logged in real time.
If you want to follow along week by week, I post the genuine progress on Instagram at @movenutritionapp. Not polished. Real.
A thank you
If you bought, downloaded, beta tested, gave me a sweat-rate-stained piece of feedback in a WhatsApp message, or just told a clubmate to try it: thank you. M0VE only exists because endurance athletes were honest with me about what was missing.
The next version is already in build. Tell me what to fix first.
Julian Founder, M0VE Nutrition · Instagram