@ManraiSingh Looks like you’ve got something going!
Shipping the app itself is a big achievement. I’m still working towards getting mine out there.
Maybe I should pick a dream car too 😂
First, I need to ship the app!
@Caffe_dell Congratulations on your first paying user! 🎉
Getting an app onto the App Store is a big achievement in itself.
I’m also working towards reaching this point, so it’s really inspiring to see.
Hope FocusPause keeps growing! 🚀
When you start building an app, everything feels like it's working exactly as you imagined.
But the more you use it, the more small but important pain points start appearing.
Some of the hardest UX problems only reveal themselves through daily use.
Like a lot of developers, I often get the urge to build an app.
You imagine it helping someone someday. Maybe you can look back and say, "I built that."
But the motivation fades when nobody needs it yet.
I'm building my app for myself first.
And that changed everything.
I first started building this app with a lot of assumptions.
But since I was a real user from day one, those assumptions kept breaking one after another.
Every week I found something that looked good on paper but didn't work in practice.
Real usage changes everything.
One decision I made early while building my app:
I initially wanted to perfect the UI before building the features.
But I realized a beautiful app means very little if it doesn’t work well.
So I focused on functionality first.
Design can always be improved later.
I was redesigning my home page when I realized something.
A home page should reflect the user's journey.
It's not just a place to show everything an app can do.
At a glance, users should understand where they are and what matters next.
When I first started building this app, it was basically a “remind me to work out” app.
I wanted something that would stop me from overdoing workouts on high-energy days and reduce the crash cycle that followed.
Now it’s become much more than a reminder app.
One product decision I changed while building my app:
I originally wanted users to create their own wellness levels.
But I realized most people would stick with the defaults.
So I standardized everything to five levels.
Less flexible. Much simpler.
After using the app for a while, I noticed something.
People rarely add just one exercise to a workout.
So instead of making them repeat the same flow multiple times, I added multi-select to the exercise picker.
Much less friction.
I started building this app because I couldn’t understand what was happening to my body.
I’d keep crashing, but I never knew what was causing it.
Then it clicked.
I didn’t need more motivation.
I needed more awareness.
That’s how this app began.
After using the app for a while, I noticed something.
Most workouts don't change much from session to session.
The exercises, reps, and weights usually stay the same for weeks.
So I started prefilling the previous workout values.
Logging became much faster.
After using the app for a while, I noticed something.
Users rarely add new exercises.
Most workouts are built from the same set of exercises over and over.
So I added a “Recent Exercises” section to the picker.
It made logging much faster.
I originally planned to build scheduled workouts first.
But using the app changed my mind.
People don’t always plan their workouts.
So I made free-form sessions the foundation and decided to build planned workouts on top of that later.
@thesammykins I've been there more times than I can count.
The only thing keeping me going this time is a simple "What if?"
What if I actually see it through for once?
Even if it doesn't work out, I think I'd finally have closure knowing I gave it my best.
Another UX realization while building my app:
Knowing what deserves its own screen and what works better as a modal is more important than I expected.
Modals reduce navigation and make quick actions faster.
But it's a balance. Too many modals can feel overwhelming.