Sharing or using passes or accounts

Abstract

To provide a computer system that displays user interfaces for accessing passes and transfer accounts, and a method thereof.SOLUTION: A method includes: displaying a user interface including an indication of an account; receiving authentication data; in response to receiving the authentication data, in accordance with a determination that the authentication data satisfies authentication criteria associated with the account, displaying a first machine-readable code associated with the account; and in response to receiving the authentication data and in accordance with a determination that the authentication data does not satisfy the authentication criteria associated with the account, stopping display of the first machine-readable code associated with the account.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is a continuation of U.S. patent application Ser. No. 17 / 030,260, filed Sep. 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. patent application Ser. No. 17 / 030,259, filed Sep. 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. patent application Ser. No. 17 / 030,257, filed Sep. 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. patent application Ser. No. 17 / 030,256, filed Sep. 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. provisional patent application Ser. No. 63 / 041,996, filed Jun. 21, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", and U.S. provisional patent application Ser. No. 63 / 041,996, filed Jun. 21, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS". This application claims the benefit of U.S. Provisional Patent Application No. 63 / 032,504, filed May 29, 2020, entitled "METHOD ACCOUNTS," the entire contents of which are incorporated herein by reference.

[0002] (Technical field) The present disclosure relates generally to computer user interfaces, and more specifically to interfaces and techniques for sharing and using passes or accounts. [Background technology]

[0003] The computer system can be used to access information related to a pass or account. The information can then be used to provide goods or services to a user, such as to gain admission to a venue or to transfer funds. Typically, the information related to a pass or account is associated with a user of the computer system. Summary of the Invention

[0004] However, some techniques for using passes or accounts with computer systems are generally cumbersome and inefficient. For example, some existing techniques offer limited options for sharing a pass with another user. In addition, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes to use a pass or account. Existing techniques take more time than necessary, wasting the user's time and the device's energy. This latter consideration is particularly important in battery-operated devices.

[0005] Thus, the present technology provides computer systems with faster, more efficient methods and interfaces for sharing and using passes or accounts. Such methods and interfaces optionally complement or replace other methods for using passes or accounts. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] An exemplary method is disclosed herein, the exemplary method including, in a computer system in communication with a display generating component and one or more input devices, displaying, via the display generating component, a first user interface including information regarding one or more passes associated with a service provider, receiving, while displaying the first user interface, via the one or more input devices, a request to add one or more passes to an account associated with a first user ID, the one or more passes providing access to services provided by the service provider, displaying, via the display generating component, a sharing affordance for providing at least one of the one or more passes to an account associated with a second user ID after receiving the request, receiving, via the one or more input devices, a user input corresponding to a selection of the sharing affordance, and in response to receiving the user input corresponding to the selection of the sharing affordance, initiating a process for providing at least one of the one or more passes to the account associated with the second user ID.

[0007] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for displaying, via the display generating component, a user interface, a first user interface including information about one or more passes associated with a service provider, receiving, while displaying the first user interface, via the one or more input devices, a request to add one or more passes providing access to a service provided by the service provider to an account associated with a first user ID, after receiving the request, displaying, via the display generating component, a shared affordance for providing at least one of the one or more passes to an account associated with a second user ID, receiving, via the one or more input devices, a user input corresponding to a selection of the shared affordance, and in response to receiving the user input corresponding to the selection of the shared affordance, initiating a process for providing at least one of the one or more passes to the account associated with the second user ID.

[0008] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for displaying, via the display generating component, a user interface, a first user interface including information about one or more passes associated with a service provider, receiving, while displaying the first user interface, via the one or more input devices, a request to add one or more passes providing access to a service provided by the service provider to an account associated with a first user ID, after receiving the request, displaying, via the display generating component, a shared affordance for providing at least one of the one or more passes to an account associated with a second user ID, receiving, via the one or more input devices, a user input corresponding to a selection of the shared affordance, and in response to receiving the user input corresponding to the selection of the shared affordance, initiating a process for providing at least one of the one or more passes to the account associated with the second user ID.

[0009] An exemplary computer system is described herein. The exemplary computer system comprises a display generating component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to: display, via the display generating component, a first user interface including a graphical object that changes appearance based on a noise level; receive, while displaying the first user interface, via the one or more input devices, a request to add one or more paths providing access to a service provided by a service provider to an account associated with a first user ID; after receiving the request, display, via the display generating component, a shared affordance for providing at least one of the one or more paths to an account associated with a second user ID; receive, via the one or more input devices, user input corresponding to a selection of the shared affordance; and initiate a process for providing at least one of the one or more paths to the account associated with the second user ID in response to receiving the user input corresponding to the selection of the shared affordance.

[0010] An exemplary computer system comprises a display generating component, one or more input devices, and means for displaying, via the display generating component, a first user interface including information regarding one or more passes associated with the service provider; means for receiving, while displaying the first user interface, a request to add one or more passes providing access to services offered by the service provider to an account associated with a first user ID, via the one or more input devices; means for displaying, via the display generating component, a shared affordance for providing at least one of the one or more passes to an account associated with a second user ID after receiving the request; and means for receiving, via the one or more input devices, user input corresponding to a selection of the shared affordance, and in response to receiving the user input corresponding to the selection of the shared affordance, initiating a process for providing at least one of the one or more passes to the account associated with the second user ID.

[0011] An exemplary method is disclosed herein, the exemplary method including: detecting, in a computer system in communication with a display generating component and one or more input devices, that data corresponding to a first path has been provided by the computer system to a pass reader terminal separate from the computer system; displaying, via the display generating component, an indication that data corresponding to the first path has been provided by the computer system to the pass reader terminal after detecting that data corresponding to the first path has been provided by the computer system to the pass reader terminal; providing a prompt to a user to provide authorization for data corresponding to the second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to the second path is available to be provided by the computer system to the pass reader terminal; and ceasing to provide the prompt to the user to provide authorization for data corresponding to the second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to the second path is not available to be provided by the computer system to the pass reader terminal.

[0012] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for detecting that data corresponding to a first path has been provided by the computer system to a pass reader terminal separate from the computer system, displaying, via the display generating component, an indication that data corresponding to the first path has been provided by the computer system to the pass reader terminal after detecting that data corresponding to the first path has been provided by the computer system to the pass reader terminal, providing a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to a second path is available to be provided by the computer system to the pass reader terminal, and ceasing to provide a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to the second path is not available to be provided by the computer system to the pass reader terminal.

[0013] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for detecting that data corresponding to a first path has been provided by the computer system to a pass reader terminal separate from the computer system, displaying, via the display generating component, an indication that data corresponding to the first path has been provided by the computer system to the pass reader terminal after detecting that data corresponding to the first path has been provided by the computer system to the pass reader terminal, providing a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to a second path is available to be provided by the computer system to the pass reader terminal, and ceasing to provide a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to the second path is not available to be provided by the computer system to the pass reader terminal.

[0014] An exemplary computer system is described herein. The exemplary computer system comprises a display generating component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for detecting that data corresponding to a first path has been provided by the computer system to a pass reader terminal separate from the computer system, displaying, via the display generating component, an indication that the data corresponding to the first path has been provided by the computer system to the pass reader terminal after detecting that the data corresponding to the first path has been provided by the computer system to the pass reader terminal, providing a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to a second path is available to be provided by the computer system to the pass reader terminal, and ceasing to provide a prompt to a user to provide authorization for data corresponding to a second path provided by the computer system to the pass reader terminal in accordance with a determination that data corresponding to the second path is not available to be provided by the computer system to the pass reader terminal.

[0015] An exemplary computer system includes a display generating component, one or more input devices, means for detecting that data corresponding to a first path has been provided by the computer system to a pass reader terminal separate from the computer system, means for displaying an indication via the display generating component that data corresponding to the first path has been provided by the computer system to the pass reader terminal after detecting that data corresponding to the first path has been provided by the computer system to the pass reader terminal, means for providing a prompt to a user to provide authorization for data corresponding to the second path to be provided by the computer system to the pass reader terminal pursuant to a determination that data corresponding to the second path is available to be provided by the computer system to the pass reader terminal, and means for ceasing to provide the prompt to the user to provide authorization for data corresponding to the second path to be provided by the computer system to the pass reader terminal pursuant to a determination that data corresponding to the second path is not available to be provided by the computer system to the pass reader terminal.

[0016] An exemplary method is disclosed herein that includes, at a computer system in communication with a display generating component and one or more input devices, displaying via the display generating component a first user interface including an indication of an account, receiving via the one or more input devices authentication data, in response to receiving the authentication data, displaying via the display generating component a first machine-readable code associated with the account in accordance with a determination that the authentication data meets an authentication criterion associated with the account, and ceasing to display the first machine-readable code associated with the account in accordance with a determination that the authentication data does not meet an authentication criterion associated with the account.

[0017] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for displaying, via the display generating component, a first user interface including an indication of the account, receiving, via the one or more input devices, and in response to receiving the authentication data, displaying, via the display generating component, a first machine-readable code associated with the account in accordance with a determination that the authentication data meets an authentication criterion associated with the account, and ceasing to display the first machine-readable code associated with the account in accordance with a determination that the authentication data does not meet an authentication criterion associated with the account.

[0018] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for displaying, via the display generating component, a first user interface including an indication of the account, receiving, via the one or more input devices, and in response to receiving the authentication data, displaying, via the display generating component, a first machine-readable code associated with the account in accordance with a determination that the authentication data meets an authentication criterion associated with the account, and ceasing to display the first machine-readable code associated with the account in accordance with a determination that the authentication data does not meet an authentication criterion associated with the account.

[0019] An exemplary computer system is described herein comprising a display generating component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying, via the display generating component, a first user interface including an indication of the account, receiving, via the one or more input devices, and in response to receiving the authentication data, displaying, via the display generating component, a first machine-readable code associated with the account in accordance with a determination that the authentication data meets an authentication criterion associated with the account, and ceasing to display the first machine-readable code associated with the account in accordance with a determination that the authentication data does not meet an authentication criterion associated with the account.

[0020] An exemplary computer system comprises a display generating component, one or more input devices, means for displaying a first user interface including an indication of the account via the display generating component, means for receiving authentication data via the one or more input devices, means for displaying a first machine-readable code associated with the account via the display generating component in response to receiving the authentication data and in accordance with a determination that the authentication data meets an authentication criterion associated with the account, and means for ceasing display of the first machine-readable code associated with the account in accordance with a determination that the authentication data does not meet an authentication criterion associated with the account.

[0021] Exemplary methods are disclosed herein. An example method includes, in a computer system in communication with a display generation component and one or more input devices, displaying, via the display generation component, an account user interface including a plurality of visual representations of a plurality of different accounts; receiving, while displaying the account user interface, a scroll input corresponding to a request to scroll the account user interface, via the one or more input devices; in response to receiving the scroll input, scrolling, via the display generation component, the account user interface to scroll a first visual representation of a first account and a second visual representation of a second account; after receiving the scroll input, while displaying the account user interface, in accordance with a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria including a criterion that is met when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the second visual representation of the second account; and in accordance with a determination that the second visual representation of the second account satisfies the set of selection criteria, reducing a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the second visual representation of the second account.

[0022] An exemplary non-transitory computer readable storage medium is described herein. The exemplary non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs displaying, via the display generation component, an account user interface including a plurality of visual representations of a plurality of different accounts, receiving, while displaying the account user interface, via the one or more input devices, a scroll input corresponding to a request to scroll the account user interface, and in response to receiving the scroll input, scrolling, via the display generation component, the account user interface to display a first visual representation of a first account. instructions for scrolling the representation and the second visual representation of the second account, and after receiving a scroll input, while displaying the account user interface, in accordance with a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria including criteria that are met when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing a visual emphasis of the second visual representation of the second account relative to a visual emphasis of the first visual representation of the first account, and in accordance with a determination that the second visual representation of the second account satisfies the set of selection criteria, reducing a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the second visual representation of the second account.

[0023] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs displaying, via the display generation component, an account user interface including a plurality of visual representations of a plurality of different accounts, receiving, while displaying the account user interface, via the one or more input devices, a scroll input corresponding to a request to scroll the account user interface, and in response to receiving the scroll input, scrolling, via the display generation component, the account user interface to display a first visual representation of a first account. The instructions include: scrolling the second visual representations of the current and second accounts, and after receiving a scroll input, while displaying the account user interface, in accordance with a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria including criteria that are met when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing a visual emphasis of the second visual representation of the second account relative to a visual emphasis of the first visual representation of the first account, and in accordance with a determination that the second visual representation of the second account satisfies the set of selection criteria.

[0024] An exemplary computer system is described herein. The exemplary computer system comprises a display generation component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs displaying, via a display device, an account user interface including a plurality of visual representations of a plurality of different accounts, receiving, while displaying the account user interface, via the one or more input devices, a scroll input corresponding to a request to scroll the account user interface, and in response to receiving the scroll input, scrolling, via the display generation component, the account user interface to display a first visual representation of a first account. instructions for scrolling the representation and the second visual representation of the second account, and after receiving a scroll input, while displaying the account user interface, in accordance with a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria including criteria that are met when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing a visual emphasis of the second visual representation of the second account relative to a visual emphasis of the first visual representation of the first account, and in accordance with a determination that the second visual representation of the second account satisfies the set of selection criteria, reducing a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the second visual representation of the second account.

[0025] An exemplary computer system comprises a display generating component, one or more input devices, and means for displaying, via the display generating component, an account user interface including a plurality of visual representations of a plurality of different accounts; means for receiving, while displaying the account user interface, a scroll input corresponding to a request to scroll the account user interface via the one or more input devices; means for scrolling, via the display generating component, the account user interface to scroll a first visual representation of a first account and a second visual representation of a second account in response to receiving the scroll input; and means for reducing, while displaying the account user interface, a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the first visual representation of the first account in accordance with a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria including a criterion that is met when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing a visual emphasis of the first visual representation of the first account relative to a visual emphasis of the second visual representation of the second account in accordance with a determination that the second visual representation of the second account satisfies the set of selection criteria.

[0026] Exemplary methods are disclosed herein. An example method includes, at a computer system in communication with a display generation component and one or more input devices, receiving a first input via the one or more input devices; in response to receiving the first input, displaying via the display generation component an account user interface including a first visual representation of the first account; receiving a second input via the one or more input devices while displaying the first visual representation of the first account, the second input corresponding to a selection of the first visual representation of the first account; in response to receiving the second input corresponding to the selection of the first visual representation of the first account, displaying via the display generation component a readable portion of machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to prepare the one or more accounts for use from the account user interface; and in response to a determination that the first visual representation of the first account was displayed in response to a request to view information about the one or more accounts without preparing the one or more accounts for use from the account user interface, displaying information corresponding to the first account without displaying the readable portion of the machine readable code corresponding to the first account via the display generation component.

[0027] An exemplary non-transitory computer readable storage medium is described herein. The exemplary non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs receiving a first input via the one or more input devices, displaying, in response to receiving the first input, via the display generating component an account user interface including a first visual representation of a first account, receiving, while displaying the first visual representation of the first account, via the one or more input devices a second input corresponding to a selection of the first visual representation of the first account, and displaying, in response to receiving the first input, an account user interface including a first visual representation of a first account, the second input corresponding to a selection of the first visual representation of the first account, In response to receiving the power, the method includes instructions for: displaying, via the display generation component, a readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to prepare the one or more accounts for use from the account user interface; and displaying, via the display generation component, information corresponding to the first account without displaying the readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to view information about the one or more accounts without preparing the one or more accounts for use from the account user interface.

[0028] An exemplary temporary computer readable storage medium is described herein. The exemplary temporary computer readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs receiving a first input via the one or more input devices, and in response to receiving the first input, displaying via the display generation component an account user interface including a first visual representation of a first account, receiving, while displaying the first visual representation of the first account, via the one or more input devices a second input corresponding to a selection of the first visual representation of the first account, and displaying the second input corresponding to a selection of the first visual representation of the first account. In response to receiving the power, the method includes instructions for: displaying, via the display generation component, a readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to prepare the one or more accounts for use from the account user interface; and displaying, via the display generation component, information corresponding to the first account without displaying the readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to view information about the one or more accounts without preparing the one or more accounts for use from the account user interface.

