Release a Kotlin Multiplatform App to the App Store and Google Play

Short answer: Kotlin Multiplatform lets you share business logic and often UI between Android and iOS, but the iOS release still runs through Xcode, Apple signing and App Store review. appsubmitter.io sets up the build pipeline for both platforms, handles signing and submission in your own accounts and helps with rejections.

On this page

The short answer: shared code, two very different release paths

Teams that adopt Kotlin Multiplatform usually come from Android. Publishing to Google Play feels familiar, but the iOS side brings a second world: the shared Kotlin module compiles into a framework, Xcode builds the app, Apple certificates and provisioning profiles must match, and App Store review applies its own rules. Many KMP projects work well on the developer machine and stall right before the first iOS release.

appsubmitter.io closes that gap. AI-assisted checks look at build configuration, metadata and privacy declarations, and human store experts set up CI/CD for iOS and Android, sign the builds and submit them in your own developer accounts. Your Android-first team keeps working in Kotlin while the release side becomes routine.

Where KMP releases typically break

  • The Kotlin/Native framework build is slow or fails on CI runners because of memory limits, missing Xcode versions or cache problems
  • Signing works locally but not in the pipeline because certificates and profiles live on one laptop
  • Dependencies pulled through CocoaPods or Swift Package Manager are pinned differently on CI and locally
  • Privacy manifests and required reason APIs are missing for iOS, which can block uploads; check the current requirement
  • Version and build numbers drift between Gradle and Xcode, so store uploads get rejected as duplicates
  • Compose Multiplatform screens behave differently on iOS, for example keyboard handling, safe areas or back navigation, and reviewers notice

Need a hand? appsubmitter.io helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.

A dependable release pipeline for Kotlin Multiplatform

With appsubmitter.io this pipeline runs in your repository and accounts, so you own every secret and every listing. Releases turn from a heroic manual effort into a repeatable step that anyone on the team can trigger.

  1. Fix toolchain versions for Kotlin, Gradle, Xcode and JDK, and document them in the repository
  2. Separate shared module builds from platform app builds and cache the Kotlin/Native output
  3. Move iOS signing into the pipeline with managed certificates stored securely, not on a single machine
  4. Generate a single version source so Android versionCode and iOS build numbers stay aligned
  5. Upload automatically to TestFlight and the Google Play internal testing track after each merge
  6. Promote tested builds to production with prepared metadata, screenshots and privacy details

When the shared code itself needs help

Some KMP projects need more than a release pipeline. Platform-specific bugs, a half-finished Compose Multiplatform migration or iOS screens that were never tested on real devices are common. apprat.io adds an agentic coding team where AI Code Engineers review every change, test on physical iPhones and Android devices and fix what blocks the release, combining AI speed with human responsibility.

If your team wants to build this competence in-house, neooutput runs workshops and 1:1 consulting on agentic coding with Claude Code, OpenAI Codex and Cursor, which pays off especially in multiplatform codebases where an AI assistant can propagate a change across shared and platform code consistently.

Accounts and costs

For a KMP app you need an Apple Developer Program membership at 99 USD per year, a Google Play developer account at 25 USD one-time, and a macOS build environment for the iOS part, either your own machines or a hosted CI service. Plan time for the first App Store review, which tends to raise more questions than later updates, and keep a short note about any login or demo mode ready for reviewers.

Frequently asked questions

Can I publish a Kotlin Multiplatform app to the App Store without a Mac?

Not directly. The iOS app must be built and signed with Xcode on macOS. You can avoid owning a Mac by using a hosted CI service with macOS runners. appsubmitter.io sets up such a pipeline so your team can trigger iOS builds and uploads from any machine.

Does Apple treat KMP or Compose Multiplatform apps differently in review?

No. Apple reviews the resulting app, not the framework. What matters is native behavior, stability, privacy declarations and meaningful functionality under Guideline 4.2 Minimum Functionality. Compose Multiplatform screens should therefore feel at home on iOS, including navigation, keyboard handling and accessibility.

How long does it take to set up a KMP release pipeline?

It depends on the project's state. A clean repository with working local builds can be automated quickly, while projects with manual signing, mixed dependency managers or unstable builds need cleanup first. We start with an assessment and tell you what is needed before the first automated release.

Combine it with

Talk to an AI Code Engineer, free of charge

Tell us about your project. In a short call we map out the fastest path, from workshop to App Store launch or a full AI-native product.

No obligation. English or German. jocapps, ISO 27001 and ISO 9001 certified. 24/7 call support: +49 761 519 751 50

Book a call for free

Related solutions

Book a call for free