While I like the minimalism of the beacon API, I wonder if it doesn't limit the usefulness of this technology, as it leads to an over-reliance on mobile Internet (apps need to fetch information after detecting a relevant beacon) and/or preinstalled apps (which will probably not talk to each other very well).
It'd be interesting if beacons could send some structured data along with their identification header. This way you could have general purpose apps which handled common types of beacon data, and an user wouldn't have to install MegaWorld, GroceryMart and BigHealth to get generic grocery or health-related notifications.
For example: if there was a standard beacon format for bus routes, I could install a BusRoute app which would let me see bus routes for any beacon-enabled bus in the world, even in places where I don't have an Internet connection.
It'd be interesting if beacons could send some structured data along with their identification header. This way you could have general purpose apps which handled common types of beacon data, and an user wouldn't have to install MegaWorld, GroceryMart and BigHealth to get generic grocery or health-related notifications.
For example: if there was a standard beacon format for bus routes, I could install a BusRoute app which would let me see bus routes for any beacon-enabled bus in the world, even in places where I don't have an Internet connection.