[0029] An exemplary computer system is described herein. The exemplary computer system comprises a display generation component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs receiving a first input via the one or more input devices, and in response to receiving the first input, displaying via the display generation component an account user interface including a first visual representation of a first account, receiving, while displaying the first visual representation of the first account, a second input via the one or more input devices corresponding to a selection of the first visual representation of the first account, and displaying the second input corresponding to a selection of the first visual representation of the first account. In response to receiving the power, the method includes instructions for: displaying, via the display generation component, a readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to prepare the one or more accounts for use from the account user interface; and displaying, via the display generation component, information corresponding to the first account without displaying the readable portion of the machine readable code corresponding to the first account in accordance with a determination that the first visual representation of the first account was displayed in response to a request to view information about the one or more accounts without preparing the one or more accounts for use from the account user interface.

[0030] an exemplary computer system comprising: a display generating component; one or more input devices; means for receiving a first input via the one or more input devices; means for displaying, via the display generating component, an account user interface including a first visual representation of the first account in response to receiving the first input; means for receiving, via the one or more input devices while displaying the first visual representation of the first account, a second input corresponding to a selection of the first visual representation of the first account; means for displaying, via the display generating component, a readable portion of machine readable code corresponding to the first account in response to receiving the second input corresponding to the selection of the first visual representation of the first account; and means for displaying, via the display generating component, information corresponding to the first account without displaying the readable portion of the machine readable code corresponding to the first account in response to a determination that the first visual representation of the first account was displayed in response to a request to view information regarding the one or more accounts without preparing the one or more accounts for use from the account user interface.

[0031] An exemplary method is disclosed herein, the exemplary method including, at a computer system in communication with a display generation component and one or more input devices, displaying a search user interface via the display generation component, receiving input via the one or more input devices while displaying the search user interface, the input including a search term, and in response to receiving the input including the search term, in accordance with a determination that the search user interface corresponds to a plurality of transfer accounts provided to the computer system and is configured to transfer resources of the respective transfer accounts upon user authorization, simultaneously displaying via the display generation component a plurality of search results selected using the search term, the plurality of search results including a first search result corresponding to resource transfer activity of a first account of the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account of the plurality of transfer accounts, different from the first account.

[0032] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for displaying a search user interface via the display generation component, receiving an input via the one or more input devices while displaying the search user interface, the input including a search term, and in response to receiving the input including the search term, in accordance with a determination that the search user interface corresponds to a plurality of transfer accounts provided to the computer system and is configured to transfer resources of the respective transfer accounts upon user authorization, simultaneously displaying via the display generation component a plurality of search results selected using the search term, the plurality of search results including a first search result corresponding to resource transfer activity of a first account of the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account of the plurality of transfer accounts, different from the first account.

[0033] An exemplary temporary computer-readable storage medium is described herein. The exemplary temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs including instructions for displaying a search user interface via the display generating component, receiving an input via the one or more input devices while displaying the search user interface, the input including a search term, and in response to receiving the input including the search term, in accordance with a determination that the search user interface corresponds to a plurality of transfer accounts provided to the computer system and is configured to transfer resources of the respective transfer accounts upon user authorization, simultaneously displaying via the display generating component a plurality of search results selected using the search term, the plurality of search results including a first search result corresponding to resource transfer activity of a first account of the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account of the plurality of transfer accounts, different from the first account.

[0034] An exemplary computer system is described herein. The exemplary computer system comprises a display generating component, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying a search user interface via the display device, receiving an input via the one or more input devices while displaying the search user interface, the input including a search term, and in response to receiving the input including the search term, in accordance with a determination that the search user interface corresponds to a plurality of transfer accounts provided to the computer system and is configured to transfer resources of the respective transfer accounts upon user authorization, simultaneously displaying via the display generating component a plurality of search results selected using the search term, the plurality of search results including a first search result corresponding to resource transfer activity of a first account of the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account of the plurality of transfer accounts, different from the first account.

[0035] An exemplary computer system comprises a display generation component, one or more input devices, and means for displaying a search user interface via the display device; means for receiving input via the one or more input devices while displaying the search user interface, the input including the search terms; and in response to receiving the input including the search terms, in accordance with a determination that the search user interface corresponds to a plurality of transfer accounts provided to the computer system and is configured to transfer resources of each transfer account upon user authorization, means for simultaneously displaying via the display generation component a plurality of search results selected using the search terms, the plurality of search results including a first search result corresponding to resource transfer activity of a first account of the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account of the plurality of transfer accounts, different from the first account.

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

[0037] This provides devices with faster and more efficient methods and interfaces for sharing and using passes and accounts, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for sharing and using passes and accounts. [Brief description of the drawings]

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

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

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

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

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

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

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

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

[0046] [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments.

[0047] [Figure 6A] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments. [Figure 6B] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments. [Figure 6C] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments. [Figure 6D] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments. [Figure 6E] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments. [Figure 6F] FIG. 1 illustrates an exemplary user interface for sharing one or more paths according to some embodiments.

[0048] [Figure 7] FIG. 1 is a flow diagram illustrating a method for sharing one or more paths according to some embodiments.

[0049] [Figure 8A] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments. [Figure 8B] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments. [Figure 8C] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments. [Figure 8D] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments. [Figure 8E] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments. [Figure 8F] FIG. 1 illustrates an example user interface for providing a prompt to a user to provide authorization according to some embodiments.

[0050] [Figure 9] FIG. 1 is a flow diagram illustrating a method for providing a prompt to a user to provide authorization according to some embodiments.

[0051] [Figure 10A] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10B] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10C]1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10D] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10E] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10F] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10G] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10H] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10I] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10J] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10K] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments. [Figure 10L] 1 illustrates an exemplary user interface for displaying machine-readable code according to some embodiments.

[0052] [Figure 11] FIG. 1 is a flow diagram illustrating a method for displaying machine-readable code according to some embodiments.

[0053] [Figure 12A] 1 illustrates an exemplary user interface for viewing computer storage accounts according to some embodiments. [Figure 12B]1 illustrates an exemplary user interface for viewing computer storage accounts according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for viewing computer storage accounts according to some embodiments.

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

[0055] [Figure 14] FIG. 1 is a flow diagram illustrating a method for displaying a transfer account according to some embodiments.

[0056] [Figure 15] FIG. 1 is a flow diagram illustrating a method for authorizing a transfer account according to some embodiments.

[0057] [Figure 16A] FIG. 1 illustrates an exemplary user interface for searching one or more computer storage accounts according to some embodiments. [Figure 16B] FIG. 1 illustrates an exemplary user interface for searching one or more computer storage accounts according to some embodiments. [Figure 16C] FIG. 1 illustrates an exemplary user interface for searching one or more computer storage accounts according to some embodiments.

[0058] [Figure 17A]FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17B] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17C] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17D] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17E] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17F] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17G] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17H] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17I] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17J] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17K] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17L]FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17M] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments. [Figure 17N] FIG. 1 illustrates an exemplary user interface for searching one or more transfer storage accounts according to some embodiments.

[0059] [Figure 18] FIG. 1 is a flow diagram illustrating a method for searching one or more transfer storage accounts according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0061] There is a need for electronic devices that provide an efficient method and interface for sharing and using passes or accounts. For example, when one or more passes are received, there is a need for a user to easily and efficiently provide one or more passes to a second user. As another example, when one or more passes are being used, there is a need for a user to easily and efficiently provide data corresponding to the passes to a pass reader terminal. As another example, when using an account for a transaction, there is a need for a user to easily and efficiently provide a machine readable code associated with the account to perform the transaction. Such techniques can reduce the cognitive burden on users who use or share passes or accounts, thereby increasing productivity. Additionally, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0062] 1A-1B, 2, 3, 4A-4B, and 5A-5B below describe an exemplary device performing techniques for sharing and using passes or accounts. FIGS. 6A-6F illustrate an exemplary user interface for sharing one or more passes, according to some embodiments. FIG. 7 is a flow diagram illustrating a method for sharing one or more passes, according to some embodiments. The user interfaces of FIGS. 6A-6F are used to illustrate processes described below, including the process of FIG. 7. FIGS. 8A-8F illustrate an exemplary user interface for providing a prompt to a user to provide authorization, according to some embodiments. FIG. 9 is a flow diagram illustrating a method for providing a prompt to a user to provide authorization, according to some embodiments. The user interfaces of FIGS. 8A-8F are used to illustrate processes described below, including the process of FIG. 9. FIGS. 10A-10L illustrate an exemplary user interface for displaying machine-readable code, according to some embodiments. FIG. 11 is a flow diagram illustrating an exemplary method for displaying machine-readable code, according to some embodiments. The user interfaces of Figures 10A-10L are used to illustrate processes described below, including the process of Figure 11. Figures 12A-12C show an example user interface for viewing computer storage accounts, according to some embodiments. Figures 13A-13AA show an example user interface for viewing and authorizing transfer accounts, according to some embodiments. Figure 14 is a flow diagram illustrating a method for viewing transfer accounts, according to some embodiments. Figure 15 is a flow diagram illustrating a method for authorizing transfer accounts, according to some embodiments. The user interfaces of Figures 12A-12C and 13A-13AA are used to illustrate processes described below, including the processes of Figures 14 and 15. Figures 16A-16C show an example user interface for searching one or more computer storage accounts, according to some embodiments.17A-17N show example user interfaces for searching one or more transfer accounts, according to some embodiments. FIG 18 is a flow diagram illustrating a method for searching one or more transfer accounts. The user interfaces of FIGS 16A-16C and 17A-17N are used to illustrate processes described below, including the process of FIG 18.

[0063] Furthermore, in methods described herein in which one or more steps are conditional on one or more conditions being satisfied, it is understood that the described method may be repeated multiple times, such that in the course of the iterations, all conditions on which the steps in the method are conditional are also satisfied in different iterations of the method. For example, if a method requires performing a first step if a condition is satisfied and a second step if the condition is not satisfied, one skilled in the art will understand that the steps claimed are repeated in a non-specific order until the conditions are satisfied and are not satisfied. Thus, a method described with one or more steps that are conditional on one or more conditions being satisfied can be rewritten as a method that is repeated until each condition described in the method is satisfied. However, this is not required for a system or computer readable medium claim in which the system or computer readable medium includes instructions to perform a conditional action based on the corresponding one or more conditions being satisfied, and thus can determine whether a condition is satisfied without explicitly repeating the steps of the method until all of the conditions on which the steps in the method depend are satisfied. Those skilled in the art will also understand that, as with methods having conditional steps, the system or computer-readable storage medium may repeat the steps of the method as many times as necessary to ensure that all of the conditional steps are performed.

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

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

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

[0067] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA function and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptop computers or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system in communication (e.g., via wired communication, via wireless communication) with a display generating component. The display generating component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generation components are separate from the computer system. As used herein, "displaying" content includes causing content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component to visually generate the content.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] Video conferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138 to initiate, conduct, and end a video conference between a user and one or more other participants in accordance with instructions from the user.

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

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

[0113] The training support module 142 includes executable instructions to cooperate with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module to create workouts (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit the workout data.

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

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

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

[0117] The calendar module 148 includes executable instructions to cooperate with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147 to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar items, to-do lists, etc.) according to user instructions.

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

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

[0120] The search module 151 includes executable instructions for operating in conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134 to search for text, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by individual event receivers 182 in an event queue.

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

[0140] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within a separate view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a separate application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the 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 separate event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more separate event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in a separate application view 191.

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

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

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

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

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

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

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

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

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

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

