Filament Map Picker Laravel Package

Technical Evaluation

• Architecture fit: nersus15/filament-map-picker is a Filament form-field plugin for map-based coordinate selection. It fits as a presentation-layer extension to Laravel/Filament admin panels and does not alter application domain architecture. Suitable for admin CRUD forms that need lat/lng capture, especially where a map picker improves data quality over raw numeric inputs.
• Integration feasibility: Low-to-moderate. Integration is typically composer require, plugin/service-provider registration, optional asset publishing, and adding the field to a Filament form schema. No server-side geospatial services are required by the package itself; map rendering and live-location behavior are client-side.
• Technical risk: Main risks are browser geolocation permissions, third-party map tile/provider dependency, client-side JavaScript fragility, coordinate-system/precision assumptions, and single-maintainer project risk. Release 1.8.3 is a patch-level behavioral fix: live location no longer overrides stored coordinates when editing an existing record. That reduces the risk of accidental coordinate corruption during edits, but it also changes edit-form behavior, so create and edit flows should be explicitly tested.
• Key questions: Which Filament major versions are supported? Which map provider/tile source is used, and are API keys or quotas required? Is live location configurable or always enabled on create? How are coordinates validated and persisted (decimal precision, SRID, nullability)? Does the field respect CSP/iframe restrictions? Is there automated test coverage for create/edit behavior? What is the maintainer bus factor and release cadence?

Integration Approach

• Stack fit: Best fit is Laravel 10/11 with Filament 3.x and Livewire/Alpine.js-based admin panels. The package is not a general Laravel geospatial library; it is specifically a Filament UI component. Confirm version constraints against the host application before adoption.
• Migration path: No database migration is required by the package itself, but the target model needs latitude/longitude storage if not already present. Use composer update within the existing major version. Treat 1.8.3 as a safe patch candidate, but verify the edit-form behavior change in a non-production environment first.
• Compatibility: Validate composer.json constraints for php, filament/filament, livewire/livewire, and any frontend build tooling. Check whether published assets are compatible with the application’s Vite/asset pipeline and whether the map provider works under the organization’s CSP and network policies.
• Sequencing: 1) Spike the package in a non-production branch with one model and one Filament resource. 2) Test create flow, edit flow, geolocation allow/deny/timeout, and coordinate persistence. 3) Confirm map provider access and CSP requirements. 4) Add to remaining resources only after edit-mode behavior is verified. 5) Pin the version and monitor upstream releases.

Operational Impact

• Maintenance: Low code footprint, but the package is a third-party dependency with a single visible maintainer. Pin versions, review changelogs, and avoid relying on it for business-critical geospatial workflows without an internal fallback for manual coordinate entry.
• Support: Community-supported via GitHub; no commercial SLA. Internal ownership should be assigned for upgrade testing, especially around Filament major-version changes and browser geolocation API behavior.
• Scaling: Negligible server-side scaling impact because map rendering and live location are client-side. Scaling risk is primarily external map tile/provider quotas and browser performance on low-end mobile devices.
• Failure modes: Geolocation permission denial or timeout; map tile provider outage or quota exhaustion; CSP blocking; coordinate precision loss; edit forms overwriting stored coordinates (addressed in 1.8.3 but should be regression-tested); inconsistent mobile browser behavior.
• Ramp-up: Low for developers already familiar with Filament form schemas. Non-technical administrators need brief guidance on browser location permissions and the difference between “use my current location” and manually selected/stored coordinates.