|
|
|
|
|
|
by magicalist
3996 days ago
|
|
|
As others noted, the packet format is documented. But this: > I really dislike the decision to make it part of the Play API (as opposed to standard Android), as it ends up not being really open after all. doesn't really make sense. How do you open source storing data associated with a beacon in the cloud? The beacon is dumb so it's the client program that associates the broadcast with some action. The only way to open source that is to document the format of the beacon broadcast and release tools to let anyone receive them and parse them, after which any action can be taken. Which is exactly what was open sourced. The Play Services support seems to just be that you don't have to do it yourself if you don't want to on Android™ devices, because play services already has support. If they really want this to take off in iOS apps, though, the only real way they can help developers out is by releasing source directly, I believe (the git repo includes an example iOS app[1] but I haven't looked at it yet) [1] https://github.com/google/eddystone/tree/master/tools/ios-ed... |
|
|