A shared module should have clear ownership. When common code becomes a place where everything lives, flexibility disappears. Architecture still matters in cross-platform development. #KMP #SoftwareArchitecture #Kotlin

A shared module should have clear ownership. When common code becomes a place where everything lives, flexibility disappears. Architecture still matters in cross-platform development. #KMP #SoftwareArchitecture #Kotlin
Kotlin Multiplatform works best when shared code supports native experiences instead of replacing them. Great products respect each platform. #KMP #iOSDev #MobileDevelopment
Compose Multiplatform shines when teams design the right boundaries. Shared UI is powerful, but great products still respect platform differences. #ComposeMultiplatform #KMP #UIEngineering
Kotlin Multiplatform libraries and tooling are becoming easier to publish and consume. A stronger ecosystem makes every developer more productive. #KMP #KotlinMultiplatform #OpenSource
Building with Kotlin, KMP, or Compose Multiplatform? Join developers discussing architecture decisions, challenges, and lessons learned. #Kotlin #KMP #DeveloperCommunity
Kotlin Multiplatform is not about writing less code. It is about reducing duplicated decisions. Share the logic that defines your product, while keeping each platform experience intentional. #KMP #KotlinMultiplatform #MobileDev
The biggest opportunity with Kotlin Multiplatform is not writing less code. It is making teams faster by sharing the parts that create the most value. #KMP #KotlinMultiplatform #DeveloperExperience
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 […]