[0151] 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 an individual application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0177] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of a discrete contact above the pressure input intensity threshold, followed by a decrease in the intensity of the contact below a hysteresis intensity threshold that corresponds to the pressure input intensity threshold, and a discrete action is performed in response to detecting a subsequent decrease in the intensity of the discrete contact below the hysteresis intensity threshold (e.g., an "upstroke" of the discrete pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a distinct action is performed in response to detecting the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

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

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

[0180] 6A-6F show example user interfaces for sharing one or more paths according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process of FIG.

[0181] FIG. 6A illustrates device 600a including a display 602a (e.g., a touch screen display). In FIG. 6A, device 600a displays a user interface 604, which includes information about three passes associated with a service provider named Amusement World (e.g., an amusement park). In some embodiments, the passes are digital passes that include data that can be transmitted (e.g., to a pass reader terminal) to use or redeem the passes. In some embodiments, the service provider is a business that provides access to a service (e.g., an amusement park, a concert venue, a merchant with memberships). In some embodiments, the service provider is a different entity (e.g., a company and / or a third party) than the entity (e.g., a first party) that developed and / or provides device 600a and / or the operating system running on device 600a. In some embodiments, user interface 604 is a user interface for a vendor application (e.g., a third party application), a vendor website (e.g., a third party website), or a wallet application (e.g., a first party wallet application included in the operating system of device 600a). In some embodiments, the user interface 604 includes information about one pass, two passes, or more than three passes. In some embodiments, the pass includes an electronic ticket, an electronic membership card, or an electronic access badge. In some embodiments, the pass provides a service offered by a service provider (e.g., admission to an amusement park, admission to a venue, admission to a retail store, access to an account or account features, and / or redemption of offers or promotions). In the embodiment shown in FIG. 6A, the pass provides access to a venue called Amusement World.

[0182] User interface 604 includes an affordance 606 that, when selected, initiates a process for adding a pass to an account associated with the first user ID (e.g., an account associated with a user or owner of device 600a and signed in to device 600a). In some embodiments, the account is for a first party wallet application associated with the user ID. In some embodiments, the first party application is an application developed, managed, and / or provided by a developer of device 600a and / or the operating system running on device 600a. In FIG. 6A, while displaying user interface 604, device 600a receives (e.g., detects) a request 603 to add a pass shown in user interface 604a to an account associated with the first user ID. In the embodiment shown in FIG. 6A, request 603 includes a selection (e.g., tap) of affordance 606.

[0183] After receiving (e.g., responding to) the request 603, the device 600a displays a sharing affordance 612a for providing (e.g., sharing) at least one of the one or more passes to an account associated with the second user ID (e.g., as shown in user interface 608a of FIG. 6B).

[0184] User interface 608a includes (e.g., simultaneously displays) a share affordance 612a, an add affordance 610a, a representation 630a of the pass(es) (or an account associated with the pass(es) and / or service provider), and a prompt for adding the pass to an account associated with the first user ID. In some embodiments, user interface 608a is displayed in response to receiving a request to launch or open a wallet account application (e.g., a double press of hardware button 635a on device 600a) after receiving a request 603 to add one or more passes to an account associated with the first user ID.

[0185] While displaying user interface 608a, device 600a may receive (e.g., detect) a request 605 (e.g., a tap on add affordance 610a) to add a pass to an account associated with the first user ID and / or to device 600a (e.g., the pass may be stored on device 600a). In some embodiments, adding a pass to an account associated with the user ID includes adding data corresponding to the pass to the account without adding (e.g., storing) the data corresponding to the pass to a device associated with the user ID, adding data corresponding to the pass to the account and adding data corresponding to the pass to a device associated with the user ID, or adding data corresponding to the pass to a device associated with the user ID without adding data corresponding to the pass to an account.

[0186] In the embodiment shown in Figure 6C, in response to receiving request 605, device 600a removes (e.g., stops displaying) the prompt to the user to add the pass to the account associated with the first user ID and displays an indication that the pass was added to the account associated with the first user ID (e.g., a text indication that "3 passes added to wallet"). In the embodiment shown in Figure 6C, in response to receiving request 605, device 600a removes (e.g., stops displaying) add affordance 610a and displays exit affordance 632.

[0187] In some embodiments, in response to receiving a selection of the add affordance 610a, the device 600a (e.g., automatically, without additional user input) adds all of the received passes to the account and / or device associated with the first user ID. In some embodiments, in response to receiving a selection of the add affordance 610a, the device 600a provides (e.g., displays) one or more options (e.g., affordances) for selecting which of the received passes to add to the account and / or device associated with the first user ID. For example, the device 600a may provide the ability to add passes one at a time, or provide the ability to add any one or two of the three passes without adding all of the passes.

[0188] In some embodiments, the share affordance 612a is displayed after adding the pass(es) (e.g., information corresponding to the pass(es)) to an account associated with the first user ID. For example, the share affordance 612a is not displayed in the user interface 608a of FIG. 6B in response to receiving the request 603 of FIG. 6A, and is displayed in the user interface 608a of FIG. 6C after adding the pass(es) to the account associated with the first user ID (e.g., in response to receiving the add selection 605 of FIG. 6B of affordance 610a).

[0189] In some embodiments, device 600a provides the ability to select a visual design for the path(s) (e.g., different artwork options that may be used as images on the path). In some embodiments, before sharing the path(s) and / or adding the path(s) to device 600a (or an account associated with device 600a), device 600a receives a request to view visual design options for the path(s) (e.g., device 600a detects a selection of an affordance that, when selected, causes device 600a to display selectable visual design options). For example, device 600a receives an input corresponding to a selection of a visual design for one or more paths and, in response, displays the path(s) according to the selected visual design. In some embodiments, data representing the visual design is provided to an account associated with the second user ID.

[0190] In some embodiments, the representation of the path(s) (e.g., in user interfaces 608a, 608b, and / or 618) is displayed with a geometric variation effect (e.g., a skew effect, a 3D effect, a depth effect, and / or a parallax effect). In some embodiments, the representation of the path(s) is a graphical animation (e.g., transitioning colors and / or transitioning shapes) that creates the illusion that the representation of the path(s) (or a portion thereof) is a three-dimensional object viewed from different angles as the angle (e.g., or orientation) of the device (e.g., 600a or 600b) changes. In some embodiments, the geometric variation effect includes shifting the position of a first layer (e.g., a first path and / or a first artwork layer) relative to a second layer (e.g., a second path and / or an artwork (e.g., a background)) based on a change in the orientation of the device relative to a reference point. In some embodiments, displaying the geometric change includes detecting a change in the orientation of the device relative to a fixed reference point on the Earth (e.g., based on device orientation sensors such as an accelerometer, gyroscope, and / or magnetometer). In some embodiments, displaying the geometric change effect includes detecting a change in the orientation of the user relative to the device (e.g., based on a face tracking sensor, such as a camera or other face tracking sensor that can detect a change in the viewing angle of the device due to the face being tracked by the device).

[0191] In some embodiments, the display of the representation of the path(s) (e.g., in user interfaces 608a, 608b, and / or 618) includes an animation (e.g., a twinkling star, an ongoing animation, and / or a repeating animation). In some embodiments, displaying the representation of the path(s) includes displaying an animation of at least one visual feature of the representation of the path(s) (e.g., a star on the path is animated to twinkle). In some embodiments, the animation includes displaying multiple intermediate states while transitioning from an initial state of the visual feature to an end state of the visual feature.

[0192] In FIG. 6C, device 600a receives (e.g., detects) a user input 609 (e.g., a tap) corresponding to a selection of shared affordance 612a. In response to receiving input 609, device 600a initiates a process for providing at least one of the passes to an account associated with a second user ID. In some embodiments, the account associated with the second user ID is a second account (e.g., a family member's account) of a first party wallet application associated with the second user. In the embodiment shown in FIG. 6D, the process for providing at least one of the passes to the account associated with the second user ID includes displaying user interface 614. In some embodiments, user interface 614 includes a graphical element having the appearance of a card or sheet that overlaps (e.g., is displayed in front of) at least a portion of user interface 608a. The user interface 614 includes a graphical representation (e.g., a list) of one or more user IDs and a graphical representation of one or more methods for providing the pass(es) (e.g., text message, email, NFC, and / or a shared cloud storage account shared by the first user ID and the second user ID).

[0193] In FIG. 6D, device 600a receives (e.g., detects) an input 611 (e.g., a tap) on a representation 616 of a user ID (e.g., a tap on a user ID associated with user Amy Appleseed). In response to receiving input 611, device 600a provides at least one of the passes to an account associated with the selected user ID (e.g., information is added to an account associated with the selected user ID such that at least one pass may be redeemed from a wallet application of a second user ID). In some embodiments, device 600a provides one or more passes by transmitting information representing the passes or by providing access to pass information from a central server. In the embodiment shown in FIG. 6D, device 600a provides one of the passes (e.g., only one of the passes, a single pass) to an account associated with the selected user ID.

[0194] In some embodiments, in response to receiving the input 611, the device 600a displays (e.g., returns) the user interface 608a shown in FIG. 6C. In some embodiments (e.g., after returning to the user interface 608a shown in FIG. 6C), in response to receiving the input 609 (e.g., selection of the share affordance 612a), the device 600a provides at least one of the passes to an account associated with a second user ID (e.g., a selected user ID).

[0195] In some embodiments, some or all of the techniques described with reference to Figures 6A-6D may be repeated to provide pass(es) to another user ID. For example, after (e.g., in response to) selection of a second user ID in user interface 614 (or after providing pass(es) to accounts associated with the second user ID), device 600a displays user interface 608a, as shown in Figure 6B, if pass(es) have not been added to device 600a, or displays user interface 608a, optionally without exit affordance 632, as shown in Figure 6C, if pass(es) have been added to device 600a. In some embodiments, more than one user ID (e.g., Amy Appleseed and John Appleseed) may be selected within user interface 614, and in response to receiving a selection of more than one user ID, device 600a provides pass(es) to accounts associated with all of the selected user IDs. In some embodiments, a representation in the user interface 614 corresponds to a group of user IDs (e.g., two or more user IDs), and in response to receiving a selection of such a representation, the device 600a provides a pass(es) to accounts associated with all of the user IDs associated with the group.

[0196] In some embodiments, device 600a (e.g., automatically, without additional user input) provides all of the received passes to the account associated with the selected user ID in response to receiving input 611. In some embodiments, device 600a provides one or more options (e.g., affordances) to select (e.g., display) which passes to provide to the account associated with the selected user ID in response to receiving input 611. For example, device 600a may provide the ability to provide passes one at a time, or to provide any one or two of the three passes without providing all passes.

[0197] In the embodiment shown in FIGS. 6A-6C, the share affordance 612a is displayed as part of a process of adding a pass to the device 600a and / or an account associated with the user ID associated with the device 600a. For example, the pass is added to the device 600a in response to receiving a selection 605 of the add affordance 610a of FIG. 6B before providing the pass to the account associated with the second user ID. In some embodiments, one or more passes can be provided to the account associated with the second user ID before or without adding the pass(es) to the device 600a. For example, the device 600a can receive (e.g., detect) an input 607 (e.g., a tap) corresponding to a selection of the share affordance 612a, as shown in FIG. 6B. In response to receiving the input 607, the device 600a initiates a process for providing at least one of the passes to the account associated with the second user ID described above with reference to FIG. 6D (e.g., the device 600a displays the user interface 614) without or before adding the pass(es) to the device 600a.

[0198] In some embodiments, after the pass(es) are shared, the device 600a returns to the application or website (e.g., the source of the pass(es)) that generated the pass(es) or where the process for adding the pass(es) to the account associated with the first user ID was initiated. For example, in response to a selection of a second user ID, such as input 611 on representation 616, the device 600a displays (e.g., automatically and without further user input) a user interface of the application corresponding to the user interface 604 of FIG. 6A (e.g., the device 600a launches, resumes, and / or switches to the service provider's third party application or website that was the source of the pass(es) or where the process for adding the pass(es) associated with the first user ID was initiated).

[0199] In some embodiments, the second user ID is associated with the first user ID (e.g., the two user IDs are included in a family sharing account in which users can share data such as photos, videos, passes, and / or access to other accounts). In some such embodiments, providing the pass(es) to the account associated with the second user ID causes the pass(es) to be added to the account associated with the second user ID without entry into a computer system associated with the second user ID and / or without providing a notification or message to a device associated with the second user ID (e.g., the pass(es) appear in the second user ID's account (e.g., appear in a wallet application logged into the second user ID's account) without sending a text message, email, and / or other notification.

[0200] In some embodiments, the pass(es) are added to a first device associated with the second user ID (e.g., a phone) and to a second device associated with the second user ID (e.g., a watch) by providing the pass(es) to an account associated with the second user ID.

[0201] In some embodiments, adding a pass(es) to an account and / or device(s) associated with a first user ID or a second user ID authorizes the respective device to redeem the pass(es).

[0202] In some embodiments, an animation (e.g., spacecraft launch and / or gate opening) is displayed when the path(s) are redeemed or used (e.g., as described with reference to FIG. 8C and FIG. 8E). For example, in some embodiments, the device 600a detects a request (e.g., a request described with reference to FIG. 8C and FIG. 8E) to provide data corresponding to a first path of the path(s) to the path leader terminal, and in response, displays an animation associated with the first path indicating that the data corresponding to the first path has been successfully provided to the path leader terminal. In some embodiments, the animation includes displaying a transition from an initial state (e.g., a spacecraft on a launch pad and / or a closed gate) to an end state (e.g., a spacecraft in space and / or an open gate), with multiple intermediate states being displayed while transitioning from the initial state to the end state. In some embodiments, the animation is displayed in response to detecting that data corresponding to the first path has been transmitted from the computer system. In some embodiments, the animation is displayed in response to receiving a confirmation that the data corresponding to the first path has been accepted by the path leader terminal.

[0203] In some embodiments, when the path(s) is used, the device 600a and / or the path leader terminal generates (e.g., outputs) a unique noise or a noise that is different from the noise generated when other events occur. In some embodiments, the noise includes a sound corresponding to custom art or animation (e.g., a spacecraft launch sound, and / or a sound associated with a visual design selected by the user). For example, in some embodiments, the device 600a detects a request to provide corresponding data to the path leader terminal and, in response, causes (e.g., by the device 600a and / or the path leader terminal) an audio notification corresponding to the path (e.g., when the path is used, the user's device and / or the path leader terminal plays a sound corresponding to the artwork on the path). In some embodiments, the audio notification is customized to the path (e.g., the notification is a specific audio output (e.g., a sound effect) associated with the path that is different from alert notifications such as incoming calls, text messages, and / or emails).

[0204] Returning to FIG. 6D, representation 616 corresponds to an option to provide one or more of the passes to an account associated with a user ID associated with user Amy Appleseed via text message, as indicated by a possible bubble indication at the bottom right of representation 616. In some embodiments, the account associated with the selected user ID is accessed via a second electronic device associated with a second user ID. FIG. 6E illustrates an example of a user interface 618 of a messaging application displayed on a display 602b of a device 600b (e.g., Amy Appleseed's phone) associated with the selected user ID. User interface 618 includes (e.g., displays) a message conversation between a user ID associated with device 600a and a user ID associated with device 600b. As a result of the user ID associated with device 600b being selected in FIG. 6D, user interface 618 includes a graphical indication 620 of the pass(es) (e.g., in the message conversation) and an affordance 622 for viewing the shared pass(es).

[0205] In FIG. 6E, device 600b receives (e.g., detects) a request 613 (e.g., a tap on affordance 622) to view the shared pass(es). In response to detecting the input 613, device 600b displays user interface 608b, as shown in FIG. 6F. In some embodiments, user interface 608b is a user interface of a wallet application (e.g., a first party wallet application) associated with a user ID associated with device 600b. In some embodiments, user interface 608b is similar to user interface 608a shown in FIG. 6B. User interface 608b includes (e.g., simultaneously displays) a share affordance 612b, an add affordance 610b, a representation 630b of the shared pass(es) (or an account associated with the shared pass(es) and / or service provider), and a prompt to add the pass(es) to an account associated with the first user ID. In some embodiments, user interface 608b is displayed in response to receiving a request to launch or open a wallet account application after receiving the pass(es) (e.g., a double press of hardware button 635b on device 600b). For example, options to add and / or share the received pass(es) may be displayed in the wallet application associated with the selected user ID without (or before) viewing a representation 620 of the pass(es) or selecting an affordance 622 in the messaging application user interface 618.

[0206] In response to receiving a selection of the add affordance 610b, the device 600b adds the pass(es) to an account (e.g., a digital wallet account) associated with the user ID associated with the device 600b. In some embodiments, the shared pass is added to the account associated with the second user ID without further input (e.g., without selection of the add affordance 610b in the user interface 608b, without input at the device 600b, and / or without other confirming input). In some embodiments, the shared pass(es) are automatically added to the account associated with the selected user ID, but further input (e.g., selection of the add affordance 610b) is required to add / store the shared pass(es) to the device 600b. In some embodiments, selection of the add affordance 610b (or other input (e.g., confirming input) at the device associated with the selected user ID) is required to add the shared pass(es) to the account associated with the selected user ID.

[0207] In response to receiving a selection of the share affordance 612b, device 600b initiates a process to share the pass with another user ID (e.g., the same or similar process as described for device 600a with reference to Figures 6C-6D).

[0208] 7 is a flow diagram illustrating a method for sharing one or more paths, according to some embodiments. Method 700 is performed on a computer system (e.g., 100, 300, 500, 600a) in communication with a display generating component (e.g., 602a) and one or more input devices (e.g., touch-sensitive surfaces). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0209] As described below, method 700 provides an intuitive way to share passes with an account associated with a second user ID. The method reduces the cognitive load on the user when sharing passes, thereby creating a more efficient human-machine interface. For battery-operated computer systems, enabling users to share passes more quickly and efficiently conserves power and extends the time between battery charges.

[0210] In method 700, a computer system (e.g., 600a), via a display generation component (e.g., 602a), displays (702) a first user interface (e.g., 604, 608a) (e.g., a vendor application, a vendor website, and / or a wallet application) that includes information about one or more passes associated with a service provider (a business that provides access to a service (e.g., an amusement park, a concert venue, and / or a merchant with membership)).

[0211] While displaying the first user interface, the computer system receives a request (e.g., 603, 605) via one or more input devices (e.g., selection of an “Add to Wallet” affordance via the touch-sensitive surface) to add one or more passes (e.g., electronic tickets, electronic membership cards, and / or electronic access badges) to an account associated with the first user ID (e.g., an account in a first-party wallet application associated with the user) (704). The one or more passes provide services offered by a service provider (e.g., admission to an amusement park, admission to a venue, admission to a retail store, access to an account or account features, and / or redemption of offers or promotions).

[0212] After receiving the request (and optionally after adding information corresponding to the one or more passes to an account associated with the first user ID (e.g., after adding information such that the passes may be redeemed from a wallet application)), the computer system, via the display generation component, displays (706) a shared affordance (e.g., 612a) (e.g., a selectable user interface object) for providing at least one of the one or more passes (e.g., transmitting information representing the pass and / or providing access to the pass information from a central server) to an account associated with a second user ID (e.g., a second account of a first party wallet application associated with the second user) (e.g., a family member's account). In some embodiments, the account associated with the second user ID is accessed via a second electronic device (e.g., 600b) associated with the second user ID.

[0213] The computer system receives (708) user input (e.g., 607, 609) (e.g., a tap gesture via the touch-sensitive surface on the shared affordance) corresponding to a selection of the shared affordance (e.g., 612a) via one or more input devices.

[0214] In response to receiving user input corresponding to the selection of the share affordance, the computer system initiates a process of providing at least one of the one or more passes to an account associated with the second user ID (710) (e.g., adding information to the second account such that at least one pass is redeemable from the second user's wallet application). By providing passes to the second account associated with the second user ID in response to the selection of the share affordance, the number of inputs required to add passes to the second account is reduced. Reducing the number of inputs required to perform an operation improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0215] In some embodiments, prior to initiating a process for providing at least one of the one or more passes to an account associated with the second user ID, the second user ID is selected from a list of user IDs (e.g., contacts in a family and / or contact list) available to receive a shared pass (e.g., selected from a user interface 614). In some embodiments, the process for providing at least one of the one or more passes to a second account associated with the second user ID includes receiving and responding to a sequence of one or more inputs and may include displaying one or more user interfaces. In some embodiments, the process for providing at least one of the one or more passes to a second account associated with the second user ID includes providing an indication (e.g., 620) (e.g., a text message) to a device associated with the second user ID that a pass has been added to (e.g., authorized to be redeemed by) the account associated with the second user ID.

[0216] In some embodiments, displaying the first user interface (e.g., 604, 608a) includes displaying the representation of the one or more paths (e.g., 630a) with a geometric change effect (e.g., skew effect, 3D effect, depth effect, parallax effect, and / or graphic animation) (e.g., color shift and / or shape shift) that creates the illusion that the representation of the one or more paths (or portions thereof) are three-dimensional objects viewed from different angles as the angle (orientation) of the display generating components changes. In some embodiments, the geometric change effect includes shifting a position of a first layer (e.g., a first path and / or a first artwork layer) relative to a second layer (e.g., a second path and / or an artwork (e.g., background)) based on a change in orientation of the display generating components relative to a reference point. In some embodiments, displaying the geometric change includes detecting a change in orientation of the display generating components relative to a fixed reference point on the Earth (e.g., based on an orientation sensor of the computer system such as an accelerometer, gyroscope, and / or magnetometer). In some embodiments, displaying the geometric change effect includes detecting a change in a user's orientation relative to the display generating component (e.g., based on a face tracking sensor, such as a camera or other face tracking sensor, that can detect a change in the viewing angle of the device due to the face being tracked by the device). Displaying a representation of one or more paths with the geometric change effect provides the user with visual feedback regarding the state of the display generating component and / or information regarding one or more paths, such as how many paths are available (e.g., by showing the height of a simulated stack of paths as the display generating component changes orientation). Additionally, displaying the geometric change effect as the display generating component changes orientation indicates to the user that the displayed paths are authentic and not a video that would be displayed regardless of the display generating component orientation.Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0217] In some embodiments, in response to receiving a request (e.g., 603, 605) to add one or more passes to an account associated with a first user ID, the computer system initiates a process for adding one or more passes to a device (e.g., 600a) associated with (e.g., logged into) the account associated with the first user ID. In some embodiments, the process for adding one or more passes to a device associated with the account associated with the first user ID includes displaying a sharing affordance (e.g., 612a) for providing at least one of the one or more passes to an account associated with a second user ID. By displaying a sharing affordance for providing at least one of the one or more passes to an account associated with a second user ID as part of the process for adding one or more passes to a device associated with the account associated with the first user ID, a user may efficiently share a pass without having to provide additional input to navigate to an additional user interface. Improves operability of the computer system by reducing the number of inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0218] In some embodiments, in response to receiving a request (e.g., 603, 605) to add one or more passes to an account associated with a first user ID, the computer system adds a first pass of the one or more passes and a second pass of the one or more passes that is different from the first pass of the one or more passes to the account associated with the first user ID (e.g., a single input on an "add pass" affordance (e.g., 606, 610a) causes multiple passes to be added to an account). Adding the first pass and the second pass to the account associated with the first user ID in response to receiving a request to add one or more passes to an account associated with the first user ID allows a user to efficiently add multiple passes to the account associated with the first user ID with a single input. Reducing the number of inputs required to perform an operation improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and also reduces power usage and improves battery life of the computer system by allowing a user to use the computer system more quickly and efficiently.

[0219] In some embodiments, the request (e.g., 603) to add one or more passes to an account associated with a first user ID does not add the one or more passes to the account associated with the first user ID. By ceasing to add passes to the account associated with the first user ID, the user is allowed to share one or more passes with an account associated with a second user ID without adding passes to the account associated with the first user ID, providing the user with additional control over which accounts have passes. Providing the user with additional control over the computer system improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0220] In some embodiments, the process for providing at least one of the one or more passes to an account associated with the second user ID includes providing a first pass of the one or more passes and a second pass, different from the first pass of the one or more passes, to the account associated with the second user ID. In some embodiments, the passes are sent to the account associated with the second user ID via a text message (e.g., 620), and the second user is then given the option (e.g., 610b) to add the passes. In some embodiments, all passes in the one or more passes are entered into the account associated with the second user ID (e.g., in response to a single input) without further input from the second user. By providing the first pass and the second pass to the account associated with the second user ID, a user can efficiently share multiple passes to the account associated with the second user ID with a single input. Improves operability of the computer system by reducing the number of inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0221] In some embodiments, the share affordance (e.g., 612a) is displayed in a second user interface (e.g., 608a) (e.g., a UI for a wallet application) that is different from the first user interface (e.g., 604) (e.g., a user interface of an application associated with the service provider). In some embodiments, in response to receiving a user input (e.g., 607, 609) corresponding to a selection of the share affordance, the computer system displays the first user interface (e.g., automatically, without further user input). Displaying the first user interface in response to receiving a user input corresponding to a selection of the share affordance allows the user to return to the first user interface without additional input. Improves usability of the computer system by reducing the number of inputs required to perform operations, makes the user system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), plus reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0222] In some embodiments, a second user ID is associated with the first user ID (e.g., the two users are included in a family shared account), and the process for providing at least one of the one or more passes to an account associated with the second user ID includes adding at least one of the one or more passes to the account associated with the second user ID without input at the computer system associated with the second user ID (e.g., 600b) (e.g., the pass appears in the second user's wallet without receiving a text message and / or the data is sent via a shared cloud storage account). Adding at least one of the one or more passes to an account associated with the second user ID provides the user with additional control over which accounts have passes. Providing the user with additional control of the computer system improves the operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0223] In some embodiments, the process for providing at least one of the one or more passes to an account associated with the second user ID includes adding (e.g., authorizing the device to redeem) at least one of the one or more passes to a first device (e.g., 600b) associated with the second user ID (e.g., a phone) and a second device (e.g., a watch) associated with the second user ID. Adding at least one of the one or more passes to a first device associated with the second user ID and a second device associated with the second user ID allows a user to add passes to multiple devices with a single input. By reducing the number of inputs required to perform an operation, the user system interface is improved (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), as well as reducing power usage and improving battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0224] In some embodiments, the computer system receives an input corresponding to a selection of a visual design for one or more paths. In some embodiments, prior to receiving the input corresponding to the selection of a visual design, the computer system detects a request to view visual design options for one or more paths, and in response to receiving the input corresponding to the selection of a visual design for one or more paths, the computer system displays the one or more paths according to the selected visual design (e.g., different artwork options that may be used as images on the paths, as shown in FIGS. 8A and 8D ). In some embodiments, data representing the visual design is provided to an account associated with the second user ID. By displaying the one or more paths according to the selected visual design, the user can customize the appearance of the paths, thereby providing visual feedback to the user that the paths are associated with the user's account. Providing improved visual feedback improves operability of the computer system and provides a more efficient user device interface (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0225] In some embodiments, the computer system detects a request to provide data corresponding to a first path of the one or more paths to a path leader terminal (e.g., 850 described with reference to FIGS. 8C and 8E), and in response to detecting the request to provide data corresponding to the first path to the path leader terminal, the computer system displays, via the display generation component, an animation (e.g., as described with reference to FIGS. 8C and 8E) associated with the first path indicating that the data corresponding to the first path has been successfully provided to the path leader terminal (e.g., an animation (e.g., a change in expression on a character, a spacecraft launch, and / or an opening of a gate) is displayed when the path is used). In some embodiments, the animation includes displaying a transition from an initial state (e.g., a spacecraft on a launch pad and / or a closed gate) to an end state (e.g., a spacecraft in space and / or an open gate), with a plurality of intermediate states being displayed while transitioning from the initial state to the end state. In some embodiments, the animation is displayed in response to the data corresponding to the first path being transmitted from the computer system. In some embodiments, the animation is displayed in response to receiving a confirmation that the data corresponding to the first path has been accepted by the path leader terminal. Displaying the animation associated with the first pass provides visual feedback to the user confirming that data corresponding to the first pass was successfully provided to the pass reader terminal. Providing improved visual feedback may improve operability of the computer system and provide a more efficient user device interface (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), which may further reduce power usage and improve battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0226] In some embodiments, the computer system, via the display generation component, displays a representation of a first path (e.g., 630a, 630b, 806a as shown in FIGS. 8A-8C, 806b as shown in FIGS. 8D and 8E) of the one or more paths. In some embodiments, displaying the representation of the first path includes displaying an animation of at least one visual feature of the representation of the first path (e.g., a star on the path is animated to twinkle). In some embodiments, the animation includes displaying a plurality of intermediate states while transitioning from an initial state of the visual feature to an end state of the visual feature. Displaying the animation of at least one visual feature of the representation of the first path provides visual feedback to the user that the displayed representation of the first path corresponds to an authentic path (e.g., the displayed path is not a static image copied from another device). Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0227] In some embodiments, the computer system detects a request to provide data corresponding to a first path of the one or more paths to a path reader terminal (e.g., 850 shown in FIGS. 8C and 8E), and in response to detecting the request to provide data corresponding to the first path to the path reader terminal, the computer system causes (e.g., by the computer system and / or the path reader terminal) an audio notification corresponding to the first path (e.g., when the path is used, the user's device and / or the path reader terminal plays a sound corresponding to artwork on the path). In some embodiments, the audio notification is customized to the first path (e.g., the notification is a specific audio output (e.g., a sound effect) associated with the first path that is different from alert notifications such as an incoming call, a text message, and / or an email). By causing an audio notification corresponding to the first path in response to detecting the request to provide data corresponding to the first path to the path reader terminal, feedback is provided to the user confirming that the first path has been used. By providing improved feedback to the user, it improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the device by allowing the user to use the device more quickly and efficiently.

[0228] In some embodiments, the computer system provides at least one of the one or more passes to an account associated with the second user ID (e.g., automatically, without further user input). In some embodiments, at least one of the one or more passes is provided to the second account associated with the second user ID in response to initiating a process for providing at least one of the one or more passes to the second account associated with the second user ID. In some embodiments, at least one of the one or more passes is provided to the second account associated with the second user ID in response to receiving a user input (e.g., 607, 609) corresponding to a selection of a shared affordance (e.g., 612a). In some embodiments, at least one of the one or more passes is provided to the second account associated with the second user ID in response to receiving another input during the process for providing at least one of the one or more passes to the second account associated with the second user ID. In some embodiments, in response to receiving user input corresponding to a selection of the share affordance, a process is initiated for providing at least one of the one or more passes to a third account associated with the third user ID (e.g., the selection of the share affordance shares a pass to two different users). In some embodiments, prior to initiating the process for providing at least one of the one or more passes to an account associated with the second user ID or the third user ID, the second user ID and the third user ID are selected from a list of user IDs (e.g., contacts in a family and / or contact list) available to receive a shared pass (e.g., selected from user interface 614). Providing at least one of the one or more passes to an account associated with the second user ID may add at least one of the one or more passes to the account associated with the second user ID without additional user input.Improves operability of the computer system by reducing the number of user inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0229] It should be noted that details of the process described above in connection with method 700 (e.g., FIG. 7) are also applicable in an analogous manner to the methods described below. For example, methods 900 and 1100 optionally include one or more of the features of the various methods described above with reference to method 700. For the sake of brevity, these details will not be repeated below.

[0230] 8A-8F show example user interfaces that provide prompts to a user to provide authorization, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0231] 8A illustrates a device 800 displaying a user interface 804 on a display 802 (e.g., a touch screen display). The user interface 804 includes a representation 806a (e.g., an image) of a pass (also referred to as pass 806a) associated with a service provider (e.g., a pass to an amusement park called Amusement World, as shown in FIG. 8A). The pass 806a includes text indicating that the pass 806a is associated with a person (e.g., a guest named Amy) and a logo of the service provider (e.g., a character and / or a robot).

