The pieces behind the curtain
GPS and sensors
What it is: The raw location signal from the phone, plus motion clues from the device.
How it is used: It keeps the moving dot aligned with the car instead of leaving it stuck on yesterday’s position.
Why it is used: Navigation only works if the app knows where you are right now.
Map matching
What it is: The logic that snaps noisy GPS data to the most likely road segment.
How it is used: It cleans up drift so routing starts from a real road, not a rough coordinate.
Why it is used: A bad starting point makes every next turn less trustworthy.
Traffic ingestion
What it is: Live slowdown, incident, and crowd report data from the road network.
How it is used: It refreshes the picture as drivers report jams, hazards, and speed changes.
Why it is used: A static map cannot warn you about a jam that started two minutes ago.
Routing engine
What it is: The decision layer that compares possible paths.
How it is used: It weighs distance, road class, current speed, and incidents to choose a better route.
Why it is used: The best route is always changing while the car is moving.
The simple path first
Open the app
The map loads, the last route state appears, and the current position starts anchoring the view.
Match the road
GPS and sensor signals decide which road segment you are actually on.
Listen for traffic
Crowd reports and speed changes update the road graph around you.
Reroute fast
A better path appears before the delay becomes the new normal.
What happens after the tap
Live rerouting as conditions change
Why the order matters
Waze is not solving routing once and stopping. It keeps comparing the current route with new traffic signals, then decides if the route should stay or change. That continuous loop is the product.
What the main layers are doing
Location input
What it is: The phone position plus sensor data.
How it is used: Map matching snaps the dot to the road, not just to raw coordinates.
Why it fits: Without that correction, every route decision starts from the wrong place.
Traffic layer
What it is: A live view of road speed and incidents.
How it is used: The system blends reports, movement signals, and road history to understand where delay is forming.
Why it fits: A static map cannot reroute you out of a fresh jam.
Routing engine
What it is: The part that chooses the best path.
How it is used: The route is recomputed when the road picture changes enough to matter.
Why it fits: The engine exists because “best right now” is a moving target.
Map rendering
What it is: The visual layer that keeps the UI readable.
How it is used: It turns complex road changes into something you can react to quickly.
Why it fits: A navigation app fails if the picture is slower to read than the traffic is to change.