Fit Log X

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!

Fitness apps used to be simple. You’d go to the gym, log your sets, and see a graph of your progress.

Today, the landscape looks very different. Most "top" fitness apps now feel like data-harvesting platforms disguised as trackers. They force you to create an account before your first set, lock your historical progress behind $10/month subscriptions, and require a constant internet connection just to save a workout.

I got tired of renting my own data.

So, I started building Fit Log X. I wanted to see if I could create a professional-grade gym logger that follows three strict "Indie" principles:

1. Local-Only by Default: All data is stored on the user's device. No cloud syncing, no databases on my end, and zero data harvesting. It works in basement gyms with no signal, and the user’s biometrics never leave their phone.

2. The "No-Subscription" Promise: I’m betting on the idea that people are exhausted by "subscription-ification." Every feature—from deep analytics to routine building—is accessible for free.

3. Zero Friction: No sign-up screens. No onboarding "tours." Just open the app and start lifting.

The Journey So Far: Building an offline-first app has its own set of challenges—especially when it comes to local data persistence and ensuring backups are easy for the user without using a centralized server. I spent the last two months in a closed beta with 30+ testers to make sure the "gym-floor UX" was fast enough for real sessions.

I’ve just moved into Open Testing, and I’m curious to hear from this community:

• As a user: Does "offline-only" make you feel safer, or do you miss the convenience of cloud-sync?

• As a dev: Have you experimented with a "Privacy-First" business model that rejects the standard subscription SaaS path?

I’m building this in the open and would love any feedback on the landing page or the philosophy behind the app!