3 powerful Waze features that still aren't supported by Android Auto

Published Aug 29, 2026, 8:00 PM EDT Arol is a tech journalist who currently works as a contributor at How-To Geek since 2022. He first began writing online for the short-lived portal of Spanish-language gaming forum Emudesc in 2013. Years later, in 2017, he got his true start in tech journalism working for a small Google-focused site called Pixel Spot. He transitioned to a news and feature writer role at XDA Developers that same year, where he worked until 2021 before making the jump to other websites. Arol brings nearly a decade of writing experience, and the occasional hot take, to his writings. While he's a technology lover at heart, he holds computer hardware and smartphones particularly close to heart. You'll normally find him covering news, although he has also written the occasional deal, buyer's guide, how-to post, and round-up. He's also written for Android Police and MakeUseOf. He's also a Political Science student. When he's not writing, you'll probably find him hitting the gym, trying to ace a new hobby, reading his textbooks, or traveling. You can reach him at me@arolwright.com. Waze packs a lot of personality and utility into its phone app, but a chunk of that gets left behind once you plug into Android Auto. Here are three features that still don't make the jump. Social layer and Wazer visibility Android Auto strips out the community feel entirely One of Waze's defining traits on a phone screen is how alive the map feels. Other drivers, or Wazers, show up as small icons with their own avatars and moods, giving a sense that you're navigating alongside a live community rather than following a static route. You can tap on nearby Wazer icons, see how long someone has been driving, and get a general feel for traffic density beyond just the color-coded roads. It's a layer of the app that leans into Waze's original identity as a crowdsourced, social driving tool rather than a straightforward GPS app. None of that carries over to Android Auto. The in-car interface reduces the map to your route, your ETA, and incident markers, with no Wazer icons or avatars in sight. This isn't an oversight so much as a deliberate design choice: Android Auto is built around minimizing glanceable distractions, and browsing other drivers' icons is the kind of casual interaction that makes sense on a phone sitting in a cupholder but not on a dashboard display meant to be seen in quick, half-second glances. Still, for people who came to Waze specifically because of that social, game-like layer, the head unit version can feel comparatively sterile. You get the routing intelligence that Waze is known for, but the sense of a shared, populated map is gone. It's a reasonable trade for safety, for what it's worth, but it does mean the app's most distinctive personality trait effectively lives only on the phone screen, not in the car. I'm sure there could be a way to integrate it without making it an on-road distraction. Detailed trip sharing Sharing options are far more limited from the dashboard On a phone, Waze's trip sharing is fairly robust. You can send a live ETA link to one contact or several, choose exactly who receives it, and let them watch your car icon move in real time until you arrive or manually stop sharing. There's also flexibility in how and when you set it up, whether that's before leaving or mid-drive if plans change. Android Auto doesn't give you that same level of control from the car's display. The detailed share sheet, with its contact picker and per-trip toggles, isn't really accessible through the head unit interface in the same way. In practice, this means trip sharing works best when it's set up on the phone before you start driving, since doing it after the fact from Android Auto is clunky at best. Voice commands can help start navigation or basic actions, but they don't replicate choosing specific people to share with or adjusting sharing settings on the fly. If you happen to rely on trip sharing as a safety habit, like letting a family member track a solo drive, this gap means a bit of extra planning is required before hitting the road, since the car screen itself won't offer the same flexibility the phone app does once you're already moving. Granular incident reporting Quick taps replace the phone app's detailed report options Reporting incidents is core to how Waze stays useful, and on the phone, that reporting can get quite specific. You can flag police presence as visible or hidden, mobile or stationary, choose from a range of hazard types like potholes, objects in the road, or weather conditions, and even attach a comment for extra context. That granularity is part of what makes Waze's crowdsourced data feel accurate and current. Android Auto trims this down to a handful of large, tap-friendly buttons, typically covering police, accidents, hazards, and traffic, designed to be selected quickly without requiring sustained attention to the screen. It's a sensible safety concession, since fumbling through detailed report menus while driving would defeat the purpose of a distraction-reduced interface. The downside is that reports filed from the car tend to be less specific than ones filed from the phone, which means the broader Waze community sometimes gets thinner information from in-car reports. Drivers who want to file a fully detailed report, noting the exact type of hazard or adding a note, generally still need to reach for their phone, which somewhat defeats the point of having a dedicated car interface in the first place. Simplicity in the car comes at a cost These gaps aren't bugs so much as intentional trade-offs for driving safety. But together, they show that Android Auto's Waze is a leaner, quieter version of the app, missing the social texture and detail that make Waze distinctive on a phone.