A better life with your iPhone.

RSS   Advertise with us ↗

Discover. Download. Do more.

Safety Button: what an alert app can and cannot promise

A historical look at location-alert apps, the difference between notification and response, and the questions that matter before relying on one.

Original security illustration for Safety Button: what an alert app can and cannot promise

A location alert from the early App Store

Safety Button belongs to the early wave of iPhone apps that tried to turn a phone into a shortcut for asking for help. A 2009 Macworld Sweden review describes an app that sent location information to a chosen contact. That is historical evidence of its intended purpose, not confirmation that the same software or its supporting service works today.

The original article at this address has not been recovered. This guide therefore examines the idea behind that legacy app without reproducing an unverified endorsement.

An alert needs someone at the other end

Sending a message and obtaining a response are separate events. A contact may be asleep, away from their phone, outside coverage, or unsure what a message means. An interface showing that an alert was sent does not establish that anyone received, read, or acted on it.

Before adopting any contemporary service in this category, establish who receives the alert, whether professional monitoring is actually included, and what the provider says about service availability. A familiar name or reassuring icon cannot answer those questions.

Location sharing needs a clear agreement

A useful review should examine who can see location information, how long the provider retains it, and whether sharing can be stopped. Contacts should understand and agree to their role. Location access also deserves periodic review when circumstances or relationships change.

This is a product-history article, not an emergency plan. For an immediate emergency, contact the appropriate local emergency service. Any future review of a replacement app should identify the exact developer, current documentation, supported region, and limits of the service before making a recommendation.