---
title: Android
description: >-
  Use the native Android client for chat, projects, groups, inbox, search,
  tasks, channels, and settings.
order: 3
---
Atoi for Android is a native Kotlin and Compose application. It uses Clerk authentication, a secure token store, and Convex-backed repositories and view models to participate in the same product state as web and Apple clients.

## Move through the product shell

The Android shell centers chat while keeping Inbox, Search, Views, and Settings available as first-class destinations. Its sidebar includes projects, recent and pinned conversations, For you items, group conversations, and work that needs a decision.

The implemented screen set includes Chat, Inbox, Search, task list and detail, Memory, Settings, and Channels. Project and group view models supply their records to the shell, and project selection returns to project-backed product context rather than creating a separate Android-only workspace.

Search spans threads, projects, files, and message history. Inbox exposes decisions, approvals, and recovery work. Views rolls up running, completed, and receipt-backed work. Channels presents linked conversations. Settings manages supported user and model preferences.

## Follow threads and tasks

Chat is the primary interaction surface. The Android client keeps conversation lists, selected thread state, group state, streaming messages, tool-call presentation, interviews, and model settings in native UI.

Durable work appears through the task surface rather than a separate top-level coding product. Task list and detail screens read the same task and proof records used elsewhere. Approval actions can be resolved from foreground-authenticated app context, including an approval request delivered through an app intent.

The distinction remains the same as on web: chat handles conversational continuity; durable implementation produces task state, changes, checks, and proof. Android renders and acts on those records.

## Return through links and notifications

The main activity accepts deep links and routes them into the app’s navigation. Approval intents carry a request identifier and the operator’s decision into the task view model. The app also registers the current push token after authentication and Convex connection are ready.

Push registration is infrastructure, not a promise that every product event produces a notification. Read the visible task or inbox state as authority.

## Use the native shape

Android adapts the product to a touch-first Compose interface. It does not copy the desktop sidebar or project pages pixel for pixel. Use it for mobile conversation, search, decision handling, and task follow-through, then continue on another surface through the same identifiers.

The Android application ID and source live under `apps/android`; it is part of Atoi’s native-complete platform posture.