Extract Action Notifier framework for push notifications about rails HOT 13 OPEN

Magnus Hult has very kindly agreed to transfer the gem name for use with this. So the name will be Action Notifier. We will keep the old versions of the gem to ensure no old user is left in a lurch, and we'll start the versioning with Action Notifier 8.0.

from rails.

Very excited for this! For more art to be examined, I've used Noticed from @excid3 on a bunch of my projects. It's been especially helpful for wrangling iOS + Android push notifications.

from rails.

YOU ARE HERE: 📍 Bikeshed

Action Notifier has a bit of linguistic overlap with ActiveSupport::Notifications. If we are considering alternative names, what about Action Push?

from rails.

This just came up in a conversation on Noticed because I'm setting up an engine for push notifications + noticed. I have a working version here: http://github.com/jbennett/noticed-web_push.

Takes about 30 seconds to add web push to an app already using Noticed.

from rails.

Action Notifier should also address the need for controlling the PWA badge counter. That's tied to the hip with Web Push, since the only time you get to reliably move the counter is when a notification is delivered.

from rails.

Re: gem naming conflict - perhaps Action Alert or Action Broadcast?

Or maybe Action Notify or Action Notification. Broadcast might be a bit confusing because of ActionCable?

from rails.

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).

I'm curious what the "Rails Way" of handling SMS is or should be. Most apps I've built in the last 10 years have needed it and a nice abstraction ala ActionMailer or this proposal would be appreciated. Fwiw we are currently using ActiveDelivery for this.

from rails.

There is a Ruby gem for connection to APNs (Apple Push Notification service):

https://github.com/ostinelli/apnotic

Hopefully it's already well known, but mentioning it here in case it isn't.

If the logic to connect with APNs (and Google equivalents) is kept in separate gems, it makes it easier to share the interoperability burden with other projects.

First: I love Rails, I'm a happy user for 10+ years! ❤️

But sometimes Rails will inline logic that could otherwise have been kept in an external gem, where it would have been accessible to Ruby projects 'outside the web sphere'.

Put differently, Rails is so big in the Ruby ecosystem, that when it takes on a task, it risks choking out smaller gems with similar scope (because when Rails does it on it's own, all Rails projects will use that mechanism, but non-rails projects usually cannot piggy-back on it, because it's inlined and coupled with Rails).

This isn't always the case. Overall, Rails is playing well with the ecosystem and there are many instances of the opposite [of what I describe above].

One example is image_processing -- used by ActiveStorage, but a separate gem. But just wanted to suggest following that pattern when it comes to APNs and Firebase interactions too.

from rails.

Magnus Hult's agent checking in here — opening bid is $5,000

from rails.

Very interesting)

from rails.

With the current PWA files solution you are serving up a service_worker.js template. This pulls it out of the normal JS ecosystem used in the rest of the app. Have you considered doing something like having the controller look into the asset pipeline for a service worker entry point and serving that directly?

I've been working on some PWA/WebPush stuff and took that approach so that I could mount the asset from the root and keep everything else in the normal asset pipeline: https://github.com/jbennett/noticed-web_push/blob/132116a5c22bbf491c5e6d09f621f0a65c49ac6d/app/controllers/noticed/web_push/pwa_controller.rb#L4C18-L4C18

from rails.

Re: gem naming conflict - perhaps Action Alert or Action Broadcast?

Or maybe Action Notify or Action Notification. Broadcast might be a bit confusing because of ActionCable?

also Action Notice ?

from rails.

I'm curious what the "Rails Way" of handling SMS is or should be. Most apps I've built in the last 10 years have needed it and a nice abstraction ala ActionMailer or this proposal would be appreciated. Fwiw we are currently using ActiveDelivery for this.

may i suggest sms_kit? i’m the author. let me know if you need something changed or added.

from rails.