Imagine you walk in to Starbucks and your app pings you saying, hey try ‘Try your regular Caramel Latte with Chicken wrap today and get 20% off bill’
Imagine you walk in to airport terminal to board and your phone automatically bring boarding pass on to your phone’s screen.
Imagine you have ‘Bring milk’ in your to do list and when you are in Walmart, and beacon in Walmart suggests you an offer ‘$2.19 for 2% fat, 2 gallons as special deal just to you’
Now imagine a world where every beacon that helps you build such scenarios as part of a global registry and each beacon has a unique metadata associated with it in that global registry, to store both public (imagine information about tourist places) and private (Starbucks, Airports, Stores, Offices, etc) and which app to open or which website to open. And that global registry has an API to give access to that metadata and showcase unique thing about that specific place, thing or event or whatever is associated with that beacon.
Now imagine a generic app to trigger specific apps ( Starbucks app, Office login apps, Airlines app, Store apps etc,) or webpages (wikipedia links) based on stored credentials on the app and the beacon information from global registry.
These are two sided implementations.. on server, given a loyalty card info on phone, combined with beacon metadata, phone can ping the server for a specific deal that is customized for that specific user. On client, it is a simple app that talks to global registry and goes to corresponding service implementers to fetch relevant data for that place, thing or event!
Ok.. Can it be done? Why not, using iBeacons from providers like Estimote, MobStac, BKON and others, cross platform mobile apps that share almost 90% codebase and all written in C# using Xamarin and Azure IoT Services combined with the latest Azure App Service, world is your playground.