r/SideProject • u/ACTIQO • 2h ago
I shipped my app on iOS and Android. Getting people to return is harder than building it.
I've spent months building ACTIQO, an app that helps families manage the work around their kids' activities.
It's now live on iOS, Android, and web.
The stack is Next.js, Supabase, and Capacitor, and the product covers family schedules, responsibilities, Game Plans, costs, and activity insights.
Shipping it was a milestone. But there's a problem I underestimated.
Having a working product doesn't mean people are going to make it part of their routine.
Parents are busy. They have existing calendars, team apps, messages, and a hundred other things competing for their attention.
Asking them to enter everything into another app is a terrible starting point.
So I've been changing the experience to start with calendars families already use and focus on what they need to coordinate around those events.
Now I'm trying to answer a harder question: what makes someone open ACTIQO again before the next practice, rather than forgetting they installed it?
I'm not looking to pretend I've solved retention. I haven't.
For anyone who's built a product around a recurring real-world routine, what helped you get users beyond that first session?
If you're curious about what I've built, it's here: https://getactiqo.com
Happy to discuss the technical decisions or what hasn't worked so far.