Originally published at claudeguide.io/claude-code-android-development

Claude Code for Android Development (2026)

To use Claude Code for Android development in 2026, open your project in Android Studio, start Claude Code in the project root, and prompt it with your target feature plus the relevant files in context. Claude Code reads your existing architecture — Gradle config, package structure, existing ViewModels — and generates idiomatic Kotlin that fits the codebase. It handles Jetpack Compose UI, ViewModel + Coroutines state management, Room database schemas, Retrofit API clients, and Hilt dependency injection without switching tools or copy-pasting boilerplate — covering 7 Android architecture patterns. This guide covers the exact workflow for each layer of a production Android app.

---

Setting Up a New Android Project with Claude Code

After creating a project in Android Studio (Empty Activity with Compose), open Claude Code in the project root and establish the architecture:

I have a new Android project using:
- Kotlin 2.0, minSdk 26, targetSdk 35
- Jetpack Compose with Material3
- Single-activity architecture

Set up the following:
- app/build.gradle.kts with dependencies for Compose, ViewModel,
  Room 2.6, Retrofit 2.11, Hilt 2.51, Coroutines
- buildSrc/Dependencies.kt for version constants
- com.example.app package with ui/, data/, domain/ layers
- Hilt application class and manifest entry

Show all files with correct versions for 2026.

Claude Code reads your existing build.gradle.kts and generates a consistent dependency block — avoiding the version conflicts that typically consume hours of setup time.

For adding Claude Code to an existing project:

Review my app/build.gradle.kts and identify missing dependencies
for: Jetpack Compose (if not present), Hilt, Room, and Retrofit.
Show only the additions needed, preserving existing versions.

---

Generating Jetpack Compose UIs

Compose screen generation is where Claude Code delivers the highest time savings. Provide the data model and describe the layout:

Generate a Jetpack Compose screen for a notes list with:
- NoteListScreen composable that takes NoteListUiState and callbacks
- LazyColumn with NoteCard items (title, preview, timestamp)
- FAB to create a new note
- Empty state illustration when list is empty
- Material3 theming (use Surface, TopAppBar, FloatingActionButton)
- Preview annotations for light and dark themes

Claude Code produces working Compose code with correct state hoisting and preview support:

// ui/notes/NoteListScreen.kt
@Composable
fun NoteListScreen(
    uiState: NoteListUiState,
    onNoteClick: (Long) -

---

## ViewModel + Coroutines Patterns

Ask Claude Code to generate the full ViewModel with state management:

Generate NoteListViewModel for the notes screen with:

• StateFlow<NoteListUiState

---

Frequently Asked Questions

Does Claude Code work inside Android Studio?

Claude Code runs in the terminal, not as an Android Studio plugin. Open a terminal tab within Android Studio (View → Tool Windows → Terminal) and run claude in the project root. Claude Code reads the same files Android Studio has open, so there is no conflict. Some developers keep Android Studio and Claude Code in a split-screen layout — Android Studio for the emulator and visual layout editor, Claude Code for code generation.

Can Claude Code generate Compose Previews and catch UI bugs?

Claude Code generates @Preview annotations correctly, including multi-preview setups for different screen sizes and themes. It cannot render them visually — that still requires Android Studio's Preview pane. However, Claude Code can review a screenshot of your Preview output if you describe visual issues: paste the screenshot path and describe what looks wrong, and Claude Code suggests Compose modifier corrections.

How does Claude Code handle Gradle version conflicts?

Give Claude Code your full build.gradle.kts and describe the error. It identifies incompatible version combinations (common with Compose BOM vs. manual artifact versions, or Hilt vs. KSP version mismatches) and provides the correct pinned versions. For KSP-based libraries (Room, Hilt), always ensure the KSP version matches your Kotlin version — Claude Code checks this automatically when you include your libs.versions.toml.

Can Claude Code write Espresso or UI Automator tests?

Yes. Provide the screen under test and the user flow to verify:

Generate an Espresso test that: launches MainActivity, navigates to
NoteListScreen, taps the FAB, enters a title and content in NoteEditScreen,
presses Save, and verifies the new note appears in the list.

Claude Code generates the test with proper ActivityScenario, Intents, and EspressoIdlingResource setup for async operations. For Compose-heavy UIs, the Compose testing API (composeTestRule) is preferable and Claude Code defaults to it when it detects Compose screens.

Does Claude Code understand the Android lifecycle?

Claude Code knows that ViewModels survive configuration changes, that LaunchedEffect keys control recomposition side effects, and that collectAsStateWithLifecycle is preferred over collectAsState for battery efficiency. When generating ViewModel code it consistently uses viewModelScope, avoids leaking coroutines, and places StateFlow over LiveData for new Compose projects. If your project still uses LiveData, specify that in the prompt and Claude Code adapts accordingly.

---