Shipping an iPhone App Without a Mac: Kotlin Multiplatform, a Cloud Mac and TestFlight
I develop on Windows and I do not own a Mac, but I wanted my small Android game 2048 on the App Store. It turns out you do not need a Mac on your desk, only one in the cloud for a few minutes per build. Here is the pipeline that took a build from my laptop to TestFlight and into App Store review within a day, and the traps I hit on the way. The shape of the project The game was already written in…
A Windows developer without a Mac can still ship an iOS app through a cloud-based solution using Kotlin Multiplatform, a cloud Mac, and TestFlight. The process involves building the project on a Windows machine, then transferring the build to a cloud Mac via GitHub Actions. The game's core logic is written in Kotlin, while the UI is implemented using Jetpack Compose and Compose Multiplatform.
The Android and iOS shells are thin wrappers around the shared code, with platform-specific functionality implemented separately. The cloud Mac runs on a GitHub Actions runner using a recent Xcode version, and the build process involves setting up the necessary dependencies and running Xcodebuild. The app is signed using an App Store Connect API key stored as a secret, allowing for cloud-managed signing and direct uploads to TestFlight.
The biggest limitation is that the Swift code must be kept small, as the cloud Mac cannot link the iOS framework or build the Swift app. Despite the need for macOS, the overall cost is minimal, with a single TestFlight run costing around six minutes of cloud Mac usage.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.