Since everything in Trello is pretty much happening on the same page/view, it is a great example of a need for optimistic UI updates! Since currently we don't have a support for it in Wasp, this is the kind of "lag" that appears in the UI:
When the card is dragged to the new position, first the API request is made and only once the response is received the UI can re-render itself with the correct info from the query. So in the time while the client is waiting for the response from the server, UI stays in its previous state (b/c the query returns the "old" data) and that is why the lag appears.
The optimistic UI update feature is currently being discussed in #63 .
Since everything in Trello is pretty much happening on the same page/view, it is a great example of a need for optimistic UI updates! Since currently we don't have a support for it in Wasp, this is the kind of "lag" that appears in the UI:
When the card is dragged to the new position, first the API request is made and only once the response is received the UI can re-render itself with the correct info from the query. So in the time while the client is waiting for the response from the server, UI stays in its previous state (b/c the query returns the "old" data) and that is why the lag appears.
The optimistic UI update feature is currently being discussed in #63 .