Filament Language Switcher Laravel Package

Product Decisions This Supports

• Localization scope for admin surfaces. A Filament language switcher directly supports the decision of whether to ship a multi-language admin panel — it converts "should our back office support N locales?" from a custom build task into a configuration task, typically via a panel render hook and a locale session/column.
• Build vs. buy on a small, well-bounded UI concern. The switcher itself is low-differentiation work: a dropdown, locale persistence, and Filament integration. Adopting a package here frees engineering capacity for the parts that actually differentiate the product (translation workflow, content model, review/approval for translated content).
• Roadmap sequencing for i18n. Lets you commit to a phased rollout — e.g. admin UI locale switching first, then translated content models (often via spatie/laravel-translatable), then locale-aware routing on the public site — without the first phase blocking on the later ones.
• Use cases unlocked: regional back-office teams operating in their own language, support staff reading localized labels and enum options, internal QA verifying translations in place rather than in the database, and demos/sales enablement in a prospect's language.
• Version 1.0.1 assessment: the release carries no substantive notes — only a changelog diff link between 1.0.0 and 1.0.1. Treat it as a patch-level maintenance release: no new capability to plan around, and no indication of breaking changes (a patch bump from 1.0.0 is a strong signal of backward compatibility). It does not change any of the above decisions, but it is a mild positive signal that the package is being maintained rather than abandoned.

When to Consider This Package

Adopt when:

• You are on Filament v3+ with a Laravel app that already has, or is about to have, more than one admin locale.
• You want locale switching to be an admin-panel concern rather than something you hand-roll into every panel, resource, and custom page.
• Your team is comfortable with a single-maintainer, small-scope community package and can absorb the risk of pinning to a specific tag.
• Your persistence model is simple — session-based or a per-user locale column. If you need per-tenant, per-role, or per-resource locale defaults, verify the package's extension points before committing.

Look elsewhere or build in-house when:

• You need locale switching across the public site as well — that is a routing/middleware concern (mcamara/laravel-localization and similar), not a panel widget; you would end up integrating two solutions.
• You require enterprise support, an SLA, or a security review trail. There is no evidence of that here.
• Your Filament version is outside the package's supported range, or you are on a major-version boundary — patch releases like 1.0.1 tell you nothing about compatibility with the next Filament major.
• The switcher would need to drive complex translation workflows (translation memory, vendor handoff, per-field approval). A UI switcher is a display concern; it does not solve content translation management.
• Exit cost matters more than build cost to you. The integration surface is small, so the true build cost is likely a day or two — price that against the ongoing cost of tracking an external dependency.

Verification before adoption: confirm the locale persistence mechanism, whether it respects Filament's panel-level ->locales() configuration, whether middleware is registered automatically, and the exact Filament/Laravel version constraints in composer.json. The 1.0.1 notes do not disclose any of this.

How to Pitch It (Stakeholders)

To executives (one paragraph): This is a small, free, open-source add-on for our admin panel that lets each back-office user work in their own language. It replaces a modest amount of custom UI work — roughly a day or two of engineering — with a configuration step, and it lets us sequence our localization roadmap so the admin experience ships first without waiting on translated content models. It is maintained by a single developer on a 1.0.x line, so the risk is low but non-zero; the integration is shallow enough that removing it later would be cheap. The latest release, 1.0.1, is a maintenance patch with no functional changes and no breaking changes.

To engineering: Scope is narrow — a locale dropdown for Filament panels plus persistence. Expect a render-hook or panel-plugin registration and a session or user-column store. Do a 30-minute spike to confirm Filament version constraints, how locale resolution interacts with existing middleware, and whether it respects ->locales() on the panel. If the spike shows friction, the fallback build is small; do not let this become a multi-day integration. Pin the version, and note that 1.0.1 shipped with no release notes beyond a diff link — so read the changelog commit-by-commit before bumping from 1.0.0, and add it to our dependency-review list rather than assuming a documented patch.