The current implementation of the Message View/Reader doesn't just use views, it largely uses the MVC pattern. There are a few instances where state for the view is pulled from multiple data objects and provided from a variety of sources. This can create an issue lacking a single source of truth, and the likelihood of creating a mutable state is too high. Performance will suffer in a Jetpack view with this.
Create a data object that can encapsulate the data we need to display a message reader view, to eventually be prepared by a viewmodel we'll create or a state machine owned by the viewmodel.
The current implementation of the Message View/Reader doesn't just use views, it largely uses the MVC pattern. There are a few instances where state for the view is pulled from multiple data objects and provided from a variety of sources. This can create an issue lacking a single source of truth, and the likelihood of creating a mutable state is too high. Performance will suffer in a Jetpack view with this.
Create a data object that can encapsulate the data we need to display a message reader view, to eventually be prepared by a viewmodel we'll create or a state machine owned by the viewmodel.