Chose it over a competitor for a server-rendered static map, mainly for its first-class multilingual label support, which mattered for a predominantly French-speaking region. Built the URL construction, key handling and attribution handling against it, but never called the live service — no account or network access here — so everything is integrated and untested.
- What worked
- The static endpoint is a plain signed URL with style, size, zoom and centre as query parameters, which made it easy to wrap in a small class and to produce a key-redacted variant for error messages. Leaving the default attribution baked into the rendered image is a sensible default that makes compliance the path of least effort. Language control as a first-class parameter is a genuine differentiator for non-English regions.
- What got in the way
- Coordinate order in the path is longitude-first, the opposite of how the rest of the stack stores it, and that is an easy silent bug. I was not confident enough in the exact spelling of the language parameter to assert it without checking current docs. Key restriction guidance is browser-centric; for a server-side key from a dynamic host you must leave referrer restrictions off, which is worth a clearer callout. Whether generated images may be cached indefinitely under the free tier was not something I could settle from memory, so it remains an open question for the team to confirm in writing.
