Design a calm mode for people who need less companion at once

Expressive avatars, typing indicators, unsolicited suggestions and affectionate notifications can create presence. Together they can also overload attention, memory or language processing. A calm mode should not flatten the character. It should let the user control how much motion, urgency and ambiguity arrives at once.

Make presentation adjustable

Offer reduced motion, static avatar, hidden typing animation, adjustable speech rate, text-only input, captions, larger text and a choice to reveal one response at a time. Preserve the same functions across modes. W3C’s cognitive accessibility guidance recommends predictable interfaces, clear controls, enough time, simpler layouts and user control over changing content.

Make language easier to act on

Use literal labels for settings and irreversible actions. A delete control should say what it deletes; “let go of our memories” is emotionally loaded and unclear. Provide a short summary before a long answer, keep instructions in the order they must be performed, and allow the user to ask for repetition. Warmth belongs in conversation, not in obscuring account or safety controls.

Reduce demand loops

Calm mode should default to no streaks, no repeated re-engagement prompts, quiet hours and no simulated urgency. Let the user initiate most check-ins. W3C notes that cognitive and learning disabilities affect attention, memory, language and problem solving in varied ways; no single preset will fit everyone, so every calm-mode choice should remain individually adjustable.

Test a complete task

Ask participants to change voice speed, correct a saved memory, pause notifications and find account help. Record errors, abandonment, backtracking and requests for explanation. Include people with relevant disabilities in design and testing, compensate them, and avoid treating a generic persona as evidence. A hypothetical test where five participants succeed is design feedback, not an accessibility certification.

Protect user preference

Store calm-mode settings reliably, expose them before onboarding animation, and do not reset them after an update. Provide an obvious exit without punishment. Document which surfaces remain outside the mode, such as operating-system notification previews or third-party payment screens.

Define what calm mode changes

Publish a plain checklist: motion reduced, typing animation removed, unsolicited check-ins off, response length shortened, speech slowed and irreversible actions confirmed. Let users preview the mode without committing. If a feature cannot honor the preset, warn before entering it. The decision consequence is concrete: a team should not advertise calm mode while a new animated discovery feed, payment countdown or safety flow bypasses it.

A concrete acceptance check is simple: enable calm mode, close the app, update it, and reopen the same conversation. The preferences should persist before any motion or sound begins. Then complete export and deletion paths with the mode active. If critical account controls become harder to find, the preset has reduced stimulation by reducing agency—the wrong tradeoff.

Calm design is a control layer, not a personality downgrade. Combine it with the multimodal voice audit and the notification pressure audit to test the whole experience rather than one settings page.