Blog

How the three differ on accounts, syncing, how progress is measured, and price, and which one suits which kind of walker.

Every map in the app moved to a new engine in 3.5. Why, how the maps look now, and the big-city problem I had to solve twice.

1,668 walks, activity roughly doubled, city-download failures down to 26%.

The two route planners: pick a duration and get a loop, or tap a destination and get routed there, both favouring streets you have not walked yet.

CityStrides and Wandrer built a community around walk every street, but both need an account and a sync step. Here is why CityWalker skips both.

242 downloads, 49 countries, walk retention curves, and what the numbers say after two months live.

Every OpenStreetMap tag I decided to include or exclude in the coverage map, and the reasoning behind each call.

Why Vienna has 23 districts, Sacramento has 15 neighbourhood groups, and how those boundaries get drawn from OpenStreetMap and city open data.

What a street segment is, and the simple math that turns segments into your coverage percentage.