Your Flutter appFrom feature to release

You build new features with AI. MainPath prepares the path to iOS and Android builds – with tests, signing and a test version before you approve the next release.

Try changes through TestFlight and internal Play tests before choosing to publish

The feature is builtHere comes the app update

The prepared pipeline follows your code. You decide which version goes to the store.

  1. Check your changes

    Tests and checks run against your code. If a job fails, use its log with your AI agent to work through the change.

  2. Build iOS and Android

    The pipeline produces the builds. iOS is built on MainPath’s macOS machines; connected store accounts and signing credentials are part of the setup.

  3. Try it on devices

    With linked store accounts, test versions go to TestFlight and the internal Play track. Check the app’s flows there before publishing.

  4. Approve the version

    After testing, start the manual release step. Store submission follows this process; the respective store decides on any required approval.

You write the appThe release flow comes with it

Manage signing in the project

Apple credentials and Android signing are available to the pipeline. For an Android app already published on Google Play, import its original upload key.

Keep store content together

Descriptions, screenshots and release notes for each language stay with the project. The pipeline uploads the content you have prepared.

Add desktop when it fits

For configured Flutter desktop targets, the pipeline builds the appropriate installers. Check which platforms your code and plugins support in your project.

Does your app need an API?The backend can belong too

Your Flutter app and backend can live in the same MainPath project. The interface and API grow from a shared project foundation, with the appropriate build and deployment steps for each component.

  • Add a backend that fits your app, such as NestJS, Laravel or FastAPI
  • App and API remain separate components with their own build flows
  • You can also keep running an existing backend outside MainPath
Publishing backends

Before your first store updateThese details still matter

  • Your own developer accounts

    You provide Apple and Google accounts with the appropriate API access and connect them to the project.

  • Identifiers and signing

    Bundle ID, package name and signing must match the app. An existing Google Play app needs its original upload key.

  • Test on your target platforms

    One Flutter codebase does not replace device testing. Check permissions, native plugins and platform-specific features too.

  • Keep generated files intact

    Generated pipeline and environment files stay unchanged. Put your own values in documented custom files or MainPath configuration.

Your next Flutter featureWith a path to release

Start a Flutter project or let your agent check whether your existing app can be imported. Then keep building on the same project foundation.

Questions about Flutter CI/CD

Do we need our own Mac for the iOS pipeline?

Not for pipeline builds. MainPath provides macOS build machines. This is separate from your local development environment; local iOS development still follows Flutter and Apple’s requirements.

macOS build machines

Can we start with an existing Flutter app?

Yes, if the project is supported. Your AI agent checks the existing code and guides the import. For an app already in the stores, the existing identifiers and signing credentials must match.

Import an existing project

Does every push become a public app update?

No. With linked store accounts, the publishing flow first distributes builds to TestFlight and internal Play tests. You start the store release manually. Review and approval by the respective store remain separate.

Will every plugin then work on every platform?

No. Your Flutter app’s supported platforms and native features depend on your code, plugins and their configuration. MainPath prepares build and release flows for the targets configured in your project.

Can we distribute desktop versions too?

For configured desktop targets, the pipeline can build macOS, Windows and Linux packages. Signing, notarization and store access depend on the target platform and distribution route.

Publishing desktop applications

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab