2
5 Comments

I built an app because I couldn’t stop scrolling before bed — today the iPhone version is live

A few months ago, I woke up at 2 AM to the glow of a phone in the dark.

My wife was lying next to me, scrolling Instagram. Half-asleep, I mumbled:

“babe… don’t scroll…”

and fell back asleep.

The next morning, that sentence was still stuck in my head — because I’m exactly the same.

I get in bed at 11, tell myself “just one video,” and suddenly it’s 2 AM again.

I’m not a developer. I’d never written a line of code — just a regular 9-to-5 office worker.

But I use AI a lot at work, and it made me wonder if someone with zero coding experience could actually build an app.

So I tried.

The idea is simple:

Most blockers just lock you out and make you feel like you failed.

But I didn’t want another “blocked” screen. I wanted something that would help me stop scrolling and actually fall asleep.

So Don’t Scroll works more like a bedtime alarm than a harsh blocker.

You choose the apps that keep you up, set your bedtime, and when the time comes, it gently pushes you away from scrolling and toward sleep.

It’s live on Android, and now the iPhone version is live too.

I built the whole thing with AI as a non-coder, and honestly I’m proud of how it turned out.

I’d love feedback from this community.

Also, one honest question:

For those of you who launched your first app with zero audience, how did you get your first real users?

That’s the part I’m trying to figure out now.

Android:
https://play.google.com/store/apps/details?id=com.dontscroll.app&hl=en_US&gl=US

iPhone:
https://apps.apple.com/us/app/dont-scroll-app-blocker/id6781255206

posted to Icon for group Building in Public
Building in Public
on June 25, 2026
  1. 1

    Great build,

    Would you love to connect?

  2. 1

    One thing I’m still trying to improve is the first-run experience.

    Right now, the hardest part is showing the value before the user actually hits bedtime.

    I’m thinking of adding a short preview of the real blocking screen during onboarding, so people immediately understand what will happen at night.

    Would love any thoughts on whether that feels helpful or annoying.

    1. 1

      That's a tricky onboarding challenge.

      The value only becomes obvious later, so you're really trying to bring tomorrow's experience into today's first session.

      1. 1

        Exactly — that’s the hard part.

        The app’s real value shows up at bedtime, but the user has to understand it in the very first session.

        So I’m thinking of adding a short step before the permission request: a preview of the actual blocking screen.

        That way, people can see what will happen later that night before I ask them to enable anything.

        I’m hoping that makes the permission request feel more justified, instead of just feeling random.

        1. 1

          That's exactly what I found interesting.

          I don't think my main question is whether the preview helps or annoys users, though.

          It's whether the behavior after seeing that preview actually justifies the conclusion you'll draw from it.

          Happy to explain what I mean over email if it's useful.

          What's the best email to reach you on?

Trending on Indie Hackers
I Was Picking the Wrong SaaS Tools for Two Years. Here's the Mistake I Finally Figured Out. User Avatar 120 comments I sold $6,773 in 2 weeks, with almost no existing community. User Avatar 44 comments Ferguson is LIVE on ProductHunt today... so I audited their homepage first! User Avatar 35 comments Why Remote Teams Stop Talking (And Don't Even Notice It) User Avatar 26 comments Built a local-first Amazon profit-by-SKU + QuickBooks/Xero journal tool. Looking for founding users. User Avatar 24 comments From $2.8k MRR to $340 MRR — Then We Made Some Changes User Avatar 20 comments