Blog
Why Navzeno
A map that stops working the moment you leave coverage is not a map. Here is what we built instead, what is in the beta, and what is not.
Somewhere north of Huntsville the bars drop to one, then to none, and the maps app on the passenger’s phone quietly stops being a map. The blue dot keeps moving, because GPS does not need a network. The roads around it do not load. Search returns nothing. The route you set an hour ago is still on screen until you take a wrong turn, and then it is gone.
Everyone who drives north in this country has had that trip. It is not an edge case and it is not going away: Ontario alone has more cottage road, park and northern highway than any carrier will ever cover. So we built the map for it.
What “offline” actually has to mean
The word gets used loosely. Most apps mean tiles: pre-download pictures of the map for an area you drew a box around, and look at them later. That is useful, and it is about a quarter of what you need. A picture of a road cannot tell you the road is one-way. You cannot search it. You cannot route across it, and you certainly cannot be re-routed on it after missing a turn — which is exactly the moment you needed a map.
For an offline navigator to be worth carrying, four things have to run on the device with the radio off:
- Drawing. The map redraws as you pan and zoom, at every zoom level, over the whole region — not just the rectangle you thought to cache.
- Search. You type “Killarney” or “boat launch” and get answers, in the woods, from the phone.
- Routing. A real route across a real road network, honouring one-ways and legal turns, with avoidances for tolls, ferries and unpaved roads if you want them.
- Turn-by-turn. Spoken directions with street names and roundabout exits, and automatic rerouting when you leave the route, because you will.
All four need structures a tile cache does not contain: a routing graph, a search index, the geometry itself. So what you download is not a folder of images. It is one file per region holding the map, the graph and the index together, which the app reads straight off disk.
Why one province in one file
We considered smaller downloads — pick your corridor, pick a park — and decided against them. The point of the exercise is that you never have to have predicted where you would go. The detour to the other side of the lake, the closed road that sends you sixty kilometres round, the friend who says come and see this: none of those are in a box you drew before you left. One province, downloaded once over Wi-Fi, and you are done thinking about it. It is a big file. It also means the map never runs out.
It has a second effect we like: it makes the promise checkable. Put the phone in airplane mode and use the app. If anything degrades, we have a bug.
Ontario first
Ontario is the flagship region for two reasons. The dull one is that it is where we are and where we drive, so we notice when something is wrong — a lake drawn without its islands, a route asking for a turn that has been illegal for years.
The better one is that Ontario is genuinely hard. It is enormous, its cottage country is a tangle of water and forest that the naive way of drawing a map falls over on, and on its northern highways a mistake in the routing graph is expensive because there is no second option for an hour. Getting Ontario right means the engine is honest everywhere else. Quebec and British Columbia come next, then the rest of Canada, then the border regions a road trip crosses.
What is in the beta, and what is not
In: offline drawing, search, routing for driving, walking and cycling, turn-by-turn with voice and rerouting, avoidances for tolls, ferries and unpaved roads, nearby search for the things a road trip needs — fuel, EV charging, campgrounds, drinking water, toilets, picnic sites, trailheads, boat launches, dump stations, hospitals — favourites and GPX import and export, on iOS, macOS and Linux, with Android still in development. No account, no telemetry, and your location never leaves the device.
Not in, and clearly marked as such wherever it comes up: house-number address search (search is by name today), French, elevation and contours, one route that crosses a provincial boundary, CarPlay and Android Auto, and anything to do with vehicle height and weight. That last one is deliberate rather than pending: the data on bridge clearances is patchy, and an app advertising low-bridge avoidance on patchy data will one day put a motorhome under a bridge that fits it on paper. We will ship it when we can show the data supports it, and not before.
The map itself comes from OpenStreetMap, made by hundreds of thousands of people, and it is not perfect either — a road can be missing, a gate unmapped, a campground in the wrong bay. We say so plainly on the attribution page, including how to fix it, which anyone can do. Signs and closures always outrank the app.
Following along
The email list is on the download page — one email when it ships, nothing else. Region builds, post-mortems and release notes go here, and there is an RSS feed if you would rather not give us an address at all.