The simple path first
Open the app
It loads the map, last route state, and your current position.
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: Waze uses map matching so the dot snaps 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: Waze blends reports, movement signals, and road history to understand where the 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: Waze recomputes the route 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.