A user interface for displaying, transmitting, and receiving communications.

Abstract

Some embodiments described in this disclosure relate to one or more electronic devices that display multiple user interfaces corresponding to messaging in a hybrid group messaging conversation. Some embodiments described in this disclosure relate to adding users to a hybrid group messaging conversation. Some embodiments described in this disclosure relate to deleting a hybrid group messaging conversation.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 500,975, filed May 9, 2023, the disclosure of which is incorporated herein by reference in its entirety for all purposes.

[0002] The present disclosure generally relates to user interfaces associated with displaying, transmitting, and receiving communications with an electronic device.

Background Art

[0003] In recent years, the interaction of users with electronic devices has increased significantly. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, etc. In some situations, a user may desire to use such devices to send and receive communications. Enhancing the interaction with the user's device improves the user experience with the device and reduces the time of user interaction, which is particularly important when the input device operates on battery power.

Summary of the Invention

[0004] Some embodiments described in the present disclosure are directed to one or more electronic devices that display multiple user interfaces corresponding to messaging in a hybrid group messaging conversation. Some embodiments described in the present disclosure are directed to adding a user to a hybrid group messaging conversation. Some embodiments described in the present disclosure are directed to deleting a hybrid group messaging conversation. It should be understood that the full description of these embodiments is set forth in the "Detailed Description of the Invention" and the above "Summary of the Invention" in no way limits the scope of the present disclosure.

[0005] It is well understood that the use of personally identifiable information should be governed by privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0006] For a better understanding of the various embodiments described, please refer to the following “Modes for Carrying Out the Invention” in conjunction with the drawings. Similar reference numbers refer to corresponding parts throughout those drawings. [Brief explanation of the drawing]

[0007] [Figure 1A] This is a block diagram showing a portable multifunctional device with a touch-sensitive display according to several embodiments.

[0008] [Figure 1B] This is a block diagram illustrating exemplary components for event handling according to several embodiments.

[0009] [Figure 2] This figure shows a portable multifunctional device having a touchscreen according to several embodiments.

[0010] [Figure 3] This is a block diagram of an exemplary multifunctional device comprising a display and a touch-sensitive surface, according to several embodiments.

[0011] [Figure 4A] This figure shows an exemplary user interface for an application menu on a portable multifunction device, according to several embodiments.

[0012] [Figure 4B] An exemplary user interface related to a multi-functional device with a touch sensing surface separate from a display, according to some embodiments, is shown.

[0013] [Figure 5A] A diagram showing a personal electronic device according to some embodiments.

[0014] [Figure 5B] A block diagram showing a personal electronic device according to some embodiments.

[0015] [Figure 5C] A diagram showing exemplary components of a personal electronic device having a touch sensing display and an intensity sensor, according to some embodiments. [Figure 5D] A diagram showing exemplary components of a personal electronic device having a touch sensing display and an intensity sensor, according to some embodiments.

[0016] [Figure 5E] Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown. [Figure 5F] Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown. [Figure 5G] Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown. [Figure 5H] Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown.

[0017] [Figure 6A] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6B]An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6C] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6D] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6E] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6F] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6G] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6H] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6I] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6J] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown. [Figure 6K] An example of an electronic device adding one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure is shown.

[0018] [Figure 7A] It is a flowchart showing a method for an electronic device to add one or more users to a hybrid group messaging conversation according to some embodiments of the present disclosure. [Figure 7B] This flowchart illustrates how an electronic device can add one or more users to a hybrid group messaging conversation, according to some embodiments of the present disclosure. [Figure 7C] This flowchart illustrates how an electronic device can add one or more users to a hybrid group messaging conversation, according to some embodiments of the present disclosure. [Figure 7D] This flowchart illustrates how an electronic device can add one or more users to a hybrid group messaging conversation, according to some embodiments of the present disclosure. [Figure 7E] This flowchart illustrates how an electronic device can add one or more users to a hybrid group messaging conversation, according to some embodiments of the present disclosure.

[0019] [Figure 8A] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8B] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8C] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8D] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8E] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8F] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8G] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8H] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8I] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure. [Figure 8J] This disclosure describes an example in which an electronic device deletes a hybrid group messaging conversation, according to some embodiments of this disclosure.

[0020] [Figure 9A] This flowchart illustrates how an electronic device deletes a hybrid group messaging conversation according to some embodiments of the present disclosure. [Figure 9B] This flowchart illustrates how an electronic device deletes a hybrid group messaging conversation according to some embodiments of the present disclosure. [Figure 9C] This flowchart illustrates how an electronic device deletes a hybrid group messaging conversation according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0021] The following description of embodiments refers to accompanying drawings that constitute a portion of the embodiments, which illustrate specific embodiments that may be implemented as an option. It should be understood that other embodiments may be used as an option and structural modifications may be implemented as an option without departing from the scope of the disclosed embodiments.

[0022] Electronic devices need to communicate with and receive communications from devices using different messaging services. Furthermore, when a group messaging conversation includes members using different messaging services (e.g., a hybrid group messaging conversation), the electronic device also needs to facilitate the addition and removal of users from the group messaging conversation. In some embodiments, the electronic device initiates a process to generate a new group messaging conversation when a user of the electronic device attempts to add a user to a hybrid group messaging conversation. Such a technique allows users to modify the membership of a hybrid group messaging conversation without requiring manual user input to create such a conversation.

[0023] There is a need for an electronic device that facilitates the deletion and blocking of hybrid group messaging conversations. In some embodiments, the electronic device initiates a process to delete hybrid group messaging conversations within a messaging application. Such a technique allows users to remove themselves from unwanted group messaging activity, thereby reducing resource consumption by the electronic device and reducing the manual user input required to delete hybrid group messaging conversations.

[0024] In the following description, terms such as “first,” “second,” etc., are used to describe various elements, but these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, the first touch may be called the second touch, and similarly, the second touch may be called the first touch. Both the first touch and the second touch are touches, but they are not the same touch.

[0025] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and is not intended to be limiting. In the descriptions of the various embodiments and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless otherwise specified in the context. Furthermore, it should be understood that, as used herein, the terms "and / or" refer to and include any and all possible combinations of one or more of the enumerated items relating to the invention. It will be further understood that, as used herein, the terms "includes," "including," "comprises," and / or "comprising" specify the presence of the described functions, integers, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other functions, integers, steps, actions, elements, components, and / or groups thereof.

[0026] The phrase "if" can be interpreted, at will, depending on the context, as "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" can be interpreted, at will, depending on the context, as "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]." Example device

[0027] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, which also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), are also optionally used. Also, in some embodiments, it should be understood that the device is not a portable communication device but a desktop computer or television with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the device does not have a touchscreen display and / or touchpad, but rather can output display information (e.g., the user interfaces of this disclosure) for display on another display device and can receive input information from another input device having one or more input mechanisms (e.g., one or more buttons, touchscreen displays and / or touchpads). In some embodiments, the device has a display but can receive input information from another input device having one or more input mechanisms (e.g., one or more buttons, a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system communicating with a display generating component (e.g., via wired communication, via wireless communication). The display generating component is configured to provide a visual output such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system.When used herein, "display" content includes displaying content (e.g., video data rendered or decoded by the display controller 156) by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component in order to visually generate the content.

[0028] The following discussion describes an electronic device including a display and a touch-sensitive surface. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick. Furthermore, as stated above, it should be understood that the electronic device, display, and touch-sensitive surface described may optionally be distributed among two or more devices. Therefore, as used in this disclosure, information displayed on or by an electronic device may optionally be used to describe information output by the electronic device for display on a separate display device (touch-sensitive or non-touch-sensitive). Similarly, as used in this disclosure, input received on an electronic device (e.g., touch input received on the touch-sensitive surface of the electronic device) may optionally be used to describe input received on another input device. From this other input device, the electronic device receives input information.

[0029] The device generally supports a variety of applications, including drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback applications, TV channel viewing applications, and / or digital video playback applications.

[0030] Various applications running on this device optionally utilize at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or modified on an application-by-application basis and / or within individual applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports a variety of applications with intuitive and transparent user interfaces for the user.

[0031] Here, we focus on embodiments of portable or non-portable devices equipped with a touch-sensitive display. However, as mentioned above, these devices do not necessarily have to include a touch-sensitive display or display. Figure 1A is a block diagram of a portable or non-portable multifunctional device 100 equipped with a touch-sensitive display 112 according to some embodiments. The touch-sensitive display 112 may be referred to as a “touchscreen” for convenience, and may be known or referred to as a touch-sensitive display system. Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or 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 intensity sensors 165 (e.g., touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100) that detect the intensity of contact on Device 100. Device 100 optionally includes one or more tactile output generators 167 that generate tactile outputs on Device 100 (e.g., on touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0032] As used herein and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact on the touch-sensitive surface (e.g., finger contact), or a substitute for the force or pressure of contact on the touch-sensitive surface. The strength of contact has a range of values, including at least four distinct values, and more typically, including several hundred (e.g., at least 256) distinct values. The strength of contact is optionally 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 touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine the estimated force of contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or modification of the contact area detected on the touch-sensing surface, the capacitance and / or modification of the touch-sensing surface adjacent to the contact, and / or the resistance and / or modification of the touch-sensing surface adjacent to the contact may optionally be used as a substitute for the force or pressure of the contact on the touch-sensing surface. In some implementations, the substitute measurement for the force or pressure of the contact is used directly to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of contact as an attribute of user input, it becomes possible for users to access additional device functions that may otherwise be inaccessible (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical control such as a knob or button) on reduced-size devices where the implementation area for displaying affordances is limited.

[0033] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their 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 properties of the device or a component of the device. For example, the movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user’s action. As another example, movement of a touch-sensitive surface can be optionally interpreted or perceived by a user as "roughness" of that surface, even if there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the user's personal sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that would produce the described sensory perception for a typical (or average) user.

[0034] Device 100 is merely one embodiment of a portable or non-portable multifunctional device, and it should be understood that 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 components. The various components shown in Figure 1A are implemented in the form of hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application-specific integrated circuits. Furthermore, the various components shown in Figure 1A may optionally be implemented across two or more devices, such as a display and audio circuitry on a display device, a touch-sensing surface on an input device, and the remaining components on Device 100. In such embodiments, Device 100 may optionally communicate with, or optionally be included within, a display and / or input device, the various components described herein relating to the display and / or input devices and the remaining display and / or input devices within Device 100, in order to facilitate the operation of the system described herein.

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

[0036] The peripheral device interface 118 can be used to connect the device's input and output peripherals to the CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data.

[0037] In some embodiments, the 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.

[0038] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, which include, but are 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, and memory. The 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 telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. The RF circuit 108 optionally includes a well-known circuit for detecting a near-field communication (NFC) field using a short-range communication radio. Wireless communication is not limited to this, but optionally includes Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPADA), and long-term evolution.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), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, Email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant messaging (e.g., Extensible Messaging and Presence Protocol) Using any of several communication standards, protocols, and technologies, including the XMPP protocol, the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this specification.

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

[0040] The I / O subsystem 106 connects input / output peripherals on device 100, such as the touchscreen 112 and other input control devices 116, to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from and transmit electrical signals to the other input or control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controllers 160 are optionally coupled to or not coupled to any of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., 208 in Figure 2) optionally include up / down buttons for adjusting the volume of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in Figure 2).

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

[0042] The touch-sensitive display 112 provides input and output interfaces between the device and the user. As described above, the touch-sensing operation and display operation of the touch-sensitive display 112 are optionally separated from each other, so that the display device is used for display purposes and the touch-sensing surface (whether or not it is a display) is used for input detection purposes. Accordingly, the components and functions described are modified. However, for the sake of brevity, the following description is provided with reference to the touch-sensitive display. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touchscreen 112. The touchscreen 112 displays a visual output to the user. This visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively, “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects.

[0043] The touchscreen 112 has a touch-sensing surface, sensor, or set of sensors that accept user input based on tactile and / or tactile contact. The touchscreen 112 and the display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of contact) on the touchscreen 112 and translate the detected contact into interaction with user interface objects displayed on the touchscreen 112 (e.g., one or more soft keys, icons, web pages, or images). In an exemplary embodiment, the point of contact between the touchscreen 112 and the user corresponds to the user's finger.

[0044] The touchscreen 112 optionally uses LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies may also be used in other embodiments. The touchscreen 112 and the display controller 156 optionally, but not limited to, use any of several currently known or future-developed touch sensing technologies, including capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more contact points with the touchscreen 112, to detect contact and any movement or interruption thereof. In one exemplary embodiment, projected mutual capacitance sensing technology is used, as seen in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

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

[0046] The touch-sensitive displays in some embodiments of the touchscreen 112 are 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"; (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input These are described in (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 A Touch-Screen Virtual Keyboard", and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, "Multi-Functional Hand-Held Device". All of these applications are incorporated herein by reference in their entirety.

[0047] The touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user optionally touches the touchscreen 112 using any suitable object or attachment such as a stylus or finger. In some embodiments, the user interface is designed to operate primarily using finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​the finger on the touchscreen. In some embodiments, the device translates coarse finger input into a precise pointer / cursor position or command to perform an action desired by the user.

[0048] In some embodiments, in addition to the touchscreen, the device 100 optionally includes a touchpad (not shown) 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 a visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0049] Device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable or non-portable device.

[0050] The device 100 also optionally includes one or more optical sensors 164. Figure 1A shows an optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106. 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 from the environment projected through one or more lenses and converts that light into data representing an image. The optical sensor 164 works in conjunction with an imaging module 143 (also called a camera module) to optionally capture still images or video. In some embodiments, the optical sensor is located on the back of the device 100 opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for acquiring still images and / or video. In some embodiments, the optical sensor is positioned at the front of the device so that the user's image is optionally acquired for video conferencing while the user is viewing other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (for example, by rotating the lens and sensor within the device housing), so that a single optical sensor 164 can be used for both video conferencing and still image and / or video acquisition, together with the touchscreen display.

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

[0052] The device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 connected to a peripheral interface 118. Alternatively, the proximity sensor 166 is optionally connected to an input controller 160 in the I / O subsystem 106. The proximity sensor 166 optionally functions as described in U.S. Patent Applications 11 / 241,839, “Proximity Detector In Handheld Device,” 11 / 240,788, “Proximity Detector In Handheld Device,” 11 / 620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output,” 11 / 586,862, “Automated Response To And Sensing Of User Activity In Portable Devices,” and 11 / 638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are all incorporated herein by reference. In some embodiments, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is positioned near the user's ear (for example, when the user is on a phone call).

[0053] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component, and / or electromechanical devices that convert energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). The contact intensity sensor 165 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by the user of device 100. In some embodiments, at least one tactile output generator is positioned alongside or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or horizontally (e.g., forward / backward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite the touchscreen display 112 which is located on the front of device 100.

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

[0055] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications 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, and an application (or instruction set) 136. Furthermore, in some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) stores a device / global internal state 157, as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active, if there is an application currently active; a display state indicating which applications, views, or other information occupy different areas of the touchscreen display 112; a sensor state including information obtained from various sensors and input control devices 116 of the device; and position information relating to the device's location and / or orientation.

[0056] An operating system 126 (for example, an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or VxWorks) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware components and software components.

[0057] The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to connect to other devices directly or indirectly via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical to, or similar to, and / or compatible with, the 30-pin connector used on iPod (a trademark of Apple Inc.) devices.

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

[0059] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (for example, whether a user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to a software parameter (for example, the intensity thresholds can be adjusted without changing the physical hardware of device 100, rather than being determined by an activation threshold of a particular physical actuator). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to one of a range of default thresholds without changing the trackpad or touchscreen display hardware. Furthermore, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (for example, by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using a system-level click "intensity" parameter).

[0060] The contact / motion module 130 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motion, timing, and / or intensity of the detected contact). Therefore, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture involves detecting a finger down event, followed by a finger up (lift-off) event at the same position (or substantially the same position) as the finger down event (e.g., the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface involves detecting a finger down event, followed by one or more finger drag events, and then a finger up (lift-off) event.

[0061] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for modifying the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). The term “graphics” as used herein includes any object that can be displayed to the user, without limitation, including text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0062] In some embodiments, 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 an application or the like, as needed, specifying the graphics to be displayed, along with coordinate data and other graphic property data, and then generates screen image data to output to the display controller 156.

[0063] The haptic feedback module 133 includes various software components for generating commands used by a tactile output generator(s) 167, and generates tactile outputs at one or more locations on the device 100 in response to the user's interaction with the device 100.

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

