PATENT DOCUMENT

Publication Number: US-11816194-B2
Application Number: US-202017076694-A
Country: US
Kind Code: B2

Title: User interfaces for managing secure operations

Abstract:
The present disclosure generally relates to methods for providing an option (e.g., a selectable option) to initiate a secure operation (e.g., a secure operation), such methods using a computer system and an external device.

Claims:
What is claimed is: 
     
       1. A 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 computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user; and
 in response to receiving the first request:
 in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and 
 in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
 
 
 
 
     
     
       2. The computer system of  claim 1 , wherein the external input device is an external automotive head unit. 
     
     
       3. The computer system of  claim 1 , wherein the computer system is a smartphone that includes a hardware secure element for use in the secure transaction. 
     
     
       4. The computer system of  claim 1 , wherein the computer system includes one or more external device communication interfaces, the one or more programs further including instructions for:
 detecting, via the one or more external device communication interfaces, connection of the computer system to the external input device; 
 wherein the first request is received after detecting connection of the computer system to the external input device. 
 
     
     
       5. The computer system of  claim 1 , wherein:
 the computer system is in communication with one or more hardware input devices; and 
 the secure transaction, when authorized from the computer system, requires authorization from the user provided via the one or more hardware input devices. 
 
     
     
       6. The computer system of  claim 5 , wherein the one or more hardware input devices includes a biometric reader and the authorization from the user provided via the one or more hardware input devices is a biometric authorization received via the biometric reader. 
     
     
       7. The computer system of  claim 1 , the one or more programs further including instructions for:
 after providing the option to initiate a secure transaction without requiring the separate authorization from the user, receiving a request from the external input device to proceed with the secure transaction; and 
 in response to receiving the request from the external input device to proceed with the secure transaction, performing the secure transaction including securely transmitting to an external receiving device first data that includes information that identifies a first account for use in the secure transaction. 
 
     
     
       8. The computer system of  claim 7 , wherein:
 the computer system is in communication with a display generation component; and 
 performing the secure transaction occurs while the display generation component is in a locked state. 
 
     
     
       9. The computer system of  claim 1 , wherein:
 the secure transaction is performed using a first application on the computer system; 
 the user interface is an interface displayed at the external input device; 
 the user interface is arranged according to a first interface layout template and includes information provided by the first application; and 
 the one or more programs further include instructions for:
 receiving a second request from the external input device to interact with a first portion of a second user interface that is displayed at the external input device and associated with a second secure transaction performed using a second application on the computer system that, if authorized from the computer system, would require separate authorization from the user, wherein:
 the second application is different from the first application; and 
 the second user interface is arranged according the first interface layout template and includes information provided by the second application. 
 
 
 
     
     
       10. The computer system of  claim 1 , wherein the set of authorization criteria is satisfied when:
 the computer system, prior to receiving the first request, received a first set of one or more inputs; and 
 in response to the first set of one or more inputs:
 authorized connection of the external input device to the computer system while the computer system is in a locked state. 
 
 
     
     
       11. The computer system of  claim 10 , wherein the external input device satisfies the set of authorization criteria based on a status that is established based on a second set of one or more inputs that is received after having received the first set of one or more inputs. 
     
     
       12. The computer system of  claim 11 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a long-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received; or 
 while the computer system was in a preceding connection session with the external input device that is different from the connection session during which the first request was received. 
 
 
     
     
       13. The computer system of  claim 11 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a short-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received. 
 
 
     
     
       14. The computer system of  claim 1 , wherein the external input device satisfies the set of authorization criteria based on an input, received prior to receiving the first request, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       15. The computer system of  claim 1 , wherein the external input device satisfies the set of authorization criteria based on an input, received while connected to the external input device, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       16. The computer system of  claim 1 , wherein the external input device satisfies the set of authorization criteria based on the external input device being identified as being a first type of device. 
     
     
       17. The computer system of  claim 1 , wherein the external input device satisfies the set of authorization criteria based on the external input device being connected to a vehicle identified as having authorized authentication hardware. 
     
     
       18. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the one or more programs including instructions for:
 while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user; and 
 in response to receiving the first request:
 in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and 
 in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
 
 
     
     
       19. The non-transitory computer-readable storage medium of  claim 18 , wherein the external input device is an external automotive head unit. 
     
     
       20. The non-transitory computer-readable storage medium of  claim 18 , wherein the computer system is a smartphone that includes a hardware secure element for use in the secure transaction. 
     
     
       21. The non-transitory computer-readable storage medium of  claim 18 , wherein the computer system includes one or more external device communication interfaces, the one or more programs further including instructions for:
 detecting, via the one or more external device communication interfaces, connection of the computer system to the external input device; 
 wherein the first request is received after detecting connection of the computer system to the external input device. 
 
     
     
       22. The non-transitory computer-readable storage medium of  claim 18 , wherein:
 the computer system is in communication with one or more hardware input devices; and 
 the secure transaction, when authorized from the computer system, requires authorization from the user provided via the one or more hardware input devices. 
 
     
     
       23. The non-transitory computer-readable storage medium of  claim 22 , wherein the one or more hardware input devices includes a biometric reader and the authorization from the user provided via the one or more hardware input devices is a biometric authorization received via the biometric reader. 
     
     
       24. The non-transitory computer-readable storage medium of  claim 18 , the one or more programs further including instructions for:
 after providing the option to initiate a secure transaction without requiring the separate authorization from the user, receiving a request from the external input device to proceed with the secure transaction; and 
 in response to receiving the request from the external input device to proceed with the secure transaction, performing the secure transaction including securely transmitting to an external receiving device first data that includes information that identifies a first account for use in the secure transaction. 
 
     
     
       25. The non-transitory computer-readable storage medium of  claim 24 , wherein:
 the computer system is in communication with a display generation component; and 
 performing the secure transaction occurs while the display generation component is in a locked state. 
 
     
     
       26. The non-transitory computer-readable storage medium of  claim 18 , wherein:
 the secure transaction is performed using a first application on the computer system; 
 the user interface is an interface displayed at the external input device; 
 the user interface is arranged according to a first interface layout template and includes information provided by the first application; and 
 the one or more programs further include instructions for:
 receiving a second request from the external input device to interact with a first portion of a second user interface that is displayed at the external input device and associated with a second secure transaction performed using a second application on the computer system that, if authorized from the computer system, would require separate authorization from the user, wherein:
 the second application is different from the first application; and 
 the second user interface is arranged according the first interface layout template and includes information provided by the second application. 
 
 
 
     
     
       27. The non-transitory computer-readable storage medium of  claim 18 , wherein the set of authorization criteria is satisfied when:
 the computer system, prior to receiving the first request, received a first set of one or more inputs; and 
 in response to the first set of one or more inputs:
 authorized connection of the external input device to the computer system while the computer system is in a locked state. 
 
 
     
     
       28. The non-transitory computer-readable storage medium of  claim 27 , wherein the external input device satisfies the set of authorization criteria based on a status that is established based on a second set of one or more inputs that is received after having received the first set of one or more inputs. 
     
     
       29. The non-transitory computer-readable storage medium of  claim 28 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a long-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received; or 
 while the computer system was in a preceding connection session with the external input device that is different from the connection session during which the first request was received. 
 
 
     
     
       30. The non-transitory computer-readable storage medium of  claim 28 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a short-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received. 
 
 
     
     
       31. The non-transitory computer-readable storage medium of  claim 18 , wherein the external input device satisfies the set of authorization criteria based on an input, received prior to receiving the first request, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       32. The non-transitory computer-readable storage medium of  claim 18 , wherein the external input device satisfies the set of authorization criteria based on an input, received while connected to the external input device, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       33. The non-transitory computer-readable storage medium of  claim 18 , wherein the external input device satisfies the set of authorization criteria based on the external input device being identified as being a first type of device. 
     
     
       34. The non-transitory computer-readable storage medium of  claim 18 , wherein the external input device satisfies the set of authorization criteria based on the external input device being connected to a vehicle identified as having authorized authentication hardware. 
     
     
       35. A method comprising:
 at a computer system:
 while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user; and 
 in response to receiving the first request:
 in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and 
 in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
 
 
 
     
     
       36. The method of  claim 35 , wherein the external input device is an external automotive head unit. 
     
     
       37. The method of  claim 35 , wherein the computer system is a smartphone that includes a hardware secure element for use in the secure transaction. 
     
     
       38. The method of  claim 35 , wherein the computer system includes one or more external device communication interfaces, further comprising:
 detecting, via the one or more external device communication interfaces, connection of the computer system to the external input device; 
 wherein the first request is received after detecting connection of the computer system to the external input device. 
 
     
     
       39. The method of  claim 35 , wherein:
 the computer system is in communication with one or more hardware input devices; and 
 the secure transaction, when authorized from the computer system, requires authorization from the user provided via the one or more hardware input devices. 
 
     
     
       40. The method of  claim 39 , wherein the one or more hardware input devices includes a biometric reader and the authorization from the user provided via the one or more hardware input devices is a biometric authorization received via the biometric reader. 
     
     
       41. The method of  claim 35 , further comprising:
 after providing the option to initiate a secure transaction without requiring the separate authorization from the user, receiving a request from the external input device to proceed with the secure transaction; and 
 in response to receiving the request from the external input device to proceed with the secure transaction, performing the secure transaction including securely transmitting to an external receiving device first data that includes information that identifies a first account for use in the secure transaction. 
 
     
     
       42. The method of  claim 41 , wherein:
 the computer system is in communication with a display generation component; and 
 performing the secure transaction occurs while the display generation component is in a locked state. 
 
     
     
       43. The method of  claim 35 , wherein:
 the secure transaction is performed using a first application on the computer system; 
 the user interface is an interface displayed at the external input device; 
 the user interface is arranged according to a first interface layout template and includes information provided by the first application; and 
 the method further comprising:
 receiving a second request from the external input device to interact with a first portion of a second user interface that is displayed at the external input device and associated with a second secure transaction performed using a second application on the computer system that, if authorized from the computer system, would require separate authorization from the user, wherein:
 the second application is different from the first application; and 
 the second user interface is arranged according the first interface layout template and includes information provided by the second application. 
 
 
 
     
     
       44. The method of  claim 35 , wherein the set of authorization criteria is satisfied when:
 the computer system, prior to receiving the first request, received a first set of one or more inputs; and 
 in response to the first set of one or more inputs:
 authorized connection of the external input device to the computer system while the computer system is in a locked state. 
 
 
     
     
       45. The method of  claim 44 , wherein the external input device satisfies the set of authorization criteria based on a status that is established based on a second set of one or more inputs that is received after having received the first set of one or more inputs. 
     
     
       46. The method of  claim 45 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a long-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received; or 
 while the computer system was in a preceding connection session with the external input device that is different from the connection session during which the first request was received. 
 
 
     
     
       47. The method of  claim 45 , wherein:
 the external input device satisfies the set of authorization criteria based on the status being a short-term authorization status; and 
 the first set of one or more inputs was received:
 while the computer system is in a connection session with the external input device that is also the connection session during which the first request was received. 
 
 
     
     
       48. The method of  claim 35 , wherein the external input device satisfies the set of authorization criteria based on an input, received prior to receiving the first request, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       49. The method of  claim 35 , wherein the external input device satisfies the set of authorization criteria based on an input, received while connected to the external input device, authorizing the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user. 
     
     
       50. The method of  claim 35 , wherein the external input device satisfies the set of authorization criteria based on the external input device being identified as being a first type of device. 
     
     
       51. The method of  claim 35 , wherein the external input device satisfies the set of authorization criteria based on the external input device being connected to a vehicle identified as having authorized authentication hardware.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to U.S. Provisional Application No. 63/041,969, filed Jun. 21, 2020, entitled “USER INTERFACES FOR MANAGING SECURE OPERATIONS.” The content of which is hereby incorporated by reference in its entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing secure operations via input received at an external device. 
     BACKGROUND 
     Users often perform operations using personal electronic devices. Such techniques typically require the user to provide various inputs and authorization to perform these operations. 
     BRIEF SUMMARY 
     Some techniques for managing secure operations using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques require the user to provide various inputs and authorization to perform these operations on a personal device (e.g., cell phone), which may not be convenient or safe for the user to provide while the user is operating a vehicle. 
     Accordingly, the present technique provides electronic devices with faster, safer, and more efficient methods and interfaces for managing secure operations using electronic devices. Such methods and interfaces optionally complement or replace other methods for managing secure operations. Such methods and interfaces are safer, such as not to distract a user while the user is operating a vehicle. Such method and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. 
     In accordance with some embodiments, a method is described. The method is performed at a computer system that is in communication with an external automotive head unit that includes one or more input components and that is in communication with an external receiving device. The method comprises: receiving, from the external automotive head unit, first data corresponding to an input received at the one or more input components of the external automotive head unit that corresponds to a request to perform a first transfer operation from a first account to a second account using an application on the computer system that is associated with the first account; and in response to receiving the first data, initiating a process to perform the first transfer operation using the application on the computer system, where performing the first transfer operation includes transmitting, to the external receiving device, second data that includes information that identifies the first account. 
     In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with an external automotive head unit that includes one or more input components and that is in communication with an external receiving device. The one or more programs include instructions for: receiving, from the external automotive head unit, first data corresponding to an input received at the one or more input components of the external automotive head unit that corresponds to a request to perform a first transfer operation from a first account to a second account using an application on the computer system that is associated with the first account; and in response to receiving the first data, initiating a process to perform the first transfer operation using the application on the computer system, where performing the first transfer operation includes transmitting, to the external receiving device, second data that includes information that identifies the first account. 
     In accordance with some embodiments, a transitory computer-readable storage medium is described. 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 an external automotive head unit that includes one or more input components and that is in communication with an external receiving device. The one or more programs include instructions for: receiving, from the external automotive head unit, first data corresponding to an input received at the one or more input components of the external automotive head unit that corresponds to a request to perform a first transfer operation from a first account to a second account using an application on the computer system that is associated with the first account; and in response to receiving the first data, initiating a process to perform the first transfer operation using the application on the computer system, where performing the first transfer operation includes transmitting, to the external receiving device, second data that includes information that identifies the first account. 
     In accordance with some embodiments, a computer system is described. The computer system comprises: one or more processors, where the computer system is in communication with an external automotive head unit that includes one or more input components, and where the computer system is in communication with an external receiving device; and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving, from the external automotive head unit, first data corresponding to an input received at the one or more input components of the external automotive head unit that corresponds to a request to perform a first transfer operation from a first account to a second account using an application on the computer system that is associated with the first account; and in response to receiving the first data, initiating a process to perform the first transfer operation using the application on the computer system, where performing the first transfer operation includes transmitting, to the external receiving device, second data that includes information that identifies the first account. 
     In accordance with some embodiments, a computer system is described, where the computer system is in communication with an external automotive head unit that includes one or more input components, and where the computer system is in communication with an external receiving device. The computer system comprises: means for receiving, from the external automotive head unit, first data corresponding to an input received at the one or more input components of the external automotive head unit that corresponds to a request to perform a first transfer operation from a first account to a second account using an application on the computer system that is associated with the first account; and means, responsive to receiving the first data, for initiating a process to perform the first transfer operation using the application on the computer system, where performing the first transfer operation includes transmitting, to the external receiving device, second data that includes information that identifies the first account. 
     In accordance with some embodiments, a method is described. The method is performed at a computer system. The computer system comprises: while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user. The computer system further comprises, in response to receiving the first request: in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
     In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user. The one or more programs further include instructions for: in response to receiving the first request: in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
     In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for: while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user. The one or more programs further include instructions for: in response to receiving the first request: in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
     In accordance with some embodiments, a computer system is described. The computer system comprises: 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 include instructions for: while the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user. The one or more programs further include instructions for: in response to receiving the first request: in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
     In accordance with some embodiments, a computer system is described. The computer system comprises: means, while the computer system is connected to an external input device, for receiving a first request from the external input device to interact with a first portion of a user interface that is associated with a secure transaction that, if authorized from the computer system, would require separate authorization from the user; and means, responsive to receiving the first request, for: in accordance with a determination that the external input device satisfies a set of authorization criteria, providing an option, via the external input device, to initiate a secure transaction without requiring the separate authorization from the user; and in accordance with a determination that the external input device does not satisfy the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user. 
     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 managing secure operations, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing secure operations. 
    
    
     
       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 F  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments. 
         FIGS.  7 A- 7 M  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments. 
         FIG.  8    is a flow diagram illustrating a method for performing a secure operation in accordance with some embodiments. 
         FIG.  9    is a flow diagram illustrating a method for providing an option to initiate a secure operation 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 managing secure operations. For example, there is a need to provide techniques that increase safety when for managing operations that can be perform while a vehicle is being operated. Such methods and interfaces are safer, such as not to distract a user while the user is operating a vehicle. Such techniques can reduce the cognitive burden on a user who needs to perform an operation, 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 managing secure operations. 
       FIGS.  6 A- 6 F  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments.  FIGS.  7 A- 7 M  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments.  FIG.  8    is a flow diagram illustrating a method for performing a secure operation in accordance with some embodiments.  FIG.  9    is a flow diagram illustrating a method for providing an option to initiate a secure operation in accordance with some embodiments. The user interfaces in  FIGS.  6 A- 6 F  and  FIGS.  7 A- 7 M  are used to illustrate the processes described below, including the processes in  FIG.  8    and  FIG.  9   . 
     Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch 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. 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, Calif. 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 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) 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. 
     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, Calif. 
     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 MIMS 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, 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 ( 187 ) 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 definition  187  includes 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 portable 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 programs (e.g., sets of instructions) need not be implemented as separate software programs, 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 touch-sensitive 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 processes  800  and  900  ( FIG.  8    and  FIG.  9   ). 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. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     Attention is now directed towards embodiments of user interfaces (“UP”) 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 F  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments. In particular,  FIGS.  6 A- 6 F  illustrate exemplary user interfaces that can be displayed during a scenario where a secure transaction (e.g., transferring a parking spot between accounts) is completed in response to receiving one or more gestures and biometric data from a user of device  600 . The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  8    and  FIG.  9   . In some embodiments, the exemplary user interfaces of  FIGS.  6 A- 6 F  can be combined or displayed simultaneously with the exemplary user interfaces of  FIGS.  7 A- 7 M  described below. 
       FIG.  6 A  illustrates device  600  displaying user interface  602  on a touch-sensitive display. In some embodiments, device  600  includes one or more features of devices  100 ,  300 , and  500 , which are described above. 
     As illustrated in  FIG.  6 A , user interface  602  includes application icons  604 . Application icons  604  includes multiple application icons for launching different applications that cause different user interfaces to be displayed on device  600 . Application icons  604  include parking application icon  604   a  for launching a parking application and coffee shop application icon  604   b  for launching a coffee shop application. At  FIG.  6 A , device  600  detects tap gesture  650   a  on (e.g., directed to, at a location corresponding to) parking application icon  604   a.    
     As illustrated in  FIG.  6 B , in response to detecting tap gesture  650   a , device  600  launches a parking application that corresponds to parking application icon  604   a  and displays user interface  610  of the parking application. User interface  610  includes account identifier  612 , current parking information  614 , and recommended parking information  616 . Account identifier  612  indicates that device  600  is currently logged into a particular account (“Jane&#39;s account”) that is recognized by and/or belongs to (e.g., stored in a database that is communication with) the parking application. Recommended parking information  616  includes information related to one or more available parking spots that are being recommended to the user of device  600 . 
     As illustrated in  FIG.  6 B , current parking information  614  indicates that parking spot #31 is currently assigned to Jane&#39;s account, which is located in Garage A at 123 Gala Street. Current parking information  614  also includes a timeframe (e.g., 9:00 AM-11:00 AM) for which parking spot #31 will be assigned to Jane&#39;s account before parking spot #31 is automatically transferred back to an account associated with Garage A. Moreover, current parking information includes check-in control  618  for transferring parking spot #31 from Jane&#39;s account to an account that belongs to Garage A. At  FIG.  6 B , device  600  detects tap gesture  650   b  on check-in control  618 . 
     As illustrated in  FIG.  6 C , in response to detecting tap gesture  650   b , device  600  initiates a process for performing a transaction (e.g., performing a secure operation) that includes transferring parking spot # 31  from Jane&#39;s account to an account associated with Garage A. As shown in  FIG.  6 C , in response to detecting tap gesture  650   b , device  600  displays user interface  620  over a portion of user interface  610  and blurs a portion of user interface  610  that remains displayed in  FIG.  6 C . User interface  620  includes transaction information  622 , confirmation instruction  624 , and input instruction  626 . Transaction information  622  includes information, such as the e-mail address (e.g., “jane-apples@mail.com) that is assigned to (e.g., on file with) the particular account (e.g., “Jane&#39;s Account”) to which parking spot # 31  is currently assigned and an identifier (“Garage A”) that is associated with the account to which parking spot # 31  will be transferred. In  FIG.  6 C , the parking application is configured to perform a transfer operation using Jane&#39;s account (e.g., and/or the e-mail address assigned to Jane&#39;s account). Confirmation instruction  624  indicates that input has to be received on hardware button  648  (e.g., “side button”) in order for the transaction to be initiated, and input instruction  626  indicates that the hardware button  648  must be quickly pressed twice (e.g., “double click”) in order for the transaction to be initiated. At  FIG.  6 C , device  600  detects double-click input  650   c  on hardware button  648 . 
     At  FIG.  6 D , in response to detecting double-click input  650   c , device  600  initiates an authentication process, which causes camera  646   a  and/or camera  646   b  to capture images in order to obtain biometric data (e.g., data corresponding to one or more features of a user&#39;s face). As a part of the authentication process, device  600  also replaces confirmation instruction  624  with biometric identification status indicator  628  to indicate that device  600  is attempting to capture images in order to obtain biometric information. 
     At  FIG.  6 D , after capturing a set of images, device  600  obtains biometric data (e.g., one or more features of a user&#39;s face) in order to authenticate the user so that the transaction can be authorized. Device  600  uses this newly obtained biometric data in order to authenticate the current user of device  600  by matching the newly obtained biometric data to previously stored biometric data that is associated with a known user who has permission to complete secure transactions via device  600  (e.g., matching within a certain confidence level). In some embodiments, the biometric data (e.g., the previously stored biometric data and the newly captured biometric data) is accessible to an application for managing secure transactions (or operations) on device  600 . In some embodiments, the parking application does not have access to the biometric data. In some embodiments, when device  600  cannot match the newly obtained biometric data with previously stored biometric data, device  600  will continue to capture images to obtain additional biometric data in order to match the previously stored biometric data. In some embodiments, device  600  will only capture images for a predetermined period of time. In some embodiments, when device  600  cannot match the biometric data, device  600  will display an indication that parking spot #31 cannot be transferred to Garage A because the user of device  600  could not be authenticated and/or display controls for completing authentication for transaction in other ways (e.g., via entry of a password). In some embodiments, device  600  can authenticate a user via capturing and comparing other types of biometric data, such as finger data (e.g., captured via the touch-sensitive displaying that includes a fingerprint sensor), voice data (e.g., via one or more microphones), etc. At  FIG.  6 D , device  600  (or another device in communication with device  600 ) matches a set of newly obtained biometric data with previously stored biometric data, which authenticates the current user of device  600  as a user that has permission to complete secure transactions via device  600 . 
     At  FIG.  6 E , in response to authenticating the current user of device  600  as a user that has permission to complete secure transactions (e.g., via Jane&#39;s account), device  600  causes parking spot #31 to be transferred from Jane&#39;s account to Garage A&#39;s account. In some embodiments, device  600  causes parking spot #31 to be transferred from Jane&#39;s account to Garage A&#39;s account using a secure hardware component (e.g., a hardware chip) that stores information that is representative of Jane&#39;s account (e.g., Jane&#39;s e-mail address; a device specific account identifier). In some embodiments, the secure hardware component does not store or have access to primary information (e.g., a primary account number) that is associated with Jane&#39;s account. In some embodiments, authenticating that the current user of device  600  has permission to complete secure transactions authorizes device  600  to use the secure hardware component to complete the secure transaction. 
     As illustrated in  FIG.  6 E , in response to authenticating the current user of device  600  as a user that has permission to complete secure transactions, device  600  also replaces biometric identification status indicator  628  with authenticated status indicator  630  to indicate that the user has been authenticated and the transfer has been completed. 
     As illustrated in  FIG.  6 F , after completing the transfer, device  600  ceases to display user interface  620  and updates user interface  610  to show that parking spot #31 is no longer assigned to Jane&#39;s account (e.g., via confirmation instruction  624 ). In addition, after completing the transfer, device  600  also receives (e.g., from one or more external devices) and displays notification  632 , which indicates that the transfer has been completed. 
       FIGS.  7 A- 7 M  illustrate exemplary user interfaces for performing a secure operation in accordance with some embodiments. In particular,  FIGS.  7 A- 7 M  illustrate exemplary user interfaces that can be displayed during scenarios where one or more secure transactions are attempted to be completed in response to receiving one or more gestures on the touch-sensitive display of automotive head unit  700  that is in communication with device  600 . The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  8    and  FIG.  9   . 
     As illustrated in  FIG.  7 A , device  600  is in operable communication with automotive head unit  700 , as indicated by communication link  708 . In some embodiments, device  600  is in operable communication with automotive head unit  700  via wireless or wired connection. In some embodiments, automotive head unit  700  includes a touch-sensitive display and is installed in the dashboard of an automobile. In some embodiments, automotive head unit  700  includes one or more features of devices  100 ,  300 , and  500 , which are described above. 
     As illustrated in  FIG.  7 A , device  600  display user interface  670  that includes lock indication  672 , which indicates that device  600  is in a locked state (e.g., a state in which one or functions of the display (e.g., display functions; input functions), which are available in an unlocked state, are disabled/unavailable). While device  600  is in the locked state, one or more operations that can be performed when device  600  is in an unlocked state cannot be performed when device  600  is in the locked state. The one or more operations include device  600  performing one or more operations for interacting with automotive head unit  700  while device  600  is in a locked state without receiving previous permission to do so. The one or more operations for interacting with automotive head unit  700  includes an operation that causes (e.g., by sending instructions and data) automotive head unit  700  to display one or more user interface components (e.g., user interfaces, icons) that correspond to applications installed on device  600 . 
     At  FIG.  7 A , device  600  has not received previous permission to interact with automotive head unit  700  while device  600  is operating in the locked state. Thus, at  FIG.  7 A , device  600  causes automotive head unit  700  to display user interface  714 . User interface  714  is displayed in response to device  600  detecting a connection (e.g., that operable communication has been established) between automotive head unit  700  and device  600 . User interface  714  includes an instruction for a user to unlock device  600  in order for device  600  to cause “Carplayer” to be started on automotive head unit  700  and/or perform one or more operations that cause automotive head unit  700  to display one or more user interface components that correspond to applications installed on device  600 . 
     As illustrated in  FIG.  7 A , because device  600  has not received previous permission to interact with (e.g., to provide data to and/or receive data from) automotive head unit  700  while device  600  is operating in the locked state, device  600  displays notification  676 , which includes an instruction that is similar to the instruction displayed on automotive head unit  700 . In some embodiments, when device  600  is in operable communication with another display device (e.g., automotive head unit  700 ) and previous permission has been received to interact with the other display device, device  600  causes the other display device to display one or more user interface components that correspond to applications installed on device  600 . At  FIG.  7 A , device  600  receives upward swipe gesture  750   a  on user interface  670  and obtains biometric data (e.g., via one or more of cameras  646   a  and  646   b ) to authenticate a user in order to perform the secure operation of unlocking device  600 . In some embodiments, device  600  obtains biometric data (e.g., via cameras  646   a  and/or  646   b ) and/or authenticates the user of device  600  to unlock device  600  using one or more similar techniques to those described above (e.g., in response to detecting gesture  650   c  in  FIG.  6 C ). 
     As illustrated in  FIG.  7 B , in response to receiving upward swipe gesture  750   a  and in response to authenticating the user of device  600 , device  600  switches to operate in an unlocked state and ceases to display user interface  670 . Moreover, in response to receiving upward swipe gesture  750   a  and in response to authenticating the user of device  600 , device  600  displays user interface  602  that includes application icons  604 . At  FIG.  7 B , user interface  602  is displayed because user interface  602  was the last user interface that was displayed by device  600  before device  600  entered into the locked state. 
     As illustrated in  FIG.  7 B , because device  600  is operating in an unlocked state, device  600  causes automotive head unit  700  to display user interface  702 , which includes an enlarged set application icons  704 . Application icons  704  include parking application icon  704   a  that corresponds to the same application (e.g., that launches an application on automotive head unit  700  that is compatible with (e.g., that can access data from) the parking application of application icon  604 ; that causes device  600  to cause automotive head unit  700  to display interfaces generated directly by the parking application on device  600 ) as parking application icon  604   a  and coffee shop application icon  704   b  that corresponds to the same application as coffee shop application icon  604   b . Application icons  704  are bigger than application icons  604 , such that application icon  704  can be more readably seen and interacted with by a user operating a vehicle. In addition, application icons  704  are a subset of application icons  604 . That is, the number of application icons  704  is smaller than the number of applications icons  604 , and some of the application icons included in application icons  604  are not included in application icons  704  (e.g., the camera application icon). 
     As illustrated in  FIG.  7 B , in response to receiving upward swipe gesture  750   a  and in response to authenticating the user of device  600 , device  600  also displays user interface  660  overlaid onto user interface  602 . Device  600  displays user interface  660  because device  600  has not received previous permission to interact with automotive head unit  700  while device  600  is operating in the locked state. User interface  660  includes allow-interaction-while-locked control  661 . At  FIG.  7 B , device  600  detects tap gesture  750   b  on allow-control-while-locked control  661 . 
     At  FIG.  7 C , in response to detecting tap gesture  750   b , device  600  receives permission to interact with automotive head unit  700  while device  600  is operating in the locked state and ceases to display user interface  660 . As illustrated in  FIG.  7 C , in response to detecting tap gesture  750   b , device  600  displays user interface  662  overlaid on user interface  602 . User interface  662  is a user interface for setting a trust level assigned to automotive head unit  700 , which device  600  will use to determine if automotive head unit  700  is trusted to initiate one or more secure operations, as further described below. As illustrated in  FIG.  7 C , user interface  662  includes three options  664 : always option  664   a ; once option  664   b , and never option  664   c.    
     When always option  664   a  is selected (e.g., via a gesture, such as a tap gesture), device  600  is configured to permanently trust automotive head unit  700 , such that automotive head unit  700  will be trusted by device  600  until device  600  is manually reconfigured (e.g., via one or more inputs on different interfaces) to not trust automotive head unit  700 . Thus, device  600  does not display the user interfaces illustrated in  FIGS.  7 A- 7 C  because automotive head unit  700  is a permanently trusted device in scenarios where device  600  is disconnected (e.g., operable communication has ceased) and subsequently reconnected (e.g., operable communication has been initiated) to automotive head unit  700  after option always  664   a  has been selected. 
     When once option  664   b  is selected, device  600  is configured to temporarily trust automotive head unit  700 , such that automotive head unit  700  will be trusted by device  600  until device  600  is disconnected from automotive head unit  700 . Thus, device  600  does re-display the user interfaces illustrated in  FIGS.  7 A- 7 C  because automotive head unit  700  would no longer be a trusted device in scenarios where device  600  is disconnected (e.g., operable communication has ceased) and subsequently reconnected (e.g., operable communication has been initiated) to automotive head unit  700  after once option  664   b  has been selected. 
     When never option  664   c  is selected, device  600  is configured to not trust automotive head unit  700 , such that automotive head unit  700  is not a trusted device. Thus, device  600  does display the user interfaces illustrated in  FIGS.  7 A- 7 C  because automotive head unit  700  is not a trusted device in scenarios where device  600  is disconnected (e.g., operable communication has ceased) and subsequently reconnected (e.g., operable communication has been initiated) to automotive head unit  700  after never option  664   c  has been selected. 
     While  FIG.  7 C  illustrates user interface  662  that includes three options  664  for setting device  600 &#39;s level of trust for automotive head unit  700 , automotive head unit  700  can be trusted or not trusted based on other factors. In some embodiments, device  600  will be configured to trust automotive head unit  700  when automotive head unit  700  is a particular type of display device, such as a display device that is from a specific manufacturer or has a particular type of software installed. In some embodiments, device  600  will be configured to trust automotive head unit  700  when device  600  is physically connected to a vehicle that includes hardware (e.g., a secure identity chip) that is trusted by device  600 . In some embodiments, when device  600  trusts automotive head unit  700  based on other factors, user interface  662  is not displayed in response to detecting tap gesture  750   b.    
       FIGS.  7 D- 7 E  illustrate exemplary user interfaces that are displayed after never option  664   c  has been selected in  FIG.  7 C . At  FIG.  7 C , device  600  detects tap gesture  750   c   3  on never option  664   c.    
     At  FIG.  7 D , in response to detecting tap gesture  750   c   3 , device  600  is configured such that automotive head unit  700  is not a trusted device, as discussed above in relation to  FIG.  7 C . As illustrated in  FIG.  7 D , device  600  is also in a locked state (e.g., as indicated by lock indicator  672 ) because a predetermined has passed since tap gesture  750   c   3  was detected, and device  600  is configured to enter into the locked state after the predetermined period of time has passed. Notably, device  600  continues to interact with automotive head unit  700  (e.g., cause user interface  702  to be displayed) while device  600  is in the locked state because device  600  received permission to do so (e.g., via tap gesture  750   b  on allow-interaction-while-locked control  661  in  FIG.  7 B ). At  FIG.  7 D , device  600  receives an indication from automotive head unit  700  that tap gesture  752   d   1  has been detected at a location on automotive head unit  700  that corresponds to parking application icon  704   a.    
     As illustrated in  FIG.  7 E , in response to device  600  receiving the indication that tap gesture  752   d   1  has been detected, device  600  causes automotive head unit  700  to display user interface  710 . User interface  710  corresponds to user interface  610  that was discussed above in relation to  FIGS.  6 B- 6 D . Thus, user interface  710  is a user interface for the parking application. When compared to user interface  610  of  FIG.  6 B , user interface  710  includes less information (e.g., no recommendation information on user interface  710 ) than the information that is displayed on user interface  610 . Also, one or more similar components (e.g., account identifier  712 ) displayed on user interface  710  is enlarged when compared to the corresponding component (e.g., account identifier  612 ) on user interface  610 . However, user interface  610  of  FIG.  6 B  and user interface  710  convey similar information. 
     As illustrated in  FIG.  7 E , user interface  710  includes account identifier  712  and current parking information  714  (e.g., which are displayed using similar techniques and for similar reasons as discussed above in relation to account identifier  612  and current parking information  614 ). As shown in  FIG.  7 E , account identifier  712  indicates that device  600  is currently logged into “Jane&#39;s Account” and currently parking information  714  indicates that parking spot #31 in Garage A is currently assigned to Jane&#39;s account. 
     Notably, as illustrated in  FIG.  7 E , device  600  does not display a control that corresponds to check-in control  618  in response to device  600  receiving the indication that tap gesture  752   d   1  has been detected. Here, device  600  does not display a control that corresponds to check-in control  618  because automotive head unit  700  is not a trusted device (e.g., via tap gesture  750   c   3  on never option  664   c ). Instead of causing a check-control to be displayed, device  600  causes automotive head unit  700  to display instruction  716 , which indicates that a user must complete the check-in process on device  600  (e.g., via one or more inputs on device  600  as discussed above in relation to  FIGS.  6 A- 6 E ). In some embodiments, device  600  causes automotive head unit  700  to display instruction  716 , even if the device is a trusted device, if the parking application on device  600  does not have an account already on file (e.g., linked to) the application. Thus, at  FIG.  7 E , one or more inputs cannot be detected on automotive head unit  700  that would cause device  600  to complete a secure operation because automotive head unit  700  is not trusted by device  600 . 
       FIGS.  7 F- 7 I  illustrate exemplary user interfaces that are displayed after always option  664   a  or once option  644   b  has been selected in  FIG.  7 C . At  FIG.  7 C , device  600  detects tap gesture  750   c   1  on always option  664   a  or tap gesture  750   c   2  on once option  644   b . At  FIG.  7 F , in response to detecting tap gesture  750   c   1  or tap gesture  750   c   2 , device  600  is configured such that automotive head unit  700  is a trusted device (e.g., as discussed above in relation to  FIG.  7 C ). At  FIG.  7 F , automotive head unit  700  and device  600  display the same respective user interfaces as the user interfaces displayed in  FIG.  7 D . At  FIG.  7 F , device  600  receives an indication from automotive head unit  700  that tap gesture  752   d   1  has been detected at a location on automotive head unit  700  that corresponds to parking application icon  704   a.    
     As illustrated in  FIG.  7 G , in response to device  600  receiving the indication that tap gesture  752   d   1  has been detected, device  600  causes automotive head unit  700  to display user interface  710 . User interface  710  of  FIG.  7 G  includes the same components as described above in relation to user interface of  FIG.  7 E , except for one distinct component. As illustrated in  FIG.  7 G , user interface  710  includes check-in control  718  that was not displayed in  FIG.  7 E  and excludes instruction  716  displayed in  FIG.  7 E . At  FIG.  7 G , device  600  causes automotive head unit  700  to display check-in control because automotive head unit  700  is trusted by device  600  (e.g., via selection of always option  664   a  or once option  644   b ). In some embodiments where tap gesture  750   c   2  on once option  644   b  was detected in  FIG.  7 C , check-in control  718  would not be displayed when user interface  710  is re-displayed after device  600  is disconnected and subsequently reconnected to automotive head unit  700 . In some embodiments where tap gesture  750   c   1  on always option  644   a  was detected in  FIG.  7 C , check-in control  718  would be displayed when user interface  710  is re-displayed after device  600  is disconnected and subsequently reconnected to automotive head unit  700 . At  FIG.  7 G , device  600  receives an indication from automotive head unit  700  that tap gesture  752   g  has been detected at a location on automotive head unit  700  that corresponds to check-in control  718 . In some embodiments, check-in control  718  is not displayed when account information (e.g., Jane&#39;s e-mail address) related to Jane&#39;s account is not stored in the secure hardware component and configured to be used to complete a transaction using the parking application. 
     As illustrated in  FIG.  7 H , in response to receiving the indication that tap gesture  752   g  has been detected, device  600  causes automotive head unit  700  to replace check-in control  718  with confirmation control  728 . At  FIG.  7 H , device  600  receives an indication from automotive head unit  700  that tap gesture  752   h  has been detected at a location on automotive head unit  700  that corresponds to confirmation control  728 . 
     At  FIG.  7 I , in response to receiving the indication that tap gesture  752   h  has been detected, device  600  causes parking spot #31 to be transferred from Jane&#39;s account to Garage A&#39;s account. In some embodiments, the transfer occurs in response to tap gesture  752   g  on check-in control  718  without requiring a further confirmation input. At  FIG.  7 I , when device  600  causes parking spot #31 to be transferred from Jane&#39;s account to Garage A&#39;s account, device  600  (and not automotive head unit  700 ) communicates one or more external devices (e.g., a database, an account management server) that updates Jane&#39;s account information and Garage A&#39;s account information to perform the transfer. In some embodiments, information (e.g., Jane&#39;s e-mail address) corresponding to Jane&#39;s account is stored in a secure hardware component of device  600 , and device  600  accesses the information corresponding to Jane&#39;s account in the secure hardware component. In some embodiments, device  600  sends the accessed information corresponding to Jane&#39;s account (e.g., or a token that corresponds to the accessed information) to one or more external devices as a part of performing the transfer. 
     Looking back at  FIG.  6 C- 6 D , device  600  caused parking spot #31 to be transferred after authenticating the user (e.g., via cameras  646   a  and  646   b ) via capturing biometric data in response detecting a confirmation gesture (e.g., double-click input  650   c ). However, in  FIG.  7 H , device  600  causes parking spot #31 to be transferred from Jane&#39;s account to Garage A&#39;s account without authenticating the user of device  600  and/or automotive head unit  700  after receiving the indication that tap gesture  752   h  was detected. In  FIG.  7 H , device  600  does not need to authenticate the user via capturing biometric data because automotive head unit  700  is trusted by device  600 . When a user is operating a vehicle, it can be helpful to allow a user of a trusted display device to complete transactions without providing biometric data (or other authentication data) via device  600  for simplicity and safety reasons. In some embodiments, device  600  does not also need to authenticate the user via biometric data because device  600  previously authenticated the user when device  600  was unlocked in  FIGS.  6 A- 6 B . 
     As illustrated in  FIG.  7 I , in response to receiving the indication that tap gesture  752   h  has been detected, device  600  causes automotive head unit  700  to display transaction interface  720  that includes transaction information  722 . Transaction interface  720  includes information concerning the transaction that was completed to transfer parking spot #31 from Jane&#39;s account to Garage A&#39;s account. Transaction information  722  is displayed using similar techniques to those described above in relation to transaction information  622  of  FIG.  6 E . Here, transaction information  722  and transaction information  622  are displayed using different layouts. In some embodiments, transaction information  722  and transaction information are displayed using the same layout. 
       FIGS.  7 J- 7 L  illustrate exemplary user interfaces that are displayed in a scenario where another type of transaction (e.g., a payment transaction) using a different application (e.g., a coffee shop application) is attempted to be completed after always option  664   a  or once option  644   b  has been selected in  FIG.  7 C . Turning back to  FIG.  7 F  (or  FIG.  7 D ), device  600  receives an indication from automotive head unit  700  that tap gesture  752   d   2  has been detected at a location on automotive head unit  700  that corresponds to coffee shop application icon  704   b.    
     As illustrated in  FIG.  7 J , in response to receiving the indication that tap gesture  752   d   2  has been detected, device  600  causes automotive head unit  700  to display user interface  730 , which a user interface for the coffee shop application. User interface  730  includes order recommendation  734  along with purchase control  738 . At  FIG.  7 J , device  600  causes automotive head unit  700  to display purchase control  738  because automotive head unit  700  is a trusted device (e.g., always option  664   a  or once option  644   b  was previously selected in  FIG.  7 C ). In some embodiments, device  600  does not cause automotive head unit  700  to display purchase control  738  when automotive head unit  700  is not trusted by device  600 . In some embodiments, automotive head unit  700  can display an instruction that indicates that device  600  must be used to purchase items from the coffee shop (e.g., a similar instruction to instruction  716 , as discussed above with reference to  FIG.  7 E ). At  FIG.  7 J , device  600  receives an indication from automotive head unit  700  that tap gesture  752   j  has been detected at a location on automotive head unit  700  that corresponds to confirmation control  728 . 
     As illustrated in  FIG.  7 K , in response to receiving the indication that tap gesture  752   j  has been detected, device  600  causes automotive head unit  700  to display user interface  740 . User interface  740  is a user interface for purchasing an order that is relevant to Jane&#39;s account. In  FIG.  7 J , Jane&#39;s account is associated with a favorite order that includes one cup of cold brew coffee that is priced at $2.59. As illustrated in  FIG.  7 J , Jane&#39;s account is also associated with card representation  734  (“Jane&#39;s Card”), which is a representation of a payment card that is linked to a bank account that is associated with Jane. As illustrated in  FIG.  7 J , user interface  740  also includes order confirmation control  742 , which is similar to confirmation control  728  in  FIG.  7 H . At  FIG.  7 K , device  600  receives an indication from automotive head unit  700  that tap gesture  752   k  has been detected at a location on automotive head unit  700  that corresponds to confirmation control  728 . 
     As illustrated in  FIG.  7 L , in response to receiving the indication that tap gesture  752   k  has been detected, device  600  causes $2.59 to be transferred from the bank account associated with Jane&#39;s card to the bank account associated with Garage A (and/or the parking application) without capturing biometric data and/or authenticating the user of automotive head unit  700  and/or device  600  (e.g., for similar reasons as discussed above in relation to  FIG.  7 I ). At  FIG.  7 L , when device  600  causes money to be transferred from the bank account associated with Jane&#39;s card to the bank account associated with Garage A, device  600  (and not automotive head unit  700 ) communicates one or more external devices (e.g., a database, an account management server) that updates the balances of Jane&#39;s account and Garage A&#39;s account to reflect the completed transaction. In some embodiments, device  600  causes money to be transferred from Jane&#39;s account to Garage A&#39;s account using a secure hardware component (e.g., a hardware chip) that has stored information that is representative of the account number that is associated with Jane&#39;s card. In some embodiments, the secure hardware component does not store or have access to primary information (e.g., a primary account number) that is associated with Jane&#39;s card. In some embodiments, when device  600  is not configured to process transactions using Jane&#39;s card, device  600  cannot process the transaction, and device  600  does not display purchase control  638  in user interface  730 , irrespective of whether automotive head unit  700  is trusted by device  600 . 
     As illustrated in  FIG.  7 L , in response to receiving the indication that tap gesture  752   k  has been detected, device  600  causes automotive head unit  700  to display user interface  760  that includes transaction information  762 . Transaction information  762  displays similar information to transaction information  722 , as described above with respect to  FIG.  7 L . In addition, transaction information  762  of  FIG.  7 L  is displayed using the same layout as transaction information  722  of  FIG.  7 L . As illustrated in  FIG.  7 L , transaction information  762  indicates that the $2.59 was transferred from an account associated with Jane&#39;s card, which is indicated by card representation  762 . 
       FIG.  7 M  illustrates device  600  displaying a settings user interface with setting  772 . Setting  772  is enabled (e.g., “on”) and is a setting for allowing transactions to be processed via gestures received at automotive head unit  700 . Looking back at the examples discussed above in relation to  FIGS.  7 A- 7 M , device  600  was able to cause various transactions to be processed in response to detecting gestures received on automotive head unit  700 , when automotive head unit  700  was trusted by device  600 . Thus, in the examples discussed above in relation to  FIGS.  7 A- 7 M , setting  772  was on. In some embodiments, when setting  772  is off, device  600  is not able to cause various transactions to be processed in response to detecting gestures received on automotive head unit  700 , irrespective of whether automotive head unit  700  is trusted by device  600 . In some embodiments, one or more other settings similar to setting  772  exists. These settings can allow a user of device  600  to control whether device  600  is able to cause various transactions to be processed for a particular application. In some embodiments, device  600  is configured to allow transactions to be processed via gestures received at automotive head unit  700  for the parking spot application and not for the coffee shop application (e.g., via the one or more settings). Thus, in some these embodiments and irrespective of whether automotive head unit  700  is trusted by device  600 , device  600  causes automotive head unit  700  to display a transaction control (e.g., check-control  718 ) when causing one or more user interfaces for the parking application (e.g., user interface  710  in  FIG.  7 G ) to be displayed on automotive head unit  700 , and device  600  does not cause automotive head unit  700  to display a transaction control (e.g., purchase control  738 ) when causing one or more user interfaces for the coffee shop application (e.g., user interface  710  in  FIG.  7 G ) to be displayed on automotive head unit  700 . 
       FIG.  8    is a flow diagram illustrating a method for performing a secure operation using a computer system in accordance with some embodiments. Method  800  is performed at a computer system (e.g.,  100 ,  300 ,  500 ,  600 ). The computer system (e.g.,  600 ) is in communication (e.g., wireless communication; wired communication) with an external automotive head unit (e.g.,  700 ) (e.g., a unified hardware interface for a plurality of entertainment and information systems (e.g., sound; navigation) of an automobile (e.g., a stereo head unit; an infotainment system)) that includes one or more input components (e.g., a touch-sensitive surface (e.g., a touchscreen), a hardware button), and wherein the computer system is in communication with an external receiving device (e.g., a transaction management server; a payment terminal). Some operations in method  800  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  800  provides an intuitive way for performing a secure operation using a computer system. The method reduces the cognitive burden on a user for performing a secure operation using a computer system, thereby creating a more efficient human-machine interface. The method also enables a user to perform secure operations safer and more securely using a computer system. For battery-operated computing devices, enabling a user to perform operations using a computer system faster and more efficiently conserves power and increases the time between battery charges. 
     The computer system receives ( 802 ), from the external automotive head unit (e.g.,  700 ), first data corresponding to an input (e.g.,  752   g ,  752   h ,  752   j ,  752   k ) (e.g., selection of a payment selectable user interface object) received at the one or more input components of the external automotive head unit (e.g.,  700 ) that corresponds to a request to perform a first transfer operation from a first account (e.g., Jane&#39;s Account indicated by  712 , Jane&#39;s Card indicated by  734 ) (e.g., an account associated with the user of the computer system; a credit account; a debit account; a cash balance account) to a second account (e.g., Garage Account, Coffee Shop account) (e.g., an account associated with a merchant) using an application (e.g., a digital storefront application; a digital wallet application; an e-commerce application) on the computer system (e.g.,  600 ) that is associated with the first account. 
     In response to receiving the first data (e.g., data associated with input  752   g ,  752   h ,  752   j , or  752   k ), the computer system initiates ( 804 ) a process to perform (e.g., a process that can require one or more additional inputs (e.g., inputs at the computer system, to fully complete) the first transfer operation using the application on the computer system (e.g., a transaction (e.g., a payment transaction; a purchase). In some embodiments, performing the first operation in response to receiving the first data. In some embodiments, the first data includes one or more parameters or variables that affect the operation (e.g., an amount of a purchase; an item for purchase). As a part of performing the first transfer operation, the computer system transmits, to the external receiving device, second data that includes information that identifies the first account (e.g., an encrypted representation of the account (e.g., a device specific account number) stored on the computer system; a representation of a payment account (e.g., a credit, debit, and/or cash balance account)). In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., a price; a quantity). Performing a transfer operation using an application on a computer system, based on an input on an automotive head unit provides the user with the ability to perform the transfer operation without having to directly interact with the computer system. Performing the operation without having to directly interact with the computer system can increase user safety while using the computer system and operating an automobile. Performing a transfer operation using an application on a computer system, based on an input on an automotive head unit, also provides the user with the option to perform the operation using inputs on the head unit. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ) was configured to (e.g., and continues to be configured to) perform transfer operations from the first account prior to receiving the first data (e.g., the first account was previously associated with the application (e.g., the first account is on file with the application)). In some embodiments, a second application that has not previously been configured to perform transfer operations from an existing account (e.g., the first account) cannot be used in conjunction with the external automotive head unit to perform transfer operations (e.g., until the second application is associated with an existing account). Performing a transfer operation using an application on a computer system that was already configured to perform the operation using the first account reduces the risk of an erroneous operation (e.g., by reducing the risk of using the wrong account or errors in providing account information). Reducing the risk of errors in operating the computer system enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, a second application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ), different from the first application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ), is installed on the computer system (e.g.,  600 ). In some embodiments, in accordance with (e.g., in accordance with a determination that) the second application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ) being configured to perform transfer operations from a third account (e.g., Jane&#39;s Account as indicated by  712 , Jane&#39;s card as indicated by  734 ) (e.g., an account that is different than the first account; that is the same as the first account), the second application is configured to perform a transfer operation in response to a request, received from the external automotive head unit (e.g.,  700 ), to perform a transfer operation from the third account (e.g., Jane&#39;s Account, Jane&#39;s Card). In some embodiments, in accordance with (e.g., in accordance with a determination that) the second application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ) not being configured to perform transfer operations from a third account (e.g., not being configured (e.g., pre-configured) to perform transfer operations from any existing accounts). In some embodiments, the second application is not configured to perform a transfer operation in response to a request (e.g.,  752   g ,  752   h ,  752   j ,  752   k ), received from the external automotive head unit (e.g.,  700 ), to perform a transfer operation from the third account (e.g., Jane&#39;s Account as indicated by  712 , Jane&#39;s card as indicated by  734 ). In some embodiments, only installed applications that are already configured to perform transfer operations from one or more existing accounts can perform transfer operations based on inputs received at the external automotive head unit. Performing a transfer operation using applications on a computer system, based on whether a given application is already configured to perform the operation using an account reduces the risk of an erroneous operation (e.g., by reducing the risk of using the wrong account or errors in providing account information). Reducing the risk of errors in operating the computer system enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the second application is configured to perform transfer operations from the third account. In some embodiments, the computer system receives (e.g., before receiving the first data; after receiving the first data), from the external automotive head unit (e.g.,  700 ) (e.g., in some embodiments, from an external automotive head unit that is different from the external automotive head unit), third data corresponding to an input (e.g.,  752   g ,  752   h ,  752   j ,  752   k ) (e.g., selection of a payment selectable user interface object) received at the one or more input components of the external automotive head unit (e.g.,  700 ) that corresponds to a request to perform a second transfer operation from the third account (e.g., Jane&#39;s Account as indicated by  712 , Jane&#39;s card as indicated by  734 ) (e.g., an account associated with the user of the computer system; a credit account; a debit account; a cash balance account) to a fourth account (e.g., Garage A&#39;s Account; Coffee Shop&#39;s Account) (e.g., an account associated with a merchant; an account that is the same as the second account; an account that is different from the second account) using the second application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ). In some embodiments, in response to receiving the third data, the computer system initiates a process to perform (e.g., a process that can require one or more additional inputs (e.g., inputs at the computer system, to fully complete) (and, in some embodiments, performing the first operation in response to receiving the first data) the second transfer operation using the second application (e.g., application indicated by  604   a ,  704   a ,  604   b ,  704   b ) (e.g., a transaction (e.g., a payment transaction; a purchase)). In some embodiments, the first data includes one or more parameters or variables that affect the operation (e.g., an amount of a purchase; an item for purchase. In some embodiments, as a part of performing the second transfer operation, the computer system transmits, to the external receiving device, fourth data that includes information that identifies the third account (e.g., Jane&#39;s Account as indicated by  712 , Jane&#39;s card as indicated by  734 ) (e.g., an encrypted representation of the account (e.g., a device specific account number) stored on the computer system; a representation of a payment account (e.g., a credit, debit, and/or cash balance account)). In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., a price; a quantity). Performing a second transfer operation using a second application on a computer system, based on an input on an automotive head unit provides the user with the ability to perform the second transfer operation without having to directly interact with the computer system. Performing the operation without having to directly interact with the computer system can increase user safety while using the computer system and operating an automobile. Performing a transfer operation using an application on a computer system, based on an input on an automotive head unit, also provides the user with the option to perform the operation using inputs on the head unit. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the computer system (e.g.,  600 ) is in communication with (e.g., includes) a display generation component (e.g., a display (e.g., an integrated, touchscreen display)), wherein the display generation component is in a locked state (e.g.,  760 ) (e.g., a state in which one or functions of the display (e.g., display functions; input functions), which are available in an unlocked state, are disabled/unavailable) while the computer system (e.g.,  600 ) receives the first data. Performing a transfer operation using an application on a computer system, based on an input on an automotive head unit, while the computer system is in a locked state also provides the user with the option to perform the operation using inputs on the head unit without having to separately unlock the computer system, which can reduce the risk of unintentional inputs at the computer system; doing so also enhances security of the system by allowing the computer system to remain in a locked state more often (e.g., while still being useable). Providing additional control options and improving security enhances the operability of the computer system 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) and secure which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the computer system more quickly, efficiently, and securely. 
     In some embodiments, the external automotive head unit (e.g.,  700 ) has been (e.g., prior to receiving the first data) authorized (e.g., the external automotive head unit is a trusted unit; authorized via input from a user) to request performance of transfer operations from the first account (e.g., Jane&#39;s Account as indicated by  712 , Jane&#39;s card as indicated by  734 ) (e.g., and from other accounts accessible from and/or stored on the computer system). In some embodiments, external automotive head units that are not authorized (e.g., trusted) cannot request performance of transfer operations from accounts accessible and/or stored on the computer system. Performing a transfer operation using an application on a computer system, based on an input on an automotive head unit, only if that unit is authorized, reduces the risk of unauthorized operations (e.g., particularly if the user of the computer system is not in control of inputs provided at the head unit). Reducing the risk of unauthorized operations and improving security of the computer system enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, prior to detecting the first data (e.g., data associated with input  752   g ,  752   h ,  752   j , or  752   k ), the computer system receives a first set of one or more inputs (e.g.,  750   c   1 ,  750   c   2 ) (e.g., inputs at the external automotive head unit and/or the computer system). In some embodiments, in response to the first set of one or more inputs (e.g.,  750   a ,  750   b    750   c   1 ,  7502 ), the computer system authorizes (e.g., authorizing before being in communication) connection of the external automotive head unit (e.g.,  700 ) to the computer system (e.g.,  600 ) while the computer system is in a locked state (e.g.,  760 ) (e.g., a state in which one or more functions of the computer system, which are available while in an unlocked state, are unavailable)); and authorizes the external automotive head unit (e.g.,  700 ) to request performance of transfer operations from the first account (e.g., and from other accounts accessible from and/or stored on the computer system). Authorizing the external automotive head unit to request performance of transfer operations based on prior user input provides the user with additional control options and reduces the need for authorization inputs on a per-operation basis. Providing additional control options and performing operations without requiring inputs at certain times enhances the operability of the computer system 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 computer system more quickly and efficiently. Performing transfer operations with an authorized (e.g., trusted) external automotive head unit also increases security by reducing the risk of unauthorized requests for transfer operations. Reducing the risk of unauthorized operations and improving security of the computer system enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, while the computer system is in communication with (e.g., while connected to) the external automotive unit (e.g.,  700 ) and while the computer system (e.g.,  600 ) is in locked state (e.g.,  760 ) (e.g., a state in which one or more functions of the computer system, which are available while in an unlocked state, are unavailable), the computer system receives a second set of one or more inputs (e.g.,  750   a ). In some embodiments, in response to the second set of one or more inputs (e.g.,  750   a ), the computer system: transitions the computer system (e.g.,  600 ) to an unlocked state (e.g.,  602 ) (e.g., a state in which one or more functions of the computer system, which were unavailable while in the locked state, are available); and authorizes the external automotive head unit (e.g.,  700 ) to request performance of transfer operations from the first account (e.g., and from other accounts accessible from and/or stored on the computer system). In some embodiments, authorizing occurs concurrently as part of (e.g., is a consequence of) transitioning the computer system to the unlocked state. Authorizing the external automotive head unit to request performance of transfer operations based on a user input that also unlocks the computer system reduces the number of inputs required to perform a set of operations and also reduces the risk of unintentional operation of the computer system, as unlocking the computer system correlates to intentional use of the system. Reducing the number of inputs required to a perform a set of operations and reducing the risk of unintentional operation input 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 and efficiently. Authorizing the external automotive head unit to request performance of transfer operations based on a user input that also unlocks the computer system improves security by providing the user with an option to link authorization of the unit with another authorization function. Improving security of the computer system enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, prior to receiving the first data (e.g., data associated with input  752   g ,  752   h ,  752   j , or  752   k ), the computer system transmits, to the automotive head unit, fifth data that includes one or more user interface elements (e.g.,  718 ,  738 ) to be displayed by the automotive head unit. In some embodiments, the one or more user interface elements include one or more elements associated with the application (e.g., an identifier of the application) and/or associated with the first account (e.g., an identifier of the first account). Transmitting data that includes one or more user interface elements to be displayed by the automotive head unit provides the user with visual feedback concerning the computer system and its connection to the head unit. Providing improved visual feedback to the user enhances the operability of the computer system 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 computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the computer system (e.g.,  600 ) is a smartphone (e.g., a mobile computing device configured to make and receive telephone calls over a cellular network)) that includes a hardware secure element (e.g., a chip that stores information representative of an account (e.g., account-related information, such as a device-specific account number (e.g., that is different than the account number) provided by an issuer of an account) that is not directly accessible to the operating system or installed applications of the computer system). In some embodiments, the secure element does not store or have access to the primary account number. In some embodiments, the secure element provides, as part of a transfer operation, an encrypted version of the device specific account number (e.g., a version unique to a given transaction) that is decrypted by the issuer of the account in order to identify the account). In some embodiments, the information that identifies the first account is stored in the hardware secure element. 
     In some embodiments, while the computer system (e.g.,  600 ) is in communication ( 806 ) with a second external automotive head unit (e.g.,  700 ) that includes one or more input components and a second external receiving device, where the second external automotive head unit (e.g.,  700 ) is different from the external automotive head unit (e.g.,  700 ), the computer system receives ( 808 ), from the second external automotive head unit (e.g.,  700 ), sixth data corresponding to an input (e.g.,  752   g ,  752   h ,  752   j ,  752   k ) received at the one or more input components of the second external automotive head unit that corresponds to a request to perform a third transfer operation from the first account to a fifth account (e.g., an account associated with a vendor) using the application (e.g., a digital storefront application; a digital wallet application; an e-commerce application; an application that is different from the first or second applications; an application that is the same as the first and/or the second applications). In some embodiments, while the computer system (e.g.,  600 ) is in communication with ( 806 ) a second external automotive head unit (e.g.,  700 ) that includes one or more input components and a second external receiving device, the computer system, in response to receiving the sixth data, initiates ( 810 ) a process to perform (e.g., a process that can require one or more additional inputs (e.g., inputs at the computer system, to fully complete) the third transfer operation using the application on the computer system (e.g.,  600 ). In some embodiments, as a part of performing the third transfer operation, the computer system transmits, to the second external receiving device, seventh data that includes information that identifies the first account. (e.g., an encrypted representation of the account (e.g., a device specific account number) stored on the computer system; a representation of a payment account (e.g., a credit, debit, and/or cash balance account). In some embodiments, the first operation is performed in response to receiving the first data. In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., a price; a quantity). Providing different head units with the ability to request transfer operations at the computer system provides the user with additional options for operating the computer system. Providing additional control options and performing operations without requiring inputs at certain times enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     Note that details of the processes described above with respect to method  800  (e.g.,  FIG.  8   ) are also applicable in an analogous manner to the methods described below. For example, method  800  optionally includes one or more of the characteristics of the various methods described below with reference to method  900 . For example, method  800  can be used to initiate a process to perform the first transfer operation (e.g.,  804 ) when the external input device satisfies a set of authorization criteria and provides an option to initiate the secure transaction (e.g., in  906 ). For brevity, these details are not repeated below. 
       FIG.  9    is a flow diagram illustrating a method for providing an option to initiate a secure operation using a computer system in accordance with some embodiments. Method  900  is performed at a computer system (e.g.,  100 ,  300 ,  500 ,  600 ). Some operations in method  900  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  900  provides an intuitive way for providing an option to initiate a secure operation using a computer system. The method reduces the cognitive burden on a user for providing an option to initiate a secure operation using a computer system, thereby creating a more efficient human-machine interface. The method also enables a user to perform secure operations safer and more securely using a computer system. For battery-operated computing devices, enabling a user to providing an option to initiate a secure operation using a computer system faster, and more efficiently conserves power and increases the time between battery charges. 
     While the computer system (e.g.,  600 ) is connected to an external input device (e.g.,  700 ) (e.g., an automotive head unit (e.g., a unified hardware interface for a plurality of entertainment and information systems (e.g., sound; navigation) of an automobile (e.g., a stereo head unit; an infotainment system))), the computer system receives ( 902 ) a first request (e.g.,  752   d   1 ,  752   d   2 ) (e.g., selection of option or a variable) from the external input device to interact with a first portion of a user interface (e.g.,  710 ,  730 ) (e.g., a an interface of digital storefront application; a digital wallet application; an e-commerce application; an interface displayed at the external input device (e.g., that is generated, at least in part, based on data from the computer system)) that is associated with a secure transaction (e.g., a transfer of resources (e.g., credits; funds) from a first account (e.g., an account associated with a user of the computer system) to a second account (e.g., an account associated with a merchant)) that, if authorized from the computer system (e.g.,  600 ), would require separate authorization (e.g.,  646   a ,  646   b ,  638 ) from the user (e.g., a transaction that requires additional authentication when performed on the computer system via one or more inputs received via one or more input devices of the computer system such as entry of a passcode or biometric authentication via fingerprint, facial, iris or other biometric authentication). 
     In response to ( 904 ) receiving the first request (e.g.,  752   d   1 ,  752   d   2 ) and in accordance with a determination that the external input device (e.g.,  700 ) satisfies a set of authorization criteria (e.g., a set of criteria that is satisfied when the external input device has been authorized by a previous user input, when the external input device is a device of a first type, and/or when the external input device is not a device of a second type), the computer system provides ( 906 ) an option (e.g.,  718 ) (e.g., a selectable user interface object; a prompt (e.g., a visual or audio prompt) to use one or more input devices (e.g., a touch-sensitive surface; a microphone) of the external input device), via the external input device (e.g.,  700 ), to initiate a secure transaction without requiring the separate authorization from the user. 
     In response to ( 904 ) receiving the first request (e.g.,  752   d   1 ,  752   d   2 ) and in accordance with a determination that the external input device (e.g.,  700 ) does not satisfy the set of authorization criteria, the computer system forgoes ( 912 ) providing the option (e.g.,  716  in  FIG.  7 E ) to initiate a secure transaction without requiring the separate authorization from the user. In some embodiments, as a part of forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user, the computer system provides a second option to initiate the secure transaction that requires separate authorization from the user at the external input device and/or the computer system. Providing an option to initiate a secure transaction without requiring separate authorization from the user in response to a request at an external input device provides the user with the option to perform the secure transaction without requiring the separate authorization and without having to directly interact with the computer system. Providing an option to perform the operation without having to directly interact with the computer system and reducing the number of required inputs can increase the ease of use of the computer; doing so also provides the user with the option to perform the operation using inputs on the external input device. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. Providing an option to initiate a secure transaction if the external input device satisfies a set of authorization criteria increases security by not providing the option when the external input device does not satisfy the criteria. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) is an external automotive head unit (e.g., a unified hardware interface for a plurality of entertainment and information systems (e.g., sound; navigation) of an automobile (e.g., a stereo head unit; an infotainment system)). In some embodiments, the computer system (e.g.,  600 ) is a smartphone (e.g., a mobile computing device configured to make and receive telephone calls over a cellular network)) that includes a hardware secure element (e.g., a chip that stores information representative of an account (e.g., account-related information, such as a device-specific account number (e.g., that is different than the account number) provided by an issuer of an account) that is not directly accessible to the operating system or installed applications of the computer system) for use in the secure transaction. In some embodiments, the secure element does not store or have access to the primary account number. In some embodiments, the secure element provides, as part of a transfer operation, an encrypted version of the device specific account number (e.g., a version unique to a given transaction) that is decrypted by the issuer of the account in order to identify the account. 
     In some embodiments, the computer system (e.g.,  600 ) includes one or more external device communication interfaces (e.g., a communication system for transferring data between the computer system and one or more external devices; a wired communication bus; a wireless communication bus; a data bus). In some embodiments, the computer system detects, via the one or more external device communication interfaces, connection (e.g.,  708 ) of the computer system to the external input device. In some embodiments, the first request (e.g.,  752   d   1 ,  752   d   2 ) is received after detecting connection of the computer system to the external input device. 
     In some embodiments, the computer system (e.g.,  600 ) is in communication with one or more hardware input devices (e.g., touch-sensitive display of  600 ) (e.g., a touch-sensitive surface (e.g., a touchscreen); a microphone; a biometric reader (e.g., a fingerprint reader; an optical and/or depth sensor for detecting facial features)). In some embodiments, the secure transaction, when authorized from the computer system (e.g.,  600 ) (e.g., rather than the external input device), requires authorization from the user provided via the one or more hardware input devices (e.g., authorization to perform the secure transaction using information from a hardware secure element (e.g., a chip that stores account information that is not directly accessible to the operating system or installed applications of the computer system) that stores information (e.g., account information; information that identifies an account) for use in the secure transaction). In some embodiments, the computer receives a request at the computer system to perform the secure transaction. In some embodiments, after receiving the first request and in accordance with a determination that authorization has been provided (e.g., provided before receiving the first request; provided after receiving the first request), via the one or more hardware input devices, the computer system performs the secure transaction. Requiring authorization to perform the secure transaction improves security by reducing the risk of unauthorized requests. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the one or more hardware input devices includes a biometric reader (e.g.,  646   a ,  646   b ) (e.g., a fingerprint reader; an optical and/or depth sensor for detecting facial features)) and the authorization from the user provided via the one or more hardware input devices is a biometric authorization (e.g., indicated by  628 ,  630 ) (e.g., an authorized fingerprint scan or an authorized face scan) received via the biometric reader (e.g.,  646   a ,  646   b ) (e.g., authorization to perform the secure transaction using information from a hardware secure element (e.g., a chip that stores account information that is not directly accessible to the operating system or installed applications of the computer system) that stores information (e.g., account information; information that identifies an account) for use in the secure transaction). Requiring authorization via a biometric reader improves security by reducing the risk of unauthorized requests. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, after providing the option (e.g.,  718 ) to initiate a secure transaction without requiring the separate authorization from the user, receiving ( 908 ) a request (e.g.,  752   g ,  752   h ) from the external input device (e.g.,  700 ) to proceed with the secure transaction (e.g., an input; selection of a payment selectable user interface object displayed at a display of the external input device; a voice command received at the external input device). In some embodiments, as a part of providing the option, the computer system transmits, to the external input device, data that includes one or more user interface elements to be displayed by the external input device). In some embodiments, in response to receiving the request from the external input device (e.g.,  700 ) to proceed with the secure transaction, the computer system performs ( 910 ) the secure transaction including securely transmitting to an external receiving device (e.g., a transaction management server; a payment terminal) first data that includes information that identifies a first account (e.g., “Jane&#39;s Account,” as indicated by  612 ,  712 ; “Jane&#39;s Card” as indicated by  734 ) (e.g., an encrypted representation of the account (e.g., a device specific account number) stored on the computer system; a representation of a payment account (e.g., a credit, debit, and/or cash balance account)) for use in the secure transaction. In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., a price; a quantity). Performing the secure transaction based on a request from the external input device provides the user with the option to perform the operation using inputs at the external input device. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the computer system (e.g.,  600 ) is in communication with (e.g., includes) a display generation component (e.g., a display (e.g., an integrated, touchscreen display)). In some embodiments, performing the secure transaction (e.g., including securely transmitting to the external receiving device the first data that includes information that identifies the first account) occurs while the display generation component is in a locked state (e.g.,  670 ) (e.g., a state in which one or functions of the display (e.g., display functions; input functions), which are available in an unlocked state, are disabled/unavailable). Performing the secure transaction while the display generation component in communication with the computer system is in a locked state provides the user with the option to perform the transaction without having to interact (e.g., view or provide inputs directed to the component) with the display generation component. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. Performing the secure transaction while the display generation component in communication with the computer system is in a locked state also increases security by allowing the computer system to remain in the locked state, while still permitting interactions via the external input device. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the secure transaction is performed using a first application (e.g., application that corresponds to  604   a ,  604   b ) on the computer system (e.g.,  600 ). In some embodiments, the user interface (e.g.,  720 ,  760 ) is an interface displayed at the external input device (e.g.,  700 ). In some embodiments, the user interface (e.g.,  720 ,  760 ) is arranged according to a first interface layout template (e.g., a scheme for arranging the graphical elements and/or contents of the interface) and includes (e.g.,  722 ,  762 ) information provided by the first application (e.g., application that corresponds to  604   a ,  604   b ) (e.g., an identifier (e.g., textual and/or graphical) of the first application; a parameter that affects performance of the secure transaction (e.g., an amount of credit or currency being transferred); a service or goods being purchased); an identifier of an account to be used within the secure transaction). In some embodiments, the computer system receives a second request (e.g.,  752   d   1 ,  752   d   2 ) from the external input device (e.g.,  700 ) to interact with a first portion of a second user interface (e.g.,  720 ,  760 ) (e.g., an interface that is the same as the user interface; an interface that is different from the user interface) that is displayed at the external input device (e.g.,  700 ) and associated with a second secure transaction performed using a second application (e.g., application that corresponds to  604   a ,  604   b ) on the computer system (e.g.,  600 ) that, if authorized from the computer system (e.g.,  600 ), would require separate authorization from the user. In some embodiments, the second application (e.g., application that corresponds to  604   a ,  604   b ) is different from the first application. In some embodiments, the second user interface (e.g.,  720 ,  760 ) is arranged according to the first interface layout template and includes information (e.g.,  722 ,  762 ) (e.g., an identifier (e.g., textual and/or graphical) of the second application; a parameter that affects performance of the secure transaction (e.g., an amount of credit or currency being transferred); a service or goods being purchased); an identifier of an account to be used within the second secure transaction) provided by the second application (e.g., application that corresponds to  604   a ,  604   b ). Arranging interfaces corresponding to different applications for performing different secure transactions according to the same interface layout provides the user with improved visual feedback that consistently informs the user about aspects of the secure transactions. Providing improved visual feedback to the user enhances the operability of the computer system 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 computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the set of authorization criteria is satisfied when: the computer system, prior to receiving the first request (e.g.,  752   d   1 ,  752   d   2 ) (e.g., and while not detecting movement of an automobile connected to the external input device), received a first set of one or more inputs (e.g.,  750   a ) (e.g., selection of an option in a peripheral management interface; a set of inputs received at the external input device; a set of inputs received at the computer system). In some embodiments, in response to the first set of one or more inputs (e.g.,  750   a ), the computer system authorized (e.g., authorizing before being in communication with the external input device) connection of the external input device (e.g.,  700 ) to the computer system (e.g.,  600 ) while the computer system is in a locked state (e.g.,  670 ) (e.g., a state in which one or more functions of the computer system, which are available while in an unlocked state, are unavailable)). Authorizing connection of the external input device to the computer system while the computer system is in a locked state provides the user with additional control options and reduces the need for authorization inputs at the time the secure transaction is requested. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. Satisfying the authorization criteria based on a previous input that also authorized connection of the external input device to the computer system while in a locked state increases security by linking authorization features to reduce the risk of unintentional authorization. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on a status (e.g., a status that establishes a duration (e.g., permanent (e.g., until revoked), temporary (e.g., for a transient duration (e.g., 1 day, 1 week) or for a preset number of connection events (e.g., 1 connection event; 5 connection events)) for which the external input device will satisfy the set of authorization criteria) that is established (e.g., set) based on a second set of one or more inputs (e.g.,  750   b ,  750   c   1 ,  750   c   2 ) (e.g., selection of a second option in a peripheral management interface; a set of inputs received at the external input device; a set of inputs received at the computer system) that is received after having received the first set of one or more inputs (e.g.,  750   a ). Establishing a status of the external input device that affects satisfaction of the authorization criteria provides the user with additional control options for precisely controlling the relationship between the computer system and the external input device. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. Satisfying the authorization criteria based on a previous input increases security by providing the user with an opportunity to provide authorization outside the context of performing the particular secure transaction, which can reduce the risk of unintended authorization. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on the status being a long-term (e.g., indefinite until revoked) authorization status. In some embodiments, the first set of one or more inputs (e.g.,  750   a ,  750   b ,  752   c   1 ) was received while the computer system (e.g.,  600 ) is in a connection session (e.g., session that starts with connection of the computer system to the external input device and sends when that connection is discontinued) with the external input device (e.g.,  700 ) that is also the connection session during which the first request (e.g.,  752   d   1 ,  752   d   2 ) was received or while the computer system (e.g.,  600 ) was in a preceding connection session with the external input device (e.g.,  700 ) that is different from the connection session during which the first request (e.g.,  752   d   1 ,  752   d   2 ) was received. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on the status being a short-term (e.g., temporary or for a transient duration (e.g., 1 day, 1 week) or for a preset number of connection events (e.g., 1 connection event; 5 connection events); expiring without requiring further user input) authorization status. In some embodiments, the first set of one or more inputs (e.g.,  750   a ,  750   b ,  750   c   2 ) was received while the computer system is in a connection session (e.g., session that starts with connection of the computer system to the external input device and sends when that connection is discontinued) with the external input device (e.g.,  700 ) that is also the connection session during which the first request (e.g.,  752   d   1 ,  752   d   2 ) was received. In some embodiments, the set of one or more inputs was not received (e.g., cannot be received) while the computer system was in a preceding connection session with the external input device that is different from the connection session during which the first request was received, when the status is a temporary authorization status. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on an input (e.g.,  750   a ,  750   b ,  750   c   1 ,  750   c   2 ) (e.g., selection of an option in a peripheral management interface), received prior to receiving the first request (e.g., prior to connecting to the external input device), the computer system authorizes (e.g., pre-authorizing) the external input device (e.g.,  700 ) to provide requests to initiate one or more secure transactions that, if authorized from the computer system (e.g.,  600 ), would require separate authorization from the user. In some embodiments, the input authorizing (e.g., pre-authorizing) the external input device to provide requests to initiate one or more secure transactions that, if authorized from the computer system, would require separate authorization from the user is different from an input authorizing the external input device to connect to the computer system while the computer system is in a locked state (e.g., a state in which one or more functions of the computer system, which are available while in an unlocked state, are unavailable). Authorizing the external input device based on a prior input allows the user to better control the relationship between the computer system and the external input device. Providing additional control options enhances the operability of the computer system 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 computer system more quickly and efficiently. Satisfying the authorization criteria based on a previous and explicit input authorizing secure transactions, reduces the risk of unintended authorization and increases security. Improving security of the computer system enhances the operability of the computer system 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 computer system more securely, quickly, and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on an input (e.g.,  750   a ) (e.g., acceptance of a prompt to provide authorization), received while connected to the external input device (e.g.,  700 ) (e.g., while connected in the same connection session during which the first request is received), the computer system authorizes the external input device (e.g.,  700 ) to provide requests to initiate one or more secure transactions that, if authorized from the computer system (e.g.,  600 ), would require separate authorization from the user. Authorizing the external input device based on an input received while connected to the external input device allows the user to better control the relationship between the computer system and the external input device and also reduces the risk of unintentionally authorizing the wrong device. Providing additional control options and reducing the risk of error enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) satisfies the set of authorization criteria based on the external input device (e.g.,  700 ) being identified as being a first type of device (e.g., a type of device that is pre-authorized (e.g., a device from a specific manufacturer; a type of device having specific hardware (e.g., secure hardware); a type of device having specific software (e.g., secure software)). In some embodiments, external input devices of a second type (e.g., not of the first type) do not satisfy the set of authorization criteria. Authorizing the external input device based on the device being a device of a first type reduces the risk that devices without the necessary characteristics are authorized, thereby increasing security and also reduces the need for explicit inputs to authorize devices of the first type. Increasing security and reducing the number of inputs required to perform an operation enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     In some embodiments, the external input device (e.g.,  700 ) (e.g., an automotive head unit (e.g., a unified hardware interface for a plurality of entertainment and information systems (e.g., sound; navigation) of an automobile (e.g., a stereo head unit; an infotainment system))) satisfies the set of authorization criteria based on the external input device being connected to a vehicle (e.g., an automobile; a motorcycle) identified as having authorized authentication hardware (e.g., an authenticated identity chip). Authorizing the external input device based on the device being connected to a vehicle identified as having authorized authentication hardware increases security and also reduces the need for explicit inputs to authorize devices connected to such vehicles. Increasing security and reducing the number of inputs required to perform an operation enhances the operability of the computer system 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 computer system more quickly and efficiently. 
     Note that details of the processes described above with respect to method  900  (e.g.,  FIG.  9   ) are also applicable in an analogous manner to the methods described below. For example, method  900  optionally includes one or more of the characteristics of the various methods described above with reference to method  800 . For example, method  800  can be used to initiate a process to perform the first transfer operation (e.g.,  804 ) when the external input device satisfies a set of authorization criteria and provides an option to initiate the secure transaction (e.g., in  906 ). For brevity, these details are not repeated below. 
     The foregoing description, for the 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 management and security of operations (e.g., transactions) being performed at various devices. 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 provide authorization for an electronic device to perform secure operations (e.g., transactions) based on the personal information that is provided. Accordingly, use of such personal information data enables a user to have calculated control and/or increased security with regards to the secure operations that are performed via the electronic device. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user&#39;s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals. 
     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, in the case of performing secure operations (e.g., payment transactions), the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select to provide other information (e.g., such as a password) to perform one or more secure operations using the electronic device. In yet another example, users can select to limit the length of time the gathered data (e.g., biometric data) is maintained or entirely prohibit the authorization of operations based on the gathered data. 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. For example, secure operations can be performed based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to authorization systems, or publicly available information.

Metadata:
Filing Date: 20201021
Publication Date: 20231114
Grant Date: 20231114
Priority Date: 20200621
Inventors: BOULE, Andre M.
CHICK, STEPHEN
DELLINGER, RICHARD R.
LANGSTROTH, EDWARD H.
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F21/31", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/54", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/606", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/83", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2221/2149", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04W12/062", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04W12/084", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F21/31", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04L63/0884", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/48", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04W12/084", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W12/50", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/6218", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W12/062", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W12/50", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/48", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/31", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/606", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/6218", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/83", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/54", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L63/0884", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/83", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F21/606", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2221/2149", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/54", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 79023566