# kotlin-multiplatform-libraries Published articles for kotlin-multiplatform-libraries. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Klibs.io Grows to 4,200+ KMP Projects With Smarter Discovery and New AI Integrations DevFeed: [Klibs.io Grows to 4,200+ KMP Projects With Smarter Discovery and New AI Integrations]() Original publisher: [Read original article]() Author: Daria Voronina Published: 2026-08-17T13:12:57Z Content type: article Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [AI-assisted coding]() Tags: [agents](), [ai-development](), [evaluation](), [kotlin](), [kotlin-multiplatform-libraries](), [llms](), [mcp](), [mcp-server](), [multiplatform](), [news]() ### AI overview Klibs.io has expanded its Kotlin Multiplatform library catalog and adds AI integrations through an MCP server. Coding agents can search projects by platform and retrieve current package-version data, while an expert skill supports library discovery and comparison. ### Source excerpt Explore a growing Kotlin Multiplatform catalog in your browser, or bring up-to-date library data directly into your AI development workflow through the klibs.io MCP server. When we introduced klibs.io in December 2024, the goal was simple: make it easier to find a Kotlin Multiplatform library that fits both your use case and target platforms. Since [...] ## Publishing Kotlin Multiplatform Swift Packages Using Google Cloud Storage and Cloud Run DevFeed: [Publishing Kotlin Multiplatform Swift Packages Using Google Cloud Storage and Cloud Run]() Original publisher: [Read original article]() Author: Nate Ebel Published: 2023-10-18T05:28:28Z Content type: tutorial Language: en Sources: [Engineering at Premise - Medium]() Topics: [Kotlin Multiplatform](), [Cloud Run](), [Gradle](), [iOS](), [kotlin-multiplatform-libraries](), [Swift](), [Cloud]() Tags: [cloud](), [cloud-run](), [github](), [google-cloud-platform](), [google-cloud-run](), [gradle](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [mobile-app-development](), [multiplatform](), [swift]() ### AI overview This tutorial describes Premise's approach to publishing and consuming Kotlin Multiplatform Swift Packages. It uses a custom Gradle plugin to publish XCFrameworks to Google Cloud Storage and a Cloud Run service to download the Swift Package binaries requested by Xcode, reducing the need to store large binaries in GitHub. ### Source excerpt By Nate Ebel, Android developer In this post, we'll detail our solution for publishing, and consuming, Kotlin Multiplatform Swift Packages. Our solution leverages a custom Gradle plugin publishing XCFrameworks to Google Cloud Storage and a Google Cloud Run service to download Swift Package binaries requested by XCode. With this solution in place, we've been able to more efficiently serve multiple Kotlin Multiplatform libraries to our iOS application. This is a part of an ongoing series on our usage of Kotlin Multiplatform at Premise: Part 1: Kotlin Multiplatform at Premise Part 2: Kotlin Multiplatform Project Structure for Integrating with Brownfield Applications Part 3: Building a CI Pipeline for Kotlin Multiplatform Mobile Using GitHub Actions Part 4: Publishing Kotlin Multiplatform Swift Packages Using Google Cloud Storage and Cloud Run -- This Post Part 5: Generating BuildConfig Files for a Kotlin Multiplatform Library -- Coming Soon Part 6: Optimizing Local Build Times for Kotlin Multiplatform Mobile Projects -- Coming Soon Premise and Kotlin Multiplatform Swift Packages We've been using Kotlin Multiplatform in production since early 2021 in the form of our mobile-shared project. During that time, we've consumed our shared code as a Swift Package within our iOS application. The integration of that Swift Package has gone through several iterations. v1: Use the multiplatform-swiftpackage plugin to build the Swift Package and store the XCFramework binary in GitHub v2: Use our own custom Gradle plugin to build the Swift Package and store the XCFramework binary in GitHub These two solutions were very similar. Build the XCFramework. Generate the Package.swiftfile. Check both into git with the desired version tag. These approaches worked fine for a while, but eventually we started to pay the price for our simple initial solution. An XCFramework binary can be pretty large. Ours were in the ballpark of 100MB. So checking 2-3 of these into each commit (1 for each iOS archit ## Multiplatform Settings 1.0.0 DevFeed: [Multiplatform Settings 1.0.0]() Original publisher: [Read original article]() Author: Russell Wolf Published: 2023-01-15T03:12:17Z Content type: release Language: en Sources: [DEV Community 👩💻👨💻: Russell Wolf]() Topics: [kotlin-multiplatform-libraries](), [Kotlin Multiplatform](), [Kotlin](), [Library](), [Android](), [iOS](), [macOS](), [tvOS](), [watchOS](), [Windows](), [Web]() Tags: [android](), [coding](), [community](), [development](), [engineering](), [inclusive](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [kotlinmultiplatform](), [library](), [macos](), [release](), [software](), [watchos](), [web](), [windows]() ### AI overview The author announces version 1.0.0 of Multiplatform Settings, a Kotlin Multiplatform library for persisting simple, unstructured key-value data. The release commits to maintaining non-experimental APIs until a possible 2.0 release and compares the library's platform-API interoperation with Google's preview multiplatform DataStore library. ### Source excerpt Today, I've released version 1.0.0 of Multiplatform Settings. That means I'm committed to maintaining the current API surface of everything not marked as experimental until there's a 2.0 release (which I don't currently have plans for). If you need to save simple, unstructured key-value data in your multiplatform apps, I hope you'll consider using it. A lot of you already are! russhwolf / multiplatform-settings A Kotlin Multiplatform library for saving simple key-value data Multiplatform Settings This is a Kotlin library for Multiplatform apps, so that common code can persist key-value data. A Korean translation of this readme is available separately, maintained by @wooram-yang Table of contents Usage Implementation Summary Creating a Settings instance Platform constructors Factories No-arg module Settings API Listeners Testing Other platforms Experimental API Experimental Implementations Serialization module Coroutine APIs DataStore Make-Observable module Adding to your project Building License Usage The Settings interface has implementations on the Android, iOS, macOS, watchOS, tvOS, JS, WasmJS, JVM, and Windows platforms. Implementation Summary The following table shows the names of implementing classes and what platforms they're available on. Class Backing API Platforms KeychainSettings2 Apple Keychain iOS, macOS, watchOS, tvOS NSUserDefaultsSettings1 User Defaults iOS, macOS, watchOS, tvOS PreferencesSettings1 java.util.prefs.Preferences JVM PropertiesSettings java.util.Properties JVM SharedPreferencesSettings1 android.content.SharedPreferences Android StorageSettings Web Storage (localStorage) JS, WasmJS RegistrySettings2 Windows Registry MingwX64 DataStoreSettings3 androidx.datastore.core.DataStore Android, ... View on GitHub Some History Multiplatform Settings was one of the first Kotlin Multiplatform libraries ever released, with the first version published on May 28, 2018. I called that first version 0.1-alpha, though I would later drop the alpha from the ve ## Building Kotlin/Multiplatform with Github Actions DevFeed: [Building Kotlin/Multiplatform with Github Actions]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2021-04-15T11:44:49Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [GitHub Actions](), [Kotlin Multiplatform](), [CI/CD](), [kotlin-multiplatform-libraries](), [Maven Central](), [Gradle](), [HTTP](), [API]() Tags: [ci-cd](), [github](), [github-actions](), [gradle](), [http](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [maven-central]() ### AI overview This tutorial explains how to automate Kotlin Multiplatform library publishing with GitHub Actions. It covers publishing snapshots to Maven Central, building across Linux, macOS, and Windows, and managing a shared Sonatype staging repository for stable releases. ### Source excerpt In a previous tutorial, I showed you how to configure your Kotlin/Multiplatform libraries to be published on Maven Central. To go beyond a publication process we now need to automate things with a good CI/CD workflow. Let's see how to do this with Github Actions. As the Kodein Open Source Initiative libraries are hosted on Github, we felt that it was the best choice to use the Github Actions pipelines to test, build and deploy our libraries, as it is entirely integrated with every other part of Github. Let's start with the snapshot publication process, as it is fairly straightforward. Publishing snapshots on Maven Central has no more constraints than just being authenticated with your Sonatype account, and having your artifacts file names ending with the uppercased word SNAPSHOT. This means that you could literally upload anything in your staging repositories. Here is a Github Actions script to upload a snapshot of a Kotlin/Multiplatform project: https://medium.com/media/41c7ac097f1ff802076f92acc8243077/href In that example, we run the task publishAllPublicationToOss on Linux, Mac & Windows, literally saying to publish every available targets onto the oss repository, which is the name we gave to it in our maven-publish configuration in our Gradle build script. This is not optimal, as every platform could upload shared targets like JVM, JS or even the Kotlin Multiplatform Metadata, but it's simple, and it works! Let's now see how to deploy stable releases. We have to discuss how we will be managing the unique staging repository we need. In fact, this is quite simple, and it is resume by this image: What we need is to create a staging repository, by using the sonatype API over HTTP. This step will generate a repository ID, that we use in later steps. In the build-upload matrix, we upload every artifact onto the same staging repository. Finally, In the drop-or-release job, depending on the success or failure of the build-upload matrix, we drop or release the staging re ## Introducing KMP FatFramework Cocoa, a Gradle plugin for iOS FatFramework DevFeed: [Introducing KMP FatFramework Cocoa, a Gradle plugin for iOS FatFramework]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2021-03-02T00:00:00Z Content type: release Language: en Sources: [Posts on Marco Gomiero]() Topics: [kotlin-multiplatform-libraries](), [Kotlin Multiplatform](), [Gradle](), [iOS]() Tags: [gradle](), [gradle-plugin](), [ios](), [kmp](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [libraries](), [plugin](), [release]() ### AI overview The article introduces KMP FatFramework Cocoa, a Gradle plugin for Kotlin Multiplatform projects. It builds iOS FatFrameworks containing the required device and simulator architectures and manages publishing the libraries to a CocoaPod repository. ### Source excerpt Today I want to share KMP FatFramework Cocoa, a Gradle plugin for Kotlin Multiplatform projects that generate a FatFramework for iOS targets and manages the publishing process in a CocoaPod Repository. The plugin is born from a set of unbundled Gradle tasks that I wrote to manage the building and the publishing process of Kotlin Multiplatform libraries for iOS that we use at Uniwhere and Revelop. The libraries are published in a FatFramework that contains the code for every required architecture (real devices use the Arm64 architecture, while the simulator uses the host computer architecture which in most of the cases is X64). ## Kotlin Multiplatform Library - Touchlab DevFeed: [Kotlin Multiplatform Library - Touchlab]() Original publisher: [Read original article]() Published: 2019-11-19T22:31:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [kotlin-multiplatform-libraries](), [Library](), [cross-platform]() Tags: [code-sharing](), [coroutines](), [cross-platform](), [kmp](), [koin](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [ktor](), [library](), [sqldelight](), [sqlite](), [thoughts]() ### AI overview Touchlab provides an overview of Kotlin Multiplatform libraries, listing libraries used by Touchlab, JetBrains, and the community, along with sample apps and a presentation on Kotlin Multiplatform library development. ### Source excerpt Introduction to Kotlin Multiplatform explains how KMP is pragmatic programming to develop apps on multiple platforms & avoid writing code twice. ## Kotlin Multiplatform Frequently Asked Questions - Touchlab DevFeed: [Kotlin Multiplatform Frequently Asked Questions - Touchlab]() Original publisher: [Read original article]() Published: 2019-11-19T22:18:08Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Library](), [Mobile](), [business logic]() Tags: [business-logic](), [code-sharing](), [great](), [kotlin](), [kotlin-compiler](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [mobile](), [multiplatform](), [thoughts]() ### AI overview This FAQ explains how Kotlin Multiplatform can be introduced into existing applications and how much code teams may share. It discusses sharing business logic while generally keeping platform-specific UI, expected app size impact, Swift and Objective-C interoperability, and libraries used by Touchlab and its community. ### Source excerpt Touchlab is building a community of mobile code sharing and Kotlin Multiplatform enthusiasts. We answer Kotlin Multiplatform frequently asked questions.