Thanks for MVVM description! A few other resources I’ve read seem to prefer pushing the business logic into the model. The model ceases to become a pure “data model” at that point, instead holding those “data model” classes and the use case actions that can be done on them, but that seems to be acceptable in MVVM. Then the view model just links the two together. Do you have any thoughts on moving business logic to the model instead of view model?