Scroll Friction, Explained: Resistance Instead of Rules

Every screen time tool ever built intervenes in the same place: the door. A timer, a passcode, an interstitial, a breathing exercise, a question asking whether you meant to open this. You cross that door once per session, and then the feed gets every swipe after it for free.

Scroll friction moves the intervention to the swipe. There is no door, no rule and no permission. There is just a scroll that costs something, every single time.

How scroll friction works, precisely

Four things happen when you swipe in an app with friction enabled.

Resistance. Your finger moves and the content does not move with it. A fluid surface rises to meet the drag, and it takes real distance to build. This alone is enough to break most autopilot, because autopilot expects an immediate response and does not supply enough input to get one.

The threshold. You choose how far the drag has to go. At the low end it is a noticeable hesitation. At the high end you are dragging a meaningful fraction of the screen before anything happens.

The bubble. Past the threshold, the fluid pinches off into a bubble under your fingertip, which then rises and leaves the screen. Only when it has left does the underlying app receive the scroll. This is the part that makes the cost felt rather than merely present.

The burst. Flick fast, in the way you flick through a feed without thinking, and the bubble bursts instead of rising. A burst dispatches nothing. This is the crucial asymmetry: deliberate slow input works, and reflexive fast input does not.

That asymmetry is the entire design. The goal was never to make scrolling impossible. It was to make sure the only scrolling that happens is the kind you are present for.

Why it holds up when blocking does not

A block has one point of failure, and it is a good one to attack: the moment you decide you want it gone. At that moment the off switch is available, you are motivated, and the app has just made itself your opponent. The full version of that argument is in why app blockers don't work.

Friction has a different shape.

• There is nothing to resent. You are never denied. Every app, every feed, every message stays available, so the tool never becomes an obstacle you have to defeat.
• There is no single decision that ends it. A block is beaten once and stays beaten. Friction is present on the next swipe, and the one after that.
• It degrades gracefully. On a night when you push through everything, you scrolled deliberately for an hour. That is a normal evening, not a relapse, and nothing about it makes you uninstall the app the next morning.

The failure mode is worth stating plainly: you can always get through. Friction will not stop a decision you have actually made. It stops the thousand non decisions that make up most of a lost evening.

What it feels like in practice

Three things surprise people in the first week.

You discover how often your thumb starts before you do. The first two days are mildly irritating in a specific way: you keep finding your hand already moving. That discovery is the mechanism working.

Sessions end without a decision to end them. Nothing blocks you. You simply stop, usually several minutes earlier than before, because the loop that normally carries you was doing the carrying.

The feed you chose is unaffected. Reading a message, checking one account, looking at something you searched for: none of these involve repeated reflex swiping, so friction is barely noticeable. It bites hardest exactly where the problem is.

Where it runs: Android and iPhone

The mechanic is identical on both platforms. Where it runs is not.

On Android, the overlay uses the accessibility service to see that a scroll is happening inside a supported app and draws the fluid on top of it, so friction applies inside Instagram, TikTok and YouTube themselves. It reads UI structure only, never message contents. Twelve apps are supported, including Instagram, TikTok, YouTube, Facebook, Reddit, X, Threads, Snapchat and Pinterest, all free in Fluid Friction on Google Play, alongside feature level blocking for surfaces you would rather never open.

iOS forbids that outright. No app may draw over or modify another, which is why every iPhone blocker in this category is built on Apple's Screen Time frameworks and works at the level of whole apps. So on iPhone the friction runs inside Fluid Friction's own browser: you open the sites you want there, and the same wave, bubble and burst physics apply to the scroll, one post per deliberate drag. That also unlocks something Android does differently, which is per surface control, because a browser can hide Reels or Shorts while DMs and search keep working.

The tradeoff is honest: on iPhone friction only applies where you browse through the app, not across the whole system. What you gain is that it works at all, on a platform that was never going to permit an overlay. Fluid Friction is on the App Store.

The settings that matter

Friction is not one setting, and the defaults are deliberately mild.

The schedule is the setting people undervalue. A flat setting is chosen for the average hour, which makes it too strict at lunchtime and far too soft at midnight, and the lunchtime annoyance is what gets the whole thing switched off. Why you scroll at night covers how to shape it.