User Interface for Messages

Abstract

To provide a messaging user interface that facilitates transmission and reception of a message.SOLUTION: An electronic device displays an expression of a messaging interaction, indicates which message is a replay to another message in the messaging interaction, creates a link (for example, a rich link) at a contact address in the messaging interaction (for example, "a mention" to display it, displays an instruction of the message as a replay of another message, and uses a proposed input user interface element to display an option of creating a link (for example, a rich link) at a contact address in the message interaction (for example, "a mention").SELECTED DRAWING: Figure 11A

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 036,927, filed June 9, 2020, and U.S. Provisional Patent Application No. 63 / 041,994, filed June 21, 2020, the contents of which are incorporated by reference in their entirety for all purposes. [Technical field]

[0002] This specification relates generally to electronic devices that present a messaging user interface and to user interaction with such devices. [Background technology]

[0003] In recent years, user interaction with electronic devices has increased significantly. These devices may be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, etc. In some situations, users wish to use electronic devices to send and receive messages. Electronic devices may present messaging user interfaces to facilitate such. Summary of the Invention

[0004] Some embodiments described in this disclosure are directed to a method of presenting a representation of a messaging conversation. Some embodiments described in this disclosure are directed to a method of indicating which messages are important to a user and providing these messages in a prominent and easily accessible location within a user interface. Some embodiments described in this disclosure are directed to a method of creating and presenting links (e.g., rich links) that tag people in a messaging conversation. Some embodiments described in this disclosure are directed to presenting indications of messages that reply to other messages. Enhancing messaging interactions improves the user experience with the device and reduces user interaction time, which is especially important when the input device is battery operated.

[0005] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users. [Brief description of the drawings]

[0006] For a better understanding of the various described embodiments, please refer to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0007] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

[0008] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

[0009] [Diagram 2] FIG. 1 illustrates a portable multifunction device having a touch screen according to some embodiments.

[0010] [Diagram 3] 1 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

[0011] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments.

[0012] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from a display in accordance with some embodiments.

[0013] [Figure 5A] FIG. 1 illustrates a personal electronic device according to some embodiments.

[0014] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0015] [Figure 5C] FIG. 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments. [Figure 5D] FIG. 1 illustrates example components of a personal electronic device having a touch-sensitive display and intensity sensor in accordance with some embodiments.

[0016] [Figure 5E] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5F] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5G] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments. [Figure 5H] 1 illustrates example components and a user interface of a personal electronic device according to some embodiments.

[0017] [Figure 6A] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6B] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6C] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6D] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6E] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6F] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6G] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6H] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6I] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6J]An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6K] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6L] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6M] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6N] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6O] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6P] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6Q] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6R] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6S] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6T] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6U] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6V] An exemplary method is shown in which an electronic device presents a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6W] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6X] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6Y] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6Z] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6AA] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6BB] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6CC] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6DD] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6EE] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6FF] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6GG] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6HH] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6II] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6JJ] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6KK] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6LL] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6MM] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6NN] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6OO] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6PP] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6QQ] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6RR] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure. [Figure 6SS] 1 illustrates an example method for an electronic device to present a representation of a messaging conversation, according to some embodiments of the present disclosure.

[0018] [Figure 7] 1 is a flow diagram illustrating a method for presenting a representation of a messaging conversation according to an embodiment of the present disclosure.

[0019] [Figure 8A]1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8B] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8C] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8D] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8E] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8F] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8G] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8H] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8I] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8J] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8K] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8L] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8M] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8N] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8O] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8P] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8Q] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8R] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8S] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8T] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8U] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8V]1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8W] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8X] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8Y] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8Z] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments. [Figure 8AA] 1 illustrates an example method for an electronic device to indicate which messages are replies to other messages in a messaging conversation, according to some embodiments.

[0020] [Figure 9] 4 is a flow diagram illustrating a method for indicating that a message is a reply to another message in a messaging conversation, according to some embodiments.

[0021] [Figure 10A] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10B] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10C]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10D] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10E] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10F] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10G] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10H] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10I] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10J] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10K] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10L]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10M] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10N] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10O] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10P] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10Q] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10R] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10S] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10T] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10U]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10V] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10W] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10X] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10Y] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10Z] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10AA] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10BB] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10CC] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Fig. 10DD]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10EE] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10FF] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10GG] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10HH] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10II] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10JJ] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10KK] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10LL] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10MM]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10NN] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10OO] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10PP] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10QQ] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10RR] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10SS] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10TT] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10UU] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10VV]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10WW] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10XX] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10YY] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10ZZ] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10AAA] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10BBB] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10CC] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10DDD] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10EEE]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10FFF] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10GGG] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10HHH] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10III] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10JJJ] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10KKK] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10LLL] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10MMM] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10NNN]1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10OOO] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10 PPP] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10QQQ] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10RRR] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10SSS] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments. [Figure 10TTT] 1 illustrates various ways in which an electronic device can create and present links (e.g., rich links) to contacts in messaging conversations (e.g., "mentions") according to some embodiments.

[0022] [Figure 11A] 1 is a flow diagram illustrating a method for creating and presenting links (e.g., rich links) to contacts within a messaging conversation (e.g., a "mention") according to some embodiments. [Figure 11B] 1 is a flow diagram illustrating a method for creating and presenting links (e.g., rich links) to contacts within a messaging conversation (e.g., a "mention") according to some embodiments.

[0023] [Figure 12A] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12B] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12C] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12D] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12E] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12F] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12G] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12H] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12I] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12J] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12K] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12L]13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12M] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12N] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12O] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12P] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12Q] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12R] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12S] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12T] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12U] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12V] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12W] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Fig. 12X]13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments. [Figure 12Y] 13 illustrates various ways in which an electronic device may present an indication of a message replying to another message, according to some embodiments.

[0024] [Figure 13] FIG. 1 is a flow diagram illustrating a method for presenting instructions for a message replying to another message, according to some embodiments.

[0025] [Figure 14A] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14B] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14C] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14D] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14E]1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14F] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14G] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14H] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14I] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14J] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments. [Figure 14K] 1 illustrates various ways in which an electronic device may present an option to create a link (e.g., a “rich link”) to a contact in a messaging conversation (e.g., a “mention”) using suggested input user interface elements, according to some embodiments.

[0026] [Figure 15] 11 is a flow diagram illustrating a method for presenting an option to create a link (e.g., a rich link) to a contact in a messaging conversation (e.g., a "mention") using a suggested input user interface element. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Description of the embodiments The following description sets forth example methods, parameters, etc., however, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0028] In some implementations, the exemplary electronic device presents a messaging user interface. In some implementations, the messaging user interface allows a user to organize representations of messaging conversations in a customized manner. In some implementations, the messaging user interface allows an easy way for a user to view replies to messages in a messaging conversation. In some implementations, the messaging user interface allows a user to create and view links (e.g., rich links) that tag people in a conversation. Such techniques can reduce the cognitive burden on a user using the exemplary electronic device. Additionally, these techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0029] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first touch can be called a second touch, and a second touch can be called a first touch, without departing from the scope of various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

[0030] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should also be understood that as used herein, the term "and / or" refers to and includes any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0031] The term "if" is interpreted, optionally, depending on the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is interpreted, optionally, depending on the context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."

[0032] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generating component. The display generating component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, "displaying" content includes causing the content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate the content.

[0033] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface, however, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0034] The device typically supports a variety of applications, such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a videoconferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0035] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface, and corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each application. In this manner, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0036] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112 according to some embodiments. Touch-sensitive display 112 may be conveniently referred to as a "touch screen" and may also be known or referred to as a "touch-sensitive display system." Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0037] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​including at least four distinct values, and more typically including hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units that correspond to the surrogate measurement). In some implementations, the surrogate measurement for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible by the user on devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0038] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, the user feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0039] It is understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in FIG. 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

[0040] Memory 102 optionally includes high-speed random access memory, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. A memory controller 122 optionally controls access to memory 102 by other components of device 100.

[0041] The peripherals interface 118 may be used to couple input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 operate or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions and process data for the device 100. In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip, such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0042] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. The RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices, by wireless communication. RF circuitry 108 optionally includes well known circuitry for detecting near field Communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LTE), and other standard cellular technologies.Examples of technologies that may be used include, but are not limited to, wireless technology (IoT), wireless LAN (LAN), wireless LAN (LANG ... The present invention may use any of a number of communications standards, protocols, and technologies, including Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this application.

[0043] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives an electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data, and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

[0044] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking user gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

[0045] A quick press of the push button optionally disengages the lock on the touch screen 112 or optionally initiates the process of unlocking the device using a gesture on the touch screen, as described in U.S. Patent Application Serial No. 11 / 322,549, filed December 23, 2005, “Unlocking a Device by Performing Gestures on an Unlock Image,” U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0046] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals from touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0047] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or breaking of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the user's finger.

[0048] Touchscreen 112 optionally uses LCD (Liquid Crystal Display), LPD (Light Emitting Polymer Display), or LED (Light Emitting Diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

[0049] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication No. 2002 / 0015024(A1), each of which is incorporated herein by reference in its entirety. However, whereas touchscreen 112 displays visual output from device 100, a touch-sensitive touchpad does not provide visual output.

[0050] The touch-sensitive display in some embodiments of the touch screen 112 may be any of the touch-sensitive displays described in U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input No. 11 / 228,758, filed Sep. 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed Sep. 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed Sep. 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed Mar. 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

[0051] Touch screen 112 optionally has a video resolution of greater than 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. A user optionally contacts touch screen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to primarily handle finger contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on a touch screen. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

[0052] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface that is separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0053] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0054] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back side of device 100, as opposed to touchscreen display 112, which is on the front side of the device, so that the touchscreen display is effective for use as a viewfinder for acquisition of still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is, optionally, obtained for videoconferencing and the user sees other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing) so that a single light sensor 164 is used for both videoconferencing and still and / or video image capture, along with the touchscreen display.

[0055] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112 located on the front of device 100.

[0056] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to an input controller 160 within I / O subsystem 106. The proximity sensor 166 optionally functions as described in U.S. patent application Ser. No. 11 / 241,839, "Proximity Detector In Handheld Device," Ser. No. 11 / 240,788, "Proximity Detector In Handheld Device," Ser. No. 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output," Ser. No. 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices," and Ser. No. 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0057] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0058] Also, device 100 optionally includes one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 within the I / O subsystem 106. The accelerometer 168 functions optionally as described in U.S. Patent Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are hereby incorporated by reference in their entirety. In some embodiments, information is displayed on the touch screen display in portrait view or landscape view based on the analysis of data received from one or more accelerometers. Device 100 optionally includes, in addition to the accelerometer(s) 168, a magnetometer (not shown), and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the position and orientation (e.g., portrait or landscape) of device 100.

[0059] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device / global internal state 157, as shown in FIGS. 1A and 3. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information are occupying various regions of touchscreen display 112; sensor state, which includes information obtained from the device's various sensors and input control devices 116; and location information regarding the location and / or orientation of the device.

[0060] Operating system 126 (e.g., Darwin®, RTXC®, LINUX®, UNIX®, OS X®, iOS®, WINDOWS®, or an embedded operating system such as VxWorks®) includes various software components and / or drivers that control and manage common system tasks (e.g., memory management, control of storage devices, power management, etc.) and facilitate communication between various hardware and software components.

[0061] The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) are adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors that are the same as or similar to and / or compatible with the 30-pin connector used on iPod® (a trademark of Apple Inc.) devices.

[0062] The contact / motion module 130 optionally detects contact with the touch screen 112 (in cooperation with the display controller 156) and other touch sensing devices (e.g., a touch pad or a physical click wheel). The contact / motion module 130 performs various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting an event of a finger being lowered), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch sensing surface (e.g., detecting one or more events of a finger being dragged), and determining whether the contact has stopped (e.g., detecting an event of a finger being raised or an interruption of the contact), and includes various software components for performing these operations. The contact / motion module 130 receives contact data from the touch sensing surface. Determining the movement of the contact point, represented by a series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., contact with one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact with multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0063] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by a user (e.g., for determining whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of a particular physical actuator, but can be adjusted without changing the physical hardware of the device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of predefined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the sets of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0064] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0065] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

[0066] In some embodiments, graphics module 132 stores data representing the graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including, as appropriate, coordinate data and other graphic characteristic data, from an application or the like, and then generates screen image data for output to display controller 156.

[0067] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0068] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0069] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as photo / video metadata, and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0070] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ● Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141, ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ●Video player module, ●Music player module, ● Browser module 147, ● Calendar module 148, ● a widget module 149, optionally including one or more of a weather widget 149-1, a stocks widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that integrates a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0071] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0072] In conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the contacts module 137 is used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in the memory 102 or memory 370), including, optionally, adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with a name, associating an image with a name, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0073] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct a conversation, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0074] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

[0075] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In conjunction with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0076] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0077] In conjunction with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 contains executable instructions for creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor the workouts, selecting and playing music for the workouts, and displaying, storing, and transmitting the workout data.

[0078] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting still images or video from memory 102.

[0079] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 contains executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0080] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0081] In cooperation with the RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) in accordance with user instructions.

[0082] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a mini-application (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is downloaded and used by a user, or a mini-application (e.g., user-created widget 149-6) that is created by a user. In some embodiments, a widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (e.g., Yahoo! Widget).

[0083] In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the widget creator module 150 is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0084] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 contains executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user commands.

[0085] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0086] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0087] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data regarding businesses and other points of interest at or near a particular location, and other location-based data), optionally in accordance with user instructions.

[0088] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos rather than email client module 140. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed December 31, 2007, the contents of which are incorporated by reference in their entireties herein.

[0089] Each of the above-identified modules and applications corresponds to a set of executable instructions that perform one or more of the functions previously described and methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0090] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

[0091] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, a home menu, or a root menu from any user interface displayed on device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

[0092] FIG. 1B is a block diagram showing exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and respective applications 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

[0093] The event sorter 170 receives event information and determines the application 136-1 to which the event information is to be delivered and the application view 191 of the application 136-1. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, the application 136-1 includes an application internal state 192 that indicates the current application view(s) displayed on the touch-sensitive display 112 when the application is active or running. In some embodiments, the device / global internal state 157 is used by the event sorter 170 to determine which application(s) is / are currently active, and the application internal state 192 is used by the event sorter 170 to determine the application view 191 to which the event information is to be delivered.

[0094] In some embodiments, the application internal state 192 includes additional information such as resume information to be used when the application 136-1 resumes execution, user interface state information indicating or ready to display the information being displayed by the application 136-1, a state queue that enables the user to return to the previous state or view of the application 136-1, and a redo / undo queue of previous actions performed by the user.

[0095] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0096] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for a predetermined duration).

[0097] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173.

[0098] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0099] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which the touch is detected is optionally referred to as a hit view, and the set of events that are recognized as suitable inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0100] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchical manner, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which an initiating sub-event (e.g., the first sub-event in a sub-event sequence that forms an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source as identified as the hit view.

[0101] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0102] Event dispatcher module 174 dispatches the event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 182 in an event queue.

[0103] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0104] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within respective views of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other characteristics. In some embodiments, each event processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. The event processing unit 190 optionally utilizes or invokes the data update unit 176, object update unit 177, or GUI update unit 178 to update the internal state 192 of the application. Alternatively, one or more of the application views 191 include one or more respective event processing units 190. Also, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included in respective application views 191.

[0105] Each event recognition unit 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from this event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).

[0106] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device's attitude).

[0107] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events in an event (187) include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch on a displayed object for a given phase (touch start), a first lift off (touch end) for a given phase, a second touch on a displayed object for a given phase (touch start), and a second lift off (touch end) for a given phase. In another example, a definition of event 2 (187-2) is a drag on a displayed object. A drag includes, for example, a touch (or contact) on a displayed object to a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0108] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, when a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0109] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0110] If the respective event recognizer 180 determines that the sequence of sub-events does not match any of the events in the event definition 186, the respective event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch gesture.

[0111] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in a view or programmatic hierarchy.

[0112] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predefined process.

[0113] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs a predetermined process.

[0114] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by a video player module. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

[0115] In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0116] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 with input devices, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple presses or holds of a keyboard, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0117] FIG. 2 illustrates portable multifunction device 100 having touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upwards and / or downwards), and / or rolling of a finger in contact with device 100 (right to left, left to right, upwards and / or downwards). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0118] Device 100 also optionally includes one or more physical buttons, such as a "home" button or menu button 204. As previously mentioned, menu button 204 is optionally used to navigate to any application 136, optionally within a set of applications running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touch screen 112.

