Skip to main content

Android UI Kit v6 — LLM docs index (Latest)

Stateful, drop-in Android chat/calling UI. Two UI flavors of ONE kit: com.cometchat:chatuikit-kotlin-android:6.+ (Kotlin, XML Views) and com.cometchat:chatuikit-compose-android:6.+ (Jetpack Compose) — both sit on com.cometchat:chat-sdk-android:5.+. This page is an Android-v6-only routing index for AI agents — a scoped alternative to the site-wide /docs/llms.txt.

How to use this index

Each link points to the docs page; append .md to its URL to fetch the clean Markdown twin (verbatim code + component/method signatures). Pick the page for the intent, then read the API there.
  • Convention: any docs page URL + .md → raw Markdown.
  • Fallback: if a .md twin 404s, fetch the same URL without .md (HTML). Never answer APIs or attributes from memory.
  • Two UI flavors, one docs tree: unlike other platforms, Android does NOT have separate Compose/Views doc trees. Almost every page below carries BOTH a Kotlin (XML Views) tab and a Jetpack Compose tab — read the tab that matches the app’s UI flavor. Only Getting Started is split into two dedicated pages (linked below).

Hot path — usually no fetch needed

For a plain “add chat” the Gradle dependency, init → login → launch flow, and the core drop-in components are stable; a well-built agent skill bakes them. Fetch below only for exhaustive attributes, long-tail components, theming tokens, or feature enablement.

Getting started / integration

Core & configuration

Theming

Customization

Components — conversations & lists

Components — messages

Components — calling

Components — search, AI & notifications

Task guides (recipes)

Something is broken — symptom to page

The answer to most first-run failures is a <Warning> on a page the symptom does not name. Match the symptom, not the component.

When the UI Kit is not the answer — drop to the Chat SDK

The kit ships no component for some things (unread counts, webhooks, low-level presence and connection, granular group management, ban/unban round-trips). Those are SDK calls — the SDK is already installed underneath the kit and init/login already use it. Never hand-roll, and never guess a method name:
  • Android Chat SDK v5 — scoped LLM index: llms-android-v5
  • ⚠️ URL trap: v5 SDK pages are VERSIONED — /sdk/android/v5/<page>. The unversioned /sdk/android/<page> tree is v4; never read it for a v6 UI Kit build.

Feature switched on OUTSIDE the app — dashboard, extensions, AI

These pages are not under ui-kit/android, and a feature will not work without them however correct the client code is. This is the commonest dead end: the component renders, and nothing happens, because the extension was never enabled.

Push notifications (Android)

The UI Kit renders nothing for push — it is a dashboard + FCM + service integration.

Campaigns, auth & webhooks

Migration & misc