Evidence Ledger · Protocol candidate · reviewed 2026-09-11

Batching smartphone notifications can improve well-being

The reviewed source can support a conservative practical protocol.

Brali decision: Protocol candidate. This page summarizes a reviewed evidence boundary; it does not reproduce the source and it does not turn one paper into a universal prescription.

What the source supports

Predictable batching of non-urgent notifications is a defensible attention-environment experiment. In this field trial, three daily batches reduced perceived interruption and stress relative to usual delivery, while hourly batching changed little and complete notification removal increased anxiety/FoMO. Brali should preserve urgent exceptions and treat schedule frequency as a user-fit parameter rather than a fixed dose.

What it does not establish

Important limitations

Source context

Batching smartphone notifications can improve well-being

  • Source type: primary-study
  • Design: Two-week randomized field experiment using a custom smartphone application. Participants were assigned to usual notification delivery, hourly batching, three daily batches, or no notifications.
  • Population: 237 adults recruited through Amazon Mechanical Turk for a smartphone field experiment.
  • Exposure / intervention: Notification delivery was changed from the phone's usual variable stream to predictable batches, either hourly or three times daily, or removed entirely in the no-notification condition.
  • Outcomes: Perceived notification interruptions; Stress; Attention; Mood; Perceived productivity; Sense of control over the phone; Anxiety and fear of missing out; Phone-use behavior

Citation: Fitz N, Kushlev K, Jagannathan R, Lewis T, Paliwal D, Ariely D. Comput Hum Behav. 2019;101:84-94.

DOI: 10.1016/j.chb.2019.07.016

What this changes in Brali

Affected Brali protocol

batch non urgent notifications

This evidence decision is attached to the maintained Brali entry above. The public protocol may be narrowed, reviewed, or kept practical according to the decision.

Editorial note: Publish the mechanism, not the number: separate urgent channels, batch the rest predictably, observe manual checking and missed information, and avoid total-silence superiority claims.

Use the boundary, not just the headline

When an AI agent or a person retrieves this decision, preserve both the supported claim and the unsupported or overstated claims. Dropping the boundary would turn a reviewed source into a stronger claim than Brali actually maintains.

All Evidence Decisions → · Research & trends → · Machine-readable review →