[0119] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on / off and locking the device, volume control button 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predefined period of time, to lock the device by pressing and releasing the button before the predefined time has elapsed, and / or to unlock the device or initiate an unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

[0120] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 that interconnect these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, including display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A) that generates tactile output on device 300, and sensors 359 (e.g., light, acceleration, proximity, touch-sensing, and / or contact intensity sensors similar to contact intensity sensor 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0121] Each of the above-identified elements of FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0122] Attention is now directed to embodiments of a user interface, optionally implemented, for example, on portable multifunction device 100.

[0123] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi® signals; ●Time 404, ●Bluetooth (registered trademark) indicator 405, ● Battery status indicator 406, ● Tray 408 with icons of frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled “Phone”, optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 of the email client module 140, labeled “Mail”, optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the Browser module 147, labeled "Browser"; and ○ An icon 422 of the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod"; and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; ○ Icon 426 of the Calendar module 148, labeled "Calendar", ○ Icon 428 of the image management module 144, labeled "Photos"; ○ An icon 430 of the camera module 143, labeled “camera”; ○ Icon 432 of the online video module 155, labeled "Online Video"; icon 434 of stock widget 149-2, labeled "Stocks" ○ Icon 436 of the map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 of alarm clock widget 149-4, labeled "Clock"; ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153, labeled "Notes"; and ○ A settings application or module icon 446 labeled “Settings,” which provides access to settings for the device 100 and its various applications 136 .

[0124] Note that the icon labels shown in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is displayed as "Music" or "Music Player." Other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0125] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3) that has a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451 and / or one or more tactile output generators 357 that generate a tactile output to a user of device 300.

[0126] Although some of the following examples are given with reference to input on touch screen display 112 (wherein the touch-sensitive surface and display are combined), in some embodiments the device detects input on a touch-sensitive surface that is separate from the display shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, user input (e.g., contacts 460 and 462 and their movements) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0127] In addition, although the following examples are given primarily with reference to finger input (e.g., finger contact, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a contact) followed by movement of a cursor along the path of the swipe (e.g., instead of a contact movement). As another example, a tap gesture is optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a contact and then stopping detection of the contact). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger contacts are optionally used simultaneously.

[0128] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0129] Exemplary techniques for detecting and processing touch intensity can be found, for example, in related applications, International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, published as International Patent Application No. WO / 2013 / 169849, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," and International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, published as International Patent Application No. WO / 2014 / 105276, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," each of which is incorporated herein by reference in its entirety.

[0130] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0131] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. The device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 can be connected to a display 504, which can have a touch-sensing component 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular, and / or other wireless communication techniques. The device 500 can include input mechanisms 506 and / or 508. The input mechanism 506 is optionally, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 is optionally a button.

[0132] In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which may be operatively connected to the I / O section 514.

[0133] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer readable storage media for storing computer executable instructions that, when executed by one or more computer processors 516, can, for example, cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, and 1500 (FIGS. 7, 9, 11, 13, and 15). A computer readable storage medium can be any medium that can tangibly contain or store computer executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer readable storage medium. In some embodiments, the storage medium is a non-transitory computer readable storage medium. A non-transitory computer readable storage medium can include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

[0134] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0135] The term "focus selector" as used herein refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations involving a cursor or other location marker, the cursor acts as the "focus selector," such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B) while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a detected contact on the touchscreen acts as the "focus selector," such that when an input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user intends to interact with).For example, positioning of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not another user interface element shown on the device's display).

[0136] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples, i.e., a set of intensity samples collected during a predefined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predefined event (e.g., after detecting a contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of a contact is optionally based on one or more of a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, a top 10 percentile value of the intensity of the contact, a half maximum intensity value of the contact, a 90 percent maximum intensity value of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to forego performing the respective action).

[0137] FIG. 5C illustrates detecting multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram showing the current intensity measurements of the intensity sensors 524A-524D versus intensity units. In this example, the intensity measurements of the intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of the intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to the contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the aggregate intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of a total intensity A according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

[0138] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a start location to an end location, at which point the intensity of the contacts increases. In this example, the characteristic intensity of the contacts at the end location is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contacts prior to determining the characteristic intensity of the contacts. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate small increases or decreases in the intensity of the swipe contacts for purposes of determining the characteristic intensity.

[0139] The intensity of the contact on the touch-sensitive surface is optionally characterized against one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an action different from an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., above a nominal contact-detection intensity threshold below which the contact is not detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light press intensity threshold or the deep press intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent among the various sets of user interface diagrams.

[0140] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detection of a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detection of a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0141] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed by a respective contact (or contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold followed by a decrease in intensity of the respective contact below the press input intensity threshold, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input intensity threshold (e.g., an "upstroke" of the respective press input).

[0142] 5E-5H illustrate detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 from an intensity below a light press intensity threshold (e.g., "ITL") in FIG. 5E to an intensity above a deep press intensity threshold (e.g., "ITD") in FIG. 5H. The gesture performed by contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed within default region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaks above a deep press intensity threshold (e.g., "ITD"). Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, contacts 562 having an intensity above a deep press intensity threshold (e.g., "ITD") during the gesture cause reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents to app2 to be displayed, as shown in Figures 5F-5H. In some embodiments, the intensity that is compared to the one or more intensity thresholds is a characteristic intensity of the contact. Note that the intensity diagrams for contacts 562 are not part of the displayed user interface, but are included in Figures 5E-5H as an aid to the reader.

[0143] In some embodiments, the display of representations 578A-578C includes an animation. For example, as shown in FIG. 5F, representation 578A is first displayed adjacent to application icon 572B. As the animation progresses, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, and representations 578A-578C appear and move upward as the intensity of contact 562 increases toward a deep press intensity threshold (e.g., "ITD"). In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H may be performed using an electronic device similar to or identical to device 100, 300, or 500.

[0144] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold having a predetermined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact above the pressure input intensity threshold, followed by a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an "upstroke" of each pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the context).

[0145] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or a gesture including a press input, are optionally triggered in response to detecting any of an increase in the intensity of the contact above the press input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of the contact below the press input intensity threshold, and / or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where operations are described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the operations are optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0146] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0147] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of applications: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and - Suspended or hibernated applications that are not running but have state information stored in memory (volatile and non-volatile respectively) and that can be used to resume execution of the application.

[0148] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the memory of the device). Thus, closing an application includes stopping and / or removing the application process for the application and removing the state information for the application from the memory of the device. Generally, opening a second application within a first application does not close the first application. When the second application is being displayed and the display of the first application is terminated, the first application becomes a background application.

[0149] Next, attention is directed to embodiments of a user interface ("UI") and associated processes implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500. User Interface and Associated Processes User Interface for Displaying Representations of Messaging Conversations

[0150] Users interact with electronic devices in many different ways, including using the electronic device to view messaging interactions. The embodiments described below provide a method of displaying representations of messaging interactions that, when selected, causes the electronic device to display the messaging interaction associated with the selected representation. In some embodiments, the electronic device displays one or more representations of the messaging interactions in a "pinned" area of ​​the user interface according to a user-defined order. Displaying the representations of the messaging interactions in a user-defined order enhances interaction with the device, such as by making it easier for a user to identify a representation of a particular interaction, thus reducing the time a user needs to perform navigational actions and increasing battery life of a battery-powered device by reducing the power usage of the device. It is understood that people use devices. When a person uses a device, the person is optionally referred to as a user of the device.

[0151] In some embodiments, the electronic device sorts one or more messaging interactions chronologically (e.g., based on the recency of messaging activity for those interactions). A user may wish to configure the electronic device to display one or more representations of messaging interactions at predetermined locations in the user interface independent of the chronology of messaging activity. FIGS. 6A-6SS show example ways in which an electronic device 500 displays representations of messaging interactions in accordance with some embodiments. The embodiments in these figures are used to illustrate the processes described below, including the process described with reference to FIG. 7. Although FIGS. 6A-6SS show various examples of ways in which an electronic device may perform the processes described below with reference to FIG. 7, it should be understood that these examples are not intended to be limiting and that an electronic device may perform one or more of the processes described below with reference to FIG. 7 in ways not explicitly described with reference to FIGS. 6A-6SS.

[0152] 6A illustrates electronic device 500 displaying an exemplary user interface 602 for configuring a pinned interaction of a messaging application. In some embodiments, user interface 602 is displayed in response to detecting activation of a pinned interaction (e.g., in response to a user input to configure the pinned interaction, in response to installing an updated version of a messaging application on the electronic device that includes the pinned interaction). In some embodiments, pinning a interaction allows a user to place a representation of the interaction in a prominent location in the user interface such that it appears in an easily accessible location for as long as the interaction is pinned. For example, a user may message his or her best friend every day. The user may wish to pin a representation of the messaging interaction to the top of the messaging application's user interface so that when the user enters the messaging application, the user can easily see the pinned interaction. The messaging application is optionally an application installed on electronic device 500 by which the electronic device can send and receive electronic messages and display information related to the messages as described herein. In some embodiments, the pinned interaction feature causes the electronic device 500 to display one or more representations of the interaction in a fixed location in the messaging application, while the representations of the non-pinned interactions are sorted in a list format, e.g., based on how recent new messaging activity has been received for the interaction, such that older messages are displayed at the bottom of the list. In some embodiments, one or both of the pinned and non-pinned messages are sorted according to different criteria. In some embodiments, both the pinned and non-pinned messages are sorted according to the same criteria. For example, both types of messages can each be sorted chronologically or in a predefined order.

[0153] As shown in Figure 6A, in some embodiments, a user selects option 604 to proceed to configure the pinned interaction (e.g., with contacts 603). In response to the user's selection in Figure 6A, electronic device 500 presents a user interface, such as the user interface shown in Figure 6B, for customizing the pinned interaction.

[0154] 6B illustrates an example messaging application user interface including representations 606a-606c of messaging interactions displayed in a pinned interactions area of ​​the messaging application user interface and representations 610a-610d of interactions displayed in an unpinned messages area of ​​the message user interface. In some embodiments, the messaging application may recommend a different number of interactions to be pinned. In some embodiments, the user may select the representations of the different interactions (e.g., 610a-d) to be pinned. The messaging interactions represented by the representations 606a-c are optionally selected by the electronic device 500 based on how frequently and / or recently messages have been received for the interaction and / or based on whether participants in the interaction are on the electronic device 500's favorite contacts list. In some embodiments, the electronic device 500 does not suggest which interactions to pin.

[0155] Representations 606a-606c are optionally displayed with a selectable option 608 that, when selected, causes electronic device 500 to remove the interaction from the pinned interaction area (e.g., moved to the unpinned area as representation 610). Representations 610a-d are optionally displayed with a selectable option 612 that, when selected, causes electronic device 500 to add the respective interaction to the pinned interaction area (e.g., and removed from the unpinned area as representation 610). In some embodiments, a user can select which representations should be displayed in the pinned interaction area and which representations should be displayed in the unpinned interaction area. In some embodiments, representations 610a-d of unpinned messaging interactions are sorted based on how recent new messaging activity has been received for the interaction. In some embodiments, representations 606a of pinned interactions are sorted by messaging interaction or other criteria, often based on other criteria such as how new messaging activity has been received.

[0156] In some embodiments, the user interface shown in FIG. 6B further includes a selectable option 614a that, when selected, causes the electronic device 500 to avoid adding any interactions to the pinned interaction area of ​​the messaging user interface, and a selectable option 614b that, when selected, causes the electronic device 500 to save the displayed arrangement of pinned and unpinned interactions and display a message user interface.

[0157] As shown in FIG. 6B, in some embodiments, a user selects option 614b (e.g., at contact 603) to save a configuration of pinned and unpinned interactions and display a messaging user interface with the pinned and unpinned interactions displayed according to the configuration, as shown, for example, in FIG. 6C.

[0158] FIG. 6C shows an exemplary messaging user interface that includes pinned conversation representations 606a - c and unpinned conversation representations 616a - f. As in FIG. 6C, the arrangement of representations 606a - c and 616a - f is the same as in FIG. 6B. Thus, in some embodiments, the user can use the user interface shown in FIG. 6B to configure the messaging user interface, for example, by selecting which conversations should be pinned, which conversations should not be pinned, and the arrangement of the pinned conversations in the displayed user interface. Next, the electronic device 500 displays the messaging user interface according to the configuration, as shown, for example, in FIG. 6C. The user interface optionally includes a selectable option 622a that, when selected, causes the electronic device 500 to display one or more settings related to the messaging user interface, and a selectable option 622b that, when selected, causes the electronic device 500 to initiate a process for creating a new message. In some embodiments, the one or more settings related to the messaging user interface displayed in response to the selection of option 622a include the option to rearrange and modify the conversations currently displayed in the pinned conversation area of the user interface.

[0159] The pinned messaging conversation representations 606a - c optionally include images (e.g., avatars) representing one or more users participating in each messaging conversation. In some embodiments, the images of the conversation participants do not include the user of the electronic device 500. In some embodiments, each representation of a messaging conversation includes text indicating the name of the user of the conversation. In some embodiments, group conversations are given a nickname that is displayed instead of the names of the conversation participants. In some embodiments, the image is associated with a group conversation (e.g., other than the image associated with the users of the conversation), and the image is used to represent the group messaging conversation. For example, the image associated with the users of the conversation is replaced with an image associated with the conversation, as will be described in more detail below with reference to FIG. 6I.

[0160] In some embodiments, each of the representations 616a-f of an unpinned messaging interaction includes an image 618a representing a user or users included in the interaction other than the user of electronic device 500, an indication 618b of the names of one or more users of the interaction other than the user of electronic device 500, and an indication 618c of the interaction's most recent messaging activity. Representations 616a-b and 616d-f optionally represent interactions that include one other user in addition to the user of electronic device 500, and representation 616c represents an interaction that includes two users in addition to the user of electronic device 500. In some embodiments, if an image is associated with a group interaction that is an image other than an image representing a user of the interaction, electronic device 500 displays an image associated with the group in representation 616 (e.g., in representation 616c) in place of an image associated with a user of the interaction.

[0161] In some embodiments, the representations 606a-c of pinned interactions do not include notifications of messaging activity in the most recent interactions, e.g., because there is no messaging activity in those interactions that are not read by the user of the electronic device 500. In contrast, in some embodiments, the representations 616a-f of unpinned interactions include notifications of messaging activity in the most recent interactions, e.g., because messaging activity in those interactions is "read" by the user. In some embodiments, messaging activity includes messages (e.g., text messages, audio messages, messages including images or other media) and tags added to messages (e.g., heart tags, thumbs up tags, thumbs down tags, loud tags, emphasis tags, etc.).

[0162] 6D , electronic device 500 optionally detects an indication 624d of messaging activity received from a contact (e.g., Alice) who is engaged in a messaging interaction with the user of electronic device 500 who has been pinned to a messaging application user interface by the user. In response to detecting the indication 624 of receipt of Alice's message, electronic device 500 optionally displays a representation 626a of received unread messaging activity, superimposed on the representation 606a of the messaging interaction, with the addition of a tag (e.g., a "heart" tag) to one of the messages of the interaction. Electronic device 500 optionally further displays an indication 620a that unread messaging activity exists in the interaction proximate to representation 606a of the messaging interaction.

[0163] In Figure 6E, the electronic device 500 receives an indication 624e that a user (e.g., Bob) is providing input to create a messaging activity in one of the interactions (e.g., currently typing a message before sending a message). In response to the indication 624e, the electronic device 500 optionally displays an indication 626b of the input superimposed on the representation 606b of the messaging interaction in which the user is providing input. As shown in Figure 6E, an indication 626a of the messaging activity in the other (e.g., Alice) interaction optionally remains displayed at the same size and / or location as the indication 626a displayed in Figure 6D. In some embodiments, the indication 626a is displayed at a smaller size in response to receiving the indication 624e.

