Turning a raw track into a session
A ride arrives either from a watch or as a file. We accept GPX, TCX and FIT,
individually or as .gz and .zip archives, and read
them into a single session record: trimmed start and end, distance, time on
the water, and per-run splits. Speed is taken from the device's Doppler
measurement where the recording carries one, and computed from position only
as a fallback, because position-derived speed on a foil is noisy enough to
invent records that never happened.
Recording on the wrist
Most riders would rather not carry a phone. The eFoilCrew Garmin watch app
records the session on the watch itself, then uploads it to the rider's
account when the watch next reaches connectivity. Pairing issues a
per-device token the rider can revoke at any time; no Garmin account
credentials pass through us. Which data screens the watch shows, and in what
order, is configured from the web app and delivered to the watch.
Reading the board
An electric hydrofoil board keeps its own logs, covering battery and motor
behaviour that no watch can see. We decode those logs over Bluetooth after a
ride and merge them into the session the watch or the uploaded file already
created, so one ride stays one record. This work is in limited testing with
selected riders rather than generally available.
Places and conditions
Riding spots are shared by the people who ride them, with conditions
reports attached. Sessions are matched to the spot they happened at and
enriched with the weather that was actually present at the time, which is
what makes one ride comparable to another months later.
Gear, records and the crew
Riders keep their setups against an equipment catalog, so a board, mast and
wing combination can be attributed to the sessions ridden on it. On top of
that sit performance statistics, leaderboards, personal records and
achievements, and the community layer: profiles, follows, posts, forums and
direct messages.
How the pieces fit
One account, one session record. Whether a ride came off a watch, out of a
board's own log, or from a file exported by some other device, it lands in
the same place and is analysed the same way. That is the whole design: the
rider should not have to care which device happened to be recording.