Plug the phone into CarPlay or Android Auto and the car screen used to show a map of its own. The route was a thick white line. The basemap ignored your language, POI choices and night mode. The turn arrows on Apple's card were not quite the ones on the phone. As of today the car draws the same map as the phone, and the vehicle marker behaves the way Google Maps taught everyone to expect.
Until this week the Adventure basemap was a FastGIS style on top of stock OpenMapTiles tiles. Everything the style could learn, it had learned; what was left was what the tiles never carried. So now we bake the tiles ourselves, with a profile of our own, and the map shows harbours, gates on forest roads and track grades. It also stopped carrying thousands of points of interest it could never draw.
The Adventure basemap has always answered the one question every other map makes you click for: what is that road made of. This week it learned to answer the rest of a rider's questions without being asked — where the ferry runs, which name is the pass, where the town stops, and which badge to keep when two collide. Four passes, each checked on real pixels before it shipped.
EpicRide has always opened on a map. You arrived, a route planner loaded, and whatever you actually came for was somewhere behind it. From today the desktop client opens on a Dashboard of what you are riding, and the planner is a place you go.
Behind that change is a new object: an event. A time, a roster, and the library records you ride.
EpicRide's Library used to be two tabs and a scroll: everything you had saved, fetched in one go and filtered in the browser. Today it becomes a primitive — one component that is the Library page, the picker inside the planner and the roadbook editor, and the save form everywhere something can be saved. And rally roadbooks move into it: a saved book is now a library record like a route or a ride, so it can be shared, exported, searched and linked to the track it came from.
For a month the roadbook program has been building its foundations: a data model that carries the official FIM/FIA structure, an exporter that real rally readers accept, a symbol library drawn glyph by glyph, a print module measured off the FIA's own Diagram 1. Today the last and largest piece ships: a full roadbook editor in EpicRide, and with it the whole pipeline — from any GPX to a printed, regulation-shaped book — is live.
Since July the rider app has been able to turn any track into a rally-style tulip roadbook — the Rally side of the Road ⇄ Rally toggle reads the corners straight off the GPX shape, no road network required. It was a document: something to scroll with a thumb at a fuel stop. Today it becomes a navigation mode.
This was the week the app stopped inferring what the motorcycle was doing and started asking it. A Bluetooth OBD-II adapter, two garage sessions, one surprise hiding in monitor mode — and by the end, live engine data on the phone and a gear indicator nobody sold us.
Two weeks ago the map stopped being flat: the routing graph learned elevation, the road score grew a climb axis, and the server could finally tell a mountain road from a merely bendy one. All of it, though, lived behind an API. This week it reaches the phone.
Plan a route with a lunch stop and a mountain pass in the middle, start navigating, and until today the app would tell you exactly one thing about time: when you'd reach the end. The intermediate stops — the whole reason the route has that shape — were invisible from the saddle.