Skip to content

Documentation

Rides, maps and sharing

What gets recorded, what the charts show, and how to get the data back out.

While the wheel is connected and you are moving, the app writes the ride into your phone's storage. None of it leaves the device.

Ride history#

The history lists your rides with a date, a distance and the headline numbers. Inside a ride you can open a chart of any recorded reading.

  • Pinch to zoom, centred where your fingers are.
  • Drag with two fingers to pan the zoomed window.
  • Several rides can be selected and deleted at once.
Ride history on Android: top and average speed, peak PWM, battery used and distance per ride
Android. Export and import sit at the top.
Ride history on iPhone: duration, distance and top speed per ride
iPhone. The same list.
A ride broken down: the summary and the choice of readings to chart
Ride summary and the readings to chart.
A chart of speed, PWM and voltage on one time axis
Several readings on one axis.

Route recording and the map#

Turn on route recording and the app logs your position while a ride is active. Afterwards the route can be viewed on the map.

The map does more than draw a line: tapping a point on the route shows the full telemetry at that point, so you can see the speed and PWM you carried through a particular climb. The app also builds an elevation profile from the track.

Route recording needs permission for precise location. Without it everything else works as usual, there is simply no track.

Ride card#

Any ride can be turned into an image to send to friends. The card carries the route, the date, distance, ride time, top and average speed, peak PWM and battery used.

Most of it is adjustable: theme, accent colour, colouring the track by a reading of your choice, and which tiles appear. Tapping a tile swaps it for another reading from the same ride.

A ride card on the dark theme: the route on a map, distance, top and average speed, peak PWM, battery used and an elevation profile
Dark theme.
The same card on the light theme, with the track coloured by PWM and a scale
Light theme, track coloured by PWM. The card follows the language of the app.

How much space it takes#

You decide how detailed the recording is.

  • Recording rate: every frame, or every second, third and so on. The app shows how many snapshots and roughly how many megabytes that works out to per hour of riding.
  • Retention: starting a new ride evicts rides older than the period you choose. While there are no new rides, nothing is touched.

Frames that set a new record for the ride in speed, PWM or current are always written, whatever rate you picked. Otherwise a sparse recording would drop exactly the moments people open the charts for.

Export and import#

  • Every ride, telemetry sample and route point exports to a single spreadsheet file and imports back. This is how you move history to a new phone, or between Android and iPhone.
  • Importing does not create duplicates: rides and samples are matched on stable keys.
  • A single ride's track exports as GPX, which third-party maps and sports apps understand.

Dump player#

The app can record the raw conversation with the wheel and then replay it as a live ride, with seeking and fast-forward. The dashboard, the charts and the alerts behave exactly as they would with a real wheel, and nothing is written to the ride database.

This is the main tool when something about a wheel needs explaining or a new model needs support: send me the recording and I see exactly what your app saw.