Methods and user interface for sharing audio

Abstract

This disclosure relates to a method and user interface for sharing audio. When an electronic device is connected to a first external device, a first user interface including a first power indicator is displayed. Input selecting the first power indicator is detected. In response to detecting the input corresponding to the selection of the first power indicator, a process for simultaneously providing audio data to the first external device and a second external device other than the first external device is initiated. After initiating the process for simultaneously providing audio data to the first and second external devices, an indication that the physical proximity between the electronic device and the second external device meets a proximity condition is detected. In response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition, a second user interface indicating that the physical proximity between the electronic device and the second external device meets the proximity condition is displayed.

Description

[0001] This application is a divisional application of patent application No. 202080039642.6, filed on March 31, 2020, entitled "Method and User Interface for Sharing Audio".

[0002] Cross-references to related applications

[0003] This application claims priority to the following patent applications: U.S. Provisional Patent Application Serial No. 62 / 855,897, filed May 31, 2019, entitled “METHODS AND USER INTERFACES FOR SHARING AUDIO”; and Danish Patent Application No. PA 2019 70533, filed August 27, 2019, entitled “METHODS AND USER INTERFACES FOR SHARING AUDIO”, the contents of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0004] This disclosure relates generally to computer user interfaces, and more specifically, to techniques for sharing audio data. Background Technology

[0005] Electronic devices can play various types of media, including audio such as music tracks, podcasts, audiobooks, and videos. Modern electronic devices can deliver audio data via wireless connections to audio output devices such as wireless speakers and wireless headphones. Summary of the Invention

[0006] However, some technologies used to share audio data using electronic devices are often cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple keystrokes or button presses. These technologies require more time than necessary, resulting in wasted user time and device power. This latter consideration is particularly important in battery-powered devices.

[0007] Therefore, this technology provides electronic devices with faster and more efficient methods and interfaces for sharing audio data. Such methods and interfaces can optionally supplement or replace other methods for sharing audio data. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-machine interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging sessions.

[0008] This document discloses an example method. An example method includes: at an electronic device having a display device: displaying a first user interface including a first power indication when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; detecting an input corresponding to a selection of the first power indication; in response to detecting the input corresponding to the selection of the first power indication, initiating a process for simultaneously providing audio data to the first external device and a second external device different from the first external device; after initiating the process for simultaneously providing audio data to the first external device and the second external device, detecting an indication that the physical proximity between the electronic device and the second external device satisfies a proximity condition; and in response to detecting the indication that the physical proximity between the electronic device and the second external device satisfies the proximity condition, displaying a second user interface indicating that the physical proximity between the electronic device and the second external device satisfies the proximity condition.

[0009] This document describes an example non-transitory computer-readable storage medium. An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: displaying a first user interface including a first power indication via the display device when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; detecting an input corresponding to a selection of the first power indication; in response to detecting the input corresponding to a selection of the first power indication, initiating a process for simultaneously providing audio data to the first external device and a second external device different from the first external device; after initiating the process for simultaneously providing audio data to the first external device and the second external device, detecting an indication that the physical proximity between the electronic device and the second external device satisfies a proximity condition; and in response to detecting the indication that the physical proximity between the electronic device and the second external device satisfies the proximity condition, displaying a second user interface indicating that the physical proximity between the electronic device and the second external device satisfies the proximity condition.

[0010] This document describes an example transient computer-readable storage medium. An example transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: displaying a first user interface including a first power indication via the display device when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; detecting an input corresponding to a selection of the first power indication; in response to detecting the input corresponding to a selection of the first power indication, initiating a process for simultaneously providing audio data to the first external device and a second external device different from the first external device; after initiating the process for simultaneously providing audio data to the first external device and the second external device, detecting an indication that the physical proximity between the electronic device and the second external device satisfies a proximity condition; and in response to detecting the indication that the physical proximity between the electronic device and the second external device satisfies the proximity condition, displaying a second user interface indicating that the physical proximity between the electronic device and the second external device satisfies the proximity condition.

[0011] This document describes an example electronic device. An example electronic device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: displaying a first user interface including a first power indication via the display device when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; detecting an input corresponding to a selection of the first power indication; in response to detecting the input corresponding to a selection of the first power indication, initiating a process for simultaneously providing audio data to the first external device and a second external device other than the first external device; after initiating the process for simultaneously providing audio data to the first external device and the second external device, detecting an indication that the physical proximity between the electronic device and the second external device meets a proximity condition; and in response to detecting the indication that the physical proximity between the electronic device and the second external device meets a proximity condition, displaying a second user interface indicating that the physical proximity between the electronic device and the second external device meets a proximity condition.

[0012] An example electronic device includes a display device; means for displaying a first user interface including a first power indication when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; means for detecting an input corresponding to a selection of the first power indication; means for initiating a process for simultaneously providing audio data to the first external device and a second external device other than the first external device in response to detecting the input corresponding to the selection of the first power indication; means for detecting an indication that the physical proximity between the electronic device and the second external device meets a proximity condition after initiating the process for simultaneously providing audio data to the first external device and the second external device; and means for displaying a second user interface indicating that the physical proximity between the electronic device and the second external device meets a proximity condition in response to detecting the indication that the physical proximity between the electronic device and the second external device meets a proximity condition.

[0013] An example method includes: at an electronic device having a display device: detecting an indication that the physical proximity between the electronic device and a second external device different from the first external device meets a proximity condition when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; in response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition, displaying a first user interface including a first power indicator via the display device; detecting an input corresponding to a selection of the first power indicator; and in response to detecting the input corresponding to the selection of the first power indicator, initiating a process for simultaneously providing audio data to the first external device and the second external device.

[0014] An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: detecting an indication that the physical proximity between the electronic device and a second external device different from the first external device meets a proximity condition when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; displaying a first user interface including a first power indicator via the display device in response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition; detecting an input corresponding to a selection of the first power indicator; and initiating a process for simultaneously providing audio data to the first external device and the second external device in response to detecting the input corresponding to a selection of the first power indicator.

[0015] An example transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: detecting an indication that the physical proximity between the electronic device and a second external device different from the first external device meets a proximity condition when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; displaying a first user interface including a first power indicator via the display device in response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition; detecting an input corresponding to a selection of the first power indicator; and initiating a process for simultaneously providing audio data to the first external device and the second external device in response to detecting the input corresponding to a selection of the first power indicator.

[0016] An example electronic device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: detecting an indication that the physical proximity between the electronic device and a second external device different from the first external device meets a proximity condition when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; displaying a first user interface including a first power indicator via the display device in response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition; detecting an input corresponding to a selection of the first power indicator; and initiating a process for simultaneously providing audio data to the first external device and the second external device in response to detecting the input corresponding to the selection of the first power indicator.

[0017] An example electronic device includes a display device; means for detecting an indication that the physical proximity between the electronic device and a second external device different from the first external device meets a proximity condition when the electronic device is connected to a first external device via a communication link, wherein the electronic device is configured to provide audio data to the first external device via the communication link; means for displaying a first user interface including a first power indicator via the display device in response to detecting the indication that the physical proximity between the electronic device and the second external device meets the proximity condition; means for detecting an input corresponding to a selection of the first power indicator; and means for initiating a process for simultaneously providing audio data to the first external device and the second external device in response to detecting the input corresponding to a selection of the first power indicator.

[0018] An example method includes: at an electronic device having a display device: receiving a request to display a first volume control indication when a first connection condition is met relative to the electronic device, a first external device, and a second external device, wherein the electronic device is configured to provide audio data to the first external device when connected and is configured to provide audio data to the second external device when connected; displaying the first volume control indication in response to receiving the request to display the first volume control indication; detecting an input corresponding to a selection of the first volume control indication; and displaying a user interface in response to detecting the input corresponding to a selection of the first volume control indication, including: displaying a second volume control indication and a third volume control indication, the second volume control indication adjusting the volume level of the first external device when selected, and the third volume control indication adjusting the volume level of the second external device when selected, based on determining that a second connection condition is met relative to the second external device; and displaying a fourth volume control indication adjusting the volume level of the first external device when selected, without displaying a volume control indication for adjusting the volume level of the second external device, based on determining that a second connection condition is not met relative to the second external device.

[0019] An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: receiving a request to display a first volume control indication when a first connection condition is satisfied relative to the electronic device, a first external device, and a second external device, wherein the electronic device is configured to provide audio data to the first external device when connected and is configured to provide audio data to the second external device when connected; displaying the first volume control indication in response to receiving the request to display the first volume control indication; and detecting a corresponding action on the first volume control indication. The input for selecting the volume control indicator; and in response to detecting an input corresponding to the selection of the first volume control indicator, displaying a user interface, including: displaying a second volume control indicator and a third volume control indicator based on determining that a second connection condition is met relative to the second external device, the second volume control indicator adjusting the volume level of the first external device when selected, the third volume control indicator adjusting the volume level of the second external device when selected; and displaying a fourth volume control indicator adjusting the volume level of the first external device when selected, based on determining that the second connection condition is not met relative to the second external device, without displaying the volume control indicator for adjusting the volume level of the second external device.

[0020] An example transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: receiving a request to display a first volume control indication when a first connection condition is satisfied relative to the electronic device, a first external device, and a second external device, wherein the electronic device is configured to provide audio data to the first external device when connected and is configured to provide audio data to the second external device when connected; displaying the first volume control indication in response to receiving the request to display the first volume control indication; and detecting a corresponding action on the first volume control indication. The input for selecting the volume control indicator; and in response to detecting an input corresponding to the selection of the first volume control indicator, displaying a user interface, including: displaying a second volume control indicator and a third volume control indicator based on determining that a second connection condition is met relative to the second external device, the second volume control indicator adjusting the volume level of the first external device when selected, the third volume control indicator adjusting the volume level of the second external device when selected; and displaying a fourth volume control indicator adjusting the volume level of the first external device when selected, based on determining that the second connection condition is not met relative to the second external device, without displaying the volume control indicator for adjusting the volume level of the second external device.

[0021] An example electronic device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request to display a first volume control indication when a first connection condition is satisfied relative to the electronic device, a first external device, and a second external device, wherein the electronic device is configured to provide audio data to the first external device when connected and is configured to provide audio data to the second external device when connected; displaying a first volume control indication in response to receiving the request to display the first volume control indication; and detecting a corresponding action on the first volume control. The input for selecting a volume control indicator; and in response to detecting an input corresponding to the selection of a first volume control indicator, displaying a user interface, including: displaying a second volume control indicator and a third volume control indicator based on determining that a second connection condition is met relative to the second external device, wherein the second volume control indicator adjusts the volume level of the first external device when selected, and the third volume control indicator adjusts the volume level of the second external device when selected; and displaying a fourth volume control indicator that adjusts the volume level of the first external device when selected, without displaying a volume control indicator for adjusting the volume level of the second external device, based on determining that the second connection condition is not met relative to the second external device.

[0022] An example electronic device includes a display device; means for receiving a request to display a first volume control indication when a first connection condition is met relative to the electronic device, a first external device, and a second external device, wherein the electronic device is configured to provide audio data to the first external device when connected and to provide audio data to the second external device when connected; means for displaying the first volume control indication in response to receiving the request to display the first volume control indication; means for detecting an input corresponding to a selection of the first volume control indication; and means for responding to detecting an input corresponding to a selection of the first volume control indication. An apparatus for displaying a user interface for selecting input, the user interface comprising: displaying a second volume control indication and a third volume control indication, based on determining that a second connection condition is met with respect to a second external device, wherein the second volume control indication adjusts the volume level of a first external device when selected, and the third volume control indication adjusts the volume level of a second external device when selected; and displaying a fourth volume control indication that adjusts the volume level of the first external device when selected, based on determining that the second connection condition is not met with respect to the second external device, without displaying the volume control indication for adjusting the volume level of the second external device.

[0023] An example method includes: at an electronic device having a display device: while displaying a first user interface including controls for an audio media application, receiving a request to display a user interface for selecting which device will output audio from the audio media application; in response to receiving the request to display a user interface for selecting which device will output audio from the audio media application, displaying a second user interface, the second user interface including: based on determining that the source electronic device is connected to a first external device and a second external device different from the first external device and is configured to simultaneously provide audio data from the audio media application to the first external device and the second external device, the first power indication, when selected, causes audio data from the audio media application to be provided to both the first and second external devices simultaneously; and based on determining that the source electronic device is connected to the first external device and is configured to provide audio data from the audio media application to the first external device but not simultaneously to the other external device, displaying a second power indication, the second power indication, when selected, causes audio data from the audio media application to be provided only to the first external device.

[0024] An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device. The one or more programs include instructions for performing the following operations: upon displaying a first user interface including controls for an audio media application, receiving a request to display a user interface for selecting which device will output audio from the audio media application; in response to receiving the request to display a user interface for selecting which device will output audio from the audio media application, displaying a second user interface, the second user interface including: upon determining that a source electronic device is connected to a first external device and a second external device different from the first external device and is configured to simultaneously provide audio data from the audio media application to both the first and second external devices, the first power indication, when selected, causes simultaneous provision of audio data from the audio media application to both the first and second external devices; and upon determining that a source electronic device is connected to the first external device and is configured to provide audio data from the audio media application to the first external device without simultaneously providing audio data from the audio media application to the other external device, the second power indication, when selected, causes only the first external device to provide audio data from the audio media application.

