public source · TypeScript

React Native bridge-contract starter

A typed shared state contract with independent Android and iOS adapter qualification instead of assumed wrapper parity.

Inside the archive

A project you can inspect before installing.

The canonical file manifest is also the archive contract. Common evidence, environment, manifest, and acceptance files accompany platform-specific source.

README.mdSetup and first-success boundary

STARTER_MANIFEST.jsonMachine-readable project scope

.env.exampleBlank non-secret configuration

EVIDENCE.mdSource and selection boundary

ACCEPTANCE.mdSuccess and hostile-path proof

src/mappls-feature.tsShared bridge contract

src/fixture-adapter.tsDeterministic bridge fixture

NATIVE_MATRIX.mdIndependent native release checklist

React Native bridge-contract starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "react-native-map-starter",
  "platform": "React Native",
  "quickstartSlug": "react-native-map",
  "readiness": "public-source",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [
    "mappls-react-native-sdk"
  ],
  "credentialRule": "Blank environment placeholders only; enable a live adapter only after account, package, host, auth, region, and entitlement review."
}

Credential boundary

Secrets have one owner.

Configure Android and iOS app credentials independently and keep privileged calls on a backend. JavaScript configuration is not a secret store.

Evidence boundary

Source before syntax.

The public wrapper is sample-classified. Confirm React Native, wrapper, New Architecture status, Gradle/Kotlin, Xcode/Swift, and underlying native Mappls versions as one release unit.

Mappls React Native SDK

Release evidence

What must be true after the scaffold.

Android and iOS return the same application-level selected ID while platform-specific failures remain visible and attributable.

A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result.

No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts.

Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends.

Wrapper/native matrix is pinned

Both release builds are proven

Bridge traffic is bounded

Unmount disposes every native resource