User interface for voice messages

Abstract

To provide a method of managing an audio message, a computer system, an electronic device, and a recording medium.SOLUTION: A method of transmitting an audio message by a computer system includes the steps of: displaying a first user interface through a display generating element; receiving an input corresponding to a request to display a second user interface while the first user interface is displayed or a plurality of user inputs received while a selectable first user interface object is displayed; displaying the second user interface in response to reception of the request to display the second user interface; receiving an audio input including a natural language request of a digital assistant through a microphone; and transmitting an audio message to any set of devices.SELECTED DRAWING: Figure 8A

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is related to U.S. Provisional Patent Application No. 63 / 023,225, filed May 11, 2020, and entitled “USER INTERFACE FOR AUDIO MESSAGE,” the contents of which are incorporated by reference in their entirety herein.

[0002] FIELD OF THE DISCLOSURE This disclosure relates generally to computer user interfaces, and more specifically to techniques for managing voice messages. [Background technology]

[0003] Users use alphanumeric characters to send instant messages to communicate with other users. Such messaging technologies typically require the user to enter characters using a keyboard or the device to phonetically transcribe speech into characters that are then transmitted. Users use mobile devices to interact with external devices. Such interactions are often cumbersome and require users to interact with multiple external devices individually. Summary of the Invention

[0004] Current techniques for managing voice messages using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing voice messages. Such methods and interfaces optionally complement or replace other methods for managing messages. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and extend the time between battery charges. Such methods and interfaces allow sending messages that include the tone of the message (e.g., importance, seriousness, sarcasm, sadness, merriment) rather than just the words of the message, and allow the recipient to recognize the speaker of a message by the speaker's unique voice. Such methods and interfaces also reduce or eliminate the need to use a keyboard to provide input or to use input to correct phonetic transcriptions.

[0006] Current techniques for managing the state of external devices on mobile devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or strokes. Existing techniques take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0007] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing external devices. Such methods and interfaces optionally complement or replace other methods for managing external devices, such as allowing a user to manage individual external devices or manage external devices simultaneously via a single input. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0008] According to some embodiments, a method is described. The method is executed on a computer system in communication with a display generation component. The method includes displaying, via the display generation component, a first user interface, a first selectable user interface object object, where selection of the first selectable user interface object object initiates a process for recording and transmitting a first voice message to a set of external devices, the set of external devices including a first set of one or more external devices and a second set of one or more external devices, and a first accessory control user interface object object corresponding to the first external accessory device, where selection of the first accessory control user interface object object initiates a process for transmitting an instruction to change a state of the first external accessory device, and responding to a request to display a second user interface while displaying the first user interface. receiving the corresponding input; and, in response to receiving the request to display the second user interface, displaying a second user interface, the second user interface including a second selectable user interface object object, where selection of the second selectable user interface object object initiates a process for recording and transmitting a second voice message to a second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices, and a second accessory control user interface object object corresponding to the second external accessory device, where selection of the second accessory control user interface object object initiates a process for transmitting an instruction to change a state of the second external accessory device.

[0009] According to some embodiments, a non-transitory computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs configured to generate a first user interface via the display generation component, the first selectable user interface object object, where selection of the first selectable user interface object object initiates a process for recording and transmitting a first voice message to a set of external devices, the set of external devices including a first set of one or more external devices and a second set of one or more external devices, and a first accessory control user interface object object corresponding to the first external accessory device, where selection of the first accessory control user interface object object initiates a process for transmitting an instruction to change a state of the first external accessory device. displaying, while displaying the first user interface, receiving an input corresponding to a request to display a second user interface, and in response to receiving the request to display the second user interface, displaying the second user interface, the second user interface including instructions to display a second selectable user interface object object, where selection of the second selectable user interface object object initiates a process for recording and transmitting a second voice message to a second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices, and a second accessory control user interface object object corresponding to the second external accessory device, where selection of the second accessory control user interface object object initiates a process for transmitting an instruction to change a state of the second external accessory device.

[0010] According to some embodiments, a temporary computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs displaying a first user interface via the display generation component, a first selectable user interface object object, where selection of the first selectable user interface object object initiates a process for recording and transmitting a first voice message to a set of external devices, the set of external devices including a first set of one or more external devices and a second set of one or more external devices, and a first accessory control user interface object object corresponding to the first external accessory device, where selection of the first accessory control user interface object object initiates a process for transmitting an instruction to change a state of the first external accessory device. and while displaying the first user interface, receiving an input corresponding to a request to display a second user interface, and in response to receiving the request to display the second user interface, displaying the second user interface, the second user interface including instructions to display a second selectable user interface object object, where selection of the second selectable user interface object object initiates a process for recording and transmitting a second voice message to a second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices, and a second accessory control user interface object object corresponding to the second external accessory device, where selection of the second accessory control user interface object object initiates a process for transmitting an instruction to change a state of the second external accessory device.

[0011] According to some embodiments, a computer system is described that includes one or more processors in communication with a display generation component and a memory storing one or more programs configured to be executed by the one or more processors to select a first user interface object via the display generation component, the selection of the first selectable user interface object object initiating a process for recording and transmitting a first voice message to a set of external devices, the set of external devices including a first set of one or more external devices and a second set of one or more external devices, and a first accessory control user interface object object corresponding to the first external accessory device, the selection of the first accessory control user interface object object initiating a process for transmitting an instruction to change a state of the first external accessory device. displaying an interface; receiving an input corresponding to a request to display a second user interface while displaying the first user interface; and in response to receiving the request to display the second user interface, displaying the second user interface, the second user interface including instructions to display a second selectable user interface object object, where selection of the second selectable user interface object object initiates a process for recording and transmitting a second voice message to a second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices, and a second accessory control user interface object object corresponding to the second external accessory device, where selection of the second accessory control user interface object object initiates a process for transmitting an instruction to change a state of the second external accessory device.

[0012] According to some embodiments, a computer system is described that includes means for displaying, via a display generation component in communication with the computer system, a first user interface including a first selectable user interface object object, selection of the first selectable user interface object object initiates a process for recording and transmitting a first voice message to a set of external devices, the set of external devices including a first set of one or more external devices and a second set of one or more external devices, and a first accessory control user interface object object corresponding to the first external accessory device, selection of the first accessory control user interface object object initiates a process for transmitting an instruction to change a state of the first external accessory device, and means for displaying, while displaying the first user interface, a first selectable user interface object object, selection of the first accessory control user interface object object initiates a process for transmitting an instruction to change a state of the first external accessory device. and means for displaying the second user interface in response to receiving the request to display the second user interface, the second user interface including a second selectable user interface object object, selection of the second selectable user interface object object initiating a process for recording and transmitting a second voice message to a second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices, and a second accessory control user interface object object corresponding to the second external accessory device, selection of the second accessory control user interface object object initiating a process for transmitting an instruction to change a state of the second external accessory device.

[0013] According to some embodiments, a method is described. The method is executed on a computer system in communication with a display generation component. The method includes receiving first data corresponding to a first media, displaying a first notification via the display generation component with a suggestion of the first media until an end of a first time period, receiving second data corresponding to a second media after receiving the first data, the second media being different from the first media, and displaying a second notification via the display generation component with a suggestion of the first media until an end of a second time period according to a determination that the second media satisfies a set of one or more criteria and a determination based on (1) a time when the second data was received and (2) a time when the first data was received, the second notification with the suggestion of the first media until an end of a second time period, the end of the first time period being different from an end of the second time period.

[0014] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display component, the one or more programs including receiving first data corresponding to a first medium, displaying, via a display generation component, a first notification having an indication of the first medium until an end of a first time period, receiving second data corresponding to a second medium after receiving the first data, the second medium being different from the first medium, and displaying, via the display generation component, a second notification having an indication of the first medium until an end of a second time period in accordance with a determination that the second media satisfies a set of one or more criteria and in accordance with a determination based on (1) a time at which the second data was received and (2) a time at which the first data was received, the second notification having an indication of the first media until an end of a second time period in accordance with a determination that the second media satisfies a set of one or more criteria, the second notification being different from an end of the second time period.

[0015] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display component, the one or more programs including receiving first data corresponding to a first medium, displaying, via a display generation component, a first notification having an indication of the first medium until an end of a first time period, receiving second data corresponding to a second medium after receiving the first data, the second medium being different from the first medium, and displaying, via the display generation component, a second notification having an indication of the first medium until an end of a second time period in accordance with a determination that the second medium satisfies a set of one or more criteria and in accordance with a determination based on (1) a time at which the second data was received and (2) a time at which the first data was received, the second notification having an indication of the first medium until an end of a second time period, the end of the first time period being different from an end of the second time period.

[0016] According to some embodiments, a computer system is described that includes one or more processors in communication with a display component and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including receiving first data corresponding to a first media, displaying, via the display generation component, a first notification having a suggestion of the first media until an end of a first time period, receiving second data corresponding to a second media after receiving the first data, the second media being different from the first media, and displaying, via the display generation component, a second notification having a suggestion of the first media until an end of a second time period, the end of the first time period being different from an end of the second time period, in accordance with a determination that the second media satisfies a set of one or more criteria and in accordance with a determination based on (1) a time at which the second data was received and (2) a time at which the first data was received.

[0017] According to some embodiments, a computer system is described that includes means for receiving first data corresponding to a first media, means for displaying, via a generation component in communication with the computer system, a first notification having an indication of the first media until an end of a first time period, means for receiving, after receiving the first data, second data corresponding to a second media, the second media being different from the first media, and means for displaying, via a display generation component, the second notification having an indication of the first media until an end of a second time period in accordance with a determination that the second media satisfies a set of one or more criteria and in accordance with a determination based on (1) a time at which the second data was received and (2) a time at which the first data was received, the second notification having an indication of the first media until an end of a second time period, the end of the first time period being different from an end of the second time period.

[0018] According to some embodiments, a method is described. The method is performed on an electronic device having one or more microphones, one or more speakers, and one or more display devices. The method includes receiving audio input via the one or more microphones and displaying a visual indication of the audio input, where in response to a determination that a portion of the audio input corresponds to the audio input being transmitted to one or more devices for display via the one or more display devices, the visual indication includes displaying a visual indication having a first set of one or more colors, and in response to a determination that the audio input does not include instructions for transmitting any portion of the audio input to another device for display via the one or more display devices, the visual indication includes displaying a second set of one or more colors different from the first set of one or more colors.

[0019] According to some embodiments, a non-transitory computer readable storage medium is described, the non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having one or more microphones, one or more speakers, and one or more display devices, the one or more programs including instructions for receiving audio input via the one or more microphones and displaying a visual indication of the audio input, where in response to a determination that a portion of the audio input corresponds to the audio input transmitted to one or more devices for display via the one or more display devices, the visual indication includes displaying a visual indication having a first set of one or more colors, and where in response to a determination that the audio input does not include instructions for transmitting any portion of the audio input to another device for display via the one or more display devices, the visual indication includes displaying a visual indication having a second set of one or more colors different from the first set of one or more colors.

[0020] According to some embodiments, a temporary computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having one or more microphones, one or more speakers, and one or more display devices, the one or more programs including instructions for receiving audio input via the one or more microphones and displaying a visual indication of the audio input, where in response to a determination that a portion of the audio input corresponds to the audio input transmitted to one or more devices for display via the one or more display devices, the visual indication includes displaying a visual indication having a first set of one or more colors, and in response to a determination that the audio input does not include instructions for transmitting any portion of the audio input to another device for display via the one or more display devices, the visual indication includes displaying a visual indication having a second set of one or more colors different from the first set of one or more colors.

[0021] According to some embodiments, an electronic device is described that includes one or more microphones, one or more speakers, one or more display devices, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for receiving audio input via the one or more microphones and displaying a visual indication of the audio input, where in response to a determination that a portion of the audio input corresponds to the audio input transmitted to one or more devices for display via the one or more display devices, the visual indication includes displaying a visual indication having a first set of one or more colors, and where in response to a determination that the audio input does not include instructions for transmitting any portion of the audio input to another device for display via the one or more display devices, the visual indication includes displaying a visual indication having a second set of one or more colors different from the first set of one or more colors.

[0022] According to some embodiments, an electronic device is described that includes one or more microphones, one or more speakers, one or more display devices, means for receiving audio input via the one or more microphones, and means for displaying a visual indication of the audio input, where in response to a determination that a portion of the audio input corresponds to the audio input being transmitted to one or more devices for display via the one or more display devices, the visual indication includes displaying a visual indication having a first set of one or more colors, and in response to a determination that the audio input does not include instructions for transmitting any portion of the audio input to another device for display via the one or more display devices, the visual indication includes displaying a second set of one or more colors different from the first set of one or more colors.

[0023] According to some embodiments, a method is described that is executed on a computer system that is in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a first state indicating that a plurality of accessory devices of a first accessory type are in a first state, the plurality of accessory devices of the first accessory type including a first accessory device of the first accessory type and in the first state and a second accessory device of the first accessory type and in the first state, the second accessory device being different from the first accessory device; detecting a gesture while displaying the first state indicator; and in response to detecting the gesture, indicating that the gesture is a gesture of a first type and is directed toward the first state indicator. The method includes causing the first accessory device and the second accessory device to change to a second state different from the first state in accordance with the determination, and displaying, via a display generation component, a first accessory control user interface object object corresponding to the first accessory device in accordance with a determination that the gesture is a second type of gesture different from the first type of gesture and is directed toward the first state indicator, wherein selection of the first accessory control user interface object object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.

[0024] According to some embodiments, a non-transitory computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs displaying, via the display generating component, a first state indicating that a plurality of accessory devices of a first accessory type are in a first state, the plurality of accessory devices of the first accessory type including a first accessory device that is the first accessory type and in the first state and a second accessory device that is the first accessory type and in the first state, the second accessory device being different from the first accessory device, and displaying a gesture while displaying the first state indicator. and in response to detecting the gesture, causing the first accessory device and the second accessory device to change to a second state different from the first state in accordance with a determination that the gesture is a first type of gesture and is directed toward the first state indicator, and displaying, via the display generation component, a first accessory control user interface object object corresponding to the first accessory device in accordance with a determination that the gesture is a second type of gesture different from the first type of gesture and is directed toward the first state indicator, wherein selection of the first accessory control user interface object object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.

[0025] According to some embodiments, a temporary computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs configured to display, via the display generating component, a first state indicating that a plurality of accessory devices of a first accessory type are in a first state, the plurality of accessory devices of the first accessory type including a first accessory device that is the first accessory type and in the first state and a second accessory device that is the first accessory type and in the first state, the second accessory device being different from the first accessory device, and to display a gesture while displaying the first state indicator. and in response to detecting the gesture, causing the first accessory device and the second accessory device to change to a second state different from the first state in accordance with a determination that the gesture is a first type of gesture and is directed toward the first state indicator, and displaying, via the display generation component, a first accessory control user interface object object corresponding to the first accessory device in accordance with a determination that the gesture is a second type of gesture different from the first type of gesture and is directed toward the first state indicator, wherein selection of the first accessory control user interface object object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.

[0026] According to some embodiments, a computer system is described that includes one or more processors in communication with a display generation component and one or more input devices, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs configured to display, via the display generation component, a first state indicating that a plurality of accessory devices of a first accessory type are in a first state, the plurality of accessory devices of the first accessory type including a first accessory device that is the first accessory type and in the first state and a second accessory device that is the first accessory type and in the first state, the second accessory device being different from the first accessory device, and displaying a gesture while displaying the first state indicator. and in response to detecting the gesture, causing the first accessory device and the second accessory device to change to a second state different from the first state in accordance with a determination that the gesture is a first type of gesture and is directed toward the first state indicator, and displaying, via the display generation component, a first accessory control user interface object object corresponding to the first accessory device in accordance with a determination that the gesture is a second type of gesture different from the first type of gesture and is directed toward the first state indicator, wherein selection of the first accessory control user interface object object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.

[0027] According to some embodiments, a computer system is described that includes means for displaying, via a display generating component, a first state indicating that a plurality of accessory devices of a first accessory type are in a first state, the plurality of accessory devices of the first accessory type including a first accessory device of the first accessory type and in the first state and a second accessory device of the first accessory type and in the first state, the second accessory device being different from the first accessory device, means for detecting a gesture while displaying the first state indicator, and means for detecting, in response to detecting the gesture, a gesture of the first type and a first state indicating that the gesture is a gesture of the first type and a first state indicating that the gesture is a gesture of the first accessory ... means for changing the first accessory device and the second accessory device to a second state different from the first state in accordance with a determination that the gesture is a second type gesture different from the first type gesture and is directed to the first status indicator, and means for displaying via the display generation component a first accessory control user interface object object corresponding to the first accessory device in accordance with a determination that the gesture is a second type gesture different from the first type gesture and is directed to the first status indicator, wherein selection of the first accessory control user interface object object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.

