ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Eddystone- Google's weapon in Beacon Industry

Updated on November 19, 2015

What is Eddystone?

Eddystone is a Google's alternative to iBeacon. It's a new method of broadcasting Bluetooth Low Energy (BLE) data from beacons. It encircles what iBeacons can do plus adds even more context.

Eddystone, likely inspired by the lighthouse off the British coast, is Google's grand entry into the beacon market. As per Google, they have serious discussion with numerous beacons providers, regarding the current limitation of the technology.

Eddystone is Open

Specifications of Eddystone are published openly on the web and have been driven by the community; anyone can access it and contribute to it.

Eddystone is for both iOS and Android

With the market demands, Eddystone should support Android, along with iOS, which it is doing. It is meant to be the most robust beacon. So far iBeacons has been making his marks for iOS and now we have something, which will support Android too. You can even also use the Nearby API to develop solutions based on the other formats. Its like one proximity service for any device and for iBeacon profile and Eddystone format.

Its not just flexible, it also opens up the technology to a wider section of use cases. Eddystone includes new APIs to make beacons more powerful. Nearby APIs makes it easy for an app to find and communicate with beacons to get specific information and context.

Best part of it, Proximity is that it's impossible to put in the latitude and longitude coordinates, indoor floor level, and Place ID, which feed into the Google Maps. Which eventually means that Google is now able to know and can direct you to a specific product showcased with in a specific area of the retail shop in your Google Map.


Beacons supporting Eddystone can broadcast three different advertising packages called frames types:

  • Eddystone-UID - A beacon's unique ID number. This frame type triggers push notifications or app actions, just like Proximity UUID, that you know from iBeacon.
  1. Fundamentally identical to iBeacon
  2. Not 100%, but for most of the application it is
  3. All beacons that broadcast Eddystone-UID are registered in Google's database
  • Eddystone-URL - A URL that can be broadcasted by a beacon or other object. Once a user's device receives suck signals, it displays URLs broadcasted by nearby emitters, ranked by proximity.
  1. Indicates smartphone to open a URL
  2. Doesn't require and app to be already installed on user's smartphone.
  3. It needs Eddystone functionality exists on the user's smartphone.
  4. A great engine to encourage users to install apps that are actually relevant to the location.
  • Eddystone-TLM (Telemetry) - It's the data obtained by the sensors. This frame type enables you to trigger different kinds of actions, depending on different situations, such as temperature, loudness, humidity or pollution.
  1. Sends Sensor data
  2. Currently supports temperature and accelerometer.

Eddystone vs. iBeacons

  • While iBeacon officially supports iOS devices only, Eddystone support both iOS and Android officially.
  • The advertising packet is naturally different from that of iBeacon. Eddystone is designed to support multiple data packet types, starting with two: Eddystone-UID and Eddystone-URL.
  • There's a third type of packet Eddystone-TLM, this packet is broadcast alongside the Eddystone-UID or Eddystone-URL packets and contains beacon's health status, like battery life. This is indented for fleet management.
  • Eddystone support in the Estimote iOS and Android SDKs is based on a single method at this moment. Eddystone discovery, which is quite similar to iBeacon's ranging. It provides proximity estimates and works only when the app is active.

iOS and Android compatible but natively only for iOS
Android and iOS compatible. It may be a part of native Android with Android M release, this would completely transform expectation for IoT, since, every smartphone would have native support for receiving notifications, even if there is no app installed via Eddystone URL protocol
Simple and Easy to implement
Flexible and opens new possibilities but at the same time requires more complicated coding to integrate as it sends more types if data than the Beacon.
Not an Open-source, specifications are in Apple's side.
Open source, specifications are published openly on Github.

Eddystone at Google beacon platform

Google beacon platform consist of following components:

  • Beacon devices
  • Eddystone format
  • Proximity beacon API

What's next?

Beacons are an important way to deliver better experience for users of your apps, specially on the retail side, whether you choose Eddystone with your own product and services, or as a part of a broader Google Solution like Places API or Nearby API.

With Eddystone and the new Google APIs, new doors of innovation have been opened. Since its an open platform, it makes the developers to jump in an use it in any way to make it useful for the world. Google is enhancing the way beacons works and they are in a right direction towards the flexible and a cross- platform solution. Soon there will be a day, when you approach a soda machine, which offers you a coupon for your next arrival, without having first installed the Soda app in your smartphone.

What do you like Most?

See results


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)