# Feature Request: Waze "Bike Presence" Safety Layer

**URL:** https://www.waze.com/discuss/t/feature-request-waze-bike-presence-safety-layer/415883
**Category:** WME Feature Requests
**Created:** [October 31, 2026, 3:37pm UTC](https://www.waze.com/discuss/t/feature-request-waze-bike-presence-safety-layer/415883 "2026-10-31T15:37:23Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![israel\_h8df6b3t](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/FD804B/32.png) [@israel\_h8df6b3t](https://www.waze.com/discuss/u/israel_h8df6b3t)
#### Post date: [October 31, 2026, 3:37pm UTC](https://www.waze.com/discuss/t/feature-request-waze-bike-presence-safety-layer/415883/1 "2026-10-31T15:37:24Z")

</div>

Feature Request: Waze “Bike Presence” Safety Layer

Overview

Introduce **Bike Presence** , a lightweight, opt-in safety layer within the Waze ecosystem designed to bridge the visibility gap between drivers and vulnerable cyclists. Unlike a dedicated cycling navigation app, Bike Presence leverages Waze’s existing driver network to provide real-time proximity alerts for shared-road encounters without requiring cyclists to navigate using the app.

Problem Statement

Cyclists are among the most vulnerable road users. A primary root cause of collisions is delayed visual acquisition by drivers—drivers often notice cyclists too late, particularly on winding roads, blind curves, or during low-visibility conditions. Existing solutions either focus on turn-by-turn cycling navigation (which cyclists prefer not to use for driving apps) or require expensive proprietary hardware.

Proposed Solution & User Flows

1. The Cyclist Experience (The Broadcaster)

**Action:** The cyclist opens Waze (or a companion quick-toggle widget) and taps **“I’m riding”**.

**Privacy & Safety Protections:**

Opt-in only.

Anonymous broadcasting.

**Location Delay:** Telemetry is delayed by 10 seconds to eliminate real-time tracking risks.

**Lifecycle:** Sharing stops automatically when the ride ends, movement ceases, or the phone goes idle, preventing battery drain and ghost-tracking.

2. The Driver Experience (The Receiver)

**Action:** When a driver approaches an active cyclist on the same road segment, Waze triggers a standardized, non-intrusive audio-visual cue.

**Alert Format:**

_Visual:_ Glanceable banner reading: ⁠"Cyclist ahead, 150 m. Leave 1.5 m when passing."⁠

_Audio:_ A subtle, distinct chime (similar to existing Waze hazard alerts, but unique to vulnerable road users).

Strategic Fit for Waze

**Synergy with Motorcycle Mode:** Waze has already proven its capability to serve two-wheelers via Motorcycle Mode.

**Leveraging Community DNA:** The Waze community is built on crowdsourced hazard reporting and safety sharing. Extending this ethos to protect vulnerable road users aligns with modern urban safety initiatives and corporate responsibility goals.

**Non-Competitive Positioning:** By acting strictly as a _safety layer_ rather than a routing engine, it avoids competing with dedicated cycling apps while adding massive utility to the driver experience.

Technical & Product Considerations (Mitigations)

**Cold Start / Adoption:** Bootstrap initial density via municipal partnerships, cycling clubs, or commuter corridors, combined with passive heat-mapping on frequent routes.

**Driver Alert Fatigue:** Implement intelligent geofence throttling (e.g., triggering only once per road segment per driver when closing speeds demand attention; suppressing alerts entirely in dense traffic gridlock where bikes are ubiquitous).

**Protected Infrastructure Filtering:** Use map data to suppress alerts when a cyclist is physically separated from car traffic by protected bike lanes, reserving alerts strictly for unbuffered shared asphalt.

 ![image](https://web-assets.waze.com/discuss/prod/original/3X/4/b/4b3862dba3cbe25feb8bf4c708794fad2d985f47.jpeg)

 ![image](https://web-assets.waze.com/discuss/prod/original/3X/6/f/6f8ad993aaad7e15c9fb8522d8b57491b6c1c989.jpeg)

 ![image](https://web-assets.waze.com/discuss/prod/original/3X/6/7/672f18d7a81cf87880b6b34d4d07dc93b4d92516.jpeg)

---

<div class="post-metadata">

### Author: ![YanisKyr](https://www.waze.com/discuss/user_avatar/www.waze.com/yaniskyr/32/5439_2.png) [@YanisKyr](https://www.waze.com/discuss/u/YanisKyr)
#### Post date: [November 13, 2026, 3:35pm UTC](https://www.waze.com/discuss/t/feature-request-waze-bike-presence-safety-layer/415883/2 "2026-11-13T15:35:08Z")

</div>

You might have seen this already 🙂

> [@It’s Live! Waze x Garmin Real-Time Cyclist Alerts are rolling out man\_biking](https://www.waze.com/discuss/t/it-s-live-waze-x-garmin-real-time-cyclist-alerts-are-rolling-out/416766):
>
> Hey everyone, We are thrilled to announce that Waze, in partnership with Garmin, is introducing the real-time cyclist alerts feature, and it is officially live! A huge thank you to everyone who helped us refine this highly requested feature, which was on top of Waze’s suggestion list for years. You can read the official announcement on the[Waze Blog](https://blog.google/waze/garmin-safety-cyclists/). As you start seeing this on the road, here are a few key things to remember: It’s an extra safety layer: Because this is strictly an opt-in feature via Garmin LiveTrack, we won’t have 100% coverage of every cyclist on the road. This is designed as a “moving insight,” not a replacement for full driver alertness. Smart alerts to prevent fatigue: To avoid alert fatigue, the full experience (map pin, insight card, and voice prompt) only triggers on higher-speed roads (segment speed limit \> 70 km/h). In dense city centers or on slower roads, the pop-up notifications and audio are suppressed. Dynamic Grouping: If multiple Garmin riders are cycling in close proximity (within a 500m radius), they dynamically group into a single consolidated map pin to keep your map clean. Thank you again for all your support in making our roads safer. We can’t wait for you to see it in action! Best, Hezi, on behalf of the Waze Communities Team
