Google Maps
Google Maps can provide static map images, address lookup, and routes. Keyless deep links can hand a user to the Google Maps app immediately. Google REST APIs are different: their key is a server secret, so a released app must call them through a backend you deploy.
What you get by connecting it
Connect Google Maps inside a project and the agent gains these capabilities for that project:
- Keyless turn-by-turn handoff. The app can open Google Maps with a destination or route without carrying an API key.
- A preview-safe REST setup. For static images, geocoding, or Routes, the agent renders an honest placeholder and generates a narrow relay contract with
SETUP REQUIREDdeployment steps. - Server-relayed map APIs after setup. Once you deploy that relay and give it its own restricted runtime key, the app can request static maps, geocoding, and routes without exposing the key.
- Turn-by-turn handoff. For full navigation, the app hands off to the Google Maps app on the device via a deep link, rather than rebuilding navigation inside your app.
The saved connector key validates access only; Appsanic never copies it into generated code or a deployment. For more on how these pieces fit together, see Maps and location.
Connecting it
Google Maps connects with one API key (a long string beginning with AIza).
- Open the Google Cloud Console and pick or create a project.
- Enable the Maps SDKs your app needs (the static map, geocoding, and routes services).
- Go to APIs & Services then Credentials and create a dedicated validation key.
- Restrict it to only the required APIs, add a small quota and billing alerts, and paste it only into the encrypted connector form. Native bundle/package restrictions do not protect plain REST calls.
- In the Appsanic project build, select Connectors → Google Maps and enter the key. An in-chat connect card opens the same form.
- For the released relay, create a different server key restricted to the relay's fixed outbound IP addresses and required APIs. Put that key directly in the relay's secret manager.
Once saved, the value is not returned to the browser or model. Use Test now to re-check it and Disconnect to remove the encrypted copy from the project. The test is a bounded geocoding probe; it does not prove every API or the deployed relay works.
Keys and security
Treat a Google Maps REST key as a server secret. It is encrypted in connector storage, omitted from browser status data and model prompts, and never exported to the generated app. Do not paste it into chat, client code, or a client-side environment variable.
REST features require a separately deployed relay with authentication, rate limits, request validation, quotas, and a separately provisioned key. Appsanic can generate that contract and setup guide, but it does not deploy the relay or transfer the saved connector key.
Useful links
- Google Maps Platform documentation: https://developers.google.com/maps/documentation
- Appsanic guide: Maps and location
Next
Read Maps and location for the full picture of building map and location features into your app.