Filament Presence Laravel Package

Product Decisions This Supports

• Feature and UX roadmap: Enables lightweight “who’s online / active” indicators inside Filament admin panels without building a custom presence system. Useful for support, account management, and internal collaboration workflows.
• Privacy and visibility controls: The new hideWhen() capability lets teams hide presence indicators for selected sessions, supporting scenarios where visibility should be limited by role, tenant, support impersonation, or sensitive operational context.
• Build vs. buy: For teams already on Laravel + Filament, this package is likely cheaper than building and maintaining session-presence UI, polling/broadcast behavior, and Filament-specific integration.
• Scope control: Presence indicators are a focused UX enhancement, not a full real-time collaboration suite. PMs can adopt it as an incremental admin-experience improvement without committing to a broader realtime platform.

When to Consider This Package

• Consider it when the product is built on Laravel and Filament, and the team wants a small, opinionated presence indicator in admin or internal tooling.
• It fits when the need is visibility of active/online sessions, not chat, typing indicators, notifications, or a full presence infrastructure.
• The new hideWhen() feature makes it more relevant when presence visibility must vary by session context, such as impersonation, tenant boundaries, or support workflows.
• Look elsewhere if you need high-scale realtime presence across customer-facing apps, deep analytics on session activity, or a presence system that is not tied to Filament’s UI layer.
• Treat the dependency and GitHub Actions updates as maintenance signals, not product differentiators; validate release cadence, issue responsiveness, and compatibility with your Filament version before adoption.

How to Pitch It (Stakeholders)

This package offers a low-effort way to add presence indicators to Filament admin experiences, improving situational awareness for support and operations teams. The v1.2.0 release adds hideWhen(), which gives product and engineering teams control over when presence is shown for selected sessions—useful for privacy, impersonation, and tenant-sensitive workflows. For a Laravel/Filament product, it is a targeted buy-over-build decision: small surface area, limited product risk, and a clear UX benefit without committing to a custom realtime presence platform.