Open lxborges opened 6 years ago
jmartsch
commented
6 years ago Hello @lxborges Scott Jenson is not longer involved in the Physical Web. See this comment https://github.com/google/physical-web/issues/931#issuecomment-340843273 Also there are many similar posts to yours here on github and on the Google Group https://groups.google.com/forum/m/#!forum/physical-web-discuss Please have a look.
ferencbrachmann
commented
6 years ago @lxborges Nearby is taking a ton of factors into consideration when to fire a notification or not. It may not be inconsistency at all, but your page performance might not be sufficient. I suggest you take a look at my blog post especially section 3. http://blog.beeem.co/2018/02/the-ultimate-nearby-notification-troubleshooting-guide/
lxborges
commented
6 years ago Hi @ferencbrachmann . Tks for the info. I have read the blog and noticed that is normal to notify from nearby 5-8 mins. To receive fast, the user should turn off the screen and turn on again or going to nearby app directly. Also, vague phrases or generic in the title (notification message) are not good sometimes. Am I correct?
ferencbrachmann
commented
6 years ago @lxborges Yes, I've detailed this in the blogpost.
lxborges
commented
6 years ago Yes. I have read it. Useful blog and article. Thank you!
Hi @scottjenson. We have 200 beacons deployed in a Brazilian Proximity Marketing Project and nearby is incosistent. Sometimes works normally and sometimes not. Should it silently notifies when a supposed smartphone turn on (local+bluetooth) gets on a perimeter bluetooth? some smartphones properly notifies and others only minutes later...