Skip to content

Blog Practical setup

Perceived time and anxiety: clear send status

Published · 2 min read

When an important action appears stuck, seconds can feel longer and invite repeated taps. A useful interface shows the current step, last check, and next path without diagnosing anxiety or inventing precision.

Recognise perceived time

A loader without explanation invites guesses: “did it send?” and “should I tap again?”. Reduce uncertainty with short words and an observable change.

Do not label an emotional response as a disorder. Instead observe which information is missing and which state the person is seeking.

Show real progress

Break the path into verifiable steps such as preparing, server request, notification, and response. Show the current step only when the product actually knows it.

A percentage that rises without an event creates false confidence. Prefer “checking” with refresh or an explicit alternative.

Say what is waiting

Explain whether the app awaits network, server response, permission, recipient, or human confirmation. “Waiting” alone does not support a decision.

Add a timestamp for the last attempt or check. Time helps only when its event and freshness are clear.

Be honest about uncertainty

“Outcome not confirmed” differs from “failed”: the system does not yet know whether delivery is complete. Do not turn uncertainty into an automatic new send.

Offer Refresh, safe close, or the agreed channel. Say what was saved and what remains unverified.

Handle notifications and interruptions

A notification should support the next step, not compete with a wall of signals. Respect system settings, focus, and the person’s chosen modes.

A persistent alert or sound cannot guarantee attention. Keep status in the app and do not simulate progress with repeated notifications.

Prepare an alternative

Try slow network, inactive app, locked phone, and delayed notification. People should know when to refresh, wait, call, or use SMS.

In immediate danger, the local emergency number comes before interpreting an app state. Document the real path, not a reassuring percentage.

Frequently asked questions

Does a percentage always reduce anxiety?

No. Without a real event behind it, it can create false confidence. Show verifiable steps and what the system is waiting for.

Does “sent” mean someone replied?

No. It is a system state; delivery, reading, and human response are different events.

How can repeated taps be avoided?

Show current state, last check, and one clear next step, distinguishing failed from not confirmed.

Sources consulted

Technical and safety information was checked against the following official sources.

Editorial note: this guide applies W3C principles on interruptions, alerts, and focus to safety notifications. Sources were checked on 8 September 2026; states and timing depend on the app and operating system.

LOOK AT STATUS

Say what the system is waiting for

Test progress, timestamps, uncertainty, and fallback without fake percentages.

Explore My Safe Circle

This guide covers interface clarity, not clinical assessment. In immediate danger, call the relevant local number.