Skip to content

DMA Library Android Deployment Guide

Document version 2.0.13 August 2025

This document is a trade secret document of DialMyApp.

Do not copy, reproduce, transfer or show this document without the prior written permission of DialMyApp.

In case the contract finishes, please destroy any copies of it.

Guide Overview

  • Changelog — Version history of the DMA library documentation, listing changes and additions from the latest release back to version 1.3.0.

  • Introduction — Overview of the DMA library's capabilities: call interception, profile display via push notifications, caching, periodic updates, analytics, and platform support (Android 5.1+).

  • Deployment — How to obtain the DMA library AAR file and integrate it into your Android project via Gradle, including dependency lists for different API levels and GMS/HMS platform variations.

  • Initialization — Required SDK initialization using InjectingRef.defineApplication() in your Application class, with optional auth token integration and DexGuard configuration.

  • Permissions Guide — Complete reference of all Android permissions required for each DMA integration mode, Google Play policy requirements, and hybrid integration variants.

  • Private Information & Privacy — Google Play's prominent disclosure and consent requirements, privacy policy setup in Play Console, and SDK methods for tracking user consent.

  • Runtime Permissions — Code examples for requesting runtime permissions, overlay permission, autostart permission, Xiaomi-specific permissions, and the full recommended permission request sequence.

  • Firebase Cloud Messaging — Integrating Firebase Cloud Messaging with the DMA SDK using FcmHandler callbacks for token registration and push message processing.

  • Deeplinks & Applinks — Setting up deeplinks and app links for DMA-sent SMS, including the required assetlinks.json configuration to associate your website with your Android app.

  • Phone Verification — Three SMS verification approaches: app-coded verification flow, DMA special profile flow, and providing a pre-verified phone number, with error handling and lifecycle callbacks.

  • Custom Application Data — Sharing custom data with the DMA SDK using CustomAppDataManager for personalization and analytics purposes.

  • Testing — Checklist for testing your SDK integration including deep link, permission, and interception tests, plus steps for collecting logs and build info when issues occur.

  • SDK Size — DMA Android library size information (2.04 MB unobfuscated, with optional reduced sizes via obfuscation) and a list of transitive dependencies.

  • Library Workflows — How DMA interception works internally, API request endpoints, app startup behavior, library control methods (stopDMA/resumeDMA), and custom intercept logic configuration.