Mappls Camera SDK

1. Introduction 2. Primary Objectives & Overview 3. Key Use Cases 4. Android SDK Integration 5. Product Overview 6. Overlay Components 7. SDK Configuration Attributes 8. Nearby Mappls PIN Selection 9. Output & Data Return Mechanism

The Mappls Camera SDK is a camera-based plugin designed for seamless integration into mobile application. It augments standard device camera functionality with rich, accurate geo-information derived from Mappls's location intelligence stack — including reverse geocoding, Mappls PINs (eLoc), and map-based visual context.

Despite providing its own default UI, the SDK is designed to be highly customizable so that consuming applications can tailor both the visual presentation and the data returned. It supports both static image capture and video recording.

Data is surfaced to the consuming application through two complementary mechanisms:

The primary objective of the Mappls Camera SDK is to embed accurate, trustworthy geo-information within images and videos at the point of capture — making that media a verifiable record of both what was captured and where (and when) it was captured.

This serves two high-level needs:

1. Geo-tagged Media as Evidence: Enable organisations to validate that field personnel, field visits, or events actually occurred at the claimed location, thereby combating fraud and errors in downstream services. 2. Location Intelligence Enrichment: Augment any use case involving photo/video capture with precise, human-readable, and machine-readable location data from the Mappls platform.

Organisations deploying field agents (e.g., financial institutions, insurance companies, logistics providers, government services) can embed geo-information in photos captured at the point of visit. This creates an auditable, tamper-evident record validating that the field agent was physically present at the correct location.

Example: A bank agent photographs a customer's premises. The captured image contains the precise coordinates, reverse-geocoded address, Mappls PIN, and timestamp. The bank's backend system can automatically verify this against the expected address on record.

During self-service Digital KYC flows, users capture photos or videos of themselves or their documents. Embedding live geo-information ensures the self-KYC was completed from the expected location, reducing fraud risk.

Consuming apps implementing face-recognition-based login can use the SDK to simultaneously capture location data alongside the biometric. This merges biometric security with location intelligence — the app knows not only who logged in but where they logged in from.

Field teams conducting surveys of assets, infrastructure, or real estate can capture geo-tagged photos and videos as a reliable ground-truth record that is easily indexed and audited.

Delivery agents can capture geo-tagged photos at the point of delivery, providing end-to-end traceability that links the delivery record to the physical location.

Claims investigators can capture geo-tagged photos of damage sites, providing insurers with credible, location-verified documentation.

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

kotlin val option = MapplsCameraOption.Builder() .setCameraFacing(CameraFacing.REAR) .setFlashMode(FlashMode.AUTO) .setDefaultMediaMode(MediaMode.PHOTO) .build() mBinding.camera.initialize(option.build())

| Output Type | Description | | Static Image | Single captured photo with geo-information overlay and embedded metadata | | Video | Recorded video with real-time geo-information overlay rendered onto frames and metadata embedded in the video container |

The SDK ships with a ready-to-use default camera UI that includes:

• Live camera viewfinder - Photo / Video mode toggle - Capture button - Camera switch button (front / rear) - Flash toggle (rear camera only) - Real-time geo-information overlay on the viewfinder - Nearby Mappls PIN selector panel (swipe-up sheet) - Branding logo area (top-right, configurable by consuming app)

All UI elements are customisable by the consuming application via configuration parameters and theming APIs.

• A small static map image (approximately 80×80dp) showing the current location pinned on the map. - The map style should match Mappls's standard map style with a green marker pin at the current location. - The Mappls logo is rendered in the bottom-left corner of the thumbnail. - The thumbnail is positioned in the bottom-left of the overlay panel.

• Displayed as a formatted URL: mappls.com/{eloc} - Example: mappls.com/mmi000 - The eLoc portion is rendered in the Mappls brand colour (teal/green) to visually distinguish it. - Rendered in the overlay panel header row.

• Human-readable address derived from real-time reverse geocoding of the current coordinates via the Mappls Reverse Geocoding API. - Displayed in 2–3 lines to maintain readability. - Should include: building/place name (if available), street/area, city, state, PIN code. - Example: 237, Okhla Industrial Estate Phase 3, Near Modi Mill, New Delhi, Delhi, 110020

• Displayed as decimal degrees: {latitude},{longitude} - Example: 28.550697, 77.268890 - Precision: 6 decimal places.

• Format: DD-MM-YYYY, HH:MM:SS (24-hour clock). - The timestamp is captured at the moment of image shutter release or continually updated from the start of video recording, and is NOT frozen (updated continuously mid-video). - Example: 08-04-2026, 17:25:11

• A small QR code (approximately 64×64dp) positioned in the bottom-right of the overlay panel. - The QR code can be configured to encode either: - The Mappls PIN URL: https://mappls.com/{eloc} (default) - The coordinate-based Mappls portal URL: https://mappls.com/@{latitude},{longitude} - Example: https://mappls.com/@28.5503,77.2502 - Scanning the QR code should take the user directly to the location on Mappls.

• A configurable logo supplied by the consuming application. - Positioned in the top-right corner of the image/video frame (outside the geo-information overlay panel). - Recommended maximum size: 100×40dp. - Supports PNG with transparency.

• Display the GPS accuracy radius in metres (e.g., ± 4 m) alongside the coordinates. - Helps reviewers assess location confidence. A colour-coded indicator (green: ≤ 10 m, amber: 10–50 m, red: > 50 m) can be rendered as a small icon.

• A small icon indicating the location source: GPS, Network, or Fused. - Adds transparency about how the location was determined.

• Display altitude in metres above sea level where available. - Particularly valuable for multi-storey building verification and infrastructure surveys. - Example: Alt: 212 m

• Display compass bearing (0°–360°) at the time of capture. - Useful for directional documentation (e.g., photograph was taken facing north-east).