Support

Tap Create Room on the home screen. You get a six character code: read it out to whoever is at the other end of the trail so they can join. Type in your riders, then hit START beside a rider at the top of the trail and STOP beside them at the bottom. The server works out the difference.

Tap Join Room and enter the six character code. The codes use characters chosen to be unmistakable when read aloud. Sessions you have been in are remembered on the join screen, so getting back into one is a tap.

Yes. That is what the app is built around. Times you capture are queued on the phone and sent when signal comes back, and nothing is lost in the meantime. If you have no signal even to start, use Time offline on the join screen to record the whole session on the phone and upload it later.

At the bottom of the trail, Stop by number works with no roster and no connection at all: hit the slab the moment the rider crosses, then say who it was afterwards. The time recorded is the instant your thumb landed, not the moment you finished the paperwork.

Times are shown to a tenth of a second, and that is deliberate. Phone clocks routinely disagree by seconds, so every device measures its offset against the server and converts to server time before sending. Without that, three seconds of clock drift on a two minute run just reads as a bad run and nobody would ever catch it.

What the app cannot correct for is two humans and two thumbs, which is worth about three tenths of a second. Showing milliseconds would imply a precision that is not there, so it does not.

Yes. Press and hold the sync strip at the top of the room screen. Count down over the radio, both of you hit the mark together, and from then on the two phones agree with each other. A duration is a subtraction, so a shared offset cancels out of it even when both phones are wrong about the time of day. The app files those runs as estimated, because "three, two, one, mark" is good to a few tenths and it should not claim otherwise.

Yes. Open Results and tap the run. You can correct it or discard it, and the standings recompute straight away. A leaderboard nobody trusts is worse than no leaderboard, so every run is correctable.

A session and everything in it is deleted one week after the last time anything was recorded in it. Recording something new starts the week again. If you want to keep times beyond that, use Export times in Results before the week is up.

Share a picture in Results paints the leaderboard into an image sized for a story, with everyone's gap to the leader down the right hand side. It is drawn on your phone and never uploaded to us. You can name the session first, and the name heads the card. The session code is deliberately never on it, since anyone holding a code can get into the session.

No. The app reconnects on its own, and anything captured while it was disconnected is queued on the phone and sent when it gets through. Being killed mid-session is survivable too: the app returns you to the session it was in, and elapsed time is recomputed from the timestamps rather than from a running clock.

Email simon@himon.dev with a short description of what happened and what you expected. Screenshots or screen recordings are always helpful, and so is the session code if the problem is with a particular set of times.