Giving a good experience with poor connectivity means the clients need to be able to reason about updates to the domain model and potential conflicts. At this p

Giving a good experience with poor connectivity means the clients need to be able to reason about updates to the domain model and potential conflicts. At this point they need to reason about almost as much as the server. Search for "offline first" to see how people are exploring architectures like this. Edit: source: I worked on a product bundling chat functionality as a plug in. In fairness, I think this is not so relevant for apps which are consumption first, but if there's any kind of collaboration, or even just writing from the client, you want to show an optimistic (at least; some systems make the client state canonical) representation regardless of sync status.