Filament Hover Sidebar Laravel Package

Product Decisions This Supports

• Tablet and touch admin usage. v0.1.3 fixes a real adoption blocker: earlier releases disabled the hover rail entirely on devices reporting hover: none / pointer: coarse (notably iPads in landscape). If your admin users work from tablets, this release is the first version worth piloting.
• Feature vs. polish trade-off. A collapsing icon rail is a workspace-density feature, not a core workflow. This package lets you test whether reclaiming sidebar width improves admin task speed before investing in custom navigation work.
• Build vs. buy for Filament admin panels. The package is a narrow CSS/JS enhancement around Filament’s sidebar. Buying/adopting is reasonable for internal tools; custom-building is only justified if you need bespoke navigation behavior, accessibility guarantees, or deep integration with your own layout system.
• UX validation of touch interaction. The new touch behavior deliberately makes the first press on a collapsed rail expand it, and the second press follow the link. That is a product decision worth testing with real users — it prevents accidental navigation but adds a tap. Instrument nav flows if you roll this out.
• Platform support commitments. Because the fix gates CSS on min-width: 1024px rather than hover capability, you can now support a consistent “desktop-style rail” across mouse, touch, and pen at tablet-landscape widths — useful if your support matrix promises iPad compatibility.

When to Consider This Package

Consider it when:

• You run a Filament-based admin panel and want to reduce sidebar width without losing navigation.
• A meaningful share of users are on tablets or hybrid devices, and you are willing to require v0.1.3+ specifically.
• You want a low-effort UX experiment — the package is a UI enhancement, not a data-model or security dependency.
• You can accept pre-1.0 maturity: v0.1.x implies possible breaking changes, limited long-term API guarantees, and the need to pin versions and smoke-test upgrades.
• You have a way to test touch behavior on real devices, especially the press-to-expand interaction and document-level pointer handling.

Look elsewhere or build custom when:

• Your admin is used primarily on phones or narrow viewports — the rail is gated to min-width: 1024px and does not address small-screen navigation.
• You need strict accessibility certification or fully keyboard-first navigation guarantees; validate the capture-phase click handling and focus behavior against your standards first.
• You require a stable, 1.0+ dependency with a broad maintainer base.
• You are not on Filament, or you have heavily customized the sidebar already — integration risk outweighs the benefit.
• You need navigation behavior that differs from the package’s opinionated touch model (first tap expands, second tap navigates).

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost admin UX improvement that makes our Filament admin panel more usable on tablets. The latest release fixes a bug that previously broke the sidebar rail on touch devices, so it is now viable for iPad-using staff. The main caveat is maturity: it is an early-stage package, so we should pilot it with a small group, pin the version, and avoid treating it as business-critical infrastructure.

For engineering: Adopt v0.1.3 or later, not earlier. It is a CSS/JS-only enhancement: the rail works at min-width: 1024px, uses event.pointerType to distinguish mouse hover from touch/pen press, and handles touch collapse on outside pointerdown or navigation. Note the capture-phase click listener that makes the first press expand a collapsed rail — verify it does not conflict with Alpine navigate or custom sidebar click handlers. Pin the dependency, test on iPad landscape, and confirm keyboard activation remains unaffected.