[0232] In some embodiments, user interface 804 is displayed in response to a user input that selects path 806a. In some embodiments, user interface 804 is displayed in response to receiving (e.g., detecting) an input (e.g., a double press of hardware button 835). In some embodiments, path 806a is displayed in response to a user input that causes data for a first path to be provided to a path reader (e.g., 850 shown in FIG. 8C).

[0233] User interface 804 includes an indication 808a that path 806a is one (e.g., a first path) of a set of multiple (e.g., three) paths (e.g., the left paging dot is highlighted and / or filled in compared to the center and right dots). In FIG. 8A, user interface 804 includes a prompt (e.g., a graphic element) for the user to hold device 800 near a pass reader terminal (e.g., to redeem pass 806a). In some embodiments, in response to device 800 being held near a pass reader terminal, device 800 provides data corresponding to pass 806a to the pass reader terminal.

[0234] Figure 8B illustrates an embodiment of a user interface 804 similar to the embodiment illustrated in Figure 8A, except that an indication 808b is displayed (e.g., instead of indication 808a). Indication 808b includes a representation of a set of three paths in a staggered stack, with at least a portion of each card displayed (e.g., so that a user can see how many paths are in the set).

[0235] FIG. 8C illustrates device 800 being held near a pass reader terminal 850. In FIG. 8C, device 800 detects that data corresponding to pass 806a has been provided by device 800 to pass reader terminal 850. In some embodiments, the data corresponding to pass 806a is provided via a signal from an NFC transceiver, an optical scan, or a communication (e.g., a confirmation message from a remote server) indicating that a visual representation of pass 806a, such as a barcode or QR code, has been optically scanned. In some embodiments, device 800 provides the data corresponding to pass 806a to pass reader terminal 850 in response to receiving (e.g., detecting) a user input at device 800 (e.g., authorization, a touch on display 802, a movement of device 800, a rotation of a rotatable input device, a biometric or authentication (e.g., fingerprint data, face data, and / or iris data), and / or a press of a hardware button on device 800).

[0236] After detecting (e.g., in response to detecting) that data corresponding to path 806a has been provided by device 800 to path reader terminal 850, device 800 displays a representation of the path 806a and displays an indication (e.g., a checkmark icon and / or an animation of the representation of path 806a) that data corresponding to path 806a has been provided by device 800 to reader terminal 850. In some embodiments, display 802 is deactivated (e.g., off and / or in sleep mode) before the data is provided to path reader terminal 850 (e.g., display 802 is activated (e.g., turned on) in response to detecting that data corresponding to path 806a has been provided by device 800 to path reader terminal 850).

[0237] In the embodiment shown in FIG. 8C, the indication that data corresponding to path 806a has been provided by device 800 to pass reader terminal 850 includes displaying a checkmark icon (e.g., in place of the icon above the text "Hold near reader" in FIGS. 8A and 8B) and displaying a star (a twinkling star animation) and an updated version of the service provider's logo (e.g., a robot animation with right arm / hand raised) on path 806a. In some embodiments, after detecting (e.g., in response) that data corresponding to path 806a has been provided by device 800 to pass reader terminal 850, device 800 provides a tactile and / or audible output, as indicated by the wavy lines around the corners of device 800 in FIG. 8C. In some embodiments, after detecting (e.g., in response) that data corresponding to path 806a has been provided by device 800 to pass reader terminal 850, pass reader terminal 850 provides an indication (e.g., an audible output and / or noise).

[0238] In some embodiments, pursuant to a determination that data corresponding to the second path is available to be provided by device 800 to pass reader terminal 850, device 800 provides a prompt (e.g., a visual, audible, and / or tactile prompt) to provide authorization for the data corresponding to the second path to be provided by device 800 to pass reader terminal 850. In some embodiments, pursuant to a determination that data corresponding to the second path is available to be provided by device 800 to pass reader terminal 850, device 800 maintains display 802 in an active state (e.g., display 800 is turned on).

[0239] In some embodiments, path 806a and the second path are associated with one another (e.g., both paths provide access to the same event and / or day / time at the service provider). In some embodiments, other paths for different events or times / days at the service provider are not used (e.g., do not result in a prompt that data corresponding to the second path is available). In some embodiments, a prompt is provided only for the additional paths associated with path 806a.

