Utilizing message metadata for improving user interface presentation
摘要
說明書
In some examples, if any one of the messages is associated with a particular characteristic that indicates that it should not be added to a message digest, the component of the server(s) 102 can refrain from generating a message digest and/or can refrain from adding that message to the message digest (e.g., and present it individually). For example, if any one of the messages is associated with an action item, the component of the server(s) 102 can refrain from generating a message digest and/or can refrain from adding that message to the message digest. As another example, if any one of the messages is associated with a high priority, the component of the server(s) 102 can refrain from generating a message digest and/or can refrain from adding that message to the message digest.
In at least one example, the user interface element representative of the message digest, such as the user interface element 300, can be associated with an indication of the originating source (e.g., user and/or application) and, in some examples, a number of messages in the message digest (e.g., three messages). In some examples, the user interface element 300 can include a date and/or date range, a timestamp and/or period of time, and/or the like. In at least one example, the user interface element 300 can be associated with an actuation mechanism. In at least one example, based at least in part on actuating the actuation mechanism, the messages can be presented via the user interface 200, as illustrated in
