Multi-User Configuration

Abstract

To execute a user-specific task in a multi-user environment.SOLUTION: A method includes, at an electronic device: receiving a request; and in response to the request: if a voice input does not match a voice profile associated with an account associated with the electronic device: causing output of first information based on the request using a first account associated with the electronic device; if a setting of the electronic device has a first state, causing update of account data of the first account based on the request; and if the setting has a second state, forgoing causing update of the account data; and if the voice input matches a voice profile associated with an account associated with the electronic device: causing output of the first information using the account associated with the matching voice profile; and causing update of account data of the account based on the request.SELECTED DRAWING: Figure 6A

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 62 / 855,903, entitled "MULTI-USER CONFIGURATION," filed May 31, 2019, U.S. Nonprovisional Application No. 16 / 584,347, entitled "MULTI-USER CONFIGURATION," filed September 26, 2019, and U.S. Nonprovisional Application No. 16 / 584,321, entitled "MULTI-USER CONFIGURATION," filed September 26, 2019, the contents of which are incorporated herein by reference in their entirety for all purposes. [Technical field]

[0002] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for multi-user configuration of electronic devices. [Background technology]

[0003] The number of electronic devices, especially smart devices, in a user's home continues to grow. These devices are required to perform more and more complex tasks, including user-specific tasks in a multi-user environment. Summary of the Invention

[0004] However, some techniques for multi-user configuration with 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 keystrokes. 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 multi-user configuration. Such methods and interfaces, optionally, complement or replace other methods for multi-user configuration. 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 increase the time between battery charges.

[0006] An exemplary method is described herein. The exemplary method includes receiving, at an electronic device having a media output device, a request determined based on a voice input, and in response to receiving the request, causing the media output device to output first information based on the request using a first account associated with the electronic device in accordance with a determination that the voice input does not match a voice profile associated with an account associated with the electronic device, causing account data for the first account to be updated based on the request in accordance with a setting of the electronic device being set to a first state, and refraining from updating the account data for the first account based on the request in accordance with a setting of the electronic device being set to a second state, and in accordance with a determination that the voice input matches a voice profile associated with the account associated with the electronic device, causing the media output device to output the first information based on the request using an account associated with the matching voice profile, and causing account data for the account associated with the matching voice profile to be updated based on the request.

[0007] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a media output device, the one or more programs including instructions for receiving a request determined based on a voice input, and in response to receiving the request, causing the media output device to output first information based on the request using a first account associated with the electronic device in accordance with a determination that the voice input does not match a voice profile associated with an account associated with the electronic device, causing a setting of the electronic device to update account data for the first account based on the request in accordance with a setting of the electronic device being set to a first state, and refraining from updating the account data for the first account based on the request in accordance with a setting of the electronic device being set to a second state, and in accordance with a determination that the voice input matches a voice profile associated with the account associated with the electronic device, causing the media output device to output the first information based on the request using an account associated with the matching voice profile, and causing the account data for the account associated with the matching voice profile to be updated in accordance with the request.

[0008] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a media output device, the one or more programs including instructions for receiving a request determined based on a voice input, and in response to receiving the request, causing the media output device to output first information based on the request using a first account associated with the electronic device in accordance with a determination that the voice input does not match a voice profile associated with an account associated with the electronic device, causing a setting of the electronic device to update account data for the first account based on the request in accordance with a setting of the electronic device being set to a first state, refraining from updating the account data for the first account based on the request in accordance with a setting of the electronic device being set to a second state, and in accordance with a determination that the voice input matches a voice profile associated with the account associated with the electronic device, causing the media output device to output the first information based on the request using an account associated with the matching voice profile, and updating the account data for the account associated with the matching voice profile in accordance with the request.

[0009] An exemplary electronic device is described herein. The exemplary electronic device includes a media output device, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to receive a request determined based on a voice input, and in response to receiving the request, cause the media output device to output first information based on the request using a first account associated with the electronic device in accordance with a determination that the voice input does not match a voice profile associated with an account associated with the electronic device, update account data for the first account based on the request in accordance with a setting of the electronic device being set to a first state, refrain from updating the account data for the first account based on the request in accordance with a setting of the electronic device being set to a second state, and in accordance with a determination that the voice input matches a voice profile associated with the account associated with the electronic device, cause the media output device to output the first information based on the request using an account associated with the matching voice profile, and update account data for the account associated with the matching voice profile in accordance with the request.

[0010] An example electronic device includes a media output device; means for receiving a request determined based on the audio input; and means for, in response to receiving the request, causing the media output device to output first information based on the request using a first account associated with the electronic device in accordance with a determination that the audio input does not match a audio profile associated with an account associated with the electronic device, causing account data for the first account to be updated based on the request in accordance with settings of the electronic device being set to a first state, and refraining from updating the account data for the first account based on the request in accordance with settings of the electronic device being set to a second state, and causing the media output device to output the first information based on the request using an account associated with the matching audio profile in accordance with a determination that the audio input matches a audio profile associated with the account associated with the electronic device, and causing account data for the account associated with the matching audio profile to be updated based on the request.

[0011] An example method includes: detecting, at a first device having a display device and one or more input devices, that one or more devices associated with the first device support respective functions; displaying, on the display device, a prompt to configure the respective functions of the one or more devices in accordance with a determination that a set of criteria is met including criteria that are met when the one or more devices support the respective functions; receiving, via the one or more input devices, a set of one or more inputs while displaying the prompt to configure the respective functions of the one or more devices; performing a configuration operation associated with the respective functions in response to receiving the set of one or more inputs; and refraining from displaying, on the display device, the prompt to configure the respective functions of the one or more devices in accordance with a determination that the one or more devices do not support the respective functions.

[0012] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the one or more programs including instructions for detecting that one or more devices associated with a first device support respective functions, displaying, on the display device, a prompt to configure the respective functions of the one or more devices in accordance with a determination that a set of criteria is met that includes criteria that are met when the one or more devices support the respective functions, receiving, via the one or more input devices, a set of one or more inputs while displaying the prompt to configure the respective functions of the one or more devices, performing a configuration operation associated with the respective function in response to receiving the set of one or more inputs, and refraining from displaying, on the display device, the prompt to configure the respective functions of the one or more devices in accordance with a determination that the one or more devices do not support the respective functions.

[0013] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the one or more programs including instructions for detecting that one or more devices associated with a first device support respective functions, displaying, on the display device, a prompt for configuring the respective functions of the one or more devices in accordance with a determination that a set of criteria is met including criteria that are met when the one or more devices support the respective functions, receiving, via the one or more input devices, a set of one or more inputs while displaying the prompt for configuring the respective functions of the one or more devices, performing a configuration operation associated with the respective function in response to receiving the set of one or more inputs, and refraining from displaying, on the display device, the prompt for configuring the respective functions of the one or more devices in accordance with a determination that the one or more devices do not support the respective functions.

[0014] An exemplary electronic device comprises a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for detecting that one or more devices associated with the first device support respective functions, displaying, on the display device, a prompt to configure the respective functions of the one or more devices in accordance with a determination that a set of criteria is met including criteria that are met when the one or more devices support the respective functions, receiving, via the one or more input devices, a set of one or more inputs while displaying the prompt to configure the respective functions of the one or more devices, in response to receiving the set of one or more inputs, performing a configuration operation associated with the respective function, and refraining from displaying, on the display device, the prompt to configure the respective functions of the one or more devices in accordance with a determination that the one or more devices do not support the respective functions.

[0015] An exemplary electronic device comprises a display device, one or more input devices, and means for detecting that one or more devices associated with the first device support respective functions; and means for displaying, on the display device, a prompt for configuring the respective functions of the one or more devices in accordance with a determination that a set of criteria is met that includes criteria that are met when the one or more devices support the respective functions; receiving, via the one or more input devices, a set of one or more inputs while displaying the prompt for configuring the respective functions of the one or more devices; performing a configuration operation associated with the respective functions in response to receiving the set of one or more inputs; and refraining from displaying, on the display device, the prompt for configuring the respective functions of the one or more devices in accordance with a determination that the one or more devices do not support the respective functions.

[0016] An example method includes, at an electronic device having a display device and one or more input devices, receiving input via the one or more input devices; and in response to receiving the input, displaying on the display device a setting interface for a plurality of devices associated with a plurality of accounts including one or more administrator accounts and one or more non-administrator accounts, wherein the electronic device is associated with a first account of the plurality of accounts, and in accordance with the first account being an administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for a second account different from the first account, the setting interface includes one or more settings of a first type and one or more settings of a second type, the one or more settings of the first type being editable via the setting interface and the one or more settings of the second type being not editable via the setting interface, and in accordance with the first account being a non-administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for the first account, the setting interface includes one or more settings of a second type and the one or more settings of the second type being editable via the setting interface.

[0017] An exemplary 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 a display device and one or more input devices, the one or more programs including instructions for receiving input via the one or more input devices and, in response to receiving the input, displaying on the display device a setting interface for a plurality of devices associated with a plurality of accounts, including one or more administrator accounts and one or more non-administrator accounts, wherein the electronic device is associated with a first account of the plurality of accounts, and in accordance with the first account being an administrator account of the plurality of accounts and the setting interface being a setting interface for a second account different from the first account, the setting interface includes one or more settings of a first type and one or more settings of a second type, the one or more settings of the first type being editable via the setting interface and the one or more settings of the second type being not editable via the setting interface, and in accordance with the first account being a non-administrator account of the plurality of accounts and the setting interface being a setting interface for the first account, the setting interface includes one or more settings of a second type and the one or more settings of the second type being editable via the setting interface.

[0018] An exemplary temporary computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the one or more programs including instructions for receiving input via the one or more input devices and, in response to receiving the input, displaying on the display device a setting interface for a plurality of devices associated with a plurality of accounts, including one or more administrator accounts and one or more non-administrator accounts, wherein the electronic device is associated with a first account of the plurality of accounts, and in accordance with the first account being an administrator account of the plurality of accounts and the setting interface being a setting interface for a second account different from the first account, the setting interface includes one or more settings of a first type and one or more settings of a second type, the one or more settings of the first type being editable via the setting interface and the one or more settings of the second type being not editable via the setting interface, and in accordance with the first account being a non-administrator account of the plurality of accounts and the setting interface being a setting interface for the first account, the setting interface includes one or more settings of a second type and the one or more settings of the second type being editable via the setting interface.

[0019] An exemplary electronic device comprises a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for receiving input via the one or more input devices and, in response to receiving the input, displaying on the display device a setting interface for a plurality of devices associated with a plurality of accounts, including one or more administrator accounts and one or more non-administrator accounts, wherein the electronic device is associated with a first account of the plurality of accounts, and in accordance with the first account being an administrator account of the plurality of accounts and the setting interface being a setting interface for a second account different from the first account, the setting interface includes one or more settings of a first type and one or more settings of a second type, the one or more settings of the first type being editable via the setting interface and the one or more settings of the second type being not editable via the setting interface, and in accordance with the first account being a non-administrator account of the plurality of accounts and the setting interface being a setting interface for the first account, the setting interface includes one or more settings of a second type and the one or more settings of the second type being editable via the setting interface.

[0020] An exemplary electronic device comprises a display device, one or more input devices, means for receiving input via the one or more input devices, and means for displaying, in response to receiving the input, on the display device a setting interface for a plurality of devices associated with a plurality of accounts, including one or more administrator accounts and one or more non-administrator accounts, wherein the electronic device is associated with a first account of the plurality of accounts, and in accordance with the first account being an administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for a second account different from the first account, the setting interface includes one or more settings of a first type and one or more settings of a second type, the one or more settings of the first type being editable via the setting interface and the one or more settings of the second type being not editable via the setting interface, and in accordance with the first account being a non-administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for the first account, the setting interface includes one or more settings of a second type and the one or more settings of the second type being editable via the setting interface.

[0021] An example method includes, at an electronic device having a display device and one or more input devices, displaying a device access configuration user interface via the display device including at least a first set of device access affordances; receiving, while displaying the device access configuration user interface, a set of one or more inputs via the one or more input devices including inputs specifying one or more users; in response to receiving the set of one or more inputs, the set of one or more inputs including an input corresponding to a selection of a first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that includes the first permission; and in response to the set of one or more inputs not including an input corresponding to a selection of the first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that does not include the first permission.

[0022] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the one or more programs including instructions for displaying, via the display device, a device access configuration user interface including at least a first set of device access affordances; receiving, while displaying the device access configuration user interface, via the one or more input devices, a set of one or more inputs including inputs specifying one or more users; in response to receiving the set of one or more inputs, the set of one or more inputs including an input corresponding to a selection of a first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that includes the first permission; and in response to the set of one or more inputs not including an input corresponding to a selection of the first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that does not include the first permission.

[0023] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the one or more programs including instructions for displaying, via the display device, a device access configuration user interface including at least a first set of device access affordances; receiving, while displaying the device access configuration user interface, via the one or more input devices, a set of one or more inputs including inputs specifying one or more users; in response to receiving the set of one or more inputs, the set of one or more inputs including an input corresponding to a selection of a first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that includes the first permission; and in response to the set of one or more inputs not including an input corresponding to a selection of the first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that does not include the first permission.

[0024] An exemplary electronic device comprises a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying, via the display device, a device access configuration user interface including at least a first set of device access affordances; receiving, while displaying the device access configuration user interface, via the one or more input devices, a set of one or more inputs including inputs specifying one or more users; in response to receiving the set of one or more inputs, the set of one or more inputs including an input corresponding to a selection of a first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that includes the first permission; and in response to the set of one or more inputs not including an input corresponding to a selection of the first permission setting, sending an invitation that, when accepted, provides access to the one or more users including access to the set of devices based on a first permission setting that does not include the first permission.

[0025] An exemplary electronic device comprises a display device, one or more input devices, and means for displaying a device access configuration user interface via the display device, the device access configuration user interface including at least a first set of device access affordances; means for receiving, while displaying the device access configuration user interface, a set of one or more inputs via the one or more input devices including inputs specifying one or more users; and means for, in response to receiving the set of one or more inputs, sending an invitation that, when accepted, provides access to the one or more users based on a first permission setting including the first permission, and sending an invitation that, when accepted, provides access to the one or more users based on a first permission setting including the first permission, and in response to the set of one or more inputs not including an input corresponding to a selection of the first permission setting, the first permission setting including the first permission.

[0026] An example method includes, at an electronic device having a display device and one or more input devices and associated with a first account of the first set of accounts, displaying a prompt on the display device to invite the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts includes at least one account not included in a second set of accounts that includes the first account; receiving, via the one or more input devices after displaying the prompt, a set of one or more inputs; in response to receiving the set of one or more inputs, sending an invitation to a selection of the at least one account not included in the second set of accounts to join the second set of accounts; and refraining from displaying the prompt on the display device to invite the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account not included in the second set of accounts.

[0027] An exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the electronic device being associated with a first account of a first set of accounts, the one or more programs including instructions for: displaying a prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts includes at least one account that is not included in a second set of accounts that includes the first account; receiving one or more sets of inputs via the one or more input devices after displaying the prompt; sending an invitation to join the second set of accounts to a selection of the at least one account that is not included in the second set of accounts in response to receiving the one or more sets of inputs; and refraining from displaying the prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts.

[0028] An exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices, the electronic device being associated with a first account of a first set of accounts, the one or more programs including instructions for: displaying a prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts includes at least one account that is not included in a second set of accounts that includes the first account; receiving, after displaying the prompt, a set of one or more inputs via the one or more input devices; sending an invitation to join the second set of accounts to a selection of the at least one account that is not included in the second set of accounts in response to receiving the set of one or more inputs; and refraining from displaying the prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts.

[0029] An example electronic device associated with a first account of the first set of accounts comprises a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a prompt on the display device to invite the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts includes at least one account that is not included in a second set of accounts that includes the first account; receiving one or more sets of inputs via the one or more input devices after displaying the prompt; sending an invitation to join the second set of accounts to a selection of the at least one account that is not included in the second set of accounts in response to receiving the one or more sets of inputs; and refraining from displaying the prompt on the display device to invite the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts.

[0030] An example electronic device associated with a first account of the first set of accounts comprises a display device, one or more input devices, and means for displaying a prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts includes at least one account that is not included in a second set of accounts that includes the first account, receiving one or more sets of inputs via the one or more input devices after displaying the prompt, and sending an invitation to a selection of the at least one account that is not included in the second set of accounts to join the second set of accounts in response to receiving the one or more sets of inputs, and means for refraining from displaying the prompt on the display device inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts.

[0031] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured for execution 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 for execution by one or more processors.

[0032] Thus, devices with faster, more efficient methods and interfaces for multi-user configuration are provided, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for multi-user configuration. [Brief description of the drawings]

