I’ve downloaded more weight-loss apps than I can remember.
Some lasted a week. A couple made it to a month. I almost always stopped using them for the same reason, and it wasn’t because they were badly made. Usually, it was the opposite. They were polished, useful, and full of things I could track.
That was the problem.
Logging my weight quickly turned into logging breakfast, looking up calories, recording a workout, checking my water intake, completing a challenge, and trying not to break a streak.
Some people genuinely want all of that in one place. I eventually realized that I didn’t.
Most mornings, I only wanted to step on the scale, save the number, and get on with my day.
So I built Weight Loss Tracker Pro around that one small job.
The fourth step is the point
The main flow has four steps:
Open the app.
Enter your weight.
Save it.
Leave.
That last step sounds a little strange in a product spec, but it matters to me.
Apps are often judged by how long people spend in them. For this app, I think a good session can last only a few seconds. If someone records their weight and immediately closes the app, it did what it was supposed to do.
At one point, I wrote a tiny spec for myself:
required inputs: 1
time to complete: a few seconds
daily streaks: none
guilt for missing a day: none
It wasn’t really a feature list. It was more of a warning to myself. Every new screen, field, and reminder would have to earn its place.
Today’s number kept stealing the spotlight
Fast entry solved one problem, but it created another: what should happen after the number is saved?
I knew that weight moves around from one day to the next. Measuring at a different time, eating later than usual, or simply drinking more water can change what appears on the scale. I knew that logically, but a small increase could still be annoying.
One number, by itself, has almost no context.
A few weeks of numbers are much more useful.
That is why the app puts the history into a calendar and charts. Instead of staring at today’s entry, I can zoom out and ask a better question: am I generally moving up, down, or staying around the same place?
There is also a goal setting feature, mostly because I got tired of calculating the remaining difference in my head. The goal is there when it is useful, but it doesn’t take over the whole screen.
I didn’t want missed days to become another failure
I have stopped using apps after breaking a streak. It sounds silly when I write it down, but I suspect I’m not the only one.
Once the perfect run is gone, opening the app again can feel like being reminded that you failed. That is a lot of emotional weight for something as ordinary as forgetting to enter a number.
So there are no streaks here.
You can record your weight every morning, a few times a week, or disappear for two weeks and come back. The history still works. The chart still works. Nothing tells you that you ruined anything.
From a data point of view, a missing day is not zero. It is just a day without a measurement. From a product point of view, it should not become a reason to stay away.
While building this, I kept coming back to one idea: design for people returning, not for people behaving perfectly.
The best feedback was a request not to add more
I expected people to ask for more features. One review caught me off guard because it asked for almost the opposite:
I chose the app because the interface is clean and simple. Please be careful when adding features in future updates. I hope it does not become another app with exercise and calorie-tracking modules. Keep it lightweight and focused.
Translated from the original review.
That meant a lot to me. The user wasn’t describing the missing features as shortcomings. Their absence was part of why they chose the app in the first place.
It also made future updates a little more complicated. Adding something new is easy to justify when it sounds useful. Deciding that it doesn’t belong is harder.
Saying no is still product work
There are plenty of obvious directions I could take the app:
meal logging
calorie tracking
workouts
water reminders
daily challenges
streaks and badges
None of those are bad ideas. They just belong to a different product.
The question I use now is not “Could I build this?” It is “Would this make quick weight tracking better?” If I can’t answer that clearly, I leave it out.
Keeping the scope small has not removed product decisions. If anything, it has made the small ones harder to ignore.
I still have to decide what appears after an entry is saved, how charts should handle irregular measurements, how easy editing should be, and how to show progress without making normal fluctuations feel like failure. When an app only does a few things, every unnecessary tap becomes obvious.
What I learned from keeping it small
Before this project, I sometimes treated scope mostly as a development concern: fewer features meant less code and a shorter build.
Now I think scope is also part of the experience. Every feature asks something from the person using it. A field asks for information. A reminder asks for attention. A streak asks for consistency.
“Simple” also turned out to involve more decisions than I expected. Defaults, editing, empty states, history, and charts all matter more when there is nowhere else for friction to hide.
I also stopped assuming that more time in the app is always better. For a utility like this, finishing quickly might be the clearest sign that it is working.
Still small on purpose
Weight Loss Tracker Pro is not trying to replace a full diet or fitness platform. It is for people who want a quiet place to record their weight and see the longer-term direction.
Open it, log the number, check the trend if you want to, and continue with your day.
If that is the kind of weight tracker you have been looking for, Weight Loss Tracker Pro is available on the App Store.
If you have built a deliberately small product, how do you decide when a new feature improves the core experience and when it starts to dilute it?
Top comments (0)