It’s no secret that both Apple and Google support Bluetooth beacon detection. It’s also no secret that the two companies take very different approaches to beacons.
Google adopts a more open approach, while Apple contains almost everything in it’s closed ecosystem. Google’s Android operating system allows you to detect any beacon signal. Apple only lets an app search for 20 UUIDs at a time*.
As this pertains to beacon detection, our data shows that Android clearly has a substantial advantage in detecting beacons. But so what…why does this matter?
As beacon adoption continues at a rapid pace, consumers with Android phones will be able to take more advantage of everything the beacon ecosystem has to offer.
We shared this data, and many more “Hidden Secrets of Beacon Data” in our June webinar. Want to see all of the data?
* A UUID is a top-level identifier for beacons, much like a parent category. For example, Major League Baseball deployed thousands of beacons across their stadiums.
UUID (parent identifier): All MLB beacons
Major (child identifier): Beacons at Fenway
Minor (grandchild identifier): The beacon at one specific location in Fenway.
The point we’re making here: Apple limiting beacon scanning to 20 UUIDs is constricting, but one UUID may represent thousands of beacons.