Sharing or using a pass or account

Abstract

To provide a method and an interface that are faster and more efficient for sharing and using passes or accounts.SOLUTION: A method includes receiving a first input (1502), displaying an account user interface including a first visual representation of a first account in response to receiving the first input (1506), receiving a second input corresponding to selection of the first visual representation (1508), displaying, in response to receiving the second input, a readable portion of a machine-readable code corresponding to the first account in accordance with a determination that the first visual representation was displayed in response to a request to prepare an account (1512), and displaying information corresponding to the first account without displaying the readable portion of the machine-readable code in accordance with a determination that the first visual representation was displayed in response to a request to view information about the account (1514).SELECTED DRAWING: Figure 15

Description

Technical Field

[0001] (Cross-Reference to Related Applications) This application claims the benefit of U.S. Patent Application No. 17 / 030,260, filed September 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. Patent Application No. 17 / 030,259, filed September 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. Patent Application No. 17 / 030,257, filed September 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. Patent Application No. 17 / 030,256, filed September 23, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", U.S. Provisional Patent Application No. 63 / 041,996, filed June 21, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS", and U.S. Provisional Patent Application No. 63 / 032,504, filed May 29, 2020, entitled "SHARING AND USING PASSES OR ACCOUNTS". The entire contents of all of these 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 Art

[0003] Computer systems can be used to access information associated with a pass or an account. The information can then be used to provide goods or services to a user, for example, to gain entry to a venue or transfer funds. Typically, information associated with a pass or account is associated with a user of a computer system. Summary of the Invention

[0004] However, some techniques for using passwords or accounts with computer systems are generally cumbersome and inefficient. For example, some existing techniques offer limited options for sharing passwords with other users. In addition, some existing techniques use complex and time-consuming user interfaces that may involve pressing or keystrokeing multiple keys to use passwords or accounts. Existing techniques take more time than necessary, wasting both the user's time and the device's energy. This latter consideration is particularly important in battery-powered devices.

[0005] Therefore, this technology provides computer systems with faster and more efficient methods and interfaces for sharing and using paths or accounts. Such methods and interfaces optionally complement or replace other methods for using paths or accounts. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated computing devices, such methods and interfaces conserve power and extend the interval between battery charges.

[0006] Exemplary methods are disclosed herein. Exemplary methods include, in a computer system communicating with a display generating component and one or more input devices, displaying a first user interface via the display generating component that includes information about one or more paths associated with a service provider; receiving a request via one or more input devices while the first user interface is being displayed to add one or more paths to an account associated with a first user ID that provides access to services provided by the service provider; displaying a shared affordance via the display generating component after receiving the request to provide at least one of the one or more paths to an account associated with a second user ID; receiving user input via one or more input devices corresponding to a selection of the shared affordance; and in response to receiving user input corresponding to a selection of the shared affordance, initiating a process to provide at least one of the one or more paths to the account associated with the second user ID.

[0007] An exemplary non-temporary computer-readable storage medium is described herein. The exemplary non-temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a first user interface via the display generating component, which includes information about one or more paths associated with a service provider; receive a request via one or more input devices while displaying the first user interface to add one or more paths that provide access to services provided by a service provider to an account associated with a first user ID; after receiving the request, display a shared affordance via the display generating component to provide at least one of the one or more paths to an account associated with a second user ID; receive a user input via one or more input devices corresponding to a selection of the shared affordance; and, in response to receiving the user input corresponding to a selection of the shared affordance, initiate a process to provide at least one of the one or more paths 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 communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a first user interface via the display generating component, which includes information about one or more paths associated with a service provider; receive a request via one or more input devices while displaying the first user interface to add one or more paths that provide access to services provided by a service provider to an account associated with a first user ID; after receiving the request, display a shared affordance via the display generating component to provide at least one of the one or more paths to an account associated with a second user ID; receive a user input via one or more input devices corresponding to a selection of the shared affordance; and, in response to receiving the user input corresponding to a selection of the shared affordance, initiate a process to provide at least one of the one or more paths to the account associated with the second user ID.

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

[0010] An exemplary computer system comprises: a display generation component; one or more input devices; means for displaying a first user interface via the display generation component, which includes information about one or more paths associated with a service provider; means for receiving, via one or more input devices, a request to add one or more paths to an account associated with a first user ID that provide access to services provided by a service provider; means for displaying, via the display generation component, a shared affordance for providing at least one of the one or more paths to an account associated with a second user ID, after receiving the request; and means for receiving, via 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, a process for providing at least one of the one or more paths to an account associated with a second user ID.

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

[0012] An exemplary non-temporary computer-readable storage medium is described herein. The exemplary non-temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs include instructions for detecting that data corresponding to a first path has been provided by the computer system to a separate path reader terminal, and after detecting that data corresponding to a first path has been provided by the computer system to the path reader terminal, displaying an indication via the display generating component that data corresponding to a first path has been provided by the computer system to the path reader terminal, providing a prompt to a user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is available for provision by the computer system to the path reader terminal, and ceasing to provide a prompt to a user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is not available for provision by the computer system to the path 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 communicating with a display generating component and one or more input devices, the one or more programs include instructions that detect that data corresponding to a first path has been provided by the computer system to a separate path reader terminal, and after detecting that data corresponding to a first path has been provided by the computer system to the path reader terminal, display an indication via the display generating component that data corresponding to a first path has been provided by the computer system to the path reader terminal, provide a prompt to the user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is available for provision by the computer system to the path reader terminal, and cease providing a prompt to the user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is not available for provision by the computer system to the path 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 for storing one or more programs configured to be executed by the one or more processors, wherein one or more programs include instructions for detecting that data corresponding to a first path has been provided by the computer system to a separate path reader terminal, and after detecting that data corresponding to a first path has been provided by the computer system to the path reader terminal, displaying an indication via the display generating component that data corresponding to a first path has been provided by the computer system to the path reader terminal, providing a prompt to the user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is available for provision by the computer system to the path reader terminal, and ceasing to provide a prompt to the user to provide authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is not available for provision by the computer system to the path reader terminal.

[0015] An exemplary computer system includes a display generation 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 separate path reader terminal, means for displaying an indication via the display generation component that data corresponding to a first path has been provided by the computer system to the path reader terminal, after detecting that data corresponding to a first path has been provided by the computer system to the path reader terminal, means for providing a user a prompt to grant authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is available for provision by the computer system to the path reader terminal, and means for ceasing to provide a user a prompt to grant authorization for data corresponding to a second path to be provided by the computer system to the path reader terminal, in accordance with a determination that data corresponding to a second path is not available for provision by the computer system to the path reader terminal.

[0016] Exemplary methods are disclosed herein. Exemplary methods include, in a computer system communicating with a display generating component and one or more input devices, displaying a first user interface including an indication of an account via the display generating component; receiving authentication data via one or more input devices; displaying a first machine-readable code associated with an account via the display generating component in response to the receipt of the authentication data, according to a determination that the authentication data satisfies the authentication criteria associated with the account; and ceasing to display the first machine-readable code associated with an account, according to a determination that the authentication data does not satisfy the authentication criteria associated with the account.

[0017] An exemplary non-temporary computer-readable storage medium is described herein. The exemplary non-temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a first user interface including an indication of an account via the display generating component, to receive authentication data via one or more input devices, and, in response to receiving the authentication data, to display a first machine-readable code associated with an account via the display generating component in accordance with a determination that the authentication data satisfies the authentication criteria associated with the account, and to stop displaying the first machine-readable code associated with an account in accordance with a determination that the authentication data does not satisfy the authentication criteria 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 communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a first user interface including an indication of an account via the display generating component, to receive authentication data via one or more input devices, and, in response to receiving the authentication data, to display a first machine-readable code associated with an account via the display generating component according to a determination that the authentication data satisfies the authentication criteria associated with the account, and to stop displaying the first machine-readable code associated with an account according to a determination that the authentication data does not satisfy the authentication criteria associated with the account.

[0019] 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 for storing one or more programs configured to be executed by the one or more processors, wherein one or more programs include instructions for displaying a first user interface including an indication of an account via the display generating component, receiving authentication data via one or more input devices, and, in response to receiving the authentication data, displaying a first machine-readable code associated with an account via the display generating component according to a determination that the authentication data satisfies the authentication criteria associated with the account, and ceasing to display the first machine-readable code associated with an account according to a determination that the authentication data does not satisfy the authentication criteria associated with the account.

[0020] An exemplary computer system comprises a display generation component, one or more input devices, means for displaying a first user interface including an account indication via the display generation component, means for receiving authentication data via one or more input devices, means for displaying a first machine-readable code associated with an account via the display generation component in accordance with a determination that the authentication data satisfies the authentication criteria associated with the account, and means for stopping the display of the first machine-readable code associated with an account in accordance with a determination that the authentication data does not satisfy the authentication criteria associated with the account.

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

[0022] An exemplary non-temporary computer-readable storage medium is described herein. The exemplary non-temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs display an account user interface via the display generating component, which includes multiple visual representations of multiple different accounts, and while displaying the account user interface, receive scroll inputs via one or more input devices corresponding to requests to scroll the account user interface, and in response to receiving scroll inputs, scroll the account user interface via the display generating component to display a first visual representation of a first account The instructions include scrolling the representation and the second visual representation of the second account, and after receiving scroll input, 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 includes criteria that are satisfied when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing the visual emphasis of the second visual representation of the second account to the visual emphasis of the first visual representation of the first account, and reducing the visual emphasis of the first visual representation of the first account to the 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 a set of selection criteria.

[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 communicating with a display generating component and one or more input devices, the one or more programs display an account user interface via the display generating component, which includes multiple visual representations of multiple different accounts, and while displaying the account user interface, it receives scroll inputs via one or more input devices corresponding to requests to scroll the account user interface, and in response to receiving scroll inputs, it scrolls the account user interface via the display generating component to a first visual representation of a first account The instructions include scrolling the current and second visual representations of the second account, and after receiving scroll input, while displaying the account user interface, the instructions include, according to a determination that the first visual representation of the first account satisfies a set of selection criteria, the set of selection criteria includes criteria that are satisfied when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing the visual emphasis of the second visual representation of the second account to the visual emphasis of the first visual representation of the first account, and according to a determination that the second visual representation of the second account satisfies a set of selection criteria, reducing the visual emphasis of the first visual representation of the first account to the visual emphasis of the second visual representation of the second account.

[0024] 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 for storing one or more programs configured to be executed by one or more processors, wherein one or more programs display an account user interface via a display device, which includes multiple visual representations of multiple different accounts, and while displaying the account user interface, receive scroll inputs via one or more input devices corresponding to requests to scroll the account user interface, and in response to receiving scroll inputs, scroll the account user interface via the display generating component to display a first visual representation of a first account The instructions include scrolling the representation and the second visual representation of the second account, and after receiving scroll input, 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 includes criteria that are satisfied when the first visual representation of the first account is displayed in the selection area for at least a threshold time, reducing the visual emphasis of the second visual representation of the second account to the visual emphasis of the first visual representation of the first account, and reducing the visual emphasis of the first visual representation of the first account to the 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 a set of selection criteria.

[0025] An exemplary computer system comprises a display generation component, one or more input devices, means for displaying an account user interface including multiple visual representations of multiple different accounts via the display generation component, means for receiving scroll inputs via one or more input devices while the account user interface is being displayed, corresponding to a request to scroll the account user interface, means for scrolling the account user interface via the display generation component in response to receiving scroll inputs, causing the first visual representation of a first account and the second visual representation of a second account to scroll, and means for, after receiving scroll inputs and while the account user interface is being displayed, according to a determination that the first visual representation of a first account satisfies a set of selection criteria, the set of selection criteria including criteria that are satisfied when the first visual representation of a first account is displayed in a selection area for at least a threshold time, reducing the visual emphasis of the second visual representation of a second account to the visual emphasis of the first visual representation of a first account, and according to a determination that the second visual representation of a second account satisfies a set of selection criteria, reducing the visual emphasis of the first visual representation of a first account to the visual emphasis of the second visual representation of a second account.

[0026] Exemplary methods are disclosed herein. An exemplary method includes, in a computer system communicating with a display generation component and one or more input devices, receiving a first input via one or more input devices; displaying an account user interface including a first visual representation of a first account via the display generation component in response to receiving the first input; receiving a second input via one or more input devices corresponding to a selection of the first visual representation of the first account while the first visual representation of the first account is being displayed; displaying a readable portion of machine-readable code corresponding to the first account via the display generation component in response to receiving the second input corresponding to a selection of the first visual representation of 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 one or more accounts from the account user interface for use; and displaying information corresponding to the first account via the display generation component without displaying 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 view information about one or more accounts without preparing one or more accounts from the account user interface for use.

[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 generation component and one or more input devices, the one or more programs comprising instructions that: receive a first input via the one or more input devices; in response to receiving the first input, display an account user interface including a first visual representation of a first account via the display generation component; while displaying the first visual representation of the first account, receive a second input corresponding to selection of the first visual representation of the first account via the one or more input devices; and in response to receiving the second input corresponding to selection of the first visual representation of 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 one or more accounts from the account user interface for use, display a readable portion of a machine-readable code corresponding to the first account via the display generation component, and in accordance with a determination that the first visual representation of the first account was displayed in response to a request to browse information about one or more accounts without preparing one or more accounts from the account user interface for use, display information corresponding to the first account via the display generation component without displaying a readable portion of a machine-readable code corresponding to the first account.

[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 communicating with a display generating component and one or more input devices, the one or more programs receiving a first input via one or more input devices, and in response to receiving the first input, displaying an account user interface via the display generating component, which includes a first visual representation of a first account, and while displaying the first visual representation of a first account, receiving a second input via one or more input devices corresponding to a selection of the first visual representation of a first account, and the second input corresponding to a selection of the first visual representation of a first account The command includes, in response to receiving power, displaying a readable portion of machine-readable code corresponding to the first account via a display generating component, in accordance with the determination that the first visual representation of the first account was displayed in response to a request to prepare one or more accounts from the account user interface for use, and displaying information corresponding to the first account via a display generating component without displaying a readable portion of machine-readable code corresponding to the first account, in accordance with the determination that the first visual representation of the first account was displayed in response to a request to view information about one or more accounts without preparing one or more accounts from the account user interface for use.

[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 including instructions for: 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 a first account; while displaying the first visual representation of the first account, receiving a second input corresponding to selection of the first visual representation of the first account via the one or more input devices; in response to receiving the second input corresponding to selection of the first visual representation of 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 one or more accounts from the account user interface for use, displaying, via the display generation component, a readable portion of a machine-readable code corresponding to the first account; and 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 one or more accounts without preparing one or more accounts from the account user interface for use, displaying information corresponding to the first account without displaying, via the display generation component, a readable portion of a machine-readable code corresponding to the first account.

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

[0031] An exemplary method is disclosed herein. The exemplary method includes, in a computer system communicating with a display generation component and one or more input devices, displaying a search user interface via the display generation component; receiving input containing a search term via one or more input devices while the search user interface is being displayed; and, in response to receiving input containing a search term, simultaneously displaying a plurality of search results via the display generation component, selected using the search term, which include a first search result corresponding to resource transfer activity of a first account among the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account among the plurality of transfer accounts, different from the first account.

[0032] An exemplary non-temporary computer-readable storage medium is described herein. The exemplary non-temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a search user interface via the display generating component, receive input containing a search term via one or more input devices while the search user interface is being displayed, and, in response to receiving input containing a search term, display via the display generating component, a plurality of search results selected using the search term, which include a first search result corresponding to resource transfer activity of a first account among the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account among 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 communicating with a display generating component and one or more input devices, the one or more programs including instructions to display a search user interface via the display generating component, receive input containing a search term via one or more input devices while the search user interface is being displayed, and, in response to receiving input containing a search term, display via the display generating component, a plurality of search results selected using the search term, which include a first search result corresponding to resource transfer activity of a first account among the plurality of transfer accounts and a second search result corresponding to resource transfer activity of a second account among 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 for storing one or more programs configured to be executed by one or more processors, wherein one or more programs include instructions for displaying a search user interface via a display device, receiving input containing a search term via one or more input devices while displaying the search user interface, and, in response to receiving input containing a search term, displaying a plurality of search results via the display generating component, according to a determination that the search user interface corresponds to a plurality of transfer accounts supplied to the computer system and is configured to transfer resources for each transfer account upon user authorization, 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 among the plurality of transfer accounts, and a second search result corresponding to resource transfer activity of a second account among 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, means for displaying a search user interface via the display devices, means for receiving input containing a search term via one or more input devices while the search user interface is being displayed, and means for simultaneously displaying a plurality of search results selected using the search term via the display generation component, in response to receiving input containing a search term, according to a determination that the search user interface corresponds to a plurality of transfer accounts supplied to the computer system and is configured to transfer resources for each transfer account upon user authorization, the search user interface includes a first search result corresponding to resource transfer activity of a first account among the plurality of transfer accounts, and a second search result corresponding to resource transfer activity of a second account among the plurality of transfer accounts that is different from the first account.

[0036] The executable instructions that perform these functions are optionally contained within a non-temporary computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0037] As a result, devices are provided 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 can complement or replace other methods for sharing and using passes and accounts. [Brief explanation of the drawing]

[0038] To better understand the various embodiments described, the following “Modes for Carrying Out the Invention” should be referenced in conjunction with the following drawings, and similar reference numbers throughout the following drawings refer to the corresponding parts.

[0039] [Figure 1A] This is a block diagram showing a portable multifunctional device with a touch-sensitive display, according to several embodiments.

[0040] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0041] [Figure 2] This figure shows a portable multifunctional device having a touchscreen, according to several embodiments.

[0042] [Figure 3]This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, according to several embodiments.

[0043] [Figure 4A] The following are exemplary user interfaces for application menus on a portable multifunction device, according to several embodiments.

[0044] [Figure 4B] This document illustrates an exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display, according to several embodiments.

[0045] [Figure 5A] A personal electronic device according to several embodiments is shown.

[0046] [Figure 5B] This is a block diagram showing a personal electronic device according to several embodiments.

[0047] [Figure 6A] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments. [Figure 6B] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments. [Figure 6C] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments. [Figure 6D] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments. [Figure 6E] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments. [Figure 6F] This figure shows an exemplary user interface for sharing one or more paths, according to several embodiments.

[0048] [Figure 7] A flowchart illustrating a method for sharing one or more paths, according to some embodiments.

[0049] [Figure 8A] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments. [Figure 8B] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments. [Figure 8C] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments. [Figure 8D] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments. [Figure 8E] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments. [Figure 8F] This figure shows an exemplary user interface for providing a user with a prompt to grant authorization, according to several embodiments.

[0050] [Figure 9] This flowchart illustrates a method for providing a user with a prompt to grant authorization, according to several embodiments.

[0051] [Figure 10A] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10B] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10C]The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10D] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10E] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10F] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10G] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10H] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10I] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10J] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10K] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments. [Figure 10L] The following are exemplary user interfaces for displaying machine-readable codes according to several embodiments.

