App, API and web in one project
Choose native iOS and Android apps, Flutter or Expo, then add suitable backend and web components. Each gets its own build process.
You are building an iOS or Android app with AI. MainPath gives the app, backend and web administration a shared project foundation, with suitable tests, builds and release steps.
For example, a booking app: choose appointments on a phone, check the rules in an API and manage bookings on the web.
Choose native iOS and Android apps, Flutter or Expo, then add suitable backend and web components. Each gets its own build process.
The project pipelines test and build your components. Try new app features together with the API on Dev and in test builds.
Manage localized copy, screenshots and release notes in the project. The pipeline prepares uploads using your connected store credentials.
The app and backend live in related repositories in the same project. Your agent can work on both; you check whether the data and responses suit the app.
Which tasks belong in the app, the API or a web interface? Create the project from that plan, or have your agent check whether existing code is supported.
Choose a server for the API and add the required store credentials. Configure the database and other features to suit the backend.
Changes on main produce the relevant builds. Test the app against the Dev API and check important cases on real devices.
Release the backend and app in their respective steps. Design the API so that app versions already installed on users’ devices continue to work.
For TestFlight and the internal Play track, connect your Apple or Google developer accounts and the required technical credentials.
Add the required signing material. For an Android app that is already published, use the original upload key.
Login, API permissions and business rules belong in your application code. MainPath project roles control development access, not the login of your app’s users.
Imports require a supported stack. An existing backend can also keep running separately if its interface suits the app.
Start with a shared project foundation. Build with your AI agent and check how the app, API and web interface work together.
You can use native iOS and Android apps, Flutter or React Native with Expo. Backend options include NestJS, FastAPI and Laravel. Choose the relevant components in the project.
Yes, if its stack is supported. Your agent checks the existing code first and guides the import. Unsupported frameworks are not automatically converted into a different stack.
No. You can start by building just the app with MainPath while keeping an existing backend or website. Agree on the interfaces and a clear process for their respective releases.
No. iOS builds run on macOS build machines in the pipeline. This is not an interactive Mac workspace and does not replace your test devices or developer accounts.
No. Components have their own appropriate build and approval steps. With connected store accounts, app test builds go to TestFlight or the internal Play track after changes on main. For a public store release, you start the manual release step; Apple or Google decides the outcome of the store review.