Your app is builtNext comes the release

You are building your app with AI. MainPath brings test builds, signing and store listings into one workflow, so you can try your update and then choose when to submit it.

Test on real devices first. Then approve submission to the store.

One workflow for your updateFrom access to submission

  1. Connect store access

    Add your store accounts and the signing material your app needs. The pipeline can then sign and upload your builds.

  2. Test on a device

    With connected store accounts, iOS builds go to TestFlight and Android builds to the internal Play track. Try your update there.

  3. Update the listing

    Maintain descriptions, screenshots and release notes for each language in your project. The listing stays with the version of your app.

  4. Approve submission

    You start the manual release step. The pipeline submits to Apple or promotes the Android build to the production track.

The store listingBelongs with your project

Maintain copy and screenshots in MainPath. The metadata is versioned in your app repository and uploaded when you publish.

  • Descriptions and release notes for each language
  • Manage store images alongside the app
  • Follow changes in the repository
Explore store metadata

For your next releaseThe pieces you need

Keep shipping an existing Android app

Import the original upload key if your app is already on Google Play. Your next builds use the correct key.

Distribute beyond the stores

For supported desktop projects, the pipeline creates installable packages for macOS, Windows and Linux that you can distribute as downloads.

Include Windows

Windows projects can connect to the Microsoft Store. Add your Partner Center access and signing configuration to use it.

What you provideWhat the stores decide

  • Your own developer accounts

    Apple and Google accounts and the required technical access are still needed. Store-provider fees are not included in MainPath.

  • The correct signing material

    Assign the right credentials to your project. An existing Android app needs its original upload key.

  • Complete information

    Store copy, privacy information and a demo account where needed must match the app. You check the content before release.

  • Review by the store

    MainPath prepares builds, signing and uploads. Apple, Google or Microsoft decides whether your app is approved.

Your next updateA clear way to release

Start an app project and connect your store accounts. Test the next version on your devices before submitting it for review.

Questions about store releases

Is a test build already in the public store?

No. With connected store accounts, the pipeline makes iOS builds available in TestFlight and Android builds in the internal Play track. Submission or promotion to production is a separate manual step.

Publishing apps

Do I need my own Mac for pipeline builds?

Not for iOS pipeline builds. MainPath uses macOS build machines. You still need developer accounts, store credentials and the devices you use to test your app before submission.

Can we keep working on an app that is already published?

Supported projects can be imported. Your agent checks the existing code first. For an existing Android app, you also import its original upload key.

Import an Android upload key

Are submissions approved automatically?

No. Each store still carries out its own review. The prepared build, signing and upload steps are automated. Complete metadata and a tested release build remain your responsibility.

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