Open Armstrong30 opened 7 years ago
At this point we have to be very careful about battery life, scanning every few minutes for all users all of the time can be non-trivial in terms of battery use. As the Physical Web is real world event, we're starting with the out-of-pocket scenario which seems to cover the main use case.
We agree that having scanning happen more often is of course better for the user when there are new beacons around. There are two ways that this can be improved that we're working on:
@scottjenson Thank you sir! Either would work fine. We like to avoid the "download an app or physical web app" scenario. Would the Nearby icon be native part of the OS (part of settings) or require a D/L. Our use case has users enter a beacon zone with the screen already on. It is complicated to explain cycling the "screen on state" by turning the screen off and back on to receive notifications. The refresh screen pull down could be an acceptable way to consider as well.
The Nearby icon/app is available right now. When you turn on Nearby it offers to do so at the end of the flow and when you are in the nearby listview, the menu offers the same option. Is this obvious enough? Not really, but like I said, it is a first step.
Are there any plans for nearby notifications for users who already have the screen on for several minutes? The current implementation requires a screen on event. What about conditions where the user does not know that beacons are around him and the screen has been on for a while?