Teach a safety app with dignity
Start with what the person wants to accomplish. Ask whether they want a demonstration, let them hold the phone and practise one step at a time. Age, disability or limited smartphone experience do not by themselves indicate incapacity: the teacher’s job is to remove obstacles, not award grades.
Begin with the goal and consent
Ask which situation the person wants to manage: reassure their circle, ask for help or answer a check-in. A concrete goal limits necessary steps and explains why this function matters. Before touching the phone, ask permission and agree on a pause. Consent to practise is not permission to monitor the person, location or conversations.
Explain, show, let them try
Use plain words for what the control does and what appears next. Demonstrate once, then let the person repeat while holding the device. Correct one thing and ask what they expect instead of demanding a memorised sequence. Support should reduce as confidence grows, not because the teacher is rushed.
Respect pace and accessibility choices
Repetition can strengthen a routine, but there is no correct number of attempts. Pause and test the real phone while considering light, noise, tremor, gloves, language, vision and connectivity. Offer equivalent options: screen reader, larger type, voice, keyboard, phone or a chosen contact. The choice is not a deficit to record.
Visible labels, truthful consequences
W3C recommends common visible words beside a control; “Send SOS” tells more than an isolated icon. The label must be truthful: a command that prepares a request is not “call emergency services”. Before confirmation, show or read action, recipients, message and location. SOS and ALL OK have a countdown and cancellation.
Practise without scoring the person
Observe the route, not performance: where they look, words they use, expectations and feared errors. Record an interface obstacle, never a judgement about age or ability. After offline confirmation, the command remains on the device and may retry in background when allowed; check the outcome. For immediate danger, manually call local services.
Temporary live sharing in 2.2
App Store lists 2.2.0 as released on 5 October 2026, checked on 9 October. Check your installed version and availability in your platform’s store.
An optional point attached to All OK, SOS or a reply remains separate from live sharing. Sending a signal does not automatically start a session: even after SOS, separate confirmation is required. Location proves neither health, arrival nor response.
Frequently asked questions
Does teaching mean doing everything for the person?
No. It means offering explanation, practice and support while leaving the person choice and control.
Is repeating a procedure infantilising?
Not when the person requests or accepts repetition and it supports their own routine.
Does a learned procedure guarantee help?
No. Network, recipients and human response still matter.
Sources consulted
Technical and safety information was checked against the following official sources.
- W3C WAI: clear visible labels
- W3C WAI: label and accessible name
- W3C WAI: consistent identification
- W3C WAI: accessibility principles
- W3C WAI: cognitive accessibility
- Nielsen Norman Group: usability heuristics
- European Commission: 112
- My Safe Circle: manual and limits
- My Safe Circle manual: 2.2 live sharing
- Official App Store listing
Editorial disclosure: this article is published by the team developing My Safe Circle. W3C guidance informs the discussion but does not replace testing with the people concerned. Sources and the product manual were checked on 8 September 2026.
REMEMBER
Leave the person choice and control.
Practise a real routine with consent, accessible alternatives and a backup channel.
Discover My Safe CircleMy Safe Circle supports communication with trusted people. It is not an emergency service or medical device, does not automatically detect events, does not continuously track location and does not guarantee delivery, reading or intervention.