Skip to content
All Claude Code plugins
Claude Code pluginLiveAndroid release automation

DroidForge

Automate every repetitive Android dev task — keystore creation, signing config, version bumping, Gradle version catalog management, new app scaffolding, and release checklists.

Built when the Android release checklist hit twelve manual steps at fleet scale. Encodes the entire Android release preparation layer — signing config generation, version management, Gradle catalog updates, pre-submission checklist — into repeatable commands. Manages 22+ Android apps in production under SudarshanTechLabs.

Claude Code pluginBashGradleAndroid

Why it exists

Running 22+ Android apps solo means the release checklist is the bottleneck — keystore generation, signing config, version bumping, Gradle catalog updates, and pre-submission verification used to eat half a day per shipping app. DroidForge encodes every step as a Claude Code command. The plugin is the same release engineer across every repo, so each app ships the same way without me re-remembering the sequence.

What's inside

  • Keystore + signing.properties scaffolding with safe defaults
  • versionCode / versionName bumps wired to config/version.properties
  • Gradle version catalog (libs.versions.toml) updates across modules
  • New app scaffolding — package, manifest, theme, Compose entry
  • Pre-submission checklist enforced before bundleRelease
  • Runs unchanged across 22+ apps in the SudarshanTechLabs portfolio

FAQ

Do I need to be using Claude Code to use DroidForge?

Yes. DroidForge is distributed as a Claude Code plugin and uses Claude's command system to drive Gradle and Android tooling.

Will it work on existing apps or only new ones?

Both. The release-lifecycle commands are project-agnostic and pick up your existing keystore.properties, signing config, and version catalog. New-app scaffolding is a separate command path.

Where are signing credentials stored?

Never in build files. DroidForge reads from local.properties or keystore.properties — both git-ignored — and never commits secrets.

Can I use it across many apps without reconfiguring per repo?

That's the design goal. The plugin runs unchanged across the 22+ apps in the SudarshanTechLabs portfolio.

Related across catalogs

Want a heads-up when DroidForge releases?

Subscribe via blog