PATENT DOCUMENT

Publication Number: US-11784956-B2
Application Number: US-202217874159-A
Country: US
Kind Code: B2

Title: Requests to add assets to an asset account

Abstract:
The present disclosure generally relates to user interfaces for requesting assets be added to an asset account.

Claims:
What is claimed is: 
     
       1. A computer system configured to communicate with a display generation component and one or more input devices and is associated with a first user account, a second user account, and a first asset account, wherein the second user account is associated with an external computer system, and wherein the first user account and the second user account are associated with different users, comprising:
 one or more processors; and 
 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 first user interface, wherein:
 the first user interface includes a first request user-interactive graphical element: 
 in accordance with a determination that the computer system is associated with a second asset account, wherein the second asset account includes assets that can be transferred to the first asset account, the first user interface includes a transfer asset user-selectable graphical element that, when selected, initiates a process for transferring assets from the second asset account to the first asset account; and 
 in accordance with a determination that the computer system is not associated with the second asset account, the first user interface does not include a transfer asset user-configurable graphical element; 
 
 while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to the first asset account, wherein the request to add assets to the first asset account includes a user input corresponding to the first request user-interactive graphical element; 
 in response to receiving the request to add assets to the first asset account, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with:
 contact information for the second user account that designates the second user account as a recipient of the message; and 
 a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the first asset account; 
 
 while displaying the preview of the message, receiving, via the one or more input devices, a request to transmit the message; and 
 in response to receiving the request to transmit the message, transmitting the message to the second user account at the external computer system. 
 
 
     
     
       2. The computer system of  claim 1 , wherein the one or more programs further include instructions for:
 receiving, via the one or more input devices, a user input corresponding to the transfer asset user-selectable graphical element; and 
 in response to receiving the user input corresponding to the transfer asset user-selectable graphical element, initiating the process for transferring assets from the second asset account to the first asset account. 
 
     
     
       3. The computer system of  claim 1 , wherein the one or more programs further include instructions for:
 displaying, via the display generation component, a second user interface, wherein displaying the second user interface includes:
 in accordance with a determination that the computer system is not currently in a paired relationship of a first type with an external device, displaying a second request user-interactive graphical element; and 
 in accordance with a determination the computer system is currently in a paired relationship of the first type with an external device, forgoing displaying the second request user-interactive graphical element; and 
 
 wherein the request to add assets is a user input corresponding to the second request user-interactive graphical element. 
 
     
     
       4. The computer system of  claim 1 , wherein the preview of the message is generated without providing an option to specify an amount of assets to be requested. 
     
     
       5. The computer system of  claim 1 , wherein the one or more programs further include instructions for:
 displaying, concurrently with the preview of the message, a set of one or more user-interactive graphical elements that, when selected, adds text to the message. 
 
     
     
       6. The computer system of  claim 1 , wherein the one or more programs further include instructions for:
 after transmitting the message to the second user account, receiving a first set of one or more user inputs that correspond to a request to display a message transcript of a message conversation between the first user account and the second user account; and 
 in response to receiving the first set of one or more user inputs, displaying the message transcript of the message conversation between the first user account and the second user account, wherein the message transcript includes the message. 
 
     
     
       7. The computer system of  claim 6 , wherein:
 prior to receiving an indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a first appearance; and 
 after receiving the indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a second appearance, different than the first appearance. 
 
     
     
       8. The computer system of  claim 1 , wherein transmitting the message to the second user account includes transmitting data indicating a current asset balance of the first asset account to the second user account. 
     
     
       9. The computer system of  claim 1 , wherein the request to add assets is received while displaying a third user interface that concurrently includes:
 an indication of a first detail of the first asset account; and 
 an indication of a second detail of the first asset account, different from the first detail. 
 
     
     
       10. The computer system of  claim 1 , wherein the process to add assets to the first asset account includes the external computer system displaying an asset addition user interface that includes a set of one or more user-interactive graphical elements that, when selected, determines an amount of assets to be added to the first asset account. 
     
     
       11. The computer system of  claim 10 , wherein the asset addition user interface of the external computer system includes:
 an indication of a current asset balance of the first asset account, prior to completion of the process to add assets to the first asset account; and 
 an indication of a future balance of the first asset account, after completion of the process to add assets to the first asset account. 
 
     
     
       12. The computer system of  claim 10 , wherein the asset addition user interface of the external computer system includes:
 an indication identifying the first user account; and 
 an indication identifying the first asset account. 
 
     
     
       13. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account, a second user account, and a first asset account, wherein the second user account is associated with an external computer system, and wherein the first user account and the second user account are associated with different users, the one or more programs including instructions for:
 displaying a first user interface, wherein:
 the first user interface includes a first request user-interactive graphical element; 
 in accordance with a determination that the computer system is associated with a second asset account, wherein the second asset account includes assets that can be transferred to the first asset account, the first user interface includes a transfer asset user-selectable graphical element that, when selected, initiates a process for transferring assets from the second asset account to the first asset account; and 
 in accordance with a determination that the computer system is not associated with the second asset account, the first user interface does not include a transfer asset user-configurable graphical element; 
 
 while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to the first asset account, wherein the request to add assets to the first asset account includes a user input corresponding to the first request user-interactive graphical element; 
 in response to receiving the request to add assets to the first asset account, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with:
 contact information for the second user account that designates the second user account as a recipient of the message; and 
 a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the first asset account; 
 
 while displaying the preview of the message, receiving, via the one or more input devices, a request to transmit the message; and 
 in response to receiving the request to transmit the message, transmitting the message to the second user account at the external computer system. 
 
     
     
       14. The non-transitory computer-readable storage medium of  claim 13 , wherein the one or more programs further include instructions for:
 receiving, via the one or more input devices, a user input corresponding to the transfer asset user-selectable graphical element; and 
 in response to receiving the user input corresponding to the transfer asset user-selectable graphical element, initiating the process for transferring assets from the second asset account to the first asset account. 
 
     
     
       15. The non-transitory computer-readable storage medium of  claim 13 , wherein the one or more programs further include instructions for:
 displaying, via the display generation component, a second user interface, wherein displaying the second user interface includes:
 in accordance with a determination that the computer system is not currently in a paired relationship of a first type with an external device, displaying a second request user-interactive graphical element; and 
 in accordance with a determination the computer system is currently in a paired relationship of the first type with an external device, forgoing displaying the second request user-interactive graphical element; and 
 
 wherein the request to add assets is a user input corresponding to the second request user-interactive graphical element. 
 
     
     
       16. The non-transitory computer-readable storage medium of  claim 13 , wherein the preview of the message is generated without providing an option to specify an amount of assets to be requested. 
     
     
       17. The non-transitory computer-readable storage medium of  claim 13 , wherein the one or more programs further include instructions for:
 displaying, concurrently with the preview of the message, a set of one or more user-interactive graphical elements that, when selected, adds text to the message. 
 
     
     
       18. The non-transitory computer-readable storage medium of  claim 13 , wherein the one or more programs further include instructions for:
 after transmitting the message to the second user account, receiving a first set of one or more user inputs that correspond to a request to display a message transcript of a message conversation between the first user account and the second user account; and 
 in response to receiving the first set of one or more user inputs, displaying the message transcript of the message conversation between the first user account and the second user account, wherein the message transcript includes the message. 
 
     
     
       19. The non-transitory computer-readable storage medium of  claim 18 , wherein:
 prior to receiving an indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a first appearance; and 
 after receiving the indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a second appearance, different than the first appearance. 
 
     
     
       20. The non-transitory computer-readable storage medium of  claim 13 , wherein transmitting the message to the second user account includes transmitting data indicating a current asset balance of the first asset account to the second user account. 
     
     
       21. The non-transitory computer-readable storage medium of  claim 13 , wherein the request to add assets is received while displaying a third user interface that concurrently includes:
 an indication of a first detail of the first asset account; and 
 an indication of a second detail of the first asset account, different from the first detail. 
 
     
     
       22. The non-transitory computer-readable storage medium of  claim 13 , wherein the process to add assets to the first asset account includes the external computer system displaying an asset addition user interface that includes a set of one or more user-interactive graphical elements that, when selected, determines an amount of assets to be added to the first asset account. 
     
     
       23. The non-transitory computer-readable storage medium of  claim 22 , wherein the asset addition user interface of the external computer system includes:
 an indication of a current asset balance of the first asset account, prior to completion of the process to add assets to the first asset account; and 
 an indication of a future balance of the first asset account, after completion of the process to add assets to the first asset account. 
 
     
     
       24. The non-transitory computer-readable storage medium of  claim 22 , wherein the asset addition user interface of the external computer system includes:
 an indication identifying the first user account; and 
 an indication identifying the first asset account. 
 
     
     
       25. A method, comprising:
 at a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account, a second user account, and a first asset account, wherein the second user account is associated with an external computer system, and wherein the first user account and the second user account are associated with different users:
 displaying a first user interface, wherein:
 the first user interface includes a first request user-interactive graphical element; 
 in accordance with a determination that the computer system is associated with a second asset account, wherein the second asset account includes assets that can be transferred to the first asset account, the first user interface includes a transfer asset user-selectable graphical element that, when selected, initiates a process for transferring assets from the second asset account to the first asset account; and 
 in accordance with a determination that the computer system is not associated with the second asset account, the first user interface does not include a transfer asset user-configurable graphical element; 
 
 while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to the first asset account, wherein the request to add assets to the first asset account includes a user input corresponding to the first request user-interactive graphical element; 
 in response to receiving the request to add assets to the first asset account, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with:
 contact information for the second user account that designates the second user account as a recipient of the message; and 
 a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the first asset account; 
 
 while displaying the preview of the message, receiving, via the one or more input devices, a request to transmit the message; and 
 in response to receiving the request to transmit the message, transmitting the message to the second user account at the external computer system. 
 
 
     
     
       26. The method of  claim 25 , further comprising:
 receiving, via the one or more input devices, a user input corresponding to the transfer asset user-selectable graphical element; and 
 in response to receiving the user input corresponding to the transfer asset user-selectable graphical element, initiating the process for transferring assets from the second asset account to the first asset account. 
 
     
     
       27. The method of  claim 25 , further comprising:
 displaying, via the display generation component, a second user interface, wherein displaying the second user interface includes:
 in accordance with a determination that the computer system is not currently in a paired relationship of a first type with an external device, displaying a second request user-interactive graphical element; and 
 in accordance with a determination the computer system is currently in a paired relationship of the first type with an external device, forgoing displaying the second request user-interactive graphical element; and 
 
 wherein the request to add assets is a user input corresponding to the second request user-interactive graphical element. 
 
     
     
       28. The method of  claim 25 , wherein the preview of the message is generated without providing an option to specify an amount of assets to be requested. 
     
     
       29. The method of  claim 25 , further comprising:
 displaying, concurrently with the preview of the message, a set of one or more user-interactive graphical elements that, when selected, adds text to the message. 
 
     
     
       30. The method of  claim 25 , further comprising:
 after transmitting the message to the second user account, receiving a first set of one or more user inputs that correspond to a request to display a message transcript of a message conversation between the first user account and the second user account; and 
 in response to receiving the first set of one or more user inputs, displaying the message transcript of the message conversation between the first user account and the second user account, wherein the message transcript includes the message. 
 
     
     
       31. The method of  claim 30 , wherein:
 prior to receiving an indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a first appearance; and 
 after receiving the indication that the process to add assets to the first asset account is completed, the message is displayed in the message transcript with a second appearance, different than the first appearance. 
 
     
     
       32. The method of  claim 25 , wherein transmitting the message to the second user account includes transmitting data indicating a current asset balance of the first asset account to the second user account. 
     
     
       33. The method of  claim 25 , wherein the request to add assets is received while displaying a third user interface that concurrently includes:
 an indication of a first detail of the first asset account; and 
 an indication of a second detail of the first asset account, different from the first detail. 
 
     
     
       34. The method of  claim 25 , wherein the process to add assets to the first asset account includes the external computer system displaying an asset addition user interface that includes a set of one or more user-interactive graphical elements that, when selected, determines an amount of assets to be added to the first asset account. 
     
     
       35. The method of  claim 34 , wherein the asset addition user interface of the external computer system includes:
 an indication of a current asset balance of the first asset account, prior to completion of the process to add assets to the first asset account; and 
 an indication of a future balance of the first asset account, after completion of the process to add assets to the first asset account. 
 
     
     
       36. The method of  claim 34 , wherein the asset addition user interface of the external computer system includes:
 an indication identifying the first user account; and 
 an indication identifying the first asset account.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to: U.S. Provisional Application Ser. No. 63/246,288, entitled “REQUESTS TO ADD ASSETS TO AN ASSET ACCOUNT,” filed Sep. 20, 2021; and U.S. Provisional Application Ser. No. 63/345,343, entitled “REQUESTS TO ADD ASSETS TO AN ASSET ACCOUNT,” filed May 24, 2022, the contents of each of which are hereby incorporated by reference in their entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to techniques for requesting the addition of assets to an asset account. 
     BACKGROUND 
     Assets accounts can be provisioned onto computer systems. For example, an asset account can include printing assets that enable a user to perform print operations. For another example, an asset account can include photo assets that enable a user to store photos. Such assets accounts may need to be replenished with assets so that the user of the computer system can continue to use the account. 
     BRIEF SUMMARY 
     Some techniques for requesting the addition of assets to an asset account using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Some technique do not enable a user to request assets from a different user, or require the user to provide user inputs to specify the user from which assets should be requested. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices. 
     Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for requesting the addition of assets to an asset account. Such methods and interfaces optionally complement or replace other methods for requesting the addition of assets to an asset account. Such methods and interfaces reduce the number of inputs required, reduce the cognitive burden on a user, and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In accordance with some embodiments, a method is disclosed. The method is performed at a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system. The method comprises: while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and in response to receiving the request to add assets, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     In accordance with some embodiments, a non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system, the one or more programs including instructions for: while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and in response to receiving the request to add assets, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     In accordance with some embodiments, a transitory computer-readable storage medium is disclosed. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system, the one or more programs including instructions for: while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and in response to receiving the request to add assets, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     In accordance with some embodiments, a computer system is disclosed. The computer system is configured to communicate with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system, comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and in response to receiving the request to add assets, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     In accordance with some embodiments, a computer system is disclosed. The computer system is configured to communicate with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system, comprising: means, while the first user account is logged in at the computer system, for receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and means, responsive to receiving the request to add assets, for displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     In accordance with some embodiments, a computer program product is disclosed. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices and is associated with a first user account and a second user account, wherein the second user account is associated with an external computer system, the one or more programs including instructions for: while the first user account is logged in at the computer system, receiving, via the one or more input devices, a request to add assets to an asset account that is associated with the computer system; and in response to receiving the request to add assets, displaying, via the display generation component, a preview of a message, wherein the message is prepopulated with: contact information for the second user account that designates the second user account as the recipient of the message; and a user-interactive graphical user interface object, that, when selected at the external computer system, initiates a process to add assets to the asset account. 
     Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. 
     Thus, devices are provided with faster, more efficient methods and interfaces for requesting the addition of assets to an asset account, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for requesting the addition of assets to an asset account. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG.  1 A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. 
         FIG.  1 B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. 
         FIG.  2    illustrates a portable multifunction device having a touch screen in accordance with some embodiments. 
         FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. 
         FIG.  4 A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG.  4 B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG.  5 A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG.  5 B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIGS.  6 A- 6 C  illustrate exemplary devices and user interfaces for requesting assets be added to an asset account, in accordance with some embodiments. 
         FIGS.  7 A- 7 O  illustrate exemplary devices and user interfaces for requesting assets be added to an asset account, in accordance with some embodiments. 
         FIG.  8    is a flow diagram illustrating methods of requesting assets be added to an asset account, in accordance with some embodiments. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments. 
     There is a need for electronic devices that provide efficient methods and interfaces for adding assets to an asset account. Such techniques can reduce the cognitive burden on a user who requests assets and/or adds assets to an asset account, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. 
     Below,  FIGS.  1 A- 1 B,  2 ,  3 ,  4 A- 4 B, and  5 A- 5 B  provide a description of exemplary devices for performing the techniques for adding assets to an asset account.  FIGS.  6 A- 6 C  illustrate exemplary user interfaces for requesting assets be added to an asset account.  FIGS.  7 A- 7 O  illustrate exemplary user interfaces for requesting assets be added to an asset account.  FIG.  8    is a flow diagram illustrating methods of requesting assets be added to an asset account in accordance with some embodiments. The user interfaces in  FIGS.  6 A- 6 C and  7 A- 7 O  are used to illustrate the processes described below, including the processes in  FIG.  8   . 
     The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed. 
     Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, the first touch and the second touch are both touches, but they are not the same touch. 
     The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses 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,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. 
     The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed 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],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller  156 ) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content. 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, 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. 
     The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application. 
     The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user. 
     Attention is now directed toward embodiments of portable devices with touch-sensitive displays.  FIG.  1 A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive display system  112  in accordance with some embodiments. Touch-sensitive display  112  is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device  100  includes memory  102  (which optionally includes one or more computer-readable storage mediums), 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  for detecting intensity of contacts 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  for generating tactile outputs on device  100  (e.g., generating tactile outputs 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 . 
     As used in the specification and 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 to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least  256 ). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;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 physical characteristics of the device or the 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 will feel a tactile sensation such as an “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&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large 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 stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  100  is only one example of a portable multifunction device, and that device  100  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG.  1 A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  102  optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller  122  optionally controls access to memory  102  by other components of device  100 . 
     Peripherals interface  118  can be used to couple input and output peripherals of the device to CPU  120  and memory  102 . The one or more processors  120  run or execute various software programs (such as computer programs (e.g., including instructions)) and/or sets of instructions stored in memory  102  to perform various functions for device  100  and to process data. In some embodiments, peripherals interface  118 , CPU  120 , and memory controller  122  are, optionally, implemented on a single chip, such as chip  104 . In some other embodiments, they are, optionally, implemented on separate chips. 
     RF (radio frequency) circuitry  108  receives and sends RF signals, also called electromagnetic signals. RF circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  108  optionally includes well-known circuitry 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, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  108  optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data is, optionally, retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG.  2   ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , depth camera controller  169 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to 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, and so forth. In some embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG.  2   ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG.  2   ). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors  164  and/or one or more depth camera sensors  175 ), such as for tracking a user&#39;s gestures (e.g., hand gestures and/or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independently of an input element that is a part of the device) and is based on detected motion of a portion of the user&#39;s body through the air including motion of the user&#39;s body relative to an absolute reference (e.g., an angle of the user&#39;s arm relative to the ground or a distance of the user&#39;s hand relative to the ground), relative to another portion of the user&#39;s body (e.g., movement of a hand of the user relative to a shoulder of the user, movement of one hand of the user relative to another hand of the user, and/or movement of a finger of the user relative to another finger or portion of a hand of the user), and/or absolute motion of a portion of the user&#39;s body (e.g., a tap gesture that includes movement of a hand in a predetermined pose by a predetermined amount and/or speed, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user&#39;s body). 
     A quick press of the push button optionally disengages a lock of touch screen  112  or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) optionally turns power to device  100  on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  112 . In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen  112  and display controller  156  optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  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, California. 
     A touch-sensitive display in some embodiments of touch screen  112  is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  112  displays visual output from device  100 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  112  is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  112  optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  optionally also includes one or more optical sensors  164 .  FIG.  1 A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical sensor  164  optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device  100 , opposite touch screen display  112  on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  164  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  164  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more depth camera sensors  175 .  FIG.  1 A  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) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module  143  (also called a camera module), depth camera sensor  175  is optionally used to determine a depth map of different portions of an image captured by the imaging module  143 . In some embodiments, a depth camera sensor is located on the front of device  100  so that the user&#39;s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor  175  is located on the back of device, or on the back and the front of the device  100 . In some embodiments, the position of depth camera sensor  175  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor  175  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG.  1 A  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, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  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 collocated 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 touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more proximity sensors  166 .  FIG.  1 A  shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  is, optionally, coupled to input controller  160  in I/O subsystem  106 . Proximity sensor  166  optionally performs as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen  112  when the multifunction device is placed near the user&#39;s ear (e.g., when the user is making a phone call). 
     Device  100  optionally also includes one or more tactile output generators  167 .  FIG.  1 A  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 a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  165  receives tactile feedback generation instructions from haptic feedback module  133  and generates tactile outputs on device  100  that are capable of being sensed by a user of device  100 . In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device  100 ) or laterally (e.g., back and forth in the same plane as a surface of device  100 ). In some embodiments, at least one tactile output generator sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more accelerometers  168 .  FIG.  1 A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  is, optionally, coupled to an input controller  160  in I/O subsystem  106 . Accelerometer  168  optionally performs 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 by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  100  optionally includes, in addition to accelerometer(s)  168 , a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG.  1 A ) or  370  ( FIG.  3   ) stores device/global internal state  157 , as shown in  FIGS.  1 A and  3   . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     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 for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/motion module  130  optionally detects contact with touch screen  112  (in conjunction with display controller  156 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  130  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  130  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some embodiments, contact/motion module  130  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  100 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  130  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, 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 (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which is, optionally, a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , IM  141 , browser  147 , and any other application that needs text input). 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  138  for use in location-based dialing; to camera  143  as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Applications  136  optionally include the following modules (or sets of instructions), or a subset or superset thereof:
         Contacts module  137  (sometimes called an address book or contact list);   Telephone module  138 ;   Video conference module  139 ;   E-mail client module  140 ;   Instant messaging (IM) module  141 ;   Workout support module  142 ;   Camera module  143  for still and/or video images;   Image management module  144 ;   Video player module;   Music player module;   Browser module  147 ;   Calendar module  148 ;   Widget modules  149 , which optionally include one or more of: weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , dictionary widget  149 - 5 , and other widgets obtained by the user, as well as user-created widgets  149 - 6 ;   Widget creator module  150  for making user-created widgets  149 - 6 ;   Search module  151 ;   Video and music player module  152 , which merges video player module and music player module;   Notes module  153 ;   Map module  154 ; and/or   Online video module  155 .       

     Examples of other applications  136  that are, 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 replication. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , contacts module  137  are, optionally, used to manage an address book or contact list (e.g., stored in application internal state  192  of contacts module  137  in memory  102  or memory  370 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  138 , video conference module  139 , e-mail  140 , or IM  141 ; and so forth. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , telephone module  138  are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module  137 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , optical sensor  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , text input module  134 , contacts module  137 , and telephone module  138 , video conference module  139  includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , e-mail client module  140  includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module  144 , e-mail client module  140  makes it very easy to create and send e-mails with still or video images taken with camera module  143 . 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , the instant messaging module  141  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , map module  154 , and music player module, workout support module  142  includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 
     In conjunction with touch screen  112 , display controller  156 , optical sensor(s)  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , and image management module  144 , camera module  143  includes executable instructions to capture still images or video (including a video stream) and store them into memory  102 , modify characteristics of a still image or video, or delete a still image or video from memory  102 . 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and camera module  143 , image management module  144  includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , browser module  147  includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , e-mail client module  140 , and browser module  147 , calendar module  148  includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , widget modules  149  are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , and dictionary widget  149 - 5 ) or created by the user (e.g., user-created widget  149 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , the widget creator module  150  are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , search module  151  includes executable instructions to search for text, music, sound, image, video, and/or other files in memory  102  that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , and browser module  147 , video and music player module  152  includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen  112  or on an external, connected display via external port  124 ). In some embodiments, device  100  optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , notes module  153  includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , and browser module  147 , map module  154  are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , text input module  134 , e-mail client module  140 , and browser module  147 , online video module  155  includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port  124 ), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module  141 , rather than e-mail client module  140 , is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 
     Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module  152 ,  FIG.  1 A ). In some embodiments, memory  102  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  102  optionally stores additional modules and data structures not described above. 
     In some embodiments, device  100  is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  100 , the number of physical input control devices (such as push buttons, dials, and the like) on device  100  is, optionally, reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  100  to a main, home, or root menu from any user interface that is displayed on device  100 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG.  1 B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  ( FIG.  1 A ) or  370  ( FIG.  3   ) includes event sorter  170  (e.g., in operating system  126 ) and a respective application  136 - 1  (e.g., any of the aforementioned applications  137 - 151 ,  155 ,  380 - 390 ). 
     Event sorter  170  receives event information and determines the application  136 - 1  and application view  191  of application  136 - 1  to which to deliver the event information. Event sorter  170  includes event monitor  171  and event dispatcher module  174 . In some embodiments, application  136 - 1  includes application internal state  192 , which indicates the current application view(s) displayed on touch-sensitive display  112  when the application is active or executing. In some embodiments, device/global internal state  157  is used by event sorter  170  to determine which application(s) is (are) currently active, and application internal state  192  is used by event sorter  170  to determine application views  191  to which to deliver event information. 
     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 that indicates information being displayed or that is ready for display by application  136 - 1 , a state queue for enabling the user to go back to a prior state or view of application  136 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  171  receives event information from peripherals interface  118 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  112 , as part of a multi-touch gesture). Peripherals interface  118  transmits information it receives from I/O subsystem  106  or a sensor, such as proximity sensor  166 , accelerometer(s)  168 , and/or microphone  113  (through 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. 
     In some embodiments, event monitor  171  sends requests to the 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., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     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 hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     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 a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of 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, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  optionally utilizes or calls data updater  176 , object updater  177 , or GUI updater  178  to update the 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 data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective 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 event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which optionally include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event  1  ( 187 - 1 ), event  2  ( 187 - 2 ), and others. In some embodiments, sub-events in an event (e.g.,  187 - 1  and/or  187 - 2 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event  1  ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event  2  ( 187 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  112 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event definitions  186  include a definition of an event for a respective user-interface object. In some embodiments, event comparator  184  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 187 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, 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 event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module. In some embodiments, object updater  177  creates and updates objects used in application  136 - 1 . For example, object updater  177  creates a new user-interface object or updates the position of a user-interface object. GUI updater  178  updates the GUI. For example, GUI updater  178  prepares display information and sends it to graphics module  132  for display on a touch-sensitive display. 
     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. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  100  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG.  2    illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  optionally also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  is, optionally, used to navigate to any application  136  in a set of applications that are, optionally, executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     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 adjustment button(s)  208 , subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with 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&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device  300  typically includes one or more processing units (CPUs)  310 , one or more network or other communications interfaces  360 , memory  370 , and one or more communication buses  320  for interconnecting these components. Communication buses  320  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  300  includes input/output (I/O) interface  330  comprising display  340 , which is typically a touch screen display. I/O interface  330  also optionally includes a keyboard and/or mouse (or other pointing device)  350  and touchpad  355 , tactile output generator  357  for generating tactile outputs on device  300  (e.g., similar to tactile output generator(s)  167  described above with reference to  FIG.  1 A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG.  1 A ). 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 remotely located from CPU(s)  310 . In some embodiments, memory  370  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  102  of portable multifunction device  100  ( FIG.  1 A ), or a subset thereof. Furthermore, 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 , while memory  102  of portable multifunction device  100  ( FIG.  1 A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG.  3    is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or computer programs (e.g., sets of instructions or including instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory  370  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  370  optionally stores additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device  100 . 
       FIG.  4 A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces are, 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 ;   Battery status indicator  406 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Messages;”   Icon  426  for calendar module  148 , labeled “Calendar;”   Icon  428  for image management module  144 , labeled “Photos;”   Icon  430  for camera module  143 , labeled “Camera;”   Icon  432  for online video module  155 , labeled “Online Video;”   Icon  434  for stocks widget  149 - 2 , labeled “Stocks;”   Icon  436  for map module  154 , labeled “Maps;”   Icon  438  for weather widget  149 - 1 , labeled “Weather;”   Icon  440  for alarm clock widget  149 - 4 , labeled “Clock;”   Icon  442  for workout support module  142 , labeled “Workout Support;”   Icon  444  for notes module  153 , labeled “Notes;” and   Icon  446  for a settings application or module, labeled “Settings,” which provides access to settings for device  100  and its various applications  136 .   
               

     It should be noted that the icon labels illustrated in  FIG.  4 A  are merely exemplary. For example, icon  422  for video and music player module  152  is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG.  4 B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG.  3   ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG.  3   ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples that follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG.  4 B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) has a primary axis (e.g.,  452  in  FIG.  4 B ) that corresponds to a primary axis (e.g.,  453  in  FIG.  4 B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG.  4 B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG.  4 B,  460    corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG.  4 B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), 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., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG.  5 A  illustrates exemplary personal electronic device  500 . Device  500  includes 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.  1 A- 4 B ). In some embodiments, device  500  has 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. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety. 
     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 permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device  500  to be worn by a user. 
       FIG.  5 B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS.  1 A,  1 B , and  3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, intensity sensor  524  (e.g., contact intensity sensor). In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  is, optionally, a button, in some examples. 
     Input mechanism  508  is, optionally, a microphone, in some examples. Personal electronic device  500  optionally includes various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including process  800  ( FIG.  8   ). 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 the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG.  5 B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS.  1 A,  3 , and  5 A- 5 B ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG.  3    or touch-sensitive surface  451  in  FIG.  4 B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG.  1 A  or touch screen  112  in  FIG.  4 A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. 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 operation has been performed by a 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 with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation. 
     Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIGS.  6 A- 6 C  illustrate exemplary user interfaces for requesting assets be added to an asset account, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  8   . At  FIG.  6 A , computer system  500  is displaying user interface  602 , which displays information about an asset account. Computer system  500  is not associated with (e.g., not paired with) a phone (e.g., a smart phone). For example, computer system  500  is being used by a child (or dependent) that does not have a phone and the child is logged into computer system  500  using the child&#39;s user account. Computer system  500  is also associated with a user account of a trusted individual, such as a parent (or guardian) of the child. For another example, computer system  500  is being used by an adult that has a phone that is not compatible for pairing with computer system  500  (e.g., computer system  500  and the adult&#39;s phone are manufactured by different entities and/or have operating systems provided by different entities) and computer system  500  is associated with a user account of a trusted individual, such as a spouse or other family member of the adult. 
     At  FIG.  6 A , user interface  602  includes an indication  604  of the amount of assets associated with (e.g., balance of, available at, stored on, and/or corresponding to) a cloud storage account that is provisioned onto computer system  500 . As illustrated in  FIG.  6 A , the cloud storage account has no space available and therefore cannot be used to store additional data, such as a new video file. At  FIG.  6 A , user interface  602  includes request option  602 A, on which computer system  500  detects input  650 A (e.g., a tap input). In response to detecting input  650 A on request option  602 A, user interface  606  is displayed, as shown in  FIG.  6 B . User interface  602  optionally includes add space option  602 B, on which computer system  500  detects input  650 B (e.g., a tap input). 
       FIG.  6 B  illustrates both computer system  500  of the child and device  100  (also referred to as computer system  100 ) of the parent/guardian. In response to input  650 A on request option  602 A, computer system  500  displays user interface  606 , which includes a preview of a message (e.g., a text message, an email message) that can be transmitted to the parent/guardian to request storage space be added to the cloud storage account. The message preview is prepopulated with contact information  606 A (e.g., a phone number and/or email address) for the parent/guardian and a graphical user interface object  606 B. When selected at device  100  (e.g., selected in a messaging application of the external computer system), graphical user interface object  606 B initiates a process to add space to the cloud storage account. In some embodiments, computer system  500  receives additional text to include in the message (e.g., “I am out of storage space”). As illustrated in  FIG.  6 B , contact information  606 A for the child&#39;s mom (the user of computer system  100 ) and graphical user interface object  606 B are prepopulated in the message. At  FIG.  6 B , computer system  500  detects input  650 C (e.g., a tap input) on send option  606 C, which transmits the message to the parent/guardian and causes display of user interface  608 , as shown in  FIG.  6 C . 
     At  FIG.  6 C , after transmitting message  608 B, computer system  500  displays message  608 B as part of a conversation  608 A between the child (e.g., the user of computer system  500 ) and the parent/guardian (e.g., the user of computer system  100 ). Also at  FIG.  6 C , device  100  displays notification  610  indicating that message  608 B has been received from the child. In this example, notification  610  provides an indication of the sender (e.g., the child named “Emily”) and an indication that the message is a request for the parent/guardian to transfer storage space to the child&#39;s cloud storage account. The child&#39;s cloud storage account is not provisioned onto computer system  100 . At  FIG.  6 C , device  100  detects input  660  (e.g., a tap input by the parent/guardian) on notification  610  that causes device  100  to display the message. 
       FIGS.  7 A- 7 O  illustrate exemplary user interfaces for requesting assets be added to an asset account, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  8   . 
     At  FIG.  7 A , computer system  500  is displaying user interface  702 , which includes icons, which when activated cause display of a corresponding application. Computer system  500  is not associated with (e.g., not paired with) a phone (e.g., a smartphone). For example, computer system  500  is being used by a child (or dependent) that does not have a phone and the child is logged into computer system  500  using the child&#39;s user account. Computer system  500  is also associated with a user account of a trusted individual, such as a parent (or guardian) of the child. For another example, computer system  500  is being used by an adult that has a phone that is not compatible for pairing with computer system  500  (e.g., computer system  500  and the adult&#39;s phone are manufactured by different entities and/or have operating systems provided by different entities) and computer system  500  is associated with a user account of a trusted individual, such as a spouse or other family member of the adult. 
     At  FIG.  7 A , computer system  500  detects input  750 A (e.g., a tap input) on icon  704  for a wallet application. In response to detecting input  750 A, computer system  500  displays user interface  706 , as shown in  FIG.  7 B . In some embodiments,  FIG.  7 B  is displayed in response to computer system  500  being placed into a communication field (e.g., an NFC field) of a contactless terminal (e.g., an NFC-enabled contactless reader, a point-of-sale terminal) and/or receiving a request for assets (e.g., funds, money, and/or travel credits) from the contactless terminal. 
     At  FIG.  7 B , computer system  500  displays representation  710  of a transit account that is provisioned onto computer system  500  and representation  712  of a transfer account provisioned onto computer system  500 . Computer system  500  detects input  750 B (e.g., a tap input) on representation  710 , which causes display of user interface  708 , as shown in  FIG.  7 C . 
     At  FIG.  7 C , user interface  708  includes representation  710  of the transit account, indication  708 A of the amount of assets associated with (e.g., balance of, available at, stored on, and/or corresponding to) the transit account, and a history of at least some past transactions performed using the transit account, such as bus ride  708 B. As illustrated in  FIG.  7 C , the transit account has no funds and therefore cannot be used to ride the transit, such as a bus. At  FIG.  7 C , computer system  500  detects input  750 C (e.g., a tap input) on representation  710 , which causes display of user interface  714 , as shown in  FIG.  7 D . 
     At  FIG.  7 D , user interface  714  includes request option  714 A and optionally includes add funds option  714 B. In some embodiments, add funds option  714 B is not displayed, displayed with a different visual appearance (e.g., greyed out), and/or cannot be activated when computer system  500  is not provisioned with an account capable of transferring assets to the transit account. For example, add funds option  714 B is not displayed when the transit account is the only asset account provisioned on computer system  500 . For another example, add funds option  714 B is not displayed when the only other transfer account (e.g., corresponding to representation  712 ) provisioned on computer system  500  does not have any funds to transfer to the transit account. At  FIG.  7 D , computer system  500  detects an input (e.g., a tap input) on request option  714 A or add funds option  714 B. When computer system  500  detects input  750 D (e.g., a tap input) on request option  714 A, user interface  716  is displayed, as shown in  FIG.  7 D . When computer system  500  detects input  750 E (e.g., a tap input) on add funds option  714 B, user interface  722  is displayed, as shown in  FIG.  7 M . 
       FIG.  7 E  illustrates both computer system  500  of the child and device  100  (also referred to as computer system  100 ) of the parent/guardian. In some embodiments, computer system  100  includes one or more features of devices  300  and/or  500 . At  FIG.  7 E , in response to input  750 D (e.g., a tap input) on request option  714 A, computer system  500  displays a preview of a message (e.g., a text message, an email message) that is prepopulated with contact information (e.g., a phone number and/or email address) for the parent/guardian and a graphical user interface object to send to the parent/guardian, as shown in user interface  716 . The message can be transmitted to the parent/guardian to request funds be added to the transit account. As illustrated in  FIG.  7 E , contact information  716 A for the child&#39;s mom (the user of computer system  100 ) and graphical user interface object  716 B are prepopulated in the message. Graphical user interface object  716 B is an object that, when selected at the parent/guardian&#39;s computer system (e.g., selected in a messaging application of the external computer system), initiates a process to add funds to the transit account. In some embodiments, computer system  500  receives additional text to include as part of the message to the parent/guardian (e.g., “I need funds to ride the bus”). The message is optionally not prepopulated with an amount of funds being requested. Computer system  500  detects input  750 F (e.g., a tap input) on send option  716 C, which transmits the message to the parent/guardian and causes display of user interface  718 , as shown in  FIG.  7 F . 
     At  FIG.  7 F , computer system  500  has transmitted the message and displays the message  718 B as part of conversation  718 A between the user of computer system  500  (e.g., the child) and the parent/guardian (the user of computer system  100 ). As shown in  FIG.  7 F , computer system  100  displays notification  720  indicating that message  718 B has been received from the child. In this example, notification  720  provides an indication of the sender (e.g., the child named “Emily”) and an indication that the message is a request for the parent/guardian to transfer funds to the child&#39;s transit account. The child&#39;s transit account is not provisioned onto computer system  100 . At  FIG.  7 F , computer system  100  detects an input  760 A (e.g., tap input by the parent/guardian) on notification  720  and, in response, displays user interface  770  as shown in  FIG.  7 G . 
     At  FIG.  7 G , user interface  770  includes conversation  770 A between the user of computer system  500  (e.g., the child) and the parent/guardian (the user of computer system  100 ). Conversation  770 A includes graphical user interface object  770 B that was received from computer system  500  and that, when selected at the parent/guardian&#39;s computer system, initiates a process to add funds to the transit account. At  FIG.  7 G , computer system  100  detects user input  760 B (e.g., a tap input) on graphical user interface object  770 B and, in response, displays user interface  772 , as shown in  FIG.  7 H , which includes indication  772 A of the transit account, amount  772 B of funds to be added to the transit account, amount  772 C of funds currently on the transit account, keypad  772 D for entering the amount of funds to be added to the transit account, and indication  772 F (e.g., an image) of the requesting user (e.g., the child). In this example, indication  772 F partially overlays indication  772 A of the transit account. At  FIG.  7 H , computer system  100  has detected input  760 C and updated amount  772 B to reflect a corresponding value. In response to detecting input  760 D on add option  772 E, computer system  100  displays conversation  770 A and includes a draft message to send to computer system  500  that adds funds to the transit account, as shown in  FIG.  7 I . In some embodiments, in response to detecting user input  760 D, computer system  100  replaces display of message  770 B with message  770 C in a draft message portion of user interface  770 . In some embodiments, in response to detecting user input  760 D, computer system  100  changes a visual appearance of message  770 B and/or ceases to display message  770 B in user interface  770 . 
     At  FIG.  7 I , computer system  100  detects input  760 E (e.g., a tap input) on send option  770 D and, in response, displays user interface  774  that is optionally overlaid on user interface  770 , as shown in  FIG.  7 J . User interface  774  enables the user of computer system  100  to select an account  774 A provisioned on computer system  100  from which funds will be transferred, indicates how much funds will be transferred  774 C, and indicates the account (the transit account  774 B) to which the funds will be transferred. 
     At  FIG.  7 J , computer system  100  detects user input  760 F (e.g., a double-press of a hardware button  760 F and/or biometric authentication) to authorize the transfer of funds and, in response (e.g., if the biometric authentication is successful) transmits message  770 C to computer system  500  and updates conversation  770  to indicate that message  770 C has been sent, as shown in  FIG.  7 K . In some embodiments, in response to detecting user input  760 F (e.g., a double-press of a hardware button  760 F and/or biometric authentication), computer system  100  replaces display of message  770 B with message  770 C. In some embodiments, in response to detecting user input  760 F (e.g., a double-press of a hardware button  760 F and/or biometric authentication), computer system  100  changes a visual appearance of message  770 B and/or ceases to display message  770 B. 
     At  FIG.  7 K , computer system  500  has received and displays message  770 C, which indicates funds have been added to the transit account. In some embodiments, message  770 C replaces message  718 B. In some embodiments, computer system  500  changes a visual appearance of message  718 B and/or ceases to display message  718 B when message  770 C is received and/or displayed. 
     At  FIG.  7 L , user interface  708  now indicates that the transit account has funds available. 
     Returning to  FIG.  7 D , in response to input  750 E (e.g., a tap input) on add funds option  714 B, computer system  500  displays user interface  722 , which enables the user to provide inputs to specify the amount of funds to be added to the transit account. Computer system  500  detects input  750 G (e.g., a tap input) and, in response, displays the user interface of  FIG.  7 N , which optionally enables the user to specify the account from which funds should be transferred to the transit account. At  FIG.  7 O , once the user has authorized the transfer of funds, computer system  500  displays that the transit account has the respective amount of funds. 
       FIG.  8    is a flow diagram illustrating a method for requesting assets be added to an asset account using a computer system, in accordance with some embodiments. Method  700  is performed at a computer system (e.g., a smart watch  500 , a smart phone, a personal computer) that is in communication with a display generation component (e.g., an integrated display; a display controller) and one or more input devices (e.g., a touch-sensitive surface (e.g., a touchscreen), a mouse, a keyboard) and is associated with a first user account (e.g., a child&#39;s account and/or a user account that has a first set of access rights at the computer system; an account of a primary user of the computer system) and a second user account (e.g., a guardian or parent&#39;s account and/or a user account that has a second set of access rights (e.g., permission-granting rights, configuration rights), different from the first set of access rights, at the computer system)(In some embodiments, the second set of access rights includes one or more access rights that are not possessed by the first user account), wherein the second user account is associated with an external computer system (e.g., a smart phone, a smart watch, a personal computer). Some operations in method  800  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     While the first user account is logged in at (e.g., is the active account) the computer system (e.g.,  500 ), the computer system (e.g.,  500 ) receives ( 802 ), via the one or more input devices, a request (e.g.,  750 D) (In some embodiments, the request does not identify a requestee/recipient of the request (e.g., the request is a set of one or more inputs that does not include inputs identifying a requestee/recipient of the request)) to add assets (e.g., service credits (e.g., transit service credits; printing credits; pre-paid minutes for a service; pre-paid monthly access to a service) and/or currency) to an asset account (e.g., a transit system account; a payment account; a store loyalty account) that is associated with the computer system (e.g., linked to the computer system and/or provisioned on the computer system). In some embodiments, one or more details of the asset account are stored in a secure element of the computer system. In some embodiments, a secure element is a hardware component (e.g., a secure microcontroller chip) (e.g., of the computer system) configured to securely store data or an algorithm such that the securely stored data is not accessible by the computer system without proper authentication information from a user of the computer system. Keeping the securely stored data in a secure element that is separate from other storage on the computer system prevents access to the securely stored data even if other storage locations on the computer system are compromised (e.g., by malicious code or other attempts to compromise information stored on the computer system). In some embodiments, the secure element provides (or releases) payment information (e.g., an account number and/or a transaction-specific dynamic security code). In some examples, the secure element provides (or releases) the payment information in response to the computer system receiving authorization, such as a user authentication (e.g., biometric authentication (e.g., fingerprint authentication; facial authentication; iris authentication; passcode authentication)). 
     In response to receiving the request (e.g.,  750 D) to add assets, the computer system (e.g.,  500 ) displays ( 804 ), via the display generation component, a preview (e.g.,  716 ) of a message (e.g., a text message, an email message) (and, optionally, sending the message), wherein the message is prepopulated (e.g., automatically includes (e.g., without requiring further user inputs)) with: contact information ( 806 ) (e.g., an email address, a texting address/handle  716 A, and/or a phone number) for the second user account that designates the second user account as the recipient of the message. In some embodiments, the recipient of the message cannot be modified. 
     In response to receiving the request to add assets, the computer system (e.g.,  500 ) displays ( 804 ), via the display generation component, the preview (e.g.  716 ) of the message (e.g., a text message, an email message) (and, optionally, sending the message), wherein the message is prepopulated (e.g., automatically includes (e.g., without requiring further user inputs)) with: a user-interactive graphical user interface object (e.g.,  716 B) ( 806 ), that, when selected at the external computer system (e.g.,  100 ) (e.g., selected in a messaging application of the external computer system), initiates a process to add assets to the asset account (e.g., a process that involves one or more steps performed at an asset management server that is capable of communicating with the external computer system and the computer system). In some embodiments, the preview of the message is generated (in some embodiments, sent) without providing an option to specify a recipient of the message, other than the second user account. In some embodiments, the preview of the message is generated by a process that includes presenting one or more options for selecting recipient(s) of the message from a set of pre-determined potential recipients (e.g., restricted list (e.g., a list that includes the second user account and user accounts of one or more parents, guardians, individual(s) who provisioned the asset account at the computer system, individual(s) who configured one or more settings of the computer system, and/or emergency contacts associated with the first user account)). In some embodiments, the set of pre-determined potential recipients is less than the set of all contacts stored (e.g., stored in a contact list and/or contact application) at the computer system (e.g.,  500 ). 
     Prepopulating the preview of the message with the contact information of the second user account reduces the number of inputs required to compose and complete the request, which performs an operation when a set of conditions has been met without requiring further user input. 
     Prepopulating the preview of the message with the contact information of the second user account (in some embodiments, of user accounts from a predetermined restricted set/list of accounts) reduces the risk that the request is sent to an incorrect and/or unauthorized user account, thereby enhancing security. Enhancing security enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly, efficiently, and securely. 
     In accordance with some embodiments, the request to add assets is a user input (e.g., tap input  750 D) corresponding to a first request user-interactive graphical element (e.g.,  714 A) that is displayed in a first user interface (e.g.,  714 , an interface of an e-wallet application and/or an interface that includes one or more details (e.g., a provider of the account, an asset balance of the account) of the asset account), wherein: in accordance with a determination that the computer system is associated (e.g., currently associated (e.g., the first user account is associated with the second asset account and the first user account is currently logged in at the computer system)) with a second asset account (e.g., corresponding to  712 ) (In some embodiments, an asset account that includes assets that can be transferred to the asset account), the first user interface (e.g.,  714 ) includes (e.g., concurrently displayed with the request user-interactive graphical element) a transfer asset user-selectable graphical element (e.g.,  714 B, an “add asset” affordance) that, when selected, initiates a process for transferring assets from the second asset account to the asset account. In some embodiments, in accordance with a determination that the computer system is not associated with a second asset account (In some embodiments, an asset account that includes assets that can be transferred to the asset account), the first user interface does not include the transfer asset user-selectable graphical element. In some embodiments, the first user interface includes a non-selectable graphical element that includes an indication that a process/function for transferring assets is currently disabled (e.g., a grey-out “add asset” graphical element). Conditionally displaying a functional transfer asset user-selectable graphical element provides the user with feedback as to the availability of a second asset account associated with the computer system, which provides improved visual feedback to the user. 
     In accordance with some embodiments, the computer system (e.g.,  500 ) receives, via the one or more input devices, a user input (e.g.,  750 E, a tap input) corresponding to the transfer asset user-selectable graphical element (e.g.,  714 B). In response to receiving the user input corresponding to the transfer asset user-selectable graphical element, the computer system (e.g.,  500 ) initiates the process for transferring assets from the second asset account to the asset account (e.g., as shown in  FIGS.  7 L- 7 O ). 
     In accordance with some embodiments, the computer system (e.g.,  500 ) displays, via the display generation component, a second user interface (e.g.,  714 ) (e.g., an interface of an e-wallet application and/or an interface that includes one or more details (e.g., a provider of the account, an asset balance of the account) of the asset account), wherein displaying the second user interface includes: in accordance with a determination that the computer system (e.g.,  500 ) is not currently in a paired relationship of a first type (e.g., a mutual data transfer relationship) (In some embodiments, a relationship in which the external device can be used to perform one or more operations at the computer system) with an external device (e.g., a smart phone having a predefined set of hardware and/or software requirements), displaying a second request user-interactive graphical element (e.g.,  714 A), and in accordance with a determination the computer system is currently in a paired relationship of the first type with an external device, forgoing displaying the second request user-interactive graphical element (e.g.,  714 A). The request to add assets is a user input (e.g.,  750 D, a tap input) corresponding to the second request user-interactive graphical element. Conditionally displaying second request user-interactive graphical element provides the user with feedback as to the pairing state of the computer system, which provides improved visual feedback to the user; doing so also provides the asset request functionality when the pairing relationship conditions are met, which performs an operation when a set of conditions has been met without requiring further user input. 
     In accordance with some embodiments, the preview (e.g.,  716 ) of the message is generated without providing an option (e.g., a user interface option) to specify an amount of assets to be requested. In some embodiments, the preview of the message does not include (and cannot include) a requested amount of assets. In some embodiments, a user of the computer system cannot specify an amount of assets to be requested. 
     In accordance with some embodiments, the computer system (e.g.,  500 ) displays, concurrently with the preview (e.g.,  716 ) of the message, a set of one or more user-interactive graphical elements (e.g., a keyboard; one or more pre-generated strings of text) that, when selected, adds text to the message (e.g., allows a user to add, to the message, text content that will be sent along with the message, when the message is sent). Displaying the set of one or more user-interactive graphical elements provides the user with feedback as to the functionality of adding text to the message, which provides improved visual feedback to the user. 
     In accordance with some embodiments, while displaying the preview (e.g.,  716 ) of the message, the computer system receives, via the one or more input devices, a request (e.g.,  750 F) to transmit the message (e.g., a selection of a “send” affordance). In response to the request (e.g.,  750 F) to transmit the message, the computer system (e.g.,  500 ) transmits the message to the second user account. 
     In accordance with some embodiments, after transmitting the message to the second user account, the computer system (e.g.,  500 ) receives a first set of one or more user inputs that correspond to a request to display a message transcript of a message conversation between the first user account and the second user account. In response to receiving the first set of one or more user inputs, the computer system (e.g.,  500 ) displays the message transcript (e.g.,  718 A) (In some embodiments, in a messaging application of the computer system) of the message conversation between the first user account and the second user account, wherein the message transcript includes the message. In some embodiments, the transcript further includes one or more messages previously sent from the first user account to the second user account and/or one or more messages previously sent from the second user account to the first user account. In some embodiments, in response to the request to transmit the message, the computer system displays the message transcript (e.g., automatically and/or without receiving and/or requiring further user input). Displaying the message in the message transcript provides the user with feedback as to the transmission state of the message and the recipient of the message, which provides improved visual feedback to the user. 
     In accordance with some embodiments, prior to receiving an indication (e.g., data transmitted from the external computer system and/or an asset management serve) that the process to add assets to the asset account is completed, the message (e.g.,  718 B) is displayed in the message transcript with a first appearance and after receiving the indication that the process to add assets to the asset account is completed, the message (e.g.,  770 C) is displayed in the message transcript (e.g.,  718 A) with a second appearance, different than the first appearance. In some embodiments, after receiving the indication, the message is replaced with a message indicating the completed request. Displaying the message with different visual states depending on completion of the process to add assets provides the user with feedback as to the state of the asset addition process, which provides improved visual feedback to the user; doing so also performs an operation when a set of conditions has been met without requiring further user input. 
     In accordance with some embodiments, transmitting the message to the second user account includes transmitting data (In some embodiments, as part of the contents of the message; In some embodiments, separately from the contents of the message) indicating the current asset balance of the asset account to the second user account. 
     In accordance with some embodiments, the request to add assets (e.g.,  750 F) is received while displaying a third user interface (e.g.,  708 ) that concurrently includes: an indication (e.g., a textual or graphical indication) of a first detail of the asset account (e.g., a provider of the account, an asset balance of the account  708 A, a recent transaction affecting the asset account, a use history of the asset account  708 B); and an indication of a second detail of the asset account, different from the first detail. In some embodiments, the third user interface does not include indications of details of asset accounts other than the asset account. Displaying indications pertaining to the asset account while receiving the request to add assets provides feedback as to what account is being affected, which provides improved visual feedback to the user. 
     In accordance with some embodiments, the process to add assets to the asset account includes the external computer system (e.g.,  100 ) displaying an asset addition user interface (e.g.,  772 ) that includes a set of one or more user-interactive graphical elements (e.g.,  772 D, one or more numeric keys and/or pre-selected amounts) that, when selected, determines an amount of assets to be added to the asset account. Displaying the set of one or more user-interactive graphical elements for determining an amount of assets provides the user of the external computer system with feedback as to the availability of the function to select the amount of assets to add, which provides improved visual feedback. 
     In accordance with some embodiments, the asset addition user interface (e.g.,  772 ) of the external computer system (e.g.,  100 ) includes: an indication (e.g.,  772 C, a textual and/or graphical indication) of the current asset balance of the asset account, prior to completion of the process to add assets to the asset account; and an indication (e.g.,  772 B, a textual and/or graphical indication) of a future balance of the asset account, after completion of the process to add assets to the asset account. Displaying indications pertaining to the balances of asset account provides the user of the external computer system with feedback as to the quantitative details of the asset transfer operation, which provides improved visual feedback. 
     In accordance with some embodiments, the asset addition user interface (e.g.,  772 ) of the external computer system (e.g.,  100 ) includes: an indication (e.g.,  772 F, a textual and/or graphical indication) identifying the first user account; and an indication (e.g.,  772 A, a textual and/or graphical indication) identifying the asset account. Displaying indications pertaining to the asset account provides the user of the external computer system with feedback as which asset account is being affected, which provides improved visual feedback. 
     As described below, method  800  provides an intuitive way for requesting assets be added to an asset account. The method reduces the cognitive burden on a user for requesting assets be added to an asset account, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to request that assets be added to an asset account faster and more efficiently conserves power and increases the time between battery charges. 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the process of requesting assets be added to an asset account. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user&#39;s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to request assets from a relevant user. Accordingly, use of such personal information data enables users to have calculated control of the requesting process. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. 
     The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country. 
     Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in requesting assets during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app. 
     Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user&#39;s privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.

Metadata:
Filing Date: 20220726
Publication Date: 20231010
Grant Date: 20231010
Priority Date: 20210920
Inventors: PONS BORDES, PABLO
AKELLA, VENKATA S.
CHESTER, BENJAMIN D.
GENTLES, Tyler
RAGONE, Laura M.
Assignee: APPLE INC
CPC Classifications: [{"code": "H04L51/224", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0484", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/14", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04L51/224", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/02", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/224", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0484", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/14", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 85572234