CycleBridge

In development

Changelog

CycleBridge is not in the App Store or on Google Play yet. Both apps are working and tested, and the remaining work is store submission — the changelog below is the real build log, updated as things land.

  1. Still to do

    Store submission

    What stands between here and production: the App Store and Google Play listings, and a first ride with the new watch pages on real hardware.

    • App Store and Google Play submissions, with the store privacy disclosures the ad SDK requires
    • A real-hardware pass over the three new watch pages — they are covered by unit tests, but no simulator run happens anywhere in this project
    • The Android Garmin integration verified against an actual watch, which it has not been yet
  2. Shipped

    Ride screens for zones, elevation and splits

    The readout became a stack of purpose-built screens you swipe between, on the phone and on the watch, instead of one grid trying to say everything.

    • Phone: heart rate zones, a 30-minute climb profile, per-kilometre splits, a dedicated speed screen and a full-screen map, all reached by swiping
    • Watch: a dense six-value page, plus climb and splits pages behind their own settings
    • Heart rate zones now mean the same thing on both apps — five zones from your Garmin profile on the watch, from a max heart rate you set on the phone
    • Watch layout geometry became unit-tested: every field is proven to sit inside the round screen’s usable circle
  3. Shipped

    Honest attribution and ad disclosure

    The privacy policy names Y-A-S ApS as the party responsible, and the site stopped implying there were no ads.

    • Both copies of the privacy policy name the company behind the apps
    • The landing page names the idle-screen ad and its one limit instead of omitting it
  4. Shipped

    Continuous integration and signed releases

    Every change now runs the phone tests, the watch tests on a headless simulator, and a site build before it can land.

    • CI for the Flutter app, the Connect IQ watch app and this website
    • Tag-triggered release workflows for both apps, with the watch package signed at build time
  5. Shipped

    Watch rework and ride statistics

    The watch app moved to hero-metric pages with circular effort and feel dials, and finished rides started adding themselves up.

    • Hero-metric watch pages, distance alerts and settings edited from Garmin Connect Mobile
    • Circular perceived-effort and perceived-feel dials, recorded into the FIT activity
    • Monthly and yearly ride statistics on the phone
    • A three.js hero and scroll-driven scenes on this site
  6. Shipped

    First working build

    The phone app, the Garmin watch app and the Bluetooth link between them, end to end.

    • Live snapshots from the watch to the phone, once a second
    • Phone-sensor mode with GPS and a Bluetooth heart rate strap
    • GPX import and export, and the route library
    • This site