# 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.

## Migrating a Real Android App to Kotlin Multiplatform 4/4 -- Shipping WebAssembly to Productio

DevFeed: [Migrating a Real Android App to Kotlin Multiplatform 4/4 -- Shipping WebAssembly to Productio](<https://devfeed.tech/articles/migrating-a-real-android-app-to-kotlin-multiplatform-4-4-shipping-webassembly-to-productio-140455.md>)

Original publisher: [Read original article](<https://proandroiddev.com/migrating-a-real-android-app-to-kotlin-multiplatform-4-4-shipping-webassembly-to-productio-e863738a8151?source=rss----c72404660798---4>)

Author: Daniel Voko

Published: 2026-11-17T19:49:30Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [compose-for-web](<https://devfeed.tech/topics/compose-for-web.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [sqldelight](<https://devfeed.tech/topics/sqldelight.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [production](<https://devfeed.tech/tags/production.md>), [splash-screen](<https://devfeed.tech/tags/splash-screen.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

A Kotlin Multiplatform app that builds for WebAssembly still needs browser-specific production work. The excerpt describes an inline HTML splash screen for a roughly 19 MB bundle, a spinner with visible timeout and error states instead of a misleading byte-based progress bar, and browser-history navigation whose fragment routes must stay synchronized with backend redirects. It also covers a server-side image proxy needed because Strava's CDN lacks CORS headers, with requests tagged by client so native apps keep using original URLs. In the browser, SQLDelight uses sql.js with a hand-maintained schema mirror, creating a risk that schema changes break web only. A deployed-origin `blob:` media issue required a custom Coil mapper and fetcher. These examples show how browser loading, routing, security, storage and media behavior can affect architecture and maintenance.

### Source excerpt

The wasm build runs locally in minutes. ./gradlew wasmJsBrowserDevelopmentRun, a browser tab opens, the app is there. It feels finished. It isn't, and the reason is the subject of this article. The browser isn't a fourth target that happens to render the same Compose code. It's a host with its own rules about what paints when, who owns navigation, what a page is allowed to fetch, and what a database even is. Compose Multiplatform hides none of that -- it just gets your UI onto the canvas, and then you're in someone else's house. Getting a multiplatform app to build is different from making it production-ready. Everything below is a thing that worked locally and didn't work for users. Nothing paints until the bundle arrives On Android, the launcher draws your icon the instant the user taps it. The OS owns that moment, and you get it for free. On the web you get nothing. A blank page, for as long as it takes to fetch a wasm bundle -- around 19MB -- uncompressed, and around 6.5MB Brotli transfer size -- and compile it. Users don't read that as "loading", they read it as broken, and they leave before the first frame. So the first thing I had to write for the web was something Android had given me for a decade: a splash screen. It lives inline in index.html, CSS and all, specifically so it costs no request of its own -- a splash that waits on a stylesheet defeats the purpose. The color values are a hand-copied duplicate of the theme tokens in core:designsystem, so the canvas takes over without a colour change. It's duplication I'd normally reject, and here there's no alternative: the theme lives in Kotlin inside the bundle that hasn't downloaded yet. It also has a known flaw I decided to keep. The splash follows the OS colour scheme, while the app also honours a theme the user picked by hand in settings. Someone who forced the theme against their OS gets one flash at the handover. Reading their choice would mean parsing the stored settings JSON from plain JavaScript, and coup

## A Rough First Sketch of the Compose Runtime

DevFeed: [A Rough First Sketch of the Compose Runtime](<https://devfeed.tech/articles/a-rough-first-sketch-of-the-compose-runtime-133218.md>)

Original publisher: [Read original article](<https://www.grokkingandroid.com/a-rough-first-sketch-of-the-compose-runtime/>)

Author: Wolfram Rittmeyer

Published: 2026-11-13T10:26:08Z

Content type: article

Language: en

Sources: [Grokking Android](<https://devfeed.tech/sources/grokking-android.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Compose Compiler](<https://devfeed.tech/topics/compose-compiler.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [cache](<https://devfeed.tech/tags/cache.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-compiler](<https://devfeed.tech/tags/compose-compiler.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [composer](<https://devfeed.tech/tags/composer.md>), [composition](<https://devfeed.tech/tags/composition.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

Compose's runtime links composable code to a UI tree and schedules updates when state changes. A Composition owns a Composer and an Applier; each call to setContent() creates a Composition. The Composer works with the SlotTable, whose groups and slots cache structure and values used to decide what to update or skip during recomposition. When the Snapshot system commits changes to mutable state, it notifies observers; the lifecycle-aware Recomposer then schedules needed recomposition on a frame clock. The Applier manages nodes and depends on their type: UI compositions commonly use UiApplier or DefaultUiApplier, while vectors and other environments can use different appliers. The Owner connects the runtime to the platform's view or controller system and handles events such as layout, invalidation, and accessibility. This is a high-level sketch; the author says detailed explanations are planned for later posts.

### Source excerpt

In my series about the inner workings of Jetpack Compose (or Compose Multiplatform), I repeatedly will mention certain parts of the runtime. While I will cover the most relevant parts in separate posts, I provide in this post a high-level view of things. It should help you understand the overall picture while my blog post [...] Continue Reading "A Rough First Sketch of the Compose Runtime" The post A Rough First Sketch of the Compose Runtime appeared first on Grokking Android.

## Migrating a Real Android App to Kotlin Multiplatform 3/4 -- Sharing the UI without losing safety net

DevFeed: [Migrating a Real Android App to Kotlin Multiplatform 3/4 -- Sharing the UI without losing safety net](<https://devfeed.tech/articles/migrating-a-real-android-app-to-kotlin-multiplatform-3-4-sharing-the-ui-without-losing-safety-net-124797.md>)

Original publisher: [Read original article](<https://proandroiddev.com/migrating-a-real-android-app-to-kotlin-multiplatform-3-4-sharing-the-ui-without-losing-safety-net-f74a6bf408ae?source=rss----c72404660798---4>)

Author: Daniel Voko

Published: 2026-11-09T14:53:26Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [robolectric](<https://devfeed.tech/topics/robolectric.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [about](<https://devfeed.tech/tags/about.md>), [all](<https://devfeed.tech/tags/all.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-library](<https://devfeed.tech/tags/android-library.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [animation](<https://devfeed.tech/tags/animation.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [article](<https://devfeed.tech/tags/article.md>), [away](<https://devfeed.tech/tags/away.md>), [build](<https://devfeed.tech/tags/build.md>), [classes](<https://devfeed.tech/tags/classes.md>), [code](<https://devfeed.tech/tags/code.md>), [code-smell](<https://devfeed.tech/tags/code-smell.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [safety](<https://devfeed.tech/tags/safety.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Most BikeHub composables moved to Kotlin Multiplatform's commonMain with few code changes; the harder work was adapting Android-centered tooling. The author had first moved UI state and logic into plain Kotlin through Ouroboros-Compose, avoiding Android ViewModel dependencies across 38 feature modules. Android-specific seams were limited and isolated behind expect/actual or an ExternalNavigator interface. Of 13,843 androidMain lines, 9,653 were previews; Compose Preview Screenshot Testing did not work in a KMP module, so the project uses Roborazzi under Robolectric in androidHostTest. A convention plugin enables screenshot tests across 40 modules and copies centralized Compose Multiplatform resources into host-test assets, relying on a reflective workaround to expose their generated location. The setup checks Android rendering only, leaves iOS and web unverified, and stores 55 MB of PNG baselines; half-scale captures limit their size. The account emphasizes auditing previews, resources, plugins and tests before changing module types.

### Source excerpt

Migrating a Real Android App to Kotlin MultiplatformPart 3: Sharing the UI without losing the safety net Part 2 ended on a pattern: the code that moved most easily was the code that knew nothing about Android. By that logic the UI layer should have been the worst part of the migration. It touches the screen, the system bars, the keyboard, the back gesture -- everything that is unmistakably a platform. And, much to my amazement, it wasn't. The composables moved about as easily as the domain models did. What didn't move was everything around them. The resource system, the build plugins, the preview tooling and the screenshot tests were all built on the assumption that a Compose module is an Android library module. Once that stopped being true, the application code was fine and the ecosystem around it wasn't. Sharing application code turned out to be easier than sharing the ecosystem around it. That's the whole article. What moved easily Most composables moved to commonMain unchanged. Layout, state, theming, animation -- Compose Multiplatform covers the surface BikeHub uses, and the diff for a typical screen was mostly imports. Two things made this smoother than it would otherwise have been. The UDF layer went first. Every feature module in BikeHub uses Ouroboros-Compose, a small unidirectional-data-flow library (influenced by Spotify's Mobius, that I used back then, when views and fragments ruled the android UI). It abstracts the ViewModel away and keeps the UI logic in plain, testable classes. I refactored it to KMP as step 0 of the whole migration, before touching a single feature module. That ordering mattered more than it looks. Because the UI logic doesn't sit inside an Android ViewModel, there was no androidx.lifecycle dependency threaded through 38 feature modules waiting to be unpicked. The state holders were already just Kotlin. Android platform code in the UI layer was already a code smell. I'd treated it that way for years, so there wasn't much of it to find.

## Compose Multiplatform: Why You Shouldn't Build Your Whole iOS App in Compose

DevFeed: [Compose Multiplatform: Why You Shouldn't Build Your Whole iOS App in Compose](<https://devfeed.tech/articles/compose-multiplatform-why-you-shouldn-t-build-your-whole-ios-app-in-compose-122709.md>)

Original publisher: [Read original article](<https://proandroiddev.com/compose-multiplatform-why-you-shouldnt-build-your-whole-ios-app-in-compose-9e1e8c978a5b?source=rss----c72404660798---4>)

Author: Anatolii Frolov

Published: 2026-11-09T00:22:32Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [liquid glass](<https://devfeed.tech/topics/liquid-glass.md>), [bottom-navigation](<https://devfeed.tech/topics/bottom-navigation.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-app-development](<https://devfeed.tech/tags/ios-app-development.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [liquid-glass](<https://devfeed.tech/tags/liquid-glass.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [swiftui](<https://devfeed.tech/tags/swiftui.md>), [uikit](<https://devfeed.tech/tags/uikit.md>)

### AI overview

The article's ClariMeal example keeps product screens and business logic shared in Kotlin and Compose while UIKit owns iOS navigation and system controls. A UIKit tab bar can adopt Apple's appearance changes, including the iOS 26 detached Add control; on iOS 17-25, the app draws the Add circle itself. Compose screens are hosted in native view controllers, and navigation events go to the native stack, avoiding a competing Compose back stack. Android uses Compose for screens, navigation, and its bottom bar. Product-specific cards and charts remain shared, while copied iOS measurements in Compose design tokens still require review as iOS changes. Native integration still involves SDK updates, integration work, and testing; a full SwiftUI rewrite is presented as unnecessary for this app's goals.

### Source excerpt

How to keep your screens shared while letting iOS handle navigation and system controls. Compose Multiplatform lets Android developers reuse Kotlin and Compose screen code on iOS. You keep the language and the UI toolkit you already know, and the same screens run on an iPhone. But a screen that runs on iOS does not automatically follow iOS. You can build the whole app in Compose, including the tab bar and navigation, and Compose Multiplatform supports the back gesture and iOS-style transitions. What it cannot do is redraw your own tab bar when Apple redesigns the system one. A Compose copy of a system control stays the way you drew it. I faced this choice while building ClariMeal, a calorie tracker for iOS and Android. I wanted the product screens shared, and I wanted the navigation and system controls to come from iOS itself. The reason was maintenance. Liquid Glass in iOS 26 is a system material, and Compose cannot draw it. On Android, ClariMeal has its own glass tab bar built in Compose, and it looks good there. On iOS it would still be an imitation: it looks different and does not behave like the system bar. Only the system bar follows iOS when Apple changes it. That did not require a SwiftUI rewrite. Screen content stayed in Compose and the logic stayed in Kotlin, while native iOS components took over navigation and system interactions. This article explains which parts of your iOS app are better left to the system when you want them to follow iOS, where I drew that boundary, and what it still cost. 1. The tab bar belongs to the operating system Start with one comparison: the same tab bar on Android, iOS 18 and iOS 26. On Android, Compose draws the whole bar, including the + button in the middle. On iOS, the tab bar comes from UIKit, and the + button shows where the line between the system and the app runs. The app supports iOS 17 and later. Before iOS 26, the + button is a circle in the middle of the system tab bar, and that circle is my code. On iOS 26, I rep

## Your Compose Code, on More Screens and Less CPU

DevFeed: [Your Compose Code, on More Screens and Less CPU](<https://devfeed.tech/articles/your-compose-code-on-more-screens-and-less-cpu-109731.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/compose-on-more-screens/>)

Author: Shai Almog

Published: 2026-10-31T00:00:00Z

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [battery](<https://devfeed.tech/tags/battery.md>), [battery-life](<https://devfeed.tech/tags/battery-life.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [button](<https://devfeed.tech/tags/button.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [card](<https://devfeed.tech/tags/card.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [codename](<https://devfeed.tech/tags/codename.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

Codename One can build Kotlin Multiplatform Compose code from the same `commonMain` sources: Kotlin compiles to JVM bytecode with the Compose compiler plugin, uses upstream Compose runtime and coroutines, and maps the UI layer to Codename One components before ParparVM creates native binaries. In the Keynote app benchmark, all three release builds reached the same frame rate, while Compose on Codename One used about 4 ms of CPU per frame versus about 17 ms for Compose Multiplatform. The measurements used an iPhone 17 Pro simulator, programmatic scrolling, and five runs; startup comparisons are limited because the Compose Multiplatform marker precedes drawing and most startup time came from iOS. The article reports a 16.8 MB executable versus 22.9 MB for Compose Multiplatform, and says imperative Java on Codename One was faster and about half the size of its Compose version. Teams can mix Compose and Codename One components per screen. The port is incomplete: `LazyColumn(reverseLayout = true)` is unsupported, and its build targets JVM 11.

### Source excerpt

Kotlin Multiplatform code with Compose now builds as a Codename One app, with about a quarter of the CPU work per frame on our benchmark screen.

## Flutter Better in Java

DevFeed: [Flutter Better in Java](<https://devfeed.tech/articles/flutter-better-in-java-109732.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/flutter-better-in-java/>)

Author: Shai Almog

Published: 2026-10-30T00:00:00Z

Content type: comparison

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Android](<https://devfeed.tech/topics/android.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [JavaFX](<https://devfeed.tech/topics/javafx.md>), [Swing](<https://devfeed.tech/topics/swing.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [maven-plugin](<https://devfeed.tech/topics/maven-plugin.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [dart](<https://devfeed.tech/tags/dart.md>), [faster](<https://devfeed.tech/tags/faster.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [java](<https://devfeed.tech/tags/java.md>), [javafx](<https://devfeed.tech/tags/javafx.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [memory](<https://devfeed.tech/tags/memory.md>)

### AI overview

Codename One can import Flutter apps from their original Dart source and build them as Codename One apps. In the October 29 CI comparison of Flutter Gallery release builds, Codename One led on all 26 measured metrics; on Android it used 4.7 MB of executable code versus 20.6 MB and started in about a third of the time. The importer copies app code and assets, adds a Dart runtime implemented through Java transpilation, and builds with Maven without requiring the Dart or Flutter SDK. The result is not pixel-identical: some text wrapping and avatar shapes differ, Dart support is experimental, some callbacks or parameters are ignored, and only one large app has been verified. The author advises testing every relied-on interaction. Android timings use an emulator; iOS start-up and memory and web start-up were not measured. The post attributes the smaller native builds partly to ahead-of-time Java compilation and dead-code elimination, while noting the compatibility layer itself adds overhead.

### Source excerpt

Codename One now builds Flutter apps from their Dart source, and the result starts faster, uses less memory and ships less code than Flutter's own release build. This week also covers KMP, Swing and JavaFX, Android apps and more.

## Migrating a Real Android App to Kotlin Multiplatform 1/4 -- Before the Migration

DevFeed: [Migrating a Real Android App to Kotlin Multiplatform 1/4 -- Before the Migration](<https://devfeed.tech/articles/migrating-a-real-android-app-to-kotlin-multiplatform-1-4-before-the-migration-107101.md>)

Original publisher: [Read original article](<https://proandroiddev.com/migrating-a-real-android-app-to-kotlin-multiplatform-1-4-before-the-migration-8b1d16f68747?source=rss----c72404660798---4>)

Author: Daniel Voko

Published: 2026-10-29T17:33:38Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [app](<https://devfeed.tech/tags/app.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bike](<https://devfeed.tech/tags/bike.md>), [browser](<https://devfeed.tech/tags/browser.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [core](<https://devfeed.tech/tags/core.md>), [dagger](<https://devfeed.tech/tags/dagger.md>), [data](<https://devfeed.tech/tags/data.md>), [domain](<https://devfeed.tech/tags/domain.md>), [feature](<https://devfeed.tech/tags/feature.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [migration](<https://devfeed.tech/tags/migration.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>)

### AI overview

BikeHub moved from native Android to Kotlin Multiplatform while keeping Android releasable at every step; about 84% of its Kotlin now lives in commonMain, with Android, iOS and WebAssembly targets. The migration benefited from early choices of KMP-compatible Ktor Client, Koin and SQLDelight, so networking, dependency injection and persistence mostly moved rather than needing replacement. Modularization provided a module-by-module migration order, limited failures to individual modules and made it practical to pause between releases. Android-specific code was pushed behind interfaces at platform boundaries, and the iOS app was kept to a thin Swift entry point and platform wiring. The author says they would add another target to CI as soon as the first module is converted, since Android-only code can compile in commonMain while still failing on other platforms; smaller, single-responsibility core modules would also have saved time.

### Source excerpt

BikeHub is KMP app that runs on Android, on iOS and in the browser via WebAssembly. It started as native Android. Around 84 percent of its Kotlin code lives in commonMain. At no point during the migration did the Android app stop being releasable. This isn't a story about a heroic rewrite. The real story is less dramatic and, I think, more useful: the migration was easier than it could have been because of choices made long before it started. How much a platform shift hurts is decided largely by architectural decisions made years earlier, often for entirely different reasons. This series isn't a KMP tutorial either. This is a case study of a real app that already had users, history and assumptions baked into its code: what moved easily, what hurt, and what I'd do differently. Part 1 covers the foundations. Where it started BikeHub is a bike maintenance tracker. It pulls your mileage from Strava, tracks wear on parts like chains, cassettes and brake pads, and tells you when something is due for a service. It is a side project, that has its own story. Initially started to try out new libraries and best practices and was for an audience of one. Later it turned into something I wanted to release to wider audiences. It started as a native Android app, split into 24 feature modules and 14 core modules (before the start of the migration). Today it has both more feature modules and more granularized core modules: Where it started Kotlin, Jetpack Compose, a layered architecture, UDF in the presentation layer, and a reasonable number of modules make it a fairly standard modern Android stack. What made the difference later wasn't how modern each piece was, but how portable it turned out to be. Choices made before the migration Ktor Client and Koin were in the app from day one, and both already supported Kotlin Multiplatform. Ktor Client is something I prefer over Retrofit, and Koin is something I prefer over Dagger. When the data and domain layers moved to shared code, the net

## Improving the Smoothness of Android Compose Screens

DevFeed: [Improving the Smoothness of Android Compose Screens](<https://devfeed.tech/articles/improving-the-smoothness-of-android-compose-screens-100955.md>)

Original publisher: [Read original article](<https://proandroiddev.com/improving-the-smoothness-of-android-compose-screens-47607da631c8?source=rss----c72404660798---4>)

Author: rayford

Published: 2026-10-26T13:33:21Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Compose Compiler](<https://devfeed.tech/topics/compose-compiler.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Android](<https://devfeed.tech/topics/android.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-compose](<https://devfeed.tech/tags/android-compose.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [compose-performance](<https://devfeed.tech/tags/compose-performance.md>), [ide](<https://devfeed.tech/tags/ide.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [monitoring-and-evaluation](<https://devfeed.tech/tags/monitoring-and-evaluation.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [performance](<https://devfeed.tech/tags/performance.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [recomposition](<https://devfeed.tech/tags/recomposition.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [screen](<https://devfeed.tech/tags/screen.md>), [skip](<https://devfeed.tech/tags/skip.md>), [stable](<https://devfeed.tech/tags/stable.md>), [state](<https://devfeed.tech/tags/state.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Compose screen performance depends on how often recomposition is triggered, parameter stability, and where state changes occur in the UI hierarchy. Frequent state changes are identified as a common source of excessive recomposition; declaring unchanged values as `val` can help avoid unnecessary updates, and IDE plugins can expose composable parameter stability. To find changing values, Rebugger compares state and parameters during recomposition and logs differences. The excerpt then describes Compose Monitor, which injects monitoring into annotated composables at compile time: its Android ASM approach uses two bytecode passes but depends on compiler-generated patterns that may change and supports only Android. Its proposed Kotlin compiler IR approach inserts monitoring calls before function exits and is intended to support Kotlin versions 2.0 and later, with platform-specific compilation backends. The excerpt notes that IR plugin APIs differ across Kotlin versions.

### Source excerpt

As Android development moves from the legacy View system to Jetpack Compose, the more modern Compose approach brings a very different development experience. The two also differ substantially in their tooling and performance-tracking workflows. In addition to frame-rate monitoring, the View system commonly relies on ANR reports to identify problematic stack traces. Compose, however, updates the UI in response to data changes, so an ANR stack trace may not point to the code responsible for the issue. Factors That Affect Compose Screen Performance Compose keeps screen state in memory. When that state changes, it triggers recomposition of the corresponding parts of the UI. The following factors affect rendering performance: How frequently recomposition is triggered Whether method parameters are stable The UI hierarchy in which the state change is triggered Stability is one of the factors Compose uses to decide whether it can skip recomposition. In day-to-day development, declaring values that do not change as val can help avoid unnecessary state updates and recompositions. Open-source IDE plugins can also show whether parameters of composable functions are stable directly in the editor. Compose Stability Analyzer The most common cause of Compose performance issues is frequent state changes that trigger excessive recompositions. Identifying the frequently changing state is the key to finding the root cause. Monitoring Compose-Triggered UI Updates One approach is to collect all state and parameters, compare their values whenever a composable function recomposes, and print the differences to logcat. Tools such as Rebugger already provide this capability, with an IDE plugin that can add the monitoring code. GitHub - theapache64/rebugger: A simple Compose Multiplatform library designed to print the reason for recomposition in your console/Logcat window." Minimizing Intrusion by Injecting Monitoring Code Automatically Most of the time, state changes do not need to be monitor

## Bring to life your SVGs in the Multiplatform project

DevFeed: [Bring to life your SVGs in the Multiplatform project](<https://devfeed.tech/articles/bring-to-life-your-svgs-in-the-multiplatform-project-99316.md>)

Original publisher: [Read original article](<https://proandroiddev.com/bring-to-life-your-svgs-in-the-multiplatform-project-0d298c15c22a?source=rss----c72404660798---4>)

Author: Robert Levonyan

Published: 2026-10-25T16:37:58Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [SVG](<https://devfeed.tech/topics/svg.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [animation](<https://devfeed.tech/tags/animation.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-app-development](<https://devfeed.tech/tags/ios-app-development.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [svg](<https://devfeed.tech/tags/svg.md>), [vector](<https://devfeed.tech/tags/vector.md>), [xml](<https://devfeed.tech/tags/xml.md>)

### AI overview

The article shows how to build a looping, animated offline ghost in Compose Multiplatform from SVG paths, without shipping a GIF, Lottie file or video. It draws the ghost before a static gravestone so the stone hides it, then animates its rise, sway, drift and sink with four synchronized keyframe tracks in one `rememberInfiniteTransition`; viewport clipping makes it disappear underground. A shared AGSL/SkSL shader adds pixel wobble: Android uses `RuntimeShader` and `RenderEffect` on API 33+, while iOS, Desktop and Web use Skiko's runtime shader APIs through a shared `skikoMain` source set. Older Android devices skip the shader but retain the basic motion. The article also describes a frame-clock time source and warns that shader sampling should stay 1:1 to avoid scaling the artwork.

### Source excerpt

Let's be honest: "No internet connection" is the saddest screen in any app. Your user wanted to do something, the Wi-Fi said no, and now they're staring at a grey box with an OK button. We can do better. We can give them a ghost. The idea comes from the lovely No internet connection GIF on Dribbble: the Wi-Fi signal has died, it's been properly buried, and its ghost keeps popping out of the grave to say hi. Before writing any animation code, let's meet the cast: The sky -- a purple gradient. The gravestone -- a static drawable. It just stands there. The deceased -- Icons.Rounded.WifiOff carved into the stone. RIP. The ghost -- the star. Rises, sways, drifts, sinks. Forever. Three of the four cast members just stand still, so they're plain Image composables. All the drama goes into one vector. And since everything lives in commonMain, the same ghost haunts Android, iOS, Desktop and the Web (Wasm and JS). One ghost, five houses. Very efficient haunting. The stage is a 300dp Box sitting on top of the gradient: Column( modifier = Modifier .fillMaxSize() .background( brush = Brush.linearGradient( colors = listOf(gradientStartColor, gradientEndColor), tileMode = TileMode.Clamp, ) ), verticalArrangement = Arrangement.Center, horizontalAlignment = Alignment.CenterHorizontally, ) { Box(modifier = Modifier.size(300.dp)) { // 1. the ghost (drawn first, so it sits behind the stone) // 2. the gravestone // 3. the dead Wi-Fi signal } } Look at the order inside the Box. The ghost is drawn first, so the gravestone is painted right over it. That's our "hiding behind the grave" trick, and it costs exactly zero lines of masking code. In Compose, whoever comes last gets to stand in front -- just like in a group photo. From SVG to a composable vector The gravestone is the easy one. It never moves (it's a gravestone, it's had a lot of practice). I converted its SVG to a vector XML with Android Studio's Vector Asset tool, dropped it into commonMain/composeResources/drawable, and loaded it with

## Morphing a Floating Action Button into a Dialog in Compose Multiplatform

DevFeed: [Morphing a Floating Action Button into a Dialog in Compose Multiplatform](<https://devfeed.tech/articles/morphing-a-floating-action-button-into-a-dialog-in-compose-multiplatform-96502.md>)

Original publisher: [Read original article](<https://joebirch.co/uncategorized/morphing-a-floating-action-button-into-a-dialog-in-compose-multiplatform/>)

Author: hitherejoe

Published: 2026-10-23T02:06:12Z

Content type: tutorial

Language: en

Sources: [Joe Birch](<https://devfeed.tech/sources/joe-birch.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Interaction Design](<https://devfeed.tech/topics/interaction-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Library](<https://devfeed.tech/topics/library.md>), [callback](<https://devfeed.tech/topics/callback.md>)

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [button](<https://devfeed.tech/tags/button.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [dialog](<https://devfeed.tech/tags/dialog.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

MorphingFab animates a floating action button into a dialog by treating both as one Surface driven by a single progress value. It interpolates position, size, corner radius, and color, while separate fade thresholds hide the icon early and reveal dialog content late; the content is measured at its final size so text does not reflow during the morph. At rest the FAB stays in the composable tree so other screen touches work. During animation it moves to a full-window Popup overlay with a scrim, then returns to the tree when collapsed. The component receives expanded state from its caller and only reports click or dismissal requests; Android handles system back, while the iOS back handler is currently a no-op. It should be placed at the screen root because it measures its parent to locate the FAB; for Scaffold's floating action button slot, the library provides an anchor-based placement.

### Source excerpt

When a floating action button kicks off an action that requires a paid plan, such as when free users hit their binder limit in Sleevd, we show an alert dialog to prompt the user to upgrade. In most apps, this dialog fades in at the centre of the screen with no connection to the button... Continue reading ->

## Moving from SKIE to Swift export in a Kotlin Multiplatform project

DevFeed: [Moving from SKIE to Swift export in a Kotlin Multiplatform project](<https://devfeed.tech/articles/moving-from-skie-to-swift-export-in-a-kotlin-multiplatform-project-84502.md>)

Original publisher: [Read original article](<https://johnoreilly.dev/posts/peopleinspace-swift-export/>)

Published: 2026-10-09T23:00:00Z

Content type: tutorial

Language: en

Sources: [John O'Reilly](<https://devfeed.tech/sources/john-o-reilly.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [SwiftUI](<https://devfeed.tech/topics/swiftui.md>), [compose-hot-reload](<https://devfeed.tech/topics/compose-hot-reload.md>)

Tags: [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [skie](<https://devfeed.tech/tags/skie.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swift-export](<https://devfeed.tech/tags/swift-export.md>), [swift-interop](<https://devfeed.tech/tags/swift-interop.md>)

### AI overview

The article explains how the PeopleInSpace Kotlin Multiplatform sample moved its SwiftUI client from an Objective-C framework with SKIE to Kotlin's alpha Swift export. It details Gradle and Xcode setup, reducing generated bindings by controlling exported APIs and dependencies, and adapting Swift code for generated namespaces, sealed classes, and flows. The author reports that the generated Swift output fell from about 18,000 lines to about 2,600; Swift export remains in alpha.

### Source excerpt

The SwiftUI client in the PeopleInSpace Kotlin Multiplatform sample has, up to now, consumed the shared Kotlin code through a framework with a generated Objective-C API, along with SKIE to make that code nicer to use from Swift (for things like sealed classes and flows). Kotlin also has Swift export (currently in alpha) which generates Swift bindings directly, and in this article we're going to go through what was needed to move PeopleInSpace over to it. The changes are in this PR.

## Pixelating Composables in Compose Multiplatform

DevFeed: [Pixelating Composables in Compose Multiplatform](<https://devfeed.tech/articles/pixelating-composables-in-compose-multiplatform-84007.md>)

Original publisher: [Read original article](<https://joebirch.co/android/pixelating-composables-in-compose-multiplatform/>)

Author: hitherejoe

Published: 2026-10-09T13:16:22Z

Content type: tutorial

Language: en

Sources: [Joe Birch](<https://devfeed.tech/sources/joe-birch.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>)

### AI overview

The article explains how to implement pixelation for Compose Multiplatform composables using cached drawing, coarse and fine bitmaps, and optional edge feathering. It also discusses grouping child composables, choosing a block ratio, accessibility semantics, and drawing costs.

### Source excerpt

When it comes to displaying portfolio data inside of Sleevd, this is only available to users on the Ultimate plan. To hide this functionality from free users, a common approach here is to swap the value out for a placeholder or completely hide the component from view. While this works, I wanted to display the... Continue reading ->

## Discontinuing Swift Language IDE Support in the Kotlin Multiplatform Plugin

DevFeed: [Discontinuing Swift Language IDE Support in the Kotlin Multiplatform Plugin](<https://devfeed.tech/articles/discontinuing-swift-language-ide-support-in-the-kotlin-multiplatform-plugin-65024.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/kotlin/2026/10/discontinuing-swift-language-ide-support-in-the-kotlin-multiplatform-plugin/>)

Author: Anton Makeev

Published: 2026-10-05T10:46:19Z

Content type: release

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>), [Kotlin](<https://devfeed.tech/sources/kotlin-a-concise-multiplatform-language-developed-by-jetbrains-the-jetbrains-blog.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [ide](<https://devfeed.tech/topics/ide.md>)

Tags: [android-studio](<https://devfeed.tech/tags/android-studio.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [intellij](<https://devfeed.tech/tags/intellij.md>), [intellij-idea](<https://devfeed.tech/tags/intellij-idea.md>), [intellij-platform](<https://devfeed.tech/tags/intellij-platform.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-native](<https://devfeed.tech/tags/kotlin-native.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [swift](<https://devfeed.tech/tags/swift.md>)

### AI overview

JetBrains will discontinue Swift editing, syntax highlighting, and navigation in the Kotlin Multiplatform plugin beginning with IntelliJ IDEA 2026.3 and Android Studio Rabbit 2 | 2026.2.2. Running iOS apps, debugging Kotlin on iOS, Swift Export, and importing Swift packages will remain supported. JetBrains cites declining use and the engineering effort required to maintain the tooling.

### Source excerpt

Starting with IntelliJ IDEA 2026.3 and Android Studio Rabbit 2 | 2026.2.2, we're discontinuing Swift language IDE features in the Kotlin Multiplatform (KMP) plugin. This includes editing, syntax highlighting, and navigation within Swift files and between Swift and Kotlin. Running iOS applications and debugging Kotlin code on iOS will remain fully supported. Kotlin/Native functionality, such [...]

## KMP's Role In Modern Native Mobile - Sam Hill

DevFeed: [KMP's Role In Modern Native Mobile - Sam Hill](<https://devfeed.tech/articles/kmp-s-role-in-modern-native-mobile-sam-hill-61272.md>)

Original publisher: [Read original article](<https://touchlab.co/kmp-modern-mobile>)

Published: 2026-09-28T18:00:00Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Mobile](<https://devfeed.tech/topics/mobile.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile](<https://devfeed.tech/tags/mobile.md>)

### AI overview

The article considers whether AI-assisted code ports could replace Kotlin Multiplatform (KMP) for mobile teams. It argues that while AI can speed up an initial port, teams still face ongoing costs maintaining parity across platforms, and that KMP can provide a shared code foundation to limit drift.

### Source excerpt

Mobile teams are using AI to move faster than ever. Kotlin Multiplatform provides the shared code foundation which prevents drift.

## 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](<https://devfeed.tech/articles/build-setup-targets-source-sets-and-buildsrc-for-tvos-in-a-compose-multiplatform-fork-22943.md>)

Original publisher: [Read original article](<https://proandroiddev.com/build-setup-targets-source-sets-and-buildsrc-for-tvos-in-a-compose-multiplatform-fork-4d9caafa30a8?source=rss----c72404660798---4>)

Author: Sajid Ali

Published: 2026-09-14T04:24:43Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [tvOS](<https://devfeed.tech/topics/tvos.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [build](<https://devfeed.tech/tags/build.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [gradle-plugin](<https://devfeed.tech/tags/gradle-plugin.md>), [ios](<https://devfeed.tech/tags/ios.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [source](<https://devfeed.tech/tags/source.md>)

### 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

## Setting Up Koin in real project: A Step-by-Step Guide

DevFeed: [Setting Up Koin in real project: A Step-by-Step Guide](<https://devfeed.tech/articles/setting-up-koin-in-real-project-a-step-by-step-guide-22976.md>)

Original publisher: [Read original article](<https://blog.insert-koin.io/setting-up-koin-in-real-project-a-step-by-step-guide-1575e2357239?source=rss----925561f2ecdf---4>)

Author: Gabriel Bronzatti Moro

Published: 2026-09-07T12:01:03Z

Content type: tutorial

Language: en

Sources: [Koin developers](<https://devfeed.tech/sources/koin-developers-medium.md>)

Topics: [koin](<https://devfeed.tech/topics/koin.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Dependency injection](<https://devfeed.tech/topics/dependency-injection.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Learning](<https://devfeed.tech/topics/learning.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [community](<https://devfeed.tech/tags/community.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [data](<https://devfeed.tech/tags/data.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [football](<https://devfeed.tech/tags/football.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [koin](<https://devfeed.tech/tags/koin.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [module](<https://devfeed.tech/tags/module.md>), [practical](<https://devfeed.tech/tags/practical.md>), [real-world](<https://devfeed.tech/tags/real-world.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [share](<https://devfeed.tech/tags/share.md>), [simulator](<https://devfeed.tech/tags/simulator.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

The guide sets up Koin 4.2.2 in a Kotlin Multiplatform app by placing shared dependencies in commonMain and Android-specific dependencies in androidMain and the Android app module. It registers repositories as singletons, use cases as factories, and ViewModels with the Compose ViewModel DSL. A shared startKoin bridge accepts a platform configuration lambda: Android passes its Application context from onCreate(), while iOS uses an empty block and calls initialization from the SwiftUI app launch. Composables obtain ViewModels with koinViewModel() defaults, which the guide says can be overridden with fakes in tests.

### 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<WorldCupRepository> { 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](<https://devfeed.tech/articles/compose-multiplatform-is-a-business-decision-not-a-technical-one-justin-mancinelli-38181.md>)

Original publisher: [Read original article](<https://touchlab.co/compose-multiplatform-business-decision>)

Published: 2026-09-01T18:00:00Z

Content type: opinion

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Flutter](<https://devfeed.tech/topics/flutter.md>), [React Native](<https://devfeed.tech/topics/react-native.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [jetbrains](<https://devfeed.tech/topics/jetbrains.md>)

Tags: [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [react](<https://devfeed.tech/tags/react.md>), [technical](<https://devfeed.tech/tags/technical.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### 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.

## 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](<https://devfeed.tech/articles/scanning-bus-stop-codes-with-ml-kit-and-vision-in-the-galwaybus-compose-multiplatform-app-25195.md>)

Original publisher: [Read original article](<https://johnoreilly.dev/posts/galwaybus-scan-stop-kmp/>)

Published: 2026-08-06T23:00:00Z

Content type: article

Language: en

Sources: [John O'Reilly](<https://devfeed.tech/sources/john-o-reilly.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [ML Kit](<https://devfeed.tech/topics/ml-kit.md>), [cameraX](<https://devfeed.tech/topics/camerax.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [bus](<https://devfeed.tech/tags/bus.md>), [camera](<https://devfeed.tech/tags/camera.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [ml-kit](<https://devfeed.tech/tags/ml-kit.md>), [ocr](<https://devfeed.tech/tags/ocr.md>), [on-device](<https://devfeed.tech/tags/on-device.md>), [plate](<https://devfeed.tech/tags/plate.md>), [recognition](<https://devfeed.tech/tags/recognition.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [text](<https://devfeed.tech/tags/text.md>), [vision](<https://devfeed.tech/tags/vision.md>)

### AI overview

GalwayBus adds a Scan tab that reads six-digit bus stop codes and opens the matching stop's departures. Camera preview, OCR results handling, matching, and UI are coordinated in shared Compose Multiplatform code; Android uses CameraX with on-device ML Kit, while iOS uses AVCaptureSession with Apple Vision through Kotlin/Native bindings. Both platforms drop incoming frames while recognition is in progress instead of queuing them. Android camera permission is bridged through an Activity launcher and a suspend function callable by shared code. Vision's language correction is disabled to avoid turning digit sequences into words. The excerpt says matching extracts full six-digit runs and requires an exact stop-code match; it does not include the remainder of the matching implementation.

### 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](<https://devfeed.tech/articles/the-one-liner-that-was-eating-our-memory-daniel-bertoldi-38330.md>)

Original publisher: [Read original article](<https://touchlab.co/the-one-liner-that-was-eating-our-memory>)

Published: 2026-07-28T18:00:00Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [jetbrains](<https://devfeed.tech/topics/jetbrains.md>), [ide](<https://devfeed.tech/topics/ide.md>)

Tags: [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [dump](<https://devfeed.tech/tags/dump.md>), [eclipse](<https://devfeed.tech/tags/eclipse.md>), [heap](<https://devfeed.tech/tags/heap.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [memory-leak](<https://devfeed.tech/tags/memory-leak.md>)

### 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](<https://devfeed.tech/articles/adding-a-koog-ai-assistant-with-structured-output-to-the-fantasypremierleague-cmp-sample-25194.md>)

Original publisher: [Read original article](<https://johnoreilly.dev/posts/fpl-koog-structured-output/>)

Published: 2026-07-27T23:00:00Z

Content type: tutorial

Language: en

Sources: [John O'Reilly](<https://devfeed.tech/sources/john-o-reilly.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [chat](<https://devfeed.tech/tags/chat.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [koog](<https://devfeed.tech/tags/koog.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [sample](<https://devfeed.tech/tags/sample.md>), [structured-output](<https://devfeed.tech/tags/structured-output.md>)

### AI overview

The FPL Assistant uses Koog structured output to return a short Markdown response plus exact player and fixture IDs. The app can resolve those IDs against its own data and render existing player and fixture cards, avoiding error-prone name matching. Its Koog tools expose player, fixture, and tracked mini-league data from the app. The excerpt also says the agent registers these tools, streams intermediate tool calls and errors to the UI, and uses a Gemini model with its executor on all platforms, which can be customized. The supplied text ends during the explanation of the agent's loops, so it does not establish the full implementation.

### 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](<https://devfeed.tech/articles/the-challenge-of-adding-a-web-target-to-droidconkotlin-kevin-schildhorn-38156.md>)

Original publisher: [Read original article](<https://touchlab.co/adding-web-target-to-droidcon>)

Published: 2026-07-22T18:00:00Z

Content type: tutorial

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [crashlytics](<https://devfeed.tech/tags/crashlytics.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [droidcon](<https://devfeed.tech/tags/droidcon.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [project](<https://devfeed.tech/tags/project.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [web](<https://devfeed.tech/tags/web.md>)

### 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.

## Introducing the Composables CLI and MCP server

DevFeed: [Introducing the Composables CLI and MCP server](<https://devfeed.tech/articles/introducing-the-composables-cli-and-mcp-server-28455.md>)

Original publisher: [Read original article](<https://composables.com/blog/introducing-composables-cli>)

Author: Alex Styl

Published: 2026-07-07T00:00:00Z

Content type: release

Language: en

Sources: [Composables](<https://devfeed.tech/sources/composables-concise-no-fluff-video-tutorials-for-android-developers.md>)

Topics: [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [npm](<https://devfeed.tech/tags/npm.md>)

### 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](<https://devfeed.tech/articles/introducing-composables-ui-28456.md>)

Original publisher: [Read original article](<https://composables.com/blog/introducing-composables-ui>)

Author: Alex Styl

Published: 2026-06-22T00:00:00Z

Content type: release

Language: en

Sources: [Composables](<https://devfeed.tech/sources/composables-concise-no-fluff-video-tutorials-for-android-developers.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Library](<https://devfeed.tech/topics/library.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [library](<https://devfeed.tech/tags/library.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### 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](<https://devfeed.tech/articles/antigravity-tagspotter-kotlinmultiplatform-evolve-32038.md>)

Original publisher: [Read original article](<https://www.maiatoday.net/p/antigravity-tagspotter-kotlinmultiplatform-evolve/>)

Published: 2026-06-14T19:10:33Z

Content type: opinion

Language: en

Sources: [Maiatoday](<https://devfeed.tech/sources/maiatoday.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Android](<https://devfeed.tech/topics/android.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Web](<https://devfeed.tech/topics/web.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [android](<https://devfeed.tech/tags/android.md>), [antigravity](<https://devfeed.tech/tags/antigravity.md>), [code](<https://devfeed.tech/tags/code.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [git](<https://devfeed.tech/tags/git.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlinmultiplatform](<https://devfeed.tech/tags/kotlinmultiplatform.md>), [migration](<https://devfeed.tech/tags/migration.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### 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

[Next page](<https://devfeed.tech/topics/compose-multiplatform.md?cursor=WyIyMDI2LTA2LTE0VDE5OjEwOjMzKzAwOjAwIiwgImY5YWUzOWNmLWRkNjUtNGIzNy1iNGQwLTE0Yzc1Zjg3ZjljZSJd>)