Mappls Intouch React Native SDK
This SDK is wrapper for ReactNative on Native SDKs (IntouchCore, IntouchAPI) to support on Android and iOS.
Compatibility decision
Use as current source evidence, then pin and validate the exact package, endpoint, authentication, entitlement, region, and release pairing before production.
Repository content, activity, code fragments, and local correspondence are discovery evidence only. They do not establish a supported package coordinate, binary identity, current version, account entitlement, runtime pairing, production compatibility, or approval.Source and identity
- Public source
- Open repository ↗
- Captured document
- Open source documentation ↗
- Default branch
main- Lifecycle risk
- Standard Review
- Authentication signals
- No authentication signal extracted; verify before integration
Products and prerequisites
- A React Native project with both native build environments
Install and configuration guidance
These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.
No install section was captured.
This is an explicit evidence gap, not permission to infer a package coordinate from the repository name. Use the source guide and product owner to resolve the distribution.
Connected implementation paths
Exact source paths
No quickstart or starter explicitly names this source. Continue through the platform path without claiming direct lineage.
Adjacent platform paths
Platform guidance—not package compatibilityBridge one map feature across Android and iOSMigration evidence
Direct LineageInTouch React Native bridge lineageProduction compatibility checklist
A clean demo is the beginning of the decision, not its conclusion.
- 01
Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.
- 02
Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.
- 03
Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.
- 04
Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.
- 05
Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.
- 06
Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.
- 07
For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.
- 08
Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.
Local repository candidates
Only minimized identity evidence is exposed. Review candidates side by side; do not assume they are the same release line.
No deterministic local candidate was found for this public source.