A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF51422 & nRF52832 & nRF51802)
What is Eddystone
Eddystone is the standard for the beacon using the BLE that Google announced in July 2015.
It is available includes a number of broadcast frame types on all platforms that use the BLE, such as iOS as well as Android open standards, designed to give developers and venue owners flexibility in their beacon developments and applications. Eddystone helps beacons using the Proximity Beacon API, including adding attachments in the cloud and monitoring their health.
Eddystone’s biggest feature is not intended to become a black box such like iBeacon service, works only for iOS. Eddystone program code is designed to be an open standard and has been published in GitHub.
The difference between iBeacon and Eddystone is the “broadcast frame type”
iBeacon transmits ID only (1 Type)
Eddystone transmits not only ID, but also URL and TLM. (3 Types)
Unlike iBeacon, Eddystone provides target users to receive the message through URL without app installing as long as the Bluetooth is turned on.
Eddystone is allowed to transmit 17 bytes every packet.
Thus, in case of URL broadcast frame type, the data must be downsize to fit in this 17 bytes limitation
User Scence Example
- Real time Bus location and operation status
- Approaching or nearby the poster, the URL link will pup up feeding immediately
- Nearby Restaurant information feeding.
- Nearby Shops information feeding
Eddystone is designed to compensate the demerit of iBeacon’s, which is standardization.
However, iBeacon so far is still the most well-known and widely applied service right now as well as iPhone is the most well selling single mobile phone all over the word.
Thus, the trend of which one will prevail the competition between Eddystone Vs. iBeacon is still a interesting topic and lead the delimma for developers and user to observe closely.