Building Steady: why we killed the streak counter
Streaks punish absence. We replaced them with rolling continuity. Here's the design thinking behind it.
Early in Steady's development, we had a streak counter. It worked the way every streak counter works: do the thing every day, watch the number go up, feel good about the number going up. Miss a day, number resets to zero, feel bad.
We killed it. Here's why.
Streak counters assume continuity. They assume that the thing you did yesterday, you can do today. For a lot of people, that's roughly true. But for people whose capacity fluctuates — because of ADHD, chronic illness, trauma responses, depression, or just the ordinary chaos of a difficult life — streaks don't motivate. They punish. And they punish specifically at the moment you're least equipped to handle punishment: the moment you return after being away.
Imagine you've been using a task app for 23 straight days. On day 24, something happens — a bad night's sleep, a crisis at work, a dysregulated morning that turns into a dysregulated week. You come back on day 30. The streak says: 0. Twenty-three days of effort, erased. The implicit message is clear: you failed. Start over.
The psychology of this is well-understood. Loss aversion means the pain of losing a streak outweighs the pleasure of building one. And for people already prone to shame spirals, a broken streak doesn't just feel bad — it becomes evidence. Evidence that you can't sustain anything. That systems don't work for you. That you should probably stop trying.
We replaced the streak with what we call rolling continuity. The system remembers where you were, not how many consecutive days you showed up. When you come back after five days away, Steady doesn't show you what you missed. It shows you where you left off. No badge. No reset counter. No implicit judgment. Just: here's your last context. Want to pick something up?
This sounds like a small design decision. It isn't. It reflects a fundamental choice about who we're building for. If you're building for people with stable capacity, streaks are fine — they're a lightweight accountability mechanism that works. If you're building for people whose relationship with consistency is complicated, streaks are hostile architecture.
The response from users confirmed what we suspected. The most common piece of feedback we get isn't about any specific feature. It's about the feeling of coming back. People tell us that Steady is the first tool that doesn't make them feel bad for being gone. And that feeling is what makes them come back at all.