when you use

LiveData<Resource<T>>

, doesn't the fragment have to make too many decisions? I.e. what to do for each result

You can see this Resource like a State

sealed class

but what about the typical sealed class Resource that just contains Success, Error, and Loading? Should the fragment make the decision what to do in each case? I thought that kind of logic belongs into the ViewModel

It is similar to that sealed class if you removes OnNextScreen and rename Form to Success, with simple screens maybe there is no problem in understand what is happening with these three states, but with complex screen that resource can be difficult to understand