๐ BIG NEWS ๐ โฆ Avo 4 has officially SHIPPED โฆ ๐ the beta is over, 4.0 is here โฆ ๐ ๏ธ build admin panels, dashboards & internal tools at light speed โฆ โญ you are visitor #1,136,382 โฆ ๐ tell a friend โฆ best viewed in Ruby on Rails โฆ ๐ click here to see what’s new โฆ
Notifications
Keep users in the loop with in-app notifications for the events and updates that matter.
# $30/mo
gem "avo-notifications"
The moment something matters in your app, a new signup, a failed payment, an order
that needs a human, the right people in your admin should know. Notifications puts
that message in front of them. Call
Avo::Notifications.send
from an action, a model callback, or a background job, and it reaches one user, a
handful, or everyone, each with their own copy to read, act on, and clear.
The payoff is a team that reacts in minutes instead of finding out at the next standup, and an inbox each person actually trusts because the read, saved, and done state is theirs alone, not a shared feed everyone ignores. Turn on real-time delivery and the bell updates the moment a notification lands, no refresh. You install and configure a gem; you don't design, build, and then babysit a per-user inbox and a delivery pipeline for the life of the app.
What you get
-
Reach exactly the right people, one user, an array of users, or
:all, with a separate notification per recipient so nothing is shared by accident -
Let people act without leaving the bell, up to three buttons per notification, each with its own
get,post,patch,put, ordeleterequest, plus an optional click-through link -
Signal urgency at a glance with four levels (
info,success,warning,error) and a freeformnotification_typetag you can route and filter on - Give every user an inbox they can rely on, with read, saved, and done state tracked per recipient instead of one feed everyone shares
- Skip the layout work, a navbar bell with an unread badge and recent-items dropdown shows up automatically for signed-in users
- Manage it like the rest of your admin through a generated Avo resource with Inbox, Unread, Read, Saved, and Done scopes and matching bulk actions
- Keep the bell live without a polling loop to maintain, real-time delivery rides ActionCable as Turbo Streams and falls back silently to a page refresh
Why it pays off
- An LLM can scaffold a notification system in an afternoon, but you still own the edge cases, the security, and every Avo upgrade after that. Here that upkeep is ours.
- It is built for a wide range of Avo apps, so it already handles what a one-off build tends to skip: per-recipient fan-out, per-user read and saved and done state, and a real-time path with a refresh fallback.
- When something breaks, it is our code in our back yard, so we fix it and ship the fix to everyone instead of you debugging admin plumbing alone.
- Your team sees what happened the moment they open Avo, and your developers stay on your product instead of building and supporting a notifications service.
# included in
# ready to ship?
You ship it this afternoon. We keep it solid for years.