I have worked out since I was 15. At 50, I'm busier and more tired than I've ever been, and not one bit less motivated. That gap between wanting to show up and actually showing up is the entire reason Momentum exists.
The gap isn't knowledge
Here's what I kept hearing when I talked to my gym friends while I was building this: nobody was confused about what to do. Everybody in that conversation had read the articles, knew the macros, could tell you the difference between progressive overload and just moving weight around. The gap wasn't knowledge. It was momentum, the actual mechanical act of doing the thing again tomorrow after you did it today.
Every single person said some version of the same sentence: it's not like college anymore. Nobody's handing you a schedule. Nobody's waiting on you at the field house. You're building the whole structure yourself, at the exact age when your calendar has the least room in it, and the apps built for 23-year-olds chasing a six-pack weren't built for that problem.
What I actually built
Momentum tracks workouts and streaks, and that's close to the whole feature list on purpose. I didn't want a dashboard full of numbers nobody checks. I wanted the one number that actually predicts whether you keep going: did you show up again. The app logs consistency the way you'd log it in a notebook if you were disciplined enough to keep one, except it remembers for you and it doesn't judge you for the week you missed.
There's a food-scanning feature in there too, and I want to be straight about what it is and isn't. It gives you a fast estimate, not a lab-grade nutrition report. If you're chasing exact macros down to the gram for a competition, this isn't that tool. If you want a quick read on whether today's plate was in the neighborhood of what you're after, it does that job well. I built it to lower the friction of logging, not to replace a dietitian.
The build choices that mattered
I kept the tech stack boring on purpose. This is a habit tool, and a habit tool that's slow to open or breaks on a Tuesday teaches you to stop opening it, which is the exact failure mode the whole app exists to prevent. Every design decision got run through one question: does this make it more likely someone opens the app tomorrow, or does it just make the app look more impressive in a screenshot. Streak tracking won that argument every time over a fancier analytics view.
The free tier isn't a trial that expires and starts nagging you. It's built to actually work for someone who just wants to track streaks and nothing else, because the whole premise of the app falls apart if I'm the one adding friction back in through a paywall three weeks after someone commits to the habit.
The schedule problem I kept designing around
A 50-year-old's schedule doesn't hold still the way a college kid's does. My gym friends aren't training at the same hour every day, and neither am I most weeks. Every design conversation I had while building this kept circling back to the same constraint: whatever the app asked of someone had to survive a calendar that changes week to week, not just a calendar that's merely full. A habit tool that assumes a fixed routine is building for the person who least needs the help. The person who needs it is the one whose Tuesday and Thursday don't look anything alike.
Where I compare it to what's already out there
MyFitnessPal is the obvious comparison, and it's a good tool for a different job. It's built for optimization: precise logging, a huge food database, the kind of detail someone training for a specific number wants. Momentum is built for consistency. The people I talked to who'd tried MyFitnessPal and quit weren't quitting because the app failed them technically. They were quitting because the app was asking them to optimize something they hadn't shown up for reliably yet. You don't need a better spreadsheet at week two. You need a reason to open the app at week two.
What I'd do differently
If I rebuilt this from scratch today, I'd delay the food-scanning feature by a few months and ship pure streak tracking first, then watch what people actually asked for before adding anything else. I built the scanning feature because I assumed people would want it immediately, and some do, but I'd rather have spent that early time hardening the one feature the whole app depends on: the daily check-in has to be fast enough that opening the app is never the hard part. The workout is the hard part. The app should never be.
Free to start, no credit card, and it's built for the person who already knows what to do and just needs the structure that makes doing it again tomorrow easier than not doing it.
Top comments (0)