[0052] [Figure 11] This flowchart illustrates a method for displaying machine-readable code according to several embodiments.

[0053] [Figure 12A] The following are exemplary user interfaces for displaying computer storage accounts, according to several embodiments. [Figure 12B]The following are exemplary user interfaces for displaying computer storage accounts, according to several embodiments. [Figure 12C] The following are exemplary user interfaces for displaying computer storage accounts, according to several embodiments.

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

[0055] [Figure 14] This flowchart illustrates a method for displaying a transfer account according to several embodiments.

[0056] [Figure 15] This flowchart illustrates a method for authorizing a transfer account according to several embodiments.

[0057] [Figure 16A] This figure shows an exemplary user interface for searching one or more computer storage accounts, according to several embodiments. [Figure 16B] This figure shows an exemplary user interface for searching one or more computer storage accounts, according to several embodiments. [Figure 16C] This figure shows an exemplary user interface for searching one or more computer storage accounts, according to several embodiments.

[0058] [Figure 17A]This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17B] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17C] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17D] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17E] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17F] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17G] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17H] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17I] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17J] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17K] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17L]This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17M] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments. [Figure 17N] This figure shows an exemplary user interface for searching for one or more transfer storage accounts, according to several embodiments.

[0059] [Figure 18] This flowchart illustrates a method for locating one or more transfer storage accounts according to several embodiments. [Modes for carrying out the invention]

[0060] The following description includes exemplary methods, parameters, etc. However, it should be noted that such descriptions are not intended to limit the scope of this disclosure, but rather are provided as descriptions of exemplary embodiments.

[0061] There is a need for electronic devices that provide efficient methods and interfaces for sharing and using passes or accounts. For example, when one or more passes are received, the user needs to be able to easily and efficiently provide one or more passes to a second user. Another example is when one or more passes are in use, the user needs to be able to easily and efficiently provide the data corresponding to the passes to a pass reader terminal. Another example is when using an account for a transaction, the user needs to be able to easily and efficiently provide the machine-readable code associated with the account to execute the transaction. Such technology can reduce the cognitive burden on users using or sharing passes or accounts, thereby increasing productivity. Furthermore, such technology can reduce the processor and battery power that would normally be wasted on redundant user input.

[0062] Figures 1A-1B, 2, 3, 4A-4B, and 5A-5B below illustrate exemplary devices that perform techniques for sharing and using paths or accounts. Figures 6A-6F show exemplary user interfaces for sharing one or more paths according to several embodiments. Figure 7 is a flowchart showing a method for sharing one or more paths according to some embodiments. The user interfaces in Figures 6A-6F are used to illustrate processes described later, including the process in Figure 7. Figures 8A-8F show exemplary user interfaces for providing a user with a prompt to grant authorization according to several embodiments. Figure 9 is a flowchart showing a method for providing a user with a prompt to grant authorization according to several embodiments. The user interfaces in Figures 8A-8F are used to illustrate processes described later, including the process in Figure 9. Figures 10A-10L show exemplary user interfaces for displaying machine-readable code according to several embodiments. Figure 11 is a flowchart showing an exemplary method for displaying machine-readable code according to several embodiments. The user interfaces in Figures 10A to 10L are used to illustrate the processes described below, including the process in Figure 11. Figures 12A to 12C show exemplary user interfaces for displaying computer storage accounts according to several embodiments. Figures 13A to 13AA show exemplary user interfaces for displaying and authorizing transfer accounts according to several embodiments. Figure 14 is a flowchart showing a method for displaying transfer accounts according to several embodiments. Figure 15 is a flowchart showing a method for authorizing transfer accounts according to several embodiments. The user interfaces in Figures 12A to 12C and Figures 13A to 13AA are used to illustrate the processes described later, including the processes in Figures 14 and 15. Figures 16A to 16C show exemplary user interfaces for retrieving one or more computer storage accounts according to several embodiments.Figures 17A to 17N show exemplary user interfaces for retrieving one or more transfer accounts according to several embodiments. Figure 18 is a flowchart illustrating a method for retrieving one or more transfer accounts. The user interfaces in Figures 16A to 16C and 17A to 17N are used to illustrate the processes described below, including the process in Figure 18.

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

[0064] In the following description, terms such as “first,” “second,” etc., are used to describe various elements, but these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, the first touch may be called the second touch, and similarly, the second touch may be called the first touch. Both the first touch and the second touch are touches, but they are not the same touch.

[0065] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and is not intended to be limiting. In the descriptions of the various embodiments and the accompanying claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless otherwise explicitly stated in the context. Furthermore, it should 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 enumerated items relating to the description. It will be further understood that, as used herein, the terms “includes,” “comprises,” and / or “comprising” specify the presence of the described features, integers, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof.

[0066] The phrase "if" can be interpreted, at will, depending on the context, as "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" can be interpreted, at will, depending on the context, as "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, which also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, California. Optionally, other portable electronic devices such as laptop computers or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or 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 touchpad). In some embodiments, the electronic device is a computer system communicating (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 component is separate from the computer system. As used herein, "display" content includes displaying content (e.g., video data rendered or decoded by the display controller 156) by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component in order to visually generate the content.

[0068] The following discussion describes electronic devices including displays and touch-sensitive surfaces. However, it should be understood that electronic devices optionally include one or more other physical user interface devices such as physical keyboards, mice, and / or joysticks.

[0069] The device typically supports a variety of applications, including drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone 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] Various applications running on this device optionally utilize at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or modified on an application-by-application basis and / or within individual applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports a variety of applications with intuitive and transparent user interfaces for the user.

[0071] Here, we turn our attention to embodiments of portable devices having a touch-sensitive display. Figure 1A is a block diagram of a portable multifunction device 100 having a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 may be conveniently referred to as a “touchscreen” and may be known or referred to as a “touch-sensitive display system”. Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 (e.g., touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100) for detecting the intensity of contact on Device 100. Device 100 optionally includes one or more tactile output generators 167 that generate tactile outputs on Device 100 (for example, on touch-sensitive surfaces such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0072] As used herein and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact on the touch-sensitive surface (e.g., finger contact), or a proxy for the force or pressure of contact on the touch-sensitive surface. The strength of contact has a range of values, including at least four distinct values, and more typically, including several hundred (e.g., at least 256) distinct values. The strength of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces 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 contact. Similarly, the 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 variation of the contact area detected on the touch-sensing surface, the capacitance and / or variation of the touch-sensing surface adjacent to the contact, and / or the resistance and / or variation of the touch-sensing surface adjacent to the contact may optionally be used as a substitute for the force or pressure of the contact on the touch-sensing surface. In some implementations, the substitute measurement of the contact force or pressure is used directly to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement of the contact force or pressure is converted into an estimate of the force or pressure, which is then used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of contact as an attribute of user input, it becomes possible for users to access additional device functions that might otherwise be inaccessible (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 control such as a knob or button) on reduced-size devices where the implementation area for displaying affordances is limited.

[0073] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, 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, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their 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 the physical properties 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) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s action. As another example, movement of a touch-sensitive surface may be interpreted or perceived by the user as "roughness" of that surface, even if there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the user's personal sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.

[0074] It should be understood that device 100 is merely an example of a portable multifunction device, and that device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in Figure 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. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

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

[0077] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 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 circuit 108 optionally includes well-known circuits for performing these functions, which include, but are not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, and memory. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. The RF circuit 108 optionally includes a well-known circuit for detecting a near-field communication (NFC) field using a short-range communication radio. Wireless communication is not limited to this, but optionally includes 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-HSPADA), and long-term evolution.Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, Email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant messaging (e.g., Extensible Messaging and Presence Protocol) Using any of several communication standards, protocols, and technologies, including the XMPP protocol, the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this specification.

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

[0079] The I / O subsystem 106 connects input / output peripherals on device 100, such as the touchscreen 112 and other input control devices 116, to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical 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. One or more input controllers 160 receive electrical signals from / transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some embodiments, one or more input controllers 160 are optionally connected to (or not connected to) one of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., 208 in Figure 2) optionally include up / down buttons for volume control of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in Figure 2). In some embodiments, the electronic device is a computer system communicating with one or more input devices (e.g., via wireless communication over wired communication). In some embodiments, one or more input devices include a touch-sensitive surface (e.g., a trackpad as part of a touch-sensitive display). In some embodiments, 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), for example, to track user gestures (e.g., hand gestures) as input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system.

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

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

[0082] The touchscreen 112 has a touch-sensing surface, sensor, or set of sensors that accept user input based on touch and / or tactile contact. The touchscreen 112 and the display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of contact) on the touchscreen 112 and translate the detected contact into interaction with user interface objects displayed on the touchscreen 112 (e.g., one or more soft keys, icons, web pages, or images). In an exemplary embodiment, the point of contact between the touchscreen 112 and the user corresponds to the user's finger.

[0083] The touchscreen 112 optionally uses LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies may also be used in other embodiments. The touchscreen 112 and the display controller 156 optionally, but not limited to, use any of a number of currently known or future-developed touch sensing technologies, including capacitive, resistive, infrared, and surface acoustic technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with the touchscreen 112, to detect contact and any movement or interruption thereof. In exemplary embodiments, projected mutual capacitive sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

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

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

[0086] The touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user optionally touches the touchscreen 112 using any suitable object or attachment such as a stylus or finger. In some embodiments, the user interface is designed to operate primarily using finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​the finger on the touchscreen. In some embodiments, the device translates coarse finger input into a precise pointer / cursor position or command to perform an action desired by the user.

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

[0088] Device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with generating, managing, and distributing power within the portable device.

[0089] The device 100 also optionally includes one or more optical sensors 164. Figure 1A shows optical sensors coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensors 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensors 164 receive light from the environment projected through one or more lenses and convert that light into data representing an image. The optical sensors 164 work in conjunction with an imaging module 143 (also called a camera module) to optionally capture still images or video. In some embodiments, the optical sensors are located on the back of the device 100, opposite the touchscreen display 112 which is on the front of the device, so that the touchscreen display can be used as a viewfinder for acquiring still images and / or video. In some embodiments, the optical sensors are located on the front of the device so that the user's image is optionally acquired for video conferencing while the user is viewing other video conference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (for example, by rotating the lens and sensor within the device housing), so that a single light sensor 164 can be used for both video conferencing and acquiring still images and / or videos, together with the touchscreen display.

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

[0091] Device 100 also optionally includes one or more contact intensity sensors 165. Figure 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, pressure-power sensors, optical force sensors, capacitive touch-sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch-sensing surface). The 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 positioned juxtaposed with or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112). In some embodiments, at least one contact intensity sensor is positioned on the back of Device 100, opposite the touchscreen display 112 located on the front of Device 100.

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