[0033] 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:

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

[0035] [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing according to some embodiments.

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

[0037] [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.

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

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

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

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

[0042] [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.

[0043] [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.

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

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

[0046] [Figure 6A] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6B] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6C] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6D] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6E] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6F] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6G] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6H] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6I] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6J] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6K] 1 illustrates an example technique for processing a user request according to some embodiments. [Figure 6L]1 illustrates an example technique for processing a user request according to some embodiments.

[0047] [Figure 7A] FIG. 1 is a flow diagram illustrating a process for processing a user request according to some embodiments. [Figure 7B] FIG. 1 is a flow diagram illustrating a process for processing a user request according to some embodiments. [Figure 7C] FIG. 1 is a flow diagram illustrating a process for processing a user request according to some embodiments.

[0048] [Figure 8A] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8B] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8C] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8D] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8E] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8F] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8G] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8H] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8I] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8J]1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8K] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8L] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8M] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8N] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8O] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8P] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8Q] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8R] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8S] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8T] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8U] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8V] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8W] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8X] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8Y] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8Z] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8AA] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 8AB] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments.

[0049] [Figure 9] FIG. 1 is a flow diagram illustrating a process for configuring a user account according to some embodiments.

[0050] [Figure 10A] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10B] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10C] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10D] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10E] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10F] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10G]1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10H] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10I] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10J] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10K] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10L] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments. [Figure 10M] 1 illustrates an exemplary user interface for configuring a user account according to some embodiments.

[0051] [Figure 11] FIG. 1 is a flow diagram illustrating a process for configuring a user account according to some embodiments.

[0052] [Figure 12A] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12B] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12D] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12E]1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12F] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 12G] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments.

[0053] [Figure 13] FIG. 1 is a flow diagram illustrating a process for adding a user to a location profile according to some embodiments.

[0054] [Figure 14A] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 14B] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 14C] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 14D] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 14E] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments. [Figure 14F] 1 illustrates an exemplary user interface for adding a user to a location profile according to some embodiments.

[0055] [Figure 15] FIG. 1 is a flow diagram illustrating a process for adding a user to a location profile according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0056] 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 rather is provided as a description of example embodiments.

[0057] There is a need for electronic devices that provide efficient methods and interfaces for multi-user configuration. Such techniques can reduce the cognitive burden on users of configuring one or more devices for multi-user applications, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that is otherwise wasted on redundant user input.

[0058] In the following, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of an exemplary device for performing a technique for managing event notifications. FIGS. 6A-6L show exemplary user interfaces for processing user requests. FIGS. 7A-7C are flow diagrams illustrating a method for processing user requests, according to some embodiments. The user interfaces of FIGS. 6A-6L are used to illustrate processes described below, including the process of FIGS. 7A-7C. FIGS. 8A-8AB show exemplary user interfaces for configuring a user account. FIG. 9 is a flow diagram illustrating a method for configuring a user account, according to some embodiments. The user interfaces of FIGS. 8A-8AB are used to illustrate processes described below, including the process of FIG. 9. FIGS. 10A-10M show exemplary user interfaces for configuring a user account. FIG. 11 is a flow diagram illustrating a method for configuring a user account, according to some embodiments. The user interfaces of FIGS. 10A-10M are used to illustrate processes described below, including the process of FIG. 11. 12A-12G show exemplary user interfaces for adding a user to a location profile. FIG. 13 is a flow diagram illustrating a method for adding a user to a location profile, according to some embodiments. The user interfaces of FIGS. 12A-12G are used to illustrate processes described below, including the process of FIG. 13. FIGS. 14A-14F show exemplary user interfaces for adding a user to a location profile. FIG. 15 is a flow diagram illustrating a method for adding a user to a location profile, according to some embodiments. The user interfaces of FIGS. 14A-14F are used to illustrate processes described below, including the process of FIG. 15.

[0059] 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.

[0060] 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.

[0061] 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]."

[0062] 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).

[0063] 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.

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

[0065] 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.

[0066] 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.

[0067] 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 various techniques and various 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., weighted averaged) 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 measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units that correspond to the surrogate measure). In some implementations, the surrogate measure of the contact force or pressure is converted to an estimate of the force or pressure, and the estimate of the force or pressure is used to determine whether an intensity threshold is 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 may enable a user to access additional device functionality (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons) that may not otherwise be accessible on devices of reduced size that have limited footprint for displaying affordances.

[0068] 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 a 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, a 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.Wireless technology includes, but is not limited to, wireless technology such as wireless LAN, wireless technology such as wireless technology with a cellular network (WAN), wireless technology such as wireless technology with a cellular network (WAN-CDMA), wireless technology such as wireless technology with a cellular network (WAN-SWAN ... 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.

[0073] 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).

[0074] 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 / 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).

[0075] A quick press of the push button optionally unlocks the touch screen 112 or optionally initiates a process of unlocking the device using gestures 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.

[0076] 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, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0077] 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.

[0078] 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.

[0079] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to a multi-touch-sensing touchpad as 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 / 0015024 (A1), each of which is incorporated by reference in its entirety. However, whereas touchscreen 112 displays visual output from device 100, a touch-sensitive touchpad does not provide visual output.

[0080] The touch-sensitive display in some embodiments of the touch screen 112 is described in the following applications: (1) 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.

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

[0082] 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 separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0083] 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.

[0084] 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 or video images. In some embodiments, the light sensor is located on the back side of device 100 opposite touchscreen display 112 on the front side of the device, so that the touchscreen display can be used as a viewfinder for still and / or video capture. In some embodiments, the light sensor is located on the front side of the device such that an image of the user is optionally obtained for a video conference while the user views 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), such that a single light sensor 164 is used for both video conferencing and still image and / or video capture, in conjunction with a touchscreen display.

[0085] 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 cooperation with imaging module 143 (also called camera module), depth camera sensor 175 is optionally used to determine a depth map of different parts of an image captured by imaging module 143. In some embodiments, a depth camera sensor is disposed on the front of device 100 to obtain an image of a user with depth information for a video conference and to capture a selfie image with depth map data while the user views other video conference participants on a touch screen display. In some embodiments, depth camera sensor 175 is disposed 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 still and / or video capture in conjunction with a touchscreen display.

[0086] 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.

[0087] Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripheral interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 in I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent applications 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,” all of which are incorporated herein by reference in their entireties. In some embodiments, when the multifunction device is placed near a user's ear (eg, when the user is making a phone call), the proximity sensor turns off and disables touchscreen 112.

[0088] 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 commands 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, the 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.

[0089] 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 entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape view based on an analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the position and orientation (e.g., vertical or horizontal) of device 100.

[0090] 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 an active application state indicating which applications, if any, are currently active, a display state indicating which applications, views, or other information are occupying various regions of touchscreen display 112, a sensor state including 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.

[0091] 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 general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

[0092] 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.

[0093] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact has occurred (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 events of dragging a finger), 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.

[0094] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine 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 modifying 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 modifying 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 by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0095] 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.

[0096] 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, video, animations, and the like.

[0097] 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.

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

[0099] 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).

[0100] The GPS module 135 determines the location of the device and provides this information for use within various applications (e.g., to the phone 138 for use in location-based dialing, to the camera 143 as picture / 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).

[0101] 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 images and / or video; ● 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 creator module 150 for creating user-created widgets 149-6; ● Search module 151, A video and music player module 152 that combines a video player module and a music player module; ● Memo module 153, Map module 154, and / or ● Online video module 155.

[0102] 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.

[0103] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), including adding name(s) to the address book, deleting name(s) from the address book, associating phone number(s), electronic address(es), physical address(es) or other information with names, associating pictures with names, 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.

[0104] Telephone module 138, 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, 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, place calls, and disconnect and hang up when a call is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0105] Video conferencing module 139 includes executable instructions to cooperate 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, contact module 137, and telephone module 138 to initiate, conduct, and end a video conference between a user and one or more other participants in accordance with instructions from the user.

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

[0107] Instant messaging module 141 includes executable instructions in cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 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 as 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).

[0108] The training support module 142 includes executable instructions to cooperate 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, the GPS module 135, the map module 154, and the music player module to create workouts (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit the workout data.

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

[0110] Image management module 144, in conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, 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.

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

[0112] The calendar module 148 includes executable instructions to cooperate 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, the email client module 140, and the browser module 147 to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) according to user instructions.

[0113] The widget module 149, in conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, optionally provides mini-applications (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 are downloaded and used by the user, or mini-applications (e.g., user-created widget 149-6) that are created by the user. In some embodiments, the widgets include a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, the widgets include an Extensible Markup Language (XML) file and a JavaScript file (e.g., Yahoo! Widget).

[0114] The widget creator module 150, 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, is optionally used by a user to create a widget (e.g., turn a user-specified portion of a web page into a widget).

[0115] The search module 151 includes executable instructions for operating 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 to search for text, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

[0116] Video and music player module 152 includes executable instructions that cooperate 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 to 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.).

[0117] The notes module 153 includes executable instructions for cooperating with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to create and manage notes, to-do lists, and the like as directed by a user.

[0118] Map module 154, 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, 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 a user's instructions.

[0119] Online video module 155, 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, 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), send emails with links to the particular online videos, and otherwise manage the 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 the particular online videos, rather than email client module 140. For additional description of online video applications, see 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.

[0120] 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 herein (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.

[0121] 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. By using the touchscreen and / or touchpad as the primary input control device for operation of device 100, optionally the number of physical input control devices (push buttons, dials, etc.) on device 100 is reduced.

[0122] 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.

[0123] 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).

[0124] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 of application 136-1. 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 delivered to.

[0125] 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.

[0126] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about a sub-event (e.g., a user touch as part of a multi-touch gesture on touch-sensitive display 112). 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.

[0127] 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).

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

[0129] 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.

[0130] 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.

[0131] 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 the 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 occurs (e.g., the first sub-event in a sub-event sequence that forms an event or potential event). 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 the touch or input source identified as the hit view.

[0132] 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.

[0133] Event dispatcher module 174 dispatches the event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers 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.

[0134] 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.

[0135] 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, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. 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 handlers 190 optionally utilize or call 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.

[0136] 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).

[0137] 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).

[0138] 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. A 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 (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0139] 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.

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

[0141] 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.

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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.

[0148] 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 (right to left, left to right, upwards and / or downwards) of a finger in contact with device 100. 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.

[0149] Device 100 optionally also 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 within a set of applications executing on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touch screen 112.

[0150] 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 an alternative embodiment, 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.

[0151] 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 and a touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to FIG. 1A) for generating 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.

[0152] 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.

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

[0154] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to 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 indicator 405, ● a battery status indicator 406; ● Tray 408 with icons of frequently used applications, such as: o An icon 416 for the phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages; o 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 o An icon 422 for the video and music player module 152, also called the iPod (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 Stocks widget 149-2, labeled "Stock Prices"; ○ Icon 436 of map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 for 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 o A settings application or module icon 446 labeled “Settings,” which provides access to settings for the device 100 and its various applications 136 .

[0155] 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player," although 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.

[0156] 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.

[0157] 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, as 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 movement) 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.

[0158] In addition, while 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 moving the contact). As another example, a tap gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact and then stopping detection of the contact) while the cursor is located over the location of the tap gesture. Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

[0159] 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 touch(s) based on their intensity, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0160] For exemplary techniques for detecting and processing touch intensity, see, for example, related applications International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Patent Application No. WO / 2013 / 169849, 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.

[0161] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, 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.

[0162] 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 technologies. 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.

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

[0164] The memory 518 of the personal electronic device 500 can 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, can cause the computer processors to perform techniques described below, including processes 700, 900, 1100, 1300, and 1500 (FIGS. 7A-7C, 9, 11, 13, and 15). A computer readable storage medium can be any medium that can tangibly contain or store computer executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some 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 can 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, and 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.

[0165] The term "affordance" as used herein optionally refers to a user-interactive graphical user interface object 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.

[0166] 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 position 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 allows 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 a 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 specific 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).

[0167] 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 (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 a lift-off of the contact, before or after detecting the start of movement of the contact, before detecting an 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 not exceeding the first threshold results in a first action, a contact having a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and a contact having a characteristic intensity above 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 refrain from performing the respective action).

[0168] 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 the aggregate intensity A according to a predefined 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.

[0169] 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 position to an end position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position is optionally based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end position) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact prior to determining the characteristic intensity of the contact. 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 narrow spikes or dips in the swipe contact intensity for purposes of determining the characteristic intensity.

[0170] 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 pressure intensity threshold, a deep pressure intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light pressure 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 pressure 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 pressure intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is not detected), the device follows the movement of the contact on the touch-sensitive surface and moves the focus selector without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent among various sets of values ​​for a user interface.

[0171] 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 detecting 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 detecting 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.

[0172] 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).

[0173] 5E-5H show the results of the light pressure intensity threshold (e.g., "IT L ") to the deep press intensity threshold 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 1"). 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 predefined region 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 pressure intensity threshold (e.g., “IT D "), reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents are displayed to app2 for contact 562, as shown in FIGS. 5F-5H. In some embodiments, this intensity, which 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.

[0174] 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 pressure intensity threshold (e.g., "ITD Representations 578A-578C appear and move upward as the intensity of the animation increases toward "intensity of contact." 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.

[0175] 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 that has a predefined 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 the 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, as the case may be).

[0176] 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 a contact above the press input intensity threshold, an increase in the intensity of a contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of a contact below the press input intensity threshold, and / or a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0177] 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 touch(s) based on their intensity, 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), a number of discrete LEDs, a cluster of discrete LEDs, or other arrangement of one or more LEDs. For example, display 580E can be an array of nine discrete 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.

[0178] 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 that operably couples 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-sensing component 584 and, optionally, an intensity sensor 585 (e.g., a contact intensity sensor). In some embodiments, the touch-sensing component 584 is a separate component from the display 582. Additionally, the I / O section 594 can be connected to a communication unit 590 that receives 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 embodiments, input mechanism 588 is optionally a microphone. Input mechanism 588 is optionally a plurality of microphones (e.g., a microphone array).

[0179] 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 to 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 from and / or transmitted to memory 598 and / or RF circuitry (e.g., of communication unit 590) by I / O section 594.

[0180] The memory 598 of the personal electronic device 580 can 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, can cause the computer processors to perform, for example, the techniques described below, including processes 700, 900, 1100, 1300, 1500 (FIGS. 7A-7C, 9, 11, 13, and 15). A computer readable storage medium can be any medium that can tangibly contain or store computer executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some 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 can 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.

[0181] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0182] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of applications: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and - A suspended or hibernated application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.

[0183] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or deleting the application process for the application and deleting state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application is taken off the display, the first application becomes a background application.

[0184] 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.

[0185] Figures 6A-6L illustrate example techniques for processing user requests, according to some embodiments. The techniques described in these figures are used to illustrate processes described below, including the processes of Figures 7A-7C.

[0186] 6A-6L generally illustrate various scenarios in which a device, such as a smart speaker, receives user input and performs voice recognition based on the user input. If a user is identified based on the user input, the device processes one or more requests for user input based on account data associated with the identified user. Exemplary techniques for voice recognition and for configuring a device to perform voice recognition include: "Personalized Hey Siri" (Apple Machine Learning Journal, vol.1, no.9, April 2018), and ● Discussed in "Generalised Discriminative Transform via Curriculum Learning for Speaker Recognition" by E. Marchi, S. Shum, K. Hwang, S. Kajarekar, S. Sigtia, H. Richards, R. Haynes, Y. Kim, and J. Bridle, International Conference on Acoustics, Speech, and Signal Processing (ICASSP), April 2018. The contents of these publications are incorporated herein by reference in their entireties.

[0187] 6A-6B illustrate a scenario including an electronic device 600 placed on a table and a user 602 standing near the device 600. In some examples, the electronic device 600 is a speaker (e.g., a smart speaker). As shown, the user 602 provides voice input 604 (e.g., natural language speech input) to the electronic device 600 including a request for information (e.g., play classical music). In some embodiments, the voice input 604 includes a digital trigger (e.g., "Hey Assistant") that, when received by the electronic device, causes the electronic device 600 to initiate a dialogue session with the user 602. In response to the voice input 604, the electronic device 600 indicates that the device is authorized to provide the requested information and / or provides the requested information. As shown in FIG. 6B, for example, the electronic device 600 provides an output 606 indicating that the device is providing classical music (e.g., "Currently playing classical music") and provides a music output 608.