[0065] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the phone 138 for location-based phone calls, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0066] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof: • Contact module 137 (sometimes called the address book or contact list), • Telephone module 138, • Video conferencing module 139, • Email client module 140, • Instant messaging (IM) module 141, • Training support module 142, • Camera module 143 for still images and / or video images, Image management module 144, • Video player module, • Music player module, • Browser module 147, Calendar module 148, A widget module 149 optionally includes one or more of the following: weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, other widgets obtained by the user, and user-created widgets 149-6. • Widget creation module 150 for creating user-created widget 149-6. • Search module 151, • A video and music player module 152 that integrates a video player module and a music player module. • Memo module 153, • Map module 154, and / or • Online video module 155.

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

[0068] Together with the touchscreen 112, display controller 156, contact / 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 (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), which includes adding names(s) to the address book, deleting names(s) from the address book, associating telephone numbers(s) to names, email addresses(s) to names, addresses(s) to names, or other information, associating images to names, categorizing and sorting names, and providing telephone numbers or email addresses to initiate and / or facilitate communication via telephone 138, video conferencing module 139, email 140, or IM 141.

[0069] The telephone module 138 works in conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to optionally input character sequences corresponding to telephone numbers, access one or more telephone numbers in the contact module 137, modify entered telephone numbers, dial individual telephone numbers, make calls, and disconnect and terminate calls at the end of a call. As previously mentioned, wireless communication may optionally use any of several communication standards, protocols, and technologies.

[0070] The video conferencing module 139 works in conjunction with the RF circuit 108, audio circuit 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 to include executable commands for starting, running, and ending video conferences between the user and one or more other participants in accordance with the user's commands.

[0071] The email client module 140, in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, includes executable commands for creating, sending, receiving, and managing emails in response to user commands. In conjunction with the image management module 144, the email client module 140 makes it extremely easy to create and send emails containing still or video images captured by the camera module 143.

[0072] The instant messaging module 141, in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, includes executable commands for inputting character sequences corresponding to instant messages, modifying previously entered characters, sending individual instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephone-based messaging (e.g., messages sent using SMS or MMS) and internet-based messaging (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0073] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 includes executable commands, which create training (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor training, select and play music for training, and display, store, and transmit training data.

[0074] The camera module 143 works in conjunction with the touchscreen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144 to include executable commands for 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.

[0075] The image management module 144 works in conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143 to include executable commands for arranging, modifying (e.g., editing), or otherwise manipulating still images and / or videos, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing them.

[0076] The browser module 147 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to include executable commands for browsing the internet according to user commands, including searching, linking, receiving, and displaying web pages or parts thereof, as well as attachments and other files linked to web pages.

[0077] The calendar module 148 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147 to include executable commands for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar entries, to-do lists, etc.) in accordance with user commands.

[0078] The widget module 149 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147 to optionally download and use mini-applications (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or mini-applications created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).

[0079] The widget creator module 150 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147 to be used by the user to optionally create widgets (for example, to turn a user-specified portion of a web page into a widget).

[0080] The search module 151 works in conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to include executable commands for searching for characters, music, sounds, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to user commands.

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

[0082] The memo module 153 works in conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to include executable commands for creating and managing memos, to-do lists, etc., according to user instructions.

[0083] The map module 154 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147 to optionally receive, display, modify, and store maps and map-related data (e.g., driving directions, data on shops and other points of interest at a specific location or nearby, and other location-based data) in accordance with user commands.

[0084] The online video module 155, in conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, includes instructions that enable the user to access, browse, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and perform other management of 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. Further descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed June 20, 2007, and U.S. Patent Application No. 11 / 968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed December 31, 2007, the entire contents of which are incorporated herein by reference.

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

[0086] In some embodiments, device 100 is a device in which the operation of a default set of functions in the device is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

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

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

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

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

[0091] The event monitor 171 receives event information from the peripheral interface 118. The event information includes information about sub-events (for example, user touch as part of a multi-touch gesture on the touch-sensitive display 112). The peripheral interface 118 transmits information received from the I / O subsystem 106, or from sensors such as the proximity sensor 166, one or more accelerometers 168, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display 112 or the touch-sensitive surface.

[0092] In some embodiments, the event monitor 171 sends requests to the peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only when there is a significant event (e.g., reception of input exceeding a predetermined noise threshold and / or exceeding a predetermined duration).

[0093] In some embodiments, the event sorting unit 170 also includes a hit view determination module 172 and / or an active event recognition determination module 173.

[0094] The hit view determination module 172 provides a software procedure for determining where in one or more views a sub-event occurred when the touch-sensitive display 112 is displaying two or more views. A view consists of control devices and other elements that the user can see on the display.

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

[0096] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views arranged in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy from which sub-events should be processed. In most situations, the hit view is the lowest-level view from which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a 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 identified as the hit view.

[0097] The active event recognition determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition determination module 173 determines that all views, including the physical location of the sub-event, are actively involved views, and therefore all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is entirely confined to an area associated with one particular view, higher-level views in the hierarchy still remain actively involved views.

[0098] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes the event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores event information retrieved by individual event receiving units 182 in an event queue.

[0099] In some embodiments, the operating system 126 includes an event sorting unit 170. Alternatively, application 136-1 includes an event sorting unit 170. In yet another embodiment, the event sorting unit 170 is a standalone module or part of another module stored in memory 102, such as a contact / motion module 130.

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

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

[0102] The event receiving unit 182 receives event information from the event sorting unit 170. The event information includes information about sub-events, such as touches or the movement of touches. 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 the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, an event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's orientation).

[0103] The event comparison unit 184 compares event information with a definition of a default event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a default sequence of default sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events within event (187) include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a displayed object. A double tap includes, for example, a first touch on the displayed object for a predetermined stage (touch start), a first lift-off for the predetermined stage (touch end), a second touch on the displayed object for the predetermined stage (touch start), and a second lift-off for the predetermined stage (touch end). In another example, the definition of event 2(187-2) is a drag on a displayed object. A drag includes, for example, a touch (or contact) on the displayed object to a predetermined stage, movement of the touch across the touch-sensitive display 112, and lift-off of the touch (end of touch). In some embodiments, the event also includes information about one or more associated event processing units 190.

[0104] In some embodiments, the event definition 187 includes event definitions for individual user interface objects. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view where three user interface objects are displayed on the touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparison unit 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 an individual event processing unit 190, the event comparison unit uses the results of the hit test to determine which event processing unit 190 should be activated. For example, the event comparison unit 184 selects the sub-event and the event processing unit associated with the object that triggers the hit test.

[0105] In some embodiments, the definition of an individual event 187 also includes a delay action that delays the transmission of event information until a determination is made as to whether the sequence of sub-events corresponds to the event type of the event recognition unit.

[0106] If an individual event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, the individual event recognition unit 180 enters an event impossible, event failed, or event terminated state, and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, those event recognition units continue to track and process the sub-events of the ongoing touch-based gesture.

[0107] In some embodiments, an individual event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate to the actively involved event recognition unit how the event distribution system should perform sub-event distribution. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how the event recognition units interact with each other, or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are distributed to various levels in the view hierarchy or program hierarchy.

[0108] In some embodiments, an individual event recognition unit 180 activates an event processing unit 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, the individual event recognition unit 180 delivers event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and delaying the sending of) sub-events to individual hit views. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with that flag captures the flag and executes a default process.

[0109] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event processing unit. Instead, the sub-event distribution command distributes event information to an event processing unit associated with a set of sub-events, or to an actively involved view. The event processing unit associated with the set of sub-events or the actively involved view receives the event information and executes a predetermined process.

[0110] In some embodiments, the data update unit 176 creates and updates data used in application 136-1. For example, the data update unit 176 updates telephone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, the object update unit 177 creates and updates objects used in application 136-1. For example, the object update unit 177 creates new user interface objects or updates the positions of user interface objects. The GUI update unit 178 updates the GUI. For example, the GUI update unit 178 prepares display information and sends it to graphics module 132 for display on touch-sensitive display.

[0111] In some embodiments, the event processing unit(s) 190 includes or has access to a data update unit 176, an object update unit 177, and a GUI update unit 178. In some embodiments, the data update unit 176, the object update unit 177, and the GUI update unit 178 are contained in a single module of an individual application 136-1 or application view 191. In other embodiments, they are contained in two or more software modules.

[0112] The foregoing description regarding the handling of user touch events on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it should be understood that not all of these begin on the touchscreen. For example, mouse movement and mouse button presses, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the events to be recognized.

[0113] Figure 2 shows a portable or non-portable multifunctional device 100 having a touchscreen 112 according to several embodiments. As described above, the multifunctional device 100 is described to have various structures (e.g., touchscreen 112, speaker 111, accelerometer 168, microphone 113, etc.). However, these structures are understood to belong to a different device at will. For example, display-related structures (e.g., display, speaker, etc.) and / or functions may at will belong to a different display device, input-related structures (e.g., touch-sensing surface, microphone, accelerometer, etc.) and / or functions may at will belong to a different input device, and the remaining structures and / or functions may at will belong to the multifunctional device 100.

[0114] The touchscreen 112 optionally displays one or more graphics within the user interface (UI) 200. In this embodiment, and in other embodiments described below, the user can select one or more of the graphics by performing a gesture on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics occurs when the user interrupts contact with that one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not constitute selection of that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture, which involves sweeping over an application icon, does not arbitrarily select the corresponding application.

[0115] Device 100 also optionally includes one or more physical buttons, such as a "Home" or menu button 204. As previously mentioned, the menu button 204 is optionally used to direct the user to any application 136 in a set of applications that can be optionally run on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on the touchscreen 112.

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

[0117] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments. Device 300 does not necessarily have to include a display and a touch-sensitive surface as described above; rather, in some embodiments, it optionally communicates with a display and a touch-sensitive surface on another device. In addition, device 300 does not have to be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia playback device (e.g., a television or set-top box), a navigation device, an educational device (e.g., a children's learning toy), a game system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 optionally include circuitry (sometimes referred to as a chipset) for interconnecting and controlling communication between system components. Device 300 includes an input / output (I / O) interface 330 including a display 340, the display 340 is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (similar to the tactile output generator 167 described above with reference to Figure 1A) for generating tactile output on Device 300, and a sensor 359 (e.g., an optical sensor, an accelerometer, a proximity sensor, a touch sensor, and / or a contact intensity sensor similar to the contact intensity sensor 165 described above with reference to Figure 1A). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices.Memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, that are stored in the memory 102 of the portable or non-portable multifunction device 100 (Figure 1A). Furthermore, memory 370 may store additional programs, modules, and data structures that are not present in the memory 102 of the portable or non-portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a document creation module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while memory 102 of the portable or non-portable multifunction device 100 (Figure 1A) does not optionally store these modules.

[0118] Each of the elements of Figure 3 identified above is optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to an instruction set that performs the function described above. The modules or programs (i.e., instruction sets) identified above do not need to be implemented as separate software programs, procedures, or modules; therefore, various subsets of those modules can optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0119] Next, we optionally turn our attention to an embodiment of a user interface implemented in, for example, a portable multi-functional device 100.

[0120] Figure 4A shows an exemplary user interface of an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. • Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular and Wi-Fi signals 402, ·Time 404, • Bluetooth® indicator 405, • Battery status indicator 406, • Tray 408 containing icons for frequently used applications, such as the following: - An icon 416 for a telephone module 138 labeled "Telephone" optionally includes an indicator 414 for the number of missed calls or voicemail messages. - An optional icon 418 labeled "Mail" for the email client module 140, which includes an indicator 410 of the number of unread emails. • Icon 420 for browser module 147, labeled "Browser", and • Icon 422 for the video and music player module 152, also known as the iPod (a registered trademark of Apple Inc.) module 152, labeled "iPod", and • Icons for other applications, such as those listed below. • Icon 424 for IM module 141, labeled "Message" • Icon 426 for calendar module 148, labeled "Calendar" • Icon 428 for image management module 144, labeled "Photo" • Icon 430 for camera module 143, labeled "Camera" • Icon 432 for online video module 155, labeled "online video". • Icon 434 for stock price widget 149-2, labeled "Stock Price". • Icon 436 for map module 154, labeled "Map" • Icon 438 for weather widget 149-1, labeled "Weather" • Icon 440 for alarm clock widget 149-4, labeled "Clock" • Icon 442 for training support module 142, labeled "Training Support" • Icon 444 for memo module 153, labeled "Memo", and • An icon 446 labeled "Settings" for a settings application or module, providing access to the settings of device 100 and its various applications 136.

[0121] Please note that the icon labels shown in Figure 4A are for illustrative purposes only. For example, the icon 422 for the video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label for an individual application icon includes the name of the application to which that individual application icon corresponds. In some embodiments, the label for a particular application icon is different from the name of the application to which that particular application icon corresponds.

[0122] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3) separate from the display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of contact on the touch-sensitive surface 451, and / or one or more tactile output generators 357 for generating tactile output to the user of device 300.

[0123] Some of the following embodiments will be described with reference to input on a touchscreen display 112 (when the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface separate from the display, as shown in Figure 4B. In some embodiments, the touch-sensing surface (e.g., 451 in Figure 4B) has a primary axis (e.g., 452 in Figure 4B) corresponding to a primary axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with the touch-sensing surface 451 (e.g., 460 and 462 in Figure 4B) at locations corresponding to each location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). In this way, user input (e.g., touches 460 and 462, and their movement) detected by the device on a touch-sensitive surface (e.g., 451 in Figure 4B) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B) when the touch-sensitive surface is separate from the display. It should be understood that a similar method may be optionally used for other user interfaces described herein.

[0124] In addition, while the following examples are given primarily with reference to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of the 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 touch), followed by a mouse click with cursor movement along the swipe path (e.g., instead of touch movement). As another example, a tap gesture may optionally be replaced by a mouse click (e.g., instead of touch detection and subsequent cessation of touch detection) while the cursor is located over the tap gesture location. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0125] Furthermore, while the following examples primarily refer to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, 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 touch), followed by a mouse click with cursor movement along the swipe path (e.g., instead of touch movement). As another example, a tap gesture may optionally be replaced by a mouse click (e.g., instead of detecting touch and then ceasing touch detection) while the cursor is positioned over the tap gesture location. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice may optionally be used simultaneously, or a mouse and finger touch may optionally be used simultaneously.

[0126] As used herein, the term “focus selector” refers to an input element that indicates the current part of the user interface that the user is interacting with. In some implementations, including a cursor or other location marker, the cursor acts as a “focus selector” when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., the touchpad 355 in Figure 3, or the touch-sensitive surface 451 in Figure 4B) and the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), and the particular user interface element is adjusted according to the detected input. In some implementations, including a touchscreen display (e.g., the touch-sensitive display system 112 in Figure 1A) that enables direct interaction with user interface elements on the touchscreen display, the contact detected on the touchscreen acts as a “focus selector” so that when input (e.g., a press input) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (for example, by moving focus from one button to another using the tab key or arrow keys). In these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, it is generally a user interface element (or touch on the touchscreen display) controlled by the user to communicate about the user's intended interaction with the user interface (for example, by pointing to the device the user interface element through which the user intends to interact).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., cursor, touch, or selection box) above the corresponding button indicates that the user is attempting to activate the corresponding button (rather than other user interface elements displayed on the device's display).

[0127] As used herein and in the claims, the term “characteristic intensity” of a contact refers to the characteristics of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a set of intensity samples collected over a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the top 10 percentile value of the contact intensity, the maximum half value of the contact intensity, the maximum 90 percent value of the contact intensity, and so on. In some embodiments, the duration of contact is used when determining characteristic intensity (for example, when characteristic intensity is the average intensity of contact over time). In some embodiments, characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action has been performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this embodiment, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity above the second threshold results in a third action. In some embodiments, the comparison between characteristic intensity and one or more thresholds is not used to determine whether a first action should be performed or a second action should be performed, but rather to determine whether one or more actions should be performed at all (for example, whether individual actions should be performed or whether individual actions should be withheld).

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