[0164] In FIG. 6F, electronic device 500 optionally receives an indication 624f of messaging activity received in one of the interactions (e.g., an interaction with Bob). As shown in FIG. 6F, in response to receiving a new message added to the interaction, indication 624f, electronic device 500 displays a representation 626c of a new unread message. The content of representation 626c is optionally the content of the message, and representation 626c is optionally displayed superimposed on representation 606b of the messaging interaction. In some embodiments, if the length of the incoming message exceeds a predetermined threshold, the notification of message 626c includes the first part of the message text, followed by a notification that the message continues (e.g., "..."). Electronic device 500 optionally further displays an indication 620b that there is unread messaging activity in the interaction represented by representation 606b proximate to representation 606b of the interaction. As shown in FIG. 6F, in some embodiments, in response to receiving a new message indication, e.g., indication 624f, electronic device 500 changes the size (e.g., reduces the size) and / or location of previously received unread messages of the pinned interaction. For example, as shown in FIG. 6F, when indication 626c is received for the messaging interaction represented by representation 606b, indication 626a of previously received unread messaging activity of the interaction with Alice is reduced in size. In some embodiments, the location of the unread message notification is displayed in the same relative position for each pinned interaction. For example, as shown in FIG. 6F, indication 626c is the same for representation 606b as the position of indication 626a for representation 606a. In some embodiments, electronic device 500 ceases displaying notifications of unread messages of other pinned interactions when a new unread message is received for a particular messaging interaction. Instead, only the notification for the most recently received new unread message is displayed. For example, in FIG. 6F, instruction 626b may be the only instruction shown in the pinned interaction area in response to receiving instruction 624f.

[0165] In FIG. 6G, electronic device 500 optionally receives an indication 624g of a messaging activity of one of the messaging interactions (e.g., an interaction with Alice). In response to indication 624g, electronic device 500 optionally displays an indication 626d of the messaging activity superimposed on representation 606a of the messaging interaction, reducing the size (while maintaining the same position) and / or changing the position of a previously received indication 626c of the messaging activity. In some embodiments, indication 626d of the messaging activity includes at least a portion of the message. If the length of the message exceeds a predetermined threshold, electronic device 500 displays a first portion of the message with a notice that the message continues (e.g., "..."). In some embodiments, indication 626a continues to be displayed in response to indication 624g. In some embodiments, indication 626d is displayed in the same location where indication 626a was displayed. In some embodiments, indication 626d is displayed in a different location than where indication 626a was displayed. The electronic device 500 optionally continues to display the indication 620a of unread messaging activity for the messaging conversation. In some embodiments, the electronic device 500 ceases displaying the representation 626a shown in FIG. 6F of previously received messaging activity for the same messaging conversation.

[0166] In FIG. 6H, electronic device 500 optionally receives an indication 624h of messaging activity in one of the non-pinned interactions (e.g., the interaction with Mother). In some embodiments, electronic device 500 updates representation 616f of the interaction to include an indication 618f of the interaction's most recent messaging activity and an indication 620c that there is unread messaging activity in the interaction. As shown in FIG. 6H, indication 620c may be a dot displayed next to image 618d representing a user of the interaction for which a message has been received. In some embodiments, rather than displaying indication 620c, electronic device 500 may update representation 616f of the messaging interaction, such as changing the color, size, translucency of representation 616f, or changing the size and / or text styling of name 618e of user of interaction or text 618f of the message. In some embodiments, electronic device 500 reorders representations 618a-f of the non-pinned messaging interactions to display representation 616f from Mother at the top of the list of representations in the non-pinned area. 6H, the size of the indications 626c-d of messaging activity received for a pinned interaction optionally does not change in response to indication 624h of messaging activity received for a pinned interaction. However, in some embodiments, the indications 626c-d are displayed at a smaller size than they were before responding to indication 624h. In some embodiments, the size of the notifications 626c-d decreases over time (e.g., as time passes because messaging activity for those notifications 626c-d is received) regardless of newly received messaging activity in either pinned or unpinned interactions.

