# compose-multiplatform Compose Multiplatform is an open-source, declarative framework for sharing native-quality user interfaces across Android, iOS, desktop, and web platforms. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork DevFeed: [Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork]() Original publisher: [Read original article]() Author: Sajid Ali Published: 2026-09-14T04:24:43Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [compose-multiplatform](), [tvOS](), [Kotlin Multiplatform](), [Gradle]() Tags: [apple](), [build](), [compiler](), [compose-multiplatform](), [gradle](), [gradle-plugin](), [ios](), [jetbrains](), [multiplatform](), [source]() ### AI overview This tutorial explains the build setup for adding tvOS support to a Compose Multiplatform fork. It covers Kotlin Multiplatform targets, source-set organization shared between iOS and tvOS, and the build-layer work used to identify missing modules and dependencies. ### Source excerpt Compose Multiplatform on tvOS This series: Compose Multiplatform on tvOS My Journey Making Compose Multiplatform Work on tvOS, and What I Learned Build Setup: Targets, Source Sets and buildSrc for tvOS in a Compose Multiplatform Fork (this post) Rendering (coming soon) Siri Remote input (coming soon) Siri Remote trackpad (coming soon) Screen density and text input (coming soon) Porting tv-material (coming soon) The Gradle plugin and third-party libraries (coming soon) Maintaining the fork (coming soon) Building a real app on it (coming soon) Part 1 was why this fork exists. This one is the build layer, and it comes before any Compose code, because in Kotlin Multiplatform a target is not a flag you flip at the end. It decides which source sets compile, which dependencies resolve, which klibs get published, which linker flags get passed. Until the build knows about tvosArm64, nothing tells you what is missing. So the first commits were build files. Once the targets were on, the compiler listed what was missing, module by module, and I worked through that list. Source set layout on the tvos branch I started on a branch called tvos, based on upstream. Back then JetBrains called iOS "uikit" in this repository and the source set was uikitMain. Because tvOS is also UIKit underneath, it made sense to have a common source parent for both iOS and tvOS. But iOS was already being called uikit, so I chose uiKitCommonMain as the source set name and moved all the UIKit files there, keeping only the iOS specific files in uikitMain and putting the tvOS specific files in a new source set, tvosMain. The problem with this approach was how to keep up with upstream. I tried a symlink to the uikit source set, and then overriding the tvOS files in a separate target. The override worked but complicated the process. At that time my goal was to make it runnable on tvOS however possible, so we would have a proof of concept. So I did a lot of hacks in the tvos branch to make it runnable, and af ## jetc.dev Newsletter Issue #330 DevFeed: [jetc.dev Newsletter Issue #330]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-08T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [compose-multiplatform](), [Compose](), [tvOS](), [Android](), [Testing](), [SwiftUI](), [JavaScript](), [TypeScript](), [Ktor]() Tags: [2026](), [android](), [compose-multiplatform](), [dev](), [ios](), [newsletter](), [swiftui](), [testing](), [typescript]() ### AI overview Newsletter Issue #330 covers Compose Multiplatform support for Apple tvOS, lessons from Android foldables for potential foldable iPhone development, testing and recomposition issues, image-loading test techniques, animated number transitions, and related Compose tools and libraries. ### Source excerpt Apple TV! Apple foldables! Microsoft Office! And other topics not necessarily involving gigantic firms! ## Setting Up Koin in a Real Kotlin Multiplatform Project: A Step-by-Step Guide DevFeed: [Setting Up Koin in a Real Kotlin Multiplatform Project: A Step-by-Step Guide]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-09-07T12:01:03Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [Kotlin](), [Android](), [iOS](), [ui]() Tags: [android](), [compose-multiplatform](), [dependencies](), [guide](), [implementation](), [ios](), [kmp](), [koin](), [kotlin](), [kotlin-multiplatform](), [mobile-app-development](), [module](), [viewmodel]() ### AI overview A step-by-step tutorial for setting up Koin in a Kotlin Multiplatform project targeting Android and iOS. It covers dependencies, data, domain, and UI modules, a platform bridge, platform entry points, and dependency injection in Composables. ### Source excerpt Hi everyone! πŸ‘‹ In this article, we'll take a practical, step-by-step approach to setting up Koin in a real-world Kotlin Multiplatform (KMP) project. Instead of starting with an isolated example or a simple Hello World, we'll work with a project created by the CodandoTV community: the World Cup Best Team Simulator. The app allows users to browse football players by country and build their own dream team. It runs on both Android and iOS, using Kotlin Multiplatform for sharing business and data logic, and Compose Multiplatform to share the UI across platforms. Step 1: Add Koin Dependencies Add the Koin libraries to your version catalog: # gradle/libs.versions.toml [versions] koin = "4.2.2" [libraries] koin_core = { group = "io.insert-koin", name = "koin-core", version.ref = "koin" } koin_android = { group = "io.insert-koin", name = "koin-android", version.ref = "koin" } koin_compose = { module = "io.insert-koin:koin-compose", version.ref = "koin" } koin_compose_viewmodel = { module = "io.insert-koin:koin-compose-viewmodel", version.ref = "koin" } In the shared module shared/build.gradle.kts, split the dependencies by source set -- commonMain gets the shared Koin libraries, androidMain gets the Android-specific one: // shared/build.gradle.kts sourceSets { commonMain.dependencies { implementation(libs.koin.core) implementation(libs.koin.compose) implementation(libs.koin.compose.viewmodel) } androidMain.dependencies { implementation(libs.koin.android) } } In the Android app module androidApp/build.gradle.kts , add the Android Koin dependency: // androidApp/build.gradle.kts dependencies { implementation(libs.koin.android) implementation(libs.koin.core) }Step 2: Create the Data Module Create shared/src/commonMain/.../data/DataModule.kt . This module provides singleton instances -- repositories, and data sources that live for the entire app lifecycle. val dataModule = module { single { WorldCupRepositoryImpl(ioDispatcher = Dispatchers.IO) } }Step 3: Create ## Compose Multiplatform Is a Business Decision, Not a Technical One - Justin Mancinelli DevFeed: [Compose Multiplatform Is a Business Decision, Not a Technical One - Justin Mancinelli]() Original publisher: [Read original article]() Published: 2026-09-01T18:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [compose-multiplatform](), [multiplatform](), [Compose](), [Flutter](), [Jetpack Compose](), [React Native](), [Kotlin](), [jetbrains]() Tags: [compose-multiplatform](), [cross-platform](), [flutter](), [javascript](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [react](), [technical](), [ui]() ### AI overview This opinion article argues that Compose Multiplatform is a strategic business choice for sharing UI across Android, iOS, desktop, and web. It compares CMP with Flutter and React Native, emphasizing its Kotlin and Jetpack Compose foundations and its native status on Android. ### Source excerpt If you are weighing Flutter, maintaining two native UI codebases "for now", or assuming cross-platform means giving something up, read this before your next roadmap conversation. ## jetc.dev Newsletter Issue #329 DevFeed: [jetc.dev Newsletter Issue #329]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-01T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [compose-multiplatform](), [Compose](), [cross-platform](), [Android](), [Streaming](), [HTML]() Tags: [android](), [compose](), [compose-multiplatform](), [cross-platform](), [dev](), [html](), [jetpack-compose](), [newsletter](), [streaming]() ### AI overview This newsletter issue reviews recent Jetpack Compose ecosystem updates, including the stable Compose Multiplatform release, new Remote Compose and Glance artifact groups, Compose Material3 changes, Navigation 3 beta updates, and related Android and Wear releases. It also covers cross-platform page curls, streaming Kotlinx HTML via Molecule, and screenshot prevention on Android and iOS. ### Source excerpt Compose Multiplatform `1.12.0`! New Remote Compose and Glance artifact groups! Cross-platform page curls! Streaming Kotlinx HTML via Molecule! Prevent screenshots! And... what does Material3 have against the rich?!? ## jetc.dev Newsletter Issue #327 DevFeed: [jetc.dev Newsletter Issue #327]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-18T14:00:00Z Content type: news Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [releases](), [compose-multiplatform](), [Jetpack Compose](), [liquid glass](), [Model Context Protocol (MCP)](), [Server-side rendering]() Tags: [compose](), [compose-hot-reload](), [compose-multiplatform](), [dev](), [liquid-glass](), [mcp-server](), [multiplatform](), [release](), [release-notes](), [releases]() ### AI overview Newsletter Issue #327 covers stable and alpha Jetpack Compose releases, Compose Multiplatform updates, Liquid Glass approaches for multiplatform apps, and related Compose developments including Hot Reload MCP server support and proposed server-side rendering. ### Source excerpt Compose stable release! Compose Material3 stable too! Liquid Glass in a multiplatform app! Preview generator! ## jetc.dev Newsletter Issue #326 DevFeed: [jetc.dev Newsletter Issue #326]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-11T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [Android](), [compose-for-web](), [debug](), [Design system](), [Testing](), [AI-assisted coding]() Tags: [coding-agents](), [compose](), [compose-for-desktop](), [compose-for-web](), [debugger](), [design-system](), [jetpack-compose](), [testing]() ### AI overview Newsletter Issue #326 covers recent Compose developments, including Places UI Kit discussions, stability considerations, design-system testing, Compose Desktop and Web test bridges, and an Android debugger aimed at coding agents. It also highlights community projects and releases around Compose Multiplatform. ### Source excerpt Why we sometimes still need to think about stability! Compose Desktop/Web test bridge! Android debugger for coding agents! And... Places, everyone?!? ## Scanning bus stop codes with ML Kit and Vision in the GalwayBus Compose Multiplatform app DevFeed: [Scanning bus stop codes with ML Kit and Vision in the GalwayBus Compose Multiplatform app]() Original publisher: [Read original article]() Published: 2026-08-06T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [compose-multiplatform](), [ML Kit](), [Android](), [cameraX](), [iOS](), [Code](), [ui]() Tags: [android](), [apple](), [camera](), [camerax](), [code](), [compose-multiplatform](), [ios](), [ml-kit](), [multiplatform](), [native](), [ocr](), [on-device](), [platform](), [recognition](), [ui]() ### AI overview This tutorial explains how the GalwayBus app scans six-digit bus stop codes using on-device ML Kit on Android and Apple's Vision framework on iOS. Camera preview, matching logic, and UI are shared through Compose Multiplatform, while platform-specific implementations handle camera access and OCR. Recognized six-digit runs are matched exactly to stops, and overlapping recognition requests are avoided by dropping newer frames. ### Source excerpt Every bus stop in Galway has a plate with a 6-digit stop code printed on it. We recently added a "Scan" tab to the GalwayBus app that lets you point the camera at that plate and jump straight to the stop's departures. The text recognition runs entirely on device (ML Kit on Android, Apple's Vision framework on iOS), with the camera preview, matching logic and UI all living in the shared Compose Multiplatform code. ## Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis DevFeed: [Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis]() Original publisher: [Read original article]() Published: 2026-07-28T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Memory Leaks](), [Compose](), [compose-multiplatform](), [jetbrains](), [ide]() Tags: [compose](), [compose-multiplatform](), [dump](), [eclipse](), [heap](), [jetbrains](), [kotlin-multiplatform](), [memory-leak]() ### AI overview The article investigates a suspected memory leak in the JetBrains Jewel project, a Compose Multiplatform library targeting desktop applications. It explains using JVM-specific tools, including heap dumps and Eclipse Memory Analyzer Tool, to examine retained heap and identify possible memory-retention issues. ### Source excerpt A kinda-brief tale about a memory leak, a heap dump, and a one-line fix. ## Adding a Koog AI assistant (with structured output) to the FantasyPremierLeague CMP sample DevFeed: [Adding a Koog AI assistant (with structured output) to the FantasyPremierLeague CMP sample]() Original publisher: [Read original article]() Published: 2026-07-27T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [Artificial Intelligence](), [compose-multiplatform](), [Kotlin](), [jetbrains](), [Framework](), [App]() Tags: [agents](), [ai](), [ai-agents](), [compose](), [compose-multiplatform](), [framework](), [jetbrains](), [kotlin](), [llm](), [multiplatform]() ### AI overview This tutorial adds a Koog-powered AI assistant to a FantasyPremierLeague Compose Multiplatform sample. It uses structured output to return typed player and fixture IDs, allowing the app to render cards and resolve references against its existing data. ### Source excerpt Koog is JetBrains' Kotlin framework for building AI agents. In this article we're going to use it to add an in-app "FPL Assistant" to the FantasyPremierLeague Compose Multiplatform sample. This is a chat screen where you can ask about players, fixtures and mini-league standings. The answers render as player and fixture cards rather than just as text. ## The challenge of adding a Web target to DroidconKotlin - Kevin Schildhorn DevFeed: [The challenge of adding a Web target to DroidconKotlin - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2026-07-22T18:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Web](), [multiplatform](), [Kotlin](), [compose-multiplatform](), [wasm](), [browser](), [Firebase]() Tags: [browser](), [browsers](), [compose-multiplatform](), [crashlytics](), [dependencies](), [droidcon](), [firebase](), [kotlin](), [kotlin-multiplatform](), [project](), [wasm](), [web]() ### AI overview This post explains how Touchlab added browser Web support to the DroidconKotlin multiplatform app. It covers dependency limitations, the decision to use Web instead of Kotlin WASM, SQLDelight support, Coil and Okio filesystem issues, the lack of Firebase Crashlytics Web support, and localization and resource handling with Compose Multiplatform. ### Source excerpt We recently added support for Web to our DroidconKotlin app. In this post we'll go over our process and the difficulties of adding a Web target to an existing project. ## jetc.dev Newsletter Issue #321 DevFeed: [jetc.dev Newsletter Issue #321]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-07-07T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Compose](), [compose-multiplatform](), [navigation](), [multiplatform](), [ui]() Tags: [compose](), [compose-multiplatform](), [dev](), [migration](), [navigation](), [newsletter](), [ui](), [updates]() ### AI overview Jetc.dev Newsletter Issue #321 reviews recent Jetpack Compose updates, including bug fixes and library releases, Nav3 migration experiences, a new 2D layout component, theme-aware Maps for Compose, Compose Multiplatform migration, and other Compose UI developments. ### Source excerpt Compose stable and beta updates! Nav3 migrations! Grid! Effects! And GLFW for Compose for Desktop?!? ## Introducing the Composables CLI and MCP server DevFeed: [Introducing the Composables CLI and MCP server]() Original publisher: [Read original article]() Author: Alex Styl Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Command-line interface](), [MCP](), [MCP Server](), [compose-multiplatform](), [Kotlin Multiplatform](), [Documentation]() Tags: [cli](), [compose-multiplatform](), [documentation](), [kotlin-multiplatform](), [mcp](), [mcp-server](), [npm]() ### AI overview The Composables CLI is a command-line tool for creating native apps and modules with Composables UI preconfigured. It provides an interactive setup wizard, supports Kotlin Multiplatform project structure, can search live Composables UI documentation from the terminal, and can run an MCP server to help coding agents access component guidance and examples. ### Source excerpt Start native apps with Composables UI without setting up every platform by hand. ## Introducing Composables UI DevFeed: [Introducing Composables UI]() Original publisher: [Read original article]() Author: Alex Styl Published: 2026-06-22T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [compose-multiplatform](), [Library](), [ui](), [Design system](), [Jetpack Compose](), [Gradle](), [Documentation]() Tags: [components](), [compose](), [compose-multiplatform](), [design-system](), [documentation](), [gradle](), [library](), [multiplatform](), [ui]() ### AI overview Composables UI is a fully accessible component library for Compose Multiplatform. It provides adaptive components for different device capabilities, consistent states and theming with dark mode, and options to use it as a Gradle dependency or copy individual component source. The article also describes upgrades to Compose Unstyled developed through testing Composables UI. ### Source excerpt A modern, fully-accessible component library for Compose Multiplatform. ## Antigravity TagSpotter - KotlinMultiPlatform evolve DevFeed: [Antigravity TagSpotter - KotlinMultiPlatform evolve]() Original publisher: [Read original article]() Published: 2026-06-14T19:10:33Z Content type: opinion Language: en Sources: [maiatoday]() Topics: [kotlinmultiplatform](), [multiplatform](), [Android](), [compose-multiplatform](), [Kotlin](), [iOS](), [Gradle](), [Web](), [Open Source]() Tags: [ai](), [ai-agents](), [android](), [antigravity](), [code](), [compose](), [compose-multiplatform](), [git](), [kmp](), [kotlin](), [kotlinmultiplatform](), [migration](), [tests]() ### AI overview The article documents an attempt to migrate the TagSpotter Android app toward Kotlin Multiplatform using Antigravity 2.0 and parallel agents. It describes preparation such as modularizing the codebase, adding tests, researching KMP migration, and planning support for iOS, Android, Desktop, and Web, while retaining Android-specific features such as the Wear app. ### Source excerpt The Challenge - bring on the subagents Can I make my TagSpotter Android app be multi-platform in a weekend using Antigravity 2.0 and a swarm of agents running in parallel? Can I do this even though I don't know how to use Xcode and I don't want to break my existing app. This was the question I had. TagSpotter is medium featured Android app I built two weeks ago. I use it to capture interesting and favourite spots in the city like unusual graffiti or yarn bombed sculptures. It has a fair few features including: Capture the places by camera with location Upload a photo AI lookup to find info on the internet from the photo, links, title, artist and suggested tags Export the spots in a zip file and import them again. This is how I share my favourite spots with friends. Make field notes by typing or speaking Share my favourites to Google maps for easy navigation Good category and location based filtering Wear app that can list started spots and navigate to a spot on the watch A good challenge because it isn't just a hello world app. The prep Because the clock would be ticking, I did a little bit of prep to make sure I had everything ready. Prep the codebase Clean up the app, no warnings, lint issues or unused imports Make sure the screens work in landscape, desktop mode will need this Split the app into feature based and pure kotlin modules. I know Compose multiplatform and pure kotlin modules can easily be re-used. Put some tests in place Checked everything works and make a tag in git incase Antigravity borked the project. Light research I collected a few salient links about KMP migration. A good blog post, some info on project structure and a link to the open source kmp libraries I might need. Nitty Gritty Friday evening, let's go. Make a plan I want to convert this app to a KMP app that supports iOS, Android, Desktop and Web. The other platforms do not have to support all features, e.g. the wear app. But Android still has to support this feature. I want to share as mu ## Koin Annotations Make expect/actual Obsolete in KMP DevFeed: [Koin Annotations Make expect/actual Obsolete in KMP]() Original publisher: [Read original article]() Author: Tezov Published: 2026-06-11T08:48:59Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [Compiler](), [cross-platform](), [interfaces]() Tags: [compiler](), [compose-multiplatform](), [cross-platform](), [dependency-injection](), [development](), [interface](), [kmp](), [koin](), [kotlin](), [kotlinmultiplatformmobile]() ### AI overview A tutorial showing how Koin annotations and the Koin compiler can replace expect/actual declarations in Kotlin Multiplatform projects. It defines shared interfaces in commonMain, provides Android and iOS implementations through dependency injection, and uses Compose Multiplatform to resolve the platform-specific behavior. ### Source excerpt Source code available at the end of the article In Kotlin Multiplatform (KMP) projects, expect/actual is traditionally used to handle platform-specific implementations. In a previous story, I showed how to reduce expect/actual to only one per module using Koin DSL. Today, we can go further. With Koin annotations and the Koin compiler, you can completely bypass expect/actual. This method works seamlessly with Compose Multiplatform and lets you maintain a clean architecture while keeping platform-specific logic where it belongs. Previous Story Mastering Koin Annotations with the Koin Compiler Through Unit Tests -> link Next Story I don't know yet-> coming soon Setting the Stage Inside commonMain, Koin is initialized like this: @Module @ComponentScan( "com.tezov.store.shared.di", "com.tezov.store.shared.data", "com.tezov.store.shared.domain", "com.tezov.store.shared.presentation" ) class SharedModule @KoinApplication(modules = [SharedModule::class]) class SharedApplication val koinConfiguration = koinConfiguration { /* nothing here for the demo */ } I'm using: koinCompiler = "0.6.2" koinCompose = "4.2.1-RC1" koinComposeAnnotation = "4.2.1-RC1" The important part here is the @ComponentScan. Koin doesn't just scan commonMain. It also scans the platform modules: androidMain and iosMain. That detail is key because it lets Koin find all implementations without any manual wiring. Defining Contracts in commonMain Instead of expect, we define interfaces for domain and presentation layers. Domainpackage com.tezov.store.shared.domain interface PlatformDomainProtocol { fun description(): String }Presentationpackage com.tezov.store.shared.presentation import androidx.compose.runtime.Composable interface PlatformPresentationProtocol { @Composable fun ComposableFromPlatform() } Yes, you can even include a @Composable in an interface. This is powerful: your shared code can remain clean while delegating platform-specific behavior entirely to the DI container. When usi ## How to use Koin Compiler in a Multimodule Project? DevFeed: [How to use Koin Compiler in a Multimodule Project?]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-06-11T08:47:55Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [koin](), [compose-multiplatform](), [multiplatform](), [Gradle](), [Kotlin](), [implementation]() Tags: [build](), [compose](), [compose-multiplatform](), [gradle](), [how-to](), [implementation](), [koin](), [kotlin](), [migrate](), [multi-module-project](), [plugin]() ### AI overview A tutorial on migrating a Compose Multiplatform multi-module project to the Koin Compiler. It covers the required Kotlin and Koin versions, configuring the compiler dependency through Gradle, creating a convention plugin, applying it to modules, and updating module initialization. The article reports replacing an approximately 80-line custom Gradle plugin with a simpler approximately 30-line setup while retaining compile-time safety through the K2 compiler. ### Source excerpt Hey everyone! Today we're diving into how to use the Koin Compiler in a Compose Multiplatform multi-module project. In the previous article, we explored how to migrate a multimodule setup to Koin Annotations, using a convention Gradle plugin to move forward in small, safe steps. We'll follow that same approach diving deep into a project called MovieDB-AppπŸ‘‹ A sticky note attached to a wall with the words "how to" written on it - Unsplash by walls_ioFirst step: Update your project, if necessary πŸš€ Your project is eligible to support the Koin Compiler if it meets at least the following requirements: βœ… Kotlin 2.3.x or higher (K2 is required) βœ… Koin 4.2.x or higher Our sample project is using the following stack overview: πŸ€– AGP: 9.1.0 🧩 Kotlin: 2.3.20 πŸ’‰ Koin: 4.2.1 🏷 Koin Annotations: 2.3.1 Second step: Configure Koin compiler dependency Let's add our Koin Compiler dependency into the libs.versions.toml : #gradle/libs.versions.toml [versions] koin-compiler-plugin = "1.0.0" ... [libraries] koin-compiler-plugin = { group = "io.insert-koin", name = "koin-compiler-gradle-plugin", version.ref = "koin-compiler-plugin" } Now, let's run Gradle Sync 🐘 Our mission is to create a conventional plugin in our build-logic so we can migrate the project module by module, taking small and safe steps along the way. To achieve that let's add the koin compiler dependency as a depency of our build-logic: // build-logic/build.gradle.kts ... dependencies { implementation(libs.koin.compiler.plugin) } After syncing Gradle, it's time to create our conventional plugin: // build-logic/src/main/kotlin/plugins/KoinCompilerSetupPlugin.kt package plugins import org.gradle.accessors.dm.LibrariesForLibs import org.gradle.api.Plugin import org.gradle.api.Project import org.gradle.kotlin.dsl.configure import org.gradle.kotlin.dsl.dependencies import org.gradle.kotlin.dsl.the import org.koin.compiler.plugin.KoinGradleExtension // Ref: https://github.com/InsertKoinIO/koin-compiler-plugin/blob/main/docs/CASE_S ## Kotlin Multiplatform in Production: Two Real-World Use Cases from Booking.com DevFeed: [Kotlin Multiplatform in Production: Two Real-World Use Cases from Booking.com]() Original publisher: [Read original article]() Author: Diego GΓ³mez Olvera Published: 2026-06-05T15:09:18Z Content type: article Language: en Sources: [Booking.com Development - Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [experiments](), [A/B Testing](), [Android](), [iOS](), [Design system](), [Mobile](), [Development]() Tags: [a-b-testing](), [android](), [booking](), [bookingcom](), [compose](), [compose-multiplatform](), [concepts](), [consistency](), [data](), [development](), [engineering](), [experiment](), [experimentation](), [experiments](), [ios](), [java](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [mobile](), [multiplatform](), [objective-c]() ### AI overview This article describes two Booking.com engineering use cases for Kotlin Multiplatform and Compose Multiplatform: a shared experimentation library for consistent experiment assignments across Android and iOS, and hosting an Android design system in a web browser. ### Source excerpt Introduction For the majority of Booking.com travelers, mobile is the primary channel for researching, planning, and booking trips. Recent data shows that over 80% of travelers rely on a mobile app during the research phase, with more than half of all bookings occurring on mobile devices. Consequently, the Android and iOS platforms are critical to the company's product strategy; engineering choices made here have significant repercussions for the entire organisation. To maintain agility at this scale, two elements must function in unison: Strict decision validation: At any time, Booking.com manages over 1,000 simultaneous experiments across its product suite, with hundreds active on mobile. Every minor adjustment undergoes A/B testing via our proprietary experimentation library before reaching the user. A unified design system ensures product consistency and makes design goals transparent to all contributors, not just maintenance engineers. This article examines two specific engineering challenges solved using Kotlin Multiplatform (KMP) and Compose Multiplatform (CMP): Developing a shared experimentation library to ensure uniform experiment assignments across Android and iOS. Using Compose Multiplatform to host our Android design system in a web browser, bridging the gap between design concepts and implementation. While both cases use the same underlying technology, each provides unique insights into multiplatform development. Use case 1: shared experimentation library on Android and iOSThe problem with two implementations Historically, our internal experimentation library, responsible for managing experiment assignments, evaluations, and tracking on mobile, was maintained as two distinct codebases: a mix of Java and Kotlin for Android and Objective-C for iOS. While intended to be identical, managing two languages with fluctuating team resources inevitably led to logic drift. Discrepancies in event-tracking and experiment-fetching behaviours emerged, though they wer ## Kotlin in 3 minutes DevFeed: [Kotlin in 3 minutes]() Original publisher: [Read original article]() Published: 2026-05-25T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Programming](), [multiplatform](), [Java](), [compose-multiplatform](), [Ktor](), [Spring Boot]() Tags: [compiler](), [compose-multiplatform](), [java](), [kotlin](), [ktor](), [multiplatform](), [null-safety](), [spring-boot](), [workshop-learning-programming]() ### AI overview A concise overview of Kotlin covering its interoperability with Java, compilation to JVM bytecode, JavaScript, and native platforms, and its use across Android, backend, iOS, desktop, and web development. It also introduces Kotlin's type inference and null-safety features. ### Source excerpt The essence of Kotlin, what is it and why it gets so popular. ## Migrating from Koin DSL to Koin Annotations in a Multimodule Project: A Step-by-Step Guide DevFeed: [Migrating from Koin DSL to Koin Annotations in a Multimodule Project: A Step-by-Step Guide]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-04-24T07:18:23Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [multiplatform](), [compose-multiplatform](), [Gradle](), [Code generation]() Tags: [code-generation](), [compose](), [compose-multiplatform](), [gradle](), [guide](), [koin](), [kotlin](), [ksp](), [multi-module-project](), [tutorial]() ### AI overview A step-by-step tutorial for migrating a Compose Multiplatform multimodule project from Koin DSL to Koin Annotations. It covers adding Koin Annotations and KSP dependencies, creating a Gradle convention plugin, enabling the setup in a module, and replacing manual Koin definitions with annotation-based registration. ### Source excerpt Hey friends πŸ‘‹ Today we're going to explore how to migrate a Compose Multiplatform multi-module project from Koin DSL to Koin Annotations. We'll take a hands-on approach, diving deep into a project example built by the CodandoTV community. ⚠ In this tutorial, we won't cover the new Koin compiler. It's a significant improvement that simplifies much of the complexity we currently deal with when using KSP, but it deserves its own dedicated deep dive. A person's hand fitting a piece into a puzzle -- Unplash by rosssneddonFirst step: Setup Koin Annotations dependency First thing is let's make sure we are running the latest version of Koin. For that, visit our documentation. After that, let's add our Koin Annotations dependency into the libs.versions.toml . // gradle/libs.versions.toml [versions] koin-annotations = "" ksp = "" ... [libraries] ... com-google-devtools-ksp-gradle-plugin = { module = "com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin", version.ref = "ksp" } koin-annotations = { module = "io.insert-koin:koin-annotations", version.ref = "koin-annotations" } koin-ksp-compiler = { module = "io.insert-koin:koin-ksp-compiler", version.ref = "koin-annotations" } KSP is also required, as it enables the code generation used by Koin Annotations. After adding the dependencies, run a Gradle sync to make them available to the project. Let's make sure we have the ksp plugin enabled in the root gradle project: // root/build.gradle.kts plugins { alias(libs.plugins.ksp) apply false ... } Let's head over to the build-logic folder and encapsulate all this setup inside a new Gradle convention plugin. To make this work, we need to add KSP as a library dependency: // build-logic/build.gradle.kts ... dependencies { implementation(libs.com.google.devtools.ksp.gradle.plugin) } Again, let's run Gradle sync 🐘 Second step: Create your conventional Gradle Plugin Inside of your build-logic , let's create a new custom plugin, we can call it com.st ## The KotlinConf 2026 talks that we're excited about - Kevin Schildhorn DevFeed: [The KotlinConf 2026 talks that we're excited about - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2026-03-03T00:00:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [Kotlin](), [compose-multiplatform](), [kotlin-native](), [iOS development](), [ui](), [amazon](), [Library]() Tags: [amazon](), [android](), [compose-multiplatform](), [ios](), [ios-development](), [js](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [kotlinconf](), [library](), [talks](), [ui]() ### AI overview A Touchlab commentary selects KotlinConf 2026 talks covering Kotlin/Native integration, Kotlin Multiplatform project organization and compilation times, Compose Multiplatform UI performance and animation, and iOS development with KMP at Amazon. ### Source excerpt The KotlinConf 2026 schedule was recently announced and there are a lot of talks to be excited about. We decided to compile a list of the talks we're excited to see. ## Announcing Landscapist Core: A New Image Loading Library for Android & Compose Multiplatform DevFeed: [Announcing Landscapist Core: A New Image Loading Library for Android & Compose Multiplatform]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-01-04T09:21:25Z Content type: release Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Kotlin Multiplatform](), [compose-multiplatform](), [Library](), [cross-platform](), [Android](), [ui](), [Mobile]() Tags: [android](), [code](), [compose](), [compose-multiplatform](), [cross-platform](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [library](), [mobile](), [multiplatform](), [ui]() ### AI overview The article introduces Landscapist Core, a standalone Kotlin Multiplatform image-loading engine, along with Landscapist Image, its Compose Multiplatform UI companion. It explains the libraries' goal of providing consistent image loading across Android, iOS, Desktop, and Wasm without duplicated or platform-specific implementations. ### Source excerpt Unsplash@britishlibrary Image loading has always been a fundamental challenge in mobile and cross-platform development. While Android developers have relied on battle-tested libraries like Glide, Coil, and Fresco for years, the rise of Kotlin Multiplatform has created a gap: how do you load images consistently across Android, iOS, Desktop, and Wasm without duplicating code or depending on platform-specific solutions? This is precisely the problem Landscapist Core solves. In this article, you'll explore the architecture behind Landscapist Core, a standalone Kotlin Multiplatform image loading engine, and Landscapist Image, its Compose Multiplatform UI companion. You'll examine the design decisions that make this library exceptionally lightweight, understand how it achieves cross-platform consistency, and learn practical patterns for integrating it into your applications. Whether you're building a consumer app or a library/SDK that needs to minimize its footprint, understanding Landscapist's approach offers valuable insights into modern image loading architecture. If you want to deeply explore the how and why behind Kotlin, from core language fundamentals and internal mechanisms to API design, check out Practical Kotlin Deep Dive, a new Kotlin book by this author. Practical Kotlin Deep Dive | Master Kotlin, Coroutines, Flow & Multiplatform The problem with existing solutions Before diving into Landscapist Core, it's worth understanding why a new image loading library is needed when mature solutions already exist. When Compose Multiplatform emerged as a serious cross-platform UI framework, the image loading story remained fragmented. Developers cobbled together solutions: Glide/Coil on Android, platform-specific loaders elsewhere, or custom implementations that duplicated effort. This has been a long-standing item on my TODO list since the initial launch of the Landscapist library in 2020. Over time, I found myself looking for: A unified solution: consistent APIs and be ## Using Navigation 3 with Compose Multiplatform DevFeed: [Using Navigation 3 with Compose Multiplatform]() Original publisher: [Read original article]() Published: 2025-11-15T00:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [compose-multiplatform](), [navigation](), [Compose](), [Google](), [Kotlin](), [ui]() Tags: [adaptive](), [compose-multiplatform](), [google](), [kmp](), [kotlin](), [material3](), [multiplatform](), [navigation](), [ui]() ### AI overview A tutorial on using Navigation 3 with Compose Multiplatform in a shared Kotlin Multiplatform project. It covers dependencies, back-stack-based navigation, route mapping, and adaptive list/detail layouts using Material3 Adaptive Navigation3. ### Source excerpt Navigation 3 is a new Compose based navigation library from Google that's designed with ease of use and flexibility in mind. ## Introducing Compose Unstyled boilerplates DevFeed: [Introducing Compose Unstyled boilerplates]() Original publisher: [Read original article]() Author: Alex Styl Published: 2025-10-23T00:00:00Z Content type: release Language: en Sources: [Composables - Concise, no-fluff video tutorials for Android developers]() Topics: [Compose](), [compose-multiplatform](), [Template](), [Android](), [multiplatform](), [Boilerplate]() Tags: [android](), [building](), [compose](), [compose-multiplatform](), [design](), [docs](), [getting-started](), [gradle](), [multiplatform](), [tokens]() ### AI overview The article announces official Compose Unstyled Boilerplates for Android and Compose Multiplatform apps. The templates are designed to provide minimal project setups with custom theming, themable components, Lucide Icons, multiplatform support, and other included configuration and development features. ### Source excerpt Start building apps with Compose Unstyled in seconds. [Next page]()