Open saliozzia opened 7 years ago
Default notification is MIN, once you tap on a notification than the notification for that URL turns LOW (apears on lockscreen).
@ferencbrachmann thanks. To clarify, once I tapped on it, for me future experiences with the notification were set to LOW (up from MIN)?
Also how long does this change stay in effect? when does it reset back to MIN?
I was away from my beacon for 10 hours today, upon returning it seemed to be back to MIN.
The questions you're posting are kind of a black box for the community and they are subject to change as Google is doing a lot of user testing with this as we speak. But we'd love to hear more on the matter from @scottjenson @nondebug
Thanks. Really the big issue is getting these to be usable. They simply would be too low in engagement right now for us, and I see many others, to consider deploying.
There is no real concept of "intent" to find something when people are digging around in the MORE list of notifications. The expectation would be to see more info on the notifications that are represented by icons. Not to discover if anything new and wonderful is hiding in my long ass list of notifications.
To me this is more of a soft launch user experience while they work out some back end issues. If that has been stated elsewhere, just point me to that. :)
Not to jump in yet again but this 'black box' issue is a bit problematic.
The challenge first is there doesn't seem to be consistency. We've read/heard/seen varying reports of how it's handled and need to be able to plan a campaign knowing what is 'locked' and what isn't.
I realize this is more of a Nearby issue than Physical Web but as I noted elsewhere, there's also a black box with Physical Web that can be remedied with at least a bit of aggregated data or ability to A/B test the phrasing of notifications.
The good news is that with Chrome URL we're adding even more ways to try to ensure PW detection and then throw in Samsung CloseBy for good measure.
All really good discussions but we're all, I think, faced with problems of opacity and a lack of benchmarks which is making it difficult to proceed.
I am working on a restaurant based solution that could benefit from this nearby notification. currently our test show the notification's current minimum priority behavior. However I have seen the notification on the lock screen a few times. Can you provide clarity on the lock screen behavior?
Is it within reason to consider showing the notification on the lock screen, without vibration or sounds etc. As that would be the ideal moment when someone is about to unlock their phone or just check the time in a place, to expose to them that there is a nearby to interact with.