[0025] An example transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: upon displaying a first user interface including controls for an audio media application, receiving a request to display a user interface for selecting which one or more devices to output audio from the audio media application; in response to receiving the request to display a user interface for selecting which one or more devices to output audio from the audio media application, displaying a second user interface, the second user interface including: upon determining that a source electronic device is connected to a first external device and a second external device different from the first external device and is configured to simultaneously provide audio data from the audio media application to the first external device and the second external device, the first power indication, when selected, causes audio data from the audio media application to be simultaneously provided to the first external device and the second external device; and upon determining that a source electronic device is connected to the first external device and is configured to provide audio data from the audio media application to the first external device without simultaneously providing audio data from the audio media application to the other external device, the second power indication, when selected, causes audio data from the audio media application to be provided only to the first external device.

[0026] An example electronic device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: upon displaying a first user interface including controls for an audio media application, receiving a request to display a user interface for selecting which device will output audio from the audio media application; in response to receiving the request to display a user interface for selecting which device will output audio from the audio media application, displaying a second user interface, the display of the second user interface including: upon determining that a source electronic device is connected to a first external device and a second external device different from the first external device and is configured to simultaneously provide audio data from the audio media application to the first external device and the second external device, the first power indication, when selected, causes audio data from the audio media application to be simultaneously provided to the first external device and the second external device; and upon determining that a source electronic device is connected to the first external device and is configured to provide audio data from the audio media application to the first external device without simultaneously providing audio data from the audio media application to the other external device, the second power indication, when selected, causes audio data from the audio media application to be provided only to the first external device.

[0027] An example electronic device includes a display device; means for receiving, while displaying a first user interface including controls for an audio media application, a request to display a user interface for selecting which device will output audio from the audio media application; and means for displaying a second user interface in response to receiving the request to display a user interface for selecting which device will output audio from the audio media application, the means of displaying the second user interface including: displaying a first power indication based on determining that a source electronic device is connected to a first external device and a second external device different from the first external device, and is configured to simultaneously provide audio data from the audio media application to the first external device and the second external device, the first power indication, when selected, causing simultaneous provision of audio data from the audio media application to the first external device and the second external device; and displaying a second power indication based on determining that a source electronic device is connected to the first external device and is configured to provide audio data from the audio media application to the first external device without simultaneously providing audio data from the audio media application to the other external device, the second power indication, when selected, causing only the first external device to provide audio data from the audio media application.

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

[0029] Therefore, providing devices with faster and more efficient methods and interfaces for sharing audio data improves the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for sharing audio data. Attached Figure Description

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

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

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

[0033] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

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

[0035] Figure 4A An exemplary user interface for a menu on an application on a portable multifunction device, according to some implementation schemes, is shown.

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

[0037] Figure 5A A personal electronic device according to some implementation schemes is shown.

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

[0039] Figures 5C-5D Exemplary components of a personal electronic device having a touch-sensitive display and an intensity sensor according to some embodiments are shown.

[0040] Figures 5E-5H Exemplary components and user interfaces of a personal electronic device according to some implementation schemes are shown.

[0041] Figures 6A-6R An exemplary user interface according to some implementation schemes is shown.

[0042] Figure 7 Exemplary methods according to some implementation schemes are shown.

[0043] Figure 8 Exemplary methods according to some implementation schemes are shown.

[0044] Figures 9A-9E An exemplary user interface according to some implementation schemes is shown.

[0045] Figure 10 Exemplary methods according to some implementation schemes are shown.

[0046] Figures 11A-11F An exemplary user interface according to some implementation schemes is shown.

[0047] Figure 12 Exemplary methods according to some implementation schemes are shown. Detailed Implementation

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

[0049] Electronic devices are needed that provide efficient methods and interfaces for sharing audio data. In some embodiments, when a primary device is connected to a first wireless device (e.g., a pair of wireless headphones paired with the primary device), the primary device enters a sharing mode in response to the selection of a shared audio power indication. A process for sharing audio data between the primary device and the second external device while simultaneously providing the same audio data to the first external device is initiated in response to the close proximity of a second wireless device (e.g., a pair of wireless headphones belonging to another user). In some embodiments, the audio data is temporarily shared with the second external device. This allows a user to easily share audio wirelessly with another person, enabling them to listen to audio together, for example, without the need for a pre-existing or persistent relationship between the primary device and the second external device. In some embodiments, the sharing process is initiated by bringing the second external device close to the primary device without initial selection of a shared audio power indication. Exemplary techniques for controlling the volume of the first and second external devices while sharing audio data are also described. For example, the primary device may provide a volume control interface based on the configuration of the connection with the second external device (e.g., whether the second external device is being controlled by a third external device (e.g., a telephone)). Exemplary techniques for selecting a device for playing audio are also described. For example, audio media user interfaces offer options on where to play music based on whether the primary device is sharing audio (e.g., a power indicator). Such technologies can reduce the cognitive burden on users sharing audio data, thereby increasing productivity. Furthermore, these technologies can reduce processor and battery power wasted otherwise on redundant user input.

[0050] under, Figure 1A-Figure 1B , Figure 2 , Figure 3 , Figures 4A-4B as well as Figures 5A-5H A description of an exemplary device for performing a technique for sharing audio data is provided. Figures 6A-6R An exemplary user interface for sharing audio data is shown. Figures 7-8 This is a flowchart illustrating a method for sharing audio data according to some implementation schemes. Figures 6A-6R The user interface is used to illustrate the processes described below, including... Figures 7-8 The process in. Figures 9A-9E An exemplary user interface for sharing audio data is shown. Figure 10 This is a flowchart illustrating a method for sharing audio data according to some implementation schemes. Figures 9A-9E The user interface in the document is used to illustrate the process described below, including Figure 10 The process in. Figures 11A-11F An exemplary user interface for sharing audio data is shown. Figure 12This is a flowchart illustrating a method for sharing audio data according to some implementation schemes. Figures 11A-11F The user interface in the document is used to illustrate the process described below, including Figure 12 The process in.

[0051] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

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

[0053] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0054] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

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

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

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

[0058] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface 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.

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

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

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

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

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

[0064] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, 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)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE...). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

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

[0066] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to the other input control device 116. The other input control device 116 optionally includes physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, input controller 160 is optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., Figure 2 Optionally, 208) includes an increase / decrease button for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push-button (e.g., Figure 2 (206 in the middle).

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

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

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

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

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

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

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

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

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

[0076] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown 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 projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

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

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

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

[0080] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0081] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "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 view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of device 100.

[0082] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

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

[0084] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

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

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

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

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

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

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

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

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

[0093] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

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

[0095] • Telephone module 138;

[0096] • Video conferencing module 139;

[0097] • Email client module 140;

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

[0099] Fitness support module 142;

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

[0101] • Image management module 144;

[0102] • Video player module;

[0103] Music player module;

[0104] • Browser module 147;

[0105] • Calendar module 148;

[0106] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0107] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0108] • Search module 151;

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

[0110] • Notepad module 153;

[0111] • Map module 154; and / or

[0112] • Online video module 155.

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

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

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

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

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

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

[0119] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0120] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for: 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.

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

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

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

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

[0125] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

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

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

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

[0129] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0130] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

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

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

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

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

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

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

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

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

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

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

[0141] 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 the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events identified as correct input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch-based gesture.

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

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

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

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

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

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

[0148] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

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

[0150] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

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

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

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

[0154] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

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

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

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

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

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

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

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

[0162] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one mentioned above)) are described. Figure 1A The contact strength sensor 165 is described above. The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

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

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

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

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

[0167] • Time 404;

[0168] Bluetooth indicator 405;

[0169] • Battery status indicator 406;

[0170] • Tray tray 408 with icons for commonly used applications, such as:

[0171] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages;

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

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

[0174] ○ The icon 422 marked "iPod" for the video and music player module 152 (also known as the iPod module 152, a trademark of Apple Inc.); and

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

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

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

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

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

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

[0181] ○ The icon 434 in the Stock Market Desktop Mini Program 149-2 that is marked as "Stock Market";

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

[0183] ○ The icon 438 in the Weather desktop mini-program 149-1 that is marked as "Weather";

[0184] ○ The icon 440 in the alarm clock desktop mini-program 149-4 that is marked as "clock";

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

[0186] ○ The icon 444 labeled "Notepad" in Notepad module 153; and

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

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

[0189] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

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

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

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

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

[0194] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

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

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

[0197] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described below, including methods 700, 800, 1000, and 1200. Figures 7 to 8 , Figure 10 and Figure 12A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

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

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

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

[0201] Figure 5C This demonstrates the use of multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. Figure 5C It also includes an intensity graph, which shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some embodiments, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. Figure 5DThe diagram illustrates the allocation of cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i = 1 to the last) from the center of force. Reference operations can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5C-5D The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included within... Figures 5C-5D This is intended to assist readers.

[0202] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, the touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position is optionally based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally 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: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0203] Optionally, the contact intensity on a touch-sensitive surface is characterized relative 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 an intensity at which the device performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0204] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

[0205] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0206] Figures 5E-5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ”) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to application 2, the gesture performed by contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines the intensity of the contact 562 within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak value above 562. Contact is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold (e.g., "IT") during the gesture... D The above contact 562 displays the scale representation 578A-578C (e.g., thumbnails) of the document recently opened for application 2, such as... Figures 5F-5H As shown. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in... Figures 5E-5H This is intended to assist readers.

[0207] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F-5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the pressure threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E to 5H The aforementioned operations.

[0208] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., 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). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0209] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

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

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

[0212] • The currently active application displayed on the screen of the device that is using the application;

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

[0214] • A suspended or hibernating application that is not running but has state information stored in memory (both volatile and non-volatile) that can be used to resume application execution.

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

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

[0217] Figures 6A-6R Exemplary user interfaces for sharing audio data are shown according to some implementation schemes. The user interfaces in these figures are used to illustrate [the following]. Figures 7 to 8 The process described below is the process in the middle.

[0218] Figure 6A Electronic devices 600 and 625 (also referred to as "Taylor's earbuds") are shown. In some embodiments, device 600 is device 100, 300, or 500. Device 600 has a display device 602 depicted as a touch-sensitive display (e.g., touchscreen 504). Device 625 is configured to connect to device 600 and output audio (e.g., audible sound waves) based on audio data received from device 600 via communication link C1. Figure 6A In the embodiments shown, communication link C1 is a wireless (e.g., Bluetooth) connection. In some embodiments, communication link C1 is a wired connection. In some embodiments, device 625 includes one or more features of device 100, device 300, or device 500 (e.g., audio circuitry 110, speaker 111, microphone 113). In some embodiments, device 625 is a wireless speaker, or any device configured to connect to device 600 and output audio based on audio data received from device 600. Figure 6AAs shown, device 625 is a pair of wireless earbuds consisting of earbud 625a and earbud 625b. Figure 6A In the embodiments shown, although device 625 is a composite device comprising two physically separate earpieces, earpieces 625a and 625b operate together as a single device. In some embodiments, device 625 has a primary earpiece connected to device 600 and a secondary earpiece communicating with the primary earpiece and receiving audio signals from device 600 via a primary component. In some embodiments, earpieces 625a and 625b are each connected to device 600 but are treated by device 600 as a single external device.

[0219] exist Figure 6A In the device 600, a user interface 604 including an audio media user interface 604a is displayed. The audio media user interface 604a includes a current audio indicator 604a-1, which includes information about the audio application associated with the device 600, such as the device providing audio output (“Taylor’s earphones”), the track name (“Track 1”), and the artist name (“DJ Appleseed”). The audio media user interface 604a includes power indicators 604a-2, 604a-3, 604a-4, 604a-5, and 604a-6. Power indicators 604a-2, 604a-3, and 604a-5 correspond to respective audio devices and, when selected, provide audio to the selected device. Figure 6A In this context, the check mark on indicator 604a-3 indicates that device 625 (“Taylor’s Earphone”) is the currently selected audio device, consistent with the current audio indicator 604a-1. Volume indicator 604a-6 can be selected to adjust the volume level of the currently selected audio device.

