Hi!
How can we share ViewModel across platforms in...
# multiplatforma
Ahmad Hassan
03/21/2023, 1:13 PMHi!
How can we share ViewModel across platforms in compose Multiplatform?
a
Alejandro Rios
03/21/2023, 1:14 PMp
Pablichjenkov
03/21/2023, 1:17 PMCompose-multiplatform is one single code base, place all compose/viewmodel stuff in commonMain.
a
Ahmad Hassan
03/21/2023, 1:21 PM@Pablichjenkov
As you know, ViewModel is a special class that survives across configuration changes.
So one solution is expect/actual.
Is there any other solution?
Ahmad Hassan
03/21/2023, 1:22 PM@amezcua
Other than expect/actual approach?
a
Alejandro Rios
03/21/2023, 1:25 PMLooking in the history I've found this
Alejandro Rios
03/21/2023, 1:25 PMBTW: I'm not
@amezcuaa
Ahmad Hassan
03/21/2023, 1:28 PMI just saw the first name..😅
p
Pablichjenkov
03/21/2023, 1:30 PMThat VM behavior is only on Android.
There are a couple of libraries that mimic the behavior to other platforms but in my opinion is a waste of energy because those platforms never had interest in process death recover or they don't suffer from things like Activity death on device rotation
Pablichjenkov
03/21/2023, 1:30 PMIf you ask me I would say Android is the wrong platform here
Pablichjenkov
03/21/2023, 1:32 PMA lot of ceremony for a problem that can/should be avoided by simply handling configuration changes at the code level, not killing the Activity.
Pablichjenkov
03/21/2023, 1:35 PMAnyways, Decompose I believe ported this behavior to the other lands. Voyager did it too but I believe they don't support iOS, haven't checked their repo in a while.
There might be some other project on GitHub doing that, do a lookup there
a
ayodele
03/21/2023, 2:55 PMIf you want to have the android viewmodel in common code, just expect-actual a class, that androidMain actuals it, extend it by ViewModel from androidx.
Then you can make your other viewmodels in common extend the expected viewmodel.
I dunno if you understand.
p
Pablichjenkov
03/21/2023, 3:10 PMBut he still needs to install it's VMs in a lifecycleowner. Meaning you will have to use Navigation Component or Fragments/Activity in Android. Then the code will get a bit fragmented between platforms.
I think that approach fits better a KMM app but if you plan to go compose-multiplatform better use the libraries I mentioned above or not using Android Viewmodel concept at all, just use compose State.
a
ayodele
03/21/2023, 3:16 PMOh compose-multiplatform!
Didn't spot that.
@Pablichjenkov you're right.
1755 Views