Essay · 6 min

Why we refuse infinite feeds for bookmarks

Feeds optimize for time-on-site. Collections optimize for memory. Here is the product tension we navigate every sprint.

Social feeds reward novelty—even when the novelty is shallow. Bookmarking products often inherit that pattern because the same UI kits are reused. We deliberately cap auto-loading and instead surface collections you chose to pin, so the homepage feels like a shelf you organized, not a slot machine.

Return visits matter more than raw scroll depth. When someone opens a saved board, they usually need a specific link fast. Infinite scroll hides edges; bounded collections expose them.

We still experiment with recommendations, but they arrive as optional modules—never as replacements for your own ordering. That stance costs short-term engagement metrics and buys long-term trust.

    Why we refuse infinite feeds | Pquko | Pquko