Why Android Nearby, iBeacons, and Eddystone failed to gain traction: low consumer awareness, spammy local notifications, complicated on-site rollouts, more
Apple, Google, and other tech titans once trumpeted beacons — tiny transmitters that interact with smartphones, wearables, and other nearby gadgets — as the future of retail.
Context & Ripple Effects
The beacon story ran hot from 2014 to 2016: McDonald's saw sales lift from beacon-driven offers, Target wired 50 stores for in-store deals, and Facebook handed free beacons to U.S. small businesses. Google built out the platform side too, launching the open-source Eddystone format and pushing nearby-beacon notifications into Chrome for Android.
The cracks showed early on Google's own stack: its Here project for third-party proximity alerts via Maps was killed over privacy concerns and doubts about demand. This 2018 VentureBeat postmortem closes the loop — low consumer awareness, spammy notifications, and painful on-site rollouts explain why the retail pilots never became infrastructure.
First-order effects
- Retailers like Target and McDonald's that ran beacon pilots are left holding hardware and integration costs without the promised engagement lift, cooling further store-level investment.
- Apple and Google see their proximity platforms (iBeacon, Eddystone, Android Nearby) lose retail mindshare just as both were positioning them as standard IoT plumbing.
Second-order effects
- Facebook's free-beacon program for U.S. SMBs loses its rationale as merchants conclude shoppers never opted into the notifications the hardware exists to deliver.
- Beacon hardware vendors and rollout integrators lose their anchor customers, pushing them toward niche uses (asset tracking, indoor navigation) where push-marketing fatigue doesn't apply.
Third-order effects
- Proximity marketing migrates from dedicated transmitters toward permissioned, app-mediated location — the same privacy-and-demand doubts that killed Google Here become the design constraint for every later ambient-notification feature.
- The episode sets a durable rule for platform makers: hardware-only distribution of context-aware experiences fails unless the OS owner controls both the trigger and the user's consent, shaping how Apple and Google gate location APIs going forward.
The trend: Ambient proximity computing is shifting from retailer-pushed beacon hardware to OS-controlled, consent-gated location services, with the platform owners deciding what reaches users.