User interface for message summarization

Abstract

The present disclosure generally relates to selectively displaying summaries of messages, displaying summaries of related messages, and displaying message summary affordances.

Description

Cross-reference to related applications

[0001] This application claims priority to the following applications: U.S. Patent Application No. 19 / 030,720, filed January 17, 2025, entitled "USER INTERFACES FOR MESSAGE SUMMARIES"; U.S. Provisional Patent Application No. 63 / 670,672, filed July 12, 2024, entitled "USER INTERFACES FOR MESSAGE SUMMARIES"; U.S. Provisional Patent Application No. 63 / 657,061, filed June 6, 2024, entitled "USER INTERFACES FOR MESSAGE SUMMARIES"; U.S. Provisional Patent Application No. 63 / 646,847, filed May 13, 2024, entitled "USER INTERFACES FOR MESSAGE SUMMARIES"; and U.S. Provisional Patent Application No. 19 / 030,720, filed April 8, 2024, entitled "USER INTERFACES FOR MESSAGE SUMMARIES". U.S. Provisional Patent Application No. 63 / 631,275, entitled "Interfaces for Message Summaries". The entire contents of each of these patent applications are incorporated herein by reference in their entirety for all purposes. Technical Field

[0002] This disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying message summaries. Background Technology

[0003] Computer systems display messages (e.g., text messages and / or emails) that include written content transmitted or received between users and / or computer systems. Summary of the Invention

[0004] However, some technologies used to display message summaries on electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may include multiple buttons or keystrokes. These existing technologies require more time than necessary, resulting in wasted user time and device power. This latter consideration is particularly important in battery-powered devices.

[0005] Therefore, the present invention provides electronic devices with a faster and more efficient method and interface for displaying message summaries. Such methods and interfaces can optionally supplement or replace other methods for displaying message summaries. These methods and interfaces reduce the cognitive burden on the user and result in a more efficient human-machine interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging cycles.

[0006] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; detecting a request to display the first message via the one or more input devices while displaying the summary of the content based on the first message; displaying the first message via the display generation component in response to detecting the request to display the first message; and displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0007] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices. The one or more programs include instructions for displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; detecting a request to display the first message via the one or more input devices while displaying the summary of content based on the first message; displaying the first message via the display generation component in response to detecting the request to display the first message; and displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0008] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and one or more input devices. The one or more programs include instructions for displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; detecting a request to display the first message via the one or more input devices while displaying the summary of content based on the first message; displaying the first message via the display generation component in response to detecting the request to display the first message; and displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0009] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; detecting a request to display the first message via the one or more input devices while displaying the summary of content based on the first message; displaying the first message via the display generation component in response to detecting the request to display the first message; and displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0010] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: components for: displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; components for: detecting a request to display the first message via the one or more input devices while displaying the summary of the content based on the first message; components for: displaying the first message via the display generation component in response to detecting the request to display the first message; and components for: displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0011] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to execute by one or more processors of a computer system communicating with a display generation component and one or more input devices. The one or more programs include instructions for displaying a first user interface via the display generation component, including: displaying a summary of content based on a first message according to determining that a first set of criteria is satisfied; detecting a request to display the first message via the one or more input devices while displaying the summary of the content based on the first message; displaying the first message via the display generation component in response to detecting the request to display the first message; and displaying the first user interface via the display generation component after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary.

[0012] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: receiving a first message including first content and a second message different from the first message including second content; displaying, via the display generation component, a first summary based on the first content of the first message and the second content of the second message; after displaying the first summary, receiving a third message associated with the first message and the second message, wherein the third message includes third content; and after receiving the third message and based on determining that a first set of criteria is met, displaying, via the display generation component, a second summary different from the first summary, wherein the second summary is based on the third content of the third message.

[0013] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices. The one or more programs include instructions for: receiving a first message including first content and a second message different from the first message including second content; displaying, via the display generation component, a first summary based on the first content and the second content of the second message; after displaying the first summary, receiving a third message associated with the first message and the second message, wherein the third message includes third content; and after receiving the third message and based on determining that a first set of criteria is met, displaying, via the display generation component, a second summary different from the first summary, wherein the second summary is based on the third content of the third message.

[0014] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and one or more input devices. The one or more programs include instructions for: receiving a first message including first content and a second message different from the first message including second content; displaying, via the display generation component, a first summary based on the first content and the second content of the second message; after displaying the first summary, receiving a third message associated with the first message and the second message, wherein the third message includes third content; and after receiving the third message and based on determining that a first set of criteria is satisfied, displaying, via the display generation component, a second summary different from the first summary, wherein the second summary is based on the third content of the third message.

[0015] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a first message including first content and a second message different from the first message including second content; displaying, via the display generation component, a first summary based on the first content of the first message and the second content of the second message; after displaying the first summary, receiving a third message associated with the first message and the second message, wherein the third message includes third content; and after receiving the third message and based on determining that a first set of criteria is met, displaying, via the display generation component, a second summary different from the first summary, wherein the second summary is based on the third content of the third message.

[0016] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: components for receiving a first message including first content and a second message different from the first message including second content; components for displaying a first summary based on the first content of the first message and the second content of the second message via the display generation component; components for receiving a third message associated with the first message and the second message after displaying the first summary, wherein the third message includes third content; and components for displaying a second summary different from the first summary via the display generation component after receiving the third message and based on determining that a first set of criteria is met, wherein the second summary is based on the third content of the third message.

[0017] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for: receiving a first message including first content and a second message different from the first message including second content; displaying, via the display generation component, a first summary based on the first content and the second content of the second message; after displaying the first summary, receiving a third message associated with the first message and the second message, wherein the third message includes third content; and after receiving the third message and based on determining that a first set of criteria is met, displaying, via the display generation component, a second summary different from the first summary, wherein the second summary is based on the third content of the third message.

[0018] According to some embodiments, a method is described that is executed at a computer system communicating with a display generation component and one or more input devices. The method includes: detecting a request to display one or more messages of a first message thread via the one or more input devices; and, in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0019] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices. The one or more programs include instructions for: detecting a request to display one or more messages of a first message thread via the one or more input devices; and, in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0020] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and one or more input devices. The one or more programs include instructions for: detecting a request to display one or more messages of a first message thread via the one or more input devices; and, in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0021] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting a request to display one or more messages of a first message thread via the one or more input devices; and, in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0022] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: components for detecting a request to display one or more messages of a first message thread via the one or more input devices; and components for: in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0023] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to execute by one or more processors of a computer system in communication with a display generation component and one or more input devices. The one or more programs include instructions for: detecting a request to display one or more messages of a first message thread via the one or more input devices; and, in response to detecting the request to display the one or more messages of the first message thread, displaying a user interface including the one or more messages of the first message thread via the display generation component, including: displaying a first summary element at a first position in the first message thread based on determining that a first message is unread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages of the first message thread; and displaying the first summary element at a second position in the first message thread based on determining that the first message is not unread, wherein the second position is different from the first position.

[0024] Executable instructions for performing these functions may optionally be included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0025] Therefore, faster and more efficient methods and interfaces are provided for displaying message summaries on devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for displaying message summaries. Attached Figure Description

[0026] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein the same reference numerals in all the drawings indicate corresponding parts.

[0027] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some implementation schemes.

[0028] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0029] Figure 2 Examples of portable multi-functional devices with touchscreens according to some implementation schemes are shown.

[0030] Figure 3A This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0031] Figures 3B to 3G This example demonstrates how to perform an operation using an Application Programming Interface (API).

[0032] Figure 4A An exemplary user interface for a menu applied to a portable multi-functional device, according to some implementation schemes, is illustrated.

[0033] Figure 4B An exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.

[0034] Figure 5A Examples of personal electronic devices according to some implementation schemes are shown.

[0035] Figure 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0036] Figures 6A to 6AD An example of a user interface for displaying a message summary is shown according to some implementation schemes.

[0037] Figure 7 This is a flowchart illustrating a method for displaying a summary of a message according to some implementation schemes.

[0038] Figure 8 This is a flowchart illustrating a method for displaying a summary of relevant messages according to some implementation schemes.

[0039] Figures 9A to 9P An example of a user interface for displaying a message summary capability representation is shown according to some implementation schemes.

[0040] Figure 10 This is a flowchart illustrating a method for displaying a message summary capability representation according to some implementation schemes. Detailed Implementation

[0041] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0042] There is a need for electronic devices that provide efficient methods and interfaces for displaying message summaries. These electronic devices display user interfaces for communications that include multiple messages. The devices need to display message summaries based on fulfilling different conditions, and in some instances, omit displaying summaries for specific messages. Such technologies can reduce the cognitive load on users viewing messages, thereby increasing productivity. Furthermore, such technologies can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0043] under, Figures 1A to 1B , Figure 2 , Figures 3A to 3G , Figures 4A to 4B and Figures 5A to 5B A description is provided of a device for performing a technique for displaying message summaries. Figures 6A to 6AD Examples of user interfaces for managing event notifications are shown according to some implementation schemes. Figure 7 This is a flowchart illustrating a method for displaying a summary of messages according to some implementation schemes. Figure 8 This is a flowchart illustrating a method for displaying a summary of relevant messages according to some implementation schemes. Figures 6A to 6AD The user interface in the document is used to illustrate the processes described below, including Figures 7 to 8 The process in. Figures 9A to 9P An example of a user interface for displaying a message summary capability representation is shown according to some implementation schemes. Figure 10 This is a flowchart illustrating a method for displaying a message summary capability representation according to some implementation schemes.

[0044] The processes described below enhance device operability and make the user-device interface more efficient through various technologies (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), including providing users with improved visual feedback, reducing the amount of input required to perform operations, providing additional control options without cluttering the user interface with additional displayed controls, performing operations when a set of conditions are met without requiring further user input, reducing the amount of time users need to view messages, and / or additional technologies. These technologies also reduce power consumption and extend device battery life by enabling users to use the device faster and more efficiently.

[0045] Furthermore, in a method described herein where one or more steps depend on the satisfaction of one or more conditions, it should be understood that the method may be repeated in multiple repetitions such that, during the repetitions, all conditions determining the steps in the method are satisfied in different repetitions of the method. For example, if the method requires performing a first step (if the conditions are satisfied) and a second step (if the conditions are not satisfied), those skilled in the art will know that the stated steps are repeated until both conditions are satisfied and not satisfied (in no particular order). Thus, a method described as having one or more steps depending on the satisfaction of one or more conditions can be rewritten as a method that repeats until each condition described in the method is satisfied. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing discretionary operations based on the satisfaction of the corresponding one or more conditions, and thus to determine whether possible conditions have been satisfied without explicitly repeating the steps of the method until all conditions determining the steps in the method are satisfied. Those skilled in the art will also understand that, similar to a method having discretionary steps, a system or computer-readable storage medium may repeat the steps of the method multiple times as needed to ensure that all discretionary steps have been performed.

[0046] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another. For example, a first touch may be referred to as a second touch, and similarly, a second touch may be referred to as a first touch, without departing from the scope of the various described embodiments. In some embodiments, a first touch and a second touch are two separate references to the same touch. In some embodiments, both a first touch and a second touch are touches, but they are not the same touch.

[0047] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the 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.

[0048] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "in," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determination..." or "in response to detection of [the stated condition or event]."

[0049] This document describes implementations of electronic devices, user interfaces for such devices, and associated processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc., Cupertino, California. ® Devices, iPod Touch ® Devices and iPads ® Device. Alternatively, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreens and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreens and / or touchpads). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless or wired communication) with a display generating component (e.g., a display device such as a head-mounted display (HMD), monitor, projector, touch-sensitive display; or other devices or components that present visual content to a user, such as visual content generated on or in or from the display generating component and visible elsewhere). The display generating component is configured to provide visual output, such as display via a CRT monitor, via an LED monitor, or 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, “display” content includes content (e.g., video data rendered or decoded by display controller 156) that is visually generated by sending data (e.g., image data or video data) to an integrated or external display generating component via a wired or wireless connection.

[0050] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0051] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0052] Various applications running on this device may optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device may optionally be adapted and / or changed for different applications, and / or within the respective applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) may optionally support various applications using a user interface that is intuitive and clear to the user.

[0053] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1A This is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display system 112 is sometimes referred to as a "touchscreen" for convenience, and is sometimes referred to as or called a "touch-sensitive display system". Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 may optionally include one or more haptic output generators 167 for generating haptic outputs on device 100 (e.g., generating haptic outputs on a haptic surface such as the haptic display system 112 of device 100 or the touchpad 355 of device 300). These components may optionally communicate via one or more communication buses or signal lines 103.

[0054] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact may optionally be determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface may optionally be used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus may optionally be used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or change of the contact area detected on the touch-sensitive surface, the capacitance and / or change of the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change of the touch-sensitive surface adjacent to the contact may be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into 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 the contact as an attribute of user input allows users to access additional device functionality that would otherwise be inaccessible to the user on a space-constrained, scaled-down device used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0055] As used in this specification and claims, the term "tactile output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of mass of the device, detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, 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 the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, does not move. As another example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of the user (e.g., "release click", "press click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or common) user.

[0056] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

[0057] Memory 102 may optionally include high-speed random access memory, and may also optionally include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may optionally control access to memory 102 by other components of device 100.

[0058] Peripheral interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0059] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, subscriber identity module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks (such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular phone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs))) and other devices. RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radio components. Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including but 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, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE 802.11ac), Internet Protocol Voice (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0060] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and sends the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and sends the audio data to peripheral interface 118 for processing. Audio data may optionally be retrieved by peripheral interface 118 from memory 102 and / or RF circuitry 108 and / or sent to that memory and / or RF circuitry. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both outputs (e.g., a mono-ear headset or a binaural headset) and inputs (e.g., a microphone).

[0061] I / O subsystem 106 couples input / output peripherals (such as touchscreen 112 and other input control devices 116) on device 100 to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, 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 electrical signals from / transmit electrical signals to the other input control device 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some embodiments, input controller 160 may optionally be coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., ... Figure 2 Optionally, 208 may include increase / decrease buttons for volume control of speaker 111 and / or microphone 113. These one or more buttons may optionally include a push-button (e.g., Figure 2(Ref. 206 in the original text). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad, 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 and / or air 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. In some implementations, air gestures are gestures detected without the user touching an input element that is part of the device (or independently of an input element that is part of the device) and based on the detected movement of a part of the user's body through the air (including movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (e.g., movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another of the user's fingers or a part of the user's hand), and / or absolute movement of a part of the user's body (e.g., a tapping gesture that includes the hand moving a predetermined amount and / or rate in a predetermined pose, or a shaking gesture that includes a predetermined rate or amount of rotation of a part of the user's body)).

[0062] A rapid press of the push button may optionally disengage the touchscreen 112 from its lock or optionally initiate a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) may optionally power on or off the device 100. The functionality of one or more of these buttons may optionally be user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0063] The touch-sensitive display system 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. The visual output may optionally include graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output may optionally correspond to user interface objects.

[0064] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and translate the detected contact into interaction 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 contact point between touchscreen 112 and the user corresponds to the user's finger.

[0065] Touchscreen 112 may optionally employ LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies may be used in other embodiments. Touchscreen 112 and display controller 156 may optionally use any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption of contact. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology, such as that used in the iPhone from Apple Inc. (Cupertino, California), is used. ® and iPod Touch ® The technology used.

[0066] In some embodiments of the touchscreen 112, the touch-sensitive display may optionally resemble a multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0067] The touch-sensitive display in some embodiments of the touchscreen 112 is described in the following applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, “Mode-Based Graphical User Interfaces For Touch Sensitive Input”. (6) U.S. Patent Application No. 11 / 228,758, filed September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, “Activating Virtual Keys Of ATouch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, “Multi-Functional Hand-Held Device”. The full text of all these applications is incorporated herein by reference.

[0068] The touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users may optionally use any suitable object or accessory, such as a stylus, finger, etc., to interact with the touchscreen 112. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positioning or commands for performing the user-desired actions.

[0069] In some embodiments, in addition to the touchscreen, device 100 may optionally include a touchpad for activating or deactivating specific 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 may optionally be a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0070] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 may optionally include a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0071] Device 100 may optionally include a secure element 163 for securely storing information. In some embodiments, secure element 163 is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, secure element 163 provides (e.g., publishes) security information (e.g., payment information (e.g., account number and / or transaction-specific dynamic security code), identification information (e.g., credentials for nationally approved digital identifiers), and / or authentication information (e.g., data generated using a cryptographic engine and / or by performing asymmetric cryptographic operations)). In some embodiments, secure element 163 provides (or publishes) security information in response to device 100 receiving authorization, such authorization being user authentication (e.g., fingerprint authentication; password authentication; detection of a double press of a hardware button when device 100 is in an unlocked state, and optionally when device 100 has been continuously on the user's wrist since being unlocked by providing authentication credentials to device 100), wherein the continued presence of device 100 on the user's wrist is determined by periodically checking the contact between the device and the user's skin. For example, device 100 detects a fingerprint at its fingerprint sensor (e.g., a fingerprint sensor integrated into a button). Device 100 determines whether the detected fingerprint matches a registered fingerprint. Based on the determination that the fingerprint matches a registered fingerprint, security element 163 provides (e.g., publishes) security information. Based on the determination that the fingerprint does not match a registered fingerprint, security element 163 abandons providing (e.g., publishing) security information.

[0072] The device 100 may optionally also include one or more optical sensors 164. Figure 1A An optical sensor 164 coupled to an optical sensor controller 158 in an I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also referred to as a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen 112 on the front of the device, allowing the touchscreen to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of other video conference participants to be optionally acquired for use in video conferencing while the user is viewing them on the touchscreen. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating lenses and sensors within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen for both video conferencing and still image and / or video image acquisition.

[0073] The device 100 may optionally also include one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as camera module), depth camera sensor 175 may be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information can be optionally acquired for video conferencing while a user views other video conferencing participants on a touchscreen, and selfies with depth map data can be captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the positioning of depth camera sensor 175 can be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen for both video conferencing and still image and / or video image acquisition.

[0074] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to a touchscreen 112 located on the front of device 100.

[0075] The device 100 may optionally also include one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may be configured as described in the following U.S. patent applications: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

[0076] The device 100 may optionally also include one or more haptic output generators 167. Figure 1A A haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic 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 haptic output generating components (e.g., components that convert electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., a haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some implementations, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touchscreen 112 located on the front of the device 100.

[0077] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may be configured as described in the following U.S. Patent Publications: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods and Apparatuses For Operating A Portable DeviceBased On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed on a touchscreen in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of device 100.

[0078] In some embodiments, the software components stored in memory 102 include an operating system 126, a biometric module 109, a communication module (or instruction set) 128, a contact / 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, an authentication module 105, and an application (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3A Storage device / global internal state 157, such as Figure 1A and Figure 3A As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of touch screen 112; sensor state, which includes information obtained from various sensors and input control devices 116 of the device; and position information relating to device position and / or orientation.

[0079] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0080] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components 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 be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, Wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0081] The biometric module 109 optionally stores information about one or more registered biometric features (e.g., fingerprint features, facial recognition features, eye and / or iris features) for verifying whether received biometric information matches the registered biometric features. In some embodiments, the stored information about one or more registered biometric features includes data that enables comparison between the stored information and the received biometric information, but does not include sufficient information to reproduce the registered biometric features. In some embodiments, the biometric module 109 stores information about registered biometric features in association with a user account of device 100. In some embodiments, the biometric module 109 compares the received biometric information with the registered biometric features to determine whether the received biometric information matches the registered biometric features.

[0082] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or a contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations can optionally be applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

[0084] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures can be detected optionally by detecting specific contact patterns. For example, detecting a finger tap gesture includes: detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes: detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0085] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0086] In some implementations, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes from applications, etc., to specify the graphics to be displayed, and also receives coordinate data and other graphic attribute data if necessary, and then generates screen image data to output to the display controller 156.

[0087] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0088] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as the contact module 137, email client module 140, IM module 141, browser module 147, and any other application that requires text input.

[0089] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to telephone module 138 for use in location-based dialing; to camera module 143 as image / video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0090] Authentication module 105 determines whether a requested operation (e.g., requested by an application in application 136) is authorized to be performed. In some implementations, authentication module 105 receives an operation to be performed that optionally requires authentication. Authentication module 105 determines whether the operation is authorized to be performed based on a range of factors, including the locked state of device 100, the location of device 100, whether a security delay has occurred, whether the received biometric information matches a registered biometric feature, and / or other factors. Once authentication module 105 determines that the operation is authorized to be performed, authentication module 105 triggers the execution of the operation.

[0091] Application 136 may optionally include the following modules (or instruction sets) or subsets or supersets thereof:

[0092] • Contacts module 137 (sometimes called address book or contact list);

[0093] • Telephone module 138;

[0094] • Video conferencing module 139;

[0095] • Email client module 140;

[0096] • Instant Messaging (IM) module 141;

[0097] • Fitness support module 142;

[0098] • Camera module 143 for still images and / or video images;

[0099] • Image management module 144;

[0100] • Video player module;

[0101] • Music player module;

[0102] • Browser module 147;

[0103] • Calendar module 148;

[0104] • Widget module 149, which may optionally include one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets acquired by the user, and user-created widget 149-6.

[0105] • Widget creator module 150 for creating user-created widgets 149-6;

[0106] • Search module 151;

[0107] • Video and music player module 152, which combines a video player module and a music player module;

[0108] • Memo module 153;

[0109] • Map module 154; and / or

[0110] • Online video module 155.

[0111] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0112] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via the telephone module 138, video conferencing module 139, email client module 140, or IM module 141; and so on.

