You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user has the chat screen open, we want a counter to appear somewhere that shows the amount of users which they are able to send messages to.
Architectural decisions
How do we want to give this information from the server to the client? Depending on the method, more/less requests between the client and the server could be made, affecting performance and scaling. For example, a websocket endpoint could be added that after each update would calculate the amount of nearby users and send this number to each client periodically. The delay for this request should be added to the server config-example if this is done. A less accurate, but more efficient example could be storing the number of addressed users in every message, and updating the user-counter from what this attribute is in the last received message.
Potential implementation
(UI) Create a design for what the user-counter will look like.
(Front-end) Create the components/styles/state needed to render this.
(Back-end) create method needed to send user-counter information to front-end.
(Front-end) Store received user-counter information from server and change state.
(Front-end) Make sure affected components are rendered properly.
Issue list will be in the comments below.
The text was updated successfully, but these errors were encountered:
This feature is written in our MVP.
Description
When a user has the chat screen open, we want a counter to appear somewhere that shows the amount of users which they are able to send messages to.
Architectural decisions
config-example
if this is done. A less accurate, but more efficient example could be storing the number of addressed users in every message, and updating the user-counter from what this attribute is in the last received message.Potential implementation
Issue list will be in the comments below.
The text was updated successfully, but these errors were encountered: