Growth & usage

When accounts were created

Horizontal bars show account counts; each row is a UTC period. The current period is incomplete. This history covers accounts that still exist, including disabled accounts. Deleted accounts cannot be reconstructed.

Cloud adoption

Current saved records belonging to existing accounts. These are not lifetime totals. Rides saved only on a phone, deleted rides, and failed uploads are excluded. Recent riding uses the ride start date, not upload time.

Recorded ride distance

Distance from currently saved cloud rides belonging to existing accounts, grouped by ride start date in UTC, not upload date. The current period is incomplete. Phone-only rides, deleted rides and failed uploads are excluded. Zero-distance rides are valid; missing or invalid distances are excluded. Values are rounded to one decimal place.

Rides by length

Counts currently saved cloud rides by recorded distance. The first two bands make empty and short test rides visible separately from meaningful riding. Missing or invalid distances are excluded and reported above.

Where rides happen

Anonymous aggregate coverage from cloud ride archives. Fixed-size markers keep riding areas visible at every zoom level. Each map cell counts a ride at most once, regardless of speed, stops or GPS sampling frequency. No account IDs, ride IDs, timestamps, start/end markers or individual tracks are sent to this page. Sparse cells are included.

Configured sensors

Bluetooth and ANT+ component entries saved on bikes, matching the app’s sensor count. The same physical sensor assigned to multiple bikes may be counted more than once. This measures configuration, not successful connections or use during rides.

Recent app reports

Distinct accounts with a successful app device report in the rolling last 7 or 30 days. Reports are best effort on sign-in/resume and throttled in memory for 24 hours. This is an activity indicator, not complete daily/monthly active-user or retention measurement.

One latest report per account across phones. Missing platform reports are Unknown. Version counts cover reporting accounts only; old reports can be stale.

What we can measure next

Saved ride summaries also contain duration, shifts and sensor-type metadata. Sensor types describe captured/configured profiles; valid-data coverage can support a more useful “rides with sensor data” metric after coverage is checked.

Reliable app-open trends, activation funnels, churn and retention need event history or scheduled aggregate snapshots. A last-sign-in date is not a reliable measure of app use.