Key takeaways
- Play requirements cut across features, so they deserve their own spec instead of being scattered over feature specs.
- design.md is the right place to settle the upload key, versionCode scheme and build variants before Kiro touches Gradle.
- Steering files and hooks for AndroidManifest.xml and the dependency catalog keep the Data safety answers in step with the code.
- Account identity, the 14-day closed test for new personal accounts and the production application are Play Console work for a human.
Why the Play release needs its own spec
In Kiro, every feature gets a spec folder with three files: requirements, design and tasks. The agent drafts each one, you review it, and only then does it move on to the next. That works well for a login screen or a sync feature. Google Play's requirements, however, do not belong to any single feature. Signing, the target API level, the Data safety form and account deletion touch the whole app.
So create a dedicated spec – for example .kiro/specs/play-release/ – and run it through the same requirements, design and tasks flow. The result is a release plan that lives in the repository, survives team changes and is visible to the agent every time it works on the app.
requirements.md: what Google Play expects from the app
Write each Play rule as a user story with an acceptance criterion someone can verify on a phone or in a build log:
| Requirement | Acceptance criterion |
|---|---|
| The app ships as an Android App Bundle under Play App Signing | CI produces a signed .aab from bundleRelease; no APK is uploaded |
| The app targets Android 16 (API level 36) | targetSdk is 36 in the release build; the app was tested on an Android 16 device or emulator |
| Users can delete their account in the app and on the web | A "Delete account" screen works, and a public page accepts deletion requests without the app installed |
| Data collection is documented | A data inventory in the repository lists every data type, SDK and purpose used for the Data safety form |
| Digital goods use Google Play Billing | Upgrades go through Play Billing; no external checkout unlocks digital content |
| Runtime permissions are asked in context | The notification permission is requested after the user enables a feature that needs it, not at first launch |
The target API rule has applied to new apps and updates since August 31, 2026 – our guide to the target API level requirement explains the details. For the deletion page, see the Google Play account deletion requirement.
Talk to an AI Code Engineer about shipping your app to Google Play.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
design.md: settle signing, versions and variants first
The design document is where you stop the agent from improvising the parts that are hard to undo. Answer these questions in writing before any task runs:
- Keys. Play App Signing holds the app signing key at Google; you keep the upload key. Where does the upload keystore live (a password manager, the CI secret store), and who can access it? Gradle reads the values from environment variables – never from a file in the repository.
- Version codes. Every upload needs a higher
versionCode. Derive it from the CI build number so neither people nor agents have to remember it. - Variants. A staging and a production flavor keep test builds away from real data – and make sure the build in review talks to the production backend.
- Shrinking. If R8 minification is on, the mapping file is kept with each release so crash reports stay readable.
Add one sentence that matters more than it looks: "Never create a new keystore if one exists." An agent that generates a fresh upload key because it cannot find the old one leaves you with a key reset request in Play Console instead of an update.
tasks.md: an order that matches the Play Console
Kiro works through tasks in order, and the list can include steps a person has to do. Marking those clearly keeps the agent from trying to fake them:
1. Release build 1.1 Read upload key values from environment variables in build.gradle.kts 1.2 Add a CI job that runs tests and bundleRelease and stores the .aab 2. Compliance 2.1 Account deletion screen with confirmation and server-side deletion 2.2 Public deletion request page on the website 2.3 docs/data-inventory.md with data types, SDKs and purposes 3. Play Console (owner: human) 3.1 Create the app and enroll in Play App Signing 3.2 Upload the first bundle to the internal testing track 3.3 Start the closed test and recruit testers
Tasks in group 3 stay open until a person ticks them. That gives everyone – including the agent in later sessions – an honest view of where the release stands.
Steering and hooks for Gradle and the manifest
Put the build facts in tech.md: the Gradle wrapper commands, the JDK version, minSdk and targetSdk, and the test command. Then add a release steering file with fileMatch inclusion for AndroidManifest.xml, the module build.gradle.kts files and the version catalog. It should say, in short: do not lower targetSdk, do not add permissions without updating the data inventory, do not touch signing configuration.
Two agent hooks keep the Data safety form honest:
- When the manifest is saved, the agent compares declared permissions with
docs/data-inventory.mdand lists any mismatch. - When the version catalog or a dependency block changes, the agent checks whether the new library collects data – analytics, crash reporting, ads, attribution – and drafts the inventory update.
Hooks remind; they do not enforce. Keep a CI check that fails the build if targetSdk drops below 36. Our playbook on the Data safety form with AI agents shows how to turn the inventory into form answers.
The Play Console part no spec can automate
Some steps need a verified human or organization behind them:
- Developer account. Personal or organization account with identity verification; organizations need a D-U-N-S Number.
- Testing tracks. Upload to internal testing first, then move to a closed track. New personal accounts must have at least 12 testers opted in for 14 consecutive days before they can apply for production access – see Google's testing requirements and our closed testing guide.
- Pre-launch report. Read it after each closed-track upload. Crashes and accessibility warnings from real devices make good new tasks for Kiro.
- Store listing and forms. Data safety, content rating, target audience, privacy policy URL and the deletion link.
- Production. Apply for production access, then roll out in stages.
Our AI Code Engineers can take this part over: upload key and Play App Signing, a CI pipeline for signed bundles, the listing and Data safety answers, test planning and the conversation with Google – all in your own Play Console via the Android submission service. For the iPhone version, read Kiro app to the App Store.
Kiro Android release checklist
- A play-release spec exists with requirements, design and tasks reviewed by a person.
- design.md names where the upload key lives and forbids creating a new keystore.
- versionCode comes from the CI build number.
- The release build targets API level 36 and is checked in CI.
- Account deletion works in the app and through a public web page.
- docs/data-inventory.md matches the manifest, the dependencies and the Data safety form.
- Digital goods use Google Play Billing.
- Human-only Play Console tasks are marked and tracked in tasks.md.
- The closed test (if your account needs it) started with a build that is already stable.
Frequently asked questions
Can Kiro publish my app to Google Play?
Kiro can build the signed App Bundle and run an upload script with a service account you set up. It cannot create the Play Console account, complete identity verification, fill in the policy forms or apply for production access – those need you.
Should Play requirements go into every feature spec?
Only where a feature is directly affected – a payment spec should state Play Billing, a sign-up spec should include deletion. Cross-cutting rules such as signing, target API and the Data safety inventory work better in one release spec.
What if Kiro created a new keystore by mistake?
If the app is not on Play yet, delete the stray key and decide which one is the upload key. If it is live, do not upload with the new key – find the original, or request an upload key reset in Play Console. That is why the design document forbids new keystores.
Does the closed test apply to my account?
The 12-testers-for-14-days rule applies to personal developer accounts created after November 13, 2023. Organization accounts are not covered by it, but a closed test is still the best way to find problems before production.
Can you help us release our Kiro app on Android?
Yes – book a free call and we look at your project, your specs and your Play Console status together, then tell you honestly what is left and whether you need us for it.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.