Skip to content

shalafi

My feedback

3 results found

  1. 139 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)
    shalafi supported this idea  · 
  2. 78 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)
    shalafi supported this idea  · 
  3. 1,565 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)
    shalafi supported this idea  · 
    An error occurred while saving the comment
    shalafi commented  · 

    *cough, cough* is this thing working? I've been with Waze for three years now, this uservoice topic has been ranked high ever since it was created in mid-2010 and still no candy.

    Is it that hard to cache your data if the client loses connectivity and re-send once you're online?
    Is it that hard to preserve that buffer between client sessions, rather than losing it on exiting?
    Don't you care about average speeds and other mapping info in no-coverage areas?

    You say this is a commuting app and is thus interested in live data only. What if my daily commute takes me through a no-coverage area? Do we need to overlay network coverage maps on top of Waze and draw "HERE BE DRAGONS" landmarks all over coverage gaps?

    I am a bit sad that Waze is not interested in parts of what we, the community, all strive to contribute - the road/gps data.

    Please stop throwing bits of it away.

Feedback and Knowledge Base