[0167] As shown in FIG. 6I, in some embodiments, the electronic device 500 receives an indication 624i of new messaging activity received in a pinned group conversation (e.g., from Chris in the Chris, Alex, and Eve conversation). In response to the indication 624i, the electronic device 500 optionally displays an indication 622e of the messaging activity superimposed on a representation 606c of the conversation proximate to an image associated with Chris, and displays an indication 620d of unread messaging activity proximate to the representation 606c of the conversation. The electronic device 500 optionally updates the representation 606c of the conversation to display an image corresponding to a contact that sent a message to the remaining side (e.g., the left side) of the representation 606c (e.g., Chris's avatar moves from within the representation 606c to an outer portion of the representation 606c). As shown in FIG. 6I, in some embodiments, the indication 622e is displayed proximate to Chris's avatar. In some embodiments, the representations of other users in the group conversation remain inside the representation 606c. In some embodiments, if the representation 606c of the group conversation is an image other than an image associated with the users of the conversation, the electronic device 500 optionally updates the representation 606c to include an image (e.g., an avatar) corresponding to the user who sent the received message, as shown in FIG. 6I, but the display is superimposed on an outer portion of an image representing the group rather than on an outer portion of a container having an image representing the other users of the conversation (e.g., as shown in FIG. 6I). In some embodiments, the indication 622e includes at least a portion of the content of the message. If the message is less than a threshold length, the indication 622e optionally includes the entire content of the message. If the message is greater than the threshold length, the indication 622e optionally includes a first portion of the message and an indication that the message continues (e.g., “…”).

[0168] As also shown in FIG. 6I, in some embodiments, the indicators 626c-d of other messaging activities of the pinned conversation are reduced in size in response to indicator 624i (e.g., while remaining in the same position). The size of indicators 626c-d is smaller than the size of indicators 626c-d in FIG. 6H before receiving indicator 624i.

[0169] As shown in FIG. 6I, in some embodiments, the user selects one of the representations 606a of the conversation (e.g., using contact 603). In response to the user's selection in FIG. 6I, the electronic device 500 optionally displays a messaging conversation corresponding to representation 606a, as shown in FIG. 6J.

[0170] As shown in FIG. 6J, the electronic device 500 optionally displays a user interface 626 that includes notifications of tags added to one of the messages received in FIG. 6D and notifications of messaging activities of the messaging conversation that include the representation of the message received in FIG. 6G. As shown in FIG. 6J, in some embodiments, the user returns to the user interface shown in FIG. 6K (e.g., using contact 603). As shown in FIG. 6K, in some embodiments, when the electronic device 500 redisplay the messaging user interface, the electronic device 500 optionally displays representation 606a without indicators 626d and 620a because the message associated with representation 626d has been read by the user of the electronic device 500 (e.g., the content of the messaging conversation is being displayed by device 500 in FIG. 6J) and there are no new unread messages associated with the message conversation with Alice.

[0171] In some embodiments, the electronic device 500 provides a way for the user to rearrange the representations of the messaging conversations of the messaging user interface to move unpinned conversations into the group of pinned conversations and vice versa.

[0172] In FIG. 6K, the user selects, for example, one of the non-pinned interaction representations 616c (e.g., using contact 603). In some embodiments, contact 603 is detected on representation 616c for a period exceeding a predetermined threshold (e.g., 0.25 seconds or 0.5 seconds or 1 second) before movement of the contact is detected, thereby dragging the interaction representation as shown in FIG. 6L. In some embodiments, if contact 603 is not detected for a period longer than a predetermined threshold before movement of the contact is detected, the input is optionally interpreted not as an input to move the non-pinned interaction to the pinned area, but as a scroll input for scrolling the non-pinned interaction.

[0173] In some embodiments, after a predetermined threshold (e.g., when the user begins to move contact 603), the device 500 optionally stops displaying representation 616c in the non-pinned area and changes the interaction representation to representation 606d (e.g., pinned area representation) as shown in FIG. 6L. In FIG. 6L, the user optionally continues to drag the interaction representation 606d, which is currently optionally the pinned interaction representation, towards other representations 606a - c of the pinned interaction (e.g., using contact 603). In some embodiments, when the electronic device 500 begins to display representation 606d, the electronic device 500 moves representations 616a - b and 616d - g downward to create an open row in the pinned area of the user interface (e.g., the row where representation 606c is displayed in FIG. 6M, the area where message 648 is displayed in FIG. 6FF, etc.), which is an area where the user can drag representation 606d towards if the user chooses to do so. In some embodiments, representation 616c continues to be displayed until it is dragged to the pinned interaction area of the user interface. In some embodiments, once representation 616c is dragged to the pinned interaction area of the user interface, the electronic device 500 replaces representation 616c with the pinned interaction representation 606d.

[0174] In FIG. 6M, the user places representation 606d in the messaging interaction with other representations 606a-c in the pinned interaction (e.g., representation 606d is optionally placed upon detecting lift-off of contact 603 at the location of contact 603 when lift-off is detected). As shown in FIG. 6M, in some embodiments, the user may select a location within the pinned interaction area in which to place representation 606d. In FIG. 6M, the user lifts off contact 603, moves representation 606d to a location determined to be representation 606c (e.g., closer to representation 606c than to another representation, e.g., representation 606b), optionally causing representation 606d to be displayed in place of representation 606c, and moves representation 606c down to a second line of display in the pinned area (e.g., automatically created by device 500 upon detecting the addition of representation 606d and the overflow of the first line of pinned representations). In contrast to the ordering of pinned interactions, in some embodiments, representations 616a-616b and 616d-f of unpinned interactions are arranged according to the order in which the interactions' most recent messaging activity was received.

[0175] As also shown in Figure 6M, in some embodiments, a user selects (e.g., with contact 603) a representation 606a of another pinned interaction. In some embodiments, contact 603 is detected on representation 606a for a period of time that exceeds a predetermined threshold (e.g., 0.25 seconds, or 0.5 seconds, or 1 second) before movement of the contact is detected, thereby dragging the representation of the interaction, as shown in Figure 6N.

[0176] In some embodiments, upon detecting the movement of representation 606a outside of the pinned region and into the unpinned region, device 500 changes representation 606a to unpinned representation 616h (e.g., no longer displays representation 606a), as shown in Figure 6N. In Figure 6N, the user continues to drag (e.g., with contact 603) representation 616h of the messaging interaction, which is currently displayed as representation 616h of the unpinned interaction, for example, into an unpinned interaction area of ​​the user interface. Thus, as shown in Figure 6N, in some embodiments, as soon as the user drags representation 606a from the pinned region of the user interface into the unpinned region of the user interface, the representation of the interaction is displayed as representation 616h of the unpinned interaction. However, in some embodiments, the electronic device 500 displays the pinned interaction representation 606a while the user continues to drag the representation to an unpinned area of ​​the user interface and, in response to detecting lift-off of the contact 603 shown in FIG. 6N, updates the representation to an unpinned interaction representation 616h.

[0177] 6O, when lift-off of contact 603 is detected, electronic device 500 displays representation 616h of the messaging interaction among the other representations 616a-b and 616d-f of the unpinned interactions. Rather than displaying representation 616h where lift-off of contact 603 was detected, electronic device 500 sorts representations 616 of the unpinned interactions according to how the last messaging activity of each interaction was received. Thus, in some embodiments, in response to detecting lift-off of contact 603, representation 616h is displayed above representation 616a of the unpinned interaction area because, although lift-off of contact 603 was detected while representation 616h was displayed below representation 616a, the last messaging activity of the interaction corresponding to representation 616h was more recent than the last messaging activity of the interaction corresponding to representation 616a.

[0178] Also, as shown in FIG. 6O, a user can select (e.g., using contact 603) an option 622a that shows one or more selectable options for performing an action related to the message user interface (e.g., selecting one or more messaging conversations, editing information associated with the user account of the electronic device, editing pinned and unpinned conversations). In some embodiments, the user can select an option (not shown) to cause the electronic device 500 to display a user interface for editing which conversations are pinned and unpinned.

[0179] FIG. 6P illustrates an exemplary user interface for editing which interactions are pinned and unpinned. The user interface illustrated in FIG. 6P is optionally similar to the user interface described above with reference to FIG. 6B. The representations 606b-d of pinned interactions may include a selectable option 608 that, when selected, causes the electronic device 500 to remove the associated representation 606 from the pinned interactions (e.g., move the interaction to an unpinned area). The electronic device may animate the representations 606b-d of pinned interactions with a wiggle or other motion to indicate that the positions of the representations 606b-d may be changed, changing which interactions are pinned and which are unpinned. The representations 610a-b, 610d, 610f, and 610h of unpinned interactions optionally include a selectable option 612 that, when selected, causes the electronic device 500 to add the associated representation 610 to the pinned interactions (e.g., remove the interaction from the unpinned area). Thus, in some embodiments, electronic device 500 moves the representation between pinned and unpinned interaction sections of the user interface according to one or more user inputs to do so. As shown in Figure 6P, in some embodiments, the user selects an option (e.g., with contact 603) to save the changes to the pinned interaction and return to the user interface shown in Figure 6Q.

[0180] In FIG. 6Q, in some embodiments, the user selects the representation 616f of the interaction with the unread message (e.g., using contact 603) as indicated by the instruction 620c included in the representation 616f. In response to the user's selection, the electronic device 500 optionally displays the messaging interaction in a manner similar to how FIG. 6J shows a different messaging interaction. After the user returns from the messaging interaction, the electronic device 500, as shown in FIG. 6R, since the message has been read by the user, the electronic device 500 optionally displays the representation 616f of the messaging interaction without the instruction 620c for the unread message.

[0181] FIG. 6S shows an electronic device 500 that displays exemplary messaging user interfaces having group interaction representations 606e, 606g, 616i, and 616j that include more than two users (including the user of the electronic device 500) (e.g., in addition to other representations of the interaction, the details of which are described with reference to FIGS. 6A - 6R).

[0182] Representations 606e and 616i optionally include images (e.g., avatars) 630a-630f of other users included in the group interaction. Representations 630a-630f are optionally sized based on how recently each user has sent messaging activity to the group interaction. In the interaction associated with representation 606e, representation 630f is optionally displayed at the largest size among the other representations of the interaction because the user associated with that representation 630f is the most recent user other than the user of electronic device 500 to send messaging activity to the group interaction. The user associated with representation 630d is optionally the least recent user other than the user of electronic device 500 to send messaging activity to the group interaction, and thus representation 630d is optionally the smallest representation of the users included in representation 606e of the group interaction. In some embodiments, representation 616i of an unpinned group interaction similarly includes avatars 630a-c of the users of the group interaction. In some embodiments, pinned and unpinned representations of a group interaction are displayed in a similar manner. In some embodiments, electronic device 500 displays representations of users up to a maximum number of representations of users in the user interface shown in FIG. 6S (e.g., 5 or 6 or 7 or 8 or 9 users). If there are more users in the interaction than the maximum number of representations of users displayed, electronic device 500 optionally displays in the representation of the group interaction the maximum number of users who most recently added messaging activity to the messaging interaction. In some embodiments, while displaying the messaging interaction of a group interaction (e.g., in a user interface similar to the user interface shown in FIG. 6J), electronic device 500 may display a different maximum number of representations of users at the top of the user interface that is either more than or less than the maximum number of representations of users that may be displayed in the representation of the group interaction in the user interface shown in FIG. 6S (e.g., 4 or 5 or 6 or 7 or 8 or 9 or 10 or 11 or 12 or 13).In some implementations, the representation of the message that displays images associated with others in the group message is based on a template. Each template can vary the size and position of the images associated with others in the group message. The size and position of the images can be based on the recency of the message received by each person in the group. There can be a specific template based on the number of people in the group message. For example, a group message that includes three people other than the user of the electronic device may have space for three images representing the other people in the group message. Each group message that includes three people other than the user of the electronic device can use the same template (e.g., vary the size and position in the same way) so that each group message representation shows images in a uniform manner. For example, an image representing the person who sent the most recent message can be shown to the right of the group representation, at the maximum size of the representation of the group members.

[0183] Representations 606g and 616j, for example, include images 628a and 628b associated with group interactions. Because these group interactions have associated images 628a and 628b set by the respective users of the respective interactions, images 628a and 628b are optionally displayed in place of an image (e.g., an avatar) associated with the user of the interaction. Thus, in some embodiments, representations of pinned and unpinned group interactions having associated images (e.g., other than the avatar of the user of the group interaction) are displayed in a similar manner.

[0184] 6T, electronic device 500 detects an indication 624t of a message received in a group interaction associated with representation 606e. In response to representation 624t, electronic device 500 optionally displays a representation 630d of the user who sent the message at the periphery (e.g., an outer portion) of representation 606e (e.g., by moving representation 630d to the periphery of representation 606e), a representation 626e of the contents of the message displayed with (e.g., overlaid on a portion of) representation 630d, and an indication 620e that there are unread messages in the interaction.

[0185] In some embodiments, representation 630d is displayed at a larger size in Figure 6T than in Figure 6S. In some embodiments, when a user views the messaging conversation associated with representation 606e and returns to the user interface shown in Figure 6T, electronic device 500 updates representation 606e to include representation 630d within it. In some embodiments, representation 630d should be displayed at a larger size than the other representations 630e and 630f within the conversation because the most recent message is from the user associated with representation 630f, and representation 630f should be displayed larger than representation 630e because the user associated with representation 630f has contributed more recent messaging activity to the conversation than the user associated with representation 630e.

[0186] As mentioned above, in some embodiments, if the number of users in the interaction exceeds a predetermined threshold (e.g., 5 or 6 or 7 or 8 or 9, etc.), then only the greatest number of users with recent messaging activity are displayed in the representation of the group interaction. In response to receiving messaging activity from a user whose representation is not included in the representation of the group interaction (e.g., because the user has not recently contributed messaging activity to the interaction), electronic device 500 optionally displays a representation of the user on the edge of the representation of the group interaction, and the least representation of the user in the representation of the group is not displayed.

[0187] In some embodiments, if a message is received in a dialogue associated with representation 606g, electronic device 500 displays the representation of the user who sent the message in a manner similar to how electronic device 500 displays representation 630d of the user who sent the message in dialogue 606e. For example, electronic device 500 displays (e.g., populates) the representation of the user in the periphery of image 606g with the representation of the received message.

[0188] In some embodiments, if a message is received in either interaction associated with representation 616i and representation 616j (e.g., an unpinned message interaction in an unpinned messaging area of ​​a messaging application user interface), electronic device 500 avoids displaying the representation of the user who sent the message in the periphery of image 628b, or the circle in which representations 630a-c are displayed. Instead, electronic device 500 optionally updates the text of representation 616i or 616j to include a notification of the most recent message, as described above. In some embodiments, if one of the users associated with representation 630b or 630c sends a message to the interaction associated with representation 616i, electronic device 500 optionally updates representation 616i of the interaction to display the representation of the user who sent the most recent message in maximum size compared to the representations of the other users. If the number of users in the interaction exceeds the maximum number of user representations that may be displayed simultaneously in a representation of the group interaction and a user who provided the most recent messaging activity is not currently displayed in the group's representation, the electronic device updates the group representation to remove the user's smallest representation in the representation, reduce the size of the other user representations, add the representation of the most recently sent user to the representation of the group message, and display that user representation at its maximum size.

[0189] In FIG. 6U, electronic device 500 optionally detects an indication 624u of another incoming message of the interaction associated with representation 606e from a user associated with image 630e (e.g., Alice). In response to detecting indication 624u, electronic device 500 displays image 630e in a periphery (e.g., outer portion) of representation 606e of the interaction and displays an indication 626f of the received message superimposed on image 630e. Electronic device 500 optionally reduces the size of image 630d and indication 626e in response to indication 624u. In some embodiments, electronic device 500 updates the user interface to display image 630d away from the periphery of representation 606e (e.g., entirely within representation 606e) in response to indication 624u.

[0190] FIG. 6U shows that in some embodiments, in response to instruction 624u, electronic device 500 decreases the size of instruction 626e, whereas electronic device 500 ceases displaying instruction 626e in response to instruction 624u as shown in FIG. 6V. As shown in FIG. 6V, in response to receiving message instruction 624u, electronic device 500 displays representation 630e of the contact who sent the message in the periphery of representation 606e of the group interaction with representation 626f of the message. Representation 630d of the contact who sent the previously received message is optionally displayed at a smaller size than the size at which representation 630d was displayed in FIG. 6T. In some embodiments, electronic device 500 displays the notification of the incoming message in representation 606g similar to the example described with reference to FIGS. 6T-6V, because representation 606g is a representation of a pinned interaction. In some embodiments, electronic device 500 ceases to display notifications of received messages in the manner described with reference to Figures 6T-6V for representations 616i and 616j because representations 616i and 616j are representations of unpinned interactions. As shown in Figure 6V, as more messaging activity is received in the group interaction, representations of contacts that sent messages are displayed on alternating sides of the periphery of representation 606e, as described in more detail below with reference to Figures 6II-6LL.

[0191] In some embodiments, as described above, a user may wish to edit which interactions are pinned to the top of the messages user interface. In some embodiments, electronic device 500 can initiate an additional process to move representations of interactions from unpinned areas of the user interface to pinned areas of the user interface, as described next.

[0192] As shown in Figure 6W, the user swipes right (e.g., with contact 603) over representation 616h of an unpinned interaction. In some embodiments, in response to a right swipe that meets one or more criteria (e.g., speed or length based criteria, such as speed above a threshold or length above a threshold), electronic device 500 pins the interaction without additional input (e.g., pins as representation 606a), as shown in Figure 6Z. In some embodiments, in response to a right swipe that fails to meet one or more criteria (e.g., speed or length based criteria, speed or length below a respective threshold, etc.), electronic device 500 displays an option to pin the interaction, as shown in Figure 6X.

[0193] In Figure 6X, in response to a swipe input that does not meet one or more criteria, such as the swipe input shown in Figure 6W, electronic device 500 displays option 632 adjacent to representation 616h that, when selected, causes electronic device 500 to display option 632 to pin the interaction associated with representation 616h. As shown in Figure 6Y, a user selects option 632 (e.g., with contact 603) to pin the interaction associated with representation 616h.

[0194] FIG 6Z illustrates a subsequent user interface of the interaction associated with the representation 616h shown in FIGS. 6W-6Y being pinned. The electronic device 500 displays a representation 606a of the interaction in the pinned interaction area in response to either a swipe input that meets the criteria, such as the swipe input shown in FIG 6W, or a selection of option 632 to pin the interaction, as shown in FIG 6Y. As shown in FIG 6Z, the representation 616h is optionally no longer displayed in the unpinned interaction area. In some embodiments, the representation 606a is added to the end of the pinned interaction.

[0195] In some embodiments, electronic device 500, in response to detecting a selection of a representation of the interaction having a first special characteristic (e.g., a contact that remains in place for a predetermined time, such as a touch-and-hold input), displays a menu associated with the messaging interaction, including an option to add the interaction to the pinned interaction. For example, FIG. 6Z shows a user selecting (e.g., with contact 603) representation 616b of the interaction. In some embodiments, the selection (e.g., with contact 603) is detected in a time that exceeds a predetermined threshold (e.g., 0.5 seconds, 1 second, 2 seconds).

[0196] In response to the user's selection of Figure 6Z, electronic device 500 optionally displays the user interface shown in Figure 6AA. As shown in Figure 6AA, electronic device 500 optionally displays a representation 642a of a messaging conversation corresponding to representation 616b, as well as a number of selectable options 644a-c that, when selected, cause electronic device 500 to send content and a message indicated by the selected option to the messaging conversation, option 644d that, when selected, causes electronic device 500 to send a custom message to the messaging conversation, and option 646a that, when selected, causes electronic device 500 to pin the messaging conversation associated with representation 616b. In Figure 6AA, the user selects option 646a (e.g., with contact 603) to pin the conversation.

[0197] In some embodiments, in response to the user's selection of Figure 6AA, the electronic device 500 updates the user interface to present the representation 606h of the messaging interaction in the pinned interaction area of ​​the user interface (e.g., and no longer displays the representation 616b in the unpinned interaction area of ​​the user interface), as shown in Figure 6BB. In some embodiments, the representation 606h is displayed at the end of the pinned interaction section of the user interface.

[0198] As also shown in FIG. 6BB, a user selects one of the pinned interaction representations 606a (e.g., with contact 603). In some embodiments, electronic device 500 detects contact 603 for a time period that exceeds a predetermined threshold (e.g., 0.5 seconds, 1 second, 2 seconds). In some embodiments, in response to detecting contact 603 shown in FIG. 6BB for a time period that exceeds the threshold, electronic device 500 displays the user interface shown in FIG. 6CC.

[0199] As shown in Figure 6CC, electronic device 500 optionally displays a representation 642b of a messaging conversation that corresponds to representation 606a, as well as a number of selectable options 644e-g that, when selected, cause electronic device 500 to send a message to the messaging conversation represented by the selected option, an option 644h to send a custom message to the conversation, and an option 646b to unpin the conversation. As shown in Figure 6CC, the user selects option 646b (e.g., with contacts 603) to unpin the conversation.

[0200] In some embodiments, in response to the user's selection of FIG. 6CC, the electronic device 500 stops displaying the representation 606a shown in FIG. 6BB and instead updates the messaging user interface to display a representation 616h of the interaction in the unpinned interaction area of ​​the user interface, as shown in FIG. 6DD.

[0201] In some embodiments, while electronic device 500 displays representations of messaging interactions in unpinned regions of the user interface without displaying representations of the messaging interactions in pinned regions of the user interface (e.g., because the interactions have not yet been placed in a pinned region by the user), the user may desire to move any one or more of the representations to a pinned region of the user interface. In response to an input to begin dragging the representation of the unpinned messaging interaction, electronic device 500 optionally displays a notification of where to drag and drop the representation of the unpinned interaction to pin the interaction when there are no unpinned interactions in the user interface, as described next with reference to FIGS.

[0202] In some embodiments, as shown in FIG. 6EE, electronic device 500 displays a messaging user interface including representations 616 of messaging interactions. Electronic device 500 optionally displays representations 616 such that representations 616 of interactions with most recent messaging activity are displayed toward the top of the user interface. For example, the interaction associated with representation 616i has the most recent messaging activity, and the interaction associated with representation 616l has at least the most recent messaging activity among the interactions for which representation 616 is currently displayed. In some embodiments, the user can scroll down in the messaging user interface to uncover additional representations of the interactions that are not pinned. In FIG. 6EE, the interaction is not yet pinned. As shown in FIG. 6EE, the user, for example, selects one of the representations 616h of the messaging interactions (e.g., with contact 603). Electronic device 500 optionally detects contact 603 for a time period that exceeds a predetermined threshold (e.g., 0.5 seconds, 1 second, 2 seconds). In some embodiments, in response to the electronic device 500 detecting contact 603 for a time period exceeding a predetermined threshold, as shown in FIG. 6FF, the electronic device 500 displays a notification of where to drag the representation to pin the interaction (e.g., at the top of the messaging user interface, in an area corresponding to where the pinned interaction is displayed).

[0203] As shown in FIG. 6FF, the electronic device 500 optionally displays an indication 648 of a region of the user interface corresponding to the representation 606a and the pinned interaction region of the user interface. In some embodiments, the representation 616h shown in FIG. 6EE is replaced with the representation 606a shown in FIG. 6FF in response to detecting the contact 603 shown in FIG. 6EE for a time exceeding a predetermined time threshold before the user begins to drag the interaction representation 606a. In some embodiments, the representation 616h shown in FIG. 6EE is replaced with the representation 606a shown in FIG. 6FF in response to the user dragging the representation 606a at least a threshold distance. In response to detecting that the user drags (e.g., using a contact) the representation 606a to the region 648, the electronic device 500 optionally displays the representation 606a in the pinned interaction region of the user interface as shown in FIGS. 6GG-6HH.

[0204] In some embodiments, as shown in FIG. 6GG, the user drags the representation 606a with the contact 603 to the indication 648. In response to detecting the lift-off of the contact 603 at the location shown in FIG. 6GG (or any other location overlapping the indication 648), the electronic device 500 optionally displays the interaction representation 606a of the pinned interaction region of the user interface as shown in FIG. 6HH.

[0205] In some embodiments, as shown in FIG. 6HH, in response to the user dragging and dropping the representation 606a to the indication 648b as shown in FIGS. 6EE-6GG, the electronic device 500 displays the representation 606a at a predetermined position (e.g., the left side, the first position of the pinned region, etc.) of the pinned interaction region of the user interface. In some embodiments, since the representation 606a is optionally the first representation displayed in the pinned region, regardless of the location within the region where the representation 606a is dropped, the electronic device 500 displays the representation 606a at a predetermined location (e.g., the left side) of the pinned interaction region.

[0206] In some embodiments, rather than displaying representation 606a in a predefined location (e.g., to the left) of the pinned interaction area as shown in Figure 6HH, electronic device 500 displays representation 606a proximate to where representation 606a was dropped (e.g., in response to detecting lift-off of contact 603). For example, in response to detecting representation 606a being dropped at the location shown in Figure 6GG, electronic device 500 optionally displays representation 606a in the center of the pinned interaction area.

[0207] As mentioned above, in some embodiments, electronic device 500 displays a notification of the last message received in the group interaction, including displaying a representation of the user who sent the last group message in the periphery of the representation of the group interaction. Electronic device 500 optionally ceases displaying the notification of the message when another message is received in the interaction, but optionally continues to display representations of users who have recently contributed messaging activity to the messaging interaction. In some embodiments, there is a maximum number of representations of users that are displayed in the periphery of the representation of the group interaction, such as two or three or four. These and other exemplary details are now described.

[0208] Fig. 6II shows an example of a representation 606e of a group interaction. Representation 606e may be, for example, the same representation having the same interaction history as described above with reference to Figs. 6T-6V. In Fig. 6II, electronic device 500 optionally displays indicia 630d (e.g., an avatar) in the periphery of representation 606e because a user represented by representation 630d has previously sent messaging activity to the interaction that has not yet been read by the user of electronic device 500. Electronic device 500 optionally displays an indication 626f of a recent messaging activity sent to the interaction, and optionally displays a representation 630e of a user who sent a message associated with indication 626f in the periphery of representation 606e (e.g., indication 626f is optionally superimposed over a portion of representation 630e). In some embodiments, representation 630e is displayed at a size larger than the size of representation 630d, even though both representations are displayed on the periphery (e.g., outer portion) of representation 606e, because a user associated with representation 630e sent messaging activity to the interaction more recently than a user associated with representation 630d, which sent messaging activity to the interaction.

[0209] In FIG. 6JJ, electronic device 500 optionally detects indication 624jj that a user associated with representation 630g is currently providing input that constitutes a messaging activity for the messaging conversation (e.g., typing, but not yet sending the messaging activity). In some embodiments, in response to indication 624jj, electronic device 500 displays indication 626h that a user is providing input to a messaging conversation with representation 630g displayed in the periphery of representation 606e (e.g., indication 626h optionally overlays a portion of representation 630f, with representation 630f moving from an inner portion to an outer portion of representation 606e). In some embodiments, representation 630f is displayed on a side of representation 606e opposite the side on which representation 630e is displayed because representation 630e was the most recent user avatar displayed in the periphery. In some embodiments, representation 630f is displayed above representation 630d because messaging activity associated with representation 630f was received more recently than messaging activity associated with representation 630d. In some embodiments, in response to displaying representation 630f, electronic device 500 moves representation 630d (e.g., moves representation 630d down to create room for representation 630f). Electronic device 500 optionally displays representation 630f at the same size as representation 630e and ceases displaying representation 626f shown in FIG. 6II. In some embodiments, in response to instruction 624jj, electronic device 500 does not reduce the size of representations 630e and 630d of other users who have recently contributed messaging activity to the messaging dialogue because a message associated with the input corresponding to instruction 624jj has not yet been sent. In some embodiments, in response to instruction 624jj, electronic device 500 reduces the size of representations 630e and 630d of other users who have recently contributed messaging activity to the messaging dialogue (e.g., while maintaining their relative size) and displays representation 630f at a size larger than representations 630e or 630d.

[0210] In Figure 6KK, the user stops providing input for configuring the messaging activity in the messaging dialogue (e.g., stops typing a message without sending the message). In some embodiments, in response to ceasing to detect user instructions 624jj for configuring the messaging activity shown in Figure 6JJ, electronic device 500 stops displaying instructions 626h, displays user instructions 630g inside representation 606e of the messaging dialogue rather than on the periphery of representation 606e of the messaging dialogue, and redisplays representation 626f of the dialogue's most recent unread message.

[0211] In FIG. 6LL, electronic device 500 detects an indication 62411 of a message sent by a user associated with representation 630g. In response to indication 62411, electronic device 500 optionally displays indication 626g of the message (e.g., overlays a portion of representation 630g), displays representation 630g of the user setting the message in the periphery of representation 606e of the messaging dialogue, reduces the size of indications 630e and 630d of other users who have recently contributed messaging activity to the dialogue, and ceases displaying representation 626f of another message as shown in FIG. 6KK. In some embodiments, representation 630f is displayed on the side of representation 606e opposite the side on which representation 630e is displayed because representation 630e was the most recent user avatar displayed in the periphery. In some embodiments, representation 630f is displayed above representation 630d because messaging activity associated with representation 630f was received more recently than messaging activity associated with representation 630d. In some embodiments, in response to displaying representation 630f, electronic device 500 moves representation 630d (eg, moves representation 630d down to create room for representation 630f).

[0212] As mentioned above, in some embodiments, there is a maximum number of representations of users that the electronic device 500 displays in the periphery of the representation of the group interaction. Although an example is described in which the electronic device 500 displays up to three representations of users, it should be understood that the maximum can be a different number, such as two or four or five or any other suitable number. In this example, while displaying the representations of the three users in the periphery of the representation of the group interaction, the electronic device 500 receives a display of an additional message received in the interaction from a user whose avatar is not currently displayed in the periphery of the representation of the interaction. In this example, in response to the notification of the new message, the electronic device 500 ceases displaying a minimal representation of another user (e.g., representation 630d of FIG. 6LL) displayed in the periphery of the representation 606e, reduces the size of the other representations of the users displayed in the periphery of the representation 606e of the interaction, and displays a representation of the user who sent the most recent message in the periphery of the representation of the group interaction. In some embodiments, the representations of the users are alternately displayed on opposite sides of the representation of the group interaction. For example, if a representation of a user who sent a most recent message to the interaction is displayed to the right of the representation of the group message, electronic device 500 optionally displays a representation of the next user to send a message to the left of the representation of the group interaction, etc. In some embodiments, electronic device 500 displays representations of users who have a most recent messaging interaction in a vertical location above representations of users who have less recent messaging activity. For example, in FIG. 6LL, representation 630g is displayed in a vertical location above representation 630d because the user associated with representation 630g sent a message to the more recent interaction to which the user associated with representation 630d has responded.

[0213] Returning to Figure 6LL, a user selects (e.g., with contact 603) a representation 606a of a messaging interaction. In some embodiments, contact 603 is detected for a time that exceeds a predetermined threshold (e.g., 0.5 seconds, 1 second, 2 seconds, 3 seconds). In some embodiments, this predetermined threshold is longer than the predetermined thresholds discussed above with reference to Figures 6Z and 6BB.

[0214] In some embodiments, in response to a user selection of FIG. 6LL in which contact 603 is detected for a time period exceeding a predetermined threshold, electronic device 500 displays a user interface for editing the pinned interactions, as shown in FIG. 6MM. In some embodiments, while displaying the user interface for editing the pinned interactions, the user can drag a representation 616 of an unpinned interaction into the pinned interactions area to pin it, drag a representation 606 of a pinned interaction down onto an unpinned interaction to unpin it, and / or rearrange the order of the representations 606 of the pinned interactions. As shown in FIG. 6MM, the user can select and drag the representation 606a of the pinned interaction (e.g., with contact 603) to rearrange its position within the other pinned interactions.

[0215] In some embodiments, as shown in Figure 6NN, in response to the input shown in Figure 6MM, electronic device 500 displays representation 606a where representation 606a was dragged by the user. Electronic device 500 optionally moves display 606g to the second column of pinned interactions to accommodate representation 606a in the first row of pinned interactions. As shown in Figure 6NN, the user selects option 612 (e.g., with contact 603) to add the interaction associated with representation 616b to the pinned interactions.

[0216] In some embodiments, as shown in Figure 6OO, in response to the user input shown in Figure 6NN, the electronic device 500 displays a representation 606h of the interaction selected by the user upon exiting the pinned interaction area of ​​the user interface and ceases displaying a representation 616b of the interaction in the unpinned area of ​​the user interface. In Figure 6OO, the user, for example, selects an option (e.g., with contact 603) to stop editing the pinned interaction.

[0217] As shown in FIG. 6PP, in response to the user's selection of FIG. 6OO, electronic device 500 optionally ceases displaying the user interface for editing the pinned conversations and displays a messaging user interface with the pinned conversations arranged according to the changes made by the user of FIGS. 66MM-6OO.

[0218] In some embodiments, the messaging user interface is scrollable, including scrolling through pinned interactions. In FIG. 6PP, the user swipes (e.g., with contact 603 detected in an unpinned or pinned area, but not remaining fixed for the predetermined time threshold previously described) to, for example, scroll the user interface downwards. As shown in FIG. 6QQ, in some embodiments, in response to an input to scroll the user interface, the electronic device 500 scrolls the user interface, including scrolling through the representations 606 of the pinned interactions (e.g., off-touch screen 504). In some embodiments, it is possible to scroll the user interface downwards such that the representations 606 of the pinned interactions are no longer displayed (e.g., if one scrolls completely off of the touch screen 504). However, in some embodiments, the representations 606 of the pinned interactions are fixed in place in the user interface, such that scrolling only scrolls through the representations 616 of the unpinned interactions while the representations 606 of the pinned interactions remain displayed.

[0219] 6RR-6SS show another example of electronic device 500 updating a representation 606e of a group interaction in response to receiving notifications 624rr and 624ss of an incoming message for the interaction. In some embodiments, electronic device 500 displays an image associated with the user who sent the most recent message in the periphery of representation 606e. In some embodiments, electronic device 500 moves a representation of a user from the periphery of representation 606e to the interior of representation 606e in response to receiving another message in the messaging interaction from a different user, even if the user of electronic device 500 does not read the messaging interaction between receipt of the message.

[0220] 6RR, in response to receiving an indication 624rr of a message of the interaction associated with the representation 606e, the electronic device 500 displays a representation 630d of the user who sent the message in the vicinity of the representation 606e of the messaging interaction. In some embodiments, the electronic device 500 also displays an indication 626e of the contents of the message in a manner similar to that described above.

[0221] As shown in FIG. 6SS, in response to receiving an indication 624ss of a subsequent message of the interaction associated with the representation 606e, the electronic device 500 displays a representation 630f of the user who sent the subsequent message at the periphery of the representation 606e of the messaging interaction. In some embodiments, as shown in FIG. 6SS, the electronic device 500 also moves a representation 630d of the user who sent the message received in FIG. 6RR to the inside of the indication 606e and ceases to display an indication 626e of the contents of the message received in FIG. 6RR in response to the indication 624ss, even if the user has not viewed the messaging interaction between receiving the indications 624rr and 624ss. As shown in FIG. 6SS, the representation 630f is displayed, for example, at a larger size than the representation 630d. In some embodiments, the electronic device 500 also displays an indication 626h of the contents of the message associated with the indication 624ss.

[0222] 7 is a flow diagram illustrating a method 700 for presenting a representation of a messaging conversation, according to an embodiment of the present disclosure. Method 700 is optionally performed on an electronic device, such as device 100, device 300, or device 500, as described above with reference to FIGS. 1A-1B, 2-3, 4A-4B, and 5A-5H. Some operations in method 700 are optionally combined and / or the order of some operations is optionally changed.

[0223] As described below, method 700 provides a way for an electronic device to present a representation of a messaging interaction. This method reduces the cognitive burden on a user when interacting with a user interface of a device of the present disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, improving the efficiency of user interaction with the user interface conserves power and increases the time between battery charges.

[0224] In some embodiments, the method 700 is performed by an electronic device in communication with a display generation component and one or more input devices (e.g., a mobile device (e.g., tablet, smartphone, media player), a computer (e.g., desktop computer, laptop computer), or a wearable device (e.g., watch, head mounted device). In some embodiments, the display generation component is a display integrated with the electronic device (optionally a touch screen display) and / or an external display such as a monitor, projector, television, etc. In some embodiments, the electronic device 500, via the display generation component, displays (702) a user interface including (1) a first visual representation 606a associated with the first messaging interaction and (2) a second visual representation 606b associated with the second messaging interaction, such as in FIG. 6C . In some embodiments, the first visual representation 606a is displayed in a first location in a user interface (704), such as in FIG. 6C . In some embodiments, the second visual representation 606b is displayed in a second location in a user interface (704), such as in FIG. Representation 606b is displayed in a second location of the user interface (706), such as in FIG. 6C. In some embodiments, such as in FIG. 6C, the second location is different from the first location (708). In some embodiments, each respective visual representation associated with a respective messaging interaction optionally includes a representation of one or more contacts included in the messaging interaction. For example, each visual representation includes an image associated with a contact card of one or more contacts in the interaction and / or an image associated with the interaction. In some embodiments, the user interface includes multiple representations of "pinned" interactions in a respective region of the user interface (e.g., the top of the user interface) and multiple representations of "unpinned" interactions. The representations of the pinned interactions optionally have a different design, format, etc. than the representations of the unpinned interactions. In some embodiments, the representations of the pinned interactions are arranged in a grid, each showing an image representing one or more participants of the interaction and text indicating the name of a contact in the messaging interaction or a name associated with a group interaction.A representation of an unpinned interaction optionally includes all elements of a representation of a pinned interaction, and optionally further includes a timestamp of the interaction's last messaging activity and a notification of the interaction's last messaging activity, regardless of whether a user of the electronic device has the interaction open since the last activity was received (e.g., whether the last activity was "read" or not). In some embodiments, a representation of a pinned interaction only includes notifications of messaging activity received from a user viewing the messaging interaction (e.g., a representation of a pinned interaction only includes notifications of unread messaging activity). In some embodiments, messaging activity includes sending a message in the interaction and / or adding tags to existing messages (e.g., reactions such as "like", "love", "dislike", laugh, highlight, or question mark), and / or making changes to the members of a group (e.g., adding or removing a contact from the interaction) and / or making changes to the interaction's name.

[0225] 6D , while displaying the first visual representation 606c in a first location in the user interface (e.g., without moving the first visual representation) (710), the electronic device 500 receives an indication 624d of a first messaging activity associated with the first messaging conversation (712). In some embodiments, the messaging activity includes sending a message in the conversation and / or adding a tag to an existing message (e.g., a reaction such as "like," "love," "dislike," laugh, highlight, or question mark), and / or making a change to the members of a group (e.g., adding or removing a contact from the conversation) and / or making a change to the name of the conversation.

[0226] In some embodiments, such as FIG. 6D , in response to receiving the indication 624d of the first messaging activity, the electronic device 500 updates (714) the first visual representation 606a to include a visual indication 626a of the first messaging activity, where the visual indication 626a of the first messaging activity is displayed in a first visual characteristic. In some embodiments, the first messaging interaction is a pinned interaction, where the visual indication of the first messaging activity is displayed superimposed on the visual representation of the first messaging interaction. The first messaging activity optionally receives a message of the first messaging interaction, where the visual indication of the message includes some or all of the text of the message. In some embodiments, the visual indication of the message is initially displayed in a first size.

[0227] In some embodiments, such as in FIG. 6F, the electronic device 500 receives (716) a notification of a second messaging activity associated with the second messaging conversation. In some embodiments, the messaging activity includes sending a message in the conversation and / or adding a tag to an existing message (e.g., a reaction such as "like," "love," "dislike," laugh, highlight, or question mark), and / or making a change to the members of the group (e.g., adding or removing a contact from the conversation) and / or making a change to the name of the conversation. In some embodiments, the second messaging conversation is a different conversation from the first messaging conversation, and both the first and second messaging conversations are "pinned" to their respective regions of the user interface.

[0228] In some embodiments, such as in FIG. 6F , in response to receiving the indication 624f of the second messaging activity, the electronic device 500 updates (718) the visual indication 626a of the first messaging activity to be displayed with a second visual characteristic different from the first visual characteristic. In some embodiments, modifying the visual characteristic of the visual indication of the first messaging activity in the first messaging interaction includes reducing a size of the visual indication, modifying a color scheme of the visual indication (e.g., from being displayed in color to being displayed in black and white or grayscale), modifying a translucency of the visual indication, etc. In some embodiments, in response to receiving a notification of the second messaging activity associated with the second messaging interaction, the electronic device displays, via a display generation component, the visual indication of the second messaging activity relative to a second visual representation associated with the second messaging interaction.

[0229] The above method of updating the display to display a visual indication of the first messaging activity having a visual characteristic having a second value different from the first value in response to receiving a notification of the second messaging activity enables the electronic device to continue to display the notification of the first messaging activity in a manner that efficiently communicates that because the first messaging activity was received, other messaging activities have been received, which simplifies the interaction between a user and the electronic device, enhances the operability of the electronic device, makes the user device interface more efficient (e.g., by allowing a user to determine the recency of the first messaging activity without entering input that requests more information about the first messaging activity or the second messaging activity), and which further reduces power usage and improves battery life of the electronic device by enabling a user to use the electronic device more quickly and efficiently.

[0230] In some embodiments, such as FIG. 6F, after the visual indication 626a is updated to be displayed with the second visual characteristic, the first visual representation 606a is still displayed in the first location. In some embodiments, the locations of the first visual representation associated with the first messaging interaction and the second visual representation associated with the second messaging interaction are displayed in a fixed location of the user interface. Updating the first visual indication displayed with the second visual characteristic optionally includes one of updating a size, color, or translucency of the visual representation of the first messaging interaction without changing the location of the first visual representation. In some embodiments, in response to receiving a notification of a subsequent messaging activity of the first messaging interaction, the electronic device displays a visual notification of the subsequent messaging activity and changes the location of the visual indication of the first messaging activity within the representation of the first messaging interaction, but does not change the location of the visual representation of the first messaging interaction itself. The above method of maintaining the location of the first visual representation upon updating visual characteristics of the visual indication allows the electronic device to provide an efficient manner of displaying the first visual representation, which simplifies the interaction between a user and the electronic device, enhances the operability of the electronic device, and makes the user device interface more efficient (e.g., by reducing the time and number of inputs required to position the first visual representation and access the first messaging interaction), which further reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0231] In some embodiments, the second visual representation continues to be displayed in a second location of the user interface in response to receiving a notification of the first messaging activity and in response to receiving a notification of the second messaging activity. For example, the user interface location of the second visual representation does not change in response to receiving a notification of messaging activity in the second interaction or any other interaction. In some embodiments, the representations of the first messaging interaction and the second messaging interaction are displayed in a "pinned interactions" area of ​​the user interface. Optionally, the location of each respective representation of the pinned interaction does not change when messaging activity is detected. In some embodiments, the messaging user interface further includes representations of additional messaging interactions that are not pinned. Optionally, the representations of the additional messaging interactions are displayed in reverse chronological order of the interactions' most recent messaging activity. For example, when a notification of messaging activity associated with each unpinned interaction is detected, the electronic device updates the location of the representation of the unpinned messaging interaction so that the representation of the respective interaction is displayed with highest priority in the user interface (e.g., at the top of the column of representations of messaging interactions).

[0232] In some embodiments, such as in FIG. 6H , the user interface further includes a third visual representation 616f associated with the third messaging conversation. In some embodiments, while displaying the first, second, and third visual representations 606a-b and 616f in the user interface, the electronic device 500 receives an indication 624h of a third messaging activity associated with the third messaging conversation (e.g., a new message (e.g., including text and / or media, such as images, audio, etc.) is added to the conversation and / or a tag is added to an existing message in the conversation). In some embodiments, such as in FIG. 6H , in response to receiving the indication 624h of the third messaging activity, the electronic device 500 updates the position of the third visual representation 616f in the user interface without updating the first location of the first visual representation 606a and the second location of the second visual representation 606b in accordance with a determination that one or more criteria have been met (e.g., not at the top of a list of messages that are not already pinned). In some embodiments, prior to receiving the notification of the third messaging activity, the most recently received messaging activity among the unpinned interactions was associated with a different messaging interaction. Optionally, prior to receiving the notification of the third messaging activity, a representation of the different messaging interaction is displayed in a highest priority area of ​​unpinned messaging interactions of the user interface. In some embodiments, in response to receiving the indication of the third messaging activity, the electronic device displays a representation of the third messaging interaction in a highest priority area of ​​unpinned messaging interactions and moves the remaining representations of the unpinned messaging interactions down in priority. For example, prior to receiving the notification of the third messaging activity, a representation of the fourth messaging interaction is displayed at the top of the unpinned message area of ​​the user interface along with representations of the other messaging interactions displayed below.In this example, in response to receiving the notification of the third messaging activity, the electronic device displays a representation of the third interaction at the top of an unpinned message area of ​​the user interface and moves the representations of the other unpinned interactions downward. In some embodiments, pursuant to a determination that one or more criteria are not met, the electronic device does not update the location of the third visual representation. For example, if the most recently received messaging activity between the unpinned interactions was in the third interaction prior to receiving the third messaging activity, the electronic device optionally displays the third visual representation at the top of the unpinned interaction area of ​​the user interface and continues to display the third visual representation in that location in response to receiving the indication of the third messaging activity.) In some embodiments, in response to receiving the notification of the third messaging activity, the electronic device updates the third visual representation to indicate the third messaging activity without updating the first visual representation and the second visual representation. In some embodiments, updating the third visual representation includes displaying the notification of the third messaging activity, such as by updating the visual representation to include a visual representation of the received messaging activity. For example, if the third messaging activity is a text message, the third visual representation is updated to include an indication of the sender of the text message and at least a portion of the text of the message. In some embodiments, in response to receiving a messaging activity associated with a non-pinned interaction, the representation of the pinned interaction is not changed. In some embodiments, the third visual representation is updated regardless of whether one or more criteria are met.The above method of updating the third visual representation to indicate the third messaging activity without updating the first visual representation and the second visual representation allows the electronic device to efficiently communicate to a user that no further messaging activity has been received in the first or second messaging interactions, which simplifies the interaction between the user and the electronic device, enhances the operability of the electronic device, and makes the user device interface more efficient (e.g., by reducing the time it takes for a user to determine which interaction has received recent messaging activity), which further reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0233] In some embodiments, such as FIG. 6I, the user interface further includes a third visual representation 606c associated with a third messaging conversation, and a visual indication 626c of a second messaging activity is displayed with a third visual characteristic (e.g., size, color, translucency, etc.). In some embodiments, such as FIG. 6I, while displaying the first, second, and third visual representations 606a - c on the user interface, an indication 624i of a third messaging activity associated with the third messaging conversation is received (e.g., receiving a new message of the third messaging conversation or a new tag added to an existing message of the third messaging conversation). In some embodiments, such as FIG. 6I, in response to receiving an indication of the third messaging activity, according to a determination that one or more criteria are met (e.g., the third messaging conversation is a "pinned" conversation), the electronic device 500 updates the visual indication of the first messaging activity 626d, displays it with a fourth visual characteristic different from the second visual characteristic, and updates the visual indication 626c of the second messaging activity to have a fifth visual characteristic different from the third visual characteristic. In some embodiments, the respective locations of the first, second, and third representations of each messaging conversation are the same after receiving a notification of the third messaging activity and before the notification of the third messaging activity is received as the respective locations of the first, second, and third representations of each messaging conversation. The electronic device optionally displays the visual indication of the most recently received messaging activity with the largest size compared to other visual indications of other messaging activities, and when a new notification of a new messaging activity is received, the electronic device reduces the size of the visual indication of the previously received messaging activity. In some embodiments, the electronic device displays only the visual indication of the messaging activity of the pinned conversation while the messaging activity has not been read by the user.In some embodiments, once the user has the respective messaging activity (e.g., by selecting the representation of the messaging interaction in which the messaging activity was received to view the messaging interaction after the messaging activity was received), the electronic device ceases to display the visual indication of the messaging activity along with the representation of the messaging activity. The above method of updating the visual characteristics of the first and second visual indications of the respective messaging activities allows the electronic device to efficiently communicate the order in which the messaging activities were received across different interactions, which simplifies the interaction between the user and the electronic device, enhances the operability of the electronic device, makes the user device interface more efficient (e.g., by reducing the inputs required to view all notifications of the messaging activity with notifications of the order in which the messaging activities were received), which further reduces the power usage of the electronic device and improves battery life by allowing the user to use the electronic device more quickly and efficiently.

