Hi guys. Hopefully this is the best place to ask. ...
# android
g
Hi guys. Hopefully this is the best place to ask. I'm currently evaluating building our app in Kotlin Multiplatform. There is a separate iOS project being developed, but the idea is to keep the door open to implement the iOS version in the KMM project later down the line. I've been researching app architectures, and there doesn't seem to be a main consensus on the best one to use (even a link to a page on the kotlin homepage discussing this is no longer available). One of the requirements is we'll be using Jetpack Compose and SwiftUI, and it seems only the MVI pattern allows us to be truly multiplatform without separate presentation logic and testing. The issue is that most of these articles i've been reading are a few years old now, and I wanted to know what the latest recommendations are? I found the todoapp example project which seems to satisfy our requirements. Would this be the recommended way to go? https://github.com/JetBrains/compose-jb/tree/master/examples/todoapp
d
Not really going to speak to the KMM part directly, but we’re doing everything new in SwiftUI and Compose. When talking anything KMM, we’re purposefully keeping anything UI related out of the discussion. Simply put, SwiftUI and Composables have a lot of synergy but they aren’t the same. With that in mind, we want to keep them in their own “world” to avoid forcing one to act like the other. If we were to have any UI elements involved in KMM, we’d defer to following he model in KMM for connecting to platform specific APIs (https://kotlinlang.org/docs/mpp-connect-to-apis.html). It also has to do with the underlying differences in how one may want to have different architectures for presenting the UI even if it is on different platforms.
🙏 1
c
Better ask in #multiplatform
🙏 1
e
👍 1
👎 1
🙅‍♀️ 1
nono 1
🙏 1
g
@Chrimaeon Thanks! There's a lot of great information in that channel.