A Ruby on Rails gem for sending notifications across multiple channels like email, SMS, Slack, and real-time UI updates.
Noticed is a Ruby on Rails gem that provides a unified system for sending notifications across multiple channels—including email, SMS, Slack, and real-time UI updates—from a single event in your application. It solves the problem of managing disparate notification logic by centralizing delivery methods, supporting both personalized alerts for users and bulk broadcasts for teams.
Ruby on Rails developers building applications that need to notify users or internal teams via various communication channels, such as SaaS products, community platforms, or internal tools.
Developers choose Noticed for its deep Rails integration, extensible delivery methods, and database-backed notification records that simplify rendering in-app feeds. It eliminates the need to write boilerplate code for each notification channel while offering fine-grained control over delivery logic and recipient preferences.
Notifications for Ruby on Rails applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Centralizes delivery across email, SMS, Slack, push notifications, and more from a single event, eliminating the need for separate implementations for each channel.
Leverages Rails conventions like ActiveJob for background processing, I18n for translations, and URL helpers, making it feel native to Rails developers.
Automatically creates Event and Notification records for all alerts, enabling easy querying, analytics, and rendering of in-app notification feeds without extra work.
Supports custom delivery methods via generators and allows fine-grained control with conditional if/unless lambdas, delays, and queues for each channel.
Exclusively designed for Ruby on Rails, so it cannot be used in applications built on other frameworks or languages, limiting its portability.
Inherently creates database records for every notification, which adds storage and performance considerations even for ephemeral alerts that don't need persistence.
Each delivery method requires specific setup—like API keys for Twilio or Slack—and understanding of external services, increasing initial integration time.
Renaming Notifier classes breaks existing notifications and requires manual database backfills, as admitted in the 'Best Practices' section, posing a maintenance risk.