Home Projects Portfolio Dashboard Export PDF Log in

Optimizing Notification UX: Moving from Persistent Bells to Ephemeral Toasts

Rethinking Background Notifications

In the landing project, we recently re-evaluated how our background jobs communicate status updates to users. Previously, many of our automated processes—such as CV analysis or technology skill syncing—triggered database-persisted notifications. These would accumulate in the Filament bell icon, creating a cluttered "notification debt" for users who rarely checked them.

The Problem: Notification Clutter

Database-persisted notifications are excellent for critical alerts requiring user action, but they often become "noise" when used for automated background updates. Over time, these entries accumulate, requiring manual dismissal and potentially masking important updates. We noticed that jobs like ReviewCvAtsJob or AnalyzeGitHubSkillsJob were flooding the notifications table, providing little real value to the user experience.

Moving Toward Ephemeral Feedback

We decided to remove these persistent entries, allowing the background jobs to finish their tasks silently or handle user feedback through more lightweight mechanisms. For non-critical updates, we are shifting towards ephemeral "toast" notifications. Unlike persistent database notifications, these UI-based toasts are transient, non-intrusive, and auto-dismiss after a few seconds.

Implementation Cleanup

To clean up the codebase, we removed the sendToDatabase() calls from our background dispatchers. This not only reduces database load but also declutters our notification logic.

// Before: Persistent notification triggering
public function handle(): void
{
    // ... processing logic
    Notification::make()
        ->title('Technologies updated')
        ->sendToDatabase($user);
}

// After: Background jobs focus purely on the task
public function handle(): void
{
    // ... processing logic
    // Notification logic handled purely by transient UI events if needed
}

By simplifying these classes, we removed unused imports and stale configuration variables, resulting in a cleaner, more maintainable service layer. The underlying business logic—such as skill analysis and CV scoring—remains intact, ensuring performance while improving the overall UX.

Conclusion

Refactoring your notification strategy is a great way to improve product polish. By reserving persistent notifications for truly actionable events and using ephemeral toasts for status updates, you can keep your UI clean and your users focused on what matters most. Always evaluate whether a user needs to see a notification history or if a simple status message is sufficient.


Generated with Gitvlg.com

Optimizing Notification UX: Moving from Persistent Bells to Ephemeral Toasts
Germanwithpants

Germanwithpants

Author

Share: