AdminConsole
← All SDKs and distributions
Android · Source SDK

Mappls Location Capture SDK

A lightweight, on-demand location capture SDK for Android that enables applications to fetch a user’s current location efficiently with accuracy limits, timeout control, and minimal battery usage. The SDK supports single-shot and subscribed location fetching without continuous tracking.

currentSource Ready After Validationhybrid
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.
PlatformAndroidKotlin · Groovy · Java
Source activityAgingLast repository push 2025-12-17
CorrespondenceUnmatched0 minimized local candidates; candidates are not compatibility proof
Captured documentation26 sections11 source samples · 18 endpoint signals
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.

3 matching sections

Getting started

A lightweight, on-demand location capture SDK for Android that enables applications to fetch a user’s current location efficiently with accuracy limits, timeout control, and minimal battery usage. The SDK supports single-shot and subscribed location fetching without continuous tracking.

Adding Mappls Configuration file

• Download Configuration files for your app (associated with Package Name and Signing Certificate SHA-256 ) - Add Configuration files ( .a.olf and .a.conf) into the module app-level root directory of your app - Add Mappls Service Plugin as a dependency in your project level build.gradle or build.gradle.kts

Add the dependency

• Add below dependency in your app-level build.gradle

Sanitized repository fragments

Source code evidence

Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.

6 shown
Kotlin (settings.gradle.kts)Kotlin
pluginManagement {
        repositories {
            maven(url = "https://maven.mappls.com/repository/mappls/")
        }
    }
    dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven(url = "https://maven.mappls.com/repository/mappls/")
    }
    }
Groovy (settings.gradle)Groovy
pluginManagement {
        repositories {
            maven {
                url 'https://maven.mappls.com/repository/mappls/'
            }
        }
    }
    dependencyResolutionManagement {  
    repositories {  
            google()  
            mavenCentral()  
            maven {  
                url 'https://maven.mappls.com/repository/mappls/'  
            }  
    }  
    }
Kotlin (build.gradle.kts)Kotlin
buildscript {
        dependencies {
            classpath("com.mappls.services:mappls-services:1.0.0")
            // NOTE: Do not place your application dependencies here; they belong
            // in the individual module build.gradle files
        }
    }
Groovy (build.gradle)Groovy
buildscript {
        dependencies {
            classpath 'com.mappls.services:mappls-services:1.0.0'
            // NOTE: Do not place your application dependencies here; they belong
            // in the individual module build.gradle files
        }
    }
Kotlin (build.gradle.kts)Kotlin
plugins {
        id("com.android.application")
        // Add the Mappls services Gradle plugin    
        id("com.mappls.services.android")
    }
Groovy (build.gradle)Groovy
plugins {
        id 'com.android.application'
        // Add the Mappls services Gradle plugin
        id 'com.mappls.services.android'
    }
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.

No deterministic local candidate was found for this public source.