Classic Bluetooth and BLE are different animals and have different theory of operation - unless they make Beacon Operation back compatible somehow then maybe yes
::::: speakerdeck.com/devunwired/google-beacons-and-the-physical-web Google Beacons and the Physical Web by Dave Smith Published July 30, 2015 in Programming An introduction to Google's Eddystone beacon format, their Proximity Beacon API features, and the Physical Web project. ::::: venturebeat.com/2015/07/14/google-embraces-bluetooth-low-energy-beacons-launches-open-format-eddystone-apis-and-management-tools/ Google today launched Eddystone, a new open format for Bluetooth low-energy (BLE) beacons to communicate with people’s devices. To help developers build apps using this technology, Google is also debuting APIs and updating its various mobile services. Last but not least, Google is also offering a way to manage a fleet of beacons efficiently. Electronic beacons have many uses, but Google is most interested in how they can be used to give mobile apps more functionality. They can provide precise location and contextual cues: A beacon can label a bus stop so your phone gets your ticket ready, or a museum app can give you more information about the exhibit you’re looking at. Eddystone is Google’s attempt to build a new class of beacons that address real-world use cases, cross-platform support, and security. Eddystone supports multiple frame types, allows versioning to make introducing new functionality easier, and works with any platform that can communicate with BLE beacons (including Android and iOS).
Exactly what I was looking for. Thanks!
What is the max spead that you can send beacons at?
can i use my old mobile phones; bluetooth as beacons for testing?
Classic Bluetooth and BLE are different animals and have different theory of operation - unless they make Beacon Operation back compatible somehow then maybe yes
::::: speakerdeck.com/devunwired/google-beacons-and-the-physical-web
Google Beacons and the Physical Web by Dave Smith
Published July 30, 2015 in Programming
An introduction to Google's Eddystone beacon format, their Proximity Beacon API features, and the Physical Web project.
::::: venturebeat.com/2015/07/14/google-embraces-bluetooth-low-energy-beacons-launches-open-format-eddystone-apis-and-management-tools/
Google today launched Eddystone, a new open format for Bluetooth low-energy (BLE) beacons to communicate with people’s devices. To help developers build apps using this technology, Google is also debuting APIs and updating its various mobile services. Last but not least, Google is also offering a way to manage a fleet of beacons efficiently.
Electronic beacons have many uses, but Google is most interested in how they can be used to give mobile apps more functionality. They can provide precise location and contextual cues: A beacon can label a bus stop so your phone gets your ticket ready, or a museum app can give you more information about the exhibit you’re looking at.
Eddystone is Google’s attempt to build a new class of beacons that address real-world use cases, cross-platform support, and security. Eddystone supports multiple frame types, allows versioning to make introducing new functionality easier, and works with any platform that can communicate with BLE beacons (including Android and iOS).