What problem does it solve? Android development inside Nix flake-based projects requires coordinating the Gradle wrapper, Android SDK paths, adb devices, and emulator tooling, and misconfigured environments cause confusing build and test failures. ## Core Features & Use Cases - Environment Setup: Enter the dev shell with nix develop or direnv allow, with ANDROID_HOME and platform-tools automatically on PATH. - Build and Test Workflows: Run ./gradlew assembleDebug, test, and connectedDebugAndroidTest with the project wrapper preferred over the system Gradle. - Device Debugging: Use adb devices, adb logcat, scrcpy, and jadx for runtime crash analysis and APK inspection. - Use Case: A developer clones a project from the spreadconfig Android template, runs scripts/android-doctor to verify the SDK and adb, then builds and deploys a debug APK to a connected phone. ## Quick Start Enter the project dev shell and ask the assistant to diagnose why my Android build fails when running the Gradle wrapper.