1
0 Comments

After 30 days and 30+ testers: My first app just hit Open Testing

Exactly one month ago, I opened up my first-ever app, Fit Log X, to a small group of 30 closed testers. Today, I’m excited to share that I’ve officially moved into Open Testing on the Google Play Store.

Coming from a background in software development, I thought I knew what to expect, but the feedback during this closed phase was a massive reality check.

What I learned from my first 30 testers:

  • UX is king on the gym floor: I had to strip away even more "clutter" than I originally planned. When someone is mid-workout, they don't want to hunt for a button; they want a high-contrast, lightning-fast way to log a set and put the phone back down.

  • The "Offline-First" appeal is real: I was surprised by how many testers mentioned that they specifically loved that the app didn't require an account or a cloud sync. It confirmed my hunch that people are genuinely tired of "renting" their fitness data.

  • Analytics over Fluff: People didn't want social features—they wanted better volume charts and strength-trend visualizations.

The Pivot to Open Testing: Moving to Open Testing is both exciting and terrifying. I’ve refined the analytics engine and smoothed out the logging friction based on that first wave of feedback. Now, the goal is to see how the app scales and ensure the local-only data model remains rock-solid across more devices.

If you’re a lifter (or just a privacy advocate): I’d love for you to put the app through its paces. It’s 100% free, no subscriptions, and zero data leaves your device.

For the fellow devs here: How did you handle the transition from your first "inner circle" of testers to the general public? Any advice on managing feature requests without bloating the UI?

I'm happy to chat about the tech stack or the Google Play review process in the comments!

posted toAvatar for product Fit Log X
Fit Log X