[0028] According to some embodiments, a method is described. The method is executed on a computer system in communication with a display generation component and one or more input devices. The method includes displaying, via the display generation component, a media user interface including a first representation of a first media message at a first location and a second representation of a second media message at a second location different from the first location, in response to displaying the media user interface, playing the first media message without based on a user input corresponding to the media user interface, and in response to detecting completion of playing the first media message, displaying the second representation of the second media message without displaying a representation corresponding to the first media message via the display generation component.

[0029] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for displaying, via the display generation component, a media user interface including a first representation of a first media message at a first location and a second representation of a second media message at a second location different from the first location, in response to displaying the media user interface, playing the first media message without based on a user input corresponding to the media user interface, and in response to detecting completion of playing the first media message, displaying the second representation of the second media message without displaying a representation corresponding to the first media message via the display generation component.

[0030] According to some embodiments, a temporary computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for displaying, via the display generation component, a media user interface including a first representation of a first media message at a first location and a second representation of a second media message at a second location different from the first location, in response to displaying the media user interface, playing the first media message without based on a user input corresponding to the media user interface, and in response to detecting completion of playing the first media message, displaying the second representation of the second media message without displaying a representation corresponding to the first media message via the display generation component.

[0031] According to some embodiments, a computer system is described that includes one or more processors in communication with a display generation component and one or more input devices, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying, via the display generation component, a media user interface including a first representation of a first media message at a first location and a second representation of a second media message at a second location different from the first location, in response to displaying the media user interface, playing the first media message without based on a user input corresponding to the media user interface, and in response to detecting completion of playing the first media message, displaying the second representation of the second media message without displaying a representation corresponding to the first media message via the display generation component.

[0032] According to some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more input devices. The computer system comprises means for displaying, via the display generation component, a media user interface including a first representation of a first media message at a first location and a second representation of a second media message at a second location different from the first location, means for playing the first media message without based on a user input corresponding to the media user interface in response to displaying the media user interface, and means for displaying the second representation of the second media message without displaying a representation corresponding to the first media message via the display generation component in response to detecting completion of playing the first media message.

[0033] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0034] Thus, devices are provided with faster, more efficient methods and interfaces for managing voice messages, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices, and such methods and interfaces may complement or replace other methods for managing voice messages. [Brief description of the drawings]

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

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

[0037] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing in accordance with some embodiments.

[0038] [Diagram 2] 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

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

[0040] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0041] [Figure 4B] 1 illustrates an exemplary user interface of a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

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

[0043] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device in accordance with some embodiments.

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

[0045] [Figure 5E] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5F] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5G] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments. [Figure 5H] 1 illustrates example components and a user interface of a personal electronic device in accordance with some embodiments.

[0046] [Figure 5I] 1 illustrates an electronic device according to some embodiments.

[0047] [Figure 5J] FIG. 1 is a block diagram illustrating an electronic device in accordance with some embodiments.

[0048] [Figure 6] FIG. 1 illustrates a set of physical structures and an exemplary device according to some embodiments.

[0049] [Figure 7A] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7B] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7C] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7C1]1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7D] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7E] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7F] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7G] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7H] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7I] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7J] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7K] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7L] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7M] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7N] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7O] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7P] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7Q] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7R] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7S] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7T] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7U] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7V] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7W] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7X] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7Y] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7Z] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AA] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AB] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AC] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7A-D] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AE] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AF] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7A-G] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments. [Figure 7AH] 1 illustrates an exemplary user interface for sending a voice message according to some embodiments.

[0050] [Figure 8A] FIG. 2 is a flow diagram illustrating a method for sending an audio message according to some embodiments. [Figure 8B] FIG. 2 is a flow diagram illustrating a method for sending an audio message according to some embodiments.

[0051] [Figure 9A] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9B] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9C] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9D] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9E] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9F] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9G] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9H]1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9I] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9J] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9K] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9L] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9M] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9N] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9O] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9P] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9Q] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9R] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9S] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9T] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9U] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9V] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9W] 1 illustrates an example user interface for displaying notifications according to some embodiments. [Figure 9X] 1 illustrates an example user interface for displaying notifications according to some embodiments.

[0052] [Figure 10] FIG. 1 is a flow diagram illustrating a method for displaying a notification according to some embodiments.

[0053] [Figure 11A] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11B] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11C] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11D] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11E] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11F] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11G] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11H] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11I] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11J] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11K]1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11L] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11M] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11N] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11O] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11P] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11Q] 1 illustrates an example user interface for displaying visual instructions according to some embodiments. [Figure 11R] 1 illustrates an example user interface for displaying visual instructions according to some embodiments.

[0054] [Figure 12] FIG. 1 is a flow diagram illustrating a method for displaying visual indications according to some embodiments.

[0055] [Figure 13A] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13B] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13C] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13D] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13E]1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13F] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13G] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13H] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13I] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13J] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13K] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13L] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13M] 1 illustrates an example user interface for managing external devices according to some embodiments. [Figure 13N] 1 illustrates an example user interface for managing external devices according to some embodiments.

[0056] [Figure 14] FIG. 1 is a flow diagram illustrating a method for managing external devices according to some embodiments.

[0057] [Figure 15A] 1 illustrates an exemplary user interface for playing an audio message according to some embodiments. [Figure 15B] 1 illustrates an exemplary user interface for playing an audio message according to some embodiments. [Figure 15C]1 illustrates an exemplary user interface for playing an audio message according to some embodiments. [Figure 15D] 1 illustrates an exemplary user interface for playing an audio message according to some embodiments. [Figure 15E] 1 illustrates an exemplary user interface for playing an audio message according to some embodiments. [Figure 15F] 1 illustrates an exemplary user interface for playing an audio message according to some embodiments.

[0058] [Figure 16] FIG. 1 is a flow diagram illustrating a method for playing an audio message according to some embodiments.

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

[0060] There is a need for electronic devices that provide efficient methods and interfaces for managing voice messages. Techniques for managing voice messages increase the efficiency of the device (e.g., reducing unnecessary displays), increase the information provided around the external device (e.g., displaying the source of the voice message), and increase privacy (by providing visual feedback to the user of the state of the device that received the audio input). Such techniques can reduce the cognitive burden on users who use voice messages, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0061] 1A-1B, 2, 3, 4A-4B, and 5A-5J below describe exemplary devices for performing techniques for sending and receiving voice messages. Figure 6 illustrates a set of physical structures and exemplary devices for performing techniques for sending and receiving voice messages, according to some embodiments.

[0062] 7A-7AH show example user interfaces for sending a voice message, according to some embodiments. Figures 8A-8B are flow diagrams illustrating a method for sending a voice message, according to some embodiments. The user interfaces of Figures 7A-7AH are used to illustrate processes described below, including the processes of Figures 8A-8B.

[0063] 9A-9X show example user interfaces for displaying a notification, according to some embodiments. FIG 10 is a flow diagram illustrating a method for displaying a notification, according to some embodiments. The user interfaces of FIGS 9A-9X are used to illustrate processes described below, including the process of FIG 10.

[0064] 11A-11R show exemplary user interfaces for displaying visual instructions. FIG 12 is a flow diagram showing a method for displaying visual instructions. The user interfaces of FIGS 11A-11R are used to illustrate processes described below, including the process of FIG 12.

[0065] 13A-13N show exemplary user interfaces for managing the state of a device. FIG 14 is a flow diagram illustrating a method for managing the state of a device. The user interfaces of FIG 13A-13N are used to illustrate processes described below, including the process of FIG 14.

[0066] 15A-15F show example user interfaces for playing a voice message, according to some embodiments. FIG 16 is a flow diagram illustrating a method for playing a voice message, according to some embodiments. The user interfaces of FIG 15A-15F are used to illustrate processes described below, including the process of FIG 16.

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

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

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

[0070] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad).

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

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

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

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

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

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

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

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

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

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

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

[0082] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

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

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

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

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

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

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

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

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

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

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

[0093] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called camera module), depth camera sensor 175 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that an image of the user with depth information is optionally obtained for a video conference and to capture a selfie image with depth map data while the user is viewing other video conference participants on a touch screen display. In some embodiments, depth camera sensor 175 is located on the back of the device, or on the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing) such that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images in conjunction with a touch screen display.

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

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

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

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

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

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

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

[0101] Contact / motion module 130 optionally detects contact with touch screen 112 (in cooperation with display controller 156) and other touch-sensing devices (e.g., a touchpad or a physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact occurs (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are, optionally, applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, any one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updaters 176, object updaters 177, GUI updaters 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updaters 176, object updaters 177, or GUI updaters 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0144] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including sub-event delivery instructions).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0172] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may, for example, cause the computer processors to perform the techniques described below, including process 800 (FIGS. 8A-8B), process 1000 (FIG. 10), process 1200 (FIG. 12), process 1400 (FIG. 14), and process 1600 (FIG. 16). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray technology, as well as resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

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

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

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

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

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

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

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

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

[0181] 5E-5H show the intensity thresholds of the light presses in FIG. 5E (e.g., “IT L ") to the intensity threshold of the deep press in Figure 5H (e.g., "IT D5 illustrates detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity above a deep press intensity threshold (e.g., "IT 2"). The gesture performed by contact 562 is detected on touch-sensitive surface 560 and cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed in default area 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device detects when the intensity of contact 562 exceeds a deep press intensity threshold (e.g., "IT D Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, a deep press intensity threshold (e.g., “IT D "), reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents are displayed for app2, as shown in FIGS. 5F-5H. In some embodiments, the intensity that is compared to one or more intensity thresholds is a characteristic intensity of the contact. Note that the intensity diagrams for contact 562 are not part of the displayed user interface, but are included in FIGS. 5E-5H as an aid to the reader.

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

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

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

[0185] FIG. 5I illustrates an exemplary electronic device 580. Device 580 includes a body 580A. In some embodiments, device 580 can include some or all of the features described with respect to devices 100, 300, and 500 (e.g., FIGS. 1A-5B). In some embodiments, device 580 has one or more speakers 580B (concealed in body 580A), one or more microphones 580C, one or more touch-sensitive surfaces 580D, and one or more displays 580E. Alternatively, or in addition to a display and touch-sensitive surface 580D, the device has a touch-sensitive display (also referred to as a touch screen). Similar to devices 100, 300, and 500, in some embodiments, touch-sensitive surface 580D (or touch screen) optionally includes one or more intensity sensors for detecting the intensity of a contact (e.g., a touch) being applied. Output data representative of the intensity of the touch may be provided by the one or more intensity sensors of touch-sensitive surface 580D (or touch screen). The user interface of device 580 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 580. In some embodiments, one or more displays 580E are one or more light emitting diodes (LEDs). For example, a display can be a single LED, a cluster of LEDs (e.g., red, green, and blue LEDs), multiple separate LEDs, multiple separate LED clusters, or other arrangements of one or more LEDs. For example, display 580E can be an array of nine separate LED clusters arranged in a circular shape (e.g., a ring). In some examples, one or more displays are composed of any one or more of another type of light emitting element.

[0186] FIG. 5J illustrates an exemplary personal electronic device 580. In some embodiments, the device 580 can include some or all of the components described with respect to FIGS. 1A, 1B, 3, and 5A-5B. The device 580 has a bus 592 operably coupling an I / O section 594 to one or more computer processors 596 and a memory 598. The I / O section 594 can be connected to a display 582, which can have a touch-sensitive component 584 and, optionally, an intensity sensor 585 (e.g., a contact intensity sensor). In some embodiments, the touch-sensitive component 584 is a separate component from the display 582. Additionally, the I / O section 594 can be connected to a communication unit 590 for receiving application and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular, and / or other wireless communication technologies. The device 580 can include an input mechanism 588. In some examples, the input mechanism 588 is optionally a button. In some examples, input mechanism 588 is optionally a microphone. Input mechanism 588 is optionally a plurality of microphones (e.g., a microphone array).

[0187] Electronic device 580 includes a speaker 586 that outputs sound. Device 580 may include audio circuitry (e.g., in I / O section 594) that receives sound data, converts the sound data into electrical signals, and transmits the electrical signals to speaker 586. Speaker 586 converts the electrical signals into human audible sound waves. Audio circuitry (e.g., in I / O section 594) also receives electrical signals converted from sound waves by a microphone (e.g., input mechanism 588). Audio circuitry (e.g., in I / O section 594) converts the electrical signals into sound data. The sound data is optionally retrieved by I / O section 594 from memory 598 and / or RF circuitry 590 (e.g., of communication unit 590) and / or transmitted to memory 102 and / or RF circuitry 108.

[0188] The memory 598 of the personal electronic device 580 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 596, may, for example, cause the computer processors to perform the techniques described below, including process 800 (FIGS. 8A-8B), process 1000 (FIG. 10), process 1200 (FIG. 12), process 1400 (FIG. 14), and process 1600 (FIG. 16). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium may include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, as well as resident solid-state memory such as flash, solid-state drives, etc. Personal electronic device 580 is not limited to the components and configuration of FIG. 5J and may include other or additional components in multiple configurations.

[0189] Attention is now directed to embodiments of user interfaces (“UI”) and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0190]

[0023] Figure 6 includes a diagram 600 showing a set of physical structures and example devices according to some embodiments. Figure 6 is used to illustrate the processes described below, including the processes of Figures 8A-8B, 10, and 12.

[0191] Diagram 600 includes a home 602 and a set of devices (e.g., device 646, device 604, etc.). Home 602 includes multiple rooms, such as kitchen 602a, dining room 602b, bedroom 602c, living room 602d, and sunroom 602e. Kitchen 602a is in the upper left portion of home 602, dining room 602b is between kitchen 602a and bedroom 602c, where bedroom 602c is to the right of dining room 602b. Kitchen 602a and dining room 602b do not have a wall between them, but there is a wall between dining room 602b and bedroom 602c. Living room 602d is in the lower left portion of home 602, and sunroom 602e is in the lower right portion of home 602. In some embodiments, home 602 includes rooms other than those illustrated in FIG. 6 and / or excludes rooms illustrated in FIG. 6. Although diagram 600 illustrates a home, it should be appreciated that this is merely an example and that the techniques described herein can function in other types of physical structures, such as office buildings, hotels, apartment buildings, etc.

[0192] As shown in Figure 6, each room of the home 602 has at least one device. However, in some embodiments, the rooms of the home 602 do not have any devices.

[0193] As shown in Figure 6, John's phone 604 is in the kitchen 602a located on the counter between the stove and the sink. In the dining room 602b, the dining room speakers 616 are located on the dining room table. In the bedroom 602c, a personal tablet 634 is located on the bed, the bedroom speakers 636 are located on the nightstand adjacent to the bed, and the bedroom light 632 is located on the opposite side of the bed. In the living room 602d, the living room speakers 646 and 648 are on opposite sides of the television, and the living room lamp 642 is positioned in front of the television screen. In the sunroom 602e, the sunroom speakers 656 and 658 are located on opposite sides of the room.

[0194] As shown in FIG. 6, computing device 674 and Jane's phone 684 are outside of home 602. Computing device 674 is located in the dashboard of an automobile that is a distance 670 from home 602, and Jane's phone 684 is a distance 680 away from home 602 and is currently in Jane's possession. In some embodiments, computing device 674 is connected to an electronic device, such as a mobile phone (e.g., a personal phone similar to John's phone 604 and / or Jane's phone 684), which provides instructions to computing device 674 that cause computing device 674 to display visual content. Because distance 670 and distance 680 exceed a threshold distance away from home (e.g., 1, 5, 10 meters), computing device 674 and Jane's phone 684 are not considered to be in a location corresponding to home 602 (e.g., not within a geofence of home 602 or not connected to a wireless network associated with (e.g., configured within) home 602).

[0195] In this example, the speakers (e.g., dining room speakers 616, bedroom speakers 636, living room speakers 646, living room speakers 648, sunroom speakers 656, and sunroom speakers 658), lights (e.g., bedroom light 632 and living room lamp 642), and personal devices (e.g., John's phone 604, tablet 634, computing device 674, and Jane's phone 684) shown in FIG. 6 are assigned (e.g., programmatically mapped) to home 602 (e.g., to corresponding groups) (e.g., by a user account associated with home 602, such as John's user account or Jane's user account).

[0196] In addition, each individual speaker and light is also assigned to the room in which it is located (e.g., mapped to a corresponding group). For example, dining room speaker 616 is assigned to dining room 602b (e.g., programmatically mapped to a corresponding group). Bedroom speaker 636 and bedroom light 632 are assigned to bedroom 602c. Living room lamp 642, living room speaker 646, and living room speaker 648 are assigned to living room 602d, and sunroom speaker 656 and sunroom speaker 658 are assigned to sunroom 602e. In some embodiments, each group corresponding to each room is also assigned to the home 602. Thus, devices that are mapped to rooms in the home 602 are also simultaneously mapped to the home 602.

