so you are saying the fragments/views shouldn’t be the ones with the responsibility to subscribe to anything, that way they don’t have to make any decisions at all (threads used, etc.). This way the views don’t need to have any RxJava dependency at all. I absolutely agree with this.
In MVVM, one of the principles is that the ViewModel shouldn’t know about the consumer, this gives a lot of flexibility and saves you from writing boiler plate to interface with the framework component like MVP does. So, taking this in mind, I can only think in one way to update the views without the views being responsible of subscribing: DataBinding.