[0129] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, which may be referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship with a press input intensity threshold (for example, the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of an individual contact above the press input intensity threshold, followed by a decrease in the intensity of a contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and the individual action is performed in response to the detection of a subsequent decrease in the intensity of an individual contact below the hysteresis intensity threshold (for example, an “upstroke” of the individual press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a press input intensity threshold, and optionally a decrease in contact intensity to an intensity below the hysteresis intensity thereafter, and individual actions are performed in response to the detection of a press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the situation).

[0130] For the sake of clarity, the description of an action performed in response to a press input associated with a press input intensity threshold, or in response to a gesture containing that press input, is optionally triggered in response to the detection of any of the following: an increase in contact intensity above the press input intensity threshold, an increase in contact intensity from below the hysteresis intensity threshold to above the press input intensity threshold, a decrease in contact intensity below the press input intensity threshold, and / or a decrease in contact intensity below the hysteresis intensity threshold corresponding to the press input intensity threshold. Furthermore, in an example where an action is described to be performed in response to the detection of a decrease in contact intensity below the press input intensity threshold, the action may optionally be performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold and lower than that threshold.

[0131] Figure 5A shows a block diagram of an exemplary architecture of device 500 according to some embodiments of the present disclosure. In the embodiment of Figure 5A, media or other content is optionally received by device 500 via a network interface 502, which is optionally wireless or wired. One or more processors 504 optionally execute any number of programs stored in memory 506 or storage. Memory 506 or storage optionally includes instructions that execute one or more of the methods and / or processes described herein (e.g., methods 700 and / or 900). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a temporary computer-readable storage medium. In some examples, the storage medium is a non-temporary computer-readable storage medium. Non-temporary computer-readable storage media may 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, CDs, DVDs, or optical disks based on Blu-ray technology, as well as persistent solid-state memory such as flash and solid-state drives. The personal electronic device 500 is not limited to the components and configurations shown in Figure 5, and may include other or additional components in multiple configurations.

[0132] Furthermore, in any method described herein that is conditional on one or more conditions being met in one or more steps, it should be understood that the method described can be repeated in multiple iterations such that all the conditions that the steps of the method are conditional on are met in different iterations of the method. For example, if a method requires that a first step be performed if a condition is met, and a second step be performed if the condition is not met, a person skilled in the art will understand that the steps described in the claim are repeated in an unspecified order until the conditions are met and then not met. Thus, a method described in one or more steps that depends on one or more conditions being met can be rewritten as a method that is repeated until each of the conditions described in the method is met. However, this is not required for a claim of a system or computer-readable medium that includes instructions that perform a conditional action based on the satisfaction of the corresponding one or more conditions, and thus can determine whether a contingency has been met without explicitly repeating the steps of the method until all the conditions that the steps of the method are conditional on are met. Those skilled in the art will also understand that, as with a method having conditional steps, a system or computer-readable storage medium may repeat the steps of the method as many times as necessary to ensure that all of the conditional steps have been performed.

[0133] As used herein, the term “affordance” refers to user interaction graphic user interface objects that are optionally displayed on the display screens of devices 100, 300, and / or 500 (Figures 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0134] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations, including a cursor or other location marker, the cursor acts as a “focus selector” when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., the touchpad 355 in Figure 3, or the touch-sensitive surface 451 in Figure 4B) and the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), and the particular user interface element is adjusted according to the detected input. In some implementations, including a touchscreen display that allows direct interaction with user interface elements on the touchscreen display (e.g., the touch-sensitive display system 112 in Figure 1A, or the touchscreen 112 in Figure 4A), detected contact on the touchscreen acts as a “focus selector,” and therefore, when input (e.g., a press input by 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 display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (for example, by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or touch on the touchscreen display) controlled by the user to communicate the user's intended interaction with the user interface (for example, by pointing to the device an element of the user interface through which the user intends to interact).For example, the location of a focus selector (e.g., cursor, touch, or selection box) over an individual button while pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (rather than other user interface elements displayed on the device's display).

[0135] As used herein and in the claims, the term “characteristic intensity” of a contact refers to the characteristics of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a set of intensity samples collected over a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the top 10 percentile value of the contact intensity, the maximum half value of the contact intensity, the maximum 90 percent value of the contact intensity, and so on. In some embodiments, the duration of contact is used when determining characteristic intensity (for example, when characteristic intensity is the average intensity of contact over time). In some embodiments, characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action has been performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this embodiment, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity above the second threshold results in a third action. In some embodiments, the comparison between characteristic intensity and one or more thresholds is not used to determine whether a first action should be performed or a second action should be performed, but rather to determine whether one or more actions should be performed at all (for example, whether individual actions should be performed or whether individual actions should be withheld).

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

[0137] In some embodiments, a portion of the gesture is identified for the purpose of determining characteristic intensity. For example, the touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting location to an ending location, where the intensity of contact increases. In this example, the characteristic intensity of the contact at the ending location is optionally based only on a portion of the series of swipe contacts (e.g., only the portion of the swipe contact that reaches the ending location), rather than the entire swipe contact. In some embodiments, optionally, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or drops in the swipe contact intensity for the purpose of determining characteristic intensity.

[0138] The intensity of contact on the touch-sensitive surface is optionally characterized to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to the intensity at which the device performs an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to the intensity at which the device performs an action different from the action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact with a characteristic intensity below the light press intensity threshold (for example, above a nominal contact detection intensity threshold below which contact is no longer detected) is detected, the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface values.

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

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

[0141] Figures 5E to 5H show the light pressure intensity threshold in Figure 5E (for example, "IT L From an intensity below ) to the deep pressing intensity threshold in Figure 5H (for example, "IT DThe device indicates the detection of a gesture including a pressing input corresponding to an increase in the intensity of contact 562 to an intensity exceeding a deep pressing intensity threshold (e.g., "IT"). The gesture performed by contact 562 is detected on the touch-sensitive surface 560, and on the display user interface 570, which includes application icons 572A-572D displayed within a predetermined area 574, a cursor 576 is displayed over the application icon 572B corresponding to app 2. In some embodiments, the gesture is detected on the touch-sensitive display 504. An intensity sensor detects the intensity of contact on the touch-sensitive surface 560. The device indicates that the intensity of contact 562 exceeds a deep pressing intensity threshold (e.g., "IT"). D It is determined that the pressure has reached its peak by exceeding the threshold (e.g., "IT"). Contact 562 is maintained on the touch sensing surface 560. Depending on the detection of the gesture, a deeper pressure intensity threshold (e.g., "IT") is set during the gesture. D According to a contact 562 having an intensity exceeding '', a scaled representation 578A-578C (e.g., thumbnail) of the recently opened document is displayed for app 2, as shown in Figures 5F-5H. In some embodiments, this intensity, compared to one or more intensity thresholds, is the characteristic intensity of the contact. Note that the intensity diagram for contact 562 is not part of the display user interface but is included in Figures 5E-5H to assist the reader.

[0142] In some embodiments, the display of representations 578A to 578C includes animation. For example, as shown in Figure 5F, representation 578A is initially displayed close to the application icon 572B. As the animation progresses, as shown in Figure 5G, representation 578A moves upward and representation 578B is displayed close to the application icon 572B. Then, as shown in Figure 5H, representation 578A moves upward and representation 578B moves upward toward representation 578A and representation 578C is displayed close to the application icon 572B. Representations 578A to 578C form an array above the icon 572B. In some embodiments, as shown in Figures 5F to 5G, the animation progresses according to the intensity of contact 562, where the intensity of contact 562 reaches a deep pressing intensity threshold (e.g., "IT").D As it increases toward (), expressions 578A-578C appear and move upward. In some embodiments, the intensity on which the animation progresses is based is the characteristic intensity of the contact. The operations described with reference to Figures 5E-5H can be performed using electronic devices similar to or identical to devices 100, 300, or 500.

[0143] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, which may be referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship with a press input intensity threshold (for example, the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of an individual contact above the press input intensity threshold, followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and the individual action is performed in response to the detection of a subsequent decrease in the intensity of an individual contact below the hysteresis intensity threshold (for example, an “upstroke” of the individual press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a press input intensity threshold, and optionally a decrease in contact intensity to an intensity below the hysteresis intensity thereafter, and individual actions are performed in response to the detection of a press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the situation).

[0144] For the sake of clarity, the description of an action performed in response to a press input associated with a press input intensity threshold, or a gesture involving a press input, is optionally triggered in response to the detection of any of the following: an increase in contact intensity above the press input intensity threshold, an increase in contact intensity from below the hysteresis intensity threshold to above the press input intensity threshold, a decrease in contact intensity below the press input intensity threshold, and / or a decrease in contact intensity below the hysteresis intensity threshold corresponding to the press input intensity threshold. Furthermore, in examples where an action is described to be performed in response to the detection of a decrease in contact intensity below the press input intensity threshold, the action is optionally performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0145] In this specification, “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., opened). In some embodiments, a downloaded application becomes an installed application by an installation program that extracts the program portion from the downloaded package and integrates the extracted portion with the operating system of the computer system.

[0146] In this specification, the terms “open application” or “running application” refer to a software application that has retained state information (e.g., as part of the device / global internal state 157 and / or application internal state 192). An open or running application is optionally one of the following types of applications: • The active application currently displayed on the display screen of the device on which the application is being used. • Background applications (or background processes) that are not currently displayed but whose one or more operations are being handled by one or more processors, and • A suspended or hibernating application that is not running but has state information stored in memory (volatile and non-volatile, respectively) that can be used to resume the execution of the application.

[0147] In this specification, the term “closed application” refers to a software application that does not retain state information (for example, state information for a closed application is not stored in the device’s memory). Therefore, closing an application involves stopping and / or removing the application process for the application and removing the state information for the application from the device’s memory. Generally, opening a second application while a first application is running does not close the first application. When the second application is displayed and the first application is stopped from being displayed, the first application becomes a background application.

[0148] Next, we will focus on embodiments of user interfaces ("UI") and related processes implemented on electronic devices such as device 100, device 300, or device 500. User interface and related processes User interface for sending and receiving messages

[0149] Users interact with electronic devices in many different ways, including interacting with messaging applications for sending and receiving electronic messages to and from other people or groups of people. In some embodiments, the electronic device displays messaging conversations within the messaging application, and these conversations include messages sent by the user of the electronic device, as well as messages sent by other people to the user of the device. In some situations, messages sent from and received by the messaging application include text messages, images, web links, and other data. The messaging application facilitates the exchange of messages between the user of the electronic device and other external users. In some situations, the messaging application facilitates group messaging conversations. Group messaging conversations allow multiple users belonging to the group messaging conversation to share messages with each other, and as a result, messaging activity occurring on the group messaging conversation becomes visible to other users or all users of the multiple users who are members / users of the group messaging conversation. In some situations, all users who are part of a group messaging conversation use the same messaging service, and therefore it is possible to adjust the membership of the group messaging conversation (e.g., the users who are part of the group messaging conversation) by adding and removing users from the group messaging conversation. However, in some situations, the members of a group messaging conversation may not use the same messaging service, which makes it more difficult to add or remove users from the group messaging conversation. In some situations, where the group messaging conversation is a "hybrid" group messaging conversation (e.g., not all users of the group messaging service use the same messaging service), it is impossible to add users to the group messaging conversation without creating an entirely new group messaging conversation from scratch that includes the users to be added.In some situations, whenever a user wants to add another user to a hybrid group messaging conversation, the user must repeat the process of creating a new group messaging conversation from scratch in order to add the additional user. Requiring the user to engage in the process of creating a new group messaging conversation from scratch every time they wish to add or remove a user from a group messaging conversation can lead to input errors on the device and consume computing resources on the device. The embodiments described below provide a way for an electronic device to provide an efficient user interface for adding and removing users from a hybrid group messaging conversation, and thus enhance the user's interaction with the device. By enhancing the interaction with the device, the amount of time the user needs to perform an action is reduced, and therefore the power consumption of the device is reduced, increasing battery life for battery-powered devices. It is understood that people use a device. When a person uses a device, that person is optionally called a user of that device.

[0150] Figures 6A–6K illustrate exemplary ways in which an electronic device displays a user interface for adding a user to a hybrid group messaging conversation. Embodiments in these figures are used to illustrate the processes described below, including the process described with reference to Figure 7. While Figures 6A–6K show various examples of how an electronic device may perform the processes described below with reference to Figure 7, these examples are not intended to be limiting, and it should be understood that an electronic device may perform one or more of the processes described below with reference to Figure 7 in ways not explicitly described with reference to Figures 6A–6K.

[0151] Figure 6A shows an exemplary device 500 that displays the user interface 612. In some embodiments, the user interface 612 is displayed via a display generating component. In some embodiments, the display generating component is a hardware component (including, for example, an electrical component) that can receive display data and display the user interface. In some embodiments, examples of the display generating component include a touchscreen display, a monitor, a television, a projector, an integrated, separate, or external display device, or any other suitable display device.

[0152] In some embodiments, an electronic device (e.g., device 500) includes a messaging application. The messaging application can represent messaging activity sent from other electronic devices (by the users of each of those devices) and messaging activity originated on the electronic device (sent by the users of the electronic device). In some embodiments, messaging activity sent and received by the messaging application includes, but is not limited to, text messages, images, photographs, web-based links, and other media. In some embodiments, the messaging application facilitates group messaging conversations. A group messaging conversation can refer to a conversation (e.g., multiple messaging activities) shared among multiple users (including users of the electronic device) such that messaging activity sent to the group messaging conversation by any of the multiple users in the group messaging conversation is displayed by the electronic device on the user interface of the messaging application used to conduct the group messaging conversation. In some embodiments, the group messaging conversation is conducted as a “non-hybrid” group messaging conversation. A “non-hybrid” group messaging conversation conducted on a messaging application can refer to a group messaging conversation in which all users of the multiple users that are part of the group messaging use the same messaging service to conduct the group messaging conversation. For example, a group messaging conversation in which all users utilize the IMESSAGE messaging service is considered a non-hybrid group messaging conversation.In some embodiments, a “hybrid” group messaging application on a messaging application can refer to a group messaging conversation in which one or more users use a first messaging service (such as IMESSAGE), while one or more users of the group messaging conversation use a second messaging service different from the first messaging service. For example, one or more users of the group messaging service use the IMESSAGE messaging service, and one or more users of the group messaging service use the Short Message Service ("SMS") messaging service. In some embodiments, the messaging application can display both hybrid and non-hybrid group messaging conversations. In some embodiments (and as will be described in more detail below), the messaging application performs certain actions associated with a group messaging conversation based on whether the group messaging conversation is a hybrid or non-hybrid group messaging conversation.

[0153] As shown in Figure 6A, the electronic device 500 displays a messaging user interface 612 (for example, a messaging application installed on the device 500) on the touchscreen 504. In some embodiments, the user interface 612 is an arbitrary user interface that displays information about one or more messaging conversations, including one or more group messaging conversations. In Figure 6A, the messaging user interface 612 includes messaging activity related to a group messaging conversation labeled "Roomies". The user interface 612 includes a group messaging conversation information section 602 that displays the name of the group (e.g., Roomies). Optionally, the conversation information section 602 of the user interface 612 also includes a photograph associated with the group messaging conversation, in addition to the name of the group messaging conversation.

[0154] In some embodiments, the user interface 612 of the messaging application shown in Figure 6A includes messaging activities associated with a group messaging conversation. For example, as shown in Figure 6A, the user interface 612 includes messaging activities 604A-B from a first user of the group messaging and messaging activities 606A-B from a user of the electronic device on which the messaging application is running. Figure 6A shows a non-hybrid group messaging conversation, where all users who are part of the group messaging conversation interact with the group messaging conversation using the same messaging service. Optionally, the user interface 612 includes one or more visual indicators to identify a group messaging conversation as a non-hybrid group messaging conversation. For example, messaging activities 606A-B on the user interface 612 are colored / highlighted to indicate that the Roomies group messaging conversation is a non-hybrid group messaging conversation. In some embodiments, messaging activities 604A-B include the same color / highlighting to indicate that the Roomies group messaging conversation is a non-hybrid group messaging conversation. In some embodiments, the user interface 612 includes a messaging activity entry section 608 (e.g., a text or content entry field) that is selectable by the user of the electronic device and receives input of messaging activities (such as text) that are displayed on the user interface 612 as part of a group messaging conversation.

[0155] In some embodiments, the group conversation information section 602 is selectable. In Figure 6A, the device 500 detects the selection of section 602 (e.g., via a tap on contact 603 on section 602). In response to detecting the selection of section 602, the device 500 displays the group messaging conversation information user interface 614 of the messaging application, as shown in Figure 6B. The group messaging conversation information user interface 614 includes a variety of selectable options 616A-D for performing various actions associated with the group messaging conversation. For example, the user interface 614 optionally includes selectable options 616A-C, which, when selected, cause the device to display information about the user associated with the selectable option. For example, when the device 500 receives an indication that a user has selected one of the options 616A-C (e.g., via a tap on a touchscreen), the device may display a user interface containing contact information associated with the selectable option.

