Thanks for making this! I was switching from one video to another until I found yours. You have covered all the basics in the best way possible. So many moving parts in this. Thanks for explaining each and every step! I am grateful to you for sharing your knowledge without any filter.
Really helpfull video. These 3 videos help me to understanding the push notification concept. I have already waste 3 days and couldn't sort it out but your 3 videos help me to solve my problem within 1 hour. Thanks❤
Best resource out there. I integrated the push notification in a NextJS application by taking reference from your video. Excellent communication and explanation skills. Thankyou keep up the Good Work.
Really helpful understanding how it works, thanks for the videos.I wanted to understand what's the difference between using third party providers like using firebase and doing our native way apart from pricing
Nice explanation I understand in one go👍, i have one question if i closed browser & heat api from postman then notification shows ? How to send notifications to particular users some users in my application ? Any idea or reference code in node.js & react, Thanks ones again really good explanation… 👌🏻👍
Nice tutorial! Though it looks a bit odd to me that you have to pass the private key to the push service for chrome, to me this is like a compromise of security.
Great series for this push notification. I am not able to see the notification in chrome, though I am seeing the message (sent from the server ) is getting logged to console in push event oof the service worker. but its not showing on UI.
Hello! Thanks for the video! How can I send notification only for special users (if they triggered some events: register, success subscription e,t,c). How to link userId and subscription object?
It is very good, thank you. one question. If the user manually deactivates and reactivates the notification permission, the notification will not be sent to him. What should be done in this case?
Thanks for this awesome series! I guess the subscription will be updated at some point in time, or if more than one user connects from the same browser, so how can we update the subscription if the SW only runs once it’s registered? Or should it make a difference to register the sw on each page load?
It is necessary to establish communication between the client and the API. The API requires both the Private and the PUBLIC KEY, whereas the client only needs the PUBLIC KEY. The PUBLIC KEY represents the location where server notifications will be received by the client.
Hi buddy very nice video.. I want a list of that notification in my project so where I can click on bell icon and see all notification there. How can I do that can anyone give some reference or solution?
Service workers have good support for Safari, so technically it should work. There might be a few little tweaks in the implementation but most of it should be the same. PWAs again at the end of the day will depend on the browser because that's what the application will be running on. So if the browser supports the SW API well, it should work without any problems.
This is one of the most up-to-date and well-narrated series about web push notifications. The author clearly knows his sh*t.
Thanks for making this! I was switching from one video to another until I found yours. You have covered all the basics in the best way possible. So many moving parts in this. Thanks for explaining each and every step! I am grateful to you for sharing your knowledge without any filter.
Really helpfull video. These 3 videos help me to understanding the push notification concept. I have already waste 3 days and couldn't sort it out but your 3 videos help me to solve my problem within 1 hour. Thanks❤
Best resource out there. I integrated the push notification in a NextJS application by taking reference from your video. Excellent communication and explanation skills. Thankyou keep up the Good Work.
Appreciate it my man.
Nicely explained... good job ❤
Awesome bro. That’s very helpful
You save the day... All the documentation from Mozilla and Google couldn't explain clearly like you
well done on this one, really clearly explianed
Nice teaching strategy, really enjoyed you teaching, keep it up bro.
Appreciate it 🙌
Really helpful understanding how it works, thanks for the videos.I wanted to understand what's the difference between using third party providers like using firebase and doing our native way apart from pricing
great video bro thanks, what about a video on how to get data from background PN and pass it to the application? It would be great, many thanks
Smoothly explained 👍🏻
Thank you 👍
Nice explanation I understand in one go👍, i have one question if i closed browser & heat api from postman then notification shows ?
How to send notifications to particular users some users in my application ?
Any idea or reference code in node.js & react,
Thanks ones again really good explanation… 👌🏻👍
Nice tutorial! Though it looks a bit odd to me that you have to pass the private key to the push service for chrome, to me this is like a compromise of security.
Great series for this push notification. I am not able to see the notification in chrome, though I am seeing the message (sent from the server ) is getting logged to console in push event oof the service worker. but its not showing on UI.
Hello! Thanks for the video! How can I send notification only for special users (if they triggered some events: register, success subscription e,t,c). How to link userId and subscription object?
It is very good, thank you. one question. If the user manually deactivates and reactivates the notification permission, the notification will not be sent to him. What should be done in this case?
7:11 XD
btw thanks for the video, good explaination. Also please make a video on background data synchronisation using SW
Thanks for this awesome series! I guess the subscription will be updated at some point in time, or if more than one user connects from the same browser, so how can we update the subscription if the SW only runs once it’s registered? Or should it make a difference to register the sw on each page load?
Not all heroes wear capes
It is necessary to establish communication between the client and the API. The API requires both the Private and the PUBLIC KEY, whereas the client only needs the PUBLIC KEY. The PUBLIC KEY represents the location where server notifications will be received by the client.
how do i get my own array buffon key, the steps is complicated after i pasted my public and private key
I created a chat app and someone sent me a message my Chrome browser is closed I'm still able to receive a push notification using the service worker.
Hi buddy very nice video..
I want a list of that notification in my project so where I can click on bell icon and see all notification there.
How can I do that can anyone give some reference or solution?
How creat backend app on google app script and sendNotification from this and save subscriber on google sheet it is posible ?
@everyone can we use this for e-commerce application, after placing an order or cancelling order?
Very good video series. What about Safari on iOS?
Does this method also work with PWAs on iOS and Android?
Service workers have good support for Safari, so technically it should work. There might be a few little tweaks in the implementation but most of it should be the same. PWAs again at the end of the day will depend on the browser because that's what the application will be running on. So if the browser supports the SW API well, it should work without any problems.
GOAT
but how can we do this on a live server ?
Nice.. Good job.
Hello sir, Please help me sir I want to background notification event i want please help sir
Bow💯💯💯🔥🔥🔥
will it work on node 18?
Yes it will
i love you
Wow, thanks I guess.
7:21 I can relate :(
💔 Promo`SM