Skip to content

Misael Bandeira Silveira

My feedback

1 result found

  1. 6 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
    Misael Bandeira Silveira commented  · 

    Hi everyone,

    I’d like to share a feature request inspired by a conversation with a regular Waze user (not a member of our editing community, but a daily driver like the rest of us).

    He recently mentioned that he might have received a speeding ticket from a mobile speed camera. The catch is that here in Brazil, highway police use laser-equipped cameras that, assuming a clear line of sight, can clock a vehicle from up to 2 kilometers (approx. 1.2 miles) away.

    This led us to discuss how useful it would be to allow users to customize their alert radius preferences directly within the app. Currently, these notification distances are standardized and defined by the backend.

    As a software developer, I completely understand that implementing this introduces additional complexity to the configuration and data modeling. However, one potential approach could be fetching these personalized notification settings during the app’s boot process.

    Ideally, this customizable notification distance could be extended to other alert types as well, such as police presence (which on highways almost always means speed checks) and fixed speed cameras.

    I’d love to hear your thoughts on the technical feasibility of this idea!

    Misael Bandeira Silveira supported this idea  ·