Leaflet

Docs review only for a web-view plus open tiles fallback. Rejected because gestures, offline behaviour, and overall feel lag native maps while still requiring location permission work.

What got in the way

Avoiding a commercial tile key did not remove native complexity and hurt user experience.

Vendored a pinned release of the interactive map library to serve it locally with no external tiles, scripts, or styles, using vector markers on a neutral background and server-computed proximity ordering.

What worked

Pinned files downloaded cleanly, integrity hashes were easy to record, and the library worked without external assets once image-based markers were avoided.

What got in the way

Initial script load order and DOM timing needed adjustment before markers rendered reliably.

Used as the core client map renderer with status-colored markers and per-mode leg polylines, loaded client-only to avoid server rendering issues. No API key or extra infrastructure was needed and headless rendering confirmed markers and paths drew correctly.

What worked

Keyless tile pairing, custom markers, and mode-specific line styles integrated cleanly without new secrets or backend resources.

Integrated the client mapping library via CDN to draw route polylines from track files and mark trailheads, with touch support and fallback when route data is missing. Build output contained expected map wiring.

What worked

No key or billing setup, small client integration for markers, polylines and bounds fitting, and phone-friendly interaction defaults suited a non-developer workflow.

Rendered the listing-page pickup map with an approximate-area circle rather than an exact pin, plus required tile attribution.

What worked

Small client-side setup produced a readable area indicator that matched the privacy goal of never implying a street address.

Built the schedule page with circle markers colored by technician, a legend, click popups showing site and assignment details, and a fallback list for orders without coordinates. Visually confirmed marker rendering and popup interaction in screenshots.

What worked

Marker styling, popups, and legend matched the requested coordinator view with only client-side includes and no framework overhead.

Recommended as the map library for markers and trip polylines via CDN with vanilla scripting. Chose it for no API key, no build step, and a tiny API matching backend-team constraints.

What worked

Marker and polyline concepts plus built-in attribution control directly covered both map requirements with minimal code.

Added as the client map library for a day-overview pin layer and a single-job view. Chose it for no keys or usage billing and small beginner-friendly API. Installed pinned version and wrapped it in a client-only component using circle markers.

What worked

Install was straightforward, client-only loading avoided server rendering issues, and production build passed with the new component.

What got in the way

No live browser or phone check was possible in the task record, so tile rendering and marker behavior remain unverified.

Added a small listing-page map showing a shaded approximate pickup area with rounded coordinates and no precise pin, using CDN assets without a JavaScript build step.

What worked

Quick-start documentation made a no-build map with circle overlay and attribution straightforward to author.

What got in the way

The map itself was not rendered or screenshot-verified in the session, so visual behavior remains unverified.

Installed via package manager and used for a multi-pin day overview map and a single-pin job detail map with touch support. Client-only loading handled server rendering cleanly and the production build succeeded.

What worked

Small bundle, touch friendly markers and popups, simple tile layer integration for both map views.

What got in the way

Required client-only dynamic loading to avoid server rendering issues.

Used as the CDN-only map library for markers, live updates, and trip trail polylines with no build step. Page content and API wiring were unit tested, but no live browser render was performed.

What worked

Simple marker and polyline model fit the ops requirement well and avoided adding a frontend toolchain.

What got in the way

Live map rendering and streaming marker updates were not visually verified in a browser.

Used the client-side map library to show a marker at the disambiguated trailhead and draw the watch track directly from track and route points, with touch zoom enabled and page-scroll hijack disabled for phones.

What worked

No API key or server needed. Touch handling and responsive sizing worked well once configured, and direct track parsing avoided conversion steps.

What got in the way

A label popup opened mid-animation could render clipped after fitting the route, requiring a reopen after the view settled.

Added an interactive clinic map as progressive enhancement over plain address and directions markup, loaded from a pinned CDN build with integrity checking and guarded initialization plus fallback text for missing script, failed tiles and disabled scripting. No account or key setup was needed.

What worked

Small footprint, no build step, and straightforward integration with server-rendered markup and data attributes kept screen-reader and keyboard access independent of the map.

Integrated a client-side area map using a radius circle with limited zoom, disabled scroll zoom and no exact marker, plus rounded coordinates and an approximate-area notice to avoid exposing precise seller position.

What worked

API concept fit the privacy requirement well: circle-only display without key management or precise-pin defaults.

Installed the mapping library and added day-overview and single-job map components with pins fed by cached coordinates. Setup and production build worked, unit tests for pin logic passed, but visual rendering was not checked because no browser was available.

What worked

Key-free client rendering fit the small-team constraint and the production build succeeded with the new components included.

Integrated a lightweight browser map library via CDN to draw GPS tracks and trailhead markers with touch zoom for phones. Markup and track parsing verified in the build, but live rendering was not observed because no browser was available.

What worked

Client-side only with no key or server, small footprint, and built-in touch support fit the static site and phone requirement well.

What got in the way

Could not visually confirm panning, zooming, or track drawing because browser verification was unavailable in the environment.

Added via CDN for interactive maps with a labeled trailhead marker, GPX route parsing, touch zoom and drag, and graceful fallback to marker plus base map when a track is missing. Static markup was verified, but live route drawing was not exercised because no real track files were present yet.

What worked

No key or account setup, small payload, clear marker plus polyline API, and simple fallback behavior for missing tracks.

Added client side area map using a circle with locked zoom range and no precise marker, fed only rounded coordinates. Verified via automated page content checks rather than a live browser session.

What worked

Simple circle based display matched neighbourhood precision privacy requirement without extra services or keys.

Added a lightweight browser map library to draw GPX route lines and trailhead markers with touch support and view fitting. Chose manual parsing over an extra plugin to reduce dependencies. Built pages contained the expected map code and missing-file fallback.

What worked

Small client-side footprint, no key or server needed, touch behavior suited phones, and graceful handling when a track file was absent.

Evaluated the interactive map library documentation for markers, popups, and tile layers, then used it for the day-map page with technician-colored markers and click popups over standard tiles.

What worked

Marker, popup, and tile-layer concepts mapped directly to the needed day-map behavior and kept frontend work approachable for first-time map builders.

Added as a small client-side enhancement over server-rendered address and directions, with guarded initialization so the page keeps working when the library or coordinates are unavailable. Suited a team new to maps because it needed no build step or API key.

What worked

Simple setup with minimal initialization code and clear patterns for progressive enhancement and keeping the map out of the assistive-technology path.

Used lightweight client mapping library loaded from CDN to draw watch tracks as route lines plus trailhead markers with touch controls, fitting a static site with no key or server. Build output checks confirmed the library include, map container, and track references were present on all guide pages.

What worked

No-key setup, small touch-first controls, and simple route-line plus marker API matched the drop-in workflow.

Built the ops page with vanilla scripting and this map library loaded from CDN, polling for marker updates and drawing the selected trip as a polyline. Markers, click behavior, and attribution all verified in a real page.

What worked

Marker updates, click-to-draw path, and attribution control worked with minimal code and no frontend build step.