Your app on the goWith the API it needs

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.

Test on devices before approving a store release

One ideaSeveral parts working together

For example, a booking app: choose appointments on a phone, check the rules in an API and manage bookings on the web.

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.

Check changes before users see them

The project pipelines test and build your components. Try new app features together with the API on Dev and in test builds.

Prepare the store presence too

Manage localized copy, screenshots and release notes in the project. The pipeline prepares uploads using your connected store credentials.

Your agent keeps buildingKeep the interface in view

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.

  • The API handles data and business rules on the server.
  • The app and a web administration interface use the agreed APIs.
  • Versions and changes remain traceable in Git history.
Set up the backend and environments

From the first promptTo a tested product flow

  1. Split the product into components

    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.

  2. Connect the backend and accounts

    Choose a server for the API and add the required store credentials. Configure the database and other features to suit the backend.

  3. Try the flow together

    Changes on main produce the relevant builds. Test the app against the Dev API and check important cases on real devices.

  4. Approve the versions deliberately

    Release the backend and app in their respective steps. Design the API so that app versions already installed on users’ devices continue to work.

Before the first releaseAgree on four things

  • Your own developer accounts

    For TestFlight and the internal Play track, connect your Apple or Google developer accounts and the required technical credentials.

  • Signing in the project

    Add the required signing material. For an Android app that is already published, use the original upload key.

  • Login and data access

    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.

  • Check existing code first

    Imports require a supported stack. An existing backend can also keep running separately if its interface suits the app.

Your next app featureWith the backend it needs

Start with a shared project foundation. Build with your AI agent and check how the app, API and web interface work together.

Questions about apps and backends

Which app and backend stacks does MainPath support?

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.

Can I bring an existing app or API?

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.

Bring an existing project

Do we have to replace existing websites or backends?

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.

Do we need our own Mac for iOS pipeline builds?

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.

Do the app and backend go live together with one click?

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.

Git workflow and releases

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