[0093] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component, and / or electromechanical devices that convert energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). The contact intensity sensor 165 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by the user of device 100. In some embodiments, at least one tactile output generator is positioned alongside or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or horizontally (e.g., forward / backward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is positioned on the back of device 100, opposite the touchscreen display 112 which is positioned on the front of device 100.

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

[0095] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a contact / 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 an application (or instruction set) 136. Furthermore, in some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) stores a device / global internal state 157, as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active, if there is an application currently active; a display state indicating which applications, views, or other information occupy different areas of the touchscreen display 112; a sensor state including information obtained from various sensors and input control devices 116 of the device; and location information relating to the device's position and / or orientation.

[0096] An operating system 126 (for example, an embedded operating system such as Darwin, RTXC, LINUX, UNIX®, OS X®, iOS, WINDOWS®, or 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 components and software components.

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

[0098] The contact / motion module 130 optionally detects contact with the touchscreen 112 and other touch-sensitive devices (e.g., a touchpad or physical click wheel) (in cooperation with the display controller 156). The contact / motion module 130 includes various software components for performing various contact detection operations, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more events of a finger dragging), and determining whether contact has stopped (e.g., detecting a finger up event or interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, represented by a 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 point. These actions can be optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the 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 (for example, to determine whether a user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to a software parameter (for example, the intensity thresholds can be adjusted without modifying the physical hardware of device 100, rather than being determined by the activation threshold of a particular physical actuator). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to one of a range of default thresholds without modifying the trackpad or touchscreen display hardware. In addition, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (for example, by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using a system-level click "intensity" parameter).

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

[0101] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for changing the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). In this specification, the term “graphics” includes, but is not limited to, any object that can be displayed to the user, including characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

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

[0104] The text input module 134 is optionally a component of the 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 applications that require text input).

[0105] The GPS module 135 determines the device's location and provides this information for use within various applications (for example, 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 weather widgets, local yellow pages widgets, and map / navigation widgets).

[0106] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof: ● Contact module 137 (sometimes called the address book or contact list), ●Telephone module 138, ●Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ●Training support module 142, ● 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, ●Optionally, a widget module 149 may include one or more of the following: weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, other widgets obtained by the user, and user-created widgets 149-6. ●Widget creator module 150 for creating user-created widget 149-6, ●Search module 151, ●Video and music player module 152, which 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 that may be 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, speech recognition, and speech duplication.

[0108] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the contact module 137 is used to manage an address book or contact list (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including optionally adding names(s) to the address book, deleting names(s) from the address book, associating telephone numbers(s) or email addresses(s) or other information with names, associating images with names, categorizing and sorting names, and providing telephone numbers or email addresses to initiate and / or facilitate communication via telephone 138, video conferencing module 139, email 140, or IM 141.

[0109] The telephone module 138 works in conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to optionally input character sequences corresponding to telephone numbers, access one or more telephone numbers in the contact module 137, modify entered telephone numbers, dial individual telephone numbers, make calls, and disconnect and terminate calls at the end of a call. As previously mentioned, wireless communication may optionally use any of several communication standards, protocols, and technologies.

[0110] The video conferencing module 139 works in conjunction with an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, a touchscreen 112, a display controller 156, a light sensor 164, a light sensor controller 158, a contact / motion module 130, a graphics module 132, a text input module 134, a contact module 137, and a telephone module 138 to include executable commands for starting, running, and ending video conferences between the user and one or more other participants, according to the user's instructions.

[0111] The email client module 140, in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, includes executable commands for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it extremely easy to create and send emails containing still or video images captured by the camera module 143.

[0112] The instant messaging module 141, in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, includes executable commands for inputting 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 telephone-based instant messaging, or XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). In this specification, “instant messaging” refers to both telephone-based messaging (e.g., messages sent using SMS or MMS) and internet-based messaging (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0113] The training support module 142 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module to create training (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (sports devices), receive training sensor data, calibrate sensors used to monitor training, select and play music for training, and includes executable commands for displaying, storing, and transmitting training data.

[0114] The camera module 143 works in conjunction with the touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144 to include executable commands for capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

[0115] The image management module 144 works in conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143 to include executable commands for arranging, modifying (e.g., editing), or otherwise manipulating still images and / or videos, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing them.

[0116] The browser module 147, in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, includes executable commands for browsing the internet according to user instructions, including searching, linking, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0117] The calendar module 148 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147 to include executable commands for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar items, to-do lists, etc.) according to user instructions.

[0118] The widget module 149 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147 to optionally download and use 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) or mini-applications created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets®).

[0119] The widget creator module 150 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147 to be used by the user to optionally create widgets (for example, to turn a user-specified portion of a web page into a widget).

[0120] The search module 151 works in conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to include executable commands for searching for characters, music, sounds, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

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

[0122] The memo module 153 works in conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134 to include executable commands for creating and managing memos, to-do lists, etc., according to user instructions.

[0123] The map module 154 works in conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147 to optionally receive, display, modify, and store maps and map-related data (e.g., driving directions, data on shops and other points of interest in or near a specific location, and other location-based data) in accordance with user commands.

[0124] The online video module 155, in conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, includes instructions that enable the user to access, browse, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and perform other management of online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. For further information regarding online video applications, please refer to U.S. Provisional Patent Application No. 60 / 936,562, “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, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed December 31, 2007, the entire contents of which are incorporated herein by reference.

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

[0126] In some embodiments, device 100 is a device in which the operation of a default set of functions in the device is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

[0127] A default set of functions, which are performed only through the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu. 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] Figure 1B is a block diagram showing exemplary components for event processing according to several embodiments. In some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) includes an event sorting unit 170 (e.g., within the operating system 126) and individual applications 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

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

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

[0131] The event monitor 171 receives event information from the peripheral interface 118. The event information includes information about sub-events (for example, user touch as part of a multi-touch gesture on the touch-sensitive display 112). The peripheral interface 118 transmits information received from the I / O subsystem 106, or from sensors such as the proximity sensor 166, one or more accelerometers 168, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display 112 or the touch-sensitive surface.

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

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

[0134] The hit view determination module 172 provides a software procedure for determining where in one or more views a sub-event occurred when the touch-sensitive display 112 is displaying two or more views. A view consists of control devices and other elements that the user can see on the display.

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

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

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

[0138] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes the event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores event information acquired by individual event receiving units 182 in an event queue.

[0139] In some embodiments, the operating system 126 includes an event sorting unit 170. Alternatively, application 136-1 includes an event sorting unit 170. In yet another embodiment, the event sorting unit 170 is a standalone module or part of another module stored in memory 102, such as a contact / motion module 130.

[0140] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each containing instructions for handling touch events occurring within a separate view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, a separate application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 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 processing unit 190 includes one or more event data 179 received from a data update unit 176, an object update unit 177, a GUI update unit 178, and / or an event sorting unit 170. The event processing unit 190 optionally uses or calls the data update unit 176, the object update unit 177, or the GUI update unit 178 to update the application's internal state 192. Alternatively, one or more of the application views 191 include one or more individual event processing units 190. In some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included in an individual application view 191.

[0141] Each individual event recognition unit 180 receives event information (e.g., event data 179) from the event sorting unit 170 and identifies an event from the event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparison unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution commands 188 (optionally including sub-event distribution commands).

[0142] The event receiving unit 182 receives event information from the event sorting unit 170. The event information includes information about sub-events, such as touches or the movement of touches. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, an event includes the 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 called the device's orientation).

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

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

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

[0146] If an individual event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, the individual event recognition unit 180 enters an event impossible, event failed, or event terminated state, and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, those event recognition units continue to track and process the sub-events of the ongoing touch-based gesture.

[0147] In some embodiments, an individual event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate to the actively involved event recognition unit how the event distribution system should perform sub-event distribution. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognition units interact with each other, or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are distributed to various levels in the view hierarchy or program hierarchy.

[0148] In some embodiments, an individual event recognition unit 180 activates an event processing unit 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, the individual event recognition unit 180 delivers event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and delaying the sending of) sub-events to individual hit views. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with that flag captures the flag and executes a default process.

[0149] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event processing unit. Instead, the sub-event distribution command distributes event information to an event processing unit associated with a set of sub-events, or to an actively involved view. The event processing unit associated with the set of sub-events or the actively involved view receives the event information and executes a predetermined process.

[0150] In some embodiments, the data update unit 176 creates and updates data used in application 136-1. For example, the data update unit 176 updates telephone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, the object update unit 177 creates and updates objects used in application 136-1. For example, the object update unit 177 creates new user interface objects or updates the position of user interface objects. The GUI update unit 178 updates the GUI. For example, the GUI update unit 178 prepares display information and sends it to graphics module 132 for display on touch-sensitive display.

[0151] In some embodiments, the event processing unit(s) 190 includes or has access to a data update unit 176, an object update unit 177, and a GUI update unit 178. In some embodiments, the data update unit 176, the object update unit 177, and the GUI update unit 178 are contained in a single module of an individual application 136-1 or application view 191. In other embodiments, they are contained in two or more software modules.

[0152] The foregoing description regarding the handling of user touch events on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it should be understood that not all of these begin on the touchscreen. For example, mouse movement and mouse button presses, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the events to be recognized.

[0153] Figure 2 shows a portable multifunction device 100 having a touchscreen 112 according to several embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, and in other embodiments described below, the user can select one or more of the graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with that one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and / or downward) and / or rolling (from right to left, left to right, upward and / or downward) with a finger in contact with the device 100. In some implementations or situations, accidental contact with a graphic does not constitute a selection of that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon does not arbitrarily select the corresponding application.

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

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

[0156] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments. Device 300 does not need to be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), game system, or 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. The communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 including a display 340, the display 340 is typically a touchscreen display. The 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 that generates tactile output on device 300 (for example, similar to the tactile output generator 167 described above with reference to Figure 1A), and a sensor 359 (for example, light, acceleration, proximity, touch sensing, and / or a contact intensity sensor similar to the contact intensity sensor 165 described above with reference to Figure 1A). The 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. The memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, that are stored in memory 102 of the portable multifunction device 100 (Figure 1A). Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of the portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, whereas memory 102 of the portable multifunction device 100 (Figure 1A) optionally does not store these modules.

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

[0158] Next, we optionally turn our attention to an embodiment of a user interface implemented in, for example, a portable multi-functional device 100.

[0159] Figure 4A shows an exemplary user interface for an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. ● Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular signals and Wi-Fi signals 402, ●Time 404, ●Bluetooth indicator 405, ●Battery status indicator 406, ●Tray 408 containing icons for frequently used applications, as shown below. ○Optionally including an indicator 414 for the number of missed calls or voicemail messages, an icon 416 of the telephone module 138 labeled "Telephone", ○Optionally includes an indicator 410 for the number of unread emails, an icon 418 labeled "Mail", for the email client module 140. ○ Icon 420 of browser module 147, labeled "Browser", and ○ Icon 422 for the video and music player module 152, also known as the iPod (trademark of Apple Inc.) module 152, which is labeled "iPod", and ● Icons of other applications, such as the following: ○ Icon 424 of IM module 141, labeled "Message" ○ Icon 426 of calendar module 148, labeled "Calendar" ○ Icon 428 of image management module 144, labeled "Photo" ○ Icon 430 of camera module 143, labeled "Camera" ○ Icon 432 of online video module 155, labeled "online video", ○ Icon 434 of stock price widget 149-2, labeled "Stock Price" ○ Icon 436 of map module 154, labeled "Map" ○ Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of the alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of training support module 142, labeled "Training Support" ○ Icon 444 of memo module 153, labeled as "Memo", and ○ An icon 446 labeled "Settings," which provides access to the settings of device 100 and its various applications 136, for a settings application or module.

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

[0161] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3) separate from the 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) for detecting the intensity of contact on the touch-sensitive surface 451, and / or one or more tactile output generators 357 for generating tactile output to the user of device 300.

[0162] Some of the following examples are given by referring to input on a touchscreen display 112 (a combination of a touch-sensing surface and a display), but in some embodiments, the device detects input on a touch-sensing surface separate from the display, as shown in Figure 4B. In some embodiments, the touch-sensing surface (e.g., 451 in Figure 4B) has a primary axis (e.g., 452 in Figure 4B) corresponding to a primary axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with the touch-sensing surface 451 (e.g., 460 and 462 in Figure 4B) at positions corresponding to each of the positions on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). In this way, user input (e.g., touches 460 and 462, and their movement) detected by the device on a touch-sensitive surface (e.g., 451 in Figure 4B) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B) when the touch-sensitive surface is separate from the display. It should be understood that a similar method may be optionally used for other user interfaces described herein.

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

[0164] Figure 5A shows an exemplary personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., Figures 1A to 4B). In some embodiments, device 500 has a touch-sensitive display screen 504, hereafter referred to as touchscreen 504. Alternatively, in addition to touchscreen 504, device 500 may have a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of the applied contact (e.g., touch). One or more intensity sensors on the touchscreen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to touches based on their intensity, meaning that touches of different intensity may invoke different user interface behaviors on device 500.

[0165] For example, see, for instance, International Patent Application PCT / US2013 / 040061, “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed 8 May 2013, published as International Publication WO / 2013 / 169849, and International Patent Application PCT / US2013 / 069483, “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed 11 November 2013, published as International Publication WO / 2014 / 105276.

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

[0167] Figure 5B shows an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described with respect to Figures 1A, 1B, and 3. The device 500 has a bus 512 that operably connects an I / O section 514 to one or more computer processors 516 and memory 518. The I / O section 514 may be connected to a display 504, which may 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 may 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 may include input mechanisms 506 and / or 508. The input mechanism 506 may optionally be, for example, a rotatable input device or a pressable and rotatable input device. In some embodiments, the input mechanism 508 may optionally be 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, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or a combination thereof, all of which can be operably connected to the I / O section 514.

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

[0170] As used herein, the term “affordance” refers to user-interactive graphical user interface objects that are optionally displayed on the display screens of devices 100, 300, and / or 500 (Figures 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.

[0171] As used herein, the term “focus selector” refers to an input element that indicates the current part of the user interface that the user is interacting with. In some implementations, including a cursor or other position marker, the cursor acts as a “focus selector,” and therefore, when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in Figure 3 or touch-sensitive surface 451 in Figure 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, including a touchscreen display that enables direct interaction with user interface elements on the touchscreen display (e.g., touch-sensitive display system 112 in Figure 1A or touchscreen 112 in Figure 4A), detected contact on the touchscreen acts as a “focus selector,” and therefore, when input (e.g., a press input by touch) 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 area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (for example, by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or touch on the touchscreen display) controlled by the user to communicate about the user's intended interaction with the user interface (for example, by pointing to the device the user interface element through which the user intends to interact).For example, the position of a focus selector (e.g., cursor, touch, or selection box) over an individual button while pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (rather than other user interface elements displayed on the device's display).

