I'm building a backend-development learning platform solo — the whole thing: Node/Express API, MongoDB, Socket, SQL, live classes, a roadmap, assignments, certificates. Real students, real fees, one developer.
Last week I posted about it here. The most valuable thing that came out of it wasn't traffic — it was one comment.
The comment that changed my roadmap
A developer in the comments pushed back on how I was thinking about retention. My instinct was streaks (the Duolingo flame). Their point, paraphrased:
Streaks are fragile. One missed day and streak-based motivation collapses. Track the % of active days vs total days as your internal health metric — and show the user an all-time tally instead. "You've practiced X times" survives a broken streak in a way "streak: 0" never does.
That reframed the whole thing for me. A streak is a motivator, not a measure. The moment it breaks, it demotivates the exact person who needed one more nudge.
So I shipped it — the same day
I added a lifetime "days practiced" count next to the streak. It counts the distinct days a student actually did the work, and it never resets — even after a missed day.
Streak = the visible nudge. "You've shown up 24 times" = the thing that keeps you going after you miss a day.
Then I realized the bigger lesson
That one comment was worth more than a week of my own planning. So I asked: how do I get more of this from actual users, not just from Dev.to?
I built an in-app "Report a bug / feedback" button. On the platform, once you're logged in: click your avatar (top-right) → Report a bug, type what broke, and hit send — and it lands in a dashboard I triage every day.
Try it here: https://asbackendinstitute.com
The bet: your users' bugs and comments are your real roadmap. Make it stupidly easy for them to hand it to you.
The takeaway
Building solo doesn't mean building alone. The best product decisions this month didn't come from me — they came from a comment, and (now) from a feedback button. My job is mostly to listen fast and ship faster.
If you've built something people use: what's the one piece of user feedback that changed your product the most?
— Akash, solo dev, AS Batch Institute
Top comments (0)