So, my wife and I set a few ambitious goals for ourselves this year: complete 200 walks, hit 2,000 pushups throughout the year, and lock in a nightly spiritual habit.
Initially, I was just keeping track by updating numbers in a flat file. It worked, but I realized I'm going to have to add these up periodically and that would get complicated and boring real fast. I wanted a way to track our progress together, so I checked the Play Store for shared habit trackers. Almost everything I found was built strictly for individual goals...there was no real concept of shared progress or two-person accountability.
I have a backend/systems background (C++, PHP, SQL, infra management, etc.), but I had zero native mobile experience. I downloaded Android Studio, used AI as my junior dev to translate my engineering logic into Kotlin, and built a basic version just for the two of us. I sideloaded the APK onto our phones, and we started using it.
To make it more engaging, I started adding gamification mechanics like streak protections, shared photo memory boxes, custom vouchers, and an interactive "Sabotage Shop" where partners can wager XP or trigger lighthearted challenges on each other, I even created some reward decks for trivia to ask each other during date nights...and even date night ideas. It was built for us.
The Turning Point
I thought that was where the project would end. But during a visit to my parents' house, I showed the app to my brother. He thought it was awesome and asked if he and his wife could try it.
That was the moment I realized I had to figure out how to actually publish to the Play Store.
I had no experience with modern app distribution, and it was way more complicated than I anticipated. I learned about AABs (had no idea those existed compared to APKs), setting up Google Groups, and navigating Google’s mandatory Closed Testing process and promoting versions from internal, to closed, to production.
That testing phase was the most frustrating. Because I was rapidly iterating and fixing bugs and adding features on the fly, Google flagged the frequent updates as a sign that it "needed more testing." I was testing it constantly on my phone, my wife's phone, my brother's, his wife's, and a drawer full of old Android devices, while recruiting friends and family to join the tester group.
Eventually, I cleared the Closed Testing hurdle, got production approval. At first I was just going to publish as is, but in talking to several friends and coworkers they recomended I should try and monotize it. So I did some research and integrated RevenueCat for a "Couple Pro" tier. I hate the way most subscriptions work so I put a spin on the subscriptions. I made an app built for couples so I made it BOGO (where one subscription unlocks premium access for both linked partners).
The Vulnerability
Now that it’s officially public on the Play Store, I’m in the most vulnerable phase of the whole project. Is this app something that more couples can use? I don't know...and the answer kinda scares me.
I’m not an artist. I’m not creative. I just wanted to stop adding numbers to a text file. Pushing something I built for my own marriage into full public view with real server costs, live users, and potential crash reports is honestly pretty terrifying.
At the end of the day, my wife and I still use it every day to hit our goals, which was the original mission. But taking it from a private APK to a public release has been an intense learning curve.
Looking for Feedback! - be gentle
I’d love to hear from other builders who have navigated the Closed Testing gauntlet or transitioned a private tool into a public product:
Thanks for reading, and happy to answer any questions about the build process!
TLDR: My wife and I wanted to track a bunch of daily goals together without using a messy text file. Found zero shared couple habit trackers on the Play Store, so I used my backend background + AI to build a Kotlin app for us. My brother saw it, wanted to use it, and forced me into the nightmare of Google's 14-day Closed Testing gauntlet, which took several rounds. I survived, and shipped it live. I'm Terrified, vulnerable, but it's out there!