Skip to content
2WAI Avatar Toolkit

Android native (Kotlin) — upon request

A dedicated Kotlin / Jetpack Compose SDK for Android is not shipped. It’s on the roadmap conditional on customer demand.

Why not shipped yet

Section titled “Why not shipped yet”

The Flutter SDK ships to Android from the same codebase as iOS, Web, Windows, macOS, and Linux. For every Android integration we’ve seen so far, the Flutter track has been the right answer:

  • Same TwaiTransport0Player widget, same mint-proxy pattern.
  • Full feature parity with iOS + Web — no “Android-only” gaps.
  • One team learns one SDK; ships everywhere.

The case for a dedicated Kotlin SDK is a Compose-first Android team that doesn’t want to add Flutter to their build. That case exists but hasn’t been loud yet.

What a Kotlin SDK would look like

Section titled “What a Kotlin SDK would look like”

When demand lands, the shape will mirror the iOS native SDK’s TwaiAvatarKit:

  • Package: com.twai.avatarkit on Maven Central
  • Minimum Android: API 24 (Android 7, 2016) — matches LiveKit Android SDK’s floor
  • UI: Jetpack Compose primary, View-based wrapper secondary
  • Transport: LiveKit Android SDK (livekit-android-sdk) as Transport 0
  • Mint-proxy: enforced (same contract as every other SDK)
  • Products: twai-core, twai-livekit, twai-player (same split as iOS)
  • Spec parity: generated from twai-protocol once that repo gets a Kotlin codegen target

Design doc would mirror ios_native_sdk_plan.md in the toolkit.

I need Android native — what do I do?

Section titled “I need Android native — what do I do?”
Use Flutter today Ships to Android from one codebase. For most Android apps this is the fastest path.
Raw LiveKit + REST Pull livekit-android-sdk from Maven, call /v1/sessions from your Kotlin backend, join the room from Compose. ~2 days of integration work vs waiting for the SDK.

If neither works and you’d specifically fund the SDK build-out, contact your 2wai account rep or ping the 2waiorg/2wai-toolkit-public issue tracker. The gating signal is one or two integrators committing to be the first users; we don’t want to ship an SDK nobody uses.

Status update when it ships

Section titled “Status update when it ships”

This page will convert from “upon request” to a real quickstart when the Kotlin SDK v0.1 lands. Watch the SDKs index or the toolkit repo’s release notes.