Android CLI: Build Android apps 3x faster using any agent

Original Article ↗ Hacker News Discussion ↗

Perceived Benefits of the Android CLI

  • Many welcome a sane, scriptable, agent-friendly interface to the Android SDK after years of clunky tooling.
  • Structured commands are seen as useful for both humans and agents, reducing trial-and-error and token usage; internal claims of “3x faster” and “70% fewer tokens” are viewed as directionally promising, if possibly marketing-inflated.
  • People like ideas such as android docs to expose APIs and signatures directly, rather than having agents grep or scrape docs.

Skepticism and Limitations

  • Some argue modern tooling (React Native, Flutter, workflow engines, etc.) already makes app building fast, even without AI.
  • Others say building high-quality apps is still hard, and this CLI mostly helps with initial setup, not daily development tasks.
  • A few are outright dismissive: see it as a thin wrapper plus telemetry, not worth installing.

Privacy, Metrics, and Control

  • Concern over Google collecting CLI usage metrics by default, with opt-out via --no-metrics. Workarounds with aliases/wrapper scripts are discussed, including pitfalls.
  • Strong suspicion that Google might gradually tighten control over APK sideloading; others push back, saying Google won’t block third‑party apps entirely.

Sideloading, Security, and Scams

  • Debate over making sideloading harder: some support friction to protect less technical users from malware; others note most fraud is social engineering and argue technical blocks are a “cannon for a mosquito.”
  • Examples from India highlight telecom and government measures against OTP/social‑engineering scams.
  • Frustration at confusing sideload UI flows that bury the “install anyway” option.

Tooling Comparisons and IDE Fatigue

  • Flutter is praised for having strong CLI tooling from the start; Android is described as an organically grown mess “held together by duct tape.”
  • iOS/macOS tooling is portrayed as worse, with Xcode seen as painful and Apple resistant to pure-CLI workflows.
  • Some want to abandon heavyweight IDEs (especially Android Studio) in favor of CLI+agents; others say IDEs remain important for debugging and emulator management.

On-Device and Agent-Centric Development

  • Several note you can already build Android apps on-device via Termux plus agent harnesses, or offload builds to CI and distribute via tools like Obtainium.
  • There is excitement about fully phone-native, automated dev loops, though log/feedback wiring for agents is still a practical hurdle.