[0220] The shared audio capability 604a-4 can be selected to initiate a process for sharing audio data with another device while simultaneously providing audio via a currently selected audio device (e.g., device 625). For example, shared audio allows device 600 to establish a temporary connection with another user's device, enabling both users to listen to the same audio simultaneously without establishing a persistent or permanent association with the other user's device (e.g., without pairing device 600 with other users' devices, as discussed in more detail below).

[0221] exist Figure 6A In this process, device 600 detects an input (e.g., a tap) 610a corresponding to a selection of shared audio enablement representations 604a-4. In response to the detection of input 610a, device 600 initiates a process for simultaneously providing audio data to device 625 and a second external device. Figure 6BIn the illustrated embodiment, the process includes displaying a user interface 606. The user interface 606 includes a user interface card 606a with instructions 606a-1 on how to share audio data with another device (e.g., another pair of wireless headphones or earbuds). Instructions 606a-1 explain that audio can be shared by bringing another pair of wireless headphones close to device 600. The user interface card 606a includes graphical elements 606a-2 that represent devices (or types of devices) with which device 600 can share audio data when the devices are close to device 600. Thus, when the devices are close to device 600, device 600 informs the user of potential devices or products with which audio data can be shared. In some embodiments, device 600 displays representations of more than one device with which device 600 can share audio data. Figure 6C In this context, device 600 displays graphic element 606a-3, which represents another graphic element that device 600 can share audio data with when it is close to device 600. Device 600 can display graphic elements (e.g., graphic elements 606a-2 and 606a-3) of potential devices in various ways (e.g., simultaneously or sequentially). Figure 6C As shown, device 600 replaces graphic element 606a-2 with graphic element 606a-3 on user interface 606.

[0222] As indicated by instruction 606a-1, device 600 may use the satisfaction of proximity conditions to share audio data with another device while simultaneously providing audio data (e.g., the same audio data) to device 625. The use of proximity between one device and another can serve as a clear indication that a user wants to perform an action (e.g., invoke an interface, share audio data) on one or both devices. For example, this can prevent wasted device resources by avoiding excessive user input for performing functions (e.g., navigating one or more menus on a device display). Furthermore, this can also save user time, for example, by reducing the amount of user input required to perform functions (e.g., invoke an interface on a display, share audio data).

[0223] Figure 6C An exemplary view is shown of a scenario including a device 650 (also referred to as "Chance's earpiece") located at a relatively long distance from device 600. Device 650 is configured to connect to device 600 and output audio (e.g., audible sound waves) based on audio data received from device 600. In some embodiments, device 650 includes one or more features of device 100, 300, 500, or 625 (e.g., audio circuitry 110, speaker 111, microphone 113). In some embodiments, device 650 is a wireless speaker, or any device configured to connect to device 600 and output audio based on audio data received from device 600. Figure 6C As shown, device 650 is a pair of wireless earbuds consisting of earbud 650a, earbud 650b, and housing 650c. In some embodiments, housing 650c engages with earbuds 650a and 650b to initiate a connection with device 600 (e.g., as referenced below). Figure 6E (as described above) and / or perform other operations associated with earbuds 650a and 650b (e.g., charging). Figure 6C In the illustrated embodiment, earplugs 650a, 650b, and housing 650c operate together as a single device and are regarded as a single device by device 600.

[0224] exist Figure 6C In the illustrated implementation, device 600 is associated with the same user (e.g., Taylor) as device 625 and is paired with device 625. In some implementations, two devices are paired if they have a persistent association with each other and are configured to exchange data via a communication link. For example, when the communication link C1 between the devices is currently inactive, device 625 remains associated with device 600 (e.g., if the connection is lost or device 600 and device 625 share common persistent configuration settings, device 600 will attempt to automatically reconnect to device 625). Figure 6C In this context, device 650 is not paired with device 600. As described below, device 600 may establish a temporary connection with device 650 to share audio data with another user (e.g., Chance) who is also provided with paired device 625 (e.g., Taylor's own earphones), but after the temporary connection ends, device 650 does not remain associated with device 600.

[0225] Figure 6CA proximity condition range indicator 605 is shown around device 600. The proximity condition range indicator is also referred to herein as a "proximity area indicator" or simply a "proximity area". Device 650 is not within the proximity condition range indicator 605. The proximity condition range indicator 605 is included as a visual aid and is intended to indicate the physical proximity at which a proximity condition will be satisfied. For example, the range indicator 605 may indicate the range of near-field communication detection circuitry of device 600. In some embodiments, any suitable technology may be used to detect proximity between devices. For example, in some examples, a broadband wireless connection is used. A broadband wireless connection is used, for example, to determine one or more of the following: the directionality, distance, and orientation of one or more devices. Therefore, the presence of a detectable device (e.g., partially or completely) within the proximity condition range indicator 605 will satisfy the proximity condition, but not if the detectable device is located outside the range indicator 605. Those skilled in the art will understand that the detection range of physical proximity may be non-uniform, susceptible to various variables (e.g., wireless interference, air humidity, etc.), and may include points in three-dimensional space, all of which are contemplated within the scope of this disclosure. Therefore, the graphical representation of the proximity condition range indicator 605 is not intended to limit the range for determining whether a proximity condition is met. Furthermore, the figures are not necessarily drawn to scale and are included herein only as visual aids. Therefore, unless otherwise stated, the dimensions and scale of the features depicted in the figures are not intended as limitations on the distances required to be in very close proximity or to meet the proximity condition. In some embodiments, in response to the detection of input 610a, device 600 is configured to detect a mode of device with which it can share audio data within the proximity condition range indicator 605.

[0226] Figure 6D An exemplary view is shown, including a scene where device 600 is located at a short distance from device 600. For example... Figure 6D As shown, devices 600 and 650 are close to each other, and device 650 is now at least partially within the proximity condition range indicator 605. Since the proximity condition range indicator 605 represents the physical proximity at which the proximity condition is satisfied, device 600 detects an indication that the physical proximity between devices 600 and 650 satisfies the proximity condition (e.g., and in response, initiates communication with device 650, such as to send the condition satisfaction indication). In some examples, device 650 detects the proximity condition satisfaction indication (e.g., and in response, initiates communication with device 600, such as to send the condition satisfaction indication).

[0227] In response to an indication that the physical proximity condition is met, device 600 displays a user interface 608 indicating that the physical proximity condition between device 600 and device 650 is met, such as... Figure 6D As shown. User interface 608 includes proximity user interface 608a, which identifies devices that meet proximity conditions with device 600 and provides a confirmation enablement indication 608a-3. When selected, this confirmation enablement indication continues the process of sharing audio data by initiating a connection (e.g., a communication link) with device 650 to provide audio data, while simultaneously providing audio data to device 625. Proximity user interface 608a uses a text indicator 608a-1 (“Chance’s Earbuds”) and a graphical element 608a-2 including a representative image of device 650 to identify device 650 as being within proximity condition range indicator 605. Graphical element 608a-2 indicates that device 650 is a pair of wireless earbuds (not, for example, as shown in the image). Figure 6C (A pair of wireless earphones depicted by graphic element 606a-3 in the image).

[0228] exist Figure 6D In this context, device 600 detects an input (e.g., a tap) 610b corresponding to a selection of the confirmation indication display 608a-3. In response to detecting input 610b, device 600 displays a user interface 612, such as... Figure 6E As shown. The user interface 612 includes a connection instruction user interface 612a, which includes a text indicator 612a-1 (e.g., 608a-1), a graphical element 612a-2, and instructions 612a-3 for continuing the process of connecting device 650 to device 600. Instructions 612a-3 instruct the user to press and hold button 650c-1 on device 650, and the graphical element 612a-2 includes a representative image of device 650 from a viewpoint where the representation of button 650c-1 is visible.

[0229] exist Figure 6E In this embodiment, device 650 detects input 610c, including pressing and holding button 650c-1. In some implementations, in response to detecting input 610c, device 650 sends a signal to device 600 indicating that device 650 can be connected to device 600. Upon receiving the signal from device 650 (e.g., in response to), device 600 displays user interface 614, such as... Figure 6FAs shown. User interface 614 indicates that device 600 is in the process of establishing a communication link C2 with device 650. User interface 614 includes a connection user interface 614a, which includes text indicators 614a-1 (e.g., 608a-1) and graphical elements 614a-2 (e.g., a representative image of device 650 viewed from a different perspective than graphical elements 608a-3 and 612a-3). In some embodiments, device 600 is connected to a second external device (e.g., device 650) and displays user interface 614 in response to the detection of input 610b (e.g., no input 610c is required on device 650 and user interface 612 is not displayed).

[0230] After (for example, in response to) establishing a communication link C2 with device 600, the device displays user interface 616, such as Figure 6G As shown. In Figure 6G In this embodiment, device 600 is simultaneously connected to devices 625 (via communication link C1) and 650 (via communication link C2) and provides them with audio data, such that devices 625 and 650 output the same audio. In some embodiments, device 600 is connected to a second external device (e.g., device 650) and displays user interface 616 in response to the detection of input 610b (e.g., no input 610c is required on device 650 and user interfaces 612 and 614 are not displayed).

[0231] User interface 616 includes an audio media user interface 616a (e.g., an updated version of audio media user interface 604a) that instructs device 600 to simultaneously provide audio data to devices 625 and 650. Audio media user interface 616a includes a current audio indicator 616a-1, which includes the track name (track 1) and artist name (DJ Appleseed). Unlike current audio indicator 604a-1, current audio indicator 616a-1 indicates positive input to both headphones, instead of... Figure 6AAudio is supplied only to device 625 (TAYLOR's earphones) as described above. The audio media user interface 616a includes power indicators 616a-2, 616a-3, 616a-4, 616a-5, and 616a-6. Check marks on power indicators 616a-3 and 616a-4 indicate that device 625 (“TAYLOR's earphones”) and device 650 are currently selected for audio output, consistent with the current audio indicator 616a-1. Power indicators 616a-3 and 616a-4 each include a volume slider that, when selected, controls a single volume level for the corresponding device (e.g., the volume slider on power indicator 616a-4 can be selected to adjust the volume level of device 650 without changing the volume level of device 625). The volume indicator 616a-2 can be selected to output audio data to a bedroom speaker associated with device 600 (e.g., and stop providing audio data to devices 625 and 650). The volume indicator 616a-6 can be selected to adjust the volume levels of devices 625 and 650 using a single input. In some embodiments, the volume levels of devices 625 and 650 are adjusted using the volume indicator 616a-6 to set the volume levels of devices 625 and 650 to the same volume level (e.g., even if devices 625 and 650 had different volume levels before the volume indicator 616a-6 was selected). In some embodiments, the volume levels of devices 625 and 650 are adjusted using the volume indicator 616a-6 to set the volume levels of devices 625 and 650 to the respective volume levels based on the initial volume level of the respective devices and an input on the volume indicator 616a-6 (e.g., the volume adjustment indicator 616a-7 moving from its initial position to a position).

[0232] exist Figure 6G In this embodiment, earbuds 650a and 650b of device 650 are depicted without housing 650c and located outside proximity condition range indicator 605. In some embodiments, earbuds 650a and 650b must be within housing 650c to establish communication link C2 (e.g., during input 610c) and can receive audio data from device 600 without housing 650c after communication link C2 is established. In some embodiments, device 650 does not include housing 650c and / or earbuds 650a and 650b do not need to be within housing 650c to establish communication link C2 with device 600.

[0233] As mentioned, in Figure 6G In this context, device 650 is located outside the proximity condition range indicator 605 while maintaining communication link C2 (e.g., device 650 does not need to remain within the proximity condition range indicator 605 to receive audio data). Figure 6H In some embodiments (e.g., after device 650 moves away from device 600 and moves outside the proximity condition range indicator 605), device 650 is positioned within the proximity condition range indicator 615 (e.g., device 650 moves back towards device 600). In some embodiments, the proximity condition range indicator 615 is the same as the proximity condition range indicator 605. In some embodiments, the proximity condition range indicator 615 is different from the proximity condition range indicator 605. The proximity condition range indicator 615 indicates the physical proximity at which the disconnect proximity condition is met. In some embodiments, the disconnect proximity condition is the same as the proximity condition described above for initiating the process of providing audio data to the second external device. In some embodiments, the disconnect proximity condition is the same as the proximity condition for initiating the process of providing audio data to the second external device.

[0234] Since the proximity condition range indicator 615 represents the physical proximity that satisfies the disconnect proximity condition, device 600 detects an indication that the physical proximity between device 600 and device 650 satisfies the disconnect proximity condition (e.g., and in response, initiates communication with device 650, for example, to send an indication that the disconnect condition is met). In some examples, device 650 detects an indication that the disconnect proximity condition is met (e.g., and in response, initiates communication with device 600, for example, to send an indication that the disconnect condition is met).

[0235] In response to an indication that physical proximity meets the disconnect proximity condition, device 600 displays a user interface 618 indicating that the physical proximity between device 600 and device 650 meets the disconnect proximity condition. The user interface 618 includes a disconnect user interface 618a that identifies a device (e.g., device 650) that meets the disconnect proximity condition with device 600, and provides a disconnect enable indication 618a-4 that, when selected, initiates a process to disconnect a device that is close to device 600 from device 600. The disconnect proximity user interface 618a uses a text indicator 618a-1 (“Chance’s Earplugs”) to identify device 650 as being within the proximity condition range indicator 615, and includes graphical elements 618a-2 and 618a-3. Graphical element 618a-2 indicates that device 600 is temporarily sharing audio with a device represented by graphical element 618a-3, which includes a representative image of device 650.

[0236] In some embodiments, if a device that meets the disconnect proximity condition with device 600 is not paired with device 600, device 600 displays a disconnect user interface 618a. In some embodiments, if device 600 determines that a device that meets the disconnect proximity condition with device 600 is paired with device 600, device 600 refrains from displaying the disconnect user interface 618a and optionally displays a different user interface. For example, in some embodiments where device 625 is paired with device 600, if device 625 meets the disconnect proximity condition with device 600, device 600 displays information about device 625 (e.g., the current state of device 625, such as battery level) without requiring the user to choose to disconnect device 625 from device 600 or stop providing audio data to device 625.

[0237] exist Figure 6H In this embodiment, device 600 detects an input (e.g., a tap) 610d corresponding to a selection of the disconnect enable indicator 618a-4. In response to detecting input 610d, device 600 stops providing audio data to device 650. In some implementations, in response to detecting input 610d, device 600 disconnects from device 650 (e.g., disconnects communication link C2) and displays user interface 620 (e.g., user interface 618 in the case of disconnecting user interface 618a), such as... Figure 6I As shown. In some embodiments, device 600 continues to provide audio data to device 625 after ceasing to provide audio data to device 650 and / or disconnecting from device 650.

[0238] exist Figure 6I In this process, after device 600 is disconnected from device 650, device 600 remains connected to device 625, and device 650 is positioned outside the proximity condition range indicator 635. Figure 6J In this configuration, device 650 is positioned within proximity condition range indicator 635 (e.g., device 650 moves backward toward device 600). In some embodiments, proximity condition range indicator 635 is the same as proximity condition range indicators 605 and / or 615. In some embodiments, proximity condition range indicator 635 is different from proximity condition range indicators 605 and / or 615. Proximity condition range indicator 635 indicates the physical proximity at which a second proximity condition is satisfied. In some embodiments, the second proximity condition is the same as the proximity condition described above for initiating the process of providing audio data to a second external device. In some embodiments, the second proximity condition is different from the proximity condition for initiating the process of providing audio data to a second external device.

[0239] Since the proximity condition range indicator 635 represents the physical proximity that satisfies the second proximity condition, device 600 detects an indication that the physical proximity between device 600 and device 650 satisfies the second proximity condition (e.g., and in response, initiates communication with device 650, for example, to send the indication that the second condition is satisfied). In some examples, device 650 detects an indication that the second proximity condition is satisfied (e.g., and in response, initiates communication with device 600, for example, to send the indication that the second condition is satisfied). In some embodiments, device 600 detects an indication that the physical proximity between device 600 and device 650 satisfies the second proximity condition without prior detection of the input corresponding to the selection of the shared audio capability representation 604a-1.

[0240] In response to an indication that physical proximity meets a second proximity condition, device 600 displays a user interface 622 indicating that physical proximity between device 600 and device 650 meets the second proximity condition. The user interface 622 includes a second proximity user interface 622a that identifies devices meeting the second proximity condition with device 600 and provides a shared audio capability indication 622a-4, which, when selected, initiates a connection establishment process with device 650 to simultaneously provide audio data to both device 625 and device 650. In some embodiments, device 600 need not have previously established a connection or communication link with device 650 to display the second proximity user interface 622a.

[0241] The second proximity user interface 622a uses a text indicator 622a-1 (“Chance’s Earbuds”), graphic elements 622a-2 and 622a-3 to identify device 650 as being within the proximity condition range indicator 635. Graphic element 622a-2 includes information (e.g., text) that device 600 can temporarily share audio with device 650. Graphic element 622a-3 includes a representative image of device 650. Furthermore, the second proximity user interface 622a includes a capability indication 622a-5 that connects (e.g., pairs) device 650 to device 600 when selected. In some implementations, instead of temporarily sharing audio by selecting shared power indicator 622a-4, connecting device 650 to device 600 by selecting power indicator 622a-5 disconnects the communication link C1 between device 625 and device 600, so that device 600 cannot provide audio data to both device 625 and device 650 at the same time (e.g., device 650 replaces device 625 as the primary headphone device).

[0242] exist Figure 6JIn this context, device 600 detects an input (e.g., a tap) 610e corresponding to a selection of the shared power display 622a-4. In response to the detection of input 610e, device 600 initiates a connection establishment process with device 650 to simultaneously provide audio data (e.g., including reference data) to both device 625 and device 650. Figures 6E-6F The process described.

[0243] In some implementations, after device 600 has established a communication link C2 with device 650, device 600 displays user interface 624, which includes a confirmation user interface 624a, such as... Figure 6K As shown. The confirmation user interface 624a indicates (e.g., via graphical elements 624a-1, 624a-2, and 624a-3) that device 600 is sharing (or configured to share) audio data with device 650, while simultaneously providing audio data to device 625. In some embodiments, the confirmation user interface 624a is displayed upon establishing a communication link between device 600 and device 650 in response to input 610b or input 610c, or after displaying the connection user interface 614a.

[0244] exist Figure 6K In this process, device 600 detects an input (e.g., a tap) 610f corresponding to a selection of the completion enable display 624a-4. In response to detecting input 610f, device 600 stops displaying the confirmation user interface 624a while maintaining communication links C1 and C2.

[0245] Now transferred to Figure 6L The diagram depicts a scenario where device 600 displays a user interface 604 (as described above) and is connected to device 625 (“Taylor’s earphone”) (e.g., via communication link C1). Device 650 (via communication link C3) is connected to device 675 (e.g., a phone associated with the same user as device 650). Device 675 is within proximity condition range indicator 635, and neither device 650 nor device 675 is connected to device 600. In some embodiments, with... Figure 6J When device 650 is within the proximity condition range indicator 635, device 600 does not display a proximity user interface (e.g., 622a) for sharing audio data with device 675. For example, depending on whether device 675 is determined to be a specific type of device (e.g., a telephone) or not a specific type of device (e.g., wireless headphones or wireless earbuds), device 600 waives the display of a proximity user interface that identifies device 675.

[0246] exist Figure 6LIn this process, device 600 detects an input (e.g., a tap) 610g corresponding to a selection of the shared audio enablement representation 604a-4. In response to the detection of input 610g, device 600 initiates a process for simultaneously providing audio data to device 625 and a second external device (e.g., referring to...). Figure 6A (The process described). In some embodiments, in response to detecting the selection of shared audio power representation 604a-4, device 600 enters a mode in which device 600 will share audio data with device 675 while simultaneously providing audio data to device 625 (e.g., device 600 applies a proximity condition in response to the selection of audio shared power representation 604a-4, which is different from the proximity condition applied before the selection of audio shared power representation 604a-4).

[0247] exist Figure 6M In this embodiment, device 675 is within proximity condition range indicator 605. In some implementations, proximity condition range indicator 635 is applied before selecting shared audio power representations 604a-4, and proximity condition range indicator 605 is applied after selecting shared audio power representations 604a-4 (e.g., for a predetermined amount of time). Since proximity condition range indicator 605 represents the physical proximity that satisfies the proximity condition, device 600 detects an indication that the physical proximity between device 600 and device 675 satisfies the proximity condition (e.g., and in response, initiates communication with device 675, e.g., to send an indication that the condition is satisfied). In some examples, device 675 detects an indication that the proximity condition is satisfied (e.g., and in response, initiates communication with device 600, e.g., to send an indication that the condition is satisfied).

[0248] In response to an indication that the physical proximity condition is met, device 600 displays a user interface 626 indicating that the physical proximity condition between device 600 and device 675 is met, such as... Figure 6MAs shown. User interface 626 includes proximity user interface 626a, which identifies a user (e.g., Chance) of a device (e.g., 675) that meets proximity conditions with device 600. Proximity user interface 626a particularly provides a confirmation enablement representation 626a-3, which, when selected, continues the process of sharing audio data by initiating a connection (e.g., a communication link) with device 675 to provide audio data, while simultaneously providing audio data to device 625. Proximity user interface 626a utilizes a text indicator 626a-1 to identify device 675 as being within proximity condition range indicator 605, and includes a graphical element 626a-2. The text indicator 626a-1 indicates the action performed by selecting the shared audio enablement representation 626a-3, and the graphical element provides information that device 600 can independently control the volume of device 625 while sharing audio data with device 675. In some embodiments, user interface 626a is displayed based on the determination that the proximity of device 675 to device 600 (e.g., rather than the proximity of device 650) meets a proximity condition. In some embodiments, in response to an indication that the physical proximity between device 600 and device 675 meets a proximity condition, device 600 displays a proximity user interface similar to proximity user interface 608a, except for information and graphical elements corresponding to device 675 instead of device 650.

[0249] exist Figure 6M In this context, device 600 detects an input (e.g., a tap) 610h corresponding to a selection of the shared power indicator 626a-3. In response to the detection of input 610h, device 600 initiates a communication link C4 with device 675 to simultaneously provide audio data to both device 625 and device 650 (via communication link C3 between device 675 and device 650), such as... Figure 6N As shown.

[0250] exist Figure 6N In the illustrated embodiment, device 600 displays user interface 628 while simultaneously providing audio data to devices 625 and 650 (via device 675). User interface 628 includes an audio media user interface 628a that indicates (via audio information 628a-1) that audio data is being provided to both headphones simultaneously. Audio media user interface 628a includes a power indicator 628a-2 that, when selected, displays user interface 630 including audio media user interface 630a (e.g., audio media user interface 616a), such as... Figure 6O As shown. The audio media user interface 630a includes a power indicator 630a-1, which, when selected (e.g., via input 610j), displays the audio application user interface 632a, such as... Figure 6PAs shown. The audio application user interface 632a specifically includes a track control 632a-1, an indicator 632a-2 that is simultaneously providing audio data to two headphones, and a volume control indicator 632a-3. Figure 6P In this process, device 600 detects an input (e.g., a tap) 610k corresponding to a selection of the volume control indicator 632a-3. In response to the detection of input 610k, device 600 displays a user interface 634, including an audio media user interface 634a, such as... Figure 6Q As shown. The audio media user interface 634a is the same as the audio media user interface 632a, except that the track control 632a-1 is replaced by individual volume control indications 634a-1 and 634a-2 corresponding to devices 625 and 650, respectively. The volume control indication 634a-2 corresponding to device 650 includes a disconnect indication 634a-3, which, when selected, causes device 600 to stop sharing audio data with device 650, for example, by disconnecting the communication link C4 between device 600 and device 675. In some embodiments, device 600 is directly connected to device 650 (e.g., via communication link C2, such as...). Figure 6G When (as shown), a user interface 634a including a disconnect power indicator 634a-3 is displayed, and the device 650 is disconnected in response to the selection of the disconnect power indicator 634a-3.

[0251] Go to Figure 6R Device 600 displays an exemplary user interface for stopping the sharing of audio data with a second external device while simultaneously providing audio data to device 625. Figure 6R In this configuration, device 600 (via device 675) is connected to devices 625 and 650. In some implementations, device 650 is directly connected to device 600. When device 600 is configured to provide audio data to both device 625 and device 650 simultaneously, device 600 displays a settings user interface 636 (e.g., a Bluetooth settings menu). The settings user interface 636 includes a graphical element 636-1 and a disconnect enable indicator 636-2. Graphical element 636-1 indicates that device 600 is sharing audio with device 650 (Chance's earbuds). The disconnect enable indicator 636-2, when selected, causes device 600 to stop sharing audio data with device 650, for example, by disconnecting the communication link C4 between device 600 and device 675. When device 600 is directly connected to device 650 (e.g., via communication link C2, such as...), device 600 is connected to device 625. Figure 6G In an embodiment where the user interface 636 is displayed (as shown), device 600 disconnects from device 650 in response to the selection of disconnection indication 636-2.

[0252] Figure 7This is a flowchart illustrating a method for sharing audio data using an electronic device according to some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, or 600) having a display device (e.g., 602). Some operations in method 700 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0253] As described below, method 700 provides an intuitive way to share audio data. This method reduces the cognitive burden on users when sharing audio data, thereby creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to share audio data more quickly and efficiently, saving power and increasing the time interval between battery charging.

[0254] When an electronic device (e.g., 600) connects to a first external device (e.g., 625; wireless headphones or wireless earbuds) via a communication link (e.g., C1; Bluetooth), the electronic device displays (702) a first user interface (e.g., 604) including a first power indication (e.g., 604-4), wherein the electronic device is configured to provide audio data to the first external device via the communication link. In some embodiments, the electronic device displays the first power indication simultaneously with an indication that the electronic device is connected to the first external device. In some embodiments, the electronic device displays the first power indication based on a determination that the electronic device is connected to the first external device, and optionally, the electronic device is running an audio media application or actively providing audio data to the first external device via the communication link. In some embodiments, the external device is a single physical device, such as a pair of headphones having two ear cups or earbuds physically connected via, for example, a wire or headband. In some embodiments, the external device is a composite device having multiple physically separate components or physical units that operate together as a single device. In some embodiments, the composite device has a primary component (e.g., an earpiece) connected to an electronic device and a secondary component that communicates with the primary component and receives audio signals from the electronic device via the primary component. In some embodiments, the composite device includes two components, each connected to an electronic device, but processed by the electronic device as a single external device.

[0255] In some embodiments, upon determining that a first external device is configured to receive audio data from an electronic device while the electronic device simultaneously provides audio data to a second external device, the electronic device displays a first user interface including the first capability indication. In some embodiments, upon determining that a first external device is not configured to receive audio data from an electronic device while the electronic device simultaneously provides audio data to a second external device, the electronic device displays a first user interface without the first capability indication.

[0256] In some embodiments, upon determining that the electronic device is running an audio media application (e.g., a music application, podcast application, audiobook application, multimedia application, web browser for playing audio and / or video), the electronic device displays a first user interface including a first power indication. In some embodiments, upon determining that the electronic device is not running an audio media application, the electronic device displays a first user interface without the first power indication.

[0257] Electronic device detection (704) corresponds to the input of the selection of the first power indication (e.g., 610a).

[0258] In response to detecting an input corresponding to a selection of a first power indication, the electronic device initiates (706) a process for simultaneously providing audio data to a first external device (e.g., 625) and a second external device different from the first external device (e.g., 650, 675; wireless headphones or wireless earbuds). In some embodiments, the electronic device displays a visual indication that the electronic device has initiated a process for simultaneously sharing audio data with the first and second external devices. In some embodiments, the process for sharing audio data includes displaying a user interface with instructions to bring another device close to the electronic device to temporarily share audio. The visual indication that the electronic device has initiated a process for simultaneously sharing audio data with the first and second external devices and the user interface with instructions to bring another device close to the electronic device to temporarily share audio provide the user with feedback that the electronic device is ready to share audio data and inform the user how to continue the audio sharing process. Providing the user with improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0259] After initiating the process for simultaneously providing audio data to a first external device and a second external device, the electronic device detects (708) an indication that the physical proximity between the electronic device and the second external device meets a proximity condition (e.g., indicated by 605). In some embodiments, near-field communication technology is used to detect the indication. In some embodiments, the proximity condition is met if the second electronic device is within a threshold distance of the electronic device. In some embodiments, the threshold distance is 6 inches, 12 inches, or 18 inches.