[0197] An external device may not be assigned to two different device groups corresponding to different rooms. For example, the dining room speaker 616 may not be assigned to the kitchen 602a (e.g., the group corresponding to the kitchen 602a) and the dining room 602b at the same time. However, two groups of devices assigned to each room may be mapped to the (same) zone. In this example, the entertainment zone 660 is assigned to the living room 602d of FIG. 6 and the sunroom 602e of FIG. 6. In this example, the entertainment zone 660 is not a physical room of the home 602c. However, the entertainment zone is programmatically defined as assigned to the sunroom living room 602d and the sunroom 602e. In some embodiments, two different zones share a group of devices (e.g., contain some overlapping devices and each contain some non-overlapping devices). For example, the group of devices assigned to the sunroom 602e may be mapped to the entertainment zone 660 and the eating zone (e.g., the eating zone is assigned to the group of devices assigned to the dining room 602b and the sunroom 602e).

[0198] In this example, the personal devices (eg, John's phone 604, tablet 634, and Jane's phone 684) are not programmatically mapped to the group corresponding to the room, but only to the group corresponding to the home.

[0199] In some embodiments, the speaker, light, and personal devices (e.g., John's phone 604, tablet 634, Jane's phone 684) shown in FIG. 6 are smart devices that are directly or indirectly connected to each other via one or more networks (e.g., wireless networks (e.g., Bluetooth, NFC, Wi-Fi, 4G, etc.)). In some embodiments, other smart devices, such as smart appliances, smart thermostats, smart plug outlets, etc., are connected to the one or more networks. In some embodiments, the one or more personal devices may also include other types of personal devices, such as a smart watch, a laptop computer, a desktop, etc.

[0200] 7A-7AH show example electronic devices and user interfaces for sending audio messages according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 8A-8B.

[0201] FIG. 7A illustrates an electronic device 700 displaying a user interface 702. In FIG. 7A, the electronic device 700 is a portable multifunction device and has one or more of the components described above with respect to any one or more of devices 100, 200, 300, and 500. With respect to the following figures, in some embodiments, the device 700 is operating less than a predetermined distance away from the home 602. However, in other embodiments, the device 700 is operating more than a predetermined distance away from the home 602. In some embodiments, the device 700 is connected to a network (e.g., a wireless network) associated with the home 602 such that the device 700 is connected to the same wireless network to which at least one device (e.g., speaker, light) located in the home 602 is connected. In some embodiments, two or more wireless networks are associated with the home 602. In some embodiments, the device 700 is connected to at least one of those networks. In some embodiments, the device 700 is not connected to one or more networks associated with the home 602. Thus, device 700 can send audio multicast messages and communicate with devices in home 602 regardless of the distance device 700 is from home 602 or the network to which device 700 is connected.

[0202] While this description often refers to messages as multicast messages (or audio multicast messages), such messages are optionally sent using (1) multicast communications, (2) broadcast communications, (3) unicast communications, (4) or any combination thereof (e.g., (1) a first device (e.g., a controller) sends a unicast communication to a second device (e.g., a hub in the home), and (2) the second device sends either a multicast or broadcast communication (e.g., including content from the unicast communication) to one or more third devices (e.g., one or more accessory devices in the home and / or one or more personal devices)). In some embodiments, a multicast communication is a communication sent to multiple recipients. In some embodiments, a broadcast communication is a communication sent to devices on a channel or network. In some embodiments, a broadcast communication is a communication sent to all devices on a channel or network. In some embodiments, a unicast communication is a communication sent to a single recipient. In such embodiments, if content needs to be sent to multiple devices, multiple unicast communications are sent.

[0203] In some embodiments, a broadcast communication is a communication that is sent to all devices on a channel or network. In such embodiments, if content needs to be sent to multiple devices, multiple unicast communications are sent.

[0204] As shown in Figure 7A, the user interface 702 includes application icons 704, such as a home application icon 704a. Each of the application icons 704 corresponds to an application, such that selecting the application icon causes the device 700 to display the user interface of the respective application. For example, the home application icon 704a corresponds to the home application. In Figure 7A, the device 700 detects a tap gesture 750a (e.g., a selection) at a location corresponding to the home application icon 704a.

[0205] 7B, in response to detecting the tap gesture 750a, the device 700 displays a home application user interface 710. The user interface 710 is a user interface for controlling multiple external devices assigned to the home 602. The user interface 710 includes a home location identifier 712, state information 714, macro controls 716, external device controls 718, navigation controls 722, home multicast instructions 724, and home multicast affordances 726 (e.g., selectable user interface object objects).

[0206] The home location identifier 712 is a name that corresponds to the home 602. In this example, the location identifier is part of the address of the home 602 (e.g., "123 Main Street"). In some embodiments, the location identifier is an alias, such as an alias assigned to the home. In some embodiments, the alias is a system-created alias. In some embodiments, the alias is a user-created alias. In some embodiments, the location identifier is set by a user of the device 700 or an external device. In some embodiments, the location identifier is a graphical user interface object object, such as an image.

[0207] Status information 714 includes information regarding the current state of some of the devices designated for home 602. Here, status information 714 indicates that at least one light is in home 602. In some embodiments, status information 714 includes information regarding the state of multiple devices (e.g., "Bedroom Fan On").

[0208] As shown in FIG. 7B, below the home location identifier 712 and state information 714 are two rows of macro controls 716. The macro controls 716 are affordances (e.g., selectable user interface object objects) for initiating the respective macros. In some embodiments, each macro causes one or more external devices to perform an action. For example, a "Good Night" macro control, when selected, causes one or more lights to turn off, one or more speakers to stop playing media, and / or one or more deadbolt locks to lock.

[0209] Additionally, in FIG. 7B, the user interface 710 includes a row for external device controls 718 below the macro controls 716. In FIG. 7B, the two rows of external device controls 718 extend across three columns, resulting in a total of six displays (e.g., when three device controls are on each corresponding row). In some embodiments, the user can have fewer external devices for controls that require fewer external device controls 718. In other embodiments, the user can have more external devices for controls that require more external device controls 718. In some embodiments, when more external device controls 718 are displayed than there is available screen space, the screen scrolls (e.g., up and down or left and right) to display all the external device controls. The external device controls 718 include a dining room speaker control 718a, a living room lamp control 718b, a living room speaker control 718c, a sunroom speaker control 718d, a bedroom speaker control 718e, and a bedroom light control 718f. Additionally, each of the external device controls 718 includes state information that represents the current state of the respective external device. For example, state information for dining room speaker control 718a indicates that dining room speaker 616 is currently playing media (not represented by state information 714 in this example), and state information for living room lamp control 718b indicates that living room lamp 642 is currently off (represented by state information 714 in this example).

[0210] Each of the external device controls 718, when selected, controls at least one device designated for the home 602. For example, selecting the dining room speaker control 718a causes the dining room speaker 616 to play or pause music. In some embodiments, when the dining room speaker control 718a is selected, the state information of the dining room speaker control 718a changes to indicate that the dining room speaker 616 has paused media playback (e.g., as indicated by the bedroom speaker control 718e) or has stopped playing media. Some of the external device controls 718, when selected, control multiple devices. For example, the sunroom speaker control 718d, when selected, causes the sunroom speakers 656 and 658 to play or pause media playback, and the state information displayed on the sunroom speaker control 718d changes accordingly. Some of the external device controls 718 are not speaker device controls. For example, the external device controls 718 include a living room lamp control 718b that, when selected, causes the living room lamp control 718b to turn the living room lamp 642 on / off and the status information displayed on the living room lamp control 718b changes accordingly.

[0211] In some embodiments, the external device control 718 is selected from a group of other external controls that are also designated to the home 602. For example, the six controls shown in FIG. 7B may be selected from 10, 20, or 50 (or any other number greater than six) external controls that are also designated to the home 602. In some embodiments, the external device control 718 is selected based on a determination that each of these external device controls is a favorite control. In some embodiments, the determination of whether an external device is a favorite control is based on whether the external device control (or external device) was most recently used, most frequently used, newly added, designated as a favorite important external device control (e.g., via detection of one or more inputs), etc., or any combination thereof.

[0212] At the bottom of the user interface 710 are navigation controls 722. The navigation controls 722 include a home navigation control 722a, a room navigation control 722b, and an automated navigation control 722c. Each of the navigation controls 722, when selected, causes the device 700 to display a different user interface for the home application.

[0213] As shown in Figure 7B, user interface 710 includes home multicast instructions 724 adjacent to a home multicast affordance 726. In Figure 7B, home multicast instructions 724 indicate that a user should select (e.g., "tap") home multicast affordance 726 to send an audio message that is multicast to one or more devices specified in home 602. In Figure 7B, device 700 detects a tap gesture 750b at a location corresponding to home multicast affordance 726.

[0214] In response to detecting the tap gesture 750b, the device 700 initiates a process for transmitting an audio multicast message to one or more devices designated for the home 602. In some embodiments, the process includes displaying a user interface illustrated in Figures 7C, 7D, and 7E, as described below. In some embodiments, the process includes displaying a user interface illustrated in Figure 7C1, as described below.

[0215] As shown in FIG. 7C, in response to detecting the tap gesture 750b, the user interface 730 includes a home destination identifier 732, an exit affordance 734, and a multicast record affordance 736. The home destination identifier 732 indicates that the audio multicast message is directed to a group of devices designated for the home 602 (e.g., to receive the audio multicast message). The exit affordance 734 is an affordance for exiting the user interface 730. In some embodiments, when the exit affordance 734 is selected, the device 700 ceases displaying the user interface 730 and redisplays the user interface 710, as illustrated in FIG. 7B. In FIG. 7C, the device 700 detects a tap gesture 750c at a location corresponding to the multicast record affordance 736.

[0216] 7D, in response to detecting tap gesture 750c, device 700 displays user interface 740. User interface 740 includes home destination identifier 732 and exit affordance 734, which were also included in user interface 730. In addition, user interface 740 also includes audio status bar 742 and audio waves 744a.

[0217] 7D, device 700 also begins recording an audio multicast message in response to detecting tap gesture 750c. The audio for the audio multicast message is detected via one or more microphones of device 700. The audio for the audio multicast message is detected from one or more external sources (e.g., user voice, etc.). Here, the recorded audio is represented by audio waves 744a, which fill up audio status bar 742 over a period of time as more audio input is received by device 700.

[0218] As shown in Figure 7D, in response to detecting tap gesture 750c, device 700 displays multicast record stop affordance 746 at the location where multicast record affordance 736 was previously displayed in Figure 7C. In Figure 7D, device 700 detects tap gesture 750d at a location corresponding to multicast record stop affordance 746.

[0219] As shown in FIG. 7E, in response to detecting the tap gesture 750d, the device 700 displays a user interface 750. In FIG. 7E, in response to detecting the tap gesture 750d, the device 700 stops recording or capturing audio from one or more external sources. Thus, the user interface 750 includes an audio status bar 742 that is mostly filled with audio waves 744a, which represent at least a portion of the recorded audio multicast message. As shown in FIG. 7E, the user interface 750 includes an audio multicast message play affordance 752 and an audio multicast message delete affordance 754 (e.g., in addition to including the home destination identifier 732, the exit affordance 734, the audio status bar 742, and the audio waves 744a). In some embodiments, in response to detecting a selection of the audio multicast message play affordance 752, the device 700 begins playing the audio multicast message. In some embodiments, in response to detecting a selection of the audio multicast message delete affordance 754, the device 700 deletes the audio multicast message. In some embodiments, in response to detecting a selection of the delete audio multicast message affordance 754, the device 700 redisplays the user interfaces 710, 730, and / or 740.

[0220] As shown in FIG. 7E, in response to detecting tap gesture 750d, device 700 displays multicast send affordance 756 at the location where multicast record stop affordance 746 was previously displayed in FIG. 7D (where multicast record affordance 736 was displayed in FIG. 7C).

[0221] In an alternative to the flows described in Figures 7C, 7D, and 7E, device 700 may display a user interface as shown in Figure 7C1 in response to detecting tap gesture 750b in Figure 7B. As shown in Figure 7C1, in response to detecting tap gesture 750b, device 700 displays user interface 741 and automatically starts recording an audio multicast message (e.g., without detecting any further gestures, such as tap gesture 750c). As shown in Figure 7C1, user interface 741 includes a home destination identifier 732, an end affordance 734, an audio wave 744a, and a multicast send affordance 747 that device 700 displays using techniques similar to those described above in connection with Figures 7C, 7D, and 7E. For example, in Figure 7C1, audio wave 744a is dynamic and changes over time with respect to one or more characteristics (e.g., level, pitch, gradation) of the currently recorded audio over the length of time that the audio is being recorded. In some embodiments, the audio wave 744a moves to the left as the audio is recorded for the length of time the audio is recorded.

[0222] In some embodiments, audio is recorded using the user interface 710 of FIG. 7B or the user interface 741 of FIG. 7C1 through the flows described in 7C, 7D, and 7E and / or instead of through the flows described in FIG. 7C. For example, in response to detecting a hold gesture on the home multicast affordance 726, the device 700 starts recording an audio multicast message. In such an example, the recording is stopped when the hold gesture ends (e.g., is released), and replacing the home multicast affordance 726 with a send affordance (e.g., similar to the multicast send affordance 756). In some embodiments, the audio is automatically sent as a multicast message when the hold gesture ends. In some embodiments, when the hold gesture ends, the home multicast instruction 724 is replaced with an affordance for playing audio (e.g., similar to the audio status bar 742) and an affordance for deleting audio (e.g., similar to the audio multicast message delete affordance 754). In another example, in response to detecting a tap gesture on the home multicast affordance 726, the home multicast affordance 726 behaves similarly to the multicast record affordance 736 (e.g., is replaced with a stop affordance (similar to the multicast record stop affordance 746)). In such an example, in response to detecting a tap gesture on the stop affordance, (1) the stop affordance is replaced with a send affordance (e.g., similar to the multicast send affordance 756), and (2) the home multicast instructions 724 are replaced with an affordance for playing audio (e.g., similar to the audio status bar 742) and an affordance for deleting audio (e.g., similar to the audio multicast message delete affordance 754). In FIG. 7E, the device 700 detects a tap gesture 750e at a location corresponding to the multicast send affordance 756, or in FIG. 7C1, the device detects a tap gesture 750c1 at a location corresponding to the multicast send affordance 747.

[0223] As shown in FIG. 7F, in response to detecting tap gesture 750e or tap gesture 750c1 (or a tap gesture on the send affordance as described in the previous paragraph), device 700 causes an audio multicast message to be multicast (transmitted) to a set of external devices designated for home 602. Such transmission optionally includes (1) sending a message including the audio multicast message to another device (e.g., a device located within the home) and (2) the other device sending the audio multicast message to the set of external devices (in some embodiments, the other device identifies the set of external devices instead of device 700). Table 706 is provided to indicate the external devices to which the audio multicast message was directed. For example, a check mark in the “Received Audio Multicast Messages” column indicates that the audio multicast message was directed (e.g., sent) to the external device on the respective row of check marks, and a dash in the “Received Audio Multicast Messages” column indicates that the audio multicast message was not directed (e.g., not sent) to the external device on the respective row of dashes.

[0224] In FIG. 7F, table 706 shows that audio multicast messages were directed to (and received by) each speaker (e.g., dining room speaker 616, bedroom speaker 636, living room speaker 646, living room speaker 648, sunroom speaker 656, and sunroom speaker 658). Notably, audio multicast messages were also directed to personal devices (e.g., John's phone 604, tablet 634, and Jane's phone 684). In some embodiments, audio multicast messages are directed to personal devices regardless of whether the personal devices were in a location corresponding to the home (e.g., regardless of whether distances 670 and 680 exceed a threshold distance). For example, audio multicast messages were directed to John's phone 604 and tablet 634, which are located inside home 602 in FIG. 6. In addition, the audio multicast message was also directed to a computing device 674 and Jane's phone 684 outside the home 602 (distant 670 and distance 680 away from the home 602, respectively). In some embodiments, the audio multicast message is directed to a personal device depending on whether the personal device is included in the home network (e.g., if the personal device is included in the home network, then the audio multicast message is directed to the personal device).

[0225] Table 706 of FIG. 7F also indicates that the audio multicast message was not directed to (and therefore did not receive) some external devices, which are designated for home 602. For example, table 706 indicates that the audio multicast message is not directed to bedroom light 632 and living room lamp 642. In some embodiments, the audio multicast message is not directed to some types of external devices, regardless of whether the audio multicast message is designated for the group of devices to which the audio multicast message is being sent. In some embodiments, these types of external devices include devices that do not have one or more audio input devices (e.g., microphones) and / or one or more audio output devices (e.g., speakers). In some embodiments, these types of external devices include devices that are inactive, unpowered, or non-functional at (or prior to) the time the audio message is sent.

[0226] As shown in FIG. 7F, at some point after detecting tap gesture 750e or tap gesture 750c1 (or a tap gesture on the send affordance, as described above), device 700 re-displays user interface 710. In some embodiments, user interface 710 is displayed without device 700 detecting any additional input (e.g., after a predetermined period of time after detecting tap gesture 750e or tap gesture 750c1 (or a tap gesture on the send affordance)) after detecting tap gesture 750e or tap gesture 750c1 (as described above (e.g., after a predetermined period of time after detecting a tap gesture)). In some embodiments, user interface 710 is displayed upon detection of one or more additional inputs, such as a tap gesture input detected on the finish affordance 734 of FIG. 7E.

[0227] In some embodiments, in response to detecting a tap gesture 750f1 at a location corresponding to living room lamp control 718b, device 700 transmits an instruction to turn living room lamp 642 on (or off if the current state was on). In some embodiments, in response to detecting a tap gesture 750f2 at a location corresponding to living room speaker control 718c, device 700 transmits an instruction to living room speakers 646 and 648 (or at least one of them) to start playing media (e.g., or pause playing media if the current state is playing). In FIG. 7F, device 700 detects a tap gesture 750f3 at a location corresponding to room navigation affordance 722b.

[0228] As shown in FIG. 7G, in response to detecting the tap gesture 750f3, the device 700 displays a home application user interface 760, indicating that the home navigation control 722b (e.g., bold in FIG. 7G) has been selected instead of the home navigation control 722a (e.g., not bold in FIG. 7G). The user interface 760 is a user interface for controlling multiple external devices designated for the living room 602d, as indicated by the living room location identifier 762. The user interface 710 includes macro controls 766, external device controls 768, navigation controls 722, living room multicast instructions 774, and living room multicast affordances 776. These elements of the user interface 760 are specific controls for living room devices, as opposed to elements of the user interface 710 that are controls for the devices throughout the home. In some embodiments, any one or more of these elements of the user interface 760 have a purpose or functionality similar to any one or more of the elements of the user interface 710 described above (e.g., of FIG. 7B). In some embodiments, the user interface 760 includes state information including a current state of the device designated for the living room 602d. In some embodiments, the device 700 displays the user interface 760 of the home application after receiving a swipe gesture on the user interface 710.

[0229] In particular, the user interfaces of the home application (e.g., user interfaces 710 and 760) are laid out in a hierarchy. For example, user interface 710 is a top node in the hierarchy and includes controls for a group of external devices designated for home 602. While displaying user interface 710, an input (e.g., a single input (e.g., tap gesture 750f)) can be detected that causes device 700 to display user interface 760, which is a bottom node in the hierarchy and includes controls for a group of external devices designated for a respective room (e.g., living room 602d) (and not other rooms) of home 602.

[0230] As shown in FIG. 7G, the external device controls 768 include a living room speaker control 768a, a living room lamp control 768b, a living room switch (e.g., light switch) control 768c, and a living room TV control 768d. In FIG. 7G, the living room speaker control 768a and the living room lamp control 768b, when selected, cause each of the corresponding external devices to perform the same action as the living room lamp device control 718b and the living room speaker device control 718c cause their respective external devices to perform (e.g., in FIG. 7B). Thus, in this example, the living room speaker control 768a and the living room lamp control 768b are effectively the same control as the living room speaker device control 718c and the living room lamp device control 718b, but they are visually different in appearance from each of their corresponding parts. In some embodiments, the living room speaker control 768a and the living room lamp control 768b do not appear visually different in appearance from the living room speaker device control 718c and the living room lamp device control 718b.

[0231] Compared to the external device controls 718 displayed in FIG. 7B, the external device controls 768 include at least one external device control displayed as part of the external device controls 718 in FIG. 7B (e.g., living room speaker control 768a and living room lamp control 768b), and at least one external device control not displayed (e.g., living room switch control 768c and living room TV control 768d). In other words, at least one external device (e.g., living room speakers 646 and 648) can be controlled from user interfaces 710 and 760, and at least one external device (e.g., bedroom speaker 636 and living room TV in user interface 760) can be controlled only from one of user interfaces 710 and 760. In some embodiments, in response to detecting a tap gesture 750g1 at a location corresponding to the living room lamp control 768b, the device 700 transmits an instruction to turn on (or off if the current state was on) the living room lamp 642. In some embodiments, in response to detecting a tap gesture 750g2 at a location corresponding to the living room speaker control 768a, the device 700 sends a command to the living room speakers 646 and 648 (or at least one of them) to start playing media (e.g., or to pause playing media if the current state is playing).

[0232] In addition, the external device control 718 is designated as a set of favorite controls for the home 602 in FIG. 7B, while the external device control 768 is a set of all controls designated for the living room 602d in FIG. 7G. In FIG. 7B, the user interface 760 does not include any external devices that are not designated for the living room 602d. For example, the dining room speaker control 718a, the sunroom speaker device control 718d, the bedroom speaker device control 718e, and the bedroom light device control 718f are not displayed on the user interface 760. In some embodiments, in response to detecting the tap gesture 750f3, a user interface for controlling multiple external devices for another room (e.g., bedroom, sunroom, kitchen, etc.) is displayed. In some embodiments, the user for controlling multiple external devices for another room is displayed in response to one or more inputs (e.g., swipe inputs) detected in FIG. 7G.

[0233] As shown in FIG. 7G, the user interface 760 includes a living room multicast instruction 774 adjacent to a living room multicast affordance 776. In FIG. 7G, the living room multicast instruction 774 indicates that the user should select (e.g., "tap") the living room multicast affordance 776 to send an audio multicast message to be multicast to one or more devices designated for the living room 602d. Here, the living room multicast affordance 776 does not appear visually different in appearance from the home multicast affordance 726 (e.g., of FIG. 7B) and is displayed in the same location on the device 700 where the home multicast affordance 726 was displayed in FIG. 7B. In some embodiments, the living room multicast affordance 776 appears visually different in appearance from the home multicast affordance 726. In FIG. 7G, the device 700 detects a tap gesture 750g3 at a location corresponding to the living room multicast affordance 776.

[0234] In response to detecting the tap gesture 750g3, the device 700 initiates a process for sending an audio multicast message to one or more devices designated for the living room 602d. In some embodiments, the process includes displaying a user interface 780a, as illustrated in FIG. 7H. In some embodiments, the process includes the device 700 displaying a user interface similar to the user interface 741 of FIG. 7C1, which is displayed in response to detecting the tap gesture 750g3. In some embodiments, the process includes the device 700 displaying a user interface similar to the user interface 741 of FIG. 7C1 to record an audio multicast message to send to the group of devices designated for the living room 602d. In some embodiments, the process includes the device 700 displaying a user interface, as described below in FIGS. 7H-7J, in which audio is recorded and sent to the group of devices designated for the living room 602d.

[0235] As shown in FIG. 7H, in response to detecting the tap gesture 750g3, the user interface 780a is similar to the user interface 730 of FIG. 7C such that the user interface 780a also includes an exit affordance 734 and a record multicast affordance 736. However, instead of the home destination identifier 732, the user interface 780a includes a living room destination identifier 782. The living room destination identifier 782 indicates that the group of devices specified in the living room 602d will receive the multicast message sent via the user interface 780a. In some embodiments, the user interface 780a does not list the individual names / identifiers of the devices that are part of the group. In some embodiments, one or more of the techniques described above with respect to the user interface 730 can be applied to the user interface 780a.

[0236] 7K, in some embodiments, user interface 780b is displayed pursuant to a determination that one or more (or all) external devices (e.g., speakers) designated for living room 602d are unavailable (e.g., inactive or off) in response to detecting tap gesture 750g3. As shown in FIG. 7K, user interface 780b includes unavailable indication 788 to indicate that any one or more of the external devices designated for living room 602d are unavailable (or all but not all are unavailable) and multicast record affordance 736 is displayed as grayed out or greyed out. In FIG. 7K, in response to detecting tap gesture 750k, device 700 continues to display user interface 780b as multicast record affordance 736 is disabled (e.g., until one or more external devices designated for living room 602d are available). In some embodiments, in response to device 700 detecting tap gesture 750c in FIG. 7C, a user interface similar to user interface 780b is displayed.

[0237] Returning to FIG. 7H, device 700 receives tap gesture 750h at a location corresponding to multicast record affordance 736.

[0238] As shown in FIG. 7I, in response to receiving the tap gesture 750h, the device 700 starts recording audio from one or more external sources (e.g., using the microphone of the device 700) and displays a user interface 784 similar to the user interface 740 of FIG. 7D. Like the user interface 740, the user interface 784 includes an exit affordance 734, an audio status bar 742, and a multicast recording stop affordance 746. However, the user interface 784 includes audio waves 744b representing different audio being recorded from the audio recorded in FIG. 7D represented by audio waves 744a. The user interface 784 also includes a living room destination identifier 782 instead of the home destination identifier 732. In some embodiments, one or more of the techniques described above with respect to the user interface 740 can be applied to the user interface 784. In FIG. 7I, the device 700 detects a tap gesture 750i at a location corresponding to the multicast recording stop affordance 746.

[0239] As shown in FIG. 7J, in response to detecting tap gesture 750i, device 700 displays user interface 786 and stops recording or capturing audio from one or more external sources. User interface 786 is similar to user interface 750, except for audio wave 744b displayed (instead of audio wave 744a) and living room destination identifier 782 displayed (instead of home destination identifier 732). In some embodiments, one or more of the techniques described above with respect to user interface 750 can be applied to user interface 786. In FIG. 7J, device 700 detects tap gesture 750j (or a tap gesture on a user interface similar to user interface 741 of FIG. 7C1 (e.g., similar to tap gesture 750c1), as described above) at a location corresponding to multicast transmission affordance 756.

