I'd propose the following changes in order to better capture the possible needs of consumers:
Since Android is moving towards Flows (StateFlow & SharedFlow), I believe it would make sense to have a separate -livedata artifact
Also with moving towards compose I think the MvvmActivity and binding adapters could also go into a separate artifact
For those who are sharing VM logic & would like to leverage the Android Arch Viewmodel, a lightweight artifact, with the Android VM abstraction, which targets all possible KMP platforms (js, macos, jvm, etc...) would be really beneficial
I'd propose the following changes in order to better capture the possible needs of consumers:
-livedata
artifactMvvmActivity
and binding adapters could also go into a separate artifact