Wire model that represents how data came from network. It may be not the best to work with UI or do any treatment.
View model that is used in conjunction with its view to display the data.
The problem is that view model is too tied to its view, so we can't reuse to other views and wire model may be to raw to be useful.
Maybe we should have a intermediary model that allow data to be more consumable than the wire model, but it is generic enough to be used almost in a delegation fashion by other view models, so they only contain UI specific code.
The con is that it imposes more indirection levels, making data flow harder to follow.
Right now I have two models:
Wire model that represents how data came from network. It may be not the best to work with UI or do any treatment. View model that is used in conjunction with its view to display the data.
The problem is that view model is too tied to its view, so we can't reuse to other views and wire model may be to raw to be useful.
Maybe we should have a intermediary model that allow data to be more consumable than the wire model, but it is generic enough to be used almost in a delegation fashion by other view models, so they only contain UI specific code.
The con is that it imposes more indirection levels, making data flow harder to follow.