Windows 10 Maps, derived from the codebase for HERE Maps, back on Windows Phone 8.1, uses public traffic data, meaning – as I covered here – that its routing only really integrates traffic on major routes and even then not really in real time. I’d have hoped that Microsoft would have put more effort into building in other data sources, but it seems that most of the upgrades to Maps (UWP) have concentrated around places of interest and general research, with an emphasis perhaps on use on the desktop.
It turns out that really good real time traffic navigation depends on human beings, driving around with navigation applications on their phones in cars. Which is kind of a chicken and egg situation, in that Windows 10 Maps isn’t brilliant for real time navigation, plus only a fraction of the population (of any country) uses it, meaning that there’s just not critical mass of any kind to make the product any better in this regard.
In contrast, both Google Maps (on Android, though GMaps Pro hijacks quite a bit of its data on Windows Phone) and Waze (all platforms) have enough real world users in all countries that the automatic speed+position reporting from each phone back to the relevant servers enables pretty good real time navigation. Not perfect (I’ve been testing all these solutions intensively over the last week), but much better at adapting to a changing traffic environment when you’re on the road.
It’s Waze I’m looking at here, in part because I couldn’t believe that such an ‘old’ application still worked properly under Windows 10 Mobile (and Creators Update in particular, in 2017) – surely something would have broken in terms of server APIs in the intervening three plus years? Although Waze is less popular than it was back in 2013/2014, there are still quite a few people using it and you’ll see some of this represented in the real world example screenshots below. And the good news is that the old (Silverlight?) client for WP 8.1 still works well, with just the minor cosmetic point that some panes of information have their bottom chopped off by the (dismissable) virtual navigation contols of Windows 10 Mobile, and with the downside that voice instructions don’t seem to work anymore. (This latter might just be my installation or, more likely, Microsoft has changed the voice APIs since Waze was coded up for Windows Phone 8.1.)
Why use Waze, then? Because your position and speed are reported back to Waze’s servers as you drive, joining in the massed pool of data that Waze maintains and allowing real time navigation instructions to be sent back to your phone as needed. Obviously, you need to keep data ‘on’ for all this and a decent bandwidth is needed (far less than media streaming though, don’t worry), but the confidence that your wellbeing on the road is being looked after by someone else is impressive. Just as it’s always been for Waze, of course. Here’s their original video promo:
Some of the social (Facebook? Pah!) aspects leave me cold and weren’t tested here, but what impressive was how much did work. The gold standard for phone-based car navigation is still Google Maps on Android, I maintain, but Waze gets quite close in terms of traffic, and adds niceties like fuel stations and warnings for ad-hoc police speed traps.
Now Google owns Waze, which is distinctly interesting, though it seems to run it fairly hands-off, with just Waze-reported traffic incidents and roadworks filtering through to its core Maps products. I’d have thought that after all this time the real time traffic data would have been combined, but it seems that each system works well enough as it is…
In return, Waze gets access to Google’s Maps API for ‘Places’, and this also proves useful, as you’ll again see below.
Time for a demo, anyway – this is Waze (from 2013/2014 and still available in the Windows 10 Store) running on a Lumia 950 in July 2017 with production Windows 10 Mobile Creators Update (Redstone 2) installed:
The interface is still…. quirky – it never fitted in with WP8.1 either though, and anyway sat-nav apps are usually different in terms of UI. In this case, these are the two main easy-touch control panels – for application functions (mainly used while stationary) and navigation functions (mainly used while moving*)
* it goes without saying that the phone needs to be in a hands-free holder and that you should exercise usual care in terms of distracting yourself from the road
Setting off driving then, with a destination planned (and note that the optional dark mode here works, though not in all forms and panes), Waze pops up useful warnings for the road ahead. Bear in mind that you’re still being optimally routed, whether you notice the warnings or confirm or deny their validity – the interaction is all optional.
What’s evident from the screens above is that the timecode for each item is important – ’20 mins ago’ for the traffic jam towards Henley sounds very believable (is the Regatta still on?), but ‘721.9 hours ago’ is a month and I’m pretty certain that these roadworks got cleared ages ago. How does Waze remove old incident reports? There’s definitely something fishy going on here!
Waze’s own place database is for towns and roads, principally, so it’s great to have a full Google Maps place search just a swipe away. Here I was looking for the ‘House of Flavours’ restaurant and the latter search picked it up. In either case, just tap on the control to confirm the location on the map.
Assuming this location is the one you want, just tap on ‘Go’ etc. (right) traffic, roadworks and police reports are available on the menu too, sorted by their distance from you. In this case, in late afternoon, I completely believe the traffic reports from around Reading. These have been helpfully tapped in (only two taps) by other Waze users – your general routing is still from the mass of all position/speed information that’s been auto-collected.
When travelling along a problem road (see the ’13mph’ tag above), the background of the route shows that’s a known problem, though local knowledge also tells me that the right hand lane travels twice as fast as the left, so….(!); (right) if I wanted to join in the Waze reporting fun then tapping on the right hand bottom control pops up the reporting menu and then ‘Traffic Jam’ here, just tap on the one you want – or just leave the screen up, a timer accepts a general report and the pane goes away. And, obviously, don’t start taking photos or typing in comments if you’re the driver!!
Oh dear, another report that’s irrelevant from 4.5 months ago! I wonder if Waze on other platforms has the same issues with out of date information? (right) There’s plenty of introductory help in Waze, from screens like this to an in-app explanatory video.
Overall, Waze is a now flawed experience (cropped off information, old data, no voice) in 2017, but an application that definitely still works and, in cases where traffic is a serious consideration (which is most of the time where I live), can still be a big time saver. Worth installing alongside both Windows 10 Maps and gMaps Pro and then use the best tool for the job, perhaps? (Or use Google Maps on Android, but that would be too much like throwing in the towel, so….!)
I’d love Waze to come out with a proper Windows 10 UWP version of this, of course. I wonder whether they’re listening?
PS. One final note on battery life and power requirements – Waze, like all sat-nav apps is using data, GPS and screen all at the same time, and so the power requirement is high. Best to have your phone plugged into a power source in your car while navigating! You can reduce the requirement a little by switching away from Waze and letting it work in the background (it does this to some degree), but given that there’s no voice (for me) under W10M then this foils the point of using the app in the first place!