Hi, All
Web-browsers can be subscribed to the push messages from a web-site.
Firebase has VAPID keys for such communications: Web Push certificates (https://developers.google.com/web/u...s#introducing_vapid_for_server_identification).
And user must allow the notifications to the web-browser, to see the popup alerts from web-sites.
Subscription looks like
1) endpoint URL, for FCM like https://fcm.googleapis.com/fcm/send/fVsd.....
2) Public key (P-256 ECDH) for push-message encoding
3) The secret key for push-message encoding
Are these different push-messages ? Android push-messages and these Web Push.
The case is to make the web-site that can send such pushes to the web-browsers, I have made such web-site. And mobile web-browser can receive such Web Push-messages.
But, as we all know, Android kills apps and the browsers also after some time, even all is allowed.
So, how to arrange the push waking up the WebView Android app, opening such web-site ? Maybe anyone did and knows?
Web-browsers can be subscribed to the push messages from a web-site.
Firebase has VAPID keys for such communications: Web Push certificates (https://developers.google.com/web/u...s#introducing_vapid_for_server_identification).
And user must allow the notifications to the web-browser, to see the popup alerts from web-sites.
Subscription looks like
1) endpoint URL, for FCM like https://fcm.googleapis.com/fcm/send/fVsd.....
2) Public key (P-256 ECDH) for push-message encoding
3) The secret key for push-message encoding
Are these different push-messages ? Android push-messages and these Web Push.
The case is to make the web-site that can send such pushes to the web-browsers, I have made such web-site. And mobile web-browser can receive such Web Push-messages.
But, as we all know, Android kills apps and the browsers also after some time, even all is allowed.
So, how to arrange the push waking up the WebView Android app, opening such web-site ? Maybe anyone did and knows?