Why Reels and Shorts Are Harder to Stop Than a Video

A single video has an ending, credits roll, a screen changes, and there's a moment to hand the phone back. Reels and Shorts don't have that moment built in at all, one clip ends and the next starts before anyone's had a chance to decide whether to stop.

Why does a child resist stopping Reels or Shorts more than a regular video?

Because there's no natural pause. A regular video ends, and even a young child recognizes that as a stopping point, whether they like it or not. A short-form feed is built to remove that moment entirely, one clip flows into the next automatically, with nothing marking where one thing ended and another began. Asking a child to stop mid-scroll is asking them to invent their own stopping point in a format specifically built not to have one.

Why is it designed that way?

Because it works, for the platform. Autoplay and an endless, algorithmically chosen feed are standard design choices across every major short-form video product, not a flaw specific to one app, and they're built to maximize how long someone keeps watching, not to give a natural exit point. That's true for adults too, but a child has far less built-in resistance to a feed engineered specifically to keep pulling them into one more clip.

Can I just block Reels or Shorts specifically, but leave the rest of the app open?

Not really, and it's worth being honest about that limitation rather than implying it's possible. Blocking works at the level of the whole app, not a feature inside it. There's no way to let YouTube open for a subscribed channel's videos while keeping its Shorts tab closed, or let Instagram open for messages while blocking Reels specifically, since both live inside the same app.

So what actually works instead?

Treat the whole app as the unit that gets blocked or allowed, rather than trying to carve out one feature from it. If Reels or Shorts specifically are the problem, blocking the entire app, on a schedule or all the time, is the only version of that control that actually exists right now. For a child who genuinely needs an app for a specific reason, a school YouTube channel, for instance, a scheduled window that opens the whole app at a set time and closes it again afterward is closer to what's actually achievable than trying to filter what happens inside it.

Does a timed unlock help with this specific problem?

A little, since it at least puts a hard stop on the session even if the feed itself never signals one. Setting a fixed length upfront, rather than trying to interrupt a scroll once it's already started, means the ending doesn't depend on anyone noticing it's time to stop. CrenelView's timed unlock works this way: pick a length, and the app closes itself when it's up, regardless of what's on screen at that moment.

The feed was built to never end on its own. The stop has to come from outside it, a schedule or a timer, since it won't come from the content itself.