Great post! I was using something similar in Java with ObservableFields but you are right, exposing the setters to the view is not a good solution. Now I am porting my app to Kotlin and I am trying something different. I don’t like using multiple ObservableField in the ViewModel so I am using a single ObservableField with an immutable object that contains all the values. Here https://github.com/fabioCollini/ArchitectureComponentsDemo you can find an example (I am using a LiveData instead of an ObservableField)