Skip to main content
Supported on: Android SDK 1.0.33+

Requirements

Before integrating the AppDNA Android SDK, ensure your project meets the following minimum requirements:
Projects targeting API levels below 24 (Android 7.0) are not supported. The SDK uses Kotlin coroutines and modern Android APIs that require minSdk 24 as a baseline.

Installation

Gradle (Kotlin DSL)

Add the AppDNA SDK to your module-level build.gradle.kts:

Gradle (Groovy DSL)

If your project uses Groovy-based Gradle files, add the following to your build.gradle:
Then sync your project with Gradle files.

Firebase Configuration

The AppDNA SDK uses Firebase Firestore for real-time configuration delivery (paywalls, experiments, feature flags, onboarding flows) and Firebase Cloud Messaging for push notifications. You must add a Firebase configuration file to your project.

Step 1: Download google-services-appdna.json

  1. Log into your AppDNA Console
  2. Go to Settings → SDK
  3. Click Download Firebase Config to download google-services-appdna.json

Step 2: Add to Your Project

Place the google-services-appdna.json file in your app module’s src/main/assets/ directory (the SDK loads it from the app’s assets at runtime):

Step 3: Apply the Google Services Plugin

Add the Google Services classpath to your project-level build.gradle (or build.gradle.kts):
Then apply the plugin in your app-level build.gradle (or build.gradle.kts):
Or with Kotlin DSL:
Without google-services-appdna.json, the SDK cannot fetch remote configuration (paywalls, experiments, feature flags) or receive push notifications. Events will still be tracked, but remote features will not work.
If your app already uses Firebase for your own services (Analytics, Crashlytics, Realtime Database), AppDNA automatically creates a separate named Firebase instance using google-services-appdna.json. Your existing Firebase setup is not affected. Just add the AppDNA config file alongside your own google-services.json.

Dependencies

The following dependencies are automatically included with the SDK. You do not need to add them manually:
If your project already includes these dependencies, ensure your version constraints are compatible with the versions listed above. Gradle will resolve version conflicts automatically in most cases, but you may need to add resolution strategies for major version mismatches.

Optional Dependencies

RevenueCat is declared as compileOnly and is only required if you configure RevenueCat as your billing provider. If you do not use RevenueCat, you do not need to add it.

Jetpack Compose

The SDK uses Jetpack Compose for rendering paywalls and onboarding flows. Compose is enabled automatically using BOM 2024.02.02. Ensure your project has Compose enabled in your module-level build.gradle.kts:

Verify Installation

After adding the SDK, verify it is correctly installed by importing the module and logging the SDK version:
You should see 1.0.43 printed in Logcat. If you get an unresolved reference error, clean your project (Build > Clean Project) and rebuild.

Troubleshooting

If you encounter issues during integration, call AppDNA.diagnose() after configuration to get a snapshot of SDK state. diagnose() returns a String — log it (or capture it for error reports) yourself:
The report is a plain-text snapshot:
Any line that shows <unset> when it shouldn’t, or configured: false, indicates a configuration issue. Common fixes:

Next Steps

Once the SDK is installed, proceed to the Quickstart guide to configure the SDK and start tracking events.