DEV Community

Henry Godnick
Henry Godnick

Posted on

A dependency-install iPhone app blocker rule to stop doomscrolling

#productivity

The easiest time to lose 20 minutes to your phone is not usually when you are avoiding work on purpose.

It is the tiny waiting window.

You run:

npm install
Enter fullscreen mode Exit fullscreen mode

or:

pip install -r requirements.txt
Enter fullscreen mode Exit fullscreen mode

or a Docker build, package install, migration, upload, or test bootstrap.

Then there is a gap.

Not a real break. Just enough dead air for your hand to pick up your phone.

You open TikTok, Reels, YouTube Shorts, Reddit, or whatever your default loop is. By the time the install finishes, your brain is not in the code anymore.

That is the part Screen Time usually fails at.

A time limit asks you to make the right decision after the loop has already started. A better iPhone app blocker rule removes the decision at the exact moment the loop usually begins.

The dependency-install rule

Before starting a command that might take more than 30 seconds:

  1. Start a focus session.
  2. Block the apps and websites you use for quick hits.
  3. Set a very small open limit for fallback apps.
  4. Keep strict mode on if you know you will override yourself.
  5. When the command finishes, review blocked attempts instead of pretending the urge was not there.

The point is not to become perfectly disciplined.

The point is to stop treating distraction like a motivation problem when it is actually an enforcement problem.

If your phone is available during every little wait, your brain learns that waiting means scrolling. If your iPhone app blocker catches that first tap, the waiting window stays a waiting window instead of turning into a doomscrolling session.

A practical setup

For dev work, I would block:

  • TikTok
  • Instagram Reels
  • YouTube Shorts
  • Reddit
  • social feeds
  • any browser path you use as a backup feed

Then I would allow only a few intentional opens for apps you actually need, like messages or calendar.

The blocked-attempt log matters because it shows the real trigger. Maybe it is dependency installs. Maybe it is CI. Maybe it is waiting for a reply. Maybe it is the moment after a task is done.

Once you see the pattern, you can block the trigger instead of relying on willpower every single time.

That is the reason I like Monk Mode for this use case: it is built around app and website blocking, open limits, strict modes, focus sessions, challenge alarms, recovery analytics, and blocked-attempt logs.

If you are looking for a Screen Time alternative or a stricter app blocker for iPhone, this is the exact kind of rule worth testing.

Monk Mode: https://www.monk-mode.lifestyle/index.html#pricing

Top comments (0)