[0156] In some embodiments, the user interface 614 includes a selectable option 616D for adding an additional user to a group messaging conversation. In Figure 6B, the device 500 detects the selection of the selectable option 616D (for example, via a tap on the contact 603 of option 616D). In response to detecting the selection of option 616D for adding an additional user to a group messaging conversation, the device 500 displays a group messaging conversation user addition user interface 618, as shown in Figure 6C. The user interface 618 includes a selectable username portion 620, which optionally allows the user of the electronic device to type the name or other identifier of the user to be added to the group messaging conversation (for example, using the touchscreen keyboard 622). In some embodiments, when the device detects that the user has typed the user's full or partial name in the username portion 620, the device searches for a matching entry in the contact list stored in the electronic device. In some embodiments, when the device finds a matching entry, the user interface 618 includes a matching entry section 624 that displays details associated with the matching entry, including the name associated with the matching entry and the electronic messaging identifier (such as a phone number or email address) associated with the matching entry. The matching entry section 624 is selectable. In Figure 6C, the device 500 detects the selection of section 624 (for example, via a tap of contact 603 on section 624).

[0157] In some embodiments, upon detecting the selection of portion 624, the device 500 determines whether the user being added uses the same messaging service as multiple users who are part of the group messaging conversation, and therefore maintains the group messaging conversation as a non-hybrid group messaging conversation. In some embodiments, if the device determines via the messaging application that adding a user would maintain the group messaging conversation as a non-hybrid group messaging conversation, the selection of portion 624 causes the device to display a user interface 612 (described above with respect to Figure 6A), as shown in Figure 6D. Optionally, upon adding a user, the user interface 612 includes an indication portion 626, which includes a message to the device user indicating that the added user has been successfully added to the group messaging conversation.

[0158] In some embodiments, if the device determines via the messaging application that adding a user will cause the group messaging conversation to become a hybrid group messaging conversation (for example, the added user uses a different messaging service than the other users in the group messaging conversation), or if the group messaging conversation was already a hybrid group messaging conversation, the selection of portion 624 on the user interface 618 in Figure 6C causes the device to display a new group messaging generation user interface 628, as shown in Figure 6E. In some embodiments, the user interface 628 includes an information portion 630 containing a message to the user indicating that by adding a user, the group messaging conversation transitions from a non-hybrid group messaging conversation to a hybrid group messaging conversation. In some embodiments, the user interface 628 includes a variety of selectable options, including a selectable option 632 that, when selected by the user, initiates the process of creating a new hybrid group messaging conversation that includes multiple users from the current group messaging conversation, as well as the user to be added. In Figure 6E, the device 500 detects the selection of the selectable option 632 (for example, via a tap of contact 603 on option 632). Upon detecting the selection of option 632, device 500 displays a group messaging conversation creation user interface 634 as shown in Figure 6F.

[0159] In some embodiments, the group messaging conversation creation user interface 634 includes a variety of selectable options that allow the user to select identification information to associate with a new group messaging conversation. Optionally, the selectable options include, when selected by the user, option 636, which transfers identification information (e.g., name and picture) associated with a previous group messaging conversation (e.g., a group messaging conversation associated with multiple members before a new member is added) to the newly created group messaging conversation. Optionally, the selectable options include, when selected by the user, option 638, which causes the device to associate new identification information (e.g., new name and picture) with the new group messaging conversation. In some embodiments, when the device detects that option 638 has been selected by the user, the device may prompt the user to provide identification information for the new group messaging conversation. In some embodiments, the user interface 634 includes a cancel option that allows the user to terminate the process of generating a new group messaging conversation. In Figure 6F, device 500 detects the selection of selectable option 636 (e.g., via a tap on contact 603 on option 636). Upon detecting the selection of option 636, device 500 displays the user interface 612 (mentioned above with respect to Figure 6A) for the newly created group messaging conversation, as shown in Figure 6G.

[0160] In some embodiments, the user interface 612 in Figure 6G includes a group messaging conversation information section 602 containing identification information associated with the new group messaging conversation. In Figure 6G, since the user chose to retain the same identification information for a previous group messaging conversation in the user interface 634 in Figure 6F, the conversation information section 602 includes the same name as the previous group messaging conversation (e.g., "Roomies"). In some embodiments (and as will be described in more detail below), depending on the user's choice to retain the same identification information for the new group messaging conversation, the device disassociates the identification information currently used for the new group messaging conversation from the previous group messaging conversation.

[0161] In some embodiments, the user interface 612 in Figure 6G includes a “Destination” field 640. Optionally, the Destination field 640 includes a list of users who are part of a new group messaging conversation. For example, as shown in Figure 6G, the Destination field 640 includes “Camille,” who has been newly added to the group messaging conversation by a user. In some embodiments, the Destination field 640 may include one or more selectable names 642. A selectable name 642 indicates a user who is part of a group messaging conversation, and that user’s electronic messaging identifier must be selected by the user to allow that user to be part of the newly created group messaging conversation. For example, as shown in Figure 6G, the entry in the Destination field 640 related to “Maddy” is selectable and therefore indicates that Maddy requires selection of an electronic messaging identifier to be included as part of the group messaging conversation. Optionally, a selectable name 642 is indicated by the user interface 612 as selectable using one or more visual indicators. For example, in Figure 6G, selectable name 642 associated with Maddy is highlighted, thereby providing the user with a visual indication that Maddy's electronic messaging identifier requires selection and / or action to include Maddy in a group messaging conversation. In Figure 6G, device 500 detects the selection of selectable name 642 (for example, via a tap on contact 603 on name 642). In response to detecting the selection of name 642, device 500 displays a user electronic messaging identifier interface 644 as shown in Figure 6H.

[0162] In some embodiments, the electronic messaging identifier interface 644 includes an electronic identifier list section 646 containing a list of electronic identifiers associated with Maddy, based on contact information associated with Maddy stored on the electronic device. In some embodiments, the electronic identifier list section 646 includes one or more selectable options 648A-C, which allow the user to select which of the electronic identifiers associated with Maddy to use for group messaging conversations. Optionally, one or more selectable options 648A-C include a visual indicator to show that the option determined by the device is the best option to use as an electronic messaging identifier for the user. In some embodiments, the device may determine the best option to use based on the type of electronic messaging identifier associated with the option, as well as the previous history of the device's interaction with the user. As an example, the device may select the user's phone number based on the user's most frequently contacted phone number. Additionally or alternatively, the device may select a phone number based on the last phone number used by the user of the electronic device to contact user 4. As shown in Figure 6H, selectable option 648A is highlighted to indicate that the device has determined that this option is the best option to select for Maddy.

[0163] In some embodiments, in Figure 6G, when the device determines that a selectable option 642 has been selected by the user, and the device determines that the user (e.g., Maddy) does not have an electronic messaging identifier compatible with the messaging service used by the newly created group messaging conversation (e.g., Maddy's contact information does not include a phone number), the device displays a user interface 644 as shown in Figure 6I. Optionally, the user interface 644 includes the same features as described above with respect to Figure 6H, but also includes a selectable option 650 that allows the user to manually enter an electronic messaging identifier for the user that is compatible with the messaging service employed by the group messaging conversation, as shown in Figure 6I. Optionally, the user interface includes a selectable option 652 that causes the device to remove the user (e.g., Maddy) rather than manually adding the user's electronic messaging identifier.

[0164] In Figure 6H, device 500 detects the selection of the selectable option 648A (for example, via a tap on contact 603 of option 648A). In response to detecting the selection of option 648A, device 500 displays user interface 612 as shown in Figure 6J. User interface 612 is substantially the same as user interface 612 in Figure 6A and includes a list of all messaging activities taking place on the newly created group messaging conversation (in this case, no messaging activities are listed as the group messaging conversation has just been created). As shown in Figure 6J, identification information associated with the previous group messaging conversation (e.g., "Roomies" and a photo) is associated with the new group messaging conversation due to the user's previous input to retain the identification information. User interface 612 in Figure 6J includes a selectable option 654 that, when selected by the user, causes the device to display a list of all active conversations maintained by the messaging application. In Figure 6J, device 500 detects the selection of the selectable option 654 (for example, via a tap on contact 603 of option 654). Upon detecting the selection of option 654, device 500 displays the active message list user interface 656, as shown in Figure 6K.

[0165] In some embodiments, the active messaging list user interface 656 includes a list of all or some of the active conversations maintained by the messaging application. For example, the user interface 656 includes entries 658 and 660. Entry 658 lists newly created group messaging conversations and includes the name and photo (e.g., identification information) previously selected by the user as described above. Entry 660 lists previous group messaging conversations, but does not include the identification name or photo of the conversation, because the device has previously unassociated the identification information used for the previous group messaging conversation (due to the user choosing to use the same identification information for the newly created group messaging conversation at contact 603 in Figure 6F). Instead, it lists the users associated with the previous group messaging conversation (not including new users, as new users have never been added to the previous group conversation and have only been added to the newly created group messaging conversation), as well as the most recent messaging activity associated with the previous group messaging conversation. The group messaging conversation associated with entry 660 (e.g., previous group messaging conversation) will only include messaging activity that existed before the user created the new group messaging conversation.

[0166] Figures 7A–7E are flowcharts illustrating how an electronic device adds one or more users to a hybrid group messaging conversation, according to some embodiments of the present disclosure. Method 700 is optionally performed on a first device and / or an electronic device such as device 100, device 300, or device 500 as described above with reference to Figures 1A–1B, 2–3, 4A–4B, and 5A–5C. Some operations in Method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0167] As described below, Method 700 provides a method for an electronic device to facilitate the addition and removal of users from a group messaging conversation when the group messaging conversation includes members using different messaging services (e.g., a hybrid group messaging conversation). Such a technique enables a user to modify the membership of a hybrid group messaging conversation without requiring manual user input to create such a group messaging conversation.

[0168] In some embodiments, Method 700 is performed in an electronic device that communicates with a display generating component and one or more input devices. For example, the electronic device is a mobile device (e.g., a tablet, smartphone, media player, or wearable device) and optionally includes a wireless communication circuit that communicates with one or more of the following: a mouse (e.g., external), a trackpad (optionally integrated or external), a touchpad (optionally integrated or external), a remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and / or a controller (e.g., external). In some embodiments, the display generating component is an integrated display with the electronic device (optionally a touchscreen display), an external display such as a monitor, projector, television, or hardware component (optionally integrated or external) for projecting a user interface or making the user interface visible to one or more users.

[0169] In some embodiments, while a first user of an electronic device is part of a first group messaging conversation involving multiple users, such as in Figure 6A (for example, the first group messaging conversation takes place via a messaging application on the electronic device, and the user of the electronic device uses the messaging application to receive and / or send messaging activity to the first group messaging conversation; in some embodiments, one or more or all of the multiple users receive messaging activity sent to the first group messaging conversation), the electronic device displays a user interface associated with the messaging application in which the first group messaging conversation takes place via a display generation component (for example, while displaying a user interface that includes a representation of messaging activity sent and / or received in the first group messaging conversation), the electronic device receives an indication to add a second user to the first group messaging conversation via one or more input devices, such as an input from contact 603 in Figure 6B (702a). In some embodiments, the indication for adding a second user includes detecting a selection of a conversation management option displayed on a user interface, thereby causing the electronic device to display one or more selectable options for adding one or more users to a first group messaging conversation. In some embodiments, while displaying a management user interface containing one or more selectable options, the electronic device detects a selection of one of the options corresponding to adding a second user to the first group messaging conversation. In some embodiments, this indication is a touch input on a touch-sensitive surface, a voice input, or a mouse input.

[0170] In some embodiments, upon receiving an indication to add a second user to a first group messaging conversation (702b), and in accordance with the determination that the multiple users to be added to the first group messaging conversation and the second user are not part of the same messaging service (e.g., a service, server, or network on which one or more users can send and / or receive messaging activity from one another), the electronic device initiates a process to generate a second group messaging conversation different from the first group messaging conversation, which is conducted via a messaging application without adding the second user to the first group messaging conversation, such as in Figure 6E (702c), and the second group messaging conversation includes the multiple users of the first group messaging conversation and the second user. In some embodiments, determining that the multiple users to be added to the first group messaging conversation and the second user are not part of the same messaging service includes determining that the second user uses a different messaging service than the messaging service used by the multiple users. Determining that multiple users added to a first group messaging conversation and a second user are not part of the same messaging service optionally includes determining that the second user does not use the messaging service used by the multiple users in the first group messaging conversation. Determining that multiple users added to a first group messaging conversation and a second user are not part of the same messaging service optionally includes determining that one or more of the multiple users in the first group messaging conversation do not use the messaging service used by the other users. If a group messaging conversation includes users using different messaging services, the group membership cannot optionally be modified after the group messaging conversation is created.Therefore, when a “mixed” messaging group requires a modification to its group membership (e.g., adding an additional user to the group), a new group messaging conversation is created that includes members from the original group messaging conversation as well as the added members. In some embodiments, if it is determined that a second user and several users from the first group messaging conversation are not part of the same messaging service, a process for generating a second group messaging conversation is initiated. In some embodiments, initiating a process for generating a second group messaging conversation includes generating the second group messaging conversation in the messaging application and adding several users from the first group messaging conversation and the second user to the second group messaging conversation. The second group conversation may optionally differ from the first group conversation in that it is not generated by adding the second user to the first group messaging conversation. Instead, a new group messaging conversation is optionally created that includes both several users from the first group messaging service and the second user. The second group messaging conversation is optionally configured to allow multiple users and the second user to send and / or receive messaging activity that is viewed by multiple members of the first and the second members. In some embodiments, initiating the process of generating the second group messaging conversation includes providing the user with one or more user interfaces configured to confirm that the user wants to create a new group messaging conversation. If the device detects that the user has confirmed that the user wants to create a new group messaging conversation, the device creates the second group messaging conversation. In some embodiments, initiating the process of generating the second group messaging conversation includes providing the first user with one or more user interfaces configured to collect the first user's preferences regarding the second group messaging conversation.In some embodiments, a second group messaging conversation is automatically created using the preferences of a first user, and multiple members and the second user are added to the second group messaging conversation. In some embodiments, after the second group messaging conversation is created, both the first and second group messaging conversations are accessible from 1) the first user's messaging application and / or 2) the messaging applications of users in the first and / or second group messaging conversations for sending and / or receiving messaging activities (for example, a user can still send / receive messages in the first group messaging conversation). By automatically creating new messaging conversations when mixed-service group conversations are involved, users using different messaging services can participate in group messaging activities, including the ability to modify membership in such group messaging activities, without requiring manual user input to create such group messaging conversations.

[0171] In some embodiments, upon receiving an indication to add a second user to a first group messaging conversation (704a), and in accordance with the determination that the multiple users to be added to the first group messaging conversation and the second user are part of the same messaging service, the electronic device adds the second user to the first group messaging conversation, such as in Figure 6D (704b). In some embodiments, determining that the multiple users to be added to the first group messaging conversation and the second user are part of the same messaging service includes determining that the second user uses the same messaging service as one or more of the multiple users. In accordance with the determination that the multiple users to be added to the first group messaging conversation and the second user are part of the same messaging service (for example, adding the second user to the first group messaging conversation does not create a hybrid group), the second user is added to the first group messaging conversation without initiating the process of generating the second group messaging conversation. Determining whether a user added to a group messaging conversation uses the same messaging service as other users in the group messaging conversation, and adding the second user to the first group messaging conversation based on that determination, avoids creating a new group messaging conversation every time the membership of a group messaging conversation changes, thereby reducing the total number of group messaging conversations that must be stored on the device and, otherwise, reducing the processing resources required to create new conversations.

[0172] In some embodiments, the process of generating a second group messaging conversation (706a) includes displaying a messaging preference user interface, such as the one shown in Figure 6F, via a display generation component, to indicate whether the identification information of the first group messaging conversation should be applied to the second group messaging conversation (706b). In some embodiments, the messaging preference user interface includes one or more selectable options that, when selected by the user, automatically apply the identification information associated with the first group messaging conversation to the second group messaging conversation. Examples of identification information include a group name, a photograph, or any other medium used to distinguish and identify the group messaging conversation from other group messaging conversations.

