Decisions are grounded in how people use the product and what the map allows, then expressed in components, specs, and documentation so the same standards hold across teams, partners, and releases.
Map & 3D content
Vision to product for B2B-embedded 3D: benchmarks, a repeatable visual language, and pipelines that scale across cities without one-off heroics.
A reusable 3D roadside library and fragment-based demo architecture: regional research, hundreds of models, and filtering that matches real road data.
Tooling & operations
From Drive folders to one system: upload, QA gates, staging vs production, and handoff engineers can rely on when volume passes thousands of models.
Internal tools and glue so demo teams scale: style checks, geo helpers, Building Box, and automation where Map Design was the bottleneck.
Demos & visual systems
HSV-based color tied to logical model parts: landmarks stay flexible like the rest of the map without breaking materials or team mental models.
High-visibility styles and deliverables: exploratory renderer work (e.g. Tron), pedestrian automation for automotive demos, and keyframe tooling for CES-style flythroughs.
Landmark and procedural color, regional palettes, and fragment-based demo architecture are moving with the current map roadmap. I am helping define how that stays expressive and controlled as the platform evolves.
Evgeny Tabolich
