The State of Kotlin Multiplatform

[@twissmueller]

Many thanks for this webinar. So much useful information. Especially looking forward to using Fleet!

[@bettertoaster]

Where can I find the Twitch recording showing Fleet?

[@Kotlin]

For Fleet demo check out one of the following webinars recording: kzbin.info/www/bejne/f3jYh3yIj9-Jis0

[@holatechm]

please do share Project resources

[@_dinesh]

Thanks for an awesome presentation. Always great to hear from a bunch of smart talented folks.. Definitely a great development toolkit to have under your belt. I just had 2 questions for the team. 1. Would KMP eventually support Hot reload for making development faster (Like flutter)? 2. Secondly, would KMP support over the air updates for production apps similar to Shorebird in Flutter (Say if I want to push some UI changes without having the users to update the app from the app store)?

[@senk0n]

For the second case familiarize yourself with zipline + redwood

[@senk0n]

Kotlin compiles into native on each platform, this wouldn't be supported officially in any way, my guess

[@mandjivatuva]

This is huge. Viva Kotlin

[@techaido]

Why Amper? Gradler or Moduler or Yamiler ...?

[@MixwellSidechains]

i'm so confused now. Why does Kotlin Multiplatform exist alongside Compose Multiplatform. What are the differences and if so, why?

[@pablovaldes6022]

Two different tech stacks. One sits on top of the other.

[@archiequinones]

Compose Multiplatform is a Kotlin Multiplatform UI Library. So now you can create your application with not only shared code (Kotlin Multiplatform) but also shared UI (Compose Multiplatform)

[@HuangTim1018]

Compose multiplatform sit on top of kotlin multiplatform. It is for sharing ui layer code

[@MixwellSidechains]

@@archiequinones Not entirely true. CMP is not about UI only because it also targets Darwin, MingW, Linux and Wasm. So sharing logic code and UI is what CMP is. KMP is only for sharing logic code between iOS (Swift) and Android (Kotlin/JVM). So, saying it's layered on top of KMP is wrong rather KMP is a little subset that has been plugged into CMP. KMP is not said to convert code to Kotlin/JS or Kotlin/Native which is used by other platform this capability came along with Compose Multiplatform which is more expansive and better at sharing both code (JVM, Swift, JS, Native) and UI to multiple targets. So rather than having KMP why don't the call the whole framework CMP and drop KMP since it's part of the larger CMP framework otherwise this would mean that desktops must have their own "KMP" for logic and then be layered with CMP. Doesn't make sense.

[@archiequinones]

@@MixwellSidechains KMP is not just mobile.

[@dleonardo3238]

instead of expect and actual why not put the function in the common interface and then in the respective android and ios classe implement the function?

[@UpToTheWhalesNow]

you can use an interface instead. Expect/actual just give you extra compile-time validation that the expected interface is implemented in all your actual targets

[@UpToTheWhalesNow]

Additionally, actual/expect enforces the actual package name to match that of expected. Expect/Actual also doesn't allow default implementations in the Expected Class (whereas an interface does). So it's all just additional rules/validations to make it harder to mess up managing your platform dependencies

[@dleonardo3238]

@@UpToTheWhalesNow ow ok, thanks for explaining

[@MrPhiltz77]

awesome!

[@_modiX]

I love the technology of Fleet, but with lack of proper Vim support I cannot adopt this IDE.

[@JazzyJesterTechPing]

You all cute, thanks!

[@georgeshalvashvili6270]

Nice

[@leomak7580]

boring )