[0260] In response to an indication that the physical proximity between the electronic device and the second external device meets a proximity condition, the electronic device displays (710) a second user interface (e.g., 608, 608a) indicating that the physical proximity between the electronic device and the second external device meets the proximity condition. Displaying the second user interface indicating that the physical proximity between the electronic device and the second external device meets the proximity condition automatically provides feedback to the user, thereby reducing the amount of input required to share audio data. Providing improved feedback when a set of conditions has been met, reducing the amount of input required to perform an operation, and performing an operation without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This also reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0261] In some embodiments, the second user interface includes instructions for completing a process of simultaneously sharing audio data with a first external device and a second external device. In some embodiments, the process of simultaneously sharing audio data with the first and second external devices includes establishing a temporary connection between the electronic device and the second external device. In some embodiments, the second user interface includes indications that the electronic device has established a connection with the second electronic device or is in the process of establishing a connection to share audio data with the second external device and simultaneously with the first device.

[0262] In some implementations, the second external device is directly connected to the electronic device and configured to output audio based on audio data from the electronic device (e.g., Figure 6G , Figure 6K For example, in some implementations, the second external device does not receive audio data from the electronic device via an intermediate device such as a telephone to which the second external device is connected.

[0263] In some implementations, a second external device (e.g., 675) is connected to a third external device (e.g., 650; wireless headphones or wireless earbuds) and is configured to provide audio data from the electronic device to the third external device.

[0264] In some embodiments, as part of initiating a process for simultaneously providing audio data to a first external device and a second external device, the electronic device displays a representation of a first potential second external device (e.g., 606a-2). In some embodiments, as part of initiating a process for simultaneously providing audio data to a first external device and a second external device, the electronic device displays a representation of a second potential second external device (e.g., 606a-3). In some embodiments, the electronic device displays images of audio output devices configured to connect to and receive audio data from the electronic device while the electronic device simultaneously provides audio data to the first external device. In some embodiments, the electronic device sequentially displays representations of the first potential second external device, followed by representations of the second potential second external device (e.g., the electronic device cycles through representations of potential second external devices). Displaying representations of one or more external devices with which the electronic device can share data provides feedback to the user by indicating which devices are available for data sharing. Since not all devices support sharing capabilities, displaying potential options helps the user know which devices are available. Providing improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0265] In some embodiments, the second user interface includes a second power indicator (e.g., 608a-3) that, when selected, causes the electronic device to simultaneously provide audio data to both a first external device and a second external device. In some embodiments, although the electronic device initiates the process of simultaneously providing audio data to both the first and second external devices in response to detecting an input corresponding to the selection of the first power indicator, the electronic device does not actually provide audio data before selecting the second power indicator. Causing the electronic device to simultaneously provide audio data to both the first and second external devices in response to the selection of the second power indicator on the second user interface provides improved control by confirming that sharing is truly desired and avoids unintentional sharing of audio data before it is expected or with unintended devices. Providing improved control over the sharing process enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and improves the device's battery life by enabling the user to use the device more quickly and efficiently.

