Why I Don't Put Streak Counters in My App

I get asked to add streaks about once a month. A little flame, a number, a gentle nudge at seven in the evening if the child has not played. It works. That is exactly the problem.

What a streak actually measures

Not learning. Return visits. A streak counter is a machine for making a person come back whether or not they want to, and it works on four-year-olds because four-year-olds are not equipped to resist a number that will break.

I have watched a child finish a puzzle and then keep tapping for six more minutes purely to protect a flame. That is not play. That is a small job with no pay.

The design choices behind the quiet

• No streak, no coins, no daily login reward.
• No notification that says the app missed you.
• No autoplay into the next activity when one finishes.
• A visible end, so a child can choose to be done.

Every one of these costs me something in a dashboard. Every one of them is why a parent can hand over the tablet without bracing.

What I optimise for instead

I want the app to be worth ten minutes and then to let go. The measure I care about is whether a child puts it down and goes to find a real object, not whether they open it eleven days in a row.

The uncomfortable part

This is worse for growth. I know. An app that nags gets used more, ranks better, and earns more. I am one person building the thing I wanted for my own child, and I would rather it be a small, honest tool than a habit nobody chose.

So: no streaks. Not now, not as a test, not behind a settings toggle. If you want to know how your child is doing, ask them what they built.