[0240] In some embodiments, providing the prompt includes displaying an indication that data corresponding to at least the second path is available to be provided by the device 800 to the path reader terminal 850 (e.g., displaying paging dots, displaying a representation of a stack of paths, displaying instructions to tap the screen, displaying instructions to swipe, displaying instructions to tilt the phone, and / or displaying a portion of the second path along an edge of the display). In the embodiment shown in FIG. 8C, the prompt includes displaying the text "PROCEED TO NEXT PATH" and displaying (e.g., maintaining the display of) an indication 808a. In some embodiments, the prompt indicates the number of paths (e.g., paging dots 808a and / or a representation of a stack of paths 808b) that are available to be provided by the device 800 to the path reader terminal 850. In some embodiments, providing the prompt includes outputting an audio notification that data corresponding to the second path is available to be provided by the device 800 to the path reader terminal 850. In some embodiments, providing the prompt includes outputting a tactile output (e.g., vibration) via one or more tactile output generators when data corresponding to the second pass is available to be provided by the device 800 to the pass reader terminal 850.

[0241] In some embodiments, pursuant to a determination that data corresponding to the second path is not available to be provided by device 800 to pass reader terminal 850, device 800 ceases providing prompts to provide authorization for data corresponding to the second path to be provided by device 800 to pass reader terminal 850. In some embodiments, pursuant to a determination that data corresponding to the second path is not available to be provided by device 800 to pass reader terminal 850, device 800 shuts down display 802 (e.g., display 802 is turned off and / or transitioned to a lower power state (e.g., a lower brightness and / or refresh rate state)).

[0242] FIG. 8D illustrates device 800 displaying a representation 806b of a second pass (also referred to as pass 806b). In FIG. 8D, the center paging dot of paging dots 808a is highlighted and / or filled in compared to the left and right dots, with the right dot indicating that pass 806b is the second of three passes. Pass 806b includes text indicating that pass 806b is associated with a person (e.g., a guest named Pete and / or a different person than pass 806a) and a logo of the service provider (e.g., a different logo, character, and / or mouse than pass 806a). Similar to user interface 804 of FIG. 8A, user interface 804 of FIG. 8D prompts the user to hold device 800 near a pass reader terminal (e.g., because pass 806b has not been redeemed).

[0243] In some embodiments, device 800 displays path 806b (e.g., as part of user interface 804 of FIG. 8D ) in response to receiving (e.g., detecting) an input (e.g., after device 800 provides a prompt to pass reader terminal 850 to authorize data corresponding to the second pass). In some embodiments, the input includes a contact on display 802, a movement of device 800, and / or biometric information (e.g., face information, iris information, fingerprint information). In some embodiments, device 800 displays path 806b (e.g., as part of user interface 804 of FIG. 8D ) in response to detecting input 803 shown in FIG. 8C (e.g., a right-to-left swipe gesture on display 802). In some embodiments, device 800 displays path 806b (e.g., as part of user interface 804 of FIG. 8D ) after detecting (e.g., automatically, without receiving further input, and / or in response to detecting) that data corresponding to path 806a has been provided by device 800 to path reader terminal 850 (e.g., without having to receive input 803). In some embodiments, device 800 displays path 806b (e.g., as part of user interface 804 of FIG. 8D ) in response to detecting movement of device 800 (e.g., a rise and / or fall of device 800, and / or a rise and / or fall of device 800 after detecting that data corresponding to path 806a has been provided by device 800 to path reader terminal 850). In some embodiments, device 800 may display path 806a in response to receiving an input (a right-to-left swipe gesture while displaying path 806b) before (e.g., without) providing data corresponding to path 806a to path reader terminal 850 or before (e.g., without) detecting that data corresponding to path 806a has been provided by device 800 to path reader terminal 850.In some embodiments, in response to receiving an input (e.g., a left-to-right swipe gesture on the display 802) while displaying path 806b (e.g., while displaying user interface 804 as shown in FIG. 8D), device 800 displays path 806a (e.g., device 800 displays user interface 804 as shown in FIG. 8C).

[0244] In some embodiments, after (or while) displaying pass 806b, device 800 detects a request to provide authorization to pass reader terminal 850 for data corresponding to pass 806b (e.g., by placing device 800 next to pass reader terminal 850). FIG. 8E shows device 800 being held near pass reader terminal 850 (e.g., while displaying pass 806b). In FIG. 8E, device 800 detects that data corresponding to pass 806b has been provided by device 800 to pass reader terminal 850. In some embodiments, the data corresponding to pass 806b is provided via a signal from an NFC transceiver, an optical scan, or a communication (e.g., a confirmation message from a remote server) indicating that a visual representation of pass 806b, such as a barcode or QR code, has been optically scanned.

[0245] After detecting (e.g., in response to) detecting that data corresponding to path 806b has been provided by device 800 to path reader terminal 850, device 800 displays a representation of the path 806b and an indication (e.g., a checkmark icon and / or an animation of the representation of path 806b) that data corresponding to path 806b has been provided by device 800 to path reader terminal 850. In some embodiments, display 802 is deactivated (e.g., off and / or in sleep mode) before the data is provided to path reader terminal 850 (e.g., display 802 is activated (e.g., turned on) in response to detecting that data corresponding to path 806b has been provided by device 800 to path reader terminal 850).

[0246] In the embodiment shown in FIG. 8E, the indication that data corresponding to path 806b has been provided by device 800 to pass reader terminal 850 includes displaying a checkmark icon, displaying a star (e.g., a twinkling star animation) on path 806b, and a modified version of the service provider's logo (e.g., a moving mouse whiskers and tail animation) on 806a. In some embodiments, after detecting (e.g., in response) that data corresponding to path 806b has been provided by device 800 to pass reader terminal 850, device 800 provides a tactile and / or audible output, as indicated by the wavy lines around the corners of device 800 in FIG. 8E. In some embodiments, after detecting (e.g., in response) that data corresponding to path 806b has been provided by device 800 to pass reader terminal 850, pass reader terminal 850 provides an indication (e.g., an audible output and / or noise).

[0247] In some embodiments, pursuant to a determination that data corresponding to the third path is available to be provided by device 800 to pass reader terminal 850, device 800 provides a prompt (e.g., a visual, audible, and / or tactile prompt) to provide authorization for the data corresponding to the third path to be provided by device 800 to pass reader terminal 850. In some embodiments, pursuant to a determination that data corresponding to the third path is available to be provided by device 800 to pass reader terminal 850, device 800 maintains display 802 in an active state (e.g., display 800 is turned on).

[0248] In some embodiments, path 806a, path 806b, and the third path are associated with one another (e.g., all three paths provide access to the same event and / or day / time at the service provider). In some embodiments, the other paths for different events or times / days at the service provider are not used (e.g., do not result in a prompt that data corresponding to the third path is available). In some embodiments, a prompt is provided only for the additional path associated with path 806b.

[0249] In some embodiments, providing the prompt includes displaying an indication that data corresponding to at least the third path is available to be provided by the device 800 to the path reader terminal 850 (e.g., displaying a paging dot, displaying a representation of a stack of paths, displaying instructions to tap the screen, displaying instructions to swipe, displaying instructions to tilt the phone, and / or displaying a portion of the second path along an edge of the display). In the embodiment shown in FIG. 8E, the prompt includes displaying the text "PROCEED TO NEXT PATH" and displaying (e.g., maintaining its display) an indication 808a. In some embodiments, the prompt indicates the number of paths that are available to be provided by the device 800 to the path reader terminal (e.g., a paging dot indication 808a and / or an indication of a representation of a stack of paths 808b). In some embodiments, providing the prompt includes outputting an audio notification that data corresponding to the third path is available to be provided by the device 800 to the path reader terminal 850. In some embodiments, providing the prompt includes outputting a tactile output (e.g., vibration) via one or more tactile output generators when data corresponding to the third pass is available to be provided by the device 800 to the pass reader terminal 850.

[0250] In some embodiments, pursuant to a determination that data corresponding to the third path is not available to be provided by device 800 to pass reader terminal 850, device 800 ceases providing the prompt to provide authorization for data corresponding to the third path to be provided by device 800 to pass reader terminal 850. In some embodiments, pursuant to a determination that data corresponding to the third path is not available to be provided by device 800 to pass reader terminal 850, device 800 shuts down display 802 (e.g., display 802 is turned off and / or transitioned to a lower power state (e.g., a state having a lower brightness and / or refresh rate)).

[0251] In some embodiments, device 800 can display a representation of the third path and provide data corresponding to the third path to path reader terminal 850 according to the same techniques described for path 806a and path 806b with reference to Figures 8A-8F.

[0252] FIG. 8F illustrates an embodiment of a user interface 804 that includes (e.g., displays) a path 806a and an indication 808a that the path 806a is one (e.g., a first path) of a set of multiple (e.g., three) paths (e.g., the left paging dot is highlighted and / or filled in compared to the center and right dots). In FIG. 8F, the user interface 804 includes an indication 812 (e.g., a prompt) that all passes that can be provided by the device 800 to the pass reader terminal 850 can be redeemed with an input (e.g., a particular type of input and / or a press and hold gesture). In FIG. 8F, the device 800 receives (detects) a request 805 to redeem all passes (e.g., a press and hold gesture on the display 802). In response to receiving request 805, device 800 (e.g., automatically, without receiving further input) provides to path leader terminal 850 data corresponding to all paths that are available to be provided by device 800 to path leader terminal 850 (e.g., data corresponding to path 806a, path 806b, and / or the path corresponding to the paging dot to the right of indication 808a).

[0253] In some embodiments, the techniques described with reference to Figures 8A-8F may be applied to a sequence of passes including only one pass, only two passes, or more than three passes.

[0254] 9 is a flow diagram illustrating a method for providing a prompt to a user to provide authorization, according to some embodiments. Method 900 is performed on a computer system (e.g., 100, 300, 500, 600a, 600b, 800) in communication with a display generating component (e.g., 602a, 602b, 802) and one or more input devices (e.g., a touch-sensitive surface). Some operations of method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0255] As described below, method 900 provides an intuitive way to provide a prompt to a user to provide authorization for data corresponding to a second pass provided to a pass reader terminal. The method reduces the cognitive burden on the user when providing data corresponding to more than one pass to a pass reader terminal, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, power is conserved and the time between battery charges is increased by allowing a user to authenticate passes (e.g., grouped passes) faster and more efficiently.

[0256] In method 900, a computer system (e.g., 800) detects (902) that data corresponding to a first pass (e.g., 806a) has been provided by the computer system to a pass reader terminal (e.g., 850) separate from the computer system (e.g., via a signal from an NFC transceiver, an optical scan, and / or a communication (e.g., a confirmation message from a remote server) indicating that a visual representation of the pass, such as a barcode or QR code, has been optically scanned).

[0257] After detecting that data corresponding to the first path has been provided by the computer system to the path leader terminal, the computer system, via a display generation component (e.g., 802), displays (904) an indication (e.g., 810, animation of path 806a) that data corresponding to the first path has been provided by the computer system to the path leader terminal.

[0258] Pursuant to a determination (906) that data corresponding to a second pass (e.g., 806b) is available to be provided by the computer system to the pass reader terminal, the computer system provides a prompt (e.g., 808a, 810, haptic notification, and / or audio notification) to the user to provide authorization for data corresponding to the second pass to be provided by the computer system to the pass reader terminal. In some embodiments, the first pass and the second pass are associated with each other (e.g., both passes provide access to the same event and / or day / time at the service provider (e.g., other passes for different events or times / days at the service provider are not used and / or prompts are provided only for additional passes associated with the first pass)). By providing a prompt to the user to provide authorization for data corresponding to the second pass to be provided to the pass reader terminal, feedback is provided to the user that additional passes are available to be provided to the pass reader terminal. By providing improved feedback to the user, it improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and in addition reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0259] Pursuant to a determination that data corresponding to the second path (e.g., 806b) is not available to be provided by the computer system to the pass reader terminal (908), the computer system ceases providing prompts to the user to provide authorization for data corresponding to the second path to be provided by the computer system to the pass reader terminal.

[0260] In some embodiments, prior to detecting (via an NFC signal from the pass reader terminal, via a confirmation message from a remote server, and / or via an optical scan) that data corresponding to the first pass has been provided by the computer system to the pass reader terminal, the computer system, via a display generating component, displays a user interface (e.g., 804) including a representation of the first pass (e.g., 806a) (e.g., an image including the name of the first guest and / or the service provider's logo). In some embodiments, the display is deactivated before the data is provided to the pass reader terminal. By displaying a user interface including a representation of the first pass, visual feedback is provided to the user confirming that the pass has been provided to the pass reader terminal. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0261] In some embodiments, after displaying an indication (e.g., 810) via the display generating components (e.g., 802) that data corresponding to a first path (e.g., 806a) has been provided by the computer system to the path leader terminal (e.g., 850), in accordance with a determination that a second path (e.g., 806b) is available to be provided by the computer system to the path leader terminal, the computer system maintains the display generating components in an active state (e.g., the display is turned on). In some embodiments, in accordance with a determination that data corresponding to the second path is not available to be provided by the computer system to the path leader terminal, the computer system deactivates the display generating components (e.g., the display is turned off and / or transitioned to a lower power state (e.g., a lower brightness and / or refresh rate state)). By maintaining the display generating components in an active state in accordance with a determination that data corresponding to the second path is available to be provided to the path leader terminal, visual feedback is provided to the user that data corresponding to the second path is available to be provided to the path leader terminal. By providing improved visual feedback to the user, the computer system's usability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and in addition, power usage is reduced and battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0262] In some embodiments, providing the prompt includes displaying, via a display generating component, an indication (e.g., 808a, 808b, 810) that data corresponding to at least the second path is available to be provided by the computer system to the pass reader terminal (e.g., displaying paging dots, displaying a representation of a stack of paths, displaying instructions to tap the screen, displaying instructions to swipe, displaying instructions to tilt the phone, and / or displaying a portion of the second path along an edge of the display). By displaying an indication that data corresponding to at least the second path is available to be provided by the computer system to the pass reader terminal, visual feedback is provided to the user that an additional path is available to be provided to the pass reader terminal. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0263] In some embodiments, the prompt indicates the number of paths (e.g., 808a, 808b) that are available to be provided by the computer system to the pass reader terminal (e.g., a representation of a paging dot and / or a stack of paths). By indicating the number of paths that are available to be provided to the pass reader terminal, visual feedback is provided to the user as to whether additional paths are available to be provided to the pass reader terminal. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0264] In some embodiments, providing the prompt includes outputting an audio notification that data corresponding to a second path is available to be provided by the computer system to the pass reader terminal. Outputting an audio notification that data corresponding to a second path is available to be provided by the computer system to the pass reader terminal provides feedback to the user that an additional path is available to be provided to the pass reader terminal. Providing improved feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0265] In some embodiments, providing the prompt includes outputting a tactile output (e.g., vibration) via one or more tactile output generators when data corresponding to a second path is available to be provided by the computer system to the pass reader terminal. Outputting a tactile output when data corresponding to a second path is available to be provided by the computer system to the pass reader terminal provides feedback to the user that an additional path is available to be provided to the pass reader terminal. Providing improved feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0266] In some embodiments, after providing a prompt to the user to provide authorization for data corresponding to the second pass to be provided by the computer system to the pass reader terminal, the computer system detects user input via one or more input devices (e.g., input on a touch-sensitive surface, movement of the computer system, and / or biometric information (e.g., face information, iris information, and / or fingerprint information)). In response to detecting the user input, the computer system displays, via a display generation component, a representation of the second pass (e.g., 806b) (e.g., an image having the name of the second guest and / or a service provider logo). In some embodiments, after displaying the representation of the second pass, the computer system detects a request to provide authorization for data corresponding to the second pass to be provided to the pass reader (e.g., placing a device next to the pass reader). In response to detecting the user input, displaying the representation of the second pass provides visual feedback to the user that data corresponding to the second pass is available to be provided to the pass reader terminal. By providing improved visual feedback to the user, the computer system's usability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and in addition, power usage is reduced and battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0267] In some embodiments, after providing a prompt to the user to give authorization for the data corresponding to the second path to be provided by the computer system to the pass reader terminal, the computer system detects authorization of the data corresponding to the second path to be provided by the computer system to the pass reader terminal. In some embodiments, the authorization includes detecting (e.g., via an accelerometer) a movement of a component of the computer system from a lowered position to a raised position (e.g., the device is lifted from the pass reader to authorize the second path). In some embodiments, the authorization further includes detecting a biometric sensor (e.g., a camera and / or a fingerprint sensor), biometric information (e.g., face information, iris information, and / or fingerprint information). In some embodiments, after lifting the device from the pass reader, the device is lowered again to provide the data corresponding to the second path to the pass reader. By authorizing the data corresponding to the second path to be provided by the computer system to the pass reader terminal in response to detecting the movement of the component of the computer system from the lowered position to the raised position, the user can efficiently authorize the data corresponding to the second path to be provided to the pass reader terminal without having to provide additional input to navigate an additional user interface. Improves operability of the computer system by reducing the number of user inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0268] In some embodiments, authorizing the data corresponding to the second path to be provided to the pass reader terminal includes detecting a swipe gesture (e.g., 803) on the display generating component. In some embodiments, after detecting the swipe gesture and authorizing the second path, the data corresponding to the second path is provided to the pass reader. In some embodiments, authorizing includes detecting a rotation of a rotatable input device (e.g., a watch crown). In some embodiments, authorizing further includes detecting biometric information (e.g., face information, iris information, and / or fingerprint information). By authorizing the data corresponding to the second path to be provided by the computer system to the pass reader terminal in response to detecting the swipe gesture on the display generating component, the user can efficiently authorize the data corresponding to the second path to be provided to the pass reader terminal without having to provide additional input to navigate an additional user interface. Improves operability of the computer system by reducing the number of user inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0269] In some embodiments, authorizing the data corresponding to the second path to be provided to the pass reader terminal includes detecting an input (e.g., 805) (e.g., a tap and hold gesture) via one or more input devices within a predetermined time (e.g., while the display generating component is in proximity to the pass reader terminal (e.g., within range of a wireless signal from the pass reader terminal). In some embodiments, the input is on an icon showing a group of paths. In some embodiments, the input is at any location on the display generating component. In some embodiments, detecting the input on the display generating component for a predetermined time authorizes data corresponding to all paths, including the first path and the second path, to be provided to the pass reader terminal. By authorizing the data corresponding to the second path and the one or more additional paths to be provided to the pass reader terminal by the computer system in response to detecting the input for a predetermined time, a user can efficiently authorize the data corresponding to the second path and the one or more additional paths to be provided to the pass reader terminal without providing additional input to navigate additional user interfaces. Improves operability of the computer system by reducing the number of user inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0270] In some embodiments, prior to detecting that data corresponding to the first pass has been provided by the computer system to the pass reader terminal, the computer system, via a display generation component, displays a user interface (e.g., 804) including a representation of the first pass (e.g., 806a) (e.g., an image including the name of the first guest and / or a service provider logo). In some embodiments, the representation of the first pass is displayed in response to a user input selecting the first pass. In some embodiments, the representation of the first pass is displayed in response to a user input that causes data for the first pass to be provided to the pass reader terminal. Displaying the user interface including the representation of the first pass provides visual feedback to the user that a pass can be provided to the pass reader terminal. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0271] In some embodiments, if (e.g., only if) a first pass (e.g., 806a) and a second pass are associated with one another (e.g., both passes provide access to the same event and / or day / time at the service provider (e.g., other passes for different events and / or times / days at the service provider are not used and / or prompts are provided only for additional passes associated with the first pass)), data corresponding to the second pass (e.g., 806b) is determined to be available to be provided by the computer system to the pass reader terminal. Determining that data corresponding to the second pass is available to be provided by the computer system to the pass reader terminal when the first pass and the second pass are associated with one another can provide the user with additional control when redeeming passes (e.g., by prompting the user to redeem the associated pass and not a pass for another venue or event). Providing a user with additional control of the computer system improves operability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0272] It should be noted that the process details described above with respect to method 900 (e.g., FIG. 9) are also applicable in a similar manner to the methods described above / below. For example, methods 700 and 1100 optionally include one or more of the features of the various methods described above with reference to method 900. For the sake of brevity, these details will not be repeated below.