[0266] In some embodiments, after detecting an indication that the physical proximity between the electronic device and the second external device meets a proximity condition, and before providing audio data to both the first and second external devices simultaneously, the electronic device displays instructions (e.g., 612a-3) for providing input at the second external device. In some embodiments, the second external device requests input (e.g., pressing a hardware button on the second external device) to be connected to the electronic device.

[0267] In some embodiments, the electronic device receives an indication that a second external device is connected to the electronic device. In some embodiments, in response to receiving the indication that a second external device is connected to the electronic device, the electronic device provides the indication that the second external device is connected to the electronic device (e.g., 608a, 616a-4, 624a). In some embodiments, providing the indication that the second external device is connected to the electronic device includes displaying a graphical representation of the second external device. In some embodiments, the indication that the second external device is connected to the electronic device includes audio output and / or haptic output.

[0268] In some implementations, when a second external device is connected to an electronic device, the electronic device displays a third power indicator (e.g., 618a-4, 634a-3, 636-2, 906-3), which, when selected, disconnects the second external device from the electronic device.

[0269] In some embodiments, when a second external device is connected to an electronic device, the electronic device detects an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition (e.g., indicated by 615). In some embodiments, the electronic device displays a third power indicator (e.g., 618a-4) in response to the indication that the physical proximity between the electronic device and the second external device meets the second proximity condition. In some embodiments, the third power indicator is displayed based on determining that the second external device has re-entered the range required to meet the proximity condition. In some embodiments, the second proximity condition may be the same as the (first) proximity condition. Displaying a power indicator for disconnecting the second external device in response to the indication that the physical proximity between the electronic device and the second external device meets the second proximity condition provides feedback to the user that they can stop sharing audio with the second external device, and automatically presents the option to disconnect the second external device, thereby reducing the amount of input required to stop sharing audio data. Providing improved feedback when a set of conditions have been met, reducing the amount of input required to perform an operation, and performing an operation without further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This also reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0270] In some implementations, the electronic device displays a third power indicator based on the determination that the second external device is not paired with the electronic device. In some implementations, two devices (e.g., the second external device and the electronic device) are paired if they have a persistent association with each other and are configured to exchange data via a communication link. In some implementations, devices are not paired if they do not have a persistent association with each other. In some implementations, paired devices remain associated with each other when the communication link between the devices is currently inactive, while temporarily connected but not paired devices are no longer associated with each other after the temporary connection ends. In some implementations, paired devices share common configuration settings. In some implementations, if the second external device is paired with the electronic device, the electronic device waives the display of the third power indicator and, optionally, displays information about the second external device (e.g., battery level).

[0271] In some implementations, a third capability indicator is displayed in a menu user interface (e.g., 636). In some implementations, the menu user interface is a Bluetooth settings menu or an audio output menu user interface of an audio media player application.

[0272] It should be noted that the above description is in contrast to the process described in method 700 (e.g., Figure 7The details of the above also apply in a similar manner to the methods described below. For example, methods 800, 1000, and / or 1200 optionally include one or more features of the various methods described above with reference to method 700. For example, operation 710 of displaying a second user interface in method 700 may be performed in response to detecting an instruction in operation 802 of method 800. As another example, the operations of method 700 may be performed prior to the operations of method 1000 and / or method 1200. For the sake of brevity, these details will not be repeated below.

[0273] Figure 8 This is a flowchart illustrating a method for sharing audio data using an electronic device according to some embodiments. Method 800 is performed at a device (e.g., 100, 300, 500, or 600) having a display device (e.g., 602). Some operations in method 800 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0274] As described below, method 800 provides an intuitive way to share audio data. This method reduces the cognitive burden on users when sharing audio data, thus creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to share audio data more quickly and efficiently, saving power and increasing the time interval between battery charging.

[0275] When an electronic device is connected to a first external device (e.g., 625; a wireless headset or wireless earbud) via a communication link (e.g., C1), the electronic device detects (802) an indication that the physical proximity between the electronic device and a second external device (e.g., 650; a wireless headset or wireless earbud) different from the first external device satisfies a proximity condition (e.g., represented by 635), wherein the electronic device is configured to provide audio data to the first external device via the communication link (e.g., and is not currently configured to provide audio data to the second external device (e.g., 650)). In some embodiments, near-field communication technology is used to detect the indication. In some embodiments, the proximity condition is satisfied if the second electronic device is within a threshold distance of the electronic device. In some embodiments, the threshold distance is 6 inches, 12 inches, or 18 inches.

[0276] In response to an indication that the physical proximity between the electronic device and the second external device meets the proximity condition, the electronic device displays (804) a first user interface (e.g., 622, 622a) including a first power indication (e.g., 622a-5) via a display device.

[0277] In some embodiments, the first user interface includes an indication that the electronic device can temporarily share audio data with a second external device. In some embodiments, the first user interface includes (e.g., on a first power indicator) an indication that selecting the first power indicator will cause the electronic device to share audio data with the second external device. In some embodiments, the electronic device displays the first power indicator upon determining that the electronic device is connected to the first external device, and optionally, the electronic device is running an audio media application or actively providing audio data to the first external device via a communication link. Displaying a first user interface with a first power indicator for sharing audio data in response to an indication that the physical proximity between the electronic device and the second external device meets proximity conditions automatically provides feedback to the user, thereby reducing the amount of input required to share audio data. Providing improved feedback when a set of conditions has been met, reducing the amount of input required to perform an operation, and performing an operation without further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This also reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0278] Electronic device detection (806) corresponds to the input of the selection of the first power indication (e.g., 610e).

[0279] In response to detecting an input corresponding to a selection of a first indication, the electronic device initiates (808) a process for simultaneously providing audio data to a first external device (e.g., 625) and a second external device (e.g., 650). In some embodiments, the process for simultaneously sharing audio data with the first and second external devices includes establishing a temporary connection between the electronic device and the second external device. In some embodiments, the process for simultaneously sharing audio data with the first and second external devices includes displaying a visual indication that the electronic device has established a connection with the second external device or is in the process of establishing a connection to simultaneously share audio data with the first and second external devices. In some embodiments, the process for simultaneously sharing audio data with the first and second external devices includes displaying instructions for completing the process of simultaneously sharing audio data with the first and second external devices. Displaying instructions for completing the process of sharing audio data provides the user with feedback that the electronic device is ready to share audio data and informs the user how to continue the audio sharing process. Providing users with improved visual feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0280] In some embodiments, upon determining that a first external device is configured to receive audio data from an electronic device while the electronic device simultaneously provides audio data to a second external device, the electronic device displays a first user interface including the first power indicator. In some embodiments, upon determining that the first external device is not configured to receive audio data from the electronic device while the electronic device simultaneously provides audio data to a second external device, the electronic device refrains from displaying the first user interface.

[0281] In some implementations, upon determining that the electronic device is running an audio media application (e.g., a music application, podcast application, audiobook application, multimedia application, or web browser for playing audio and / or video), the electronic device displays a first user interface including a first power indication. In some implementations, upon determining that the electronic device is not running an audio media application, the electronic device refrains from displaying the first user interface.

[0282] In some implementations, upon determining that the second external device is not paired with the electronic device, the electronic device displays a first user interface including a first power indicator. In some implementations, two devices (e.g., the second external device and the electronic device) are paired if they have a persistent association with each other and are configured to exchange data via a communication link. In some implementations, if the devices do not have a persistent association with each other, they are not paired. In some implementations, paired devices remain associated with each other when the communication link between the devices is currently inactive, while temporarily connected but not paired devices are no longer associated with each other after the temporary connection ends. In some implementations, paired devices share common configuration settings. In some implementations, if the second external device is paired with the electronic device, the electronic device waives the display of the first user interface and, optionally, displays information about the second external device (e.g., battery level).

