DEV Community

Martin Ma
Martin Ma

Posted on Edited on Originally published at dev.to

Short-form video has no stopping cues - that is the whole design

I spent three months tracking why I could not stop watching short dramas.

It was not the episodes. It was that nothing in the interface ever says stop.

What a stopping cue actually is

A book chapter ends. A film has credits. A podcast episode has an outro. Each one is a
built-in moment where you get to decide whether to continue. Short-form video removed all
of them: autoplay, seamless transitions, and a feed that preloads the next clip before
you have finished judging the current one.

The result is that the only decision point left is your own fatigue - and fatigue is the
worst possible decision-maker, because it arrives after the behaviour has already run.

Three things I measured on myself

I logged every session for three weeks, then changed one variable at a time.

  1. Sessions start intentionally, then drift. 71% of my sessions started with a
    specific reason ("check one clip", "look up that actor") and crossed the 20-minute mark.
    So the problem is not starting - it is the absence of a checkpoint afterwards.

  2. A single daily budget does not work. With one global limit, I either blew through
    it by noon and ignored the rest, or hoarded it and felt punished. Splitting the budget
    per app changed the behaviour, because exhausting the video app no longer blocked
    messaging or maps - so there was no legitimate excuse to override it.

  3. Invisible overrides are not limits. When overriding was frictionless and unrecorded,
    I overrode it 5-6 times a week and forgot each time. When the app started showing
    "bypassed 4 times this week", the number itself became the restraint.

What I built instead of a blocker

I did not want another app that hard-locks the phone, because hard locks create a
single dramatic failure mode: you disable the whole thing in a bad moment and lose
everything.

Instead I built three small mechanics:

  • a one-line intention prompt before the app opens (costs two seconds, no punishment)
  • per-app budgets rather than one number for the whole device
  • a visible count of the times you chose to override

That is the entire product. It is deliberately boring, because the mechanism that
survives contact with a tired brain is the boring one.

The honest limits

This does not fix the feed's design, and it is not therapy. If your use is a symptom of
something larger, a timer is the wrong tool. What it does fix is the specific case of
"the session started fine and ended three hours later".

I shipped it as a small iOS app - ChoiceField - mostly because I wanted the
bypass counter to exist and nothing off the shelf had it. The mechanisms are easy to
copy manually: Screen Time limits per app, plus a note where you tally every override.

If you have tried something similar, I would like to know which of the three held up for
you and which one you dropped.

ChoiceField download card

Per-app budget screen

Bypass counter

Daily overview


相关阅读 / Related

Top comments (0)