If the leader drops off, the ride keeps going.

Phones lose signal. Batteries die. A leader dropping off a group ride shouldn't mean the ride is over — it should mean someone else leads for a bit. That's what failover does, automatically, without anyone needing to notice it's happening.

• Detection

  The app notices before you do

  When the leader's connection drops, the group's live-tracking connection detects it almost immediately and promotes a new leader — no one has to notice a stalled marker and manually intervene.

• Promotion

  The first rider to join leads next

  Whoever joined the ride earliest among the remaining riders is promoted. Every screen updates at once — the new leader's app switches to the leader view and starts broadcasting; everyone else re-centres on them.

• Recovery

  The original leader gets it back

  If the original leader reconnects, leadership is restored to them automatically — no one has to hand it back manually, and the temporarily-promoted rider quietly returns to following.

Not the same as ending the ride

Failover only fires on an unexpected drop. Ending a ride on purpose is a separate, explicit action — the leader confirms it, every follower sees a clean "ride ended" screen instead of a leadership handoff, and everyone's track is saved. The two flows look different on purpose: one is a group losing its leader mid-ride and needing to keep moving, the other is the ride being over.

Built to correct itself, not just to react once

A patchy connection is exactly the situation where a phone might miss the message telling it who's leading now. Rather than leaving a rider stuck on a stale role until the ride ends, every device double-checks who's actually leading each time its connection comes back — so even a rider who was briefly offline for the handoff itself lands on the correct screen instead of staying wrong for the rest of the ride.