MapConductorAPI reference
An index of the public API on all three platforms, one concept per row. Most types share a name across the three languages; how you build them — constructor, factory, hook — and a handful of type names follow each language conventions. The table is arranged so you only have to read the differences.
01 · Packages
Add core plus only the modules you use. For the provider modules (for-*), see Switching providers.
Android publishes a BOM (com.mapconductor:mapconductor-bom) so versions can be pinned in one place. iOS is Swift Package Manager; React is npm.
02 · Core types
03 · Element states
Everything you put on the map follows one shape: build one state object and hand it to the map view. Kotlin and Swift use the constructor; TypeScript uses a factory such as createMarkerState().
Every state object carries id, zIndex, clickable, extra and onClick. Assigning to a property applies just that difference — the map object is never rebuilt.
04 · Components
These are the wrappers that declare a state object as a child of the map view. The names line up across all three: Android uses MapViewScope extension functions, iOS a MapViewContentBuilder result builder, React plain child components.
One marker, or a list
Lines (iOS also has the plural)
Areas, with holes
Metre-radius circles
An image pinned to bounds
A tile layer
A bubble anchored to a marker; InfoBubbleCustom is the low-level form where you draw the frame and tail yourself.
Renders the attribution text
05 · Functions
The spherical and ellipsoidal models expose the same method set; Planar is the straight lat/lng model. →
The same functions the SDK own hit testing and great-circle rendering use. →
Projections and the Earth constants; exposed on Android and React. →
Present on every provider state object. →