Move beta-era bridges to a release-specific Mappls wrapper while testing the Android and iOS implementations as separate products.
Repository naming identifies the Mappls wrapper candidate; exact supported React Native, Android, iOS, rendering, and API-kit versions remain release-specific and must be approved.
Legacy sources are fully covered. Candidate links expose the closest public evidence and its maturity; they do not silently upgrade it to an entitlement or support declaration.
mapmyindia-map-react-native-betamapmyindia-restapi-react-native-betamappls-react-native-sdkResolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.
Beta props, commands, event payloads, and imperative refs may be spread through the app.
Normalize camera, features, commands, readiness, errors, and cleanup in application-owned types.
Component contract tests plus device screenshots and interaction traces.
Old repository, manifest, pod, or project steps can remain in generated projects.
Apply only the confirmed wrapper's Android and iOS setup and remove superseded native entries.
Resolved dependency graphs and built-binary inspection from clean clones.
Bridge traffic and rerenders can hide platform-specific bottlenecks.
Bound event rates and move large/high-frequency data to native or tiled paths.
Startup, pan/zoom, marker/layer load, memory, battery, and background measurements.
Do not advance on calendar alone. Each stage creates evidence that makes the next one safe and reversible.
Inventory every React Native map or REST bridge, package, host, credential class, callback, and owner before changing production.
Resolve the exact entitled package or endpoint with Mappls and verify its supported toolchain, region, quotas, authentication, and lifecycle.
Move React Native map or REST bridge calls behind a narrow application-owned interface without changing product behavior.
Replay approved fixtures and shadow eligible reads while preventing duplicate writes or user-visible duplicate commands.
Release to internal users and bounded cohorts with health gates, ownership, automatic stop conditions, and immutable version evidence.
Remove legacy credentials and dependencies only after rollback and audit retention obligations expire.
These examples deliberately model the seam and verification pattern—not unconfirmed package symbols. Implement the adapters only after the exact target contract is issued.
export type Camera = { center: [number, number]; zoom: number };
export type MapEvent = { type: "ready" } | { type: "camera"; camera: Camera } | { type: "error"; code: string };
export interface NativeMapPort {
configure(input: { styleId: string }): Promise<void>;
setCamera(camera: Camera): Promise<void>;
subscribe(listener: (event: MapEvent) => void): () => void;
dispose(): Promise<void>;
}
// Keep wrapper-specific props and native event names inside the adapter.
// The application consumes only this versioned, testable contract.The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region.
Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator.
Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences.
A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression.
Stopping traffic is not enough. Recover durable resources, sessions, events, and in-flight commands without duplicates or hidden divergence.
Prepare support packetKeep the previous signed artifact, dependency lock, configuration, and credential valid until the observation window closes.
Make the provider selection server- or release-controlled; define automatic stop signals and one accountable rollback owner.
For durable state, prove backward-readable records or a reversible data migration before allowing candidate writes.
After rollback, reconcile in-flight requests and resources by stable identifiers instead of replaying commands blindly.