[0173] In some embodiments, while displaying the messaging preference user interface, the electronic device receives an indication via one or more input devices, such as contact 603 in Figure 6F, to apply the identification information of a first group messaging conversation to a second group messaging conversation (706c). In some embodiments, the indication to apply the identification information of a first group messaging conversation to a second group messaging conversation includes detecting a selection of an option displayed in the messaging preference user interface to use all (or some) of the identification information associated with the first group messaging conversation for the second group messaging conversation. Optionally, the messaging preference user interface includes a number of selectable options that allow the user to choose which specific identification information associated with the first group messaging conversation to apply to the second group messaging conversation.

[0174] In some embodiments, upon receiving an indication to apply the identification information of a first group messaging conversation to a second group messaging conversation, the electronic device associates the identification information, such as the name Roomies in Figure 6G, with the second group messaging conversation (706d). In some embodiments, associating the identification information with the second group messaging conversation includes copying the identification information associated with the first group messaging conversation and storing the copied information in a memory location associated with the identification information of the second group messaging conversation. For example, a user optionally indicates, via the messaging preference user interface, that they want to use the name and / or picture associated with the first group messaging conversation for the second group messaging conversation. The name and / or picture associated with the first group messaging conversation is optionally copied and stored as the identification information associated with the second group messaging conversation. By allowing users to reuse identification information when generating new group messaging conversations in response to changes in membership in previous group messaging conversations, users can easily identify relationships between two or more group messaging conversations, thus minimizing the cognitive load on the user, leading to a more efficient user experience on the device, reducing errors in providing identification information for new group messaging conversations, and thus reducing the need for user input to correct those errors.

[0175] In some embodiments, while displaying the messaging preference user interface, the electronic device receives an indication via one or more input devices that it does not want to apply the identification information of a first group messaging conversation to a second group messaging conversation, such as when contact 603 in Figure 6F is detected by the device selection option 638 (708a). In some embodiments, the messaging preference user interface includes selectable options that allow the user to indicate that they do not want to associate any (or some) identification information associated with a first group messaging conversation with a second group messaging conversation.

[0176] In some embodiments, upon receiving an indication that the identification information of a first group messaging conversation should not be applied to a second group messaging conversation, the electronic device displays a prompt via a display generation component to provide identification information to associate with the second group messaging conversation, for example, when contact 603 in Figure 6F is detected by the electronic device selection option 638 (708b). In some embodiments, upon receiving an indication that the identification information of a first group messaging conversation should not be applied to a second group messaging conversation, the user is prompted to manually enter identification information to associate with the second group messaging conversation. For example, if the user declines to reuse the group name and / or photo associated with the first group messaging conversation, the user is prompted to provide a new photo and / or name for the second group messaging conversation. Optionally, the device detects one or more inputs from the user via one or more input devices to manually provide identification information to associate with the second group messaging conversation. Optionally, the prompt includes selectable options that allow the user to indicate that they do not wish to provide identification information for the second group messaging conversation. If a user selects an optional option that allows them to indicate that they do not want to provide their identification information to a second group messaging conversation, the first group messaging conversation retains its identification information. By allowing the user the option not to reuse the identification information associated with the first group messaging conversation for the second group messaging conversation, the user is given control over how their group messaging conversations are organized, thus enabling customization of the user experience on the device and reducing the need for user input to provide identification information for all group messaging conversations stored on the device.

[0177] In some embodiments, upon receiving an indication to apply the identification information of a first group messaging conversation to a second group messaging conversation, the electronic device disassociates the identification information from the first group messaging conversation (710), as shown in Figure 6K, and the first group messaging conversation is no longer identified by the name Roomies. In some embodiments, if a user provides an indication via the messaging preference user interface to use the identification information associated with a first group messaging conversation for a second group conversation, optionally the identification information is from the first group messaging conversation after it has been associated with the second group messaging conversation. Optionally, disassociating the identification information from a group messaging conversation includes deleting the identification information in memory from a memory location associated with the storage of the identification information associated with the first group messaging conversation. Optionally, disassociating the identification information from a group messaging conversation includes disassociating the image from the group messaging conversation and disassociating the name from the group messaging conversation, and instead identifying the group messaging conversation using the name of the user associated with the group messaging conversation. Disassociating an identifier from a group messaging conversation when a user reuses it for a different group messaging conversation ensures that the same identifier is not used for two different group messaging conversations, thereby minimizing user confusion when viewing multiple group messaging conversations on the messaging application and reducing the amount of input errors applied to the device by the user.

[0178] In some embodiments, the process of generating a second group messaging conversation includes identifying a user in the second group messaging conversation using a second electronic messaging identifier, based on the determination that a user among a plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier used for messaging using a first messaging service, and using a second electronic messaging identifier different from the first messaging identifier used for messaging using a second messaging service different from the first messaging service (712), wherein the second electronic messaging identifier is determined from contact information associated with the user, as shown in Figure 6G. In some embodiments, the first electronic messaging identifier used to identify a user in the first group messaging conversation may be compatible with the messaging service employed by the first group conversation but not with the messaging service used by the second group messaging conversation. Therefore, in order to facilitate the user's participation in the second group messaging conversation, the process of generating the second group messaging conversation includes determining that the user's contact information includes a second electronic messaging identifier compatible with the messaging service used by the second group messaging conversation, and using the second electronic messaging identifier to identify the user in the second group messaging conversation. For example, if a user adopts an electronic messaging identifier (e.g., an email address) in the first group conversation, but the electronic messaging identifier is not compatible with the messaging service used by the second group messaging service, the process of generating the second group messaging conversation includes determining whether the user has a telephone number (compatible with the second messaging service) stored in the contact information associated with the user, and using the telephone number instead to identify the user in the second group messaging conversation.In some embodiments, contact information associated with a user in a group messaging conversation is stored on an electronic device (for example, in a contacts or address book application on the electronic device). Optionally, contact information associated with a user is stored on a separate device accessed by the electronic device. By automatically switching the user's identification information to a format compatible with the new group messaging conversation, the user can participate in a second group messaging conversation without requiring manual user input to enter identification information compatible with the new group messaging conversation.

[0179] In some embodiments, the process of generating a second group messaging conversation determines that a user among multiple users is identified in the first group messaging conversation using a first electronic messaging identifier used for messaging using the first messaging service, and that the contact information associated with the user includes multiple electronic messaging identifiers used for messaging using a second messaging service different from the first messaging service. In this determination, the electronic device displays a separate user interface associated with the messaging application in which the second group messaging conversation takes place via a display generation component (714). The separate user interface includes multiple users and multiple representations of the second user that are part of the second group messaging conversation, such as the destination field 640 in Figure 6G, and the representation of a user among multiple users whose contact information includes multiple electronic messaging identifiers is visually distinguished from the others among the multiple representations of the user and the second user, such as Maddy in Figure 6G. In some embodiments, once the second group messaging conversation is created, the user interface used to conduct the second group messaging conversation on the messaging application includes a list of users associated with the second group messaging conversation. Optionally, a list of users is displayed in the "To" field of the user interface used to conduct a group messaging conversation. In some embodiments, the contact information includes multiple electronic messaging identifiers used for messaging services associated with the second group messaging conversation, and users who are asked to select one of the multiple messaging identifiers for use are visually distinguished within the list of users associated with the second group messaging conversation, thereby indicating to the users that a selection of an electronic messaging identifier is required of them.In some embodiments, users whose contact information includes multiple electronic messaging identifiers and other members whose names are visually distinguishable include users whose electronic messaging identifiers do not require selection by the user for use in a second group messaging conversation. Optionally, visually distinguishing a list of users includes visually highlighting the list by using a specific color, using a specific colored font, using a different font size (e.g., larger), or using a different font within the list of users. By providing a visually distinguishable representation of users who have electronic messaging identifiers that need to be selected by the user, users can quickly and efficiently set up a new group messaging conversation without having to manually provide input for reviewing the electronic messaging identifiers of all members of the group messaging conversation, thus avoiding the input required to correct errors associated with manually providing input.

[0180] In some embodiments, while displaying an individual user interface, the electronic device receives input via one or more input devices corresponding to a selection of a user representation from among multiple users whose contact information includes multiple electronic messaging identifiers, such as contact 603 in Figure 6G (716a). In some embodiments, receiving input via one or more input devices includes receiving a tap on a touchscreen at a location corresponding to the representation. Optionally, receiving input via one or more input devices includes receiving a mouse click at a display location corresponding to the representation. In some embodiments, users whose contact information includes multiple electronic messaging identifiers are selectable on a list so that the user can identify which electronic messaging identifier from the multiple electronic messaging identifiers to use in a second group messaging conversation.

[0181] In some embodiments, upon receiving input, the electronic device displays, via a display generation component, a plurality of selectable options corresponding to a plurality of electronic messaging identifiers that can be selected to identify a user having a corresponding electronic messaging identifier in a second group messaging conversation, such as the selectable options 648A-C in Figure 6H (716b). In some embodiments, when a user selects from a list a user whose contact information includes a plurality of electronic messaging identifiers, the user is presented with a list of a plurality of electronic identifiers and selects an electronic messaging identifier from the plurality of electronic messaging identifiers for use in the second group messaging conversation. In some embodiments, the electronic device receives input to select an electronic messaging identifier from a plurality of electronic messaging identifiers and uses the selected electronic messaging identifier to identify a user in the second group messaging conversation. By providing the user with a selectable list of electronic identifiers to be used in the second group messaging conversation, the user can efficiently select an electronic identifier to associate with each user in the second group messaging conversation, thereby reducing the need for the user to manually enter electronic messaging identifiers and thus minimizing incorrect user input applied to the electronic device.

[0182] In some embodiments, the process of generating a second group messaging conversation performed by an electronic device includes, upon determination that a user among a plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier used for messaging using a first messaging service, and that the contact information associated with the user does not include a second electronic messaging identifier used for messaging using a second messaging service different from the first messaging service, via a display generation component (718), wherein the user interface includes a content entry field configured to receive input for entering a third electronic messaging identifier used for messaging using a second messaging service to associate with the user in the second group messaging conversation, as shown in Figure 6I. In some embodiments, if a user of the first group messaging conversation does not have an electronic messaging identifier used with the messaging service associated with the second group messaging conversation, the user is prompted to manually enter an electronic messaging identifier to associate with the user for use in the second group messaging conversation. Optionally prompting the user to manually enter an electronic messaging identifier includes providing the user with a content entry field on a user interface that allows the user to manually enter an electronic messaging identifier. In some embodiments, an electronic device receives one or more inputs that provide an electronic messaging identifier and uses the provided electronic messaging identifier to identify a user in a second group messaging conversation.By allowing users to manually enter the electronic messaging identifier of a specific user in a group messaging conversation, it is ensured that a new group messaging conversation includes all desired members who were part of a previous group messaging conversation, thereby minimizing the number of separate group messaging conversations stored on the electronic device.

[0183] In some embodiments, the process of generating a second group messaging conversation performed by an electronic device includes, upon determination that a user among a plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier, and that the contact information associated with the user does not include a second electronic messaging identifier used for messaging using a second messaging service different from the first messaging service, via a display generation component (720), wherein the individual user interface, such as selectable option 652 in Figure 6I, includes a selectable option for removing the user from the second group messaging conversation. In some embodiments, if a user of the first group messaging conversation does not have an electronic messaging identifier used with the messaging service associated with the second group messaging conversation, the user of the device is presented with a selectable option on the user interface for removing the user of the first group messaging conversation from the second group messaging conversation. In some embodiments, when the device receives input from the user corresponding to a selection of the selectable option, the device disassociates the user of the first group messaging conversation from the second group messaging conversation. Optionally, unassociating a user from a second group messaging conversation includes ceasing to add a user from a first group messaging conversation to a second group messaging conversation.By allowing users to remove users who do not have an electronic messaging identifier that can be used in a newly generated group messaging conversation, it is ensured that users can still generate a new group messaging conversation even if one or more users from the previous group messaging conversation (used to create the new group messaging conversation) do not have an electronic messaging identifier that can be used with the new group messaging conversation. Thus, the device can generate a new group messaging conversation to respond to user requests even if it does not have complete information about each user in the group messaging conversation.

[0184] In some embodiments, such as in Figure 6K, the first group messaging conversation is maintained by the messaging application after the second group messaging conversation has been generated (722). In some embodiments, once the second group messaging conversation has been generated, both the first and second group messaging conversations are maintained by the messaging application. Optionally, maintaining the first and second group messaging conversations includes displaying both the first and second group messaging conversations in a list of active conversations on the messaging application (as described, for example, with reference to Method 900) and providing the user with the ability to view the messaging activity associated with both group messaging conversations. By maintaining the previous group messaging conversation on the messaging application even when a new group messaging conversation is generated based on the previous group messaging conversation, the user can access older messaging activity that was part of the previous group messaging conversation, thereby ensuring a complete record of messaging activity associated with the user on the device, and thus the device can generate a new group messaging conversation without losing information from the previous group messaging conversation.

[0185] In some embodiments, receiving an indication in an electronic device to add a second user to a first group messaging conversation (724a) includes receiving a first input via one or more input devices to display one or more details associated with the first group messaging conversation, such as contact 603 in Figure 6A (724b). In some embodiments, receiving a first input to display one or more details associated with the first group messaging conversation includes the device receiving a selection from the device user to select the name (or other identifying information) of the first group messaging conversation displayed on a user interface in a messaging application where the first group messaging conversation takes place (e.g., a user interface that includes a representation of the messaging activities included in the first group messaging conversation). Optionally, receiving a first input includes the device receiving a selection from the device user to select a picture (or other identifying information) of the first group messaging conversation displayed on the user interface. In some embodiments, the selection of identifying information corresponds to the selection of conversation management options described with reference to Method 700. In some embodiments, the first input is a touch input on a touch-sensitive surface, a voice input, or a mouse input.

[0186] In some embodiments, upon receiving a first input for displaying one or more details associated with a first group messaging conversation, the electronic device displays a details user interface for the first group messaging conversation (e.g., the management user interface described with reference to Method 700) via a display generating component (724c), the details user interface including information associated with the first group messaging conversation that is not displayed in the user interface associated with the messaging application in which the first group messaging conversation takes place, such as user interface 614 in Figure 6B. In some embodiments, the details user interface for the first group messaging conversation includes, but is not limited to, a name associated with the first group messaging conversation, a photograph associated with the first group messaging conversation, and / or other identifying information associated with the first group messaging conversation, a list of users associated with the first group messaging conversation, and / or selectable options for adding new users to the first group messaging conversation.

[0187] In some embodiments, while displaying a detailed user interface, the electronic device receives a second input via one or more input devices, such as contact 603 in Figure 6B, for adding a second user to a first group messaging conversation (724d). In some embodiments, receiving a second input for adding a second user to a first group messaging conversation includes the device receiving a selection from the user in the detailed user interface of the first group messaging conversation, where the user selects an option to add a new user to the first group messaging conversation. In some embodiments, in response to the user's selection of a new user to the first group messaging conversation, the device displays one or more user interfaces for indicating an identifier that identifies the added user (e.g., from contact information stored in an address book application, from a manual entry of an identifier (singular or plural) (e.g., phone number, email address)). By allowing the user to indicate their desire to add a new user to the group messaging conversation in a user interface separate from the user interface used to display messaging activity in the group messaging conversation, the user interface in which the group messaging conversation takes place can display more messaging activity on a single display.

[0188] It should be understood that the specific order of operations described in Figures 7A to 7E is merely illustrative and not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various methods for rearranging the operations described herein. It should also be noted that details of other processes described herein with respect to other methods described herein (e.g., Method 900) are also applicable in a manner similar to Method 700 described above with respect to Figures 7A to 7E. For example, the operation of an electronic device that adds a user to a hybrid group messaging conversation with reference to Method 700 optionally has one or more characteristics of deleting a hybrid group messaging conversation with reference to other methods described herein (e.g., Method 900). In another example, the hybrid and non-hybrid group messaging conversations of Methods 700 and 800 share one or more characteristics. In addition, the messaging interaction described with reference to Method 700 optionally has one or more characteristics of the messaging interaction described with reference to Method 900. For brevity, those details will not be repeated here.