[0240] In some embodiments, device 700 displays user interface 790 in response to detecting tap gesture 750j, as shown in FIG. 7L (or a tap gesture on a user interface similar to user interface 741 of FIG. 7C1 (e.g., similar to tap gesture 750c1, as described above). Device 700 displays user interface 790 upon determining that the audio multicast message cannot be transmitted to one or more (or all) of the external devices specified for living room 602d. User interface 790 does not transmit suggestion 791 to indicate that the audio multicast message was not transmitted to the targeted external device. In some embodiments, a user interface similar to user interface 790 is displayed in response to device 700 detecting tap gesture 750e of FIG. 7E or tap gesture 750c1 of FIG. 7C1.

[0241] In some embodiments, any one or more of user interfaces 730, 740, 750, 780a, 780b, 784, 786, and 790 include an affordance for swapping the intended target of the recorded audio multicast message (e.g., changing the destination identifier). For example, after initiation of a process for transmitting an audio multicast message to a first group of devices (e.g., devices designated for home 602) (such as while showing FIG. 7J and before receiving an input 750j or a tap gesture (e.g., similar to tap gesture 750c1) on a user interface similar to user interface 741 of FIG. 7C1 as described above), device 700 can detect a selection of an affordance for swapping the intended target (e.g., or affordances for swapping the intended target) of the recorded audio multicast message from the first group of devices to a second group of devices (e.g., devices designated for dining room 602b).

[0242] In some embodiments, audio is recorded and transmitted from a user interface similar to user interface 741 of FIG. 7C1, which is displayed in response to detection of tap gesture 750g. In some embodiments, audio is recorded from user interface 760 of FIG. 7G instead of the flows described in FIGS. 7H-7J. For example, in response to detection of a hold gesture on living room multicast affordance 776, device 700 starts recording an audio multicast message. In such an example, recording is stopped when the hold gesture ends (e.g., is released), and replacement of living room multicast affordance 776 with a send affordance (e.g., similar to multicast send affordance 756) occurs. In such an example, living room multicast instruction 774 is replaced with an affordance for playing audio (e.g., similar to audio status bar 742) and an affordance for deleting audio (e.g., similar to audio multicast message delete affordance 754). In another example, in response to detecting a tap gesture on living room multicast affordance 776, living room multicast affordance 776 operates similarly to multicast record affordance 736 (e.g., is replaced with a stop affordance (e.g., similar to multicast record stop affordance 746)). In such an example, in response to detecting a tap gesture on the stop affordance, the stop affordance is replaced with a send affordance (e.g., similar to multicast send affordance 756), and living room multicast instructions 774 are replaced with an affordance for playing audio (e.g., similar to audio status bar 742) and an affordance for deleting audio (e.g., similar to audio multicast message delete affordance 754).

[0243] As shown in table 706 of FIG. 7M, in response to detecting tap gesture 750j (or a tap gesture on a send affordance as described in the previous paragraph or a tap gesture on a user interface similar to user interface 741 of FIG. 7C1 as described above (e.g., similar to tap gesture 750c1)), device 700 causes an audio multicast message to be multicast (transmitted or directed) to a set of external devices designated for living room 602d. Such transmission optionally includes (1) sending a message including the audio multicast message to another device (e.g., a device located in the living room) and (2) the other device sending the audio multicast message to the set of external devices (in some embodiments, the other device identifies the set of external devices instead of device 700). As shown in table 706, the audio multicast message is directed only to living room speakers 646 and 648, which receive the audio multicast message. In particular, the audio multicast message is not directed to the personal devices (e.g., John's phone 604, tablet 634, and Jane's phone 684) because they are not designated to a group corresponding to a room (e.g., personal devices are not designated to a group corresponding to living room 602d). Additionally, the audio multicast message is not directed to living room lamp 642 because living room lamp 642 is not a type of external device that can receive audio multicast messages for similar reasons described above (e.g., in FIG. 7F).

[0244] In FIG. 7M, device 700 detects audio input 792a including the phrase "Hey Assistant, Hello Multicast." Sometime after detecting the portion of audio input 792a, device 700 displays a suggestion 794a in user interface 794 (e.g., on the left side of user interface 794), where suggestion 794a is a response to the portion of audio input 792a. Suggestion 794a is text that reads "What can I do for you?" In some embodiments, device 700 outputs media that includes an audible version of suggestion 794a.

[0245] In FIG. 7N, after displaying the user interface 794 of FIG. 7M, the device 700 displays a suggestion 794b on the right side of the user interface 794. In addition, the device 700 displays a suggestion 794c on the left side of the user interface 794 and below the suggestion 794b. The suggestion 794b is text that reads "Hey Assistant, Hello Multicast," which are text that correspond to the audible phrase included in the speech input 792a. In addition, the suggestion 794c is text that reads "OK, I sent your multicast to 123 Main Street." In particular, 123 Main Street is an identifier for the home 602 (e.g., the home location identifier 712 of FIG. 7B). In some embodiments, the device 700 outputs media that includes an audible version of the response 794c.

[0246] As shown in table 706 of Figure 7N, after detecting audio input 792a, device 700 directs (e.g., sends) an audio multicast message to one or more devices specified in home 602, as described above in connection with Figure 7F. Table 706 indicates that an audio multicast message (e.g., "hello") is directed to each speaker in the home (e.g., dining room speaker 616, bedroom speaker 636, living room speaker 646, living room speaker 648, sunroom speaker 656, and sunroom speaker 658), regardless of whether the device is in a location corresponding to the home (as described above) and / or whether the device is connected to a network associated with the home, and that an audio multicast message (e.g., "hello") is directed to personal devices in the home (e.g., John's phone 604, tablet 634, Jane's phone 684).

[0247] As shown in Figure 7O, some time after displaying user interface 794 in Figure 7N, device 700 displays user interface 710. While displaying user interface 710, device 700 detects gesture 750o (e.g., a long press gesture) at a location that corresponds to bedroom speaker control 718e in Figure 7O.

[0248] As shown in FIG. 7P, in response to detecting the gesture 750o, the device 700 displays a user interface 796 including a number of settings affordances for controlling the bedroom speaker 636 (e.g., room settings (e.g., if the bedroom is selected in FIG. 7P to indicate that the bedroom speaker 636 is designated for the bedroom 602c), favorite settings (e.g., a location included in the favorites is selected in FIG. 7P, which may cause the bedroom speaker control 718e to be displayed on the user interface 710)). As shown in FIG. 7P, one of the settings affordances is a multicast settings affordance 796a, which includes an indication that the bedroom speaker 636 is configured to receive multicast messages. In FIG. 7P, the device 700 detects a tap gesture 750p at a location corresponding to the multicast settings affordance 796a.

[0249] As shown in Figure 7Q, in response to detecting a tap gesture 750p, the device 700 displays a user interface 798 that includes a multicast settings toggle 798a. In Figure 7Q, the multicast settings toggle 798a indicates that the bedroom speaker 636 is configured to receive multicast messages (e.g., a circle displayed to the right of the settings toggle). In Figure 7Q, the device 700 detects a tap gesture 750q at a location that corresponds to the multicast settings affordance 798a.

[0250] As shown in Figure 7R, in response to detecting a tap gesture 750q, device 700 changes the state of multicast toggle 798a (e.g., moves the circle to the left of the settings toggle) to indicate that bedroom speaker 636 is not configured to receive multicast messages. In some embodiments, the multicast settings affordance 796a in Figure 7P is selectable to change the setting from on to off without navigating to a different user interface (e.g., user interface 798).

[0251] In FIG. 7S, device 700 detects audio input 792b including the phrase "Hey Assistant, Multicast to Sunroom, Hello." Sometime after detecting the portion of audio input 792b, device 700 displays a suggestion 794d in user interface 794 (e.g., on the left side of user interface 794), where suggestion 794d is a response to the portion of audio input 792b. Suggestion 794d is text that reads "What can I do for you?" In some embodiments, device 700 outputs media that includes an audible version of suggestion 794d.

[0252] In Figure 7T, after displaying user interface 794 in Figure 7S, device 700 displays suggestion 794e on the right side of user interface 794 and suggestion 794f on the left side of user interface 794 (and below suggestion 794e). Suggestion 794e is text that reads "Hey Assistant, Multicast to Sunroom, Hello," which are text that correspond to the audible phrase contained in voice input 792b. Additionally, suggestion 794f is text that reads "OK, I sent your multicast to Sunroom." In particular, "Sunroom" is an identifier for the group of devices designated for sunroom 602e in Figure 6.

[0253] As shown in table 706 of FIG. 7T, after detecting audio input 792b, device 700 directs (e.g., sends) an audio multicast message to one or more devices designated as sunroom 602e. Table 706 indicates that the audio multicast message (e.g., "hello") is directed to sunroom speaker 656 and sunroom speaker 658, and that the audio multicast message (e.g., "hello") is not directed to other devices. Notably, audio input 792b included an identifier (e.g., "sunroom"), whereas audio 792a did not include an identifier. Thus, in some embodiments, when audio input is detected without an identifier, device 700 sends an audio multicast message to a group of devices designated as a default group. In some embodiments, the default group is a group corresponding to a home (e.g., has home 602, etc.), as described above in connection with FIG. 7N.

[0254] In FIG. 7U, device 700 detects speech input 792c including the phrase "Hey Assistant, multicast to entertainment zone, hello." Sometime after detecting the portion of speech input 792c, device 700 displays a suggestion 794g in user interface 794 (e.g., on the left side of user interface 794), where suggestion 794g is a response to the portion of speech input 792c. Suggestion 794g is text that reads "What can I do for you?" In some embodiments, device 700 outputs media that includes an audible version of suggestion 794g.

[0255] In Figure 7V, some time after displaying user interface 794 of Figure 7U, device 700 displays suggestion 794i to the left of user interface 794 (and below suggestion 794h). Suggestion 794i is text that reads "OK, your multicast has been sent to the entertainment zone." A zone is an identifier for a group of devices. Here, entertainment zone 660 is designated for the group of devices that corresponds to sunroom 602e of Figure 6 and the group of devices that corresponds to living room 602d of Figure 6.

[0256] After detecting audio input 792c, device 700 directs (e.g., sends) an audio multicast message to one or more devices designated for the entertainment zone, as shown in table 706 of Figure 7V. Table 706 shows that the audio multicast message (e.g., "hello") is directed to living room speaker 646, living room speaker 648, sunroom speaker 656, and sunroom speaker 658, and that the audio multicast message (e.g., "hello") is not directed to any other devices.

[0257] As shown in Figure 7V, device 700 also displays a multicast notification 708a indicating that a new audio multicast message has been received from the group of devices designated for sunroom 602e. The new audio multicast message is a reply to the audio multicast message sent in Figure 7T.

[0258] In FIG. 7W, the device 700 detects audio input 792d including the phrase "Hey Assistant, Multicast, I'm going to be leaving soon."

[0259] In FIG. 7X, some time after detecting audio input 792d, device 700 displays suggestion 794j on the left side of user interface 794 and below suggestion 794i. Suggestion 794j is text that reads, "Hey Assistant, Multicast, I'm about to leave." This text corresponds to the audible phrase included in audio input 792d, where audio input 792d does not include an identifier. Additionally, in FIG. 7X, device 700 also displays suggestion 794k on the right side of user interface 794 and below suggestion 794j. Suggestion 794k is text that reads, "OK, I've sent your multicast to the sunroom."

[0260] As shown in table 706 of FIG. 7X, after detecting audio input 792d, device 700 begins a process to send an audio multicast message to a group of devices designated for the sunroom (e.g., "I'm leaving soon"). Specifically, device 700 directs (e.g., sends) an audio multicast message to one or more devices designated for the sunroom 602e without audio input 792d including an identifier for the sunroom. Thus, device 700 intelligently directs the next detected audio multicast message to the sunroom instead of the default group (the group corresponding to home 602) because audio input 792d was detected within a predetermined period of time after receiving multicast notification 708a. In some embodiments, device 700 intelligently sends the next detected audio multicast message to the sunroom instead of the default group because audio input 702d was received within a predetermined time from when the previous multicast message was sent to the sunroom. In some embodiments, two different zones can share at least one group of devices (e.g., the same group of devices designated for a particular room).

[0261] 7X, device 700 also displays multicast notification 708b indicating that an audio multicast message was received from a group of devices designated for sunroom 602e, where device 700 receives this message at 10:19.

[0262] In Figure 7Y, the device 700 detects a speech input 792e containing the phrase "Hey Assistant, Multicast, let's go to dinner" and displays a user interface 794 with suggestions 794l, which read "What can I do for you?" In Figure 7Y, the time is now 10:30 (e.g., 11 minutes have passed since the user interface of Figure 7X was displayed).

[0263] In Figure 7Z, after displaying user interface 794 in Figure 7Y, device 700 displays suggestion 794m on the right side of user interface 794 and suggestion 794n on the left side of user interface 794 (and below suggestion 794m). Suggestion 794m is text that reads "Hey Assistant, multicast, let's go to dinner," which is text that corresponds to the voice phrase included in voice input 792e. Additionally, suggestion 794n is text that reads "OK, I've sent your multicast to 123 Main Street."

[0264] As shown in table 706 of FIG. 7Z, after detecting audio input 792e, device 700 directs (e.g., sends) an audio multicast message (e.g., "Let's go to dinner") to one or more devices designated for home 602, but no audio input 792e includes an identifier for home 602. Now, because more than a predetermined period of time has passed since multicast notification 708b was received, device 700 intelligently sends the next detected audio multicast message to the default group (the group corresponding to home 602) instead of sunroom 602e. In some embodiments, device 700 intelligently sends the detected audio multicast message to the default group because audio input 702e was not received within a predetermined period of time since the previous multicast message was sent to sunroom 602e.

[0265] Further, as shown in table 706 of FIG. 7Z, (in contrast to FIG. 7N) the multicast message of FIG. 7Z was not directed to bedroom speaker 636 because the multicast setting for bedroom speaker 636 was turned off in response to detecting tap gesture 750q of FIG. 7Q.

[0266] Sometime after displaying user interface 794 in Figure 7Z, device 700 displays user interface 710 as shown in Figure 7AA, in which device 700 detects tap gesture 750aa at a location corresponding to home setting affordance 928 above the home location identifier 712 of Figure 7AA.

[0267] As shown in Figure 7AB, in response to detecting tap gesture 750aa, device 700 displays user interface 797. User interface 797 includes a group of people 797a (e.g., a group corresponding to home 602a) who have one or more personal devices designated to a home application. User interface 797 also includes a multicast permission affordance 797b. In Figure 7AB, device 700 detects tap gesture 750ab at a location corresponding to multicast permission affordance 797b.

[0268] As shown in FIG. 7AC, in response to detecting the tap gesture 750ab, the device 700 displays a user interface 799 including a number of options for when to allow audio multicast messages to be sent to the personal device. In FIG. 7AC, the options include a never option 779a, an at home option 779b, and an any time option 799c. In FIG. 7AC, the any time option 799c is selected. Thus, in some embodiments, the device 700 is configured to receive multicast messages at any time, regardless of the location of the device 700. In some embodiments, in response to detecting the tap gesture 750c1 at a location corresponding to the never option 779a, the device 700 is configured to never receive multicast messages, regardless of the location of the device 700. In some embodiments, in response to detecting tap gesture 750c2 at a location corresponding to at home option 799b, device 700 is configured to only receive multicast messages while device 700 is at a location corresponding to or within home 602 (e.g., within a threshold distance of home or whether the device is connected to one or more networks associated with home 602). In some embodiments, when device 700 is away from home, distances 670 and 680, devices 700 such as computing device 674 and Jane's phone 684 do not receive audio multicast messages when selected at home option 799b if their distance is greater than the threshold distance. In some embodiments, one or more options are selectable and displayed, such as an option to only receive messages while the device is away from home.In some embodiments, when device 700 is connected to one or more networks associated with home 602 (e.g., connected to a home Wi-Fi network), device 700 receives the audio multicast message when at home option 799b is selected, and when device 700 is not connected to one or more networks associated with home 602 (e.g., not connected to a home Wi-Fi network), device 700 does not receive the audio multicast message even when at home option 799b is selected (e.g., regardless of the device's location).

[0269] 7AD-7AE show example user interfaces for displaying the user interfaces described above on a device having a larger screen than device 700, such as tablet 634. User interface 711 of FIG. 7AD corresponds to user interface 710 described above. In addition, user interface 731 of FIG. 7AE corresponds to user interface 730 described above. However, any of the user interfaces described above can be displayed and transitioned on tablet 634 using one or more techniques similar to those described above for FIGS. 7A-7AC.

[0270] 7AF-7AH show example user interfaces for displaying the above-described user interfaces on a device having a smaller screen than device 700, such as smartwatch 701. User interface 713 of FIG. 7AF corresponds to user interface 710 described above. Moreover, user interface 741 of FIG. 7AG corresponds to user interface 740 described above. Furthermore, user interface 751 of FIG. 7AH corresponds to user interface 750 described above. However, any of the above-described user interfaces can be displayed and transitioned to on smartwatch 701 using one or more techniques similar to those described above for FIGS. 7A-7AC.

[0271] 8A-8B are flow diagrams illustrating a method for sending an audio message, according to some embodiments. Method 800 is performed on a computer system (e.g., 100, 300, 500, 634, 674, 700, 701, 850) in communication with a display generation component (e.g., a touch-sensitive display). Some operations of method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0272] As described below, method 800 provides an intuitive way to send audio messages, according to some embodiments. The method reduces the cognitive burden on a user of sending audio messages, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, enabling a user to send audio messages faster and more efficiently conserves power and increases the time between battery charges.

[0273] The computer system (802) displays, via a display generation component, a first user interface (e.g., 730) (e.g., a user interface for controlling a set of external devices). The first user interface includes (e.g., includes a display) a first selectable user interface object object (e.g., 726), and selection of the first selectable user interface object object initiates a process (e.g., user interfaces 730, 740, and 750) for recording (e.g., at the computer system via a microphone) and transmitting a first audio message to a set of external devices (e.g., 706 of FIG. 7F) (e.g., each external device in the set of external devices), the set of external devices including a first set of one or more external devices (e.g., 616) and a second set of one or more external devices (e.g., 646, 648). In some embodiments, while displaying the first selectable user interface object object, the computer system receives an input corresponding to a selection of the first selectable user interface object object, and in response to receiving the input corresponding to a selection of the first selectable user interface object object, the computer system displays a user interface for recording and sending a voice message to a first set of one or more devices and a second set of one or more devices (e.g., a set of external devices). In some embodiments, the first set of one or more devices is different from the second set of one or more devices. In some embodiments, the user interface for controlling the set of external devices includes displaying a plurality of representations and / or accessory control user interface object objects corresponding to the first set of one or more devices and the second set of one or more devices. In some embodiments, the plurality of accessory control user interface object objects correspond to the first set of one or more devices, and the second set of one or more devices is a set of one or more selectable user interface object objects.In some embodiments, each of the plurality of accessory control user interface object objects, when selected, causes a respective accessory device of the set of external devices to perform one or more functions and / or change a state of the respective accessory device. In some embodiments, the set of external devices includes an external electronic device (e.g., a cellular phone, a tablet computer) of a type that is not in the first set of one or more devices (e.g., a smart speaker) or the second set of one or more devices (e.g., a smart speaker). In some embodiments, the set of external devices is associated with a top-level location (or destination) (e.g., a first type of location) (e.g., a home location, a business, an office (a location at a top-level location (e.g., one or more regions (or zones) within a location (e.g., sub-locations) that define one or more locations and / or an area and / or perimeter defined by a location at a top-level location, a location at a top level of a hierarchy of locations, a location and / or one or more regions (or zones) that are linked (e.g., programmatically) to one or more locations (e.g., sub-locations))). In some embodiments, the set of external devices includes a first group of devices (e.g., a sub-group of devices) and a second group of devices (e.g., a sub-group of devices). In some implementations, In an embodiment, a sub-group of devices is associated with a sub-location of a top-level location (e.g., a room located within a boundary, area, or periphery of the top-level location and / or defined, identified, and / or linked (e.g., programmatically linked) to the top-level location (e.g., by a user)) and / or a zone (e.g., a location defined by two or more sub-locations) within the top-level location (e.g., within a boundary, area, or periphery of the top-level location and / or defined, identified, and / or linked (e.g., by a user)).In some embodiments, a target group is associated with a subgroup of devices and is not a top-level group of devices.

[0274] The first user interface includes a first accessory control user interface object object (e.g., one of 718) (e.g., a selectable user interface object object) corresponding to a first external accessory device, and selection (e.g., 750f1, 750f2) of the first accessory control user interface object object initiates a process of transmitting (e.g., selection causes transmission of) an instruction to change a state of the first external accessory device (e.g., lock or unlock a door, turn a light on or off). In some embodiments, in response to receiving the input, the computer system initiates a process of transmitting (e.g., selection causes transmission of) an instruction to change a state of the first external accessory device, changing a visual appearance of the first accessory control user interface object object from a first visual appearance to a second visual appearance different from the first visual appearance (e.g., pressed to a pressed state (or vice versa), a first color to a second color, one or more differential characters (e.g., "on" to "off" (or vice versa)).

[0275] The computer system receives (804) an input (e.g., 750f3) corresponding to a request to display a second user interface (e.g., 760) while displaying a first user interface (e.g., the first user interface) (e.g., a single user input (e.g., a tap input on a selectable user interface object or icon that navigates to a user interface for controlling a second set of one or more external devices) or multiple user inputs received while the first selectable user interface object object is displayed) (e.g., a user interface for controlling the second set of one or more external devices (e.g., without controlling the first set of one or more external devices)). In some embodiments, the computer system receives the request to display the second user interface when the computer system receives a selection of a selectable user interface object object for displaying the second user interface.

[0276] In response to receiving the request to display the second user interface, the computer system displays (806) a second user interface (e.g., 760). The second user interface includes (e.g., displays) a second selectable user interface object object (812) (e.g., 776), where selection of the second selectable user interface object object initiates a process (e.g., user interfaces 780a, 784, and 786a) for recording and transmitting the second voice message to a second set of one or more external devices (e.g., 646, 648) without transmitting the second voice message to a first set of one or more external devices (e.g., 706 of FIG. 7M). The second user interface includes a second accessory control user interface object object (814) (e.g., one of 768) (e.g., a selectable user interface object object) corresponding to a second external accessory device (e.g., 642, 646, 648) (e.g., not corresponding to the first set of one or more devices), and selection of the second accessory control user interface object object (e.g., 750g1, 750g2) initiates a process of transmitting an instruction (e.g., selection causes transmission of an instruction) to change a state of the second external accessory device. In some embodiments, in response to receiving the input, the computer system initiates a process of transmitting an instruction (e.g., selection causes transmission of an instruction) to change a state of the second external accessory device, changing a visual appearance of the second accessory control user interface object object from a first visual appearance to a second visual appearance different from the first visual appearance (e.g., pressed to a pressed state (or vice versa), a first color to a second color, one or more difference characters (e.g., "on" to "off" (or vice versa)). In some embodiments, in response to receiving the request to display the second user interface, the computer system ceases displaying the first user interface and the first user interface object.In some embodiments, the second selectable user interface object object replaces the first selectable user interface object object. In some embodiments, the second selectable user interface object object is displayed in the same location where the first selectable user interface object object was previously displayed. In some embodiments, the second user interface replaces the display of the first user interface. In some embodiments, the computer system is unable to control (e.g., unable to cause the external device to change state) the first set of one or more external devices (e.g., the accessory control user interface object object corresponding to one of the first set of one or more devices that is not displayed) from the second user interface. In some embodiments, the first user interface includes displaying one or more representations and / or a set of accessory control user interface object objects corresponding to the first set of one or more external devices (without displaying a set of one or more representations corresponding to the second set of one or more external devices). In some embodiments, each of the accessory control user interface object objects, when selected, causes the respective device to perform one or more functions or change a state of the respective device. In some embodiments, while displaying the second selectable user interface object object, the computer system receives input corresponding to a selection of the second selectable user interface object object, and in response to receiving the input corresponding to a selection of the second selectable user interface object object, the computer system displays a user interface for recording and sending an audio message to a second set of one or more external devices without sending the audio message to the first set of one or more external devices.In some embodiments, while displaying the second selectable user interface object object, the computer system receives a user input (e.g., a swipe input) corresponding to a request to display a user interface for controlling a first set of one or more external devices (e.g., without controlling a second set of one or more external devices) including displaying the selectable user interface object object, which, when selected, initiates a process for recording and transmitting an audio message to the first set of one or more external devices without transmitting the audio message to the second set of one or more external devices. In some embodiments, the audio message includes audio recorded at the computer system. In some embodiments, the process of recording and transmitting the audio message to the external device includes recording the audio message using the computer system (e.g., using a microphone in communication with the computer system). In some embodiments, the audio message includes audio of a voice of a user of the computer system. Providing a hierarchical user interface for controlling a set of controls, each user interface corresponding to a node in the respective hierarchy, provides a user with visual feedback regarding the set of devices in the hierarchy of controls that can be controlled via the respective user interface, along with visual feedback regarding how the user can intuitively navigate to another user interface for controlling another respective set of devices. By providing improved visual feedback to the user, it improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by enabling the user to use the device more quickly and efficiently.

[0277] In some embodiments, the first external accessory device (e.g., 718b) is different from the second external accessory device (e.g., 768c). In some embodiments, the first external accessory device is grouped under the "Home" group but is not part of the "Dining Room" category (e.g., a light located in a bedroom), and the second external accessory device is an external device that is grouped under both the "Home" group and the "Dining Room" category (e.g., a light located in a dining room). In contrast, in some embodiments, the first external accessory device is the same device as the second external accessory device (e.g., they are the same light located in the dining room, or they are the same smart speaker located in the dining room).

[0278] In some embodiments, a first selectable user interface object object (e.g., 726) (e.g., while being displayed as part of a first user interface) is displayed via (e.g., on) the display generation component at a first location (e.g., at locations 726 and 776) and a second selectable user interface object object (e.g., 776) (e.g., while being displayed as part of a second user interface) is displayed via (e.g., on) the display generation component at a first location (e.g., at locations 726 and 776). In some embodiments, input received while displaying the first user interface causes the second selectable user interface object object to replace the display of the first selectable user interface object object. By providing a first selectable user interface object or a second selectable user interface object object at the same location when a predetermined condition is met, a user can quickly locate a selectable user interface object object for multicast without having to identify any different operational characteristics of the selectable user interface object objects (e.g., which particular set of devices are selectable, which particular selectable user interface object object sends a recorded voice message). Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), plus reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0279] In some embodiments, a first external accessory device (e.g., 646, 648) (e.g., a smart speaker that can be configured to play music using a first accessory control user interface object object) is included in the set of external devices (e.g., the first external accessory device is configurable from a first user interface and audio (recorded on a computer system) is sent to the first external accessory device using a first selectable user interface object object). In some embodiments, the first user interface includes a third accessory control user interface object object (e.g., 718b) (e.g., a selectable user interface object object) that corresponds to a third external accessory device (e.g., 642). In some embodiments, selection of the third accessory control user interface object object initiates a process of sending a command (e.g., selection causes sending of a command) to change a state of the third external accessory device (e.g., lock or unlock a door, turn a light on or off). In some embodiments, the third external accessory device (e.g., 642) is not included in the set of external devices and selection of the first selectable user interface object object (e.g., 776) does not initiate a process for sending (and / or recording) the first voice message to the third external accessory device (e.g., 706 of 7F). In some embodiments, the first user interface includes accessory control user interface object objects for some external accessory devices that can be controlled (e.g., turned on / off) but the first voice message is not sent (e.g., because the external accessory device does not have a speaker for playing the voice message), and the first user interface includes accessory control user interface object objects for some external accessory devices that can be controlled (e.g., turned on / off) and the first voice message is sent (e.g., because the external accessory device has a speaker for playing the voice message).In some embodiments, the second user interface includes accessory control user interface object objects for some external accessory devices that may be controlled (e.g., turned on / off) but for which the second voice message is not transmitted (e.g., because the external accessory device does not have a speaker for playing the voice message), and the second user interface includes accessory control user interface object objects for some external accessory devices that may be controlled (e.g., turned on / off) and for which the second voice message is transmitted (e.g., because the external accessory device has a speaker for playing the voice message). In some embodiments, the first set of one or more external devices (e.g., devices in the bedroom group for which the voice message is transmitted) does not include a first external accessory device (e.g., a light in the bedroom group for which the voice message is not transmitted), and the second set of external devices (e.g., devices in the dining room for which the voice message is transmitted) does not include a second external accessory device (e.g., a light in the dining room group for which the voice message is not transmitted). Thus, in some embodiments, the voice message is not necessarily sent to all devices that can be controlled using an accessory control user interface object object that, when selected, causes the respective accessory device to perform one or more functions and / or change the state of the respective accessory device. In some embodiments, the external devices that can be controlled using the respective accessory control user interface object object (to perform one or more functions and / or change the state of the respective accessory device) are included in a set of external devices (e.g., a first or second set of external devices) and thus the voice message can be sent to that external device and the external device can be controlled separately.

[0280] In some embodiments, a first user interface corresponds to a top-level location (e.g., 602) (e.g., structure, home) and a second user interface corresponds to a first sub-location (e.g., 602d) of a first type (e.g., 602a-602e) (e.g., room of the structure, dining room of the home). In some embodiments, a second set of one or more external devices (e.g., 646, 648) corresponds to the first sub-location (e.g., 602d) (e.g., the second set of one or more external devices is designated for the sub-location of the first type). In some embodiments, a second set of (e.g., any) one or more external devices (e.g., 646, 648) may be made to correspond to a second sub-location (e.g., 602a, 602b, 602c, or 602e) (e.g., any sub-location other than the first sub-location) of the first type (e.g., any other room of the structure) based on the second set of one or more external devices (e.g., 602a-602e) corresponding to the first sub-location. In some embodiments, the first user interface corresponds to a top-level location and the second user interface corresponds to a sub-location of the top-level location (e.g., a room of the home). In some embodiments, the first room and the second room are part of a zone (e.g., a collection of rooms grouped together). In some embodiments, the second set of one or more external devices are devices identified (e.g., by a user) to be located in the room to which the second user interface corresponds.

[0281] In some embodiments, the first user interface corresponds to a top-level location (e.g., structure, home) and the second user interface corresponds to a third sub-location of a second type (entertainment zone (e.g., 602d and 602e)) (e.g., first zone, main floor) that corresponds to a plurality of sub-locations (e.g., 602a-602e) of a first type (e.g., 602a-602e) (e.g., a plurality of rooms). In some embodiments, the second set of one or more external devices corresponds to a third sub-location (e.g., a plurality of rooms of a structure including a first room (e.g., dining room of a home) and a second room (e.g., bedroom of a home)) based on the second set of one or more external devices included in the plurality of sub-locations (e.g., 602a-602e) of the first type. In some embodiments, the first user interface corresponds to a top-level location and the second user interface corresponds to a sub-location of the top-level location (e.g., a plurality of rooms of a home). In some embodiments, the second set of one or more external devices includes at least one device designated for the first room and at least one device designated for the second room. In some embodiments, the top-level location corresponds to at least one device that the third sub-location does not correspond to (e.g., the home includes some devices that are not included within the third sub-location).

[0282] In some embodiments, the second external accessory device is associated with (e.g., corresponds to) a third sub-location of the second type (e.g., entertainment zone (e.g., 602d and 602e)) (e.g., the first zone). In some embodiments, the second external accessory device (e.g., 646, 648) is also associated with (e.g., corresponds to) a fourth sub-location (e.g., second zone) of the second type (e.g., entertainment zone (e.g., 602d and 602e)) that is different from the third sub-location. In some embodiments, the second zone is a sub-location (e.g., multiple rooms of a home). In some embodiments, the second zone is associated with an external accessory device that is not associated with the first zone. In some embodiments, the computer system can initiate a process to record and send messages to the various zones. The first zone and the second zone can correspond to different sets of devices, some of which correspond to both the first zone and the second zone, and some of which correspond to only one of the first zone or the second zone.

[0283] In some embodiments, a second set of one or more external devices (e.g., 646, 648) is associated with the first location (e.g., 602d) (e.g., a room, a sub-location, a zone), and the process for recording and transmitting the second voice message to the second set of one or more external devices without transmitting the second voice message to the first set of one or more external devices includes displaying an indication (e.g., a textual indication, a graphical indication) of the first location (e.g., 782) (e.g., text specifying the name of the room or zone to which the voice message is to be transmitted). In some embodiments, the process for recording and transmitting the voice message includes displaying an indication of the location corresponding to the external device to which the respective voice message is to be transmitted. In some embodiments, the first user interface corresponds to a top-level location (e.g., a structure such as a home), and the second user interface corresponds to a sub-location of the top-level location (e.g., a room of the home, a zone of the home). In some embodiments, upon displaying the second user interface, the computer system detects a selection (e.g., a tap on, a press, and a hold) of a second selectable user interface object. In some embodiments, in response to detecting a selection of the second selectable user interface object object, the computer system displays (e.g., by replacing all or a portion of the second user interface) a record user interface object object (e.g., a selectable record button) where selection (e.g., tapping, pressing, and holding) of the record user interface causes recording of the voice message by recording the voice detected by the computer system, and a record user interface that simultaneously includes a suggestion (e.g., a text suggestion, a graphical suggestion) of a sub-location (e.g., letters specifying the name of a room or zone where the voice message is to be sent). In some embodiments, the second user interface includes the suggestion of the sub-location.By displaying an indication of a location associated with a group of devices to which the audio message is intended to be multicast, the user is provided with visual feedback regarding the status of the process for recording and transmitting the audio message. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0284] In some embodiments, as part of initiating the process for recording and transmitting an audio message to an external device, the computer system automatically (e.g., without intervening user input corresponding to a request to start recording audio) records the new audio message and displays a recording user interface (e.g., 741) that includes a dynamic indication of the audio being recorded (e.g., 744a).

[0285] In some embodiments, the computer system detects a selection (e.g., a tap, press, and hold) of the record user interface object object. In response to detecting the selection of the record user interface object object, the computer system records a voice message. After recording the voice message (and before sending the voice message), the computer system provides an option to change the external device to which the message is sent. In some embodiments, the computer system receives activation of a drop-down affordance and, in response, displays one or more sub-locations (each corresponding to a respective set of external devices). The computer system receives a selection of one of the one or more sub-locations and a confirmation to send the voice message. In response, the computer system sends the voice message to the respective set of external devices corresponding to the selected sub-location instead of the second set of one or more external devices corresponding to the second user interface.

[0286] In some embodiments, the set of external devices includes a personal mobile electronic device (e.g., 604, 634, 684) (e.g., a smart phone, a mobile phone, a watch). In some embodiments, the personal mobile electronic device is not included in the first set of one or more devices and is not included in the second set of one or more external devices. In some embodiments, the personal mobile electronic device is not assigned to any sub-location of the top-level location, but is a member of the top-level location. Thus, in some embodiments, selecting the first selectable user interface object object initiates a process of recording and sending a voice message to the set of external devices, including the personal mobile electronic device (and any other personal mobile electronic devices that are members of the top-level location).

[0287] In some embodiments, the second set of one or more external devices does not include a personal mobile electronic device (e.g., 604, 634, 684) (e.g., a smart phone, a mobile phone, a watch). In some embodiments, a personal mobile electronic device is not included in the first set of one or more devices and is not included in the second set of one or more devices. In some embodiments, the set of external devices includes a personal mobile electronic device, and thus a voice message sent from the first user interface is sent to the personal mobile electronic device (and, optionally, to other mobile devices that are part of the home). In some embodiments, a voice message sent from the second user interface (or any user interface corresponding to a sub-location) is not sent to the personal mobile electronic device (and, optionally, not sent to other mobile devices that are part of the home). In some embodiments, the computer system refuses to assign the personal mobile electronic device to any sub-location of the top-level location, but allows the personal mobile electronic device to be assigned to the top-level location. Thus, in some embodiments, selecting the second selectable user interface object object initiates a process of recording and sending a voice message to a second set of one or more devices that do not include the personal mobile electronic device (or any other personal mobile electronic devices that are members of the top-level location).

[0288] In some embodiments, the computer system receives an input (e.g., 750q) (e.g., user input, input on a settings user interface) after displaying the second user interface to disable sending of the voice message to the second set of one or more external devices (e.g., 638). In some embodiments, in response to receiving the input to disable sending of the voice message to the second set of one or more external devices, the computer system disables sending of the voice message to the second set of one or more external devices via selection of the first selectable user interface object object (e.g., 726) (e.g., without disabling sending of the voice message to the first set of one or more external devices via selection of the first selectable user interface object object) and to the second set of one or more external devices via selection of the second selectable user interface object object (e.g., 776) (e.g., 768a). In some embodiments, after disabling sending of the voice message to the second set of one or more external devices, navigating to the first user interface and receiving a selection of the first selectable user interface object object initiates a process of recording and sending a voice message to the first set of one or more external devices without sending the voice message to the second set of one or more external devices. In some embodiments, in response to receiving an input to disable sending of the voice message to the second set of one or more external devices, the computer system removes the second set of one or more external devices from the set of external devices. In some embodiments, after disabling sending of the voice message to the second set of one or more external devices, navigating to the second user interface and receiving a selection of the second selectable user interface object object does not initiate a process of recording and sending a voice message to any device.In some embodiments, after disabling the sending of voice messages to the second set of one or more external devices, the second user interface does not include a second selectable user interface object object (or includes a non-selectable / disabled version of the user interface object object), thereby preventing the process of recording and sending a voice message to the second set of one or more external devices from being initiated.

[0289] In some embodiments, the first user interface corresponds to a top-level location (e.g., 602) (e.g., a structure such as a home), and the second user interface corresponds to a sub-location (e.g., 602a-602d) of the top-level location (e.g., 602) (e.g., a room of the home, a zone of the home). In some embodiments, the computer system receives (808) an audio input (e.g., 792a-792e) including a natural language request of the digital assistant at a microphone communicating with the computer system (e.g., a microphone of the computer system) (e.g., while not displaying the first user interface and not displaying the second user interface), the audio input includes a voice message (e.g., including the term "multicast"), a location identifier (e.g., a top-level location, a sub-location), and a voice message (e.g., received after an instruction to initiate a process to send the voice message and / or received after the location identifier). In some embodiments, pursuant to a determination that the location identifier corresponds to a top-level location (e.g., 782a), the computer system transmits (810) the audio message to any of the set of external devices, including the first set of one or more external devices and the second set of one or more external devices, for playback on the set of external devices without establishing a two-way audio communication channel (e.g., without establishing a full-duplex audio communication channel) (e.g., multicast). In some embodiments, pursuant to a determination that the location identifier corresponds to a sub-location (e.g., 792b, 792c), the computer system transmits (812) the audio message to any of the set of external devices, for playback on the second set of one or more external devices and not on the first set of one or more external devices, without establishing a full-duplex audio communication channel with any of the set of external devices (e.g., multicast). In some embodiments, the computer system transmits the location identifier along with the audio message such that a remote device (e.g., a service, an external device of the set of external devices) can distribute the audio message to the external devices corresponding to the respective external devices.

[0290] In some embodiments, when part of initiating a process for recording and sending a voice message to an external device, the computer displays (e.g., by replacing all or a portion of the second user interface) a record user interface object object (e.g., 736) (e.g., a selectable record button) where selection (e.g., 750c) of the record user interface object object (e.g., tapping and then pressing the end when the voice message is completed, pressing and holding while speaking the voice message, tapping to allow the computer system to identify the end of the voice message) causes recording of the voice message by recording the voice detected by the computer system, and a send user interface object object (e.g., 756) (e.g., a selectable send button) where selection (e.g., 750e) of a second user interface object object (e.g., tapping) causes the computer system to send the voice message to the external device. In some embodiments, the recording user interface also simultaneously includes a suggestion (e.g., a text suggestion, a graphical suggestion) of the location (e.g., letters specifying the name of a top-level location, a sub-location, a room or zone from which the voice message is being sent) corresponding to the external device from which the voice message is being sent.

[0291] In some embodiments, the computer system communicates with one or more input devices, including a microphone. In some embodiments, as part of a process (e.g., user interfaces 730, 740, 750) for recording and transmitting a first audio message to a set of external devices, the computer system receives a second audio input via the microphone. In some embodiments, the computer system transmits a first audio message to a set of external devices, the first audio message being based on the second audio input (e.g., including a recording of).

[0292] It should be noted that the process details described above with respect to method 800 (e.g., FIGS. 8A-8B) apply equally to the methods described below. For example, method 800 optionally includes any one or more of the various method features described below with respect to methods 1000 and 1200. For example, the computer system may be the same system. In another example, the voice message sent in method 800 may be the media received in 1000. In another example, the voice input sent in method 1200 may be the same as the media received in method 1000. For the sake of brevity, these details will not be repeated below.

[0293] 9A-9X show example devices and example user interfaces for displaying notifications, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0294] The phrases "multicast message" and / or "audio multicast message" are generally used herein with respect to Figures 9A-9X to refer to multicast messages transmitted from a device using techniques similar to those described in Figures 7A-7AH, 8A-8B, 11A-11F, and 12. However, as used herein, multicast message and / or audio multicast message are not necessarily intended to include multicast communications transmitted using other features of device 700.

