Live spectator sharing connects the runner's recording device to a viewer on another device. Before using it for a race or club event, test the whole journey: start the recording, open the viewer and check what a supporter can actually see.
Give supporters the correct link
Send the spectator link separately from the participant invitation. Include the expected start window, runner name and a backup meeting plan. Open it in an ordinary browser on a second device; a host's signed-in view may expose controls that a supporter does not have.
For several runners, check how the viewer selects a participant and whether the map follows that person or the whole group. A tap-to-focus control should make the current selection clear. Do not interpret a marker disappearing from view as the runner leaving the event.
Read timestamps before positions
GPS reception, mobile coverage, permissions and battery settings can interrupt updates. A last-known location is not a guarantee of where someone is now. Likewise, an estimated arrival time can change with pace, stops, hills and incoming data. Use a generous meeting window rather than moving across a closed course to chase an ETA.
Official timing and event instructions remain the appropriate sources for results and spectator access. See the marathon spectator guide for the race-day checklist.
Audio, haptics and full-screen cheers
Agree whether the runner wants encouragement during the session. Ask what can be muted and how often prompts arrive. An audio cheer, vibration and full-screen interruption have different effects on attention; a runner should be able to prioritise navigation and their surroundings.
Before promising a watch interaction, verify it on the exact watch, phone and released app version. A browser animation does not prove that a remote watch receives a haptic or that audio works with a locked phone.
Runwiv's current position
Runwiv has a public spectator demo and is preparing shared-session features for launch. The demo illustrates the interface; it is not a live broadcast from a real runner. Check product availability before relying on the planned app for an event. Try the demo and keep session links within the intended audience.