A route planner that thinks about the whole journey.

Route choices that are actually useful

Waybi can compare multiple driving routes and explain why a route is useful — for example, a shorter distance, a quicker ETA, lighter traffic or fewer matched fixed safety cameras. The goal is not to manufacture three routes when only one sensible route exists. When alternatives are too similar or clearly worse, Waybi can keep the choice simple.

Driving routes sit alongside walking, cycling and transit options where the underlying provider supports them. During a trip, the interface keeps the next manoeuvre, ETA and route context close to the map so the navigation screen stays readable rather than turning into a dashboard full of competing cards.

Traffic-aware without pretending every road is live

Waybi uses live traffic information when the selected provider supplies it. Traffic is treated as one source of context, not a promise that every street has complete real-time coverage. When live traffic segments are unavailable, the UI can say so instead of colouring a route in a way that suggests traffic data exists when it does not.

Journey Brief before the first turn

Before navigation starts, Waybi condenses the decision into one pre-trip summary. The Journey Brief can surface expected arrival time, current traffic or delay information, route distance, the number of matched safety cameras, nearby or selected parking and the reason a route is recommended. The deeper controls remain available underneath for people who want them.

Parking is part of arriving

For supported destinations, Waybi can surface parking near the destination before the driving leg begins. In Auckland, Auckland Transport Open GIS parking data is preferred where it is available. Published capacity is presented as static capacity — not as a claim that a particular space is free right now.

A parking-assisted trip can work as one continuous journey: drive to the selected parking location, finish the driving leg, then continue with a walking route to the original destination. That keeps “where do I leave the car?” inside the same planning flow as “how do I get there?”

New Zealand road intelligence on top of the map

Waybi adds New Zealand-specific road context to the base navigation experience. That includes published NZTA fixed safety-camera locations, official NZTA traffic and travel road events used by Route Watch, and speed-limit information where the product has a supported source. These layers are supplementary driving information; road signs, current conditions and New Zealand law always take priority.

Two map providers, one Waybi experience

The mobile app supports Google Maps and Waybi Map, an independent mapping stack based on OpenFreeMap and OpenStreetMap data. Search, routing and content handling remain provider-aware so the product can reduce dependence on a single vendor without silently mixing data in ways that violate provider rules.

The important part for the driver is that the overall navigation model stays familiar. Changing the map provider should not mean relearning the app.

Bilingual navigation for New Zealand

Waybi supports English and Chinese navigation. Search is location-aware rather than hard-coded to one city, so nearby places should rank as nearby places while the product remains usable outside Auckland. New Zealand-specific features such as the current fixed-camera data layer remain clearly scoped to the country where the source is valid.