Devices, Methods, and User Interfaces for Controlling Operation of Wireless Electronic Accessories

A wearable audio output device includes a first portion configured to be inserted in a user's ear and a second portion that extends from the first portion and includes one or more input devices. The wearable audio output device detects an input via the one or more input devices. In response to detecting the input, and in accordance with a determination that the input is a swipe gesture along the second portion of the wearable audio output device, the wearable audio output device adjusts an output volume for the wearable audio output device based on movement of the swipe gesture along the second portion of the wearable audio output device.

TECHNICAL FIELD

This relates generally to electronic accessories such as wearable audio output devices and accessory charging cases, including but not limited to systems for controlling wearable audio output devices with input devices, electronic accessories with physical markings, and accessory cases with speakers.

BACKGROUND

Electronic accessories, including wearable audio output devices such as headphones, earbuds, and earphones, as well as charging cases, watches, and styluses are widely used to receive inputs from and provide outputs to a user. But conventional methods of controlling and interacting with such devices are cumbersome, inefficient, and limited.

In some cases, limited control over audio outputs is given to inputs provided at the wearable audio output devices; for example, an input may be limited to having control over a single predefined feature of audio output, such as toggling power or a feature on or off In some cases, limited control over audio outputs interferes with a user's ability to control the volume of audio content being played back by the wearable audio output devices and/or control the amount of conversational sound that the user is able to hear from the surrounding physical environment while wearing the wearable audio output devices. In some cases, user interfaces for controlling the wearable audio output devices, as well as other accessory devices, do not provide users with sufficient information for the users to be able to quickly distinguish between multiple devices of the same type, such as multiple sets of earbuds or multiple charging cases.

In some cases, user interfaces for controlling audio output settings provide too few controls, for example by providing controls for only one audio output device, thus requiring a user to provide numerous inputs and navigate through different menus or user interfaces to perform a particular operation, or provide too many controls, thus cluttering the user interface and increasing the likelihood that the user will mistakenly interact with the wrong control, particularly for implementations where display area is limited.

In addition, conventional methods take longer and require more user interaction than necessary to operate the electronic accessories, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

Furthermore, accessory cases for electronic accessories have typically been configured only to charge and/or store the electronic accessories. While some electronic accessories include output mechanisms (e.g., a speaker or display), accessory cases traditionally do not include means of providing output such as audio feedback to users. Instead, feedback, if provided at all, has traditionally been supplied by other devices, such as a smart phone, tablet, or computer paired or wirelessly connected with the accessory case. Thus, conventional means of providing feedback require multiple devices and communication channels.

SUMMARY

Accordingly, there is a need for electronic accessories (e.g., wearable audio output devices and charging cases) and associated electronic devices with improved methods and interfaces for controlling and interacting with, such as adjusting volume, selecting between different audio output modes, and providing feedback to aid a user in operating such devices. Such methods and interfaces optionally complement or replace conventional methods for controlling operation of electronic accessories. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated systems and devices, such methods and interfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with user interfaces for electronic devices and accessories are reduced or eliminated by the disclosed computer systems and electronic accessories. In some embodiments, the computer system includes a desktop computer. In some embodiments, the computer system is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the computer system includes a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the computer system includes (and/or is in communication with) the wearable audio output devices (e.g., in-ear earphones, earbuds, over-ear headphones, etc.). In some embodiments, the computer system has (and/or is in communication with) a touch-sensitive surface (also known as a “touchpad”). In some embodiments, the computer system has (and/or is in communication with) a display device, which in some embodiments is a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the computer system has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, audio output device pairing and calibration, digital music/audio playing, note taking, and/or digital video playing. 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.

In accordance with some embodiments, a method is performed at a wearable audio output device that includes a first portion configured to be inserted in a user's ear and a second portion that extends from the first portion of the wearable audio output device, the second portion including one or more input devices. The method includes detecting an input via the one or more input devices; and, in response to detecting the input, in accordance with a determination that the input is a swipe gesture along the second portion of the wearable audio output device, adjusting an output volume for the wearable audio output device based on movement of the swipe gesture along the second portion of the wearable audio output device.

In accordance with some embodiments, a method is performed at an electronic device that includes or is in communication with a display generation component. The method includes detecting occurrence of a respective condition associated with an electronic accessory, distinct from the electronic device, the electronic accessory in communication with the electronic device; and, in response to detecting the occurrence of the respective condition, causing a user interface corresponding to the respective condition to be displayed via the display generation component, the user interface including a representation of the electronic accessory. Causing the user interface to be displayed includes, in accordance with a determination that the electronic accessory includes a first physical marking, causing a representation of the first physical marking to be displayed in the user interface; and, in accordance with a determination that the electronic accessory includes a second physical marking that is different from the first physical marking, causing a representation of the second physical marking to be displayed in the user interface.

In accordance with some embodiments, a method performed at an accessory charging case that includes a speaker. The method includes detecting a first event comprising a change in an opened or closed state of the accessory charging case; and, in response to detecting the change in the opened or closed state of the accessory charging case, causing the speaker to generate an audio notification corresponding to a status for at least one of the accessory charging case and one or more accessories associated with the accessory charging case.

In accordance with some embodiments, a method performed at an electronic device that is in communication with a display generation component and one or more wearable audio output devices. The method includes causing a user interface to be displayed via the display generation component, the user interface including a volume control element for the one or more wearable audio output devices; and detecting an input that corresponds to the volume control element. The method further includes, in response to detecting the input, and in accordance with a determination that the input is a first type of gesture, adjusting a volume of the audio output of the one or more wearable audio output devices. The method also includes, in response to detecting the input, and in accordance with a determination that the input is a second type of gesture, causing display of a conversation boost element for the one or more wearable audio output devices that, when selected, initiates a process for adjusting audio output of the one or more wearable audio output devices to boost conversation audio, corresponding to conversations with audio that is accessible to the one or more wearable audio output devices, relative to other audio being output by the one or more wearable audio output devices.

In accordance with some embodiments, an electronic device (e.g., a multifunction device, an electronic accessory, or electronic accessory case) includes one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions that, when executed by an electronic device cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device includes means for performing or causing performance of the operations of any of the methods described herein.

Thus, electronic devices that include or are in communication with one or more display devices, one or more input devices, one or more audio output devices, and/or one or more electronic accessories are provided with improved methods and interfaces for controlling operation of wireless electronic accessories, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for controlling operation of wireless electronic accessories.

DESCRIPTION OF EMBODIMENTS

As noted above, electronic accessories, including wearable audio output devices such as headphones, earbuds, and earphones, as well as charging cases, watches, and styluses are widely used to provide outputs to a user. Many computer systems that include or are in communication with wearable audio output devices give a user only limited control over outputs in response to inputs at the wearable audio output devices, or provide user interfaces with too few or too many output controls. The methods, systems, and user interfaces/interactions described herein improve how outputs are provided in multiple ways. For example, embodiments disclosed herein describe improved ways to control audio outputs using inputs at the wearable audio output devices and to provide improved user interfaces for controlling audio output settings.

As also noted above, electronic accessory cases are commonly passive devices used to store and/or charge electronic accessories. While some electronic accessories include output mechanisms (e.g., a speaker or display), accessory cases traditionally do not include means of providing output such as audio feedback to users. The methods, systems, and user interfaces/interactions described herein improve the functionality of an electronic accessory case. For example, embodiments disclosed herein describe improved ways of providing status information and/or feedback to a user at the electronic accessory case.

The processes described below enhance the operability of devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual, audio, and/or tactile feedback to the user, reducing the number of inputs needed to perform an operation, providing control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.

Below,FIGS.1A-1B,2, and3A-3F,4A-4Cillustrate example devices.FIGS.5A-5CBillustrate example user interfaces and device interactions for controlling the example devices.FIGS.6A-6Cillustrate a flow diagram of a process for adjusting audio output of one or more wearable audio output devices.FIGS.7A-7Cillustrate a flow diagram of a process for displaying status information of an electronic accessory.FIGS.8A-8Dillustrate a flow diagram of a process for presenting status information at an accessory charging case.FIGS.9A-9Cillustrate a flow diagram of a process for adjusting audio output of a wearable audio output device. The user interfaces and device interactions inFIGS.5A-5CBare used to illustrate the processes inFIGS.6A-6C,7A-7C,8A-8D, and9A-9C.

Example Devices

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).

In some embodiments, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, and/or the duration of the tactile output.

When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency and amplitude can be adjusted to indicate to the user that different operations have been performed. As such, tactile outputs with tactile output patterns that are designed, selected, and/or engineered to simulate characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, expansion, etc.); and/or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface that includes graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and/or a combination of any of the above) will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, tactile outputs are, optionally, generated to correspond to feedback that is unrelated to a simulated physical characteristic, such as an input threshold or a selection of an object. Such tactile outputs will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device.

In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue for the occurrence of an event of interest in a user interface or behind the scenes in a device. Examples of the events of interest include activation of an affordance (e.g., a real or virtual button, or toggle switch) provided on the device or in a user interface, success or failure of a requested operation, reaching or crossing a boundary in a user interface, entry into a new state, switching of input focus between objects, activation of a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, tactile outputs are provided to serve as a warning or an alert for an impending event or outcome that would occur unless a redirection or interruption input is timely detected. Tactile outputs are also used in other contexts to enrich the user experience, improve the accessibility of the device to users with visual or motor difficulties or other accessibility needs, and/or improve efficiency and functionality of the user interface and/or the device. Tactile outputs are optionally accompanied with audio outputs and/or visible user interface changes, which further enhance a user's experience when the user interacts with a user interface and/or the device, and facilitate better conveyance of information regarding the state of the user interface and/or the device, and which reduce input errors and increase the efficiency of the user's operation of the device.

Memory102optionally includes high-speed random-access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory102by other components of device100, such as CPU(s)120and the peripherals interface118, is, optionally, controlled by memory controller122.

In some embodiments, peripherals interface118, CPU(s)120, and memory controller122are, optionally, implemented on a single chip, such as chip104. In some other embodiments, they are, optionally, implemented on separate chips.

I/O subsystem106couples input/output peripherals on device100, such as touch-sensitive display system112and other input or control devices116, with peripherals interface118. I/O subsystem106optionally includes display controller156, optical sensor controller158, intensity sensor controller159, haptic feedback controller161, and one or more input controllers160for other input or control devices. The one or more input controllers160receive/send electrical signals from/to other input or control devices116. The other input or control devices116optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)160are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g.,208,FIG.2) optionally include an up/down button for volume control of speaker111and/or microphone113. The one or more buttons optionally include a push button (e.g.,206,FIG.2).

Touch-sensitive display system112provides an input interface and an output interface between the device and a user. Display controller156receives and/or sends electrical signals from/to touch-sensitive display system112. Touch-sensitive display system112displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.

Touch-sensitive display system112has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system112and display controller156(along with any associated modules and/or sets of instructions in memory102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system112and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system112. In some embodiments, a point of contact between touch-sensitive display system112and the user corresponds to a finger of the user or a stylus.

Touch-sensitive display system112optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system112using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

Device100optionally also includes one or more optical sensors164(e.g., as part of one or more cameras).FIG.1Ashows an optical sensor coupled with optical sensor controller158in I/O subsystem106. Optical sensor(s)164optionally include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor(s)164receive light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module143(also called a camera module), optical sensor(s)164optionally capture still images and/or video. In some embodiments, an optical sensor is located on the back of device100, opposite touch-sensitive display system112on the front of the device, so that the touch screen is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user's image is obtained (e.g., for selfies, for videoconferencing while the user views the other video conference participants on the touch screen, etc.).

Device100optionally also includes one or more contact intensity sensors165.FIG.1Ashows a contact intensity sensor coupled with intensity sensor controller159in I/O subsystem106. Contact intensity sensor(s)165optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s)165receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system112). In some embodiments, at least one contact intensity sensor is located on the back of device100, opposite touch-screen display system112which is located on the front of device100.

Device100optionally also includes one or more proximity sensors166.FIG.1Ashows proximity sensor166coupled with peripherals interface118. Alternately, proximity sensor166is coupled with input controller160in I/O subsystem106. In some embodiments, the proximity sensor turns off and disables touch-sensitive display system112when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device100optionally also includes one or more accelerometers168.FIG.1Ashows accelerometer168coupled with peripherals interface118. Alternately, accelerometer168is, optionally, coupled with an input controller160in I/O subsystem106. In some embodiments, information is displayed on the touch-screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device100optionally includes, in addition to accelerometer(s)168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device100.

In some embodiments, the software components stored in memory102include operating system126, communication module (or set of instructions)128, contact/motion module (or set of instructions)130, graphics module (or set of instructions)132, haptic feedback module (or set of instructions)133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions)136. Furthermore, in some embodiments, memory102stores device/global internal state157, as shown inFIGS.1A and3. Device/global internal state157includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch-sensitive display system112; sensor state, including information obtained from the device's various sensors and other input or control devices116; and location and/or positional information concerning the device's location and/or attitude.

Communication module128facilitates communication with other devices over one or more external ports124and also includes various software components for handling data received by RF circuitry108and/or external port124. External port124(e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a USB Type-C connector that is the same as, or similar to and/or compatible with the USB Type-C connector used in some electronic devices from Apple Inc. of Cupertino, California.

Contact/motion module130optionally detects contact with touch-sensitive display system112(in conjunction with display controller156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module130includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module130receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module130and display controller156detect contact on a touchpad.

In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.

The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).

Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have criteria that are met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).

Haptic feedback module133includes various software components for generating instructions (e.g., instructions used by haptic feedback controller161) to produce tactile outputs using tactile output generator(s)167at one or more locations on device100in response to user interactions with device100.