[0188] In some examples, one or more user accounts are associated with the electronic device. For example, a first user account associated with the electronic device can correspond to a first user, and a second user account associated with the electronic device can correspond to a second user. In some examples, any number of user accounts are associated with the electronic device. In other examples, up to a threshold number (e.g., five) of user accounts are associated with the electronic device. In some examples, each user account associated with the electronic device is associated with a voice profile that can be used, for example, to determine whether a user associated with the user account is speaking to the electronic device. For example, during operation, the electronic device can receive a voice input (e.g., voice input 604) and determine whether the voice input matches a voice profile of a user account associated with the electronic device. If a match exists, the electronic device determines that a user of a user account associated with the matching voice profile provided the voice input. In some examples, account data associated with the user account is updated to reflect previous use (e.g., listening history) of the electronic device (and / or other devices) by a user of the user account. In some examples, the account data of the user account can be updated based on information provided in response to a request from a user of the user account.

[0189] In some examples, the user account is a default account (e.g., the owner account). The default account can be enabled or disabled in some examples, for example, by toggling a setting on the electronic device. As an example, the electronic device can be associated with (e.g., signed in to) a default account such that requests not attributable to an identified user are processed according to the default account. (For example, if the user provides input that does not match an audio profile, the request is processed according to the default account). As an example, a user can request that the electronic device play music, and if the electronic device determines that the input comprising the request does not match the audio profile of any user account, the electronic device processes the request according to the default account. Thus, the electronic device can play music according to the account data of the default account (e.g., the listening history of the default account). In some examples, the account data associated with the default account is updated to reflect previous use of the electronic device (and / or other devices associated with the default user account). In some examples, the account data of the default account can be updated based on information provided in response to requests provided by any number of users.

[0190] In the scenario illustrated in FIGS. 6A-6B, the electronic device 600 determines that the audio input 604 does not match the audio profile of any of the user accounts. Thus, the electronic device 600 does not update the account data of any of the user accounts. However, because a default account associated with the electronic device is enabled (e.g., the account is set up), the electronic device updates the account data of the default account. As illustrated in FIG. 6B, for example, the electronic device 600 updates the listening history of the default account based on the request. In some embodiments, updating the account data in this manner can enable the electronic device to provide a more intuitive user experience. As an example, when a user requests that the electronic device perform music playback without specifying a genre or artist, the electronic device 600 can identify music for playback based on the listening history of the default account, such that the identified music corresponds appropriately with the previously requested music.

[0191] 6C-6D illustrate a scenario in which a default account associated with the electronic device is disabled (e.g., no default account is set) and the audio input 604 does not match the audio profile of any user account. As shown, in some embodiments, in response to the audio input 604, the electronic device 600 provides an output (e.g., output 606) that the electronic device is authorized to provide the requested information, and provides the requested information (e.g., music output 608) as described. Because the default account associated with the electronic device is disabled, the electronic device does not update the account data of the default account. Furthermore, because the audio input 604 does not match the audio profile of any user account, the electronic device does not update the account data of any user account. In other embodiments, if the default account associated with the electronic device is disabled and the audio input 604 does not match the audio profile of any user account, the electronic device 600 does not respond to the request or indicates to the user that it is unable to process the request. In such embodiments, the electronic device does not update the account data of any user account.

[0192] 6E-6F illustrate a scenario in which a default account associated with the electronic device is enabled and audio input 604 matches an audio profile associated with the user account of the user 602. In response to the audio input 604, the electronic device 600 provides an output (e.g., output 606) that the electronic device is authorized to provide the requested information, and provides the requested information (e.g., music output 608) as described. Because the audio input 604 matches an audio profile associated with the user account of the user 602, the electronic device updates account data for the user's 602 user account. Updating the account data in this manner may include updating a listening history for the user account. In some embodiments, the electronic device 600 updates the account data for the default account only when the audio input does not match an audio profile (unless the audio input matches the audio profile of the default account). Thus, as shown in FIGS. 6E-6F, because the audio input 604 matches an audio profile associated with the user account of the user 602, the electronic device 600 does not update the account data for the default account associated with the electronic device in response to the audio input 604.

[0193] 6G-6H illustrate a scenario in which a user 610, different from user 602, provides voice input 612 (e.g., natural language speech input) to electronic device 600, including a request for information (e.g., play jazz music). In some embodiments, the voice input 612 includes a digital trigger (e.g., "Hey Siri") that, when received by the electronic device, causes electronic device 600 to initiate a dialogue session with user 610, for example. In response to the voice input 612, electronic device 600 indicates that the device is authorized to provide the requested information and / or provides the requested information. As shown in FIG. 6G, for example, electronic device 600 provides output 614 indicating that the device is providing jazz music (e.g., "Playing jazz music now") and provides music output 616.

[0194] In the scenario illustrated in FIGS. 6G-6H, a default account associated with the electronic device is enabled and the audio input 612 matches an audio profile associated with the user account of the user 610. Because the audio input 612 matches an audio profile associated with the user account of the user 610, the electronic device updates the account data of the user account of the user 610. Updating the account data in this manner may include updating a listening history of the user account. As described, in some implementations, the electronic device 600 updates the account data of the default account only when the audio input does not match the audio profile (unless the audio input matches the audio profile of the default account). Thus, the electronic device 600 does not update the account data of the default account associated with the electronic device in response to the audio input 612.

[0195] In some examples, the electronic device receives one or more requests for private information associated with a user account. In some examples, the electronic device provides the private information of a user account only when the voice input requesting the private information matches a voice profile associated with the user account. For example, in the scenario illustrated in FIGS. 6I-6J, the voice input 618 provided by the user 630 does not match any voice profile associated with any user account. As illustrated in FIG. 6J, the voice input 618 includes a request for private information (e.g., "read my messages"), and because the voice input 618 does not match a voice profile, the electronic device 600 provides an output indicating that the device is not authorized to provide the requested information and does not provide the requested information. As illustrated in FIG. 6J, for example, in response to the voice input 618, the electronic device provides an output 620 indicating that the electronic device is not authorized to output a message to the user 602.

[0196] As another example, in the scenario shown in Figures 6K-6L, a voice input 604 provided by a user 602 matches a voice profile associated with the user account of the user 602. As shown in Figure 6L, because the voice input 622 matches the voice profile of the user account of the user 602, the electronic device 600 provides an output indicating that the device is authorized to provide the requested information and provides the requested information. As shown in Figure 6L, for example, the electronic device 600 provides an output 624 indicating that the electronic device is authorized to provide a message associated with the user account of the user 602 and provides the message.

[0197] 7A-7C illustrate a method for processing a user request using an electronic device (e.g., smart speaker, home media hub) according to some embodiments. Method 700 is performed in a device (e.g., 100, 300, 500, 580, 600) having a media output device. Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0198] As described below, the method 700 provides an intuitive way to process user requests with an electronic device. This method reduces the cognitive burden on a user to provide a request to perform a task on the electronic device, thereby creating a more efficient human-machine interface. For example, by processing a request for voice input based on whether the voice input matches a voice profile, the electronic device can intuitively and efficiently perform the task as requested. For example, matching the voice input to a user's voice profile allows the device to identify the user and then perform the task based on account data associated with the user, thereby ensuring that the task is performed according to the user's preferences and previous use of the device associated with the user. Thus, by processing a task in this manner, the electronic device is used more efficiently by reducing the number of inputs and time required for a user to operate the electronic device (e.g., by reducing user errors in operating / interacting with the device and ensuring that the device provides noticeable results), which in addition reduces power usage and improves the device's battery life.

