Status: Private beta — contact us for access
The official Android SDK is in private beta. It is not yet published to Maven Central. Don't search for it there — you won't find it, and any package with a similar name on a public registry is not ours.
During the private beta we ship signed builds directly to a small number of customers so we can collect feedback before publishing to a public registry. There are no synthetic gates — if you want access, just ask.
Request Android beta accessInclude your project ID and a short note on what you're integrating with. We usually reply within a business day.
In the meantime: REST API
You can already track Android events today by calling the REST API directly from your app's HTTP client. Every event the future SDK will send is just a POST /v1/projects/{id}/events — see the REST API guide and the Server-side guide for payload shape.
Important: a mobile app is a "public client" in security terms — anyone can decompile your app and read embedded secrets. For now, the recommended pattern is:
- Have your app POST events to your own backend.
- Have your backend forward to OpenAnalyticsAPI using a secret
oa_live_*key.
When the official SDK ships, it will use a mobile-safe authentication flow (short-lived per-install tokens) so you won't need this backend hop. Pre-built builds for the beta program already use that flow.
What the SDK will provide at GA
- Native Kotlin 1.9+ library; Gradle dependency on Maven Central.
- Automatic Activity / Fragment lifecycle tracking.
- Custom events and conversions with the same API as the JavaScript snippet.
- Offline queue persisted to local storage; flushed on next launch or network availability.
- Background flush on Activity.onStop via WorkManager.
- Advertising ID never collected; per-install identifier rotated on opt-out.
- Source code published on git for review at GA.