4 setups

Two things can feed the screen. Two phones can hold it.

A Garmin watch or the phone’s own GPS with a Bluetooth heart rate strap; an iPhone or an Android phone. Each combination pairs differently, records the ride somewhere different, and treats pause differently — so each has a page that says exactly what it does.

Fed byiPhoneAndroid

Garmin watchSettings · Garmin

Garmin watch and iPhonePair a Garmin watch to CycleBridge on an iPhone through Garmin Connect’s own device picker; the watch records the ride, the phone shows it.How it works Garmin watch and AndroidPair a Garmin watch to CycleBridge on Android by picking it from the watches already in Garmin Connect; the watch records, the phone shows.How it works

Phone GPS and a heart rate strapSettings · This Phone

iPhone GPS and a heart rate strapNo watch: the iPhone’s own GPS and any Bluetooth heart rate strap, saved to Apple Health with the route. The whole readout, with nothing else to buy.How it works Android GPS and a heart rate strapNo watch: the Android phone’s own GPS and any Bluetooth heart rate strap, saved to Health Connect with the route. The whole readout on the phone alone.How it works

True of every setup

These hold whichever cell you pick, so the setup pages do not repeat them.

The readout is the same: the five ride screens and any you build yourself, refreshed once a second on one timer.
Every finished ride adds a line to CycleBridge’s own log on the phone — date, duration, distance, climb, average and maximum speed — and the monthly and yearly totals are added up from it.
A GPX route can be imported beforehand and drawn under the ride on the map, and the ride exported as one afterwards.
Nothing leaves the phone for a server of ours. There is no account and no analytics; the privacy policy lists every case.