Mapmyindia Intouch Android SDK
A Mappls sdk for tracking telematics, workforce, gis analytics, widgets deep links, identity platform across Android.
Compatibility decision
Do not start a new production build from this evidence. Contain existing use, identify a supported target, migrate with rollback, and retire the dependency.
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
master- Lifecycle risk
- Retire
- Authentication signals
- oauth2
Products and prerequisites
- An Android project with a supported Gradle and Kotlin or Java toolchain
- OAuth client credentials issued for the intended Mappls project
Install and configuration guidance
These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.
Setup.
We use your Client ID to identify your account details and assign all your user's devices under a single account.
To get your Outh2 Rest API Client ID and Client Secret please login to MapmyIndia API Dashboard
Please contact apisupport@mapmyindia.com to get InTouch SDK access to your Client ID
After getting the access, you can start with the InTouchDemo app, or Integrate the InTouch SDK in your app.
Step 1: Setup a project
1. Start Android Studio. 2. Create a new project as follows: - If you see the Welcome to Android Studio dialog, choose Start a new Android Studio project, available under 'Quick Start' on the right of the dialog. - Otherwise, click File in the Android Studio menu bar, click New-> New Project. - Select the form factors you need for your app. If you're not sure what you need, just select Phone and Tablet. - Select Add No Activity and click Next. 3. Enter your app name, package name, project location, language and minimum API version as prompted. Click Next. 4. Create a Basic Activity in the 'Add an activity to Mobile' dialog. Click Next. 5. Enter the activity name, layout name and title as prompted. Click Finish.
Android Studio starts Gradle and builds your project. This may take a few seconds. For more information about creating a project in Android Studio, see the Android Studio documentation.
The next few sections contain the code samples that you need to add to your activity's java file as well as its xml layout file for creating an app with MapmyIndia InTouch SDK for live tracking.
Step 3: Initialize InTouch SDK
Initialization can be done either of the below mentioned method. Keep the same method accross your project.
Source code evidence
Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.
allprojects {
repositories {
maven {
url 'https://maven.mapmyindia.com/repository/mapmyindia/'
}
}
}implementation 'com.mapmyindia.sdk:intouch-sdk:0.9.4'compileOptions {
sourceCompatibility 1.8
targetCompatibility 1.8
}Required Minimum sdk version
minSdkVersion 18InTouch.initialize(<device name>, <your client id>, <your client secret>, object : IAuthListener {
override fun onSuccess() {
//write your code here
}
override fun onError(reason: String?, errorIdentifier: String?, errorDescription: String?) {
// reason gives the error type.
// errorIdentifier gives information about error code.
// errorDescription gives a message for a particular error.
}
})InTouch.initialize(<device name>, <your client id>, <your client secret>, <uniqueId>, <fcmToken>, object : IAuthListener {
override fun onSuccess(Long entityId) {
//write your code here
}
override fun onError(reason: String?, errorIdentifier: String?, errorDescription: String?) {
// reason gives the error type.
// errorIdentifier gives information about error code.
// errorDescription gives a message for a particular error.
}
})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 compatibilityCreate a lifecycle-safe Android mapMigration evidence
Direct LineageInTouch Android SDK 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.
contenthub/dochub/mapmyindia-intouch-android-sdklocal-contenthub-dochub-mapmyindia-intouch-android-sdk