The app has a name: Epona
Epona is the Gaulish goddess of horses and riders — the one deity the Roman cavalry adopted wholesale and carried across the empire. Protector of anyone on the move.
It seemed like the right name for the thing in your tank bag.
What changed, and what didn't
The rider app is now Epona. EpicRide is the desktop planner. FastGIS is the platform and the API underneath both — the thing that serves 346 endpoints to all of them.
Deliberately, the infrastructure did not follow. Service names, package identifiers and hostnames stay exactly as they were, because renaming the plumbing to match a product decision is how you spend a fortnight, break a deployment and gain nothing a user can see.
The display name now lives in one file per client, reached everywhere else through a constant or an i18n variable — and there is a test that fails if someone hard-codes it again. The next rename is two edits instead of an archaeological dig.
Explore the Trans Euro Trail in 3D
The TET explorer shipped: the whole catalogue on a globe you can fly. Three rounds of polish went into making it feel considered rather than technical — the camera aims itself at the trail instead of at empty ocean, the overview stays legible at continental zoom, only one section card opens at a time, and on a phone it gets out of the way entirely and hands the screen back to the globe.
A 3D globe is easy to build and hard to make legible. Most of the work is deciding what to hide.
And adv.fastgis.eu was rebuilt as a single 14,300 km ride across Europe —
one continuous story rather than a feature grid. If the product is about the
ride, the landing page should be a ride.
Weather that stays true
Weather along the route now refreshes during the ride, re-sampling ahead of you as you go. A forecast fetched three hours ago at the start of a long day is a historical document, not a prediction — and the rain it did not mention is still rain.
Tiers, named
Centaur, Pegasus and Alicorn — with the entitlement system rebuilt to be rail-agnostic and subtractive from the top. The app ships complete, the highest tier holds everything by construction, and each lower tier is defined by what it keeps rather than by features bolted on.
That inversion matters more than it sounds. Additive tiering means every new feature needs a decision in every plan, forever; subtractive means a new feature is included by default and you decide once where to cut. Moving a feature between tiers is one value in one registry, and admins can grant or revoke per plan at runtime with no deploy.
Which mythological creature you are is, we admit, the most fun product decision we have made all year.
Onward
A name is a small thing that makes everything after it easier to talk about. Now back to the riding.
Dig deeper: accounts and tiers, and the rider app.