We want to use beacon technology in our applications to create interaction with events with screen off.
In this use case, we assume that the end user will be in constant motion.
So far, we have tested two different approaches.
- Kontakt SDK / Android Beacon Library to constantly scan beacons. Using the UUID (assuming we use Eddystone), we can associate it with the cached message we received for our back-end. However, this leads to a large amount of battery.
- Next to the message / next to Awareness, this had potential, as it has a beacon panel to easily configure attachments on each beacon and to have the “same” implementation on both iOS and Android. However, after reading the documentation and after numerous tests, we could not get the bindings of the beacon radio signals if we turned off the screen. The only possible way was to keep the user in front of the beacon for 3 minutes (depending on the settings of the smartphone and energy), and this contradicts our premise that the user is in constant motion, so scanning can be caused when the user is not located next to the lighthouse.
In addition: using “Neighbor Messages” on iOS, we had the desired behavior: the application would detect beacons when using “Neighbor Messages” if both applications and APIs were configured to use the background.
So we ask:
- Is there a way to use the Near-off API with events to turn off the screen? How to plan scans all the time?
- What other alternatives do we have that can be used cross-platform between iOS and Android? (so that we can try to provide similar behavior between platforms)
:
, BLE ( , ), . this.
: api Not Related Messages, , ? , iOS...