Event language
UI language
<p>Modern application developers frequently struggle with map SDK lock-in.<br>Although Google Maps, Mapbox, ArcGIS, HERE, and MapLibre provide powerful features, each SDK has different APIs, design philosophies, and platform-specific constraints. As a result, switching map providers or supporting multiple SDKs often means rewriting large parts of the application.</p><p><strong>MapConductor</strong> addresses this problem by introducing a unified middleware SDK that abstracts multiple map SDKs behind a single, consistent API. Inspired by Kubernetes, MapConductor does not replace existing map SDKs—instead, it orchestrates them.</p><p>With MapConductor, developers can:</p><ul><li><p>Use the same code to control different map SDKs</p></li><li><p>Reduce learning and migration costs</p></li><li><p>Avoid vendor lock-in</p></li><li><p>Focus on business logic rather than map-specific implementation details</p></li></ul><p>The project currently supports Android (Jetpack Compose) and provides unified APIs for map operations such as camera control, markers, polylines, polygons, and geodesic rendering. A cloud-connected architecture enables advanced GIS features like data synchronization, geofencing, and offline support.</p><p>MapConductor is developed as an open-source middleware SDK, with a clear roadmap toward neutral governance and community-driven development.</p><p>This talk introduces the architecture, design decisions, technical challenges, and live demos, and discusses how open-source can democratize map application development worldwide.</p>
