I built ADB Ready after repeatedly losing Android development sessions to mismatched ADB targets, rotated wireless-debugging ports, stale reverse mappings, and applications that appeared to be running but were not actually ready. https://i.redd.it/6wdrxpymbmth1.gif ADB Ready keeps the complete workflow tied to one explicitly selected Android target—from device discovery and ports to app launch, verification, logs, screenshots, and recovery. Why it may be relevant here: • fully open source under the MIT License • runs locally and uses the real adb binary • no account, hosted service, telemetry, or model API key required • works as an ordinary CLI with stable JSON and NDJSON output • supports USB devices, emulators, wireless debugging, and remote ADB targets • supports Gradle, Expo, React Native, Flutter, Capacitor, and custom commands • optional MCP integration is available, but the core product has no AI dependency Quick start: npm install --save-dev adb-ready npx adb-ready dev Repository, documentation, and demo: https://github.com/Adam014/adb-ready or https://www.npmjs.com/package/adb-ready I would appreciate feedback on the project’s portability, packaging, documentation, and anything that would make it easier to trust as part of a daily development workflow. If it genuinely earns a place in your workflow, a GitHub star helps other developers discover it.   submitted by   /u/kindast1 [link]   [comments]