Release is where mistakes become public. Agents can help prepare a release, but certain steps should stay firmly under human control.
What agents can safely assist with
Drafting release notes, updating version numbers, checking that the build passes, and summarizing changes since the last release are all low-risk, easily reviewed tasks.
Keep signing separate
App signing keys are among the most sensitive assets you have. They should never appear in the agent's environment or context. Perform signing in a controlled pipeline that the agent cannot modify.
Review changes carefully
Review diffs that affect permissions, manifests, network configuration, dependencies, and build scripts with extra care. These can change an app's security posture without changing visible behavior.
Use staged rollouts
Release gradually, watch crash and performance metrics, and be ready to halt. This limits the impact of any defect that slipped through.
Check compliance
Confirm that the app's declared data practices match what it actually does, and that new dependencies have acceptable licenses.
Keep an audit trail
Record who approved each release and what the agent changed, so you can investigate problems later.
Takeaway
Automation can speed up preparation, but approvals for signing and publishing should remain deliberate human decisions.
Continue with the book
Explore the full treatment, worked examples, and exercises in Agentic Android App Development.
Adapted from Agentic Android App Development, published by Choral Software. Article text and original examples © 2026 Choral Software. All rights reserved.