If you're working on a client side mobile application, for a smoother UX, optimistic rendering is encouraged. This is where the application makes UI updates based on user requests that get sent to the server without waiting for the response assuming the response will be successful.What this also means is that the requests need to be handled client-side to make corresponding updates which requires business logic that the server side uses. And this is duplication which in usual terms is bad.Apart from that the business-logic might require information and resources which server readily has. For example, if the user rates a business, that rating must be aggregated and calculated to retrieve a community rating. That process will be complex and inaccurate (obvious, as we're already making assumptions of the request success).Are there any solutions to ease such complexity in implementation and yet make the experience smoother for the user? Is the duplication of logic the only way?
Optimistic rendering imposes duplication of logic?
client server;business logic;user experience