[0199] In some embodiments, an electronic device (e.g., 600) (e.g., one or more speakers, one or more displays, one or more components connecting the device to one or more external output devices (e.g., external speakers and / or displays)) receives (702) a request (e.g., for information) determined based on audio input (e.g., 604) (e.g., via one or more microphone devices of the electronic device, via communication from another device (e.g., audio detected by the other device which forwards the request to the electronic device).

[0200] In some embodiments, in response to receiving the request (704), and in accordance with a determination that the voice input does not match a voice profile associated (e.g., via voice recognition analysis) with an (e.g., any) account (e.g., a user account used across multiple devices) associated with (e.g., registered with, authorized to operate with) the electronic device (706), the electronic device (e.g., 600) causes the media output device to output (e.g., play music) (708) the first information (e.g., 608) based on the request using a first account associated with the electronic device (e.g., the smart speaker owner's account, even if no default account has been set).

[0201] In some embodiments, in response to receiving the request, and in accordance with a determination that the voice input does not match a voice profile associated (e.g., via speech recognition analysis) with an (e.g., any) account (e.g., a user account used across multiple devices) associated with (e.g., registered with, authorized to operate with) the electronic device (706), and in accordance with settings on the electronic device being set to a first state (e.g., the first account is set as a default account), the electronic device causes account data for the first account to be updated (e.g., listening history, listening preferences) based on the request (710).

[0202] In some embodiments, in response to receiving the request, following a determination that the voice input does not match a voice profile associated (e.g., via speech recognition analysis) with an (e.g., any) account (e.g., a user account used across multiple devices) associated with (e.g., registered with, authorized to operate with) the electronic device (706), and following a setting on the electronic device being set to a second state (e.g., the first account is not set as a default account or no default account is set), the electronic device refrains from updating the account data for the first account based on the request (712).

[0203] In some embodiments, in response to receiving the request (704), and in response to determining that the voice input matches a voice profile associated with an account associated with the electronic device (714), the electronic device causes (716), by a media output device, to output the first information based on the request using the account associated with the matching voice profile.

[0204] In some embodiments, in response to receiving the request (704), and in response to determining (714) that the audio input matches an audio profile associated with an account associated with the electronic device, the electronic device causes (718) account data for the account associated with the matching audio profile to be updated (e.g., updating listening history, listening preferences) based on the request.

[0205] In some embodiments, the electronic device receives (720) a second request (e.g., for information) determined based on a second voice input (e.g., 610) (e.g., via one or more microphone devices of the electronic device, via a communication from another electronic device (e.g., voice detected by the other device forwarding the request to the electronic device). In some embodiments, the second voice input matches (722) a voice profile associated with a second account associated with the electronic device. In some embodiments, the first account is distinct from the second account (724). In some embodiments, in response to receiving (726) the second request, and following a determination that the second voice input matches a second voice profile associated (e.g., via voice recognition analysis) with the second account (e.g., a user account used across multiple devices), the electronic device causes (728) a media output device to output (e.g., play music) the second information (e.g., 616) based on the second request using the second account associated with the electronic device. In some embodiments, in response to receiving the second request (726), and in accordance with determining that the second voice input matches a second voice profile associated (e.g., via speech recognition analysis) with a second account (e.g., a user account used across multiple devices), the electronic device causes account data for the second account to be updated (e.g., listening history, listening preferences) based on the second request (730).

[0206] In some embodiments, causing the information to be output using the respective account (e.g., first account, second account) includes accessing the media using credentials associated with the respective account (e.g., username, password, token, etc.).

[0207] In some embodiments, updating the account data for each account includes updating a media profile (e.g., media history, preferred (e.g., favorited) media, non-preferred (e.g., disliked) media, frequently played media) associated with each account. Updating the media profile in this manner ensures that user preferences and previous usage of the device associated with the user are current for one or more media applications employed by the user. Thus, the electronic device is used more efficiently by reducing the number of inputs and time required for a user to operate the electronic device (e.g., by reducing user errors in operating / interacting with the device and ensuring that the device provides noticeable results) by processing the electronic device and requests, which in turn reduces power usage and improves the battery life of the device.

[0208] In some embodiments, the electronic device receives (732) a third request (e.g., for information) determined based on a third voice input (e.g., 618, 622) (e.g., via one or more microphone devices of the electronic device, via a communication from another electronic device (e.g., voice detected by the other device forwarding the request to the electronic device). In some embodiments, the third request is a request to output (734) private information (e.g., a text message, a calendar item, an email) associated with a third account (e.g., the first account, the second account, or another account associated with the electronic device). In some embodiments, in response to receiving the third request (736), and following a determination (738) that the third voice input (e.g., 622) matches a third voice profile associated (e.g., via voice recognition analysis) with a third account (e.g., a user account used across multiple devices), the electronic device causes the media output device to output (e.g., 624) private information based on the third request (e.g., dictate a text message, dictate a calendar entry, dictate an email) (740) using the third account. In some embodiments, in response to receiving the third request (736), and following a determination (742) that the third voice input (e.g., 618) does not match a third voice profile associated (e.g., via voice recognition analysis) with a third account (e.g., a user account used across multiple devices), the electronic device refrains from causing the media output device to output private information (e.g., refrain from dictating text messages, refrain from dictating calendar entries, refrain from dictating emails) based on the third request using the third account associated with the electronic device (744). For example, a request for private information with a voice input request that does not match a voice profile associated with the corresponding account, as opposed to a request for non-private information, causes the request to not be able to output the private information.For example, a request by a person who is not the account owner will not cause the device to output private information associated with the account. Selective output of private information in this manner allows the user device to provide information only when requested by a user authorized to receive the requested information. Thus, processing the electronic device and request may result in safer use of the electronic device while reducing the number of inputs and time required for a user to operate the electronic device (e.g., by reducing user errors in operating / interacting with the device), in addition to reducing power usage and improving the battery life of the device.

[0209] It should be noted that the details of the processes (e.g., FIGS. 7A-7C) described above with respect to method 700 are also applicable in an analogous manner to the methods described below. For example, method 900 optionally includes one or more of the characteristics of the various methods described below with reference to method 900. For example, as described in method 900, when a personal request feature is enabled, the electronic device can selectively execute user-specific requests, as described in method 700. For the sake of brevity, these details will not be repeated below.

[0210] 8A-8AB show example user interfaces for configuring a user account, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0211] 8A-8M may be employed to perform a configuration process that allows a user to configure one or more features provided by one or more devices. The devices providing the configurable features include, but are not limited to, the electronic device 800, a second device such as a smart speaker, and / or a third device such as a home media hub.

[0212] During the configuration process, for example, a voice recognition feature can be enabled in the user account to configure the external device (e.g., smart speaker, home media hub) to recognize the user's voice. As described with reference to FIGS. 6A-6L, the voice profile of the user account can be used to identify the user. Furthermore, during the configuration process, a personal request feature can be enabled for the user account such that the external device performs user-specific tasks in response to requests provided by the user. Thus, in combination with the voice recognition feature, the personal request feature can be enabled to cause the external device to identify the user in response to speech input (e.g., by matching the voice profile of the user's user account) and perform one or more tasks specific to the user (e.g., play the user's music).

[0213] As another example, during a configuration process, a profile feature can be enabled in a user account to configure an external device (e.g., a home media hub) to share content of the user account with users of one or more other user accounts. In some examples, the same external device is configured to support each of the voice recognition feature, the personal request feature, and the profile feature. In some examples, multiple external devices are configured to each support one or more features. As an example, a first external device can be configured to support the voice recognition feature and the personal request feature, and a second external device can be configured to support the profile feature.

[0214] As described in more detail below, in some examples, the configuration process is performed using a home control application. The home control application may be an application used to manage (e.g., configure) a set of devices (e.g., external devices) associated with a particular location (e.g., "123 Main St."). Examples of locations include, but are not limited to, addresses, places, buildings, businesses, environments (e.g., backyards, automobiles, porches), and the like. In some examples, a location includes multiple designated areas within or associated with a location, such as rooms within a location. An example of a home control application is "Home" (by Apple Inc., Cupertino, California, USA).

[0215] In some embodiments, one or more user accounts are associated with a location of the home control application. In some embodiments, a user account is associated with a location when it is included in a location profile of the home control application for that location. In some embodiments, a location profile is information that describes various aspects of a location, including devices associated with the location, user accounts associated with the devices, and / or permissions (e.g., privileges) of the user accounts to control and / or configure devices associated with the location.

[0216] In some examples, user accounts may be assigned permissions using a home control application. By way of example, using the home control application, a first user account may be an administrator account that is assigned administrator permissions. In some examples, a user with an administrator account has permissions to configure devices associated with a location and / or to configure one or more settings for each user account in a location profile. A second user account may be a non-administrator account that is not assigned administrator permissions. In some examples, a user with a non-administrator account has permissions to configure one or more settings of the second user account.

[0217] A user may use a configuration process to configure features of a user account to enable the features on one or more devices that support the features. In some embodiments, each of multiple users (e.g., users with user accounts that belong to the same location profile) may configure features of their respective user accounts to enable a respective set of features on one or more devices. Thus, one or more devices may support features for any number of users. As an example, a device may support a voice recognition feature and personal requests for a first user, and only a voice recognition feature for a second user. As another example, a device may support a profile feature for a first user, but not for a second user.

[0218] In some embodiments, the features are configured at the account level. For example, a voice recognition feature, when enabled, may enable the voice recognition feature for all devices associated with a user account. In some embodiments, the features are configured at the device level. For example, a personal requests feature may be enabled (or disabled) individually for each device associated with a user account.

[0219] 8A illustrates an indication interface 803 displayed on a display device 802 of an electronic device 800. The indication interface 803 includes a continuation affordance 805 and indicators 804A-804E. Each of the indicators 804A-804E can indicate one or more new and / or updated features of a home control application (e.g., a first party's home control application).

[0220] While displaying the indication interface 803, the electronic device 800 detects a selection of a continuation affordance 805. As shown in FIG. 8A, the selection of the continuation affordance 805 is, optionally, a tap gesture 806. In some examples, the selection of the continuation affordance 805 initiates a configuration process (e.g., of a home control application) for a user account of a user of the electronic device. As an example, the configuration process may be used to configure (e.g., enable) a voice recognition feature for the user account. As another example, the configuration process may be used to configure (e.g., enable) a personal request feature for the user account. In some examples, the personal request feature is enabled for the user account only if the voice recognition feature is enabled for the user account. As another example, the configuration process may be used to configure (e.g., enable) a profile feature for the user account.

[0221] In response to a selection of the continuation affordance 805, the electronic device 800 determines whether an external device (e.g., a smart speaker) associated with the electronic device 800 is available to support the voice recognition functionality. In some examples, a device is associated with the electronic device if the electronic device 800 and each of the external device are associated with the same user account. The electronic device 800 can determine, for example, whether the external device is already configured to recognize a threshold number of voices and / or whether the current language of the external device supports the voice recognition functionality hub.

[0222] If the electronic device determines that the external device is available to support the voice recognition feature, the electronic device displays a configuration interface 810 on the display 802 as shown in FIG. 8B (e.g., replaces the display of the update indication interface 803 with the configuration interface 810). The configuration interface 810 includes an indicator 811, a continue affordance 812, and a cancel affordance 816. The indicator 811 may optionally indicate that the voice recognition feature can be configured for the user account, for example, to have the external device identify the user's voice (e.g., using a voice profile of the user's user account). Selection of the cancel affordance 816 causes the electronic device to not enable (e.g., disable) the voice recognition feature for the user account and / or to cease displaying the configuration interface 810.

[0223] While displaying the configuration interface 810, the electronic device 800 detects a selection of a continuation affordance 812. As shown in FIG. 8B, the selection of the continuation affordance 812 is, optionally, a tap gesture 814. In response to the selection of the continuation affordance 812, the electronic device 800 configures (e.g., enables) a voice recognition feature for the user account (recall that in some embodiments, the voice recognition feature is enabled or disabled for all devices associated with the user account). Thus, the external device can subsequently identify the user in response to speech input provided by the user. In further response to the selection of the continuation affordance 812, the electronic device displays a configuration interface 820 on the display 802 (e.g., replaces the display of the configuration interface 810 with the configuration interface 820), as shown in FIG. 8C.

[0224] The configuration interface 820 includes an indicator 821, a customization affordance 822, and a feature enable affordance 823. The indicator 821 indicates that the personal request feature can be configured for the user's user account on the external device. In some examples, when the personal request feature is enabled on the external device, the external device is configured to respond to user-specific requests provided by the user when the user's device (e.g., external device 800) is in external proximity and / or when the user's voice input matches the user's voice profile. As described in more detail below with respect to FIG. 8K, the customization affordance 822, when selected, causes the electronic device to display one or more editable options for configuring the personal request feature for the user account.

[0225] While displaying the configuration interface 820, the electronic device 800 detects a selection of a function-enablement affordance 823. As shown in FIGURE 8C, the selection of the function-enablement affordance 823 is, optionally, a tap gesture 824. In response to the selection of the function-enablement affordance 823, the electronic device configures (e.g., enables) a personal requested function on the user account for the external device.

[0226] Further responsive to the selection of the continue affordance 823, the electronic device 800 determines whether an external device (e.g., a home media hub) associated with the electronic device 800 is enabled to support the profile feature. If so, the electronic device 800 displays a configuration interface 830 on the display 802 (e.g., replaces the display of the update indication interface 810 with the configuration interface 830), as shown in FIG. 8D . The configuration interface 830 includes an indicator 831, a disable affordance 832, and a feature enable affordance 833. The indicator 831 indicates that the profile feature may be enabled for a user account on an external device that supports the profile feature. In some embodiments, enabling the profile feature in this manner allows media content associated with the user account to be accessed, for example, by one or more other users using the home media hub. Selection of the feature enable affordance 833 causes the electronic device to enable the profile feature for the user account, and selection of the disable affordance 832 causes the electronic device to not enable (e.g., disable) the profile for the user account. In response to selecting either the feature enable affordance 833 or the disable affordance 832, the electronic device completes the configuration process. In some examples, after (e.g., in response to) completing the configuration process, the electronic device displays a notification indicating that the configuration process is complete, such as notification 851B in lock screen interface 850B ( FIG. 8AA ). In some examples, the notification is displayed only if one or more particular features (e.g., a voice recognition feature and / or a personal request feature) were enabled during the configuration process.

[0227] As described, in some embodiments, before displaying the configuration interface 810, the electronic device 800 determines whether an external device associated with the electronic device 800 (e.g., a smart speaker, a home media hub) is available to support the voice recognition functionality. If an external device is not available, the electronic device 800 refrains from displaying the configuration interface 810 and the configuration interface 820. As described, in some embodiments, before displaying the configuration interface 830, the electronic device 800 determines whether an external device associated with the electronic device 800 (e.g., a home media hub) is available to support the profile functionality. If an external device is not available to support the profile functionality, the electronic device refrains from displaying the configuration interface 830.

[0228] In some examples, before enabling the voice recognition feature, if the electronic device determines that the external device already supports the voice recognition feature for a threshold number of users (e.g., a non-zero threshold), the electronic device 800 displays a configuration interface 840 on the display 802 (e.g., replaces the display of the update indication interface 803 with the configuration interface 840), as shown in FIG. 8E. The configuration interface 840 includes an indicator 841 and a continuation affordance 842. The indicator 841 indicates that the external device has reached the threshold number of users for the voice recognition feature and that the external device cannot identify additional voices. The continuation affordance 842, when selected, causes the electronic device to not enable (e.g., disable) the voice recognition feature for the user account.

[0229] In some examples, before enabling the voice recognition feature, if the electronic device 800 determines that the current language of the external device does not support the voice recognition feature, the electronic device 800 displays a configuration interface 850 on the display 802 as shown in FIG. 8F (e.g., replaces the display of the update indication interface 803 with the configuration interface 850). The configuration interface 830 includes an indicator 851, a continuation affordance 852, and a language affordance 853. The indicator 851 indicates that the external device cannot support the voice recognition feature using the current language of the external device, and, optionally, the electronic device 800 notifies the user when the current language becomes supported. Once the language is supported, the electronic device 800 can provide a notification to the user's electronic device, such as, for example, notification 861B in the lock screen interface 860B (FIG. 8AB). The continuation affordance 852, when selected, causes the electronic device 800 not to enable (e.g., disable) the voice recognition feature for the user's account.

[0230] In some examples, the user can change the language of the external device to a language supported by the voice recognition capability. As an example, while displaying the configuration interface 850, the electronic device 800 detects a selection of a language affordance 853. As shown in FIG. 8F, the selection of the language affordance 853 is, optionally, a tap gesture 854. In response to the selection of the language affordance 853, the electronic device 800 displays, on the display 802, a language interface 860 (e.g., replaces the display of the update indication interface 850 with the language interface 860), as shown in FIG. 8G.

[0231] Language interface 860 includes language elements 861A-861C, keep affordance 863, and change affordance 864. Keep affordance 863, when selected, causes the electronic device to keep the current language of the external device and not enable (e.g., disable) the voice recognition feature for the user account.

[0232] In some examples, each of the language elements 861A-861C corresponds to a respective language. By way of example, language element 861A corresponds to English (US), language element 861B corresponds to English (UK), and language element 861C corresponds to Spanish. In some examples, a user may select a language element to choose a new language for the external device. As shown in FIG. 8G, for example, a user may select language element 861A (e.g., by providing user input at a location on display 802 corresponding to language element 861A) to specify English (US) as the language of the external device. The selected language may be identified by selection indicator 862. After a new language is selected for the external device, electronic device 800 detects a selection (e.g., input 865) of change affordance 864 confirming the selection of the new language.

[0233] In some examples, electronic device 800 determines that multiple external devices associated with electronic device 800 are available to support voice recognition functionality. In some examples, if electronic device 800 determines that multiple external devices are available and that at least two of the external devices have different current languages, electronic device 800 displays configuration interface 870 on display 802 (e.g., replaces the display of configuration interface 810 with configuration interface 870), as shown in FIG.

[0234] Configuration interface 870 includes change affordance 871, change affordance 872, and keep affordance 873. Keep affordance 873, when selected, causes the electronic device to maintain the current language of the external device and not enable (e.g., disable) the voice recognition feature for the user account.

[0235] When selected, change affordance 872 causes electronic device 800 to display an interface that allows the user to select a subset of available external devices and change the language for the selected subset of external devices. For example, while displaying configuration interface 870, electronic device 800 detects selection of change affordance 872. As shown in FIG. 8H, selection of continue affordance 872 is, optionally, a tap gesture 874. In response to selection of change affordance 872, electronic device 800 displays configuration interface 880 on display 802 (e.g., replaces display of update indication interface 870 with configuration interface 880), as shown in FIG. 8I.

[0236] The configuration interface 880 includes device elements 881A-881C, each of which may correspond to a respective external device available to support the voice recognition functionality. By way of example, device element 881A may be associated with external device "Bedroom," device element 881B may be associated with external device "Living Room," and device element 881C may be associated with external device "Kitchen." While displaying the configuration interface 880, the electronic device receives one or more inputs selecting a subset of the external devices. In some embodiments, the selected external devices are indicated by a selection indicator (e.g., selection indicators 882A, 882B).

[0237] The configuration interface 880 further includes a cancel affordance 883 and a continue affordance 884. Selecting the cancel affordance 883 causes the electronic device to not enable (e.g., disable) the voice recognition feature for the user account and / or to cease displaying the configuration interface 880.

[0238] While displaying configuration interface 880, electronic device 800 detects a selection of continuation affordance 884. As shown in FIG. 8I , the selection of continuation affordance 884 is, optionally, a tap gesture 885. In response to the selection of continuation affordance 884, electronic device 800 displays on display 802 one or more configuration interfaces (e.g., configuration interface 860) that allow the user to select a language for each of the selected external devices (e.g., replacing the display of update indication interface 880 with the configuration interface).

[0239] In some examples, a user can selectively enable the personal request feature on each external device on which the voice recognition feature is enabled. For example, while displaying configuration interface 820 (FIG. 8C), electronic device 800 detects a selection of customization affordance 822. In some examples, the selection of customization affordance 822 causes electronic device 800 to display configuration interface 890 on display 802 (e.g., replacing the display of configuration interface 820 with configuration interface 890), as shown in FIG.

[0240] Configuration interface 800A includes device elements 892A-C, each of which may correspond to an external device. As an example, device element 891A may be associated with external device "Bedroom," device element 891B may be associated with external device "Kitchen," and device element 891C may be associated with external device "Living Room." Each of device elements 891A-C may include a respective toggle affordance. For example, device element 891A may include toggle affordance 892A, device element 891B may include toggle affordance 892B, and device element 891C may include toggle affordance 892C. In some examples, each of the toggle affordances represents a parameter indicating whether a personal request feature for the user account is enabled on the respective external device.

[0241] Configuration interface 890 further includes a cancel affordance 893 and a continue affordance 894. Selection of the cancel affordance 893 causes the electronic device 800 to not enable (e.g., disable) the voice recognition feature for the user account (e.g., for any of the enumerated external devices) and / or to cease displaying the configuration interface 890. Selection of the continue affordance 894 (e.g., using input 895) causes the electronic device to enable the personal request feature for the user account on each of the selected external devices.

[0242] In some examples, the personal request feature is enabled only if the voice recognition feature is enabled. Thus, during the configuration process, if the user selects not to enable (e.g., disable) the voice recognition feature for the user account, the electronic device 800 may omit displaying the configuration interface 820 (and / or one or more other interfaces directed to configure the personal request feature). In some examples, the user may have enabled the personal request feature before beginning the configuration process, or may indicate an intent not to enable voice recognition after indicating an intent to enable the personal request feature (e.g., selecting affordance 894 in FIG. 8J after selecting affordance 823 in FIG. 8B). If so, the electronic device 800 may request the user to disable the personal request feature. In some examples, the electronic device 800 prompts the user to indicate whether the user intended to disable the personal request feature. By way of example, referring to FIG. 8K, the electronic device 800 may optionally display a confirmation interface 800A. Confirmation interface 800A includes inquiry 801A, confirmation affordance 802A, and resume affordance 803A. Enquiry 801A is an inquiry that requests the user to confirm that the user intends to disable the personal request functionality. Confirmation affordance 802A, when selected, causes the electronic device to disable the personal request functionality. Resume affordance 803A, when selected, signals to the electronic device that the user does not intend to disable the personal request functionality, and then electronic device 800 stops displaying confirmation interface 800A (and optionally, displaying one or more user interfaces that allow the user to enable the voice recognition functionality, as described).

[0243] In some examples, the confirmation interface 800A is overlaid on one or more displayed user interfaces. For example, as shown in FIGURE 8K, the confirmation interface 800A is overlaid on the configuration interface 890. It will be appreciated that the confirmation interface 800A may be displayed at any point during the configuration process where the user indicates an intent to proceed without enabling the voice recognition feature while the personal request feature is enabled.

[0244] In some embodiments, enabling the voice recognition feature requires that the digital assistant of the electronic device be trained based on the user's voice. For example, during the configuration process, the electronic device 800 can determine whether the digital assistant of the electronic device has been trained based on the user's voice. Referring to FIG. 8L, if the digital assistant of the electronic device 800 has not been trained based on the user's voice, the electronic device displays the configuration interface 810A.

[0245] In some examples, the configuration interface 810A includes instructions 812A that indicate one or more actions of a voice training operation for a digital assistant of the electronic device 800. The instructions 812A can prompt the user to provide a set of speech inputs, for example, in which the user speaks (e.g., repeats) a word or phrase (e.g., a digital trigger such as "Hey Assistant").

[0246] The configuration interface 810A further includes a cancel affordance 814A and a continue affordance 816A. Selection of the cancel affordance 814A causes the electronic device to not enable (e.g., disable) the voice recognition feature for the user account and / or to stop displaying the configuration interface 810A. Selection of the continue affordance 814A causes the electronic device to initiate a voice training operation in which the digital assistant is trained using one or more speech inputs provided by the user. In some embodiments, training the digital assistant in this manner includes generating a model (e.g., a speech model) based on a set of speech inputs provided by the user during the voice training operation.

[0247] In some examples, the electronic device provides voice identification data to one or more external devices (e.g., each external device for which the voice identification feature is enabled for the user account). The external device can then use the voice identification data to identify the user in response to the received speech input. The voice identification data can be used, for example, to generate and / or update a voice profile of the user for use on the external device.

[0248] In some embodiments, the electronic device determines whether the language of the digital assistant of the electronic device is the same as the language of the external device. Referring to FIG. 8M, if the language of the digital assistant of the electronic device is not the same as the language of the external device, the electronic device displays the configuration interface 820A.

[0249] The configuration interface 820A includes an indicator 821A, a change affordance 822A, and a cancel affordance 823A. In some examples, selection of the change affordance 822A causes the electronic device to display one or more user interfaces that allow the user to change the language of the digital assistant to the language of the external device, thereby enabling the voice recognition functionality. Selection of the cancel affordance 823A causes the electronic device to not enable (e.g., disable) the voice recognition functionality and / or to stop displaying the configuration interface 820A.

[0250] Descriptions are provided herein regarding electronic device 800 being used during a configuration process to selectively enable functionality supported by one or more external devices (e.g., devices associated with the electronic device). It will be appreciated that in some embodiments, electronic device 800 may support functionality such that a configuration process may be used to configure electronic device 800. By way of example, electronic device may be configured to support voice recognition functionality and personal request functionality in addition to or as an alternative to external devices.

[0251] 8N, the device 800 displays a home interface 830A of a home control application. As shown, the home interface 830A includes an indicator 833A that indicates a location ("123 Main St."). In some embodiments, the indicator 833A includes text. In some embodiments, the indicator 833A additionally or alternatively includes an image or other identifying information.

[0252] The home interface 830A further includes a home affordance 834A that, when selected, causes the electronic device 800 to display an interface through which a user can view and / or edit settings for a user account of a location profile (e.g., a user account associated with a location). For example, while displaying the configuration interface 830A, the electronic device 800 detects a selection of the home affordance 834A. As shown in FIG. 8O, the selection of the home affordance 834A is, optionally, a tap gesture 835A. In response to the selection of the home affordance 834A, the electronic device 800 displays the home interface 840A on the display 802 (e.g., replaces the display of the home interface 830A with the home interface 840A), as shown in FIG. 8O.

[0253] Home interface 840A corresponds to user affordances 841A, each of which corresponds to a user account (and in turn, a user of the user account). By way of example, user affordance 841AA corresponds to a user account for user John Appleseed ("John A"), and user affordance 841AB corresponds to a user account for user Jane Appleseed ("Jane A"). Home interface 840A further includes invite affordance 842A that, when selected, allows the user to invite other users (e.g., personal contacts) to the location profile, as described in further detail below. Inviting other users in this manner, as described in further detail below, may include providing notifications to each of the users that may be used to respectively add the user's user account to the location profile.

[0254] While displaying home interface 840A, electronic device 800 detects a selection of user affordance 841AA. As shown in FIG. 8O, the selection of user affordance 841AA is, optionally, a tap gesture 843A. In some examples, in response to the selection of user affordance 841AB, electronic device 800 displays user account interface 850A for user John Appleseed on display 802 (e.g., replaces the display of home interface 840A with user account interface 850A), as shown in FIG. 8P (recall that selected user affordance 841AA corresponds to user John Appleseed).

[0255] User account interface 850A includes a user indicator 851A, a user identification 852A, a voice capabilities portion 853A, a profile portion 854A, a playback portion 855A, and an authorization portion 856A. User indicator 851A indicates the name of a user associated with the user account for user account interface 850A. User identification 852A indicates information associated with the user (e.g., the user's email address). In some embodiments, user identification 852A serves as a unique identifier for the user account.

[0256] The voice feature portion 853A includes a voice recognition element 853AA and a personal request affordance 853AB. The voice recognition element 853AA includes a toggle affordance that represents a parameter indicating whether the voice recognition feature is enabled for the user account. The personal request affordance 853AB, when selected, causes the electronic device 800 to display one or more user interfaces (e.g., interface 1070 of FIG. 10H ) through which the user can view and / or adjust one or more settings associated with the personal request feature for the user account (e.g., enabling the personal request feature for the user account on one or more devices).

[0257] The profile portion 854A includes a profile affordance 854AA that, when selected, causes the electronic device 800 to display one or more user interfaces (e.g., interface 1080 of FIG. 10I) through which a user can view and / or adjust one or more settings associated with a profile feature on the device (e.g., a home media hub). The playback portion 855A includes a toggle affordance representing a parameter indicating whether the user's listening history has been updated in response to a user request, e.g., as described with reference to FIGS. 6A-6L. The permissions portion 856A includes a remote access affordance 856AA that, when selected, causes the electronic device 800 to display one or more user interfaces (e.g., interface 1090 of FIG. 10J) through which a user can view and / or adjust one or more settings associated with remote access of one or more devices associated with the location.

[0258] In some examples, a user may wish to switch between user accounts. For example, while the user is signed in to a first user account on the electronic device, the user may prefer to sign in to a second user account on the electronic device, e.g., to view content associated with the second user account. FIGS. 8Q-8U show user interfaces for a process in which, in response to the user signing in to the second user account, the electronic device prompts the user to add the second user account to a location profile (and, optionally, remove the first user account from the location profile) such that the same user account is used consistently across the user's devices (e.g., electronic device 800 and one or more external devices).

[0259] FIG. 8Q illustrates a user account interface 860A displayed on the display device 802 of the electronic device 800. In some embodiments, the user account interface 860A is a user interface of a settings application of the electronic device 800. The user account interface 860A includes a user indicator 861A, a user identification 862A, an account affordance 863A, and an option affordance 864A. The user indicator 861A indicates the name of a user associated with the user account for the user account interface 860A. The user identification 862A indicates information associated with the user account (e.g., the email address of the user account). In some embodiments, the user identification 862A serves as a unique identifier for the user account. The account affordance 863A, when selected, causes the electronic device to display one of a respective set of user interfaces that allow the user to view and / or edit user-specific (e.g., private) information of the account. As an example, the user may change the name of the user account, the password of the user account, and / or the payment method of a transaction made belonging to the user account.

[0260] When selected, option affordance 864A causes electronic device 800 to display a respective set of user interfaces through which the user can view and / or edit various settings associated with the user account. The user can select option affordance 865A, for example, to adjust various signs for the settings associated with the user account. By way of example, and referring to FIG. 8Q, while displaying user account interface 860A, electronic device 800 detects selection of user affordance 865A. As shown in FIG. 8Q, the selection of user affordance 865A is, optionally, a tap gesture 866A. In some embodiments, in response to the selection of user affordance 865A, electronic device 800 displays user account interface 870A on display 802 (e.g., replacing the display of home interface 840A with user account interface 870A), as shown in FIG. 8R. In some embodiments, user account interface 870A is overlaid on user account interface 860A.

[0261] User account interface 870A includes a view affordance 871A, a sign out affordance 872A, a forgot password affordance 873A, and a cancel affordance 874A. When selected, view affordance 871A causes electronic device 800 to display a user interface including additional information about the user account. When selected, forgot password affordance 873A causes electronic device 800 to initiate a password recovery operation so that the user can change and / or retrieve the password for the user account. When selected, cancel affordance 874A causes electronic device 800 to stop displaying user account interface 870A, and optionally re-display user account interface 870 as shown in FIG. 8R.

[0262] Sign-out affordance 872A, when selected, causes a user to sign out of a first user account (e.g., "j.appleseed@email.com") and, optionally, prompts the user to sign in to a second user account (e.g., "john_a@email.com"). For example, while displaying user account interface 870A, the electronic device detects a selection of user affordance 872A. As shown in FIG. 8R, the selection of user affordance 865A is, optionally, a tap gesture 875A. In some examples, in response to the selection of user affordance 872A, electronic device 800 displays user account interface 880A on display 802 (e.g., replaces the display of home interface 870A with user account interface 880A), as shown in FIG. 8S. In some examples, user account interface 880A is superimposed on user account interface 860A.

[0263] User account interface 880A includes username field 881A, password field 882A, cancel affordance 883A, and sign-in affordance 884A. In some examples, user account interface 880 functions as a prompt for a user to sign in to a user account on electronic device 800. Thus, a user can provide a user account username and password in fields 881A and 882A, respectively. Sign-in affordance 885A, when selected, causes the electronic device to submit the account username and password as the account credentials. Selection cancel affordance 883A, when selected, causes the electronic device 800 to stop displaying user account interface 870A and, optionally, re-display user account interface 860A, as shown in FIG. 8Q.

[0264] As an example, while displaying user account interface 880A, the electronic device detects a selection within sign-in affordance 884A. As shown in FIG. 8S, the selection of sign-in affordance 884A is, optionally, a tap gesture 885A. In some examples, in response to the selection of sign-in affordance 884A, electronic device 800 initiates a sign-in operation in which the user is signed into a second user account (e.g., "john_a@email.com") and displays user account interface 890A on display 802 (e.g., replacing the display of home interface 880A with user account interface 890A), as shown in FIG. 8T.

[0265] In some examples, before performing the sign-in operation (e.g., in response to a selection of a user affordance), the electronic device 800 determines whether the second user account (e.g., john_a@email.com) is the same user account as the user account in the location profile of the home control application. If the user accounts are not the same, the electronic device 800 displays a sign-on interface 891A, as shown in FIG. 8T. The sign-on interface 891A, in some examples, is overlaid on the user account interface 890A.

[0266] Sign-on interface 891A includes sign-on affordance 892A, device affordance 893A, and cancel affordance 894A. Selection of device affordance 893A causes the electronic device to perform a sign-in operation for a user account only on electronic device 800. Selection of cancel affordance 894A causes electronic device 800 to terminate the sign-in operation such that the user remains signed in to a first user account (e.g., "j.appleseed@apple.com") or remains signed out of all user accounts.

[0267] Selection of sign-on affordance 892 causes the electronic device to perform a sign-in operation for a user account on the electronic device and an additional sign-in operation to add a second user account to the location profile. As an example, while displaying sign-on interface 891A, electronic device 800 detects selection of sign-on affordance 892A. As shown in FIG. 8T, selection of sign-on affordance 892A is, optionally, a tap gesture 895A. In response to the selection on sign-on affordance 892A, electronic device 800 adds the user account (e.g., user account "john_a@email.com") to the location profile, as shown in user account interface 800B (FIG. 8U) of the home control application.

[0268] 8V-8Z show user interfaces for a process by which a user account may be added to a location profile for a device location. FIGURE 8V shows a settings interface 810B for an external device associated with a location and user account (e.g., user account "jane.applewood").

[0269] In some examples, a device associated with a location is associated with a user account that is not included in a location profile for that location. Because the user account is not included in the location profile, when viewing the settings interface 810B of the device, the electronic device displays an account interface 811B within the settings interface 810B. The account 811B includes an invitation affordance 812B, a default affordance 813B, and a sign-out affordance 814B. The invitation affordance 812B, when selected, causes the electronic device to provide an invitation in which the invited user can choose to add their user account to the location profile. As an example, while displaying the settings interface 810B, the electronic device 800 detects a selection of the invitation affordance 812B. As shown in FIG. 8V, the selection of the invitation affordance 812B is, optionally, a tap gesture 815B. In response to the selection of the invitation affordance 812B, the electronic device provides a notification, such as notification 1241 (FIG. 12F) in the lock screen interface 1240, and the invited user can accept to add their user account to the location profile. The sign-out affordance 814B, when selected, causes the electronic device to sign out the user account from the device such that the device is no longer associated with the user account.

[0270] 8W , in some examples, while displaying the settings interface 810B, the electronic device 800 detects a selection of a default affordance 813B. As shown in FIG. 8W , the selection of the default affordance 813B is, optionally, a tap gesture 815B. In response to the selection of the invite affordance 812B, the electronic device 800 assigns the user account as a default account for the device. As described, requests subsequently provided to the device that do not belong to a particular user are processed according to the default account.

[0271] FIG. 8X illustrates a settings interface 820B for a device associated with the location. The settings interface 820B includes an account affordance 821B that, when selected, causes the electronic device 800 to display one or more user interfaces through which a user can view and / or set a default user account for the device. By way of example, while displaying the settings interface 820B, the electronic device 800 detects a selection of the account affordance 821B. As shown in FIG. 8X, the selection of the account affordance 821B is, optionally, a tap gesture 822B. In response to the selection of the account affordance 821B, the electronic device 800 displays a sign-on interface 830B on the display 802 (e.g., replaces the display of the settings interface 821B with the sign-on interface 830B), as shown in FIG. 8Y.

[0272] The sign-on interface 810 includes a username field 831B, a password field 832B, a cancel affordance 834B, and a sign-in affordance 833B. The sign-in affordance 833B, when selected, causes the electronic device to submit the account username and password as the user account credentials. The cancel affordance 834B, when selected, causes the electronic device 800 to stop displaying on the sign-on interface 830B and, optionally, re-display the settings interface 820B.

[0273] In an example operation, while displaying user account interface 880A, the electronic device detects a selection of sign-in affordance 834B. As shown in FIGURE 8Y, the selection of sign-in affordance 834B is, optionally, a tap gesture 835B. In some examples, in response to the selection of sign-in affordance 834B, the electronic device 800 initiates a sign-in operation in which the user signs in to the specified user account and sets the user account as the device's default account, as shown in interface 840B of FIGURE 8Z.

[0274] 9 is a flow diagram illustrating a method for configuring a user account using an electronic device (e.g., a smartphone, a tablet computer) according to some embodiments. Method 900 is performed on a device (e.g., 100, 300, 500, 580, 600) having a display device and one or more input devices. Some operations of method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0275] As described below, the method 900 provides an intuitive way to configure a user account. This method reduces the cognitive burden on a user to configure a user account, thereby creating a more efficient human-machine interface. As an example, by detecting devices that support a function and displaying a prompt to configure the function if one or more devices that support the function are detected, the user can efficiently and intuitively perform the configuration operation of the function. For example, by first detecting devices that support the function, it ensures that devices that support the function are available before starting the configuration operation. This then reduces the number of inputs and time required for a user to operate an electronic device (e.g., by assisting the user to provide appropriate inputs and reducing user errors when operating / interacting with the device), and further reduces power usage and improves the battery life of the device.

[0276] In some embodiments, an electronic device (e.g., a first device) (e.g., 800) detects (902) that one or more devices (e.g., smart devices) associated with the first device (e.g., associated with a user account of the first device) support a respective feature (e.g., a voice recognition feature).

[0277] In some embodiments, the respective function is a voice recognition function. In some embodiments, the electronic device (e.g., 800) causes (e.g., during a configuration process to configure the respective function, after completion of the configuration process (e.g., the respective function is enabled)) voice recognition data (e.g., voice profile, received voice command) to be transmitted to one or more of the one or more devices (e.g., transmitted by the first device, transmitted by a device other than the first device). By transmitting the voice data in this manner, the device can use the voice data to compare the voice input received by the device and accurately determine whether the voice profile of the user account matches the voice input. Matching the voice input in this manner ensures that the device performs tasks according to the user preferences and previous use of the device. This then reduces the number of inputs and time required for a user to operate the electronic device (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device, reducing user errors, and ensuring that the device returns significant results), as well as reducing power usage and improving the battery life of the device.

[0278] In some embodiments, pursuant to a determination that a set of criteria is met (904), including criteria that are met when the one or more devices support the respective functionality, the electronic device displays (906) on the display device a prompt (e.g., 803, 810, 820, 830) to configure the respective functionality of the one or more devices (e.g., displaying an interface during a configuration process (e.g., during an initial setup process for a voice command process), displaying a banner, notification, or pop-up message while not in the configuration process).

[0279] In some embodiments, pursuant to a determination that a set of criteria is met (904), including criteria that are met when the one or more devices support the respective functionality, the electronic device receives (908) one or more sets of inputs (e.g., 806, 816, 824, 834) via one or more input devices while displaying a prompt to configure the respective functionality of the one or more devices.

[0280] In some embodiments, pursuant to determining that a set of criteria are met (904), including criteria that are met when one or more devices support the respective feature, and in response to receiving a set of one or more inputs, the electronic device performs (910) a configuration action associated with the respective feature (e.g., displaying the next interface (e.g., if “Continue” is selected), disabling the feature (e.g., if “Don't Recognize” or “No” is selected)).

[0281] In some embodiments, performing the configuration operation includes initiating (912) a configuration process (e.g., initiated in response to user input (e.g., selecting “continue”) while a prompt is displayed) to configure the respective features of the one or more devices. In some embodiments, this configuration process includes displaying one or more interfaces (e.g., 803, 810, 820, 830, 840, 850, 860, 870, 880, 890, 800A, 810A, 820A) for configuring one or more settings (e.g., associated with the respective features). For example, the process may include a series of interfaces that the device progresses through based on user input. In some embodiments, whether an interface is displayed and / or which options are displayed on the interface depends on one or more conditions (e.g., how many devices are configured to use the respective features, whether other users use such devices, etc.).

[0282] In some embodiments, while performing the configuration process (914), the electronic device (e.g., 800) displays on a display device a first interface (e.g., 800A) including one or more options for enabling a respective function on one or more devices (916). In some embodiments, while performing the configuration process, the electronic device receives input (e.g., 805A) via one or more input devices representing a selection of a set of devices among the one or more devices (918). In some embodiments, in response to receiving the input representing the selection of the set of devices while performing the configuration process, the electronic device enables the respective function on the set of devices (920). In some embodiments, the device receives a selection by a user of which of the one or more devices to enable a sub-function (e.g., output of personal data (e.g., personal request)) that is dependent on the respective function.

[0283] In some embodiments, the set of criteria includes a first criterion that is met when fewer (e.g., zero) than a threshold number (e.g., six accounts) of user accounts associated with one or more devices (e.g., registered, logged in) have the respective feature enabled. In some embodiments, the device displays an interface (e.g., 840) indicating that the maximum number of user accounts has been reached (e.g., does not include an option to enable the respective feature).

[0284] In some examples, the respective feature is a voice recognition feature. In some embodiments, the set of criteria includes a second criterion that is met when one or more devices are configured to use a language (e.g., for interpreting voice input and / or for outputting voice output (e.g., verbal output of information)) supported by the respective feature. In some embodiments, the device displays an interface (e.g., 850) indicating that a language of the one or more devices is not supported. In some embodiments, the interface includes an option (e.g., 853) to change the language associated with at least one of the one or more devices.

[0285] In some embodiments, the electronic device (e.g., 800) (first device) is associated with (e.g., logged into) a first user account. In some embodiments, in response to the second criterion not being met while performing the configuration process and in accordance with a determination that the first user account is an administrator account, the electronic device displays, on a display device, a second interface (e.g., 860) including one or more options for changing a language that the one or more devices are configured to use. In some embodiments, the second interface is displayed in response to a selection (e.g., 854) in the interface indicating that the language of the one or more devices is not supported. In some embodiments, the second interface is displayed if the second criterion is not met. In some embodiments, in response to the second criterion not being met while performing the configuration process and in accordance with a determination that the first user account is an administrator account, the electronic device receives, via one or more input devices, an input (e.g., 864) representing a change to a language that the one or more devices are configured to use. In some embodiments, during execution of the configuration process, in response to the second criterion not being met and in response to receiving input representing a change to the language pursuant to a determination that the first user account is an administrator account, the electronic device changes the language that the one or more devices are configured to use.

[0286] In some embodiments, while the electronic device is performing the configuration process, in response to the second criterion not being met, the electronic device displays, on the display device, one or more options (e.g., 864, 871, 872) for changing the language that the one or more devices are configured to use. In some embodiments, displaying the one or more options includes displaying, on the display device, a third interface (e.g., 870) including one or more options (e.g., 871, 872) for configuring a language for the plurality of devices in accordance with a determination that two or more devices of the one or more devices are configured to use a language not supported by the respective capabilities. In some embodiments, displaying the one or more options includes displaying, on the display device, a fourth interface (e.g., 880) including one or more options (e.g., 881A, 881B, 881C) for configuring a language for the one or more devices in accordance with a determination that one device of the one or more devices is configured to use a language not supported by the respective capabilities. In some embodiments, the electronic device receives an input (e.g., 885) representing a change to the language that at least one of the one or more devices is configured to use. In some embodiments, in response to receiving an input representing a change to the language, the electronic device changes the language that the at least one device is configured to use.

[0287] In some embodiments, while performing the configuration process, the electronic device receives inputs (e.g., 814, 824, 834) via one or more input devices representing selections of options to enable the respective features on one or more devices. In some embodiments, a (first) device of the electronic device is associated with a first language (e.g., English) and one or more devices are associated with a second language (e.g., French). In some embodiments, in response to receiving inputs representing selections of options to enable the respective features on one or more devices while performing the configuration process, and in accordance with a determination that the first language (e.g., English) is different from the second language (e.g., French), the electronic device displays, on a display device, a fifth interface (e.g., 820A) including one or more options (e.g., 822A) for changing the language of the first device. In some embodiments, in response to receiving inputs representing selections of options to enable the respective features on one or more devices while performing the configuration process, and in accordance with a determination that the first language (e.g., English) is not different from the second language (e.g., French), the electronic device refrains from displaying the fifth interface.

[0288] In some embodiments, during execution of the configuration process, following a determination that a voice profile (e.g., obtained by executing a voice training process) is not associated with the first device (e.g., not stored in the first device, not used by the first device), the electronic device displays on the display device a sixth interface (e.g., 810A) for performing a voice training operation for the voice recognition function.

[0289] In some embodiments, pursuant to a determination while performing the configuration process that a voice profile (e.g., obtained by performing a voice training process) is associated with the first device (e.g., stored on, used by the first device), the electronic device refrains from displaying, on the display device, a sixth interface for performing a voice training operation for the voice recognition function. In some embodiments, pursuant to a determination while performing the configuration process that a voice profile (e.g., obtained by performing a voice training process) is associated with the first device (e.g., stored on, used by the first device), the electronic device configures the voice recognition function to use the voice profile.

[0290] In some embodiments, in accordance with a determination during the configuration process that the voice recognition function is enabled (e.g., during the process for configuring the respective function), the electronic device displays, on the display device, a seventh interface (e.g., 820) for configuring a second function different from the respective function. In some embodiments, enabling the second function requires that the first function is enabled. In some embodiments, in accordance with a determination during the configuration process that the voice recognition function is not enabled (e.g., during the process for configuring the respective function), the electronic device refrains from displaying, on the display device, a seventh interface for configuring the second function. In some examples, by displaying an interface for enabling the second function only when the first function is enabled, an electronic device is provided that provides an intuitive and efficient configuration process for a user. As an example, the user does not need to provide an input indicating whether the user prefers to enable the second function when the first function is not enabled, thus reducing the number of inputs and time required for the user to operate the electronic device (e.g., by assisting the user to provide appropriate inputs and reducing user errors when operating / interacting with the device), and further reducing power usage and improving the battery life of the device.

[0291] In some embodiments, pursuant to a determination that the voice recognition feature is not enabled (e.g., disabled during a process for configuring the respective feature) and the second feature is enabled (e.g., prior to being disabled during the configuration process), the electronic device displays, on the display device, an eighth interface that includes one or more of an option to enable the respective feature (e.g., 893) and an option to disable the second feature (e.g., 892). In some embodiments, pursuant to a determination that the voice recognition feature is enabled (e.g., during a process for configuring the respective feature) and the second feature is enabled, the electronic device refrains from displaying, on the display device, the eighth interface.

[0292] In some embodiments, pursuant to a determination that the one or more devices include a plurality of devices, the electronic device displays, on the display device, a ninth interface (e.g., 800A) for configuring the second functionality including one or more options (e.g., 802AA, 802AB, 802AC) for selecting which of the plurality of devices have the second functionality enabled (e.g., for a particular user account). In some embodiments, pursuant to a determination that the one or more devices do not include a plurality of devices, the electronic device refrains from displaying the ninth interface for configuring the second functionality including one or more options for selecting which of the plurality of devices have the second functionality enabled (e.g., for a particular user account).

[0293] In some embodiments, in accordance with a determination that the one or more devices do not support the respective capabilities, the electronic device refrains from displaying (922) a prompt on the display device to configure the respective capabilities of the one or more devices.

[0294] In some embodiments, the set of criteria includes criteria that are met when an account associated with the first device accepts (e.g., using the first device) an invitation to join a group of accounts associated with one or more devices (e.g., join a smart home group). For example, an interface for configuring voice recognition functionality is displayed (e.g., upon switching to an application or interface for managing a group of devices associated with a geographic location (e.g., home) or upon arriving at a new geographic location associated with the group of devices).

[0295] In some embodiments, the set of criteria includes criteria that are met when a new device (e.g., of a particular type, such as a smart speaker or home media hub) is added to the group of devices associated with the first device.

[0296] In some embodiments, the notification is sent to multiple devices (e.g., a first device) in response to the set of criteria being met. For example, each device (e.g., a first device) associated with a group of devices can receive the data and cause a prompt to be displayed in response to the set of criteria being met.

[0297] In some embodiments, pursuant to a determination that the first device is associated with a group of devices that includes a particular type of device (e.g., a home media hub) (e.g., not necessarily the same as one or more devices (e.g., that are smart speakers)), the electronic device displays on the display device one or more of an option (e.g., 834) to enable displaying an indication of a user account associated with the first device by the particular type of device and an option (e.g., 832) to disable displaying an indication of a user account associated with the first device by the particular type of device.

[0298] In some embodiments, in response to receiving a request to log into the first account on the first device and in accordance with a determination that a second device (e.g., smart speaker, home media hub) of the one or more devices is logged into an account other than the first account, the electronic device displays a prompt (e.g., 891A) including one or more of an option to log the second device into the first account (e.g., 892A) and an option to leave the second device logged into the account other than the first account (e.g., 893A). In some embodiments, in response to receiving a user input selection of the option to log the second device into the first account, the electronic device logs the second device into the first account. In some embodiments, both the first device and the second device are logged into the second account and both remain logged into the second account after logging the second device into the first account. For example, the first account can be a media account and the second account can be a cloud-based service (e.g., storage) account that remains logged into both devices even when the first account changes on one of the devices. In some embodiments, pursuant to receiving a user input selection of an option for the second device to remain logged into an account other than the first account, the electronic device refrains from logging into the first account for the second device.

[0299] In some embodiments, the first device is logged into a second account. In some embodiments, a third device of the set of devices is logged into a fourth account. In some embodiments, the second account is associated with a group of accounts (e.g., smart devices in the user's home that are linked together (e.g., by an application for controlling such devices)). In some embodiments, pursuant to a determination that the fourth account is not associated with the group of accounts, the electronic device displays a prompt (e.g., 811B) on the display device that includes an option (e.g., 812B) to invite the fourth account to the group of accounts. In some embodiments, the prompt includes an option (e.g., 813B) to use the fourth account as a default account (e.g., an account used to output information in response to requests that do not otherwise match an audio profile associated with the respective account). In some embodiments, selection of the default account option (e.g., 816B) causes a prompt (e.g., 830B) to log into the account (e.g., to enter login credentials) to be displayed.

[0300] In some embodiments, in response to determining that the fourth account is associated with the group of accounts, the electronic device refrains from displaying on the display device a prompt including an option to invite the fourth account to the group of accounts. In some embodiments, after displaying the prompt including the option to invite the fourth account to the group of accounts, the electronic device receives an input (e.g., 815B) representing a selection of the option to invite the fourth account to the group of accounts. In some embodiments, in response to receiving the input representing a selection of the option to invite the fourth account to the group of accounts, the electronic device sends an invitation to the group of accounts to the fourth account.

[0301] It should be noted that details of the process described above in connection with method 900 (e.g., FIG. 9) are also applicable in an analogous manner to the methods described below. For example, method 1100 optionally includes one or more of the features of the various methods described above with reference to method 900. For example, after performing a configuration process for a user account on one or more devices, settings for the user account may be subsequently configured on one or more devices. For the sake of brevity, these details will not be repeated below.

[0302] 10A-10M show example user interfaces for configuring a user account, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0303] 10A-10M may be employed to configure (e.g., edit) settings for one or more user accounts using an electronic device such as electronic device 1000. As will be described in more detail, in some embodiments, the settings so configured include personalized settings, which include one or more user preferences, and non-personalized settings, which include one or more user permissions.

[0304] 10A shows a home interface 1003 for managing a set of controllable external devices associated with a location on a display 1002 of an electronic device 1000. In some examples, the home interface 1003 is an interface of a home control application.

[0305] The home interface 1003 includes a home affordance 834A that, when selected, causes the electronic device 800 to display an interface through which a user can view and / or edit a user account's set of location profiles. For example, while displaying the configuration interface 1003, the electronic device 1000 detects a selection of a home affordance 1004. As shown in FIG. 10A, the selection of the home affordance 1004 is, optionally, a tap gesture 1005. In response to the selection of the home affordance 1004, the electronic device 1000 displays the home interface 1010 on the display 1002 (e.g., replaces the display of the home interface 1003 with the home interface 1010), as shown in FIG. 10B.

[0306] Home interface 1010 includes user affordances 1011, each of which, in some embodiments, corresponds to a respective user account. By way of example, user affordance 1011A corresponds to a user account for user John Appleseed ("John A"), and user affordance 1011B corresponds to a user account for user Jane Appleseed ("Jane A"). In the example shown in FIG. 10B, user John Appleseed's user account is an administrator account, and user Jane Appleseed's user account is not an administrator account. Home interface 1010 further includes invite affordance 1012, which, when selected, allows a user to invite one or more other users to their location profile.

[0307] In some embodiments, users of administrator accounts are permitted to configure both personalized and non-personalized settings for their own account, as well as non-personalized settings for other user accounts. As another example, users of non-administrator accounts are permitted to configure only personalized settings for their own user accounts.

[0308] For example, while displaying the home interface 1010, the electronic device 1000 detects a selection of a user affordance 1011A. As shown in FIG. 10B, the selection of the user affordance 1011A is, optionally, a tap gesture 1013. In some examples, in response to the selection of the user affordance 1011A, the electronic device 800 displays a user account interface 1020 for the user account of user John Appleseed on the display 802 (e.g., replaces the display of the home interface 1010 with the user account interface 1020), as shown in FIG. 10C (recall that the selected user affordance 841AB corresponds to user John Appleseed).

[0309] The user account interface 1020 includes a user indicator 1021, a user identification 1022, a voice capabilities portion 1023, a profile portion 1024, a playback portion 1025, a permissions portion 1026, a permissions portion 1027, and an exit affordance 1028. The user indicator 1021 indicates the name of a user associated with the user account for the user account interface 1020. The user identification 1021 indicates information associated with the user (e.g., the user's email address). In some embodiments, the user identification 1021 serves as a unique identifier for the user account (e.g., a username).

[0310] The voice feature portion 1023 includes a voice recognition element 1023A and a personal request affordance 1023B. The voice recognition element 1023A includes a toggle affordance representing a parameter indicating whether the voice recognition feature is enabled for the user account. In some examples, selection of the toggle affordance of the voice recognition element 1023A causes the value of the parameter to change (e.g., turn on to off, turn on to off). The personal request affordance 1023B, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1070 of FIG. 10H ) through which the user can view and / or adjust one or more settings associated with the personal request feature. As an example, a user can selectively enable the personal request feature of the user account for each device of a set of devices associated with a location. As another example, a user can selectively enable, upon request, a requirement that the user be authenticated before providing secure and / or private information. The user can be authenticated, for example, in response to a detected proximity of the electronic device 1000 and / or a match of a voice input to the user's voice profile.

[0311] The profile portion 1024 includes a profile affordance 1024A that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1080 of FIG. 10I) through which the user can view and / or adjust one or more settings associated with the profile feature. As an example, a user may selectively enable the profile feature for each of a set of devices (e.g., media playback devices) associated with a location. In this manner, one or more other users may access the user's content while using devices for which the profile feature is enabled for the user account.

[0312] The playback unit 1025 includes a toggle affordance representing a parameter indicating whether the user's listening history has been updated in response to a user request, for example as described with reference to FIGS. 6A-6L.

[0313] The permissions portion 1026 includes a remote access affordance 1026A that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1090 of FIG. 10J) through which the user can view and / or configure one or more settings associated with the remote access functionality. As an example, a user can, for example, use the electronic device to selectively enable whether the user is authorized to remotely control an accessory. The permissions portion further includes an accessory affordance 1026B that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1000A of FIG. 10K) through which the user can view and / or configure settings for adding and / or configuring devices associated with a location.

[0314] The permissions portion 1027 includes a camera affordance 1027A that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1010A of FIG. 10L) through which the user can view and / or configure settings associated with video streaming. As an example, the user can configure permissions to view live video, permissions to view recorded, or a combination thereof. The permissions portion 1027 includes a network affordance 1027B that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1020A of FIG. 10M) through which the user can view and / or configure settings associated with network sharing. As an example, the user can select from a set of permission levels for accessing a network, a set of permission levels for sharing on a network, or a combination thereof.