GPS module135determines the location of the device and provides this information for use in various applications (e.g., to telephone module138for use in location-based dialing, to camera143as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, and text input module134, contacts module137includes executable instructions to manage an address book or contact list (e.g., stored in application internal state192of contacts module137in memory102or memory370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone module138, video conference139, e-mail140, or IM141; and so forth.

In conjunction with RF circuitry108, audio circuitry110, speaker111, microphone113, touch-sensitive display system112, display controller156, contact module130, graphics module132, and text input module134, telephone module138includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.

In conjunction with RF circuitry108, audio circuitry110, speaker111, microphone113, touch-sensitive display system112, display controller156, optical sensor(s)164, optical sensor controller158, contact module130, graphics module132, text input module134, contact list137, and telephone module138, videoconferencing module139includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry108, touch-sensitive display system112, display controller156, contact module130, graphics module132, and text input module134, the instant messaging module141includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

In conjunction with RF circuitry108, touch-sensitive display system112, display controller156, contact module130, graphics module132, text input module134, GPS module135, map module154, and video and music player module152, workout support module142includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

In conjunction with touch-sensitive display system112, display controller156, optical sensor(s)164, optical sensor controller158, contact module130, graphics module132, and image management module144, camera module143includes executable instructions to capture still images or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete a still image or video from memory102.

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, text input module134, and camera module143, image management module144includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry108, touch-sensitive display system112, display controller156, contact module130, graphics module132, text input module134, e-mail client module140, and browser module147, calendar module148includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry108, touch-sensitive display system112, display controller156, contact module130, graphics module132, text input module134, and browser module147, the widget creator module150includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, and text input module134, search module151includes executable instructions to search for text, music, sound, image, video, and/or other files in memory102that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, audio circuitry110, speaker111, RF circuitry108, and browser module147, video and music player module152includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system112, or on an external display connected wirelessly or via external port124). In some embodiments, device100optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, and text input module134, notes module153includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry108, touch-sensitive display system112, display controller156, contact module130, graphics module132, text input module134, GPS module135, and browser module147, map module154includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

In conjunction with touch-sensitive display system112, display controller156, contact module130, graphics module132, audio circuitry110, speaker111, RF circuitry108, text input module134, e-mail client module140, and browser module147, online video module155includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on touch-sensitive display system112, or on an external display connected wirelessly or via external port124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module141, rather than e-mail client module140, is used to send a link to a particular online video.

Hit view determination module172provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system112displays more than one view. Views are made up of controls and other elements that a user can see on the display.

FIG.3Ais a block diagram of an example multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device300need not be portable. In some embodiments, device300is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device300typically includes one or more processing units (CPU's)310, one or more network or other communications interfaces360, memory370, and one or more communication buses320for interconnecting these components. Communication buses320optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device300includes input/output (I/O) interface330comprising display340, which is typically a touch-screen display. I/O interface330also optionally includes a keyboard and/or mouse (or other pointing device)350and touchpad355, tactile output generator357for generating tactile outputs on device300(e.g., similar to tactile output generator(s)167described above with reference toFIG.1A), sensors359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)165described above with reference toFIG.1A). In some embodiments, device300includes a wireless interface311for communication with one or more wearable audio output devices301and/or an electronic accessory case342(e.g.,FIG.3E). In some embodiments, device300includes a network communications interface360for communication with remote devices (e.g., in conjunction with communication module128).

Memory370includes high-speed random-access memory, such as DRAM, SRAM, DDR RAM or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory370optionally includes one or more storage devices remotely located from CPU(s)310. In some embodiments, memory370stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory102of portable multifunction device100(FIG.1A), or a subset thereof. Furthermore, memory370optionally stores additional programs, modules, and data structures not present in memory102of portable multifunction device100. For example, memory370of device300optionally stores drawing module380, presentation module382, word processing module384, website creation module386, disk authoring module388, and/or spreadsheet module390, while memory102of portable multifunction device100(FIG.1A) optionally does not store these modules.

FIG.3Billustrates physical features of an example wearable audio output device301in accordance with some embodiments. In some embodiments, the wearable audio output device301is one or more in-ear earphone(s), earbud(s), over-ear headphone(s), or the like. In the example ofFIG.3B, wearable audio output device301is an earbud. In some embodiments, wearable audio output device301includes a head portion303and a stem portion305. In some embodiments, head portion303is configured to be inserted into a user's ear. In some embodiments, stem portion305physically extends from head portion303(e.g., is an elongated portion extending from head portion303). For example, head portion303physically extends downward, in front of, and/or past a user's earlobe while head portion303is inserted into a user's ear.

In some embodiments, wearable audio output device301includes one or more audio speakers306(e.g., in head portion303) for providing audio output (e.g., to a user's ear). In some embodiments, wearable audio output device301includes one or more placement sensors304(e.g., placement sensors304-1and304-2in head portion303) to detect positioning or placement of wearable audio output device301relative to a user's ear, such as to detect placement of wearable audio output device301in a user's ear.

In some embodiments, wearable audio output device301includes one or more microphones302for receiving audio input. In some embodiments, one or more microphones302are included in head portion303(e.g., microphone302-1). In some embodiments, one or more microphones302are included in stem portion305(e.g., microphone302-2). In some embodiments, microphone(s)302detect speech from a user wearing wearable audio output device301and/or ambient noise around wearable audio output device301. In some embodiments, multiple microphones of microphones302are positioned at different locations on wearable audio output device301to measure speech and/or ambient noise at different locations around wearable audio output device301.

In some embodiments, wearable audio output device301includes one or more input devices308(e.g., in stem portion305). In some embodiments, input device(s)308includes a pressure-sensitive (e.g., intensity-sensitive) input device. In some embodiments, the pressure-sensitive input device detects inputs from a user in response to the user squeezing the input device (e.g., by pinching stem portion305of wearable audio output device301between two fingers). In some embodiments, input device(s)308include a touch-sensitive surface (e.g., a capacitive sensor) for detecting touch inputs, accelerometer(s), and/or attitude sensor(s) (e.g., for determining an attitude of wearable audio output device301relative to a physical environment and/or changes in attitude of the device), and/or other input device by which a user can interact with and provide inputs to wearable audio output device301. In some embodiments, input device(s)308include one or more capacitive sensors, one or more force sensors, one or more motion sensors, and/or one or more orientation sensors.FIG.3Bshows input device(s)308at a location in stem portion305, however in some embodiments one or more of input device(s)308are located at other positions within wearable audio output device301(e.g., other positions within stem portion305and/or head portion303). In some embodiments, wearable audio output device301includes a housing with one or more physically distinguished portions307at locations that correspond to input device(s)308(e.g., to assist a user in locating and/or interacting with input device(s)308). In some embodiments, physically distinguished portion(s)307include indent(s), raised portion(s), and/or portions with different textures. In some embodiments, physically distinguished portion(s)307include a single distinguished portion that spans multiple input devices308. For example, input devices308include a set of touch sensors configured to detect swipe gestures and a single distinguished portion (e.g., a depression or groove) spans the set of touch sensors. In some embodiments, physically distinguished portion(s)307include a respective distinguished portion for each input device of input device(s)308.

FIG.3Cis a block diagram of an example wearable audio output device301in accordance with some embodiments. In some embodiments, wearable audio output device301is one or more in-ear earphone(s), earbud(s), over-ear headphone(s), or the like. In some examples, wearable audio output device301includes a pair of earphones or earbuds (e.g., one for each of a user's ears). In some examples, wearable audio output device301includes over-ear headphones (e.g., headphones with two over-ear earcups to be placed over a user's ears and optionally connected by a headband). In some embodiments, wearable audio output device301includes one or more audio speakers306for providing audio output (e.g., to a user's ear). In some embodiments, wearable audio output device301includes one or more placement sensors304to detect positioning or placement of wearable audio output device301relative to a user's ear, such as to detect placement of wearable audio output device301in a user's ear. In some embodiments, wearable audio output device301conditionally outputs audio based on whether wearable audio output device301is in or near a user's ear (e.g., wearable audio output device301forgoes outputting audio when not in a user's ear, to reduce power usage). In some embodiments where wearable audio output device301includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones, earbuds, or earcups), each component includes one or more respective placement sensors, and wearable audio output device301conditionally outputs audio based on whether one or both components is in or near a user's ear, as described herein. In some embodiments, wearable audio output device301furthermore includes an internal rechargeable battery309for providing power to the various components of wearable audio output device301.

In some embodiments, wearable audio output device301includes audio I/O logic312, which determines the positioning or placement of wearable audio output device301relative to a user's ear based on information received from placement sensor(s)304, and, in some embodiments, audio I/O logic312controls the resulting conditional outputting of audio. In some embodiments, wearable audio output device301includes a wireless interface315for communication with one or more multifunction devices, such as device100(FIG.1A) or device300(FIG.3A), and electronic accessory case342(see FIG.3E). In some embodiments, interface315includes a wired interface for connection with a multifunction device, such as device100(FIG.1A) or device300(FIG.3A) (e.g., via a headphone jack or other audio port). In some embodiments, a user can interact with and provide inputs (e.g., remotely) to wearable audio output device301via interface315. In some embodiments, wearable audio output device301is in communication with multiple devices (e.g., multiple multifunction devices, and/or an audio output device case), and audio I/O logic312determines, which of the multifunction devices from which to accept instructions for outputting audio.

In some embodiments, wearable audio output device301includes one or more microphones302for receiving audio input. In some embodiments where wearable audio output device301includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones or earbuds), each component includes one or more respective microphones. In some embodiments, audio I/O logic312detects or recognizes speech or ambient noise based on information received from microphone(s)302.

In some embodiments, wearable audio output device301includes one or more input devices308. In some embodiments where wearable audio output device301includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones, earbuds, or earcups), each component includes one or more respective input devices. In some embodiments, input device(s)308include one or more volume control hardware elements (e.g., an up/down button for volume control, or an up button and a separate down button, as described herein with reference toFIG.1A) for volume control (e.g., locally) of wearable audio output device301. In some embodiments, inputs provided via input device(s)308are processed by audio I/O logic312. In some embodiments, audio I/O logic312is in communication with a separate device (e.g., device100,FIG.1A, or device300,FIG.3A) that provides instructions or content for audio output, and that optionally receives and processes inputs (or information about inputs) provided via microphone(s)302, placement sensor(s)304, and/or input device(s)308, or via one or more input devices of the separate device. In some embodiments, audio I/O logic312is located in device100(e.g., as part of peripherals interface118,FIG.1A) or device300(e.g., as part of I/O interface330,FIG.3A), instead of device301, or alternatively is located in part in device100and in part in device301, or in part in device300and in part in device301.

FIG.3Dillustrates physical features of an example electronic accessory case342in accordance with some embodiments. In some embodiments, electronic accessory case342includes a lid367and a container369. In some embodiments, electronic accessory case342includes one or more sensors to detect if lid367is opened, closed, and/or moving. In some embodiments, electronic accessory case342is configured to house and/or charge one or more electronic accessories, such as headphones, a smartwatch, an electronic stylus, a fitness tracker, and/or earbuds. In some embodiments, electronic accessory case342includes one or more audio output devices (e.g., speaker(s)345) (e.g., to providing status and/or event information to a user). In some embodiments, electronic accessory case342includes one or more input device(s).

FIG.3Eis a block diagram illustrating an electronic accessory case342in accordance with some embodiments. In some embodiments, electronic accessory case342a headphone case (e.g., a wireless headphone case). In some embodiments, electronic accessory case342an accessory charging case configured to charge one or more accessories while the accessories are positioned (e.g., mounted, inserted, and/or attached) to the accessory charging case. Electronic accessory case342includes memory349(which optionally includes one or more computer readable storage mediums), one or more processing units (CPUs)343, and peripherals interface344. In some embodiments, peripherals interface344includes one or more speakers345, one or more input devices346(e.g., one or more buttons, switches, and/or levers), and one or more communication components348(e.g., a wireless interface) for communicating with devices such as one or more wearable audio output devices301, and one or more electronic devices such as a smart phone, tablet, computer or the like. In some embodiments, peripherals interface344includes a set of LEDs and/or display elements capable of displaying icons and/or other visual information. In some embodiments, peripherals interface344includes one or more tactile output generators347for generating tactile outputs (also called haptic feedback), e.g., via an external case362(also called the housing) of the electronic accessory case342.

In accordance with some embodiments, electronic accessory case342includes an internal rechargeable battery363for providing power to the various components of electronic accessory case342, as well as for charging the internal battery309(FIG.3B) of one or more wearable audio output devices301. In some embodiments, electronic accessory case342includes a battery charger364for charging internal battery363when battery charger364is connected to an external power source via a power connect port365. In some embodiments, the internal battery363and/or battery charger364are configured to charge the internal battery309(FIG.3B) of an audio output device (e.g., headphone or earbud) when the audio output device is connected to (e.g., properly positioned in) an accessory charger366. These components optionally communicate over one or more communication buses or signal lines341.

In some embodiments, external case362, when closed (e.g., seeFIG.4C), has an extent (e.g., width or height) in a first dimension of between 1.5 and 3 inches, an extent (e.g., height or width) in a second dimension of between 1 and 2.5 inches, and an extent in a third dimension (e.g., depth) of between 0.5 and 1 inch.

In some embodiments, the software components stored in memory349include operating system351(or a BIOS), communication module (or set of instructions)352, an input module (or set of instructions)353, graphics module (or set of instructions)354, haptic feedback module (or set of instructions)356, and headphone control module(s)358. Furthermore, in some embodiments, memory349stores a device/global internal state361, which includes one or more of: active application state, indicating which applications, if any, are currently active; and sensor state, including information obtained from the device's various sensors and other input devices346.

FIG.3Fillustrates example audio control by a wearable audio output device301in accordance with some embodiments. While the following example is explained with respect to implementations that include a wearable audio output device having earbuds to which interchangeable eartips (sometimes called silicon eartips or silicon seals) are attached, the methods, devices and user interfaces described herein are equally applicable to implementations in which the wearable audio output devices do not have eartips, and instead each have a portion of the main body shaped for insertion in the user's ears. In some embodiments, when a wearable audio output device having earbuds to which interchangeable eartips may be attached are worn in a user's ears, the earbuds and eartips together act as physical barriers that block at least some ambient sound from the surrounding physical environment from reaching the user's ear. For example, inFIG.3F, wearable audio output device301is worn by a user such that head portion303and eartip314are in the user's left ear. Eartip314extends at least partially into the user's ear canal. Preferably, when head portion303and eartip314are inserted into the user's ear, a seal is formed between eartip314and the user's ear so as to isolate the user's ear canal from the surrounding physical environment. However, in some circumstances, head portion303and eartip314together block some, but not necessarily all, of the ambient sound in the surrounding physical environment from reaching the user's ear. Accordingly, in some embodiments, a first microphone (or, in some embodiments, a first set of one or more microphones)302-1(and optionally a third microphone302-3) is located on wearable audio output device301so as to detect ambient sound, represented by waveform322, in region316of a physical environment surrounding (e.g., outside of) head portion303. In some embodiments, a second microphone (or, in some embodiments, a second set of one or more microphones)302-2(e.g., of microphones302,FIG.3C) is located on wearable audio output device301so as to detect any ambient sound, represented by waveform324, that is not completely blocked by head portion303and eartip314and that can be heard in region318inside the user's ear canal. Accordingly, in some circumstances in which wearable audio output device301is not producing a noise-cancelling (also called “antiphase”) audio signal to cancel (e.g., attenuate) ambient sound from the surrounding physical environment, as indicated by waveform326-1, ambient sound waveform324is perceivable by the user, as indicated by waveform328-1. In some circumstances in which wearable audio output device301is producing an antiphase audio signal to cancel ambient sound, as indicated by waveform326-2, ambient sound waveform324is not perceivable by the user, as indicated by waveform328-2.

In some embodiments, ambient sound waveform322is compared to attenuated ambient sound waveform324(e.g., by wearable audio output device301or a component of wearable audio output device301, such as audio I/O logic312, or by an electronic device that is in communication with wearable audio output device301) to determine the passive attenuation provided by wearable audio output device301. In some embodiments, the amount of passive attenuation provided by wearable audio output device301is taken into account when providing the antiphase audio signal to cancel ambient sound from the surrounding physical environment. For example, antiphase audio signal waveform326-2is configured to cancel attenuated ambient sound waveform324rather than unattenuated ambient sound waveform322.

In some embodiments, wearable audio output device301is configured to operate in one of a plurality of available audio output modes, such as an active noise control audio output mode, an active pass-through audio output mode, and a bypass audio output mode (also sometimes called a noise control off audio output mode). In the active noise control mode (also called “ANC”), wearable audio output device301outputs one or more audio-cancelling audio components (e.g., one or more antiphase audio signals, also called “audio-cancelation audio components”) to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. In the active pass-through audio output mode, wearable audio output device301outputs one or more pass-through audio components (e.g., plays at least a portion of the ambient sound from outside the user's ear, received by microphone302-1, for example) so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., a greater amount of ambient sound than would be audible with the passive attenuation of wearable audio output device301placed in the user's ear). In the bypass mode, active noise management is turned off, such that wearable audio output device301outputs neither any audio-cancelling audio components nor any pass-through audio components (e.g., such that any amount of ambient sound that the user perceives is due to physical attenuation by wearable audio output device301).

Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device100.

It should be noted that the icon labels illustrated inFIG.4Aare merely examples. For example, other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental recognition of deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.

FIG.4Cillustrates physical features of an example wireless accessory case480(e.g., an electronic accessory case, such as electronic accessory case342,FIG.3E) that includes a physical marking482(e.g., an engraving, embossing, and/or printed, painted, or otherwise applied marking). The descriptions provided with respectFIGS.3D and3Eare applicable to wireless accessory case480described herein. Wireless accessory case480is in wireless communication with (e.g., paired with) wearable audio output devices301-1and301-2, an audio source, and/or a display device (e.g., multifunction device100). In accordance with some embodiments, wearable audio output devices301inFIG.4Cinclude physical markings484(e.g., physical marking484-1on wearable audio output device301-1and physical marking484-2on wearable audio output device301-2). In some embodiments, wireless accessory case480is configured to charge (e.g., charge internal batteries of) wearable audio output devices301when wearable audio output devices301are positioned inside wireless accessory case480. In some embodiments, wireless accessory case480includes a battery (e.g., battery363,FIG.3E) for charging internal batteries (e.g., battery309,FIG.3C) of wearable audio output devices301and for powering functions of wireless accessory case480while the wireless accessory case480is not connected to an external power source. In some embodiments, as illustrated inFIG.4C, wireless accessory case480has a hinged lid486to encase wearable audio output devices301while they are inside the wireless accessory case480and/or charging. In accordance with some embodiments, a frontside of the accessory case480includes apertures(s) for speaker(s)345, an input device346, physical marking482, and a divot488for easing opening and closing of the hinged lid486. In some embodiments, one or more of speaker(s)345, input device346, physical marking482are located on a different portion of wireless accessory case480(e.g., on a backside, top, and/or bottom). Further, althoughFIG.4Cillustrates wearable audio output devices301positioned within wireless accessory case480with respective eartips facing away from one another (e.g., facing outward), in some embodiments, wearable audio output devices301are positioned (e.g., mounted and/or coupled) differently within wireless accessory case480(e.g., with eartips facing toward one another). For example, wireless accessory case480optionally only charges wearable audio output devices301while wearable audio output devices301are positioned in a particular orientation within wireless accessory case480.

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device100, device300, wearable audio output devices301, electronic accessory case342, and/or wireless accessory case480.

FIGS.5A-5Dillustrate example user interfaces for pairing electronic accessories in accordance with some embodiments.FIGS.5E-5Rillustrate example user interfaces and user interactions for adjusting the audio output of wearable audio output devices in accordance with some embodiments.FIGS.5S-5BIillustrate example user interfaces and user interactions for various features associated with an electronic accessory case in accordance with some embodiments.FIGS.5BJ-5CBillustrate example user interfaces and user interactions for adjusting the audio output of wearable audio output devices in accordance with some embodiments. The user interfaces and device interactions in these figures are used to illustrate the processes described below, including the processes inFIGS.6A-6C,7A-7C,8A-8D, and9A-9C. For convenience of explanation, some of the embodiments will be discussed with reference to operations performed on a device with a touch-sensitive display system112. In such embodiments, the focus selector is, optionally: a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., a centroid of a respective contact or a point associated with a respective contact), or a centroid of two or more contacts detected on the touch-sensitive display system112. However, analogous operations are, optionally, performed on a device with a display450and a separate touch-sensitive surface451in response to detecting the contacts on the touch-sensitive surface451while displaying the user interfaces shown in the figures on the display450, along with a focus selector. Additionally, analogous operations are, optionally, performed on a device in communication with a display generation component (e.g., a wireless display device) that is separate from the device.

FIGS.5A-5Dillustrate example user interfaces for pairing electronic accessories in accordance with some embodiments.

FIG.5Aillustrates user interface400on touch-sensitive display system112of device100. In some embodiments, (e.g., while displaying user interface400) device100periodically and repeatedly listens for wireless broadcast signals (e.g., pairing requests) from one or more peripherals (e.g., wearable audio output devices301-1and301-2as well as wireless accessory case480) to pair the peripheral(s) with device100. In some embodiments, as illustrated throughoutFIGS.5A-5D, device100can detect pairing requests from peripherals when the peripheral is within threshold distance502of device100and cannot detect pairing requests from peripherals when the peripheral is outside of threshold distance502. For example, at the bottom ofFIG.5A,FIG.5Aillustrates an example spatial relationship (e.g., physical distance) between device100and wearable audio output devices301-1and301-2as well as wireless accessory case480, where wearable audio output devices301-1and301-2as well as wireless accessory case480are outside of threshold distance502of device100. In contrast,FIG.5Billustrates wearable audio output devices301-1and301-2as well as wireless accessory case480(illustrated and hereinafter referred to collectively as earbud set503) are within threshold distance502of device100, where the device is capable of detecting pairing requests from the peripherals.

FIG.5Billustrates an example user interface504(e.g., a window), displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to detecting movement of a peripheral (e.g., wearable audio output device301-1) or set of peripherals (e.g., earbud set503), from outside of threshold distance502to within threshold distance502, for initiating pairing of device100with the peripheral (e.g., wearable audio output device301-1) or set of peripherals (e.g., earbud set503). InFIG.5B, device100detects a pairing request from a peripheral (e.g., wearable audio output device301-1, which is shown inFIG.5Aand part of earbud set503inFIG.5B) within threshold distance502. In some embodiments, in response to detecting the pairing request from wearable audio output device301-1, device100determines whether wearable audio output device301-1meets coupling criteria. In the example shown inFIG.5B, coupling criteria is met when an earbud (e.g., wearable audio output device301-1) is placed within and/or is electrically coupled to an earbud case (e.g., wireless accessory case480) (e.g., to form earbud set503). After device100determines that wearable audio output device301-1meets coupling criteria (e.g., in response to device100determining that wearable audio output device301-1meets the coupling criteria), device100displays window504-1overlaid on user interface400ofFIG.5A. Window504-1includes a representation505of earbud set503and button507(labeled “Connect”), which, when activated by a user input, initiates pairing of device100with the peripherals (e.g., wearable audio output devices301-1and301-2and wireless accessory case480shown inFIG.5A) of earbud set503. Window504-1further includes a representation506of physical marking482on wireless accessory case480. In some embodiments, the user interface(s) shown in window504-1are instead displayed on the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of touch-sensitive display system112. Device100also displays an exit button508that, when activated by a user input, such as a tap gesture, causes window504-1to cease to be displayed so that the user can perform other operations on device100. In some embodiments, where exit button508accompanies another user interface described herein (e.g., a user interface that is part of a usage tutorial), exit button508, when activated by a user input, causes that user interface to cease to be displayed.

FIGS.5C-5Dillustrate transitions fromFIG.5B. In particular,FIG.5Cshows input510(e.g., a tap gesture) on button507in window504-1. In response to detecting input510, device100initiates pairing of device100with the peripherals of earbud set503. InFIG.5D, after device100has paired with the peripherals of earbud set503, device100displays an indication512(labeled “Connected”) in window504-2to indicate that device100is paired with (e.g., communicatively connected to) earbud set503. In some embodiments, device100displays, in window504-2, a button that, when activated, causes device100to proceed from the pairing process to a usage tutorial for wearable audio output devices301.

FIGS.5E-5Rillustrate example user interfaces and user interactions for adjusting the audio output of wearable audio output devices in accordance with some embodiments.FIGS.5E and5Fillustrate example user interface514showing available user interactions for wearable audio output devices301. In particular,FIG.5Eshows user interface514-1with representations513of wearable audio output devices and illustrations of a user gesture517(e.g., a swipe along stem portion305away from head portion303, seeFIG.3B) for decreasing volume of audio output at wearable audio output devices301.FIG.5Fshows user interface514-2with representations513of wearable audio output devices and illustrations of a user gesture519(e.g., a swipe along stem portion305toward head portion303) for increasing volume of audio output at wearable audio output devices301. In the example ofFIGS.5E and5F, the representations513of the wearable audio output devices include representations515of physical markings484(e.g.,FIG.4C) on wearable audio output devices301.

FIGS.5G-5Rillustrate example user interactions with wearable audio output devices301to control audio outputs in accordance with some embodiments.FIG.5Gshows wearable audio output devices301-1and301-2inserted in respective ears516-1and516-2of a user and having respective output volume levels518-1and518-2. For example, wearable audio output devices301are configured to play back audio content via respective speakers306(e.g.,FIG.3B) with output volume levels518.

In some embodiments, each of wearable audio output devices301include a stem portion305that the user can use to provide inputs to the wearable audio output devices (e.g., described with reference toFIG.3B). In some embodiments, stem portion305is or includes input device(s) (e.g., input devices308) that respond to user inputs applied to stem portion305. In some embodiments, the input device(s) include a touch-sensitive input device that responds to touch inputs applied to stem portion305, such as finger touches as illustrated inFIG.5H. In some embodiments, the input device(s) include a pressure-sensitive input device that responds to press inputs applied to stem portion305when held and squeezed between two fingers as illustrated inFIG.5O. Although only one wearable audio output device is shown inFIG.5H, one of ordinary skill will recognize that wearable audio output device301-1can have an analogous structure with a corresponding stem, and that the same functionality described herein with reference to wearable audio output device301-2may be available using wearable audio output device301-1and its corresponding stem as well.

FIGS.5H-5Iillustrate an input520received at stem portion305of wearable audio output device301-2. Input520has an initial location of520-aand an ending location of520-b. For example, input520is a swipe gesture toward head portion303detected based on a determination that the user's finger contact movement is greater than a predefined magnitude. In some embodiments, stem portion305includes a set of capacitive sensors arranged to detect movement of a contact along a length of stem portion305. In some embodiments, stem portion305includes a housing with one or more physically distinguished portions at locations corresponding to the set of capacitive sensors (e.g., to guide the user's finger during the movement). In some embodiments, a user's finger contact movement that is less than the predefined magnitude does not change the volume of the audio output; e.g., the user's finger contact movement is ignored if the amount of the user's finger contact movement is less than the predefined magnitude.

FIG.5Jillustrates a transition fromFIG.5Gin response to input520. In response to input520(e.g., and in accordance with a determination that input520is a swipe gesture moving toward head portion303), wearable audio output devices301adjust a volume of audio output to respective output levels522-1and522-2. In some embodiments, audio feedback524is provided at each wearable audio output device301as the volume of audio output is adjusted (e.g., an audible tone is output to indicate an increase in volume level). In some embodiments, audio feedback524is adjusted based on one or more characteristics of input520(e.g., a speed of the swipe gesture and/or a distance of the swipe gesture). In some embodiments, audio feedback524includes a quantity of tones that corresponds to an amount of volume change due to input520(e.g., a tone for each increment of volume level change). In some embodiments, audio feedback is provided (e.g., the same or different from audio feedback524) to indicate to a user that output volume is at a maximum or minimum level (e.g., as defined in software of wearable audio output devices301). In some embodiments, wearable audio output device301includes one or more tactile output generators, optionally located in stem portion305. In some such embodiments, an activation tactile output is output to indicate a detection of input520.

FIGS.5K-5Lillustrate an input526received at stem portion305of wearable audio output device301-1. Input526has an initial location of526-aand an ending location of526-b. For example, input526is a swipe gesture away from head portion303detected based on a determination that the user's finger contact movement is greater than a predefined magnitude.

FIG.5Millustrates a transition fromFIG.5Jin response to input526. In response to input526(e.g., and in accordance with a determination that input526is a swipe gesture moving away from head portion303), wearable audio output devices301adjust a volume of audio output to respective output levels528-1and528-2. In some embodiments, audio feedback530is provided at each wearable audio output device301(e.g., an audible tone is output to indicate a decrease in volume level). In some embodiments, audio feedback530includes a quantity of tones that corresponds to an amount of volume change due to input526(e.g., a tone for each increment of volume level change). In some embodiments, audio feedback530is different from audio feedback524(e.g., so that a user can distinguish between volume increases and volume decreases).

FIG.5Nshows wearable audio output devices301-1and301-2inserted in respective ears516-1and516-2of a user. For example, wearable audio output devices301are configured to play back audio content via respective speakers306.FIG.5Nalso shows an example user interface532that includes a representation of an album531(e.g., an album having audio content) and audio playback controls such as a previous button for moving to the previous track or rewinding the audio being played, a play/pause button533for toggling audio playback between on and off, and a next button for moving to the next track or fast forwarding through the audio being played. In accordance with some embodiments, a volume control is also concurrently displayed with (e.g., below) the audio playback controls. In the example ofFIG.5N, play back of media content from album531is paused, as indicated by display of play button533. In some embodiments, user interface532is presented at an electronic device (e.g., multifunction device100or device300) that is communicatively coupled to wearable audio output devices301. In some embodiments, the functionality associated with user interface532is available to the user via inputs and/or gestures at wearable audio output devices301(e.g., regardless of whether user interface532is presented to the user).

FIG.5Oillustrates an input534received at stem portion305of wearable audio output device301-1. Input534is a different type of input from input526, e.g., a non-swipe gesture, such as a tap (e.g., an input having a contact duration that is less than a threshold duration), press (e.g., an input having a contact intensity that is less than a threshold intensity), and/or squeeze gesture.FIG.5Pillustrates a transition fromFIG.5Nin response to input534. In response to input534(e.g., and in accordance with a determination that input534is a single squeeze gesture), playback of the media content from album531is active (e.g., unpaused and playing), as indicated by pause button535being displayed inFIG.5Pinstead of play button533(FIG.5N). In some embodiments, audio feedback536is provided at wearable audio output device301-1. For example, audio feedback536is provided at the wearable audio output device where input534is detected and is not provided at the other wearable audio output device. In some embodiments, audio feedback536includes one or more words (e.g., the term “unpaused” or “playing”). In some embodiments, audio feedback536includes one or more tones and/or beeps. In some embodiments, audio feedback536is different from audio feedback530and audio feedback524(e.g., so that a user can distinguish between volume changes and play back changes).

FIG.5Qillustrates an input538received at stem portion305of wearable audio output device301-1. Input538is a different type of input from input534, e.g., a long press input (e.g., an input having a contact duration that is greater than a threshold duration), a deep press input (e.g., an input having a contact intensity that is greater than a threshold intensity), and/or a long (and/or deep) squeeze input (e.g., a squeeze gesture that includes a squeeze of stem portion305that is maintained for at least a threshold amount of time).

FIG.5Rillustrates a transition fromFIG.5Pin response to input538. In response to input538(e.g., and in accordance with a determination that input538is a long press and/or long squeeze gesture), wearable audio output devices301enable (e.g., switch to or activate) an active pass-through mode (also sometimes called a transparency mode). In the active pass-through audio output mode, wearable audio output device301outputs one or more pass-through audio components (e.g., plays at least a portion of the ambient sound from outside the user's ear, received by microphone302-1, for example) so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., a greater amount of ambient sound than would be audible with the passive attenuation of wearable audio output device301placed in the user's ear). In some embodiments, a squeeze gesture is a gesture that involves pressing something (e.g., stem portion305) between two or more fingers. In some embodiments, a squeeze is maintained for less than a threshold amount of time (e.g., 0.5 seconds, 1 second, 1.5 seconds, or 2 seconds). In some embodiments, a long squeeze gesture is a squeeze gesture that is maintained for at least the threshold amount of time.

In some embodiments, in combination with changing output mode, wearable audio output device301-1outputs an audible tone and/or one or more words, e.g., audio feedback540, to indicate that the audio output mode has been changed. In some embodiments, wearable audio output devices301transition from a bypass mode or ANC (active noise cancelation) mode to the active pass-through mode in response to input538. In some embodiments, wearable audio output devices301transition between modes to a next audio output mode in a predefined order, which in this example is the active pass-through mode, as indicated by audio feedback540. In some embodiments, the predefined order of audio output modes is configurable using a settings menu.

In some embodiments, wearable audio output device301includes one or more tactile output generators, optionally located in stem portion305. In some such embodiments, tactile outputs are output to indicate detection of user inputs and/or activation of functions of wearable audio output device301, e.g., in addition to, or alternatively to, providing audio feedback. In some embodiments, the tactile outputs for different functions and/or user inputs have different tactile output amplitudes, frequencies, and/or patterns (e.g., so the user can differentiate between detection of different user inputs and/or activation of different functions).

FIGS.5S-5BIillustrate example user interfaces and user interactions for various features associated with an electronic accessory case in accordance with some embodiments.

FIG.5Sillustrates an example spatial relationship (e.g., physical distance) between device100and wireless accessory cases480-1,480-2, and480-3, where wireless accessory cases480-1,480-2, and480-3are inside of threshold distance502of device100, e.g., where device100is capable of detecting pairing requests from peripherals and other devices. In the example ofFIG.5S, wireless accessory case480-1includes a physical marking482-1, wireless accessory case480-2includes a physical marking482-2that is different from physical marking482-1, and wireless accessory case480-3does not include a physical marking (e.g., a personalized physical marking such as a digital engraving and/or embossing).

FIG.5Tillustrates an example user interface, e.g., displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to detecting a pairing request from wireless accessory case480-1for initiating pairing of device100with wireless accessory case480-1. InFIG.5T, device100detects a pairing request from wireless accessory case480-1while within threshold distance502. Device100displays window504-1overlaid on user interface400ofFIG.5A. Window504-1includes a representation542-1of wireless accessory case480-1and button507(labeled “Connect”). Window504-1further includes a representation544-1of physical marking482-1on wireless accessory case480-1. In some embodiments, representation542-1is a three-dimensional representation of wireless accessory case480-1. In some embodiments, representation542-1includes one or more animated movements (e.g., rotating, shifting, and/or lateral movement) as indicated by arrows543. In some embodiments, representation542-1is movable by a user (e.g., in response to detection of swipe or drag gestures at window504-1.

FIG.5Uillustrates an example user interface, e.g., displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to detecting a pairing request from wireless accessory case480-2for initiating pairing of device100with wireless accessory case480-2. InFIG.5U, device100detects a pairing request from wireless accessory case480-2while within threshold distance502. Device100displays window504-1overlaid on user interface400ofFIG.5A. Window504-1includes a representation542-2of wireless accessory case480-2and button507. Window504-1further includes a representation544-2of physical marking482-2on wireless accessory case480-2. In this way, representations544-1and544-2enable or help a user to distinguish between wireless accessory case480-1and wireless accessory case480-2.

FIG.5Villustrates an example user interface, e.g., displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to detecting a pairing request from wireless accessory case480-3for initiating pairing of device100with wireless accessory case480-3. InFIG.5V, device100detects a pairing request from wireless accessory case480-3while within threshold distance502. Device100displays window504-1overlaid on user interface400ofFIG.5A. Window504-1includes a representation542-3of wireless accessory case480-3and button507. Wireless accessory case480-3does not include a physical marking482and, accordingly, window504-1does not include a representation544of a physical marking.

FIG.5Willustrates an example user interface550for adding a physical marking to an electronic accessory (e.g., a wireless accessory case480). In some embodiments, the electronic accessory is a set of headphones, a smart watch, a findable electronic device, a stylus, or an accessory case. In some embodiments, the physical marking is, or includes, an engraving, an embossing, and/or printed, painted, or otherwise applied, markings. In some embodiments, user interface550is presented to a user as part of a purchase (or update) process for the electronic accessory. User interface550includes a representation552of an electronic accessory including a preview554of a physical marking selected (e.g., inputted or accepted) by a user. User interface550further includes an input section556to accept user inputs such as inputs558(e.g., text and/or selection(s) from section560(e.g., emojis and/or symbols), a button562(labeled “Save”) that, when activated by a user input, saves and/or confirms inputs558as a physical marking for the electronic accessory, and a button564(labeled “Cancel”) that, when activated by a user input, removes inputs558and/or closes user interface550(e.g., returns to a previous user interface or advances to a new or next user interface). In some embodiments, user interface550includes an option (e.g., a button or other affordance) that, when activated by a user, changes a font for text inputs. In some embodiments, user interface550includes an option (e.g., a button or other affordance) that, when activated by a user, allows a user to input handwritten inputs (e.g., a signature, handwritten text, and/or a drawing).

FIG.5Xshows wireless accessory case480and associated wearable audio output devices301within a threshold distance of device100. Wireless accessory case480inFIG.5Xincludes speaker(s)345(e.g., and associated apertures) and a physical marking574. Device100includes a user interface570(e.g., a lock and/or sign-in screen). Wireless accessory case480is open (e.g., lid367is up) inFIG.5Xand wearable audio output devices301are inserted in case480.

FIG.5Yillustrates a transition fromFIG.5Xin response to an occurrence of a condition associated with wireless accessory case480(e.g., a closure of lid367). In response to closure of lid367, wearable audio output devices301begin charging, audio feedback585is optionally provided via speaker(s)345indicating to the user that wearable audio output devices301are charging, and user interface576is presented on device100(e.g., optionally displayed over a portion of another user interface, such as user interface570). In some embodiments, wearable audio output devices301begin charging in response to being inserted (e.g., mounted and/or secured) within wireless accessory case480. In some embodiments, audio feedback585includes one or more tones and/or one or more spoken terms. User interface576includes a representation578of wireless accessory case480, including a representation579of physical marking574, and a representation580of wearable audio output devices301. User interface576further includes an indication582of the charging status of wearable audio output devices301. In the example shown inFIG.5Y, wearable audio output devices301are 20% charged. User interface576also includes indication584of the charging status of case480. In the example shown inFIG.5Y, case480is 50% charged.

In addition, in the example shown inFIG.5Y, optimization of the charging of wearable audio output devices301is enabled, as indicated by indication586(e.g., the text “Charging optimized”) underneath representation580of wearable audio output devices301. In some embodiments, charging of wearable audio output devices301by case480is performed under the control of device100(e.g., while device100is in communication with case480and/or wearable audio output devices301). For example, device100sends instructions to case480and/or wearable audio output devices301to initiate charging of wearable audio output devices301by case480, and optionally to limit charging to a threshold charge level in accordance with optimized charging being enabled, or alternatively, to permit charging to full (e.g., to the full storage capacity of wearable audio output devices301) in accordance with optimized charging being disabled. User interface576also includes optimized charging override button588(e.g., labeled “Charge to Full Now”), which, when activated, disables the optimization of the charging of wearable audio output devices301and, if other charging criteria are met, initiates charging of wearable audio output devices301to a fully charged state. In the example shown inFIG.5Y, optimized charging of case480is not enabled (e.g., is unavailable or has been disabled), so no optimized charging indication, nor any optimized charging override button, is displayed for case480(as opposed to optimized charging for the wearable audio output devices301).

FIG.5Zshows wireless accessory case480and associated wearable audio output device301-1within a threshold distance of device100. Wireless accessory case480is open (e.g., lid367is up) inFIG.5Zand one wearable audio output device301(wearable audio output device301-1) is inserted in case480.

FIG.5AAillustrates a transition fromFIG.5Zin response to an occurrence of a condition associated with wireless accessory case480(e.g., a closure of lid367). In response to closure of lid367, audio feedback587is provided via speaker(s)345indicating to the user that only one wearable audio output devices301is inside case480and user interface590is presented on device100(e.g., optionally displayed over a portion of another user interface, such as user interface570(seeFIG.5X)). In some embodiments, audio feedback587includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback587is different from audio feedback585(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions. User interface590includes a representation592of wireless accessory case480, including a representation594of physical marking574, and a representation596of wearable audio output device301-1. User interface576further includes a notification598that case480includes only one wearable audio output devices301.

FIG.5ABshows wireless accessory case480and associated wearable audio output devices301within a threshold distance of device100. Wireless accessory case480is closed (e.g., lid367is down) inFIG.5ABand wearable audio output devices301are inserted in case480. In the example ofFIG.5AB, wearable audio output devices301include physical markings575and wireless accessory case480includes physical marking574.

FIG.5ACillustrates a transition fromFIG.5ABin response to an occurrence of a condition associated with wireless accessory case480(e.g., an opening of lid367). In response to opening lid367, audio feedback5001is provided via speaker(s)345indicating to the user a charging status of wearable audio output devices301and user interface5002is presented on device100(e.g., optionally displayed over a portion of another user interface, such as user interface570). In some embodiments, audio feedback5001includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5001is different from at least one of audio feedback585and587(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions. User interface5002includes a representation5012of wireless accessory case480, including a representation5014of physical marking574, and a representation5006of wearable audio output devices301, including representations5008of physical markings575. User interface5002further includes an indication5004of the charging status of wearable audio output devices301. In the example shown inFIG.5AC, wearable audio output devices301are 40% charged. User interface5002also includes indication5010of the charging status of case480. In the example shown inFIG.5AC, case480is 10% charged.

FIG.5ADillustrates a transition in response to an occurrence of a condition associated with wireless accessory case480(e.g., an opening of lid367). In the example ofFIG.5AD, wireless accessory case480is empty (e.g., does not contain any wearable audio output devices). In response to opening lid367, audio feedback5018is provided via speaker(s)345indicating to the user a charging status of wireless accessory case480(e.g., 15% charge). For example, when case480is opened while wearable audio output devices are inside, audio feedback indicating a charging status of the wearable audio output devices is provided. In this example, when case480is opened while empty (e.g., no wearable audio output devices are inside), audio feedback indicating a charging status of the case is provided. In some embodiments, audio feedback5018includes one or more tones and/or one or more spoken terms (e.g., recorded and/or simulated vocal outputs). In some embodiments, audio feedback5018is different from at least one of audio feedback585,587, and5001(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions.

FIG.5AEillustrates a transition in response to an occurrence of a condition associated with wireless accessory case480(e.g., insertion of wearable audio output device301-1). In response to insertion of wearable audio output device301-1, audio feedback5020is provided via speaker(s)345indicating to the user that wearable audio output device301-1has been inserted properly (e.g., has been electrically coupled to wireless accessory case480). In some embodiments, audio feedback5020includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5020is different from at least one of audio feedback585,587,5001, and5018(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions.

FIG.5AFshows wireless accessory case480including speaker(s)345(e.g., and associated apertures), input device346, and a physical marking574.FIG.5AFfurther shows a user input5024(e.g., a tap or press input) at input device346.FIG.5AGillustrates a transition fromFIG.5AFin response to detection of user input5024. In response to detecting user input5024, audio feedback5026is provided via speaker(s)345indicating to the user that wireless accessory case480(and optionally wearable audio output devices inserted within case480) is pairing with an electronic device (e.g., device100).

FIG.5AGfurther illustrates audio feedback5028being provided via speaker(s)345indicating to the user that wireless accessory case480(and optionally wearable audio output devices inserted within case480) has completed pairing with the electronic device (e.g., in response to a user activation of button507inFIG.5B). In some embodiments, audio feedback5026and/or5028includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5028is different from5026(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions.

FIG.5AHillustrates audio feedback5029being provided via speaker(s)345indicating to the user that wireless accessory case480has failed to pair with the electronic device (e.g., due to a device mismatch, permission setting, and/or connection issue). In some embodiments, audio feedback5029includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5029is different from at least one of audio feedback5026and5028(e.g., includes different tones, words, and/or frequencies) so that a user can distinguish between the conditions.

FIG.5AIshows wireless accessory case480including speaker(s)345(e.g., and associated apertures), input device346, and a physical marking574.FIG.5AIfurther shows a user input5030(e.g., a long and/or deep press input) at input device346. In some embodiments, user input5024inFIG.5AFis a first type of input and user input5030is a second type of input, different from the first type.FIG.5AIfurther illustrates a transition fromFIG.5AFin response to detection of user input5030(e.g., initiation of a factory reset). In response to detecting user input5030, audio feedback5032is provided via speaker(s)345indicating to the user that wireless accessory case480(and optionally wearable audio output devices inserted within case480) is initiating a factory reset. In some embodiments, wireless accessory case480provides additional audio feedback (e.g., distinct from audio feedback5032) in accordance with completion of the factory reset.

FIG.5AJillustrates a device100and a wireless accessory case480in accordance with some embodiments. Device100shows a user interface5035, e.g., displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to activation of an accessory locate user interface element (e.g., an icon or button). User interface5035corresponds to wireless accessory case480and includes label5036(“Max's charging case”) and a button5038that, when activated by a user, causes a sound to be output at wireless accessory case480.

FIG.5AKillustrates a user input5040detected at button5038and a corresponding audio output5042at wireless accessory case480. In some embodiments, wireless accessory case480provides audio output5042via speaker(s)345in response to user input5040being detected at a location that corresponds to button5038. In some embodiments, audio output5042includes one or more tones and/or one or more spoken terms. In some embodiments, wireless accessory case480produces audio output5042multiple times. For example, activation of button5038toggles on audio output5042, which repeats until a user activates button5038again (or the user activates another affordance to disable audio output5042, or another predefined user input, such as button press or case lid movement, is detected at the wireless accessory case480). In some embodiments, wireless accessory case480produces audio output5042a preset number of times (e.g., 5, 10, or 20) in response to activation of button5038.

FIG.5ALshows wireless accessory case480with wearable audio output devices5046and5050inserted inside. Wireless accessory case480inFIG.5ALincludes speaker(s)345(e.g., and associated apertures), input device346, and physical marking574. Wearable audio output device5046includes a physical marking5048(e.g., the same or similar to physical marking574) and wearable audio output device5050includes a physical marking5052that is different from physical marking5048. Wireless accessory case480is open (e.g., lid367is up) inFIG.5AL.

FIG.5AMillustrates a transition fromFIG.5ALin response to an occurrence of a condition associated with wireless accessory case480(e.g., a closure of lid367). In response to closure of lid367, one or more warning alerts are produced, for example audio feedback5054is provided via speaker(s)345indicating to the user that wearable audio output devices301are mismatched, and/or user interface5056is presented on device100(e.g., optionally displayed over a portion of another user interface, such as user interface570). In some embodiments, audio feedback5054includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5054includes information about the type of mismatch (e.g., different owners and/or different versions) and/or information about which wearable audio output device is different. User interface5056includes a representation5058of the wireless accessory case480, including a representation5060of physical marking574, a representation5062of wearable audio output device5050, including a representation5064of physical marking5052, and a representation5063of wearable audio output device5046including a representation5065of physical marking5048. User interface5056also includes a notification5057that wearable audio output device5050has a different owner than wearable audio output device5046and/or wireless accessory case480(e.g., as indicated by physical marking5052). In some embodiments, the owner of a device is based on an account to which the device is linked or associated (e.g., devices linked to a same account are considered to have a same owner). In some embodiments, the owner of the device is based on an identity of a person who purchased the device.

FIGS.5AN and5AOare similar toFIGS.5AL and5AMexcept that wearable audio output devices5046and5050inFIGS.5AN and5AOdo not include physical markings (e.g., do not include physical markings5048and5052) to distinguish them from each other. In some embodiments, wearable audio output devices5046and5050do not include personalized physical markings (e.g., markings set, selected, and/or accepted by the user). In some embodiments, user interface5056includes an indication5086of which wearable audio output device is associated with an owner that is different than wireless accessory case480. In some embodiments, notification5057indicates which wearable audio output device is associated with an owner that is different than wireless accessory case480.

FIG.5APshows wireless accessory case480with wearable audio output devices5046and5070inserted inside. Wireless accessory case480inFIG.5APincludes speaker(s)345(e.g., and associated apertures), input device346, and physical marking574. Wearable audio output device5046includes a physical marking5048(e.g., the same or similar to physical marking574) and wearable audio output device5070includes a physical marking5072(e.g., the same as physical marking5048). Wireless accessory case480is open (e.g., lid367is up) inFIG.5AP.

FIG.5AQillustrates a transition fromFIG.5APin response to an occurrence of a condition associated with wireless accessory case480(e.g., a closure of lid367). In response to closure of lid367, audio feedback5074is provided via speaker(s)345indicating to the user that wearable audio output devices301are mismatched, and user interface5076is presented on device100(e.g., optionally displayed over a portion of another user interface, such as user interface570). In some embodiments, audio feedback5074includes one or more tones and/or one or more spoken terms. In some embodiments, audio feedback5074includes information about the type of mismatch (e.g., different owners and/or different versions) and/or information about which wearable audio output device is different. User interface5076includes a representation5078of wireless accessory case480, including a representation5080of physical marking574, a representation5082of wearable audio output device5070, including a representation5084of physical marking5072, and a representation5083of wearable audio output device5046including a representation5085of physical marking5048. User interface5056also includes a notification5077that wearable audio output device5070has a different version (e.g., a different hardware and/or software version) than wearable audio output device5046and/or wireless accessory case480. In some embodiments, user interface5056includes an indication5087of the version associated with one or both of the wearable audio output devices5046and5070in the wireless accessory case480. In some embodiments, a wearable audio output device having a different version is due to the wearable audio output device being a different generation of device.

FIG.5ARillustrates a device100and a wireless accessory case480in accordance with some embodiments. Device100shows a user interface5090, e.g., displayed subsequent to user interface400inFIG.5A, and in some embodiments in response to activation of an accessory user interface element (e.g., an icon or button). User interface5090corresponds to wireless accessory case480(labeled as “Max's charging case”) and includes a volume control element5091that, when interacted with by a user, adjusts a volume of the audio output of speaker(s)345. Wireless accessory device480is within a threshold communication distance of device100and has a volume level indicated by volume level5094inFIG.5AR, where volume level5094corresponds to volume level indicator5092in user interface5090.FIG.5ASillustrates a user input5095detected at volume control element5091. Input5095is a swipe gesture as indicated by the downward arrow inFIG.5AS.

FIG.5ATillustrates a transition fromFIG.5ARin response to input5095. In response to input5095(e.g., and in accordance with a determination that input5095is a swipe gesture moving in a direction toward a lower volume (e.g., a downward swipe)), wireless accessory case480adjusts a volume of audio output to volume level5097(e.g., a lower volume level than volume level5094), which corresponds to volume level indicator5096in user interface5090.FIG.5AUillustrates a user input5098detected at volume control element5091. In some embodiments, input5098is a tap or press input.

FIG.5AVillustrates a transition fromFIG.5ATin response to input5098. In response to input5098(e.g., and in accordance with a determination that input5098is a tap gesture at a location that corresponds to zero volume level on volume control element5091), wireless accessory case480disables audio output of speaker(s)345as indicated by volume indicator5100, which corresponds to volume level indicator5099of user interface5090. In some embodiments, input5098(e.g., a tap or press gesture) causes wireless accessory case480to toggle audio output of speaker(s)345(e.g., regardless of a location of input5098on volume control element5091. In some embodiments, input5098is a press gesture and a volume level of wireless accessory case480is adjusted in accordance with a location and/or duration of the press gesture.

FIG.5AWillustrates device100including volume buttons5104(e.g., volume-up button5104-1and volume-down button5104-2) and ringer switch5102.FIG.5AWalso shows wireless accessory device480within a threshold communication distance of device100.FIG.5AWfurther shows an indicator5106of a ringer status of device100and an indicator5108of a volume level of wireless accessory device480.

FIG.5AXillustrates a transition fromFIG.5AW. In particular,FIG.5AXshows device100and a user's hand providing an input5110at volume-down button5104-2(e.g., to disable a ringer of device100). AlthoughFIG.5AXshows input5110provided at volume-down button5104-2, input5110could similarly be provided at ringer switch5102(e.g., to toggle a state of the ringer between enabled and disabled).

FIG.5AYillustrates a transition fromFIG.5AX. In particular,FIG.5AYillustrates that, in response to input5110at volume-down button5104-2, the ringer for device100is disabled (e.g., device100is set to a silent state) as illustrated by ringer status indicator5112.FIG.5AYfurther shows audio output of wireless accessory case480disabled (e.g., volume level of speaker(s)345set to zero) as indicated by volume indicator5114.

FIG.5AZillustrates a device100and a wireless accessory case480in accordance with some embodiments. Wireless accessory case480inFIG.5AZis beyond a communication threshold distance5119(e.g., is not in active communication with device100) and has a non-zero volume level as indicated by volume level indicator5108.

FIG.5AZillustrates settings user interface5117, e.g., displayed over the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of the user interface shown inFIG.5A(e.g., in response to detecting a swipe gesture or activation of a button or icon). In some embodiments, user interface400ofFIG.5Ais at least partially obscured or blurred behind settings user interface5117such that distinct features of user interface400ofFIG.5Aare not discernible. Settings user interface5117includes a plurality of controls for various features of device100. Notably, settings user interface5117includes a focus mode control5118.

FIG.5BAillustrates input5120(e.g., a press gesture that meets an intensity threshold that is above a nominal contact detection intensity threshold, or a long press gesture that is maintained on touch-sensitive display system112for at least a threshold amount of time) at focus mode control5118.

FIG.5BBillustrates a transition fromFIG.5BA. In particular,FIG.5BBshows a focus mode user interface5121, which is displayed (e.g., in place of, or overlaid with, user interface5117) in response to input5120. Focus mode user interface5121includes controls for two or more focus modes, for example a do-not-disturb control5126, a personal control5128, and a sleep control5130. Do-not-disturb control5126, when activated by a user, causes at least a subset of incoming calls and/or notifications at device100to be silenced. In some embodiments, the do-not-disturb controls are customizable by a user (e.g., the user is able to set which types of incoming calls and/or notifications are silenced). Personal control5128, when activated by a user, causes at least a subset of incoming calls and/or notifications at device100to be silenced (e.g., the same or different subset as do-not-disturb control5126). Sleep control5130, when activated by a user, causes at least a subset of incoming calls and/or notifications at device100to be silenced (e.g., the same or different subset as do-not-disturb control5126and/or personal control5128). For example, personal control5128sets notifications and ringer settings during a user's personal time and sleep control5130sets notifications and ringer settings during a user's sleep time.

FIG.5BCillustrates input5132(e.g., a press gesture that meets an intensity threshold that is above a nominal contact detection intensity threshold, or a long press gesture that is maintained on touch-sensitive display system112for at least a threshold amount of time) at do-not-disturb control5126.

FIG.5BDillustrates a transition fromFIG.5BC. In particular,FIG.5BDshows do-not-disturb mode enabled in response to input5132as illustrated by indicator5136.FIG.5BDfurther shows wireless accessory device480beyond threshold distance5119and having a non-zero volume level as indicated by volume level indicator5108(e.g., wireless accessory device480is not affected by the do-not-disturb mode being enabled at device100).

FIG.5BEillustrates a transition fromFIG.5BD. In particular,FIG.5BEshows wireless accessory device480inside threshold distance5119and audio output of wireless accessory case480being disabled (e.g., volume level of speaker(s)345set to zero) as indicated by volume indicator5138. In some embodiments, in accordance with moving inside threshold distance5119, wireless accessory case480establishes a communicative connection with device100. In some embodiments, after establishing a communicative connection, wireless accessory case480receives information regarding do-not-disturb mode being enabled at device100and disables audio output in response to the received information.

FIG.5BFillustrates a transition fromFIG.5BE. In particular,FIG.5BFshows wireless accessory device480beyond threshold distance5119and audio output of wireless accessory case480being disabled (e.g., volume level of speaker(s)345set to zero) as indicated by volume indicator5138. In some embodiments, in accordance with moving beyond threshold distance5119, wireless accessory case480maintains audio settings (e.g., does not adjust volume of audio output). In some embodiments, in accordance with moving beyond threshold distance5119, wireless accessory case480maintains audio settings established while wireless accessory case480was in communication with device100.

FIG.5BGillustrates a transition fromFIG.5BE. In particular,FIG.5BGshows wireless accessory device480beyond threshold distance5119and audio output of wireless accessory case480being enabled (e.g., volume level of speaker(s)345set to a non-zero value) as indicated by volume level indicator5108. In some embodiments, in accordance with moving beyond threshold distance5119, wireless accessory case480enables audio output (e.g., enables audio output at a volume level that was established prior to audio output being disabled). In some embodiments, wireless accessory case480enables audio output in accordance with a user setting (e.g., a user preference regarding whether to maintain silence settings when not in communication with an electronic device).

FIG.5BHillustrates a transition fromFIG.5BC. In particular,FIG.5BHshows do-not-disturb mode enabled in response to input5132as illustrated by indicator5136.FIG.5BHfurther shows wireless accessory device480and wearable audio output devices5142in communication with one another and beyond threshold distance5119.FIG.5BHalso shows wireless accessory device480having a non-zero volume level as indicated by volume level indicator5108(e.g., wireless accessory device480is not affected by the do-not-disturb mode being enabled at device100).

FIG.5BIillustrates a transition fromFIG.5BH. In particular,FIG.5BIshows wearable audio output devices5142inside threshold distance5119while in communication with wireless accessory case480, which is beyond threshold distance5119.FIG.5BIfurther shows audio output of wireless accessory case480being disabled (e.g., volume level of speaker(s)345set to zero) as indicated by volume indicator5150. In some embodiments, in accordance with wearable audio output devices5142moving inside threshold distance5119, wearable audio output devices5142establish a communicative connection with device100. In some embodiments, after establishing a communicative connection, wearable audio output devices5142receive information regarding do-not-disturb mode being enabled at device100. In some embodiments, after receiving the information regarding the do-not-disturb mode, wearable audio output devices5142transmits the information regarding the do-not-disturb mode to wireless accessory case480. In some embodiments, in response to wireless accessory case480receiving the information regarding the do-not-disturb mode being enabled at device100, wireless accessory case480disables audio output. Thus,FIGS.5AR-5BIillustrate various ways to adjust volume (e.g., increase volume, decrease volume, disable audio output, and/or enable audio output) of audio output at wireless accessory case480.

FIGS.5BJ-5CBillustrate example user interfaces and user interactions for adjusting the audio output of wearable audio output devices in accordance with some embodiments.

FIG.5BJillustrates example user interface5158, which is similar to user interface400as shown in, and described with reference to,FIG.4A, and also shown inFIG.5A. Additionally,FIG.5BJshows swipe gesture5160beginning from an initial position in the upper right corner of touch-sensitive display system112and moving downward across touch-sensitive display system112.FIG.5BKillustrates that in response to a first portion of swipe gesture5160from the initial position inFIG.5BJto a second position inFIG.5BK, device100displays a first portion of a settings user interface5164(sometimes also called a control panel user interface) over at least a portion of user interface5158.

FIG.5BLillustrates settings user interface5164displayed over the entirety (or substantially all, e.g., greater than 95%, 96%, 97%, 98%, or 99%) of user interface5158(e.g., in response to ceasing to detect swipe gesture5160, optionally after further downward movement of swipe gesture5160across touch-sensitive display system112). In some embodiments, settings user interface5164is displayed in response to a user activation of a settings icon (e.g., icon446, shown inFIG.4A). In some embodiments, user interface5158is at least partially obscured or blurred behind settings user interface5164such that distinct features of user interface5158are not discernible. Settings user interface5164includes a plurality of controls for various features of device100. Notably, settings user interface5164includes volume control5166. Upward and downward swipe inputs on volume control5166may be provided to increase or decrease, respectively, the volume of audio outputs from device100(e.g., via wearable audio output devices301).

FIG.5BMillustrates a user input5168detected at volume control5166. Input5168is a swipe gesture as indicated by the upward arrow inFIG.5BM.FIG.5BNillustrates a transition fromFIG.5BMin response to input5168. In response to input5168(e.g., and in accordance with a determination that input5168is a swipe gesture moving in a direction toward a higher volume (e.g., an upward swipe)), a volume of audio output at wearable audio output devices301is increased to volume level5180.FIG.5BOillustrates a user input5182(e.g., a different type of input from input5168) detected at volume control5166. In some embodiments, input5182is a tap, press, long press, and/or deep press input.

FIG.5BPillustrates a transition fromFIG.5BO. In particular,FIG.5BPshows an audio control user interface5184, which is displayed (e.g., in place of, or overlaid with, user interface5164) in response to input5182. Audio control user interface5184includes volume control5196, which is an enlarged version of volume control5166(FIG.5BN), and which allows for finer (e.g., more granular) volume control. User interface5164also includes noise control5194, spatial audio control5192, and conversation boost control5190.FIG.5BPshows wearable audio output devices301operating with a spatial audio mode disabled and a conversation mode disabled, as indicated by indicator5191. Additionally, as indicated by indicator5195inFIG.5BP, wearable audio output devices301are operating in a transparency (e.g., active pass-through) audio output mode in which one or more pass-through audio components are output so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., as described herein with reference toFIG.3F).

FIG.5BQillustrates a user input5198detected at conversation boost control5190. In some embodiments, input5198is a tap, press, long press, and/or deep press input.FIG.5BRillustrates a transition fromFIG.5BQ. In particular,FIG.5BRshows audio control user interface5200, in which display of noise control5194, spatial audio control5192, and conversation boost control5190is replaced with display of a conversation boost adjustment control5206and a boost level indicator5204. In response to input5198(e.g., and in accordance with a determination that input5198is a tap or press gesture at conversation boost control5190, or otherwise meets predefined input activation criteria), noise control5194, spatial audio control5192, and conversation boost control5190cease to be displayed and conversation boost adjustment control5206and boost level indicator5204are displayed. In some embodiments, conversation boost adjustment control5206and boost level indicator5204are displayed concurrently with noise control5194and/or spatial audio control5192in response to input5198. In some embodiments, conversation boost adjustment control5206, when adjusted by a user (e.g., by performing a drag gesture with respect to boost level indicator5204), adjusts a boost level (e.g., an amplification) of conversation audio that is being picked up by one or more microphones of the wearable audio output devices (e.g., microphone(s)302), conversation audio that is being picked up by one or more microphones of the electronic device (e.g., microphone113), or conversation audio that is being picked up by one or more external microphones.

FIG.5BSillustrates a user input5210detected at noise control5194in audio control user interface5184. In some embodiments, input5210is a tap, press, long press, and/or deep press input.FIG.5BSalso illustrates that wearable audio output devices301are operating with conversation boost enabled as illustrated by indicator5209in user interface5184.FIG.5BTillustrates a transition fromFIG.5BS. In particular,FIG.5BTshows audio control user interface5201, in which display of noise control5194, spatial audio control5192, and conversation boost control5190is replaced with display of an expanded noise management control5211, which includes representations of a plurality of available audio output modes (e.g., three available audio output modes) for wearable audio output devices301, each of which is associated with a different audio output mode available for wearable audio output devices301. In particular, expanded noise management control5211includes pass-through icon5216, bypass icon5214, and active noise control icon5212. Active noise control icon5212represents an active noise control (“ANC”) audio output mode in which one or more audio-cancelling audio components are output to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. Bypass icon5214represents a bypass audio output mode in which neither audio-cancelling audio components nor pass-through audio components are provided (e.g., any amount of ambient sound that the user perceives is due to physical attenuation by the wearable audio output devices301(and any attached eartips) in the user's ears). Selection indicator5217displayed over pass-through icon5216(e.g., and not displayed over either bypass icon5214or active noise control icon5212) indicates that the audio pass-through mode represented by pass-through icon5216is the mode in which wearable audio output devices301are currently operating. In response to input5210(e.g., and in accordance with a determination that input5210, shown inFIG.5BS, is a tap or press gesture at noise control5194), noise control5194, spatial audio control5192, and conversation boost control5190cease to be displayed and expanded noise management control5211is displayed. In some embodiments, expanded noise management control5211is displayed concurrently with spatial audio control5192and/or conversation boost control5190in response to input5210.

FIG.5BUillustrates a user input5218detected at active noise control icon5212in audio control user interface5201. In some embodiments, input5218is a tap, press, long press, and/or deep press input.FIG.5BVillustrates a transition fromFIG.5BU. In particular,FIG.5BVshows audio control user interface5184shows audio control user interface5184, which is displayed in response to input5218. InFIG.5BV, noise control5194is set to ANC (e.g., in accordance with detection of user input5218at active noise control icon5212).FIG.5BValso shows spatial audio disabled as shown by spatial audio control5192and conversation boost mode enabled, but not active, as shown by conversation boost control5190and indicator5219. In some embodiments, conversation boost mode is disabled while ANC is active. In some embodiments, conversation boost mode is only enabled while pass-through mode is enabled.

FIG.5BWillustrates settings user interface5164including a hearing control5222and a user input5224detected at hearing control5222. In some embodiments, input5224is a tap, press, long press, and/or deep press input.FIG.5BXillustrates a transition fromFIG.5BW. In particular,FIG.5BXshows a hearing user interface5230, which includes a plurality of activatable control options for wearable audio output devices301, such as the following, or a subset or superset thereof:background sounds control5232that, when activated, initiates a process for producing background sound at wearable audio output devices301;live listen control5234that, when activated, initiates a process for providing audio data at wearable audio output devices301, where the audio data is captured via a microphone at device100;reduce loud sounds control5235that, when activated, initiates a process to reduce a volume of sounds that meet one or more criteria;ambient noise control5236for setting audio output modes available for wearable audio output devices301(e.g., active noise cancelation mode, bypass mode, and/or pass-through mode);conversation boost control5242that, when activated, initiates a process for adjusting audio output of wearable audio output devices301to boost conversation audio;live listen control5244for toggling live listen mode on and off;background sounds control5246for toggling background sounds mode on and off; andconversation boost control5248for toggling conversation boost mode on and off.

In the example ofFIG.5BX, wearable audio output devices301are operating in pass-through mode, as indicated by ambient noise control5236. In some embodiments, selecting an option of the activatable control options in settings user interface5164assigns the selected type of operation to the operation of both wearable audio output devices301.

FIG.5BYillustrates a user input5250detected at conversation boost icon5248. In some embodiments, input5250is a tap, press, long press, and/or deep press input.FIG.5BZillustrates a transition fromFIG.5BY. In particular,FIG.5BZshows hearing user interface5252, in which background sounds control5232has ceased to be displayed, conversation boost mode is enabled as illustrated by conversation boost control5242and conversation boost icon5248, and a conversation boost adjustment control5256is displayed. In response to input5250(e.g., and in accordance with a determination that input5250is a tap or press gesture at conversation boost icon5248), background sounds control5232ceases to be displayed (e.g., to provide space to display conversation boost adjustment control5256) and conversation boost adjustment control5256is displayed. In some embodiments, conversation boost adjustment control5256is displayed concurrently with background sounds control5232in response to input5250(e.g., a different control from hearing user interface5230ceases to be displayed and/or sizing/spacing of the controls is adjusted to concurrently display conversation boost adjustment control5256with the controls of user interface5230).

FIG.5CAillustrates a user input5260detected at reduce loud sounds control5235. In some embodiments, input5260is a tap, press, long press, and/or deep press input.FIG.5CBillustrates a transition fromFIG.5CA. In particular,FIG.5CBshows hearing user interface5262, in which conversation boost control5242(and conversation boost adjustment control5256) has ceased to be displayed (e.g., but conversation boost mode is still enabled, as illustrated by conversation boost icon5248), loud sound reduction mode is enabled as illustrated by reduce loud sounds control5235, and a loud sound reduction adjustment control5268and associated information5266are displayed. In response to input5260(e.g., and in accordance with a determination that input5260is a tap or press gesture at reduce loud sounds control5235), conversation boost control5242ceases to be displayed (e.g., to provide space to display loud sound reduction adjustment control5268) and loud sound reduction adjustment control5268is displayed. In some embodiments, loud sound reduction adjustment control5268, when adjusted by a user (e.g., by performing a drag gesture), adjusts a maximum audio output level (e.g., a maximum output decibel level) for wearable audio output devices301. For example, while reduce loud sounds mode is enabled, wearable audio output devices301reduce any sounds that would otherwise be above the maximum audio output level.

FIGS.6A-6Care flow diagrams illustrating method600of adjusting audio output of one or more wearable audio output devices in accordance with some embodiments. Method600is performed at a wearable audio output device (e.g., wearable audio output device301,FIGS.3B-3C) that includes a first portion (e.g., head portion303) configured to be inserted in an ear of a user of the wearable audio output device and a second portion (e.g., stem portion305) that extends from the first portion and includes one or more input device (e.g., input device(s)308). In some embodiments, the first portion includes a speaker (e.g., speaker(s)306) or other audio output device and optionally one or more elements to enable the speaker to be positioned in a respective physical arrangement relative to an ear of a person using the wearable audio output device. In some embodiments, the second portion includes a stem or other elongated portion extending from the first portion. In some embodiments, the wearable audio output device includes a housing with one or more physically distinguished portions. In some embodiments, the wearable audio output device includes one or more audio output devices (e.g., speaker(s)306). In some embodiments, the wearable audio output device includes one or more placement sensors (e.g., sensor(s)304). Some operations in method600are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, method600provides an improved interface for controlling audio outputs by changing an output volume of an audio output device, such as a wearable device, in response to a particular type of gesture. Providing additional control options for controlling audio outputs, such as changing the audio output mode, interacting with a digital assistant, or adjusting audio playback reduces power usage and improves battery life (e.g., by alleviating the need to power a display or power communication circuitry to communicate with a remote display) and allows for a user to not have to switch between multiple devices to interact with the audio output device (e.g., the user need not find/switch to other electronic devices (e.g., a smartphone or tablet) to control the audio outputs), as well as reducing the number of inputs needed for the user to control the audio outputs, and enhances the operability of the audio output device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the audio output device), which, additionally, reduces power usage and improves battery life of the audio output device by enabling the user to use the audio output device more quickly and efficiently.

The wearable audio output device detects (602) an input via one or more input devices (e.g., input device(s)308). In some embodiments, the one or more input devices include one or more capacitive sensors, one or more force sensors, one or more motion sensors, and/or one or more device orientation sensors.

In some embodiments, the one or more input devices include (604) a sequence of capacitive sensors arranged to detect user gestures. In some embodiments, the sequence of capacitive sensors are arranged in a column or row along a length of the second portion. In some circumstances, capacitive sensors consume less power and/or provide improved detection of user touch gestures than other types of sensors (e.g., force or pressure sensors).

In some embodiments, the wearable audio output device includes (606) a housing with one or more physically distinguished (e.g., indented, raised, and/or differently textured) portions (e.g., physically distinguished portion(s)307, as shown inFIG.3B) at a location corresponding to the sequence of capacitive sensors. In some embodiments, the one or more physically distinguished portions include a single groove that spans the sequence of capacitive sensors, a respective groove for each capacitive sensor, and/or other configuration of grooves spanning the location of the capacitive sensors. Providing a physically distinguished portion at a location corresponding to the capacitive sensors allows a user to locate and interact with the sensors quickly and efficiently (e.g., without requiring the user to visually locate the sensors), which enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In response to detecting the input, in accordance with a determination that the input is a swipe gesture along a second portion of a wearable audio output device, the wearable audio output device adjusts (608) an output volume for the wearable audio output device based on movement of the swipe gesture along the second portion of the wearable audio output device. For example,FIGS.5H-5Iillustrate a swipe gesture along stem portion305andFIG.5Jillustrates a corresponding change in volume of audio output. In some embodiments, the swipe gesture includes movement of one or more fingers, or a pinch for stability and then a swipe to adjust, or another finger input. In some embodiments, the swipe gesture is a pinch-and-swipe gesture that includes two fingers concurrently in contact with the second portion of the wearable audio output device (e.g., the two fingers are a thumb and a second finger different from the thumb). For example, the user's thumb contacts the wearable audio output device to maintain stability while the user's second finger performs the swipe gesture (e.g., as illustrated inFIG.5H). In some embodiments, the output volume for the wearable audio output device is adjusted in response to detecting the input and in accordance with determinations that (i) the input is a swipe gesture along the second portion of the wearable audio output device, and (ii) the first portion of the wearable audio output device is inserted in an ear of the user (e.g., based on data from placement sensor(s)304).

In some embodiments, the second portion is (610) a stem of the wearable audio output device (e.g., stem portion305), and the swipe gesture includes movement of one or more fingers along a length of the stem (e.g., as illustrated inFIGS.5H-5I and5K-5L). Providing an elongated stem portion with sensors for detecting user inputs allows a user to locate and interact with the sensors quickly and efficiently (e.g., without requiring the user to visually locate the sensors), which enhances the operability of the device and makes the user-device interface more efficient.

In some embodiments, a first portion of the wearable audio output device includes (612) an audio output device configured to be inserted in the user's ear (e.g., speaker(s)306) and one or more positioning elements (e.g., eartip314, shown inFIG.3F) configured to maintain the audio output device in the user's ear after insertion, and the second portion of the wearable audio output device is an elongated portion (e.g., stem portion305) extending from the first portion. In some embodiments, the second portion extends in a downward direction while the first portion is inserted in a user's ear. In some embodiments, the second portion extends in front of (e.g., past) a user's earlobe while the first portion is inserted in the user's ear (e.g., as illustrated inFIG.5G). Improving the fit of the wearable audio output devices via the positioning element(s) improves the seal between the wearable audio output devices and the user's ears, which enables audio to be played at a lower volume to produce the same effective audio volume perceived by the user (e.g., relative to when the wearable audio output devices are not properly fitted, in which case hearing some ambient noise may cause the user to increase the audio output volume), thereby further reducing power usage and improving battery life of the devices. In some situations, locating the sensor(s) in an elongated portion extending from the first portion improves the user-device interface by allowing a user to stabilize the device with a pinch gesture while performing input gestures and allowing a user to perform gestures away from the portion of the device that is inserted into the user's ear (e.g., to avoid interfering with the fit between the wearable audio output device and the user's ear).

In some embodiments, the wearable audio output device is (614) in communication with a second wearable audio output device (e.g., wearable audio output device301-1is in communication with wearable audio output device301-2) to form a pair of wearable audio output devices, and adjusting the output volume for the wearable audio output device includes adjusting the output volume for both the wearable audio output device and the second wearable audio output device (e.g., as illustrated by respective output volume levels518-1and518-2inFIG.5Gand respective output volume levels522-1and522-2inFIG.5J). Adjusting the output volume for both wearable audio output devices in response to a single gesture reduces the number of inputs needed, which enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, the wearable audio output device detects (616) a second input via an input device of the second wearable audio output device, and, in response to detecting the second input, in accordance with a determination that the second input is a swipe gesture along a second portion of the second wearable audio output device, the wearable audio output device adjusts the output volume for both the wearable audio output device and the second wearable audio output device. For example,FIGS.5H-5Iillustrate a swipe gesture at wearable audio output device301-2andFIG.5Jillustrates a corresponding change in volume at each of wearable audio output devices301-1and301-2. Additionally,FIGS.5K-5Lillustrate a swipe gesture at wearable audio output device301-1andFIG.5Millustrates a corresponding change in volume at each of wearable audio output devices301-1and301-2. Adjusting the output volume for both wearable audio output devices in response to a single gesture at either of the wearable audio output devices enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, in conjunction with adjusting the audio output volume for the wearable audio output device, the wearable audio output device provides (618) audio feedback (e.g., audio feedback530) of volume adjustment to the user via an audio output device (e.g., speaker(s)306) of the wearable audio output device. In some embodiments, the feedback is provided via a speaker in the first portion of the wearable audio output device, and/or in the second portion of the wearable audio output device. Providing audio feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, providing the audio feedback of volume adjustment includes (620) providing the audio feedback of volume adjustment at both the wearable audio output device and the second wearable audio output device (e.g., audio feedback530-1and530-2). In some embodiments, the audio feedback corresponds to an increase or decrease in volume, and/or the volume reaching a maximum or minimum endpoint. Providing audio feedback to the user at each of the wearable audio output devices enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, in response to detecting the input, in accordance with a determination that the input is a non-swipe gesture, the wearable audio output device activates (622) a function of the wearable audio output device, where the function is distinct from adjusting the output volume. For example,FIG.5Oillustrates a non-swipe gesture andFIG.5Pillustrates a corresponding activation of a playback function. In some embodiments, the non-swipe gesture is a tap gesture, a double tap gesture, a squeeze gesture, or other finger input. In some embodiments, the input satisfies second gesture criteria, such as single squeeze gesture criteria that require that, after intensity applied by the input to the input device satisfies an intensity threshold (e.g., a predefined intensity threshold), the intensity applied by the input to the input device decreases below the intensity threshold (e.g., due to the input ceasing to remain in contact with the input device) within a threshold amount of time since the input intensity satisfied the intensity threshold, or, alternatively, since initial detection of the input via the input device. In some embodiments, the first wearable audio output device and the second wearable audio device have different behaviors. For example, the first wearable audio output device has a different set of assignments between type of input gesture and operation performed in response than the second wearable audio output device (e.g., a long squeeze gesture via the first wearable audio output device changes the audio output mode of the wearable audio output device, or both wearable audio output devices, while a different gesture, such as a short squeeze (e.g., single squeeze) gesture, via the second wearable audio output device changes the audio output mode of the second wearable audio output device, or both wearable audio output devices, and/or a long squeeze gesture via the second wearable audio output device performs a different operation, such as toggling playback of media content instead of changing audio output mode.

Detecting and being responsive in different ways to different types of gestures enhances operability of the device (e.g., provides flexibility without requiring a graphical user interface and/or cluttering the graphical user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the function of the wearable audio output device that is activated in response to detecting the input is (624) an audio playback function (e.g., a play, pause, or skip function). In some embodiments, the audio playback function toggles playback of a respective media audio component (e.g., that is independent of ambient sound from the physical environment, and that is based on media content from or obtained by the electronic device). For example, if the respective media audio component is being played when the audio playback function is activated, playing of the respective media audio component is paused; if the respective media audio component is paused when the audio playback function is activated, playing of the respective media audio component is resumed (e.g., as illustrated inFIG.5P). In some embodiments, the media audio component is combined with one or more pass-through audio components (e.g., if the device is operating in a transparency mode) or one or more cancelation audio components (e.g., if the device is operating in a noise cancelation mode). In some embodiments, activation of the audio playback function skips any remaining portion of the respective media audio component and instead plays a different respective audio component (e.g., a second, next audio track from the electronic device). Adjusting audio playback functions in response to gestures at the wearable audio output device enhances operability of the device (e.g., provides flexibility without requiring a graphical user interface and/or cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the function of the wearable audio output device that is activated in response to detecting the input is (626) an ambient noise adjustment function (e.g., adjusting active noise cancelation for ambient noise, transparency for ambient noise, and/or other ambient sound functions). For example,FIGS.5Q-5Rshow a transparency mode being enabled in response to a user input at stem portion305of wearable audio output device301-1. In some embodiments, when ambient sound from the physical environment is being actively passed through (e.g., the first ambient-sound audio level is non-zero), noise-cancelation is disabled (e.g., the audio-cancelling audio level is zero). In some embodiments, the ambient noise adjustment function activates a pass-through mode (or transparency mode or non-noise canceling mode) that allows the user to hear unaided audio (e.g., normal voices) from the user's environs. In some embodiments, when noise-cancelation is enabled (e.g., the audio-cancelling audio level is non-zero), no ambient sound from the physical environment is actively passed through (e.g., the first ambient-sound audio level is zero). In some embodiments, the ambient noise adjustment function activates an active noise control mode (ANC) and the wearable audio output device outputs one or more audio-cancelling audio components (e.g., one or more antiphase audio signals, also called “audio-cancelation audio components”) to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. In some embodiments, an ambient sound waveform is detected by one or more microphones of the wearable audio output device, and an antiphase (or partially antiphase) audio signal waveform is produced by the wearable audio output device to at least partially cancel the ambient sound waveform.

Adjusting ambient noise control in response to gestures at the wearable audio output device enhances operability of the device (e.g., provides flexibility without requiring a graphical user interface and/or cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient. Additionally, using different levels of pass-through audio components and cancellation audio components in different audio output modes provides the user with flexibility between different levels of audio immersion (via ambient audio cancellation) or audio transparency (via ambient audio pass-through) that can be achieved with a gesture, e.g., a gesture detected at an input device of one of the wearable audio output devices.

In some embodiments, the function of the wearable audio output device that is activated in response to detecting the input is (628) a digital assistant function (e.g., invoking, interacting with, or dismissing a digital assistant). In some embodiments, a digital assistant comprises functionality for performing operations on a device in response to user inputs (e.g., audio and/or textual inputs such as spoken or typed commands). In some embodiments, invoking the digital assistant causes the digital assistant to be responsive to user inputs (gestures, phrases, and/or commands). In some embodiments, dismissing (and/or disabling) the digital assistant causes the digital assistant to not be responsive to user inputs. In some embodiments, the function causes a digital assistant invocation command to be sent to a network connected device, e.g., device100, and the network connected device invokes the digital assistant and provides corresponding audio to the wearable audio output device, e.g., via wireless communication.

Invoking, interacting with, and/or dismissing a digital assistant in response to gestures at the wearable audio output device enhances operability of the device (e.g., provides flexibility without requiring a graphical user interface and/or cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the wearable audio output device provides (630), in conjunction with activating (622) the function of the wearable audio output device, audio feedback (e.g., audio feedback540) of the activation of the function via the audio output device (e.g., in the first portion and/or second portion) and forgoes providing the audio feedback at the second wearable audio output device of the pair of wearable audio output devices. For example,FIG.5Rshows audio feedback540provided at wearable audio output device301-1and no audio feedback provided at wearable audio output device301-2. Providing audio feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, the wearable audio output device detects (632) a third input via the one or more input devices, and, in response to detecting the third input: (i) in accordance with a determination that the third input is a swipe gesture along the second portion of the wearable audio output device and a determination that the first portion of the wearable audio output device is inserted in an ear of the user, the wearable audio output device adjusts the output volume for the wearable audio output device; and (ii) in accordance with a determination that the third input is the swipe gesture along the second portion of the wearable audio output device and a determination that the first portion of the wearable audio output device is not inserted in an ear of the user, the wearable audio output device forgoes adjusting the output volume for the wearable audio output device. In some embodiments, wearable audio output devices301are configured to adjust volume levels in response to user swipe inputs only while wearable audio output devices301are inserted in an ear of a user (e.g., determined based on data from placement sensor(s)304). Forgoing adjusting volume while the wearable audio output device is not inserted in an ear of the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, the one or more input devices include (634) a first type of sensor (e.g., a touch sensor) and a second type of sensor (e.g., a force sensor), the input is detected via the first type of sensor, the device detects a fourth input via the second type of sensor, and, in response to detecting the fourth input, the wearable audio output device activates a function of the wearable audio output device that is distinct from adjusting the output volume (e.g., sensor types can include capacitive, force, motion (e.g., accelerometer), and orientation). In some embodiments, the one or more input devices include an input device that is pressure-sensitive (sometimes also called “intensity-sensitive”). For example, the input device responds to squeeze inputs (e.g., inputs where intensity (also called pressure) is applied to the input device when held and pinched between two fingers) that satisfy an intensity threshold, which in some embodiments is greater than a nominal contact detection intensity threshold that would be used for touch inputs. In some embodiments, the one or more input devices include an input device that is touch-sensitive (e.g., the input device responds to touch inputs, such as by a finger or stylus, that satisfy a nominal contact detection intensity threshold). Including multiple types of sensors in the device expands the number and/or type of gestures that can be detected at the device. Expanding the number and/or type of gestures that can be detected enhances operability of the device (e.g., provides flexibility without requiring a graphical user interface and/or cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the wearable audio output device establishes (636) a connection (e.g., pairing the devices, or adding the wearable audio output device to a user account associated with the electronic device) between an electronic device and the wearable audio output device, and, after (e.g., in response to) establishing the connection, the electronic device causes a user interface (e.g., user interface514-1and/or514-2) to be displayed, the user interface illustrating a simulated swipe gesture and corresponding output volume adjustment. For example, the user interface is displayed as part of a usage tutorial that is shown in conjunction with: pairing the wearable audio output device, adding the wearable audio output device to a user account (e.g., via a QR code), or activating the wearable audio output device for a first time while connected to the electronic device.

Displaying simulated gestures and corresponding functions and/or adjustments provides visual feedback to the user by indicating operation and states of the device. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

It should be understood that the particular order in which the operations inFIGS.6A-6Chave been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods700,800, and900) are also applicable in an analogous manner to method600described above with respect toFIGS.6A-6C. For example, the inputs, gestures, functions, and feedback described above with reference to method600optionally have one or more of the characteristics of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods700,800, and900). For brevity, these details are not repeated here.

FIGS.7A-7Care flow diagrams illustrating method700for displaying status information of an electronic accessory in accordance with some embodiments. Method700is performed at an electronic device (e.g., device300,FIG.3, or portable multifunction device100,FIG.1A) including, or in communication with, a display generation component and, optionally, a touch-sensitive surface. In some embodiments, the display generation component is a touch-screen display. In some embodiments, the display is separate from a touch-sensitive surface. Some operations in method700are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, method700provides an improved interface for presenting information about an electronic accessory (e.g., headphones or an earbud case) at an electronic device that is in communication with the electronic accessory in response to detecting an occurrence of a respective condition associated with the electronic accessory, which is presented with a representation of the electronic accessory that includes a representation of a physical marking on the electronic accessory. Providing the representation of the electronic accessory with the representation of the physical marking to the user enhances identification (e.g., distinguishing between multiple electronic accessories of a same type) and security (e.g., distinguishing between electronic accessories owned by the user and electronic accessories owned by other users) and makes the user-device interface more efficient (e.g., by helping the user to interact with the desired electronic accessory), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to control the devices more quickly and efficiently.

The electronic device detects (702) occurrence of a respective condition associated with an electronic accessory (e.g., wireless accessory case480), distinct from the electronic device, the electronic accessory in communication with the electronic device (e.g., wired or wireless communication). In some embodiments, the electronic device is a smartphone or tablet. In some embodiments, the electronic accessory is a set of headphones, a smartwatch, a findable electronic device, a stylus, or an earbud case.

In some embodiments, the occurrence of the respective condition includes (704) a wireless coupling event (e.g., pairing and/or handshaking) between the electronic device and the electronic accessory. For example,FIGS.5A-5Dillustrate a pairing event between device100and earbud set503. In some embodiments, the wireless coupling event comprises detecting a pairing request from the electronic accessory. In some embodiments, the wireless coupling event comprises detecting a broadcast signal from the electronic accessory and/or sending a pairing request to the electronic accessory. In some embodiments, the wireless coupling event comprises completing a pairing process between the electronic device and the electronic accessory (e.g., establishing a communication channel between the electronic device and the electronic accessory and/or storing connection information to facilitate future connections with the electronic accessory). In some embodiments, the wireless coupling event comprises detecting the presence of a previously-paired electronic accessory. In some embodiments, the wireless coupling event comprises a disconnect and/or dissociation between the electronic device and the electronic accessory (e.g., in response to a “forget this device” command). Providing representation of an electronic accessory with a representation of a physical marking in response to a wireless coupling event provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the wireless coupling event, particularly in instances where the electronic accessories are associated with different users and/or user accounts.

In some embodiments, the occurrence of the respective condition includes (706) a proximity-based communication between the electronic device and the electronic accessory. For example,FIG.5Tillustrates a proximity-based communication between wireless accessory case480-1and device100. In some embodiments, the occurrence of the respective conditions comprises the electronic device and the electronic accessory satisfying one or more proximity criteria (e.g., being close enough to wirelessly communicate with one another, and/or being within a predefined physical distance of one another). In some embodiments, the one or more proximity criteria comprise a one or more communication quality criteria (e.g., a signal strength and/or stability requirement). In some embodiments, the proximity-based communication comprises a wireless coupling communication (e.g., an advertising, pairing, and/or handshaking communication). Providing representation of an electronic accessory with a representation of a physical marking in response to a proximity-based communication provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the proximity-based communication, particularly in instances where the electronic accessories are associated with different users and/or user accounts.

In some embodiments, the occurrence of the respective condition includes (708) a status change event at the electronic accessory, and a user interface corresponding to the respective condition includes status information corresponding to the status change event. For example,FIG.5Dillustrates earbud set503communicatively connecting to device100and user interface504-2includes indication512of the connection. Providing representation of an electronic accessory with a representation of a physical marking in response to a status change event provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the status change event, particularly in instances where the electronic accessories are associated with different users and/or user accounts.

In some embodiments, the status change event includes (710) a change in an opened or closed state of the electronic accessory. For example,FIGS.5X-5Yshow lid367of wireless accessory case480closing and a corresponding user interface576displayed on device100. In some embodiments, the electronic accessory is a charging case, and the status change event involves a user opening and/or closing the charging case. For example, in response to a user closing the charging case, the user interface shows the representation of the charging case and information about a current charge level of the charging case (e.g., as illustrated inFIG.5AC). As another example, in response to a user opening the charging case, the user interface shows the representation of the charging case (e.g., representation5012) and a representation of one or more accessories (e.g., representation5006) within the charging case (e.g., with information about a current charge level of the one or more accessories within the charging case). Providing representation of an electronic accessory with a representation of a physical marking in response to a change in an opened or closed state of the electronic accessory provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the status change event and provides enhanced feedback about a state of the electronic accessory.

In some embodiments, the status change event includes (712) an electrical charging event at the electronic accessory (e.g., as illustrated inFIG.5YorFIG.5AC). For example, the electrical charging event involves a user connecting the electronic accessory to a power source (e.g., an outlet, charging station, and/or charging case) and, in response, the user interface shows the representation of the electronic accessory and information indicating that it is currently charging (e.g., indication5004,FIG.5AC, of the charging status of wearable audio output devices301). As another example, the electrical charging event involves a user disconnecting the electronic accessory from a power supply and, in response, the user interface shows the representation of the electronic accessory and information indicating a current charge level of the electronic accessory. Providing representation of an electronic accessory with a representation of a physical marking in response to an electrical charging event provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the electrical charging event and provides enhanced feedback about a state of the electronic accessory.

In some embodiments, the occurrence of the respective condition includes (714) an error event (e.g., a mismatch event as shown inFIG.5AM), and a user interface corresponding to the respective condition includes error information corresponding to the error event (e.g., notification5057). In some embodiments, the error event involves the electronic accessory failing to establish a connection (e.g., a Bluetooth and/or Wi-Fi connection) with the electronic device, and the error information includes information about the failure (e.g., and information about how to correct the failure). For example, the electronic accessory is a wearable audio output device, and the error event is a failure to pair with the electronic device. In this example, the error information includes instructions to reset the wearable audio output device. In some embodiments, the error event involves the electronic accessory failing to charge while connected to a power source, and the error information includes a notification of the failure (e.g., and information about how to correct the failure). In some embodiments, the error event involves a software error such as firmware, an operating system, and/or an application failing to execute. Providing representation of an electronic accessory with a representation of a physical marking in response to an error event provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, in a user interface for the error event, particularly in instances where the electronic accessories are associated with different users and/or user accounts.

In response to detecting the occurrence of the respective condition, the electronic device causes (716) a user interface (e.g., user interface5056) corresponding to the respective condition to be displayed via the display generation component (e.g., touch-sensitive display system112), the user interface including a representation of the electronic accessory (e.g., representation5058of wireless accessory case480).

Causing the user interface to be displayed includes (718): (i) in accordance with a determination that the electronic accessory includes a first physical marking (e.g., engraving, embossing, and/or printed, painted or otherwise applied markings), causing a representation of the first physical marking (e.g., representation544-1of physical marking482-1) to be displayed in the user interface (e.g., without including a representation of another, second physical marking, that is included in a different electronic accessory); and (ii) in accordance with a determination that the electronic accessory includes a second physical marking that is different from the first physical marking, causing a representation of the second physical marking to be displayed in the user interface (e.g., representation544-2of physical marking482-2), e.g., without including a representation of the first physical marking.

In some embodiments, the first physical marking is (720) specified or selected by a user while purchasing the electronic accessory (e.g., via user interface550shown inFIG.5W). For example, the first physical marking is a personalized marking, a marking selected from a group of markings, or a marking suggested by a computer system, such as the electronic device, that the user accepts. Providing users with physical markings specified or selected by the user provides improved security and privacy by distinguishing between multiple electronic accessories that would otherwise be indistinguishable, or more difficult to distinguish, particularly in instances where the electronic accessories are associated with different users and/or user accounts.

In some embodiments, in accordance with a determination that the electronic accessory does not include the first physical marking, the electronic device causes (722) the user interface that includes the representation of the electronic accessory to be displayed without the representation of the first physical marking. For example, wireless accessory case480-3(shown inFIG.5S) does not include a physical marking482and user interface504-1is displayed with representation542-3of wireless accessory case480-3without any representation544of a physical marking482, e.g., as shown inFIG.5V. Providing representation of an electronic accessory without a representation of a physical marking distinguishes the electronic accessory from other electronic accessories that include physical markings. Distinguishing between multiple electronic accessories when interacting with one of them via a user interface improves security and privacy of the interaction(s).

In some embodiments, the representation of the electronic accessory is (724) a three-dimensional representation of the electronic accessory. For example, the electronic accessory is a wireless accessory case, and the representation is a three-dimensional model of the wireless accessory case. Providing a three-dimensional representation of an electronic accessory improves security and privacy by distinguishing between multiple electronic accessories that would be indistinguishable, or more difficult to distinguish, with a two-dimensional representation.

In some embodiments, the user interface includes (726) one or more animated movements (e.g., rotation, shifting, and/or lateral movement) of the representation of the electronic accessory. For example,FIG.5Tshows arrows543in user interface504-1that indicate movement of representation542-1of wireless accessory case480-1. Providing a representation of an electronic accessory with animated movement(s) improves security and privacy by distinguishing between multiple electronic accessories that would be indistinguishable, or more difficult to distinguish, with a static representation (e.g., the representation of the physical marking is not fully visible in a static representation).

In some embodiments, the electronic device detects (728) the occurrence of a respective condition associated with a second electronic accessory (e.g., wireless accessory case480-2), distinct from the electronic device (e.g., device100) and the electronic accessory (e.g., wireless accessory case480-1), the second electronic accessory in communication with the electronic device and having a same device type as the electronic accessory (e.g., wireless accessory cases), and, in response to detecting the occurrence of the respective condition associated with the second electronic accessory, in accordance with a determination that the second electronic accessory does not include the first physical marking, the electronic device causes a second user interface corresponding to the respective condition to be displayed via the display generation component, where the second user interface includes a representation of the second electronic accessory without a representation of the first physical marking. For example, if the second electronic accessory includes a third physical marking, the second user interface includes a representation of the second electronic accessory with a representation of the third physical marking; and if second electronic accessory does not include a personalized physical marking, the second user interface includes a representation of the second electronic accessory without a representation of a personalized physical marking. In accordance with some embodiments, the user interfaces described previously with respect to the electronic accessory are displayed in response to occurrences of respective conditions associated with the second electronic accessory and include the representation of the second electronic accessory (e.g., in addition to, or alternatively to the representation of the electronic accessory). Providing representation of an electronic accessory without a representation of a physical marking distinguishes the electronic accessory from other electronic accessories that include physical markings. Distinguishing between multiple electronic accessories when interacting with one of them via a user interface improves security and privacy of the interaction(s).

In some embodiments, the second electronic accessory includes (730) a third physical marking, distinct from the first physical marking, and the second user interface includes the representation of the second electronic accessory with the representation of the third physical marking. In some embodiments, the occurrence of the respective condition associated with the second electronic accessory is further associated with the electronic accessory and the user interface includes the representation of the electronic accessory with the representation of the first physical marking and the representation of the second electronic accessory with the representation of the third physical marking. For example,FIG.5AMshows user interface5056with a representation5062of wearable audio output device5050that includes a representation5064of physical marking5052and a representation5063of wearable audio output device5046that includes a representation5065of physical marking5048. Providing representation of a second electronic accessory with a representation of a third physical marking distinguishes the second electronic accessory from other electronic accessories (e.g., the first electronic device with the first physical marking). Distinguishing between multiple electronic accessories when interacting with one of them via a user interface improves security and privacy of the interaction(s).

In some embodiments, while the user interface is being displayed, the electronic device detects (732) a user input corresponding to a user interface element on the user interface, where the user interface element corresponds to a function of the electronic accessory, and, in response to the user input, the electronic device activates the function of the electronic accessory. For example, the occurrence of the respective condition comprises a pairing request from the electronic accessory and the user interface element comprises a selectable connection element (e.g., button507, as shown inFIGS.5B-5C) that corresponds to a pairing function for initiating (or continuing, or confirming) pairing between the electronic device and the electronic accessory. In this example, the user input corresponds to the selectable connection element and activates the pairing function. As another example, the occurrence of the respective conditions is an error event, and the user interface includes a selectable troubleshooting element that corresponds to a troubleshooting function. In this example, the user input corresponds to the selectable troubleshooting element and activates the troubleshooting function. Providing representation of a second electronic accessory with a representation of a third physical marking distinguishes the second electronic accessory from other electronic accessories (e.g., the first electronic device with the first physical marking). Distinguishing between multiple electronic accessories when interacting with one of them via a user interface improves security and privacy of the interaction(s). Additionally, providing the distinguishing features with the user interface elements reduces the number of inputs needed to identify/validate the electronic accessory prior to interaction (e.g., via activation of the function corresponding to the user interface element).

It should be understood that the particular order in which the operations inFIGS.7A-7Chave been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods600,800, and900) are also applicable in an analogous manner to method700described above with respect toFIGS.7A-7C. For example, the inputs, gestures, functions, and feedback described above with reference to method700optionally have one or more of the characteristics of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods600,800, and900). For brevity, these details are not repeated here.

FIGS.8A-8Dare flow diagrams illustrating method800of presenting status information at an accessory charging case in accordance with some embodiments. Method800is performed at an accessory charging case (e.g., electronic accessory case342,FIGS.3D-3E) that includes a speaker (e.g., speaker(s)345). In some embodiments, the accessory charging case includes a lid (e.g., lid367or hinged lid486). In some embodiments, the accessory charging case includes one or more input devices (e.g., input device(s)346). In some embodiments, the accessory charging case is a charging case for a wireless accessory to another device, the wireless accessory including one or more of a smartwatch, one or more earbuds, wireless headphones, a stylus, or a fitness tracker. Some operations in method800are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, method800provides an improved interface for presenting status notifications at an accessory charging case. Providing audio notifications at the charging case reduces power usage and improves battery life (e.g., by alleviating the need to power a display or power communication circuitry to communicate with a remote display) and allows for a user to not have to switch between multiple devices to interact with the charging case and/or associated accessories (e.g., the user need not find/switch to other electronic devices (e.g., a smartphone or tablet) to receive the status notification), as well as reducing the number of inputs needed for the user to receive notifications, and enhances the operability of the charging case and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the charging case), which, additionally, reduces power usage and improves battery life of the charging case by enabling the user to use the charging case more quickly and efficiently.

The accessory charging case detects (802) a first event that includes a change in an opened or closed state of an accessory charging case. For example,FIGS.5X-5Yillustrate a closing event (e.g., lid closing) for wireless accessory device480. As another example,FIGS.5AB-5ACillustrate an opening event (e.g., lid opening) for wireless accessory device480.

In response to detecting the change in the opened or closed state of the accessory charging case, the case causes (804) a speaker (e.g., speaker(s)345) of the accessory charging case to generate an audio notification (e.g., audio feedback5001) corresponding to a status for at least one of the accessory charging case and one or more accessories associated with (e.g., communicatively coupled with, and/or linked to a same user account as) the accessory charging case. In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to a status of the accessory charging case and an audio notification corresponding to a status of the one or more accessories associated with the accessory charging case. In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to a status of the accessory charging case without generating an audio notification corresponding to a status of the one or more accessories. In some embodiments, the speaker of the accessory charging case generates an audio notification corresponding to a status of the one or more accessories without generating an audio notification corresponding to a status of the accessory charging case.

In some embodiments, the audio notification includes (806) one or more words describing the status for at least one of the accessory charging case and the one or more accessories associated with the accessory charging case. For example,FIG.5AOshows audio feedback5054that includes the words “Alert, mismatched earbuds.” In some embodiments, the audio notification includes one or more sounds (e.g., tones and/or beeps) and does not include any words.

Providing audio notifications with word(s) describing the status provides improved audio feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently (e.g., without the need for a display device and/or graphical user interface).

In some embodiments, the status corresponds to (808) a charge state of at least one of the one or more accessories associated with the accessory charging case (e.g., currently charging, charging complete, or charging terminated). For example,FIG.5ACshows audio feedback5001that includes information regarding a charge state of wearable audio output devices301. In some embodiments, audio notification is different for each state of the one or more accessories (e.g., so the user can differentiate between different states). For example, an audio notification for a charging-initiated status includes a beep having a first tone and an audio notification for a charging-complete status includes a beep having a second tone, distinct from the first tone. As another example, an audio notification for a charging-initiated status includes a first number of beeps and an audio notification for a charging-complete status includes a second number of beeps, distinct from the first number of beeps. As another example, each audio notification includes one or more words that describe the corresponding charge state (e.g., one or more words that distinguish between the charge states). Providing audio information about a charge state of at least one of the one or more accessories associated with the accessory charging case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the status includes (810) a state of communicatively coupling between the accessory charging case and at least one of the one or more accessories associated with the accessory charging case (e.g., pairing initiated, in-progress, completed, or failed). In some embodiments, audio notification is different for each state of communicative coupling between the accessory charging case and at least one of the one or more accessories associated with the accessory charging chase (e.g., so the user can differentiate between different states). Providing audio information about the state of communicatively coupling improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the accessory charging case is configured to (812) concurrently hold a plurality of accessories (e.g., wearable audio output devices301-1and301-2), the first event includes a closure of the accessory charging case, and the status corresponds to a determination that the accessory charging case contains only a subset of the plurality of accessories. For example,FIGS.5Z-5AAshow closure of wireless accessory case480with only wearable audio output device301-1inside and corresponding audio feedback587. Providing audio information about the charging case including only a subset of the accessories improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the status corresponds to (814) a reset event for the accessory charging case (e.g., a soft reset, hard reset, and/or factory reset event). For example,FIG.5AIshows input5030at input device346causing initiation of a factory reset and corresponding audio feedback5032. An example of a soft reset event includes closing applications that were executing, clearing data in volatile memory, and/or cycling power off for the accessory charging case. An example of a hard reset event includes clearing memory associated with hardware of the accessory charging case and/or updating a driver for the hardware (e.g., updating with a stable driver from a manufacturer of the hardware). An example of a factory reset includes restoring and/or reverting settings, firmware, and/or software for the accessory charging case to a same state as when the accessory charging case shipped from the factory. An example of a factory reset includes removing user data, settings applied by the user, and/or applications installed by the user. For example, a factory reset event includes resetting (e.g., deleting and/or removing) wireless connection information (e.g., pairing information and/or Wi-Fi network information). Providing audio information about the reset event improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the status includes (815) a charge state of the accessory charging case not meeting one or more preset criteria (e.g., the charge state of the accessory charging case is determined to be insufficient to fully charge an accessory associated with the charging case, or the charge state is below a preset threshold (e.g., below 50%, 30%, or 20%)). For example,FIG.5ADshows audio feedback5018indicating that wireless accessory case480has only 15% charge. In some embodiments, the one or more preset criteria are static criteria and correspond to an amount of charge required to fully charge the one or more accessories associated with the accessory charging case from any charge state (e.g., an amount of charge required to fully charge the one or more accessories from a completely drained state). In some embodiments, the one or more preset criteria are dynamic criteria and correspond to an amount of charge required to fully charge the one or more accessories associated with the accessory charging case from a current charge state. For example, the one or more accessories is a wearable audio output device having a current charge state of 40 percent of full charge and the one or more preset criteria correspond to an amount of charge required to fully charge the wearable audio output device from the 40 percent charged state. Providing audio information about the charge state of the accessory charging case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the status corresponds to (818) a determination that the accessory charging case contains a plurality of accessory devices and a determination that the plurality of accessory devices are mismatched. For example,FIGS.5AL-5AMshow closure of wireless accessory case480with mismatched wearable audio output devices5046and5050inside and corresponding audio feedback5054. Providing audio information about the mismatched accessory devices improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the first event includes (820) an opening of the accessory charging case. For example,FIG.5ADshows opening of wireless accessory case480and corresponding audio feedback5018. Providing audio information upon opening of the wireless accessory case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the accessory charging case is (822) in communication with a display generation component, and the case causes a user interface to be displayed via a display generation component, the user interface including a mismatch notification. For example,FIG.5AMshows closure of wireless accessory case480with mismatched wearable audio output devices5046and5050inside and corresponding user interface5056with notification5057. Providing visual information about the mismatched accessory devices improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the user interface further includes (824) a representation of the accessory charging case (e.g., representation5058) and respective representations of the plurality of accessory devices (e.g., representations5062and5063, as shown inFIG.5AM). Providing visual representations of the accessory devices and the accessory charging case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the determination that the plurality of accessory devices are mismatched includes (826) a determination that individual accessories of the plurality of accessory devices have different owners (e.g., are linked to, or associated with, different user accounts), and the user interface further includes ownership information for the plurality of accessory devices (e.g., as illustrated inFIG.5AM). For example, the ownership information includes names or identifiers for the owners of the individual accessories and/or an indication of which accessories have ownership that differs from an ownership of the accessory charging case. Providing audio information about the mismatched ownership of the accessory devices improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient. Additionally, providing audio information about the mismatched ownership improves security/privacy by identifying devices that are associated with other users and/or user accounts.

In some embodiments, the determination that the plurality of accessory devices are mismatched includes (828) a determination that individual accessories of the plurality of accessory devices have different hardware and/or software versions, and the user interface further includes version information for the plurality of accessory devices (e.g., the version information includes version numbers or identifiers for each of the plurality of accessory devices). For example,FIGS.5AP-5AQshow closure of wireless accessory case480with mismatched wearable audio output devices5046and5070inside and corresponding displayed indications5087of the versions associated with the wearable audio output devices5046and5070in the wireless accessory case480. Providing version information about the mismatched versions for the accessory devices improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the case detects (830) a second event that includes a change in charging state of at least one of the accessory charging case and the one or more accessories associated with the accessory charging case, and, in response to detecting the second event, the case causes the speaker to generate a second audio notification, distinct from the audio notification, corresponding to the change in charging state. For example, audio feedback5001provided via speaker(s)345inFIG.5AC, may be generated in response to detecting a change in charging status of wearable audio output devices301or accessory charging case480. Providing audio information about a change in charging state for at least one of the accessory charging case and the one or more accessories associated with the accessory charging case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, the change in charging state includes (832) initiation or termination of charging for at least one of the one or more accessories associated with the accessory charging case. For example,FIGS.5X-5AYshow closure of wireless accessory case480and initiation of charging of wearable audio output devices301and corresponding audio feedback585. Providing audio information about initiation or termination of charging for at least one of the one or more accessories associated with the accessory charging case improves feedback to the user by indicating a relevant state of the system, which enhances the operability of the devices and makes the user-device interface more efficient.

In some embodiments, in accordance with a user request to locate the accessory charging case (e.g., or an accessory associated with the charging case), the case causes (834) the speaker to generate a third audio notification corresponding to the user request, where the third audio notification is distinct from (e.g., and optionally has a different audio waveform than an audio waveform of) the audio notification (e.g., of operation804). For example,FIGS.5AJ-5AKshow user input5040detected at button5038that, when activated by a user, causes audio output5042to be output at wireless accessory case480. In some embodiments, the user request is to locate an accessory device rather than the accessory charging case (e.g., an accessory device inside the charging case, paired with the charging case, or associated with the charging case), and in response the accessory device generates an audio notification (e.g., in accordance with a determination that the accessory is inside the charging case or in communication with the charging case). Providing an audio notification in response to a user request to locate the accessory charging case or an accessory device inside the charging case improves security/privacy by assisting a user in quickly locating a lost or stolen accessory charging case and/or accessory device.

In some embodiments, the case detects (836) a third event comprising a change of state of the accessory charging case, and, in response to detecting the third event: (i) in accordance with a determination that a sound setting for the accessory charging case is in an enabled state, the case causes the speaker to generate a fourth audio notification; and (ii) in accordance with a determination that the sound setting for the accessory charging case is in a disabled state, the case forgoes causing the fourth audio notification to be generated. For example,FIG.5AVshows wireless accessory case480having disabled audio outputs (e.g., as illustrated by volume indicator5100). In some embodiments, in response to an event while wireless accessory case480has disabled audio outputs, wireless accessory case480forgoes causing an audio notification to be generated. In some embodiments, a user input is detected at the accessory charging case (e.g., via a hardware or software button), and, in response to the user input, the sound setting is set to the disabled state (or toggled off). Forgoing providing an audio notification in accordance with a sound setting being in a disabled state improves security/privacy by preventing undesirable audio notifications (e.g., while the user is in a crowded/public location). Additionally, forgoing undesirable audio notifications reduces power usage and improves battery life of the device.

In some embodiments, an electronic device (e.g., electronic device100) distinct from the accessory charging case causes (838) a user interface (e.g., user interface5090) to be displayed via a display generation component, the user interface including a control element (e.g., volume control element5091) for the sound setting for the accessory charging case, detects an input that corresponds to the control element (e.g., user input5098), and, in response to detecting the input, causes the sound setting for the accessory charging case to be set to the disabled state (e.g., as illustrated by volume level indicator5099inFIG.5AV). In some embodiments, in response to detecting the input, the electronic device causes the sound setting for the accessory charging case to be toggled from a prior state to a new state. For example, the accessory charging case forgoes generating audio notifications while the sound setting is in the disabled state (e.g., forgoes generating an audio notification in response to detecting events occurring at the accessory charging case and/or involving the accessory charging case). In some embodiments, generating audio notifications via the speaker is conditional on the sound setting being set to an enabled state. In some embodiments, the accessory charging case includes a haptic output device and, in response to events occurring at the accessory charging case and/or involving the accessory charging case, the haptic output device generates haptic feedback (e.g., in addition to or alternatively to generating audio notifications). Displaying the user interface with the control element for the sound setting reduces the number of inputs needed to set the sound setting for the accessory charging case to the disabled state.

In some embodiments, after setting the sound setting for the accessory charging case to the disabled state, the case detects (840) a fourth event including a change in an opened or closed state of the accessory charging case, and, in response to detecting the fourth event and in accordance with the sound setting being in the disabled state, the case forgoes causing the speaker to generate an audio notification corresponding to a status for the accessory charging case and/or one or more accessories associated with the accessory charging case (e.g., forgoes generating audio feedback5018and/or5020). In some embodiments, causing the speaker to generate the audio notification corresponding to the status for at least one of the accessory charging case and the one or more accessories associated with the accessory charging case is in accordance with a determination that the sound setting is set to an enabled state. Forgoing providing an audio notification in accordance with a sound setting being in a disabled state improves security/privacy by preventing undesirable audio notifications (e.g., while the user is in a crowded/public location). Additionally, forgoing undesirable audio notifications reduces power usage and improves battery life of the device.

In some embodiments, the case sets (842) the sound setting to the disabled state in accordance with an audio output silencing setting (e.g., a ring silencing setting and/or an audio notification silencing setting) being enabled at an electronic device that is communicatively coupled to the accessory charging case (e.g., as illustrated inFIGS.5AX-5AY). In some embodiments, a user input corresponding to the ring silencing setting is detected at a companion device (e.g., at the electronic device100, e.g., via a hardware or software affordance); and, in response to the user input, the ring silencing setting is enabled (or toggled on). In some embodiments, while the audio output silencing setting is enabled, the electronic device forgoes generating audio notifications in response to an incoming phone call, text message, voicemail, electronic mail, and/or calendar events. In some embodiments, the electronic device includes a hardware switch configured to toggle the audio output silencing setting between enabled and disabled states. In some embodiments, the electronic device includes a hardware volume button and a first type of user input at the hardware volume button causes the audio output silencing setting to be enabled. In some embodiments, the electronic device causes an audio control user interface to be displayed and the audio control user interface includes a selectable silencing element that, when selected, causes the audio output silencing setting to be enabled. Alternatively, the audio control user interface of the electronic device includes a volume control element that enables the user to set audio output volume to zero. Configuring the sound setting of the accessory case based on the audio output silencing setting or volume control setting of the electronic device avoids requiring the user to configure sound settings of the device and accessory case individually, which reduces the number of inputs needed to perform the operations.

In some embodiments, the case sets (844) the sound setting to the disabled state in accordance with a focus mode being active at an electronic device that is communicatively coupled to the accessory charging case. For example,FIGS.5BB-5BEillustrate activation of a focus mode (e.g., a do-not-disturb mode) and a corresponding silencing of wireless accessory device480as illustrated by volume indicator5138. Configuring the sound setting of the accessory case based on the focus mode of the device avoids requiring the user to configure sound settings of the device and accessory case individually, which reduces the number of inputs needed to perform the operation.

In some embodiments, the sound setting for the accessory charging case is (846) set to the disabled state in accordance with the electronic device being communicatively coupled to at least one of the one or more accessories associated with the accessory charging case. For example,FIGS.5BH-5BIillustrate wearable audio output devices5142moving inside threshold distance5119while in communication with electronic device100and wireless accessory case480, and corresponding silencing of wireless accessory device480as illustrated by volume indicator5150. Configuring the sound setting of the accessory case based on settings of a device in communication with one or more accessories associated with the accessory charging case avoids requiring the user to configure sound settings of the device and accessory case individually, which reduces the number of inputs needed to perform the operation. Additionally, configuring the sound setting of the accessory case based on settings of a device in communication with one or more accessories associated with the accessory charging case avoids requiring the user to connect the accessory charging case and the device directly, which reduces the number of inputs/user interactions required to perform the operation.

In some embodiments, an enablement state of the sound setting is (848) stored at the accessory charging case (e.g., is stored in memory349). In some embodiments, the setting state is synchronized with the electronic device (or server system or other device associated with the same user account) in accordance with a communicative coupling being established between the electronic device and the accessory charging device). For example, in accordance with the accessory charging state being paired or connected to a first user device (e.g., a phone, laptop, or other electronic device), the accessory charging case obtains sound setting information from the first user device (e.g., based on a silence setting of the first user device) that, in this example, causes the sound setting to be set to the enabled state. Further, the accessory charging case internally maintains that setting until the setting is changed by the first user device or another user device. To continue the example, the accessory charging case subsequently pairs or connects with a second user device and obtains second sound setting information from the second user device. In this example, the second sound setting information causes the sound setting to be set to the disabled state (e.g., in accordance with the second user device having an audio output silencing setting enabled). Saving the enablement state of the sound setting and reusing the same enablement state avoids requiring the user to subsequently configure the enablement state of the sound setting when subsequently interacting with the accessory case, which reduces the number of inputs needed to perform the operation.

It should be understood that the particular order in which the operations inFIGS.8A-8Dhave been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods600,700, and900) are also applicable in an analogous manner to method800described above with respect toFIGS.8A-8D. For example, the inputs, gestures, functions, and feedback described above with reference to method800optionally have one or more of the characteristics of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods600,700, and900). For brevity, these details are not repeated here.

FIGS.9A-9Care flow diagrams illustrating method900of adjusting audio output of a wearable audio output device in accordance with some embodiments. Method900is performed at an electronic device (e.g., device300,FIG.3, or portable multifunction device100,FIG.1A) including, or in communication with, a display generation component and, optionally, a touch-sensitive surface. In some embodiments, the electronic device is a desktop computer, a laptop computer, a tablet, a smartphone, a smart watch, or other computing device. In some embodiments, the display generation component is a touch-screen display. In some embodiments, the display is separate from a touch-sensitive surface. Some operations in method900are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, method900provides an improved interface for controlling audio outputs by changing the audio output mode of an audio output device, such as a wearable device, between audio pass-through and conversation boost in response to a particular type of gesture. Providing additional control options for controlling audio outputs, such as changing the audio output mode in response to particular gestures reduces clutter on the user interface, reduces the number of inputs needed to perform the control options, enhances the operability of the electronic device, and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the electronic device), which, additionally, reduces power usage and improves battery life of the electronic device by enabling the user to use the electronic device more quickly and efficiently.

The electronic device causes (902) a user interface to be displayed (e.g., user interface5164), the user interface including a volume control element (e.g., volume control5166, shown inFIGS.5BL-5BO) for one or more wearable audio output devices (e.g., headphones or earbuds).

The electronic device detects (904) an input that corresponds to the volume control element (e.g., detects via a touchscreen, motion sensors, rotatable input element, button, or the like).

In response to detecting the input: (i) in accordance with a determination that the input is a first type of gesture (e.g., the input satisfies first gesture criteria, such as swipe gesture criteria that require application of a touch input and movement of the touch input), the electronic device adjusts (906) a volume of the audio output of the one or more wearable audio output devices; and, (ii) in accordance with a determination that the input is a second type of gesture (e.g., a tap, double tap, or a long press), the electronic device causes display of a conversation boost element for the one or more wearable audio output devices that, when selected, initiates a process for adjusting audio output of the one or more wearable audio output devices to boost conversation audio, corresponding to conversations with audio that is accessible to the one or more wearable audio output devices, relative to other audio being output by the one or more wearable audio output devices. For example,FIG.5BMshows user input5168(e.g., a swipe or drag gesture) andFIG.5BNshows a corresponding change in volume of audio output. To further the example,FIG.5BOshows user input5182(e.g., a tap or press gesture) andFIG.5BPshows corresponding user interface5184with conversation boost control5190. In some embodiments, the electronic device concurrently displays a volume control element and a conversation boost element (e.g., as shown in user interface5184, as shown inFIG.5BP). In some embodiments, the first type of gesture is a swipe, a drag, a rotation, and/or an air gesture. In some embodiments, the conversation audio includes conversation audio that is being picked up by one or more microphones of the wearable audio output devices, conversation audio that is being picked up by one or more microphones of the electronic device, and/or conversation audio that is being picked up by one or more external microphones. In some embodiments, the second type of gesture is a double tap gesture that meets one or more gesture criteria that require two single tap gestures performed within a threshold amount of time of each other and within a threshold distance of each other. In some embodiments, in response to activation (e.g., by a force press or long press on an input device (a touch-sensitive surface or mechanical button) of the volume control element, the electronic device updates the user interface (or replaces display of the (e.g., first) user interface with display of a second user interface) to include the conversation boost element. In some embodiments, the conversation boost element is conditionally displayed (at least in part) in accordance with a determination that the one or more wearable audio output devices is in communication with the electronic device and that the one or more wearable audio output devices are in use (e.g., by playing audio or being inserted in the user's ear). In some embodiments, while the one or more wearable audio output devices are not in communication with the electronic device and/or not in use, the conversation boost element is not displayed.

In some embodiments, selection of the conversation boost element initiates (908) the process for adjusting audio output of the one or more wearable audio output devices to boost conversation audio while active noise cancelation for ambient noise is disabled at the one or more wearable audio output devices. For example, the conversation boost is not active while in a noise cancelation mode (e.g., as illustrated inFIG.5BV), or while noise control is disabled (e.g., while noise cancelation is off, as opposed to being in transparency mode). In some embodiments, selection of the conversation boost element initiates the process for adjusting audio output of the one or more wearable audio output devices to boost conversation audio while transparency for ambient sound is enabled (e.g., is greater than zero or another preset threshold) at the one or more wearable audio output devices. Adjusting audio output to boost conversation audio only while ANC is disabled enhances the operability of the devices and reduces power usage and improves battery life of the devices.

In some embodiments, the first type of gesture is (910) a swipe gesture at a location that corresponds to the volume control element and the volume is adjusted in accordance with movement of the swipe gesture (e.g., as illustrated inFIGS.5BM-5BN), and the second type of gesture is a press gesture at the location that corresponds to the volume control element (e.g., as illustrated inFIG.5BO). Detecting and being responsive in different ways to different types of gestures enhances operability of the device (e.g., provides flexibility without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, in response to detecting the input, in accordance with a determination that the input is a third type of gesture, the electronic device activates (912) an audio function that is distinct from the volume adjustment and the display of the conversation boost element (e.g., the function changes an audio setting or mode of the wearable audio output devices). For example, the third type of gesture is a long press and/or a deep press and the audio function changes an audio mode (e.g., a noise control mode). Detecting and being responsive in different ways to different types of gestures enhances operability of the device (e.g., provides flexibility without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, in accordance with the determination that the input is the second type of gesture, the electronic device causes (914) display of an audio control user interface (e.g., user interface5184,FIG.5BP) that includes a plurality of elements (e.g., noise control5194, spatial audio control5192, and conversation boost control5190) for operation for the one or more wearable audio output devices, where the plurality of elements includes the conversation boost element (e.g., conversation boost control5190). Displaying the audio control user interface in response to a particular type of gesture enhances operability of the electronic device (e.g., provides flexibility without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the plurality of elements includes (916) an ambient noise control element (e.g., noise control5194) and one or more spatial audio control elements (e.g., spatial audio control5192). For example, the spatial audio control settings include a balance setting, a stereo setting, and/or an amplification setting. In some embodiments, when selected, the ambient noise control element causes activation of an ambient noise adjustment function. In some embodiments, the ambient noise control element, when selected, adjusts active noise cancelation for ambient noise, transparency for ambient sound, and/or other ambient sound functions. For example, increasing transparency for ambient sound includes using external microphones at the one or more wearable audio output devices to capture audio and play it via one or more speakers at the one or more wearable audio output devices. In some embodiments, the electronic device or the one or more wearable audio output devices includes one or more pass-through audio components (e.g., active when the device or one or more wearable audio output devices is operating in the transparency mode) and one or more cancelation audio components (e.g., active when the device or one or more wearable audio output devices is operating in a noise cancelation mode). Presenting an ambient noise control element and a conversation boost element enhances operability of the device (e.g., provides flexibility by reducing the number of inputs needed) and makes the user-device interface more efficient.

In some embodiments, the plurality of elements includes (920) a live listen element (e.g., live listen control5234, shown inFIG.5BX) that, when selected, initiates a process for providing audio data at the one or more wearable audio output devices, where the audio data is captured via a microphone at the electronic device. In some embodiments, selection of the live listen element causes a live listen mode to be enabled (e.g., selection of the live listen element toggles the live listen mode). In some embodiments, while the live listen mode is enabled, audio data is captured via one or more microphones at the electronic device and transmitted to a remote audio output device (e.g., a headset, earbuds, or device including a speaker component) for playback to a user. For example, audio data captured via the one or more microphones is transmitted to a paired headset (or one or more wearable audio output devices) worn by the user so that the user is provided playback of sounds occurring around the electronic device. Presenting a live listen element and a conversation boost element enhances operability of the device (e.g., provides flexibility by reducing the number of inputs needed) and makes the user-device interface more efficient.

In some embodiments, the plurality of elements includes (922) a background sound element (e.g., background sounds control5232, shown inFIG.5BX) that, when selected, initiates a process for producing background sound at the one or more wearable audio output devices (e.g., producing white noise, water sounds (e.g., ocean or rain sounds), or other sounds intended to mask environmental noise). Presenting a background sound element and a conversation boost element enhances operability of the device (e.g., provides flexibility by reducing the number of inputs needed) and makes the user-device interface more efficient.

In some embodiments, the plurality of elements includes (924) an element (e.g., reduce loud sounds control5235, shown inFIG.5BX) that, when selected, initiates a process to reduce a volume of sounds that meet one or more criteria (e.g., the one or more criteria comprise a maximum decibel threshold that is set by the electronic device and/or the user). In some embodiments, a maximum decibel slider is displayed with (or in response to selection of) the element for reducing loud sounds, e.g., as shown inFIG.5CB. Presenting a reduce loud sounds element and a conversation boost element enhances operability of the device (e.g., provides flexibility by reducing the number of inputs needed) and makes the user-device interface more efficient.

In some embodiments, the electronic device detects (926) a second input that corresponds to the volume control element, and, in response to the second input: (i) in accordance with a determination that the second input is the second type of gesture and at least one of the one or more wearable audio output devices is operating in a transparency mode (e.g., as illustrated by noise control5194inFIG.5BQ), the electronic device causes display of the conversation boost element; and (ii) in accordance with a determination that the second input is the second type of gesture and the one or more wearable audio output devices are not operating in the transparency mode, the electronic device forgoes causing the conversation boost element to be displayed (e.g., display of the conversation boost element is replaced with display of a control element for noise control or spatial audio control). In some embodiments, conversation boost control5190is not displayed in user interface5184in accordance with an ANC mode being active. Forgoing displaying the conversation boost element while the device is not operating in the transparency mode enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.

In some embodiments, while the conversation boost element is displayed, the electronic device detects (928) a third input (e.g., a tap, double tap, or long press gesture) that corresponds to the conversation boost element, in response to detecting the third input, the electronic device causes a conversation boost adjustment control to be displayed, e.g., as shown inFIGS.5BR-5BQ. Further, while the conversation boost adjustment control is displayed, the electronic device detects a fourth input that corresponds to the conversation boost adjustment control, and, in response to detecting the fourth input, the electronic device adjusts an amount of adjustment applied to the conversation audio in accordance with the fourth input. For example,FIG.5BQshows input5198at conversation boost control5190andFIG.5BRshows display of conversation boost adjustment control5206in response to input5198. For example, the fourth input is a swipe, drag, rotation, or air gesture and the adjustment is based on movement and/or direction of the gesture. In some embodiments, display of the conversation boost slider replaces display of the conversation boost element. In some embodiments, the conversation boost slider is displayed adjacent to the conversation boost element (e.g., the conversation boost slider replaces one or more other elements in the user interface, such as control element(s) for transparency and/or spatial audio) Alternatively, in some embodiments, the conversation boost slider is (automatically) displayed in response to detecting the first input, or in response to the detecting the first input and satisfaction of additional criteria (e.g., passage of at least a predefined amount of time while continuing to display the (settings) user interface). In some embodiments, the amount of adjustment and/or direction of adjustment (e.g., increase or decrease) corresponds to movement, direction, location, duration, force, and/or pressure of the fourth input. In some embodiments, the fourth input is a particular type of input (e.g., tap) and the amount of adjustment is preset for the particular type of input (e.g., 5, 10, 20, 25, 40, or 50 percent or 5, 10, 25, 50, or 100 units (e.g., dB) increase per tap). Displaying the conversation boost adjustment control and adjusting the amount of adjustment applied to the conversation audio in accordance with an input at the conversation boost adjustment control enhances operability of the device (e.g., provides flexibility without cluttering the user interface with additional displayed controls, as well as reducing the number of inputs needed to access this flexibility) and makes the user-device interface more efficient.

In some embodiments, the electronic device detects (930) a sequence of one or more inputs including a fifth input (e.g., a tap, double tap, or long press gesture) that corresponds to an accessibility user interface element (e.g., hearing control5222,FIG.5BW), and, in response to detecting the fifth input, the electronic device causes the accessibility user interface (e.g., user interface5230,FIG.5BX) to be displayed, the accessibility user interface including the conversation boost element (e.g., conversation boost control5242). For example, the accessibility user interface element is displayed within a control center UI or settings menu for the one or more wearable audio output devices. In some embodiments, the sequence of one or more inputs includes one or more of: an input corresponding to an accessibility element (e.g., that when selected causes an accessibility user interface to be displayed) in a settings user interface, an input corresponding an audio element (e.g., that when selected causes an audio accessibility user interface to be displayed) in the accessibility user interface, and an input corresponding to a wearable audio output device accommodation element (e.g., that when selected causes a wearable audio output device accommodation user interface to be displayed) in the audio accessibility user interface. In some embodiments, the sequence of one or more inputs includes an input corresponding to a control center element (e.g., that when selected causes a control center user interface to be displayed) in a settings user interface, and/or an input corresponding to a hearing element (e.g., that when selected causes a hearing user interface to be displayed) in the control center user interface. In some embodiments, the sequence of one or more inputs includes one or more of: an input corresponding to an audio control center element (e.g., that when selected causes an audio control center user interface to be displayed) in a control center interface, an input corresponding to a wearable audio output device accommodation element (e.g., that when selected causes a wearable audio output device accommodation user interface to be displayed) in the audio control center user interface, and an input corresponding to an ambient noise control element in the wearable audio output device accommodation user interface. Displaying the accessibility user interface in response to the sequence of one or more inputs enhances operability of the device (e.g., provides flexibility without cluttering the user interface with additional displayed controls) and makes the user-device interface more efficient.

It should be understood that the particular order in which the operations inFIGS.9A-9Chave been described is merely an example and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods600,700, and800) are also applicable in an analogous manner to method900described above with respect toFIGS.9A-9C. For example, the inputs, gestures, functions, and feedback described above with reference to method900optionally have one or more of the characteristics of the inputs, gestures, functions, and feedback described herein with reference to other methods described herein (e.g., methods600,700, and800). For brevity, these details are not repeated here.