[0172] As used herein and in the claims, the term “characteristic intensity” of a contact refers to the characteristics of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a set of intensity samples collected over a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the top 10 percentile value of the contact intensity, the maximum half value of the contact intensity, the maximum 90 percent value of the contact intensity, and so on. In some embodiments, the duration of contact is used when determining characteristic intensity (for example, when characteristic intensity is the average intensity of contact over time). In some embodiments, characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action has been 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, contact with a characteristic intensity not exceeding the first threshold results in a first action, contact with a characteristic intensity above the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a characteristic intensity above the second threshold results in a third action. In some embodiments, the comparison between characteristic intensity and one or more thresholds is not used to determine whether a first action should be performed or a second action should be performed, but rather to determine whether one or more actions should be performed at all (for example, whether individual actions should be performed or whether individual actions should be postponed).

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

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

[0175] An increase in the characteristic intensity of contact from an intensity below a light pressure intensity threshold to an intensity between the light and deep pressure intensity thresholds is sometimes referred to as a "light pressure" input. An increase in the characteristic intensity of contact from an intensity below a deep pressure intensity threshold to an intensity above a deep pressure intensity threshold is sometimes referred to as a "deep pressure" input. An increase in the characteristic intensity of contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold is sometimes referred to as the detection of contact on the touch surface. A decrease in the characteristic intensity of contact from an intensity above a contact detection intensity threshold to an intensity below a contact detection intensity threshold is sometimes referred to the detection of contact lift-off 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 the detection of a gesture including an individual press input, or in response to the detection of an individual press input performed by an individual contact (or multiple contacts), wherein the individual press input is detected at least in part on the detection of an increase in the intensity of the contact (or multiple contacts) above a press input intensity threshold. In some embodiments, the individual action is performed in response to the detection of an increase in the intensity of the individual contact above a press input intensity threshold (e.g., a "downstroke" of the individual press input). In some embodiments, the press input includes an increase in the intensity of the individual contact above a press input intensity threshold, followed by a decrease in the intensity of the contact below the press input intensity threshold, and the individual action is performed in response to the detection of a subsequent decrease in the intensity of the individual contact below the press input threshold (e.g., an "upstroke" of the individual press input).

[0177] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, which may be referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship with a press input intensity threshold (for example, the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of an individual contact above the press input intensity threshold, followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and the individual action is performed in response to the detection of a subsequent decrease in the intensity of an individual contact below the hysteresis intensity threshold (for example, an “upstroke” of the individual press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a press input intensity threshold, and optionally a decrease in contact intensity to an intensity below the hysteresis intensity, and individual actions are performed in response to the detection of a press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the situation).

[0178] For the sake of clarity, the description of an action performed in response to a press input associated with a press input intensity threshold, or a gesture involving a press input, is optionally triggered in response to the detection of any of the following: an increase in contact intensity above the press input intensity threshold, an increase in contact intensity from below the hysteresis intensity threshold to above the press input intensity threshold, a decrease in contact intensity below the press input intensity threshold, and / or a decrease in contact intensity below the hysteresis intensity threshold corresponding to the press input intensity threshold. Furthermore, in examples where an action is described to be performed in response to the detection of a decrease in contact intensity below the press input intensity threshold, the action is optionally performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold.

[0179] Next, we will focus on embodiments of user interfaces ("UI") and related processes implemented on electronic devices such as portable multifunction device 100, device 300, or device 500.

[0180] Figures 6A to 6F show exemplary user interfaces for sharing one or more paths according to several embodiments. The user interfaces in these figures are used to illustrate processes described later, including the process in Figure 7.

[0181] Figure 6A shows a device 600a including a display 602a (e.g., a touchscreen display). In Figure 6A, the device 600a displays a user interface 604, which contains information about three paths associated with a service provider named Amusement World (e.g., Amusement Park). In some embodiments, the paths are digital paths containing data that can be transmitted (e.g., to a path reader terminal) for use or redemption. 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 membership). In some embodiments, the service provider is an entity (e.g., a company and / or a third party) different from the entity (e.g., a first party) that developed and / or provides the device 600a and / or the operating system running on the device 600a. In some embodiments, the 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 the 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 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). In the embodiment shown in Figure 6A, the pass provides access to a venue called Amusement World.

[0182] The user interface 604 includes an affordance 606, which, when selected, initiates a process to add the path to an account associated with a first user ID (e.g., an account associated with the user or owner of device 600a and used to sign 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 the developer of device 600a and / or the operating system running on device 600a. In Figure 6A, while displaying the user interface 604, device 600a receives (e.g., discovers) a request 603 to add the path shown in user interface 604a to an account associated with a first user ID. In the embodiment shown in Figure 6A, the request 603 includes selecting (e.g., tapping) the affordance 606.

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

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

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

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

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

[0188] In some embodiments, the shared affordance 612a is displayed after a path(s) (e.g., information corresponding to a path(s)) is added to the account associated with the first user ID. For example, the shared affordance 612a is not displayed in the user interface 608a in Figure 6B in response to receiving request 603 in Figure 6A, but is displayed in the user interface 608a in Figure 6C after the path(s) have been added to the account associated with the first user ID (e.g., in response to receiving the additional selection 605 for affordance 610a in Figure 6B).

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

[0190] In some embodiments, the representation of a path(s) (for example, in user interfaces 608a, 608b, and / or 618) is displayed with geometric transformation effects (e.g., skew effects, 3D effects, depth effects, and / or parallax effects). In some embodiments, the representation of a path(s) is a graphical animation (e.g., transitioning colors and / or transitioning shapes) that creates the illusion that the representation(s) 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 transformation 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 artwork (e.g., background)) based on a change in the orientation of the device relative to a reference point. In some embodiments, displaying geometric changes includes detecting changes in the orientation of the device relative to a fixed reference point on Earth (based on the device's orientation sensors, such as an accelerometer, gyroscope, and / or magnetometer). In some embodiments, displaying geometric change effects includes detecting changes in the user's orientation relative to the device (based on a face tracking sensor, such as a camera or other face tracking sensor, which can detect changes in the device's field of view by tracking the face of the device).

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

[0192] In Figure 6C, device 600a receives (e.g., detects) a user input 609 (e.g., a tap) corresponding to the selection of a shared affordance 612a. Upon receiving input 609, device 600a initiates a process to provide at least one pass to an account associated with a second user ID. In some embodiments, the account associated with the second user ID is a second account in a first-party wallet application associated with the second user (e.g., a family member's account). In the embodiment shown in Figure 6D, the process to provide at least one pass to an account associated with the second user ID includes displaying a user interface 614. In some embodiments, the user interface 614 includes a graphic element having the appearance of a card or sheet (e.g., displayed on its front) that overlaps with at least a portion of the 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 a path (e.g., text message, email, NFC, and / or a shared cloud storage account shared by a first user ID and a second user ID).

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

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

[0195] In some embodiments, a path(s) can be provided to another user ID by repeating some or all of the techniques described with reference to Figures 6A to 6D. For example, after a second user ID is selected in user interface 614 (e.g., depending on the selection) (or after a path(s) is provided to the account associated with the second user ID), device 600a displays user interface 608a as shown in Figure 6B if no path(s) have been added to device 600a, or optionally displays user interface 608a without termination affordance 632 as shown in Figure 6C if a path(s) have been added to device 600a. In some embodiments, two or more user IDs (e.g., Amy Appleseed and John Appleseed) can be selected within user interface 614, and in response to receiving the selection of two or more user IDs, device 600a provides a path(s) to the accounts associated with all of the selected user IDs. In some embodiments, a representation within the user interface 614 corresponds to a group of user IDs (e.g., two or more user IDs), and upon receiving a selection of such a representation, device 600a provides a pass(s) to the 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 received paths to the account associated with the selected user ID in response to receiving input 611. In some embodiments, in response to receiving input 611, device 600a provides one or more options (e.g., affordances) to select (e.g., display) which paths to provide to the account associated with the selected user ID. For example, device 600a may provide the ability to provide paths one at a time, or to provide one or two of three paths without providing all of them.

[0197] In the embodiments shown in Figures 6A to 6C, the shared affordance 612a is displayed as part of the process of adding a path to an account associated with the device 600a and / or a user ID associated with the device 600a. For example, a path is added to the device 600a in response to receiving the selection 605 of the additional affordance 610a in Figure 6B, before providing the path to an account associated with a second user ID. In some embodiments, one or more paths may be provided to an account associated with a second user ID before or without adding the path(s) to the device 600a. For example, the device 600a may receive (e.g., detect) an input 607 (e.g., a tap) corresponding to the selection of the shared affordance 612a, as shown in Figure 6B. In response to receiving the input 607, the device 600a initiates a process to provide at least one of the paths to an account associated with a second user ID as described above, with reference to Figure 6D, before or without adding the path(s) to the device 600a (e.g., the device 600a displays the user interface 614).

[0198] In some embodiments, after a path(s) has been shared, device 600a returns to the application or website (e.g., the source of the path(s)) that generated the path(s) or initiated the process to add the path(s) to the account associated with the first user ID. Depending on the selection of a second user ID, such as input 611 on representation 616, device 600a displays the user interface of the application corresponding to user interface 604 in Figure 6A (e.g., automatically, without further user input). (For example, device 600a launches, restarts, and / or switches to the third-party application or website of the service provider that was the source of the path(s) or initiated the process to add the path(s) associated with the first user ID.)

[0199] In some embodiments, a second user ID is associated with a first user ID (for example, the two user IDs are included in a family sharing account that allows users to share data such as photos, videos, passes, and / or access to other accounts). In some such embodiments, a pass is added to an account associated with a second user ID by providing the pass(s) to the account associated with the second user ID without requiring input into the computer system associated with the second user ID and / or without sending notifications or messages to the device associated with the second user ID (for example, the pass(s) appear in the second user ID's account without sending text messages, emails, and / or other notifications (for example, they appear in a wallet application logged into the second user ID's account)).

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

[0201] In some embodiments, the system authorizes each device to redeem a password by adding a password to the account and / or device(s) associated with a first or second user ID.

[0202] In some embodiments, an animation (e.g., spacecraft launch and / or gate opening) is displayed when a path(s) is redeemed or used (e.g., as described with reference to Figures 8C and 8E). For example, in some embodiments, device 600a detects a request (e.g., a request described with reference to Figures 8C and 8E) to provide data corresponding to a first path(s) of the path(s), and accordingly displays an animation associated with the first path indicating that the data corresponding to the first path has been successfully provided to the path reader 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 a plurality of intermediate states displayed as the transition from the initial state to the end state. In some embodiments, the animation is displayed in response to detection that data corresponding to the first path has been transmitted from a computer system. In some embodiments, the animation is displayed in response to receiving confirmation that data corresponding to the first path has been accepted by the path reader terminal.

[0203] In some embodiments, when a path(s) is used, device 600a and / or the path reader terminal generate (e.g., output) noise that is different from the inherent noise or noise that is generated when other events occur. In some embodiments, the noise includes sounds that correspond to custom art or animation (e.g., spaceship launch sounds and / or sounds associated with user-selected visual designs). For example, in some embodiments, device 600a detects a request to provide corresponding data to the path reader terminal and, accordingly, generates an audio notification corresponding to the path (e.g., by device 600a and / or the path reader terminal) (e.g., when a path is used, the user's device and / or the path reader terminal play sounds that correspond to the artwork on the path). In some embodiments, the audio notification is customized for the path (e.g., the notification is a specific audio output (e.g., sound effects) associated with the path that is different from alert notifications such as incoming calls, text messages and / or emails).

[0204] Returning to Figure 6D, representation 616 corresponds to an option to provide one or more paths to an account associated with a user ID associated with the user Amy Appleseed via text message, as indicated by a possible callout indication in the lower 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. Figure 6E shows an example of a user interface 618 of a messaging application displayed on the display 602b of a device 600b (e.g., Amy Appleseed's phone) associated with the selected user ID. The 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 selection of a user ID associated with device 600b in Figure 6D, the user interface 618 includes a graphical indication 620 of paths (e.g., in a message conversation) and affordances 622 for browsing shared paths (e.g., in a message conversation).

[0205] In Figure 6E, device 600b receives (e.g., detects) a request 613 (e.g., a tap on affordance 622) to view a shared path(s). In response to detecting input 613, device 600b displays user interface 608b, as shown in Figure 6F. In some embodiments, user interface 608b is the 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 Figure 6B. User interface 608b includes the shared affordance 612b, additional affordance 610b, representation 630b, and a prompt (e.g., simultaneously displayed) for adding a path(s) to an account associated with a first user ID. In some embodiments, the user interface 608b is displayed after receiving a pass(s) and in response to receiving a request to launch or open a wallet account application (e.g., a double press of a hardware button 635b on device 600b). For example, the option to add and / or share the received pass(s) may be displayed in the wallet application associated with the selected user ID without (or before) viewing the pass(s) representation 620 in the messaging application's user interface 618 or selecting an affordance 622.

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

[0207] Upon receiving the selection of the shared affordance 612b, device 600b initiates the process of sharing the path with another user ID (for example, the same or similar process described for device 600a with reference to Figures 6C-6D).

[0208] Figure 7 is a flowchart illustrating a method for sharing one or more paths according to several embodiments. Method 700 is performed in a computer system (e.g., 100, 300, 500, 600a) communicating with a display generation component (e.g., 602a) and one or more input devices (e.g., touch-sensing 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 accounts and paths associated with a second user ID. This method reduces the cognitive load on the user when sharing paths, thereby creating a more efficient human-machine interface. In the case of battery-powered computer systems, enabling users to share paths more quickly and efficiently saves power and extends the time between battery charges.

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

[0211] While the first user interface is being displayed, the computer system receives a request (e.g., 603, 605) via one or more input devices 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) (e.g., selection of the “Add to Wallet” affordance via a touch-sensitive surface) (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 a request (and optionally after adding information corresponding to one or more paths to the account associated with the first user ID (e.g., after adding information such that the paths can be redeemed from a wallet application)), the computer system provides, via a display generation component, a shared affordance (e.g., 612a) (e.g., displaying a selectable user interface object (706)) for providing at least one of the one or more paths to the account associated with the second user ID (e.g., a second account of a first-party wallet application associated with the second user) (e.g., a family account) (e.g., sending information representing a path and / or providing access to path information from a central server). 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 user input (e.g., 607, 609) (e.g., a tap gesture via a touch-sensitive surface on the shared affordance) corresponding to the selection of a shared affordance (e.g., 612a) via one or more input devices (708).

[0214] In response to receiving user input corresponding to the selection of a shared affordance, the computer system initiates the process of providing at least one of one or more paths to an account associated with a second user ID (710) (for example, adding information to the second account so that at least one path can be redeemed from the second user's wallet application). By providing paths to a second account associated with a second user ID in response to the selection of a shared affordance, the number of inputs required to add a path to the second account is reduced. By reducing the number of inputs required to perform the operation, the usability of the computer system is improved, the user system interface is made more efficient (for example, by helping the user to provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0215] In some embodiments, before initiating the process of providing at least one of one or more passes to an account associated with a second user ID, the second user ID is selected from a list of user IDs available to receive a shared pass (e.g., family and / or contacts in a contacts list) (e.g., selected from user interface 614). In some embodiments, the process of providing at least one of one or more passes to a second account associated with a 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 of providing at least one of one or more passes to a second account associated with a second user ID includes providing an indication (e.g., 620) (e.g., a text message) to a device associated with the second user ID where the pass has been added to the account associated with the second user ID (e.g., authorized to be redeemed by that account).

[0216] In some embodiments, displaying a first user interface (e.g., 604, 608a) includes displaying one or more path representations (e.g., 630a) accompanied by geometric change effects (e.g., skew effect, 3D effect, depth effect, parallax effect, and / or graphic animation) (e.g., color shift and / or shape shift) that create the illusion that one or more path representations (or parts thereof) are three-dimensional objects viewed from different angles as the angle (orientation) of the display generation components changes. In some embodiments, the geometric change 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 artwork (e.g., background)) based on a change in the orientation of the display generation components relative to a reference point. In some embodiments, displaying geometric change includes detecting a change in the orientation of the display generation components relative to a fixed reference point on Earth (e.g., based on orientation sensors of a computer system such as an accelerometer, gyroscope, and / or magnetometer). In some embodiments, displaying a geometric change effect includes detecting a change in the user's orientation relative to the display generation component (for example, based on a face tracking sensor such as a camera or other face tracking sensor that can detect changes in the device's field of view by the face being tracked by the device). By displaying a representation of one or more paths with a geometric change effect, the user is provided with visual feedback regarding the state of the display generation component and / or information about one or more paths, such as how many paths are available (for example, by showing the height of the simulated stack of paths as the orientation of the display generation component changes). Furthermore, displaying a geometric change effect as the orientation of the display generation component changes indicates to the user that the displayed paths are authentic and not a video that is displayed regardless of the orientation of the display generation component.By providing users with improved visual feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by helping users provide appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and device battery life is improved by enabling users to use the device more quickly and efficiently.

[0217] In some embodiments, upon receiving a request (e.g., 603, 605) to add one or more paths to an account associated with a first user ID, the computer system initiates a process to add one or more paths to a device (e.g., 600a) associated with the account associated with the first user ID (e.g., logged in). In some embodiments, the process to add one or more paths to a device associated with the account associated with the first user ID includes displaying a shared affordance (e.g., 612a) to provide at least one of the one or more paths to an account associated with a second user ID. By displaying the shared affordance to provide at least one of the one or more paths to an account associated with a second user ID as part of the process to add one or more paths to a device associated with the account associated with the first user ID, the user can efficiently share paths without having to provide additional input to navigate to an additional user interface. By reducing the number of inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0218] In some embodiments, upon receiving a request (e.g., 603, 605) to add one or more paths to an account associated with a first user ID, the computer system adds a first path from the one or more paths and a second path from the one or more paths different from the first path to the account associated with the first user ID (e.g., a single input on the “add path” affordance (e.g., 606, 610a) causes multiple paths to be added to the account). By adding the first and second paths to the account associated with the first user ID upon receiving a request to add one or more paths to an account associated with a first user ID, the user can efficiently add multiple paths to the account associated with the first user ID with a single input. This improves the usability of the computer system by reducing the number of inputs required to perform the operation, makes the user system interface more efficient (e.g., by helping the user to provide appropriate input when operating / interacting with the computer system and reducing user errors), and reduces power consumption and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0219] In some embodiments, a request to add one or more paths to an account associated with a first user ID (e.g., 603) does not add one or more paths to an account associated with a first user ID. By refraining from adding paths to an account associated with a first user ID, the user is able to share one or more paths with an account associated with a second user ID without adding paths to an account associated with a first user ID, and the user is given additional control over which account has the paths. By providing the user with additional control over the computer system, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0220] In some embodiments, the process for providing at least one of one or more paths to an account associated with a second user ID includes providing the account associated with the second user ID with a first path from the one or more paths and a second path different from the first path from the one or more paths. In some embodiments, the paths are sent to the account associated with the second user ID via text message (e.g., 620), and the second user is then given the option to add paths (e.g., 610b). In some embodiments, all paths within one or more paths 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 account associated with the second user ID with the first and second paths, the user can efficiently share multiple paths to the account associated with the second user ID with a single input. By reducing the number of inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0221] In some embodiments, a shared 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 a first user interface (e.g., 604) (e.g., a user interface for an application associated with a service provider). In some embodiments, upon receiving user input (e.g., 607, 609) corresponding to the selection of a shared affordance, the computer system displays the first user interface (e.g., automatically, without further user input). By displaying the first user interface upon receiving user input corresponding to the selection of a shared affordance, the user can return to the first user interface without additional input. This improves the usability of the computer system by reducing the number of inputs required to perform an operation, 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 reduces power consumption and improves the 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 a first user ID (e.g., the two users are included in a family shared account), and the process for providing at least one of one or more paths to an account associated with the second user ID adds at least one of one or more paths to the account associated with the second user ID without any input on the computer system associated with the second user ID (e.g., 600b) (e.g., the path appears in the second user's wallet without receiving a text message, and / or data is sent via a shared cloud storage account). By adding at least one of one or more paths to an account associated with the second user ID, the user is provided with additional control over which accounts have paths. By providing the user with additional control over the computer system, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0223] In some embodiments, the process for providing at least one of one or more paths to an account associated with a second user ID includes adding at least one of one or more paths to a first device (e.g., 600b) (e.g., a telephone) associated with the second user ID, and a second device (e.g., a watch) associated with the second user ID (e.g., authorizing the device to redeem). By adding at least one of one or more paths to the first device associated with the second user ID and the second device associated with the second user ID, a user can add paths to multiple devices with a single input. This improves the usability of the computer system by reducing the number of inputs required to perform an operation, 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 reduces power consumption and improves the 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 input corresponding to the selection of a visual design for one or more paths. In some embodiments, before receiving input corresponding to the selection of a visual design, the computer system detects a request to browse visual design options for one or more paths, and upon receiving input corresponding to the selection of a visual design for one or more paths, the computer system displays one or more paths according to the selected visual design (e.g., different artwork options that can be used as images on the paths, as shown in Figures 8A and 8D). In some embodiments, the data representing the visual design is provided to an account associated with a second user ID. By displaying one or more paths according to the selected visual design, the user can customize the appearance of the paths, thereby providing the user with visual feedback that the paths are associated with the user's account. By providing improved visual feedback, the usability of the computer system is improved, the user device interface becomes more efficient (e.g., by helping the user make appropriate inputs when operating / interacting with the computer system and reducing user errors), which further reduces the power consumption of the computer system and improves battery life 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 among one or more paths to a path reader terminal (e.g., 850 described with reference to FIGS. 8C and 8E), and in response to detecting the request to provide the data corresponding to the first path to the path reader terminal, the computer system displays, via a display generation component, an animation associated with the first path (e.g., as described with reference to FIGS. 8C and 8E) indicating that the data corresponding to the first path has been successfully provided to the path reader terminal (e.g., when the path is used, an animation (e.g., a change in expression on a character, launching of a spacecraft, and / or opening of a gate) is displayed). 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 a final state (e.g., a spacecraft in space and / or an opened gate), wherein a plurality of intermediate states are displayed while transitioning from the initial state to the final 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 confirmation that the data corresponding to the first path has been accepted by the path reader terminal. Displaying the animation associated with the first path provides a user with visual feedback confirming that the data corresponding to the first path has been successfully provided to the path reader terminal. Providing improved visual feedback enhances the operability of the computer system and makes the user device interface more efficient (e.g., by assisting the user in making correct inputs when operating or interacting with the computer system and reducing user errors), which in turn reduces power consumption of the computer system and improves battery life by allowing the user to use the device more quickly and efficiently.

[0226] In some embodiments, the computer system displays a representation of a first path among one or more paths (e.g., 630a, 630b, 806a as shown in Figures 8A-8C, and 806b as shown in Figures 8D and 8E) via a display generation component. In some embodiments, displaying a representation of the first path includes displaying an animation of at least one visual feature of the representation of the first path (e.g., stars on the path are animated to twinkle). In some embodiments, the animation includes displaying a plurality of intermediate states while transitioning from the initial state of the visual feature to the final state of the visual feature. By displaying an animation of at least one visual feature of the representation of the first path, the user is provided with visual feedback that the displayed representation of the first path corresponds to the true path (e.g., the displayed path is not a still image copied from another device). By providing users with improved visual feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by helping users provide appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and device battery life is improved by enabling users 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 among one or more paths to a path reader terminal (e.g., 850 shown in Figures 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 (e.g., by the computer system and / or the path reader terminal) generates 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 play a sound corresponding to the 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., sound effect) associated with the first path, distinct from alert notifications such as incoming calls, text messages, and / or emails). By generating 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 users with improved feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by helping users provide appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and device battery life is improved by enabling users to use the device more quickly and efficiently.

