Customer map interfaces, not a Retick map service

Review the relationship between map pins and search results

Use fictitious places to review how your map, list, and area-refresh controls describe the same selected result.

  • ✓The highlighted pin loses its card
  • ✓Movement looks like a completed search
  • ✓Dense pins obscure selection

A bounded visual review of spatial result context

Pin-to-card evidence

Keep a recognizable sample location visible on both sides of the interface.

Bounds behavior stated

Record whether moving the map applies results immediately or requires confirmation.

Selection after refresh

Agree how to retain or clear a selected location when the result area changes.

Review a selection across two surfaces

A customer explores sample pickup locations in your application's map search. Selecting a result card highlights a pin, but moving the map leaves that highlight attached to a different-looking list state. Review how the map and list communicate the same selection. Retick helps inspect captured map interfaces; it does not supply mapping, geocoding, location search, or an integration with your map provider.

Use fictitious locations and fixed conditions

Prepare authorized synthetic locations that do not reveal homes, customer movements, or device location. Record the initial bounds, list selection, highlighted pin, map movement, and any search-this-area action. Note zoom, viewport, active filters, build, and whether bounds changes automatically refresh results. Use supported browser capture or upload authorized media. Keep location permissions and personal map history outside the captured view.

Name the cross-surface inconsistency

An example issue is Selected result card loses its matching pin after area refresh. Annotate the sample place name in both surfaces and inspect AI candidate findings for mistaken identities. Edit unsupported statements that coordinates are wrong when the evidence only shows inconsistent selection. Separate a missing selection indicator from a result-refresh question. Reject invented distances or geographic explanations not supplied by the application team.

Example acceptance criteria

For the seeded locations, selecting a card should identify its corresponding pin using the agreed visible treatment. After the approved bounds refresh, the interface should either retain a valid selection or clearly clear it when that location is absent. Search-this-area feedback should distinguish pending movement from applied results. Check card destinations and selection changes directly rather than assuming proximity on a screenshot establishes the correct relationship.

Revisit movement and dense result states

Keep selected, moved, and refreshed media in a review cycle. Follow up with overlapping sample pins, a narrow split view, clearing selection, and returning from a location detail screen. Export reviewed findings as files or selected individual-media Trello cards. Retick does not verify coordinate accuracy, map licensing, location permissions, or spatial query correctness. Those require separate application checks; the visual report should explain the observed map-list disagreement without claiming a geographic or provider-level diagnosis.

Review the map and list as one selection journey

Capture controlled locations and define what should happen after the search area changes.