[0113] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify input telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As noted above, wireless communication may optionally use any of a variety of communication standards, protocols, and technologies.

[0114] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0115] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0116] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions for performing the following operations: entering a character sequence corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing received instant messages. In some embodiments, the sent and / or received instant messages may optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages delivered using SMS or MMS) and internet-based messages (e.g., messages delivered using XMPP, SIMPLE, or IMPS).

[0117] Incorporating RF circuitry 108, touchscreen 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, fitness support module 142 includes executable instructions for performing the following operations: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0118] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for performing the following operations: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

[0119] Incorporating the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for performing operations such as arranging, modifying (e.g., editing) or otherwise manipulating, marking, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0120] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for performing the following operations: browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as linking to attachments and other files on web pages.

[0121] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0122] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 may be a micro-application (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or a user-created micro-application (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

[0123] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 can optionally be used by the user to create widgets (e.g., turning a user-specified section of a webpage into a widget).

[0124] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions for performing the following operations: searching the memory 102 for text, music, sound, images, videos, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

[0125] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users to download and play back 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 back video (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.).

[0126] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do items, etc., according to user instructions.

[0127] In conjunction with RF circuitry 108, touchscreen 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 may optionally be used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0128] Incorporating touchscreen 112, display controller 156, touch / 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, the online video module 155 includes instructions to: allow users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0129] Each of the modules and applications described above corresponds to an executable set of instructions for performing one or more functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 may optionally store a subset of the aforementioned modules and data structures. Additionally, memory 102 may optionally store additional modules and data structures not described above.

[0130] In some implementations, device 100 is a device whose operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (such as push-buttons and dial pads) on device 100 can be optionally reduced.

[0131] A predefined set of functions unique to touchscreens and / or touchpads may optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to the main menu, main desktop menu, or root menu. In such embodiments, a "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0132] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3A This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

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

[0134] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or ready to be displayed by the application 136-1, a state queue for enabling the user to return to the previous state or view of the application 136-1, and a repeat / undo queue for the user's previous actions.

[0135] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events, such as user touches on touch-sensitive display system 112 as part of a multi-touch gesture. Peripheral device interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display system 112 or touch-sensitive surfaces.

[0136] In some implementations, the event monitor 171 sends requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 sends event information. In other implementations, the peripheral device interface 118 sends event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0137] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0138] When the touch-sensitive display system 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0139] Another aspect of the user interface associated with an application is a collection 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 corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected may optionally be called the hit view, and the set of events identified as correct input may optionally be determined at least in part based on the hit view of the initial touch that initiates the touch-based gesture.

[0140] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0141] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0142] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0143] In some implementations, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another implementation, event classifier 170 is a separate module or part of another module (such as contact / motion module 130) stored in memory 102.

[0144] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 may optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0145] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which may optionally include sub-event delivery instructions).

[0146] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. 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 touch movement, the event information may optionally also include the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0147] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (e.g., 187-1 and / or 187-2) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch-sensitive display system 112, and lifting of the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0148] In some implementations, event definition 186 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on a touch-sensitive display system 112, when a touch is detected on the touch-sensitive display system 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 corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

[0149] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0150] When the corresponding event recognizer 180 determines that the sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0151] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0152] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from delivering (and deferred delivering) the sub-events to the corresponding hit view. In some implementations, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag retrieves the flag and performs a predefined process.

[0153] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

[0154] In some implementations, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some implementations, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits that display information to graphics module 132 for display on a touch-sensitive display.

[0155] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other implementations, they are included in two or more software modules.

[0156] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0157] Figure 2A portable multi-functional device 100 with a touchscreen 112 is illustrated according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon may optionally not select the corresponding application when the gesture corresponding to selection is a tap.

[0158] Device 100 may optionally also include one or more physical buttons, such as a "main desktop" or menu button 204. As previously described, menu button 204 may optionally be used to navigate to any application 136 of a set of applications optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touchscreen 112.

[0159] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to: power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts speech input via microphone 113 for activating or deactivating certain functions. Device 100 may also optionally include one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic output for the user of device 100.

[0160] Figure 3AThis is a block diagram of an exemplary multi-functional device with 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, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial 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 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 may also optionally include a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The described tactile output generator 167), sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one described above)) Figure 1A The described contact strength sensor 165). 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 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 310. In some embodiments, memory 370 stores information related to portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 may optionally store additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 may optionally store a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 ( Figure 1A The memory 102 may optionally not store these modules.

[0161] Figure 3AEach of the elements described above may optionally be stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to a set of instructions for performing the functions described above. The modules or computer programs described above (e.g., instruction sets or including instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may optionally store a subset of the modules and data structures described above. In addition, memory 370 may optionally store additional modules and data structures not described above.

[0162] Specific embodiments within the scope of this disclosure may be implemented, in whole or in part, using a tangible computer-readable storage medium (or a plurality of tangible computer-readable storage media of one or more types) that encodes one or more computer-readable instructions. It should be understood that computer-readable instructions may be organized in any format, including applications, widgets, processes, software, and / or components.

[0163] Specific embodiments within the scope of this disclosure include computer-readable storage media that encode instructions organized as an application (e.g., application 3160) that, when executed by one or more processing units, control the execution of an electronic device (e.g., device 3150). Figure 3B Methods Figure 3C The methods and / or one or more other processes and / or methods described herein.

[0164] It should be recognized that the application of 3160 ( Figure 3D The application 3160 (as shown in the diagram) can be any suitable type of application, including one or more of the following: browser applications, applications used as execution environments for plugins, widgets, or other applications, fitness applications, health applications, digital payment applications, media applications, social networking applications, messaging applications, and / or map applications. In some embodiments, application 3160 is an application pre-installed on device 3150 at the time of purchase (e.g., a first-party application). In some embodiments, application 3160 is an application provided to device 3150 via operating system update files (e.g., a first-party or second-party application). In some embodiments, application 3160 is an application provided via an app store. In some embodiments, the app store can be an app store pre-installed on device 3150 at the time of purchase (e.g., a first-party app store). In some embodiments, the app store is a third-party app store (e.g., an app store provided by another app store, downloaded via a network, and / or read from a storage device).

[0165] refer to Figure 3B and Figure 3FApplication 3160 obtains information (e.g., 3010). In some embodiments, at 3010, information is obtained from at least one hardware component of device 3150. In some embodiments, at 3010, information is obtained from at least one software module of device 3150. In some embodiments, at 3010, information is obtained from at least one hardware component external to device 3150 (e.g., peripheral devices, accessory devices, and / or servers). In some embodiments, the information obtained at 3010 includes location information, time information, notification information, user information, environmental information, electronic device status information, weather information, media information, historical information, event information, hardware information, and / or motion information. In some embodiments, in response to obtaining information at 3010 and / or thereafter, application 3160 provides the information to the system (e.g., 3020).

[0166] In some implementations, the system (e.g., Figure 3E The system shown as 3110 is the operating system hosted on device 3150. In some implementations, the system (e.g., Figure 3E 3110 shown in the figure is an external device (e.g., a server, peripheral device, accessory and / or personal computing device) that includes an operating system.

[0167] refer to Figure 3C and Figure 3G Application 3160 obtains information (e.g., 3030). In some embodiments, the information obtained at 3030 includes location information, time information, notification information, user information, environmental information, electronic device status information, weather information, media information, historical information, event information, hardware information, and / or motion information. In response to obtaining information at 3030 and / or thereafter, application 3160 performs an operation on the information (e.g., 3040). In some embodiments, the operations performed at 3040 include: providing notifications based on the information, sending messages based on the information, displaying information, controlling the user interface of a fitness application based on the information, controlling the user interface of a health application based on the information, controlling focus mode based on the information, setting reminders based on the information, adding calendar entries based on the information, and / or calling the API of system 3110 based on the information.

[0168] In some implementations, execution is performed in response to a trigger. Figure 3B Methods and / or Figure 3C The method involves one or more steps. In some implementations, triggering includes detecting an event, receiving a notification from system 3110, user input, and / or responding to a call to an API provided by system 3110.

[0169] In some implementations, when the instructions of application 3160 are executed, control device 3150 executes them by calling an application programming interface (API) (e.g., API 3190) provided by system 3110. Figure 3B Methods and / or Figure 3C The method. In some implementations, application 3160 executes without calling API 3190. Figure 3B Methods and / or Figure 3C At least a part of the method.

[0170] In some implementation schemes, Figure 3B Methods and / or Figure 3C One or more steps of the method include: invoking the API (e.g., API 3190) using one or more parameters defined by the API. In some implementations, one or more parameters include constants, keys, data structures, objects, object classes, variables, data types, pointers, arrays, lists, or pointers to functions or methods and / or references to data or other items to be passed via the API in another way.

[0171] refer to Figure 3D Example 3150 is shown. In some embodiments, device 3150 is a personal computing device, smartphone, smartwatch, fitness tracker, head-mounted display (HMD) device, media device, public utility, speaker, television, and / or tablet computer. Figure 3D As illustrated, device 3150 includes application 3160 and operating system (e.g., Figure 3E System 3110 is shown in the diagram. Application 3160 includes application implementation module 3170 and API call module 3180. System 3110 includes API 3190 and implementation module 3100. It should be understood that device 3150, application 3160 and / or system 3110 may include... Figure 3D and Figure 3E The examples illustrate more, fewer, and / or different components.

[0172] In some implementations, application implementation module 3170 includes a set of one or more instructions corresponding to one or more operations performed by application 3160. For example, when application 3160 is a messaging application, application implementation module 3170 may include operations for receiving and transmitting messages. In some implementations, application implementation module 3170 communicates with API calling module 3180 via API 3190 (in... Figure 3E (As shown in the figure) communicates with system 3110.

[0173] In some implementations, API 3190 is a software module (e.g., a set of computer-readable instructions) that provides an interface that allows different modules (e.g., API calling module 3180) to access and / or use one or more functions, methods, procedures, data structures, classes, and / or other services provided by implementation module 3100 of system 3110. For example, API calling module 3180 can access features of implementation module 3100 through one or more API calls or enablements (e.g., embodied by function or method calls) exposed by API 3190 (e.g., software and / or hardware modules capable of receiving, responding to, and / or transmitting API calls), and can pass data and / or control information via API calls or enablements using one or more parameters. In some implementations, API 3190 allows application 3160 to use services provided by software development kit (SDK) libraries. In some implementations, application 3160 combines calls to functions or methods provided by the SDK library and API 3190, or uses data types or objects defined in the SDK library and provided by API 3190. In some implementations, API calling module 3180 makes API calls via API 3190 to access and use features of implementation module 3100 specified by API 3190. In such implementations, implementation module 3100 may return a value to API calling module 3180 via API 3190 in response to an API call. This value may report to application 3160 the capabilities or status of hardware components of device 3150, including those capabilities or statuses related to aspects such as input capabilities and status, output capabilities and status, processing capabilities, power status, storage capacity and status, and / or communication capabilities. In some implementations, API 3190 is implemented partly by firmware, microcode, or other low-level logic executed on the hardware components.

[0174] In some implementations, API 3190 allows the developer of API calling module 3180 (which may be a third-party developer) to utilize features provided by implementation module 3100. In such implementations, one or more API calling modules (e.g., including API calling module 3180) may exist that communicate with implementation module 3100. In some implementations, API 3190 allows multiple API calling modules written in different programming languages ​​to communicate with implementation module 3100 (e.g., API 3190 may include features for translating calls and returns between implementation module 3100 and API calling module 3180), and API 3190 is implemented in a specific programming language. In some implementations, API calling module 3180 calls APIs from different providers, such as a set of APIs from an OS provider, another set of APIs from a plugin provider, and / or another set of APIs from another provider (e.g., a software library provider) or the creator of another set of APIs.

[0175] Examples of API 3190 may include one or more of the following: pairing API (e.g., for establishing a secure connection, such as with an accessory), device detection API (e.g., for locating nearby devices, such as media devices and / or smartphones), payment API, UIKit API (e.g., for generating user interfaces), location detection API, locator API, map API, health sensor API, sensor API, messaging API, push notification API, streaming API, collaboration API, video conferencing API, app store API, advertising service API, web browser API (e.g., WebKit API), transportation API, networking API, WiFi API, Bluetooth API, NFC API, UWB API, fitness API, smart home API, contact transfer API, photo API, camera API, and / or image processing API. In some implementations, a sensor API is an API for accessing data associated with sensors of device 3150. For example, a sensor API may provide access to raw sensor data. Alternatively, a sensor API may provide data derived (and / or generated) from raw sensor data. In some implementations, sensor data includes temperature data, image data, video data, audio data, heart rate data, IMU (Inertial Measurement Unit) data, lidar data, location data, GPS data, and / or camera data. In some implementations, sensors include one or more of accelerometers, temperature sensors, infrared sensors, optical sensors, heart rate sensors, barometers, gyroscopes, proximity sensors, and / or biometric sensors.

[0176] In some embodiments, implementation module 3100 is a system (e.g., an operating system and / or server system) software module (e.g., a set of computer-readable instructions) configured to perform operations in response to receiving an API call via API 3190. In some embodiments, implementation module 3100 is configured to provide an API response (via API 3190) as a result of processing the API call. By way of example, implementation module 3100 and API call module 3180 may each be any of an operating system, library, device driver, API, application, or other module. It should be understood that implementation module 3100 and API call module 3180 may be the same as or different from each other. In some embodiments, implementation module 3100 is at least partially embodied in firmware, microcode, or hardware logic.

[0177] In some implementations, implementation module 3100 returns a value via API 3190 in response to an API call from API call module 3180. While API 3190 defines the syntax and results of the API call (e.g., how to enable the API call and what the API call does), API 3190 may not reveal how implementation module 3100 performs the function specified by the API call. Various API calls are transmitted via one or more application programming interfaces between API call module 3180 and implementation module 3100. Transmitting API calls may include issuing, initiating, calling, receiving, returning, and / or responding to function calls or messages. In other words, transmissions may describe the actions of either API call module 3180 or implementation module 3100. In some implementations, function calls or other references to API 3190 send and / or receive one or more parameters via parameter lists or other structures.

[0178] In some implementations, implementation module 3100 provides more than one API, each API providing a different view or aspect of the functionality implemented by implementation module 3100. For example, one API of implementation module 3100 may provide a first set of functions and be exposed to third-party developers, while another API of implementation module 3100 may be hidden (e.g., not exposed) and provide a subset of the first set of functions, and also provide another set of functions, such as test or debug functions not in the first set of functions. In some implementations, implementation module 3100 calls one or more other components via lower-level APIs, thus acting as both an API calling module and an implementation module. It should be recognized that implementation module 3100 may include additional functions, methods, classes, data structures, and / or other features not specified through API 3190 and not available to API calling module 3180. It should also be recognized that API calling module 3180 may be on the same system as implementation module 3100, or may be remotely located and accessed via a network using API 3190. In some implementations, implementation module 3100, API 3190, and / or API calling module 3180 are stored in a machine-readable medium, which includes any means for storing information in a machine-readable (e.g., computer or other data processing system) form. For example, a machine-readable medium may include a magnetic disk, optical disk, random access memory, read-only memory, and / or flash memory devices.

[0179] An Application Programming Interface (API) is an interface between a first software process and a second software process, specifying the format for communication between the two processes. Limited APIs (e.g., private or partner APIs) are APIs accessible to a limited set of software processes (e.g., only software processes within the operating system or only software processes authorized to access the limited API). Public APIs are accessible to a broader set of software processes. Some APIs enable a software process to communicate or set the state of one or more input devices (e.g., one or more touch sensors, proximity sensors, vision sensors, motion / or orientation sensors, pressure sensors, intensity sensors, sound sensors, wireless proximity sensors, biometric sensors, buttons, switches, rotatable elements, and / or external controllers). Some APIs enable a software process to communicate and / or set the state of one or more output generation components (e.g., one or more audio output generation components, one or more display generation components, and / or one or more haptic output generation components). Some APIs enable specific capabilities (e.g., scrolling, handwriting, text input, image editing, and / or image creation) to be accessed, executed, and / or used by a software process (e.g., generating output for use by the software process based on input from the software process). Some APIs enable content from software processes to be inserted into templates and displayed in user interfaces with layouts and / or behaviors specified by the templates.

[0180] Many software platforms include a set of frameworks that provide core objects and behaviors that software developers need to build software applications that can be used on the platform. Software developers use these objects to display content on a screen, interact with that content, and manage interactions with the software platform. The basic behavior of a software application depends on this framework, and this framework provides software developers with numerous ways to customize the application's behavior to match the specific needs of the application. Many of these core objects and behaviors are accessed via APIs. APIs typically specify the format for communication between software processes, including specifying and grouping available variables, functions, and protocols. API calls (sometimes called API requests) are typically transmitted from a sending software process to a receiving software process as a way to achieve one or more of the following: the sending software process requests information from the receiving software process (e.g., for the sending software process to take an action); the sending software process provides information to the receiving software process (e.g., for the receiving software process to take an action); the sending software process requests an action from the receiving software process; or the sending software process provides information to the receiving software process about the action taken by the sending software process. In some cases, interaction with a device (e.g., using a user interface) will involve transmitting and / or receiving one or more API calls (e.g., multiple API calls) between multiple different software processes (e.g., different parts of an operating system, applications and operating systems, or different applications) via one or more APIs (e.g., via multiple different APIs). For example, when input is detected, direct sensor data is frequently processed into one or more input events, which are provided (e.g., via an API) to a receiving software process, which makes some determinations based on the input events and then (e.g., via an API) transmits information to the software process to perform an operation (e.g., change the device state and / or the user interface) based on the determinations. While the determinations and the operations performed in response can be made by the same software process, alternatively, the determinations can be made in a first software process and relayed (e.g., via an API) to a second software process different from the first software process, allowing the operation to be performed by the second software process. Alternatively, the second software process can relay instructions (e.g., via an API) to a third software process different from the first and / or second software processes to perform the operation. It should be understood that some or all user interactions with a computer system may involve one or more API calls within the steps of interacting with the computer system (e.g., between different software components of the computer system or between software components of the computer system and software components of one or more remote computer systems).It should be understood that some or all user interactions with a computer system may involve one or more API calls between steps of interaction with the computer system (e.g., between different software components of the computer system or between software components of the computer system and software components of one or more remote computer systems).

[0181] In some implementations, the application can be any suitable type of application, including one or more of the following: browser applications, applications used as execution environments for plugins, widgets or other applications, fitness applications, health applications, digital payment applications, media applications, social networking applications, messaging applications and / or map applications.

[0182] In some embodiments, the application is an application pre-installed on the first computer system at the time of purchase (e.g., a first-party application). In some embodiments, the application is an application provided to the first computer system via an operating system update file (e.g., a first-party application). In some embodiments, the application is an application provided via an app store. In some embodiments, the app store is pre-installed on the first computer system at the time of purchase (e.g., a first-party app store) and allows the download of one or more applications. In some embodiments, the app store is a third-party app store (e.g., an app store provided by another device, downloaded via a network, and / or read from a storage device). In some embodiments, the application is a third-party application (e.g., an application provided by an app store, downloaded via a network, and / or read from a storage device). In some embodiments, the application controls the first computer system to execute methods 700, 800, and / or 1000 by calling an application programming interface (API) provided by a system process using one or more parameters. Figure 7 , Figure 8 and / or Figure 10 ).

[0183] In some implementations, exemplary APIs provided by system processes include one or more of the following: pairing API (e.g., for establishing a secure connection, such as with an accessory), device detection API (e.g., for locating nearby devices, such as media devices and / or smartphones), payment API, UIKit API (e.g., for generating user interfaces), location detection API, locator API, map API, health sensor API, sensor API, messaging API, push notification API, streaming API, collaboration API, video conferencing API, app store API, advertising service API, web browser API (e.g., WebKit API), transportation API, networking API, WiFi API, Bluetooth API, NFC API, UWB API, fitness API, smart home API, contact transfer API, photo API, camera API, and / or image processing API.

[0184] In some embodiments, at least one API is a software module (e.g., a set of computer-readable instructions) that provides an interface allowing different modules (e.g., API calling module 3180) to access and use one or more functions, methods, procedures, data structures, classes, and / or other services provided by an implementation module of a system process. The API may define one or more parameters passed between the API calling module and the implementation module. In some embodiments, API 3190 defines a first API call that can be provided by API calling module 3180. An implementation module is a system software module (e.g., a set of computer-readable instructions) configured to perform operations in response to receiving an API call via the API. In some embodiments, the implementation module is configured to provide an API response (via the API) as a result of processing the API call. In some embodiments, the implementation module is included in a device (e.g., 3150) running an application. In some embodiments, the implementation module is included in an electronic device separate from the device running the application.

[0185] Now let’s turn our attention to the implementation of the user interface, which may be optionally implemented on, for example, a portable multifunction device 100.

[0186] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is illustrated. A similar user interface may optionally be implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof:

[0187] • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0188] • Time 404;

[0189] • Bluetooth indicator 405;

[0190] • Battery status indicator 406;

[0191] • Tray 408 features icons for frequently used applications, such as:

[0192] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 for the number of missed calls or voicemails;

[0193] ○ An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails;

[0194] ○ The icon 420 labeled "Browser" in browser module 147; and

[0195] ○ The video and music player module 152 (also known as the iPod (Apple Inc. trademark) module 152) is marked with an icon 422 labeled "iPod"; and

[0196] • Icons of other applications, such as:

[0197] ○The icon 424 of the IM module 141 marked as "Message";

[0198] ○The calendar module 148 has an icon 426 labeled "Calendar";

[0199] ○ The icon 428 of the image management module 144 is labeled "Photo".

[0200] ○ The icon 430 of camera module 143, which is labeled "camera";

[0201] ○ The icon 432 of the online video module 155, which is labeled "Online Video";

[0202] ○ The icon 434 labeled "Stock Market" in the Stock Market widget 149-2;

[0203] ○The icon 436 of the map module 154 that is labeled "map";

[0204] ○The weather widget 149-1 has icon 438 labeled "weather";

[0205] ○ The alarm clock widget 149-4 has an icon 440 labeled "clock";

[0206] ○ The icon 442 of the fitness support module 142 is labeled "fitness support";

[0207] ○ The icon 444 labeled "Memo" in the Memo module 153; and

[0208] ○ The icon 446, labeled "Settings," is used to set the settings of the device 100 and its various applications 136.

[0209] It should be pointed out that, Figure 4A The illustrated icon labels are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0210] Figure 4B An example is illustrated having a touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen 112)). Figure 3A Devices such as tablets or touchpads (e.g., 355) Figure 3A An exemplary user interface on the device 300. The device 300 may also optionally include one or more contact intensity sensors (e.g., one or more sensors in sensor 359) for detecting the intensity of contact on the touch-sensitive surface 451 and / or one or more haptic output generators 357 for generating haptic output for the user of the device 300.

[0211] While some examples of input are given below with reference to touchscreen 112 (which combines a touch-sensitive surface and a display), in some implementations, the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B The touch-sensitive surface 451 in the middle has a spindle (e.g., on the display 450) corresponding to the main axis on the display (e.g., Figure 4B The main shaft of 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., in the example). Figure 4B In the middle, contact 460 corresponds to 468 and contact 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B Contacts 460 and 462 in the middle). Thus, when the touch-sensitive surface (e.g., Figure 4B The touch-sensitive surface 451 in the middle) and the display of the multi-functional device (e.g., Figure 4BWhen the display (450) is separated, user input detected by the device on the touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may be used alternatively for other user interfaces described herein.

[0212] Additionally, while the examples below are given primarily with reference to finger input (e.g., finger touch, finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the touch). As another example, a tap gesture may optionally be replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0213] Figure 5A An exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include information about device 100 and device 300 (e.g., Figures 1A to 4B The device 500 may include some or all of the features described herein. In some embodiments, the device 500 has a touchscreen 504, referred to below as touchscreen 504. Alternatively, or in addition to touchscreen 504, the device 500 may also have a display and a touch-sensitive surface. Similar to the cases of devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) may optionally include one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to touches based on the intensity of the touch, meaning that touches of different intensities may invoke different user interface operations on device 500.

[0214] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying UserInterface Objects Corresponding to an Application,” published as WIPO Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” published as WIPO Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0215] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. 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, allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0216] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, device 500 may include information about... Figure 1A , Figure 1B and Figure 3ASome or all of the components described. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to touchscreen 504, which may have touch-sensitive component 522 and optionally have intensity sensor 524 (e.g., contact intensity sensor). Furthermore, I / O portion 514 may be connected to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may optionally be a rotatable input device or a pressable and rotatable input device. In some examples, input mechanism 508 may optionally be a button.

