Kotlin Multiplatform keeps improving as the ecosystem matures. Sharing business logic, libraries, and workflows is becoming a practical choice for more teams. #KMP #KotlinMultiplatform #MobileDev

Kotlin Multiplatform keeps improving as the ecosystem matures. Sharing business logic, libraries, and workflows is becoming a practical choice for more teams. #KMP #KotlinMultiplatform #MobileDev
Good cross-platform development is not about eliminating differences. It is about managing differences with a clear architecture. #iOSDev #KMP #MobileDevelopment
A shared UI strategy should start with product goals, not technology excitement. Compose Multiplatform is powerful when it solves a real development problem. #ComposeMultiplatform #KMP #MobileApps
📣 Berlin, we’re here!
Touchlab is at #nextapp26 this week.
🎤 Wed 12:00 — @kpgalligan.bsky.social + Filip Dolník: Native Mobile and AI
🎤 Fri 16:30 — @tadeas.bsky.social : Advanced Kotlin Native Integration
Come talk #KMP, native mobile & AI with us at📍Stand 9!
Shared code should reduce complexity, not move complexity somewhere else. Good KMP architecture starts with clear responsibilities between modules. #KMP #KotlinMultiplatform #SoftwareArchitecture
🚀 Compose Multiplatform 1.13.0-alpha02 is here!
✨ iOS trackpad gestures
⚡ Kotlin 2.4.20
🌐 Better Web accessibility
📦 Stable resource preload APIs
🐛 iOS, Web & Desktop fixes
Okay!
Registration with SignPath begun, to get an Authenticode cert. And the app is in "Internal Testing" in the Google Play store!
Things are moving...
Compose Multiplatform is not about forcing every pixel into shared code. Great architecture knows what to share and what should stay platform-specific. #ComposeMultiplatform #KMP #UIEngineering
Working on Kotlin, KMP, or Compose Multiplatform? Share your ideas, questions, and lessons with developers building similar things. Join the watermelonKode community. #Kotlin #KMP #DeveloperCommunity
Shared code is not the goal of Kotlin Multiplatform. Shared understanding is. If common code makes the product easier to change across platforms, it is doing useful work. #KMP #KotlinMultiplatform #SoftwareArchitecture
Kotlin Multiplatform works best when you share business decisions, not just files. A well-designed shared layer can reduce duplication while keeping each platform feeling native. #KMP #KotlinMultiplatform #MobileDev
I'm adding a BMR base metabolic rate and maintenance calorie computation into #HealthCoach.
https://github.com/bigtlb/healthcoach
But, I didn't want to constrain to just the binary gender options. And wanted to also provide guidance […]
Just registered Konuq for Shipaton!
Added deep link support to FantasyPremierLeague #KMP sample using the new Navigation 3 deep link support. github.com/joreilly/Fan...
One set of matchers in shared code that works on Android and iOS (and desktop), with a synthetic back stack so it lands in the list-detail layout.
KMP does not make iOS a secondary platform. Shared logic should reduce duplication while the iOS experience still feels native to the people using it. #KMP #iOSDev #KotlinMultiplatform
Kotlin Multiplatform gets interesting when shared code removes duplicated decisions, not when the goal becomes sharing every possible line. Share what creates leverage. Keep platform strengths. #KMP #KotlinMultiplatform #MobileDev
A practical Compose Multiplatform question for any new screen: what truly belongs in shared UI, and what should remain platform-specific? Good reuse starts with that boundary—not with a percentage target. #ComposeMultiplatform #KMP #SoftwareDesign
The best shared code is often the code that captures product behavior: validation, state transitions, data mapping, domain rules. That is where KMP can reduce duplicated decisions—not just duplicated syntax. #KotlinMultiplatform #KMP #MobileArchitecture