Health at Human Speed: Notes from Building Slowly

There’s a folder on my phone called Wellness. Right now it’s empty. But over the last three years it has, at various points, held Cult.fit, HealthifyMe, MyFitnessPal, Apple Fitness, and one Hindi-language one whose name I genuinely can’t recall anymore.

Every install was hopeful. Every uninstall was quiet. And every time, the story I told myself was the same: yaar, mera consistency hi nahi hai. Discipline ki kami hai.

Then I started noticing it everywhere. The senior engineer who sat next to me had downloaded and uninstalled Cult.fit at least twice. Half my college WhatsApp group had a “Day 1 of getting back on track” Instagram story every January. My cousins, my school friends, the uncles in my building’s morning walk group — everyone had the same loop.

That’s a lot of broken discipline for a country full of supposedly broken people.

After enough cycles, the story stops being convincing. Either an entire generation of Indian working professionals is uniquely lazy (along with several hundred million other people globally), or the apps are designed around an assumption about willpower that doesn’t survive a normal Tuesday in Bengaluru traffic.

That’s the spark for Slowly — a capacity-first health app I’m building for the version of me that kept quitting. This post is less a product pitch, more a notebook of the design decisions that fell out of taking one belief seriously.

The belief

If the user repeatedly fails the plan, the plan failed to understand the user’s life.

Every product disagreement I’ve had with myself about Slowly has been resolved by this one sentence.

Most fitness apps don’t believe it. They believe you failed the plan, and the right intervention is sterner UI: a red day on the heatmap, a broken streak, a guilt-shaped notification at 8 PM when you’re still in office and your manager just dropped a “quick sync?” on Slack. The shame is the retention mechanic. The shame is the product.

I’m building the opposite.

What got removed

Before figuring out what Slowly was, I had to be ruthless about what it wasn’t.

The kill list:

• No streaks. Not as the hero feature, not as a freeze, not as a quiet stat on a profile page. Streaks turn the user into the prosecutor of their own past. The cost of breaking a 47-day streak becomes greater than the cost of skipping today’s session — which is exactly the wrong incentive when your manager pulled a fire-drill standup at 9 PM.
• No rings. Rings communicate failure four hundred times a year. Bilkul nahi chahiye. The math underneath survives — the user just sees three versions of a plan instead of three unfilled circles.
• No discipline score. No XP. No grades. The word “discipline” doesn’t appear in the product. Discipline is a story we tell about character; bodies don’t respond to character. They respond to volume over time.
• No “transformation.” No before-and-afters. No “six weeks to your best self.” That promise has been broken so many times — by aunties on YouTube, by every Instagram reel with a six-pack countdown — it became its own form of harm.
• No leaderboards or shared streaks. Weaponizing relationships for engagement is one of the things tech got most wrong this decade. We’re not turning your group chat into a guilt machine.

What’s left after subtracting all of that is more interesting than what was there before.

What replaced it

Three small ideas — sound obvious in isolation, almost completely absent from the category:

1. Three versions of every plan, always. Every workout, every meal, every recovery practice exists in three sizes: Full, Small, and Rescue. A 45-minute strength session is also an 18-minute circuit and a 5-minute mobility flow. All three count. The point isn’t compromise — it’s eliminating the binary of “did the plan / didn’t do the plan.” Most of us live in the middle of that binary every week, and the middle should feel like the best place in the app, not the worst.

2. Return is the habit, not consistency. Slowly doesn’t measure how many days in a row you showed up. It measures whether you came back. Two weeks off because Diwali, family, late deployments — the app’s job isn’t to scold; it’s to make Day 15 emotionally cheap. A pre-recalibrated week, a handwritten greeting, no red anywhere. The whole product is shaped around making the return easy.

3. Habit-stacking anchors instead of willpower. Every Rescue routine ships with an anchor — an existing daily moment to attach it to. “3-minute stretch — while the kettle boils for morning chai.” For the first 14 days, the app sends one gentle push at the user’s chosen anchor time. After five completions, the push goes away. By then, the kettle has become the trigger. The environment is doing the work, not the user.

Naming the expectation gap honestly

The hardest design problem in Slowly isn’t technical. It’s this: people search “fitness,” they install the app, and three months in they will quietly notice they don’t look meaningfully different. Three months of consistent showing up does not change a body visibly. That’s just biology.

Most apps would never name this — they’d just lose the user on Month 6 to a competitor promising faster results.

Slowly names it. At Day 90, an in-app card surfaces:

Three months in. Here’s what we hope you’ve noticed: a little more energy. Less of that “I should be exercising” guilt humming in the background. Maybe a workout that didn’t feel like work. Here’s what we want to be honest about: bodies change slowly. Most of the visible stuff usually shows up closer to month nine or twelve, if it shows up at all. You’ve been showing up at human speed. That’s the speed bodies actually respond to.

The bet: honesty earns long-arc retention. The user who’s told the truth at Month 3 is still around at Month 9. The user who was promised a transformation churns the moment the bathroom mirror disagrees.

Slow is the point

The internal team line for Slowly is: Slow is the point. We’re instrumented for Month 12 retention, not D7. We measure return rate after fourteen days inactive. We measure 90-day Season completion. We literally count how often users use the words “kind,” “relief,” or “permission” in feedback.

None of these metrics are exciting. They don’t spike on a dashboard the way streak counts do. They’re also the only metrics I think actually correlate with someone’s life getting better.

What building this taught me

Designing Slowly forced me to be honest about something I’d been avoiding for years: I’d been trying to make willpower do work it was structurally bad at — in trading, in writing, in fitness, in everything. (More on that in this post.)

The same logic that’s now built into Slowly’s engine — eliminate the moments where being a different person is the only thing that could’ve saved you — has crept into how I structure my own days. My morning is non-negotiable for the same reason a Rescue routine is anchored to a kettle. The decisions get made once, calmly, in advance. The 3 PM version of me — tired, mid-sprint, post-difficult-review — doesn’t get a vote.

That’s the meta-claim Slowly is making, expressed as software: a kind environment outperforms a stern self, every time. I believed it intellectually before I started building. Now I believe it because I’ve watched my own habit accumulation start to look different when the environment was redesigned instead of the person.

The bet

A philosophically pure health app — one that respects how an actual Indian working professional actually lives — can compound for ten years where a streak-coded app burns out in nine months. It’s an unglamorous bet. It probably loses on D7. It might win on D365 + D730 + D1825, and if it does, it’ll be because the product never asked the user to be someone they weren’t.

I don’t know yet if Slowly will work. I know it’s the app I would have downloaded four years ago, before three different fitness apps quietly took my hope and gave back a red ring.

If you want to see what we’re building, the landing page is at slowly.health and the work is at SlowlyLabs.