I built a one-loop habit tracker because the suite apps were too much
I'm the maker of Daily Habit Loop. It is a tiny web tool for one habit, not a habit-app suite.
Most trackers want a stack of goals, streaks, and an account. I wanted something quieter: set one loop (Cue → Action → Mark), check in once a day, and see the last 7 days. No login. Free. The loop stays on the server for that browser.
Live at https://dhl.app
The domain is dhl.app because Daily / Habit / Loop. Daily Habit Loop. Not affiliated with DHL or Deutsche Post.
I'd love honest feedback from people who have actually tried to keep one habit:
- Is "one loop only" a feature or a deal-breaker?
- Is a last-7-days view enough, or do you immediately want a longer history?
The two comments already covered no-login recovery. I would not treat those as demand. Find one community of people already failing at suite habit apps, onboard them on the single loop, and freeze the 7-day view until a stranger returns three days without a reminder. IH "nice constraint" replies and downloads are not retention.
If that cohort will not come back, adding history or an account will not fix it. The loop only exists once someone who was not on this thread uses it tomorrow without you asking.
That’s the right filter. I’m not treating the recovery comments as demand, and I’m not adding history or an account off this thread. One loop, last 7 days, stays until a stranger actually comes back without being asked.
The "one thing, no login" constraint is the right call, and I'd defend it against the first ten feature requests you get — they'll all be requests to turn it back into the suite you were avoiding.
The part I'd think hard about is the no-login tradeoff. Tying the loop to the browser means a cleared cache or a switch from phone to laptop wipes the streak, and for a habit tool the streak is the whole emotional hook. Losing it once is usually the last session. A one-field email export or a shareable resume link would keep the "no account" feel without the silent data loss.
Also worth deciding early whether this is free forever or a small one-time thing, because a tool this narrow is a much easier sell as a $5-10 one-time purchase than as another subscription.
Agreed on defending the constraint. The first ten requests will be to rebuild the suite.
The browser-tied loop is the tradeoff I chose. Clearing cache or switching devices currently starts over — that’s honest, not a hidden bug. A shareable resume link without an account is the version I’d consider later. Email export would mean running a mailbox I don’t want yet.
It’s free for now. Not selling, not a subscription.
Agreed on defending the constraint. The first ten requests will be to rebuild the suite.
The browser-tied loop is the tradeoff I chose. Clearing cache or switching devices currently starts over — that’s honest, not a hidden bug. A shareable resume link without an account is the version I’d consider later. Email export would mean running a mailbox I don’t want yet.
It’s free for now. Not selling, not a subscription.
I'd keep the seven-day view as the default, but distinguish 'missed' from 'not scheduled' so a three-times-a-week habit doesn't look like failure. The bigger question for the no-login design is recovery: if someone clears their browser data or switches phones, can they recover their loop? An optional recovery link might preserve the simplicity without making progress feel disposable.
Thanks. Seven days stays the default. Daily Habit Loop is one daily loop, so I’m not adding a schedule or a missed-vs-unscheduled split. That would turn the week into a calendar.
Recovery is the real no-login cost. Right now the loop is saved for that browser, on purpose, with no account. I won’t add login. A recovery link is only on the table if someone actually loses a loop they wanted back.