CycleBridgeRide screens · iPhone & Android
Screens you build yourself
The five screens the app opens with are one arrangement of one grid. Settings has a Ride Screens page where you copy that set and change it in two steps: tick the parts a screen should show, then give each its place — with a live preview of the screen as you edit it.
What it shows
- A live preview of the screen at the top of the editor, drawn by the readout itself
- The parts first: the whole catalogue as a checklist, a tick putting a widget on the screen where the built-in screens would put it
- Then the places: the parts in reading order, dragged into another slot, with one or two across and a small, medium or large height for every row
- Any widget on any screen: the eight number fields, the zone hero and zone bars, average and peak heart rate, the climb profile, the split list and the map
- Presets — the list of screens you swipe through — to choose between, make, duplicate, rename and delete
A widget alone in its row is drawn large and centred, the way speed leads the first screen; two sharing a row are the size the grid’s pairs have always been. That is the whole vocabulary, so a screen you build looks like the ones that shipped.
No screen is one widget alone. Even the map and the split list keep a row of numbers beneath them, which is why two rows is the floor: a screen should read as a readout, not a picture.
The built-in preset is the five screens the app has always had, and it is read-only. A new preset starts as a copy of it, so you are rearranging a working readout rather than filling a blank one, and the default is always there to come back to.
Every edit is saved as it is made, and the presets live in a file on your phone. A cell naming a widget a build does not know is dropped on its own rather than taking the screen, or the preset, with it.