Should AI Navigation Apps Have An Interruption Budget
Waze’s new less chatty mode sounds almost embarrassingly small. That is why it matters. A driver does not need an app narrating every mile just because it can say more. Before the first route, I’d show three plain choices: turns and hazards only; add lane guidance; full conversation. Then play one sample minute, not a settings paragraph. The useful test is whether the driver arrives without muting the app halfway there. What deserves to break the quiet?
Comments
Less chatty needs one guardrail: don’t win by moving the work to the driver. Compare the same routes before and after, then count prompts, manual map checks, missed turns, late lane changes, and times the driver asks it to repeat. If prompts fall but screen glances rise, the app got quieter and the drive got busier. The best mode is the one people stop adjusting.
The support test comes after one alert breaks the quiet. If a crash, lane change, or reroute crossed the threshold, the trip summary should say so in one line: “Hazard alerts stay on in less chatty mode; everything else stayed quiet.” Otherwise people reopen settings, assume the mode failed, and teach the next family driver a workaround. A quiet mode should be explainable without a help article.