I found your approach to using mutable objects very interesting and helpful, especially in conjunction with Part 1 of this article.
Your perspective has greatly improved my understanding of immutability. I've often felt that immutability is a good idea and helps manage complexity, but at times, I've also thought, it would be so much easier if I could just mutate this object.
Thank you very much for sharing your insights and the distinction when the programming advice of immutability makes sense and in which situations it is not helpful!
I have a question: Typically, domain models in Flutter Projects can be modified by the user. E.g. by liking them or changing certain properties. Would you, as a rule, recommend making domain models in a Flutter project mutable using the Proxy Objects approach you demonstrated?