# swift-package-manager A tool for managing Swift source-code distribution, dependencies, versioning, compilation, and linking. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Swift 6.4 unifies building across Linux, macOS, Windows DevFeed: [Swift 6.4 unifies building across Linux, macOS, Windows]() Original publisher: [Read original article]() Author: Joab Jackson Published: 2026-09-17T04:27:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [Swift](), [swift-package-manager](), [Development](), [Linux](), [macOS](), [Windows]() Tags: [build](), [cross-platform-development](), [devops](), [linux](), [macos](), [open-source](), [programming-languages](), [swift](), [swift-6-4](), [swift-package-manager](), [windows]() ### AI overview Swift 6.4 makes Swift Build the default engine for the Swift Package Manager, with building unified across Linux, macOS, and Windows. ### Source excerpt Swift Build is now the default engine for the Swift Package Manager ## CocoaPods Deprecation Notice for OpenTelemetry Swift DevFeed: [CocoaPods Deprecation Notice for OpenTelemetry Swift]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-20T14:05:37Z Content type: release Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [cocoapods](), [Swift](), [swift-package-manager](), [migration](), [Package manager](), [maintenance](), [Maintainers]() Tags: [cocoapods](), [maintenance](), [migration](), [opentelemetry](), [release](), [releases](), [swift](), [swift-package-manager]() ### AI overview OpenTelemetry Swift maintainers plan to deprecate CocoaPods support for the opentelemetry-swift and opentelemetry-swift-core pods as CocoaPods moves into maintenance mode. Swift Package Manager is the recommended installation method, and existing CocoaPods users are encouraged to plan migration. ### Source excerpt As it was announced via CocoaPods Support Plan and via CocoaPods Spec Repository, CocoaPods is transitioning their project to maintenance mode, and cocoapods trunk is going to be read-only in a few months. The OpenTelemetry Swift maintainers are planning to deprecate CocoaPods support for all the pods published under opentelemetry-swift and opentelemetry-swift-core. Swift Package Manager (SPM) is now the recommended and preferred installation method for all new integrations. We encourage existing CocoaPods users to begin planning a migration to SPM. ## Migrating a Flutter Application from CocoaPods to Swift Package Manager DevFeed: [Migrating a Flutter Application from CocoaPods to Swift Package Manager]() Original publisher: [Read original article]() Author: iamgirya (Яндекс) Published: 2026-07-13T07:01:51Z Content type: tutorial Language: ru Sources: [Яндекс - Как мы делаем Яндекс / Статьи]() Topics: [Flutter](), [cocoapods](), [swift-package-manager](), [iOS](), [Dart](), [macOS](), [Package manager]() Tags: [cocoapods](), [dart](), [flutter](), [ios](), [ios-development](), [macos](), [swift](), [swift-package-manager](), [swiftpm]() ### AI overview A practical guide to migrating Flutter applications from CocoaPods to Swift Package Manager. It covers dependency-graph analysis, plugin migration, dependency resolution, incremental migration, duplicate transitive dependencies, and successful iOS or macOS builds, including scripts for analysis and plugin conversion. ### Source excerpt Flutter активно движется в сторону Swift Package Manager (SPM) и, как и весь Swift-мир, постепенно отказывается от CocoaPods. Сам Flutter описывает миграцию в два шага: включить флаг flutter config --enable-swift-package-manager и запустить сборку. Если после этого приложение собирается и в консоли появляется предложение deintegrate CocoaPods -- вы счастливчик. Если нет, добро пожаловать под кат. Привет! Меня зовут Даниил Гиренко, я Flutter-разработчик в Яндекс Про. Проект по переводу нашего супераппа с CocoaPods на Swift Package Manager оказался одним из самых сложных и долгих в моей карьере программиста. Весь мой пережитый ужас опыт я решил выразить в этой статье, чтобы решившиеся на миграцию разработчики (или агенты) понимали, какие подводные камни их ждут. Буду рад, если ваш проект займёт недели, а не месяцы, как у меня. В этой статье -- полноценный гайд по миграции любого Flutter-приложения. Разберём граф зависимостей, научимся мигрировать плагины, зарезолвим зависимости и доберёмся до успешного билда. Внутри есть готовые скрипты для анализа и автоматического перевода плагинов, множественные нюансы миграции и рассказы о моих костылях. Читать далее ## Ship It Right: A Swift Package Quality Checklist. Part 1 of 3. DevFeed: [Ship It Right: A Swift Package Quality Checklist. Part 1 of 3.]() Original publisher: [Read original article]() Author: Oleksii Kolomiiets Published: 2026-01-05T08:49:11Z Content type: tutorial Language: en Sources: [Snapp Mobile - Medium]() Topics: [Swift](), [Documentation](), [swift-package-manager](), [GitHub Actions](), [Open Source](), [Automation](), [Code]() Tags: [automation](), [build](), [documentation](), [github-actions](), [guides](), [ios-development](), [open-source](), [swift](), [swift-package](), [swift-package-manager](), [tests]() ### AI overview This tutorial presents a checklist for turning internal Swift Package Manager packages into polished public repositories. Part 1 focuses on documentation and README design, including installation instructions, usage examples, badges, links to full documentation, and licensing, while also introducing quality automation, community infrastructure, and discoverability. ### Source excerpt I still remember the moment I decided to open-source my first Swift Package Manager plugin. The code worked perfectly in our internal projects at Snapp, but making it public-ready? That was a different story. I spent the next week adding DocC documentation, setting up GitHub Actions CI, writing example apps, and addressing edge cases I'd been ignoring because "it worked for us". Photo by Vooglam Eyewear on UnsplashThis series is for Swift developers turning internal packages into polished public repositories -- covering documentation, quality, and community setup. Here's the thing: most developers know how to write good code. But there's a massive gap between "code that works" and "a repository that welcomes users and contributors." That gap includes: Documentation that assumes zero context -- Your README.md makes sense to you, but will it help someone discovering your project at 2 AM? Quality automation -- Are you manually checking code style, or does your CI catch issues before they reach main? Community infrastructure -- When someone wants to contribute, is the path clear or confusing? Discoverability -- Great code that nobody knows about might as well not exist. I learned these lessons by studying successful repositories, discussing best practices with experienced coworkers, and developing my own sense of what makes a project polished versus what might fall short. Let's start with the most visible part of any repository -- the README. README: Keep It ConciseREADME is the door, not the whole house. Follow a simple rule: the README should answer three questions: What does this do? How do I install it? Where can I learn more? What Belongs in a README 1. Title and One-Line Description -- make it crystal clear what this is. # SwiftFormatLintPlugin A Swift Package Manager plugin that integrates swift-format linting and formatting into your build workflow. 2. Key Badges -- status, version, license, supported platforms etc. [![Tests](https://github.com/oleksiikolomiietssnapp/Me ## KMMBridge 1.2.1 Released - Kevin Schildhorn DevFeed: [KMMBridge 1.2.1 Released - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2025-02-04T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [cocoapods](), [releases](), [swift-package-manager](), [gradle-plugin](), [iOS]() Tags: [cocoapods](), [gradle-plugin](), [ios](), [kmmbridge](), [kotlin-multiplatform](), [release](), [spm](), [swift-package-manager](), [xcode]() ### AI overview KMMBridge 1.2.1 adds support for publishing Kotlin Multiplatform framework binaries as GitHub Releases for CocoaPods integration. It also improves CocoaPods build error logging. ### Source excerpt KMMBridge is a Gradle plugin that publishes Kotlin Multiplatform Xcode Framework dependencies for Swift Package Manager and CocoaPods. The 1.2.1 release fixes issues around publishing packages using CocoaPods. ## Debugging Kotlin in Xcode with SPM Builds - Kevin Galligan DevFeed: [Debugging Kotlin in Xcode with SPM Builds - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-12-13T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Xcode](), [debugging](), [swift-package-manager](), [iOS](), [Swift](), [Mobile]() Tags: [builds](), [debugging](), [developers](), [ios](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [skie](), [spm](), [swift-package-manager](), [xcode]() ### AI overview This article explains how updated SKIE and KMMBridge support local debugging of Kotlin Multiplatform binaries distributed through Swift Package Manager. With the Xcode Kotlin plugin, iOS developers can browse and debug the Kotlin code without locally compiling or configuring KMP dependencies. ### Source excerpt Virtually all native mobile teams integrate Kotlin Multiplatform by publishing Xcode binaries, usually with SPM. This is generally easy to integrate, but prevented iOS developers from browsing or debugging Kotlin. Today we have fixed that situation. ## KMMBridge 1.1.0 Released - Kevin Galligan DevFeed: [KMMBridge 1.1.0 Released - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-12-05T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Refactoring](), [gradle-plugin](), [Maintainability](), [swift-package-manager](), [cocoapods](), [iOS](), [.NET 11]() Tags: [cocoapods](), [gradle](), [gradle-plugin](), [ios](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [maintainability](), [refactoring](), [releases](), [spm](), [swift-package](), [swift-package-manager](), [xcode]() ### AI overview KMMBridge 1.1.0 is a significant internal refactoring of the Gradle plugin used to publish Kotlin Multiplatform Xcode Framework binaries through Swift Package Manager and CocoaPods. The release improves maintainability and adds Gradle configuration cache support where possible, while introducing separate modules for GitHub features and potentially requiring plugin ID changes for GitHub publishing. ### Source excerpt KMMBridge is a Gradle plugin that publishes Kotlin Multiplatform Xcode Framework dependencies for Swift Package Manager and CocoaPods. The 1.1.0 release is a significant internal refactoring to support ongoing improvements and maintainability. ## KMMBridge 1.0 Release - Kevin Galligan DevFeed: [KMMBridge 1.0 Release - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-08-28T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [swift-package-manager](), [Tool](), [Mobile](), [Framework]() Tags: [binaries](), [cocoapods](), [configuration](), [dependencies](), [ios](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [release](), [spm](), [swift](), [tool](), [xcode]() ### AI overview KMMBridge 1.0.0 simplifies publishing Kotlin Multiplatform XCFramework binaries for iOS, with a primary focus on Swift Package Manager. CocoaPods remains supported, while the templates and tutorials are SPM-only. ### Source excerpt KMMBridge is a tool that helps you publish iOS XCFramework binaries from Kotlin Mutliplatform. The tool has seen multiple iterations over the past few years. This version simplifies the configuration and usage of KMMBridge, with a primary focus on Swift Package Manager (SPM). ## Choosing Local Linking or Dependency Managers for Kotlin Multiplatform iOS Frameworks DevFeed: [Choosing Local Linking or Dependency Managers for Kotlin Multiplatform iOS Frameworks]() Original publisher: [Read original article]() Published: 2024-06-26T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [iOS](), [multiplatform](), [swift-package-manager](), [cocoapods](), [Development]() Tags: [cocoapods](), [ios](), [kmp](), [kotlin-multiplatform](), [spm]() ### AI overview This article compares direct local linking with Swift Package Manager and CocoaPods for Kotlin Multiplatform frameworks in iOS projects. It recommends direct linking for local KMP development when possible, while noting that CocoaPods can make sense when it is already used for the app's dependencies and dependency managers are generally suited to published binaries. ### Source excerpt Do you actually need to use SPM or Cocoapods to include KMP? You don't, and it might not be the right answer ## Scaling iOS at Bumble: Part 2/3 -- The Assessment DevFeed: [Scaling iOS at Bumble: Part 2/3 -- The Assessment]() Original publisher: [Read original article]() Author: Jonathan Crooke Published: 2024-02-15T13:49:17Z Content type: article Language: en Sources: [Bumble Tech]() Topics: [iOS](), [Tuist](), [swift-package-manager](), [bazel](), [toolchain](), [Xcode](), [Requirements](), [Testing]() Tags: [bazel](), [ios](), [ios-app-development](), [performance](), [requirements](), [swift](), [swift-package-manager](), [testing](), [toolchain](), [tuist](), [xcode]() ### AI overview This article recaps Bumble's assessment process for replacing parts of its iOS project and build toolchain. It describes onboarding, proof-of-concept work, full-app conversion, and assessment criteria for Swift Package Manager, Tuist, and Bazel, including blockers, user experience, and performance. ### Source excerpt Scaling iOS at Bumble: Part 2/3 -- The AssessmentRecap In our previous post we discussed how we came to be investigating project and build toolchain replacement solutions for our iOS codebase at Bumble Inc. We began executing proofs of concept for Swift Package Manager (SPM), Tuist and Bazel. The Process Our investigative process for each tool was performed in roughly the same manner: 1. Onboarding With the exception of some light use of SPM as a third-party dependency manager, no-one on the team was fully fluent with any of the tools. This meant that at first, we needed to learn the basics, which could be achieved by creating a minimum-viable manifest for one of our node modules. This would involve learning the manifest format and core commands for building, testing etc. 2. Medium-sized proof of concept Following on from the initial onboarding, we would then progress to converting parent modules, traversing the tree post-order. At each level we'd cover more of our core requirements and encounter edge-cases. Throughout, we noted learnings, limitations and fixes. 3. Full-app conversion At this stage, since our module tree exhibits a strong level of uniformity, we'd now have gathered enough experience to fully convert the app's child modules, and do so using automated tooling. How we achieved this will be discussed below. Unsurprisingly, the top-level app target was its own challenge, and required considerably handcrafting. We only aimed to achieve a minimum-viable conversion at this stage, and didn't expect tests to pass. That said, we'd usually have a fairly conformant conversion anyway, that would launch successfully to its home screen and usually plenty more. 4. Assessment With a converted app target in hand, we would now have a candidate for assessment. But what did we want to know? Our analysis looked at these areas: Blockers: simple enough, any limitations or issues in the tool's functionality whereby it was unable to serve our basic requirements Subjective user ## How Apollo Manages Swift Packages in a Monorepo with Git Subtrees DevFeed: [How Apollo Manages Swift Packages in a Monorepo with Git Subtrees]() Original publisher: [Read original article]() Author: Zach FettersMoore Published: 2024-01-30T07:45:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [monorepo](), [Swift](), [swift-package-manager](), [Git](), [Submodules](), [Library](), [Package manager](), [iOS](), [Code](), [Development]() Tags: [development](), [git](), [ios](), [library](), [mobile](), [monorepo](), [packages](), [pull-requests](), [submodules](), [swift](), [swift-package](), [swift-package-manager](), [testing]() ### AI overview The article describes Apollo iOS's challenges with managing multiple Swift Package Manager library targets in a monorepo. It explains the goal of distributing smaller, independently versioned packages while preserving an efficient shared development and testing workflow, and discusses Git submodules as one approach and its operational drawbacks. ### Source excerpt The monorepo is a common structure for many software projects, and Apollo iOS is no different. Our project was structured in a single repo containing many different Swift Package Manager (SPM) library targets, along with test code and code only used as part of development. This presents a few problems however, one being that when a user adds the SPM package as a dependency, it will pull down all of the code and files in the repo, even though most of them aren't needed. ## An Introduction to Swift Package Manager and how it works DevFeed: [An Introduction to Swift Package Manager and how it works]() Original publisher: [Read original article]() Author: prateek arora Published: 2023-04-11T05:00:35Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [swift-package-manager](), [Package manager](), [Package Management](), [Swift](), [Xcode](), [Open Source](), [iOS](), [Linux](), [tvOS]() Tags: [apple](), [cocoapods](), [dependencies](), [introduction](), [ios](), [linux](), [macos](), [open-source](), [package-management](), [packages](), [swift](), [swift-package](), [swift-package-manager](), [xcode]() ### AI overview An introductory tutorial explains Swift Package Manager (SPM), its role in downloading, compiling, and linking Swift dependencies, and its integration with Swift. It compares SPM with third-party options such as CocoaPods and Carthage, outlines supported platforms and requirements, and describes advantages and limitations. ### Source excerpt What is a package Manager? A package manager or package-management system is a collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs for a computer in a consistent manner. or A package manager deals with packages, distributions of software and data in archive files. Packages contain metadata, such as the software's name, description of its purpose, version number, vendor, checksum (preferably a cryptographic hash function), and a list of dependencies necessary for the software to run properly. What is Swift Package Manager (SPM) As per official Apple Swift Documentation: "The Swift Package Manager is a tool for managing the distribution of Swift code. It's integrated with the Swift build system to automate the process of downloading, compiling, and linking dependencies." The Package Manager is included in Swift 3.0 and above. Why do we need Swift Package Manager? Though we have multiple other ways to manage the dependencies like cocoa pods, Carthage etc. then why is there a need to use SPM? The answer is both cocoa pods and Carthage are third-party package managers, which eventually leads to extra code and efforts one has to put in order to utilise these third-party package managers. For example: For cocoa pods, we need to have a pod framework to be installed, which then needs ruby, gem file or brew in order to install pods. But then SPM comes inbuilt with XCode, so there won't be extra effort and extra files that will be getting added once we use SPM. System Requirement SwiftPM is compatible with macOS, iOS, tvOS and Linux For macOS, you need XCode 11 and above. For Linux, you have to install it manually or use swiftenv. Advantages SwiftPM is open-source like Cocoapods. It may be challenging or fast to contribute but it is possible. Ease of managing dependency's dependencies. If a dependency relies on another dependency, the Swift Package manager will handle it for you. Ease of resetting, manag ## When Should I Use KMMBridge? - Russell Wolf DevFeed: [When Should I Use KMMBridge? - Russell Wolf]() Original publisher: [Read original article]() Published: 2023-01-10T08:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Mobile](), [Development](), [cocoapods](), [swift-package-manager]() Tags: [cocoapods](), [kmmbridge](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [mobile](), [multiplatform](), [swift-package-manager](), [thoughts]() ### AI overview This article explains when teams should use KMMBridge rather than KaMPKit for Kotlin Multiplatform projects. It focuses on teams with existing iOS applications, separate repositories, or developers who do not need to work directly with Kotlin, and describes consuming published Kotlin binaries through CocoaPods or Swift Package Manager. ### Source excerpt Here is how to determine when to use KMMBridge vs KaMPKit for your multiplatform projects, depending on your team's needs. ## Samples of Using KMMBridge DevFeed: [Samples of Using KMMBridge]() Original publisher: [Read original article]() Author: Michael Friend Published: 2022-11-30T20:46:11Z Content type: tutorial Language: en Sources: [Touchlab]() Topics: [Kotlin Multiplatform](), [Gradle](), [Android](), [iOS](), [cocoapods](), [swift-package-manager](), [monorepo]() Tags: [cocoapods](), [coding](), [community](), [development](), [engineering](), [frontend](), [gradle](), [guide](), [inclusive](), [ios](), [javascript](), [kmm](), [kotlin-multiplatform](), [monorepo](), [react](), [software](), [swift-package-manager](), [webdev]() ### AI overview This sample demonstrates how to use Touchlab's KMMBridge Gradle plugin to publish a Kotlin Multiplatform SDK binary for iOS consumption. It describes a setup spanning Android and iOS applications, with separate repositories using CocoaPods or Swift Package Manager, and explains the project's shared module and publishing configuration. ### Source excerpt What is KMM Bridge? KMMBridge is a Gradle plugin by Touchlab that aims to simplify the process of pushing a Kotlin Multiplatform SDK binary to a remote repo to allow iOS developers to use the shared SDK without installing the Kotlin toolchain or building the Kotlin code on every app build. What is this Sample? This sample project showcases our typical project setup for adding Kotlin Multiplatform Mobile code to existing separate Android and iOS apps using KMMBridge. We keep the Android app and the shared code in the same repo and keep the code to an absolute minimum with no dependencies so the project will build faster to speed things up when playing around with custom publish config. To see how to set up a project that keeps the Android app in a separate repo and uses a more realistic structure in shared code, check out the article Quickstart Guide to KMMBridge Sample Repos The basic KMMBridge sample is split into four repos rather than being a monorepo to emulate the trend we've seen from teams adopting KMM into existing apps by publishing a KMM library from one repo for iOS apps in other repos to consume. The four repos are: KMMBridgeSampleKotlin aka Kotlin Repo - This is the Kotlin repo with the shared SDK code as well as an Android app that uses it. KMMBridgeSampleCocoaPods aka CocoaPods Repo- a repo that pulls down the sdk with CocoaPods to use in an iOS app KMMBridgeSampleSpm aka SPM Repo - a repo that pulls down the sdk with Swift Package Manager to use in an iOS app PublicPodspecs aka Podspec Repo - A CocoaPods custom Podspec repo. When publishing for CocoaPods a podspec file will be pushed to this repo in a folder with the version number. See the CocoaPods section for more info on this. KMMBridgeSampleKotlin - The Kotlin Code This repo demonstrates the usual first step for a larger team that wants to try out Kotlin Multiplatform: putting new or existing Kotlin code in a shared module in your Android app repo. This repo also has a standard Android app modul ## Samples of Using KMMBridge - Michael Friend DevFeed: [Samples of Using KMMBridge - Michael Friend]() Original publisher: [Read original article]() Published: 2022-11-29T16:25:42Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [gradle-plugin](), [cocoapods](), [swift-package-manager](), [iOS](), [Android]() Tags: [cocoapods](), [code-sharing](), [gradle](), [kmm](), [kmmbridge](), [kotlin](), [kotlin-multiplatform](), [spm](), [swift-package]() ### AI overview This sample project demonstrates how to add Kotlin Multiplatform code to existing Android and iOS apps using KMMBridge. It describes a setup split across four repositories, with SDK distribution through CocoaPods and Swift Package Manager. ### Source excerpt As you explore how KMM can help your mobile dev team, we've put together more KMMBridge sample to help you evaluate this best-in-class tool. ## The Evolution of Kotlin Multiplatform Mobile - 2022 Edition - Russell Wolf DevFeed: [The Evolution of Kotlin Multiplatform Mobile - 2022 Edition - Russell Wolf]() Original publisher: [Read original article]() Published: 2022-10-31T18:13:15Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [kotlin multiplatform mobile](), [multiplatform](), [Kotlin](), [Mobile](), [kotlin-native](), [Gradle](), [cocoapods](), [Library](), [swift-package-manager](), [swift-package](), [Maven Central]() Tags: [cocoapods](), [gradle](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [kotlin-native](), [libraries](), [maven-central](), [mobile](), [multiplatform]() ### AI overview This retrospective traces Kotlin Multiplatform Mobile from its early experimental stage, when Kotlin/Native memory management, Gradle configuration, and Xcode integration were difficult, to a more mature state with improved memory management, iOS integration through CocoaPods and Swift Package Manager, and better Kotlin-to-Swift interoperability. It also describes growth in the KMM library ecosystem, from about five published libraries in 2018 to more than 1,000 relevant artifacts on Maven Central. ### Source excerpt Kotlin Multiplatform has come a long way in the last few years. As someone who was there when the KMP community first formed, I've seen the ecosystem grow from a few developers trying things out experimentally to a growing number of teams using it in their production apps. With the Kotlin Multiplatform Mobile Beta freshly announced, it's a neat moment to look back on how far everything has come. How It Started In the early days, KMP wasn't very easy for new users. ## Quick Start with KMMBridge - 1 hour tutorial - Kevin Galligan DevFeed: [Quick Start with KMMBridge - 1 hour tutorial - Kevin Galligan]() Original publisher: [Read original article]() Published: 2022-10-24T23:13:36Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Tutorial](), [Development](), [GitHub Actions](), [Gradle](), [CI/CD](), [cocoapods](), [GitHub](), [swift-package-manager]() Tags: [android](), [built-by-touchlab](), [ci-cd](), [cocoapods](), [github](), [github-actions](), [gradle](), [hosting](), [kmm](), [kmmbridge](), [kmp](), [kotlin](), [kotlin-multiplatform](), [quick-start](), [tooling](), [tutorial]() ### AI overview A tutorial for using Touchlab's KMMBridge Gradle tool to build and publish an Xcode Framework from Kotlin for integration into an Xcode project without compiling Kotlin locally. It focuses on basic Kotlin Multiplatform integration for teams using GitHub, CocoaPods or Swift Package Manager, and GitHub Actions. ### Source excerpt Staying true to our goal of making it easier for teams to get the benefits of Kotlin Multiplatform more quickly, this tutorial will help many of you get a basic integration working in about an hour or less. The tooling available for KMM and KMP has been mostly focused around local dev, but as adoption continues to increase, tooling for teams needs to mature as well. ## Building an XCFramework on Kotlin Multiplatform from Kotlin 1.5.30 DevFeed: [Building an XCFramework on Kotlin Multiplatform from Kotlin 1.5.30]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2021-08-30T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Gradle](), [cocoapods](), [iOS](), [macOS](), [swift-package-manager]() Tags: [apple](), [building](), [cocoapods](), [gradle](), [ios](), [kotlin](), [kotlin-multiplatform](), [macos](), [release](), [swift-package-manager]() ### AI overview A tutorial on using the official XCFramework support introduced in Kotlin 1.5.30 for Kotlin Multiplatform projects. It explains how to replace custom Gradle tasks, build debug and release XCFramework variants, and distribute them through options such as CocoaPods or Swift Package Manager. ### Source excerpt A few days ago, Kotlin 1.5.30 has been released. One of the features contained in the release is the official support for XCFrameworks on Kotlin Multiplatform. XCFramework is a binary that can contain multiple platform-specific variants (even for iOS and macOS at the same time). It has been introduced by Apple during the WWDC 2019 as a replacement for FatFrameworks. Before Kotlin 1.5.30, an XCFramework could be created only by running the xcrun command that will pack the frameworks for every different required platform into an XCFramework. ## AppCode 2021.2: улучшения поддержки Swift, автодополнение выражений, окно иерархии вызовов для Swift и не только DevFeed: [AppCode 2021.2: улучшения поддержки Swift, автодополнение выражений, окно иерархии вызовов для Swift и не только]() Original publisher: [Read original article]() Author: yeswolf (JetBrains) Published: 2021-08-16T09:53:35Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [Swift](), [ide](), [Kotlin Multiplatform](), [swift-package-manager](), [async/await](), [Kotlin](), [multiplatform](), [Objective-C]() Tags: [appcode](), [async](), [await](), [call-hierarchy](), [complete-statement](), [ide](), [kmm](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [local-history](), [mobile](), [multiplatform](), [objective-c](), [swift](), [swift-package-manager]() ### AI overview This release article describes AppCode 2021.2 improvements, including support for Swift features such as result builders, enum Codable synthesis, and async/await. It also covers documentation completion, Call Hierarchy, Swift Package Manager build and debugging support, a Kotlin Multiplatform Mobile plugin, a debugger Preview Tab, and Local History search. ### Source excerpt Привет, Хабр! В этом посте, как и всегда, расскажем о новом релизе AppCode. Всем, кому интересно, -- добро пожаловать под кат. Читать далее