Explain the system path of a Google Maps search, from keystroke to results on the map

Walk through what happens when someone types a query into the Google Maps search bar, from the first keystroke until results appear on the map. Name the main systems involved and explain what each one does along the way. ```hint Two halves Split the flow in two: what happens while the person is still typing, and what happens once they pick a suggestion or press search. Then ask what Maps knows about the request besides the text itself. ``` ### Clarifying Questions - Should I describe the mobile app or the web version, and should I assume the user is online or has offline maps downloaded? - What kind of query: a street address, a named place, a category such as "coffee near me", or a request for directions? - How deep should I go: the end-to-end flow at the component level, or one component, such as ranking, in detail? - Is the user signed in with location access granted, so their location and history can shape the results? ### What a Strong Answer Covers - The client side: capturing keystrokes, limiting how often requests are sent, and attaching the device location and the visible map area as context. - Autocomplete: how suggestions are produced and ranked on every keystroke fast enough to keep up with typing. - Query understanding and retrieval: working out what the user means, turning addresses into coordinates, and finding candidate places in an index. - How candidates are ranked and how the response is shown as a list, pins and a map view. - Latency, caching, failure handling, privacy, and how search quality is measured. ### Follow-up Questions - The query is "pizza" and the user is zoomed out over an entire country. What should Maps do differently from when they are zoomed into one neighborhood? - Suggestions feel slow on weak mobile networks. Where in the flow would you look, and what would you change? - How would you tell whether a change to search ranking made Maps better for users?