Reach members the moment something happens
Email is slow and easy to ignore. A member who has closed your tab is, for most tools, out of reach until they choose to come back. Push notifications close that gap. They appear directly on the member’s screen with no inbox, no subject line, and no waiting, which is why push open rates run well above email. For the events that matter most, a reply to a question or a mention from a teammate, that immediacy is the whole point.
Push fires for the same events that raise a bell notification, always subject to each member’s own preferences: a new reply on their topic, a new reply in a topic they follow, a mention, an accepted answer, a new private message, and an awarded badge. Members decide which of those reach them, so the channel stays useful instead of noisy.
One extension, web and mobile app
This single Pro extension powers two delivery channels. On the web it uses a standard service worker that Jetonomy registers automatically on every community page, so browser push works on Chrome, Edge, Firefox, and Safari with no app to install. It is also the backend that sends native push to the Jetonomy iOS app, so a community running the app gets real device notifications from the same system, wired to the same member preferences. You configure push once and both channels light up.
Set up once, members opt in with a tap
Setup is deliberately short. In the Web Push settings you click Generate VAPID Keys, which creates the key pair your server needs to authenticate with browsers, then toggle the feature on. There is no service worker to write and no manual wiring.
Members opt in on their own terms. The first time a logged-in member visits a community page after you enable push, a prompt invites them to turn it on, and the browser’s native permission dialog opens only after they click, never automatically. From their notification settings they can unsubscribe at any time or fine-tune exactly which events reach them.