← Back to library

Who Invented Infinite Scroll (and Why He Says He Regrets It)

Aza Raskin invented infinite scroll in 2006 while working on Firefox's interface at Mozilla, intending to remove the click required to load the next page of a list, and has since said publicly, including in testimony at the New Mexico v. Meta trial, that he regrets not anticipating how the design would be used to maximize time on screen rather than usefulness.

Infinite scroll wasn't discovered. It was built, on purpose, by one engineer solving one specific problem in 2006. What happened after he shipped it is the part he didn't see coming, and the part he now talks about openly.

The problem he was actually solving

In 2006, Aza Raskin was working on interface design at Mozilla. The problem in front of him was small: loading a new page of search results or a long list required a click, and that click was a place where people stopped. He built a page that kept loading automatically as you neared the bottom, removing the click entirely. That's the whole original idea, a fix for pagination, not a plan for attention capture.[1]

What that fix quietly removed

A paginated list has a shape. It has a first page, a middle, and a last page, and reaching the last page tells you something: you're done. Infinite scroll doesn't have a last page. There's always more to load, so there's never a structural signal that says stop. Raskin didn't add anything that captures attention. He removed the one thing that used to end it.

Why he says he regrets it

Raskin has been on the record about this for years, including under oath. Testifying in the New Mexico v. Meta trial, he described not thinking through what happens when a feature built to remove friction gets deployed at the scale social platforms operate at, where every additional minute on screen is the thing the business is optimized to produce.[1] In a separate interview, he put it plainly: he was blind to how the design he shipped for a usability problem would be picked up and used for something else entirely.[2]

That's the part worth sitting with. Nobody had to invent a new manipulation technique to make feeds addictive. They just had to take a legitimate fix for a legitimate problem and never put the ending back.

Why every major feed still uses it

Once infinite scroll existed, there was no reason for an engagement-driven platform not to use it. It's strictly better than pagination at the one metric that matters to a ranked feed: time spent. YouTube, Instagram, TikTok, X, and Reddit all load the next batch of content automatically, silently, before you've decided you want it. The click Raskin removed in 2006 is the same click none of them ever brought back.

That's what a following-only, chronological feed restores, not different content, just a bottom. DoomOff sets feeds back to the people you follow, in the order they posted, which means the list is finite again. You can reach the end. That's the part infinite scroll took away, and it's the part getting it back gives back.

Frequently asked questions

Who invented infinite scroll?
Aza Raskin, an interface designer who worked on Firefox at Mozilla, built infinite scroll in 2006. He wasn't working for a social media company at the time. He was solving a narrower problem: the click required to load the next page of a list.
Does Aza Raskin regret inventing infinite scroll?
Yes, he has said so directly in multiple interviews and in testimony during the New Mexico v. Meta trial. His stated regret isn't the mechanism itself, but that he didn't think through how removing a stopping point would be used once it left his hands.
Why was infinite scroll originally created?
To remove a single point of friction: the click or tap needed to load more results on a page. It shipped as a usability improvement, not as an engagement mechanic.