Utilizing message metadata for improving user interface presentation
摘要
說明書
In some examples, a user can comment on a message in a “thread.” A thread can be a message associated with another message that is not posted to a communication channel, but instead is maintained within an object associated with the original message. Messages and/or threads can be associated with file(s), emoji(s), application(s), etc. and can be viewed based on an interaction with a user interface element representative of the thread. In some examples, such a user interface element can be associated with an actuation mechanism that when actuated can cause the threaded messages to be presented via the user interface 200. In some examples, the threaded messages can be presented via a third section of the user interface 200.
A communication channel or other virtual space can be associated with data and/or content other than messages, or data and/or content that is associated with messages. For example, non-limiting examples of additional data that can be presented via the second section 206 of the user interface 144 include members added to and/or removed from the communication channel, file(s) (e.g., file attachment(s)) uploaded and/or removed from the communication channel, application(s) added to and/or removed from the communication channel, post(s) (data that can be edited collaboratively, in near real-time by one or members of a communication channel) added to and/or removed from the communication channel, description added to, modified, and/or removed from the communication channel, modifications of properties of the communication channel, etc. Indications of such additional data and/or actions can present as messages and can be represented by user interface elements in the user interface 200.