[0273] 10A-10L show example user interfaces for displaying machine-readable code, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0274] 10A shows a device 1000 that includes a display 1002 (e.g., a touch screen display). In FIG. 10A, the device 1000 displays a user interface 1004 that includes information regarding conducting a transaction with an account (e.g., a payment account, a bank account, a credit card account, a debit card account, and / or a data storage account). In some embodiments, the user interface 1004 is a user interface for a vendor application (e.g., a third-party application associated with a bank, credit card, and / or data migration service) or a vendor website (e.g., a third-party website associated with a bank, credit card, and / or data migration service).

[0275] User interface 1004 includes an affordance 1006 that, when selected, initiates a process for adding an account to the wallet application. In some embodiments, the wallet application is a first party application developed, managed, and / or provided by a developer of device 1000 and / or an operating system running on device 1000. In FIG. 10A , while displaying user interface 1004, device 1000 receives (e.g., detects) a request 1003 to add an account presented on user interface 1004 to the first party wallet application. In the embodiment shown in FIG. 10A , request 1003 includes a selection (e.g., tap) of affordance 1006.

[0276] FIG 10B shows device 1000 displaying user interface 1008 (e.g., a user interface for a wallet application). After (e.g., in response to) receiving request 1003 (e.g., as shown in FIG 10A), user interface 1008 includes a representation 1010 of an account (e.g., an image of a card), as shown in FIG 10B. In some embodiments, while displaying user interface 1008, device 1000 receives (e.g., detects) a request 1005 to use the account in a transaction. In the embodiment shown in FIG 10B, request 1005 includes a selection (e.g., tap) of representation 1010 of the account.

[0277] FIG 10C illustrates a device 1000 displaying a user interface 1012 that includes a representation 1010 of an account to be used in a transaction. In some embodiments, the user interface 1012 is displayed in response to receiving (e.g., detecting) a request 1005 to use the account in a transaction, as shown in FIG 10B. In some embodiments, the user interface 1012 further includes offers 1014 (e.g., selectable offers), as shown in FIG 10D. In some embodiments, the offers 1014 are discounts that can be used for transactions performed with the account (e.g., the offers 1014 can be selected to obtain additional information about the offers, access the offers, and / or apply the offers).

[0278] In order to use an account for a transaction, the identity of a user of device 1000 is authenticated. In some embodiments, the identity of a user of device 1000 is authenticated using facial recognition. In some embodiments, facial recognition is initiated in response to receiving (e.g., detecting) a request 1001 to initiate facial recognition of a user. In the embodiment shown in FIG. 10C, the request 1001 includes detecting a double-click input (e.g., two presses within a predetermined period of time) using button 1040. In some embodiments, the identity of a user of device 1000 is authenticated using fingerprint recognition, a passcode, or other biometric information.

[0279] 10E, pursuant to a determination that the identity of the user of the device 1000 corresponds to an authorized user of the account, a first machine-readable code 1018 (e.g., a QR code and / or a two-dimensional code) is displayed. In some embodiments, a second machine-readable code 1020 (e.g., a barcode and / or a one-dimensional code) is displayed simultaneously with the first machine-readable code 1018. In some embodiments, displaying the first machine-readable code 1018 includes displaying an animation of the representation 1010 of the account transitioning to the machine-readable code 1018 (e.g., gradually transitioning between multiple intermediate states while transitioning from the representation 1010 of the account to the machine-readable code 1018) (as shown in FIGS. 10C and 10D). In some embodiments, the representation 1010 of the account is animated to appear inverted, such that the back side 1016 of the representation is displayed (e.g., the card image is flipped over) and the machine-readable code 1018 is included on the back side 1016 of the representation (the back side of the card image includes the machine-readable code).

[0280] In some embodiments, the first machine-readable code 1018 or the second machine-readable code 1020 can be scanned (e.g., with a camera, laser, and / or other optical sensing device) to initiate a transaction using the account. For example, in some embodiments, the first machine-readable code 1018 and the second machine-readable code 1020 correspond to account information (e.g., an account number). The account information can be used to transfer money into or out of the account. In some embodiments, the transaction is a transfer of money to a merchant to purchase an item. In some embodiments, the transaction is a person-to-person transfer of money.

[0281] In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 are different each time the code is displayed (e.g., a different code is displayed each time a request to use an account for a transaction is received and the user's identity is determined to correspond to an authorized user), allowing a unique code to be displayed for each transaction.

[0282] In FIG. 10E, while displaying the first machine-readable code 1018, the device 1000 receives (e.g., detects) a request 1007 to display the machine-readable code at a larger size. In the embodiment shown in FIG. 10E, the request 1007 includes a selection (e.g., tap) of the back side 1016 of the representation of the account. In response to detecting the request 1007 to display the machine-readable code at a larger size, the second machine-readable code 1020 is displayed at a larger size, as shown in FIG. 10F. In some embodiments, in response to detecting the request 1007 to display the machine-readable code at a larger size, the first machine-readable code 1018 is displayed at a larger size. In some embodiments, displaying the machine-readable code at a larger size may make it easier to scan the machine-readable code by a camera, laser, or other optical sensing device.

[0283] In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 are stopped from displaying after a predetermined time (e.g., after 5 seconds, 15 seconds, 1 minute, and / or in response to a time threshold being met). In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 are stopped from displaying if a transaction confirmation is not received within a predetermined time (e.g., within 5 seconds, 15 seconds, 1 minute, and / or in response to a time threshold being met). In some embodiments, the predetermined amount of time is the amount of time since authenticating the user or since first displaying the machine-readable code.

[0284] 10G, after the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 is stopped, a prompt to authenticate the user's identity again is displayed. In some embodiments, a notification 1026 is displayed indicating that a transaction confirmation has not been received. In some embodiments, stopping the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 includes replacing the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 with a display of the representation of the account 1010. In some embodiments, replacing the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 with a display of the representation of the account 1010 includes displaying an animation of the first machine-readable code 1018 and / or the second machine-readable code 1020 transitioning to the representation of the account 1010 (e.g., gradually transitioning between multiple intermediate states while transitioning from the machine-readable code to the representation of the account). In some embodiments, the representation 1010 of the account is displayed with the back side 1016 of the representation animated to appear inverted (e.g., the card image is flipped from back to front) (as shown in FIG. 10E).

[0285] In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 are replaced with a different machine-readable code after a predetermined time (e.g., after 5 seconds, 15 seconds, 1 minute, and / or depending on whether a time threshold is met). In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 are replaced with a different machine-readable code if a transaction confirmation is not received within a predetermined time (e.g., after 5 seconds, 15 seconds, 1 minute, and / or depending on whether a time threshold is met). In some embodiments, the predetermined amount of time is the amount of time since authenticating the user or since first displaying the machine-readable code. In some embodiments, after a new machine-readable code is displayed, the previously displayed machine-readable code becomes invalid.

[0286] As shown in FIG. 10H, after receiving a transaction confirmation (e.g., from a third-party vendor application) that the first machine-readable code 1018 and / or the second machine-readable code 1020 were used to successfully access information associated with the account (e.g., the transaction using the account was authorized), the first machine-readable code 1018 and / or the second machine-readable code 1020 ceases to be displayed and an indication 1030 (e.g., a check mark) is displayed that the information associated with the account was successfully accessed.

[0287] FIG 10I illustrates a device 1050 that includes a display 1052 (e.g., a touchscreen display). In FIG 10I, the device 1000 displays a user interface 1054 that includes a representation 1056 of an account to be used for the transaction (e.g., a payment account, a bank account, a credit card account, a debit card account, and / or a data storage account). In FIG 10I, while displaying the user interface 1054, the device 1050 receives (e.g., detects) a request 1053 to use the account for the transaction. In the embodiment illustrated in FIG 10I, the request 1053 includes a selection (e.g., a tap) of the representation 1056 of the account.

[0288] In response to receiving (e.g., detecting) a request 1053 to use the account for the transaction, a first machine-readable code 1058 (e.g., a QR code and / or a two-dimensional code) is displayed, as shown in FIG. 10J. In some embodiments, an indication 1062 (e.g., a paging dot) indicating the first machine-readable code 1058 is one (e.g., a first code) of a set of multiple (e.g., two) types of machine-readable codes (e.g., a left paging dot is highlighted and / or filled in compared to a right dot). In FIG. 10J, while displaying the first machine-readable code 1058, the device 1050 receives (e.g., detects) a request 1055 to display a different type of machine-readable code. In the embodiment shown in FIG. 10J, the request 1055 includes a swipe gesture on the display 1052.

[0289] In response to receiving (e.g., detecting) a request 1055 to display a different type of machine-readable code, a second machine-readable code 1060 (e.g., a barcode and / or a one-dimensional code) is displayed, as shown in Figure 10K. In some embodiments, the indication 1062 is updated to indicate that a different type of machine-readable code is being displayed.

[0290] In some embodiments, the type of machine-readable code displayed in response to receiving (e.g., detecting) a request 1053 to use an account for a transaction is based on the type of machine-readable code last used for the transaction (e.g., if a barcode was last used for the transaction, then a barcode is displayed in response to the request 1053 instead of a QR code).

[0291] As shown in FIG. 10L, after receiving a transaction confirmation (e.g., from a third-party vendor application) that the first machine-readable code 1058 and / or the second machine-readable code 1060 were used to successfully access information associated with the account (e.g., the transaction using the account was authorized), the first machine-readable code 1018 and / or the second machine-readable code 1020 ceases to be displayed and an indication 1064 (e.g., a check mark) is displayed that the information associated with the account was successfully accessed.

[0292] 11 is a flow diagram illustrating a method for displaying a machine-readable code in response to receiving authentication data, according to some embodiments. Method 1100 is performed on a computer system (e.g., 100, 300, 500, 600a, 600b, 800, 1000, 1050) in communication with a display generating component (e.g., 602a, 602b, 802, 1002, 1052,) and one or more input devices (e.g., a touch-sensitive surface, a camera, a fingerprint sensor, and / or a biometric sensor). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0293] As described below, the method 1100 provides an intuitive way to display machine-readable code. The method reduces the cognitive burden on a user when displaying machine-readable code on a computer system. For battery-operated computing systems, allowing a user to display machine-readable code more quickly and efficiently conserves power and extends the time between battery charges.

[0294] In method 1100, a computer system (e.g., 1000, 1050), via a display generating component (e.g., 1002, 1052), displays (1102) a first user interface (e.g., 1008, 1012, 1054) including an indication (e.g., 1010, 1056) of an account (e.g., a payment card and / or a data storage account). In some embodiments, the first user interface is displayed in response to a double tap (e.g., 1001) of a hardware button (e.g., 1040).

[0295] The computer system receives 1104 authentication data (eg, facial information, fingerprint information, and / or a passcode) via one or more input devices (eg, via one or more biometric sensors).

[0296] In response to receiving the authentication data (1106), and in accordance with a determination that the authentication data meets an authentication criteria associated with the account (1108) (e.g., the facial information matches the account owner's facial information, the fingerprint information matches the account owner's fingerprint information, and / or the passcode matches the account owner's passcode), the computer system, via the display generation component, displays a first machine-readable code (e.g., 1018, 1020, 1058, 1060) (e.g., a two-dimensional code (e.g., a QR code) and / or a one-dimensional code (e.g., a barcode)) associated with the account (e.g., the machine-readable code may be used to authorize a transaction for the account). Displaying the machine-readable code in accordance with a determination that the authentication data meets the authentication criteria associated with the account provides visual feedback to the user confirming that the authentication criteria have been met, and improves security of the transaction using the machine-readable code. By providing improved visual feedback to the user, the computer system's usability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and in addition, power usage is reduced and battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0297] In response to receiving the authentication data (1106), and in accordance with a determination that the authentication data does not meet the authentication criteria associated with the account (1110), the computer system ceases displaying a first machine-readable code (e.g., 1018, 1020, 1058, 1060) associated with the account.

