Extract Action Notifier framework for push notifications
One of the most exciting developments in web standards this year was the full adoption of Web Push by Apple. This means we now have a reliable push notification standard that works in Safari, Chrome, and Firefox, which [reduces the need for native applications](https://world.hey.com/dhh/native-mobile-apps-are-optional-for-b2b-startups-in-2024-4c870d3e). But getting the service worker, web push configuration, and permission flow right is surprisingly complicated. We already have some great gems, like web-push, to handle some of the underlying plumbing, but putting it all together is far more complicated than it ought to be. So let's compress that complexity with a new dedicated framework. While compressing the complexity of Web Push is the primary motivation for Action Notifier, it's also a great time to add an plugin setup that allows us to plug in adapters for services like pinpoint or other native platform protocols. But the intention is not to support every possible delivery format for notifications under the sun (like SMS and definitely not email, we have Action Mailer for that). The first stab at this will be an extraction from ONCE #1. So until there's a first gem for this, let's hold any more detailed discussion of features or capabilities. Prior art that'll be examined: https://github.com/palkan/active_delivery + [Notified](https://github.com/excid3/noticed)
Posted by dhh on Dec 27, 2023, 12:58 AM
Tags
Related issues
- The only thing keeping me on VSCode these days is the remote SSH development.
- Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
- Proposal for OpenHarmony Adaptation of [ ThreadPool ]
- Proposal for a pipe-like operator to chain constructor/method invocations without nesting
- Implement support for Node Stashing
- RSC and CDN interaction makes next.js inefficient for highload projects
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
support (E-commerce)
The only thing keeping me on VSCode these days is the remote SSH development.
Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
Proposal for OpenHarmony Adaptation of [ ThreadPool ]
Proposal for a pipe-like operator to chain constructor/method invocations without nesting
Implement support for Node Stashing
RSC and CDN interaction makes next.js inefficient for highload projects
Extract Action Notifier framework for push notifications
Extract Action Notifier framework for push notifications
One of the most exciting developments in web standards this year was the full adoption of Web Push by Apple. This means we now have a reliable push notification standard that works in Safari, Chrome, and Firefox, which [reduces the need for native applications](https://world.hey.com/dhh/native-mobile-apps-are-optional-for-b2b-startups-in-2024-4c870d3e). But getting the service worker, web push configuration, and permission flow right is surprisingly complicated. We already have some great gems, like web-push, to handle some of the underlying plumbing, but putting it all together is far more complicated than it ought to be. So let's compress that complexity with a new dedicated framework. While compressing the complexity of Web Push is the primary motivation for Action Notifier, it's also a great time to add an plugin setup that allows us to plug in adapters for services like pinpoint or other native platform protocols. But the intention is not to support every possible delivery format for notifications under the sun (like SMS and definitely not email, we have Action Mailer for that). The first stab at this will be an extraction from ONCE #1. So until there's a first gem for this, let's hold any more detailed discussion of features or capabilities. Prior art that'll be examined: https://github.com/palkan/active_delivery + [Notified](https://github.com/excid3/noticed)
Comments (0)
No comments yet. Start the discussion.