[0315] 10C, in some examples, a portion of the user account interface 1020 may not be displayed on the display 1002. Thus, in some examples, a user may provide a set of inputs, such as a swipe gesture, to reveal a portion of the user interface 1020 that would otherwise not be displayed.

[0316] In some embodiments, an administrator cannot configure one or more settings for a user account that has administrator privileges. For example, John Appleseed's user account is an administrator account and therefore cannot configure settings corresponding to the permissions section 1026. An administrator cannot, for example, revoke the permission to remotely control accessories or to add and / or edit accessories. Thus, both affordances 1026A,B of the permissions section 1026 are shown as not configurable.

[0317] As described, in some examples, one or more features (e.g., a personal request feature) may be configured only if another feature (e.g., a voice recognition feature) is enabled. By way of example, referring to FIG. 10C, the electronic device detects a selection of a personal request affordance 1023B, but the voice recognition feature is not enabled for the user account of the user account interface 1020 (e.g., as indicated by the toggle affordance of the voice recognition element 1023A). As shown in FIG. 10C, the selection of the user affordance 1023B is, optionally, a tap gesture 1029. In some examples, if the voice recognition feature is disabled, in response to the selection of the user affordance 1023B, the electronic device 800 displays a feature enablement interface 1030 on the display 802, as shown in FIG. 10D. In some examples, the feature enablement interface is overlaid on the user interface 1020.

