Hi Everyone can anyone guide me how i can use ViewModel in KMM Is there any example with Use Case, Repository and ViewModel in CommonMain

I wouldn't recommend using Android's ViewModel in your commonMain, instead you can write your business logic in a platform agnostic way and have a ViewModel use this logic on Android, and do the same thing in a UIViewController on iOS. Although, if you really want to refer to Android's ViewModels in commonMain, then you can do the following:

// in commonMain
expect abstract class ViewModel

// in androidMain
actual typealias ViewModel =  androidx.lifecycle.ViewModel

// in iosMain
actual abstract class ViewModel

@Benoît as per POC requirement we are trying to put ViewModel Use Case and Repository in CommonMain Only UI part will in Android and in iOS

The architecture I'm using heavily uses functional programming and thus would probably not be what you're looking for. If you really have to make your VM class extend

androidx.lifecycle.ViewModel

then you can do what I said above with the expect/actual keywords

Reminder that if you are building a full compose app you don't have to use AAC VM but you can instead just create your own concept of a VM.

@joney @Colton Idle @Benoît if we create our own ViewModel then how we can achieve screen rotation and how we can achieve life cycle aware benefit, please suggest if there is any good example

Being lifecycle aware is an Android thing, it has to be implemented in an

android

module not a

common

one

@Benoît Thanks

@Napa Ram compose handles configuration changes (e.g. rotation) with composition locals.

you can check my project i have the viewmodels shared 🙂 it is in

client

module https://github.com/CurrencyConverterCalculator/CCC