[0234] In some embodiments, such as in FIG. 6I , while displaying the first visual representation 606a including a visual indication of the first messaging activity, includes receiving input via one or more input devices (e.g., via contact 603) to display the first messaging activity within the first messaging conversation. In some embodiments, the electronic device detects a selection of the first visual representation. In some embodiments, displaying the first messaging activity within the first messaging conversation includes displaying an additional message included in the messaging conversation. In some embodiments, in response to receiving an input to display the first messaging activity within a first messaging conversation, such as in FIG. 6I , the electronic device 500 displays, via the display generation component, the first messaging conversation including the first messaging activity (e.g., a representation of other messaging activities in the first messaging conversation, and a representation of the first messaging activity). In some embodiments, such as in FIG. 6K , after displaying the content of the first messaging conversation including the first messaging activity, the electronic device displays, via the display generation component, a first visual representation 606a associated with the first messaging conversation and a representation of the second messaging activity. and a second visual representation 606b associated with the interaction, where the first visual representation 606b does not include the visual indication of the first messaging activity 626b as in FIG. 6I. For example, removing the visual indication of the first messaging activity from the first visual representation. In some embodiments, the first visual representation is not displayed while the electronic device displays content of the first messaging interaction. The electronic device optionally displays the first visual representation in response to receiving an input corresponding to a request to navigate within the user interface to a user interface including a representation of the messaging interaction including the first visual representation without the visual indication of the first messaging activity.In some embodiments, the electronic device displays a visual representation of the pinned interactions that includes a visual indication of messaging activity received since the last time the user viewed the content of the respective pinned interaction. The electronic device optionally stops displaying the visual indication of messaging activity in the visual representation of the pinned interaction in response to detecting that the user has viewed the content of the respective pinned messaging interaction since the messaging activity was received. In some embodiments, the representation of a non-pinned interaction always includes a visual indication of the most recent messaging activity, regardless of whether the user has viewed the content of the messaging interaction since the most recent messaging activity was received. In some embodiments, the electronic device displays a representation of a non-pinned interaction that includes a visual indication of the most recently received messaging activity in the interaction, even if the most recent messaging activity was generated by a user account associated with the electronic device. The electronic device optionally does not display an indication of messaging activity generated by a user account of the electronic device with the visual representation of the pinned interaction. The method of removing a visual indication of a first messaging activity in response to an input to display content of the first messaging conversation enables an electronic device to efficiently indicate to a user whether there is unread messaging activity associated with the first messaging conversation, which simplifies the interaction between the user and the electronic device, enhances the operability of the electronic device, makes the user device interface more efficient (e.g., by reducing the time and number of inputs required by the user to determine whether new messaging activity associated with the first messaging conversation has been received), and additionally reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0235] In some embodiments, such as in Figure 6C, the user interface further includes a third visual representation 616a associated with the third messaging interaction. In some embodiments, such as in Figure 6C, the first and second locations are in a first region of the user interface (e.g., a pinned interaction region of the user interface). In some embodiments, such as in Figure 6C, the third location is in a second region of the user interface (e.g., an unpinned interaction region of the user interface), and the second region is displayed at a lower priority (e.g., below) than the first region in the user interface. In some embodiments, such as in FIG. 6C , the first respective visual representations of the first respective messaging interactions, including the third visual representation 616a of the third messaging interaction, are displayed in the second region of the user interface in an order based on recency of messaging activity in the first respective messaging interaction (e.g., in response to receiving new messaging activity in one of the respective messaging interactions, the priority at which the respective visual representations of the respective messaging interactions are displayed is updated to display the respective messaging interaction for which new messaging activity was received with the highest priority). The electronic device optionally displays the first respective visual representations of the first respective messaging interactions in the topmost region of the user interface. and displaying the representations of the messaging interactions in the second region having the most recent activity in the first region and displaying the remaining representations of the messaging interactions displayed in order from most recent to oldest activity. In some embodiments, the second respective visual representations of the second respective messaging interactions, including the first visual representation 606c of the first messaging interaction and the second visual representation 606b of the second messaging interaction, are displayed in the first region of the user interface in an order that is not based on the recency of messaging activity in the second respective messaging interaction. In some embodiments, the visual representations of the interactions in the first region of the user interface are arranged according to a user-defined order.In some embodiments, the visual representations of the interactions in the second region of the user interface are displayed in an order in which messaging interactions with more recent activity are displayed with a higher priority than messaging interactions with older activity (e.g., the representations are arranged in reverse chronological order). The above method of displaying the representations of interactions in different regions based on different orders enables the electronic device to provide efficient access to specific interactions, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device and making the user device interface more efficient (e.g., by reducing the number of inputs required to view the content of a pinned interaction). This additionally reduces the power usage and improves the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0236] In some embodiments, such as FIG. 6K, the user interface further includes a third visual representation 616c associated with the third messaging interaction, the third visual representation 616c being displayed in a third location within the user interface. In some embodiments, such as FIG. 6K, the first and second locations are within a first region of the user interface (e.g., a pinned interaction region of the user interface). In some embodiments, such as FIG. 6K, the third location is within a second region of the user interface (e.g., an unpinned interaction region of the user interface). In some embodiments, while displaying the third visual representation 616c of the third messaging interaction in the second region of the user interface, the electronic device 500 receives input via one or more input devices (e.g., with contact 603) corresponding to a request to move the third visual representation from the second region to the first region. In some embodiments, the electronic device detects the selection and movement of the third visual representation from the second region to the first region (e.g., the electronic device detects the user “dragging” the third representation from the second region to the first region). In some embodiments, in response to receiving an input corresponding to a request to move the third visual representation 616c from the second region to the first region, the electronic device moves the third representation from the second region to a third location within the first region, as in FIG. 6K, where the third location is different from the first location and the second location, and the third location does not change in response to detecting messaging activity at the electronic device, such as in FIG. 6M. In some embodiments, in response to detecting the movement of the third visual representation to the first region, the electronic device displays the third visual representation at the end of the group of pinned interactions. In some embodiments, in response to detecting the movement of the third visual representation to the first region, the electronic device displays the third visual representation at a location selected by the user (e.g., defined by the location to which the user drags the third representation). While the first, second, and third visual representations are displayed within the first region, positions of the first, second, and third visual representations remain unchanged in response to detected receipt of new messaging activity.The above method of moving the third representation to the first region in response to an input enables the electronic device to provide an efficient method of adding interactions to pinned interaction regions, simplifying the interaction between a user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to add interactions to pinned interaction regions), which additionally reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0237] In some embodiments, such as in FIG. 6M , the first and second locations are within a first region of the user interface (e.g., a pinned interactive region of the user interface). In some embodiments, such as in FIG. 6M , the user interface includes a second region of the user interface (e.g., an unpinned interactive region of the user interface). In some embodiments, such as in FIG. 6M , while displaying the first visual representation 606a within the first region of the user interface, the electronic device 500 receives input via one or more input devices corresponding to a request to move the first visual representation from the first region to the second region. In some embodiments, the electronic device detects a selection of the first visual representation and a movement from the first region to the second region (e.g., the electronic device detects a user “dragging” the first representation from the first region to the second region). In some embodiments, in response to receiving an input corresponding to a request to move the first visual representation 606a from the first region to the second region, as in FIG. 6M, the electronic device 500 moves the first representation from the first region to a third location in the second region, the third location being based on the recency of messaging activity in the first messaging interaction relative to other messaging interactions having visual representations displayed in the second region of the user interface, such as in FIG. 6N. In some embodiments, in response to detecting the movement of the first representation to the second region, the electronic device displays the first visual representation within the representations of the other non-pinned interactions according to a reverse chronological order of the order in which messaging activity was received in each non-pinned interaction independent of the location in the user interface where the input moving the first visual representation ends (e.g., the location where the user "drops" the first visual representation in the second region). In response to receiving a messaging activity associated with a non-pinned interaction, the electronic device optionally updates the order in which the representations of the messaging interactions are displayed.The above method of moving the third representation to the second region in response to an input enables the electronic device to provide an efficient method of removing interactions from a pinned interaction region, simplifying the interaction between a user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to remove interactions from a pinned interaction region), which additionally reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0238] In some embodiments, such as FIG. 6E, the visual indication of the first messaging activity includes respective indications 626b for each of the first to receive one or more input characters without another device associated with the first messaging conversation receiving a request to send one or more characters to the first messaging conversation. For example, each user other than the user of the electronic device included in the first messaging conversation is currently providing input to the first messaging conversation. In some embodiments, each respective indication of the first does not indicate the type of input (e.g., voice input, typing, etc.) or messaging activity (e.g., text message vs. tag vs. image, etc.) being provided to the first messaging conversation by each user. The electronic device optionally displays the same typing indicator regardless of the type of input provided by the user or the type of message. For example, the typing indicator is shown in response to detecting that the user is entering text with a soft keyboard. As another example, the typing indicator is shown in response to detecting an indication that the user is selecting an image for transmission in the messaging conversation within the message. In some embodiments, in response to detecting that each user has stopped providing input to the first messaging conversation, the electronic device stops displaying the visual indication. For example, in response to detecting an indication that each user is typing a message to be sent to the first messaging conversation, the electronic device displays the visual indication. By the above method of displaying a visual indication of the user providing input to the first messaging conversation, the electronic device can efficiently indicate that the user is providing input without receiving an input requesting to view the content of the messaging conversation, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to view the indication).Additionally, it reduces power usage and improves battery life of electronic devices by allowing users to use the electronic devices more quickly and efficiently.

