What the AppConnect render is doing now puts an end to the creation of large real-time messenger format applications.
Each time the data is updated, the renderer does not redraw the small element of the DOM tree in which the changes occurred, but everything related to the server action.
The operation of a simple chat is shown below. I change the status of the message to “read”. And with each change, not a separate element is rendered, but the entire chat window, which leads to the start of scrolling. Such an interface in production is a constant dissatisfaction and complaints of users about the interface:
But that’s half the trouble. The real hell arises from the fact that the renderer redraw interface from all users who are connected to the server at the moment when updating data. And it’s hell when 10+ users are connected to the app:
I will also place an archive of the application here (a simple chat with the sqlite database) so that you can also run it very quickly on your computer and reproduce what I showed in the recordings above.
chattest.zip (316.4 KB)
@sid I reading in your messages that one of the projects you were working on was a messenger. Aren’t your users facing a rendering problem? Or did you manage to find a solution to work around the problem? Maybe I’m missing something?