[0228] In some embodiments, the computer system provides (e.g., automatically, without further user input) at least one of a set of paths to an account associated with a second user ID. In some embodiments, at least one of a set of paths is provided to the second account associated with the second user ID in response to the initiation of a process for providing at least one of a set of paths to the second account associated with the second user ID. In some embodiments, at least one of a set of paths is provided to the second account associated with the second user ID in response to receiving user input (e.g., 607, 609) corresponding to a selection of shared affordances (e.g., 612a). In some embodiments, at least one of a set of paths 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 a set of paths to the second account associated with the second user ID. In some embodiments, upon receiving user input corresponding to a selection of a shared affordance, a process is initiated to provide at least one of one or more paths to a third account associated with a third user ID (for example, the selection of a shared affordance shares a path to two different users). In some embodiments, the second and third user IDs are selected from a list of user IDs available to receive a shared path (e.g., contacts in a family and / or contacts list) (e.g., selected from a user interface 614) before initiating the process to provide at least one of one or more paths to an account associated with a second user ID. By providing at least one of one or more paths to an account associated with a second user ID, at least one of one or more paths can be added to the account associated with the second user ID without additional user input.By reducing the number of user inputs required to perform an action, the operability of a computer system is improved, and (for example, by assisting a user to provide appropriate inputs and reducing user errors when operating the computer system / interacting with the computer system) the user-system interface is made more efficient. In addition, by enabling a user to use a computer system more quickly and efficiently, power consumption is reduced and the battery life of the computer system is improved.

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

[0230] FIGS. 8A to 8F illustrate an exemplary user interface that provides a user with a prompt for granting authorization according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in FIG. 9.