[0298] In some embodiments, displaying the machine-readable code (e.g., 1018, 1020, 1058, 1060) includes replacing the display of the account indication (e.g., 1010, 1056) with a display of the machine-readable code (e.g., ceasing to display the account indication and displaying the machine-readable code). In some embodiments, replacing the display of the account indication with a display of the machine-readable code includes an animated transition from the account indication to the machine-readable code (e.g., gradually transitioning between multiple intermediate states while transitioning from the account indication to the machine-readable code). Replacing the display of the account indication with a display of the machine-readable code provides visual feedback to the user confirming that the authentication criteria have been met, improving the security of the transaction using the machine-readable code. By providing improved visual feedback to the user, the computer system's usability is improved, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and in addition, power usage is reduced and battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0299] In some embodiments, the computer system, via the display generation component, displays a second user interface (e.g., 1004) for an application associated with the service provider (e.g., a third party application associated with a vendor (e.g., a bank and / or merchant)). In some embodiments, an account is associated with the service provider. In some embodiments, while displaying the second user interface, the computer system detects (e.g., via the touch-sensitive surface) a request (e.g., 1003) to configure the account for use with the first user interface (e.g., a request to add a card associated with the vendor to the first user interface), and in response to detecting the request to configure the account for use with the first user interface, the computer system includes an indication of the account in the first user interface (e.g., 1008). By detecting a request to configure the account for use with the first user interface while displaying the second user interface, a user may efficiently configure an account (e.g., for use with a wallet application) without having to manually navigate between multiple user interfaces. Improves operability of the computer system by reducing the number of inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0300] In some embodiments, the computer system receives, via one or more input devices, second authentication data (e.g., facial information, fingerprint information, and / or a passcode), and in response to receiving the second authentication data, pursuant to a determination that the second authentication data meets an authentication criteria associated with the account (e.g., the facial information matches the account owner's facial information, the fingerprint information matches the account owner's fingerprint information, and / or the passcode matches the account owner's passcode), the computer system displays, via the display generating component, a second machine-readable code (e.g., 1018, 1020, 1058, 1060) (e.g., a two-dimensional code (e.g., a QR code) and / or a one-dimensional code (e.g., a barcode)) associated with the account, where the second machine-readable code is different from the first machine-readable code (e.g., each time a transaction is authorized a different machine-readable code is displayed). In some embodiments, the machine-readable code is different from all previous codes (e.g., the machine-readable code is unique). In some embodiments, in response to receiving the second authentication data and following a determination that the second authentication data does not meet an authentication criterion associated with the account, the computer system ceases to display the second machine-readable code associated with the account. Displaying the second machine-readable code, which is different from the first machine-readable code, provides visual feedback to the user confirming that the authentication criterion has been met, improving security of the transaction by using a different machine-readable code for each transaction. Providing improved visual feedback to the user improves operability of the computer system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0301] In some embodiments, after displaying a machine-readable code associated with an account (e.g., 1018, 1020, 1058, 1060), the computer system stops displaying the machine-readable code after a predetermined time (e.g., 5 seconds, 15 seconds, 1 minute). In some embodiments, the computer system stops displaying the machine-readable code in response to determining that a time threshold has been met (e.g., the machine-readable code has been displayed for a predetermined time and / or a predetermined time has passed since receiving the authentication information or since initially displaying the machine-readable code). Stopping displaying the machine-readable code after a predetermined time improves the security of the transaction by limiting the time the machine-readable code is displayed.

[0302] In some embodiments, the machine-readable code is a first machine-readable code, and after displaying a first machine-readable code (e.g., 1018, 1020, 1058, 1060) associated with the account, the computer system stops displaying the first machine-readable code after a predetermined time (e.g., after 5 seconds, 15 seconds, 1 minute, and / or in response to a time threshold being met), and the computer system displays a second machine-readable code (e.g., 1018, 1020, 1058, 1060) associated with the account that is different from the first machine-readable code associated with the account. In some embodiments, the second machine-readable code is displayed in response to a time threshold being met (e.g., when the first machine-readable code has been displayed for a predetermined time). Displaying a second machine-readable code that is different from the first machine-readable code improves the security of the transaction by limiting the time the machine-readable code is displayed.

