Yup, I use something very similar to this as well. So far I’ve been very happy with how it works. It allows for easy testing as well, just collecting all the states and events fired by the viewmodel and compare with expected states for respective input.

I think having a single process() method, that accepts `EVENT` is not completely necessary and it can be replaced by call methods to view model (this is especially easier to use when using data binding), but I also have some experience with doing that and it can have some advantage.

It’s even better, if the view events object wraps Rx `Observable`s because then it’s easy to do things like debounce on input fields etc.