[0217] In some examples, the input mechanism 508 may optionally be a microphone. The personal electronic device 500 may optionally include 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.

[0218] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700 and 800. Figure 7 and Figure 8 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 examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0219] As used herein, the term "power indication" refers to the ability to indicate power in devices 100, 300, and / or 500 (…). Figure 1A , Figure 3A and Figures 5A to 5BA user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) may each constitute a display representation.

[0220] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other position marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3A The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the touchscreen, that particular user interface element is adjusted according to the detected input. This applies to touchscreens capable of enabling direct interaction with user interface elements on the touchscreen (e.g., ...). Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by a touch) 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, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen) that conveys the user's expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate that the user expects to activate the corresponding button (rather than other user interface elements shown on the device display).

[0221] As used in the specification and claims, the term "characteristic strength" of a contact refers to a characteristic of the contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on multiple strength samples. The characteristic strength may optionally be based on a predefined number of strength samples or a set of strength samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted, before or after contact begins to move, before contact ends, before or after contact strength is detected to increase, and / or before or after contact strength is detected to decrease). The characteristic strength of the contact may optionally be based on one or more of the following: the maximum value of the contact strength, the mean value of the contact strength, the average value of the contact strength, the value at the top 10% of the contact strength, the half maximum value of the contact strength, or the 90% maximum value of the contact strength, etc. In some embodiments, the duration of the contact is used when determining the characteristic strength (e.g., when the characteristic strength is the average value of the contact strength over time). In some implementations, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether a user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the characteristic intensity and one or more thresholds is used to determine whether one or more actions should be performed (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0222] As used herein, "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application using an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the computer system's operating system.

[0223] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application can optionally be any of the following types of applications:

[0224] • Active app, which is currently displayed on the screen of the device that is using the app;

[0225] • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and

[0226] • Suspended or hibernating applications that are not currently running but have state information stored in memory (either volatile or non-volatile) that can be used to resume the application's execution.