[0231] FIG. 8A shows 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 associated with a service provider (also referred to as pass 806a) (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, the user interface 804 is displayed in response to user input selecting a path 806a. In some embodiments, the user interface 804 is displayed in response to receiving (e.g., detecting) input (e.g., a double press of a hardware button 835). In some embodiments, the path 806a is displayed in response to user input causing a path reader (e.g., 850 shown in Figure 8C) to provide data for a first path.

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

[0234] Figure 8B shows one embodiment of the user interface 804 similar to the embodiment shown in Figure 8A, except that indication 808b is displayed (for example, 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 (for example, so that the user can see how many paths there are in the set).

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

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

[0237] In the embodiment shown in Figure 8C, the indication that data corresponding to path 806a has been provided to the path reader terminal 850 by device 800 includes displaying a checkmark icon (e.g., instead of the icon above the text “Hold Near Reader” in Figures 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 raising its right arm / hand) on path 806a. In some embodiments, after detecting that data corresponding to path 806a has been provided to the path reader terminal 850 by device 800 (e.g., accordingly), device 800 provides tactile and / or audible output, as indicated by the wavy lines around the corners of device 800 in Figure 8C. In some embodiments, after detecting that data corresponding to path 806a has been provided to the path reader terminal 850 by device 800 (e.g., accordingly), the path reader terminal 850 provides an indication (e.g., audible output and / or noise).

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

[0239] In some embodiments, path 806a and the second path are related to each other (for example, 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 (for example, they do not generate a prompt that data corresponding to the second path is available). In some embodiments, prompts are provided only for additional paths associated with path 806a.

[0240] In some embodiments, providing a prompt includes displaying an indication that data corresponding to at least a second path is available for the device 800 to provide to the path reader terminal 850 (e.g., displaying a paging dot, displaying a representation of the path stack, displaying a tap-screen command, displaying a swipe command, displaying a tilt-phone command, and / or displaying a portion of the second path along the edge of the display). In the embodiment shown in Figure 8C, the prompt includes displaying the text “Proceed to next path” and displaying an indication 808a (e.g., maintaining its display). In some embodiments, the prompt indicates the number of paths available for the device 800 to provide to the path reader terminal (e.g., a paging dot 808a and / or a representation of the path stack 808b). In some embodiments, providing a prompt includes outputting an audio notification that data corresponding to a second path is available for the device 800 to provide to the path reader terminal 850. In some embodiments, providing a 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 for the device 800 to provide to the path reader terminal 850.

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

[0242] Figure 8D shows device 800 displaying a representation 806b of the second path (also called path 806b). In Figure 8D, the central paging dot of paging dot 808a is highlighted and / or filled in compared to the left and right dots, and the correct dot indicates that path 806b is the second of three paths. Path 806b includes text indicating that path 806b is associated with a person (e.g., a guest named Pete and / or a different person from path 806a), and a service provider logo (e.g., a different logo, character, and / or mouse from path 806a). Similar to the user interface 804 in Figure 8A, the user interface 804 in Figure 8D prompts the user to hold device 800 near the path reader terminal (e.g., because path 806b has not been redeemed).

[0243] In some embodiments, device 800 displays path 806b (for example, as part of user interface 804 in Figure 8D) in response to receiving (e.g., detecting) input (e.g., after device 800 has provided a prompt to grant authorization to data corresponding to a second path to path reader terminal 850). In some embodiments, the input includes touch on display 802, movement of device 800, and / or biometric information (e.g., facial information, iris information, fingerprint information). In some embodiments, device 800 displays path 806b (for example, as part of user interface 804 in Figure 8D) in response to detecting input 803 shown in Figure 8C (e.g., a right-to-left swipe gesture on display 802). In some embodiments, device 800 displays path 806b (for example, as part of user interface 804 in Figure 8D) after detecting that data corresponding to path 806a has been provided by device 800 to path reader terminal 850 (for example, without needing to receive input 803) (for example, automatically, without receiving any further input, and / or as detected). In some embodiments, device 800 displays path 806b (for example, as part of user interface 804 in Figure 8D) in response to detecting movement of device 800 (for example, rising and / or descending of device 800, and / or rising and / or descending 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 can display path 806a in response to receiving input (a right-to-left swipe gesture while displaying path 806b) before (e.g., without providing) the data corresponding to path 806a to the path reader terminal 850, or before (e.g., without detecting) that the data corresponding to path 806a has been provided to the path reader terminal 850 by device 800.In some embodiments, in response to receiving input (e.g., a left-to-right swipe gesture on the display 802) while displaying path 806b (e.g., while displaying the user interface 804 as shown in Figure 8D), device 800 displays path 806a (e.g., device 800 displays the user interface 804 as shown in Figure 8C).

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

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

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

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

[0248] In some embodiments, pass 806a, pass 806b, and the third pass are associated with each other (e.g., all three passes provide access to the same event and / or same date / time at a service provider). In some embodiments, other passes for different events or different times / dates at the service provider are not used (e.g., do not trigger a prompt that data corresponding to the third pass is available). In some embodiments, the prompt is only provided for additional passes associated with pass 806b.

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

[0250] In some embodiments, in accordance with the determination that data corresponding to a third path is not available for the path reader terminal 850 to be provided by device 800, device 800 ceases to provide prompts for authorization of the data corresponding to the third path that is provided to the path reader terminal 850 by device 800. In some embodiments, in accordance with the determination that data corresponding to a third path is not available for the path reader terminal 850 to be provided by device 800, device 800 shuts down the display 802 (for example, the display 802 is turned off and / or transitioned to a low-power state (e.g., a state with low brightness and / or refresh rate)).

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

[0252] Figure 8F shows one embodiment of a user interface 804 that includes (e.g., displays) a path 806a and an indication 808a that indicates path 806a is one of a set of multiple (e.g., three) paths (e.g., the first path) (e.g., the left paging dot is highlighted and / or filled in compared to the center and right dots). In Figure 8F, the user interface 804 includes an indication 812 (e.g., prompt) that all paths that can be provided to the path reader terminal 850 by device 800 can be redeemed with input (e.g., a specific type of input and / or press and long-press gestures). In Figure 8F, device 800 receives (detects) a request 805 (e.g., press and long-press gestures on display 802) to redeem all paths. Upon receiving request 805, device 800 provides the path reader terminal 850 with data corresponding to all paths available for provision by device 800 to the path reader terminal 850 (e.g., data corresponding to paths 806a, 806b, and / or paths corresponding to the right-hand paging dot of indication 808a).

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

[0254] Figure 9 is a flowchart illustrating a method for providing a user with a prompt to grant authorization, according to several embodiments. Method 900 is performed on a computer system (e.g., 100, 300, 500, 600a, 600b, 800) communicating with display generation components (e.g., 602a, 602b, 802) and one or more input devices (e.g., touch-sensitive surfaces). 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 method for providing a user with a prompt to authorize data corresponding to a second path provided to a path reader terminal. This method reduces the cognitive burden on the user when providing data corresponding to two or more paths to a path reader terminal, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, power is saved and the interval between battery charges is increased by enabling the user to authenticate paths (e.g., grouped paths) faster and more efficiently.

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

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

[0258] In accordance with the determination that data corresponding to a second path (e.g., 806b) is available for the computer system to provide to the path reader terminal (906), the computer system provides the user with a prompt (e.g., 808a, 810, haptic notification, and / or audio notification) to authorize the data corresponding to the second path provided to the path reader terminal by the computer system. In some embodiments, the first and second paths are associated with each other (e.g., both paths provide access to the same event and / or day / time at the service provider (e.g., no other paths are used for different events or times / days at the service provider, and / or prompts are provided only for additional paths associated with the first path)). By providing the user with a prompt to authorize the data corresponding to the second path provided to the path reader terminal, the user is provided with feedback that additional paths are available for the path reader terminal to provide. By providing users with improved feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by helping users provide appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and the battery life of the computer system is improved by enabling users to use the computer system more quickly and efficiently.

[0259] In accordance with the determination that data corresponding to a second path (e.g., 806b) is not available for the computer system to provide to the path reader terminal (908), the computer system ceases to provide the user with a prompt to authorize the data corresponding to the second path that the computer system provides to the path reader terminal.

[0260] In some embodiments, before detecting that data corresponding to a first path has been provided to the path reader terminal by the computer system (via NFC signals from the path reader terminal, via confirmation messages from a remote server, and / or via optical scanning), the computer system displays a user interface (e.g., 804) via a display generating component, which includes a representation of the first path (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 path reader terminal. By displaying the user interface including the representation of the first path, the user is provided with visual feedback confirming that the path has been provided to the path reader terminal. By providing the user with improved visual feedback, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0261] In some embodiments, after displaying an indication (e.g., 810) via a display generation component (e.g., 802) that data corresponding to a first path (e.g., 806a) has been provided by the computer system to a path reader terminal (e.g., 850), the computer system maintains the display generation component in an active state (e.g., the display is turned on) according to a determination that a second path (e.g., 806b) is available for the computer system to provide to the path reader terminal. In some embodiments, the computer system deactivates the display generation component (e.g., the display is turned off and / or transitions to a low-power state (e.g., a low brightness and / or refresh rate state)) according to a determination that data corresponding to a second path is available for the computer system to provide to the path reader terminal. By maintaining the display generation component in an active state according to a determination that data corresponding to a second path is available for the computer system to provide to the path reader terminal, the user is provided with visual feedback that data corresponding to a second path is available for the computer system to provide to the path reader terminal. By providing users with improved visual feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by assisting users in providing appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and battery life of the computer system is improved by enabling users to use the computer system more quickly and efficiently.

[0262] In some embodiments, providing a prompt includes displaying an indication (e.g., 808a, 808b, 810) via a display generation component that data corresponding to at least a second path is available for the computer system to provide to the path reader terminal (e.g., displaying a paging dot, displaying a representation of a stack of paths, displaying a tap-screen instruction, displaying a swipe instruction, displaying a tilt-phone instruction, and / or displaying a portion of the second path along the edge of the display). By displaying an indication that data corresponding to at least a second path is available for the computer system to provide to the path reader terminal, the user is provided with visual feedback that additional paths are available for the path reader terminal to provide. By providing the user with improved visual feedback, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0263] In some embodiments, the prompt indicates the number of paths available for the computer system to provide to the path reader terminal (e.g., 808a, 808b) (e.g., a representation of paging dots and / or a stack of paths). By indicating the number of paths available for the path reader terminal, the user is provided with visual feedback on whether additional paths are available for the path reader terminal. By providing the user with improved visual feedback, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0264] In some embodiments, providing a prompt includes outputting an audio notification that data corresponding to a second path is available for the computer system to provide to the path reader terminal. By outputting an audio notification that data corresponding to a second path is available for the computer system to provide to the path reader terminal, feedback is provided to the user that an additional path is available for the path reader terminal to provide. By providing the user with improved feedback, the usability of the computer system is improved, the user-system interface is made more efficient (for example, by helping the user to provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0265] In some embodiments, providing a 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 for the computer system to provide to the path reader terminal. By outputting a tactile output when data corresponding to a second path is available for the computer system to provide to the path reader terminal, feedback is provided to the user that an additional path is available for the path reader terminal to provide. By providing the user with improved feedback, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

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

[0267] In some embodiments, after providing the user with a prompt to authorize data corresponding to a second path to be provided by the computer system to a path reader terminal, the computer system detects authorization of the data corresponding to the second path provided by the computer system to the path reader terminal. In some embodiments, authorization includes detecting movement of a component of the computer system from a lowered position to an raised position (e.g., a device being lifted from the path reader to authorize the second path) (e.g., via an accelerometer). In some embodiments, authorization further includes detecting a biometric sensor (e.g., a camera and / or fingerprint sensor), biometric information (e.g., facial information, iris information, and / or fingerprint information). In some embodiments, after lifting the device from the path reader, the device is lowered again to provide the data corresponding to the second path to the path reader. By authorizing the data corresponding to the second path provided by the computer system to the path reader terminal in response to detecting movement of a component of the computer system from a lowered position to an raised position, the user can efficiently authorize the data corresponding to the second path provided to the path reader terminal without having to provide additional input to navigate an additional user interface. By reducing the number of user inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0268] In some embodiments, authorization for data corresponding to a second path provided to a path reader terminal includes detecting a swipe gesture (e.g., 803) on a display generating component. In some embodiments, after detecting a swipe gesture and authorizing the second path, data corresponding to the second path is provided to the path reader. In some embodiments, authorization includes detecting the rotation of a rotatable input device (e.g., the crown of a watch). In some embodiments, authorization further includes detecting biometric information (e.g., facial information, iris information, and / or fingerprint information). By authorizing data corresponding to a second path provided to the path reader terminal by a computer system in response to the detection of a swipe gesture on a display generating component, the user can efficiently authorize data corresponding to a second path provided to the path reader terminal without having to provide additional input to navigate additional user interfaces. By reducing the number of user inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0269] In some embodiments, authorization of data corresponding to a second path provided to a path reader terminal includes detecting input (e.g., 805) (e.g., tap and hold gestures) (e.g., tap and hold gestures) via one or more input devices within a predetermined time (e.g., while the display generating component is in close proximity to the path reader terminal (e.g., within range of a radio signal from the path reader terminal)). In some embodiments, the input is on an icon indicating a group of paths. In some embodiments, the input is at any position on the display generating component. In some embodiments, by detecting input on the display generating component over a predetermined time, authorization is granted to provide the path reader terminal with data corresponding to all paths, including the first and second paths. By authorizing data corresponding to the second path and one or more additional paths provided to the path reader terminal by the computer system in response to the detection of input over a predetermined time, the user can efficiently authorize data corresponding to the second path and one or more additional paths provided to the path reader terminal without providing additional input to navigate additional user interfaces. By reducing the number of user inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0270] In some embodiments, before detecting that data corresponding to a first path has been provided to the path reader terminal by the computer system, the computer system displays a user interface (e.g., 804) via a display generation component, which includes a representation of the first path (e.g., an image including the name of the first guest and / or the logo of the service provider). In some embodiments, the representation of the first path is displayed in response to user input selecting the first path. In some embodiments, the representation of the first path is displayed in response to user input that generates data for the first path to be provided to the path reader terminal. By displaying the user interface including the representation of the first path, the user is provided with visual feedback that a path can be provided to the path reader terminal. By providing the user with improved visual feedback, the usability of the computer system is improved, the user-system interface is made more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0271] In some embodiments, if the first path (e.g., 806a) and the second path are related to each other (e.g., both paths provide access to the same event and / or day / time at the service provider (e.g., other paths for different events and / or times / days at the service provider are not used, and / or prompts are provided only for additional paths associated with the first path)) (e.g., only in that case), then the data corresponding to the second path (e.g., 806b) is determined to be available for the computer system to provide to the path reader terminal. By determining that the data corresponding to the second path is available for the computer system to provide to the path reader terminal when the first and second paths are related to each other, additional control can be provided to the user when redeeming paths (e.g., by prompting the user to redeem the relevant path and not a path for another venue or event). By providing users with additional control over the computer system, the usability of the computer system is improved, the user-device interface is made more efficient (for example, by assisting users in providing appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling users 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 (for example, Figure 9) are also applicable in a similar manner to the methods described above and below. For example, Methods 700 and 1100 optionally include one or more characteristics of the various methods described above with reference to Method 900. For brevity, these details will not be repeated below.

[0273] Figures 10A to 10L show exemplary user interfaces for displaying machine-readable code according to several embodiments. These user interfaces are used to illustrate processes described later, including the process shown in Figure 11.

[0274] Figure 10A shows a device 1000 including a display 1002 (e.g., a touchscreen display). In Figure 10A, the device 1000 displays a user interface 1004 which contains information about performing transactions using accounts (e.g., payment accounts, bank accounts, credit card accounts, debit card accounts, and / or data storage accounts). In some embodiments, the user interface 1004 is a user interface for a vendor application (e.g., a third-party application associated with banking, credit cards, and / or data migration services) or a vendor website (e.g., a third-party website associated with banking, credit cards, and / or data migration services).

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

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

[0277] Figure 10C shows a device 1000 that displays a user interface 1012 including a representation 1010 of an account 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 an account for a transaction, as shown in Figure 10B. In some embodiments, the user interface 1012 further includes an offer 1014 (e.g., a selectable offer), as shown in Figure 10D. In some embodiments, the offer 1014 is a discount that can be used for a transaction performed on the account (e.g., the offer 1014 allows the user to choose to retrieve additional information about the offer, access the offer, and / or apply the offer).

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

[0279] As shown in Figure 10E, a first machine-readable code 1018 (e.g., a QR code® and / or a two-dimensional code) is displayed in accordance with the determination that the user ID of device 1000 corresponds to the authorized user of the account. 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 account representation 1010 transitioning to the machine-readable code 1018 (e.g., gradually transitioning between multiple intermediate states while transitioning from the account representation 1010 to the machine-readable code 1018) (as shown in Figures 10C and 10D). In some embodiments, the account representation 1010 is animated to appear inverted, thereby revealing the back side 1016 of the representation (for example, the card image is flipped over), and the machine-readable code 1018 is included in the back side 1016 of the representation (the back side of the card image contains 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., using a camera, laser, and / or other optical sensing device) to initiate a transaction using an 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). Using the account information, money can be transferred to or from the account. In some embodiments, the transaction is a transfer of money to a vendor for the purchase of goods. In some embodiments, the transaction is a transfer of money between individuals.

