Understand map discovery states
Some Customer App experiences define a map surface alongside business discovery. The map, its business list, search results, selected location, and device location are related presentations, not one authoritative state.
:::warning Map and location data is private
Do not copy an address, search text, coordinates, map image, provider response, account context, or business identifier into documentation or diagnostics. A visible marker is not proof of serviceability, current availability, or a safe provider boundary.
:::
Entry and location context
The pinned source registers a map destination and defines a map control from business discovery. Source reachability does not certify that the control is present in every app variant or deployed build.
Business discovery normally depends on an active ordering location. If that location is absent, the map can still have a configured presentation center while the principal business search may remain unstarted. The center is not the customer's location and does not establish delivery coverage.
Keep visible states separate
| Visible state | Safe interpretation |
|---|---|
| Map shell without results | A provider-backed surface has a center; no business result is established. |
| Loading cards or list | The controller remains in a loading presentation; this does not prove that a request started. |
| Empty message | The current result set has no displayed businesses, or an error converged on the same presentation. |
| Business markers | Returned business coordinates produced marker presentations. |
| Selected marker and expanded list | Local selection synchronized two presentations; no business mutation occurred. |
| Panned map with search-area control | A candidate map center differs from the center used for current results. |
| Search or filters | A local query/filter intent can start another business read. |
| Recenter control | The source-defined control is visible and can request a camera recenter; it does not prove a device location exists. |
| User-location display | The native map can display a device location only when its platform and permission state provide one. |
The pinned surface does not provide a distinct universal error presentation. Do not use an empty message to infer that no businesses exist.
Map, list, and city data
The map and nearby-business list use one returned result set, but markers, remote logos, cards, pagination, and map camera changes can settle at different times. A marker count, nearby-store label, or loaded image does not prove that the result is complete or current.
An auxiliary city-data read can be enabled by presentation configuration even when the map does not need the full returned structure. That response requires a separately reviewed, minimal public-data contract. This page does not treat the auxiliary read as necessary, private, or safe merely because it is available.
Search and coordinate boundaries
Typed search, filters, the active ordering location, and a deliberately chosen search-area center can affect a business query. Panning the map can also cross a coordinate-to-address provider boundary in the pinned shared map primitive.
A future accepted implementation must send only the minimum query and coarse location needed for the stated purpose, avoid background or movement-triggered provider work, bind every response to the latest account/project/session/ location/query generation, and discard stale or late responses. It must not place provider keys, session identifiers, precise coordinates, or sensitive search context in logs or public artifacts.
Permission and current-location ownership
The operating system owns the location-permission decision; the app owns the explanation, deliberate request, fallback, and lifecycle cleanup. App consent, OS permission, provider configuration, and a returned coordinate are separate states.
The visible recenter control can use the most recent device coordinate cached by the map. If none exists, its source-defined fallback is the supplied active or configured presentation center—not the center produced by panning. The control does not by itself save an address, select a business, or prove that a displayed position is precise or current. Source inspection does not certify whether or how either platform requests location permission for this map surface.
Marker and business handoff
Selecting a marker can synchronize the selected marker with a nearby-business card. A separate business action can hand off to the business page. Marker selection, callout visibility, a remote logo, or navigation does not establish business authorization, availability, menu freshness, cart readiness, or successful ordering.
Remote media and provider boundary
The map provider can receive map viewport and device/network context. Marker logos and supporting business images can load from separate remote media origins. A rendered tile, marker, or image does not establish provider consent, content trust, freshness, or ownership.
An accepted provider contract must use approved destinations, minimize query and coordinate precision, keep provider credentials out of client-visible records where possible, redact telemetry, prevent repeated passive requests, and clear provider callbacks and cached identity on account, project, session, permission, or consent change.
Accessibility and safe troubleshooting
Map-only discovery is not an accessible alternative by itself. The business list, search, filters, empty/error feedback, current-location control, selected marker, sheet, Back control, and business handoff require independent iOS and Android validation for names, roles, selected/busy state, focus order, live announcements, large text, keyboard handling, reduced motion, and platform Back behavior.
For safe troubleshooting:
- distinguish no location, loading, empty/error, partial markers, and stale results without sharing the location or search text;
- use the business list as the non-map reference when it is available;
- do not repeatedly pan, search an area, request current location, or select a marker to diagnose an unknown result;
- confirm only whether a permission or manual-location alternative is visible, not the underlying address or coordinates;
- re-certify after changes to search, location precision, map/native setup, permissions, city responses, marker media, provider identity, navigation, session cleanup, or accessibility primitives.
This page is a source-safe state reference. It does not certify a deployed map, provider, current location, delivery area, business result, or navigation outcome.
Related guides: Browse businesses · Search and filter businesses · Choose a location · Location permission and unavailable-location states · Business page overview