A timeline used to have a natural stopping point
An older-style feed was easier to finish because it mostly showed posts in time order. Once you had caught up with the people and pages you followed, there was little new to see until someone posted again. A visible end was not just a screen feature; it reflected a limited, recognizable pool of updates.
Recommendations keep the stream replenished
A modern feed can draw from far more than accounts a person chose to follow. A ranking system selects and orders posts from that wider pool, including suggested videos, creators, and topics. As the reader moves down the page, the service can load more items, so reaching the bottom of one screenful does not mean reaching the end of what is available.
The selection is also less predictable than a simple chronological list. A familiar friend’s update may sit beside an unfamiliar creator’s clip or a post on a newly relevant topic. That variety can make the next item feel worth checking, even when the reader did not open the app looking for it.
Why an ending is a design choice
For an ad-supported platform, more time spent viewing can create more chances to show ads and learn what holds attention. Recommendations help maintain that viewing session by filling gaps that a finite set of followed accounts would leave. The feed’s lack of an endpoint turns “I’ve seen everything” into a decision the user has to make, rather than a signal the interface supplies. In practice, stopping often means choosing to close the app while there are still more posts waiting.