[0281] In some embodiments, the first machine-readable code 1018 and / or the second machine-readable code 1020 differ each time the code is displayed (for example, a different code is displayed each time a request to use a transaction account is received and it is determined that the user's ID corresponds to an authorized user). This allows a unique code to be displayed for each transaction.

[0282] In Figure 10E, while displaying the first machine-readable code 1018, device 1000 receives (e.g., detects) a request 1007 and displays the machine-readable code in a larger size. In the embodiment shown in Figure 10E, request 1007 includes selecting (e.g., tapping) the back side 1016 of the account representation. In response to detecting request 1007 to display the machine-readable code in a larger size, the second machine-readable code 1020 is displayed in a larger size, as shown in Figure 10F. In some embodiments, in response to detecting request 1007 to display the machine-readable code in a larger size, the first machine-readable code 1018 is displayed in a larger size. In some embodiments, displaying the machine-readable code in a larger size makes 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 deactivated after a predetermined period of time (e.g., 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 deactivated if transaction confirmation is not received within a predetermined period of time (e.g., 5 seconds, 15 seconds, 1 minute, and / or depending on whether a time threshold is met). In some embodiments, the predetermined period of time is the time since the user was authenticated or since the machine-readable code was first displayed.

[0284] As shown in Figure 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 ID is displayed again. In some embodiments, a notice 1026 is displayed indicating that no transaction confirmation has 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 account representation 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 account representation 1010 includes displaying an animation of the first machine-readable code 1018 and / or the second machine-readable code 1020 transitioning to the account representation 1010 (for example, gradually transitioning through several intermediate states while transitioning from the machine-readable code to the account representation). In some embodiments, the representation is animated so that the back side 1016 of the representation is inverted and revealed (as shown in Figure 10E) to display the representation 1010 of the account (for example, the card image is inverted from the back to the front).

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

[0286] As shown in Figure 10H, after receiving transaction confirmation (e.g., a transaction authorized to use the account) that the first machine-readable code 1018 and / or the second machine-readable code 1020 (e.g., from a third-party vendor application) has been used to successfully access the information associated with the account, the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 stops, and an indication 1030 (e.g., a checkmark) is displayed indicating that the information associated with the account has been successfully accessed.

[0287] Figure 10I shows a device 1050 including a display 1052 (e.g., a touchscreen display). In Figure 10I, device 1000 displays a user interface 1054 including a representation 1056 of an account used for a transaction (e.g., a payment account, a bank account, a credit card account, a debit card account, and / or a data storage account). In Figure 10I, while displaying the user interface 1054, device 1050 receives (e.g., discovers) a request 1053 to use an account for a transaction. In the embodiment shown in Figure 10I, the request 1053 includes selecting (e.g., tapping) the representation 1056 of the account.

[0288] In response to receiving (e.g., detecting) a request 1053 to use a transaction account, a first machine-readable code 1058 (e.g., a QR code® and / or a two-dimensional code) is displayed, as shown in Figure 10J. In some embodiments, the indication 1062 (e.g., paging dots) showing the first machine-readable code 1058 is one of a set of multiple (e.g., two) types of machine-readable codes (e.g., the first code) (e.g., the left paging dot is highlighted and / or filled in compared to the right dot). In Figure 10J, while displaying the first machine-readable code 1058, the device 1050 receives (e.g., detecting) a request 1055 to display a different type of machine-readable code. In the embodiment shown in Figure 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 the receipt (e.g., detection) of request 1053 to use the transaction account is based on the type of machine-readable code last used in the transaction (e.g., if a barcode was last used in the transaction, the barcode will be displayed in response to request 1053 instead of a QR code).

[0291] As shown in Figure 10L, after receiving transaction confirmation (e.g., a transaction authorized to use the account) that the first machine-readable code 1058 and / or the second machine-readable code 1060 (e.g., from a third-party vendor application) has been used to successfully access the information associated with the account, the display of the first machine-readable code 1018 and / or the second machine-readable code 1020 stops and an indication 1064 (e.g., a checkmark) is displayed, indicating that the information associated with the account has been successfully accessed.

[0292] Figure 11 is a flowchart illustrating a method for displaying a machine-readable code in response to the receipt of authentication data, according to several embodiments. Method 1100 is performed on a computer system (e.g., 100, 300, 500, 600a, 600b, 800, 1000, 1050) communicating with display generation components (e.g., 602a, 602b, 802, 1002, 1052) and one or more input devices (e.g., touch-sensitive surfaces, cameras, fingerprint sensors, and / or biometric sensors). 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, Method 1100 provides an intuitive way to display machine-readable codes. This method reduces the cognitive burden on the user when displaying machine-readable codes on a computer system. In the case of battery-powered computing systems, it saves power and extends battery charging time by allowing users to display machine-readable codes faster and more efficiently.

[0294] In Method 1100, a computer system (e.g., 1000, 1050) displays 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) via a display generating component (e.g., 1002, 1052) (1102). 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 authentication data (e.g., facial information, fingerprint information, and / or passcodes) via one or more input devices (e.g., via one or more biometric sensors) (1104).

[0296] Upon receiving authentication data (1106), and in accordance with the determination that the authentication data satisfies the authentication criteria associated with the account (1108) (e.g., facial information matches the account holder's facial information, fingerprint information matches the account holder's fingerprint information, and / or passcode matches the account holder's passcode), the computer system 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., a machine-readable code that can be used to authorize transactions in the account) via a display generation component. By displaying the machine-readable code in accordance with the determination that the authentication data satisfies the authentication criteria associated with the account, the user is provided with visual feedback confirming that the authentication criteria have been met and that the machine-readable code can be used to improve the security of transactions. By providing users with improved visual feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by assisting users in providing appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and battery life of the computer system is improved by enabling users to use the computer system more quickly and efficiently.

[0297] Upon receiving authentication data (1106) and determining that the authentication data does not meet the authentication criteria associated with the account (1110), the computer system ceases displaying the first machine-readable codes associated with the account (e.g., 1018, 1020, 1058, 1060).

[0298] In some embodiments, displaying machine-readable codes (e.g., 1018, 1020, 1058, 1060) includes replacing the display of account indications (e.g., 1010, 1056) with the display of machine-readable codes (e.g., stopping the display of account indications and displaying machine-readable codes). In some embodiments, replacing the display of account indications with the display of machine-readable codes includes an animated transition from account indications to machine-readable codes (e.g., a gradual transition through multiple intermediate states while transitioning from account indications to machine-readable codes). By replacing the display of account indications with the display of machine-readable codes, the user is provided with visual feedback confirming that authentication criteria have been met, and the security of transactions is improved by using machine-readable codes. By providing users with improved visual feedback, the usability of the computer system is enhanced, the user-system interface is made more efficient (for example, by assisting users in providing appropriate input when operating / interacting with the computer system and reducing user errors), and power consumption is reduced and battery life of the computer system is improved by enabling users to use the computer system more quickly and efficiently.

[0299] In some embodiments, the computer system displays a second user interface (e.g., 1004) for an application associated with a service provider (e.g., a third-party application associated with a vendor (e.g., a bank and / or retailer)) via a display generation component. In some embodiments, an account is associated with a service provider. In some embodiments, while displaying the second user interface, the computer system detects a request (e.g., 1003) (e.g., a request to add a vendor-associated card to the first user interface) (e.g., a request to add a vendor-associated card to the first user interface) (e.g., via a touch-sensitive surface), and in response to detecting a request to configure an account for use in 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 an account for use in the first user interface while displaying the second user interface, the user can efficiently configure an account (e.g., for use in a wallet application) without having to manually navigate between multiple user interfaces. By reducing the number of inputs required to perform an operation, the usability of the computer system is improved; the user system interface is made more efficient (for example, by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors); and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling the user to use the computer system more quickly and efficiently.

[0300] In some embodiments, the computer system receives second authentication data (e.g., facial information, fingerprint information, and / or a passcode) via one or more input devices, and upon receiving the second authentication data, according to a determination that the second authentication data satisfies the authentication criteria associated with the account (e.g., facial information matches the account holder's facial information, fingerprint information matches the account holder's fingerprint information, and / or passcode matches the account holder's passcode), the computer system displays 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 via a display generation component, wherein the second machine-readable code is different from the first machine-readable code (e.g., a different machine-readable code is displayed each time a transaction is authorized). In some embodiments, the machine-readable code is different from all previous codes (e.g., machine-readable codes are unique). In some embodiments, upon receiving second authentication data and determining that the second authentication data does not meet the authentication criteria associated with the account, the computer system stops displaying the second machine-readable code associated with the account. By displaying a second machine-readable code different from the first machine-readable code, the system provides the user with visual feedback confirming that the authentication criteria are met, and improves transaction security by using different machine-readable codes for each transaction. By providing the user with improved visual feedback, the system improves the usability of the computer system, making the user-system interface more efficient (for example, by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, reduces power consumption and improves the battery life of the computer system by enabling 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 a determination 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 elapsed since authentication information was received or the machine-readable code was first displayed). By stopping the display of the machine-readable code after a predetermined time, transaction security is improved by limiting the time for which the machine-readable code is displayed.

[0302] In some embodiments, the machine-readable code is a first machine-readable code, and after displaying the first machine-readable code associated with the account (e.g., 1018, 1020, 1058, 1060), the computer system stops displaying the first machine-readable code after a predetermined time (e.g., 5 seconds, 15 seconds, 1 minute, and / or depending on whether the time threshold is met), and the computer system displays a second machine-readable code associated with the account that is different from the first machine-readable code associated with the account (e.g., 1018, 1020, 1058, 1060). In some embodiments, the second machine-readable code is displayed depending on whether the time threshold is met (e.g., if the first machine-readable code has been displayed for a predetermined time). By displaying a second machine-readable code that is different from the first machine-readable code, transaction security is improved by limiting the time for which the machine-readable code is displayed.

[0303] In some embodiments, after displaying a machine-readable code associated with an account (e.g., 1018, 1020, 1058, 1060), and after determining that second authentication data is received within a predetermined time (e.g., within 5 seconds, 30 seconds, 2 minutes, and / or depending on whether a time threshold is met) and that the second authentication data satisfies the authentication criteria associated with the account (e.g., facial information matches the account holder's facial information, fingerprint information matches the account holder's fingerprint information, and / or passcode matches the account holder's passcode), the computer system continues to display the machine-readable code associated with the account. In some embodiments, after displaying a machine-readable code associated with an account, and after determining that second authentication data is not received within a predetermined time (e.g., within 5 seconds, 30 seconds, 2 minutes, and / or depending on whether a time threshold is met) or that the second authentication data does not satisfy the authentication criteria associated with the account (e.g., depending on whether a passcode matches the account holder's passcode), the computer system stops 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). By stopping the display of the machine-readable code according to the determination that the second authentication data is not received within a predetermined time, the user is provided with visual feedback that the authentication criteria were not met, and the security of the transaction is improved by limiting the time the machine-readable code is displayed. By providing improved visual feedback, the usability of the computer system is improved, the user device interface becomes more efficient (e.g., by helping the user make appropriate inputs when operating / interacting with the computer system and reducing user errors), and this further reduces the power consumption of the computer system and improves battery life by allowing the user to use the device more quickly and efficiently.

[0304] In some embodiments, after displaying a machine-readable code associated with an account (e.g., 1018, 1020, 1058, 1060), and in accordance with a determination that second authentication data is not received within a predetermined time (e.g., 5 seconds, 30 seconds, 2 minutes, and / or depending on whether the time threshold is met) or that the second authentication data does not meet the authentication criteria associated with the account, the computer system displays a request for second authentication data (e.g., a user interface 1012 as shown in Figure 10G) (e.g., a request to reauthorize the transaction using biometric information (e.g., facial information and / or fingerprint information) and / or a passcode). By displaying the request for second authentication data, the user is provided with visual feedback that the second authentication data was not received within a predetermined time or that the authentication criteria were not met. By providing improved visual feedback, the usability of the computer system is enhanced, the user device interface becomes more efficient (for example, by helping users make appropriate inputs when operating / interacting with the computer system and reducing user errors), and this further reduces the power consumption of the computer system and improves battery life by allowing users to use the device more quickly and efficiently.

[0305] In some embodiments, after displaying the machine-readable codes 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 codes were successfully used to access the information associated with the account (e.g., a transaction using the account was authenticated), and in response to receiving confirmation that the machine-readable codes were successfully used to access the information associated with the account, the computer system stops displaying the machine-readable codes and displays an indication (e.g., 1030) (e.g., a checkmark icon) via a display generation component that the information associated with the account has been successfully accessed. By displaying the indication that the information associated with the account has been successfully accessed, the user is provided with visual feedback that the machine-readable codes were successfully used to access the information associated with the account. By providing improved visual feedback, the usability of the computer system is enhanced, the user device interface becomes more efficient (for example, by helping users make appropriate inputs when operating / interacting with the computer system and reducing user errors), and this further reduces the power consumption of the computer system and improves battery life by allowing users to use the device more quickly and efficiently.

[0306] In some embodiments, displaying a machine-readable code includes displaying the machine-readable code (e.g., 1020) in a first size. In some embodiments, while displaying the machine-readable code in the first size, the computer system detects a request to display the machine-readable code in a larger size (e.g., 1007) (e.g., a tap gesture on the machine-readable code), and in response to detecting the request to display the machine-readable code in a larger size, the computer system displays the machine-readable code in a second size that is larger than the first size (e.g., 1020 as shown in Figure 10F). Displaying the machine-readable code in a second size that is larger than the first size provides the user with additional control over the size of the machine-readable code. Larger machine-readable codes may improve the ability of the code scanner to read the machine-readable code. By providing users with additional control over the computer system, the usability of the computer system is improved, the user-device interface is made more efficient (for example, by assisting users in providing appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by enabling users 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., 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., 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., QR Code® is replaced with a barcode, and / or a barcode is replaced with a QR Code®). In some embodiments, for example, on a watch (e.g., 1050), the request to display the second type of machine-readable code is detected after tapping on an account representation (1056) to display a machine-readable code. In some embodiments, the display order of QR Code® or barcodes is based on the type of code that was displayed last. By displaying a second type of machine-readable code, the user is given additional control over the type of machine-readable code. Different types of machine-readable codes may allow the machine-readable code to be scanned by additional types of code scanners. By providing the user with additional control over the computer system, the usability of the computer system is improved, the user-device interface is made more efficient (for example, by helping the user provide appropriate input when operating / interacting with the computer system and reducing user errors), and in addition, power consumption is reduced and the battery life of the computer system is improved by allowing the user to use the computer system more quickly and efficiently.

[0308] In some embodiments, displaying a first user interface includes displaying one or more offers associated with an account (e.g., 1014, selectable offers) (e.g., discounts that may be used in transactions with the account provider). By displaying one or more offers associated with an account, the user can access contextually relevant offers from the first user interface without having to navigate to additional user interfaces. This improves the usability of the computer system by reducing the number of inputs required to perform an operation, makes the user system interface more efficient (e.g., by helping the user to provide appropriate inputs when operating / interacting with the computer system and reducing user errors), and reduces power consumption and improves the 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 the details of the process described above with respect to Method 1100 (e.g., Figure 11) are also applicable in a similar manner to the methods described above. For example, Methods 700 and 900 optionally include one or more characteristics of the various methods described above with reference to Method 1100. For brevity, these details will not be repeated below.

[0310] Figure 12A shows an electronic device 1200 having a display 1202 (e.g., a touchscreen) and one or more input devices (e.g., a rotatable input mechanism 1204, a side button 1206). In Figure 12A, the electronic device 1200 displays an account user interface 1208 (e.g., similar to the account user interface 1302 described below with reference to Figure 13B) on the display 1202. The electronic device 1200 displays multiple platters 1210 associated with each user's computer storage account on the account user interface 1208. Each user's computer storage account contains varying 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). Therefore, upon detecting user input corresponding to the selection of a platter from multiple platters 1210, the electronic device 1200 displays information related to the computer storage resources associated with each computer storage account corresponding to the selected platter (e.g., the amount of available data and / or the amount of data consumed).

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

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

[0313] In Figure 12C, the electronic device 1200 detects 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 has scrolled the account user interface 1208). As a result of pausing the memory platter 1210b (e.g., memory player 1210b) at least for a predetermined period of time (e.g., without scrolling the memory platter 1210b during the predetermined period), the account user interface 1208 is modified as shown in Figure 12C.

