Why I’m building a fitness app that doesn’t have a cloud (and never will)
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:
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.
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.
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!
