A short-video feed decides what you see next with a simple loop: a huge pool of clips is cut down to a short list, a ranker scores that list, and your reaction to each clip feeds back into the next score. This post draws that loop and explains each part. It describes a generic recommendation loop, not any one platform’s real system.

The loop in four boxes

Video poolvery large Candidatesshort list Rankerscores each clip Your feedone clip at a time filter score order watch time, replays, likes, skips, shareswhat you did with the last clip
The dashed line is the part people forget. The ranker does not only pick clips. It learns from what you do with each one, then picks again. Illustrative sketch.

Two things follow from this shape. The pool is far too large to score clip by clip, so a cheap filter runs first and the expensive scoring happens on a short list. And the loop never stops. A new account has little feedback, so early clips are broad guesses that tighten quickly.

What happens in the first fifteen seconds

0s3s6s9s12s15s allnone hook window loop pointa replay here is a strong signal
A sketch of the usual shape, not measured data. Most of the drop happens early, which is why creators spend their effort on the opening frame.

The signals, side by side

SignalWhat it tells the rankerWeak spot
Watch timeWhether the clip held attention, scaled by clip length.Favors clips that are only long, not good.
ReplayThe viewer wanted to see it again.Looping content can inflate it.
Like or shareAn active choice, so a stronger vote than passive viewing.Rare, so each one carries a lot of noise.
Fast skipA clear no, and cheap to collect.Says nothing about why.

This is a general explanation written for readers who build or study apps. Platforms publish few details about their real systems, so treat the diagram as a mental model and check each platform’s own documentation for specifics.