We have a blog now

Notes from building MapConductor, starting here.

Notes from wrapping seven map SDKs behind one API.

Why write it down

Building a unified API means running into each provider's quirks over and over. Searching does not find them. If nobody writes them down they are lost, so we are writing them down.

  • SDKs that accept a negative camera tilt, and SDKs that do not
  • Whether tile requests can carry a rewritten header
  • Where a thousand markers start to stutter

There will be code

kotlin
val state = rememberMapLibreMapViewState(
    cameraPosition = MapCameraPosition(GeoPoint(35.68, 139.76), zoom = 14.0),
)

When something here goes stale, we fix it.