Skip to main content

​
Android Chat SDK v5 — LLM docs index (Latest)

Low-level Android (Kotlin/Java) chat + calling client. Gradle coordinate com.cometchat:chat-sdk-android:5.+ (calls add com.cometchat:calls-sdk-android:5.+). This page is an Android-SDK-v5-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 + method signatures, parameters, and listener contracts). 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 from memory.
  • Pages show Kotlin and Java variants side by side where they differ.

​
Hot path — usually no fetch needed

For a plain “add chat” the Gradle setup, init → login, and the core send/receive listener flow are stable; a well-built agent skill bakes them. Fetch below only for exhaustive parameters, long-tail methods, group/user management, calling, or edge-case listeners.

​
Getting started / integration

​
Messaging

​
Calling

​
Users

​
Groups

​
AI & advanced features

​
Resources & listeners

​
Advanced

​
Want ready-made UI instead? — the Android UI Kit

This SDK is headless: it gives you data and methods, no screens. If the app needs a conversation list, a message list or a composer, the UI Kit already ships them (and sits on this SDK, so init/login are shared — never initialise twice).
  • Android UI Kit v6 — scoped LLM index: llms-android-v6
  • Use the SDK directly for what the kit has no component for: unread counts, webhooks, low-level presence/connection, granular group management, ban/unban round-trips.

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

Sending the right SDK call is not enough when the capability is dashboard-gated. These pages are outside the SDK tree:

​
Push, campaigns, auth & webhooks

​
Migration & misc