{"id":4147,"date":"2019-09-03T23:05:14","date_gmt":"2019-09-03T21:05:14","guid":{"rendered":"https:\/\/stephaniewalter.design\/?p=4147"},"modified":"2021-01-18T10:07:05","modified_gmt":"2021-01-18T09:07:05","slug":"the-ultimate-guide-to-not-fck-up-push-notifications","status":"publish","type":"post","link":"https:\/\/stephaniewalter.design\/blog\/the-ultimate-guide-to-not-fck-up-push-notifications\/","title":{"rendered":"The Ultimate Guide to Not F#!@ing Up Push Notifications"},"content":{"rendered":"
TLdNR: push notifications became yet another way to artificially re-engage users and force content down their throat. That\u2019s why so many of them hate it. But there\u2019s some interesting use cases for it. Here is some advice on how to stop ruining it for the rest of us. Spoiler alert: stop asking for permission on page load (and make them useful for users)<\/em><\/p>\n A few weeks ago I stumbled upon a kind of fun \/ trollesque site: “Should I Add Push Notifications To My Website? – No<\/a>“.\u00a0 That’s all fun and I understand the purpose of this site and also why it exists. But I would not be that strict. There’s some interesting use-cases for push notification, BUT as usually website abused it for the sake of engagement. Users are now annoyed by it, the usual story of our industry. Here is my opinion and advice on that matter.<\/p>\n Push notifications used to be a \u201cnative app feature only\u201d. You needed users to download your app to push them content. But things changed. Thanks to a few cool APIs like Push<\/a> + Service Workers<\/a> browsers now have the ability to send notifications to users<\/strong>. This works on both mobile (Android Chrome and Firefox) and desktop (Chrome on Mac and Win, Safari on Mac and Edge on Win10). Fortunately, users need to give permission to the site to send those. And sadly, that\u2019s when things are starting to get annoying for them.<\/p>\nWe got greedy, that\u2019s why we can\u2019t have nice things<\/h2>\n