public interface MapProvider

The service-provider interface a native map backend implements so the core NativeMap component can drive it without knowing which provider (Apple MapKit, Google Maps, Bing, Huawei, …) is in use.

This is a plain interface, deliberately not a com.codename1.system.NativeInterface: core neither ships nor references any concrete implementation. When the developer selects a provider with the maps.provider build hint, the build pushes a provider implementation (carrying the platform-native methods) into the com.codename1.maps package of the app and weaves in a call to MapProviderRegistry.register(MapProvider). Absent that injection the registry stays empty and NativeMap falls back to the pure-vector MapView.

Every method is keyed by a mapId so a single provider implementation can serve multiple NativeMap instances. Coordinate conversion uses a stateful “calculate then read” idiom (calcScreenPosition then getScreenX / getScreenY) to avoid returning multiple values across the native boundary. Native code reports user interaction back through the static callbacks on NativeMap (fireTap, fireLongPress, fireMarkerClick, fireCameraChange, fireMapReady).