[0318] The feature enablement interface 1030 includes an indicator 1031, a feature enablement affordance 1032, and a refusal affordance 1033. The indicator 1031 indicates that the voice recognition feature must be enabled first in order to enable the personal request feature. The refusal affordance 1033, when selected, indicates to the electronic device 1000 that the user does not intend to enable the voice recognition feature for the user account. Thus, in response to selecting the refusal affordance 1033, the electronic device 1000 does not enable the voice recognition feature or the personal request feature and stops displaying the feature enablement interface 1030. The feature enablement affordance 1032, when selected, causes the electronic device 1000 to display a user interface for performing a configuration process.

[0319] As an example, while displaying the function-enabling interface 1030, the electronic device detects a selection of a function-enabling affordance 1033. As shown in FIG. 10D, the selection of the function-enabling affordance 1033 is, optionally, a tap gesture 1034. In response to the selection of the function-enabling affordance 1034, the electronic device 1000 displays a configuration interface 1040 including a continuation affordance 1041 on the display 1002 (e.g., replaces the display of the function-enabling interface 1030 with the configuration interface 1040), as shown in FIG. 10E. In some examples, the configuration interface 1040 is substantially the same as the configuration interface 820 of FIG. 8B. Thus, in response to the selection of the continuation affordance 1041, the electronic device 800 initiates a configuration process for configuring the voice recognition feature, such as the configuration process described with respect to FIGS. 8A-8M.

