How Infinite Scroll Changes Your Sense of Time

A social media session doesn't feel like it lasted 45 minutes. It feels like it lasted 10, maybe 15. That gap between felt and actual duration isn't random — it follows directly from how feed interfaces are structured. Specifically, from what they remove.

Most media formats build in temporal reference points as a matter of course: a page number, a timestamp, a progress bar, the physical weight of what you've already read. Feeds strip all of these out. The result is a session with no internal way to track how much time has passed.

What other formats tell you that feeds don't

The difference between a social feed and other media formats isn't just content — it's the structural information each format provides about where you are in it. Open a book and you know what page you're on, what chapter you're in, and roughly how far through the book you are. These aren't decorative features. They let you situate yourself in time.

The feed provides no indication of how long you've been in the session, how many posts you've seen, or how much remains. There's no position in something with no total. Without these markers, estimating elapsed time during a session requires an internal clock that the format does nothing to support.

Why Aza Raskin describes the design as removing a moment of choice

Infinite scroll was invented by Aza Raskin in 2006 as a way to eliminate the friction of paginated feeds — where reaching the bottom of a loaded page required clicking to load the next one. The technical problem it solved was real: the click interrupted the reading experience.

What the click also did, incidentally, was create a natural pause. A small interval where you were no longer looking at content and were, instead, waiting for more. That interval was a moment in which the question of whether to continue could naturally arise.

Raskin has since spoken publicly about the design's effects.^[1] He describes infinite scroll as eliminating that pause — so the next piece of content arrives before any gap opens between viewing the current one and deciding to continue. When impulse and action happen without an interval between them, the decision to keep going is never explicitly made. The session simply continues.

How progress markers shape your sense of duration

When you know you're on page 180 of 340, you have a clear sense that you're about halfway through the book. That information shapes how you experience the remaining time — you can calibrate your pace, decide whether to continue, estimate when you'll finish. The progress marker functions as a temporal anchor.

A podcast timestamp works the same way. You're 22 minutes into a 45-minute episode. That number tells you something concrete about where you are in time, not just content.

Feeds offer no equivalent. There's no position in a stream that doesn't have a total. You can't be "halfway through" something with no end. The absence of progress markers isn't a minor omission — it removes the structural basis for knowing how long you've been in the session. The only clock available is the one in your head, unsupported by any external reference.

Why the scrolling gesture gives no temporal information

There's nothing in the scrolling gesture itself that accumulates into a signal about elapsed time. The 200th swipe feels identical to the 5th. The content that loads in response is formatted the same way. The interface looks the same. Nothing in the interaction changes as a function of how long you've been in the session.

Compare this to other navigation: turning pages in a book builds a visible, physical stack of what you've read. Advancing through a podcast moves a timestamp marker along a bar. Both of these provide cumulative feedback — the longer you've been engaged, the more visibly something has changed.

Scrolling a feed provides no cumulative feedback. Each gesture produces an outcome indistinguishable from any other gesture. There's no way to read duration from the interaction itself, because the interaction is designed to look the same regardless of how long it has been going on.

Why each scroll commitment feels small even when the session is long

The commitment to see the next item in a feed is small at the moment it happens. One more post. One more video. The content that appears takes a few seconds to a few minutes. The next item is already loaded below. Nothing about the individual decision registers as significant.

But these individually small commitments don't stay small in aggregate. A session made up of dozens of items that each felt brief still took however long it took. The felt scale of each unit doesn't adjust the total.

This is the same dynamic that makes small recurring costs hard to account for. Each individual charge is small enough that it doesn't register at the moment it processes. The annual total of average daily phone use looks different from any individual session the same way an annual subscription total looks different from any individual monthly charge — the unit of measurement changes what you see.

What the gap between felt and actual session length costs annually

Studies of self-reported phone use consistently find that people estimate their usage lower than their phone's screen time data records. Harmony Healthcare IT's data on U.S. phone use puts the reported daily average at around 5 hours and 16 minutes.^[2] Most people, when asked, put their estimate lower than that.

Whatever the gap is for any individual — an hour, 30 minutes, 15 minutes — it compounds across the year. An underestimate of one hour per day is 365 untracked hours annually. At 8 hours each, that's about 45 additional workdays that don't appear in most people's mental accounting of where their time goes.

At the reported average of 5 hours and 16 minutes daily, the annual totals come out as follows.

If you want to see what your actual daily usage translates to in the same terms, the Doom Scroll Cost Calculator shows the full picture in about 30 seconds. If you're working from your phone's screen time data rather than an estimate, the number you get back will be more accurate than most people expect it to be.

What stays constant regardless of how time feels during a session

Perception doesn't change the actual total. A session that felt like 10 minutes but lasted 40 still cost 40 minutes. The feed doesn't adjust the clock to match how the session felt — it only affects what you're likely to believe when you're not looking at the data.

Your phone's screen time data records the actual total. Screen time tools on both iOS and Android track per-app usage down to the minute. That data is available and doesn't require an estimate. Most people don't check it regularly, which means the gap between felt and actual usage persists without correction.

The same dynamic applies to any cost that processes without requiring attention. Subscriptions that renew on autopay cost what they cost regardless of whether you thought about them. The monthly charge doesn't adjust to reflect how much you used the service or whether the renewal felt significant at the time. The normalization of recurring costs and the normalization of scrolling time work the same way: a number that doesn't surface regularly stops feeling like a real number, even when it continues to accumulate.