[0303] In some embodiments, after displaying the machine-readable code associated with the account (e.g., 1018, 1020, 1058, 1060) and pursuant to a determination that second authentication data is received within a predetermined time (e.g., within 5 seconds, 30 seconds, 2 minutes, and / or in response to a time threshold being met) and the second authentication data meets an authentication criterion associated with the account (e.g., the facial information matches the account owner's facial information, the fingerprint information matches the account owner's fingerprint information, and / or the passcode matches the account owner's passcode), the computer system maintains the display of the machine-readable code associated with the account. In some embodiments, after displaying the machine-readable code associated with the account, pursuant to (e.g., in response to) a determination that second authentication data is not received within a predetermined time (e.g., within 5 seconds, 30 seconds, 2 minutes, and / or in response to a time threshold being met) or the second authentication data does not meet an authentication criterion associated with the account, the computer system ceases displaying the machine-readable code associated with the account. In some embodiments, the machine-readable code is replaced with a payment card image (e.g., 1010, 1056) (e.g., the card associated with the previously displayed machine-readable code). Ceasing to display the machine-readable code pursuant to a determination that the second authentication data is not received within a predetermined time provides visual feedback to the user that the authentication criteria was not met, and improves the security of the transaction by limiting the time the machine-readable code is displayed. Providing improved visual feedback improves operability of the computer system and makes the user device interface more efficient (e.g., by assisting the user in making appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0304] In some embodiments, after displaying the machine-readable code associated with the account (e.g., 1018, 1020, 1058, 1060) and (for example) pursuant to a determination that the second authentication data is not received within a predetermined time (e.g., within 5 seconds, 30 seconds, 2 minutes, and / or in response to a time threshold being met) or the second authentication data does not meet an authentication criterion associated with the account, the computer system displays a request for second authentication data (e.g., a user interface 1012 as shown in FIG. 10G) (e.g., a request to re-authorize the transaction using biometric information (e.g., facial information and / or fingerprint information) and / or a passcode). Displaying a request for second authentication data provides visual feedback to the user that the second authentication data was not received within the predetermined time or the authentication criterion was not met. Providing improved visual feedback can improve operability of the computer system and can make the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn can reduce power usage and improve battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0305] In some embodiments, after displaying the machine-readable code associated with the account (e.g., 1018, 1020, 1058, 1060), the computer system receives confirmation (e.g., from a third-party vendor app) that the machine-readable code was successfully used to access information associated with the account (e.g., a transaction using the account was authorized), and in response to receiving confirmation that the machine-readable code was successfully used to access information associated with the account, the computer system stops displaying the machine-readable code and the computer system displays, via the display generating component, an indication (e.g., 1030) (e.g., a checkmark icon) that the information associated with the account was successfully accessed. Displaying an indication that the information associated with the account was successfully accessed provides visual feedback to the user that the machine-readable code was successfully used to access information associated with the account. Providing improved visual feedback can improve operability of the computer system and can make the user device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn can reduce power usage and improve battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0306] In some embodiments, displaying the machine-readable code includes displaying the machine-readable code (e.g., 1020) at a first size. In some embodiments, while displaying the machine-readable code at the first size, the computer system detects a request (e.g., 1007) to display the machine-readable code at a larger size (e.g., a tap gesture on the machine-readable code), and in response to detecting the request to display the machine-readable code at a larger size, the computer system displays the machine-readable code at a second size that is larger than the first size (e.g., 1020 as shown in FIG. 10F). Displaying the machine-readable code at a second size that is larger than the first size provides the user with additional control over the size of the machine-readable code. A larger machine-readable code may improve the ability of a code scanner to read the machine-readable code. Providing a user with additional control of the computer system improves operability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0307] In some embodiments, the machine-readable code is a first type of machine-readable code (e.g., 1058) (e.g., a QR code). In some embodiments, while displaying the first type of machine-readable code, the computer system detects a request (e.g., 1055) (e.g., a swipe gesture) to display a second type of machine-readable code (e.g., 1060) (e.g., a barcode), and in response to detecting the request to display the second type of machine-readable code, the computer system displays the second type of machine-readable code (e.g., the QR code is replaced with a barcode and / or the barcode is replaced with a QR code). In some embodiments, the request to display the second type of machine-readable code, for example on a watch (e.g., 1050), is detected after tapping on a representation of an account (1056) to display the machine-readable code. In some embodiments, the order of display of the QR code or barcode is based on the type of code last displayed. Displaying a second type of machine-readable code provides the user with additional control over the type of machine-readable code. A different type of machine-readable code may allow the machine-readable code to be scanned by an additional type of code scanner. Providing the user with additional control of the computer system improves operability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0308] In some embodiments, displaying the first user interface includes displaying one or more offers (e.g., 1014, selectable offers) associated with the account (e.g., discounts that may be used in transactions with the account provider). Displaying one or more offers associated with the account allows the user to access contextually related offers from the first user interface without navigating to additional user interfaces. Improves usability of the computer system by reducing the number of inputs required to perform operations, makes the user system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the computer system), and reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0309] It should be noted that details of the process (e.g., FIG. 11) described above with respect to method 1100 are also applicable in a similar manner to the methods described above. For example, methods 700 and 900 optionally include one or more of the features of the various methods described above with reference to method 1100. For the sake of brevity, these details will not be repeated below.

[0310] FIG. 12A illustrates an electronic device 1200 having a display 1202 (e.g., a touch screen) and one or more input devices (e.g., a rotatable input mechanism 1204, side buttons 1206). In FIG. 12A, the electronic device 1200 displays an account user interface 1208 (e.g., similar to account user interface 1302 described below with reference to FIG. 13B) on the display 1202. The electronic device 1200 displays a number of platters 1210 associated with a user's respective computer storage account on the account user interface 1208. The user's respective computer storage account includes various amounts of (e.g., cloud-based) computer storage resources. In some embodiments, different types of data (e.g., data corresponding to photo files, data corresponding to document files, data corresponding to music files, data corresponding to video files, data corresponding to application files) can be stored and / or archived within the computer storage resources associated with the user account (e.g., computer storage account). Thus, in response to detecting a user input corresponding to a selection of a platter of the plurality of platters 1210, the electronic device 1200 displays information related to computer storage resources (e.g., amount of data available and / or amount of data consumed) associated with the respective computer storage account corresponding to the selected platter.

[0311] In FIG. 12A , the electronic device 1200 displays a storage card platter 1210a and a memory platter 1210b (e.g., a partial view of a memory computer storage account platter 1210b) on an account user interface 1208. Further, in FIG. 12A , the electronic device 1200 detects a swipe gesture 1250a (e.g., an upward swipe gesture). In response to detecting the swipe gesture 1250a, the electronic device 1200 scrolls the account user interface 1208 (e.g., scrolls and / or translates the plurality of platters 1210 of the account user interface 1208 in a downward direction) to display additional platters of the plurality of platters 1210. In some embodiments, the electronic device 1200 is also configured to scroll the account user interface 1208 based on a rotation of the rotatable input mechanism 1204 in addition to the swipe gesture.

[0312] 12B , electronic device 1200 displays storage card platter 1210a (e.g., storage card platter 1210a), memory platter 1210b, and shared data platter 1210c (e.g., a partial view of shared data platter 1210c) in account user interface 1208. Thus, swipe gesture 1250a causes an additional platter of plurality of platters 1210 (e.g., shared data platter 1210c) to be at least partially displayed on account user interface 1208.

[0313] 12C, the electronic device 1200 has detected the end of the swipe gesture 1250a, and the electronic device 1200 displays the account user interface 1208 while the memory platter 1210b is centered on the display 1202 (e.g., the memory platter 1250a has stopped scrolling and / or the electronic device 1200 does not detect any further user input to scroll the platter after the swipe gesture 1250a caused the account user interface 1208 to scroll). As a result of pausing the memory platter 1210b (e.g., the memory player 1210b) at a predefined position (or within a predefined area) of the display or user interface for at least a predetermined period of time (e.g., without scrolling the memory platter 1210b for a predetermined period of time), the account user interface 1208 is modified as shown in FIG.

[0314] In FIG. 12C , the appearance of storage card platter 1210a and shared data platter 1210c is de-emphasized compared to memory platter 1210b. Storage card platter 1210a and shared data platter 1210c are de-emphasized by being reduced in size compared to memory platter 1210b. To further emphasize the platters, the appearance of storage card platter 1210a and the appearance of shared data platter 1210c are altered (e.g., reduced opacity, blurred, and / or changed color) compared to memory platter 1210b (e.g., as represented in FIG. 12C by hatching). In some embodiments, electronic device 1200 is configured to de-emphasize the platters by ceasing to display platters that are not centered on display 1202.

[0315] Further, in some embodiments, as a result of pausing on memory platter 1250a, account user interface 1208 updates to include indicator 1212 ("tap view") indicating a prompt for a user of electronic device 1200 to view additional details related to the computer storage account associated with and / or represented by memory platter 1210b. In response to detecting a tap gesture on memory platter 1210b, electronic device 1200 displays a details user interface that provides a user with a visual representation related to computer storage resources of the computer storage account associated with memory platter 1210b. In some embodiments, electronic device 1200 ceases displaying indicator 1212 on account user interface 1208 based on the user input that caused account user interface 1208 to be displayed, as discussed in more detail below with reference to FIGS. 13A-13N. In some embodiments, a tap gesture on memory platter 1210b causes the details user interface to be displayed regardless of whether indicator 1212 is displayed on account user interface 1208.

[0316] FIG. 13A illustrates electronic device 1200 displaying a user interface 1300. In FIG. 13A, user interface 1300 is a watch face. In other embodiments, user interface 1300 is a user interface associated with an application of electronic device 1200. In FIG. 13A, electronic device 1200 detects user input 1350a (e.g., a double press gesture and / or a double tap gesture) on side button 1206. In response to detecting user input 1350a, electronic device 1200 displays account user interface 1302 of a money transfer application (e.g., an electronic wallet application), as shown in FIG. 13B. Further, in FIG. 13A, electronic device 1200 detects user input 1350b (e.g., a single press and / or a single tap input) on crown 1204. In response to detecting user input 1350b, electronic device 1200 displays application user interface 1320, as shown in FIG. 13I. In some embodiments, the electronic device 1200 displays the account user interface 1302 in response to detecting a user input 1350a (e.g., a double press gesture and / or a double tap gesture) regardless of what is displayed on the display 1202 (e.g., the clock face user interface 1300, the user interface of another application, and / or the application user interface 1320).

[0317] As discussed in detail below with reference to Figures 13B-13N, the user input 1350a authorizes and / or activates the transfer account linked to the electronic device 1200. Thus, the electronic device 1200 reveals (e.g., transmits) the credentials associated with the respective transfer account when a set of transfer criteria is met (e.g., when the electronic device 1200 is located within a threshold proximity of the receiver and the linked transfer account is authorized / activated). In contrast, upon receiving a different set of user inputs (e.g., in Figure 13I, the tap gesture 1350h followed by the user input 1350b), the electronic device 1200 causes the account user interface 1302 to be displayed without the electronic device 1200 (without further user input) authorizing and / or activating the linked transfer account. Thus, in response to detecting the user input 1350b (detecting the tap gesture 1350h), the electronic device 1200 does not reveal the credentials associated with the respective transfer account when a set of transfer criteria is met.

[0318] In FIG. 13B, the account user interface 1302 includes a number of platters 1304 associated with respective transfer accounts (e.g., payment accounts, such as third-party credit card accounts, debit card accounts, and / or stored value accounts, pass accounts, ticket accounts, points accounts, rewards accounts, and / or transit accounts) linked (e.g., provisioned) to the electronic device 1200. In some embodiments, a user may provide the electronic device 1200 with one or more transfer accounts and make transfers using the transfer accounts. For example, upon receiving access to the user's transfer account, the electronic device 1200 receives and stores in a secure element of the electronic device 1200 credentials associated with the transfer account (e.g., account number, pin code, authorization code, pass code, card number, balance information, and / or address). The electronic device 1200 exposes (e.g., transmits) credentials associated with the transfer account to a terminal (e.g., a wireless communication terminal and / or an NFC terminal) when the transfer account is activated and / or authorized by the user (e.g., via user input 1350a).

[0319] In Figure 13B, the electronic device 1200 displays a transfer card platter 1304a representing a first transfer account (e.g., a credit card account, a debit card account, and / or a dual credit / debit card account) and a cash platter 1304b (e.g., a partial view of the cash platter 1304b) representing a second transfer account (e.g., a cash card and / or a gift card) on the account user interface 1302. In Figure 13B, the transfer card platter 1304a and the cash platter 1304b have the same emphasis (e.g., the same opacity, the same size, and / or the same height). The transfer card platter 1304a is displayed centered on the display 1202 (e.g., at a predefined position (or within a predefined area) of the display or user interface), but because the electronic device 1202 has not paused the transfer card platter 1304a (e.g., the display 1202 of the electronic device has not displayed the card platter 1304a at a predefined position (or within a predefined area) of the display or user interface for at least a predefined period of time (e.g., the electronic device 1202 has not scrolled the transfer card platter 1304a during the predefined period of time)), the emphasis of the cash platter 1304b relative to the transfer card platter 1304a is not changed (e.g., the emphasis is not reduced).

[0320] In Figure 13B, the electronic device 1200 detects a swipe gesture 1350c (e.g., an upward swipe gesture) before the predetermined period of time has elapsed. In response to detecting the swipe gesture 1350c, the electronic device 1200 scrolls the account user interface 1302 (e.g., scrolls upward and / or translates the plurality of platters 1304 of the account user interface 1302) to display additional platters (e.g., 1304c, 1304d) of the plurality of platters 1304, as shown in Figure 13C. In some embodiments, the electronic device 1200 is also configured to scroll the account user interface 1208 based on rotation of the rotatable input mechanism 1204 in addition to the swipe gesture.

[0321] 13C , the electronic device 1200 displays a cash platter 1304b representing a second transfer account (e.g., a partial view of cash platter 1304b), a boarding pass platter 1304c representing a third transfer account (e.g., an airline account), and a frequent flyer card platter 1304d representing a fourth transfer account (e.g., a partial view of frequent flyer card platter 1304d) in the account user interface 1302. Thus, a swipe gesture 1350c causes additional platters of the plurality of platters 1304 (e.g., boarding pass platter 1304c and / or frequent flyer card platter 1304d) to be at least partially displayed on the account user interface 1302.

[0322] 13C, the platters have stopped scrolling and are stationary. Although boarding pass platter 1304c is displayed centered on display 1202 (e.g., at a predefined position (or within a predefined area) of a display or user interface), the display 1202 of the electronic device has not paused boarding pass platter 1304c (e.g., the display 1202 of the electronic device has not displayed boarding pass platter 1304c at a predefined position (or within a predefined area) of a display or user interface for at least a predefined period of time (e.g., the electronic device 1202 has not scrolled boarding pass platter 1304c during the predefined period of time)), and therefore does not change the emphasis (e.g., does not reduce the emphasis) of platters 1304b and 1304d relative to boarding pass platter 1304c.

[0323] 13C (and before the predetermined period of time has elapsed), the electronic device 1200 detects a swipe gesture 1350d (e.g., a downward swipe gesture) on the account user interface 1302. In response to detecting the swipe gesture 1350d, the electronic device 1200 scrolls the account user interface 1302 (e.g., scrolls upward and / or translates the multiple platters 1304 of the account user interface 1302) to display the account user interface 1302 as shown in FIG. In FIG. 13D , after the swipe gesture 1350d stops, the electronic device 1200 stops scrolling the account user interface 1302 (e.g., 3 seconds after detecting the end of the swipe gesture 1350d), and the electronic device 1200 pauses the transfer card platter 1304a (e.g., the transfer card platter 1304a remains centered on the display 1202 (e.g., at a predefined position (or location) of the display or user interface) for at least a predetermined period of time (e.g., without scrolling the transfer card platter 1304a for a predetermined period of time). is displayed within a predefined area). As a result of pausing on the transfer card platter 1304a (for a predetermined period of time (e.g., 2 seconds, 1 second, 2 seconds)), the account user interface 1302 is modified, as shown in FIG. 13D. In some embodiments, prior to pausing on a particular platter, each platter of the plurality of platters comprises a uniform size (e.g., each platter comprises the same size and / or shape). In some embodiments, prior to pausing on a particular platter, the platters of the plurality of platters have different heights, sizes, and / or shapes.

[0324] In Figure 13D, as a result of the pause on the transfer card platter 1304a, the appearance of the cache platter 1304b is de-emphasized relative to the transfer card platter 1304a (regardless of whether the platters have a uniform or non-uniform appearance in Figure 13C). De-emphasizing the cache platter 1304b relative to the transfer card platter 1304a may include, for example, reducing the size of the cache platter 1304b relative to the transfer card platter 1304a (e.g., reducing the size of the cache platter 1304b without reducing (or increasing) the size of the transfer card platter 1304a and / or increasing the size of the transfer card platter 1304a without increasing (or reducing) the size of the cache platter 1304b). Further, the additional appearance of cache platter 1304b is optionally altered (e.g., reduced opacity, blurred, and / or color changed) to reduce emphasis of cache platter 1304b compared to transfer card platter 1304a (e.g., as represented in FIG. 13D by the hatching of cache platter 1304b). In some embodiments, electronic device 1200 is configured to reduce emphasis of a platter that is not located at the center of display 1202 (e.g., cache platter 1304b) by ceasing to display the platter.

[0325] 13D , because the user input that caused the account user interface 1302 to be displayed as a result of pausing the transfer card platter 1304a was user input 1350a (and not tap gesture 1350h), the electronic device 1200 displays an indicator 1306 ("Hold Near Reader") indicating that the transfer account associated with the transfer card platter 1304a (e.g., the first transfer account) has been activated (e.g., authorized for use to perform transfers and / or transactions). The indicator 1306 prompts the user of the electronic device 1200 to place the electronic device in proximity to a receiver (e.g., within a threshold proximity of a device that can receive transmissions from the electronic device 1200). Thus, when the electronic device 1200 is placed in proximity to a receiver (e.g., within the proximity of a wireless communication terminal), the transfer account associated with the transfer card platter 1304a can be utilized to perform transfers (e.g., transactions using financial funds, transfers of points, transfers of credits, and / or authorization of entries) without further user input. A user input 1350a (as compared to a tap gesture 1350h) that causes the electronic device 1200 to display an account user interface 1302 enables the electronic device 1200 to authorize transfer accounts associated with the multiple platters 1304 of the account user interface 1302. As discussed below with reference to FIGS. 13I-13K, pausing the transfer card platter 1304a in the account user interface 1302 by accessing the account user interface 1302 via a technique that does not include a user input 1350a (e.g., instead includes a tap gesture 1350h and / or a voice command) does not activate the transfer account associated with the transfer card platter 1304a.

[0326] In Figure 13D, the electronic device 1200 detects a swipe gesture 1350e (e.g., an upward swipe gesture). In response to detecting the swipe gesture 1350e, the electronic device 1200 optionally cancels the reduction in emphasis (e.g., returns the platters to their visual appearance before the reduction in emphasis) and scrolls the account user interface 1302 (e.g., scrolls downward and / or translates the multiple platters 1304 of the account user interface 1302) to display the cash platter 1304b, the boarding pass platter 1304c, and the frequent flyer card platter 1304d, as shown in Figure 13E. Alternatively, to detect the swipe gesture 1350e, the electronic device 1200 detects a tap gesture 1350f on the transfer card platter 1304a. In response to detecting the tap gesture 1350f, the electronic device 1200 displays a user interface 1330, as shown in FIG. 13O.

[0327] In Figure 13E, in response to detecting a swipe gesture 1350e, the electronic device 1200 displays the account user interface 1302 and pauses the account user interface 1302 on the boarding pass platter 1304c. As shown in Figure 13E, as a result of pausing (for a predetermined period of time (e.g., 0.5 seconds, 1 second, 2 seconds)) on the boarding pass platter 1304c, the account user interface 1302 is modified.

[0328] In Figure 13E, in response to a pause on boarding pass platter 1304c, the appearance of cash platter 1304b and the appearance of frequent customer card platter 1304d are de-emphasized relative to boarding pass platter 1304c. The de-emphasis optionally includes cash platter 1304b and frequent customer card platter 1304d being reduced in size relative to boarding pass platter 1304c. Further, the de-emphasis optionally includes the appearance of cash platter 1304b and frequent customer card platter 1304d being altered (e.g., reduced opacity, blurred, and / or changed color) relative to boarding pass platter 1304c (e.g., as shown in Figure 13E by the hatching of cash platter 1304b and frequent customer card platter 1304d).

[0329] 13E, in response to pausing the boarding pass platter 1304c, the electronic device 1200 displays an indicator 1308 ("tap to see code") indicating that the transfer account associated with the boarding pass platter 1304c (e.g., a third transfer account) has been authorized and / or activated (e.g., the boarding pass is authorized for scanning). In FIG. 13E, the boarding pass platter 1304c includes a display of a visual indicator of information related to the particular pass represented by the boarding pass platter 1304c. For example, the boarding pass platter 1304c includes a display of a visual indication that distinguishes the boarding pass platter 1304c from the other boarding pass platters of the plurality of platters 1304. The boarding pass platter 1304c displays the name of the passenger associated with the boarding pass platter 1304c ("John Appleseed"), the date of travel (e.g., flight) associated with the boarding pass platter 1304c ("February 3, 2020"), the airline information for the flight associated with the boarding pass platter 1304c ("Airline"), and / or flight information for the flight associated with the boarding pass platter ("SFO DEN", ​​origin and destination). Thus, the electronic device 1200 allows a user to easily avoid confusion between different passes (e.g., boarding passes) that have a similar appearance on the account user interface 1302 based on the display details represented by the visual indications on the boarding pass platter 1304c.

[0330] In FIG. 13E, while boarding pass platter 1304c is authorized and / or activated (visually indicated by reduced highlighting of other platters), electronic device 1200 detects tap gesture 1350g on boarding pass platter 1304c. In response to detecting tap gesture 1304c, electronic device 1200 displays a machine-readable code 1310 (e.g., a QR code and / or a barcode), as shown in FIG. 13G. To display code 1310 in FIG. 13G, electronic device 1200 displays a transition (e.g., animation) between account user interface 1302 of FIG. 13E and code 1310 of FIG. 13G. For example, in FIG. 13F, electronic device 1200 displays boarding pass details user interface 1326 in response to tap gesture 1350g. In some embodiments, the boarding pass details user interface 1326 includes additional information (e.g., flight details) related to the transfer account associated with the boarding pass platter 1304c. In some embodiments, the electronic device 1200 display...

Claims

1. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; a memory storing one or more programs configured to be executed by the one or more processors; the one or more programs displaying, via the display generation component, a first user interface including an indication of an account; receiving authentication data via the one or more input devices; In response to receiving the authentication data, displaying, via the display generation component, a first machine-readable code associated with the account in accordance with a determination that the authentication data satisfies an authentication criterion associated with the account; and forgoing display of the first machine-readable code associated with the account in accordance with a determination that the authentication data does not satisfy the authentication criteria associated with the account; displaying the first machine readable code associated with the account; maintaining a representation of the first machine-readable code associated with the account in accordance with a determination that second authentication data is received within a predetermined time and that the second authentication data satisfies the authentication criteria associated with the account; receiving a confirmation that the first machine readable code was successfully used to access information associated with the account; and in response to receiving the confirmation that the first machine readable code was successfully used to access information associated with the account, ceasing to display the first machine-readable code; and displaying, via the display generating component, an indication that information associated with the account was successfully accessed; and ceasing to display the first machine-readable code associated with the account in accordance with a determination that second authentication data is not received within the predetermined time or that the second authentication data does not meet the authentication criteria associated with the account; and A computer system comprising instructions for:

2. the one or more programs displaying, via the display generation component, a second user interface for an application associated with a service provider, the account being associated with the service provider; and detecting, while displaying the second user interface, a request to configure the account for use with the first user interface; in response to detecting the request to configure the account for use with the first user interface, including the indication of the account in the first user interface; The computer system of claim 1 further comprising instructions for:

3. 2. The computer system of claim 1, wherein displaying the first machine-readable code comprises replacing the display of the indication of the account with the display of the first machine-readable code.

4. the one or more programs receiving third authentication data via the one or more input devices; In response to receiving the third authentication data, displaying, via the display generating component, a second machine-readable code associated with the account, the second machine-readable code being different from the first machine-readable code, in accordance with a determination that the third authentication data satisfies the authentication criteria associated with the account; forgoing display of the second machine-readable code associated with the account in accordance with a determination that the third authentication data does not satisfy the authentication criteria associated with the account; and The computer system of claim 1 further comprising instructions for:

5. the one or more programs displaying the first machine readable code associated with the account; in response to said determination that the second authentication data is not received within said predetermined time period, ceasing to display the first machine-readable code; and displaying a second machine readable code associated with the account that is different from the first machine readable code associated with the account; The computer system of claim 1 further comprising instructions for:

6. the one or more programs displaying the first machine readable code associated with the account; indicating a request for the second authentication data in accordance with a determination that second authentication data is not received within the predetermined time period or that the second authentication data does not satisfy the authentication criteria associated with the account; The computer system of claim 1 further comprising instructions for:

7. displaying the first machine-readable code includes displaying the first machine-readable code in a first size, and the one or more programs: while displaying the first machine-readable code at the first size, detecting a request to display the first machine-readable code at a larger size; 2. The computer system of claim 1, further comprising instructions for: in response to detecting the request to display the first machine-readable code at a larger size, displaying the first machine-readable code at a second size larger than the first size.

8. the first machine-readable code being a first type of machine-readable code, and the one or more programs comprising: detecting a request to display a first machine-readable code of a second type while displaying the first machine-readable code of the first type; 2. The computer system of claim 1, further comprising instructions for: in response to detecting the request to display the first machine-readable code of the second type, displaying the first machine-readable code of the second type.

9. The computer system of claim 1 , wherein displaying the first user interface comprises displaying one or more offers associated with the account.

10. 1. 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 in communication with a display generating component and one or more input devices, the one or more programs comprising: displaying, via the display generation component, a first user interface including an indication of an account; receiving authentication data via the one or more input devices; In response to receiving the authentication data, displaying, via the display generation component, a first machine-readable code associated with the account in accordance with a determination that the authentication data satisfies an authentication criterion associated with the account; forgoing display of the first machine-readable code associated with the account in response to a determination that the authentication data does not satisfy the authentication criteria associated with the account; displaying the first machine readable code associated with the account; maintain a representation of the first machine-readable code associated with the account pursuant to a determination that second authentication data is received within a predetermined time and that the second authentication data satisfies the authentication criteria associated with the account; receiving a confirmation that the first machine-readable code was successfully used to access information associated with the account; in response to receiving the confirmation that the first machine readable code was successfully used to access information associated with the account, ceasing to display the first machine-readable code; displaying, via the display generation component, an indication that information associated with the account was successfully accessed; a non-transitory computer-readable storage medium comprising instructions for ceasing to display the first machine-readable code associated with the account in accordance with a determination that second authentication data is not received within the predetermined time or that the second authentication data does not meet the authentication criteria associated with the account.

11. 1. A method comprising:

1. A computer system in communication with a display generation component and one or more input devices, comprising: displaying, via the display generation component, a first user interface including an indication of an account; receiving authentication data via the one or more input devices; In response to receiving the authentication data, displaying, via the display generation component, a first machine-readable code associated with the account in accordance with a determination that the authentication data satisfies an authentication criterion associated with the account; forgoing display of the first machine-readable code associated with the account in response to a determination that the authentication data does not satisfy the authentication criteria associated with the account; displaying the first machine readable code associated with the account; maintain a representation of the first machine-readable code associated with the account pursuant to a determination that second authentication data is received within a predetermined time and that the second authentication data satisfies the authentication criteria associated with the account; receiving a confirmation that the first machine-readable code was successfully used to access information associated with the account; in response to receiving the confirmation that the first machine readable code was successfully used to access information associated with the account, ceasing to display the first machine-readable code; displaying, via the display generation component, an indication that information associated with the account was successfully accessed; ceasing to display the first machine-readable code associated with the account in accordance with a determination that second authentication data is not received within the predetermined time or that the second authentication data does not meet the authentication criteria associated with the account.

Images