Eddystone was a Bluetooth Low Energy beacon profile released by Google in July 2015. In December 2018 Google stopped delivering both Eddystone and Physical Web beacon notifications. The Apache 2.0-licensed, cross-platform, and versioned profile contained several frame types, including Eddystone-UID, Eddystone-URL, and Eddystone-TLM. [1] Eddystone-URL was used by the Physical Web project, whereas Eddystone-UID was typically used by native apps on a user's device, including Google's first party apps such as Google Maps. [2]
The format was named after the Eddystone Lighthouse in the UK, motivated by the simplicity of a lighthouse-signal and its one-directional nature. [3]
Though similar to the iBeacon profile released by Apple in 2013, Eddystone can be implemented without restriction. Eddystone also contains a telemetry frame (Eddystone-TLM) designed for reporting on a beacon's health, including, for example, battery level. Like other beacon technology, beacons with Eddystone can give devices a better indication of what objects and places are around them. [4] Importantly, beacons do not generally accept connections from other devices, meaning that the beacon itself cannot record what devices are in its vicinity. In many cases, the simplicity of the beacon frame means that an app (for example Google Chrome) is required in order to interpret the beacon's signal.
Nearby Messages is the API that can be used off of this protocol to receive data that is stored within beacons. Differing from iBeacon, Google beacons use not only Bluetooth but also WiFi and near ultrasonic sounds to communicate between devices. [5]
Eddystone has 4 frame types.
In tandem with the Eddystone, Google launched the Google beacon platform. The platform includes the Proximity Beacon API designed to associate content with individual beacons. [11] The Proximity Beacon API fronts a registry of beacons where extra information (known as "attachments"), useful to developers' applications, can be associated with individual beacon IDs. Several attachments can be associated with a single beacon. Attachments can be updated in real-time and can be retrieved by an app using the Nearby API in Android (through Google Play Services) and the Nearby library for iOS.
In 2018, the security of the Google Nearby API and ecosystem came under scrutiny from privacy advocates over the use and recording of ultrasonic (high frequency) audio in combination with Bluetooth and Wi-Fi to better discover, track, and connect nearby devices. [12] Users may not be aware of the extent of the information that is exposed and potentially recorded by consenting to the use of the Nearby API.
Google's navigation platform Waze has deployed Eddystone beacons in tunnels around the world (where GPS would not work) [13]
They transmit the following data:
They will ignore this information from any beacons that do not use an ID number belonging to Waze. [14]
In December 2018, Google stopped delivering both Eddystone and Physical Web beacon notifications. [15] The low number of users and the poor user experience were the reasons to discontinued the Eddystone beacons. Google continues to enable access to the beacon dashboard and can deliver proximity-based experiences similar to Nearby Notifications via third-party apps using the Proximity Beacons API.