Visual, audio and haptic feedback in a safety app

Combine channels, do not stack effects

Text communicates meaning, an icon orients, sound signals change and haptics add sensation. None should be the only cue for an important action. Tie feedback to the correct state and keep the logic consistent across recurring routes so the message remains interpretable.

Test text, icon, sound and haptics

For each state, write what the person needs to understand and test it on the real device. Show a visible label with the icon, hear the sound and feel the haptic. If channels conflict, reduce the effect or clarify text instead of adding intensity.

Test silent mode, reader and environment

Try silent mode, low volume, headphones, screen reader, bright light, noise and a phone at a distance. Confirm the state is available without audio and reading order retains meaning. Haptics may not be felt; sound may be inappropriate or disabled.

Respect customisation and accessibility

Let people choose volume, haptics, contrast, text size and presentation where the system allows. Do not hide important meaning behind one preference. Customisation should preserve distinction and meaning: changing intensity must not change the state communicated.

Do not confuse feedback with confirmation

An animation, sound or haptic may say a control activated or state changed; it does not prove delivery, reading or intervention. SOS and ALL OK still use explicit confirmation with a countdown. Show understandable status text and a way to recover.

Use a test matrix

Test every state with all channels, then disable one at a time. Repeat with assistive technology and in the intended context, recording what was perceived and understood. If no signal is enough, keep text, a call or human contact as an alternative; no sound is guaranteed on every device.

Frequently asked questions