AdminConsole
← All SDKs and distributions
Android · Source SDK

Mappls Intouch Android SDK

A Mappls sdk for tracking telematics, workforce, gis analytics, widgets deep links, capture feedback across Android.

currentSource Ready After Validationstateful
Source Ready After Validation

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.
PlatformAndroidNo implementation language identified in the source snapshot
Source activityActiveLast repository push 2026-05-18
CorrespondenceNormalized1 minimized local candidates; candidates are not compatibility proof
Captured documentation4 sections0 source samples · 20 endpoint signals
Scope

Products and prerequisites

GIS & AnalyticsCapture & Feedback
  • An Android project with a supported Gradle and Kotlin or Java toolchain
  • OAuth client credentials issued for the intended Mappls project
  • A Mappls project key restricted to the intended app, domain, or backend
Captured source evidence

Install and configuration guidance

These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.

0 matching sections

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.

From discovery to release

Connected implementation paths

Exact source paths

No quickstart or starter explicitly names this source. Continue through the platform path without claiming direct lineage.

Release gate

Production compatibility checklist

A clean demo is the beginning of the decision, not its conclusion.

  1. 01

    Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.

  2. 02

    Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.

  3. 03

    Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.

  4. 04

    Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.

  5. 05

    Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.

  6. 06

    Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.

  7. 07

    For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.

  8. 08

    Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.

Private correspondence

Local repository candidates

Only minimized identity evidence is exposed. Review candidates side by side; do not assume they are the same release line.

mapmyindia-intouch-android-sdkcontenthub/dochub/mapmyindia-intouch-android-sdklocal-contenthub-dochub-mapmyindia-intouch-android-sdk