Live location sharing for motorcycle rides, done properly

“Text me when you get there” is the standard arrangement, and it fails in the obvious way: the text arrives when everything is fine, and nothing arrives when it is not. Silence is ambiguous — it means either “still riding” or “in a ditch”, and the person at home cannot tell which.

Live location sharing removes that ambiguity. Done badly, it introduces a different problem. Here is how to get the good half without the bad.

Two problems, not one

The reassurance problem. One person at home wants to know you are moving and roughly where. They do not need corner-by-corner detail; they need to be able to check, and they need it to end when the ride ends.

The cohesion problem. Six riders on a 200-kilometre day want to not fragment. The fast riders vanish, the last rider misses a turn, and forty minutes go by before anyone realises. This needs live position for everyone in the group, all at once, plus alerts when something changes.

These want different designs, and an app that treats them as one feature ends up doing both badly.

The right shape for reassurance: a per-ride link

The design we settled on is a link minted for a specific ride:

• Created when you want it, not running by default.
• Opens in a browser. The person watching does not need an account or the app, which matters when it is a parent.
• Ends with the ride. When you end the ride, the link stops showing a position.
• Revocable mid-ride, in one tap, if you change your mind.
• Shows position, not history. It is a “where is he now” tool, not a searchable archive of your movements.

You can see who has opened it, and if a viewer happens to have the app they show up by name rather than as an anonymous visitor.

Why permanent sharing is a bad idea

Always-on location sharing feels like the simpler version of the same feature. It is meaningfully riskier, and the reason is that continuous data reveals patterns rather than positions.

A week of continuous location tells anyone holding the link where you live, where you work, when the house is empty and which nights you are out. A ride link tells them where you were on Sunday between 9 and 2. The first is a profile; the second is a fact.

Links get forwarded. Phones get unlocked. Relationships change. Design for the version you would be comfortable with in a year.

For groups: the dot is not the feature

Six dots on a map is nice. The useful part is what the app notices about them.

A rider has stopped moving. This is the alert that matters. Someone pulled over at the side of a road — a mechanical, a wrong turn, a call of nature, or something worse — is invisible on a map full of moving dots and obvious when the app says so. The group gets told, rather than discovering it at the next fuel stop.

Gaps in the group. How far behind the back marker actually is, in kilometres, rather than “he’ll catch up”.

Hazard reports flow backwards. A rider who finds gravel across the exit of a left-hander flags it, and the riders behind hear about it before they see it — which is the only useful time to know.

Everyone is on the same route. Position sharing solves nothing if half the group has a different route loaded. Plan the group ride properly and the map, the stops and the RSVP list all come from one place.

Alerts should be spoken as well as shown. Reading a notification while riding is exactly what you do not want the group doing, so the ones that matter are announced through your helmet comms.

Battery, the practical constraint

Live sharing means the phone is using GPS and the network continuously. That is real drain, on top of recording and navigation.

• Ride with a charging lead. This is not optional on a full day. See the mount and power guide.
• Expect the position to update on a sensible cadence rather than every second. Sub-second updates cost battery and tell a watcher nothing extra.
• Through poor coverage, updates queue and catch up. A stale dot means no signal, not a stopped rider — which is why “stopped moving” alerts use the sensors rather than the last update time.

A sensible default setup

For a solo ride on good roads: share with one person, ride, forget about it. It ends when you end the ride.

For a solo ride somewhere remote: share with one person, turn crash detection on, and tell them your expected return time. Location sharing plus a human who knows when to worry is a far better system than either alone.

For a group: everyone in the group ride, positions visible to each other, hazard reports on, and one person nominated as sweeper. The app handles the map. The sweeper handles the humans.

What we do not do with it

Since this is location data, the commitments should be explicit: live positions are transient, they are not built into a profile, they are not sold, and they are visible only to the people you gave a link to or the group you are riding with. When the ride ends, the sharing ends. Full detail is in our ride-tracking privacy write-up.