Voice for the Documentation Half of Android Dev

Short answer: open Android Studio, place your cursor in a KDoc block, markdown file, or Play Store draft, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak as long as you need, press again. AICHE inserts cleaned-up text in 2-3 seconds.

Android development is layered: Kotlin source, XML layouts, Gradle build files, manifest declarations, ProGuard rules, Compose UI trees, Play Store metadata. The code is the easy part. The hard part is leaving enough context that future-you (or the next teammate) understands why this Gradle dependency is pinned to 2.4.1, why this composable accepts a ColumnScope-receiving lambda, why this ViewModel handles process death the way it does.

Voice handles that part well because the explanations are conversational. You know the reasons. You skip writing them down because typing a paragraph in a KDoc block feels like it'll take forever.

How It Works

1. Open Android Studio with your project.
2. Position your cursor in a KDoc comment, a Kotlin/Java source file, build.gradle.kts, or a markdown doc.
3. Type /** to open a KDoc block (Studio auto-completes it).
4. Press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux).
5. Speak. No length cap.
6. Press the hotkey again. AICHE transcribes, applies AI cleanup, inserts.
7. Add KDoc tags (@param, @return, @throws, @sample) manually. Studio's autocomplete suggests them.

Heads-up: Android Studio is IntelliJ-based. AICHE runs as a desktop app, not a plugin, so no Gradle sync, no build-script changes.

Where Voice Pays Off in Android Studio

Composable Documentation

Jetpack Compose composables behave differently based on parameters, state, and composition context. Worth documenting properly. Position cursor above the composable, dictate: "Renders a card with elevation 4dp. Content lambda receives a ColumnScope so children can use Modifier.align. onClick fires after the ripple animation completes; passing null disables clickability and removes the ripple. State hoisting follows the standard pattern."

ViewModel and Repository Reasoning

Architecture components are where business logic lives, surviving multiple UI rewrites. Dictate per public method: what it does, which LiveData / StateFlow it updates, threading guarantees, configuration-change behavior, process-death recovery. Future-you reads it and saves an hour.

Gradle Build Comments

Above each non-obvious dependency or task, dictate the why: "Pinned to 2.4.1 because 2.5.0 has a binary incompatibility with our custom serializer. Tracking issue link in CHANGELOG. Safe to upgrade once the serialization module migrates to the new API." Saves the next dependency-bump hero an hour of detective work.

Play Store Listings

Short description: 80 chars. Full description: 4000 chars. Most developers hate writing these. Press the hotkey, talk like you're describing the app to a friend: who it's for, what it does, why it's useful. AI cleanup polishes it into store-listing tone. Dictate two or three takes, pick the strongest.

Release Notes That Aren't "Bug Fixes"

Real release notes increase update adoption. Dictate what actually shipped: new features, fixed bugs, perf wins in specific places, breaking changes users should know about. Two minutes of speaking, three weeks of "you fixed the offline-mode crash" goodwill.

Logcat and Layout Inspector Annotations

While debugging, dictate observations into a markdown scratch file: "Recomposition triggers in HomeScreen every time the timer ticks because the Modifier reference changes. Fix: hoist the modifier or use derivedStateOf for the formatted string." The notes outlive the session.

What You Get

• Unlimited voice notes with AI cleanup - filler words removed, punctuation and paragraph breaks added.
• Software Development profile (Pro) - recognition tuned for code, APIs, library names, Gradle/Kotlin syntax.
• Custom vocabulary - drop in package names, internal libraries, brand names, codenames.
• System-wide dictation - same hotkey in Studio, terminal, browser, Slack, Play Console.
• Multilingual voice input - speak in your language, transcribe in that language or auto-translate to English.
• Zero-retention audio - audio purged immediately after processing, within 1 second.

Plans start at $3.99/mo (annual) with a 7-day free trial, no credit card. See pricing.

Common Questions

Q: Does AICHE work in IntelliJ IDEA, RubyMine, GoLand, etc.?
A: Yes. Same JetBrains-platform behavior. AICHE inserts wherever the cursor is.

Q: My team uses Android Studio Bumblebee (or a specific version). Does the version matter?
A: No. AICHE inserts via the OS event path, independent of the IDE version.

Q: Can I dictate Kotlin code itself?
A: You can, but the Software Development profile (Pro) is the difference between usable and frustrating for code-heavy speech. Dictating prose comments is the high-leverage use; dictating raw code is a softer win.

Q: Will the hotkey conflict with Studio's Cmd+Alt+R (debug rerun)?
A: ⌃+⌥+R is Control+Option+R, distinct from Cmd+Alt+R. On Linux/Windows it's Ctrl+Alt+R. If you've remapped Studio bindings to collide, change one of them in AICHE settings.

Q: Does dictating in build.gradle.kts mess with Gradle sync?
A: No. AICHE just inserts text. Studio's Gradle sync runs as normal.

Result: KDoc that captures lifecycle and threading reasoning. Play Store listings written in minutes. Gradle files where every non-obvious choice has an explanation. Migration guides that keep the team aligned.

Try it now: open one undocumented ViewModel or composable, type /** above it, press your hotkey, and dictate complete documentation including the Android-specific concerns (lifecycle, threading, recomposition).