Where should I keep the viewModel? In common code ...

# multiplatform

[Hasan Nagizade]

Where should I keep the viewModel? In common code or platform spesific?

[streetsofboston]

Can be either. Your choice

[streetsofboston]

You'll have to abstract out a common expect (or interface) so that it works on both platforms if you do decide to share it.

[Kevin S]

We tend to keep it in common code, and then have expect / actuals for the ViewModel itself, so we can use the viewModelScope for android and simulate it for iOS. Like Anton said though it could be either

[ayodele]

@Kevin S do you wrap the viewModel in ObservableObject on the iOS side??

[Kevin S]

Yes, you can see an example here https://github.com/touchlab/KaMPKit/blob/main/ios/KaMPKitiOS/BreedListScreen.swift

[ayodele]

But is the ObservableObject avoidable? Where by we use the common viewModel in SwiftUI like compose does?

[Rick Clephas]

I am currently working on something for that (initial release coming soon): https://github.com/rickclephas/KMM-ViewModel
It’s just removing the boilerplate, in the end it still uses an observable object since that’s needed for SwiftUI.

[Hasan Nagizade]

@Rick Clephas it looks awesome already.