[0239] In some embodiments, as in FIG. 6F, in response to an indication that another device associated with the first messaging dialogue has received a request to send one or more characters to the first messaging dialogue (e.g., the end of an input to the first messaging dialogue provided by the respective user, such as an input to send a message configured to the messaging dialogue), the first respective instruction 626b as in FIG. 6E is replaced with a second respective instruction 636c as in FIG. 6F to indicate a type of messaging activity (e.g., optional content) provided by the respective user to the first messaging dialogue. In some embodiments, possible types of messaging activities include sending text to the dialogue, sending an image to the dialogue, sending audio to the dialogue, or adding a tag (e.g., a like tag, a dislike tag, etc.) to an existing message in the dialogue. For example, if the messaging content includes adding a tag to an existing message in the dialogue, the second respective instruction is an image corresponding to the tag. As another example, if the messaging content includes a message including text, the second respective instruction includes at least a portion of the text of the message. In some embodiments, if the respective user stops providing input to the messaging dialogue without sending a messaging activity, the first respective indication ceases to be displayed without displaying the second respective indication. The above method of replacing the first respective indication with the second respective indication indicating the type of messaging activity allows the electronic device to provide an efficient way of viewing the type of messaging content added to the dialogue, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to view the type of messaging activity added to the dialogue). In addition, reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0240] In some embodiments, the visual indication 626c of the first messaging activity includes at least a portion of a most recent unread message in the first messaging dialogue, such as FIG. 6F. In some embodiments, if the most recent unread message in the messaging dialogue has a length less than a threshold, the entire content of the message is displayed. In some embodiments, if the most recent unread message in the messaging dialogue has a length greater than a threshold, a portion of the message is displayed. The electronic device optionally does not display a visual indication of the messaging activity read in the first messaging dialogue. The above method of including at least a portion of a most recent unread message allows the electronic device to efficiently provide the content of the messaging activity without receiving an input to view the content of the messaging dialogue, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to view a portion of the messaging activity). In addition, by allowing the user to use the electronic device more quickly and efficiently, it reduces the power usage of the electronic device and improves battery life.

