|
<< Click to Display Table of Contents >> Navigation: Telegram > 2021 > 01 > 03 > Telegram_2021-01-03T16 |
2021-01-03T16:28:28
type: mention_name Jac user_id: 925574912 type: link https://webpushdemo.azurewebsites.net/ talks about some of this. Its down to what browser/services you want to use most likely. For the most part its including some .js files ( I assume mostly for device register/desegister from service and simply the HTTPS/body creation message posting to the provider) ... and after that the browser itself handles the rest.
Requiring the user to enable their browser for push notifications from your site... and the browser will handle this service of keep track of it.
2021-01-03T16:28:47
Can see how new edge browser has a spot for known push notification sites
2021-01-03T16:30:36
So to add for IW, i don't see much of an issue other than going through the pains of getting setup for FCM or whatever service to get your keys to the kingdom ( we use FCM for FMX mobile app push notifications ) and then just kicking off your JS code to run to register/deregister browsers.
then once you have known tokens of registered browsers, can fire off messages to those tokens in whatever method... ?
2021-01-03T16:34:50
FCM is my choice as its Chrome / New Edge browser happy.. and works for iOS and Android Mobile Apps really well.