Flutter Store Deployment Kit

Ship your Flutter app to App Store + Google Play from terminal with AI agents. No Xcode. No Play Console. No CI/CD pipeline. Two commands.

What is this?

A set of templates that let any AI agent (Devin, Claude Code, Cursor, Windsurf) deploy your Flutter app to both stores by reading a single markdown file.

Instead of opening Xcode, archiving, opening Transporter, dragging the IPA, opening Play Console, creating a release, and uploading the AAB — you tell your AI agent "ship version 1.0.1 to both stores" and it does the rest.

What's included

File	Purpose
STORE_DEPLOYMENT.md	Single source of truth — credentials, commands, error recovery
SETUP.md	15-minute setup guide
AGENTS.md.template	Pointer file so agents know where to look

How it works

1. You store credentials on your machine (API keys, service account JSON)
2. STORE_DEPLOYMENT.md references those paths + has all build/upload commands
3. Your AI agent reads the file and executes the full deploy flow
4. No secrets leave your machine — the agent uses official CLI tools locally

Requirements

• Flutter SDK
• Xcode (macOS, for iOS builds)
• fastlane (brew install fastlane)
• App Store Connect API key
• Google Play service account JSON

Quick start

# 1. Copy STORE_DEPLOYMENT.md into your repo
cp STORE_DEPLOYMENT.md your-project/docs/STORE_DEPLOYMENT.md

# 2. Copy the AGENTS.md template (or merge with existing AGENTS.md)
cp AGENTS.md.template your-project/AGENTS.md

# 3. Follow SETUP.md to fill in your credentials
# 4. Tell your AI agent: "Ship version 1.0.0 to both stores"

What it looks like in practice

You're in your terminal. You just finished a feature. You say to your AI agent:

"Ship version 1.2.0 to both stores."

Your agent reads STORE_DEPLOYMENT.md and does the rest:

✓ Bumping version to 1.2.0 in pubspec.yaml
✓ Building AAB: flutter build appbundle --release
  → build/app/outputs/bundle/release/app-release.aab (48.2 MB)
✓ Building IPA: flutter build ipa --release
  → build/ios/ipa/yourapp.ipa (52.1 MB)
✓ Uploading to Google Play...
  → fastlane supply --aab app-release.aab --track production
  → ✓ Uploaded. Release 1.2.0 is now live on Play Store.
✓ Uploading to App Store...
  → xcrun altool --upload-app --type ios --file yourapp.ipa
  → ✓ Uploaded. Build 1.2.0 is now in App Store Connect.
✓ Done. Both stores updated. Total time: 4 minutes 12 seconds.

No Xcode. No Android Studio. No Play Console. No CI/CD YAML. Just a markdown file and one command.

The pattern: agent-readable infrastructure

This kit demonstrates a broader pattern: you don't need to build new tools for AI agents — you need to make existing tools readable.

xcrun altool and fastlane supply are already CLI tools. The reason we use Xcode and Play Console is that remembering CLI flags and credential paths is annoying for humans. But for an AI agent, reading a file and filling in variables is zero friction.

This pattern works for any repeatable workflow:

• Database migrations
• Server provisioning
• Incident response
• Content publishing
• Data pipelines

If a human can do it by following instructions, an agent can do it by reading them.

License

MIT — use it, fork it, sell it. Attribution appreciated but not required.

---

Made by Eidetic Works — building AI agents that ship real things.