[0227] As used herein, the term "closed application" refers to a software application that does not retain state information (e.g., the state information of a closed application is not stored in the device's memory). Therefore, closing an application includes: stopping and / or removing the application's process and removing the application's state information from the device's memory. Generally, opening a second application while the first application is running does not close the first application. When the second application is displayed and the first application stops displaying, the first application becomes a background application.

[0228] As described herein, content is automatically generated by one or more computers in response to a request to generate content. The automatically generated content may optionally be generated on a device (e.g., at least in part by the computer system that received the request to generate content) and / or generated outside the device (e.g., at least in part by one or more nearby computers available via a local network or one or more computers available via the Internet). The automatically generated content may optionally include visual content (e.g., images, graphics, and / or video), audio content, and / or text content.

[0229] In some implementations, novel, automatically generated content produced via one or more artificial intelligence (AI) processes is referred to as generative content (e.g., generative images, generative graphics, generative videos, generative audio, and / or generative text). Generative content is typically generated by an AI process based on prompts provided to that AI process. The AI ​​process typically uses one or more AI models to generate output based on input. The AI ​​process may optionally include one or more preprocessing steps (e.g., adjusting user-provided prompts, creating system-generated prompts, and / or selecting AI models) to adjust the input before it is used by the AI ​​model to generate output. The AI ​​process may optionally include one or more postprocessing steps (e.g., passing the AI ​​model output to different AI models, scaling up, down, cropping, formatting, and / or adding or removing metadata) to adjust the AI ​​model output before it is used for other purposes (e.g., providing it to different software processes for further processing or presenting it to a user, for example, visually or aurally). The AI ​​process that generates generative content is sometimes referred to as a generative AI process.

[0230] Hints used to generate generative content may include one or more of the following: one or more words (e.g., natural language hindrances in written or spoken language), one or more images, one or more pictures, and / or one or more videos. AI processes may include machine learning models, which may include neural networks. Neural networks may include transformer-based deep neural networks, such as Large Language Models (LLMs). A generative pre-trained transformer model is an LLM that can efficiently generate novel generative content based on hindrances. Some AI processes use hindrances that include text to generate diverse generative text, generative audio content, and / or generative visual content. Some AI processes use hindrances that include visual content and / or audio content to generate generative text (e.g., transcriptions of audio and / or descriptions of visual content). Some multimodal AI processes use hindrances that include multiple types of content (e.g., text, images, audio, video, and / or other sensor data) to generate generative content. Hints may sometimes also include values ​​for one or more parameters indicating the importance of the various parts of the hindrance. Some tips include a structured set of instructions that the AI ​​process can understand, which includes wording, specified style, relevant context (e.g., starting content and / or one or more examples) and / or the role of the AI ​​process.

[0231] Generative content is typically based on a cue, but it is not deterministically selected from pre-generated content; rather, it is generated using the cue as a starting point. In some implementations, pre-existing content (e.g., audio, text, and / or visual content) is used as part of the cue for creating the generative content (e.g., pre-existing content is used as a starting point for creating the generative content). For example, the cue may request that a piece of text be summarized or rewritten in a different tone, and the output will be the generative text summarized or written in a different tone. Similarly, the cue may request that visual content be modified to include or exclude content specified by the cue (e.g., removing identified features from the visual content, adding features described in the cue to the visual content, changing the visual style of the visual content, and / or creating additional visual elements based on the visual content beyond its spatial or temporal boundaries). In some implementations, a random or pseudo-random seed is used as part of the cue for creating the generative content (e.g., random or pseudo-random seed content is used as a starting point for creating the generative content). For example, when generating images from a diffusion model, random noise patterns are iteratively denoised based on the cue to generate images based on the cue. While this article has described specific types of AI processes, it should be understood that a variety of different AI processes can be used to generate generative content based on prompts.

[0232] Now let’s turn our attention to the implementation of user interfaces (“UIs”) on electronic devices, such as portable multifunction devices 100, 300 or 500, and the associated processes.

[0233] Figures 6A to 6AD The figures illustrate user interfaces for displaying message summaries according to some implementation schemes. These user interfaces serve to illustrate the processes described below, including... Figure 7 and Figure 8 The process in.

[0234] exist Figure 6A At this location, device 600 (e.g., a laptop computer) displays a messaging application icon 604 and an email application icon 606 on display 601. In some embodiments, device 600 is a portable multifunction device 100, 300, and / or 500, or includes one or more features of such devices. In some embodiments, the messaging application icon 604 corresponds to a text messaging application for sending and / or receiving text messages (e.g., SMS messages, instant messaging (e.g., IM) and / or MMS messages). Figure 6A At this location, device 600 detects input 605a1 (e.g., mouse click, air gesture, and / or touch input) on input device 602 (e.g., a touch-sensitive surface) pointing to the messaging application icon 604. In response to detecting input 605a1, device 600 displays the messaging user interface 608, such as... Figure 6B As depicted. In Figure 6A At this point, device 600 detects input 605a2 pointing to the email application icon 606 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605a2, device 600 displays... Figure 6L The email user interface 632. It is worth noting that, although... Figures 6B to 6K and Figures 6AB to 6AD The user interface for text messaging is described and depicted, but it is for illustrative purposes only. About Figures 6B to 6K and Figures 6AB to 6AD The described technology is applicable to various communication application user interfaces, including written communication. Figures 6L to 6U and Figures 6V to 6AA The email user interface 632. Similarly, although Figures 6L to 6U and Figures 6V to 6AA The user interface for email messaging is described and depicted, but it is for illustrative purposes only. About Figures 6L to 6U and Figures 6V to 6AA The described technology is applicable to various communication application user interfaces, including written communication. Figures 6A to 6K and Figures 6AB to 6AD The message sending and receiving user interface 608.

[0235] exist Figure 6B At this location, the message sending and receiving user interface 608 includes an inbox interface 614 and a content interface 616. The inbox interface 614 includes messages 610a through 610g. In some embodiments, the inbox interface 614 includes information about the sender, receiver, and / or when the latest message was received. The content interface 616 includes the content of the selected message (and / or content from messages related to the message, such as content from related messages in the same message thread). A selection indicator 611 indicates that a message is selected for viewing. For example, message 610g is selected, as depicted in gray shading. The content interface 616 therefore includes the content 622g of message 610g. The message sending and receiving user interface 608 also includes a message composition area 618 configured to receive content to be sent as a message in response to device 600 detecting input pointing to the transmission enable display 619.

[0236] exist Figure 6B In this embodiment, the inbox interface 614 also includes an unread message indicator 612. In some implementations, device 600 conditionally displays the unread message indicator 612 based on whether a message is read or unread (e.g., opened and / or not opened). For example, device 600 displays the unread message indicator 612 at messages 610a to 610f in response to determining that messages 610a to 610f are unread. In response to detecting that message 610g is read (e.g., opened and / or read), device 600 does not display the unread message indicator 612 at message 610g.

[0237] exist Figure 6B At this location, device 600 displays a preview (e.g., "preview") of the content of a specific message or a summary (e.g., "summary") based on the content of the specific message. In some embodiments, the preview copies (e.g., mirrors and / or duplicates) the content of the message, while the summary summarizes the content of the message, such as regarding... Figure 6E Described in more detail. In some implementations, a summary (e.g., automatically generated text content and / or generative text content) is generated via machine learning algorithms (e.g., generative AI models and / or large language models). As described in more detail herein, device 600 conditionally displays the summary or preview based on the fulfillment of one or more conditions.

[0238] exist Figure 6BAt this point, messages 610a to 610c, 610e, and 610g respectively include previews 620a to 620c, 620e, and 620g. Previews 620a to 620c, 620e, and 620g each include a portion of the content of messages 610a to 610c, 610e, and 610g. In some embodiments, previews 620a to 620c, 620e, and 620g each include the beginning portion of the content of messages 610a to 610c, 610e, and 610g. For example... Figure 6B The description, preview 620g includes a portion of content 622g (e.g., “Thank you so much! I just received your gift…”).

[0239] exist Figure 6B At this point, device 600 displays summaries 624d and 624f of messages 610d and 610f, respectively. Summary 624d and summary 624f summarize the contents of messages 610d and 610f, such as regarding... Figure 6E A more detailed description follows. Device 600 also displays a summary indicator 625 to distinguish messages 610d and 610f from messages 610a to 610c, 610e, and 610g. Figure 6B At this location, the summary indicator 625 is a graphic element (e.g., a shape, icon, and / or logo) displayed adjacent to the text of summaries 624d and 624f, respectively. In some embodiments, the device 600 displays the summary indicator 625 by differentiating the appearance of the text of summaries 624d and 624f from the appearance of the text of previews 620a to 620c, 620e, and 620g (e.g., the text of summaries 624d and 624f has a different font color, font style, and / or size than the text of previews 620a to 620c, 620e, and 620g). Figure 6B At this point, device 600 detects input 605c (e.g., mouse click, air gesture, and / or touch input) on the scrolling inbox interface 614. In response to the detection of input 605c, device 600 displays effect 626 at messages 610d and 610f, such as... Figure 6C What is depicted.

[0240] exist Figure 6CAt the same time, device 600 displays effect 626 for messages 610d and 610f, but not for messages 610c, 610e, 610g, 610h, and 610i. In some embodiments, device 600 displays effect 626 (e.g., glow, outline, and / or highlight effects) at summaries 624d and 624f (e.g., text glow in summaries 624d and 624f), but not at previews 620b to 620c, 620e, 620g, 620h, and 620i (or any other visual emphasis). In some embodiments, effect 626 is an indication of what is being displayed as a summary. In some embodiments, device 600 displays effect 626 by showing at least a portion (e.g., some but not all, or all) of messages 610d and 610f having visual characteristics (e.g., color, animation, and / or brightness) different from the visual characteristics of messages 610c, 610e, 610g, 610h, and 610i. In some embodiments, device 600 displays different visual characteristics by modifying colors, displaying animation, and / or increasing the brightness of at least a portion of messages 610d and 610f. In some embodiments, effect 626 is an animation with visual characteristics that change gradually over time (e.g., the effect gradually changes position, pulses, and / or fades over time). Figure 6D At this point, device 600 detects input 605d directed at message 610c (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605d, device 600 displays the content 622c of message 610c in content interface 616, such as... Figure 6D As depicted. In some embodiments, effect 626 is color and / or brightness in high dynamic range (HDR) (e.g., rather than color and / or brightness in standard dynamic range (SDR)). In some embodiments, effect 626 has a wider dynamic range than a standard dynamic range (SDR) display. In some embodiments, dynamic range is a brightness range (e.g., the range between the brightest and darkest levels) and / or a color range (e.g., the range and / or variation of colors). In some embodiments, the maximum brightness of messages 610c, 610e, 610g, 610h, and 610i is less than the maximum brightness of effect 626. In some embodiments, the HDR visual effect has color and / or brightness that meet the guidelines defined by common HDR standards, including HDR10, HDR10+, Advanced HDR, and / or Dolby Vision.

[0241] exist Figure 6D At this point, device 600 does not display effect 626 at outlines 624d and 624f. In some implementations, effect 626 is not displayed when a triggering event is detected (e.g., Figure 6BAfter the scrolling input 605b, effect 626 is displayed for a threshold amount of time (e.g., 2 seconds, 5 seconds, and / or 10 seconds). In some embodiments, the triggering event is scrolling the messaging user interface 608. In some embodiments, the triggering event is opening the messaging application associated with the messaging user interface 608 and / or bringing the messaging user interface 608 to the foreground. In some embodiments, device 600 gradually stops displaying effect 626 over time (e.g., the colors of messages 610d and 610f gradually return to the colors that messages 610d and 610f would have without the effect, the animation begins to slow down until there is no animation, and / or the brightness of messages 610d and 610f begins to decrease until the brightness of messages 610d and 610f returns to the brightness that messages 610d and 610f would have without effect 626).

[0242] exist Figure 6D At this point, device 600 detects input 605d corresponding to a request to view the content of message 610d while displaying summary 624d (e.g., mouse click, air gesture, and / or touch input). In some embodiments, input 605d points to message 610d. In response to detecting input 605d, device 600 displays message sending and receiving user interface 608, such as... Figure 6E or Figure 6G What is depicted.

[0243] exist Figure 6E At this point, device 600 displays content 622d in content interface 616. For example... Figure 6EThe described summary 624d (“Maybe going cycling. Inviting you to come.”) summarizes content 622d (“I know you’ve been really busy lately, but I think exploring nature is good for us. Sorry I’ve been traveling so I haven’t been able to reply sooner. I might go cycling tomorrow. Let me know if you’re interested in cycling on some local trails.”). In some embodiments, summary 624d is an automatically generated summary (e.g., automatically generated text content and / or generative text content) based on message content 622d. In some embodiments, summary 624d is alphanumeric text (e.g., automatically generated text content and / or generative text content) generated via machine learning algorithms (e.g., diffusion models and / or large language models). In some embodiments, the automatically generated summary is generated by an artificial intelligence (AI) process (e.g., a generative AI model) that generates content consistent with content 622d (e.g., automatically generated text content and / or generative text content). In some embodiments, summary 624d is alphanumeric text that represents an overview of content 622d without copying (e.g., mirroring) the exact text in content 622d. In some implementations, the summary includes content based on the message's content, which (e.g., based on a set of criteria) is determined to be more important than the content of other messages within the message thread (e.g., rather than the recentity of the received message). In some implementations, summary 624d displays content determined to meet a threshold importance level, regardless of the content's position within the message (e.g., beginning, middle, and / or end). In some implementations, summary 624d is a summary from a specific perspective (e.g., a third-person perspective, rather than a first-person perspective) to distinguish the content of summary 624d from the content of the preview.

[0244] exist Figure 6E In some embodiments, device 600 displays a summary or preview of a message based on the amount of content in the message. As depicted, device 600 displays a summary 624d of message 610d and a preview 620c of message 610c. In some embodiments, device 600 displays summary 624d when content 622d includes a threshold amount of content (e.g., content 622d includes more than 5, 10, and / or 15 words, and / or content 622d includes 20, 30, and / or 50 alphanumeric characters). In some embodiments, the amount of content 622c (e.g., as shown in the image) is... Figure 6D The amount depicted did not exceed the threshold amount of the content, and therefore did not trigger a summary. In some implementations, the amount of content 622d (e.g., as...) Figure 6E The amount depicted exceeded the threshold of the content, and thus triggered the summary.

[0245] exist Figures 6E to 6FAt this point, device 600 stops displaying summary 624d and instead displays preview 620d. In some embodiments, in response to detecting that message 610d is in a read state (e.g., not in an unread state), device 600 replaces summary 624d with preview 620d. Figure 6E At this point, message 610d is in an unread state, as illustrated by unread message indicator 612. In some embodiments, after detecting input of navigation leave content 622d and / or message 610d, device 600 updates the state of message 610d from unread to read. For example, in Figure 6E At this point, device 600 detects input 605e (e.g., mouse click, air gesture, and / or touch input) pointing to message 610c. In response to detecting input 605e, device 600 displays... Figure 6F The message sending and receiving user interface 608. In some embodiments, after detecting input navigating to content 622d and / or message 610d (e.g., input 605e), device 600 updates the status of message 610d from unread to read. In some embodiments, in response to detecting input navigating to content 622d and / or message 610d (e.g., input 605e), device 600 stops displaying summary 624d and instead displays preview 620d.

[0246] exist Figure 6F At this point, device 600 selects message 610c and displays content 622c in content interface 616. Furthermore, message 610d has been switched to a read state. For example, device 600 no longer displays the unread message indicator 612 for message 610d. In response to detecting that message 610d is in a read state, device 600 displays preview 620d in the position previously occupied by summary 624d. As depicted, preview 620d includes content different from the content of summary 624d (e.g., text and / or other content). The content of preview 620d is an exact copy of the beginning of content 622d (e.g., “I know you’ve been really busy lately…”), while the content of summary 624d includes content that is not copied from a portion of content 622d. Device 600 has also stopped displaying the summary indicator 625 for message 610d because summary 624d is no longer displayed.

[0247] exist Figure 6G At that location, equipment 600 is in contact with Figures 6E to 6F The different times depicted in the figures, or in a different manner than those depicted in these figures, replace the summary 624d with preview 620d. In response to detection... Figure 6D Input 605d, device 600 display Figure 6G The message sending and receiving user interface 608. Figure 6GAt this point, device 600 displays a preview 620d of message 610d instead of a summary 624d. In some embodiments, in response to input 605d selecting message 610d, message 610d changes from an unread state to a read state. As depicted, device 600 does not display the summary indicator 625 for message 610d, nor does it display the unread message indicator 612 for that message. Notably, device 600 maintains the display of a summary 624f for message 610f because message 610f remains in an unread state. Figure 6G As depicted, device 600 maintains an unread message indicator 612 and a summary indicator 625 for display message 610f.

[0248] exist Figures 6H to 6J At this point, device 600 detects that multiple messages have been received within a threshold time period, and that these multiple messages are part of the same message thread. In response, device 600 displays a summary. Figure 6H At this point, device 600 displays the first message 610j1 with preview 620j1. For example... Figure 6H As depicted, device 600 displays a first message 610j1 with a timestamp 628, indicating that message 610j1 was received at 11:09 PM. The first message 610j1 also includes an indication 629 to the sender (e.g., "Chelse"). Device 600 also displays the first message 610j1 with an unread message indicator 612. In some embodiments, device 600 detects the content of the first message 610j1 (e.g., Figure 6K The amount of content 622j1 does not exceed the threshold amount of content, and in response, a summary of the first message 610j1 is not displayed.

[0249] exist Figure 6I Location, self-display Figure 6J A certain amount of time has elapsed since the message sending and receiving user interface 608 was accessed, and device 600 has detected that a second message 610j2 has been received. The second message 610j2 is part of the same message thread as the first message 610j1. In some implementations, when a new message is associated with a previous message sent by a sender to the user of device 600 (e.g., a reply to that previous message and / or a message sent in addition to that previous message), multiple messages are identified as being part of the same message thread (e.g., such as...). Figure 6KAs depicted in the content interface 616, where contents 622j1, 622j2, and 622j3 are part of the same session between the user of device 600 and Chelse. In some embodiments, device 600 determines that the second message 610j2 is part of a message thread based on information associated with the first message 610j1 and the second message 610j2 (e.g., metadata, headers, and / or recipient lists), indicating that the first message 610j1 and the second message 610j2 are part of the same message thread. Device 600 displays the second message 610j2 with a preview 620j2 (e.g., “I want to show you my new car”), without displaying a summary of the second message 610j2. In some embodiments, device 600 determines the content of the second message 610j2 (e.g., ...). Figure 6K The content of the second message 610j2 does not exceed a certain threshold, and in response, no summary of the second message 610j2 is displayed. Device 600 receives the second message 610j2 within one minute of the first message 610j1, such as... Figure 6J The timestamp 628 (e.g., "11:10 p.m.") and Figure 6I The timestamp 628 (e.g., "11:09 PM") indicates this. Furthermore, the second message 610j2 originates from the same sender as the first message 610j1, as depicted in instruction 629 (e.g., "Chelse").

[0250] exist Figure 6J Location, self-display Figure 6I A certain amount of time has elapsed since the message sending and receiving user interface 608 was accessed, and device 600 has detected that a third message 610j3 has been received. The third message 610j3 is part of the same message thread as the first message 610j1 and the second message 610j2. Device 600 displays the third message 610j3 with a summary 624j (e.g., "Invited to go cycling. She said she'd bring lunch."). In some implementations, device 600 determines that a threshold number of messages (e.g., 2, 4, and / or 5) have been received, and in response, displays a summary of the third message 610j3. It is worth noting that even the content of the third message 610j3 (e.g., Figure 6K The content (622j3) does not exceed the content threshold, and device 600 does not display a preview of the third message 610j3. For example... Figure 6JThe third message 610j3 is received within two minutes of the first message 610j1 and one minute of the second message 610j2, as indicated by the timestamp 628 (e.g., "11:11 PM"). In some embodiments, device 600 detects that the third message 610j3 is received within a threshold amount of time that the first message 610j1 was received (and / or in some embodiments, within a threshold amount of time that the second message 610j2 was received), and displays summary 624j in response. In some embodiments, device 600 determines that the first message 610j1 and the second message 610j2 are unread, and displays summary 624j of the third message 610j3 in response. In some embodiments, device 600 determines that only one of these conditions and / or a combination of these conditions are met. For example, in some embodiments, device 600 detects that a threshold number of messages are part of the same thread, and displays summary 624j in response. In some implementations, device 600 displays summary 624j independently of detecting that a third message 610j3 has been received within a threshold amount of time that the first message 610j1 and / or the second message 610j2 were received. As another example, in some implementations, device 600 determines that the threshold number of messages are part of the same thread and, in response, displays summary 624j independently of the first message 610j1 and / or the second message 610j2 being unread. Figure 6J At this point, device 600 detects input 605j directed at the third message 610j3 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605j, device 600 displays... Figure 6K The message user interface 608.

[0251] exist Figure 6K In this context, device 600 displays the content of the message thread in content interface 616. For example, device 600 displays the content 622j1 of the first message 610j1, the content 622j2 of the second message 610j2, and the content 622j3 of the third message 610j3 in content interface 616. Figure 6K The device 600 depicts the content of messages in the message thread, excluding content 622j1, content 622j2, and content 622j3. Figure 6K In response to detecting a third selection message 610j3 (e.g., in response to input 605j), device 600 displays preview 620j3 instead of summary 624j. In some embodiments, device 600 replaces summary 624j with preview 620j3 in response to detecting input 605j.

[0252] exist Figure 6L At that point, in response to detecting input 605a2 pointing to the email application icon 606, such as Figure 6A As depicted, device 600 displays an email user interface 632. The email user interface 632 includes an inbox interface 614 and a content interface 616. Figures 6L to 6U The inbox interface 614 and the content interface 616 are similar Figures 6A to 6K The device 600 displays an inbox interface 614 and a content interface 616, but with different states. For example, the device 600 displays... Figures 6A to 6K When a summary similar to the one described in the text is displayed, device 600 displays the summary independently of whether the message is in a read state, such as messages 610m to 610n depicted by device 600 having summaries 624m to 624n and a summary indicator 625 but not an unread message indicator 612. Figure 6L At this point, messages 610l and 610o to 610q include previews 620l and 620o to 620q based on certain conditions (e.g., the content amount of the corresponding message does not exceed a threshold amount of content, and / or the summary is not available for the corresponding message).

[0253] exist Figure 6L At this location, device 600 displays content 622k1-1 based on message 610k1 (e.g., in...). Figure 6R The message 610k1, depicting a summary 624k1 (e.g., “Asking if anyone has a place to stay.”) in the inbox interface 614, includes an indication 637 to the sender (e.g., “Travis”) and is in an unread state, as depicted by the new message indicator 612. The message 610k1 includes an indication 639 to the email subject, which is separate from the summary 624k1. In some embodiments, device 600 detects input 605l directed at message 610k1 (e.g., mouse click, air gesture, and / or touch input). In such embodiments, device 600 displays the content of message 610k1 (e.g., Figure 6R The content of 622k1) and / or update message 610k1 to be read.

[0254] exist Figure 6M At this point, a certain amount of time has passed, and device 600 displays a new message, message 610k2, which is part of the same message thread as message 610k1. Message 610k2 includes an indication 637 to the sender (e.g., "Matt") and is in an unread state, as depicted by unread message indicator 612. Device 600 displays a portion of the content 622k2 of a copy of message 610k2 (e.g., in...). Figure 6R The preview 620k2 (described in the content interface 616) is shown in the content interface. Figure 6MIn some implementations, device 600 displays preview 620k2 instead of a summary when one or more conditions are met. For example, in some implementations, device 600 determines that an email user interface 632 is currently being displayed and, in response, abandons displaying a summary of message 610k2. In some implementations, device 600 determines that a summary has not been generated and / or is unavailable for display within a threshold time period (e.g., 5 seconds, 10 seconds, and / or 30 seconds) and, in response, displays preview 620k2. In some implementations, device 600 displays preview 620k2 until device 600 detects that a triggering event has occurred (e.g., the application has been closed and / or moved to the background). In some implementations, device 600 displays preview 620k2 even if a summary has been generated and / or is available for display. Figure 6M At this point, device 600 detects input 605m pointing to the music application icon 633 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605m, device 600 displays the music user interface 634 of the music application associated with the music application icon 633.

[0255] exist Figure 6N At this location, device 600 displays a music user interface 634. Device 600 prioritizes displaying the music user interface 634 relative to the display of the email user interface 632, as depicted where the music user interface 634 obscures a portion of the email user interface 632. In some embodiments, device 600 operates the music application in the foreground while simultaneously operating the email application in the background. In some embodiments, in response to detecting input 605m, device 600 moves the email application from foreground operation to background operation. Figure 6N At this point, device 600 detects input 605n directed at email user interface 632 (e.g., mouse click, air gesture, and / or touch input). In response to the detection of input 605n, device 600 prioritizes displaying email user interface 632 over music user interface 634.

[0256] exist Figure 6O In some embodiments, device 600 prioritizes displaying email user interface 632 over music user interface 634, as depicted where email user interface 632 obscures a portion of music user interface 634. In some implementations, in response to detecting input 605n, device 600 moves the email application from background operation to foreground operation. In such implementations, in response to detecting input 605n, device 600 moves the music application from foreground operation to background operation.

[0257] exist Figure 6OAt this point, device 600 displays summary 624k2 but not preview 620k2. Summary 624k2 is based on the content of two different messages from two different senders. Device 600 displays message 610k2, which is part of the same message thread as message 610k1. Summary 624k2 (e.g., “Inquiring if anyone has accommodation. Indicates 1 place to stay is available.”) is based on content 622k1 and content 622k2, which are in... Figure 6R The description is as follows. It is worth noting that summary 624k2 differs from summary 624k1 (e.g., summary 624k2 indicates "1 place to stay" is available). Summary 624k2 is displayed in the position previously occupied by preview 620k2. Device 600 also displays a summary indicator 625 for message 610k2. In some embodiments, device 600 displays summary 624k2 in response to detecting that: the email application has been closed at a time after the time message 610k2 was received; a user interface different from the email user interface 632 takes precedence over the email user interface 632 at a time after the time message 610k2 was received; and / or the email application has been closed and / or moved to background operation at a time after the time message 610k2 was received. In some embodiments, device 600 detects input 605o directed at message 610k2 (e.g., mouse click, air gesture, and / or touch input). In such embodiments, device 600 displays the content of message 610k2 (e.g., Figure 6R The content 622k2) and / or update message 610k2 to be in a read state. In some implementations, summary 624k2 is based on the content of two different messages from the same sender.

[0258] exist Figure 6P At this point, a certain amount of time has passed, and device 600 displays a summary 624k3-1 based on the content of three different messages from three different senders. Message 610k3-1 is part of the same message thread as messages 610k1 and 610k2. Message 610k3 includes an indication 637 to the sender (e.g., "Aaron") and is in an unread state, as depicted by unread message indicator 612. Device 600 displays summary 620k3-1 (e.g., "Inquiring if anyone has accommodation. Indicates 2 accommodations available."), which is based on content 622k1, content 622k2, and content 622k3, which... Figure 6R The description is as follows. It is worth noting that summary 620k3-1 differs from summaries 624k1 and 624k2 (e.g., summary 624k3-1 indicates "2 accommodations" are available). In some embodiments, summary 624k3-1 is based on the content of three different messages, where at least two of these messages originate from the same sender.

[0259] exist Figure 6Q In some embodiments, device 600 displays summary 624k3-2, which is similar to summary 624k3-1 but has different states. Summary 624k3-2 includes instructions for the transmitter in its content, while summary 624k3-1 does not include instructions for the transmitter. For example, summary 624k3-2 includes instructions 636a (e.g., “Travis”), instructions 636b (e.g., “Matt”), and instructions 636c (e.g., “Aaron”). In some embodiments, instructions 636a, 636b, and 636c are consistent with the instructions for the transmitter included in the transmitter field (e.g., ...). Figure 6P Indicator 637 is separate from and / or independent of the indication. Furthermore, indications 636a, 636b, and 636c are displayed with visual characteristics (e.g., color, bold, underline, and / or shape) that differ from the visual characteristics of the rest of the content 624k3-2, such as indications 636a, 636b, and 636c being underlined while the rest of the content 624k3-2 is not depicted by the underline. Indicators 636a, 636b, and 636c also identify which part of the content summary 624k3-2 is associated with each sender. Device 600 detects input 605q directed at message 610k3 (e.g., mouse click, air gesture, and / or touch input). In response to the detection of input 605q, device 600 displays the content of message 610k3, such as... Figure 6R What is depicted.

[0260] exist Figures 6R to 6T In this context, device 600 displays different summaries based on whether a specific message in the message thread is in a read state. In some implementations, device 600 displays a summary of the content of unread messages and does not display a summary of the content of read messages. Figures 6R to 6T At this location, device 600 displays the content 622k3 of message 610k3. Content 622k3 includes content 622k1 corresponding to the content of message 610k1, content 622k3-2 corresponding to the content of message 610k2, and content 622k3 corresponding to the content of message 610k3. In some embodiments, content 622k1, content 622k2, and content 622k3 are derived from messages 610k1, 610k2, and 610k3, respectively. Figures 6R to 6TIn some implementations, device 600 displays content 622k1, content 622k2, and content 622k3 in a panel. In some implementations, device 600 does not display content 622k1, content 622k2, and / or content 622k3 in a panel. In some implementations, device 600 displays content 622k1, content 622k2, and / or content 622k3 as continuous text (e.g., as part of the body of an email).

[0261] exist Figure 6R At this point, device 600 displays summary 624k3-2, which includes a summary of the content based on three unread messages from the message thread. Status indicator 640 indicates whether a specific message within the message thread was read or unread when the summary was generated. In some embodiments, device 600 does not display status indicator 640. Status indicator 640 indicates that messages 610k1, 610k2, and 610k3 were in and / or were previously in an unread state when the summary was generated. In response to determining that messages 610k1, 610k2, and 610k3 were in an unread state, device 600 displays summary 624k3-2 based on the content from messages 610k1, 610k2, and 610k3. Figure 6R As depicted, summary 624k3-2 includes a summary of content associated with content 622k1 from message 610k1 (e.g., "Travis wants to finalize the plan"). Summary 624k3-2 includes a summary of content associated with content 622k2 from message 610k2 (e.g., "Matt has a place to stay"). Summary 624k3-2 includes a summary of content associated with content 622k3 from message 610k3 (e.g., "Aaron has a place to stay"). In some embodiments, summary 624k3-2 is based on the original content from messages 610k1, 610k2, and 610k3. In some embodiments, summary 624k3-2 is based on content from a previously received email, wherein the content of the previously received email has been incorporated into the content of the newly received message (e.g., in the body of the new message's email). In some embodiments, status indicator 640 indicates that messages 610k1, 610k2, and / or 610k3 are detected by device 600. Figure 6P The state of the time shortly before the input of message 610k3 (e.g., exactly shortly before the action) and / or the time when the summary was initially displayed.

[0262] exist Figure 6SAt this point, device 600 displays a summary 624k3-3 based on the content of two unread messages from the message thread. Status indicator 640 indicates that message 610k1 is in a read state, while messages 610k2 and 610k3 are in an unread state. In response to detecting that message 610k1 is in a read state while messages 610k2 and 610k3 are in an unread state, device 600 displays a summary 624k3-3 based on the content from messages 610k2 and 610k3, but not based on the content from message 610k1. (As...) Figure 6S The described summary 624k3-3 does not include summary content associated with content 622k1 from message 610k1 (e.g., "Travis wants to finalize the plan"). Summary 624k3-3 includes summary content associated with content 622k2 from message 610k2 (e.g., "Matt has a place to stay"). Summary 624k3-3 includes summary content associated with content 622k3 from message 610k3 (e.g., "Aaron has a place to stay").

[0263] exist Figure 6T At this point, device 600 displays a summary 624k3-4 based on the content of an unread message from a message thread. Status indicator 640 indicates that messages 610k1 to 610k2 are in a read state, while message 610k3 is in an unread state. In response to detecting that messages 610k1 to 610k2 are in a read state and message 610k3 is in an unread state, device 600 displays a summary 624k3-4 based on the content of message 610k3, but not on the content of messages 610k1 to 610k2. Figure 6T As depicted, summary 624k3-4 does not include content associated with content 622k1 from message 610k1 (e.g., "Travis wants to finalize the plan"). Summary 624k3-4 does not include content associated with content 622k2 from message 610k2 (e.g., "Matt has a place to stay"). Summary 624k3-4 includes content associated with content 622k3 from message 610k3 (e.g., "Aaron has a place to stay"). In some embodiments, device 600 maintains the display of summary 624k3-4 when message 610k3 has been read (e.g., after the user opens message 610k3). In such embodiments, device 600 displays summary 624k3-4 independently of message 610k3 being in a read state.

[0264] exist Figure 6TAt this point, device 600 displays a summary setting 638. Device 600 detects that the summary setting 638 is activated (e.g., enabled and / or turned on), and in response, displays summaries 624k3-4, 624l, and 624m. In some embodiments, the summary setting 638 is displayed in a user interface different from the email user interface 632. In some embodiments, device 600 is based on the summary setting (e.g., similar to...). Figure 6T The display summary setting (638) is activated to conditionally display... Figures 6A to 6K The summary is displayed in the message sending and receiving user interface 608. Device 600 detects input 605t (e.g., mouse click, air gesture, and / or touch input) pointing at the summary settings 638. In response to the detection of input 605t, device 600 does not display (e.g., removes and / or stops displaying) summaries 624k3-4, 624l, and 624m, as shown. Figure 6U What is depicted.

[0265] exist Figure 6U At this point, device 600 detects that display summary setting 638 is disabled (e.g., disabled and / or not turned on). In response to detecting that display summary setting 638 is disabled, device 600 displays previews 620k3, 620l, and 620m of messages 610k3, 610l, and 610m, respectively. Figure 6U As depicted, device 600 does not display summaries 624k3-4, 624l, and 624m. Furthermore, device 600 does not display the summary indicator 625 for messages 610k3, 610l, and 610m.

[0266] exist Figures 6V to 6X In response to a detected request to display a summary, device 600 displays summaries of multiple messages in content interface 616. Device 642 is similar to device 600. Device 642 includes one or more features of device 600 and / or portable multifunction devices 100, 300 and / or 500. Device 642 displays an email user interface 632 on display 643. The email user interface 632 is similar to... Figures 6L to 6U The email user interface is 632, but it has a different state.

[0267] exist Figure 6V At this point, device 642 displays messages 610n, 610o, 610p1, and 610q. Device 642 displays summaries 624n, 624o, and 624q1 of messages 610n, 610o, and 610q, respectively. Device 642 also displays a preview 620p of message 610p. In some embodiments, in response to determining that one or more conditions are met, device 642 displays summaries 624n, 624o, and 624q1 of messages 610n, 610o, and 610q (e.g., instead of a preview), as described herein. Figures 6A to 6U As described. In some embodiments, in response to determining that one or more conditions are met, device 642 displays a preview 620p of message 610p1 (e.g., "11:00 PM"). For example, in some embodiments, in response to determining the content of message 610p1 (e.g., Figure 6X The content (622p1) does not exceed the content threshold amount, and device 642 displays a preview of 620p (e.g., "11:00 PM"). Figure 6V At this point, device 642 detects input 605v1 directed at message 610p1 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605v1, device 642 displays the content 622p1 of message 610p1, such as... Figure 6W As depicted. In Figure 6V At this point, device 642 detects input 605v2 directed at message 610q (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605v2, device 642 displays the content 622q of message 610q, such as... Figure 6Z What is depicted.

[0268] exist Figure 6W At this point, device 642 displays the message thread of message 610p1 in the content interface 616 of email user interface 632. The message thread of message 610p1 includes contents 622p1 to 622p4. For example... Figure 6W As depicted, device 642 does not display a summary of message 610p and / or a summary of content 622p1 to 622p4. In some embodiments, email user interface 632 includes a summary display 644. In some embodiments, the summary display 644 displays a summary of the message thread when selected. In some embodiments, the summary is based on the content from unread messages, not on read messages, such as those about... Figures 6R to 6T As described. In some implementations, the summary is based on the content of messages from the message thread and is independent of whether a particular message in the message thread is in an unread and / or read state. Figure 6W At this point, device 642 detects input 605w1 pointing at summary display 644 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605w1, device 642 displays summary 624p1, such as... Figure 6X As depicted. In Figure 6W In some embodiments, device 642 detects input 605w2 (e.g., mouse click, air gesture, and / or touch input) pointing to return indication display 648. In such embodiments, in response to the detection of input 605w2, device 642 displays inbox interface 614.

[0269] exist Figure 6X At this point, device 642 displays summary 624p1 in content interface 616. In some embodiments, summary 624p1 is based on content 622p1 to 622p4. In some embodiments, summary 624p1 includes a summary of content from at least one of content 622p1, content 622p2, content 622p3, and / or content 622p4. In some embodiments, device 642 modifies the position of content 624p1 to 624p4 to display summary 624p1. Figure 6X As depicted, device 642 displays content 624p1 to 624p4 below summary 624p1. In some embodiments, summary 624p1 is generated in response to the detection of input 605w1 (e.g., at device 642 and / or a device other than device 642). In some embodiments, device 642 displays summary enablement representation 644 with different visual characteristics (e.g., color, shape, and / or animation) to indicate that a summary is being generated. Device 642 also displays a hidden summary enablement representation 646, which, when selected, causes device 642 to stop displaying summary 624p1. For example, in some embodiments, device 642 detects input 605x1 pointing to the hidden summary enablement representation 646 (e.g., mouse click, air gesture, and / or touch input). In such embodiments, in response to the detection of input 605x1, device 642 displays content 624p1 to 624p4 below the hidden summary enablement representation 641. Figure 6W The content interface is similar to 616. In some implementation schemes, in Figure 6X At this point, device 642 detects input 605x2 pointing to the return indication display 648 (e.g., mouse click, air gesture, and / or touch input). In such embodiments, in response to detecting input 605x2, device 642 displays inbox interface 614.

[0270] exist Figure 6Y At that point, device 642 displays summary 624p2, instead of... Figure 6V A preview of 620p. In some embodiments, when the content of a corresponding message is determined to be relevant to the content of another message in a message thread, device 642 displays a summary or preview of the corresponding message. In some embodiments, device 642 determines that the content of one message is relevant to the content of another message based on the content of different messages exceeding a relevance threshold level. In some embodiments, the content of a message is determined to exceed a relevance threshold level when the content of a message answers a question from a different message. In some embodiments, device 642 determines that the content exceeds a relevance threshold when the content of a message is incomplete and / or lacks information included in the content from a different message. Figure 6WAs depicted, message 610p includes content 622p1 (e.g., "11:00 PM"). In some embodiments, device 642 determines that content 622p1 is related to the content of a previous message (e.g., content 622p2, content 622p3, and / or content 622p4). In response to determining that content 622p1 is related to the content of a previous message, device 642 displays summary 624p2 (e.g., "Your flight departs at 11:00 PM, booking number #124AB"), as... Figure 6Y What is depicted.

[0271] exist Figure 6Y In some embodiments, the summary displayed in the inbox interface 614 differs from the summary displayed in the content interface 616. In some embodiments, device 642 detects input 605y (e.g., mouse click, air gesture, and / or touch input) pointing to message 610p1, which includes summary 624p2. In such embodiments, in response to detecting input 605y, device 642 displays a summary in the content interface that is different from the summary displayed in the content interface. Figure 6X A summary similar to summary 624p1 in the content interface 616. In such embodiments, a summary displayed in the content interface in response to device 600 detecting input 605y is automatically displayed (e.g., instead of summary 624p1, which is displayed in response to detecting a request to display a summary and / or in response to device 600 detecting input 605w1). In some embodiments, the summary displayed in the content interface 616 differs from the summary displayed in the inbox interface 614 (e.g., including more general information than the summary displayed in the inbox interface, including a more detailed summary than the summary displayed in the inbox interface, including less general information than the summary displayed in the inbox interface, and / or including a less detailed summary than the summary displayed in the inbox interface).

[0272] exist Figure 6Z At the location, in response to detection Figure 6V Input 605v2, device 642 displays content 622q. In Figure 6Z At this location, device 642 displays content 622q but not a summary. Figure 6Z At this point, device 642 detects input 605z pointing at summary display 644 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605z, device 642 displays summary 624q2, such as Figure 6AA What is depicted.

[0273] exist Figure 6AAAt this point, device 642 displays summary 624q2 in content interface 616. As depicted, summary 624q2 differs from summary 624q1 (e.g., including more general information and / or a more detailed summary than the latter). In some embodiments, summary 624q2 is identical to summary 624q1.

[0274] exist Figures 6AB to 6AD At this point, device 642 displays a preview after displaying the content of the message associated with the summary. Figures 6AB to 6AC At this point, device 642 displays the message sending and receiving user interface 608. Figures 6AB to 6AD The message sending and receiving user interface 608 is similar to Figures 6A to 6L The message sending and receiving user interface 608 has different states. Figures 6AB to 6AD The inbox interface 614 and the content interface 616 are similar Figures 6A to 6L The inbox interface 614 and the content interface 616 have different states.

[0275] exist Figure 6AB At this point, device 642 displays message 610r and summary 624r based on content 622r (e.g., such as...). Figure 6AC (As depicted). In Figure 6AB At this location, device 642 also displays a summary indicator 625 and an unread message indicator 612. Device 642 detects input 605ab directed at message 610r (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605ab, device 642 displays the content 622r of message 610r, such as... Figure 6AC What is depicted.

[0276] exist Figure 6AC In this configuration, device 642 displays content 622r in content interface 616, but not inbox interface 614 (and / or summary 624r). Figure 6AC At this point, device 642 detects input 605ac pointing to the return indication display 648 (e.g., mouse click, air gesture, and / or touch input). In response to detecting input 605ac, device 642 displays the inbox interface 614, such as... Figure 6AD What is depicted.

[0277] exist Figure 6AD At this point, device 642 displays a preview 620r of message 610r and content 622r, but not a summary 624r. Furthermore, device 642 does not display the summary indicator 625 and / or the unread message indicator 612.

[0278] Figure 7This is a flowchart illustrating a method for displaying a summary of a message using a computer system, according to some implementation schemes. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600 and / or 642) (e.g., a smartphone, smartwatch, tablet computer, laptop computer, desktop computer, wearable device and / or head-mounted device), which communicates with display generating components (e.g., 601 and / or 643) (e.g., a display, touchscreen display, monitor, holographic display system and / or head-mounted display system) and one or more input devices (e.g., 602 and / or 643) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); a mouse; a keyboard; a remote control; a visual input device (e.g., one or more cameras (e.g., an infrared camera, a depth camera, a visible light camera and / or a gaze-tracking camera)); an audio input device (e.g., a microphone); a biometric sensor (e.g., a fingerprint sensor, a facial recognition sensor, a gaze-tracking sensor and / or an iris recognition sensor); and / or one or more mechanical input devices (e.g., a pressable input mechanism; a button; a rotatable input mechanism; a crown; and / or a dial)). Some operations in method 700 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0279] As described below, method 700 provides an intuitive way to display message summaries. This method reduces the cognitive burden on users when viewing messages and / or message summaries, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to view messages and / or message summaries more quickly and efficiently saves power and increases the time interval between battery charging.

[0280] The computer system displays (702) (e.g., for a communication application) a first user interface (e.g., 608, 614, and / or 632) via a display generation component, including: displaying (704) content (e.g., text and / or written content) based on a first message (e.g., 610d, 610e, 610j1 to 610j3, 610k1, 610k2, and / or 610k3) (e.g., text message and / or email ...). A summary of content generated (e.g., 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p2 and / or 624r) (e.g., a text and / or graphical summary of one or more messages; an automatically generated summary (e.g., a summary including automatically generated text content and / or a summary including generative text content); and / or a summary generated without user input). In some embodiments, displaying a first user interface includes: abandoning the display of the summary based on determining that a first set of criteria is not met. In some embodiments, the summary is generated via one or more machine learning algorithms (e.g., automatically) (e.g., the summary includes automatically generated text content and / or the summary includes generative text content). When displaying a summary of the content based on the first message, the computer system detects (706) a request to display the first message (e.g., 605d, 605j, 605l, 605o, 605p, 605q, 605v2, 605y, and / or 605ab) via one or more input devices (e.g., a request to open the first message and / or a request to update the message viewing pane to display the content from the selected message). In some embodiments, the request to display the first message includes: detecting input pointing to a representation of the first message (or optionally, input pointing to a summary). In response to detecting the request to display the first message, the computer system displays (708) the first message (e.g., the content of the message is displayed in a content interface 616, such as...) via a display generation component (e.g., in a second user interface different from the first user interface). Figure 6E , Figure 6G , Figure 6K , Figure 6R , Figure 6S , Figure 6T , Figure 6Z and / or Figure 6AC(As depicted). In some embodiments, in response to detecting a request to display the content of the first message, the computer system displays content of the first message that was not displayed when the summary was shown. In some embodiments, a summary based on the content of the first message is displayed, without displaying a preview of the content of the first message. In some embodiments, the preview of the content of the first message is different from (e.g., excluding) the subject line associated with the first message, instructions to the sender, and / or time. After the first message is displayed (e.g., after the content of the message is displayed in content interface 616, such as...), Figure 6E , Figure 6G , Figure 6K , Figure 6R , Figure 6S , Figure 6T , Figure 6Z and / or Figure 6AC As depicted), the computer system displays (710) a first user interface via a display generation component, including displaying at least a portion (e.g., some but not all, or all) of the content of a first message (e.g., 620d, 620j3, 620k2, 620k3 and / or 620r) (in some embodiments, for preview) without displaying a summary (e.g., displaying 620d, 620j3, 620k2, 620k3 and / or 620r without displaying a summary, such as...). Figure 6F , Figure 6K , Figure 6M , Figure 6U , Figure 6AD (As depicted) (e.g., after the first message has been opened and / or viewed, the summary is replaced by a preview of the first message). In some embodiments, the computer system concurrently displays the summary and an indication that the first message is a new message. In some embodiments, after displaying the first message, the computer system displays a portion of the content of the first message without displaying an indication that the first message is a new message (e.g., because the first message has been opened). Detecting a request to display the first message while displaying the first user interface includes: conditionally displaying a summary based on the content of the first message when a first set of criteria is met; and, in response, displaying the first message; and displaying the first user interface after displaying the first message, including displaying at least a portion of the content of the first message without displaying the summary, which performs the operation when a set of conditions has been met without requiring further user input, keeps the user interface clean, provides conditional display of the summary, and provides improved visual feedback about the first message having been displayed.

[0281] In some implementations, displaying the first message includes: the computer system displaying the first message in a second user interface (e.g., 616) that is different from the first user interface, without displaying a summary (e.g., in...) in the second user interface. Figure 6E , Figure 6K , Figure 6R , Figure 6S , Figure 6T , Figure 6Z and Figure 6AC In this implementation, summaries 624d, 624j, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624q1, and 624r are not displayed in content interface 616 (e.g., even if the summaries are available and / or have been generated, they are not displayed in the second user interface). In some embodiments, the second user interface is displayed instead of the first user interface. In some embodiments, the second user interface is displayed concurrently with the first user interface. In some embodiments, the second user interface includes summaries. Detecting a request to display the first message while the first user interface is displayed includes: conditionally displaying a summary based on the content of the first message when a first set of criteria is met; and, in response, displaying the first message in a second user interface different from the first user interface, which reduces the amount of input required to perform the operation, provides conditional display of the summary, and keeps the user interface tidy.

[0282] In some implementations, displaying the first user interface includes concurrently displaying: a summary of the content of a first message (e.g., 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p2 and / or 624r); and at least a portion of a second message, without displaying a summary of the content of the second message (e.g., in...). Figures 6B to 6G In this context, summaries 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p2, and / or 624r are displayed together with previews 620a, 620b, 620c, and 620g (e.g., a summary of a message is displayed together with a message that does not include a summary). In some embodiments, based on the determination that a first set of criteria is not met (e.g., a summary is not triggered), the computer system displays at least a portion of a second message without displaying a summary based on the content of the second message. In some embodiments, a summary based on the content of the second message was previously displayed (e.g., the summary was triggered but subsequently replaced by a preview). Displaying the first user interface includes concurrently displaying a summary based on the content of the first message and at least a portion of the second message, without displaying a summary based on the content of the second message. This reduces the amount of input required to perform operations, provides conditional display of the summary, and makes the user interface cleaner.

[0283] In some implementations, when displaying a summary of the content based on a first message (e.g., 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p2 and / or 624r): Based on a set of indication criteria determined to be satisfied (e.g., including a set of criteria satisfied when displaying the text of the summary and / or when displaying the text of the summary message's content), the computer system displays indications (e.g., 625 and / or 626) (e.g., logos, shapes, colors, and / or animations) regarding the summary being displayed (e.g., a summary based on the content of the first message) (e.g., not the actual content of the first message). In some implementations, this set of indication criteria differs from the first set of criteria (e.g., when displaying the summary, in...). Figures 6B to 6E (See 625 and / or 626). In some embodiments, based on the determination that this set of indication criteria is not met, the indication to display the summary being displayed (e.g., a summary based on the content of the first message) is abandoned. Displaying the first user interface includes: conditionally displaying the indication to display the summary being displayed based on a set of indication criteria different from the first set of criteria, which performs the action when a set of conditions has been met without requiring further user input, providing improved visual feedback on the summary being displayed (e.g., rather than the actual content of the message).

[0284] In some implementations, this set of indication criteria includes criteria that are met when an event is detected (e.g., when scrolling the inbox interface 614, in...). Figure 6C (See Figure 626). In some embodiments, the event includes detecting input corresponding to a request for navigation (e.g., scrolling and / or not scrolling) of the first user interface. In some embodiments, the event includes displaying a summary (e.g., a summary based on the content of the first message). In some embodiments, if the summary is not displayed, no indication is displayed. Displaying the first user interface includes conditionally displaying an indication about a summary being displayed based on a second set of criteria, which includes criteria satisfied when the event is detected. This provides improved visual feedback about a summary being displayed (e.g., rather than the actual content of the message) provided once a set of conditions has been met, without requiring further user input.

[0285] In some implementations, the summary is based on the content of a second message (e.g., 610j1, 610j2, 610j3, 610k1, 610k2, 610k3, 622k3-1, 610k3-2, and / or 610k3-3) that is different from the first message (e.g., 610j1, 610j2, 610j3, 610k1, 610k2, 610k3, 622k3-1, 610k3-2, and / or 610k3-3) (e.g., 622j1, 622j2, 622j3, 622k3-1, 622k3-2, and / or 622k3-3) (e.g., the summary is based on multiple messages). In some implementations, the second message is associated with the first message (e.g., it has the same subject line as the first message, is part of the same message thread as the first message, and / or is delivered to the same user group as the first message). In some implementations, the second message and the first message are associated with common characteristics (e.g., having the same subject line, being part of the same message thread, and / or being delivered to the same user group) (e.g., linked and / or grouped together). A summary of the content of the first message and the second message is conditionally displayed when a first set of criteria is met. This performs the action once a set of conditions is met without requiring further user input, keeping the user interface clean and providing a conditional display of the summary.

[0286] In some implementations, the first set of criteria includes criteria that are met when a threshold number of messages (e.g., 2, 4, 7, and / or 10 messages) are received within a threshold time period (e.g., 1 minute, 5 minutes, 30 minutes, 1 hour, and / or 2 hours). For example, when a third message 610j3 is received within 2 minutes of the first message 610j1 and / or 1 minute of the second message 610j2, in... Figure 6J The summary is shown in section 624j. In some embodiments, the threshold time period is measured from the time when the first message (e.g., the first message in a message sequence) is received out of the threshold number of messages. In some embodiments, the first set of criteria includes criteria that are met when the threshold number of messages are associated with common characteristics (e.g., the same sender, the same receiver, the same header, the same receiver group, and / or the same message thread). When the first set of criteria is met, a summary based on the content of the first message and the content of the second message is conditionally displayed, wherein the first set of criteria includes criteria that are met when the threshold number of messages are received within the threshold time period. This performs the operation when a set of conditions has been met without requiring further user input, keeping the user interface clean and providing a conditional display of the summary.

[0287] In some implementations, the first set of criteria includes when the profile settings are activated (e.g., 638 in...). Figure 6T Activated in and Figure 6U The criteria are met when the profile is disabled (e.g., when the profile is enabled and / or allowed). In some implementations, the profile settings are user-configurable (e.g., activated and / or deactivated in response to detected input). A profile based on the content of a first message is conditionally displayed when a first set of criteria is met, wherein the first set of criteria includes those met when the profile settings are activated. This performs the action without further user input once a set of conditions has been met, and provides conditional display of the profile.

[0288] In some implementations, the first set of criteria includes criteria that are met when the content of the first message meets a threshold amount of content (e.g., as per [reference to...]). Figure 6E The described method involves displaying a summary 624d based on a content threshold 622d exceeding the content threshold (e.g., a threshold amount of text, a threshold number of alphanumeric characters, and / or a threshold number of content lines) (e.g., a computer system displays a summary of a longer message but not a summary of a shorter message). A summary of the content of a first message is conditionally displayed when a first set of criteria is met, wherein the first set of criteria includes criteria for when the content of the first message meets the content threshold. This operation is performed when a set of conditions has already been met without requiring further user input and provides a conditional display of the summary.

[0289] In some implementations, the first set of criteria includes criteria that are met when the first message is in an unread state (e.g., 610d in...). Figure 6E In the unread state and Figure 6F The 610d is in a read state. Figure 6E In the unread state and Figure 6G The 610j3 is in a read state; Figure 6J It is in a read state and in Figure 6K The message is in an unread state (e.g., it has not been read and / or has not been opened). (e.g., a summary is displayed for messages in an unread state, and no summary is displayed for messages that have been read and / or opened.) A summary based on the content of a first message is conditionally displayed when a first set of criteria is met, wherein the first set of criteria includes criteria that are met when the first message is in an unread state. This performs the operation when a set of conditions has been met without requiring further user input and provides a conditional display of the summary.

[0290] It should be noted that the above text regarding method 700 (for example, Figure 7The details of the process described herein can also be applied in a similar manner to the methods described herein (e.g., methods 800 and 1000). For example, methods 800 and 1000 may optionally include one or more features of the various methods described above with reference to method 700. For example, methods 800 and 1000 include features of method 700 to selectively display the content of a message (e.g., a preview) or a summary of a message. For example, methods 800 and 1000 include features of method 700 to visually distinguish the summary from other written content. For the sake of brevity, these details will not be repeated herein.

[0291] Figure 8 This is a flowchart illustrating a method for displaying a summary of relevant messages using a computer system, according to some implementation schemes. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600 and / or 642) (e.g., a smartphone, smartwatch, tablet computer, laptop computer, desktop computer, wearable device and / or head-mounted device), which communicates with display generating components (e.g., 601 and / or 643) (e.g., a display, touchscreen display, monitor, holographic display system and / or head-mounted display system) and one or more input devices (e.g., 602 and / or 643) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); a mouse; a keyboard; a remote control; a visual input device (e.g., one or more cameras, such as an infrared camera, a depth camera, a visible light camera and / or a gaze-tracking camera); an audio input device (e.g., a microphone); a biometric sensor (e.g., a fingerprint sensor, a facial recognition sensor, a gaze-tracking sensor and / or an iris recognition sensor); and / or one or more mechanical input devices (e.g., a pressable input mechanism; a button; a rotatable input mechanism; a crown; and / or a dial)). Some operations in method 800 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0292] As described below, method 800 provides an intuitive way to display summaries of relevant messages. This method reduces the cognitive burden on users when viewing message summaries and / or related messages, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to view messages and / or message summaries more quickly and efficiently saves power and increases the time interval between battery charging.

[0293] The computer system receives (802) a first message (e.g., 610k1 and / or 610k2) including first content (e.g., 622k1 and / or 622k2) (e.g., a text message and / or an email) and a second message (e.g., 610k1 and / or 610k2) different from the first message, including second content (e.g., 622k1 and / or 622k2) (e.g., a text message and / or an email). The computer system displays (804) a first summary (e.g., 624k2) based on the first content of the first message and the second content of the second message (e.g., derived from and / or generated from these contents) (e.g., an automatically generated summary (e.g., a summary including automatically generated text content and / or a summary including generative text content); and / or a summary generated without user input) via a display generation component. In some embodiments, the first summary (and / or the second summary) is generated via one or more machine learning algorithms (e.g., the first summary (and / or the second summary) includes automatically generated text content and / or generative text content) (e.g., as about Figure 6E (As described). After displaying the first summary, the computer system receives (806) a third message (e.g., 610k3) (e.g., a text message and / or email) associated with the first and second messages (e.g., having the same subject line as the first and second messages, being part of the same message thread as the first and second messages, and / or being delivered to the same user group as the first and second messages) (e.g., 610k3 being part of the same thread as 610k1 and 610k2, and / or 610k3 being delivered to the same user group as 610k1 and 610k2), wherein the third message includes a third content (e.g., 622k3-3). In some embodiments, the first, second, and / or third messages are associated (e.g., having the same subject line, being part of the same message thread, and / or being delivered to the same user group) through common characteristics (e.g., having the same subject line, being part of the same message thread, and / or being delivered to the same user group). Upon receiving the third message and based on the determination that the first set of criteria (e.g., the first set of summary criteria) are met, the computer system displays (808) a second summary (e.g., 624k3-1, 624k3-2, 624k3-3, and / or 624k3-4) via a display generation component, which differs from the first summary (e.g., includes information different from the first summary and / or includes a summary different from the first summary). The second summary is based on the third content of the third message (e.g., derived from the content; generated based on the content; and / or automatically generated based on the content (e.g., using an AI process or a generative AI process)). Figures 6P to 6TThe depicted summaries 624k3-1, 624k3-2, 624k3-3, and / or 624k3-4 include summaries from content 622k3. In some embodiments, displaying a second summary includes updating a first summary to a second summary and / or replacing the first summary with the second summary. In some embodiments, the second summary is based on a third content of a third message, as well as the first and / or second content (e.g., determined based on these contents and / or automatically generated based on these contents (e.g., using an AI process or a generative AI process)). In some embodiments, the second summary is based on the first and third content, but not on the second content. In some embodiments, the second summary is based on the second and third content, but not on the first content. In some embodiments, the computer system abandons displaying the second summary (e.g., abandons updating the first summary) based on the determination that a first set of criteria is not met. In some embodiments, the first set of criteria includes criteria that are met when the second summary is available (e.g., has been generated) (e.g., is available for display). In some implementations, the first set of criteria includes criteria that are met when the third content meets a threshold amount of content (e.g., the third content includes a threshold amount of character and / or alphanumeric text). A third message associated with the first and second messages is received after displaying a first summary of the first content and a second content based on the first message and the second message, and a second summary based on the third content is conditionally displayed when the first set of criteria is met. This performs the operation without further user input once a set of conditions has been met, and provides a different summary after receiving additional messages.

[0294] In some implementations, showing the second summary includes: determining that the first message is in an unread state (e.g., as...). Figures 6P to 6T The second summary (e.g., 624k3-1, 624k3-2, 624k3-3 and / or 624k3-4) is based on the first content (e.g., determined according to the first content and / or automatically generated according to the first content (e.g., using an AI process or a generative AI process)). Figures 6P to 6T The depicted summaries 624k3-1, 624k3-2, 624k3-3, and / or 624k3-4 conditionally include summaries from content 622k3-1 and / or 622k3-2 (e.g., the second summary includes a summary of the first message). In some embodiments, displaying the second summary includes: based on determining that the first message is not in an unread state (e.g., as...). Figures 6P to 6T The second summary is not based on the first content (e.g., as depicted in 640 and / or as the message does not include the unread message indicator 612) (e.g., the first message has been read and / or opened). Figures 6P to 6TThe depicted summaries 624k3-1, 624k3-2, 624k3-3, and / or 624k3-4 conditionally include summaries from content 622k3-1 and / or 622k3-2 (e.g., the second summary does not summarize the first message). In some embodiments, the second summary is based on (e.g., only on) content from unread messages (e.g., the second summary is not based on content from messages that have been opened and / or read). In some embodiments, the second summary is based on the second content based on determining that the second message is unread (e.g., not yet read and / or not yet opened). In some embodiments, the second summary is not based on the second content based on determining that the second message is not unread. The conditional display of a second summary based on the first content when the first message is unread performs an action without further user input once a set of conditions are met, and provides summaries of multiple messages.

[0295] In some implementations, after the first message has been opened, the second summary is based on the first content (e.g., in response to...). Figure 6L Input 605l and / or Figure 6O After entering 605o to open message 610k1 and / or message 610k2, Figures 6P to 6Q The second summary is displayed as 624k3-1 and / or 624k3-2 (e.g., read, in a read state, and / or not in an unread state). In some embodiments, displaying the second summary includes summaries of the first and third content, based on the determination that the first message has been opened and the first content meets a relevance criterion. In some embodiments, displaying the second summary includes summaries of the third content but excludes summaries of the first content, based on the determination that the first message is in a read state and the first content does not meet a relevance criterion. Displaying a second summary based on the first content after the first message has been opened reduces the amount of input required to perform actions (e.g., opening multiple messages to view their contents).

[0296] In some implementations, the second summary is based on the first content (e.g., summaries 624k3-1 and / or 624k3-2 are based on 622k3-1 and / or 622k3-2). In some implementations, the first message comes from a first sender (e.g., message 610k1 comes from Travis and / or message 610k2 comes from Matt). In some implementations, the third message comes from a second sender different from the first sender (e.g., message 610k3 comes from Aaron) (e.g., the summary is based on a message from a different sender). When the first message comes from the first sender and the third message comes from a different sender, a second summary based on the third content and the first content is displayed, which reduces the amount of input required to perform operations (e.g., opening multiple messages to view content sent from different senders).

[0297] In some implementations, the second summary (e.g., within the summary itself and / or within the abstract) includes indications (e.g., alphanumeric text, shapes, and / or images) to a first sender (e.g., 636a, 636b, and / or 636c) and indications to a second sender (e.g., 636a, 636b, and / or 636c). In some implementations, the indications to the first sender and the second sender are independent of the indications in the sender field (or optionally, the receiver field). In some implementations, in addition to the second indication to the first sender (and / or the second indication to the second sender), the computer system concurrently displays the indications to the first sender and the second sender (e.g., in the receiver field and / or the sender field). Including indications to the first sender and the second sender in the second summary reduces the amount of input required to perform operations (e.g., opening multiple messages to see which part of the summary belongs to which sender).

[0298] In some implementations, the second summary is displayed independently of (e.g., regardless of) the state of the third message (e.g., 624k3-1, 624k3-2, 624k3-3, and 624k3-4 are displayed independently of the read or unread state of message 610k3) (e.g., the summary is displayed regardless of whether the third message is open or closed). In some implementations, the second summary is displayed when the third message is in a read (and / or unread) state. Displaying the second summary independently of the state of the third message reduces the amount of input required to perform operations (e.g., opening the message and / or displaying the message's content), regardless of the message's state.

[0299] In some implementations, the computer system concurrently displays the first summary and the third content via a display generation component before displaying the second summary (e.g., device 600 displays summaries 624k1 and / or 62k2 and content 622k3 before displaying summaries 624k3-1, 624k3-2, 624k3-3 and / or 624k3-4) (e.g., summaries not based on the third content are displayed together with the content of new messages). In some implementations, the computer system displays the third content before displaying the second summary. Concurrently displaying the first summary and the third content provides rapid access to the third content, as it can be viewed regardless of whether the second summary is displayed (and / or available).

[0300] In some implementations, the first, second, and third messages are messages from a communication application (e.g., a messaging application associated with the messaging user interface 608 and / or an email application associated with the email user interface 632) (e.g., corresponding to the communication application) (e.g., the first, second, and third messages are messages from the same communication application). In some implementations, the first set of criteria includes criteria satisfied by the following condition: the communication application is already inactive (e.g., closed and / or running in the background) after receiving the third message (e.g., summary 624k2 is not displayed until the email user interface 632 is moved to the background, such as...). Figures 6M to 6O (As depicted) (e.g., the second summary is not displayed until the communication application is moved to the background or closed after a third message is received). In some embodiments, the computer system abandons (and / or delays) displaying the second summary until the communication application has transitioned to an inactive state. In some embodiments, the computer system detects the state of the communication application (e.g., whether the communication application is inactive and / or active). In some embodiments, the computer system detects a request to activate a second application different from the communication application (e.g., navigating to the second application and / or bringing the second application to the foreground), and in response, transitions the communication application (e.g., from an active state) to an inactive state, and transitions the second application (e.g., from an inactive state) to an active state. In some embodiments, when the communication application is inactive, the computer system detects a request to activate the communication application (e.g., navigating to the communication application and / or bringing the communication application to the foreground), and in response, transitions the communication application to an active state (and / or transitions the corresponding active application to an inactive state). A second summary is conditionally displayed based on whether the communication application has transitioned from an active to an inactive state to an inactive state associated with different messages. This performs an action without requiring further user input when a set of conditions are met.

[0301] In some implementations, the first set of criteria includes criteria that are met when a second summary (e.g., available for display) is generated within a threshold time period (e.g., 1 second, 3 seconds, 10 seconds, and / or 1 minute) after the third message is received (e.g., if a summary (such as summary 603k3-1) has not been generated within the threshold time period after receiving message 610k3, then device 600 displays a preview 620k3 of message 610k3) (and / or is available for display). In some implementations, after receiving the third message and based on the determination that the first set of criteria is not met, the computer system displays at least a portion of the third content without displaying the second summary (e.g., device 600 displays a preview of message 610k3 without displaying the summary (such as summary 624k3-1)) (e.g., if the third content is available for display and the second summary is not available within the threshold time period, then the computer system does not delay displaying at least a portion of the third content). Based on whether the second summary is generated within a threshold time period, the system conditionally displays the second summary or displays a portion of the third content without displaying the second summary. This operation is performed when a set of conditions are met without requiring further user input and prevents delays in displaying content when no summary is generated.

[0302] In some implementations, after receiving a first message (e.g., 610k1) (and / or in some implementations, before receiving a second message), the computer system displays a third summary (e.g., 624k1) based on the first content (e.g., determined based on the first content and / or automatically generated based on the first content (e.g., using an AI process or a generative AI process)) via a display generation component. This third summary differs from the second summary (e.g., includes information different from the second summary and / or includes a summary different from the second summary) (e.g., 624k1 differs from 624k3-1, 624k3-2, 624k3-3, and / or 624k3-4) (and / or in some implementations, differs from the first summary) (e.g., the summary of the initial message differs from the summaries of multiple messages). Displaying a third summary based on the first content after receiving the first message, where the third summary differs from the second summary message, reduces the amount of input required to perform an action (e.g., opening the message).

[0303] It should be noted that the above text regarding method 800 (for example, Figure 8The details of the process described herein can also be applied in a similar manner to the methods described herein (e.g., methods 700 and 1000). For example, methods 700 and 1000 may optionally include one or more features of the various methods described above with reference to method 800. For example, methods 700 and 1000 include features of method 800 to selectively display summaries of relevant messages. For example, methods 700 and 1000 include features of method 800 to display different summaries based on the state of the message (and / or relevant messages) (e.g., determined based on the state of the message and / or automatically generated based on the state of the message (e.g., using an AI process or a generative AI process)). For example, methods 700 and 1000 include features of method 800 to display summaries of relevant messages from different senders and / or to display instructions to different senders. For example, methods 700 and 1000 include conditionally displaying summaries based on various conditions (e.g., whether the communication application was already inactive after receiving the message and / or whether the summary was generated within a threshold time period). For the sake of brevity, these details will not be repeated herein.

[0304] Figures 9A to 9P User interfaces for displaying message summary capabilities are illustrated according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including... Figure 10 The process. Although Figures 9A to 9P The user interface for email messaging is described and depicted, but it is for illustrative purposes only. About Figures 9A to 9P The described technology is applicable to various communication application user interfaces, including text messaging and instant messaging user interfaces, encompassing written communication. About Figures 9A to 9P The described technology is applicable to Figures 6A to 6AD The message sending and receiving user interface 608 and the email user interface 632. Additionally, regarding... Figures 6A to 6AD The technologies described in the message sending and receiving user interface 608 and the email user interface 632 are applicable to Figures 9A to 9P Email user interface 632. Figures 9A to 9P Features and reference numerals include those related to Figures 6A to 6AD Several common features and reference numerals are described in further detail below. For the sake of brevity, in Figures 9A to 9P The details of these common features will not be repeated here.

[0305] exist Figure 9AAt this point, device 642 displays an inbox interface 614 of an email application corresponding to email user interface 632 on display 643. Inbox interface 614 includes messages 910a through 910d (e.g., email messages) that are part of message thread 902. As depicted by unread message indicator 612, message thread 902 includes at least one unread message. In some embodiments, message thread 902 includes messages that device 642 has determined to be grouped together in a message thread based on a set of criteria (e.g., based on message ID, based on message header, and / or based on similar recipient grouping). In some embodiments, in response to detecting input pointing to message thread view option 901, device 642 displays a single message from message thread 902 (e.g., Michael's message 910a, Sara's message 910b, Carrie's message 910c, or Carrie's message 910d) in inbox interface 614. Figure 9J As illustrated, as depicted, the summary display setting 638 is turned off. In response to detecting that the summary display setting 638 is turned off, the device 642 does not display summaries of one or more messages, such as those about..., in the inbox interface 614. Figures 6A to 6AD For a more detailed description. In some implementations, in response to detecting that the display summary setting 638 is turned on, the device 642 displays a summary of one or more messages, such as about..., in the inbox interface 614. Figures 6A to 6AD A more detailed description.

[0306] exist Figure 9A At this point, device 642 detects a request to view message thread 902. In some implementations, the request to view message thread 902 includes input 905a (e.g., touch input, air gesture, button press, gaze, and / or voice input) pointing to message thread 902 and / or messages of message thread 902 (e.g., messages 910a, 910b, 910c, and / or 910d). In response to detecting input 905a, device 642 displays information based on the read and / or unread status of messages 910a, 910b, 910c, and / or 910d in message thread 902. Figure 9B Content interface 616 or Figure 9C The content interface 616. In some implementations, in response to the detection of input 905a, device 642 displays the read and / or unread status of messages 910a, 910b, 910c and / or 910d in message thread 902. Figure 9E Content interface 616 or Figure 9F Content interface 616.

[0307] exist Figure 9BIn response to the detection of input 905a and based on the determination that Sara's message 910b is unread (and / or based on the determination that Michael's message 910a is read), device 642 displays content interface 616. In some embodiments, Sara's message 910b is the first unread message in a series of unread messages (e.g., messages 910b through 910d), wherein the series of unread messages is received after Sara's message 910b is received. Content interface 616 displays a portion 905 of message thread 902 corresponding to dashed box 904, which surrounds a portion of the expanded representation 900 of message thread 902. Dashed box 904 illustrates that content interface 616 of device 642 is displaying specific content and / or is located at a specific position within message thread 902. Because the expanded representation 900 of message thread 902 is provided for illustrative purposes, the expanded representation 900 includes only a portion of the content depicted in content interface 616 of device 642. Furthermore, the expanded representation 900 of message thread 902 depicts an example layout of the message thread, an example order of messages, and / or an example orientation of messages within message thread 902. In some embodiments, the expanded representation 900 of message thread 902 includes... Figure 9B The layout, message order, and / or message orientation of the different message threads depicted. In some implementations, the content of the content interface 616 (messages 910a to 910d, summary display 908a, summary display 908b, and / or summary 924) is visually distinguished from each other (e.g., by using one or more tiles, by using different colors, by using one or more shapes to separate the content, and / or by using one or more icons to separate the content).

[0308] exist Figure 9B At this point, device 642 displays a summary capability representation 908a in content interface 616. Summary capability representation 908a is similar to summary capability representation 644 but has a different state. As described herein, device 642 displays the summary in response to detecting input directed at summary capability representation 908a (e.g., touch input, air gesture, button press, gaze, and / or voice input). In some embodiments, device 642 generates the summary in response to detecting input directed at summary capability representation 908a. In some embodiments, device 642 has already generated the summary before detecting input directed at summary capability representation 908a. In such embodiments, device 642 displays the previously generated summary in response to detecting input directed at summary capability representation 908a.

[0309] exist Figure 9BAt a specific location within the content interface 616, device 642 displays a summary capability representation 908a. As depicted, summary capability representation 908a is displayed above at least a portion of Sara's message 910b. For example, summary capability representation 908a is displayed above the message header 903b of Sara's message 910b. In some embodiments, the message header (e.g., message header 903b) includes the message's subject line (e.g., title), an indication of the sender (e.g., "Sara Appleseed"), the message's recipient (e.g., "team serv"), and / or the date or time the message was received (e.g., "yesterday"). Device 642 also displays an indication of the number of new messages being summarized and / or to be summarized, as depicted by reference numeral 912 (e.g., "3 new messages"). Device 642 displays an indication 914 of the total number of messages in a message thread (e.g., "4 messages").

[0310] exist Figure 9B In the context of message thread 902, as depicted in expanded representation 900, summary display 908a is displayed at position 906a. For example, summary display 908a is displayed below Michael's message 910a (e.g., below the message header 903a of Michael's message 910a and / or below the content 922a of Michael's message 910a). Furthermore, summary display 908a is displayed above Sara's message 910b (e.g., above the header 903b of Sara's message 910b and / or above the content 922b of Sara's message 910b). Summary display 908a is displayed above Carrie's message 910c (e.g., above the header 903c of Carrie's message 910c and / or above the content 922c of Carrie's message 910c). Summary display 908a is displayed above Carrie's message 910d (e.g., above the header 903d of Carrie's message 910d and / or above the content 922d of Carrie's message 910d).

[0311] exist Figure 9BAt the location depicted in the expanded representation 900 of message thread 902, the summary indication 908a has a specific orientation relative to read and unread messages. Status indicator 640 illustrates the status of messages immediately following (or optionally, within a threshold time) before device 642 detects a request to view message thread 902 (and / or input 905a). The summary indication 908a is displayed between read messages (e.g., Michael's message 910a) and unread messages (e.g., Sara's message 910b). As depicted, no summary indication is displayed between two unread messages (e.g., between Sara's message 910b and / or Carrie's message 910c).

[0312] exist Figure 9B In some embodiments, in response to a request to scroll the content of the content interface 616, device 642 scrolls the summary display 908a. For example, in some embodiments, in response to a request to scroll the content interface 616 in a corresponding direction, device 642 scrolls both the content of the content interface 616 (e.g., content 922b) and the summary display 908a. In some embodiments, device 642 detects input 905b1 corresponding to a request to scroll in the downward direction (e.g., touch input, air gesture, button press, gaze, and / or voice input). In such embodiments, in response to the detection of input 905b1, device 642 shifts both content 922b and summary display 908a in the upward direction. In some embodiments, in response to the detection of input 905b1, device 642 displays the content 922c of Carrie's message 910c without displaying the summary display 908a. In some implementations, device 642 detects input 905b2 corresponding to a request to scroll in the upward direction (e.g., touch input, air gesture, button press, gaze, and / or voice input). In such implementations, in response to the detection of input 905b2, device 642 shifts both content 922b and summary functionality display 908a downwards. In some implementations, in response to the detection of input 905b2, device 642 displays the content 922a of Michael's message 910a without displaying the summary functionality display 908a.

[0313] exist Figure 9B At this point, device 642 detects input 905b3 (e.g., touch input, air gesture, button press, gaze, and / or voice input) pointing at summary display 908a. In response to detecting input 905b3, device 642 displays... Figure 9F Summary 924.

[0314] exist Figure 9C At the location, in response to detection Figure 9AUpon receiving input 905a and determining that Carrie's message 910c is unread (and / or determining that Sara's message 910b and Michael's message 910a are read), device 642 displays content interface 616. In some embodiments, Carrie's message 910c is the first unread message in a series of unread messages received after Carrie's message 910c. As depicted in dashed box 904 in expanded representation 900, device 642 displays summary enable representation 908a at location 906b. Location 906b is in message thread 902 and... Figure 9B Position 906a is at a different position (e.g., position 906b is below position 906a). Figure 9C The depicted summary display 908a has a specific positioning (e.g., between, above, below, to the left, and / or to the right) relative to the read and unread messages of message thread 902. For example, device 642 displays summary display 908a between Carrie's message 910c (which is unread) and Sara's message 910b (which is read). Figure 9C The depicted summary display indicates that 908a is not displayed between Michael's message 910a and Sara's message 910b (e.g., Figure 9B (Position 906a). In Figure 9C At this point, device 642 detects input 905c (e.g., touch input, air gesture, button press, gaze and / or voice input) pointing to summary display 908a.

[0315] exist Figure 9D At this point, in response to the detection of input 905c, device 642 displays animation 916. Animation 916 includes effects that change over a period of time (e.g., 1 second, 3 seconds, 10 seconds) (e.g., glowing, outlining, and / or highlighting effects) until device 642 no longer displays animation 916. In some embodiments, animation 916 indicates that a summary is being generated.

[0316] exist Figure 9E In response to the detection of input 905c and / or after animation 916 has ended, device 642 displays summary 924 in content interface 616. Summary 924 is similar to About Figures 6A to 6ADThe described summaries (e.g., summaries 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p1, 624p2, 624q1, 624q2, and / or 624r) have different states. For example, summary 924 summarizes the content of a message and / or one or more messages in a message thread. In some implementations, the summaries are content generated based on machine learning algorithms (e.g., generative AI models and / or large language models) (e.g., automatically generated text content and / or generative text content). In some embodiments, summary 924 includes content based on one or more messages (e.g., derived from, determined based on, and / or automatically generated based on the content (e.g., using an AI process or a generative AI process)) and / or machine-generated content different from the content (e.g., automatically generated text content and / or generative text content). In some embodiments, summary 924 provides an overview of the content of one or more messages (e.g., the exact text of the content is not copied (e.g., mirrored)).

[0317] exist Figure 9E At this point, summary 924 summarizes (e.g., based on) unread messages of message thread 902. For example, summary 924 summarizes Carrie's message 910c (e.g., content 922c) and Carrie's message 910d (e.g., content 922d). Summary 924 does not summarize read messages of thread 902, including Michael's message 910a (e.g., content 922a) and Sara's message 910b (e.g., content 922b). As depicted, summary 924 includes an indication 923 (e.g., "Carrie...") belonging to a specific person, similar to a statement about... Figures 6A to 6AD The described instructions are 636a, 636b, and / or 636c. In some embodiments, summary 924 does not include instruction 923. Device 642 displays summary 924 and an indication of how many messages are included in summary 924, as depicted by reference numeral 912 (e.g., "2 new messages").

[0318] exist Figure 9E At this location, device 642 displays summary 924 instead of summary power indication 908a. In some embodiments, the location occupied by at least a portion (e.g., some but not all and / or all) of summary 924 replaces the location occupied by at least a portion (e.g., some but not all and / or all) of summary power indication 908a. Summary 924 is displayed at the location 906b previously occupied by summary power indication 908a, as per [reference to...]. Figure 9CAs depicted. Position 906b has a specific location within message thread 902, as described above. Figure 9C As described. Device 642 also displays a summary menu display 926, which shows information about... Figure 9F A more detailed description is needed. For example, regarding... Figure 9F In more detail, in response to a request to detect the content of the scrolling content interface 616, the device 642 scrolls both the summary 924 and the content in the content interface 616.

[0319] exist Figure 9E At this location, device 642 displays summary 924 with visual feature 925 to distinguish summary 924 from other content in message thread 902. In some embodiments, visual feature 925 is displayed at the text. In some embodiments, visual feature 925 is a font feature (e.g., bold, underline, font color, and / or font size). In some embodiments, visual feature 925 is displayed adjacent to text (e.g., color, shape, glow, and / or outline). In some embodiments, visual feature 925 is displayed in response to the detection of an event (e.g., scrolling and / or user interaction with content interface 616). In such embodiments, visual feature 925 is displayed for a threshold time period, and once the threshold time period is met, device 642 stops displaying visual feature 925. In some embodiments, visual feature 925 is persistent (e.g., not displayed in response to the detection of an event) and / or displayed while summary 924 is being displayed.

[0320] exist Figure 9E In some implementations, in response to a request to view a message thread, device 642 displays (e.g., automatically) a summary 924 (e.g., in the absence of input to the summary indication 908a and / or without displaying the summary indication 908a). For example, in response to detecting input 905a and based on determining that Carrie's message 910c is unread (and / or based on determining that Sara's message 910b and Michael's message 910a are read), device 642 displays... Figure 9F Summary 924 (e.g., automatically and / or without a reference) Figure 9C (The summary can represent the user input in the case of 908a).

[0321] exist Figure 9F At the location, in response to detection Figure 9B Input 905b3, device 642 displays summary 924. Figure 9F Summary 924 is different Figure 9E Summary 924. Figure 9FSummary 924 summarizes the unread messages of message thread 902, including Sara's message 910b (e.g., content 922b), Carrie's message 910c (e.g., content 922c) and Carrie's message 910d (e.g., content 922d). Figure 9F Summary 924 does not summarize the read messages of message thread 902, including Michael's message 910a (e.g., content 922a). Device 642 displays summary 924 along with an indication of how many messages are included in summary 924, as depicted by reference numeral 912 (e.g., "3 new messages"). Device 642 displays summary 924 at location 906a, as per [reference to...]. Figure 9B As described.

[0322] exist Figure 9F In some embodiments, in response to a request to scroll the content of the content interface 616, device 642 scrolls the summary 924. For example, in some embodiments, in response to a request to scroll the content of the content interface 616 in a corresponding direction, device 642 shifts both the content of the content interface 616 (e.g., content 622b) and the summary 924. In some embodiments, device 642 detects input 905f2 (e.g., touch input, air gesture, button press, gaze, and / or voice input) corresponding to a request to scroll in the upward direction. In such embodiments, in response to the detection of input 905f2, device 642 shifts both content 622b and summary 924 in the downward direction. In some embodiments, in response to the detection of input 905f3, device 642 displays the content 922a of Michael's message 910a without displaying the summary 924. In some embodiments, device 642 detects input 905f3 (e.g., touch input, air gesture, button press, gaze, and / or voice input) corresponding to a request to scroll in the downward direction. In such embodiments, in response to the detection of input 905f3, device 642 shifts both content 622b and summary 924 in an upward direction. In some embodiments, in response to the detection of input 905f2, device 642 displays the content 922c of Carrie's message 910c without displaying summary 924.

[0323] exist Figure 9F In some implementations, in response to a request to view a message thread, device 642 displays (e.g., automatically) a summary 924 (e.g., in the absence of input to the summary indication 908a and / or without displaying the summary indication 908a). For example, in response to detecting input 905a and based on determining that Sara's message 910b is unread (and / or based on determining that Michael's message 910a is read), device 642 displays... Figure 9F Summary 924 (e.g., automatically and / or without a reference) Figure 9B (The summary can represent the user input in the case of 908a).

[0324] exist Figure 9F At this point, device 642 displays a summary menu display 926. When selected, the summary menu display 926 causes device 642 to display the option corresponding to summary 924. Device 642 detects input 905f1 directed at the summary menu display 926 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input 905f1, device 642 displays... Figure 9G Summary menu 928.

[0325] exist Figure 9G At this point, the summary menu 928 includes one or more options corresponding to summary 924. For example, the summary menu 928 includes a report capability indicator 930. In some embodiments, device 642 detects input 905g1 directed at the report capability indicator 930 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input 905g1, device 642 initiates communication with an external computer system regarding a question corresponding to summary 924. In some embodiments, in response to detecting input 905g1, device 642 stops displaying summary 924. In some embodiments, one or more options corresponding to summary 924 include a capability indicator that stops displaying (e.g., hides) summary 924 when selected. In some embodiments, one or more options corresponding to summary 924 include a capability indicator that provides feedback on summary 924 when selected (e.g., feedback that summary 924 is a good summary and / or negative feedback that summary 924 is not a good summary).

[0326] exist Figure 9G At this point, device 642 detects input 905g2 (e.g., touch input, air gesture, button press, gaze, and / or voice input) on the scrolling content interface 616. In response to detecting input 905g2, device 642 scrolls the content interface 616 (e.g., up, down, left, and / or right), such as... Figure 9H As depicted. In some embodiments, device 642 detects input 905g3 pointing towards the return indication display 936 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In such embodiments, in response to detecting input 905g3, device 642 displays... Figure 9J The inbox interface is similar to 614.

[0327] exist Figure 9HIn response to the detection of input 905g2, device 642 displays a summary capability representation 908b. Summary capability representation 908b is similar to summary capability representation 908a, but has a different state. In some embodiments, summary capability representation 908b summarizes all messages of message thread 902 (e.g., summary capability representation 908b summarizes both read and unread messages). In some embodiments, summary capability representation 908a summarizes messages of message thread 902 based on (e.g., according to) the read and / or unread state of a specific message (e.g., summary capability representation 908a summarizes unread messages).

[0328] exist Figure 9H At position 906, summary indication 908b is located, which differs from positions 906a and 906b. Position 906c is above Michael's message 910a (e.g., above header 903a and / or content 922a). As depicted in expanded indication 900, position 906c is located at the topmost part of message thread 902. As depicted, position 906c is above read and unread messages (e.g., messages 910a to 910d) in message thread 902. In some embodiments, summary indication 908b is not displayed. Figure 9H The content interface 616 is displayed and / or not displayed at the top of message thread 902. In some embodiments, device 642 displays summary power indication 908b at a location different from position 906c. In some embodiments, device 642 displays summary power indication 908b at both positions 906a and 906b (e.g., and / or concurrently displays summary power indication 908a).

[0329] exist Figure 9H At this point, device 642 detects a request to display a summary based on all messages in message thread 902. In some embodiments, device 642 detects input 905h1 directed at the summary display 908b (e.g., touch input, air gesture, button press, gaze, and / or voice input). In such embodiments, in response to detecting input 905h1, device 642 displays... Figure 9I Summary 924. In Figure 9H In some embodiments, device 642 detects input 905h2 (e.g., touch input, air gesture, button press, gaze, and / or voice input) that scrolls content interface 616 beyond its boundaries (e.g., top and / or bottom boundaries) and / or beyond message thread 902. In response to detecting input 905h2, device 642 displays... Figure 9I Content interface 616.

[0330] exist Figure 9IAt position 905h2 (and / or input 905h1), in response to the detection of input 905h2 (and / or input 905h1), device 642 displays content interface 616. Content interface 616 includes summary 924 at position 906c. As depicted, device 642 no longer displays summary 924 at position 906b (e.g., because a different summary is displayed). Device 642 also causes message thread 902 to shift in the corresponding direction (e.g., up, down, left, and / or right) in response to displaying summary 924.

[0331] exist Figure 9I At location 906c, summary 924 summarizes a set of messages that differ from summary 924 at location 906b and / or summary 924 at location 906a. Summary 924 at location 906c summarizes both read and unread messages of message thread 902 (e.g., messages 910a to 910d). In some embodiments, summary 924 at location 906c summarizes all messages of message thread 902. Device 642 displays summary 924 at location 906c along with an indication of how many messages are included in summary 924, as depicted by reference numeral 912 (e.g., "all messages"). Device 642 detects input 905i pointing to a return enable display 936 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to the detection of input 905i, device 642 displays a summary 905i pointing to a return enable display 936. Figure 9J The inbox interface is similar to 614.

[0332] exist Figure 9J At this point, device 642 has received message 910e from Issac, which is part of message thread 902. Messages 910a to 910d were not received. Figure 9J The display shows that message thread view option 901 is set to show a collapsed view of message thread 902. Device 642 detects input 905j (e.g., touch input, air gesture, button press, gaze, and / or voice input) directed at message 910e of Issac. In response to the detection of input 905j, device 642 displays... Figure 9K Content interface 616.

[0333] exist Figure 9KAt this location, content interface 616 includes a summary indication 908a above Issac's message 910e (e.g., above header 903e and / or content 922e). As depicted in the expanded indication 900 of message thread 902, summary indication 908a is displayed at position 906d, above Issac's message 910e and below Carrie's message 910d. Issac's message 910e is unread, and Carrie's message 910d is read, as illustrated by status indicator 640. In some embodiments, based on device 642's determination that Carrie's message 910d was previously displayed in content interface 616, Carrie's message 910d is in a read state. In some embodiments, device 642 responds to scrolling... Figure 9E and / or Figure 9F The content interface 616 is used to display Carrie's message 910d, so as to display the content 622d of Carrie's message 910d. Figure 9K As depicted in the expanded representation 900 of message thread 902, device 642 does not display summary capability representation 908a at locations where summary capability representation 908a was previously displayed in message thread 902 (e.g., location 906a and / or location 906b).

[0334] exist Figure 9K In this location, device 642 does not display the previously displayed summary (e.g., Figures 9E to 9F and / or Figure 9I (Summary 924). In some embodiments, device 642 does not display the summary previously displayed in response to detected events (e.g., navigation away from content interface 616, display of inbox interface 614, navigation to an application different from the messaging application corresponding to content interface 616, and / or generation of a different message thread summary).

[0335] exist Figure 9K At this location, device 642 displays multiple options to initiate the process of displaying a summary. In some embodiments, device 642 detects input 905k1 (e.g., touch input, air gesture, button press, gaze, and / or voice input) pointing at the summary display 908a. In such embodiments, in response to detecting input 905k1, device 642 displays a summary of message 910e of Issue (e.g., messages 910a to 910d are not summarized). In such embodiments, device 642 displays the summary at location 906d. Figure 9K At this point, device 642 detects input 905k2 pointing at option 938 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input 905k2, device 642 displays... Figure 9M Message menu 944b and / or Figure 9N Message menu 944b. In Figure 9K At this point, device 642 detects input 905k3 pointing at option 940 (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input 905k3, device 642 displays... Figure 9L The message menu 944a. In some embodiments, option 938 scrolls along with the content of content interface 616. In some embodiments, option 940 scrolls along with the content of content interface 616 (e.g., option 940 is always displayed independently of what content and / or message is currently displayed in content interface 616). In some embodiments, option 940 is located in menu bar 942, which is displayed independently of what content and / or message is currently displayed in content interface 616.

[0336] exist Figure 9L At this location, message menu 944a includes various options corresponding to message 910e and / or message thread 902 of Issac. Message menu 944a includes a summary display 908b. Figure 9L The summary of the capability representation is similar to that of the 908b. Figure 9H The summary representation is 908b, but it has different states. Figure 9L At this location, device 642 detects input 905l pointing at the summary display 908b (e.g., touch input, air gesture, button press, gaze, and / or voice input). In some embodiments, in response to the detection of input 905l, device 642 displays a summary of both read and unread messages in message thread 902 (e.g., a summary based on messages 910a to 910e (e.g., determined based on these messages and / or automatically generated based on these messages (e.g., using an AI process or a generative AI process))). In some embodiments, device 642 displays a summary of both read and unread messages at location 906d, which is related to... Figure 9K A more detailed description is provided. In some embodiments, device 642 displays a summary of both read and unread messages at a location different from location 906d. In some embodiments, device 642 displays a summary of both read and unread messages at location 906c, as per [the description of the previous sentence]. Figure 9I As described. In such embodiments, device 642 may optionally scroll content interface 616 to position 906c in response to the detection of input 905l (e.g., to display a summary of both read and unread messages at position 906c). In some embodiments, message menu 944a includes an enablement for message 910e for replying to Issac, an enablement for replying to all recipients of message thread 902, and / or an enablement for deleting message 910e from Issac.

[0337] exist Figure 9M At that location, device 642 responded to the detection Figure 9K Input 905k2 is used to display message menu 944a. Message menu 944a includes summary display 908c. Summary display 908c is similar to summary displays 908a and 908b, but has a different state. For example, when selected, summary display 908c causes device 642 to display a summary of a single message and / or the currently selected message (e.g., Issac's message 910e). In some embodiments, device 642 detects input 905m (e.g., touch input, air gesture, button press, gaze, and / or voice input) pointing at summary display 908c. In such embodiments, device 642 displays a summary of Issac's message 910e. In some embodiments, a summary of Issac's message 910e is displayed at location 906d. In some embodiments, a summary of Issac's message 910e is displayed at different locations. In some implementations, message menu 944a includes a power indication for message 910e in response to Issac, a power indication for all recipients of message thread 902 in response to message 902, and / or a power indication for message 910e in deletion of Issac.

[0338] exist Figure 9N At that location, device 642 responded to the detection Figure 9K The input is 905k2 (or optionally, Figure 9K The device 642 displays a message menu 944c by input 905k3. The message menu 944c includes a summary display 908d. The summary display 908d is similar to summary displays 908a, 908b, and 908c, but has different states. For example, when selected, summary display 908d causes the device 642 to display a summary of the currently selected message (e.g., message 910e for Issac) and all remaining messages received after the currently selected message in message thread 902. In some embodiments, when selected, summary display 908c causes the device 642 to display a summary of message 910e for Issac and one or more messages received after receiving message 910e for Issac. In some embodiments, the device 642 detects input 905n (e.g., touch input, air gesture, button press, gaze, and / or voice input) directed at summary display 908d. In such implementations, in response to the detection of input 905n, device 642 displays Issac message 910e and one or more messages received after Issac message 910e (e.g., Figure 9PThe summary of message 910e of the Issuer. In some embodiments, the summary enablement representation 908c summarizes one or more messages received after message 910e of the Issuer, regardless of the read status of the one or more messages received after message 910e of the Issuer. In some embodiments, device 642 displays message 910e of the Issuer and a summary of one or more messages received after message 910e of the Issuer at location 906d. In some embodiments, device 642 displays message 910e of the Issuer and a summary of one or more messages received after message 910e of the Issuer at a location different from location 906d. In some embodiments, message menu 944c includes enablement representations for replying to message 910e of the Issuer, replying to enablement representations for all recipients of message thread 902, and / or enablement representations for deleting message 910e of the Issuer.

[0339] exist Figure 9O At location 906d, in response to a request to display a summary of Issac's message 910e (e.g., in response to the detection of input 905k1, input 905m, or input 905n), device 642 displays a summary 924 that summarizes Issac's message 910e. Device 642 displays summary 924 along with an indication of how many messages are included in summary 924, as depicted by reference numeral 912 (e.g., "1 new message"). While displaying summary 924, device 642 receives new messages, such as... Figure 9P What is depicted.

[0340] exist Figure 9P At the point where summary 924 is displayed and as depicted in the expanded representation 900 of message thread 902, device 642 has received message 910f from Issue, including content 922f. As depicted in content interface 616, device 642 maintains the display of summary 924 and an indication of how many messages are included in summary 924 (e.g., "1 new message"). In response to receiving message 910f from Issue, device 642 displays an indication 952 regarding messages not included in summary 924 (e.g., "+1"). In some embodiments, while displaying summary 924, device 642 detects a request to display a new summary (e.g., via option 938 and / or via option 940). In some embodiments, in response to receiving message 910f from Issue and while displaying summary 924, device 642 displays (e.g., redisplays) the content 922f from Issue. Figure 9K The summary energy representation is similar to that of 908a.

[0341] Figure 10This is a flowchart illustrating a method for displaying a message summary capability representation according to some implementation schemes. Method 1000 is performed at a computer system (e.g., 100, 300, 500, 600 and / or 642) (e.g., a smartphone, smartwatch, tablet computer, laptop computer, desktop computer, wearable device and / or head-mounted device), which communicates with display generating components (e.g., 601 and / or 643) (e.g., a display, touchscreen display, monitor, holographic display system and / or head-mounted display system) and one or more input devices (e.g., 602 and / or 643) (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); a mouse; a keyboard; a remote control; a visual input device (e.g., one or more cameras, such as an infrared camera, a depth camera, a visible light camera and / or a gaze-tracking camera); an audio input device (e.g., a microphone); a biometric sensor (e.g., a fingerprint sensor, a facial recognition sensor, a gaze-tracking sensor and / or an iris recognition sensor); and / or one or more mechanical input devices (e.g., a pressable input mechanism; a button; a rotatable input mechanism; a crown; and / or a dial)). Some operations in method 1000 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0342] As described below, Method 1000 provides an intuitive way to display message summary power indicators. This method reduces the cognitive burden on users when viewing message summaries and / or related messages, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to view message summary power indicators and / or message summaries more quickly and efficiently saves power and increases the time interval between battery charging.

[0343] The computer system detects (1002) the display of the first message thread (e.g., 902) via one or more input devices. Figure 6K The message thread described in Figure 6E The message threads and / or described in Figures 6R to 6W and / or Figure 6X One or more messages (e.g., 910a to 910f) of a message thread (e.g., a set of one or more messages with shared characteristics and / or a set of one or more messages shared and / or derived from a common message) as described in the text thread. Figure 6K The message thread described in the text Figure 6E The message thread described in the text and / or Figures 6R to 6W and / or Figure 6XThe request (e.g., 905a, 605c, 605d, 605j, 605l, 605m, 605n, 605o, 605p and / or 605q) for messages (e.g., text messages and / or emails) depicted in the message thread (e.g., text messages and / or emails) includes one or more inputs. In some embodiments, the request to display one or more messages of the first message thread includes a request to display the content (e.g., text, images and / or written content) of one or more messages of the message thread. In response to detecting a request to display one or more messages of the first message thread, the computer system displays (1004) a user interface (e.g., 608, 614, 616 and / or 632) including one or more messages of the first message thread (e.g., the user interface includes the content of one or more messages of the first message thread) via a display generation component, including: determining that the first message is unread (e.g., 910b in Figure 9B The text is unread and / or 910c is in Figure 9C(e.g., not yet read and / or not yet opened), the computer system displays (1006) a first summary element (e.g., 908a) (e.g., selectable graphical user interface element, user interactive graphical user interface element, button, selectable icon and / or display) at a first position (e.g., 906a, 906b, 906c and / or 906d) in the first message thread, wherein when the first summary element is selected, the computer system displays a summary of one or more messages of the first group in the first message thread (e.g., 924, 624d, 624f, 624j, 624k1, 624k2, 624k3-1, 624k3-2, 624k3-3, 624k3-4, 624l, 624m, 624n, 624o, 624p2 and / or 624r) (e.g., text summary and / or graphical summary). In some implementations, the summary of a first group of one or more messages in a first message thread includes a summary of a portion (e.g., at least a portion, some but not all, or all) of the content of the first group of one or more messages in the first message thread. In some implementations, the group of one or more messages is the same as one or more messages requested to be displayed. In some implementations, the group of one or more messages is different from one or more messages requested to be displayed. In some implementations, the computer system detects input pointing to a first summary element and, in response, displays a summary of a portion of the content of one or more messages in the first message thread. In response to detecting a request to display one or more messages in the first message thread, the computer system displays (1004) a user interface (e.g., 608, 614, 616, and / or 632) including one or more messages in the first message thread (e.g., the user interface includes the content of one or more messages in the first message thread) via a display generation component, including: determining that the first message is not unread (e.g., 910b in Figure 9C The text is incomplete and contains numerous errors. A direct translation isn't possible without further context or a clearer understanding of the intended message. Figure 9KIn some embodiments, in response to a selection of the first summary element being detected when it is displayed in a second position (e.g., 906a, 906b, and / or 906d) within the first message thread, the computer system displays (1008) a first summary element, wherein the second position differs from the first position (e.g., the position of the first summary element within the first message thread is based on whether the first message has been read). In some embodiments, in response to a selection of the first summary element being detected when it is displayed in a second position within the first message thread, the computer system displays a summary based on a first set of one or more messages of the first message thread (e.g., determined based on these messages and / or automatically generated based on these messages (e.g., using an AI process or a generative AI process)) (or optionally, a second set of one or more messages of the first message thread, wherein the second set of one or more messages differs from the first set of one or more messages). In some embodiments, displaying the first summary element in the first position includes displaying the first summary element in a first orientation (e.g., relative to one or more messages of the first message thread), and displaying the first summary element in the second position includes displaying the first summary element in a second orientation different from the first orientation (e.g., the first summary element is displayed in different orientations at different positions within the first message thread). In some embodiments, the first summary element is embedded (e.g., inserted, placed, and / or positioned at a fixed location) within a first message thread. In some embodiments, when the first summary element is displayed at a first position, the computer system detects a request to scroll the first message thread (e.g., scroll one or more messages and / or the content of one or more messages in the first message thread), and in response, concurrently scrolls the first message thread and the first summary element (e.g., the first summary element scrolls along with the content of the first message thread and / or maintains the same position relative to the first message thread as the first message thread is scrolled). In some embodiments, the first summary is generated via one or more machine learning algorithms (e.g., large language models and / or diffusion models) (e.g., the first summary includes automatically generated text content and / or generative text content). In some embodiments, the first summary is generated via artificial intelligence processes (e.g., generative AI) (e.g., including automatically generated text content and / or generative text content). The first summary element is conditionally displayed at different locations in the first message thread based on whether the first message is unread. This allows actions to be performed when a set of conditions have been met without requiring further user input, provides additional control options without cluttering the user interface, and reduces the amount of input required to perform actions such as navigating to a summary button and / or generating a summary.

[0344] In some implementations, the first summary element is displayed at a first position in the first message thread (e.g., 908a is displayed in...). Figure 9CFollowing (e.g., in response to a request to display one or more messages in the first message thread, based on determining that the first message is unread, and / or after the computer system has navigated away from a user interface including one or more messages in the first message thread), the computer system detects a second request (e.g., 905j) via one or more input devices to display one or more messages in the first message thread (e.g., the first message thread is the same as or different from one or more previously displayed messages). In response to the detection of the second request to display one or more messages in the first message thread, the computer system displays the first summary element at a third position (e.g., 906a, 906b, and / or 906d) in the first message thread via a display generation component, wherein the third position is different from the first position (and / or the second position). In some embodiments, the computer system displays the first summary element at the third position based on detecting that the first message is not unread (e.g., is read). For example, in some embodiments, when the user navigates back to a user interface including one or more messages in the message thread (e.g., after navigating away from a user interface including one or more messages in the message thread), the computer system displays the first summary element at a different location. In some embodiments, the third position is the same as the second position. Displaying the first summary element at a different location in the first message thread after it has already been displayed in the first location provides additional control options without cluttering the user interface and reduces the amount of input required to perform actions such as navigating to the summary button and / or generating a summary.

[0345] In some implementations, when displaying a user interface including one or more messages comprising a first message thread, the computer system detects input directed to a first profile element (e.g., 905b3, 905c, and / or 905k1) via one or more input devices (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input directed to the first profile element and determining that the first profile element is displayed at a first location (e.g., 906a, 906b, and / or 906d) (e.g., and / or determining that the first message is unread), the computer system displays a first profile (e.g., 924 and / or 624p1) based on the first message (e.g., determined based on the first message and / or automatically generated based on the first message (e.g., using an AI process or a generative AI process)) via a display generation component. Figure 9F924 is based on 910b). In response to detecting input pointing to the first summary element and determining that the first summary element is displayed at a second location (e.g., 906a, 906b, and / or 906d) (e.g., and / or determining that the first message is not unread), the computer system displays a second summary (e.g., 924 and / or 624p1) based on a second message different from the first message (e.g., determined based on the second message and / or automatically generated based on the second message (e.g., using an AI process or a generative AI process)). Figure 9E The 924 is based on 910c and / or 910d). In some implementations, the second summary is not based on the first message (e.g., Figure 9E 924 is not based on 910b (e.g., when the first summary is in the first position, the summary generated from the first summary element is based on the first message, and when the first summary element is in the second position, the summary generated from the first summary element is not based on the first message). In some embodiments, based on determining that the first summary element is displayed in the first position (e.g., and / or based on determining that the first message is unread), the computer system displays a summary based on both the first message and the second message (e.g., determined based on these messages and / or automatically generated based on these messages (e.g., using an AI process or a generative AI process)). Displaying a summary conditionally based on the first message based on whether the first summary element is displayed in the first or second position performs actions without requiring further user input when a set of conditions have been met, provides additional control options without cluttering the user interface, reduces the amount of input required to perform actions (e.g., navigating to a summary button and / or generating a summary), and selectively summarizes unread messages to reveal relevant information.

[0346] In some implementations, the second message is unread (e.g., Figure 9E (910c and / or 910d in the first message are unread). When the first message is read, a summary of the second message based on the unread message is displayed instead of the first message. This provides additional control options without cluttering the user interface, reduces the amount of input required to perform operations, and selectively summarizes unread messages to display relevant information.

[0347] In some implementations, when the first summary element (e.g., 908a) is displayed at a first position (e.g., 906a) (and / or a second position) in the first message thread, the computer system detects input directed at the first summary element (e.g., 905b3) via one or more input devices (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input directed at the first summary element, the computer system displays a summary of a first group of one or more messages in the first message thread (e.g., 924 and / or 624p1) via a display generation component (e.g., 924 is displayed on...). Figure 9H (e.g., at 906a in the first message thread); in some embodiments, the summary is embedded (e.g., inserted, placed, and / or positioned at a fixed location) within the first message thread. In some embodiments, the computer system scrolls the summary in response to detecting a request to scroll one or more messages of the first message thread. In some embodiments, the computer system stops displaying the summary element in response to detecting input pointing to a first summary element (and / or in response to displaying a summary of one or more messages of the first message thread). In some embodiments, after displaying a summary of the first group of one or more messages of the first message thread, the computer system detects an event (e.g., input pointing to 908b, input pointing to 936, 905j, 905i, etc.). Figure 9J The depicted inbox display interface 614 allows viewing different messages and / or different message threads, and / or, as well as... Figures 6M to 6OThe described event involves bringing 632 and / or 616 to the foreground after they have been moved to the background (e.g., an event corresponding to a first message thread and / or an event corresponding to displaying a second summary different from the summary of one or more messages of the first message thread). In some embodiments, the detection event includes: the computer system detecting that the computer system has navigated away from (e.g., and / or subsequently returned to) a user interface including one or more messages of the first message thread. In some embodiments, the detection event includes: the computer system detecting a request to display a summary of a second set of one or more messages, which is different from the first set of one or more messages of the first message thread (e.g., where the second set of one or more messages corresponds to a different message thread and / or a different set of messages of the same message thread). In some embodiments, the detection event includes: the computer system detecting that the summary of the first set of one or more messages of the first message thread has become outdated (e.g., the state of the message thread has changed). In some embodiments, the first message thread becomes outdated in response to the computer system detecting that a new message has been received and / or detecting that an unread message of the first message thread has changed to a read message. In some implementations, in response to the detection of an event (or optionally, after the event is detected), the computer system displays a user interface including one or more messages from a first message thread, without displaying a summary in the first message thread (e.g., 924 is not displayed). Figure 9I At position 906a, and / or 924 is not displayed. Figure 9K (e.g., at 906a, 906b, and / or 906c) (e.g., the computer system no longer displays a summary in the first message thread). In some embodiments, in response to detecting an event, the computer system removes (e.g., deletes and / or erases) the summary from the first message thread. In some embodiments, after detecting an event, the computer system detects a request to display one or more messages of the first message thread, and in response, displays one or more messages without displaying a summary of that set of one or more messages. Displaying a user interface that includes one or more messages of the first message thread in response to detecting an event, without displaying a summary in the first message thread, reduces the amount of input required to perform operations and makes the user interface cleaner.

[0348] In some implementations, when the first profile element is displayed in a first position in the first message thread, the computer system detects input directed to the first profile element (e.g., 905b3, 905c, and / or 905k1) via one or more input devices (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input directed to the first profile element, the computer system displays a summary of a corresponding set of one or more messages in the first message thread (e.g., 924 and / or 624p1) via a display generation component (e.g., ...). Figure 9E The 924 in the text is based on the 910c and 910d, and / or Figure 9F The 924 in the text is based on 910b, 910c, and 910d), and the number of messages in a corresponding set of one or more messages (e.g., Figure 9E and Figure 9F The summary is indicated by a number (e.g., 912) of “2 new messages” and / or “3 new messages” (e.g., number and / or quantity) (e.g., a summary displayed along with an indication of the number of messages on which the summary is based). In some embodiments, the summary is based on unread messages (e.g., determined based on the message and / or automatically generated based on the message (e.g., using an AI process or a generative AI process)) rather than read messages. In some embodiments, the indication of the number of one or more messages on which the summary is based is an indication of the number of unread messages on which the summary is based. Responding to the detection of input directed to a first summary element, a summary of a corresponding set of one or more messages of a first message thread is displayed, along with an indication of the number of messages in the corresponding set of one or more messages. This provides visual feedback about the status of the summary and / or what messages are included in the summary.

[0349] In some implementations, when the first profile element is displayed in a first position in the first message thread, the computer system detects input directed to the first profile element (e.g., 905b3, 905c, and / or 905k1) via one or more input devices (e.g., touch input, air gesture, button press, gaze, and / or voice input). In response to detecting input directed to the first profile element, the computer system displays a summary of a corresponding set of one or more messages in the first message thread (e.g., 924 and / or 624p1) via a display generation component (e.g., ...). Figure 9E The 924 in the text is based on the 910c and 910d, and / or Figure 9F 924 (based on 910b, 910c, and 910d) and optional feedback elements (e.g., 926, 928, and / or 930) (e.g., user-interactive graphical user interface elements, buttons, selectable icons, and / or display indicators), which, when selected, initiate a process for conveying feedback on the summary (e.g., difficulty, problem, positive feedback, and / or negative feedback) (e.g., as about...). Figures 9F to 9GAs described, 928 includes options for initiating communication to provide feedback to 924, such as 930 (e.g., a summary is displayed along with a button for providing feedback). In some embodiments, the computer system detects input pointing to a selectable object and, in response, initiates a process for conveying feedback to the summary. Responding to the detection of input pointing to a first summary element, a summary of a corresponding set of one or more...

Claims

1. A method, the method comprising: At the computer system that communicates with the display generation components and one or more input devices: Displaying a first user interface via the display generation component includes: Based on the determination that the first set of criteria is met, a summary of the content based on the first message is displayed; When displaying the summary of the content based on the first message, a request to display the first message is detected via the one or more input devices; In response to detecting the request to display the first message, the first message is displayed via the display generation component; and After the first message is displayed, the first user interface is displayed via the display generation component, including displaying at least a portion of the content of the first message without displaying the summary.

2. The method of claim 1, wherein displaying the first message comprises: The first message is displayed in a second user interface, which is different from the first user interface, instead of the summary being displayed in the second user interface.

3. The method according to any one of claims 1 to 2, wherein displaying the first user interface comprises concurrently displaying: The summary based on the content of the first message; and At least a portion of the second message, without displaying a summary based on the content of the second message.

4. The method according to any one of claims 1 to 3, further comprising: When displaying the summary based on the content of the first message: Based on the determination that a set of indication criteria is met, an indication is displayed regarding the summary being displayed, wherein the set of indication criteria is different from the first set of criteria.

5. The method according to any one of claims 1 to 4, wherein the set of indication criteria includes criteria satisfied when an event is detected.

6. The method according to any one of claims 1 to 5, wherein the summary is based on the content of a second message different from the first message.

7. The method of claim 6, wherein the first set of criteria includes criteria satisfied when a threshold number of messages are received within a threshold time period.

8. The method according to any one of claims 1 to 7, wherein the first set of criteria includes criteria satisfied when the profile settings are activated.

9. The method according to any one of claims 1 to 8, wherein the first set of criteria includes criteria satisfied when the content of the first message satisfies a threshold amount of content.

10. The method according to any one of claims 1 to 9, wherein the first set of criteria includes criteria satisfied when the first message is in an unread state.

11. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 1 to 10.

12. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method according to any one of claims 1 to 10.

13. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Components for performing the method according to any one of claims 1 to 10.

14. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 10.

15. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: Displaying a first user interface via the display generation component includes: Based on the determination that the first set of criteria is met, a summary of the content based on the first message is displayed; When displaying the summary of the content based on the first message, a request to display the first message is detected via the one or more input devices; In response to detecting the request to display the first message, the first message is displayed via the display generation component; as well as After the first message is displayed, the first user interface is displayed via the display generation component, including displaying at least a portion of the content of the first message without displaying the summary.

16. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: Displaying a first user interface via the display generation component includes: Based on the determination that the first set of criteria is met, a summary of the content based on the first message is displayed; When displaying the summary of the content based on the first message, a request to display the first message is detected via the one or more input devices; In response to detecting the request to display the first message, the first message is displayed via the display generation component; and After the first message is displayed, the first user interface is displayed via the display generation component, including displaying at least a portion of the content of the first message without displaying the summary.

17. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Components for displaying a first user interface via the display generation component include: Based on the determination that the first set of criteria is met, a summary of the content based on the first message is displayed; The component is used to detect a request to display the first message via the one or more input devices when displaying a summary of the content based on the first message; Components for: displaying the first message via the display generation component in response to detecting the request to display the first message; and The component is used for displaying the first user interface via the display generation component after the first message is displayed, including displaying at least a portion of the content of the first message without displaying the summary.

18. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: Displaying a first user interface via the display generation component includes: Based on the determination that the first set of criteria is met, a summary of the content based on the first message is displayed; When displaying the summary of the content based on the first message, a request to display the first message is detected via the one or more input devices; In response to detecting the request to display the first message, the first message is displayed via the display generation component; as well as After the first message is displayed, the first user interface is displayed via the display generation component, including displaying at least a portion of the content of the first message without displaying the summary.

19. A method comprising: At the computer system communicating with the display generation component: Receive a first message containing first content and a second message containing second content, which is different from the first message; A first summary of the first content based on the first message and the second content based on the second message is displayed via the display generation component; After displaying the first summary, a third message associated with the first message and the second message is received, wherein the third message includes third content; as well as Upon receiving the third message and based on the determination that the first set of criteria is met, a second summary, different from the first summary, is displayed via the display generation component, wherein the second summary is based on the third content of the third message.

20. The method of claim 19, wherein displaying the second summary comprises: Based on the determination that the first message is unread, the second summary is based on the first content; as well as Based on the determination that the first message is not in an unread state, the second summary is not based on the first content.

21. The method of claim 19, wherein after the first message has been opened, the second summary is based on the first content.

22. The method according to any one of claims 19 to 21, wherein: The second summary is based on the first content; The first message comes from the first sender; and The third message comes from a second sender that is different from the first sender.

23. The method of claim 22, wherein the second summary includes instructions to the first transmitter and instructions to the second transmitter.

24. The method according to any one of claims 19 to 23, wherein the second summary is displayed independently of the state of the third message.

25. The method according to any one of claims 19 to 24, further comprising: Before the second summary is displayed, the first summary and the third content are displayed concurrently via the display generation component.

26. The method according to any one of claims 19 to 25, wherein: The first message, the second message, and the third message are messages from a communication application; and The first set of criteria includes criteria that are satisfied by the following condition: the communication application is already inactive after receiving the third message.

27. The method of any one of claims 19 to 26, wherein the first set of criteria includes criteria satisfied when the second summary is generated within a threshold time period of receiving the third message, the method further comprising: Upon receiving the third message and determining that the first set of criteria is not met, at least a portion of the third content is displayed instead of the second summary.

28. The method according to any one of claims 19 to 27, further comprising: Upon receiving the first message, a third summary based on the first content is displayed via the display generation component, wherein the third summary differs from the second summary.

29. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 19 to 28.

30. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method according to any one of claims 19 to 28.

31. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Components for performing the method according to any one of claims 19 to 28.

32. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 19 to 28.

33. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: Receive a first message containing first content and a second message containing second content, which is different from the first message; A first summary of the first content based on the first message and the second content based on the second message is displayed via the display generation component; After displaying the first summary, a third message associated with the first message and the second message is received, wherein the third message includes third content; as well as Upon receiving the third message and based on the determination that the first set of criteria is met, a second summary, different from the first summary, is displayed via the display generation component, wherein the second summary is based on the third content of the third message.

34. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: Receive a first message containing first content and a second message containing second content, which is different from the first message; A first summary of the first content based on the first message and the second content based on the second message is displayed via the display generation component; After displaying the first summary, a third message associated with the first message and the second message is received, wherein the third message includes third content; as well as Upon receiving the third message and based on the determination that the first set of criteria is met, a second summary, different from the first summary, is displayed via the display generation component, wherein the second summary is based on the third content of the third message.

35. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for receiving a first message including first content and a second message including second content, which is different from the first message; A component for displaying a first summary of the first content based on the first message and the second content based on the second message via the display generation component; The component is used to: after displaying the first summary, receive a third message associated with the first message and the second message, wherein the third message includes third content; and The component is used to: upon receiving the third message and based on determining that a first set of criteria is met, display a second summary, different from the first summary, via the display generation component, wherein the second summary is based on the third content of the third message.

36. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the following operations: Receive a first message containing first content and a second message containing second content, which is different from the first message; A first summary of the first content based on the first message and the second content based on the second message is displayed via the display generation component; After displaying the first summary, a third message associated with the first message and the second message is received, wherein the third message includes third content; as well as Upon receiving the third message and based on the determination that the first set of criteria is met, a second summary, different from the first summary, is displayed via the display generation component, wherein the second summary is based on the third content of the third message.

37. A method, the method comprising: At the computer system that communicates with the display generation components and one or more input devices: A request to display one or more messages of the first message thread is detected via the one or more input devices; as well as In response to detecting a request to display one or more messages from the first message thread, displaying a user interface including the one or more messages from the first message thread via the display generation component includes: Based on the determination that the first message is unread, a first summary element is displayed at a first position in the first message thread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages in the first message thread; as well as Based on the determination that the first message is not unread, the first summary element is displayed at a second position in the first message thread, wherein the second position is different from the first position.

38. The method according to claim 37, further comprising: After the first summary element is displayed at the first position in the first message thread, a second request to display one or more messages of the first message thread is detected via the one or more input devices; as well as In response to detecting a second request to display one or more messages of the first message thread, the first summary element is displayed at a third position in the first message thread via the display generation component, wherein the third position is different from the first position.

39. The method according to any one of claims 37 to 38, further comprising: When displaying the user interface including the one or more messages from the first message thread: Input directed to the first profile element is detected via the one or more input devices; as well as In response to detecting the input directed to the first profile element: Based on the determination that the first summary element is displayed at the first position, a first summary based on the first message is displayed via the display generation component; as well as Based on the determination that the first summary element is displayed at the second position, a second summary based on a second message different from the first message is displayed via the display generation component, wherein the second summary is not based on the first message.

40. The method of claim 39, wherein the second message is unread.

41. The method according to any one of claims 39 to 40, further comprising: When the first profile element is displayed at the first position in the first message thread, input directed to the first profile element is detected via the one or more input devices; In response to detecting the input directed to the first summary element, a summary of the first group of one or more messages of the first message thread is displayed in the first message thread and via the display generation component; After displaying the summary of the first group or more messages of the first message thread, an event is detected; as well as In response to the detection of the event, the user interface including the one or more messages of the first message thread is displayed, without displaying the summary in the first message thread.

42. The method according to any one of claims 37 to 41, further comprising: When the first profile element is displayed in the first position of the first message thread, input directed to the first profile element is detected via the one or more input devices; as well as In response to detecting the input directed to the first profile element, the following is displayed via the display generation component: A summary of the corresponding group or more messages in the first message thread; and An indication of the number of messages in one or more messages in the corresponding group.

43. The method according to any one of claims 37 to 42, further comprising: When the first profile element is displayed in the first position of the first message thread, input directed to the first profile element is detected via the one or more input devices; as well as In response to detecting the input directed to the first profile element, the following is displayed via the display generation component: A summary of one or more messages in the corresponding group of the first message thread; and An optional feedback element, which, when selected, initiates a process for conveying feedback to the summary.

44. The method of any one of claims 37 to 43, wherein the second position in the first message thread is between the first message and a second message different from the first message, wherein the second message is unread.

45. The method of any one of claims 37 to 44, wherein the user interface for displaying the one or more messages including the first message thread comprises: A second summary element is displayed at a third position in the first message thread, wherein the third position is different from the first position and the second position, and wherein the second summary element, when selected, causes the computer system to display a summary of a corresponding group or more messages of the first message thread.

46. ​​The method of claim 45, wherein: When the first summary element is selected, the computer system displays a summary based on unread messages in the first message thread, but not on read messages; and When the second summary element is selected, the computer system displays a summary based on read and unread messages in the first message thread.

47. The method according to any one of claims 37 to 46, the method further comprising: When the first summary element is displayed at the first location, input pointing to the corresponding option element is detected via the one or more input devices; as well as In response to detecting the input pointing to the corresponding option element, a third summary element is displayed via the display generation component. When selected, the third summary element causes the computer system to display a summary based on a third group of one or more messages in the first message thread, wherein the third group of one or more messages is different from the first group of one or more messages.

48. The method of claim 47, wherein causing the computer system to display the summary based on the third group or more messages in the first message thread comprises: Based on the determination that the corresponding option element is the first option element, the computer system displays a summary of all messages based on the first message thread.

49. The method of any one of claims 47 to 48, wherein causing the computer system to display a summary based on the third group or more messages in the first message thread comprises: Based on the determination that the corresponding option element is a second option element, the computer system displays a summary of a single message based on the first message thread.

50. The method according to any one of claims 37 to 49, the method further comprising: Detect requests to scroll beyond the boundaries of the first message thread via one or more input devices; as well as In response to the request that the scrolling exceeds the boundary of the first message thread: Shift the first message thread; and Displays a summary of one or more messages from the first message thread.

51. The method according to any one of claims 37 to 50, the method further comprising: Requests to display one or more messages of the second message thread are detected via the one or more input devices; as well as In response to detecting a request to display one or more messages from the second message thread, displaying a user interface including the one or more messages from the second message thread via the display generation component includes: Based on the determination that the first message of the second message thread is unread, a fourth summary element is displayed at a first position in the second message thread, wherein the fourth summary element summarizes the first group of one or more messages of the second message thread; as well as Based on the determination that the first message in the second message thread is not unread, the fourth summary element is displayed at a second position in the second message thread, the second position being different from the first position in the second message thread.

52. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 37 to 51.

53. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method according to any one of claims 37 to 51.

54. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Components for performing the method according to any one of claims 37 to 51.

55. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system communicating with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 37 to 51.

56. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: A request to display one or more messages of the first message thread is detected via the one or more input devices; as well as In response to detecting a request to display one or more messages from the first message thread, displaying a user interface including the one or more messages from the first message thread via the display generation component includes: Based on the determination that the first message is unread, a first summary element is displayed at a first position in the first message thread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages in the first message thread; as well as Based on the determination that the first message is not unread, the first summary element is displayed at a second position in the first message thread, wherein the second position is different from the first position.

57. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: One or more processors; and The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: A request to display one or more messages of the first message thread is detected via the one or more input devices; as well as In response to detecting a request to display one or more messages from the first message thread, displaying a user interface including the one or more messages from the first message thread via the display generation component includes: Based on the determination that the first message is unread, a first summary element is displayed at a first position in the first message thread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages in the first message thread; as well as Based on the determination that the first message is not unread, the first summary element is displayed at a second position in the first message thread, wherein the second position is different from the first position.

58. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for detecting a request to display one or more messages of the first message thread via the one or more input devices; and A component for displaying a user interface including the one or more messages of the first message thread via the display generation component in response to detecting a request to display the one or more messages of the first message thread, comprising: Based on the determination that the first message is unread, a first summary element is displayed at a first position in the first message thread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages in the first message thread; as well as Based on the determination that the first message is not unread, the first summary element is displayed at a second position in the first message thread, wherein the second position is different from the first position.

59. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the following operations: A request to display one or more messages of the first message thread is detected via the one or more input devices; as well as In response to detecting a request to display one or more messages from the first message thread, displaying a user interface including the one or more messages from the first message thread via the display generation component includes: Based on the determination that the first message is unread, a first summary element is displayed at a first position in the first message thread, wherein the first summary element, when selected, causes the computer system to display a summary of a first group of one or more messages in the first message thread; as well as Based on the determination that the first message is not unread, the first summary element is displayed at a second position in the first message thread, wherein the second position is different from the first position.

Images