[0320] In some examples, a user of a first user account cannot configure one or more settings of a second user account, even though the privileges are assigned to the first user account. As an example, a user account with administrator privileges may only have privileges to configure non-personalized settings for other user accounts.

[0321] FIG. 10F illustrates a scenario in which a user of a first user account (e.g., “John Appleseed”) with administrative privileges views a user account interface 1050 for another user's second user account (e.g., “Jane Appleseed”). The user account interface 1050 can be viewed, for example, in response to a selection of a user affordance 1011B (e.g., input 1014 in FIG. 10B) corresponding to the user account. As shown, personalization settings 1053, 1054, 1055, such as settings directed to enabling multi-user features (e.g., voice recognition features, profile features), are shown as non-configurable, and non-personalization settings 1051, 1052, such as those directed to user permissions (e.g., remote access permissions, streaming permissions), are shown as configurable. Additionally, a user with administrative privileges can further remove the second user account from the location profile using a remove affordance 1056.

[0322] 10G illustrates a scenario in which a user (e.g., “Jane Appleseed”) associated with a user account without administrative privileges views his or her user account. As illustrated, personalization settings 1063, 1064, 1065, such as settings directed to enabling multi-user features (e.g., voice recognition features, profile features), are shown as configurable (recall that these settings are personal to the user account), and non-personalization settings 1061, 1062, such as those directed to user permissions (e.g., remote access permissions, streaming permissions), are shown as non-configurable (recall that the user account does not have administrative privileges). In some examples, a user associated with a user account without administrative privileges can further remove the user account from the location profile using a delete affordance 1066.

[0323] 11 is a flow diagram illustrating a method for configuring a user account using an electronic device (e.g., a mobile device) according to some embodiments. Method 1100 is performed on a device (e.g., 100, 300, 500, 580, 600) having a display device and one or more input devices. Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0324] As described below, the method 1100 provides an intuitive way to configure a user account using an electronic device. This method reduces the cognitive burden on a user configuring a user account using an electronic device, thereby creating a more efficient human-machine interface. For example, by displaying a settings interface where settings are selectively editable based on the user account associated with the settings interface and the user account associated with the electronic device, a user is allowed to efficiently and intuitively edit settings in the settings interface. As an example, the electronic device may allow a user to edit personalized settings only for the user's user account and non-personalized settings if the user is an administrator. Limiting the number of editable settings in this manner reduces the number of inputs and time required for a user to operate the electronic device (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving the device's battery life.

[0325] In some embodiments, the electronic device receives (1102) an input (eg, 1014) (eg, a selection of a settings affordance) via one or more input devices.

[0326] In some embodiments, in response to receiving the input, the electronic device displays (1104) on a display device a settings interface (e.g., 1050) for a plurality of devices (e.g., smart devices) associated with a plurality of accounts (e.g., members of a smart home), including one or more administrator accounts (accounts for 1011A) and one or more non-administrator accounts (accounts for 1011B). In some embodiments, the electronic device (e.g., 1000) is associated with (e.g., logged into) a first account of the plurality of accounts (1106).

