Google launches Eddystone, an open source, cross-platform Bluetooth LE beacon format
Meet Google's “Eddystone”—a flexible, open source iBeacon fighter — Google's cross-platform standard combines the best of iBeacon and The Physical Web. — Move over iBeacon—today Google is launching …
Context & Ripple Effects
In mid-2015 Apple's iBeacon was the de facto proximity standard but was iOS-first; Google's answer is Eddystone, an open source Bluetooth LE frame format that also carries Physical Web URLs so any phone — not just iPhones — can discover what's nearby. Within two weeks Chrome on iOS shipped gestures that put the Physical Web in Apple's own browser, showing Google's cross-platform bet working against its rival's home turf.
The corpus then traces Eddystone's whole life: Chrome 49 for Android turned nearby beacons into system notifications alongside an IoT research pilot, Google layered in secure beacon frames for private interactions, and by 2018 a VentureBeat post-mortem declared Android Nearby, iBeacons, and Eddystone stalled on low consumer awareness and spammy notifications. That failure arc is the real story this launch opens.
First-order effects
- Apple's iBeacon gains a direct, open-source competitor that runs identically on iOS and Android, letting venue operators deploy one hardware fleet instead of per-platform stacks.
- Developers building on The Physical Web get a shipping standard overnight, with Google's own Chrome acting as the reader on both mobile platforms.
Second-order effects
- Beacon hardware vendors such as Estimote respond by differentiating beyond the protocol itself — its next-gen Proximity Beacons added programmable NFC chips — since commodity Eddystone compatibility erodes lock-in.
- Google's control of Chrome turns the browser into the proximity discovery layer, pulling web publishers and retailers into beacon deployments without requiring native apps.
Third-order effects
- The 2018 collapse — driven by low consumer awareness and spammy local notifications — sets a structural lesson that proximity push is a UX dead end; the surviving use of Bluetooth LE in Google's orbit reappears in 2023 as Nest's AirTag-like "Grogu" tracker, where the radio finds objects instead of shouting URLs at people.
- Platform-level standards battles of this shape end up favoring whichever ecosystem owns the notification surface, not whoever publishes the most open spec.
The trend: Proximity beacons are migrating from push-notification infrastructure toward findable-object tracking, with openness losing to whoever controls the consumer-facing surface.