Nova Notifications Laravel Package

Product Decisions This Supports

• Whether an admin notification inbox is worth building at all. This package proves the surface area is small: a bell dropdown, a read/unread list, and mark-as-read against Laravel's existing notifications table. That is a scoping input for the "Q-now / Q-later / never" call on internal tooling — if the answer looks like days of work rather than a roadmap epic, the decision changes.
• Build vs. buy vs. borrow. With 64 stars, zero dependents, and no release since March 2022, this is a borrow-the-pattern candidate, not an adopt-the-dependency candidate. Use it to price the build option (roughly 1–2 days in-house) before committing engineering time or a vendor approval cycle.
• Ops and support workflow design. Useful when scoping how staff see transactional events — order failures, approval requests, system alerts — and whether those land in email/Slack only or also in a persistent in-app inbox with acknowledgement (read/unread) semantics.
• Prioritization against Nova's native notifications. Nova's built-in bell is ephemeral toast messaging; this exposes persistent, per-user notifications. That distinction is a product decision (do users need durable history and "unread" state?) rather than a purely technical one.
• Vendor risk register. A concrete entry for evaluating small Laravel-ecosystem packages: single maintainer, stale releases, and coupling to a paid, private host framework (laravel/nova) that CI cannot resolve without license credentials.

When to Consider This Package

Consider it when:

• You are already standardized on Laravel Nova and want to validate an admin notification inbox cheaply, before committing to a maintained package or an owned build.
• You want a short-lived spike or prototype to test whether ops staff actually use an in-app inbox — a half-day install against a licensed dev environment answers that.
• You want a reference implementation for how a Nova tool wraps notification data; an engineer can read it and write the real version in-house quickly.
• Your Nova major matches the package's 2022-era target, and you accept that any fix means forking.

Look elsewhere when:

• You run recent Laravel or Nova versions. Nova 5's Inertia/Vue 3 front-end shift is a plausible breaking axis; no upstream activity means you patch it yourself. Budget 1–2 engineer-days per Nova major upgrade, permanently.
• You need production-grade assurance — no vendor, no SLA, no community backstop. Prefer an owned thin Nova tool or a maintained alternative.
• You are not on Nova. The underlying Laravel notification system is what you want; the package is meaningless outside the admin panel.
• You need notification logic, not display — digesting, dedupe, escalation, per-role fan-out, or real-time delivery. This is a display layer; routing logic belongs in your app regardless.
• You need multi-tenant isolation across per-tenant database connections, or the admin panel is being migrated off Nova entirely.

Non-negotiable gate before any pilot: confirm the tool's routes sit inside Nova's middleware group and scope queries to the current Nova user. A mis-scoped endpoint is a cross-user notification leak — treat it as a release blocker, not a nice-to-have.

How to Pitch It (Stakeholders)

Executive summary: This is a small Laravel Nova add-on that displays persistent user notifications inside our admin panel. The recommendation is not to adopt it as infrastructure. The signals are weak — 64 stars, zero dependents, no release in roughly three years, single maintainer — and it is coupled to Nova, a commercial framework we upgrade on our own cadence. Its real value is as a cheap reference: it shows that an admin notification inbox is a days-sized build, not a quarter-sized one. If the capability proves valuable in a short pilot, we build a thin owned version on Laravel's native notification system, eliminating the maintenance risk at negligible incremental cost. Approval requested is for a timeboxed spike, not a dependency.

Engineering summary: mirovit/nova-notifications is a thin Nova tool — a Tool subclass, service provider, Vue component, and controller reading Laravel's standard notifications table for the authenticated Nova user. Architecturally additive and non-invasive, but treat it as a fork candidate, not a drop-in. Constraints: last release March 2022; Nova 5 and PHP 8.3/8.4 drift are likely breaking; laravel/nova is a private Composer package, so CI needs license credentials or a mocked user resolver. The second gate is a payload contract — existing notification classes store free-form data, so budget real work standardizing title/body/level/url for anything that should render. Sequence: half-day spike, security review of middleware and per-user scoping, payload contract, then decide fork vs. ~1-day rebuild. Also confirm the list endpoint paginates and that a pruning job exists — an unbounded notifications table polled by every admin is a slow-rolling query-load problem, not a package bug. Recommend the rebuild if Nova 5 remediation exceeds a day; the buy-vs-build line is genuinely thin here, and owned code with no bus factor is the better outcome.