[0327] In some embodiments, in accordance with the first account being an administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for a second account different from the first account (e.g., an administrator viewing another user's page) (1108), the setting interface includes one or more settings (e.g., 1051, 1052, 1056) of a first type (e.g., non-personalized settings such as control of a camera device, ability to share network credentials, etc.) and one or more settings (e.g., 1053, 1054, 1055) of a second type (e.g., personalization settings such as enabling voice ID, personal requests, whether the account is displayed on a smart device, and updating listening history) (1110). In some embodiments, in accordance with the first account being an administrator account of the plurality of accounts and in accordance with the setting interface being a setting interface for a second account different from the first account (e.g., an administrator viewing another user's page), the one or more settings of the first type are editable via the setting interface (1112). In some embodiments, in accordance with the first account being an administrator account of the plurality of accounts and in accordance with the settings interface being a settings interface for a second account different from the first account (e.g., an administrator viewing another user's page), the one or more settings of the second type are not editable via the settings interface (1114). In some embodiments, in accordance with the first account being a non-administrator account of the plurality of accounts and in accordance with the settings interface (e.g., 1060) being a settings interface for the first account (e.g., a non-administrator viewing its own settings interface) (1116), the settings interface includes one or more settings (e.g., 1063, 1064, 1065) of the second type (e.g., personalization settings) (1118).In some embodiments, one or more settings of the second type are editable via the settings interface (1120) in accordance with the first account being a non-administrator account of a plurality of accounts and in accordance with the settings interface being a settings interface for the first account (e.g., a non-administrator viewing its own settings interface).

[0328] In some embodiments, in accordance with the first account being a non-administrator account of the plurality of accounts and in accordance with the settings interface being a settings interface for the first account (e.g., a non-administrator viewing its settings interface), the settings interface includes one or more settings of a first type (e.g., non-personalized settings) (1122). In some embodiments, in accordance with the first account being a non-administrator account of the plurality of accounts and in accordance with the settings interface being a settings interface for the first account (e.g., a non-administrator viewing its settings interface), the one or more settings of the first type are not editable via the settings interface (1124).

[0329] In some embodiments, the one or more settings of the second type include an option (e.g., 1065) that enables updating of data associated with the first account (e.g., listening history) based on a user input request (e.g., a voice input request) to output content (e.g., play music) received on one or more of the multiple devices.

[0330] In some embodiments, the one or more settings of the second type (eg, 1063) include an option to enable voice recognition functionality on one or more of the plurality of devices.

[0331] In some embodiments, the one or more settings of the second type (e.g., 1063) include an option to enable output of private information associated with the first account in response to a user input request received at one or more of the plurality of devices to output private information from the first account. Including an option in the second type of setting for enabling output of private information allows a user to configure the functionality supported by the device such that the user can efficiently and intuitively request output of private information from the device. Providing information in this manner reduces the number of inputs and time required for a user to operate an electronic device (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving battery life of the device.

[0332] In some embodiments, the electronic device receives a first set of one or more inputs associated with an option to enable output of private information associated with the first account (e.g., selection of one or more devices (in the displayed interface (e.g., 1070) after receiving a selection of a “Private Request” affordance displayed in the settings interface, or direct selection of a device in the settings interface). In some embodiments, in response to receiving the first set of one or more inputs, the electronic device displays on a display device one or more options (e.g., 1071A, 1071B, 1071C) for selecting one or more devices of a plurality of devices that enable output of private information associated with the first account, and one or more options that require authentication in response to a user input request to output private information from the first account.

[0333] In some embodiments, pursuant to a determination that the first functionality (e.g., of the second type (e.g., personalization setting)) is enabled, the electronic device displays an option to enable output of private information associated with the first account in response to a user input request to output private information from the first account. In some embodiments, pursuant to a determination that the first functionality (e.g., voice recognition) is disabled, the electronic device refrains from displaying an option to enable output of private information associated with the first account in response to a user input request to output private information from the first account (e.g., the option is hidden, obscured, or not displayed). For example, the option (e.g., output private information in response to voice input) is displayed only if the first functionality (e.g., voice recognition functionality) is enabled.

[0334] In some embodiments, the second set of one or more inputs represents a request to enable output of private information associated with the first account in response to a user input request to output private information from the first account received at one or more of the multiple devices. In some embodiments, in response to detecting the second set of one or more inputs associated with an option to enable output of private information, in accordance with a determination that the second functionality (e.g., voice recognition) is disabled, the electronic device displays a prompt (e.g., 1030) on a display device to enable the second functionality. For example, the prompt includes an option (e.g., 1032) (e.g., an affordance) to enable the second functionality (e.g., voice recognition) and / or an option (e.g., 1033) to disable the first functionality (e.g., output of private information on request). If enabling the second functionality is required to use the first functionality, such a prompt can provide the user with relevant information to make a decision regarding whether to disable the desired first functionality. In some embodiments, in response to detecting a second set of one or more inputs associated with the option to enable output of private information, in accordance with a determination that the second functionality (e.g., voice recognition) is enabled, the electronic device refrains from displaying a prompt on the display device to enable the second functionality.

[0335] In some embodiments, the electronic device receives a third set of one or more inputs (e.g., 1034) associated with prompts to enable the second setting. In some embodiments, in response to receiving the third set of one or more inputs associated with prompts to enable the second setting, the electronic device initiates a process for configuring the second functionality, including displaying an interface (e.g., 1040) for configuring the second functionality.

[0336] In some embodiments, the electronic device is associated with (e.g., included in a group of devices that are connected to and include) a particular type of device (e.g., different from the electronic device) (e.g., a home media hub). In some embodiments, the one or more settings of the second type include one or more of an option (e.g., 1024A, 1064) for enabling displaying, by the particular type of device, an indication of the first account associated with the electronic device, and an option for disabling displaying, by the particular type of device, an indication of the first account associated with the electronic device.

[0337] In some embodiments, the group of devices includes a plurality of devices of a particular type of device. In some embodiments, the electronic device receives a fourth set of one or more inputs associated with one or more of an option to enable display of the first account and an option to disable display of the first account. In some embodiments, in response to receiving the fourth set of one or more inputs, the electronic device displays on the display device an interface for selecting a device of the particular type of device in the group of devices for one or more of enabling display of the first account on the selected device and disabling display of the first account on the selected device.

[0338] In some embodiments, the one or more settings of the first type include one or more options (e.g., 1027A, 1062) for controlling the permissions of the first account with respect to one or more network-connected camera devices of the plurality of devices (e.g., permissions to stream cameras, permissions to view recorded camera streams).

[0339] In some embodiments, the electronic device receives a fifth set of one or more inputs associated with one or more options for controlling permissions of the first account with respect to the one or more networked camera devices. In some embodiments, in response to receiving the fifth set of one or more inputs, the electronic device displays on a display device an interface for selecting from a plurality of permission levels for the first account with respect to the one or more networked camera devices (e.g., permissions to stream cameras, permissions to view recorded camera streams, permissions to remotely access camera streams).

[0340] In some embodiments, the one or more settings of the first type include one or more options (e.g., 1027B, 1062) that control the permissions of a first account with respect to sharing credentials for accessing a network (e.g., a Wi-Fi network) associated with multiple devices (e.g., access by the first account or access by a third account on a device nearby the electronic device).

[0341] In some embodiments, the electronic device receives a sixth set of one or more inputs associated with one or more options for controlling the authority of the first account with respect to sharing credentials to access the network. In some embodiments, in response to receiving the sixth set of one or more inputs, the electronic device displays on a display device an interface (e.g., 1020A) for selecting from a plurality of authority levels for sharing credentials to access the network (e.g., authority for the first account and its associated devices to access the network, authority for the first account to share network credentials with a third account that is not a member of the plurality of accounts). For example, the electronic device may display a prompt or other interface in response to determining that a device associated with a non-member (e.g., of the plurality of accounts) is nearby (e.g., in a geographic location associated with the plurality of accounts, such as the user's home), the prompt including an option to have the network credentials (e.g., Wi-Fi network name and password) sent to the nearby non-member device. Displaying the prompt or being able to share the credentials may be conditional on the authority of the first account.

[0342] In some embodiments, the one or more settings of the first type include one or more options (e.g., 1026A, 1051, 1061) for controlling the first account's permissions with respect to accessing the multiple devices when the electronic device is away from the multiple devices (e.g., not in a geographic location (e.g., a home location) associated with the multiple devices (e.g., not connected to a network (e.g., a Wi-Fi network) associated with the multiple devices to which the multiple devices are connected or configured to connect).

[0343] In some embodiments, the one or more settings of the first type include one or more options (e.g., 1026B, 1051, 1061) for controlling the authority of the first account to perform one or more of: adding a device to the plurality of devices and removing a device from the plurality of devices.

[0344] In some embodiments, the settings interface includes an affordance (e.g., 1028, 1056, 1066). In some embodiments, the electronic device receives input via one or more input devices corresponding to a selection of the affordance. In some embodiments, in response to receiving input corresponding to a selection (e.g., a tap) of the affordance, the electronic device causes the first account to be removed from the multiple accounts (e.g., the affordance represents an option (e.g., smart home) that allows the user to retain the multiple accounts). In some embodiments, an administrator account viewing a settings interface of a non-administrator account includes an affordance that, when selected, causes the corresponding non-administrator account to be removed from the multiple accounts.

[0345] It should be noted that the details of the process (e.g., FIG. 11) described above in connection with method 1100 are also applicable in an analogous manner to the methods described below. For example, method 1100 optionally includes one or more of the characteristics of the various methods described below with reference to method 1300. For example, one or more settings associated with the user's user account may be configured after the user joins a location profile in response to an invitation. For the sake of brevity, these details will not be repeated below.

[0346] 12A-12G show example user interfaces for adding a user to a location profile according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0347] FIG. 12A shows a home interface 1203 of a home control application associated with a location (e.g., "123 Main St."). The home interface 1203 includes an invite affordance 1204 that, when selected, allows a user to invite other users to add the user account to a location profile. By way of example, while displaying the home interface 1203, the electronic device 1200 detects a selection of the invite affordance 1204. As shown in FIG. 12A, the selection of the invite affordance 1204 is, optionally, a tap gesture 835A. In response to the selection of the invite affordance 1204, the electronic device 1200 displays an invite interface 1210 on the display 1202 (e.g., replacing the display of the home interface 1203 with the invite interface 1210), as shown in FIG. 12B.

[0348] The invitation interface 1210 includes a user group 1221, which in turn includes user affordances 1222-1224. In some examples, the user group 1221 includes a set of users (e.g., personal contacts) associated with the user of the electronic device 1200. By way of example, the group 1221 can include users known to be family members of the user of the electronic device 1200. Although the home interface 1210 is shown as including a single group of user accounts, in other examples, one or more other groups can alternatively or additionally be included in the home interface 1210, such as a coworker group or a best friend group. In some examples, one or more groups in the home interface 1210 can include users suggested by the electronic device.

[0349] In some examples, each of the user affordances 1212-1214 corresponds to a respective user account and, when selected, invites the user to add the user account to the location profile. Each of the user affordances 1212-1214 can include, for example, an indicator (e.g., indicator 1212A) that identifies the user (or user account) of the user affordance (e.g., user affordance 1212), a user identification (e.g., user identification 1212B) that indicates information associated with the user (e.g., the user's email address), and an icon (e.g., icon 1212C) that optionally indicates a representation of the user's appearance. In some examples, the user identification serves as a unique identifier for the user account.

[0350] In an exemplary operation, while displaying the home interface 1210, the electronic device 1200 detects a selection of a user affordance 1212. As shown in FIG. 12B, the selection of the user affordance 1212 is, optionally, a tap gesture 1215. In response to the selection of the user affordance 1212, the electronic device 1200 populates an invite field 1216 with the name of the selected user, as shown in FIG. 12C. While displaying the invitation interface 1210, the electronic device 1200 detects a selection of a next affordance 1217. As shown in FIG. 12C, the selection of the next affordance 1217 is, optionally, a tap gesture 1218. In response to the selection of the affordance 1217, the electronic device 1200 then displays an invite interface 1220 on the display 1202 (e.g., replaces the display of the home interface 1210 with the invite interface 1220), as shown in FIG. 12D.

[0351] Invite interface 1220 includes user indicator 1221, user identification 1222, authority portion 1223, and authority portion 1224. User indicator 1221 indicates the name of the user for user account interface 850A. User identification 1222 indicates information associated with the user (e.g., the user's email address). In some embodiments, user identification 1222 serves as a unique identifier for the user account.

[0352] In some examples, the invite interface 1220 allows a user to view and / or configure one or more permissions of a user before inviting the user. For example, the permissions portion 1223 includes a remote access affordance 1223A that, when selected, causes the electronic device 1200 to display one or more user interfaces (e.g., interface 1090 of FIG. 10J) through which the user can view and / or configure one or more settings associated with the remote access functionality. As an example, a user can selectively enable whether the user has permission to remotely control an accessory after it is added to a location profile. The permissions portion further includes an accessory affordance 1223B that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1000A of FIG. 10K) through which the user can view and / or configure settings for adding and / or configuring devices associated with the location.

[0353] The permissions portion 1224 includes a camera affordance 1224A that, when selected, causes the electronic device 1200 to display one or more user interfaces (e.g., interface 1010A of FIG. 10L) through which the user can view and / or configure settings associated with video streaming. As an example, the user can configure permissions to view live video, permissions to view recorded video, or a combination thereof. The permissions portion 1224 includes a network affordance 1224B that, when selected, causes the electronic device 1000 to display one or more user interfaces (e.g., interface 1020A of FIG. 10M) through which the user can view and / or configure settings associated with network sharing. As an example, the user can select from a set of permission levels for accessing a network, a set of permission levels for sharing on a network, or a combination thereof.

[0354] While displaying the invitation interface 1220, the electronic device 1200 detects a selection of an invitation affordance 1225. As shown in FIG. 12D , the selection of the invitation affordance 1225 is, optionally, a tap gesture 1226. In response to the selection of the invitation affordance 1225, a selected user (e.g., user “Jane Appleseed”) is invited to add their user account to the location profile.

[0355] In some examples, further in response to a selection of the invite affordance 1225, the electronic device displays a home interface 1230 on the display 1202 (e.g., replacing the display of the invite interface 1220 with the home interface 1230), as shown in FIG 12E. As shown, the home interface 1230 includes an invitation indicator 1231 that indicates that an invited user (e.g., Jane Appleseed) has been invited to add their user account to the location profile.

[0356] FIG. 12F illustrates a device 1250 of a user who has been invited to add their account to a location profile (e.g., "123 Main St."). In response to the invitation, the electronic device 1250 displays a notification 1241 on the lock screen interface 1240. The invitation may, for example, indicate that the user is being invited to the location profile. For example, while displaying the lock screen interface, the electronic device 1250 detects a selection of the notification 1241. As shown in FIG. 12F, the selection of the notification 1241 is, optionally, a tap gesture 1242. In response to the selection of the notification 1241, the electronic device 1250 displays an acceptance interface 1245 on the display 1252 (e.g., replacing the display of the home interface 1240 with the acceptance interface 1245), as shown in FIG. 12G.

[0357] The acceptance interface 1245 includes an acceptance affordance 1246, a rejection affordance 1247, and a delay affordance 1248. The rejection affordance 1247, when selected, indicates an intention to reject the invited user's invitation. Thus, the electronic device 1250 does not cause one or more devices (e.g., the electronic device 1200) associated with the location (or a remote server hosting the location profile) to add the user to the location profile. The delay affordance 1248, when selected, causes the electronic device to stop displaying the acceptance interface 1245 and, optionally, re-display one or more of the notification 1241 and / or the acceptance interface 1245 (e.g., after a period of time) if a delay criterion is met. In some embodiments, the delay criterion includes a requirement that a predetermined time has elapsed since the acceptance interface 1245 was last displayed. In some embodiments, the delay criterion includes a requirement that a user of the electronic device 1250 has a home control application of the electronic device 1250 open.

[0358] In some examples, while displaying the acceptance interface 1245, the electronic device 1200 detects a selection of the acceptance interface 1245. As shown in FIG. 12G , the selection of the acceptance interface 1245 is, optionally, a tap gesture 1246. In response to the selection of the invitation affordance 1225, the electronic device 1250 causes one or more devices associated with the location (e.g., the electronic device 1200) (or a remote server hosting a location profile) to add the invited user to the location profile.

[0359] 13 is a flow diagram illustrating a method for adding a user to a location profile using an electronic device (e.g., a mobile device) according to some embodiments. Method 1300 is performed on a device (e.g., 100, 300, 500, 580, 600) having a display device and one or more input devices. Some operations of method 1300 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0360] As described below, method 1300 provides an intuitive way to add a user to a location profile. This method reduces the cognitive burden on the user when adding a user to a location profile, thereby creating a more efficient human-machine interface. For example, by providing an invitation to a user account that selectively provides access to a set of devices, the user can configure one or more permissions for the user account before providing the invitation. This reduces the need to configure user account permissions after the account accepts the invitation. This then reduces the number of inputs and time required for a user to operate an electronic device (e.g., by assisting the user to provide appropriate inputs and reducing user errors when operating / interacting with the device), and further reduces power usage and improves the battery life of the device. An exemplary implementation of method 1300 further eliminates the risk of a user account having inappropriate permissions after an invitation is accepted and before the user configures permissions for the account.

[0361] In some embodiments, the electronic device (e.g., 1200) displays (1302) via a display device a device access configuration user interface (e.g., 1210, 1220) including at least a first set of device access affordances (e.g., 1211, 1212, 1213, 1223A, 1223B, 1224A, 1224B) (e.g., affordances for identifying one or more users, affordances for selecting a permission level).

[0362] In some embodiments, while displaying the device access configuration user interface, the electronic device receives (1306) one or more sets of inputs (e.g., 1215, 1217, 1225) via one or more input devices, including inputs designating one or more users (e.g., use of a first set of device access affordances, selection of a user, selection of multiple users, and / or selection of the finish / next affordance, and / or selection of “send invite”).

[0363] In some embodiments, in response to receiving (1308) a set of one or more inputs, where the set of one or more inputs includes an input corresponding to a selection (e.g., selection of the “Invite” affordance while a default setting is selected, changing a default selection) of a first permission setting (e.g., 1223A, 1223B, 1224A, 1224B) (e.g., non-personalized settings such as control of a particular accessory, ability to view streams from one or more camera devices, and / or ability to share network credentials), the electronic device sends (1310) an invitation providing access to one or more users, including access to a set of devices (e.g., smart devices), based on the first permission setting, including the first permission (e.g., user can view camera streams, user can share network credentials).

[0364] In some embodiments, in response to receiving 1308 the set of one or more inputs, where the set of one or more inputs does not include an input corresponding to a selection of the first permission setting, the electronic device sends 1310 an invitation that, when accepted, provides access to one or more users, including access to the set of devices, based on the first permission setting that does not include the first permission (e.g., the user cannot view the camera stream, the user cannot share network credentials).

[0365] In some embodiments, the first permission setting is a setting that controls access by one or more users to one or more network-connected camera devices. For example, access that includes the first permission can include access to streams of the one or more camera devices, and access that does not include the first permission does not include access to streams of the one or more camera devices.

[0366] In some embodiments, the input corresponding to selection of the first permission setting includes an input corresponding to selection of one of a plurality of access permission levels by one or more users to one or more network-connected camera devices.

[0367] In some embodiments, the set of devices is associated with (e.g., connected to) a network. In some embodiments, the first permission setting is a setting that controls permissions regarding access to the network.

[0368] In some embodiments, the input corresponding to a selection of the first permission setting includes an input corresponding to a selection of one of a plurality of permission levels controlling permission to access the network.

[0369] In some embodiments, the set of devices includes one or more devices that can be remotely controlled (e.g., controlled by devices not directly connected to it and / or not connected to the same network). In some embodiments, the first permission setting is a setting that controls permission to remotely control one or more devices that can be remotely controlled. For example, music can be played remotely from a device, lights can be turned on / off / dim, a thermostat can be adjusted, etc.

[0370] In some embodiments, the electronic device is associated with (e.g., logged into) a set of users (e.g., a set of accounts that share storage for one or more services and / or cloud-based services). In some embodiments, displaying the device configuration user interface includes displaying (1304) on the display device an indication of one or more proposed users that are included in the set of users (e.g., that do not currently have access to the set of devices). In some embodiments, the input designating the one or more users is a selection of at least one of the set of users.

[0371] It should be noted that the details of the process (e.g., FIG. 13) described above with respect to method 1300 are also applicable in a similar manner to the methods described above. For example, method 1300 optionally includes one or more of the characteristics of the various methods described above with reference to method 1100. For example, one or more settings associated with the user's user account may be configured after the user joins a location profile in response to an invitation. For the sake of brevity, these details will not be repeated below.

[0372] 14A-14F show example user interfaces for adding a user to a location profile according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0373] 14A shows a home screen interface 1403 displayed on a display device 1402 of the electronic device 1400. While displaying the home screen interface 1403, the electronic device 1400 further displays a prompt interface 1404. In some examples, the prompt interface 1404 is overlaid on the home screen interface 1403 and / or displayed during an initialization process of an external device. The prompt interface 1404 includes a continue affordance 1405 and a delay affordance 1406. The delay affordance 1406, when selected, causes the electronic device 1400 to stop displaying the prompt interface 1404, and optionally re-display the prompt interface 1404 (e.g., after a predetermined period of time) if a predetermined time has elapsed since the prompt interface 1404 was last displayed.

[0374] While displaying the prompt interface 1404, the electronic device 1400 detects a selection of a continuation affordance 1405. As shown in FIG. 14A, the selection of the continuation affordance 1405 is, optionally, a tap gesture 1407. In response to the selection of the continuation affordance 1405, the electronic device 1400 displays a selection interface 1410 on the display 1402 (e.g., replacing the display of the prompt interface 1404 with the selection interface 1410), as shown in FIG. 14B. The selection interface 1410 includes user affordances 1410A, 1410B, 1410C, each of which corresponds to a user account in some embodiments. By way of example, the user affordance 1410A corresponds to a user account of user Jane Appleseed, the user affordance 1410B corresponds to a user account of user Johnny Appleseed, and the user affordance 1410C corresponds to a user account of user Emma Appleseed. Selection interface 1410 further includes an invitation affordance 1411 and a delay affordance 1412. The delay affordance 1412, when selected, causes the electronic device 1400 to stop displaying the prompt interface 1410 and, optionally, to re-display the prompt interface 1406 (e.g., after a predetermined period of time) if a predetermined time has passed since the prompt interface 1406 was last displayed.

[0375] In some examples, one or more of the users of the selection interface 1410 may be selected. By way of example, in response to a selection of a user affordance, a user corresponding to user affordance 1410A is selected. As shown in FIG. 14C, in response to a selection of user affordance 1410A (e.g., input 1413), a selection indicator 1415 is displayed indicating that a user associated with user affordance 1410A (e.g., "Jane Applewood") has been selected.

[0376] In some examples, one or more user affordances of the selection interface 1410 can be hidden (e.g., not fully displayed). User affordance 1410C of the selection interface 1410 is partially displayed, for example, in FIG. 14C. Thus, in some examples, a user can provide a set of inputs to reveal a hidden portion of the selection interface 1410 including one or more additional user affordances. As shown in FIG. 14C, in response to an input (e.g., a swipe gesture) 1414, the electronic device 1400 reveals a hidden portion of the selection interface 1410, as shown in FIG. 14D. As shown, revealing the hidden portion of the selection interface 1410 results in the electronic device displaying user affordance 1410C.

[0377] While displaying the selection interface 1410, the electronic device detects a selection of an invite affordance 1412. As shown in FIG. 14D , the selection of the invite affordance 1412 is, optionally, a tap gesture 1417. In response to the selection of the invite affordance 1412, the electronic device 1400 invites each of the users selected in the selection interface 1410 to the location profile. In the scenario shown in FIG. 14D , where user Jane Appleseed is selected, the electronic device 1400 invites user Jane Appleseed to add her user account to the location profile.

[0378] In some embodiments, the electronic device can identify users who have been invited to the location profile but have not yet responded to the invitation. By way of example, FIG. 14E illustrates a home interface 1403 of a home control application. The home interface 1420 includes user affordances 1421 and 1422, each of which corresponds to a respective user. For example, user affordance 1421 corresponds to user John Appleseed ("John A") and user affordance 1422 corresponds to user Jane Appleseed ("Jane A"). The home interface 1420 further includes an indicator 1423 indicating that, for example, in response to selection of invitation affordance 1412, the user corresponding to user affordance 1422 has been invited to the location profile but has not yet responded to the invitation.

[0379] While displaying the home interface 1420, the electronic device detects a selection of a user affordance 1422. As shown in FIG. 14E, the selection of the invitation affordance 1422 is, optionally, a tap gesture 1424. In response to the selection of the user affordance 1422, the electronic device 1400 displays on the display 1402 a user account interface 1430 for a user (e.g., "Jane Appleseed") associated with the user affordance 1422 (e.g., replacing the display of the home interface 1420 with the user account interface 1430). As indicated by indicator 1431, user Jane Appleseed has been invited to add her user account to the location profile.

[0380] 15 is a flow diagram illustrating a method for adding a user to a location profile using an electronic device, according to some embodiments. Method 1500 is performed on a device (e.g., 100, 300, 500, 580, 600) having a display device and one or more input devices. The device, in some embodiments, is associated with a first account of a first set of accounts (e.g., a cloud-based family account). Some operations of method 1500 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0381] As described below, the method 1500 provides an intuitive way to add a user to a location profile. This method reduces the cognitive burden on the user when adding a user to a location profile, thereby creating a more efficient human-machine interface. For example, by prompting the user to invite a user account of the first set of user accounts to the second set of user accounts only if the user account is not included in the second set of user accounts, the user is allowed to invite the user to the second set of accounts efficiently and intuitively. As an example, ensuring that the user account is not part of the second set of user accounts would unnecessarily provide a prompt to the user and / or provide an invitation to a set of user accounts in which the user account is already included. This then reduces the number of inputs and time required for the user to operate the electronic device (e.g., by assisting the user to provide appropriate inputs and reducing user errors when operating / interacting with the device), and further reduces power usage and improves the battery life of the device.

[0382] In some embodiments, pursuant to a determination (1502) that the first set of accounts includes at least one account (e.g., a member of a smart home that includes the first account) that is not included in the second set of accounts (e.g., associated with a geographic location), the electronic device (e.g., 1400) displays (1504) on a display device (e.g., 1402) a prompt (e.g., 1404, 1410) inviting the at least one account to join the second set of accounts.

[0383] In some embodiments, after displaying the prompt (1506) (e.g., after selecting “Invite to iCloud Family” or a continue affordance in the prompt), the electronic device receives (1508) one or more sets of inputs (e.g., 1407, 1413, 1414, 1417) via one or more input devices.

[0384] In some embodiments, after displaying the prompt (1506), in response to receiving a set of one or more inputs (e.g., in response to selecting “send invitation”), the electronic device sends (1510) an invitation to join the second set of accounts to a selection of at least one account not included in the second set of accounts.

[0385] In some embodiments, pursuant to a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts, the electronic device refrains from displaying (1512) a prompt on the display device to invite the at least one account to join the second set of accounts.

[0386] In some embodiments, prior to sending the invitation, the electronic device receives input (e.g., 1413) (e.g., a selection of an affordance) via one or more input devices corresponding to a selection of one or more representations (e.g., affordances) representing a selection of at least one account not included in the second set of account...

Claims

1. 1. A computer-implemented method comprising:

1. An electronic device having a display device and one or more input devices, the electronic device being associated with a first account of a first set of accounts, comprising: In response to a determination that the first set of accounts includes at least one account that is not included in a second set of accounts that includes the first account, displaying on the display device a prompt inviting the at least one account to join the second set of accounts; After displaying the prompt, receiving a set of one or more inputs via the one or more input devices; In response to receiving the set of one or more inputs, sending an invitation to join the second set of accounts to a selection of the at least one account not included in the second set of accounts; and refraining from displaying, on the display device, the prompt inviting the at least one account to join the second set of accounts in accordance with a determination that the first set of accounts does not include at least one account that is not included in the second set of accounts; A method comprising:

2. 2. The computer-implemented method of claim 1, further comprising receiving, prior to sending the invitation, via the one or more input devices, input corresponding to a selection of one or more representations representing the selection of the at least one account not included in the second set of accounts.

3. displaying, on the display device, an interface including one or more affordances corresponding to the at least one account not included in the second set of accounts; receiving, via the one or more input devices, input associated with the one or more affordances; In response to receiving the input associated with the one or more affordances, navigating the one or more affordances to display at least one previously undisplayed affordance corresponding to the at least one account not included in the second set of accounts; 3. The computer implemented method of claim 1 or 2, further comprising:

4. displaying, on the display device, an interface including one or more options for configuring one or more permissions of the selected account of the at least one account, further after displaying the prompt and after sending the invitation; receiving input via the one or more input devices corresponding to a request to change a first privilege setting for the account from a first state to a second state; in response to receiving the input corresponding to the request to change the first privilege setting from the first state to the second state, causing the first privilege setting for the account to change from the first state to the second state; The computer implemented method of claim 1 , further comprising:

5. A computer program product causing a computer to carry out the computer implemented method of any one of claims 1 to 4.

6. 1. An electronic device comprising: A memory for storing the computer program of claim 5; one or more processors capable of executing the computer programs stored in the memory; The electronic device has a display device and one or more input devices, the electronic device being associated with a first account of a first set of accounts.

7. an electronic device having a display device and one or more input devices, the electronic device being associated with a first account of a first set of accounts; 5. An electronic device comprising means for executing the computer-implemented method of any one of claims 1 to 4.

Images