The messaging system has one giant issue currently. And that's that when a message fails to send it just clears the entire input and let's you write everything from scratch and that it loads way too long. We should have a system that queues messages in the message feed and has the ability to retry sending. Those messages can be dropped if the app is closed.
The queue would make sure that you can write a new message while one is sending. With the two requests that it takes to get a message to the server, loading times can sometimes be >200ms and really noticeable. To prevent this, the queue is needed.
I'll see if I can do something about this issue and implement this in Liphium v0.6.0, but for now v0.5.0 needs to get out with support for messaging in Spaces and then we can work on fixing the message sending.
The messaging system has one giant issue currently. And that's that when a message fails to send it just clears the entire input and let's you write everything from scratch and that it loads way too long. We should have a system that queues messages in the message feed and has the ability to retry sending. Those messages can be dropped if the app is closed.
The queue would make sure that you can write a new message while one is sending. With the two requests that it takes to get a message to the server, loading times can sometimes be >200ms and really noticeable. To prevent this, the queue is needed.
I'll see if I can do something about this issue and implement this in Liphium v0.6.0, but for now v0.5.0 needs to get out with support for messaging in Spaces and then we can work on fixing the message sending.