In the Compose tutorials, it is advised to use State in the ViewModel as much as possible because it makes the code simpler and it's right BUT is State lifecycle aware like LiveData ? Can we achieve the same ?

Compose itself is ofc lifecycle aware. You are not going to accidentally update a view that doesn't exist anymore because activity or fragment is destroyed. View "updates" itself anyway.

thanks @Halil Ozercan, i didnt see it that way but you're right.