Skip to content

Matthew Koss

My feedback

1 result found

  1. 1,208 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Koss commented  · 

    Waze should show ETA and arrival time in the destination's local time zone, not the phone's current zone.
    Why it matters: On a Stevensville, MI (Eastern) → Great Lakes / Chicago (Central) drive, Waze showed arrival an hour late until the phone flipped zones. That breaks appointment planning when the destination is in another zone.
    How to implement (practical path):
    At route start (and whenever the destination TZ differs from the device TZ), look up the destination's IANA time zone (same data Apple Maps / Google Maps already use).
    Compute arrival as now + remaining_duration, then display that clock in the destination zone.
    Label it clearly, e.g. Arrives 2:15 PM CT (or a small TZ badge), so users aren't guessing.
    Keep duration as-is; only the clock face changes. Optional: show both "2:15 PM local" and "3:15 PM your time" on long cross-TZ trips.
    Re-resolve TZ if the destination is edited mid-trip.
    Apple Maps and Google Maps already do destination-local arrival. Car nav systems do too. This is a display fix, not a routing change—high value, low risk.
    Happy to beta-test. Thanks.

    Matthew Koss supported this idea  ·