In the past, we needed to load message history for every channel in order to determine what the state of each channel was i.e., whether you had any unread messages (channel name shown in bold), or mentions (channel name has a “badge” overlay with a number on the right.) An example of the channel list UI. Refactoring the Slack web app to fetch messages for only the current, active channel (instead of all channels), seemed straightforward enough. Doing Less Up Front: “Stopping Fetch From Happening” Even when scale is considered up front, changes in usage patterns can impact the performance of your app on both backend and frontend - sometimes in interesting, and unexpected, ways.
0 Comments
Leave a Reply. |