Utilizing message metadata for improving user interface presentation
摘要
說明書
As described above, in some examples, high priority messages can cause a user interface element to be presented in association with the communication channel, direct message, and/or the like with which they are associated, for example, to alert a user that there is a high priority message associated therewith. In some examples, high priority messages can cause notification settings to be overridden (e.g., pass through a “do not disturb” or “notifications off” setting), cause subsequent messages and/or alerts to be presented via the user interface 200 until the high priority message is read, and/or the like.
While three priorities are described above, messages can be associated with any number of different priorities, which can be set by a developer and/or learned by machine learning mechanisms. In some examples, each priority can be associated with different presentation characteristic(s) to enable a user to quickly differentiate between priorities of messages on the user interface 200. As described above, priorities can mean different things to different users. In some examples, priorities can affect presentation characteristics differently for different users. For instance, a customer service ticket associated with a code glitch can be of high priority to a developer but may be of low priority to a designer. As such, in some examples, the component of the server(s) 102 can modify priorities and/or presentation characteristics based at least in part on user data associated with recipient user(s).
