An open Bluetooth Low Energy (BLE) beacon protocol specification from Google for proximity messaging.
Eddystone is an open Bluetooth Low Energy (BLE) beacon protocol specification from Google that defines a message format for proximity beacon communications. It enables devices to broadcast different types of data frames, such as unique identifiers, URLs, telemetry, and secure ephemeral IDs, for applications like location-based services and secure asset tracking. The specification is designed to be interoperable, flexible, and compatible with both Android and iOS platforms.
Hardware manufacturers, IoT developers, and application developers building proximity-based solutions, such as location-aware apps, asset tracking systems, or secure beacon networks.
Developers choose Eddystone for its open, standardized approach to BLE beacon messaging, which includes secure frame types like Eddystone-EID for encrypted broadcasts and a flexible architecture that supports multiple use cases while ensuring cross-platform compatibility.
Specification for Eddystone, an open beacon format from Google
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designed to work well with Android and iOS Bluetooth APIs, ensuring broad device support for proximity applications.
Eddystone-EID provides cryptographically secure broadcasts that only authorized parties can decrypt, enhancing privacy for sensitive use cases.
Supports multiple frame types like UID, URL, TLM, and EID, allowing for diverse applications from location services to asset tracking.
Defines a GATT configuration service for interoperability between hardware and apps, simplifying beacon setup and management.
As a protocol specification, it requires deep BLE knowledge and custom implementation on both hardware and software sides, with no out-of-box solutions.
Provided tools are primarily Android-focused and basic, lacking comprehensive SDKs, iOS samples, or cloud management features.
Being a Google-driven specification, adoption depends on manufacturer support, which could lead to fragmentation if not widely embraced.