- Prefer coroutines to RXJava - Have a clean archi...

# multiplatform

[ivano]

• Prefer coroutines to RXJava
• Have a clean architecture  with MVVM with view and even viewModels small as possible( you could use MOKO in the future)
• Use Compose
• Map models with Kotlin Serialization because Moshi is not sure will be implemented
• try to put generics as extension functions because is not sure will be implemented soon
• for new projects implement Ktor for simple rest api
• Be aware that your repository could be shared with iOS

[Michal Klimczak]

Why Compose in the context of kmm?

[Tiago Nunes]

I was wondering the same thing

[solidogen]

similarities between compose and swiftUI may help create UI faster

[wellingtoncosta]

but it is platform-specific, right? btw, I agree with @solidogen

[Michal Klimczak]

Fair point, But I would not say that you need to jump into compose or swiftui if you're planning to use kmm. It's no game changer (in the context of kmm).
Also, I would not use either in a production app yet ;)

[ivano]

I get your point everyone! Better not sum alpha to alpha! But I reckon within 3 months kinda should become official, and when Compose will be awake 🔥, the community will start to try in any way to write once in a declarative way the view for the two systems(actually there is already a library called multiplatform-compose) and then implement kind of specific iOS features with a kind of Cupertino(as in Flutter)

[ivano]

And to be honest I am not going to jump in production neither with KMM, my idea is to prepare for a migration without pain