Platforms/React Native

React Native

Share product logic while keeping native Mappls capabilities honest on both platforms.

TypeScriptJavaScript

How the pieces fit

Shared JavaScript/TypeScript interfaces backed by Mappls native SDKs. Use this boundary as a starting point, then narrow it around the exact Mappls products and trust model your application needs.

01

TypeScript interface

Expose stable application-level components, hooks, and event types instead of leaking every native implementation detail.

02

Native Mappls bridges

Configure Android and iOS independently, including packages, credentials, manifests, permissions, and lifecycle callbacks.

03

Backend services

Retain credentials and stateful workflows centrally so app reinstalls and cross-device use remain recoverable.

From empty project to one real journey

Each step produces a testable boundary. Keep the first release deliberately small, then expand from observed product behavior.

  1. 1

    Align the version matrix

    Confirm React Native, Android, iOS, Mappls wrapper, and underlying native SDK compatibility.

  2. 2

    Install both native halves

    Complete Gradle and Xcode configuration before treating the JavaScript API as available.

  3. 3

    Create a typed boundary

    Normalize coordinates, feature IDs, commands, callbacks, and errors at the application edge.

  4. 4

    Test asymmetric failures

    Verify upgrades, permissions, backgrounding, and process recovery independently on Android and iOS.

4 product families

2 of these families include durable or session state. Follow their complete lifecycle guidance rather than integrating only the first successful call.

Platform tutorials

Start with one focused result, then move into complete stateful journeys and operational failure handling.

Production readiness

Pass these checks in addition to the requirements of the selected product, SDK release, operating system, and security program.

  • Native and wrapper releases are compatible
  • High-frequency events are throttled before crossing the bridge
  • Unmount releases native views and listeners
  • Platform-specific behavior is documented, not hidden