AdminConsole
Migration center/React Native
React Nativestatefulcritical risk

InTouch React Native bridge lineage

Align JavaScript, wrapper, and both native dependency graphs while keeping tracking identity and recovery above the bridge.

Start the plan Review source evidence
Direct Lineage

Strong lineage, still not a compatibility promise

The branded repository lineage is strong evidence, but Android and iOS native dependencies, wrapper compatibility, background policy, and entitlement require release-specific confirmation.

Traceable inputs

What the repository snapshot actually proves

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.

Before and after

Re-contract the integration

Resolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.

DimensionLegacy exposureCandidate targetRequired proof
Version matrix

JavaScript package, React Native, Android, and iOS versions may drift independently.

Treat wrapper and both native graphs as one tested release unit.

Lockfile, Gradle graph, resolved Swift packages/pods, and physical-device build matrix.

Bridge events

Event names, payloads, and listener cleanup can leak into product code.

Normalize a bounded discriminated event model with one unsubscribe owner.

Contract tests cover malformed events, high frequency, backgrounding, remount, and process recovery.

Durable tracking

JavaScript memory can accidentally become the journey source of truth.

Keep session identity and command outcomes in durable native/server state.

Kill/relaunch, offline, upgrade, reinstall, cross-device, and logout journeys reconcile correctly.

Compatibility matrix

  • Package, wrapper, native runtime, build tool, operating-system, and architecture versions are recorded together.
  • Credentials are classified by client/server use, restricted to the exact environment, and never copied between generations by assumption.
  • Normalized fixtures cover success, zero results, invalid input, authentication, quota, timeout, offline, cancellation, and malformed provider data.
  • Telemetry distinguishes legacy and candidate generations without logging credentials, precise private locations, or raw provider bodies.
  • Every state-changing operation has an idempotency, reconciliation, ownership, and ambiguous-outcome policy before cutover.
  • Android and iOS are accepted separately; success on one platform never stands in for the other.
Controlled cutover

Six stages, each with an exit gate

Do not advance on calendar alone. Each stage creates evidence that makes the next one safe and reversible.

  1. 01

    Freeze the baseline

    Inventory every cross-platform tracking bridge, package, host, credential class, callback, and owner before changing production.

    Deliverable
    A signed baseline manifest, representative fixtures, latency/error measurements, and a dependency lockfile.
    Exit gate
    The current build is reproducible and its externally visible behavior is covered by contract tests.
  2. 02

    Prove the candidate

    Resolve the exact entitled package or endpoint with Mappls and verify its supported toolchain, region, quotas, authentication, and lifecycle.

    Deliverable
    An approved compatibility matrix linked to source fingerprints and an account-specific entitlement record.
    Exit gate
    No candidate is inferred only from a similar repository name; the owning product team confirms the integration line.
  3. 03

    Install an adapter seam

    Move cross-platform tracking bridge calls behind a narrow application-owned interface without changing product behavior.

    Deliverable
    A legacy adapter, candidate adapter, normalized domain types, safe error taxonomy, and dependency-injection switch.
    Exit gate
    The same journey tests run against either adapter without UI or domain-code changes.
  4. 04

    Compare safely

    Replay approved fixtures and shadow eligible reads while preventing duplicate writes or user-visible duplicate native work.

    Deliverable
    A privacy-reviewed parity report covering results, ordering, geometry, errors, latency, resource use, and lifecycle behavior.
    Exit gate
    Every material difference is accepted, fixed, or converted into an explicit product decision.
  5. 05

    Cut over by cohort

    Release to internal users and bounded cohorts with health gates, ownership, automatic stop conditions, and immutable version evidence.

    Deliverable
    A staged rollout record with cohort, package/data versions, success metrics, support routing, and stop/go decisions.
    Exit gate
    The target service level and full-journey acceptance criteria hold through the agreed observation window.
  6. 06

    Retire deliberately

    Remove legacy credentials and dependencies only after rollback and audit retention obligations expire.

    Deliverable
    Revocation evidence, dependency removal, archived compatibility report, updated runbooks, and owner sign-off.
    Exit gate
    No runtime, build, secret, dashboard, or operational process depends on the retired line.
Application-owned boundary

Make the provider replaceable before replacing it

These examples deliberately model the seam and verification pattern—not unconfirmed package symbols. Implement the adapters only after the exact target contract is issued.

React Native migration seam
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.
Release decision

Evidence required to cut over

  1. 1

    The candidate and exact package/endpoint versions are approved by the owning Mappls product team for the target account and region.

  2. 2

    Journey-level contract tests pass on every supported device, browser, architecture, and release build—not only a debug simulator.

  3. 3

    Security, privacy, accessibility, performance, quota, observability, and support owners accept measured differences.

  4. 4

    A bounded cohort completes the agreed observation window without an unresolved severity-one or severity-two regression.

Design before rollout

Rollback is a product journey

Stopping traffic is not enough. Recover durable resources, sessions, events, and in-flight commands without duplicates or hidden divergence.

Prepare support packet
  1. 01

    Keep the previous signed artifact, dependency lock, configuration, and credential valid until the observation window closes.

  2. 02

    Make the provider selection server- or release-controlled; define automatic stop signals and one accountable rollback owner.

  3. 03

    For durable state, prove backward-readable records or a reversible data migration before allowing candidate writes.

  4. 04

    After rollback, reconcile in-flight requests and resources by stable identifiers instead of replaying commands blindly.