- How do I install filament-pwa in a Laravel Filament panel?
- Install it with Composer using composer require jeffersongoncalves/filament-pwa, then register the plugin on the panel you want to enable inside your PanelProvider. After that, publish the package config and supply your own icon set. There are no migrations, middleware, or auth changes involved, so most of the setup effort goes into generating and curating icon assets rather than writing code.
- Which Filament versions does filament-pwa support?
- The package is built as a Filament panel plugin, and its release history points to Filament v3-era support, with newer majors potentially only permitted by the Composer constraint rather than explicitly tested. Check the composer.json constraint and the changelog in the repository before committing. If you are evaluating Filament v4, verify it in a staging panel instead of assuming the version constraint means tested compatibility.
- Does filament-pwa register a service worker and cache assets for offline use?
- Despite the name, this package is primarily a head-markup injector: it appends the web app manifest link, theme-color, Apple touch icons, and msapplication tile tags to your Filament panel layout. It does not ship offline caching, push notifications, background sync, or its own install-prompt handling. If you need real offline behavior you must add a service worker yourself, and you should weigh that carefully for an authenticated admin panel where stale or exposed cached HTML is a genuine risk.
- Can I set a different manifest and icon set for each Filament panel or tenant?
- The package is designed around per-panel configuration with enable and disable options, so you can register the plugin on selected panels rather than globally. In multi-tenant or multi-domain deployments, confirm in staging that each panel emits its own manifest and icon URLs, because the worst failure mode is one tenant seeing another tenant's branding. Verify this explicitly before rolling out to every tenant.
- Why are my manifest and icons blocked in production?
- Strict Content-Security-Policy headers on admin panels commonly block manifest and icon fetches, and the failure usually surfaces only as console errors rather than visible breakage. Add the manifest and icon origins to the relevant CSP directives and test against your real production headers. Because the tags are injected into the panel head, a silent CSP block can ship unnoticed.
- Does filament-pwa emit a dark mode theme-color variant?
- A single theme-color tag is straightforward, but matching Filament's dark theme requires a second meta tag using a prefers-color-scheme dark media query. It is unclear from the package documentation whether that variant is emitted by default. Inspect the rendered head in both light and dark mode, and be prepared to publish and adjust the config or views if the dark variant is missing.
- Do the PWA meta tags appear on the Filament login page and error pages?
- The tags are rendered through Filament render hooks, which only fire inside the panel layout. Custom login pages, error pages, and other non-panel routes therefore will not receive the manifest or icon tags. If installability and branding matter on the login screen, you will need to add that markup manually to those views.
- How do I test whether my Filament panel is installable as a PWA?
- Serve the panel over HTTPS, open it in Chrome, and use the Application tab in DevTools to check for a detected manifest, valid icons, and installability warnings. Run a Lighthouse audit to confirm the manifest and icon requirements are met. Because the package does not provide a service worker, expect the audit to flag that gap, and treat install-to-home-screen behavior as the realistic outcome.
- Is filament-pwa safe to depend on in production?
- It is a small, single-maintainer package with low adoption and zero dependents, and it sits at the top of a three-package chain that all share the same author. Recent releases have been dependency bumps rather than feature work, so an upstream breaking change can leave you waiting or forking. Running it is low risk because it only emits static head markup, but plan for the maintenance and version-lag risk.
- Do I need this package, or can I just add the manifest tags myself?
- The package is a convenience wrapper that owns the icon set and configuration surface for you, emitting roughly fifteen lines of static HTML into the panel head. If you already manage icons and head tags, adding the manifest link and theme-color meta tags directly to your panel layout takes minutes and removes a transitive dependency. Choose it when you want the config scaffolding and icon defaults, not because it adds capability you could not write yourself.