Turn-by-turn navigation

Once you tap Go, the map tilts, locks onto you, and a card appears at the top with your next turn. Everything else on screen gets out of the way after ten seconds. Here’s what each part is telling you.

The turn card sits at the top: the instruction, the road you’re on underneath it in amber, the distance to the turn on the right in green.

Along the bottom, the strip shows how far is left and what time you’ll get there. The speed pill sits just above it.

The navigation screen, ten seconds in. drawn from code

The turn card

Four things live in that card, and each one can be absent:

  • The instruction — the turn itself. While the app is working out a new route this is replaced by Recalculating… and a small spinner. Before the first GPS fix lands you may briefly see Navigating….
  • The road name, centred underneath in amber. This is the road the current leg of your route runs along. It’s blank if the route data doesn’t name it.
  • The next turn after this one, shown as Then: … in small grey text. It only appears when that turn is within 80 metres of this one — the two-in-a-row case where you need to know both before you commit to the first.
  • The distance to the turn, in green, counting down.
A red border means a U-turn is involved.

If the instruction — or the Then: line under it — contains a U-turn, the card’s border changes from green to red and thickens. NavForge works hard to avoid handing you a U-turn, so when you see that border, read the card properly before you act on it.

Distance and arrival time

The bottom strip shows two numbers: how far you have left, and the clock time you should arrive. Both update as you ride.

The arrival time is worked out from your rolling average speed over roughly the last ten GPS readings — or the average speed the routing engine expected for the whole route, whichever is higher. That second half matters: crawling through one set of lights won’t blow your arrival time out by an hour. If you’re stopped and there’s no usable estimate, the time is left blank rather than shown as something invented.

Distance and speed follow whatever you’ve set under Units. Metric gives you metres under a kilometre, then kilometres; imperial gives you yards then miles.

Why the buttons disappear

Ten seconds after navigation starts — and ten seconds after your last tap — the side buttons and the Road blocked pill fade out over about a third of a second. At the same time the turn card widens: in portrait it stretches almost to the right edge, in landscape it goes from around 45% of the screen to 60%. Bigger text, less clutter, more map.

Tap anywhere on the map and everything comes back, and the ten-second countdown starts again.

Three things never fade.

The turn card, the bottom distance-and-time strip, and the Stop pill stay put the whole time. You never have to wake the screen up to see where you’re going or to end the ride.

How the map moves

The view tilts to 45° and turns with you. The camera doesn’t sit on top of your position — it’s pushed ahead of you, from about 80 metres at walking pace out to 400 metres at highway speed, so you’re near the bottom of the screen with the road ahead filling the rest.

Zoom follows speed too: close in when you’re slow, further out as you pick up. It zooms out the instant you accelerate, but only zooms back in after you’ve been slower for three seconds — otherwise it would breathe in and out at every set of lights.

Your arrow is snapped onto the route line whenever you’re within 30 metres of it, which keeps it running cleanly down the road rather than wandering with GPS noise. Past 30 metres the snap is dropped and you see your raw position — that’s also roughly the point where the app starts thinking about a reroute.

Stopping

  1. Tap Stop

    Bottom-right corner, outlined in pink. One tap ends navigation immediately.

  2. That’s it

    There’s no “are you sure?”. The route line clears, the turn card goes, the map returns to normal. Worth knowing if you ride with gloves.

Arriving

When you get within 30 metres of your destination the app says You have arrived at your destination. and navigation stops on its own.

There is no arrival screen.

You get that one spoken line, then the turn card, the route line and the bottom strip disappear. No summary, no “you’ve arrived” panel, no tap to dismiss. If you were recording the ride, that recording is separate and keeps going until you stop it.

If GPS drops out

Nothing tells you.

If your position stops updating — a tunnel, a deep cutting, a phone that’s decided to nap — the turn card and the distance freeze on their last values. There’s no warning banner and no greyed-out state. The one visible clue is the speed number: after five seconds with no fix it drops back to a dash. If the distance to your turn has been stuck while the road went by, treat what’s on screen as history until it starts moving again.

If the app is killed mid-ride

Navigation state is saved as you go. Next time you open NavForge you’ll be asked Resume navigation? with the note NavForge was interrupted. Continue your previous route? — Resume picks the route back up, Dismiss throws it away.

One thing doesn’t survive the resume.

The amber road-name line under the turn instruction stays blank for the rest of that route. The turns, the distances and the voice all work normally — only that one label is gone until you start a fresh route.

← Elevation profile Voice guidance →