[0189] The operations of the information processing method described above are optionally performed by activating one or more functional modules within the information processing device, such as a general-purpose processor (e.g., as described above in relation to Figures 1A-1B, 3, 5A-5J) or an application-specific chip. Furthermore, the operations described above with reference to Figures 7A-7E are optionally performed by the components shown in Figures 1A-1B. For example, the display operation 702a, the reception operation 702a, and the start operation 702c are optionally performed by the event sorting unit 170, the event recognition unit 180, and the event processing unit 190. When an individual default event or sub-event is detected, the event recognition unit 180 activates the event processing unit 190 associated with the detection of that event or sub-event. The event processing unit 190 optionally uses or calls the data update unit 176 or the object update unit 177 to update the application internal state 192. In some embodiments, the event processing unit 190 accesses an individual GUI update unit 178 to update what is displayed by the application. Similarly, it will be obvious to those skilled in the art how other processes can be carried out based on the components shown in Figures 1A and 1B. User interface for sending and receiving messages

[0190] Adding users to a hybrid group messaging conversation (or adding users to a non-hybrid group messaging conversation that makes it a hybrid conversation), as well as leaving a hybrid group messaging conversation, can present challenges to electronic devices. In some situations, users of messaging applications that facilitate group messaging conversations may want to no longer view the group messaging conversation (e.g., the user wants to delete the group messaging conversation) or not receive new messaging activity associated with the group messaging conversation (e.g., the user wants to block future messaging activity received on the group messaging conversation). However, in situations where the group messaging conversation is a hybrid group messaging conversation, the messaging service used to facilitate the group messaging conversation may not make it easy to delete and block the group messaging conversation. In some situations, if the group messaging conversation is a hybrid conversation, the user may be able to delete the group messaging conversation, but if an external user, who is also part of the group messaging conversation, sends new messaging activity to the group conversation, the electronic device will receive the new messaging activity and display the messaging activity as a new active group messaging conversation. In some situations, users cannot block new messaging activity, forcing them to repeatedly delete the group messaging conversation every time new messaging activity is received. Requiring users to participate in the process of deleting a group messaging conversation every time new messaging activity is received can lead to input errors on the device and consume computing resources.The embodiments described below provide an electronic device that offers an efficient user interface for deleting and blocking hybrid group messaging conversations, and thus a method for enhancing user interaction with the device. By enhancing interaction with the device, the amount of time required by the user to perform an action is reduced, and thus the power consumption of the device is reduced, increasing battery life for battery-powered devices. It is understood that people use a device. When a person uses a device, that person is optionally called a user of that device.

[0191] Figures 8A–8J illustrate exemplary ways in which an electronic device displays a user interface for deleting and blocking hybrid group messaging conversations. Embodiments in these figures are used to illustrate the processes described below, including the process described with reference to Figure 9. While Figures 8A–8J show various embodiments of how an electronic device may perform the processes described below with reference to Figure 9, these embodiments are not intended to be limiting, and it should be understood that an electronic device may perform one or more of the processes described below with reference to Figure 9 in ways not expressly described with reference to Figures 8A–8J.

[0192] Figure 8A shows an exemplary device 500 that displays the user interface 812. In some embodiments, the user interface 812 is displayed via a display generating component. In some embodiments, the display generating component is a hardware component (including, for example, an electrical component) that can receive display data and display the user interface. In some embodiments, examples of the display generating component include a touchscreen display, a monitor, a television, a projector, an integrated, separate, or external display device, or any other suitable display device.

[0193] As shown in Figure 8A, the electronic device 500 displays a messaging user interface 812 on the touchscreen 504 (for example, a messaging application installed on the device 500). In some embodiments, the user interface 812 is an arbitrary user interface that displays information about one or more messaging conversations, including one or more group messaging conversations. In Figure 8A, the messaging user interface 812 includes messaging activity related to a group messaging conversation labeled “Friends”. The user interface 812 includes a group messaging conversation information section 802 that displays the name of the group (e.g., Friends). Optionally, the conversation information section 802 of the user interface 812 includes a photograph associated with the group messaging conversation, in addition to the name of the group messaging conversation, similar to the information section 602 in Figure 6A. Although the example in Figure 8 describes a hybrid group messaging conversation that includes identifying information such as names and photographs, this disclosure should not be considered limiting. In some embodiments, a hybrid group messaging conversation does not include associated identification information, either because the user of the electronic device does not provide identification information, or because the messaging application does not allow identification information to be associated with the hybrid group messaging conversation. The systems and processes described below are applicable to all hybrid group messaging conversations, regardless of whether the hybrid group messaging conversation includes identification information or not.

[0194] In some embodiments, the user interface 812 of the messaging application shown in Figure 8A includes messaging activities associated with a group messaging conversation. For example, as shown in Figure 8A, the user interface 812 includes messaging activities 804A-B from a first user of the group messaging and messaging activities 806A-B from a user of the electronic device on which the messaging application is running. Figure 8A illustrates a hybrid group messaging conversation, such as described with reference to Figure 6G and Methods 700 and / or 900, where one or more users who are part of a group messaging conversation use a different messaging service than one or more other users to interact with the group messaging conversation. Optionally, the user interface 812 includes one or more visual indicators to identify a group messaging conversation as a hybrid group messaging conversation. For example, messaging activities 806A-B on the user interface 812 are colored / highlighted to indicate that a friends group messaging conversation is a hybrid group messaging conversation. In some embodiments, messaging activities 804A-B include the same color / highlighting to indicate that a friends group messaging conversation is a hybrid group messaging conversation. Since Roomies conversations are non-hybrid group messaging conversations, the color / highlighting of friend group messaging conversations differs from the color / highlighting of Roomies group messaging conversations in Figure 6A. In some embodiments, the user interface 812 includes a messaging activity entry section 808 (e.g., a text or content entry field) that is selectable by the user of the electronic device and receives input of messaging activity (such as text) to be displayed in the user interface 812 as part of a group messaging conversation.

[0195] In some embodiments, the group conversation information section 802 is selectable. In Figure 8A, the device 500 detects a selection of the selectable section 802 (e.g., via a tap on a contact 803 on section 802). In response to detecting a selection of section 802, the device 500 displays the group messaging conversation information user interface 814 of the messaging application, as shown in Figure 8B and similar to the user interface 614 in Figure 6B. The group messaging conversation information user interface 814 includes various selectable options 816A-C for performing various actions associated with the group messaging conversation. For example, the user interface 814 optionally includes a selectable option 816A, which, when selected, causes the device to display information about one or more users associated with the selectable option. For example, when the device 500 receives an indication that a user has selected option 816A (e.g., via a tap on a touchscreen), the device may display a user interface containing contact information associated with the selectable option. Optionally, the user interface 814 includes selectable options 816B that, when selected, cause the device to display information about the location of one or more users associated with the selectable option. For example, when the device 500 receives an indication that a user has selected option 816B (e.g., by a tap on the touchscreen), the device may display a user interface that includes a map containing the locations of the users associated with selectable option 816B.

[0196] In certain situations, a user of an electronic device may want to remove themselves from a group messaging conversation, but this may not be possible because the group messaging conversation is a hybrid conversation. When a group messaging conversation is a hybrid conversation, the user can instead delete and block the group messaging conversation, as described below. In some embodiments, the user interface 814 includes selectable options 816C for deleting and blocking the group messaging conversation. In Figure 8B, the device 500 detects a selection of the selectable option 816C (for example, via a tap of a contact on option 816C). In response to detecting a selection of option 816C for deleting and blocking the group messaging conversation, the device determines whether the group messaging conversation is a hybrid group messaging conversation or a non-hybrid group messaging conversation. In response to the device determining that the group messaging conversation is a hybrid group messaging conversation and detecting a selection of option 816C for deleting and blocking the group messaging conversation, the device removes the group messaging conversation from the active message set of the messaging application and stores the group messaging conversation in the deleted message set of the messaging application (described in more detail below). If a group messaging conversation is a non-hybrid conversation, users can simply leave the group messaging conversation and will no longer receive messaging activity sent to the group messaging conversation.

[0197] Figure 8C shows the Active Message Set User Interface 818. In some embodiments, the Active Message Set User Interface 818 displays one or more active messaging conversations. An “active” messaging conversation can refer to a messaging conversation that is actively displayed to the user by the device through the messaging application when the user interacts with the messaging application. In some embodiments, messaging conversations (groups or others) that are part of the active message set of the messaging application are automatically displayed to the user on the Active Message Set User Interface when the user interacts with the messaging application. In some embodiments, the Active Message Set User Interface 818 includes one or more messaging conversation entries 820A-F that display information about each group messaging conversation stored in the active message set. Optionally, the information displayed in each entry 820A-F includes information about the user(s) that are part of the messaging conversation, information about the messaging activity received in each messaging conversation associated with the entries 820A-F, and, if the entry is a group messaging conversation, identification information associated with the group messaging conversation, including but not limited to the name and / or photo associated with the group messaging conversation.

[0198] In some embodiments, the electronic device removes the group messaging conversation (indicated by the user to be deleted and blocked) from the active message set in response to detecting that the user of the electronic device has selected option 816C in Figure 8B. Thus, as shown in Figure 8C, the friend group messaging conversation deleted and blocked by the user no longer appears in the active message set user interface 818. In addition, in response to the user of the electronic device selecting option 816C in Figure 8B, the group messaging conversation is moved from the active message set to the deleted message set, as shown in Figure 8D. Figure 8D shows the deleted message set user interface 824 of the messaging application. In some embodiments, the deleted message set includes messaging conversations (group or otherwise) that the user of the electronic device has instructed to be deleted. In some embodiments, messaging conversations stored in the deleted message set are accessible to the user but are not actively displayed by the messaging application unless the user specifically navigates to the deleted message set user interface 824 on the messaging application. In some embodiments, the deleted message set user interface 824 includes one or more selectable entries 826A-C. In some embodiments, selectable entries 826A-C display information about each group messaging conversation stored in the deleted message set. Optionally, the information displayed in each entry 826A-C includes information about the user(s) who are part of the messaging conversation, information about the messaging activity received in each messaging conversation associated with entries 826A-C, and, if the entry is a group messaging conversation, identification information associated with the group messaging conversation, including but not limited to names and / or photos associated with the group messaging conversation.

[0199] In some embodiments, depending on whether the user of the electronic device selects option 816C in Figure 8B, the group messaging conversation (indicated by the user to be deleted and blocked) is removed from the active message set and stored in the deleted message set. Thus, as shown in Figure 8D, the friend group messaging conversation deleted and blocked by the user appears here in the deleted message set user interface 824 (having been removed from the active message set 818 as described above). In some embodiments, the deleted and blocked hybrid group messaging conversation continues to receive messaging activity directed to the group messaging conversation even while stored in the deleted message set. In contrast, when a non-hybrid group messaging conversation is moved to the deleted message set, the conversation does not receive further messaging and becomes inactive. For example, as shown in Figure 8D, the selectable entry 826A associated with the friend group messaging conversation includes a messaging activity indicator 828 that indicates the group messaging conversation has received new messaging activity (since the group messaging conversation was last accessed by the user on the electronic device and / or since the group messaging conversation was moved to the deleted message set). Optionally, the messaging activity indicator 828 includes a visual indicator (such as a colored dot or other shape) indicating that a group messaging conversation has received new messaging activity. Optionally, the messaging activity indicator 828 includes at least a “snippet” (e.g., a portion) of the most recent messaging activity received in a group messaging conversation that is not accessed by the user. In some embodiments, an optional entry 826A associated with a friends group messaging conversation includes a numerical indicator 830 indicating the number of messages (e.g., messaging activity) received in the group messaging conversation since the user last accessed it.

[0200] In some embodiments, while a messaging conversation is part of a deleted message set, messaging activity associated with the messaging conversation is stored as part of the deleted message set for a predetermined amount of time. After the predetermined time, the messaging activity is permanently deleted from the group messaging conversation and / or device 500 and is no longer accessible to the user of the electronic device. In some embodiments, the predetermined amount of time is specific to individual messages (e.g., messaging activity) and begins the moment the messaging activity is stored in the deleted message set. For example, messaging activity that was part of a group messaging conversation when it was moved from the active message set to the deleted message set (in response to a user deleting and blocking the group messaging conversation) is permanently deleted from the group messaging activity after being in the deleted message set for a predetermined amount of time. New messaging activity received in the group messaging conversation after it has been moved to the deleted messaging conversation is deleted after being on the deleted message set for a predetermined amount of time (measured from the time the new messaging activity was first stored in the deleted message set). As an example, the predetermined time may range from one hour to 100 days.

[0201] In some embodiments, selectable entries 826A-C are selectable. In Figure 8D, device 500 detects the selection of selectable entry 826A (for example, via a tap of contact 803 in selectable entry 826A). In response to detecting the selection of selectable entry 826A, device 500 displays the group messaging recovery portion 832 on the deleted message set user interface 824 of the messaging application, as shown in Figure 8E. In some embodiments, a user of the electronic device can recover a group messaging conversation. “Recovering” a group messaging conversation includes removing the group messaging conversation from the deleted message set and moving the group messaging conversation to the active message set. In some embodiments, the group messaging recovery portion 832 of the user interface 824 includes various selectable entries, as shown in Figure 8D.

[0202] In some embodiments, the group messaging recovery unit 832, when selected, initiates the process of moving the group messaging conversation from the deleted message set to the active message set. If the device detects that the user has chosen to cancel, the group messaging recovery unit 832 is no longer displayed by the device, and the recovery process is not initiated. In Figure 8E, device 500 detects the selection of the recovery unit 832 (e.g., via a tap of contact 803). In response to detecting the selection of the recovery unit 832, device 500 displays the active message set 824, as shown in Figure 8F. Optionally, the user navigates to the active message set 824 using other inputs after the recovery unit 832 has been selected. As shown in Figure 8F, the friends group messaging conversation reappears on the active message set interface 818 in entry 834A. In some embodiments, the friends group messaging conversation retains its name and picture. Similar to the example in Figure 8C, the active message set interface 818 includes entries 834B-F corresponding to other messaging conversations stored in the active message set. Upon detecting the selection of recovery portion 832 in Figure 8E, device 500 removes the friend group messaging conversation from the deleted message set, as shown in Figure 8H.

[0203] In some embodiments, entries 834A-F are selectable by the user of the electronic device. In Figure 8F, device 500 detects the selection of entry 834A corresponding to a friends group messaging conversation (e.g., via a tap of contact 803). In response to detecting the selection of entry 834A, device 500 displays the group messaging user interface 812 as shown in Figure 8G. Similar to the example in Figure 8A, the group messaging user interface 812 in Figure 8G includes messaging activity associated with the group messaging conversation. As shown in Figure 8G, one or more messages (e.g., messages that were part of the friends group messaging conversation before the group messaging conversation was deleted and blocked by the user) are no longer part of the group messaging conversation because they have exceeded a predetermined amount of time stored in the deleted message set before those messages are permanently deleted (as described above). For example, as shown in Figure 8A, the friends group messaging conversation included messaging activity received in the group messaging conversation on Thursday, March 12 and Wednesday, May 3, and the group messaging conversation was part of the active message set (before it was deleted and blocked). However, upon recovery, as shown in Figure 8G, the group messaging conversation only included messaging activity received today, because those messages were not stored in the deleted message set for longer than a predetermined time, and "today" is longer than a predetermined time after May 3.

[0204] In some embodiments, if all messaging activities associated with a group messaging conversation are permanently deleted (due to exceeding a predetermined allocated time) while the group messaging conversation is stored in the deleted message set, any new messaging activities directed to the deleted group messaging conversation are automatically stored and / or displayed in the active message set, as shown in Figure 8I. Optionally, when new messaging activities directed to a deleted group messaging conversation are automatically stored in the active message set, the messaging activity is stored as a new group messaging activity and therefore does not have any associated customized identification information, such as the group name and / or photo. Instead, the group messaging conversation includes default identification information, but is not limited to, the names of the participants and a default avatar. In some embodiments, the user interface 818 includes one or more selectable entries 838A-F, as in the example in Figure 8C. In Figure 8I, device 500 detects the selection of entry 838A corresponding to a newly created group messaging conversation (e.g., via a tap on contact 803). Upon detecting the selection of entry 838A, device 500 displays the group messaging user interface 812 as shown in Figure 8J. In some embodiments, the user interface 812 includes messaging activity 840 associated with a newly created group messaging conversation (for example, after a friends group messaging conversation has been automatically removed from the deleted message set by device 500, in response to messaging activity received in that group messaging conversation). As shown in Figure 8J, messages that were part of the group messaging activity before the group messaging conversation was deleted and blocked in Figure 8B are not part of the newly created group messaging conversation (because they are permanently deleted while on the deleted message set).The messaging activity 840 of user interface 812 is associated with a newly created group messaging conversation because it was received after the friends group messaging conversation was permanently deleted from the deleted message conversation (due to all messages in the group messaging conversation exceeding their predetermined time allocation for the deleted message set).

