MapConductorSetup, provider by provider
MapConductor does not replace a map SDK; it lays a shared API over one. The code that draws the map is common, but getting each SDK into your project — the key, the dependency, the initialisation ritual — still follows that vendor's rules. This is that part, written out for every platform and provider pair.
01 · The matrix
The combinations that have a guide today. A dash means no module exists for that provider on that platform.
React Native covers Google Maps, MapLibre, ArcGIS and HERE. It shares the same state objects and components as the Web, so rather than separate pages it is noted inside each React guide.
02 · Choosing a provider
If you are undecided, the quickest route is to get something running on a key-free provider first and swap later. As long as you wrote against the shared API, almost nothing is lost in the swap.
03 · Every guide has the same shape
Each page runs in the same order, so when you move between providers you only need to read what differs.
MapConductor never holds your key
Your key is fed to the map SDK exactly the way that SDK expects — the Android manifest, an iOS initialisation closure, a state object on the Web. MapConductor never relays or stores it. Restricting and revoking keys stays where it always was: in each provider's own console.