[0314] In Figure 12C, the appearance of the storage card platter 1210a and the shared data platter 1210c is less emphasized compared to the memory platter 1210b. The storage card platter 1210a and the shared data platter 1210c are less emphasized compared to the memory platter 1210b by being smaller in size. To further emphasize the platters, the appearance of the storage card platter 1210a and the shared data platter 1210c are modified compared to the memory platter 1210b (for example, by reducing opacity, blurring, and / or changing color), as shown in Figure 12C by hatching. In some embodiments, the electronic device 1200 is configured to less emphasize the platters by refraining from displaying platters that are not centered on the display 1202.

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

[0316] Figure 13A shows an electronic device 1200 displaying a user interface 1300. In Figure 13A, the user interface 1300 is the watch face. In other embodiments, the user interface 1300 is a user interface associated with an application of the electronic device 1200. In Figure 13A, the electronic device 1200 detects a user input 1350a (e.g., a double-press gesture and / or a double-tap gesture) on the side button 1206. In response to detecting the user input 1350a, the electronic device 1200 displays the account user interface 1302 of a transfer application (e.g., an e-wallet application), as shown in Figure 13B. Furthermore, in Figure 13A, the electronic device 1200 detects a user input 1350b (e.g., a single press and / or a single tap input) on the crown 1204. In response to detecting the user input 1350b, the electronic device 1200 displays the application user interface 1320, as shown in Figure 13I. In some embodiments, the electronic device 1200 displays the account user interface 1302 in response to detecting 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., a clock face user interface 1300, a user interface for another application, and / or an application user interface 1320).

[0317] As will be discussed in detail below with reference to Figures 13B to 13N, user input 1350a authorizes and / or activates a transfer account linked to electronic device 1200. Thus, when a set of transfer criteria is met (e.g., when electronic device 1200 is positioned near the receiver threshold and the linked transfer account is authorized / activated), electronic device 1200 exposes (e.g., transmits) the credentials associated with each transfer account. In contrast, upon receiving a different set of user inputs (e.g., tap gesture 1350h following user input 1350b in Figure 13I), electronic device 1200 displays the account user interface 1302 without authorizing and / or activating the linked transfer account (without further user input). Thus, in response to detecting user input 1350b (detecting tap gesture 1350h), electronic device 1200 does not expose the credentials associated with each transfer account when a set of transfer criteria is met.

[0318] In Figure 13B, the account user interface 1302 includes multiple platters 1304 associated with each transfer account (e.g., payment accounts, pass accounts, ticket accounts, points accounts, reward accounts, and / or transit accounts, such as third-party credit card accounts, debit card accounts, and / or stored value accounts) linked to (e.g., supplied to) the electronic device 1200. In some embodiments, a user can provide one or more transfer accounts to the electronic device 1200 and use the transfer accounts to make transfers. For example, upon receiving access from a user to a transfer account, the electronic device 1200 receives credentials associated with the transfer account (e.g., account number, PIN code, authorization code, passcode, card number, balance information, and / or address) and stores them in the secure element of the electronic device 1200. The electronic device 1200 exposes (e.g., transmits) the 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 representing a second transfer account (e.g., a cash card and / or a gift card) (e.g., a partial view of the cash platter 1304b) 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 in the center of the display 1202 (for example, in a predefined position (or within a predefined area) of the display or user interface), but the electronic device 1202 does not pause the transfer card platter 1304a (for example, the display 1202 of the electronic device does not display the card platter 1304a in a predefined position (or within a predefined area) of the display or user interface for at least a predetermined period of time (for example, the electronic device 1202 does not scroll the transfer card platter 1304a during a predetermined period of time), and therefore does not change the emphasis of the cache platter 1304b on the transfer card platter 1304a (for example, does not reduce the emphasis).

[0320] In Figure 13B, the electronic device 1200 detects a swipe gesture 1350c (e.g., an upward swipe gesture) before a predetermined period of time has elapsed. In response to the detection of the swipe gesture 1350c, 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 additional platters (e.g., 1304c, 1304d) of the multiple 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 a rotatable input mechanism 1204 in addition to the swipe gesture.

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

[0322] In Figure 13C, the platter has stopped scrolling and is stationary. The boarding pass platter 1304c is displayed in the center of the display 1202 (for example, in a predefined position (or within a predefined area) of the display or user interface), but the display 1202 of the electronic device has not paused the boarding pass platter 1304c (for example, the display 1202 of the electronic device has not displayed the boarding pass platter 1304c in a predefined position (or within a predefined area) of the display or user interface for at least a predetermined period of time (for example, the electronic device 1202 has not scrolled the boarding pass platter 1304c during a predetermined period of time), and therefore does not change the emphasis of platters 1304b and 1304d relative to the boarding pass platter 1304c (for example, does not reduce the emphasis).

[0323] In Figure 13C (and before a 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 the multiple platters 1304 of the account user interface 1302 upward and / or translates them) to display the account user interface 1302 as shown in Figure 13D. In Figure 13D, after the swipe gesture 1350d is stopped, the electronic device 1200 stops scrolling the account user interface 1302 (for example, 3 seconds after detecting the end of the swipe gesture 1350d), and the electronic device 1200 pauses the transfer card platter 1304a (for example, the transfer card platter 1304a stays at the center of the display 1202 for at least a predetermined period (for example, without scrolling the transfer card platter 1304a for a predetermined period) (for example, a predefined position on the display or user interface (or (displayed within a predefined area). As a result of a pause on the transfer card platter 1304a for a predetermined period (e.g., 2 seconds, 1 second, 2 seconds), the account user interface 1302 is modified as shown in Figure 13D. In some embodiments, prior to the pause on a particular platter, each platter of a plurality of platters has a uniform size (e.g., each platter has the same size and / or shape). In some embodiments, prior to the pause on a particular platter, the platters of a 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 cash platter 1304b is reduced in emphasis compared to the transfer card platter 1304a (regardless of whether the platter has a uniform or non-uniform appearance in Figure 13C). Reducing the emphasis of the cash platter 1304b compared to the transfer card platter 1304a includes, for example, reducing the size of the cash platter 1304b compared to the transfer card platter 1304a (e.g., reducing the size of the cash 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 decreasing) the size of the cash platter 1304b). Furthermore, the additional appearance of the cache platter 1304b is optionally modified (e.g., by reducing opacity, blurring, and / or changing color) compared to the transfer card platter 1304a (e.g., as shown in Figure 13D by the hatching of the cache platter 1304b) to reduce the emphasis on the cache platter 1304b. In some embodiments, the electronic device 1200 is configured to reduce the emphasis on platters that are not centrally located in the display 1202 (e.g., the cache platter 1304b) by ceasing to display the platter.

[0325] Furthermore, in Figure 13D, since 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 (not tap gesture 1350h), the electronic device 1200 displays indicator 1306 ("Keep near reader") indicating that the transfer account associated with the transfer card platter 1304a (e.g., the first transfer account) is activated (e.g., authorized for use to perform transfers and / or transactions). Indicator 1306 prompts the user of the electronic device 1200 to position the electronic device close to the receiver (e.g., within a threshold proximity of a device capable of receiving transmissions from the electronic device 1200). Therefore, when the electronic device 1200 is positioned close to the receiver (e.g., within proximity to a wireless communication terminal), it can use the transfer account associated with the transfer card platter 1304a to perform transfers (e.g., transactions using financial funds, point transfers, credit transfers, and / or entry authorizations) without further user input. User input 1350a (compared to a tap gesture 1350h) that causes the electronic device 1200 to display the account user interface 1302 allows the electronic device 1200 to authorize transfer accounts associated with multiple platters 1304 of the account user interface 1302. When the transfer card platter 1304a is suspended in the account user interface 1302 by accessing the account user interface 1302 via a technique that does not include user input 1350a (e.g., including tap gestures 1350h and / or voice commands instead), as discussed below with reference to Figures 13I to 13K, the transfer account associated with the transfer card platter 1304a is not activated.

[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 emphasis reduction (e.g., returns the platter to its visual appearance before emphasis reduction) and scrolls the account user interface 1302 (e.g., scrolls down 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 customer 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. Upon detecting the tap gesture 1350f, the electronic device 1200 displays the user interface 1330, as shown in Figure 13O.

[0327] In Figure 13E, upon 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, the account user interface 1302 is corrected as a result of the pause (for a predetermined period (e.g., 0.5 seconds, 1 second, 2 seconds)) on the boarding pass platter 1304c.

[0328] In Figure 13E, in response to the pause on the boarding pass platter 1304c, the appearance of the cash platter 1304b and the customer card platter 1304d are less emphasized compared to the boarding pass platter 1304c. The reduction in emphasis optionally includes reducing the size of the cash platter 1304b and the customer card platter 1304d compared to the boarding pass platter 1304c. Furthermore, the reduction in emphasis optionally includes modifying the appearance of the cash platter 1304b and the customer card platter 1304d compared to the boarding pass platter 1304c (e.g., by reducing opacity, blurring, and / or changing the color), as shown in Figure 13E by the hatching of the cash platter 1304b and the customer card platter 1304d.

[0329] Furthermore, in Figure 13E, in response to the suspension of 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) is authorized and / or activated (e.g., the boarding pass is authorized for scanning). In Figure 13E, the boarding pass platter 1304c includes the display of a visual indicator of information related to the specific path represented by the boarding pass platter 1304c. For example, the boarding pass platter 1304c includes the display of a visual indicator that distinguishes the boarding pass platter 1304c from other boarding pass platters in a group of platters 1304. The boarding pass platter 1304c displays the passenger's name 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 the flight information for the flight associated with the boarding pass platter ("SFO DEN", ​​origin and destination). Thus, the electronic device 1200 allows the user to easily avoid confusion with 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 Figure 13E, while the boarding pass platter 1304c is authorized and / or activated (visually indicated by reduced emphasis on other platters), the electronic device 1200 detects a tap gesture 1350g on the boarding pass platter 1304c. In response to the detection of the tap gesture 1304c, the electronic device 1200 displays a machine-readable code 1310 (e.g., a QR code® and / or barcode) as shown in Figure 13G. To display the code 1310 in Figure 13G, the electronic device 1200 displays a transition (e.g., an animation) between the account user interface 1302 in Figure 13E and the code 1310 in Figure 13G. For example, in Figure 13F, the electronic device 1200 displays the boarding pass details user interface 1326 in response to the 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 displays the boarding pass details user interface 1326 as an animation before displaying the code 1310 as shown in Figure 13G (for example, the electronic device 1200 di...

Claims

1. It is a method, In a computer system that communicates with a display generation component and one or more input devices, Receiving a first input via one or more input devices, Upon receiving the first input, The display generation component is used to display an account user interface including a first visual representation of the first account, While displaying the first visual representation of the first account, a second input corresponding to the selection of the first visual representation of the first account is received via one or more input devices. Upon receiving the second input corresponding to the selection of the first visual representation of the first account, In accordance with the determination that the first visual representation of the first account was displayed in response to a request to prepare one or more accounts from the account user interface for use, the display generation component displays the readable portion of the machine-readable code corresponding to the first account. A method comprising, upon determination that the first visual representation of the first account has been displayed in response to a request to view information about one or more accounts without preparing one or more accounts from the account user interface for use, displaying information corresponding to the first account via the display generation component without displaying the readable portion of the machine-readable code corresponding to the first account.

2. The readable portion of the machine-readable code corresponding to the first account is displayed via the display generation component at a first brightness level. The information corresponding to the first account is displayed via the display generation component at a second brightness level lower than the first brightness level. The method according to claim 1.

3. Receiving scroll input via one or more input devices while displaying the readable portion of the machine-readable code corresponding to the first account, In response to receiving the aforementioned scroll input, the details of the first account are displayed, The method according to any one of claims 1 to 2, further comprising:

4. The displayed information corresponding to the first account is The visual representation of the first account, At least some of the parts of the machine-readable code, The method according to any one of claims 1 to 3, comprising one or more details of the first account, wherein the one or more details of the first account are displayed between the visual representation of the first account and at least some of the portions of the machine-readable code.

5. The method according to any one of claims 1 to 4, wherein a visual representation of a first type of account is displayed in the account user interface at the respective heights, and a visual representation of a second type of account is displayed in the account user interface at the respective heights.

6. The method according to any one of claims 1 to 5, wherein the first visual representation of the first account includes a display of one or more data corresponding to the first account, and the one or more data is selected from a plurality of data corresponding to the first account.

7. The method according to claim 6, wherein the one or more data includes data that distinguishes the first visual representation of the first account from other visual representations of other accounts in the account user interface.

8. The method according to any one of claims 6 to 7, wherein the one or more data includes an indication of the source of the first account.

9. Receiving a second scroll input while displaying the account user interface, which includes the first visual representation of the first account; In response to receiving the second scroll input, the second visual representation of the second account is displayed on the account user interface via the display generation component, After receiving the second input corresponding to the selection of the first visual representation of the first account, a third scroll input is received, In response to receiving the third scroll input, additional information corresponding to the first account is displayed, The method according to any one of claims 1 to 8, further comprising:

10. The first account mentioned above is a preferred customer account, and the method is, The method according to any one of claims 1 to 9, further comprising displaying a second visual indication of a second account to be used in response to the use of the first account, wherein the second account is a payment account.

11. The display generation component enables the display of the readable portion of the machine-readable code corresponding to the first account. The method according to any one of claims 1 to 10, comprising scrolling content via the display generation component to display the readable portion of the machine-readable code corresponding to the first account.

12. Receiving a fourth scroll input while displaying information corresponding to the first account without displaying the readable portion of the machine-readable code corresponding to the first account, In response to receiving the aforementioned fourth scroll input, additional information is scrolled, After scrolling through the additional information, the brightness of the display of the readable portion of the machine-readable code corresponding to the first account is increased, in accordance with the determination that the readable portion of the machine-readable code is displayed in the selected area for at least a threshold time. The method according to any one of claims 1 to 11, further comprising:

13. A computer program that causes a computer to perform the method described in any one of claims 1 to 12.

14. A computer system, A memory for storing the computer program described in claim 13, A computer system comprising one or more processors capable of executing the computer program stored in the memory, wherein the computer system is configured to communicate with a display generation component and one or more input devices.

15. A computer system, Display generation components and One or more input devices, Means for carrying out the method described in any one of claims 1 to 12, A computer system equipped with the following features.

Images