O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Clicking on the real world with iBeacon and eddystone

My slides from my Xamarin Evolve talk on iBeacon and Eddystone

  • Entre para ver os comentários

Clicking on the real world with iBeacon and eddystone

  1. 1. Clicking on the real world with iBeacon and Eddystone Jim Bennett Mobile Application Developer at EROAD in New Zealand http://eroad.com @JimBobBennett http://JimBobBennett.io Question during the talk? Tweet them to @JimBobBennett
  2. 2. Buying coffee is not as easy as it could be…
  3. 3. We click on apps all the time… Our phone has become an extension of our physical selves But to interact with the real world we have to find the virtual representation of the world on our phones
  4. 4. …but can we ‘click’ on the real world? Can our phone intuitively show a link to the app for the coffee shop we are in? Can the act of walking into a coffee shop ‘click’ the buy button on their app? Can sitting down in the coffee shop send the app our seat location?
  5. 5. Yes - using bluetooth beacons Bluetooth Low Energy Beacons transmit an Id to any device that is listening Apple created iBeacon - focus on proximity/indoor location and notifications to installed apps Google created the Physical Web using Eddystone beacons and iBeacon - focus on attaching URLs or messages to physical locations and interacting with them on demand
  6. 6. iBeacon on iOS Transmits an Id (128bit GUID), major and minor version (16bit int), transmission power indicator iOS apps can monitor for an Id/version even when terminated, and be woken up Once awake the app can range all found beacons to get distance based off transmission power Lock screen icons when in range of beacons Built into the Core Location iOS APIs and needs user location permissions Any app can monitor or range any iBeacon id’s
  7. 7. iOS iBeacon Hands-On Coding Demo
  8. 8. Google’s open source beacon standard and part of the Physical Web - attaching URLs or messages to physical objects Eddystone UID transmits a 10 byte namespace and 6 byte instance Eddystone EID is like UID but with a rotating, secure ID Eddystone URL transmits a compressed URL All formats also include a TLM packet for telemetry (e.g. remaining battery life) Google have published a configuration GATT service Eddystone
  9. 9. Eddystone UID/EID Beacons are registered using the Proximity API to a project so can’t be shared between different apps Interact with UID using Nearby Messages API from Google Play Services Messages can include a latitude, longitude, floor location or Place Id for use with the Places API Requires internet connection Passive interaction - will not wake your device up EID - same as UID except using a secure, rotating ID
  10. 10. Eddystone URL Compressed URL embedded in the BLE packet Only 17 ASCII characters available but they have shortcuts for http://, https://, www, .com etc. Chrome or Google Physical Web app can show these links on Android lock screen or iOS Chrome today widget No SDK available - just code examples based on raw BLE interactions
  11. 11. Which one to use? Depends! iBeacon for waking your app up and for indoor location Nearby Messages API helps with crowdsourced location data from Places API Nearby Messages API works on iOS and Android with Eddystone and iBeacon Vendor SDK’s are blurring the lines - they support iBeacon like functionality on Android Newer beacons can broadcast both iBeacon and Eddystone at the same time
  12. 12. Plenty of vendors providing hardware Vendors have proprietary API’s with extra functionality and back end management systems Where to get beacons? Xamarin Component Available!
  13. 13. Questions? @JimBobBennett jim@JimBobBennett.io http://JimBobBennett.io http://github.com/JimBobBennett http://slideshare.net/JimBennett10 http://careers.eroad.com