[0283] In some embodiments, the first user interface includes a second power indicator (e.g., 622a-5) that, when selected, pairs the second external device with the electronic device. In some embodiments, pairing the second external device with the electronic device creates a persistent association between the second external device and the electronic device. In some embodiments, the second power indicator disconnects the first external device from the electronic device when selected. Displaying a power indicator for pairing the second external device (e.g., in addition to simultaneously displaying a power indicator for temporarily sharing data with the second external device) in response to detecting that physical proximity between the electronic device and the second external device meets proximity conditions provides feedback to the user that they have the option to pair with the second external device or temporarily share audio data, and those options are presented automatically. Providing the user with improved visual feedback and performing actions (e.g., displaying pairing and sharing options) when a set of conditions has been met without requiring further user input enhances device operability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0284] In some implementations, the second external device is directly and wirelessly connected to the electronic device and configured to output audio based on audio data from the electronic device (e.g., Figure 6K For example, in some implementations, the second external device does not receive audio data from the electronic device via an intermediate device such as a telephone to which the second external device is connected.

[0285] In some embodiments, after detecting input corresponding to a selection of the first indication and before providing audio data to both the first and second external devices simultaneously, the electronic device displays instructions (e.g., 612a-3) for providing input at the second external device. In some embodiments, the second external device requests input (e.g., pressing a hardware button on the second external device, e.g., 610c) to be connected to the electronic device.

[0286] In some embodiments, the electronic device receives an indication that a second external device is connected to the electronic device. In some embodiments, in response to receiving the indication that a second external device is connected to the electronic device, the electronic device provides the indication that the second external device is connected to the electronic device (e.g., 616a-4, 624a). In some embodiments, providing the indication that the second external device is connected to the electronic device includes displaying a graphical representation of the second external device. In some embodiments, the indication that the second external device is connected to the electronic device includes audio output and / or haptic output.

[0287] In some embodiments, when a second external device is connected to an electronic device, the electronic device displays a second power indicator (e.g., 618a-4, 634a-3, 636-2, 906-3), which, when selected, disconnects the second external device from the electronic device. In some embodiments, when a second external device is connected to an electronic device, the electronic device detects that the physical proximity between the electronic device and the second external device meets a second proximity condition (e.g., ...). Figure 6H The indication of disconnecting the second external device is displayed in response to an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition. In some embodiments, the second power indication is displayed based on the determination that the second external device has re-entered the range required to meet the proximity condition (e.g., the second proximity condition or the (first) proximity condition). In some embodiments, the second proximity condition may be the same as the (first) proximity condition. Displaying a power indication for disconnecting the second external device in response to an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition provides feedback to the user that they can stop sharing audio with the second external device and automatically presents the option to disconnect the second external device, thereby reducing the amount of input required to stop sharing audio data. Providing improved feedback when a set of conditions has been met, reducing the amount of input required to perform an operation, and performing an operation without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0288] In some embodiments, the electronic device displays a second power indicator based on the determination that the second external device is not paired with the electronic device (e.g., 618a-4). In some embodiments, if the second external device is paired with the electronic device, the electronic device waives the display of the second power indicator and optionally displays information about the second external device (e.g., battery level). In some embodiments, the second power indicator is displayed in a menu user interface (e.g., 636). In some embodiments, the menu user interface is a Bluetooth settings menu or an audio output menu user interface of an audio media player application.

[0289] It should be noted that the above is relative to method 800 (e.g., Figure 8 The details of the process described herein also apply in a similar manner to the methods described above and below. For example, method 700, method 1000, and / or method 1200 optionally include one or more features of the various methods described above with reference to method 800. For example, operation 804 of displaying a second user interface in method 700 may be performed in response to detecting an instruction in operation 708 of method 700. As another example, the operation of method 800 may be performed prior to the operation of method 1000 and / or method 1200. For the sake of brevity, these details will not be repeated below.

[0290] Figures 9A-9E The accompanying drawings illustrate exemplary user interfaces for adjusting the volume levels of one or more devices, according to some embodiments. The user interfaces in these drawings are used to illustrate the following descriptions, including... Figure 10 The process of...

[0291] Figure 9AA device 600 is shown that is simultaneously connected to device 625 (via communication link C5) and device 650 (via communication link C6) and provides audio data to these devices. Device 600 displays a user interface 900 (e.g., a home screen or application pop-up) and detects input 910a (e.g., a swipe on a touch-sensitive display 602). In response to the detection of input 910a, device 600 displays a user interface 902 (e.g., a control center). User interface 902 includes power indicators for controlling various functions and settings of device 600 and peripheral devices connected to device 600, such as device 625 and device 650. Power indicator 902-1 corresponds to the audio media application currently playing media item (track 1 of DJ Appleseed). Volume power indicator 902-2 provides the ability to adjust the volume level of device 625 and device 650 from user interface 902 using a single input. Based on the determination that device 600 is providing audio data to more than one device (e.g., sharing audio data with device 650 while simultaneously providing audio data to device 625), user interface 902 includes graphical elements 902-3 (e.g., badges on volume indicator 902-2). Graphical elements 902-3 provide visual indications that device 600 is providing audio data to multiple devices (e.g., devices associated with multiple users).

[0292] exist Figure 9B In the process, device 600 detects input 910b corresponding to the selection of volume indicator 902-2 (e.g., dragging upwards). Based on whether input 910b is a first type of input (e.g., ...), Figure 9B As shown, by dragging upwards, device 600 adjusts (e.g., increases) the volume level of device 625 and the volume level of device 650, as indicated by... Figure 9C The volume indicator in the 902-2 is indicated by its updated visual appearance. Figure 9CIn the illustrated embodiments, the height of the horizontal line within the volume indicator 902-2 indicates the current master volume level of devices 625 and 650. In some embodiments, the volume levels of devices 625 and 650 are adjusted using the indicator 902-2 to set the volume levels of devices 625 and 650 to the same volume level (e.g., even if devices 625 and 650 had different volume levels before the indicator 902-2 was selected). In some embodiments, the volume levels of devices 625 and 650 are adjusted using the indicator 902-2 to set the volume levels of devices 625 and 650 to the respective volume levels based on the initial volume level of the respective devices and the inputs on the indicator 902-2 (e.g., the direction and length of input 910b). In some embodiments, if the volume level of device 625 is the same as the volume level of device 650, the volume indicator 902-2 indicates the volume levels of devices 625 and 650. In some implementations, if the volume level of device 625 is different from the volume level of device 650, the volume indicator 902-2 indicates the volume level of device 625, the volume level of device 650, the volume level of the device with a higher volume level, the volume level of the device with a lower volume level, or a combination of the volume levels of device 625 and device 650 (e.g., an average value).

[0293] exist Figure 9C In this process, device 600 detects input 910c corresponding to the selection of volume indicator 902-2. Since input 910c is a second type of input, different from input 910b, device 600 displays a user interface, wherein the displayed user interface depends on the connection conditions relative to an external device (e.g., device 650).

[0294] If the connection conditions are met (e.g., device 650 and device 625 are simultaneously connected to device 600), device 600 displays user interface 904, such as... Figure 9D As shown. The user interface 904 includes graphical elements 904-1 to 904-4. Graphical element 904-1 represents device 625 and indicates that volume indicator 904-3 controls the volume level of device 625. Graphical element 904-2 represents device 650 and indicates that volume indicator 904-4 controls the volume level of device 650. When indicator 904-3 is selected (e.g., by vertical dragging), it adjusts the volume level of device 625 without changing the volume level of device 650. When indicator 904-4 is selected (e.g., by vertical dragging), it adjusts the volume level of device 650 without changing the volume level of device 625. Figure 9DIn the illustrated embodiment, the volume level of device 625 is the same as the volume level of device 650, which corresponds to the volume level indicated by the volume indicator 902-2.

[0295] If the connection conditions are determined not to be met (e.g., device 650 is connected to device 600 via device 675), device 600 displays user interface 906, such as... Figure 9E As shown. In Figure 9E In this configuration, device 625 is connected to device 600 via communication link C5; device 675 is connected to device 600 via communication link C8; and device 650 is connected to device 675 via communication link C7. Depending on the configuration of devices 600, 625, and 675, user interface 906 includes graphical elements 906-1 to 906-4. Graphical element 906-1 represents device 625 and indicates that volume indicator 906-2 controls the volume level of device 625. User interface 906 does not include an indicator for controlling the volume level of device 650 (e.g., since device 650 is connected to device 600 via device 675). For example, since device 650 is connected to device 675 via communication link C7, device 675 maintains control over the volume level of device 650 (e.g., the volume level of device 650 can only be controlled via input on device 675). When selected, the disconnect enable indicator 906-3 causes device 600 to stop sharing audio data with device 650 (e.g., device 600 disconnects the communication link C8 with device 675), as indicated by graphic element 906-4 (“Chance Stop Listening”).

[0296] Figure 10 This is a flowchart illustrating a method for adjusting the volume level of one or more devices using an electronic device according to some embodiments. Method 1000 is performed at a device (e.g., 100, 300, 500, or 600) having a display device (e.g., 602). Some operations in method 1000 may be combined, some operations may be changed in order, and some operations may be omitted.

[0297] As described below, Method 1000 provides an intuitive way to adjust the volume levels of one or more devices. This method reduces the cognitive burden on users adjusting the volume levels of one or more devices, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to adjust the volume levels of one or more devices faster and more efficiently saves power and increases the time interval between battery charging.

[0298] When a first connection condition is met relative to an electronic device (e.g., 600), a first external device (e.g., 625), and a second external device (e.g., 650, 675), the electronic device receives (1002) a request (e.g., input 910a) to display a first volume control indication (e.g., 902-2), wherein the electronic device is configured to provide audio data to the first external device when connected and is configured to provide audio data to the second external device when connected. In some embodiments, the connection condition is based on the connection status of the first external device and / or the second external device to the electronic device. In some embodiments, the connection condition is met if the electronic device is simultaneously connected to the first external device (e.g., a wireless headset or a pair of wireless earbuds operating as a single device) and a second external device different from the first external device (e.g., a wireless headset or a pair of wireless earbuds operating as a single device). In some embodiments, the electronic device is directly connected to the second external device. In some embodiments, the electronic device is connected to the second external device via a third external device (e.g., a telephone). For example, the electronic device is connected to the third external device, and the third external device is connected to the second external device. In some implementations, the connection condition is satisfied only when the first external device and the second external device operate as independent devices (e.g., not as a pair of earbuds operating together). Examples of a request to display the first volume control power indicator include, but are not limited to, touch input on the touch-sensitive surface of the electronic device (e.g., an upward swipe gesture from the bottom edge of the touch-sensitive surface, a downward swipe gesture from the top edge of the touch-sensitive surface), selection of the power indicator, pressing a mechanical button on the electronic device (e.g., when the electronic device is in sleep mode or the display device is inactive), and movement of the electronic device that meets motion conditions (e.g., picking up the electronic device or moving the electronic device to a viewing location). In some implementations, a request to display the volume control power indicator includes a request to display a user interface (e.g., a control center user interface) with the volume control power indicator.

[0299] In response to receiving a request to display a first volume control indication, the electronic device displays (1004) a first volume control indication (e.g., 902-2).

[0300] Electronic device detection (1006) corresponds to an input (e.g., 910c) for selecting a first volume control indication. In some embodiments, the input corresponding to the selection of the volume control indication includes a contact on a touch-sensitive surface of the electronic device, wherein the contact is determined to have a characteristic intensity exceeding a predefined threshold intensity. In some embodiments, the input corresponding to the selection of the volume control indication includes a contact on a touch-sensitive surface of the electronic device, wherein the contact is determined to have a duration exceeding a predefined threshold duration.

[0301] In response to detecting an input corresponding to a selection of a first volume control indication, the electronic device displays (1008) a user interface (e.g., 904, 906). As part of displaying the user interface, based on determining that a second connection condition is met relative to the second external device (e.g., the second external device is directly connected to the electronic device; the second external device is not connected to the electronic device via a third external device (e.g., a telephone); the second external device is simply connected to the electronic device), the electronic device displays (1010) a second volume control indication (e.g., 904-3) and a third volume control indication (e.g., 904-4), the second volume control indication adjusting the volume level of the first external device when selected (e.g., without adjusting the volume of the second external device), the third volume control indication adjusting the volume level of the second external device when selected (e.g., without adjusting the volume of the first external device); the electronic device displays separate controls for the first and second external devices, which provide the ability to control the volume level of the first external device independently of the volume level of the second external device, and vice versa). In some implementations, the electronic device stops displaying the first volume control indicator and displays a second and a third volume control indicator. In some implementations, a second connection condition is satisfied relative to the second external device if the second external device is a composite device (e.g., a pair of earbuds operating collaboratively as a single device) and one or more elements of the composite device are directly connected to the electronic device. Based on determining that the connection condition is satisfied relative to the second external device, displaying the volume control indicator for the first external device and the separate volume control indicator for the second external device provides feedback to the user by displaying controls relevant to the current context. Providing improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling the user to use the device more quickly and effectively.