[0295] 9A illustrates electronic device 700 displaying user interface 900. In FIG. 9A, electronic device 700 is a portable multifunction device and includes one or more of the components described above with respect to any one or more of devices 100, 200, 300, and 500. With respect to the figures described below, in some embodiments, device 700 is operating less than a threshold distance away from home 602. However, in other embodiments, device 700 is operating more than a threshold distance away from home 602.

[0296] As shown in FIG. 9A, user interface 900 is a settings user interface corresponding to the home application, as described above (e.g., FIGS. 6 and 7A-7AH). Here, the settings user interface is a settings page for Cam Appleseed, which is a person (e.g., a user) registered with device 700 and recognized by the home application (e.g., group of people 797a in FIG. 7AB). As shown in FIG. 9A, device 700 is configured to receive multicast notifications, as indicated by multicast option 900a being enabled in FIG. 9A. Because multicast option 900a is enabled, multicast notifications are received by device 700, as shown in FIGS. 9B-9X. In some embodiments, device 700 detects a tap gesture 950a at a location corresponding to multicast option 900a. In some embodiments, in response to detecting the tap gesture 950a (or one or more subsequent tap gestures), the device 700 changes the multicast option 900a from enabled to disabled, such that the device 700 is not configured to receive multicast messages that are transmitted according to the flows described herein. Thus, in some embodiments, when the multicast option 900a is disabled, the device 700 does not receive multicast messages.

[0297] 9B-9H illustrate multicast and non-multicast notifications displayed over a period of time while multicast option 900a is enabled. Specifically, FIGS. 9B-9H illustrate that multicast notifications (e.g., multicast messages sent using methods described herein) directed to (e.g., corresponding to) a particular target group of devices disappearing or ceasing to display (e.g., after a predetermined period of time) unless a new multicast notification also directed to the particular target group of devices is received within the predetermined period of time. In some embodiments, the particular target group of devices is a group of devices designated for a home (e.g., home 602 of FIG. 6), a room (e.g., dining room 602b, bedroom 602c of FIG. 6), or a zone (e.g., an "entertainment zone" as described in connection with FIG. 7U, for example).

[0298] For example, in FIG. 9B, at 10:00 AM, device 700 receives data indicating that updated content has been published by a news application.

[0299] As shown in Figure 9B, in response to receiving the data, the device 700 displays a user interface that includes a news notification 902. In Figure 9B, the news notification 902 is not a multicast notification. Thus, the news notification 902 is displayed regardless of whether the multicast option 900a is enabled or disabled. In other words, the state of the multicast option 900a does not affect the news notification 902 because it is not a multicast notification.

[0300] At 10:02 AM, device 700 receives data indicating that a new audio multicast message has been sent to home 602 (e.g., directed to devices including electronic device 700). In some embodiments, the data includes a target group identifier (e.g., "home") as a receiver of the new audio multicast message.

[0301] As shown in Figure 9C, in response to receiving the data, the device 700 displays a multicast notification 904 representing the data received at 10:02 AM. In Figure 9C, the multicast notification 904 is displayed simultaneously with the news notification 902. The multicast notification 904 includes application suggestions 904a, notification type suggestions 904b, sender suggestions 904c, target suggestions 904d, and time of reception suggestions 904e.

[0302] Application suggestion 904a indicates the application that provided the notification, where application suggestion 904a includes a graphical representation icon designated for the home application and similar to home icon 704a of FIG.

[0303] The notification type indication 904b indicates the notification type of the notification, where the notification type is a multicast notification.

[0304] Sender suggestion 904c indicates the sender of the audio multicast message. Here, the sender is a person, John, who is registered with the device that initiated the process to send the audio multicast message (e.g., a device in the home target group). In some embodiments, if the sender is a person, the identity of the sender is established by one or more devices analyzing the audio input corresponding to the audio multicast message using one or more audio identification algorithms. In some embodiments, if the identity of the sender cannot be established as a person, sender suggestion 904c indicates that the sender is a device, such as the device that is sending the audio multicast message (e.g., a "living room speaker"). In some embodiments, the sender is not established as a person, e.g., when a person is not registered with the sender device that initiated the process to send the audio multicast message and / or when multiple people are registered with the sender device that initiated the process to send the audio multicast message, the person is not established with the sender device.

[0305] Target suggestion 904d indicates a target group of devices to which the audio multicast message corresponds. Here, target suggestion 904d is a home target group (e.g., "From Home"). In some embodiments, the target group (corresponding to the audio multicast message) is a group identified by the sender of the audio multicast message, as described above in connection with FIGS. 7E-7F, 7J-7M, and 7S-7U. In some embodiments, the target group is identified by the sender of the audio multicast message based on one or more user inputs (e.g., voice inputs (e.g., 792a-792d) and / or gestures (e.g., 750b and 750g3). In some embodiments, when a return message is received at device 700, the target group is identified based on the initial audio multicast message. For example, device 700 may receive a return audio multicast message having a target group corresponding to bedroom 602c in some circumstances, such as when device 700 previously directed an initial audio multicast message to a group of devices designated for bedroom 602c.

[0306] The time of receive suggestion 904e indicates when the notification was displayed (or, in some embodiments, when the data corresponding to the notification was received), where the time of receive suggestion 904e indicates that the notification was displayed "NOW" or at 10:02 AM.

[0307] As shown in Figure 9D, at 10:09 AM, device 700 continues to display news notification 902 and ceases displaying multicast notification 904. In some embodiments, notification 904 is not displayed at all on the user interface of device 700 after the multicast notification ceases to be displayed. In some embodiments, notification 904 is not displayed on the user interface of Figure 9D at any other time after the multicast notification ceases to be displayed. In some embodiments, the device receives user input to view pending notifications (e.g., notifications not affected by the user) and, in response, displays new notification 902 without displaying multicast notification 904.

[0308] 9D, the device 700 stops displaying the multicast notification 904 (even if the display is on) because no data corresponding to a new audio multicast message corresponding to the home target group is received before the end of the decay period (e.g., 1 second, 30 seconds, 60 seconds, 300 seconds, etc.) of the multicast notification 904 (and / or within a predetermined period of time). On the other hand, if the device 700 determines that the news notification 902 is not a multicast notification and the predetermined period of time has elapsed (and if the display is on), the device 700 continues displaying the news notification 902.

[0309] Figures 9E-9H show examples of techniques in addition to the examples described above in connection with Figures 9B-9D. In Figures 9B-9D, the decay period of the multicast notification (e.g., the predetermined period of time) is 5 minutes for illustrative purposes only. In some embodiments, the decay period is less than or greater than 5 minutes.

[0310] At 10:10, device 700 receives three different sets of data: a first set of data indicates that a new audio multicast message has been received corresponding to the home target group; a second set of data indicates that a new audio multicast message has been received corresponding to a group of devices designated for the bedroom 602c (the "bedroom target group"); and a third set of data indicates that a new audio multicast message has been received corresponding to a group of devices designated for an entertainment zone (the "entertainment zone target group") (e.g., a combination of the groups of devices designated for the living room 602d and sunroom 602e).

[0311] In some embodiments, the first set of data represents an initial audio multicast message or a reply audio multicast message (e.g., a reply to an initial audio multicast message sent by device 700) corresponding to a home target group. In some embodiments, the second set of data and the third set of data represent reply audio multicast messages, i.e., audio multicast messages, received in response to an initial audio multicast message sent separately to the corresponding target group. In some embodiments, the second set of data and the third set of data are not initial messages received from the respective target groups because device 700 is not designated for the zone or room target groups and cannot receive initial messages sent from those target groups, as described above (e.g., FIGS. 7M, 7T, 7V, and 7X).

[0312] As shown in FIG 9E, in response to receiving the set of three data, device 700 displays multicast notifications 906a, 908a, and 910. Device 700 also continues to display news notification 902. As shown in FIG 9E, the notifications are displayed in a notification list. The oldest notifications are displayed at the bottom of the list (e.g., news notification 902) and the newest notifications are at the top of the list (e.g., multicast notification 910). Thus, notifications 906a, 908a, and 910 were displayed approximately simultaneously, although notifications 906a, 908a, and 910 were each displayed in the order shown in FIG 9E. In some embodiments, the notifications are displayed in a different order or in a different sequence.

[0313] As shown in Figure 9E, notification 906a indicates that an audio multicast message was sent by "John" from the home target group. Notification 908a indicates that an audio multicast message was sent by "Jane" from the bedroom target group, and notification 910 indicates that an audio multicast message was sent by "Emma" from the entertainment zone target group. As shown in Figure 9E, all three of the new multicast notifications include a time reception indication of "NOW" because the data was recently received (or the notification was recently displayed) at 10:10 AM. However, the time reception indication for news notification 902 is "10 minutes ago" because the data was recently received (or the notification was displayed) at 10:00.

[0314] At 10:11 AM, device 700 receives data indicating that a new audio multicast message corresponding to the home target group has been received.

[0315] As shown in Figure 9F, in response to receiving the new data, device 700 displays multicast notification 906b before the decay period of multicast notification 906a expires (e.g., within a predetermined period of time after displaying multicast notification 906a or receiving the first data of Figure 9E) because data has been received indicating a new audio multicast message corresponding to the home target group (e.g., data received at 10:11). In particular, device 700 does not update the display of notifications 906a and 910 and continues to display these notifications because data has not been received indicating a new audio multicast message corresponding to their respective target groups and their decay periods have not expired (e.g., they have not been displayed for more than five minutes without receiving data corresponding to a new multicast message for their target group).

[0316] Multicast notification 906b is an updated version of multicast notification 906a that device 700 stopped displaying in FIG. 9F. Looking again at FIG. 9E, multicast notification 906a indicates that John has sent a multicast message corresponding to the home target group. Returning to FIG. 9F, multicast notification 906b also includes information that John sent a previous multicast message (the multicast message of the original representation by notification 906a) corresponding to the home target group (e.g., “John” in notification 906b). In addition, multicast notification 906b includes information that the other has sent a multicast message corresponding to the home target group. Thus, multicast notification 906b includes information about two audio multicast messages, i.e., multicast notification 906b includes information representing a sender (“John”) of a first audio multicast message corresponding to the home target group and a sender (e.g., “the other”) of a second audio multicast message corresponding to the home target group.

[0317] As shown in FIG. 9F, multicast notification 906b is displayed at the top of the list with the current time reception indication because it is the most recent notification. In particular, the time reception indication of multicast notification 906b is changed in FIG. 9F to reflect the time when a new audio multicast message corresponding to the home target group was received (e.g., data received at 10:11), whereas multicast notification 906a was first displayed (or data corresponding to multicast notification 906a was first received) at 10:10 in FIG. 9E. In some embodiments, multicast notification 906a is displayed simultaneously with multicast notification 906b. In some embodiments, when multicast notification 906a is displayed simultaneously with multicast notification 906b, the time reception indication of multicast notification 906a is updated to read "NOW." In some embodiments, updating the time indication of multicast notification 906a extends the decay period of multicast notification 906a. In some embodiments, receipt of the data in FIG. 9F extends the decay period of multicast notification 906a (or the content of multicast notification 906a, for example, because multicast notification 906b includes content representing the audio multicast message represented by multicast notification 906a).

[0318] As shown in Figure 9F, notifications 910, 908a, and 902, each listed from most recent to least recent, are below multicast notification 906b. In addition, the time reception indications of notifications 910, 908a, and 902 have been updated in Figure 9F to reflect the amount of time each has been displayed (or the amount of time that has passed since the data corresponding to each respective notification was received).

[0319] At 10:12 AM, device 700 receives data indicating that a new audio multicast message corresponding to the bedroom target group has been received.

[0320] As shown in FIGURE 9G, in response to receiving the data, device 700 displays multicast notification 908b before the decay period of multicast notification 908b expires (e.g., within a predetermined period of time after displaying multicast notification 906b or receiving the second data of FIGURE 9E) because data indicating a new audio multicast message corresponding to the Bedroom target group has been received (e.g., data received at 10:12). Notably, device 700 does not update notifications 908b and 910 and continues to display notifications 908b and 910 because data indicating a new audio multicast message corresponding to their respective target groups has not been received and their decay periods have not expired. In some embodiments, multicast notification 908b is displayed using a technique similar to that described above in FIGURE 9F with respect to multicast notification 906b.

[0321] Multicast notification 908b is an updated version of multicast notification 908a, which device 700 stopped displaying in FIG. 9G. Returning to FIG. 9E, multicast notification 908a indicates that Jane sent a multicast message corresponding to the Bedroom target group. Returning to FIG. 9G, multicast notification 908b indicates that two multicast messages were sent by Jane corresponding to the Bedroom target group. Now, instead of multicast notification 908b including a new sender, multicast notification 908b displays content representing an increased amount of notifications sent by each sender as compared to multicast notification 908a. In some embodiments, multicast notification 908a includes a representation of the amount of notifications received from the Bedroom target group, regardless of whether a different sender sent a new multicast message.

[0322] As shown in FIG. 9H, multicast notification 908b is displayed at the top of the list, and notifications 906b, 910, and 902 are displayed below multicast notification 908b in order of most recent to least recent.

[0323] 9H, at 10:15 AM, device 700 ceases displaying multicast notification 910 because the decay period for multicast notification 910 has expired. In other words, device 700 has not received data indicating a new audio multicast message corresponding to the target group of multicast notification 910 (e.g., "entertainment zone") within a predetermined time (or before the end of the decay period for notification 910) when multicast notification 910 was first displayed (or data indicating an audio multicast message corresponding to the entertainment target group was received). Thus, referring to FIG. 9E, because data corresponding to each of the target groups indicated in the first and second sets of data was received before the decay period of each respective notification expired, while data corresponding to the target group indicated in the third set of data was not received before the decay period of the multicast notification 910 expired, the device 700 continues to display the content representing the first set of data (e.g., John in multicast notification 906b) and the content representing the second set of data (e.g., one of the multicasts in multicast notification 908b) and no longer displays the content representing the third set of data (e.g., multicast notification 910).

[0324] 9I-9P illustrate user interfaces for playback of received audio multicast messages. Specifically, FIGS. 9I-9K illustrate a scenario in which multiple audio multicast messages are automatically played in response to a single input. Additionally, FIGS. 9L-9P illustrate a scenario in which one received audio multicast message is selected from a group of other received audio multicast messages and played. In FIG. 9H, device 700 detects tap gesture 950h at a location corresponding to multicast notification 906b.

[0325] As shown in FIG. 9I, in response to detecting the tap gesture 950h, the device 700 displays a user interface 920. The user interface 920 is a user interface for displaying the audio multicast messages shown in the multicast notification 906b, which are audio multicast messages corresponding to the home target group (as indicated by "Multicast from Home" in FIG. 9I). The user interface 920 includes a graphical sender suggestion 924a and a graphical sender suggestion 924b, each of which represents one of the audio multicast messages represented in the multicast notification 906b. Here, the graphical sender suggestion 924a is larger than the graphical sender suggestion 924b, and indicates in the center of the user interface that the audio multicast message corresponding to the graphical sender suggestion 924a is currently selected for playback. The graphical sender suggestion 924a is an image of a speaker device and represents data corresponding to the audio multicast message sent by the "other" received at 10:11 AM in FIG. 9F. Graphical sender suggestion 924b is an image of John (i.e., 797a containing an image of John A. in FIG. 7AB) and the data representative corresponds to the audio multicast message sent by John received at 10:10 AM in FIG. 9E. In some embodiments, the audio messages are displayed in the order in which they were received (e.g., in FIG. 9E, graphical sender suggestion 924b and graphical sender suggestion 924b are toggled). User interface 920 further includes current sender suggestion 922a, which indicates the name assigned to the speaker or device displayed in the center of the user interface (or the largest graphical sender suggestion). Here, current sender suggestion 922a indicates that the speaker has a name of "Living Room" and that an audio multicast message from the sender is currently playing or can currently be played by selection of play affordance 926.In addition, device 700 also displays a remaining indication 928 indicating that the currently selected audio multicast message has a length of 10 seconds that can be played, and a count indication 930 representing that the selected audio multicast message is 2 messages 1 out of the total number of audio multicast messages that correspond to the home target group. In some embodiments, when settings are enabled to enable phonetic transcription of audio multicast messages, user interface 920 includes a textual representation of the currently selected audio multicast message.

[0326] As shown in Figure 9I, device 700 receives data indicating that a new audio multicast message corresponding to the bedroom target group has been received and, in response to receiving the data, displays multicast notification 940. In some embodiments, device 700 updates the list of notifications based on this received data, as described in connection with Figure 9L below. In Figure 9I, device 700 detects a tap gesture 950i at a location corresponding to playback affordance 926.

[0327] As shown in FIGS. 9J-9K, in response to detecting the tap gesture 950i, the device 700 starts playing media. As shown in FIG. 9J, the device 700 plays the last received audio multicast message corresponding to the home target group (e.g., received at 10:11 in FIG. 9F above). In FIG. 9J, the device 700 displays a time display 932 and updates suggestions 928 and 930 while playing the currently selected audio multicast message (e.g., audio multicast message from “the other” received at 10:11). As shown in FIG. 9K, the device 700 is currently playing the first audio multicast message corresponding to the home target group (e.g., received at 10:10 from John in FIG. 9E above). In particular, the device 700 automatically plays the first audio multicast message after completing playback of the last audio multicast message corresponding to the home target group (e.g., without receiving additional input after detecting the tap gesture 950i).

[0328] As shown in FIG. 9L, some time after displaying the user interface in FIG. 9K, device 700 redisplays the list of notifications. Notification 902b now ceases to display. In some embodiments, notification 902b ceases to display because a gesture was detected at the location corresponding to the notification and / or any one or more of the audio multicast messages were played in FIGS. 9J-9K. In some embodiments, notification 902b ceases to display because its decay period ended (e.g., at 10:16 AM) before a new multicast corresponding to the home target group was received.

[0329] In FIG. 9L, the device 700 is also displaying the multicast notification 908c and has ceased displaying the multicast notification 908b. The multicast notification 908c is an updated version of the multicast notification 908b that has been updated to reference data corresponding to the audio multicast message received in FIG. 9I, which was represented in FIG. 9I by the multicast notification 940. Thus, the multicast notification 908b includes content indicating that two multicast notifications corresponding to the Bedroom target group have been received, while the multicast notification 908c has been updated to include content indicating that three multicast notifications corresponding to the Bedroom target group have been received. In FIG. 9L, the device 700 detects a press and hold gesture 950l at a location corresponding to the multicast notification 908c. In some embodiments, the device 700 detects the press and hold gesture 950l while the gesture continues to be detected (or held). In some embodiments, the device 700 detects the press and hold gesture after the gesture is released.

[0330] As shown in FIG. 9M, in response to detecting the press and hold gesture 950l, the device 700 displays a user interface 960 (e.g., after termination of the press and hold gesture 950l while continuing to detect the press and hold gesture 950l). The user interface 960 includes user interface elements similar to the user interface 920 (as described above in connection with FIGS. 9I-9K). However, the user interface 960 has a smaller area than the user interface 920. While the user interface 960 is a user interface for playing an audio multicast message from the bedroom target group, the device 700 can use one or more techniques such as those described above in connection with the user interface 920. In some embodiments, in response to detecting a user input 950m1 on the open affordance 962, the device 700 ceases displaying the user interface 960 and displays a user interface of a similar size to the user interface 920. In FIG. 9M, the device 700 detects a swipe gesture 950m2 at a location corresponding to the user interface 960.

[0331] As shown in Figure 9N, in response to detecting a first gesture (e.g., swipe gesture 950m2), device 700 changes the currently selected audio multicast message from the last received audio multicast message corresponding to the Bedroom target group (e.g., when its corresponding data was received in Figure 9I) to a second last received audio multicast message corresponding to the Bedroom target group (e.g., when its corresponding data was received in Figure 9G). In Figure 9N, device 700 detects a swipe gesture 950n at a location corresponding to user interface 960.

[0332] As shown in Figure 9O, in response to detecting a second gesture (e.g., swipe gesture 950n), device 700 changes the currently selected audio multicast message from the second most recently received audio multicast message corresponding to the Bedroom target group (e.g., when its corresponding data was received in Figure 9F) to the first received audio multicast message corresponding to the Bedroom target group (e.g., when its corresponding data was received in Figure 9E). In Figure 9O, device 700 detects a tap gesture 950o at a location corresponding to user interface 960 (e.g., on playback affordance 926).

[0333] As shown in FIG. 9P, in response to detecting tap gesture 950o, device 700 begins playing the first received audio multicast message (e.g., currently selected) corresponding to the Bedroom target group without beginning playback of any other audio multicast messages. In some embodiments, in FIG. 9P (or 9I-9J), device 700 detects tap gesture 950p at a location corresponding to multicast affordance 736, and in response to detecting tap gesture 950p at a location corresponding to multicast affordance 736, device 700 begins recording media via one or more input devices, as described above (e.g., FIG. 7C and FIG. 7I). In some embodiments, in FIG. 9P, device 700 detects one or more audio inputs, such as audio input 720a (as described above), and sends an audio multicast message corresponding to the Bedroom target group for playback to Jane.

[0334] 9Q-9V show example user interfaces for displaying the above-described user interfaces on a device having a smaller display than device 700, such as smartwatch 701. Any of the above-described user interfaces can be displayed and transitioned on smartwatch 701 (e.g., user interfaces 970, 972, 974, 976, 978, and 980) (or tablet 634) using one or more techniques similar to those described above for FIGS.

[0335] 9W-9X show example user interfaces for displaying the above-described user interfaces on a device, such as computing device 674. As described above, in some embodiments, computing device 674 communicates with one or more devices that transmit instructions for computing device 674 to display one or more user interfaces. Any of the above-described user interfaces can be displayed and transitioned on computing device 674 (e.g., user interfaces 996 and 998) using one or more techniques similar to those described above for FIGS. 9A-9P.

[0336] 10 is a flow diagram illustrating a method for displaying a notification using a computer system, according to some embodiments. Method 1000 is performed on a computer system (e.g., 100, 300, 500, 634, 674, 700, 701, 850) in communication with a display generation component. Some operations of method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0337] As described below, the method 1000 provides an intuitive way to display notifications. This method reduces the cognitive burden on the user when viewing notifications, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling users to access notifications more quickly and efficiently conserves power and extends the time between battery charges.

