Status: planned — not available yet
The Android SDK is on our roadmap but has not been released. There is no package on Maven Central, and no beta build to request — any package with a similar name on a public registry is not ours. We would rather say this plainly than take your email for a waiting list that doesn't exist.
You can track Android apps today through the REST API (below) — that is the same endpoint the SDK will wrap, so the integration work is not wasted.
Tell us you want the Android SDKWe use this to decide which platform to build first — it is not a signup for a private beta.
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/{site_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 SDK ships it is intended to use a mobile-safe authentication flow (short-lived per-install tokens) so you won't need this backend hop. That flow is designed but not built yet — today the backend hop is the correct pattern.
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.