Filament Ui Switcher Laravel Package

Product Decisions This Supports

• Enhancing User Experience (UX) for Admin Panels: Justifies investment in customizable UI themes for internal tools, improving developer and end-user satisfaction by reducing friction in navigation and readability.
• Brand Consistency Across Products: Enables alignment of admin panel aesthetics with company branding (e.g., custom colors/self-hosted brand fonts) without requiring custom development or third-party font CDNs.
• Roadmap for "Dark Mode" and Accessibility: Supports future-proofing for compliance (WCAG) and user preference trends (e.g., dark mode, font scaling) with minimal technical debt.
• Phased / Scoped Rollout Strategy: New ability to disable and configure individual switcher sections (colors, fonts, layout) means we can ship a narrow slice of customization first—e.g., brand fonts only—and expand per role, tenant, or product line without a second integration.
• Build vs. Buy Decision: Avoids reinventing a UI customization wheel for Filament-based admin panels, leveraging an MIT-licensed, actively maintained package that now closes the "Google Fonts only" gap.
• Use Cases:
  • Internal tools (e.g., SaaS dashboards, CMS backends).
  • Multi-tenant applications where UI preferences differ by role/team.
  • Brand-sensitive customer-facing admin portals requiring licensed/self-hosted fonts.
  • Developer tools requiring rapid iteration on UI themes.

When to Consider This Package

• Adopt When:

  • Your product uses Filament 4.1+ or 5.x as the admin panel framework.
  • You need low-code UI customization (colors, fonts, layouts) without deep frontend work.
  • You must serve brand or licensed fonts locally rather than loading from Google Fonts (compliance, privacy/GDPR, offline/air-gapped, or performance reasons).
  • You want granular control over what end users can change — sections can be individually disabled or configured, so scope of customization is a product decision, not a plugin constraint.
  • Your team lacks bandwidth for custom theme systems but wants user-controlled preferences.
  • You prioritize session-based or user-specific persistence of UI settings.
  • Your stakeholders value consistency (e.g., matching brand guidelines) or accessibility (e.g., font scaling).

• Look Elsewhere If:

  • You require highly bespoke UI components beyond Filament’s supported layouts (e.g., custom navigation bars).
  • Your stack doesn’t include Filament/Laravel/Livewire (e.g., React/Vue-based admin panels).
  • You need enterprise-grade theming (e.g., dynamic CSS variables, SASS variables, or plugin ecosystems like Tailwind).
  • Your team prefers database-agnostic storage (this package defaults to session/database).
  • You’re targeting public-facing apps where UI customization might introduce security/complexity risks.
  • You need a fully managed font pipeline (subsetting, variable-font axes, per-locale font fallback chains) — local font support covers hosting and registration, not a font asset build system.

How to Pitch It (Stakeholders)

For Executives: *"This package lets us ship a self-service UI customization tool for our admin panels in days—not months. For $0 cost, we can:

• Reduce support tickets by letting users tweak fonts, colors, and layouts to their preference.
• Align internal tools with our brand without custom dev work—and now with our own licensed fonts, served from our infrastructure (no Google Fonts dependency, no privacy/compliance exposure).
• Future-proof for accessibility with adjustable font sizes and dark mode, meeting WCAG standards with minimal effort.
• Control the blast radius: the latest release lets us turn individual customization sections on or off, so we can launch a tightly scoped version and widen it based on measured adoption. It’s a no-code lever for UX improvements, paid for by open-source contributors, not our team."*

For Engineering: *"This is a drop-in plugin for Filament that handles:

• Theme toggles (colors, fonts, layouts) via a modal UI.
• Local font support — register self-hosted font files instead of relying on Google Fonts, plus fluent methods to disable and configure individual sections (v1.1.2).
• Storage flexibility: Session-based (default) or database-backed per-user preferences.
• Livewire integration: Changes apply instantly without page reloads. Tradeoffs:
• Limited to Filament’s supported layouts (no custom nav bars).
• Fonts are supported as registered local files or Google Fonts; there’s still no font build pipeline (subsetting, variable axes, per-locale fallbacks).
• Section-level disabling is configuration, not per-role authorization—we’d wire policies ourselves if we need role-scoped customization. Recommendation: Pilot in our [Product] admin panel to validate UX lift before wider adoption. Start with a scoped config (brand fonts + color only) and enable layout switching after measuring adoption. Estimated dev time: <1 day to integrate and test; ~1 additional day to register and verify self-hosted brand fonts."*