I bought a set of proximity beacons for use at a careers event. The beacons will broadcast the address of our website when people are near our stand. I’d also like to configure the beacons so that tapping on them with a phone will launch the website via NFC.
It does not appear to be possible to set a URL NFC record on the beacon using the Estimote app (you can only set an Android app package name), so I installed Android Studio, downloaded a Configuration template, updated the SDK version to 0.13, and then modified the template to write a NFC URL record as detailed here:
This appears to have worked, in that I was able to build the updated sample, and use it to update a beacon with the app running on phone.
However, when I tap another Android device on the beacon, rather than opening Chrome immediately, it opens the “New tag collected” screen, on which you then have to tap the URL to open it in Chrome. This feels unnecessarily janky, and appears to be because the sample insists on writing the estimote.com:id and estimote.com:mac records as well.
How do I prevent this from happening? I need the beacon to just respond with a single URL record, so that Chrome opens immediately on the website when tapped.