xcframework-distribution

Distribute Kotlin Multiplatform Mobile modules to iOS via XCFramework, CocoaPods, or Swift Package Manager.

1|Updated Apr 24, 2026

Search Tags:#ios #distribution #spm #kmm #cocoapods #xcframework

Ready to run

npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill xcframework-distribution

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: xcframework-distribution
Source: https://github.com/dimitriRemoiville/cc-mobile/tree/main/plugins/cc-mobile-kmm/skills/xcframework-distribution
Command: npx skills add https://github.com/dimitriRemoiville/cc-mobile --skill xcframework-distribution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies distributing the shared Kotlin Multiplatform Mobile (KMM) module to iOS by offering XCFramework, CocoaPods, and Swift Package Manager distribution options, ensuring consistent consumption across projects.

Core Features & Use Cases

Direct XCFramework: Package and embed a static XCFramework for fast, framework-based iOS consumption in mono-repo setups.
CocoaPods integration: Generate a podspec and integrate with existing CocoaPods workflows for legacy iOS projects.
Swift Package Manager: Wrap the XCFramework with a binaryTarget for clean, modern iOS integration and versioned releases.
Versioning & interop: Provide checksums, releases, and interop hygiene guidance to keep iOS consumers in sync with Kotlin API changes.

Quick Start

Select a distribution mode (XCFramework, CocoaPods, or SPM) and follow the corresponding build steps to package and publish the Shared KMM artifact.

Frequently Asked Questions about xcframework-distribution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I distribute a Kotlin Multiplatform Mobile module to iOS consumers?▼

To distribute a Kotlin Multiplatform Mobile module to iOS, you can package it as an XCFramework, generate a CocoaPods podspec, or wrap it as a Swift Package Manager binaryTarget. This ensures consistent consumption across iOS projects.

What is the best way to integrate a KMM shared module into an existing CocoaPods workflow?▼

The best way to integrate a KMM shared module into existing CocoaPods workflows is to generate a podspec from the shared Kotlin code. This allows legacy iOS projects to consume the module using standard CocoaPods dependency management.

Can I use Swift Package Manager to distribute an XCFramework built from Kotlin Multiplatform?▼

Yes, you can use Swift Package Manager to distribute an XCFramework built from Kotlin Multiplatform by wrapping the binary as an SPM binaryTarget. This approach provides clean, modern iOS integration and supports versioned releases.

How does XCFramework distribution handle versioning and checksums for iOS consumers?▼

XCFramework distribution handles versioning and checksums by generating release metadata and validating artifacts. This ensures iOS consumers stay in sync with Kotlin API changes and maintain interop hygiene across mono-repo and multi-project setups.

When should I use direct XCFramework packaging over Swift Package Manager for KMM iOS distribution?▼

You should use direct XCFramework packaging for fast, framework-based iOS consumption in mono-repo setups, while Swift Package Manager is better suited for clean, modern integration requiring versioned binary releases across multiple projects.

Does KMM iOS distribution support both mono-repo and multi-project setups?▼

Yes, KMM iOS distribution supports both mono-repo and multi-project setups. It applies to iOS projects that depend on the shared module and provides specific build scripts and configurations for direct XCFramework, CocoaPods, or SPM integration.