Nova Google Maps Laravel Package

Product Decisions This Supports

• Admin UX for address & location capture. This is a Nova field, so its product value is confined to internal/admin surfaces: store locators, delivery addresses, property listings, event venues, customer site records. It buys a searchable place autocomplete plus a map pin in an afternoon instead of a sprint.
• Data quality on address input. Constraining operators to select a real place (rather than free-text) reduces bad addresses, failed geocoding downstream, and manual cleanup — the kind of quiet operational win that shows up in support tickets, not demos.
• Build vs. buy at the component level. This is a ~1–2 day build. The "buy" is cheap; the question is whether the dependency is durable. That calculus, not the feature itself, is the actual decision.
• Roadmap placement: non-differentiating. Treat as internal tooling hygiene, not a product bet. Do not put it on a customer-facing critical path.
• Fork/replace planning. Given a 2020 last release and reliance on a discontinued third-party geocoder, this is a candidate for a "replace or fork" line item rather than a new adoption.

When to Consider This Package

Consider it when all of these hold:

• You are already running Laravel Nova and need an address/map field this quarter.
• The consumer is internal staff, not end users.
• You accept forking or patching it — 15 stars and a 2020-05-04 release means effectively no upstream maintenance.
• You have verified the Algolia Places dependency still works for you. Algolia Places was sunset (announced around 2021, wound down in 2022); if your keys no longer authenticate, the autocomplete is dead and the package is a map widget with a broken search box — plan to swap the geocoder for Google Places, Mapbox, or Photon.

Look elsewhere when:

• You are building new admin tooling — a hand-rolled Nova field against Google Places or Mapbox is comparable effort and carries a live dependency.
• The map is customer-facing, subject to Google Maps terms/branding/attribution requirements, or needs SLA-backed uptime.
• You need offline/self-hosted geocoding, bulk geocoding, routing, or international address formats beyond what a Places autocomplete returns.
• You are not on Nova (the package is inert outside it), or your team has no appetite for maintaining a vendored fork.

How to Pitch It (Stakeholders)

To executives: A small convenience component for our internal admin panel — it saves roughly a day or two of engineering, and it is not a competitive differentiator. The upside is modest and the maintenance risk is real, so I would not fund it as an initiative. If we already have it in place, keep it running and schedule a replacement the next time we touch that admin surface.

To engineering: It's a Nova field wrapping Algolia Places for autocomplete with a Google Maps pin. Two concerns: last release was May 2020 and the repo has ~15 stars, so we own it; and Algolia Places has been discontinued, so the autocomplete almost certainly needs re-pointing at another provider. Recommendation: adopt only as a vendored fork with the geocoder swapped, budgeted at 1–3 days including tests — or skip it and build the equivalent field directly against Google Places, which is the same order of effort and leaves us with something we can support.