On November 9, 2026 Google said Maps Platform can be enabled inside AI Studio (see our summary). Google’s own example is “Build an interactive 3D tour of NYC showcasing iconic landmarks.” These patterns are our own advice for getting a better first draft from a prompt like that.
1. State the goal and the audience
Build a map app for [audience] that helps them [goal]. Start with a single screen: a map centred on [place] and a side list of [things].
A narrow first screen beats a full product description. Add features in later turns.
2. Name the data you want shown
Show these places as markers: [list of 5 to 10 names]. Each marker opens a card with the name, one line of description and a placeholder photo.
Giving the list yourself avoids the model inventing places. Check every place and fact it adds.
3. Describe interactions in plain steps
When I click a marker, centre the map on it and highlight the matching list item. When I click a list item, do the reverse.
4. Ask for a route or tour order
Add a “Start tour” button that visits the markers in a sensible walking order and pauses at each for a short caption.
5. Set limits up front
Keep it to one page, no login, and no data stored. Use clear labels and large tap targets for phones.
Google says usage is free to try within daily quotas and that production needs a paid billing account, so keep the first version small and check quotas before sharing it widely.
6. Fix in small turns
The marker cards overlap on mobile. Keep everything else the same and only fix the card layout.
Saying what to keep stops unrelated changes. The same habit works in sketch-to-app prompts, and the general method is in our prompt workflow. See also the Gemini page.