[0205] Figures 9A–9C are flowcharts illustrating how an electronic device deletes a hybrid group messaging conversation according to some embodiments of the present disclosure. Method 900 is optionally performed on a first device and / or an electronic device such as device 100, device 300, or device 500 as described above with reference to Figures 1A–1B, 2–3, 4A–4B, and 5A–5C. Some operations in Method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0206] As described below, Method 900 provides a method for an electronic device to delete a hybrid group messaging conversation. Automatically deleting a messaging conversation when a mixed-service group conversation is involved allows users using different messaging services to remove themselves from unwanted group messaging activities, including the ability to modify their membership in such group messaging activities so that they no longer receive automatic notifications about messaging activity in mixed-service group conversations, thereby reducing resource consumption by the electronic device and reducing manual user input required to manually delete messaging conversations.

[0207] In some embodiments, Method 900 is performed in an electronic device that communicates with a display generation component and one or more input devices. In some embodiments, the electronic device, the display generation component, and / or one or more input devices have one or more of the characteristics of the electronic device, the display generation component, and / or one or more input devices of Method 700.

[0208] In some embodiments, while a user of an electronic device is part of a first group messaging conversation involving multiple users (as described with reference to Method 700, for example), and is viewing a user interface associated with a messaging application in which the first group messaging conversation takes place (for example, the user interface and / or messaging application has one or more of the characteristics of the user interface and / or messaging application described with reference to Method 700) via a display generating component, the electronic device receives an indication via one or more input devices to remove the user of the electronic device from the first group messaging conversation, such as contact 803 in Figure 8B (902a). In some embodiments, the indication for removing the first user includes detecting a selection of a conversation management option displayed on the user interface (as described with reference to Method 700, for example), thereby displaying one or more selectable options for removing the user from the first group messaging conversation. In some embodiments, while viewing a management user interface that includes one or more selectable options, the electronic device detects a selection of one of the options corresponding to removing the user from the first group messaging conversation. In some embodiments, this indication is touch input on a touch-sensitive surface, voice input, or mouse input.

[0209] In some embodiments, upon receiving an indication to remove a user of the electronic device from a first group messaging conversation (902b), the electronic device initiates a process to remove the first group messaging conversation from the messaging application, for example, as shown in Figure 8C, based on the determination that the first group messaging conversation includes one or more users of a group of users who are not part of the same messaging service (as described, for example, with reference to Method 700) (902c). In some embodiments, determining that the first group messaging conversation includes one or more users who are not part of the same messaging service includes determining that a first user of the one or more users uses a different messaging service than the messaging service used by a second user of the one or more users. Additionally or alternatively, determining that the first group messaging conversation optionally includes determining that a first user of the first group messaging conversation does not use a messaging service used by one or more other users of the first group messaging conversation. In some embodiments, initiating the process of deleting a first group messaging conversation includes removing the first group messaging conversation from the list of active messaging conversations maintained by the messaging application. Optionally, deleting the first group messaging conversation from the list of active messaging conversations includes not allowing any messaging activity received on the first group messaging conversation to be presented to one or more users through a user interface as new messaging activity on an active messaging conversation. In some embodiments, deleting a first group messaging conversation includes moving the first group messaging conversation to a list of inactive messaging conversations.Optionally moving a first group messaging conversation to a list of inactive messaging conversations includes displaying any messaging activity received on the first group messaging conversation to the list of inactive messaging conversations. In some embodiments, deleting a first group messaging conversation includes preventing automatic notifications from being generated (e.g., displayed and / or presented as audio) on the user's electronic device when messaging activity is received on the first group messaging conversation. In some embodiments, initiating the process of deleting a group messaging conversation in a messaging application includes providing the user with one or more user interfaces configured to confirm that the user wants to delete the first group messaging conversation. If the device detects that the user has confirmed that they want to delete the first group messaging conversation, the device moves the first group messaging conversation to a list of inactive messages. When deleted, the first group messaging conversation appears inactive to the user who deleted the conversation, but optionally remains active and / or accessible to other users who are part of the first group messaging conversation (for example, these other users can still send / receive messages in the first group messaging conversation). Automatically deleting messaging conversations when mixed-service group conversations are involved allows users using different messaging services to remove themselves from unwanted group messaging activities, including the ability to modify their membership in such group messaging activities so that they no longer receive automatic notifications about messaging activity in mixed-service group conversations, thereby reducing resource consumption by electronic devices and reducing the manual user input required to manually delete messaging conversations.

[0210] In some embodiments, deleting a first group messaging conversation involves moving the first group messaging conversation from the messaging application's active message set to the messaging application's deleted message set, as shown in Figure 8D, where the messaging application's deleted message set includes one or more deleted messaging conversations (904). In some embodiments, the active message set includes a set of conversations and messages in which the user is currently engaged and which are displayed by the messaging application when the user accesses the messaging application. In some embodiments, the deleted message set includes a set of conversations and messages that the user has chosen not to be included in the active message set anymore. Optionally, conversations and messages stored in the deleted message set are accessible to the user when the device receives an indication that the user has selected the option to view the deleted message set on the messaging application. By automatically moving a messaging conversation to the deleted message set when the user indicates that the messaging conversation is to be deleted, the user can still access the messaging conversation without it always being displayed to the user when the user accesses the messaging application, thus maximizing the amount of display area on the electronic device that may be dedicated to active messages.

[0211] In some embodiments, while the first group messaging conversation is included in the deleted message set of the messaging application (906a), the electronic device adds the new messaging activity to the first group messaging conversation, such as the friends group messaging conversation in Figure 8D, upon determination that the first group messaging conversation has received new messaging activity (906b). In some embodiments, while the first group messaging conversation is maintained on the deleted message set of the messaging application, any new messaging activity added to the first group messaging conversation (some, some, or all of it) (e.g., from a user other than the user of the electronic device) becomes part of the first group messaging conversation and is accessible to the user when the user accesses the first group messaging conversation stored on the deleted message set. Optionally, when the user accesses the deleted message set on the messaging application, the user interface associated with the deleted message set displays an indication of the new messaging activity associated with the first group messaging conversation via a display generation component. Optionally, the indication of new messaging activity includes placing a visual indicator overlaid on or adjacent to the list of first group messaging conversations on the deleted message set. Optionally, the visual indicator includes placing a visual marker next to the list of first group messaging conversations on the deleted message set, changing the font of the list, and / or changing the color associated with the list.By adding new messaging activity generated on a deleted group messaging conversation while the deleted group messaging conversation remains part of the deleted message set, users can access new messaging activity on the deleted group messaging conversation even if the conversation was deleted by the user. Therefore, the user interface in which the group messaging conversation takes place can display more messaging activity on a single display.

[0212] In some embodiments, while the first group messaging conversation is included in the deleted message set of the messaging application (908a), messaging activity received before the first group messaging conversation is moved to the deleted message set is maintained in the first group messaging conversation by the electronic device (908b) for a first predetermined amount of time after the time the first group messaging conversation is moved to the deleted message set. In some embodiments, messaging activity received before the first group messaging conversation is moved to the deleted message set is deleted from the first group messaging conversation by the electronic device (908c) after a first predetermined amount of time after the time the first group messaging conversation is moved to the deleted message set by the electronic device, such as the message in Figure 8A being deleted from the group messaging conversation in Figure 8G. In some embodiments, when a user deletes a first group messaging conversation and the conversation is moved to the deleted message set, the messaging activity that was associated with the group messaging conversation before deletion is retained for a predetermined amount of time (e.g., a first predetermined amount of time) from the time the group messaging conversation was moved to the deleted message set. Optionally, the messaging activity that was associated with the group messaging conversation before deletion is deleted after the first predetermined amount of time has elapsed.

[0213] In some embodiments, messaging activity received after the first group messaging conversation has been moved to a set of deleted messages by the electronic device is maintained by the electronic device (908d) in the first group messaging conversation for a second predetermined amount of time prior to the current time on the electronic device (e.g., optionally the same as the first predetermined amount of time).

[0214] In some embodiments, messaging activity received after a first group messaging conversation has been moved to a deleted message set by the electronic device is deleted by the electronic device after a second predetermined time period prior to the current time on the electronic device, for example, if message 836b in Figure 8G remains on the deleted message set longer than a predetermined time period (908e). In some embodiments, messaging activity received in a group messaging conversation after the conversation has been moved to a deleted message set is retained for a predetermined time period (e.g., a second predetermined time period) and deleted after the second predetermined time period has expired. By automatically deleting messages older than a predetermined time threshold on a group conversation moved to a deleted message set, the user can still access recent messaging activity on the group messaging conversation while saving memory on the device by deleting old messaging activity.

[0215] In some embodiments, after a first group messaging conversation is included in the deleted message set of a messaging application, an electronic device receives messaging activity associated with the first group messaging conversation via one or more input devices, such as entry 826a in Figure 8D (910a).

[0216] In some embodiments, upon receiving messaging activity associated with a first group messaging conversation, and in accordance with the determination that the first group messaging conversation does not contain any previous messaging activity, the electronic device adds the messaging activity to the conversation in the active message set of the messaging application, such as entry 838a in Figure 8I, via a display generation component (910b). In some embodiments, as described above, if the first group messaging conversation is placed in a deleted message set, and no new messaging activity is received on the first group messaging conversation within a predetermined time, then ultimately, all messaging activity stored on the first group messaging conversation is removed from the first group messaging conversation and / or the messaging application. Optionally, if the first group messaging conversation stored in the deleted message set no longer contains messaging activity (because the messaging activity has been deleted), the first group messaging conversation is removed from the deleted message set, thereby no longer appearing in the deleted message set, and therefore no longer accessible by the device via the messaging application, and / or no longer displayed. In some embodiments, when a first group messaging conversation is removed from the deleted message set because it no longer contains messaging activity, some, all, or any new messaging activity directed to the first group messaging conversation automatically appears in the active message set as part of a new group messaging conversation (for example, different from the first group messaging conversation but including one or more or all of the former participants of the first group messaging conversation as participants).By automatically adding new messaging activity directed to deleted group messaging conversations that have been removed from a message set because they no longer contain messaging activity, it is ensured that users of electronic devices will receive and access new messaging activity even if a group messaging conversation is deleted from the messaging application, and the device does not need to permanently store deleted messages, thereby saving the device's memory resources.

[0217] In some embodiments, while a first group messaging conversation is included in the deleted message set of a messaging application, the electronic device, via a display generation component, displays a user interface that includes one or more representations of one or more deleted conversations, including a representation of the first group messaging conversation that includes a visual indication of the number of unread messages received in the first group messaging conversation while the first group messaging conversation is included in the deleted message set of a messaging application, such as the numerical indicator 830 in Figure 8D (912). In some embodiments, the user interface displaying conversations in the deleted message set includes a visual indication of the number of unread messages (e.g., separate messaging activity instances) received in the first group messaging conversation since the first group messaging conversation was moved to the deleted message set. Optionally, the visual indicator includes a number indicating the number of unread messages displayed along with the entry on the deleted message set associated with the first group messaging conversation. Optionally, the indicator includes at least a portion of the messaging activity displayed on the user interface. By displaying an indicator of unread messages associated with a group messaging conversation while it resided on a deleted message set, users can efficiently determine how many messages have been received in that group messaging conversation since they last accessed the deleted message set. This minimizes the likelihood of users missing messaging activity stored on the deleted message set and reduces the amount of user input on the device required to determine if new messaging activity has occurred in the deleted group messaging conversation.

[0218] In some embodiments, while a group messaging conversation is in a deleted message set of a messaging application, the electronic device displays a user interface via a display generation component that includes one or more representations of the deleted conversations (914), the user interface including a selectable option that allows the user to move the first group messaging conversation from the deleted message set to the active message set. In some embodiments, the user interface displaying the conversations and messages contained in the deleted message conversation includes a selectable option that allows the user to move the first group messaging conversation back to the active message set. Optionally, the user interface having the selectable option is part of the user interface displaying messaging activity associated with the first group messaging conversation. In some embodiments, in response to the device receiving an indication to recover the first group messaging conversation (e.g., move the first group messaging conversation from the deleted message set to the active message set), such as selecting one of the selectable options, the first group messaging conversation is displayed on the user interface including one or more representations of the active (e.g., not deleted) conversations. Optionally, when a first group messaging conversation is recovered and placed in the active message set, it appears in the active message list position based on the time the last messaging activity of the first group messaging conversation was received, even if messaging activity of the first group messaging conversation was received while it was in the deleted list. Optionally, when an electronic device recovers and places a first group messaging conversation in the active message set, it displays it at the top of the list of conversations and messages in the active message set.By providing users with the option to recover group messaging conversations previously selected for deletion, and by automatically replacing the recovered group messaging conversations on the active message set with them, it is ensured that the decision to delete a group messaging conversation is not permanent and is reversible at the user's discretion, thereby allowing the device to reversibly suppress the active display of deleted messages on the device.

[0219] In some embodiments, upon receiving an indication to remove a user of an electronic device from a first group messaging conversation, and in accordance with a determination that multiple users are part of the same messaging service (and optionally, in accordance with a determination that the messaging service used by the users of the first group messaging conversation allows for changes in group conversation membership), the electronic device removes the user of the electronic device from the first group messaging conversation without initiating a process to delete the first group messaging conversation (and without maintaining the first group messaging conversation) (916). In some embodiments, determining that multiple users of the first group messaging conversation are part of the same messaging service includes determining that each user of the first group messaging conversation uses the same messaging service (e.g., optionally, the first messaging service as described with reference to Method 700) while being part of the first group messaging conversation. In some embodiments, the messaging service used by multiple users includes the ability for users to remove themselves from the group messaging conversation (whereas, in contrast, other messaging services may not have this ability). In accordance with the determination that multiple users who are part of the first group messaging conversation are using the same messaging service to conduct the first group messaging conversation, the users are removed from the first group messaging conversation without moving the first group messaging conversation to a deleted message set. By allowing users to remove themselves from the group messaging conversation without moving the group messaging conversation to a deleted message set, the memory and other computing resources of the electronic device are saved.

[0220] It should be understood that the specific order of operations described in Figures 9A to 9C is merely illustrative and is not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various methods for rearranging the operations described herein. It should also be noted that details of other processes described herein with respect to other methods described herein (e.g., Method 700) are also applicable in a manner similar to Method 900 described above with respect to Figures 9A to 9C. For example, the operation of an electronic device presenting the communication features described above with reference to Method 900 optionally has one or more characteristics of adding a user to a hybrid group messaging conversation described herein with reference to other methods described herein (e.g., Method 700). Furthermore, deleting a hybrid group messaging conversation described with reference to Method 900 has one or more characteristics of adding a user to a hybrid group messaging conversation described with reference to Method 700. For brevity, those details will not be repeated here.

[0221] The operations of the information processing method described above are optionally performed by activating one or more functional modules within the information processing device, such as a general-purpose processor (for example, as described above in relation to Figures 1A-1B, 3, 5A-5J) or an application-specific chip. Furthermore, the operations described above with reference to Figures 9A-9C are optionally performed by the components shown in Figures 1A-1B. For example, the display operation 902a, the reception operation 902a, and the start operation 902c are optionally performed by the event sorting unit 170, the event recognition unit 180, and the event processing unit 190. When an individual default event or sub-event is detected, the event recognition unit 180 activates the event processing unit 190 associated with the detection of that event or sub-event. The event processing unit 190 optionally uses or calls the data update unit 176 or the object update unit 177 to update the application internal state 192. In some embodiments, the event processing unit 190 accesses an individual GUI update unit 178 to update what is displayed by the application. Similarly, it will be obvious to those skilled in the art how other processes can be carried out based on the components shown in Figures 1A and 1B.

[0222] As stated above, one aspect of this technology is the capture and display of content and location information. This disclosure intends that in some cases the data used may include personal data that uniquely identifies a particular person, or personal data that can be used to contact a particular person or to locate them. Such personal data may include demographic data, content consumption activity, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a user's health or fitness level (e.g., vital signs measurements, medication information, exercise information), birth dates, or any other identifying or personal information.

[0223] This disclosure acknowledges that such use of personal data in this technology may be for the benefit of the user. For example, by capturing and transmitting content, the user can view the content later. Thus, by using such personal data, the user can view the content using an electronic device. Furthermore, other uses of personal data that may benefit the user are also conceivable in this disclosure. For example, location data may be used to enhance communication between devices.

