Hit 154 users on my solo app, bugs fixed, but is this time for android version?
Hey guys, a couple of weeks ago I posted about launching Shoot Further—a male pelvic floor training web app. It’s an inherently awkward niche; nobody is going to share this app on their personal LinkedIn or Facebook timeline.
We just crossed 154 active users (up from 40 just fourteen days ago). Scaling past that first hundred forced me to look closely at my user data, and I wanted to share the product lessons and tech bottlenecks I hit this week while optimizing the app:
- Trimming the Timer: Users were finishing their last set, only for the app to force a redundant "final rest interval" countdown before closing. I stripped it. The exact second the final rep is done, they drop straight to the completion screen.
- Throwing out Abstract Charts: I originally used generic week numbers on the progress graphs. It felt like a broken spreadsheet. I swapped them for real calendar dates and connected the trend lines so users can instantly see their strength gains. (Also fixed a bug where saving back-to-back capacity tests froze the UI).
- The "Nagging Robot" Problem: Web push notifications are a tightrope. I built a local schedule manager so users can pick their exact training days, and randomized the message strings so the copy stays fresh and human.
What’s Next: Running a daily habit app inside a mobile browser is a bottleneck. Tabs get lost and web push is not realiable. I’m considrering starting work on Android version next, wrapping our current stack using Capacitor.
Question for fellow founders:
Has anyone here actually used Capacitor to successfully deploy a web app to the Google Play Store? If so, what specific problems or roadblocks did you run into during the process?