Your app and APIOne shared workflow

You are building an app with AI that needs more than a screen. MainPath brings app, backend and web interface into one project, with the right builds, test distribution and a deliberate step for releasing to production.

Try test builds on real devices before approving the version for publication.

Keep the product togetherFollow each release step

The project and the pipeline do different jobs. MainPath connects them without publishing a version before you are ready.

Inside the project

  • Create the mobile app, backend and web interface your product needs
  • Manage the repositories, configuration and access for each component
  • Keep building with your AI agent on a prepared project foundation

Along the release workflow

  • Check changes automatically and build the relevant components
  • Distribute app test builds and deploy web services to Dev
  • Approve the tested version for production or store submission

Each component gets the build and deployment steps it needs. A shared project does not mean releasing every part simultaneously without checking it.

From your code changeto the next app version

  1. Choose the project components

    Start with Flutter, Expo or a native app template. Add a backend and web interface to the same project when you need them.

  2. Connect your store accounts

    Provide your developer accounts, app identifiers and the appropriate signing material. Import the original upload key for an existing Android app.

  3. Check and try the change

    The pipeline tests and builds your code. With connected store accounts, iOS builds go to TestFlight and Android builds to the internal Play track.

  4. Start the release yourself

    Try the app and its connected services. Then start the manual release step. The relevant store decides whether the app is approved.

Ready for the app uploadManaged with your project

Sign with the right key

Manage store access inside your project. For an Android app that is already published, import its original upload key.

Maintain store content together

Edit descriptions, screenshots and release notes per language. The files are versioned in the app repository and uploaded when you publish.

Your agent changes the codeThe pipeline checks the result

A new AI-built feature is a useful next version when the existing parts still work. Tests and builds make problems visible before you approve the release.

  • Follow jobs and error messages in GitLab
  • Try app builds and backend changes deliberately
  • Keep production approval as a separate step
App publishing in detail

Your next app updateWith the whole product in view

Create an app project and add the components it needs. Try the next version before publishing it.

Questions about mobile CI/CD

Which app technologies can I use?

MainPath offers prepared projects for Flutter, Expo and native iOS and Android apps. Backend services and a web interface can belong to the same project.

Do I need my own Mac for iOS pipeline builds?

No. MainPath uses macOS build machines for the pipeline. You still need suitable test devices and the relevant developer access to try your app.

macOS build machines

Do I need my own store accounts?

Yes. To distribute through TestFlight and the internal Play track, connect your Apple or Google developer accounts and provide the necessary technical access. Without a linked store account, the pipeline distributes debug builds through Firebase App Distribution.

Store access and app publishing

Does every push go straight to the public store?

No. Test distribution and store release are separate steps. You start the manual release step; Apple or Google then reviews the submitted version through its store processes. MainPath does not guarantee approval.

Can I edit the generated pipeline myself?

MainPath maintains and overwrites the generated .gitlab-ci.yml. Use the documented configuration options or contact support for additional automation. Do not edit the generated file directly, including when fixing a failure.

Pipeline stages and manual jobs

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