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.
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.
Add your store accounts and the signing material your app needs. The pipeline can then sign and upload your builds.
With connected store accounts, iOS builds go to TestFlight and Android builds to the internal Play track. Try your update there.
Maintain descriptions, screenshots and release notes for each language in your project. The listing stays with the version of your app.
You start the manual release step. The pipeline submits to Apple or promotes the Android build to the production track.
Maintain copy and screenshots in MainPath. The metadata is versioned in your app repository and uploaded when you publish.
Import the original upload key if your app is already on Google Play. Your next builds use the correct key.
For supported desktop projects, the pipeline creates installable packages for macOS, Windows and Linux that you can distribute as downloads.
Windows projects can connect to the Microsoft Store. Add your Partner Center access and signing configuration to use it.
Apple and Google accounts and the required technical access are still needed. Store-provider fees are not included in MainPath.
Assign the right credentials to your project. An existing Android app needs its original upload key.
Store copy, privacy information and a demo account where needed must match the app. You check the content before release.
MainPath prepares builds, signing and uploads. Apple, Google or Microsoft decides whether your app is approved.
Start an app project and connect your store accounts. Test the next version on your devices before submitting it for review.
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.
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.
Supported projects can be imported. Your agent checks the existing code first. For an existing Android app, you also import its original upload key.
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.