[0302] As part of the user interface display, based on the determination that the second connection condition is not met relative to the second external device, the electronic device displays (1012) a fourth volume control indication (e.g., 906-2) that adjusts the volume level of the first external device (e.g., without adjusting the volume of the second external device) when selected, instead of displaying a volume control indication for adjusting the volume level of the second external device (e.g., the electronic device displays a single volume control indication for adjusting the volume level of the first external device). Displaying a volume control indication for only the first external device based on the determination that the connection condition is not met relative to the second external device provides feedback to the user by displaying controls relevant to the current context. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0303] In some implementations, if a second external device is paired with a third external device (e.g., a telephone) and receives audio data directly from or indirectly via the electronic device, the second connection condition is not satisfied relative to the second external device. In some implementations, if the second external device is a pair of earbuds paired with a device different from the electronic device, the second connection condition is not satisfied relative to the second external device. In some implementations, two devices are paired if they have a persistent association with each other and are configured to exchange data via a communication link. In some implementations, devices are not paired if they do not have a persistent association with each other. In some implementations, paired devices remain associated with each other when the communication link between the devices is currently inactive, while temporarily connected but not paired devices are no longer associated with each other after the temporary connection ends. In some implementations, paired devices share common configuration settings. In some implementations, the electronic device stops displaying the first volume control indicator and displays a fourth volume control indicator. In some implementations, the user interface is displayed based on determining that the input corresponding to the selection of the first volume control indicator is a first type of input (e.g., a force press or a static long press). In some implementations, the first volume indicator provides the ability to adjust the volume levels of both the first and second external devices simultaneously. For example, in some implementations, based on the determination that the input corresponding to the selection of the first volume control indicator is a second type of input different from the first type (e.g., an up or down swipe gesture on the first volume control indicator), the electronic device updates the first volume control indicator to indicate a new volume level and sends instructions to adjust the volume level of the first external device and, in the case where the second external device is not connected to the third external device.

[0304] In some embodiments, the electronic device simultaneously displays a second volume control indicator (e.g., 616a-3), a third volume control indicator (e.g., 616a-4), and a fifth volume control indicator (e.g., 616a-6), which, when selected, adjusts the volume level of a first external device and also adjusts the volume level of a second external device (see also, for example...). Figure 6O and Figure 6Q In some implementations, the fifth volume control indicator is the first volume control indicator (e.g., the first volume control indicator remains displayed when it is selected).

[0305] In some embodiments, the input corresponding to the selection of the first volume control power indication (e.g., 910c) includes a contact with a characteristic intensity, and a display user interface is executed (e.g., 904, 906) based on determining that the characteristic intensity exceeds a threshold intensity. In some embodiments, the electronic device abandons the display user interface based on determining that the characteristic intensity does not exceed the threshold intensity. The input-based characteristic display user interface provides additional control options for the first volume control power indication and avoids cluttering the display with additional displayed controls. Providing additional control options without cluttering the display with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby reducing power consumption and extending the device's battery life by enabling users to use the device more quickly and efficiently.

[0306] In some embodiments, the electronic device simultaneously displays a first volume control power indicator and an indication that a first connection condition is met relative to the electronic device, the first external device, and the second external device (e.g., 902-3). In some embodiments, the indication that the first connection condition is met relative to the electronic device, the first external device, and the second external device is displayed on the first volume control power indicator.

[0307] In some embodiments, the electronic device simultaneously displays a fifth volume control power indicator and a disconnect power indicator (e.g., 906-3), which, when selected, disconnects the second external device from the electronic device. In some embodiments, a disconnect power indicator and a fourth volume control power indicator are displayed simultaneously. Displaying a power indicator for disconnecting the second external device provides feedback to the user that they can stop sharing audio with the second external device, and presents the option to disconnect the second external device without additional input (e.g., accessing a separate options menu), thus reducing the amount of input required to stop sharing audio data. Providing improved feedback and reducing the amount of input required to perform the operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0308] It should be noted that the above is relative to method 1000 (for example, Figure 10 The details of the process also apply in a similar manner to the methods described above and below. For example, methods 700, 800, and / or 1200 optionally include one or more features of the various methods described above with reference to method 1000. For example, the operation of method 1000 may be performed after the operation of method 700 and / or method 800 and before or after the operation of method 1200. For the sake of brevity, these details will not be repeated below.

[0309] Figures 11A-11F Exemplary user interfaces for controlling audio media applications, according to some embodiments, are shown. The user interfaces in these figures are used to illustrate the processes described below, including... Figure 12 The process in.

[0310] Figure 11A A device 1100 (e.g., a watch) is shown, having a display device 1102, a rotatable input device 1104, and mechanical buttons 1106. In some embodiments, device 1100 is device 100, 300, or 500. In some embodiments, the rotatable input device 1104 is pressable and rotatable. Figure 11A In the display, device 1100 shows a user interface 1108 including power indicators 1108-1 and 1108-2. Power indicator 1108-1 corresponds to an audio media application on a first device (e.g., a telephone) to which device 1100 is connected (e.g., via Bluetooth or the Internet). Figures 11A-11FIn the illustrated embodiment, device 1100 is connected to (e.g., paired with) device 600, and power indicator 1108-1 corresponds to an audio media application on device 600. Power indicator 1108-2 corresponds to an audio media application on a second device (e.g., a wireless speaker) to which device 1100 is connected (e.g., via Bluetooth or the Internet). Power indicators 1108-1 and 1108-2 can be selected to display a user interface for controlling the corresponding application on the corresponding device.

[0311] exist Figure 11A In this embodiment, device 1100 detects input 1110a (e.g., a tap) corresponding to a selection of the power indicator 1108-1. In response to the detection of input 1110a, device 1100 displays an audio media user interface 1112 for controlling an audio media application on device 600 corresponding to the power indicator 1108-1. The audio media user interface 1112 includes, in particular, track information 1112-1, a volume level indicator 1112-2, and controls 1112-3. The volume level indicator 1112-2 indicates the volume level (or multiple volume levels) of an audio output device (or multiple audio output devices) to which device 600 is providing audio data. In some embodiments, the number of arcs to the right of the volume level indicator 1112-2 indicates the volume level (e.g., one arc for low, two arcs for medium, and three arcs for high).

[0312] exist Figure 11B In this process, device 1100 detects input 1110b (e.g., rotation of rotatable input device 1104). In response to the detection of input 1110b, device 1100 sends an instruction to device 600 to adjust the volume level of one or more devices outputting audio provided by an application corresponding to audio media user interface 1112. For example, if device 600 simultaneously provides audio data to devices 625 and 650 as described above, rotatable input device 1104 can be rotated to adjust the volume levels of devices 625 and 650 using a single input. In some embodiments, adjusting the volume levels of devices 625 and 650 using rotatable input device 1104 sets the volume levels of devices 625 and 650 to the same level (e.g., even if devices 625 and 650 had different volume levels before the rotatable input device 1104 was moved). In some implementations, the volume levels of devices 625 and 650 are adjusted using the rotatable input device 1104 based on the initial volume level of the respective devices and the movement of the rotatable input device 1104 (e.g., the amount of rotation and / or the rotation speed of the rotatable input device 1104).

[0313] Based on the determination that the device corresponding to the audio media user interface 1112 is providing audio to multiple devices (e.g., device 600 is providing audio data to devices 625 and 650), device 1100 displays multiple volume level indicators in response to detecting input 1110b. For example... Figure 11C As shown, device 1100 displays a volume level indicator 1112-4, which includes a single volume level indicator 1112-4a corresponding to a first output device (e.g., device 625) and a single volume level indicator 1112-4b corresponding to a second output device (e.g., device 650). In response to detecting that input 1110b has stopped (e.g., a predetermined amount of time after detecting that input 1110b has stopped), device 1100 displays an updated volume level indicator 1112-5 indicating the volume level after input 1110b, as shown. Figure 11D As shown. In some embodiments, if the volume level of device 625 is the same as the volume level of device 650, then volume level indicators 1112-5 indicate the volume levels of devices 625 and 650. In some embodiments, if the volume level of device 625 is different from the volume level of device 650, then volume level indicators 1112-5 indicate the volume level of device 625, the volume level of device 650, the volume level of the device with the higher volume level, the volume level of the device with the lower volume level, or a combination of the volume levels of devices 625 and 650 (e.g., an average value).

[0314] exist Figure 11D In this context, device 1100 detects input 1110c (e.g., a tap) corresponding to a selection of the enable displays 1112-6 on user interface 1112. In response to the detection of input 1110c, device 1100 displays a user interface for selecting one or more audio output devices. The user interface depends on output device conditions configured based on, for example, available output devices.

[0315] For example, if device 600 provides audio data to two devices (device 625 and device 650) simultaneously, device 1100 displays the device selection user interface 1114, such as... Figure 11E As shown. The device selection user interface 1114 includes a power indicator 1114-1 and a power indicator 1114-2. Power indicator 1114-1 corresponds to device 600, and when selected, device 600 is selected as the device to output audio. Power indicator 1114-2 corresponds to devices 625 and 650, and when selected, both devices 625 and 650 are selected as the devices to output audio. That is, selecting a single power indicator (power indicator 1114-2) causes audio data from the audio media application to be provided to more than one device (device 625 and device 650) simultaneously.

[0316] If device 600 does not provide audio data to both devices simultaneously (e.g., device 600 only provides audio data to device 625), then device 1100 displays the device selection user interface 1116, such as... Figure 11F As shown. The device selection user interface 1116 includes power indicators 1116-1, 1116-2, and 1116-3. Power indicator 1116-1 corresponds to device 600, and when selected, device 600 is selected as the device to output audio; power indicator 1116-2 corresponds to device 625, and when selected, device 625 is selected as the device to output audio; and power indicator 1116-3 corresponds to a third device to which device 600 is configured to provide audio data. In some embodiments, there is no single power indicator on the device selection user interface 1116 corresponding to more than one device (e.g., there is no single power indicator causing audio to be output on more than one device).

[0317] Figure 12 This is a flowchart illustrating a method for controlling an audio media output application using an electronic device, according to some embodiments. Method 1200 is performed at a device (e.g., 100, 300, 500, or 1100) having a display device (e.g., 1102). Some operations in method 1200 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0318] As described below, method 1200 provides an intuitive way to control audio media output. This method reduces the cognitive burden on users when controlling audio media output, thus creating a more efficient human-computer interface. For battery-powered computing devices, it enables users to control audio media output more quickly and effectively, saving power and increasing the time interval between battery charging.

[0319] When a first user interface (e.g., 1112) including controls for an audio media application (e.g., 1112-3) is displayed, the electronic device receives (1202) a request (e.g., input 1110c) to display a user interface (e.g., 1114, 1116) for selecting one or more devices (e.g., wireless headphones or wireless earbuds) from which to output audio from the audio media application.

[0320] In response to receiving a request to display a user interface of one or more devices for selecting audio to be output from an audio media application, the electronic device displays (1204) a second user interface (e.g., 1114, 1116).

[0321] As part of displaying a second user interface, based on determining that a source electronic device (e.g., 600, 1100) is connected to a first external device (e.g., 625; a wireless headset or a pair of wireless earbuds operating as a single device) and a second external device different from the first external device (e.g., 650; a wireless headset or a pair of wireless earbuds operating as a single device), and configured to simultaneously provide audio data from an audio media application to both the first and second external devices, the electronic device displays (1206) a first power indicator (e.g., 1114-2), which, when selected, causes the simultaneous provision of audio data from the audio media application to both the first and second external devices. Based on determining that the source electronic device is connected to both the first and second external devices and that the source electronic device is configured to simultaneously provide audio data from the audio media application to both the first and second external devices, the first power indicator used to cause the simultaneous provision of audio data from the audio media application to both the first and second external devices provides feedback to the user by displaying controls relevant to the current context. Providing improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0322] In some embodiments, the source electronic device is an electronic device. In some embodiments, the source electronic device is an external device connected to the electronic device. In some embodiments, an audio media application runs on the source device external to the electronic device, and the audio media application can be controlled via input at the electronic device through the connection between the electronic device and the source device. In some embodiments, audio is not provided to the second external device via the first external device. In some embodiments, the second external device appears to the electronic device as a separate external device from the first external device. In some embodiments, the first and second external devices are not a pair of earbuds operating as a single device.

[0323] As part of displaying a second user interface, based on the determination that the source electronic device is connected to a first external device and configured to provide audio data from an audio media application to the first external device without simultaneously providing audio data from the audio media application to another external device, the electronic device displays (1208) a second power indicator (e.g., 1116-2), which, when selected, causes only the audio data from the audio media application to be provided to the first external device. The second power indicator, used to cause only the audio data from the audio media application to be provided to the first external device, provides feedback to the user by displaying controls relevant to the current context, based on the determination that the source electronic device is connected to the first external device and configured to provide audio data from the audio media application to the first external device without simultaneously providing audio data from the audio media application to another external device. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0324] In some implementations, if the source electronics are connected to multiple output devices (e.g., a first external device and a second external device) and configured to provide audio data from an audio media application to each of the output devices (but not to more than one output device at a time), the electronics display an indication for each output device to provide audio data to the corresponding output device. In some implementations, providing audio only to the first external device includes providing audio to a pair of physically separate earbuds operating as a single external device.

[0325] In some implementations, a first external device (e.g., 625) is paired with a source electronic device (e.g., 600, 1100). In some implementations, two devices (e.g., the first external device and the source electronic device) are paired if they have a persistent association with each other and are configured to exchange data via a communication link. In some implementations, devices are not paired if they do not have a persistent association with each other. In some implementations, paired devices remain associated with each other when the communication link between the devices is currently inactive, while temporarily connected but not paired devices are no longer associated with each other after the temporary connection ends. In some implementations, paired devices share common configuration settings.

[0326] In some implementations, the second external device (e.g., 650) is not paired with the source electronic device (e.g., 600, 1100). In some implementations, the source electronic device (e.g., 600) is paired with the electronic device (e.g., 1100).

