The stopping cue

An app can fail your life without ever being wrong about it, simply by never ending. Most engagement software is built on a premise stated nowhere in its interface: a session without a close, a feed without a bottom, midnight as a timestamp like any other. Life runs on the opposite premise. Days end, weeks turn, attention rises and falls with a body attached to it, and everything alive eventually stops. The fourth REAL question asks which premise a technology honors: does it respect that your life is finite and cyclical, or does it feed on unbounded attention?

The mechanism turns on a feature so small it looks typographic: the ending. A page-end, a bottom to the feed, a session that closes are stopping cues, built-in moments in which a person can notice they are done. Aza Raskin, who invented infinite scroll in 2006 and has spent years publicly regretting it, describes the pattern exactly this way: it removed the page-end, autoplay then removed the next decision, and what remains is consumption without punctuation. Strip the endings from a design and the question of whether to continue is not asked and answered badly. It is never asked again. The design answered it once, at ship time, in its own favor, and that answer stands every night thereafter. A design with no ending has made the decision to continue on your behalf, permanently, which is why surfacing from a feed feels like waking: the faculty that chooses was switched off while you were inside.

Living design restores the punctuation, and in shipped form it looks modest. Notifications batched into predictable windows convert always-on vigilance into availability you can plan a day around. A session that closes and does not immediately offer its successor is telling the truth about what a session is. A few products ship an actual goodnight and mean it: you are done here tonight, and the screen ends. None of this makes the software worse at its job; it defines the job as something that can be finished. The honest caveat belongs in the open, because we hold it to the same grading as everything else: a decade of frictionless connection tooling has coincided with rising reported loneliness, and whether the always-on premise caused the loneliness is still argued in the literature. The structural argument does not need the causation settled. A person’s capacity for connection is finite and renewed in cycles, and software indifferent to the cycles draws down what it does not replenish.

So the audit is the question our research kept circling until it condensed the whole test into a sentence you can carry: does this interaction leave you with more capacity for connection than you started with, or less? Every session answers it, whether or not anyone asks. Builders can ship their answer: a bottom in the feed, an end in the session, a goodnight in the product, because an ending is a design’s way of acknowledging that its user has somewhere else to be. And anyone can run the audit tonight on the last app still open: if you cannot remember deciding to be there, the deciding was done for you, and the mornings belong to whoever takes it back.