▲ 2 r/gitlab+1 crossposts

A user sent me 600 words of feedback. It led me to a cron job that had been silently zeroing every family's streak since launch.

I run a family chore/habit app (solo, iOS, React Native + Supabase). This week I got my first real piece of organic user feedback. A parent who tried the app with her kids and wrote 600 words on why she churned. Thoughtful, specific, kind. The dream feedback letter.

One line in it: "Streaks also are not working."

I assumed a display bug. What I actually found: months ago, a nightly pg\_cron job had been deployed straight to the database — no commit, no changelog, nothing in the repo. It compared task completion dates against `CURRENT_DATE - 1`in UTC. So any family finishing tasks after 5pm Pacific was treated as having missed a day, and their streak was zeroed at 1am UTC. Every night.

I ran the numbers: zero children in production had a streak above 0. The app's most visible motivation mechanic had been dead the entire life of the product, and no error, log, or dashboard would ever have told me. The job "succeeded" every night.

The kicker: the rest of her list things she said were missing had mostly shipped in the current version. She was on an old build and never got the update. So one letter surfaced a silent data-destroying bug AND told me my update path doesn't reach installed users.

Lessons I'm taking:

  1. Anything deployed outside version control is invisible to every future debugging session. My database had a whole layer of behavior git couldn't see. Everything goes in migrations now.
  2. A job that returns "success" can still be destroying your product. Success meant "the SQL ran," not "the SQL was right."
  3. One motivated user writing real feedback is worth more than any analytics dashboard at small scale. She found in a week what I hadn't found in three months.

Happy to answer questions about the stack or the debugging. And if you have early users writing you long feedback emails read every word. Twice.

reddit.com
u/ThriveTrack — 7 days ago

We tried chore charts, reward jars, and 4 different apps. Nothing stuck — so I built something rooted in behavioral science

Hey r/ParentingTech,

I'm a solo founder and parent who got frustrated enough to build my own solution. Here's the honest version of why.

Every chore app we tried followed the same pattern: novelty for a week, then dead. The kids lost interest, we stopped enforcing it, and we were back to nagging. I started digging into why — and the behavioral science is actually pretty clear.

Kids don't respond to obligation. They respond to visible progress, earned rewards, and a sense of leveling up.

So I built ThriveTrack around that. Kids earn XP points for completing chores and daily habits. They level up from Seedling to Champion. Streak shields protect their progress if they miss a day so they don't feel like quitting. It's gamified — but not in a cartoon distraction way. The mechanics are borrowed from habit science, not game design.
It's live on iOS right now. I'm actively learning from every family using it and building in public.

A few things I'm genuinely curious about from this community:
— What made you give up on the last chore app you tried?
— Do your kids respond better to rewards or consequences?
— What would make a habit app actually stick in your house?
Not here to just drop a link — I want to understand what's actually broken for real families. Happy to answer anything about how I built it or why I made certain design decisions.
You can find it at thethrivetrack.com if you want to try it.

reddit.com
u/ThriveTrack — 3 months ago