[0224] This disclosure implies that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal data should adhere to a robust privacy policy and / or privacy practices. Specifically, such entities should implement and consistently use a privacy policy and practices that are generally recognized as meeting or exceeding industry or government requirements for the strict confidentiality of personal data. Such policies should be readily accessible to users and should be updated as data collection and / or use changes. Personal data from users should be collected for the lawful and legitimate use of the entity and should not be shared or sold for any other purpose. Furthermore, such collection / sharing should be carried out only after informing and obtaining the user's consent. In addition, such entities should consider taking all necessary steps to protect and secure access to such personal data and to ensure that others with access to the personal data faithfully adhere to those privacy policies and procedures. Furthermore, such entities may undergo third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal data collected and / or accessed, and to applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, the collection or access to certain health data may be subject to federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA). Health data in other countries, on the other hand, may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained in each country with respect to different types of personal data.

[0225] Notwithstanding the foregoing, the Disclosure also envisions embodiments that allow a user to selectively prevent the use of or access to personal data. That is, the Disclosure envisions that hardware and / or software elements may be provided to prevent or prevent access to such personal data. For example, in the case of a location service, the Technology may be configured to allow a user to choose to “opt in” or “opt out” of participating in the collection of personal data during or at any time thereafter when registering for the service. In another example, a user may choose not to enable the location service in a particular application (e.g., a first application and / or a second application). In addition to providing “opt-in” and “opt-out” options, the Disclosure envisions providing notices regarding access to or use of personal data. For example, a user should be notified when the collection of personal data content begins, and then notified again immediately before the personal data is accessed by a device(s).

[0226] Furthermore, the intent of this disclosure is that personal data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data when it is no longer needed. In addition, where applicable in certain health-related applications, data anonymization can be used to protect user privacy. Anonymization can be facilitated, where appropriate, by removing certain identifiers (e.g., birth dates), controlling the amount or specificity of data stored (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across all users), and / or by other means.

[0227] Therefore, while this disclosure broadly covers the use of personal data to implement one or more different disclosed embodiments, it is also conceivable that these different embodiments could be implemented without requiring access to such personal data. In other words, the different embodiments of the technology would not be rendered inoperable by the absence of all or part of such personal data. For example, an electronic device transmits communications without associating content with location data.

[0228] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0229] The above is written with reference to specific embodiments for illustrative purposes. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the exact form disclosed. Many modifications and variations are possible in light of the above teachings. These embodiments have been selected and described in order to best illustrate the principles of the invention and its practical applications, thereby enabling other persons skilled in the art to best use the invention and the various described embodiments with various modifications suitable for specific applications that may be conceived.

Claims

1. It is a method, In an electronic device that communicates with a display generation component and one or more input devices, While a first user of the electronic device is part of a first group messaging conversation involving multiple users, and is viewing a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component, the first user receives an indication via one or more input devices to add a second user to the first group messaging conversation. Upon receiving the indication to add the second user to the first group messaging conversation, In accordance with the determination that the plurality of users added to the first group messaging conversation and the second user are not part of the same messaging service, a second group messaging conversation, distinct from the first group messaging conversation, is initiated via the messaging application without adding the second user to the first group messaging conversation, wherein the second group messaging conversation includes the plurality of users of the first group messaging conversation and the second user, and the process of generating the second group messaging conversation is initiated. Methods that include...

2. Upon receiving the indication to add the second user to the first group messaging conversation, In accordance with the determination that the multiple users added to the first group messaging conversion and the second user are part of the same messaging service, the second user is added to the first group messaging conversation. The method according to claim 1, further comprising:

3. The process for generating the second group messaging conversation is: The method according to any one of claims 1 to 2, comprising: displaying a messaging preference user interface via the display generation component for indicating whether the identification information of the first group messaging conversation should be applied to the second group messaging conversation; receiving an indication via one or more input devices while the messaging preference user interface is displayed to apply the identification information of the first group messaging conversation to the second group messaging conversation; and associating the identification information with the second group messaging conversation in response to receiving the indication to apply the identification information of the first group messaging conversation to the second group messaging conversation.

4. While the messaging preference user interface is displayed, an indication is received via one or more input devices that the identification information of the first group messaging conversation will not be applied to the second group messaging conversation. Upon receiving an indication that does not apply the identification information of the first group messaging conversation to the second group messaging conversation, the display generation component displays a prompt to provide identification information to associate with the second group messaging conversation. The method according to claim 3, further comprising:

5. Upon receiving the indication to apply the identification information of the first group messaging conversation to the second group messaging conversation, the identification information is to be unassociated from the first group messaging conversation. The method according to any one of claims 3 to 4, further comprising:

6. The method according to any one of claims 1 to 5, wherein the process for generating the second group messaging conversation includes identifying the user in the second group messaging conversation using the second electronic messaging identifier, based on the determination that the user among the plurality of users is identified in the first group messaging conversation using the first electronic messaging identifier used for messaging using the first messaging service, and using the second electronic messaging identifier, which is different from the first messaging identifier, used for messaging using a second messaging service different from the first messaging service, the second electronic messaging identifier is determined from contact information associated with the user.

7. The method according to any one of claims 1 to 6, wherein the process for generating the second group messaging conversation includes, upon determination that a user among the plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier used for messaging using a first messaging service, and that contact information associated with the user includes a plurality of electronic messaging identifiers used for messaging using a second messaging service different from the first messaging service, the display generation component displays a separate user interface associated with the messaging application in which the second group messaging conversation takes place, the separate user interface includes a plurality of representations of the plurality of users and the second user that are part of the second group messaging conversation, and the representation of the user among the plurality of users whose contact information includes the plurality of electronic messaging identifiers is visually distinguishable from the other plurality of representations of the plurality of users and the second user.

8. While the individual user interface is being displayed, input is received via one or more input devices, corresponding to the selection of the representation of the user among the multiple users, which includes the multiple electronic messaging identifiers, In response to receiving the aforementioned input, the display generation component displays, via the display generation component, a plurality of selectable options corresponding to the plurality of electronic messaging identifiers that can be selected to identify the user having the corresponding electronic messaging identifier, The method according to claim 7, further comprising:

9. The method according to any one of claims 1 to 8, wherein the process for generating the second group messaging conversation includes, upon determination that a user among the plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier used for messaging using a first messaging service, and that the contact information associated with the user does not include a second electronic messaging identifier used for messaging using a second messaging service different from the first messaging service, the display generation component displays a separate user interface associated with the messaging application in which the second group messaging conversation takes place, the user interface includes a content entry field configured to receive input for inputting a third electronic messaging identifier used for messaging using the second messaging service to associate with the user in the second group messaging conversation.

10. The method according to any one of claims 1 to 9, wherein the process for generating the second group messaging conversation includes, upon determination that a user among the plurality of users is identified in the first group messaging conversation using a first electronic messaging identifier and that the contact information associated with the user does not include a second electronic messaging identifier used for messaging using a second messaging service different from the first messaging service, the display generation component displays a separate user interface associated with the messaging application in which the second group messaging conversation takes place, the separate user interface includes a selectable option for removing the user from the second group messaging conversation.

11. The method according to any one of claims 1 to 10, wherein the first group messaging conversation is maintained by the messaging application after the second group messaging conversation has been generated.

12. Receiving the indication to add the second user to the first group messaging conversation means Receiving a first input via one or more input devices for displaying one or more details associated with the first group messaging conversation, In response to receiving the first input for displaying one or more details associated with the first group messaging conversation, the display generation component shall display a details user interface for the first group messaging conversation, wherein the details user interface includes information associated with the first group messaging conversation that is not displayed in the user interface associated with the messaging application in which the first group messaging conversation takes place. The method according to any one of claims 1 to 11, comprising: while displaying the detailed user interface, receiving a second input via one or more input devices for adding the second user to the first group messaging conversation.

13. An electronic device that communicates with a display generation component and one or more input devices, wherein the electronic device is One or more processors, Memory and One or more programs, The system comprises, and the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs are While a first user of the electronic device is part of a first group messaging conversation involving multiple users, and is viewing a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component, the first user receives an indication via one or more input devices to add a second user to the first group messaging conversation. Upon receiving the indication to add the second user to the first group messaging conversation, An electronic device comprising an instruction to initiate a process of generating a second group messaging conversation, which is different from the first group messaging conversation, via the messaging application, without adding the second user to the first group messaging conversation, in accordance with the determination that the plurality of users added to the first group messaging conversation and the second user are not part of the same messaging service, wherein the second group messaging conversation includes the plurality of users of the first group messaging conversation and the second user.

14. A non-temporary computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by one or more processors of an electronic device, the electronic device... While a first user of the electronic device is part of a first group messaging conversation involving multiple users, and is viewing a user interface associated with a messaging application in which the first group messaging conversation takes place via a display generation component, the first user receives an indication via one or more input devices to add a second user to the first group messaging conversation. Upon receiving the indication to add the second user to the first group messaging conversation, A non-temporary computer-readable storage medium that causes a method to perform a second group messaging conversation, which is different from the first group messaging conversation, conducted via the messaging application without adding the second user to the first group messaging conversation, in accordance with the determination that the plurality of users and the second user to be added to the first group messaging conversation are not part of the same messaging service, wherein the second group messaging conversation includes the plurality of users and the second user of the first group messaging conversation.

15. It is an electronic device, One or more processors, Memory and Means for receiving an indication to add a second user to the first group messaging conversation via one or more input devices, while the first user of the electronic device is part of a first group messaging conversation including multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via a display generation component, Upon receiving the indication to add the second user to the first group messaging conversation, A means for initiating a process to generate a second group messaging conversation, which is different from the first group messaging conversation, conducted via the messaging application without adding the second user to the first group messaging conversation, in accordance with the determination that the plurality of users added to the first group messaging conversation and the second user are not part of the same messaging service, wherein the second group messaging conversation includes the plurality of users of the first group messaging conversation and the second user, An electronic device equipped with the following features.

16. An information processing device for use in an electronic device, wherein the information processing device is Means for receiving an indication to add a second user to the first group messaging conversation via one or more input devices, while the first user of the electronic device is part of a first group messaging conversation including multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via a display generation component, Upon receiving the indication to add the second user to the first group messaging conversation, A means for initiating a process to generate a second group messaging conversation, which is different from the first group messaging conversation, conducted via the messaging application without adding the second user to the first group messaging conversation, in accordance with the determination that the plurality of users added to the first group messaging conversation and the second user are not part of the same messaging service, wherein the second group messaging conversation includes the plurality of users of the first group messaging conversation and the second user, An information processing device equipped with the following features.

17. It is an electronic device, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 1 to 12.

18. A non-temporary computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by one or more processors of an electronic device, the instructions cause the electronic device to perform the method according to any one of claims 1 to 12.

19. It is an electronic device, One or more processors, Memory and An electronic device comprising means for carrying out the method according to any one of claims 1 to 12.

20. An information processing device for use in an electronic device, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 1 to 12.

21. It is a method, In an electronic device that communicates with a display generation component and one or more input devices, The user of the electronic device receives an indication via one or more input devices to remove the user of the electronic device from the first group messaging conversation while the user of the electronic device is part of a first group messaging conversation involving multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component. Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, In accordance with the determination that the first group messaging conversation includes one or more users from among the multiple users who are not part of the same messaging service, the messaging application initiates a process to delete the first group messaging conversation. Methods that include...

22. The method according to claim 21, wherein deleting the first group messaging conversation comprises moving the first group messaging conversation from the active message set of the messaging application to the deleted message set of the messaging application, the deleted message set of the messaging application comprising one or more deleted messaging conversations.

23. The aforementioned method, While the first group messaging conversation is included in the deleted message set of the messaging application, The method according to claim 22, further comprising adding the new messaging activity to the first group messaging conversation in accordance with the determination that the first group messaging conversation has received new messaging activity.

24. While the first group messaging conversation is included in the deleted message set of the messaging application, Messaging activity received before the first group messaging conversation is moved to the deleted message set is maintained in the first group messaging conversation for a predetermined amount of time after the time the first group messaging conversation is moved to the deleted message set. Messaging activity received before the first group messaging conversation is moved to the deleted message set is deleted from the first group messaging conversation in the electronic device after a predetermined amount of time after the time the first group messaging conversation was moved to the deleted message set. Message activity received after the first group messaging conversation has been moved to the deleted message set is maintained in the first group messaging conversation on the electronic device for a second predetermined amount of time prior to the current time. The method according to any one of claims 22 to 23, wherein messaging activity received after the first group messaging conversation has been moved to the deleted message set is deleted from the first group messaging conversation in the electronic device after a second predetermined amount of time prior to the current time.

25. The aforementioned method, After the first group messaging conversation is included in the deleted message set of the messaging application, messaging activity associated with the first group messaging conversation is received via one or more input devices, The method according to any one of claims 22 to 24, further comprising: receiving the messaging activity associated with the first group messaging conversation and determining that the first group messaging conversation does not contain any prior messaging activity, and adding the messaging activity to the conversation in the active message set of the messaging application via the display generation component.

26. The method according to any one of claims 22 to 25, further comprising, while the first group messaging conversation is included in the deleted message set of the messaging application, displaying a user interface via the display generation component that includes a representation of the first group messaging conversation that includes a visual indication of the number of unread messages received in the first group messaging conversation while the first group messaging conversation is included in the deleted message set of the messaging application, one or more representations of one or more deleted conversations.

27. The method according to any one of claims 21 to 26, further comprising displaying a user interface via the display generation component that includes one or more representations of one or more deleted conversations while the group messaging conversation is in the deleted message set of the messaging application, wherein the user interface includes selectable options for moving the first group messaging conversation from the deleted message set to the active message set.

28. Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, and in accordance with the determination that the multiple users are part of the same messaging service, remove the user of the electronic device from the first group messaging conversation without initiating the process for deleting the first group messaging conversation. The method according to any one of claims 21 to 27, further comprising:

29. An electronic device that communicates with a display generation component and one or more input devices, wherein the electronic device is One or more processors, Memory and One or more programs, The system comprises, and the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs are While the user of the electronic device is part of a first group messaging conversation involving multiple users, and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component, the user of the electronic device receives an indication via one or more input devices to remove the user from the first group messaging conversation. Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, An electronic device including a command to initiate a process in the messaging application to delete the first group messaging conversation, based on a determination that the first group messaging conversation includes one or more users from the plurality of users who are not part of the same messaging service.

30. A non-temporary computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by one or more processors of an electronic device, the electronic device... The user of the electronic device receives an indication via one or more input devices to remove the user of the electronic device from the first group messaging conversation while the user of the electronic device is part of a first group messaging conversation involving multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component. Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, A non-temporary computer-readable storage medium that causes the messaging application to perform a method including: initiating a process for deleting the first group messaging conversation in accordance with a determination that the first group messaging conversation includes one or more users of the plurality of users who are not part of the same messaging service.

31. An information processing device for use in an electronic device, wherein the information processing device is Means for receiving an indication via one or more input devices to remove the user of the electronic device from a first group messaging conversation while the user of the electronic device is part of a first group messaging conversation including multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component, Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, Means for initiating a process in the messaging application to delete the first group messaging conversation in accordance with the determination that the first group messaging conversation includes one or more users from among the multiple users who are not part of the same messaging service, An information processing device equipped with the following features.

32. It is an electronic device, One or more processors, Memory and An electronic device comprising one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing the method according to any one of claims 21 to 28.

33. A non-temporary computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when executed by one or more processors of an electronic device, the instructions cause the electronic device to perform the method according to any one of claims 21 to 28.

34. An information processing device for use in an electronic device, wherein the information processing device is An information processing apparatus comprising means for performing the method described in any one of claims 21 to 28.

35. It is an electronic device, One or more processors, Memory and Means for receiving an indication via one or more input devices to remove the user of the electronic device from a first group messaging conversation while the user of the electronic device is part of a first group messaging conversation including multiple users and is displaying a user interface associated with a messaging application in which the first group messaging conversation takes place via the display generation component, Upon receiving the indication to remove the user of the electronic device from the first group messaging conversation, Means for initiating a process in the messaging application to delete the first group messaging conversation in accordance with the determination that the first group messaging conversation includes one or more users from among the multiple users who are not part of the same messaging service, An electronic device equipped with the following features.

36. It is an electronic device, One or more processors, Memory and Means for carrying out the method described in any one of claims 21 to 28, An electronic device equipped with the following features.

Images