
Native Android SDK · In preparation
Android analytics for the journey inside your app
The Talivia Kotlin SDK is in preparation. It is designed to record native screen views, product events, and known users in the same workspace as your website. The Maven Central artifact is not published yet.

Wednesday, September 16th, 2026
Product analytics for mobile apps
Plan the signals your Android app needs
Choose the navigation and product milestones you want to instrument when the package becomes available.
Understand app navigation
Call screen() when the visible destination changes.
Capture product milestones
Call track() after signup, onboarding, or another meaningful action.
Connect known users
Call identify() after login with your stable account ID.
How it works
How the Android SDK is designed to work
The planned Maven coordinate is not yet available for installation. Use this outline to prepare your event design.
Read the setup guide- 01
Wait for the Maven release
The installation command will be added after the artifact is published.
- 02
Connect your Website ID
Initialize with your app context, Website ID, and hostname.
- 03
Instrument screens and actions
Call screen(), track(), and identify() from your app flow.
Choose your SDK
Start with the framework you ship
Each SDK sends native app activity to Talivia. Pick your platform for installation details and the exact tracking calls.
What you can learn
A clear path for native Android measurement
Screen views
Measure the destinations people visit in the app.
Custom events
Use product names that match your actual business flow.
Shared workspace
Use the same Website ID as web when the SDK is available.
Clear measurement boundaries
Know what the SDKs do today
Mobile tracking follows the events your app explicitly sends. Known identities can be linked, while cross-device funnels are still visitor-based.
- Screen changes and business events require explicit calls in your app.
- Offline retry is memory-only and capped at 100 events; app restarts clear the queue.
- Install attribution and verified app purchases require separate trusted integrations.
Questions
Mobile analytics, explained
What you can collect now, and where additional integrations are needed.
Can I install the Android SDK from Maven Central now?
No. The native Android package has not been released to Maven Central yet. This page will include the install instructions after publication.
Will screen views be automatic?
No. The SDK requires explicit screen() calls when navigation changes.
Does the SDK verify purchases?
No. Client events are not trusted payment records. Use a backend or trusted payment integration for verified revenue.
Bring your app into focus
Explore the Android SDK while release is in preparation
Read the current Kotlin API and release status.
Read the Android guide