[0241] In some embodiments, such as FIG. 6U, while displaying the first visual representation 606e including the visual indication 626e of the first messaging activity (e.g., before displaying the content of the first messaging conversation including the first messaging activity), the electronic device 500 receives an indication 624u of a third messaging activity associated with the first messaging conversation. In some embodiments, such as FIG. 6U, in response to receiving the indication 624u of the third messaging activity associated with the first messaging conversation, the electronic device updates the first visual representation 626e to simultaneously include the visual indication 626e of the first messaging activity and the visual indication 626f of the third messaging activity. In some embodiments, the electronic device displays visual indications of two or more unread messaging activities received in a pinned conversation. In some embodiments, there is a limit to the number of indications of unread messaging activities in a single conversation that the electronic device displays. In response to detecting that the user has viewed the content of the first messaging conversation, the electronic device optionally ceases displaying the indications of the first and third messaging activities as part of the visual representation of the first messaging conversation. The above method of simultaneously displaying visual indications of the first and third messaging activities allows the electronic device to display indications of multiple messaging activities added to the first messaging conversation without receiving input presenting the content of the first messaging conversation, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to determine that a conversation has multiple unread messages). In addition, reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0242] In some embodiments, as in FIG. 6U, a size of the visual indication of the first messaging activity is based on the recency of the first messaging activity, and a size of the visual indication of the third messaging activity is based on the recency of the third messaging activity. In some embodiments, the more recent the messaging activity, the larger the indication of the messaging activity. In response to receiving an indication of the third messaging activity while displaying the visual indication of the first messaging activity, the electronic device optionally displays the indication of the first messaging activity in a smaller size than the indication of the third messaging activity. In some embodiments, in response to receiving an indication of a fourth messaging activity associated with the second interaction, the electronic device optionally reduces a size of the visual indications of the first and third messaging activities. In some embodiments, in response to receiving an indication of a fourth messaging activity associated with the second interaction, the electronic device optionally does not update a size of the visual indications of the first and third messaging activities. The above method of displaying visual indications with sizes based on the recency of messaging activities allows an electronic device to efficiently communicate the order in which messaging activities were received, thereby simplifying the interaction between a user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to see the order in which messaging activities were received). In addition, it reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0243] In some embodiments, such as FIG. 6T, prior to receiving the indication of the third messaging activity, the visual indication 626e of the first messaging activity has a first size. In some embodiments, such as FIG. 6U, after receiving the indication 624u of the third messaging activity, the visual indication 626e of the first messaging activity has a second size that is smaller than the first size (e.g., the visual indication of the third messaging activity has a third size that is larger than the second size). In some embodiments, in response to detecting receipt of the new messaging activity, the electronic device reduces a size of the indication of the other messaging activity associated with the same (or different) interaction and displays the indication of the new messaging activity in a size larger than the size of the representation of the other messaging activity. In some embodiments, rather than reducing the size of the visual indication of the first messaging activity, the electronic device stops displaying the visual indication of the first messaging activity in response to receiving the indication of the third messaging activity. The above method of reducing the size of the visual indication of the first messaging activity in response to receiving an indication of the third messaging activity allows the electronic device to efficiently indicate the order in which the messaging activities were received, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to see the order in which the messaging activities were received). In addition, reducing the power usage and improving the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0244] In some embodiments, prior to receiving the indication of the third messaging activity, the visual indication of the first messaging activity is at a first respective location within the first visual representation. In some embodiments, after receiving the indication of the third messaging activity, the visual indication of the first messaging activity has a second respective location within the first visual representation that is different from the first respective location, and the visual indication of the third messaging activity has a third respective location within the first visual representation that is different from the second respective location. In some embodiments, the location of the visual representation of the messaging activity in the pinned conversation changes as additional messaging activities in the pinned conversation are received. In some embodiments, the location is predefined based on the number of indications displayed in one visual representation and the order in which the messaging activities corresponding to the indications are received. In some embodiments, the location is random. The above method of changing the position of the visual indication of the first messaging activity in response to receiving an indication of the third messaging activity allows the electronic device to display the indication of the messaging activity in a non-overlapping position for easy viewing by the user, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by allowing the user to see the indication, reducing the need for the user to provide input to view the content of the messaging dialogue in order to view the indication of the messaging activity). In addition, reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0245] In some embodiments, the size of the visual indication of the messaging activity is within a range set by a lower size threshold and an upper size threshold. In some embodiments, the electronic device displays a maximum of two lines of text when displaying the visual indication of the text messaging activity in a pinned interaction. The electronic device optionally displays an indication in a portion of the message at the beginning of the message that the message has additional content if the message exceeds the maximum visual indication size.

[0246] In some embodiments, while displaying the multiple visual indications of the messaging activity in each visual representation of each pinned messaging interaction, the electronic device displays the visual indications of the messaging activity at different vertical positions within the user interface.

[0247] In some embodiments, such as FIG. 6D, in response to receiving the indication 624d of the first messaging activity, the electronic device 500 updates the user interface to include a visual indication 620a associated with the first visual representation indicating the presence of unseen messaging activity in the first messaging conversation. In some embodiments, in addition to displaying the visual indication of the messaging activity, in response to detecting receipt of a new messaging activity in the pinned conversation, the electronic device displays a visual indication that a new messaging activity has been added to the conversation since the user viewed the contents of the messaging conversation. The visual indication is optionally the same regardless of the type, content, or number of unread messaging activities associated with the pinned conversation. In some embodiments, the visual indication displayed in association with the first visual representation is displayed in a position that does not overlap with the visual representation of the conversation. In some embodiments, the respective visual indication of the respective messaging activity is displayed superimposed on the visual representation of the conversation. The above method of displaying a visual representation indicating the presence of unseen messaging activity allows the electronic device to efficiently indicate that the messaging conversation includes unseen activity. This simplifies the interaction between the user and the electronic device, enhances the operability of the electronic device, and makes the user device interface more efficient (e.g., by reducing the number of inputs required to determine that an unseen messaging activity exists, such as by eliminating the need for a user to view the contents of a messaging dialogue to determine if new messaging activity has been added to the dialogue), and additionally reduces power usage and improves battery life of the electronic device by allowing a user to use the electronic device more quickly and efficiently.

[0248] In some embodiments, following a determination that one or more criteria are met (e.g., that the electronic device has not set a pinned interaction feature for the messaging activity), the electronic device optionally configures a pinned interaction feature of the messaging application, which includes automatically selecting one or more “pinned” interactions based on one or more criteria (e.g., the recency of the messaging activity in the interaction, how frequently messaging activity is received within the interaction, how recently the messaging interaction was initiated, whether one or more participants in the messaging interaction are on a favorite contacts list).

[0249] In some embodiments, in a pinned interaction configuration user interface, the electronic device displays representations of multiple pinned interactions each associated with a selectable option that, when selected, removes the respective interaction from the pinned interaction area, and the electronic device displays representations of additional messaging interactions that are not yet pinned with selectable options that, when selected, cause the electronic device to add the respective interaction to the pinned interactions.

[0250] In some embodiments, while displaying an indication of the automatically selected pinned interaction, the electronic device receives an input confirming that the interaction should be pinned. In response to the input, the electronic device optionally displays a messaging user interface with a representation of the automatically selected pinned interaction displayed in a pinned interaction area of ​​the user interface and representations of other messaging interactions in an unpinned interaction user interface.

[0251] In some embodiments, while displaying an indication of the automatically selected pinned interaction, the electronic device receives an input denying that the interaction should be pinned. In response to the input, the electronic device optionally displays a messaging user interface with a representation of the automatically selected pinned interaction displayed in an unpinned interaction area of ​​the user interface.

[0252] In some embodiments, while displaying a message user interface, the electronic device detects an input corresponding to a request to edit a selection of which interactions are pinned interactions. In response to the input, the electronic device displays representations of the pinned interactions in a first region each associated with a selectable option that, when selected, removes the respective interactions from the pinned interaction region and places them in the unpinned interaction region. The electronic device displays representations of additional messaging interactions in the unpinned interaction region with selectable options that, when selected, cause the electronic device to add the respective interactions to the pinned interaction region.

[0253] In some embodiments, for example, as in FIG. 6I, the first messaging interaction is a group messaging interaction (e.g., includes three or more participating electronic devices, including the electronic device), and the first messaging activity is provided to the first messaging interaction by a first respective contact in the first messaging interaction. Updating the first visual representation 606c in response to receiving an indication of the first messaging activity includes updating the first visual representation 606c to include a visual representation of the first respective contact displayed in association with the visual indication 622e of the first messaging activity. In some embodiments, the first visual representation includes a representation of a plurality of contacts participating in the first messaging interaction, and in response to the indication of the first messaging activity, the representation of the first respective contact is displayed at an updated position within the first representation of the first messaging interaction. The electronic device optionally displays the representation of the first respective contact and a visual indication of the first message at an edge of the representation of the first messaging interaction. In some embodiments, the visual representation of the first messaging interaction includes an image associated with the messaging interaction that does not include an image associated with a contact included in the messaging interaction. Optionally, in response to receiving an indication of the first messaging activity, the electronic device updates the first visual representation to include an image associated with the first respective contact displayed in proximity to the visual indication of the first message. The above method of updating the first visual representation to include a visual representation of the first respective contact displayed in association with the visual indication of the first messaging activity enables the electronic device to communicate which user in the group interaction sent the first messaging activity, thereby simplifying interaction between the user and the electronic device, enhancing operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to determine who sent the first messaging activity).Additionally, it reduces power usage and improves battery life of electronic devices by allowing users to use the electronic devices more quickly and efficiently.

[0254] In some embodiments, the first messaging interaction is a group messaging interaction (e.g., includes three or more participating electronic devices, including the electronic device), e.g., as in FIG. 6T. In some embodiments, the first messaging activity is provided to the first messaging interaction by a first respective contact in the first messaging interaction, e.g., as in FIG. 6T. In some embodiments, such as in FIG. 6T, the first visual representation 606e includes a first region configured to include one or more representations 630e-f of each contact included in the first messaging interaction that does not have a messaging activity visible at the electronic device. In some embodiments, instead of displaying one or more representations of each contact included in the first messaging interaction that does not have a messaging activity visible at the electronic device, the first visual representation includes an image associated with the group interaction that is different from the image associated with the one or more contacts included in the messaging interaction. The representation of each contact optionally includes an image associated with a contact card of the one or more contacts. In some embodiments, the first region of the first visual representation is optionally within a visual indication of an outline of the region, such as a circle. In some embodiments, such as in FIG. 6T, the first visual representation 606e includes a second region distinct from the first region, the second region configured to include one or more representations 630d of respective contacts included in the first messaging conversation that have messaging activity that is not visible at the electronic device. In some embodiments, in response to receiving a new messaging activity at the electronic device and before the user views the messaging activity within the content of the messaging conversation, the electronic device displays a visual representation of one or more contacts that sent the new messaging activity. The second region is optionally on the periphery of a visual outline of the region (e.g., a circle surrounding a visual representation of one or more users that do not have a messaging activity that is not visible, or a circle surrounding a visual indication of the messaging activity that is distinct from one or more images associated with the contacts included in the messaging conversation).In some embodiments, such as FIG. 6T, updating the first visual representation 606e in response to receiving an indication 624t of the first messaging activity includes moving a visual representation 630d of the first respective contact from a first region in the first visual representation to a second region. For example, the electronic device displays a plurality of representations of contacts in the messaging interaction within a circle that is part of the representation of the first messaging interaction after the user has viewed the content of the messaging interaction and before receiving a new messaging activity in the first interaction. In this example, in response to receiving a first messaging activity from a first user of the plurality of users, the electronic device updates the visual representation of the first messaging interaction to move a representation of the first user from within the circle to the periphery of the circle. In some embodiments, a representation of the first contact who sent the first messaging activity is displayed in proximity to the visual indication of the first messaging activity. The above method of updating the first visual representation and moving the visual representation of the first respective contact from the first area to the second area allows the electronic device to efficiently communicate which users were in the dialogue before the user sent the first messaging activity, and which user provided the first messaging activity after the first messaging activity was received. This simplifies the interaction between the user and the electronic device, enhances the operability of the electronic device, and makes the user device interface more efficient (e.g., by reducing the number of inputs required to see the users in the dialogue and the user who sent the first messaging activity). In addition, it reduces the power usage and improves the battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0255] In some embodiments, while displaying the first visual representation 606e including the visual indication 626e of the first messaging activity and the visual representation 630d of the first respective contact, as in FIG. 6T, the electronic device 500 receives an indication 624t of a third messaging activity provided to the first messaging interaction by a second respective contact different from the first respective contact, as in FIG. 6U. In some embodiments, such as in FIG. 6U, in response to receiving the third messaging activity, the electronic device reduces the size of the visual representation 630d of the first respective contact displayed within the first visual representation (e.g., in some embodiments, the size of the visual indication of the first messaging activity is also reduced in response to receiving the third messaging activity). In some embodiments, rather than reducing the size of the visual indication of the first messaging activity and the visual representation of the first respective contact, the electronic device stops displaying the visual indication of the first messaging activity and / or the visual representation of the first respective contact. In some embodiments, in addition to changing the size of the visual representation of the first respective contact and / or the visual indication of the first messaging activity, the electronic device updates the position of the visual representation of the first respective contact and / or the position of the visual indication of the first messaging activity within the visual representation of the first messaging interaction. In some embodiments, such as FIG. 6U, the electronic device 500 adds a visual representation 630e of the second respective contact to the first visual representation (e.g., the visual representation of the second respective contact is displayed at a larger size than the visual representation of the first respective contact). In some embodiments, the electronic device 500 displays a visual indication 626f of the third messaging activity within the first visual representation in association with the visual representation 630e of the second respective contact. In some embodiments, the visual indication of the third messaging activity is displayed in physical proximity to the visual representation of the second respective contact.By reducing the size of the visual representation of the first respective contact in response to receiving the third messaging activity and adding the visual representation of the second respective contact and the visual indication of the third messaging activity, the electronic device frees up space to display additional indications of the incoming messaging activity as the incoming messaging activity is received while continuing to display visual representations of the previously received messaging activity and the user who sent the previously received messaging activity, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to see the indication of the received messaging activity), as well as reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0256] In some embodiments, such as in FIG. 6S, the first messaging interaction is a group messaging interaction (e.g., includes three or more participating electronic devices, including the electronic device), and the first visual representation 606e includes a plurality of representations 630d-f of a plurality of respective contacts included in the first messaging interaction, the plurality of representations 630d-f of the plurality of respective contacts being displayed at different sizes based on the recency of the messaging activity of the respective contacts in the first messaging interaction. In some embodiments, the representation of the user who most recently sent a messaging activity to the first messaging interaction is displayed at the largest size within the representation of the first messaging interaction, and the user whose representation is displayed who most recently sent a messaging activity to the first messaging interaction is displayed at the smallest size within the representation of the first messaging interaction. In some embodiments, the electronic device displays a maximum predetermined number of representations of the contacts included in the first messaging interaction (e.g., six or seven or eight), which is the maximum number of most recently active users in the interaction. For example, if there are ten users other than the user of the electronic device involved in the messaging interaction, then the representation of the messaging interaction includes an indication of the seven users who most recently sent messaging activity to the interaction. The indication is sized based on the recency with which the users sent messaging activity to the interaction, with the representation of the user who most recently sent messaging activity to the messaging interaction being the largest and the representation size of other users being smaller as they contributed messaging activity to the interaction more recently. In some embodiments, the first visual representation of the group messaging interaction does not include a representation of the user of the current electronic device (e.g., the device on which the first visual representation is displayed) (regardless of the messaging activity of the current electronic device in the group messaging interaction).The above method of displaying representations of other contacts sized based on how recently the contacts contributed messaging activity to the interaction allows an electronic device to identify interactions based on users who have recently sent messaging activity to the interaction, thereby simplifying the interaction between the user and the electronic device, enhancing the operability of the electronic device, and making the user device interface more efficient (e.g., by reducing the number of inputs required to view a desired messaging interaction by displaying the representations of the interaction in a manner that is quickly recognizable to the user), as well as reducing power usage and improving battery life of the electronic device by allowing the user to use the electronic device more quickly and efficiently.

[0257] It should be understood that the particular order described for the operations in FIG. 7 is merely exemplary, and the order described is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other process details described herein with respect to other methods described herein (e.g., methods 900, 1100, 1300, and 1500) are also applicable in a similar manner to method 700 described above with respect to FIG. 7. For example, the method of presenting a representation of a messaging dialogue described above with reference to method 700 optionally has one or more of the characteristics described herein with reference to other methods described herein (e.g., methods 900, 1100, 1300, 1500), such as the method of creating and presenting a mention, the method of presenting an indication of a message that is a reply to another message in the dialogue, etc. For the sake of brevity, those details will not be repeated here.

[0258] The operations in the information processing method described above are optionally performed by running one or more functional modules in an information processing device, such as a general-purpose processor (e.g., as described above in connection with FIGS. 1A-1B, 3, 5A-5H) or an application specific chip. Additionally, the operations described above with reference to FIG. 7 are optionally performed by the components shown in FIGS. 1A-1B. For example, displaying operation 702 and receiving operations 712 and 716 are optionally performed by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 of event sorter 170 detects a contact on touch screen 504, and event dispatcher module 174 delivers the event information to application 136-1. Each event recognizer 180 of application 136-1 compares the event information to a respective event definition 186 to determine whether a first contact at a first location on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of that event or sub-event. The event handler 190 optionally utilizes or calls a data updater 176 or an object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes can be implemented based on the components shown in FIGS. 1A-1B. A user interface that indicates which messages are replies to other messages

[0259] Users interact with electronic devices in many different ways, including using the electronic device to display representations of messages within messaging conversations. The embodiments described below provide a way for an electronic device to present an indication of messages that are replies to other messages. Presenting an indication of messages that are replies to other messages in the manner described herein enhances interaction with the device by reducing the time and inputs required by the user to view messages in the same reply thread, thus reducing the power usage of the device and extending the battery life of battery-powered devices by reducing the time required for the user to perform an action. It is understood that people use devices. When a person uses a device, that person is optionally referred to as the user of the device.

[0260] 8A-8AA illustrate example ways in which an electronic device 500 may display representations of messages in a conversation that are replies to respective other messages in the conversation, according to some embodiments. The embodiments in these figures are used to illustrate the processes described below, including the process described with reference to FIG. 9. Although FIGS. 8A-8AA illustrate various examples of ways in which an electronic device may perform the processes described below with reference to FIG. 9, it should be understood that these examples are not intended to be limiting, and that an electronic device may perform one or more of the processes described below with reference to FIG. 9 in ways not explicitly described with reference to FIGS. 8A-8AA.

