Utilizing message metadata for improving user interface presentation
摘要
說明書
In some examples, the user interface element 228 can be associated with a mechanism for generating a subscription. In some examples, the user interface element 228 can be presented proximate to the user interface elements 224 representative of existing subscriptions (e.g., subscription user interface elements). In at least one example, the user interface element 228 can be associated with an actuation mechanism that when actuated can cause a subscription user interface to be presented via the user interface 200. The subscription user interface can enable authorization of a subscription. In some examples, the subscription user interface can include subscription features from which a user can select, an authorization indication for authorizing the subscription, an input mechanism for obtaining authentication data, and/or the like. Additional details are provided below.
In some examples, one or more messages can be aggregated into a message digest, which can be presented via a single user interface element. For example, the user interface elements 219-221 are all associated with the same originating source (e.g., Application A) and the same priority (e.g., low priority). As such, in at least one example, a single user interface element 300 can be presented via the second section 206 instead of the three user interface elements representative of each message. Such an aggregation can be called a “message digest.” An example of the user interface 200, wherein the messages associated with Application A are presented via a message digest, is illustrated in
