Work
Geo Architecture Center
A public catalog that turns repeated enterprise questions into reusable system patterns for Google Maps Platform.
The goal
API reference docs answer "what does this endpoint do?" They don't answer "how do I build a fleet tracker, a store locator, or a logistics stack that scales?" Enterprise evaluations live and die on those system-level questions, and so does product growth when the same architecture gap blocks many teams at once.
What shipped
I started the Geo Architecture Center and wrote several of its guides as principal author. The team publishes end-to-end system patterns for Google Maps Platform: architecture diagrams, cost considerations, and reference implementations grounded in repeated enterprise questions.
What I learned
One precise solution architecture can answer a repeated question once, then help many teams move faster. Structured, opinionated system designs also give AI agents better context than an API reference alone.