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
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.
The project and the pipeline do different jobs. MainPath connects them without publishing a version before you are ready.
Each component gets the build and deployment steps it needs. A shared project does not mean releasing every part simultaneously without checking it.
Start with Flutter, Expo or a native app template. Add a backend and web interface to the same project when you need them.
Provide your developer accounts, app identifiers and the appropriate signing material. Import the original upload key for an existing Android app.
The pipeline tests and builds your code. With connected store accounts, iOS builds go to TestFlight and Android builds to the internal Play track.
Try the app and its connected services. Then start the manual release step. The relevant store decides whether the app is approved.
Manage store access inside your project. For an Android app that is already published, import its original upload key.
Edit descriptions, screenshots and release notes per language. The files are versioned in the app repository and uploaded when you publish.
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.
Create an app project and add the components it needs. Try the next version before publishing it.
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.
No. MainPath uses macOS build machines for the pipeline. You still need suitable test devices and the relevant developer access to try your app.
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.
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.
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.