Skip to main content

Claude Code and Flutter: One Codebase, Two Stores

By the OnlineAppCreator editorial team4 min read

Short answer

Flutter lets Claude Code maintain one Dart codebase for iOS and Android, and the agent can verify most work with flutter analyze, flutter test and widget tests on any operating system. Store releases still split by platform: iOS builds need macOS and Xcode, Android bundles need an upload key, and each store has its own listing, privacy declarations and review process.

On this page
  1. Project setup that keeps the agent consistent
  2. The testing loop
  3. Platform folders still matter
  4. Releasing to both stores
  5. Where releases usually stall

Flutter is a good fit for agentic development. Dart is strongly typed, the analyzer is strict and fast, and widget tests run without a device. That gives Claude Code a short, reliable feedback loop: write code, run flutter analyze, run flutter test, fix. One codebase covers both phones, so every improvement the agent makes reaches both stores. The two stores, however, remain two separate processes, and that is where most of the release effort goes.

Project setup that keeps the agent consistent

Create the project with flutter create --org com.yourcompany your_app so that bundle and package identifiers are correct from the start. Then make the decisions an agent should not improvise. In CLAUDE.md, record the state management approach (Riverpod, Bloc or Provider, but only one), the routing package, the folder structure (feature-first works well for agents because a task maps to a folder), the lint rules in analysis_options.yaml, and the commands to run. Tell the agent to add packages only with flutter pub add and to explain each new package in the pull request, including whether it uses native code and what data it collects.

Pin the Flutter version with a version manager such as FVM or document the exact version. Agents tend to suggest APIs that changed between releases, and a pinned version gives them, and you, a fixed reference.

The testing loop

Ask Claude Code to write widget tests for every screen, covering empty, loading, error and success states, and golden tests for important layouts if your team maintains them. Integration tests with the integration_test package run on a simulator or emulator and are worth having for the core flows: sign-up, purchase, the main task of the app. Claude Code can start an emulator, run flutter run or the integration tests, and capture screenshots to check the result visually.

Test platform differences deliberately. Back navigation on Android, safe areas on iPhones with a notch or Dynamic Island, keyboard handling and permission dialogs all behave differently. These are exactly the details a generator overlooks and a reviewer notices.

Platform folders still matter

A Flutter app is not entirely Dart. The ios/ and android/ folders hold configuration that the stores care about: Info.plist purpose strings, the iOS privacy manifest, entitlements, the Android manifest, Gradle settings and the targetSdk. Plugins add their own native dependencies and sometimes their own permissions and privacy manifests. Make it a rule that any change in these folders gets human review, and ask Claude Code to summarize what each plugin adds to the native projects.

TaskiOSAndroid
Release build commandflutter build ipaflutter build appbundle
Build machinemacOS with XcodemacOS, Linux or Windows
SigningDistribution certificate and provisioning profileUpload key, with Play App Signing
Beta testingTestFlightInternal, closed and open testing tracks
Privacy declarationsPrivacy manifest and privacy nutrition labelsData safety form
Account cost (at the time of writing)USD 99 per yearUSD 25 one-time

Push notifications deserve a separate note. On iOS they require the push capability on the App ID, an APNs key and a permission prompt at a sensible moment; on Android 13 and later, apps must request the notification permission at runtime. Agents tend to implement the Dart side and forget one of the platform steps, so add both to your release checklist and test delivery on real devices for each platform, not only in debug builds. The same applies to deep links, which need associated domains on iOS and verified app links on Android.

Releasing to both stores

  1. Set the version in pubspec.yaml as 1.0.0+1; the part after the plus sign is the build number and must increase with every upload.
  2. Prepare icons and splash screens for both platforms, for example with a launcher icon generator package, and check the results on devices.
  3. Build the Android App Bundle with your upload key injected from environment variables, and upload it to internal testing in the Play Console.
  4. On a Mac or in macOS CI, build the IPA and upload it to App Store Connect, then distribute it through TestFlight.
  5. For new personal Google Play accounts, run the closed test that is currently required: at least 12 testers for 14 days.
  6. Complete both listings, the privacy labels and the Data safety form, and submit for review.

Many teams automate steps three and four with Fastlane; see Fastlane plus Claude Code for a pipeline setup. Signing details are in code signing and certificates for AI-built apps.

Where releases usually stall

The code is rarely the blocker. Delays come from organization enrollment with Apple, the Google Play closed test, missing privacy information, and rejections for incomplete features or missing demo accounts. Plan these in parallel with development, not after it. AppSubmitter.io runs this publishing process for both stores, including accounts, listings, screenshots, privacy forms and communication with reviewers, until the app is live. If your team is new to agent-driven Flutter work, the agentic coding workshops by neoOutput cover task design and review habits with real codebases. For a comparison with the JavaScript route, read Codex and React Native with Expo.

Frequently asked questions

Can Claude Code build the iOS version of a Flutter app on Linux?

It can write and test the Dart code on Linux, but the iOS release build requires macOS and Xcode, either locally or in macOS CI.

Is Flutter or React Native better for AI agents?

Both work well. Flutter offers a strict analyzer and fast widget tests; React Native with Expo offers TypeScript and hosted builds. Choose based on your team's existing skills and libraries.

Do Flutter plugins affect App Store privacy requirements?

Yes. Plugins can bring native SDKs that collect data or use APIs that require privacy manifest declarations. Review each plugin's native footprint before release.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.