[0327] In some implementations, the second user interface includes a third power indicator (e.g., 1114-1, 1116-1) which, when selected, causes audio from an audio media application to be output by the source electronic device.

[0328] In some implementations, the electronic device detects an input (e.g., a single input; a single input on a single volume control indicator). In some implementations, in response to the detected input (e.g., 1110b), the electronic device adjusts the volume level of a first external device and adjusts the volume level of a second external device. Adjusting the volume levels of the first and second external devices in response to a single input reduces the number of inputs required to adjust the volume of both devices and reduces the need to display additional controls to adjust the volume of both devices. Reducing the number of inputs required to perform the operation and providing additional control options without cluttering the user interface with additional displayed controls enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), thereby reducing power consumption and improving device battery life by enabling users to use the device more quickly and efficiently.

[0329] In some embodiments, in response to detected input, the electronic device displays a graphical indication of the volume level of a first external device (e.g., 1112-4a) and a graphical indication of the volume level of a second external device (e.g., 1112-4b), which is different from the graphical indication of the volume level of the first external device. In some embodiments, the graphical indications of the volume levels of the first and second external devices are visually distinct graphical elements (e.g., separate sliders or bars). Displaying separate graphical indications of the volume level of each device provides the user with feedback on input to adjust the volume of both devices. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and effectively.

[0330] In some embodiments, input includes the rotation of a rotatable input device (e.g., 1104) that rotates relative to the housing of the electronic device. In some embodiments, the rotatable input device is both rotatable and pressable.

[0331] It should be noted that the above description is in contrast to the process described in method 1200 (e.g., Figure 12The details of the methods described above also apply in a similar manner. For example, methods 700, 800, and / or 1000 optionally include one or more features of the various methods described above with reference to method 1200. For example, the operation of method 1200 may be performed before or after the operation of methods 700 and / or 800 and before or after the operation of method 1000. For the sake of brevity, these details will not be repeated below.

[0332] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. These embodiments were chosen and described in order to best explain the principles of these techniques and their practical applications. Others skilled in the art will thus be able to best utilize these techniques and the various embodiments with various modifications suitable for the particular intended use.

[0333] While this disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of this disclosure and examples as defined by the claims.

[0334] As described above, one aspect of the present invention involves collecting and using data from various sources to improve the delivery of audio media to users. This disclosure contemplates that, in some instances, the collected data may include personal information that uniquely identifies or can be used to contact or locate specific individuals. Such personal information may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, account information and / or user preferences for audio media services (e.g., streaming music services), data or records related to a user's health or health level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0335] This disclosure recognizes that the use of such personal information data in the present invention can benefit users. For example, personal information data can be used to provide users with audio media that they are more interested in. Therefore, the use of such personal information data enables users to have planned control over the content provided. Furthermore, this disclosure also anticipates other uses of personal information data that are beneficial to users. For example, health and fitness data can be used to provide insights into a user's overall health status or can be used as positive feedback for individuals using technology to pursue health goals.

[0336] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to 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 information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

[0337] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to streaming audio services, the technology of this invention can be configured to allow users to opt-in or opt-out at any time during or after service registration to participate in the collection of personal information data. In another example, users can choose not to provide user preferences or account information for streaming audio services. As another example, users can choose to limit the length of time preference data is retained or completely prohibit the development of baseline preference profiles. In addition to providing opt-in and opt-out options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users can be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0338] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0339] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or an absolute minimum of personal information (e.g., content requested by a device associated with a user, other non-personal information or publicly available information available for audio content delivery services), thereby selecting audio content and delivering it to the user.

Claims

1. A method for sharing audio, comprising: At electronic devices with display devices: When the electronic device is connected to a first external device via a communication link and when displaying a first user interface, wherein the electronic device is configured to provide audio data to the first external device via the communication link, the physical distance between the electronic device and the second external device is determined: Based on the determination that the physical distance between the electronic device and the second external device meets the proximity condition, the first user interface and a second user interface including a first power indicator and a second power indicator are simultaneously displayed via the display device. as well as Based on the determination that the physical distance between the electronic device and the second external device does not meet the proximity condition, the display of the second user interface including the first power indicator and the second power indicator via the display device is abandoned; When both the first user interface and the second user interface are displayed simultaneously, input is detected: Based on the determination that the input includes the selection of the first power indication, a process is initiated via a second communication link to simultaneously provide audio data to the first external device and the second external device, wherein when the second communication link is disconnected, the second external device and the electronic device are not associated. as well as Based on the determination that the input includes the selection of the second power indication, a process is initiated to provide audio data to the second external device via a third communication link, wherein the electronic device and the second external device remain associated when the third communication link is disconnected.

2. The method according to claim 1, wherein, Based on the determination that the first external device is configured to receive audio data from the electronic device while the electronic device simultaneously provides audio data to the second external device, the first user interface, including the first display, is executed.

3. The method according to any one of claims 1 to 2, wherein, Based on the determination that the electronic device is running an audio media application, the first user interface, which includes the first power indication, is executed.

4. The method according to any one of claims 1 to 2, wherein, Based on the determination that the second external device is not paired with the electronic device, the first user interface, including the first power indication, is executed.

5. The method according to any one of claims 1 to 2, wherein, The second indication means that when selected, the second external device will be paired with the electronic device.

6. The method according to any one of claims 1 to 2, wherein, The second external device is configured to output audio based on the audio data from the electronic device and to connect directly and wirelessly to the electronic device.

7. The method according to any one of claims 1 to 2, further comprising: After detecting the input corresponding to the selection of the first indication and before providing audio data to both the first external device and the second external device simultaneously, an instruction for providing input at the second external device is displayed.

8. The method according to any one of claims 1 to 2, further comprising: Receive an indication that the second external device is connected to the electronic device; as well as In response to receiving the indication that the second external device is connected to the electronic device, an indication is provided that the second external device is connected to the electronic device.

9. The method according to any one of claims 1 to 2, further comprising: When the second external device is connected to the electronic device, a third power indicator is displayed, which, when selected, disconnects the second external device from the electronic device.

10. The method of claim 9, further comprising: When the second external device is connected to the electronic device, an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition is detected, wherein in response to the indication that the physical proximity between the electronic device and the second external device meets the second proximity condition, the third power indication is displayed.

11. The method according to claim 10, wherein, Based on the determination that the second external device is not paired with the electronic device, the third power indication is displayed.

12. The method according to claim 9, wherein, The third indicator is displayed in the menu user interface.

13. An electronic device, comprising: Display devices; One or more processors; as well as The memory stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: When the electronic device is connected to a first external device via a communication link and when displaying a first user interface, wherein the electronic device is configured to provide audio data to the first external device via the communication link, the physical distance between the electronic device and the second external device is determined: Based on the determination that the physical distance between the electronic device and the second external device meets the proximity condition, the first user interface and a second user interface including a first power indicator and a second power indicator are simultaneously displayed via the display device. as well as Based on the determination that the physical distance between the electronic device and the second external device does not meet the proximity condition, the display of the second user interface including the first power indicator and the second power indicator via the display device is abandoned; When both the first user interface and the second user interface are displayed simultaneously, input is detected: Based on the determination that the input includes the selection of the first power indication, a process is initiated via a second communication link to simultaneously provide audio data to the first external device and the second external device, wherein when the second communication link is disconnected, the second external device and the electronic device are not associated. as well as Based on the determination that the input includes the selection of the second power indication, a process is initiated to provide audio data to the second external device via a third communication link, wherein the electronic device and the second external device remain associated when the third communication link is disconnected.

14. The electronic device according to claim 13, wherein, Based on the determination that the first external device is configured to receive audio data from the electronic device while the electronic device simultaneously provides audio data to the second external device, the first user interface, including the first display, is executed.

15. The electronic device according to any one of claims 13 to 14, wherein, Based on the determination that the electronic device is running an audio media application, the first user interface, which includes the first power indication, is executed.

16. The electronic device according to any one of claims 13 to 14, wherein, Based on the determination that the second external device is not paired with the electronic device, the first user interface, including the first power indication, is executed.

17. The electronic device according to any one of claims 13 to 14, wherein, The second indication means that when selected, the second external device will be paired with the electronic device.

18. The electronic device according to any one of claims 13 to 14, wherein, The second external device is configured to output audio based on the audio data from the electronic device and to connect directly and wirelessly to the electronic device.

19. The electronic device according to any one of claims 13 to 14, wherein the one or more programs further include instructions for performing the following operations: After detecting the input corresponding to the selection of the first indication and before providing audio data to both the first external device and the second external device simultaneously, an instruction for providing input at the second external device is displayed.

20. The electronic device according to any one of claims 13 to 14, wherein the one or more programs further include instructions for performing the following operations: Receive an indication that the second external device is connected to the electronic device; and In response to receiving the indication that the second external device is connected to the electronic device, an indication is provided that the second external device is connected to the electronic device.

21. The electronic device according to any one of claims 13 to 14, wherein the one or more programs further include instructions for performing the following operations: When the second external device is connected to the electronic device, a third power indicator is displayed, which, when selected, disconnects the second external device from the electronic device.

22. The electronic device of claim 21, wherein the one or more programs further include instructions for performing the following operations: When the second external device is connected to the electronic device, an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition is detected, wherein in response to the indication that the physical proximity between the electronic device and the second external device meets the second proximity condition, the third power indication is displayed.

23. The electronic device according to claim 22, wherein, Based on the determination that the second external device is not paired with the electronic device, the third power indication is displayed.

24. The electronic device according to claim 21, wherein, The third indicator is displayed in the menu user interface.

25. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs including instructions for performing the following operations: When the electronic device is connected to a first external device via a communication link and when displaying a first user interface, wherein the electronic device is configured to provide audio data to the first external device via the communication link, the physical distance between the electronic device and the second external device is determined: Based on the determination that the physical distance between the electronic device and the second external device meets the proximity condition, the first user interface and a second user interface including a first power indicator and a second power indicator are simultaneously displayed via the display device. as well as Based on the determination that the physical distance between the electronic device and the second external device does not meet the proximity condition, the display of the second user interface including the first power indicator and the second power indicator via the display device is abandoned; When both the first user interface and the second user interface are displayed simultaneously, input is detected: Based on the determination that the input includes the selection of the first power indication, a process is initiated via a second communication link to simultaneously provide audio data to the first external device and the second external device, wherein when the second communication link is disconnected, the second external device and the electronic device are not associated. as well as Based on the determination that the input includes the selection of the second power indication, a process is initiated to provide audio data to the second external device via a third communication link, wherein the electronic device and the second external device remain associated when the third communication link is disconnected.

26. The computer-readable storage medium according to claim 25, wherein, Based on the determination that the first external device is configured to receive audio data from the electronic device while the electronic device simultaneously provides audio data to the second external device, the first user interface, including the first display, is executed.

27. The computer-readable storage medium according to any one of claims 25 to 26, wherein, Based on the determination that the electronic device is running an audio media application, the first user interface, which includes the first power indication, is executed.

28. The computer-readable storage medium according to any one of claims 25 to 26, wherein, Based on the determination that the second external device is not paired with the electronic device, the first user interface, including the first power indication, is executed.

29. The computer-readable storage medium according to any one of claims 25 to 26, wherein, The second indication means that when selected, the second external device will be paired with the electronic device.

30. The computer-readable storage medium according to any one of claims 25 to 26, wherein, The second external device is configured to output audio based on the audio data from the electronic device and to connect directly and wirelessly to the electronic device.

31. The computer-readable storage medium according to any one of claims 25 to 26, wherein the one or more programs further include instructions for performing the following operations: After detecting the input corresponding to the selection of the first indication and before providing audio data to both the first external device and the second external device simultaneously, an instruction for providing input at the second external device is displayed.

32. The computer-readable storage medium according to any one of claims 25 to 26, wherein the one or more programs further include instructions for performing the following operations: Receive an indication that the second external device is connected to the electronic device; and In response to receiving the indication that the second external device is connected to the electronic device, an indication is provided that the second external device is connected to the electronic device.

33. The computer-readable storage medium according to any one of claims 25 to 26, wherein the one or more programs further include instructions for performing the following operations: When the second external device is connected to the electronic device, a third power indicator is displayed, which, when selected, disconnects the second external device from the electronic device.

34. The computer-readable storage medium of claim 33, wherein the one or more programs further include instructions for performing the following operations: When the second external device is connected to the electronic device, an indication that the physical proximity between the electronic device and the second external device meets a second proximity condition is detected, wherein in response to the indication that the physical proximity between the electronic device and the second external device meets the second proximity condition, the third power indication is displayed.

35. The computer-readable storage medium according to claim 34, wherein, Based on the determination that the second external device is not paired with the electronic device, the third power indication is displayed.

36. The computer-readable storage medium according to claim 33, wherein, The third indicator is displayed in the menu user interface.

37. An electronic device comprising: Display devices; as well as Apparatus for performing the method according to any one of claims 1 to 2.

38. A computer program product comprising one or more programs configured to be executed by one or more processors of an electronic device having a display device, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 2.

Images