[0338] The computer system receives (1002) first data corresponding to a first medium.

[0339] The computer system (e.g., in response to receiving the first data) displays (1004) via the display generation component a first notification (e.g., 906a, 908a, 910) having a suggestion of the first media (e.g., 904b, 904c) (e.g., a notification corresponding to the first data) (e.g., a notification selectable to initiate a process of playing the first media) until the end of the first time period (e.g., a predetermined first time period).

[0340] After receiving the first data (e.g., after initiating display of the first notification), the computer system receives (1006) second data corresponding to a second media, where the second media (e.g., 932 of 9J) is different from the first media (e.g., 932 of 9K).

[0341] The computer system, pursuant to a determination that the second media satisfies a set of one or more criteria (and in some embodiments the one or more criteria include criteria that are met when the second media is directed to the same target group as the first media), as well as a determination based on (1) the time the second data was received and (2) the time the first data was received (e.g., a determination that the second data was received within a predetermined time after the first data was received), displays (1008) via the display generation component until the end of the second time period (e.g., in response to receiving the second data). In some embodiments, the second time period is based on receiving the second data. In some embodiments, the second time period is not based on receiving the first data. In some embodiments, the second time period is a predetermined second time period), a second notification (e.g., 906b, 908b, 908c) having an indication (e.g., indication of 906b (e.g., "John"), 908b (e.g., "2")) of the first media (e.g., 932 of 9K) (e.g., a notification corresponding to at least the first data) (e.g., a notification selectable to initiate a process for playing at least the first media) (e.g., a notification indicating receipt of at least the first data), where an end of the first time period is different from an end of the second time period. In some embodiments, the second notification is the first notification. In some embodiments, the second notification is different from the first notification (e.g., the second notification is a notification that combines (1) information corresponding to the first media and (2) information corresponding to the second media). In some embodiments, the second notification is displayed after the first time period (e.g., displayed initially). In some embodiments, when receipt of the second media is within a predetermined time of receipt of the first media, the amount of time that the information corresponding to the first media is displayed is extended. In some embodiments, the second time period is determined based on a difference between when the first data is received and when the second data is received.In some embodiments, the media (e.g., first media, second media) is an audio message recorded on another device and sent to a group of devices, including a computer system that receives the first data and the second data. In some embodiments, the set of one or more criteria includes a criterion that is met when the second media is received before the end of the display period of the first media (e.g., the duration that the notification is active, the duration that the notification is displayed in the collection of notifications). In some embodiments, the set of one or more criteria includes a criterion that is met when the second media is received before ceasing to display the first notification (e.g., via activation of the first notification, via user input clearing the first notification). Dynamically displaying the second notification, including a notification included in the first notification that is related to the second notification when certain criteria are met, provides the user with feedback about the relationship between the second notification and the first notification, while also allowing the user to continue to display suggestions included in the first notification even when ceasing to display the first notification. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0342] In some embodiments, the first notification (e.g., 906a) is displayed when the second data is received (e.g., pursuant to a determination that the second media meets a set of one or more criteria). In some embodiments, as part of displaying the second notification (e.g., 906b), the computer system ceases displaying the first notification (e.g., in FIG. 9E). In some embodiments, the display of the first notification is stopped pursuant to a determination that the second media meets a set of one or more criteria (and in some embodiments, the one or more criteria include criteria that are met when the second media is directed to the same target group as the first media) and pursuant to a determination that the second data is received within a predetermined time after the first data is received. By ceasing to display the first notification when the second notification includes information regarding the first notification, feedback is provided to the user regarding the information in the first notification without disrupting the user interface. Providing improved visual feedback to the user improves usability of the device, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with a computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0343] In some embodiments, the first media is a first audio message (e.g., 932 in 9K) (e.g., an audio message recorded (using a microphone) at an external device and transmitted by an external device to a group of devices, an audio message directed (e.g., sent) to multiple external devices including the computer system). In some embodiments, the second audio message is a second audio message directed (or sent) to a second multiple external devices (e.g., different from the multiple external devices, the same as the multiple external devices). Displaying a notification associated with the multicast audio message provides visual feedback to the user regarding the type of notification, thereby allowing the user to identify that the notification will decay and need to be responded to within a predetermined period of time. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0344] In some embodiments, the first notification (e.g., 904) includes an indication (e.g., 904d) of a group of multiple external devices to which the first media (e.g., 932 of 9K) was sent (e.g., the first data corresponding to the media was sent). In some embodiments, the first data identifies a group of multiple external devices to which the first media was intended. In some embodiments, the multiple external devices include computer systems. Displaying the notification including an indication of the group of devices to which the first media was intended provides the user with feedback regarding the devices sending and / or receiving the playback message. Providing the user with improved visual feedback enhances operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0345] In some embodiments, in response to receiving the first data, the computer system adds the first notification (e.g., 906a) to a collection of notifications (e.g., the notifications displayed in FIGS. 9B-9H) (e.g., a collection of notifications accessible for display, a list display of recent notifications, displayed in response to a user input requesting display of a collection of notifications) until the end of a first time period (e.g., a predetermined first time period). In some embodiments, pursuant to reaching the end of the first time period, the computer system removes the first notification (e.g., 904) from the collection of notifications. In some embodiments, pursuant to receiving second data corresponding to the second media prior to the end of the first time period, and pursuant to a determination that the second media satisfies a set of one or more criteria, the computer system removes the first notification (e.g., 906a) from the collection of notifications and adds the second notification (e.g., 906b) to the collection of notifications. In some embodiments, the second notification is added to the set of notifications without removing the first notification from the set of notifications in accordance with receiving data corresponding to the media before the end of the first predetermined time period and in accordance with determining that the second media does not satisfy a set of one or more criteria. In some embodiments, the computer system removes the first notification from the set of notifications in accordance with a display end condition being met for the first notification. By choosing to remove a notification when no additional data related to the notification (e.g., no updates or no new media) has been received within a certain period of time, the device can avoid providing stale (e.g., old, irrelevant) notifications to the user that clutter the UI without requiring the user to manually remove the notification.By performing an optimized action when a set of conditions are met without requiring further user input, the computer system's operability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and, in addition, reducing power usage and improving the computer system's battery life by enabling the user to use the computer system more quickly and efficiently.

[0346] In some embodiments, the first data identifies a target group of multiple external devices to which the first media is directed (e.g., sent). In some embodiments, while displaying a notification (e.g., 906a, 908a, 910) (e.g., a first notification) corresponding to the first media (e.g., and which, when activated, initiates a process for playing the first media (e.g., a first audio message), the computer system receives (1010) third data corresponding to a third media. In some embodiments, in response to receiving third data corresponding to the third media (1012), and in accordance with a determination that the third media satisfies a set of one or more criteria (in some embodiments, the one or more criteria include criteria that are met...

Claims

1. 1. A method comprising:

1. A computer system in communication with a display generating component, comprising: via said display generating component, a first representation of a first media message comprising a first audio, at a first location of a media user interface, the first media message being directed to a target group of devices, the target group of devices including a plurality of devices designated to a physical location, each device in the target group of devices being programmatically mapped to the target group of devices; a second representation of a second media message including a second voice at a second location of the media user interface different from the first location of the media user interface, the second representation of a third media message including a third voice, the second media message and the third media message being directed to the target group of devices; a multicast affordance within the media user interface that, when activated, initiates the process of sending an audio multicast message to the target group of devices; displaying the media user interface, in response to displaying the media user interface, playing the first audio of the first media message not based on user input corresponding to the media user interface; in response to detecting a completion of the playback of the first audio of the first media message, via the display generation component; the second representation of the second media message in the first location of the media user interface without displaying a representation corresponding to the first media message; and the third representation of the third media message in a third location of the media user interface different from the first location; and and A method comprising:

2. Displaying the first representation of the first media message at the first location includes displaying the first representation of the first media message at the first location and in a first size; displaying the second representation of the second media message at the second location includes displaying the second representation of the second media message at the second location in a second size different from the first size. The method of claim 1.

3. via the display generation component, simultaneously with the first representation of the first media message at the first location and the second representation of the second media message at the second location; displaying a fourth representation of a fourth media message in a third size different from the first size and at a third location different from the first location and the second location; in response to detecting a completion of the playback of the first audio of the first media message, via the display generation component; the second representation of the second media message without displaying the first representation of the first media message in the first location at the first size; the fourth representation of the fourth media message at the second size and at the second location; and and The method of claim 1 or 2, further comprising:

4. The computer system is configured to communicate with one or more input devices, and the method further comprises: receiving data corresponding to media messages, the first media message being a first message from a first remote user, and the second media message being a second message from a second remote user different from the first remote user; displaying, via the display generation component, a notification corresponding to the first media message; receiving, via the one or more input devices, a selection of the notification while displaying the notification, wherein displaying the media user interface occurs in response to receiving the selection of the notification, and playing the first media message occurs in response to receiving the selection of the notification; The method of claim 1 , further comprising:

5. The method of claim 1 , wherein the first size is greater than the second size and the third size.

6. 6. The method of claim 1, further comprising, in response to detecting completion of playback of the first audio of the first media message, playing the second media message without receiving further user input.

7. Prior to detecting completion of playback of the first media message, the third representation of the third media message is not displayed simultaneously with the first representation of the first media message, and the method further comprises:

7. The method of claim 1, further comprising: displaying, via the display generation component, the third representation of the third media message after detecting completion of playback of the first media message.

8. The computer system is configured to communicate with one or more input devices, and the method further comprises: while playing the second media message, displaying in the media user interface a next media user interface object that, when activated, causes playback of the second media message to be completed; receiving, via the one or more input devices, an activation of the next media user interface object while playing the second media message; in response to receiving the activation of the next media user interface object, displaying via the display generation component the fourth representation of the fourth media message in the first location without displaying via the display generation component the second representation of the second media message; The method of claim 1 , further comprising:

9. 9. The method of claim 1, further comprising, after playing the final media message, displaying in the media user interface via the display generation component a playback user interface object that, when activated, plays the first media message before proceeding to play a subsequent media message.

10. 10. The method of claim 1, further comprising displaying, via the display generation component, in the media user interface during playback of each media message, the name of each user from whom the respective media message was received.

11. 11. The method of claim 1, wherein the representation of the currently playing media message is displayed in a first background color that is different from one or more background colors of respective display representations of media messages that are not currently playing.

12. The method of claim 1 , wherein the first media message and the second media message are audio messages.

13. 13. The method of claim 1, wherein the first representation of the first media message indicates a first sender and the second representation of the second media message indicates a second sender.

14. the first representation of the first media message is displayed together with a representation of a currently playing media message; 14. The method of claim 1, wherein the second representation is displayed without the representation of the currently playing media message.

15. and further in response to detecting a completion of playing the first audio of the first media message.

15. The method of claim 14, further comprising displaying the second representation of the second media message in the first location along with the representation of the currently playing media message.

16. The method of claim 14 , wherein the representation of the currently playing media message varies in size based on the audio of the currently playing media message.

17. 17. The method of claim 1, wherein the media user interface further comprises a count indicator indicating a total number of media messages queued for playback.

18. 20. The method of claim 17, wherein the total number of representations of media messages displayed in the media user interface is a predetermined number, and the number indicated by the count indicator is greater than the number of representations of media messages displayed in the media user interface.

19. The method of claim 14 , wherein the media user interface includes a progress indicator that indicates the number of the currently playing media message relative to a total number of media messages queued for playing.

20. 20. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the computer system being in communication with a display generating component, the one or more programs including instructions for performing the method of any one of claims 1 to 19.

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

22. 1. A computer system comprising: Means for carrying out the method according to any one of claims 1 to 19, A computer system comprising:

Images