> My problem with this is that no-one else other than Google and Apple can build an "open" network - you'd have to find a way to push your code to everyone's devices.
If you want a non-Apple, non-Google solution, you go to the OG tracker tag -- Tile. You have to install their app, so the reach won't be nearly as extensive, but that is fine by me -- the last thing I want is a third party developer able to push code to my device without me explicitly installing it.
Yes - but my point for that wasn't about allowing anyone to push anything on random devices. It was about the market penetration of those two companies.
Tile, as you mentioned, will never get any reach since users have to opt-in to start contributing to the location data, making their network incredibly smaller compared to Apple's or Google's own networks.
If you're Tile - you have no way to start such a network because you'd have to convince every single iPhone user (or Android user) to install your app, while Google / Apple can just do it with the push of a button (kind of!)
My point was about starting your own network with a similar coverage - it's nearly impossible. Thus competing with Apple or Google here is extremely difficult.
A protocol that allows the beacon to define which endpoint is used to forward the encrypted location data.
Alternatively (since the adv data is limited), a "routing" endpoint that allows custom endpoints to be defined depending on the network ID.
There are plenty of possible implementations that would allow for a fair market in this regard, but I don't think Apple or Google would ever introduce them, unless forced to
If you want a non-Apple, non-Google solution, you go to the OG tracker tag -- Tile. You have to install their app, so the reach won't be nearly as extensive, but that is fine by me -- the last thing I want is a third party developer able to push code to my device without me explicitly installing it.