← Back to blog

Publishing Native Apps for iOS and Android

The 1 August 2026 release adds native Swift and Kotlin apps and more settings for publishing macOS applications.

AppsReleases
Publishing Native Apps for iOS and Android

The first shared release often reveals where an app’s credentials live: an Android signing key in a downloads folder, a certificate in a colleague’s keychain and an app identifier in a note. When somebody else takes over publishing, those details need to be collected first.

The 1 August 2026 release expands the available publishing paths in MainPath and keeps the credentials for them in one place.

Swift and Kotlin in the project wizard

Native iOS apps in Swift and native Android apps in Kotlin are available as project types alongside Flutter and Expo. They accommodate existing native projects as well as apps that work closely with platform APIs.

When you choose a native stack, MainPath suggests matching tools: Xcode for iOS, and Java or Kotlin for Android. Shared libraries can be published as Dart, NPM or other supported packages. At the time of this release, Composer, Maven and Kotlin packages were announced as further package types to come.

Choose macOS signing and distribution separately

An internally distributed app needs a different publishing path from an app in the Mac App Store. Four macOS settings can therefore be configured independently: Developer ID signing, notarisation, Mac App Store distribution and a public download.

An internal tool can be signed, notarised and offered as a download. Mac App Store distribution can also be configured for the same project. For Windows, the Microsoft Store and Azure Artifact Signing are available as connections.

  • App StoreApple releases with prepared metadata and assets.
  • Google PlayPlay Store listings populated automatically.
Powered by Fastlane
The pipeline prepares builds for the App Store and Play Store. Release approval and store review remain part of publishing.

Select existing apps from a linked store account

When you link an App Store or Play Store account, MainPath loads the apps already listed there. You can then select the iOS bundle identifier and Android package name from a list, without retyping them, and check them against the store entry.

Imported Android upload keystores can also be downloaded again, keeping the stored key available if the local copy is missing. Updates to an existing Android app still require the appropriate key.

Let the team trigger builds and releases

Builds run in CI, with macOS machines available for iOS. The workflow does not need a permanently configured Mac in the office. Publishing runs through Fastlane and can be triggered by people with the appropriate permissions.

A successful build does not mean the app is publicly available. Approval to release to the store is a separate step, and review by Apple or Google remains part of the respective store process. The guide to publishing apps explains the steps from test versions to release approval.

Set up the publishing path your app needs

The native project types extend the existing options for Flutter and Expo. For a Flutter project, see Flutter CI/CD. The app store automation page explains how store accounts, builds and approvals fit into the overall workflow.

Prepare your app for its first release

Choose the project type, then check which store accounts, identifiers and signing keys your release needs.

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