Skip to content
Indiana
Dashboard
Docs
Browse docs / Android / Kotlin integration

Android / Kotlin integration

Connect native identity, isolate sessions and check Play purchase availability.

API v1Updated

1. Install the native SDK

Integrate the indiana source module from packages/android into Gradle. Use the module Gradle configuration for Android SDK, Kotlin and Play Billing dependencies.

Source packages are currently available. See version information for distribution and protocol requirements. Connect Customer sessions and readHoldings before adding Funnel.

Related:Versions and integration

2. Issue the current customer's session

  • Your backend verifies the app login, then identifies the customer and issues a short-lived customerToken using a Server Key bound to this App and Sandbox. Do not trust a customer identity supplied by the device.
  • Configure the HTTPS API URL, App UUID and Sandbox environment. Use only a Customer Token in the app; keep Server Keys and Console sessions in their trusted environments.
  • The SDK keeps the token in memory. Refresh through your authenticated backend. Clear current customer data and authenticate again after 401 / 403.

Related:Identity and credential boundaries

3. Connect and read customer data

IndianaSession.kt
import android.content.Contextimport ai.tinkerland.indiana.*import java.util.UUID suspend fun connectIndiana(context: Context, baseUrl: String,    projectId: UUID, customerToken: String, runToken: String): Pair<IndianaClient, IndianaFunnelSession> {    val client = IndianaClient(context, IndianaConfiguration(baseUrl,        IndianaScope(projectId, IndianaEnvironment.SANDBOX)))    client.identify(customerToken)    client.readHoldings()    return Pair(client, client.funnel(runToken))} // Add IndianaFunnelView(activity, flow) to the host UI on its main thread.// Authenticate the Customer before starting the Run; its Customer never changes.// Set onEvent for authored native events.// Store purchase/restore requires an explicitly supported server release.// On sign-out: client.reset(); destroy the old Funnel view; client.close()

Connection checkpoint

Show connected only after readHoldings succeeds for the current customer. Preserve decimal credits. Cancel host tasks on account changes or navigation, reject late responses and clear the previous snapshot as a whole.

4. Check store availability

Apple/Google purchase, notification and restore are not yet available as a complete integration. Connect Customer sessions and holdings first. Enable store purchases only when a supported release is available.

5. Check results and recover

Integration checks
ScenarioExpected result
First connectionHoldings match Console customer details; invalid, expired and cross-scope sessions are rejected.
Sign-out and account changeClear old data immediately; old requests cannot overwrite the new customer; authenticate again after restart.
Network loss and timeoutShow a retryable error without success; retry the original request after reconnection.
Purchase, restore and refundDeliver a real Sandbox transaction once; restoration does not duplicate grants; verified refunds and revocations reach entitlements and history.

Integration checks

  • First connection

    Expected result
    Holdings match Console customer details; invalid, expired and cross-scope sessions are rejected.

  • Sign-out and account change

    Expected result
    Clear old data immediately; old requests cannot overwrite the new customer; authenticate again after restart.

  • Network loss and timeout

    Expected result
    Show a retryable error without success; retry the original request after reconnection.

  • Purchase, restore and refund

    Expected result
    Deliver a real Sandbox transaction once; restoration does not duplicate grants; verified refunds and revocations reach entitlements and history.
Once store integration is available, test purchase, restore and refund in Sandbox and verify results through readHoldings and transaction status.