You can test an app for weeks at a desk and learn less than you learn in one afternoon with it mounted on a handlebar. This week was the bill for a real ride.

You get home from four days in the mountains with two hundred photos, a GPX track and no intention of ever writing a trip report. We think that is a shame, so we built the thing that writes it for you.

Two threads this week, and they meet in the same place: the moment you stop looking at a phone and start riding.

A platform that can only be read by its own app is a trap, however nice the app is. This week FastGIS learned to speak the standards, and to let riders see each other move.

Here is the uncomfortable truth about a navigation app for adventure riding: the better the road, the worse the coverage. The places worth going are exactly the places your phone gives up.

So this fortnight we made the phone stop needing us.

A week ago FastGIS was a browser tool for running GRASS modules. This week it learned to plan a motorcycle route — and it turns out those two things want the same foundations.

If you've ever used GRASS GIS, you know it's one of the most powerful spatial analysis platforms ever built. Decades of algorithms, impeccable accuracy, a passionate community. You also know that getting it installed, configured, and running on a new machine can be a bit of an adventure — and sharing your work with a colleague who doesn't have GRASS set up? That's a whole afternoon gone.

FastGIS started as a personal itch-scratcher for exactly that problem.