[0261] 8A illustrates an exemplary user interface including a messaging dialogue 802 between a user of electronic device 500 and two contacts named Alice and Bob. In some embodiments, electronic device 500 displays messaging dialogue 802 in response to detecting a selection of a representation of a dialogue, such as one of the representations of messaging dialogues described above with reference to FIGS. 6A-7. Messaging dialogue 802 optionally includes a representation 804a of a message from the user of electronic device 500 that is not a reply to any particular message in the dialogue, a representation 808a of a message from another user that is not a reply to any particular message in the dialogue, a representation 806a of a message from the user of electronic device 500 that is a reply to a message associated with representation 808a, and a representation 808b of another message from a user other than the user of electronic device 500 that is not a reply to a particular message in the dialogue. Representation 808a is optionally displayed with an indication 814a indicating that a message (e.g., from the user of electronic device 500) has been received in reply to the message corresponding to representation 808a. In some embodiments, the electronic device 500 does not display the indication 814a because the representation 806a of the reply is displayed in close proximity to the representation 808a of the message (e.g., immediately without other intervening messages). The representation 808a and the representation 806a are optionally connected by a line 844a indicating that the message corresponding to the representation 806a is a reply to the message corresponding to the representation 808a. As shown in FIG. 8A, in some embodiments, the line 844a connects the representation, e.g., avatar, of the contact Alice displayed in association with the representation 808a to the representation 806a. The user interface optionally further includes a text entry field 822 in which inputs to compose the message are indicated, and a selectable option 848 that, when selected, causes the electronic device 500 to send a draft message to the messaging dialogue. As shown in FIG. 8A, in some embodiments, the representations 804a and 806a of messages sent by the user of the electronic device 500 are displayed in a different color than the representations 808a and 808b of messages received from users other than the user of the electronic device 500.In some embodiments, representations 804a and 806a are displayed on a green, blue, or other colored background with white or another colored text, and representations 808a and 808b are displayed on a white, gray, or other colored background with black text, or a black or other colored background with white text. Further, in some embodiments, representations 804a and 806a of messages from a user of electronic device 500 are displayed on one side (e.g., the right side) of the user interface, and representations 808a and 808b of messages sent by other users are displayed on the other side (e.g., the left side) of the user interface.

[0262] In FIG. 8B, electronic device 500 optionally detects an indication 842b of an incoming message from a user of the interaction other than the user of electronic device 500 (e.g., Bob). In response to indication 842b, electronic device 500 optionally displays representation 812a of the message. In some embodiments, representation 812a of the incoming message includes an indication of the user who sent the message and an indication of the user to whom the message is replied (e.g., "Bob replying to Alice"). Because the message corresponding to representation 812a is a reply to another message in the interaction, electronic device 500 optionally displays an indication 810a of the message to which the most recent message is replied. Representation 810a and representation 808a may correspond to the same message. Representation 810a and representation 808a may have one or more differences in visual characteristics. For example, the size of representation 810a may be smaller than the size of representation 808a. As another example, the color and / or opacity of representation 810a may differ from the color and / or opacity of representation 808a. Because a message corresponding to representation 808b, which may not be a reply to the message corresponding to representation 808a, was optionally received prior to receiving the message corresponding to representation 812a, electronic device 500 optionally displays a second representation 810a of the message in which the most recent message is a reply to reduce the number of inputs required to view the contents of the message associated with representation 808a and the contents of the message corresponding to representation 812a. In some embodiments, even if a message corresponding to representation 808b was not received between the messages corresponding to representation 808a and representation 812a, electronic device 500 still displays the second representation 810a of the message corresponding to representation 808a.

[0263] Representation 810a of a message in which the most recent message is a reply optionally includes an indication 816a of the number of reply messages received between the message corresponding to representation 808a and the message corresponding to representation 812a. For example, the message corresponding to representation 806a is also a reply to the message corresponding to representation 808a. Because there is one other reply (e.g., the message corresponding to representation 806a) other than the message corresponding to representation 812a that is a reply to the message corresponding to representation 810a, indication 816a shows one additional reply. In some embodiments, instead of displaying the number of replies received between the message corresponding to representation 810a and the message corresponding to representation 812a, electronic device 500 displays an indication of the number of messages received after representation 810a. For example, if another message is received after receiving the message corresponding to representation 812a, and the new message is a reply to the message corresponding to representation 810a, the representation is updated to show the two replies received since displaying representation 810a. However, in some embodiments, the indication 816a reflects the total number of replies to the messages corresponding to the representations 808a and 810a (eg, two replies in this example).

[0264] 8B, electronic device 500, in response to instruction 842b, optionally updates indication 814b of the number of replies to the message corresponding to representation 808a. In some embodiments, electronic device 500 does not display indication 814b. In some embodiments, electronic device 500 displays an indication of the number of replies to the message corresponding to representation 808a other than the message corresponding to representation 806a (e.g., one message in this example). In some embodiments, an indication of the number of replies to the message corresponding to representation 808a other than the message corresponding to representation 806a is displayed at the location of instruction 814b or in another location (e.g., below representation 806a).

[0265] As shown in FIG. 8B, in some embodiments, a user selects (e.g., with contacts 803) an indication 814b of the number of replies to the message corresponding to indication 808a. In response to the user's selection in FIG. 8B, electronic device 500 optionally displays a user interface that includes a representation of the message corresponding to representation 808a and a representation of a message that is a reply to that message, without displaying representations of other messages in the conversation that are not replies to the message corresponding to representation 808a. FIG. 8C shows an exemplary user interface that includes a representation 838a of the message represented by representations 808a and 810a in FIG. 8B, and representations 840a and 838b of subsequent messages in the conversation that are replies to the message corresponding to representation 838a. The user interface shown in FIG. 8C, optionally, does not include representations of messages that are not in the same reply thread, such as representation 808b.

[0266] In some embodiments, representations 838a, 838b, and 840a are displayed overlaid on the messaging user interface shown in Figure 8B. However, in some embodiments, representations 838a, 838b, and 840a are not overlaid on the messaging user interface, but instead are displayed on some other background (e.g., a plain background or an image, etc.). Although representations 838a, 840a, and 838b are shown as having the same color scheme as representations 808a, 806a, and 812a shown in Figure 8B, in some embodiments, representations 838a, 840a, and 838b are displayed in different colors than representations 808a, 806a, and 812a. In some embodiments, different visual characteristics (e.g., size, font, outline color, translucency, etc.) are modified between representations 808a, 806a, and 812a and representations 838a, 840a, and 838b. The user interface further includes a text entry field 824 that is updated to indicate that the messaging content entered into the text entry field 824 creates a message that is also a reply to the message corresponding to the representation 838a. In some embodiments, the text entry field 824 is not updated (e.g., to include the text "message" instead of "reply").

[0267] As shown in FIG. 8C, in some embodiments, the reply user interface does not include lines connecting representations 838a, 840a, and 838b of messages in the reply thread because the reply user interface includes only messages that reply to the same thread. Thus, it is clear that the messages corresponding to representations 840a and 838b are replies to the message corresponding to representation 838a without including lines connecting the representations. In some embodiments, as shown in FIG. 8C, there is only one representation 838a of the message corresponding to representation 838a because intervening messages in the conversation that are not replies to the message associated with representation 838a are not shown in the reply user interface. Thus, in some embodiments, an additional representation of the message corresponding to representation 838a is not needed for a user to easily see the content of the message in the conversation. As shown in FIG. 8C, representations 838a and 838b of messages from users other than the user of electronic device 500 are displayed on one side (e.g., the left side) of the user interface, and representation 840a of messages from the user of electronic device 500 is displayed on the other side (e.g., the right side) of the user interface.

[0268] As shown in Figure 8C, in some embodiments, a user selects (e.g., with contacts 803) text entry field 803. In response to the user's selection of Figure 8C, electronic device 500 optionally displays soft keyboard 846 while remaining within the reply user interface of Figure 8C, as shown in Figure 8D.

[0269] 8D illustrates an updated user interface that may include a soft keyboard 846 whose input is prompted to compose a message that is a reply to the message corresponding to representation 838a. As shown in FIG. 8D, in some embodiments, the user selects (e.g., with contact 803) an area of ​​soft keyboard 846 that corresponds to a letter at which to begin message input.

[0270] In FIG. 8E, in some embodiments, the user finishes entering text into text input field 826, which becomes a reply to the message corresponding to representation 838a. Optionally, the user selects option 848 (e.g., using contact 803) to send the reply message to the messaging conversation.

[0271] In some embodiments, in response to the user's selection in FIG. 8E, electronic device 500 sends a message and updates the user interface, as shown in FIG. 8F.

[0272] As shown in FIG. 8F, in some embodiments, electronic device 500 displays representation 840b of the message sent by the user within the user interface, along with representations 840a and 838b of the message that is a reply to the message corresponding to representation 838a. For example, representation 840b is displayed on the same side of the user interface as representation 840a of another message sent by the user of electronic device 500. Optionally, electronic device 500 updates the messaging user interface within the background of the user interface to include another representation of the user's message corresponding to representation 840b that is connected to the representation of the message corresponding to representation 838a having a curve. Messages that are not replies to the message corresponding to representation 838a are received during the reception of the message corresponding to representation 838b and the message corresponding to representation 840b, so additional representations of the message corresponding to representation 838a can be displayed. The curve connecting the representation of the message corresponding to representation 838a and the representation of the message corresponding to representation 840b is optionally displayed as described in more detail below with reference to FIGS. 12A - 13.

[0273] 8G, in some embodiments, electronic device 500 detects an indication 842g of a message received from another user in the conversation while device 500 is displaying the reply user interface. The message is, optionally, a reply to the message corresponding to representation 838a. Thus, because the message was sent by a user other than the user of electronic device 500, electronic device 500 optionally displays a representation 838c of the message in a reply user interface on the left side of the user interface. In some embodiments, electronic device 500 also updates the user interface in the background to include the additional representation of the received message.

[0274] As shown in FIG. 8G, the user selects (e.g., with contact 803) the ...

Claims

1. 1. An electronic device in communication with a display generating component and one or more input devices, comprising: displaying, via the display generation component, a messaging user interface including one or more indications of messages of the interaction and a text entry field; receiving, while displaying the messaging user interface, an indication via the one or more input devices of inputting a first text into the text entry field; and displaying the first text in the text input field of the messaging user interface in response to receiving the indication of input of the first text, the displaying of the first text comprising: after receiving a first portion of the first text including a first one or more characters and before receiving a second portion of the first text including a second one or more characters different from the first one or more characters; displaying the first portion of the first text with a visual characteristic having a first value in response to a determination that the first portion of the first text does not partially correspond to a respective contact; displaying the first portion of the first text with the visual characteristic having a second value different from the first value in accordance with a determination that the first portion of the first text partially corresponds to the respective contact; after receiving the second portion of the first text; displaying the first and second portions of the first text with the visual characteristic having the second value in accordance with a determination that the first and second portions of the first text correspond to the respective contacts; displaying the first portion and the second portion of the first text with the visual characteristic having the first value in accordance with a determination that the first portion and the second portion of the first text do not correspond to a contact; after receiving the second portion of the first text, in response to a determination that the first and second portions of the first text correspond to the respective contacts, displaying the first text with the visual characteristic having a third value different from the first value and the second value in response to receiving an input associating the first text with the respective contact; displaying the first text with the visual characteristic having the first value in response to receiving an input that does not associate the first text with the respective contact; The method includes:

2. each of the contacts is a contact involved in the interaction; Displaying the first text includes: after receiving the second portion of the first text; displaying the first and second portions of the first text with the visual characteristic having the first value in accordance with a determination that the first and second portions of the first text correspond to a second respective contact not included in the conversation. The method of claim 1 , comprising:

3. 2. The method of claim 1, wherein the input associating the first text with the respective contact comprises selecting a selectable option while the first text is displayed with the visual characteristic having the second value.

4. The method of claim 1 , wherein the inputting of the first text with the respective contact comprises inputting a predefined character in the first text.

5. after receiving the second portion of the first text, in response to a determination that the first text corresponds to the respective contact, removing display of the default text from the messaging user interface in response to a determination that the input has been received associating the first text with the respective contact. The method of claim 4 further comprising:

6. The respective contact is identified by the first text in combination with a second text on the electronic device, and the indication of input of the first text does not indicate the second text, and the method further comprises: after receiving the second portion of the first text, in response to a determination that the first text corresponds to the respective contact, displaying the first text with the visual characteristic having the third value without adding the second text to the messaging user interface pursuant to determining that the input has been received associating the first text with the respective contact. The method of claim 1 further comprising:

7. while the conversation is in a mode in which an indication of messaging activity within the conversation does not cause presentation of a notification of the messaging activity at the electronic device. receiving an indication that a respective messaging activity has been added to the conversation; in response to receiving the indication that the respective messaging activity has been added to the interaction; ceasing to present, at the electronic device, a respective notification of the respective messaging activity in accordance with a determination that the respective messaging activity is not associated with text associated with a user of the electronic device; and presenting the respective notification of the respective messaging activity at the electronic device in accordance with a determination that the respective messaging activity is associated with text associated with a user of the electronic device; The method of claim 1 further comprising:

8. receiving an indication that a respective messaging activity has been added to the dialogue, the respective messaging activity including text linked to a user of the electronic device; presenting, in response to receiving an indication that the respective messaging activity has been added to the interaction, a respective notification of the respective messaging activity at the electronic device, the respective notification including a visual indication of the respective notification, the visual indication being displayed via the display generation component, the visual indication being displayed while the messaging user interface is not displayed; displaying the visual indication of the respective notification and receiving, while not displaying the messaging user interface, input directed to the visual indication of the respective notification via the one or more input devices; displaying, via the display generation component, the messaging user interface in response to receiving the input directed to the visual indication of the respective notification, wherein the messaging user interface is navigated to display a representation of the respective messaging activity; The method of claim 1 further comprising:

9. the messaging user interface includes respective text associated with respective users; responsive to a determination that the respective user is a user of the electronic device, the respective text is displayed with a respective visual characteristic having a first respective value; 2. The method of claim 1, wherein, pursuant to a determination that the respective user is a user of a second electronic device different from the electronic device, the respective text is displayed with a respective visual characteristic having a second respective value different from the first respective value.

10. receiving, while displaying the messaging user interface, a sequence of one or more inputs via the one or more input devices, the sequence including an instruction to input, into the text entry field, second text corresponding to a second respective contact not included in the interaction; In response to receiving said sequence of one or more inputs, displaying the second text in the text input field of the messaging user interface; displaying, on the messaging user interface, respective user interfaces corresponding to one or more contacts associated with the electronic device, the respective user interfaces including a selectable option selectable to initiate a process of adding the second respective contact to the conversation; The method of claim 1 further comprising:

11. receiving, via the one or more input devices, an input corresponding to a request to send a respective message including the first text to the respective contact while the first text is associated with the respective contact; in response to receiving an input corresponding to a request to send the respective message including the first text to the interaction, sending a string including the first text to a second electronic device, the string being encoded with a communication identifier for the respective contact determined by the electronic device; The method of claim 1 further comprising:

12. receiving, at the electronic device, a string corresponding to a respective message, the respective message including respective text associated with a second respective contact, the string being encoded with a communication identifier for the second respective contact; responsive to receiving the character string, using the communication identifier for each of the second contacts to associate the respective text with a contact entry stored on the electronic device; The method of claim 1 further comprising:

13. The input associating the first text with the respective contact is a first input of a first type received while the predefined character is displayed in the text input field with the first text, and the method further comprises: receiving a delete input directed to the text entry field via the one or more input devices after removing display of the default character from the messaging user interface while the first text is associated with the respective contact; in response to receiving the delete input directed to the text entry field, dissociating the first text from the respective contact; and redisplaying the default characters with at least a respective portion of the first text in the text input field; receiving a second input of the first type via the one or more input devices while displaying the default character together with the first text in the text input field after disassociating the first text with the respective contact; in response to receiving the second input of the first type, updating the contacts in the text input field according to the second input of the first type without associating the first text with the respective contact and without removing the display of the default character from the text input field; The method of claim 5 further comprising:

14. one or more processors; Memory, and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing a method according to any one of claims 1 to 13.

15. A computer program comprising instructions which, when executed by one or more processors of an electronic device, cause the electronic device to perform a method according to any one of claims 1 to 13.

Images