Android SDK Version 1.0.0

Install the Zeta Android SDK version 1.0.0 from Maven Central, verify the minimum toolchain requirements, and confirm the release build setup needed for production apps.

This page focuses on installation and setup prerequisites for Android SDK 1.0.0. After installation, continue with Getting Started to initialize ZetaClient with your clientSiteId and clientSecret.

Before exploring related pages, the documentation index is available at https://docs.zetaglobal.com/llms.txt.

Requirements

Your Android project should meet the following minimum supported versions before adding the SDK.

If your app uses a newer Gradle or Kotlin version, standard Gradle dependency resolution applies. The key requirement is meeting or exceeding the minimum versions listed above.

Install via Gradle

The SDK is distributed as a single AAR artifact through Maven Central.

Add the dependency to your module-level build.gradle.kts file:

dependencies {
    implementation("net.zetaglobal.app:core:1.0.0")
}

If your project uses Groovy, add the dependency to build.gradle instead:

dependencies {
    implementation 'net.zetaglobal.app:core:1.0.0'
}

The artifact is published on Maven Central. If your project already includes mavenCentral() in its repositories configuration, no additional repository setup is required.

Push notification dependency

Push notifications require Firebase Cloud Messaging in your app module.

dependencies {
    implementation("net.zetaglobal.app:core:1.0.0")
    implementation("com.google.firebase:firebase-messaging:24.1.0")
}

Firebase Messaging is a compileOnly dependency of the SDK. You must explicitly declare com.google.firebase:firebase-messaging:24.1.0 in your own app module for push notifications to work.

ProGuard / R8

No custom ProGuard or R8 rules are required for Android SDK 1.0.0.

The SDK AAR already includes the necessary keep rules through consumer-rules.pro, so release builds work without additional shrinker configuration.

Transitive dependencies

The SDK pulls in the following dependencies through implementation scope. If your app already includes one or more of these libraries at a different version, Gradle resolves the final version according to normal dependency resolution rules.

Mobile app registration

Before initializing the SDK, register your app with ZMP using the Mobile App Registration guide.

Registration provides the credentials you use during SDK initialization:

• clientSiteId

• clientSecret

During registration, you will also need your Android app's package name, which is the applicationId defined in your module-level Gradle file.

SDK API tokens are write-only and are restricted to updating profiles, tracking events, and logging errors. Refresh tokens are scoped to mobile-specific APIs and cannot access broader platform functionality.

Next step

Once installation is complete, continue to Getting Started to initialize the SDK with your registered credentials and configure tracking behavior.

References

• Documentation Index

• Android SDK Installation

• Android SDK Getting Started

• Maven Central artifact: net.zetaglobal.app:core

• Mobile App Registration guide