Account management user interface

Abstract

This disclosure relates to an account management user interface. This disclosure as a whole relates to managing user accounts. In some embodiments, managing user accounts includes managing remote data storage associated with the user account. In some embodiments, managing user accounts includes managing the deletion of data in the remote data storage associated with the user account. In some embodiments, managing user accounts includes managing balance transfers for the user account.

Description

[0001] This application is a divisional application of Chinese patent application filed on August 31, 2020, with application number 202080060828.X and invention title "Account Management User Interface". Technical Field

[0002] This disclosure relates in general to computer user interfaces, and more specifically to user interfaces for managing accounts. Background Technology

[0003] Electronic devices can be used to manage accounts configured on them. Various characteristics of accounts can be controlled, executed, or managed using electronic devices. Summary of the Invention

[0004] However, some technologies used to manage accounts with electronic devices are often cumbersome and inefficient. For example, some existing technologies require users to use applications that the device user may not frequently use, potentially forcing the user to open rarely used applications or navigate rarely used interfaces. Similarly, some existing technologies offer limited options for easily and conveniently managing disk space associated with an account. Furthermore, some existing technologies offer limited options for easily and conveniently managing installment plans associated with a transfer account. Moreover, some existing technologies use complex and time-consuming user interfaces that may involve multiple keystrokes or button presses. Therefore, existing technologies require more time than necessary, resulting in wasted user time and device power. This latter consideration is particularly important in battery-powered devices.

[0005] Therefore, this technology provides electronic devices with faster and more efficient methods and interfaces for managing accounts. Such methods and interfaces optionally complement or replace other methods used for account management. These methods and interfaces reduce the cognitive burden on users and result in more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charging. These methods and interfaces also reduce the amount of unnecessary, irrelevant, or repetitive input required on computing devices such as smartphones and smartwatches.

[0006] According to some embodiments, a method performed at an electronic device having a display and one or more input devices is described. The method includes: displaying a first user interface corresponding to a user account on the display device, wherein the first user interface includes: a first user interface element corresponding to a first task performed using the user account; and a second user interface element corresponding to a second task performed using the user account; detecting first user input while displaying the first user interface; and in response to detecting the first user input: displaying a second user interface having a first image without displaying a second image, the first image corresponding to one or more items associated with the first task performed using the user account, the second image corresponding to one or more items associated with the second task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element; and displaying the second user interface having the second image without displaying the first image, the second image corresponding to one or more items associated with the second task performed using the user account, the first image corresponding to one or more items associated with the first task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element.

[0007] According to some embodiments, a non-transitory computer-readable storage medium is described, the non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices. The one or more programs include instructions for: displaying a first user interface corresponding to a user account on the display device, wherein the first user interface includes: a first user interface element corresponding to a first task performed using the user account; and a second user interface element corresponding to a second task performed using the user account; detecting first user input while displaying the first user interface; and in response to detecting the first user input: displaying a second user interface having a first image without displaying a second image, the first image corresponding to one or more items associated with the first task performed using the user account, the second image corresponding to one or more items associated with the second task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element; and displaying the second user interface having the second image without displaying the first image, the second image corresponding to one or more items associated with the second task performed using the user account, the first image corresponding to one or more items associated with the first task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element.

[0008] According to some embodiments, a transient computer-readable storage medium is described, the transient computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices. The one or more programs include instructions for: displaying a first user interface corresponding to a user account on the display device, wherein the first user interface includes: a first user interface element corresponding to a first task performed using the user account; and a second user interface element corresponding to a second task performed using the user account; detecting first user input while displaying the first user interface; and in response to detecting the first user input: displaying a second user interface having a first image without displaying a second image, the first image corresponding to one or more items associated with the first task performed using the user account, the second image corresponding to one or more items associated with the second task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element; and displaying the second user interface having the second image without displaying the first image, the second image corresponding to one or more items associated with the second task performed using the user account, the first image corresponding to one or more items associated with the first task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element.

[0009] According to some embodiments, an electronic device is described, the electronic device including a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: displaying a first user interface corresponding to a user account on the display device, wherein the first user interface includes: a first user interface element corresponding to a first task performed using the user account; and a second user interface element corresponding to a second task performed using the user account; detecting first user input while displaying the first user interface; and in response to detecting the first user input: displaying a second user interface having a first image without displaying a second image, the first image corresponding to one or more items associated with the first task performed using the user account, the second image corresponding to one or more items associated with the second task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element; and displaying the second user interface having the second image without displaying the first image, the second image corresponding to one or more items associated with the second task performed using the user account, the first image corresponding to one or more items associated with the first task performed using the user account, based on determining that the first user input corresponds to a selection of the second user interface element.

[0010] According to some embodiments, an electronic device is described. The electronic device includes a display device; one or more input devices; means for displaying a first user interface corresponding to a user account on the display device, wherein the first user interface includes: a first user interface element corresponding to a first task performed using the user account; and a second user interface element corresponding to a second task performed using the user account; means for detecting first user input when displaying the first user interface; and means for performing the following operations: in response to detecting the first user input: based on determining that the first user input corresponds to a selection of the first user interface element, displaying a second user interface having a first image without displaying a second image, the first image corresponding to one or more items associated with the first task performed using the user account, the second image corresponding to one or more items associated with the second task performed using the user account; and based on determining that the first user input corresponds to a selection of the second user interface element, displaying the second user interface having the second image without displaying the first image, the second image corresponding to one or more items associated with the second task performed using the user account, the first image corresponding to one or more items associated with the first task performed using the user account.

[0011] According to some embodiments, a method is described performed at an electronic device having a display and one or more input devices. The method includes: receiving a request to display a numeric selection user interface; and in response to receiving the request to display the numeric selection user interface, displaying a numeric selection user interface for selecting a value for a corresponding parameter, wherein the numeric selection user interface includes: a predefined path having a corresponding size and shape, a value selector, and an optional user interface object for initiating a process of performing a predefined operation using a value associated with the value selector; wherein displaying the numeric selection user interface includes: displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and ..., and the second point on the predefined path corresponds to a second value, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value, and the second point on the predefined path corresponds to a second value, wherein a second point on the predefined path corresponds to a first value, and the second point on the predefined path corresponds to a second value, wherein a second point on the predefined path corresponds to a first value, and the second point on the predefined path corresponds to a second value, wherein a second point on the predefined path corresponds to a first value, and the second point on the predefined path corresponds to a second value, wherein a second point Define a path, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value; when displaying the value selection user interface, detect input corresponding to activation of the optional user interface object; and in response to detecting the input corresponding to activation of the optional user interface object: initiate a process of performing the predefined operation using the first value based on the determination that the value selector is at the first point on the predefined path and the request to display the value selection user interface meets the first criterion; initiate a process of performing the predefined operation using the second value based on the determination that the value selector is at the second point on the predefined path and the request to display the value selection user interface meets the first criterion; initiate a process of performing the predefined operation using the third value based on the determination that the value selector is at the first point on the predefined path and the request to display the value selection user interface meets the second criterion; and initiate a process of performing the predefined operation using the fourth value based on the determination that the value selector is at the second point on the predefined path and the request to display the value selection user interface meets the second criterion.

[0012] According to some embodiments, a non-transitory computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices. The one or more programs include instructions for: receiving a request to display a numeric selection user interface; and, in response to receiving the request to display the numeric selection user interface, displaying a numeric selection user interface for selecting a value for a corresponding parameter, wherein the numeric selection user interface includes: a predefined path having a corresponding size and shape, a value selector, and an optional user interface object for initiating a process of performing a predefined operation using a value associated with the value selector; wherein displaying the numeric selection user interface includes: displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and ..., wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value, wherein a first point on the predefined path corresponds to The predefined path of the shape, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value; when displaying the value selection user interface, detecting input corresponding to activation of the optional user interface object; and in response to detecting the input corresponding to activation of the optional user interface object: initiating a process of performing the predefined operation using the first value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the second value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the third value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the second criterion; and initiating a process of performing the predefined operation using the fourth value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the second criterion.

[0013] According to some embodiments, a transient computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of an electronic device having a display device and one or more input devices. The one or more programs include instructions for: receiving a request to display a numeric selection user interface; and, in response to receiving the request to display the numeric selection user interface, displaying a numeric selection user interface for selecting a value for a corresponding parameter, wherein the numeric selection user interface includes: a predefined path having a corresponding size and shape, a value selector, and an optional user interface object for initiating a process of performing a predefined operation using a value associated with the value selector; wherein displaying the numeric selection user interface includes: displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and ..., wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value, wherein a first point on the predefined path corresponds to The predefined path of the shape, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value; when displaying the value selection user interface, detecting input corresponding to activation of the optional user interface object; and in response to detecting the input corresponding to activation of the optional user interface object: initiating a process of performing the predefined operation using the first value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the second value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the third value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the second criterion; and initiating a process of performing the predefined operation using the fourth value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the second criterion.

[0014] According to some embodiments, an electronic device is described, the electronic device including a display device, one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving a request to display a numeric selection user interface; and, in response to receiving the request to display the numeric selection user interface, displaying a numeric selection user interface for selecting a value for a corresponding parameter, wherein the numeric selection user interface includes: a predefined path having a corresponding size and shape, a value selector, and an optional user interface object for initiating a process of performing a predefined operation using a value associated with the value selector; wherein displaying the numeric selection user interface includes: displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and ..., wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value, wherein a first point on the predefined path corresponds to The predefined path of the shape, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value; when displaying the value selection user interface, detecting input corresponding to activation of the optional user interface object; and in response to detecting the input corresponding to activation of the optional user interface object: initiating a process of performing the predefined operation using the first value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the second value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the first criterion; initiating a process of performing the predefined operation using the third value based on determining that the value selector is at the first point on the predefined path and that the request to display the value selection user interface meets the second criterion; and initiating a process of performing the predefined operation using the fourth value based on determining that the value selector is at the second point on the predefined path and that the request to display the value selection user interface meets the second criterion.

[0015] According to some embodiments, an electronic device is described. The electronic device includes a display device; one or more input devices; means for receiving a request to display a numeric selection user interface; and means for performing the following operations: in response to receiving the request to display the numeric selection user interface, displaying a numeric selection user interface for selecting a value for a corresponding parameter, wherein the numeric selection user interface includes: a predefined path having a corresponding size and shape, a value selector, and an optional user interface object for initiating a process of performing a predefined operation using a value associated with the value selector; wherein displaying the numeric selection user interface includes: displaying the predefined path having the corresponding size and shape, wherein a first point on the predefined path corresponds to a first value, and a second point on the predefined path corresponds to a second value; and displaying a second criterion, wherein the request to display the numeric selection user interface is satisfied, based on the determination that the request to display the numeric selection user interface satisfies a second criterion, which includes a criterion satisfied when the request to display the numeric selection user interface occurs simultaneously with the display of a second user interface different from the first user interface and associated with the corresponding parameter. The system displays a predefined path with the corresponding size and shape, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value; when displaying the value selection user interface, it detects input corresponding to activation of the optional user interface object; and in response to detecting the input corresponding to activation of the optional user interface object: based on the determination that the value selector is at the first point on the predefined path and the request to display the value selection user interface satisfies the first criterion, it initiates the execution of the predefined operation using the first value. The process includes: initiating a process to perform a predefined operation using a second value based on the determination that the value selector is at the second point on the predefined path and the request to display the value selection user interface satisfies the first criterion; initiating a process to perform a predefined operation using a third value based on the determination that the value selector is at the first point on the predefined path and the request to display the value selection user interface satisfies the second criterion; and initiating a process to perform a predefined operation using a fourth value based on the determination that the value selector is at the second point on the predefined path and the request to display the value selection user interface satisfies the second criterion.

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

[0017] Therefore, faster and more efficient methods and interfaces are provided for managing accounts on such devices, thereby improving their effectiveness, efficiency, and user satisfaction. These methods and interfaces can complement or replace other methods used for account management. Attached Figure Description

[0018] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals indicate corresponding parts in all the drawings.

[0019] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some embodiments.

[0020] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0021] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0022] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0023] Figure 4A An exemplary user interface for a menu on an application on a portable multifunction device, according to some implementation schemes, is shown.

[0024] Figure 4B An exemplary user interface for a multifunctional device having a touch-sensitive surface separate from the display is shown according to some embodiments.

[0025] Figure 5A A personal electronic device according to some implementation schemes is shown.

[0026] Figure 5B This is a block diagram illustrating a personal electronic device according to some implementation schemes.

[0027] Figure 6 An exemplary device connected via one or more communication channels according to some implementation schemes is shown.

[0028] Figures 7A to 7DAn exemplary user interface for managing remote data storage associated with user accounts is shown according to some implementation schemes.

[0029] Figures 8A to 8AK An exemplary user interface for managing user accounts is shown according to some implementation schemes.

[0030] Figure 9 This is a flowchart illustrating a method for managing user accounts according to some implementation schemes.

[0031] Figures 10A to 10H An exemplary user interface for managing the deletion of data from a remote data store associated with a user account, according to some implementation schemes, is shown.

[0032] Figures 11A to 11R An exemplary user interface for managing balance transfers in a user account, according to some implementation schemes, is shown.

[0033] Figures 12A to 12B This is a flowchart illustrating a method for managing user accounts according to some implementation schemes. Detailed Implementation

[0034] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0035] Electronic devices need to provide efficient methods and interfaces for managing accounts. For example, they need convenient and efficient methods for managing remote data storage associated with user accounts. They also need simpler technologies for managing the deletion of data from remote data storage associated with user accounts, and convenient and efficient methods for managing balance transfers within user accounts. Such technologies can reduce the cognitive burden on users managing and using user accounts on electronic devices, thereby increasing productivity. Furthermore, such technologies can reduce processor and battery power wasted otherwise on redundant user input.

[0036] under Figures 1A to 1B , Figure 2 , Figure 3 , Figures 4A to 4B , Figures 5A to 5B and Figure 6 A description of an exemplary device for implementing technologies for managing accounts is provided. Figures 7A to 7D An exemplary user interface for managing remote data storage associated with user accounts is shown. Figures 8A to 8AK An exemplary user interface for managing user accounts is shown. Figure 9This is a flowchart illustrating a method for managing user accounts according to some implementation schemes. Figures 7A to 7D and Figures 8A to 8AK The user interface in the document is used to illustrate the processes described below, including... Figure 9 The process in. Figures 10A to 10H An exemplary user interface is shown for managing the deletion of data from a remote data store associated with a user account. Figures 11A to 11R An exemplary user interface for managing balance transfers in user accounts is shown. Figure 12 is a flowchart illustrating a method for managing user accounts according to some implementation schemes. Figures 10A to 10H and Figures 11A to 11R The user interface is used to illustrate the processes described below, including the process shown in Figure 12.

[0037] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch may be named a second touch and similarly, a second touch may be named a first touch, without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

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

[0039] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0040] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc. (Cupertino, California). ® Devices, iPod Touch ® Devices and iPads ® Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0041] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0042] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0043] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0044] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 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 strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface 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.

[0045] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity 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 tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited physical space, which is used (e.g., on a touch-sensitive display) to display an indication and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0046] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, has not moved. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception of a typical (or common) user.

[0047] It should be understood that device 100 is merely an example of a portable multifunctional device, and 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 these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

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

[0049] Peripheral interface 118 can be used to couple the device's input and output peripherals to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data. In some embodiments, 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.

[0050] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but 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, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular phone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), and 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 Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

[0051] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data is optionally retrieved by peripheral interface 118 from and / or transmitted to memory 102 and / or RF circuitry 108. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset with both output (e.g., a single-ear headphone or a dual-ear headphone) and input (e.g., a microphone).

[0052] I / O subsystem 106 couples input / output peripherals on device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from / send electrical signals to the other input control device 116. The other input control device 116 optionally includes physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click dials, etc. In some alternative embodiments, input controller 160 is optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing device such as mouse. One or more buttons (e.g., Figure 2 Optionally, 208) includes increase / decrease buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include a push-button (e.g., Figure 2 (206 in the middle).

[0053] A quick press of the push button optionally disengages the touchscreen 112 from its lock or optionally initiates a process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application 11 / 322,549 (i.e., U.S. Patent No. 7,657,849), filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A long press of the push button (e.g., 206) optionally powers the device 100 on or off. The function of one or more buttons is optionally user-customizable. The touchscreen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0054] 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 sends electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

[0056] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the iPhone from Apple Inc. (Cupertino, California). ®and iPod Touch ® The technology used.

[0057] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles a multi-touch-sensitive touchpad described in the following U.S. patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

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

[0059] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally use any suitable object or accessory such as a stylus, finger, etc., to interact with touchscreen 112. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

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

[0061] The device 100 also includes a power system 162 for supplying 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 recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0062] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0063] The device 100 may optionally also include one or more depth camera sensors 175. Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touchscreen display, and selfies with depth map data are captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the position of depth camera sensor 175 may be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

[0064] In some implementations, a depth map (e.g., a depth map image) contains information (e.g., values) relating to the distance of objects in the scene from the viewpoint (e.g., a camera, optical sensor, depth camera sensor). In one implementation of the depth map, each depth pixel defines the location of its corresponding two-dimensional pixel on the Z-axis of the viewpoint. In some implementations, the depth map consists of pixels, where each pixel is defined by a value (e.g., 0 to 255). For example, a "0" value represents the pixel furthest from the viewpoint (e.g., a camera, optical sensor, depth camera sensor) in the "3D" scene, and a "255" value represents the pixel closest to the viewpoint in the "3D" scene. In other implementations, the depth map represents the distance between objects in the scene and the plane of the viewpoint. In some implementations, the depth map includes information about the relative depth of various features of the object of interest within the field of view of the depth camera (e.g., the relative depth of the eyes, nose, mouth, and ears of a user's face). In some implementations, the depth map includes information that enables the device to determine the contour of the object of interest in the z-direction.

[0065] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0066] The device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

[0067] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0068] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "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 view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of device 100.

[0069] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication 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 program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

[0070] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0071] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is for use with an iPod. ® (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0072] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or a contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0073] In some implementations, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., determining whether the user has “clicked” an icon). In some implementations, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some specific implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0074] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0075] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0076] In some implementations, 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 to specify the graphic to be displayed, and, if necessary, also receives coordinate data and other graphic attribute data, and then generates screen image data for output to the display controller 156.

[0077] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0078] Optionally, the text input module 134, a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

[0079] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to phone 138 for use in location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services, such as weather desktop apps, local yellow pages desktop apps, and map / navigation desktop apps).

[0080] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof: • Contacts module 137 (sometimes called address book or contact list); • Telephone module 138; • Video conferencing module 139; • Email client module 140; • Instant Messaging (IM) module 141; • Fitness support module 142; • Camera module 143 for still images and / or video images; • Image management module 144; • Video player module; • Music player module; • Browser module 147; • Calendar module 148; • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6. • Desktop Mini Program Creator Module 150 for creating user-created desktop mini programs 149-6; • Search module 151; • Video and music player module 152, which combines a video player module and a music player module; • Notepad module 153; • Map module 154; and / or • Online video module 155.

[0081] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0082] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in the application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

[0083] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0084] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

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

[0086] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0087] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness; and displaying, storing, and transmitting fitness data.

[0088] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions 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.

[0089] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0090] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0091] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0092] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, desktop applet module 149 is optionally a micro-application downloaded and used by a user (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a user-created micro-application (e.g., user-created desktop applet 149-6). In some embodiments, the desktop applet includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop applet includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! desktop applet).

[0093] Combining RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134 and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

[0094] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) according to user instructions.

[0095] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions allowing users 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 instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0096] Combining the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0097] Combining RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135 and browser module 147, map module 154 is optionally used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0098] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage 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. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0099] Each of the above modules and applications corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the aforementioned modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0100] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push-buttons, dials, etc.) on device 100 can be optionally reduced.

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

[0102] Figure 1B This is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0103] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

[0104] In some implementations, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or ready to be displayed by the application 136-1, a state queue for enabling the user to return to the previous state or view of the application 136-1, and a repeat / undo queue for the user's previous actions.

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

[0106] In some implementations, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other implementations, peripheral device interface 118 transmits event information only when a significant event occurs (e.g., receiving input above a predetermined noise threshold and / or receiving input for a predetermined duration).

[0107] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

[0108] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that the user can see on the display.

[0109] 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 the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected is optionally referred to as the hit view, and the set of events identified as correct input is optionally determined at least in part based on the hit view of the initial touch that initiates a touch-based gesture.

[0110] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming 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 to which it was identified as the hit view.

[0111] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0112] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

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

[0114] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0115] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0116] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0117] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0118] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

[0119] In some implementations, the definition of the corresponding event (187) also includes a delay action that delays the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0120] When the corresponding event recognizer 180 determines that the sub-event sequence does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

[0121] In some embodiments, the corresponding event recognizer 180 includes metadata 183 having configurable attributes, flags, and / or lists instructing how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing how or how event recognizers can interact with each other. In some embodiments, the metadata 183 includes configurable attributes, flags, and / or lists instructing whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0122] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

[0123] In some implementations, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined procedure.

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

[0125] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other implementations, they are included in two or more software modules.

[0126] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0127] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0129] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0130] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial 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 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which 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, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference)) are described. Figure 1A The contact strength sensor 165 is mentioned above. 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 disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

[0131] Figure 3Each of the elements described above is optionally stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to an instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subgroup of the modules and data structures described above. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0132] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

[0133] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof: • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals; • Time 404; • Bluetooth indicator 405; • Battery status indicator 406; • Tray 408 with icons for frequently used applications, such as: o The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages; o An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails; o The browser module 147's icon 420 labeled "Browser"; and o The video and music player module 152 (also known as the iPod module 152, a trademark of Apple Inc.) with an icon 422 labeled "iPod"; and • Icons of other applications, such as: o IM module 141's icon 424 labeled "Message"; o Calendar module 148 has an icon 426 labeled "Calendar"; o Image management module 144 icon 428 labeled "Photo"; o The icon 430 of the camera module 143 is labeled "camera"; o The icon 432 of the online video module 155 is labeled "Online Video"; o The icon 434 in the Stock Market Desktop Mini Program 149-2 that is labeled "Stock Market"; o Map module 154's icon 436 labeled "map"; o Weather desktop mini-program 149-1, icon 438 marked as "weather"; o The alarm clock desktop mini-program 149-4 has an icon 440 marked as "clock"; o The icon 442 of the fitness support module 142 is labeled "fitness support"; o The notepad module 153 has an icon 444 labeled "Notepad"; and o The icon 446, labeled "Settings," is used to set up applications or modules, providing access to settings for device 100 and its various applications 136.

[0134] It should be pointed out that, Figure 4A The icon labels shown are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0135] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices such as tablets or touchpads 355 Figure 3 An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0136] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450) with the spindle on the display (e.g., 451). Figure 4BThe main axis corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the diagram, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451 in the middle) and the display of a multi-functional device (e.g., Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may be optionally used for other user interfaces described herein.

[0137] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these 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 a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0138] Figure 5A An exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A to 4B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface operations on device 500.

[0139] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

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

[0141] Figure 5B An exemplary personal electronic device 500 is illustrated. In some embodiments, device 500 may include a reference... Figure 1A , Figure 1B and Figure 3Some or all of the components described herein. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive components 522 and optionally have an intensity sensor 524 (e.g., a contact intensity sensor). Furthermore, I / O portion 514 may be connected to communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may optionally be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may optionally be a button.

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

[0143] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described below, including processes 900 and 1200. Figure 9 and Figures 12A to 12B A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0144] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figure 1A , Figure 3 and Figures 5A to 5BA user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0145] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that 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, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0146] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity decreases). The characteristic intensity of the 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 value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon its execution) rather than to determine whether to perform the first or second action.

[0147] In some implementations, a portion of the gesture is identified to determine the 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 contact intensity 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, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally 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: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0148] Optionally, the contact intensity on a touch-sensitive surface is characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0149] An increase in contact intensity from below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact intensity from below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact intensity from below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

[0150] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0151] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and an operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and an operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0152] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0153] Figure 6 Exemplary devices are illustrated, connected via one or more communication channels to participate in transactions according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field) and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0154] Electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes one or more of the following: a person's or company name, a billing address, a login name, a password, an account number, an expiry date, a security code, a telephone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some embodiments, payment account information includes images, such as photographs of payment cards (e.g., photographs taken by and / or received by the device). In some embodiments, the electronic device receives user input that includes at least some payment account information (e.g., receiving user-input credit, debit, account, or shopping card number and expiry date). In some embodiments, the electronic device detects at least some payment account information from an image of the payment card (e.g., captured by the device's camera sensor). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or server). In some implementations, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio and / or video files), where the user or the user device's account has previously made purchases for that other service or has identified payment account data.

[0155] In some implementations, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), such that the payment account information is securely stored on the electronic device. In some implementations, after a user initiates such a process, the electronic device transmits the payment account information to a transaction coordination server, which then communicates with a server (e.g., a payment server) operated by the account's payment network to ensure the validity of the information. The electronic device is optionally configured to receive scripts from a server that allows the electronic device to program the account's payment information onto a secure element.

[0156] In some implementations, communication between devices 100, 300, and 500 facilitates transactions (e.g., general or specific transactions). For example, a first electronic device (e.g., 100) may be used as a configuration or management device and may send new or updated payment account data (e.g., information about new accounts, updated information about existing accounts, and / or warnings about existing accounts) to a second electronic device (e.g., 500). Alternatively, the first electronic device (e.g., 100) may send data to the second electronic device reflecting information about a payment transaction facilitated at the first electronic device. This information may optionally include one or more of the following: payment amount, account used, purchase time, and whether the default account has been changed. The second device (e.g., 500) may optionally use such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0157] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, devices may communicate using Bluetooth connectivity 608 (e.g., including traditional Bluetooth connectivity or Bluetooth Low Energy connectivity) or using a WiFi network 606. Communication between user devices may optionally be modulated to reduce the likelihood of inappropriate sharing of information between devices. For example, communication regarding payment information may require the communicating devices to be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0158] In some embodiments, electronic devices (e.g., 100, 300, 500) communicate with a point-of-sale (POS) payment terminal 600, which optionally supports NFC. This communication may optionally utilize various communication channels and / or technologies. In some embodiments, the electronic devices (e.g., 100, 300, 500) use NFC channel 610 to communicate with the payment terminal 600. In some embodiments, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with the electronic devices (e.g., 100, 300, 500). The electronic devices (e.g., 100, 300, 500) are optionally configured to transmit signals to the payment terminal 600, including payment information of a payment account (e.g., a default account or an account selected for a specific transaction).

[0159] In some implementations, continuing the transaction includes transmitting a signal containing payment information, including an account such as a payment account. In some implementations, continuing the transaction includes reconfiguring an electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (e.g., an NFC-enabled contactless payment card), and then transmitting the account credentials via NFC to, for example, a payment terminal 600. In some implementations, after transmitting the account credentials via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before reconfiguring it to respond as a contactless payment card via NFC).

[0160] In some embodiments, the generation and / or transmission of the signal is controlled by a secure element in an electronic device (e.g., 100, 300, 500). Prior to issuing payment information, the secure element optionally requests specific user input. For example, the secure element optionally requests: detection of a worn electronic device, detection of a button press, detection of a password input, detection of a touch, detection of one or more option selections (e.g., option selections received during interaction with an application), detection of a fingerprint signature, detection of a voice or voice command, and / or detection of a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) is established with another device (e.g., payment terminal 600) within a defined time period from the detection of input, the secure element issues payment information for transmission to the other device (e.g., payment terminal 600). In some embodiments, the secure element is a hardware component controlling the issuance of secure information. In some embodiments, the secure element is a software component controlling the issuance of secure information.

[0161] In some implementations, the protocols associated with transaction participation depend on, for example, the device type. For instance, the conditions for generating and / or transmitting payment information may differ for wearable devices (e.g., device 500) and telephones (e.g., device 100). For example, the generation and / or transmission conditions for wearable devices may include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for telephones do not require a button press but rather require detecting a specific interaction with the application. In some implementations, the conditions for transmitting and / or publishing payment information include receiving specific input from each of a plurality of devices. For example, publishing payment information may optionally require detecting a fingerprint and / or password at one device (e.g., device 100) and mechanical input (e.g., button press) at another device (e.g., device 500).

[0162] Payment terminal 600 optionally uses payment information to generate a signal to be transmitted to payment server 604, thereby determining whether the payment is authorized. Payment server 604 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether a proposed purchase is authorized. In some embodiments, payment server 604 includes a server of an issuing bank. Payment terminal 600 communicates directly with payment server 604 or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).

[0163] Payment server 604 optionally uses at least some of the payment information from the payment information to identify a user account from a database of user accounts (e.g., 602). For example, each user account includes payment information. Accounts are optionally located by locating accounts that have specific payment information that matches the information from the POS communication. In some implementations, payment is refused when the provided payment information is inconsistent (e.g., the expiry date does not correspond to a credit card number, debit card number, or shopping card number) or when no account includes payment information that matches the information from the POS communication.

[0164] In some implementations, user account data further identifies one or more constraints (e.g., credit limit); current or previous balance; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen); and / or authorization instructions. In some implementations, the payment server (e.g., 604) uses this data to determine whether to authorize a payment. For example, the payment server may refuse payment if adding a purchase amount to the current balance would result in exceeding the account limit, if the account is frozen, if previous transaction amounts exceed a threshold, or if the number or frequency of previous unusual transactions exceeds a threshold.

[0165] In some implementations, payment server 604 responds to POS payment terminal 600 with indications of whether the proposed purchase is authorized or rejected. In some implementations, POS payment terminal 600 signals to electronic devices (e.g., 100, 300, 500) to identify the result. For example, when a purchase (e.g., via a transaction coordination server managing transactions on a user device) is authorized, POS payment terminal 600 sends a receipt to electronic devices (e.g., 100, 300, 500). In some cases, POS payment terminal 600 presents an output indicating the result (e.g., visual or audio output). Payment may be transmitted to the merchant as part of the authorization process or may be transmitted later.

[0166] In some implementations, electronic devices (e.g., 100, 300, 500) participate in transactions completed without involving the POS payment terminal 600. For example, upon detecting received mechanical input, a secure element in the electronic device (e.g., 100, 300, 500) issues payment information to allow an application on the electronic device to access that information (e.g., and transmit that information to a server associated with the application).

[0167] In some implementations, the electronic device (e.g., 100, 300, 500) is in a locked or unlocked state. In the locked state, the electronic device is powered on and operable, but it is prevented from performing a predefined set of operations in response to user input. This predefined set of operations may include navigating between user interfaces, activating or deactivating a predefined set of functions, and activating or deactivating certain applications. The locked state can be used to prevent unintentional or unauthorized use of certain functions of the electronic device, or to activate or deactivate certain functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and operable, and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed when in the locked state.

[0168] When a device is in a locked state, it is said to be locked. In some implementations, a locked device can respond to user input from a restricted group, including input corresponding to an attempt to switch the device to an unlocked state or input corresponding to turning off the device.

[0169] In some implementations, the secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some implementations, the secure element provides (or publishes) payment information (e.g., account and / or transaction-specific dynamic security codes). In some implementations, the secure element provides (or publishes) payment information in response to receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; double pressing of a hardware button when the device is unlocked, and optionally while the device has been continuously on the user's wrist since being unlocked by providing authentication credentials, wherein the device's continued presence on the user's wrist is determined by periodically checking contact between the device and the user's skin). For example, the device detects a fingerprint at the device's fingerprint sensor (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint matches a registered fingerprint. Based on the determination that the fingerprint matches a registered fingerprint, the secure element provides (or publishes) payment information. Based on the determination that the fingerprint does not match a registered fingerprint, the secure element abandons providing (or publishing) payment information.

[0170] As used herein, "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application using an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the computer system's operating system.

[0171] Now let’s turn our attention to the implementation of user interfaces (“UIs”) on electronic devices, such as portable multifunction devices 100, 300 or 500, and the associated processes.

[0172] Figures 7A to 7D Exemplary user interfaces for managing remote data storage associated with user accounts (e.g., computer storage management accounts) are shown according to some implementation schemes. The user interfaces in these figures are used to illustrate the following description, including... Figure 9 The process in this context. In some cases, the computer storage management account may be referred to as a computer storage account, data storage management account, data storage account, etc.

[0173] like Figures 7A to 7D As shown, an exemplary user interface for managing remote data storage associated with a user account is represented as a view of the corresponding user interface on an exemplary date (e.g., January 15, 2020). In the various figures disclosed herein, representative dates are used to indicate exemplary dates on which the corresponding user interface is viewed, for example, as... Figures 7A to 7D , Figures 8A to 8AK , Figures 10A to 10H and Figures 11A to 11R As shown. It should be understood that dates are indicated as non-limiting examples to aid in understanding the sequence of events associated with the corresponding user interface and the corresponding disclosure illustrated in the accompanying drawings.

[0174] Figure 7A An electronic device 100 with a display (e.g., a touchscreen 112) is shown. Figure 7A In this embodiment, electronic device 100 is displaying a summary user interface 710 on display 112. In some embodiments, the summary user interface 710 includes a representation 704 of a user account (e.g., a computer storage account), a usage indicator user interface element 712, a past usage user interface element 714, an account details user interface element 715, a deletion user interface element 716, and a list of stored data 720. In some embodiments, the term "user interface element" refers to "enabled representation".

[0175] In some implementations, a user account is a computer storage account that provides access to a predetermined amount of computer storage resources (e.g., cloud-based). In some implementations, the user account is used to store and / or archive data to computer storage resources accessible via the user account (e.g., remote, cloud-based computer storage resources not local to electronic device 100) and to delete data from computer storage resources. In some implementations, the data can be of different types, such as data corresponding to photo files, data corresponding to document files, data corresponding to music files, data corresponding to video files, and data corresponding to application files.

[0176] In some implementations, user accounts are associated with different data retention policies for managing data stored on computer storage resources. For example, in some implementations, a first type of data (referred to herein as "standard data") is associated with a data retention policy in which a user-selectable standard amount of data should be deleted periodically (e.g., monthly). For example, the user is presented with an option to select the standard amount of data to be deleted monthly, but at least a minimum standard amount of data needs to be deleted (e.g., 5% of the remaining amount of stored standard data). Standard data may include, for example, data corresponding to photo files, data corresponding to document files, data corresponding to music files, data corresponding to video files, and data corresponding to application files. In some implementations, a second type of data (referred herein as "chunk data") is associated with a data retention policy in which chunks of data are scheduled to be partially deleted periodically (e.g., monthly) until all chunks of data are deleted. When chunks of data become deletable, the portion of the chunk to be deleted is converted into standard data (e.g., added to the remaining amount of standard data), which is available for deletion according to the data retention policy for standard data. Chunks of data may include, for example, large amounts of related data, such as large photo albums. In some implementations, data retention policies for standard data and block data allow for different data usage quotas, such as 2GB of storage space for standard data and 5GB for block data.

[0177] In some implementations, indicator user interface element 712 is used (e.g., similar to the one referenced below). Figure 8D The described balance indicator user interface element 812 includes a current indication (e.g., measured in megabytes (MB) or gigabytes (GB)) of the amount of computer storage resources currently used to store archived data associated with a user account (e.g., a computer storage account), and an indication of the available amount of computer resources, which may also represent the user account's usage quota—a predetermined limit on the amount of computer storage resources that can be used via the user account (e.g., the computer storage account). Figure 7AIn this context, a portion of a user account's (e.g., a computer storage account) usage quota—that is, a portion of the computer storage resources associated with the user account—is storing data. Figure 7A In the illustrated implementation, the indicator user interface element 712 distinguishes between standard data and block data usage by indicating "block" next to the block data amount. In this example, 1.5GB of the 2.0GB usage quota is used for standard data, as indicated by the indicator user interface element 712. Specifically, the indicator user interface element 712 indicates (e.g., by showing "1.5GB") that 1.5GB of computer storage resources associated with the user account is being used for standard data, and (e.g., by showing "500MB available") that 500MB of computer storage resources associated with the user account are still available for standard data. By indicating that 1.5GB is used and 500MB is available, the indicator user interface element 712 indicates that the user quota for standard data is 2GB (the sum of 1.5GB and 500MB). The indicator 712 also indicates (e.g., by showing "2.5GB block") that 2.5GB of computer storage resources associated with the user account is being used for block data. In some implementations, an indication of available block data is optionally displayed. For example, if the usage quota for block data is 5GB, indicator 712 can optionally display "2.5GB block available" to indicate the available margin of block data.

[0178] In some implementations, the user interface element 714 has historically included a bar chart depicting the types of stored and / or archived data associated with a user account (e.g., a computer storage account) that have been stored on available computer storage resources associated with the user account during a predetermined time period (e.g., the past week). These data types include data corresponding to photo files, data corresponding to document files, data corresponding to music files, data corresponding to video files, and data corresponding to application files. Each bar corresponds to the usage of computer storage resources associated with the user account during a corresponding day within the predetermined time period.

[0179] In some implementations, the account details user interface element 715 may be selected (e.g., similar to the one referenced below). Figure 8D The user interface element 815 describes the account details to display additional details about the user account (e.g., computer storage account).

[0180] In some implementations, user interface element 716 is removed (e.g., similar to the reference below). Figure 8DThe described balance transfer user interface element 816 includes an indication of a date before which a certain amount of archived data should be deleted from the user account (e.g., a computer storage account) to avoid storage penalties (e.g., reduction of the user account's usage quota). See below for reference. Figures 10A to 10H A more detailed description of the features of deleting user interface element 716 is provided.

[0181] In some implementations, the stored data list 720 (e.g., similar to the one referenced below) Figure 8D The described list of transfer items 720 shows multiple recent user account activities corresponding to requests to store (or delete) data on computer storage resources associated with a user account (e.g., a computer storage account). In this example, the stored data list 720 includes a first previously stored data item 720A corresponding to a first type of data (e.g., data corresponding to photo files) of a first amount (e.g., 150MB) stored on computer storage resources associated with a user account (e.g., a computer storage account). In this example, the stored data list 720 also includes a second previously stored data item 720B corresponding to a second type of data (e.g., data corresponding to document files) of a second amount (e.g., 3MB) stored on computer storage resources associated with a user account (e.g., a computer storage account).

[0182] like Figure 7A As shown, each request in the request to store a data item includes a date that indicates, for example, the date on which a request was made to store or delete the corresponding data item to or from computer storage resources associated with the user account (or when the corresponding storage or deletion operation was completed).

[0183] In some implementations, items in the stored data list 720 may represent previously stored data items that have been deleted (or requested to be deleted) from computer storage resources associated with a user account. For example, the stored data list 720 may include a third previously stored data item 720C that corresponds to a first type of data (e.g., data corresponding to photo files) of a first amount (e.g., 10 MB) that has been requested to be deleted from computer storage resources associated with a user account.

[0184] like Figure 7A As shown, device 100 detects input 702 (e.g., a tap gesture) at a location corresponding to the second previously stored data item 720B. In response, Figure 7B In the process, device 100 displays a data type summary user interface 725 (e.g., similar to the reference below). Figure 8KThe merchant user interface 836 is described. In this example, the data type summary user interface 725 corresponds to the data type summary user interface for data corresponding to a document file (e.g., data of a second type), the data corresponding to the document file being... Figure 7A The data type of the second previously stored data item 720B is selected.

[0185] like Figure 7B As shown, the data type summary user interface 725 includes a representation 727 of document file data types, which optionally corresponds to an application used to view / edit / create document file data types (e.g., word processing documents, PDF documents, etc.).

[0186] In some implementations, the data type summary user interface 725 also includes a data item details user interface element 730, which provides... Figure 7A Details regarding the second previously stored data item 720B selected. (For example...) Figure 7B As shown, the item details user interface element 730 includes a first portion 730A that displays details of a second previously stored data item 720B, such as an indication of the data size of the second previously stored data item 720B (e.g., 3MB) and the time (e.g., “yesterday”) when the second previously stored data item 720B was stored in (or deleted from) a computer storage resource associated with the user account. In some embodiments, the first portion 730A can be selected to view additional details related to a request to store (or delete) the second previously stored data item 720B.

[0187] The project details user interface element 730 also includes a second portion 730B that shows an image 731 of a document (e.g., a second previously stored data item 720B) stored in (or deleted from) a computer storage resource associated with a user account. In some embodiments, image 731 is an accurate (e.g., exactly or substantially similar) visual representation of the stored document, including text, images, or any other content visible in the stored document. In other words, image 731 is a visual representation of the document showing what a user would see if they opened and viewed the document requested to be stored (or deleted) at the computer storage resource associated with their account.

[0188] In some implementations, the item details user interface element 730 also includes a third part 730C, which provides options for viewing additional details related to a request to store (or delete) a second past data item 720B at a computer storage resource associated with the user account.

[0189] like Figure 7BAs shown, device 100 detects input 732 and, in response, returns to summary user interface 710, as follows. Figure 7C As shown.

[0190] exist Figure 7C In the process, device 100 detects input 734 on the first previously stored data item 720A. In response, Figure 7D In this example, device 100 displays a data type summary user interface 725. The data type summary user interface 725 corresponds to a data type summary user interface for data corresponding to a photo file (e.g., data of a first type), where the data corresponding to the photo file is... Figure 7C Select the data type of the first previously stored data item 720A.

[0191] exist Figure 7D In the data type summary user interface 725, there is a representation 736 of the photo file data type, which optionally corresponds to an application used to view / edit / create data of the photo file data type (e.g., image, photo).

[0192] exist Figure 7D In the data type summary user interface 725, there is a data item details user interface element 730, which is shown updated to provide information related to... Figure 7C Details regarding the first previously stored data item 720A selected. For example... Figure 7D As shown, the first section 730A illustrates details of a first previously stored data item 720A, such as an indication of the data size of the first previously stored data item 720A (e.g., 150 MB) and the time (e.g., "today") when the first previously stored data item 720A was stored in (or deleted from) a computer storage resource associated with a user account. In some embodiments, the first section 730A may be selected to view additional details related to a request to store (or delete) the first previously stored data item 720A.

[0193] The project details user interface element 730 also includes a second portion 730B that shows an image 735 of a photograph (e.g., a first previously stored data item 720A) stored in (or deleted from) a computer storage resource associated with the user account. In some embodiments, image 735 is an accurate (e.g., exactly or substantially similar) visual representation of the stored photograph, including the content visible in the stored photograph. In other words, image 735 is a visual representation of the photograph that shows what a user would see if they opened and viewed the photograph requested to be stored in the computer storage resource associated with the user account.

[0194] In some implementations, the item details user interface element 730 also includes a third part 730C that provides options for viewing additional details related to a request to store (or delete) a first past data item 720C at a computer storage resource associated with the user account.

[0195] Figures 8A to 8AK Exemplary user interfaces for managing user accounts (e.g., transfer accounts) according to some implementation schemes are shown. The user interfaces in these figures are used to illustrate the following descriptions, including... Figure 9 The process of...

[0196] In some implementations, the user account is a transfer account. In some implementations, the transfer account is a first-party credit account (e.g., a revolving credit account issued or branded by, for example, an electronics manufacturer) and rewards are offered based on the amount of transfers made using the transfer account (e.g., payment transactions, points transfers) (e.g., cash back rewards, extra points rewards) (e.g., cash back rewards based on a specific percentage of the value of each transaction). In some implementations, the transfer account is a points account that offers rewards based on the amount of points used with the transfer account (e.g., points rewards) (e.g., points for dining, printer credits, membership points).

[0197] Figure 8A A device 100 with a display (e.g., a touchscreen 112) is shown. Figure 8A In this configuration, device 100 displays a purchase confirmation user interface 802 on display 112, which is shown to provide a user interface that allows a user to initiate a transfer to obtain (e.g., purchase) an item. Figure 8A In the example shown, the purchase (e.g., a transfer) is split into two payment transactions (e.g., transfers). The first payment transaction is a standard payment transaction, where the first part of the purchase is fulfilled via immediate (or near-immediate) payment (e.g., via credit transfer) to the transfer account (e.g., the first part is charged / billed / etc. to the transfer account). Figure 8AIn the example shown, the tax portion 802A of the purchase (e.g., $65.77) is payable immediately, as indicated by the now-pay portion 802B. The second payment transaction is an installment payment plan, in which the installment portion of the purchase (e.g., the loan amount) is satisfied by accumulating equal portions of the periodically (e.g., monthly) satisfied installments of the purchase until the entire installment balance is satisfied. In the implementation discussed herein, each portion of the installment amount is referred to as an installment payment, and the transfer used to satisfy the installment payment is referred to herein as an installment payment transfer or installment payment transaction. It can be said that the installment payment plan is partially satisfied by each installment payment made. When all installments are satisfied, the installment payment plan is fully satisfied (e.g., paid out). Figure 8A In the illustrated implementation, the installment payment section 802C indicates the terms of the installment plan, showing a loan amount of $511 divided into twenty-four monthly installments (e.g., approximately $21.30 per installment), commencing on December 31. In other words, the first installment (an equal portion of the $511) is billed to the transfer account on December 31. The payment source section 802D indicates that the purchase (e.g., the $65.77 now due and the installment plan) is charged to a “credit card” associated with the transfer account. In other words, the purchase for which a “credit card” is charged is fulfilled through a credit transfer from the transfer account. In some implementations, installment transfers to the transfer account do not incur interest, while non-installment transfers are subject to interest.

[0198] Now for reference Figure 8B The main screen user interface 803 is displayed, which shows notifications 806 and 808. In some embodiments, notifications 806 and 808 are initiated... Figure 8A The purchase is generated after the purchase is made for display purposes (e.g., by double-pressing a button on one side of device 100 while displaying the purchase confirmation user interface 802).

[0199] Notice 806 provides information about... Figure 8A Information about installment payment plans associated with telephone purchases. For example, such as... Figure 8B As shown, Notice 806 indicates the name of the merchant (e.g., Electronics Store), the product purchased (e.g., a telephone), the account to which the purchase is charged (e.g., a credit card (debit account)), and the terms of the installment plan, including the installment amount (e.g., $21.30), the frequency (e.g., monthly), and the date on which the first installment or the next installment will be charged to the debit account (e.g., at the end of the month).

[0200] Notice 808 provides information about Figure 8AInformation regarding the non-installment portion of a telephone purchase. Specifically, Notification 808 indicates the merchant's name (e.g., Electronics Store), the account to which the purchase is charged (e.g., credit card (debit account)), and the amount charged to that account (e.g., $65.77). Since the transaction is not an installment transaction, $65.77 is charged to the debit account without significant delay.

[0201] In some implementations, notification 806 or notification 808 may be selected to display a user interface associated with the transaction that caused the notification, such as a merchant user interface (e.g., Figure 8K The merchant user interface 836 shown), and the account summary user interface (e.g., Figure 8D The outline user interface 810 shown) or the virtual wallet user interface (e.g., Figure 8C The virtual wallet user interface shown is 805.

[0202] exist Figure 8C In this embodiment, device 100 is displaying a virtual wallet user interface 805 on display 112, which is the user interface for a transfer application (e.g., an electronic or virtual wallet application). In some embodiments, the virtual wallet user interface 805 is displayed in response to the detection of input on a notification such as notification 806 or notification 808. In some embodiments, the virtual wallet user interface 805 includes a representation 804 of transfer accounts. In some embodiments, the virtual wallet user interface 805 includes representations of different accounts configured on the electronic device, including: different transfer accounts configured on or linked to the electronic device 100 (e.g., payment accounts, such as third-party credit card accounts, debit card accounts and / or stored-value accounts; points accounts; rewards accounts), stored-value accounts issued (or branded) by first-party manufacturers, and other accounts (e.g., other transfer accounts, points cards, rewards cards), ID cards (e.g., student IDs, government-issued IDs), and / or tickets (e.g., event tickets, boarding passes).

[0203] exist Figure 8C In the middle, device 100 detects input 809 on the representation 804 of the transfer account and, in response, displays... Figure 8D The summary user interface 810 of the transfer account (e.g., a display panel user interface).

[0204] exist Figure 8DIn the illustrated implementation, the summary user interface 810 includes a representation 804 of a user account (e.g., a transfer account), a balance summary user interface element 812 (e.g., a balance module), a recent transaction activity user interface element 814 (e.g., an activity module), an account details user interface element 815, a balance transfer user interface element 816 (e.g., a balance payment module), and a list of transfer items 820 (e.g., transaction history). In some implementations, the summary user interface 810 also includes notification user interface elements (e.g., ...). Figure 8G The notification user interface element 818 in the middle.

[0205] The balance summary user interface element 812 provides a current indication of the current balance of the transfer account, and in some implementations includes an indication of the installment balance of any installment plans associated with the transfer account. Figure 8D In the balance summary user interface element 812, the current balance of the transfer account (e.g., card balance) is $65.77, the available balance of the account (e.g., available credit) is $434.23, and the currently unpaid installment payment balance is $511. Figure 8D In the middle, the card balance of $65.77 corresponds to Figure 8A The tax portion of the purchase was made in [location], and the transfer account has a credit limit of $500 (calculated as the sum of the current balance of $65.77 and the available balance of $434.23). The installment balance of $511 corresponds to [amount]. Figure 8A The remaining balance of the installment payment plan when purchasing the project. Figure 8D The user interface shown is from December 25, 2019. Therefore, Figure 8D The image shows the card balance and installment balance before the first installment payment of the installment plan incurs a charge on December 31st, as shown. Figure 8A and Figure 8B As shown.

[0206] In some implementations, the activity user interface element 814 (e.g., activity module) includes a bar chart depicting transfer activity (e.g., payment activity) of a transfer account (e.g., a first-party credit account; a points account) during a predetermined time period (e.g., the past week), where each bar corresponds to a transfer (e.g., a payment transaction, points transfer) that occurred during a corresponding day within the predetermined time period, and different colors are used to represent different types of transfers based on the category of each transfer.

[0207] In some implementations, the balance transfer user interface element 816 (e.g., the balance payment module) includes an indication (e.g., text) of when the next balance transfer (e.g., balance payment) to the transfer account (e.g., a first-party credit account, a points account) is due (e.g., the next bill due date). In some implementations, the balance transfer user interface element 816 includes an indication that the balance transfer is due if the balance transfer has already expired (e.g., at least a portion of the previous bill balance has not been paid by the due date). In some implementations, the balance transfer user interface element 816 includes an indication of the amount of that portion of the next balance transfer if a portion (but not all) of the next balance transfer has been made (e.g., a portion but not all of the bill balance has been paid). In some implementations, the balance transfer user interface element 816 includes an indicator 816A indicating (e.g., in text such as “Pay,” “Pay in Advance,” “Pay More,” and / or symbols such as checkmarks or exclamation marks) the status of the balance transfer (e.g., whether the balance payment is currently due, whether the balance payment is due urgently, or whether the balance payment has been made). Figure 8D In the code, indicator 816A displays "Advance Payment," indicating that a balance transfer can be applied to the account balance (e.g., a payment to the account balance), but the balance transfer is not yet due. See below for further details. Figures 11A to 11R A more detailed description of the features of element 816 of the balance transfer user interface.

[0208] In some implementations, the electronic device 100 also displays notification user interface elements (e.g., notification modules) in the summary user interface 810, which display notifications or optimizations regarding the transfer account (e.g., a first-party credit account; a points account), and optionally, display an indication (e.g., a "Get Help" sign) for seeking assistance using the transfer account (e.g., contacting customer service). Examples of notification user interface elements are shown in... Figure 8G As shown in the figure, and described in more detail below.

[0209] exist Figure 8DIn the illustrated implementation, multiple transfers (e.g., payment transactions, points transfers) have previously been performed using a transfer account (e.g., a first-party credit account, a points account). Therefore, the electronic device 100 displays a list 820 (also referred to as a transaction list) of individual transfer items (e.g., a single transaction item) and / or group transfer items (e.g., a group transaction item) in a summary user interface 810, where a single transfer item corresponds to a single past transfer made using the transfer account (e.g., a single past payment transaction, a single past points transaction), and a group transfer item corresponds to multiple past transfers (e.g., multiple past payment transactions, multiple past points transfers) made using the transfer account in a shared category (e.g., shopping, groceries, dining, travel, education, entertainment). In some implementations, the items in the transfer item list 820 are arranged chronologically, such that the item corresponding to the most recent transfer (e.g., the most recent payment transaction, the most recent points transfer) is displayed at the top of the list. For example, in... Figure 8D In the transfer item list 820, the first transfer item 820A is shown (for example, corresponding to...). Figure 8A The transactions are: a tax payment transaction made at an Electronics Store when purchasing a phone, a second transfer item 820B (e.g., a balance transfer (e.g., credit) to the balance of a transfer account), and a third transfer item 820C (e.g., a payment transaction made at Glasses Guys), wherein the first transfer item 820A corresponds to the most recent transfer made using the transfer account (e.g., a first-party credit account; a points account) (e.g., the most recent payment transaction, the most recent points transfer), and the third transfer item 820C corresponds to the oldest transfer made using the transfer account.

[0210] Now for reference Figure 8E Device 100 displays the main screen UI 803. The main screen UI 803 shows December 31, 2019, and displays First Installment Payment Notification 821, indicating that the first installment payment of the installment plan has been added (e.g., with electricity) to the December balance of the transfer account. Specifically, First Installment Payment Notification 821 indicates the purchased product (e.g., phone), the account to which the installment payment was added (e.g., credit card (transfer account)), and details of the installment payment transaction, including the installment payment amount (e.g., $21.30), the monthly balance affected by the added installment payment (e.g., December balance), the date the installment payment is charged to the transfer account (e.g., now), and the sequence of installments in the installment plan (e.g., 1 / 24).

[0211] In some implementations, a similar notification is generated each time an installment payment is added to the transfer account (e.g., monthly, until the installment plan is fully paid off). In some implementations, subsequent installment payment notifications may include details different from those shown in the first installment payment notification 821. For example, in Figure 8F When a second installment payment is added to the transfer account, a second installment payment notification 822 is generated on January 31, 2020. Second installment payment notification 822 indicates the product purchased (e.g., a phone), the merchant (e.g., an Electronics Store), the account to which the installment payment is added (e.g., a credit card (transfer account)), the installment amount (e.g., $21.30), the date the installment payment will be charged to the transfer account (e.g., now), and the sequence of installments in the installment plan (e.g., 2 / 24). Compared to the first installment payment notification 821, the second installment payment notification 822 adds the merchant but omits the monthly balance affected by the added installment payment.

[0212] Refer again Figure 8E Device 100 detects input 823 on the first installment payment notification 821 and, in response, displays... Figure 8G The summary user interface 810.

[0213] exist Figure 8G In the current balance summary user interface element 812, the balance is updated to show a balance of $87.07, which is the sum of the previous balance (e.g., $65.77) and the new installment payment transaction ($21.30). Therefore, the installment payment balance is reduced by the installment payment transaction amount, showing an installment payment balance of $489.70. Additionally, a notification user interface element 818 is displayed, indicating that the first installment payment of $21.30 has been added to the current monthly balance of the transfer account, and the transfer item list 820 is updated to include a fourth transfer item 820D corresponding to the installment payment transaction $21.30. In some implementations, the notification user interface element 818 includes an option to view the details of the installment payment. Figure 8G As shown, the fourth transfer item 820D illustrates the details of the transfer, including instructions to the merchant (Electronics Store), identification of the installment plan (telephone installment), the installment transfer amount, the installment sequence (1 / 24), and optional instructions for rewards associated with the transfer (e.g., 3% of the transfer amount).

[0214] exist Figure 8G In the process, device 100 detects input 824 on balance summary user interface element 812 and, in response, displays... Figure 8H Balance details user interface 825.

[0215] like Figure 8H As shown, the balance details user interface 825 includes card balance details 826, which provides details of the current balance of the transfer account. For example, in Figure 8H In this context, card balance details 826 include current card balance 826A, monthly balance 826B, new spending 826C, and credit 826D. In some implementations, card balance 826A is the total unpaid balance of transfers charged to the transfer account (offset by credit 826D), monthly balance 826B is the current month's billing balance (e.g., the amount of balance transfers due this month), new spending 826C is the total amount of transfers charged to the transfer account this month, and credit 826D is any balance transfers applied to the transfer account during the current month (e.g., settlement, credit).

[0216] The balance details user interface 825 also includes installment payment balance 828 and credit data 830, which indicates the credit limit of the transfer account, the balance 830A on the transfer account, and the amount of credit available for the transfer account. In some embodiments, balance 830A represents the card balance (e.g., card balance 826A). In some embodiments, balance 830A represents the sum of the card balance (e.g., card balance 826A) and the unpaid installment payment balance 828.

[0217] The balance details user interface 825 also includes bill 832. Figure 8H In the process, device 100 detects input 833 on the December bill 832A, which is the current bill for that month, and in response, displays... Figure 8I The billing user interface 834 is shown in some implementations. The billing user interface 834 displays details of the current month's bill, including, for example, the bill balance, date range, new spending for the month, interest charged to the transfer account for the month, payments and credits applied to the transfer account for the month, and rewards earned for the month (e.g., cash rewards).

[0218] Now for reference Figure 8J Device 100 displays something similar to Figure 8G The outline user interface 810 shown is shown, but there is no notification user interface element 818, and the transfer item list 820 expands to show transfer items 820A-820D. Figure 8J As shown, device 100 detects input 835 on the third transfer item 820C and, in response, displays... Figure 8K Merchant user interface 836.

[0219] like Figure 8K As shown, the merchant user interface 836 includes a representation 837 of the merchant associated with the selected transfer item. Figure 8KIn the embodiment shown, the third transfer item 820C corresponds to the purchase of sunglasses from, for example, a Glasses Guys retail store in Cupertino, CA. Therefore, the merchant user interface 836 displays a Glasses Guys sign 837A.

[0220] The merchant user interface 836 also includes a purchase user interface element 838, which includes a first portion 838A containing details of the transaction, such as the location of the purchase, the date of the purchase, and the purchase amount. In some implementations, the first portion 838A can be selected to view additional details about the transaction (see, for example, see...). Figure 8Z (and related public information), such as digital receipts for transactions.

[0221] The purchase user interface element 838 also includes a second part 838B that shows details of the purchased item. For example, the second part 838B shows an image 838B-1 of sunglasses purchased using a third transfer item 820C. In some embodiments, the image of the sunglasses looks substantially identical to the actual purchased item, showing sunglasses with the style, color, size, or any other visible item attributes purchased. The second part 838B also includes text describing some of the attributes of the purchased item, such as style (e.g., style XY2.1) and purchase date (December 25, 2019). In some embodiments, the second part 838B may include a representation of the merchant or a map showing the approximate location of the purchased item (e.g., sunglasses). If, for example, details of the purchased item are not available, a map or a representation of the merchant may be displayed instead of image 838B-1.

[0222] In some implementations, the purchase user interface element 838 also includes a third section 838C, which is an optional option to view additional details about the purchase. The merchant user interface 836 also includes a list 839 of previous transfers associated with Glasses Guys, including a first list 839A corresponding to the third transfer item 820C. In some implementations, a list (e.g., list 839A) can be selected to view additional details about the transaction (e.g., see...). Figures 8AA to 8AD (and related public information), such as digital receipts for transactions.

[0223] like Figure 8K As shown, device 100 detects input 840 and, in response, in Figure 8L The summary user interface 810 is displayed in the middle, which is similar to Figure 8J The outline user interface 810 shown is shown.

[0224] like Figure 8LAs shown, device 100 detects input 841 on the fourth transfer item 820D, which, as previously discussed, corresponds to an installment transfer added to the December balance of the transfer account. In response to the detection of input 841, in Figure 8M In the middle, device 100 displays and Figure 8K The merchant user interface 836 shown is similar, but updated to reflect details associated with the fourth transfer item 820D, rather than the details associated with the third transfer item 820C. For example, the merchant user interface 836 shows a representation 837B of the retailer (merchant) Electronics Store from which a telephone purchase was made. Additionally, the merchant user interface 836 includes an installment purchase user interface element 842, which is similar to the purchase user interface element 838, but updated to include details related to installment transfers.

[0225] For example, the purchase user interface element 842 includes a first portion 842A that provides transaction details for the installment payment transfer, such as a representation of the time the transfer occurred (e.g., the time the installment was added to the card balance of the transfer account), the sequence of the installments (e.g., 1 / 24), and the installment payment transfer amount (e.g., $21.30). In some implementations, the first portion 842A can be selected to view additional details about the transaction (e.g., see...). Figure 8Z (and related public information), such as digital receipts for transactions.

[0226] The purchase user interface element 842 also includes a second part 842B that shows details of the item associated with the installment purchase. For example, the second part 842B shows an image 842B-1 of a phone purchased using an installment plan associated with the fourth transfer item 820D (installment transfer). In some embodiments, the image of the phone looks substantially identical to the actual purchased phone, showing a phone with the style, color, size, or any other visible product attributes. The second part 842B also includes text describing some of the attributes of the purchased item, such as the device name (e.g., Emily's phone), model (e.g., Model 1), storage capacity (e.g., 128GB), color (e.g., blue), and purchase date (December 25, 2019). Thus, image 842B-1 shows the purchased phone, which is Model 1, has 128GB of storage, and is blue. In some embodiments, the second part 842B may include a representation of the merchant or a map showing the approximate location of the purchased item (e.g., the phone). If, for example, details of the purchased goods are unavailable, a map or a representation of the merchant may be displayed instead of image 842B-1. In some embodiments, the second part 842B shows images of multiple goods included in the transaction (e.g., see...). Figures 8AI to 8AJ(and related public disclosures).

[0227] like Figure 8M As shown, the installment purchase user interface element 842 also includes a third part 842C, which is an optional option to view additional details about the installment purchase.

[0228] The merchant user interface 836 also includes a list 843 of previous transfers associated with the Electronics Store, including a first list 843A corresponding to an installment transfer (e.g., fourth transfer item 820D), and previous lists 843B and 843C corresponding to previous transfers associated with the Electronics Store (previous list 843B corresponds to the initial tax purchase associated with the installment purchase). In some implementations, a list (e.g., list 843A) can be selected to view additional details about the transaction (e.g., see...). Figures 8AA to 8AD (and related public information), such as digital receipts for transactions.

[0229] exist Figure 8M In the middle, device 100 detects input 844 on the third part 842C of the installment purchase UI element, and in response, displays Figure 8N Installment payment details user interface 845.

[0230] like Figure 8N As shown, the installment payment details user interface 845 includes a representation of goods purchased using the installment payment plan. Figure 8N In the illustrated embodiment, the representation is a phone representation 846. In some embodiments, representation 846 includes a representative image 846-1 of the phone and text describing the phone's attributes. The representative image 846-1 is similar to image 842B-1, but shown from a different angle. Thus, like image 842B-1, the corresponding image 846-1 shows an image of a phone purchased using an installment plan, appearing substantially identical to the actual purchased phone (e.g., having the style, color, size, or any other visible phone attributes). In some embodiments, the text describing the phone's attributes may include the device name (e.g., Emily's phone), model (e.g., Model 1), storage capacity (e.g., 128GB), and color (e.g., blue).

[0231] The installment payment details user interface 845 also includes an installment payment progress user interface element 847 indicating the progress of the installment payment plan. The installment payment progress user interface element 847 is updated in real time when the balance of the installment payment plan is changed. The installment payment progress user interface element 847 includes the accumulated installment payment balance 847A, the remaining installment payment balance 847B, the next installment payment details 847C, the loan amount 847D, and the installment payment progress bar 848. The accumulated installment payment balance 847A represents the total amount already disbursed to the transfer account in the installment payment plan, including the current installment payment. Figure 8N As shown, only the first installment has been billed, therefore the accumulated installment balance 847A is the amount of the first installment, $21.30. The remaining installment balance 847B is calculated by subtracting the accumulated installment balance 847A ($21.30) from the loan amount 847D (511). Figure 8N In the implementation shown, the remaining installment balance 847B is $489.70. The loan amount 847D is the total amount of the installment plan, and is the sum of the accumulated installment balance 847A and the remaining installment balance 847B. The next installment details 847C provide details of the next installment, such as the amount of the next installment (e.g., $21.30) and the date the next installment will be billed to the transfer account (e.g., January 31).

[0232] The installment payment details user interface 845 also includes an installment payment progress bar 848, which provides a visual representation of the progress toward the completion (e.g., fulfillment) of the installment payment plan. The installment payment progress bar 848 includes a shaded area 848-1 representing the accumulated installment payment balance 847A and a non-shaded area 848-2 representing the remaining installment payment balance 847B. The installment payment progress bar 848 is updated in real time to reflect changes in the accumulated installment payment balance 847A and the remaining installment payment balance 847B.

[0233] The installment details user interface 845 also includes an installment history 849, which provides a list of previous installment transactions for the installment plan. Figure 8N In the installment history 849, the first installment transfer 849-1 is included, which shows the details of the first installment transfer, such as the amount of the first installment transfer ($21.30), the time when the transfer occurred (e.g., 10 hours ago), and the sequence of installments (e.g., "1 / 24", meaning the first installment in a series of twenty-four installments).

[0234] The installment payment details user interface 845 also includes an installment payment payment user interface element, which is an optional step to initiate an additional payment process to the installment plan. Additional details of this process are discussed below.

[0235] exist Figure 8N In the process, device 100 detects input 851 on the first installment payment transfer 849-1 and, in response, displays... Figure 8O Installment payment receipt user interface 852.

[0236] exist Figure 8O In this context, the installment payment receipt user interface 852 essentially provides an electronic receipt for the installment purchase, which displays the loan amounts 853A and 853B and details 854, such as the merchant, the date of the installment purchase, and the time of the installment purchase (in some embodiments, the date and time shown indicate the date and time when the selected installment transfer (first installment transfer 849-1) occurred). The installment payment receipt user interface 852 also includes a purchase details user interface element 855, which provides a breakdown of the purchased goods and additional details related to the installment purchase.

[0237] like Figure 8O As shown, the purchase details user interface element 855 includes a first part 855A, a second part 855B, and a third part 855C. The first part 855A includes installment payment information, such as the instruction that the receipt is used for an installment plan, the length of the installment plan (24 months), and any interest rate (0% APR) applied to the installment plan. The first part 855A also includes details of the purchased item, such as the instruction for the item (e.g., a telephone), the purchase price of the item (e.g., $599.00), and other identifying information, such as the device's serial number (e.g., #123456ABCD), model (e.g., model 1), storage capacity (e.g., 128GB), and color (e.g., blue). The first part 855A also indicates any credit applied to the purchase, such as a trade-in credit for another item (e.g., another telephone) to offset a portion of the telephone purchase associated with the installment plan. Figure 8O In the implementation shown, Part 855A instructs a trade-in value of $200 to be applied to the purchase of the app, which offsets $200 of the installment plan amount. Therefore, Part 855A instructs that the subtotal of the installment plan, calculated by subtracting the $200 credit from the purchase price of the phone at $599, is $399. Part 855A also instructs the use of any rewards earned from the purchase (e.g., cash rewards, points rewards), such as a 3% cash reward of $11.97.

[0238] Part 2, 855B, illustrates any additional purchases associated with the installment plan and any rewards earned from such purchases. For example, in Figure 8O Part 2, 855B, shows that an accident protection device (e.g., insurance for the equipment) was purchased for $112, and a $3.06 bonus was earned on the purchase of the accident protection device.

[0239] Part 3, 855C, indicates the total loan amount and the total reward earned. The total loan amount, 853B, is calculated as the sum of the subtotal in Part 1, 855A ($399) and the additional purchases in Part 2, 855B ($112). Similarly, the total reward earned is calculated as the sum of the rewards in Part 1, 855A and the rewards in Part 2, 855B.

[0240] Purchase details user interface element 855 also includes total installment payments 856A and total balance 856B, which correspond to the accumulated installment payment balance and the unpaid installment payment balance (the remaining balance of the installment payment plan), respectively.

[0241] The purchase details user interface element 855 also includes optional options 857 for reporting problems with the installment plan or otherwise requesting assistance, such as making changes to the installment plan.

[0242] In some implementations, one or more elements of the installment receipt user interface 852 are static and do not change because they represent a snapshot of the corresponding installment details at the time of the installment transaction. For example, Total Outflow 856A and Total Remaining 856B may represent the status of the installment plan associated with the installment receipt at the time of the installment transaction. Figure 8O In this context, Total Outflow 856A and Total Remaining 856B represent the status of the installment plan as of December 31, 2019, when the first installment payment transfer 849-1 occurred. However, if the installment payment receipt user interface 852 then displays a receipt corresponding to, for example, an installment payment transfer that occurred on October 28, 2019, Total Outflow 856A and Total Remaining 856B will show the exact balance as of October 28, 2019. It should be understood that Total Outflow 856A and Total Remaining 856B are used herein as examples, and in some implementations, these balances may be updated to reflect the current total outflow and total remaining balance to date.

[0243] In some implementations, one or more elements of the installment payment receipt user interface 852 are dynamic and update in real time as changes are made to the installment payment plan. For example, Figure 8PThe updated installment receipt user interface 852 is shown after a change to the installment plan has been made (e.g., by selecting option 857 and initiating the plan change). For example, the updated installment receipt user interface 852 can be automatically displayed after initiating a change to the installment plan, or after subsequently selecting the first installment transfer 849-1. Specifically, Figure 8P This illustrates an implementation scenario where the installment plan is updated due to the cancellation of incident protection after the initial purchase and implementation of the installment plan. Therefore, the purchase details user interface element 855 is updated to include a fourth section 855D, which indicates that the credit 855D-1 is $112 and the reward offset 855D-2 is $3.06 to account for the loss of rewards initially earned from the purchase utilizing incident protection. The $3.06 reward offset 855D-2 affects the total reward balance in the third section 855C. Therefore, the total reward balance in the third section 855C is updated to $11.97. Similarly, because incident protection is included as part of the installment plan, the return / cancellation of incident protection affects the loan balance and thus the remaining balance of the installment plan. Therefore, lengths 853A and 853B, as well as the total remaining balance 856B, are updated to reflect the removal of $112 of incident protection from the loan amount, resulting in a new loan amount of $399 and a new remaining installment plan balance of $377.70.

[0244] exist Figure 8P In the middle, device 100 detected input 858 and, in response, displayed... Figure 8Q Installment payment details user interface 845.

[0245] like Figure 8Q As shown, the installment details user interface 845 is updated to reflect the changes to the installment plan discussed above. Specifically, the remaining installment balance 847B is reduced to $377.70, and the installment progress bar 848 is updated to reflect the correct proportion of the billed installment balance 847A relative to the remaining installment balance 847B. Therefore, the shaded area 848-1 of the progress bar increases proportionally, and the unshaded area 848-2 decreases proportionally. In addition, the next installment details 847C is updated to show the revised amount of the next installment transaction, which is now $16.42 (calculated as the new remaining installment balance 847B divided by the number of installments in the remaining installment transactions in the installment plan (23)), and the loan amount 847D is changed to $399. It is worth noting that there are no changes to other details, such as the accumulated billed installment balance 847A or the installment history 849.

[0246] Now for reference Figure 8RDevice 100 displays on display 112 an implementation where the installment details user interface 845 is shown on October 31, 2020, a date after the eleventh installment transfer has been added to the transfer account (e.g., the eleventh installment transfer of the installment plan has been satisfied (e.g., paid)). As Figure 8R As shown, the accumulated installment payment balance 847A is updated to $185.50, which is the sum of all eleven installment payment transfers up to October 31, 2020 (e.g., the first installment payment of $21.30 plus the subsequent ten installments of $16.42 each). The remaining installment payment balance 847B is correspondingly reduced to $213.50, and the installment payment progress bar 848 is updated to reflect the current ratio of the outstanding installment payment balance 847A to the remaining installment payment balance 847B. The next installment payment details 847C are updated to show that the next installment payment will be added to the transfer account on November 30. Finally, the installment payment history 849 has been updated to show the previous installment payment transfers 849-9, 849-10, and 849-11 corresponding to the ninth, tenth, and eleventh installment payment transfers, respectively.

[0247] exist Figure 8R In the middle, device 100 detected input 859 on the eleventh installment payment transfer 849-11, and in response, displayed Figure 8S Installment payment receipt user interface 852.

[0248] exist Figure 8S In the embodiment shown, the installment payment receipt user interface 852 is similar to Figure 8P The interface shown has updated total bill balance 856A and total remaining balance 856B, which are now updated to show current balances of $185.50 and $213.50, respectively.

[0249] Now for reference Figure 8T Device 100 shows on display 112 an implementation of a user interface 845 that displays installment payment details after the installment plan has been fully satisfied (e.g., paid). Figure 8TAs shown, the accumulated installment payment balance 847A is updated to $399, which is the sum of all twenty-four installment payment transfers. The remaining installment payment balance 847B is correspondingly reduced to $0.00, and the installment payment progress bar is replaced with marker 860 (e.g., a checkmark and text indicating "Completed"), indicating that the installment payment plan has been completed. The next installment payment details 847C are updated to show the date the final installment payment occurred (e.g., November 30, 2021). Finally, the installment payment history 849 has been updated to show the previous installment payment transfers 849-22, 849-23, and 849-24 corresponding to the last three installment payment transfers of the installment payment plan.

[0250] exist Figure 8T In the middle, device 100 detected input 861 on the 24th installment payment transfer 849-24, and in response, displayed Figure 8U Installment payment receipt user interface 852.

[0251] exist Figure 8U In the embodiment shown, the installment payment receipt user interface 852 is similar to Figure 8P and Figure 8S The interface shown has updated total bill balance 856A and total remaining balance 856B, which are now updated to show current balances of $399 and $0.00, respectively.

[0252] Now for reference Figure 8V Device 100 displays the summary user interface 810 shown on December 31, 2019 on display 112. Device 100 detects input 862 on account details user interface element 815 and, in response, displays... Figure 8W Account details user interface 863.

[0253] like Figure 8W As shown, the account details user interface 863 displays details about the transfer account, such as options for viewing the virtual card number associated with the transfer account, billing address information, options for contacting the bank associated with the transfer account, and option 865 for viewing the installment payment plans associated with the transfer account. In some embodiments, option 865 includes an indication of the number of installment payment plans associated with the transfer account. Figure 8W In the illustrated implementation, the transfer account is associated with three installment payment plans. The detailed user interface 863 also includes optional options 864A and 864B (shown with option 864A selected) for use in the view of account details (such as...). Figure 8W Switch between views of (as shown) or transactions associated with a transfer account (e.g., transfers similar to those shown in Transfer Items List 820).

[0254] exist Figure 8W In the middle, device 100 detects input 866 on option 865 and, in response, displays... Figure 8X The installment payment plan user interface 867.

[0255] exist Figure 8X In the installment plan user interface 867, three different installment plans are displayed for the transfer account. The first installment plan option 868-1 corresponds to the installment plan for a phone. Option 868-1 includes some details of the phone, such as the device name (“Emily’s Phone”), model (Model 1), storage capacity (128GB), and color (blue). In some embodiments, option 868-1 also includes a representative image 869-1 of the phone, which in some embodiments has the same physical appearance as the phone associated with the first installment plan. The second installment plan option 868-2 corresponds to a different phone installment plan. Option 868-2 includes some details of the phone, such as the device name (“John’s Phone”), model (Model 2), storage capacity (64GB), and color (black). In some embodiments, option 868-2 also includes a representative image 869-2 of the phone, which in some embodiments has the same physical appearance as the phone associated with the second installment plan. The third installment plan option 868-3 corresponds to the installment plan for the tablet computer. Option 868-3 includes some details of the tablet computer, such as the device name (“Emily’s Tablet Computer”), model (Model A), storage capacity (128GB), and color (white). In some embodiments, option 868-3 also includes a representative image 869-3 of the tablet computer, which in some embodiments has the same physical appearance as the tablet computer associated with the third installment plan. In some embodiments, each installment plan option (e.g., 868-1 to 868-3) can be selected to view the installment plan details user interface (e.g., similar to...) corresponding to the selected installment plan option. Figure 8N The installment payment details user interface (845) is shown in the example. In some implementations, each installment payment plan option (e.g., 868-1 to 868-3) can be selected to view the merchant user interface corresponding to the selected installment payment plan option, as discussed below.

[0256] exist Figure 8X In the middle, device 100 detects input 870 on the first installment payment plan option 868-1, and in response, displays Figure 8Y The merchant user interface 836 is similar to Figure 8M As shown in the Merchant User Interface 836 discussed above.

[0257] like Figure 8Y As shown, device 100 detects input 871 on the first part 842A of the installment purchase user interface element 842, and in response, displays... Figure 8Z The transaction details user interface 872.

[0258] like Figure 8Z As shown, the transaction details user interface 872 displays details of the installment payment transaction with the merchant indicated in the merchant user interface 836. Specifically, the transaction details user interface 872 displays transaction details 873, which indicate the amount ($21.30, which is the amount of the first installment), the merchant (Electronics Store), and the date / time of the transaction (11:55 AM on December 31, 2019). The transaction details user interface 872 also displays an information user interface element 874 that identifies the transaction as an installment payment transaction (credit card installment payment), indicates the installment sequence (1 / 24) and the amount of the installment payment transaction ($21.30), and indicates whether interest is charged on the transaction. The transaction details user interface 872 also includes an option 875 that provides identification of the corresponding installment payment plan (e.g., similar to...). Figure 8X Option 868-1 of the first installment payment plan.

[0259] exist Figure 8Z In the middle, device 100 detected input 876 and, in response, displayed... Figure 8AA The merchant user interface 836 is similar to Figure 8Y The interface shown.

[0260] exist Figure 8AA In the process, device 100 detects input 877 on a past transfer item 843B and, in response, displays a transaction details user interface 872, which is similar to... Figure 8Z The interface shown has been updated to reflect the transaction details of past transfer item 843B. For example, in Figure 8AB In the transaction details user interface 872, transaction details 873 are displayed, indicating the transaction amount ($65.77, which is the tax charged when purchasing the phone associated with the installment plan), the merchant (Electronics Store), and the date / time of the transaction (10:09 AM on December 25, 2019). The transaction details user interface 872 also displays an information user interface element 874 that identifies the transaction as associated with the initial tax used to purchase the phone, indicates the transaction amount ($65.77), and indicates whether interest is charged on the transaction. The transaction details user interface 872 also includes an option 875 to provide identification of the corresponding installment plan (e.g., similar to...). Figure 8XOption 868-1 of the first installment payment plan.

[0261] Now for reference Figure 8AC Device 100 displays the merchant user interface 836 shown on January 17, 2020 on display 112. Merchant user interface 836 is similar to... Figure 8AA The interface shown differs in that past transfer item 843D has been added to the past transfer item list 843. Figure 8AC In the implementation scheme shown, past transfer item 843D corresponds to the above regarding... Figure 8O The adjustment discussed pertains to trade-in credit applied to the initial purchase of a telephone. For example, if the trade-in device is not received or is in poor condition, the credit is adjusted by charging a transfer account (e.g., a transfer associated with past transfer item 843D) to offset at least a portion of the initial $200 credit applied to the purchase of the telephone.

[0262] exist Figure 8AC In the middle, device 100 detected input 878 on past transfer item 843D and, in response, displayed Figure 8AD The transaction details user interface 872.

[0263] like Figure 8AD As shown, the transaction details user interface 872 is similar to Figure 8AB The interface shown is updated to reflect the transaction details of past transfer item 843D. For example, in Figure 8AD In the transaction details user interface 872, transaction details 873 are displayed, indicating the transaction amount ($100, which is the amount of the adjustment to the trade-in credit applied to the initial purchase of the phone associated with the installment plan), the merchant (Electronics Store), and the date / time of the transaction (January 17, 2020, 10:00 AM). The transaction details user interface 872 also displays an information user interface element 874 that identifies the transaction as associated with the adjustment to the trade-in credit, indicates the transaction amount ($100), and indicates whether interest is charged on the transaction. The transaction details user interface 872 also includes an option 875 to provide identification of the corresponding installment plan (e.g., similar to...). Figure 8X The first installment plan option 868-1 in the plan. In some implementations, transactions associated with past transfer item 843D are added to the transfer balance associated with the transfer account, and therefore interest is charged to the transfer account for that transaction. In some implementations, transactions associated with past transfer item 843D cause an adjustment to the loan amount associated with the installment plan (e.g., similar to the adjustment regarding the first installment plan option 868-1). Figure 8PThe returned items under the accident protection plan discussed are therefore not added to the balance of the transfer account and no interest is charged to the transfer account. In some implementations, the information user interface element 874 includes additional information, such as an explanation of why the transaction occurred (e.g., the trade-in value was adjusted due to additional damage to the trade-in device).

[0264] Now for reference Figure 8AE The device 100 displays a summary user interface 810 via a display 112. The summary user interface 810 is similar to the embodiment described above, except that transfer items 820-1 and 820-2 have been added to the transfer item list 820, and the balance summary user interface element 812 has been updated to reflect the additional transfers of $9.99 and $10.00 associated with transfer items 820-1 and 820-2, respectively.

[0265] exist Figure 8AE In the illustrated implementation, transfer item 820-1 corresponds to the purchase of a music album (e.g., a "featured album") for $9.99 via a "music app". In some implementations, the "music app" is an app accessible to device 100 for purchasing and optionally playing music content (e.g., songs). Transfer item 820-2 corresponds to the purchase of two movies for $10.00 via a "movie store". In some implementations, the "movie store" is an app accessible to device 100 for purchasing and optionally playing video content (e.g., movies).

[0266] exist Figure 8AE In the middle, device 100 detected input 879 on transfer item 820-1 and, in response, displayed... Figure 8AF Merchant user interface 836.

[0267] like Figure 8AF As shown, the merchant user interface 836 is similar to the above implementation scheme, but updated to show the corresponding... Figure 8AE The selected transfer item 820-1 contains details of the associated music purchase. For example, the purchase user interface element 838 includes a first part 838A, which includes transaction details such as the name of the purchased item (e.g., “Featured Album”), the date of purchase, and the purchase amount.

[0268] The purchase user interface element 838 also includes a second portion 838B that shows details of the purchased item. For example, the second portion 838B shows an image 838B-2 of an album purchased using transfer item 820-1. In some embodiments, the album image looks substantially identical to the actual purchased album, showing the album with the purchased style, color, size, or any other visible product attributes. In some embodiments, the second portion 838B may include a representation of the merchant or a map showing the approximate location of the purchased item (e.g., the album). If, for example, details of the purchased item are not available, a map or a representation of the merchant may be displayed instead of image 838B-2.

[0269] exist Figure 8AF In the illustrated implementation, the third part 838C' is an optional option (e.g., a "Open Music App" option) to initiate playback of the purchased item. For example, selecting... Figure 8AF The third part 838C' can launch the "Music Application" to initiate playback of purchased albums on device 100. In some implementations, playback of purchased albums can be initiated by selecting image 838B-2.

[0270] The merchant user interface 836 also includes a list 839 of previous transfers 839-1, 839-2, and 839-3 associated with the "Music App". Figure 8AF In the implementation shown, the previous transfer 839-1 corresponds to the purchase represented in the purchase user interface element 838 and associated with transfer 820-1 (e.g., the purchase of "Featured Albums").

[0271] exist Figure 8AF In the middle, device 100 detected input 880 on transfer item 839-1 and, in response, displayed... Figure 8AG The transaction details user interface 872 displays details of the transaction associated with the previous transfer 839-1 (e.g., transfer 820-1).

[0272] Now for reference Figure 8AH The device 100 displays a summary user interface 810 via a display 112, which is similar to Figure 8AE The interface shown is displayed, and input 881 is detected on transfer item 820-2. In response to the detection of input 881 on transfer item 820-2, device 100 displays merchant user interface 836, as shown. Figure 8AI As shown.

[0273] like Figure 8AI As shown, the merchant user interface 836 is similar to the above implementation scheme, but updated to show the corresponding... Figure 8AH The selected transfer item 820-2 details the movie purchase associated with it. Figure 8AI In the illustrated implementation, transfer 820-2 corresponds to a single (e.g., one-time) transfer for purchasing multiple movies (e.g., requesting to purchase multiple movies simultaneously, or requesting to purchase multiple movies on different days). Therefore, the second portion 838B of the purchase user interface element 838 displays details of the purchased item, including, for example, images 883 and 884, each representing a movie purchased using transfer 820-2. Image 883 is a visual representation of the first purchased movie, showing, for example, an illustration or screenshot associated with the first movie. Similarly, image 884 is a visual representation of the second purchased movie, showing, for example, an illustration or screenshot associated with the second movie. The second portion 838B also includes pagination points 882 that indicate that the second portion 838B is a scrollable area that can be manipulated (e.g., scrolled) to display images 883 and 884, as discussed in more detail below.

[0274] exist Figure 8AI In the user interface shown, the third part 838C′′ is an optional feature (e.g., "Open Music App" enabled) to initiate playback of a movie from the purchased movies. For example, selecting... Figure 8AI The third part 838C'' of the device 100 launches a "music application" (e.g., replacing the user interface 836 with an application for the "music application") to initiate playback of a movie corresponding to the image 883 shown in the center of the second part 838B. In some embodiments, playback of a purchased movie can be initiated by selecting the corresponding image 883 / 884 in the second part 838B.

[0275] exist Figure 8AI In the middle, image 883 is displayed in the center of the second part 838B. Device 100 detects input 885 (e.g., a swipe gesture) on the second part 838B and, in response, updates the second part 838B to display image 884 in the center of the second part 838B, as shown. Figure 8AJ As shown.

[0276] exist Figure 8AJ In the process, device 100 detects input 886 on the first part 838A and, in response, displays... Figure 8AK The transaction details user interface 872 displays the details of the transaction associated with transfer 820-2.

[0277] exist Figure 8AKIn the illustrated implementation, information user interface element 874 shows two components of the transfer: a first request to purchase a first movie (“The Family Dog”) (indicated by detail 887-1) and a second request to purchase a second movie (“Sports Documentary”) (indicated by detail 887-2). Detail 887-1 indicates a request to purchase (e.g., including processing and availability for viewing) the first movie on December 28, 2019. Detail 887-2 indicates a request to purchase (e.g., including processing and availability for viewing) the second movie on December 30, 2019. Transaction detail 873 indicates that the transfer for purchasing both movies is processed as a single transfer at 10:09 AM on December 31, 2019 (e.g., transfer 820-2). Thus, the purchase of both movies was requested on different days (e.g., and available for viewing on those corresponding dates), and a single transfer was processed on a subsequent date to pay for the purchase of both movies. Therefore, the information user interface element 874 shows a separate receipt for transfer 820-2 with two movie purchases, wherein the requests for movie purchases were processed on different dates, and the corresponding transfers for the two purchases were processed into a single transaction for the two purchases on a subsequent date.

[0278] Figure 9 This is a flowchart illustrating a method for managing user account usage using an electronic device according to some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500) having a display device (e.g., 112) and one or more input devices (e.g., a touchscreen of display 112). Some operations in method 900 may be combined, some operations may be changed in order, and some operations may be omitted.

[0279] As described below, Method 900 provides an intuitive way to manage user accounts. This method reduces the cognitive burden on users when managing user accounts, thus creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to manage user accounts faster and more efficiently saves power and increases the time interval between battery charging sessions.

[0280] An electronic device (e.g., 100) displays (902) a first user interface (e.g., 710, 810) corresponding to a user account (e.g., a data storage management account) (e.g., a transfer account, a payment account, a virtual card account) (e.g., a display panel user interface, a display panel page of a user account showing summary information of the use of the user account, a main details page of the user account) at a display device (e.g., 112). The first user interface includes: a first user interface element (e.g., 720A; 720B) (e.g., 820A; 820C; 820D; 820-1; 820-2) (e.g., a first transfer item), the first user interface element corresponding to a first task performed using the user account (e.g., a request to store first data at a remote storage database) (e.g., a past transfer; one or more past payment transactions); and a second user interface element (e.g., a different one of 720A; 720B) (e.g., a different one of 820A; 820C; 820D; 820-1; 820-2) (e.g., a second transfer item), the second user interface element corresponding to a second task performed using the user account (e.g., a second request to store second data different from the first data at a remote storage database) (e.g., a second past transfer independent of the first past transfer; one or more past payment transactions independent of the first past transfer).

[0281] In some implementations, the user account is a computer storage management account.

[0282] In some embodiments, the first task performed using the user account is a request to store first data on available computer storage resources associated with the computer storage account (e.g., an available amount of computer resources (e.g., memory) in MB or GB) (e.g., 720B). In some embodiments, the second task performed using the user account is a request to store second data, different from the first data, on available computer storage resources associated with the computer storage account (e.g., 720A).

[0283] In some implementations, the first data corresponds to a document, and the first image (e.g., 731) has the appearance of that document.

[0284] In some implementations, the second data corresponds to a photograph, and the second image (e.g., 735) has the appearance of that photograph.

[0285] When displaying the first user interface (e.g., 720A; 720B) (e.g., 820A; 820C; 820D; 820-1; 820-2), the device (e.g., 100) detects (904) the first user input (e.g., 702; 734) (e.g., 835; 841; 879; 881).

[0286] In response to the detection of first user input, the device (e.g., 100) executes (906) one or more of the items in 908 and 910 discussed below.

[0287] Based on the determination that the first user input (e.g., 702; 734) (e.g., 835; 841; 879; 881) corresponds to the selection of the first user interface element (e.g., 720A; 720B) (e.g., 820A; 820C; 820D; 820-1; 820-2), the device (e.g., 100) displays (908) a second user interface (e.g., 725) (e.g., 836) with the first image (e.g., 731; 735) (e.g., 838B-1; 842B-1; 838B-2; 883, 884) (e.g., simultaneously stopping the display of the first user interface) without displaying the second image (e.g., 731; The second image corresponds to one or more items (e.g., data, media, goods and / or services) associated with the first task performed using the user account (e.g., the first image has an appearance representing the content included in the first data requested to be stored in the first request) (e.g., the first image has an appearance representing at least one item acquired (e.g., purchased) in the first transfer), and the second image corresponds to one or more items associated with the second task performed using the user account.

[0288] Displaying a second user interface with a first image corresponding to one or more items associated with the first task performed using the user account, instead of displaying a second image associated with the second task performed using the user account, provides enhanced feedback by visually confirming to the user the items associated with the selected first task, without requiring additional input from the user (e.g., searching for product details or receipt data) to determine the items associated with the task. Providing improved visual feedback and reducing the amount of input enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0289] In some implementations, the first image represents one or more content items included in the first data. For example, the second user interface may display an image of a document requested in the first request and stored at a remote storage database. The image of the document is substantially identical to at least a portion of the document stored at the remote storage database. For example, the image of the document includes the same images, text, and other displayed content included in the actual document stored at the remote storage database. In some implementations, the first image represents one or more items acquired in the first transfer. For example, the second user interface may display an image of an electronic device purchased in the first transfer. The image of the electronic device may have the same style, color, and shape as the actually purchased electronic device. In some implementations, the second user interface may display images of multiple items acquired in the first transfer. In some implementations, the second user interface is interactive and can switch between displayed images of items in response to input (e.g., user input such as a swipe).

[0290] In some embodiments, the one or more items associated with the first request include a first electronic device (e.g., a smartphone) having multiple physical characteristics (e.g., size, color, shape). In some embodiments, the second user interface also includes information identifying the first electronic device (e.g., 842B) (e.g., a user account name or device name associated with the first electronic device). In some embodiments, the first image (e.g., 842B-1) includes a representation of the first electronic device having one or more of the multiple physical characteristics of the first electronic device (e.g., the first image is an image of the first electronic device including a representation of one or more of the physical characteristics of the first electronic device).

[0291] In some implementations, the second user interface includes a scrollable area (e.g., displaying the first image (e.g., 883)). Figure 8AI (838B in the original text), the first image corresponds to one or more items associated with the first task performed using a user account.

[0292] In some implementations, the device (e.g., 100) detects input (e.g., 885) on a scrollable area (e.g., swipe input). In response to the detection of input on the scrollable area, the device displays a third image (e.g., 884) corresponding to one or more items associated with a first task performed using a user account (e.g., scrolling the scrollable area to display a third image corresponding to one or more items, which differs from the first image corresponding to one or more items). Displaying a third image in response to the detection of input on the scrollable area allows the user to quickly and easily access multiple items associated with the first task without requiring additional input from the user to navigate different user interfaces to view / access different items. This reduces the amount of input required to view items associated with the first task. Reducing the amount of input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0293] In some embodiments, the first image (e.g., 838B-1) corresponds to one or more items associated with a first task performed using a user account; the first image is an image of the corresponding item associated with the first task. In some embodiments, the second image (e.g., 842B-1) corresponds to one or more items associated with a second task performed using a user account; the second image is an image of the corresponding item associated with the second task, different from the image of the corresponding item associated with the first task. In some embodiments, the different items associated with the first task and the second task are represented by different images. For example, the item associated with the first task could be sunglasses, and the item associated with the second task could be a smartphone. In this example, the first image is a visual representation of sunglasses, and the second image is a visual representation of a smartphone, the second image having a different appearance than the image of sunglasses.

[0294] Displaying a first image of the corresponding item associated with the first task and a second image of the corresponding item associated with the second task, distinct from the image of the corresponding item associated with the first task, provides enhanced feedback by visually confirming to the user the items associated with the corresponding first and second tasks, without requiring additional user input (e.g., searching for product details or receipt data) to determine the different items associated with the tasks. Providing improved visual feedback and reducing the amount of input enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and effectively.

[0295] Based on the determination that the first user input (e.g., 702; 734) (e.g., 835; 841; 879; 881) corresponds to the selection of the second user interface element (e.g., 720A; 720B) (e.g., 820A; 820C; 820D; 820-1; 820-2), the device (e.g., 100) displays (910) the second user interface (e.g., 725) having the second image (e.g., 731; 735) (e.g., 838B-1; 842B-1; 838B-2; 883, 884) (e.g., different from the first image). 36) Instead of displaying the first image (e.g., 731; 735) (e.g., 838B-1; 842B-1; 838B-2; 883, 884), the second image corresponds to one or more items associated with the second task performed using the user account (e.g., the second image has an appearance representing the content included in the second data requested to be stored in the second request) (e.g., the second image has an appearance representing at least one item acquired (e.g., purchased) in the second transfer), the first image corresponding to one or more items associated with the first task performed using the user account.

[0296] Displaying a second user interface with a second image corresponding to one or more items associated with the second task performed using the user account, instead of displaying a first image associated with the first task performed using the user account, provides enhanced feedback by visually confirming to the user the items associated with the selected second task, without requiring additional input from the user (e.g., searching for product details or receipt data) to determine the items associated with the task. Providing improved visual feedback and reducing the amount of input enhances device operability and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0297] In some embodiments, the second image represents one or more content items included in the second data. For example, the second user interface may display an image of a photograph requested via a second request and stored in a remote storage database. In some embodiments, the second image represents one or more items acquired in the second transfer. For example, the second user interface may display an image of an album cover corresponding to an album or song purchased in the second transfer. In some embodiments, the second user interface may display images of multiple items acquired in the second transfer. For example, the second user interface may display a first image of an album cover corresponding to a purchased song and a second image of a cover image corresponding to a purchased movie. In some embodiments, the second user interface is interactive and can (e.g., in response to input) switch between displaying an image such as an album cover image and an image of a cover image.

[0298] In some examples, the user account is a transfer account (e.g., a payment account; a virtual card account; a first-party credit account; a points account). In some implementations, the first task performed using the user account is a first transfer (e.g., 820D) (e.g., a past transfer; one or more past payment transactions). In some implementations, the second task performed using the user account is a second transfer (e.g., 820C) that is different from (e.g., independent of) the first transfer.

[0299] In some implementations, the first transfer is an installment transaction within an installment plan (e.g., 820D) (e.g., a transaction within a series of transactions (e.g., financial transactions) scheduled to be settled in regular installments over multiple periodic periods (e.g., monthly) until the installment plan purchase (e.g., debt) is fully settled). In some implementations, method 900 further includes detecting second user input (e.g., 844) while displaying a second user interface having a first image (e.g., 842B-1) (e.g., 836), the first image corresponding to one or more items associated with a first task performed using a user account. In response to detecting the second user input, the device displays an installment plan details user interface (e.g., 845) corresponding to the item associated with the installment transaction (e.g., a phone call) (e.g., an item acquired (purchased) via (e.g., all or part of) the installment transaction / plan).

[0300] In some implementations, the installment plan details user interface (e.g., 845) includes a visual representation of the items associated with the installment transaction (e.g., 846-1). Displaying a visual representation of the items associated with the installment transaction in the installment plan details user interface provides enhanced feedback by visually confirming the items associated with the installment plan to the user, without requiring additional input from the user (e.g., searching for product details or receipt data) to determine the items associated with the installment plan. Providing improved visual feedback and reducing the amount of input enhances the operability of the device and makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0301] In some implementations, the second user interface (e.g., 836) includes a first indication (e.g., 842C) (e.g., "Installment Details" indication), and the second user input (e.g., 844) corresponds to a selection of the first indication.

[0302] In some implementations, the installment plan details user interface (e.g., 845) includes a first set of installment progress data (e.g., 847A) (e.g., the amount billed to the installment plan) and a second set of installment progress data (e.g., 847B) (e.g., the remaining amount to be paid to the installment plan (e.g., the remaining balance)). In some implementations, method 900 further includes: displaying the first set of installment progress data having a first value (e.g., in...). Figure 8N847A has a value of $21.30 (e.g., the first billing amount) and second set of installment payment progress data with a second value (e.g., in...). Figure 8N After 847B has a value of $489.70 (e.g., a first remaining balance), the device performs one or more of the following: detects a third transfer performed using the user account (e.g., 849-11) (e.g., a subsequent installment payment to the transfer account); detects a request to redisplay the installment plan details user interface (e.g., a subsequent selection of the "Installment Details" enablement in the second user interface) (e.g., a request to refresh the display of the installment plan details user interface); and in response to detecting the request to redisplay the installment plan details user interface, displays the installment plan details user interface, wherein the first set of installment progress data has a first updated value (e.g., in Figure 8R 847A has a value of $185.50 (e.g., the amount of the outflow is updated (e.g., increased) to include subsequent installments to be made to the transfer account), and the second set of installment progress data has a second updated value (e.g., in...). Figure 8R 847B has a value of $213.50 (e.g., the remaining balance is updated (e.g., reduced) to reflect subsequent installments that have been billed to the transfer account) (e.g., the first update value and the second update value are determined based on the amount of the subsequent installments billed to the transfer account).

[0303] The installment plan details user interface is re-displayed, with the first set of installment progress data having a first updated value and the second set of installment progress data having a second updated value. This provides the user with the current status of the installment plan without requiring additional data input to indicate updates. Reducing the input required to perform tasks enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0304] In some implementations, the installment plan details user interface includes a visual representation of the progress toward completion of the installment plan (e.g., 848) (e.g., an installment progress bar). Displaying the installment plan details user interface with a visual representation of the progress toward completion of the installment plan provides the user with the current status of the installment plan without requiring additional data input to indicate updates. Reducing the input required to perform tasks enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0305] In some implementations, the installment plan details user interface (e.g., 845) includes a second indicator (e.g., 842A; 843A; 843B; 843C; 847D; 849-11; 849-24) (e.g., an item in the installment history) (e.g., an installment progress bar). In some implementations, the electronic device detects input pointing to the second indicator (e.g., 859; 861; 871); and in response to detecting input pointing to the second indicator, displays an installment transaction user interface (e.g., 852) including transaction details of the installment plan (e.g., 854; 855; 856A; 856B) (e.g., an installment receipt user interface). In some implementations, transaction details include one or more of the following items: purchase amount, supplier, purchase date / time, installment payment duration, itemized list of the purchased items (e.g., equipment, accident protection), identification of the purchased equipment, credit applied to the purchase (e.g., trade-in value), subtotal of loan amount, rewards / points received for the purchase, and the total of loan amount and rewards / points.

[0306] In some implementations, the transaction details of the installment plan (e.g., 855) have a first set of values ​​associated with the installment plan (e.g., the first state of the installment receipt) (e.g., such as...). Figure 8O (As shown). In some implementations, the user interface displaying installment payment transactions includes a first set of values ​​associated with the installment plan (e.g., ...). Figure 8OFollowing step 855, the device detects adjustments to one or more aspects of the installment plan (e.g., adjustments to credit applied to the installment plan) (e.g., returns / refunds of prepaid purchases (e.g., accident insurance) included in the installment plan). The device also detects a request to redisplay the installment transaction user interface (e.g., a subsequent selection of a second indication in the installment plan details user interface) (e.g., a request to refresh the display of the installment transaction user interface). In response to detecting the request to redisplay the installment transaction user interface, the device displays the installment transaction user interface (e.g., step 852), where the transaction details of the installment plan have a set of updated values ​​associated with the installment plan and based on adjustments to one or more aspects of the installment plan (e.g., in...). Figure 8P (e.g., the second (updated) status of an installment receipt that is updated to reflect an adjustment to the installment plan).

[0307] The installment payment transaction user interface displays a set of updated values ​​for the installment plan's transaction details. These updated values ​​are associated with the installment plan and based on adjustments to one or more aspects of the plan. This provides the user with a current electronic transaction receipt without requiring additional data entry to indicate updates to the installment plan. Reducing the input required to perform tasks enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0308] In some implementations, the one or more items associated with the first transfer include a first item (e.g., a movie associated with image 883) acquired (e.g., purchased or requested to be purchased) on a first date and a second item (e.g., a movie associated with image 884) acquired (e.g., purchased or requested to be purchased) on a second date different from the first date. In some implementations, the first transfer is performed on a third date different from at least one of the first and second dates (e.g., 820-2). In some implementations, when displaying a second user interface (e.g., 836), the device receives a request to display transaction details of the one or more items associated with the first transfer (e.g., 886). In response to receiving the request to display transaction details of the one or more items associated with the first transfer, the device displays a representation of the first item acquired on the first date (e.g., 887-1) and a representation of the second item acquired on the second date (e.g., 887-2). In some implementations, the transaction details of the one or more items associated with the first transfer also include information detailing the date on which the first transfer was performed (e.g., processed) (e.g., the third date).

[0309] Displaying a representation of the first item acquired on a first date and a representation of the second item acquired on a second date allows users to view two items acquired separately but charged for in a single transaction without navigating between different interfaces to view different items. This reduces the amount of input required to view items associated with a transaction. Reducing the amount of input required to perform actions enhances device operability and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0310] In some implementations, a second user interface (e.g., 836) with a second image is displayed instead of a first image, the second image corresponding to one or more items associated with a second task performed using a user account, the first image corresponding to one or more items associated with a first task performed using a user account, including one or more of the following items: If a first criterion is satisfied, including a criterion that image detail data (e.g., data indicating the physical characteristics of an item (e.g., size, color, shape)) is available for the one or more items associated with the second task, the device displays a second image (e.g., 842B-1) representing the image detail data used for the one or more items associated with the second task (e.g., the second image represents the physical characteristics indicated by the image detail data). If the first criterion is not satisfied, the device displays a second image (e.g., an image of a merchant) representing a merchant associated with the one or more items (e.g., an image of the merchant), the one or more items associated with the second task.

[0311] In some implementations, the one or more items (e.g., 820-1; 820-2) associated with the first task performed using a user account include media items (e.g., songs, photos, videos, music, etc.). In some implementations, when displaying the second user interface (e.g., 836), the device detects a selection of a third enable signal (e.g., 838C'; 838C'') (e.g., a selection of a "Open Music App" enable signal, a selection of an image associated with the media item, or a selection of a "View in Movie App" enable signal). In response to detecting a selection of the third enable signal, the device initiates playback of the media item on the electronic device (e.g., 100) (e.g., playing the media item on the electronic device, such as directly in the second user interface or in an app designated for playback of the media item (e.g., opening a music app or video app to play the media)).

[0312] In some implementations, while displaying the second user interface (e.g., 836), the device detects a selection of a fourth indication (e.g., 842A) (e.g., 871) (e.g., a selection of an installment payment indication indication). In response to detecting a selection of the fourth indication, the device displays details of a first task performed using the user account (e.g., 873; 874). In some implementations, the first task is an installment payment transaction, and the details of the first task include the amount of the installment payment transaction, the sequence of the installment payment transactions (e.g., 1 / 24), and information explaining that the installment payment transaction excludes the charging of interest on the user account.

[0313] In some implementations, the user account is a transfer account. In some implementations, when displaying the second user interface (e.g., 863), the device detects a selection of the fifth indication (e.g., 865) (e.g., 866). In response to detecting a selection of the fifth indication, the device displays a list of installment plans associated with the transfer account (e.g., 867). In some implementations, the installment plans are associated with different purchase items and optionally include images representing one or more items associated with each respective installment plan.

[0314] It should be noted that the above is relative to method 900 (e.g., Figure 9 The details of the process described herein also apply in a similar manner to the methods described below. For example, method 1200 optionally includes one or more features of the various methods described above with reference to method 900. For example, the user interface discussed in method 1200 can be used to initiate a balance transfer for a user account discussed in method 900. For the sake of brevity, these details will not be repeated below.

[0315] Figures 10A to 10H An exemplary user interface for managing the deletion of data from a remote data store associated with a user account (e.g., a computer storage management account), according to some implementation schemes, is shown. Unless otherwise stated, Figures 10A to 10H User accounts are similar to those mentioned above. Figures 7A to 7D User accounts are described. For the sake of brevity, redundant details will not be repeated below. The user interface in these figures is used to illustrate the processes described below, including the process in Figure 12.

[0316] Figure 10A An electronic device 100 with a display 112 is shown. Figure 10A In the middle, device 100 displays a summary user interface 710, which is similar to Figure 7A The interface shown and described above differs in that... Figure 10A In the illustrated implementation, the user account does not currently manage block data (e.g., there is currently no remotely stored block data, or no such policy exists for managing block data via the user account). Therefore, the summary user interface 710 (e.g., at the use of indicator 712 or the stored data list 720) does not include any indication of the display of block data, and thus, as Figure 10A The outline user interface 710 shown is not considered to be associated with block data.

[0317] like Figure 10A As shown, device 100 detects input 1001 on the delete user interface object 716-1, and in response, displays the data delete user interface 1002, as follows. Figure 10B As shown.

[0318] Figure 10B The device 100 is shown displaying a data deletion user interface 1002 on a display 112 (e.g., similar to the one described in the reference below). Figure 11B The balance transfer user interface 1102 is described above. In some embodiments, the data deletion user interface 1002 enables the selection of the amount of data to be deleted from data (e.g., standard data) stored and / or archived on computer storage resources associated with a user account (e.g., a computer storage account).

[0319] In some embodiments, the data deletion user interface 1002 includes a selector user interface element 1004 (e.g., shaped as a closed loop such as a circle) with a selection indicator 1008 that enables the selection of the amount of data to be deleted by moving the selection indicator 1008 along the selector user interface element 1004. In some embodiments, the device 100 moves the selection indicator 1008 along the selector user interface element 1004 in response to detecting an input 1005 (e.g., touch and drag input) directed along a predefined path (e.g., clockwise or counterclockwise) of the selection indicator 1004. In some embodiments, the data deletion user interface 1002 includes an indicator 1010 that shows the amount of data currently selected by the selection indicator 1008 on the selector user interface element 1004. In some embodiments, the data deletion user interface 1002 includes a usage indicator 1007 that shows the total amount of data currently stored at a computer storage resource associated with a user account (e.g., a computer storage account).

[0320] In some embodiments, the selector user interface element 1004 includes a minimum selectable value position (e.g., a first endpoint adjacent to or near the top region of the closed loop shape of the user interface element), which corresponds to the minimum amount of data (e.g., standard data) that can be selected to be deleted from data stored and / or archived on computer storage resources associated with a user account (e.g., a computer storage account) using the current instance of the selector user interface element 1004. In some embodiments, the selector user interface element 1004 includes a maximum selectable value position (e.g., a second endpoint located at the top region of the closed loop shape of the user interface element), which corresponds to the maximum amount of data (e.g., standard data) that can be selected to be deleted from data stored and / or archived on computer storage resources associated with a user account (e.g., a computer storage account) using the current instance of the selector user interface element 1004.

[0321] In some implementations, the selector user interface element 1004 includes a plurality of suggested optional data amounts indicated on the user interface element via suggested quantity indicators 1006A to 1006E. In some implementations, the suggested quantity indicator 1006D corresponds to a data (e.g., standard data) amount corresponding to the total amount of data that should be deleted from computer storage resources associated with a user account (e.g., computer storage account) within a given time period (e.g., the previous month) to completely avoid penalties for reducing the user account's usage quota. In some implementations, the suggested quantity indicator 1006E corresponds to a data amount that is greater than the total amount of data (e.g., standard data) that should be deleted from computer storage resources associated with a user account (e.g., computer storage account) within a given time period (e.g., the previous month) but less than the amount representing the total amount of data (e.g., standard data) that can be deleted using the current instance of the selector user interface element 1004.

[0322] In some implementations, the suggested quantity indicator 1006A corresponds to a suggested optional amount of data to be deleted from computer storage resources associated with a user account (e.g., a computer storage account), the suggested optional amount of data enabling the avoidance of basic usage quota reduction penalties. In some implementations, the suggested quantity indicator 1006B corresponds to a suggested optional amount of data to be deleted from computer storage resources associated with a user account (e.g., a computer storage account), the suggested optional amount of data enabling the deletion of data (e.g., standard data) at a reasonable rate within a first time period (e.g., 2 years, 1.5 years, 1 year). In some implementations, the suggested quantity indicator 1006C corresponds to a suggested optional amount of data to be deleted from computer storage resources associated with a user account (e.g., a computer storage account), the suggested optional amount of data enabling the deletion of data (e.g., standard data) at a reasonable rate within a second time period (e.g., 9 months, 6 months, 3 months).

[0323] In some embodiments, the proposed quantity indicators 1006A-1006E may have different locations (e.g., positions) on the selector user interface element 1004, which vary depending on various factors (e.g., the amount of data represented by the full range of the predefined path of the selector user interface element 1004). Therefore, in the embodiments disclosed herein, the drawings illustrating the selector user interface element 1004 are shown with fixed markers 1003A-1003D positioned at fixed locations along the selector user interface element 1004. The selector user interface element 1004 has a range of values ​​for expenditure along its predefined path, and the fixed markers 1003A-1003D provide an indication of the numerical value (e.g., the number of GB of storage) associated with the fixed position along the selector user interface element 1004. In other words, fixed markers 1003A-1003D show samples of the expenditure values ​​along a predefined path (at a fixed position) of the selector user interface element 1004, and the portion of the selector user interface element 1004 located between the fixed markers has values ​​between the values ​​of the shown fixed markers. In some embodiments, such as Figure 10B As shown, the range of values ​​is proportionally distributed along the selection user interface element 1004. However, in some implementations, for example... Figure 10F As shown, the range of values ​​is not proportionally distributed along the selection user interface element 1004. If the selection indicator 1008 moves to a fixed position corresponding to a fixed position of a corresponding fixed mark in the fixed marks, and the device initiates the deletion of data (e.g., in response to the detection of deletion selection is now shown as 1016), the amount of data corresponding to the corresponding fixed mark is deleted as described herein.

[0324] Because the range of values ​​represented by selector user interface element 1004 varies, the values ​​indicated by fixed markers 1003A-1003D change, but the positions of fixed markers 1003A-1003D remain constant along selector user interface element 1004. Fixed markers 1003A-1003D (and their corresponding values) are not included in the user interface. Instead, providing them is beneficial to the reader and better illustrates the changes in values ​​associated with fixed positions along selector user interface element 1004.

[0325] like Figure 10B As shown, fixed marker 1003A is positioned at the 12 o'clock position along the selector user interface element 1004, fixed marker 1003B is positioned at the 3 o'clock position, fixed marker 1003C is positioned at the 6 o'clock position, and fixed marker 1003D is positioned at the 9 o'clock position. Figure 10BIn the diagram, fixed marker 1003A corresponds to the value 1.5, indicating that the amount of data associated with the position of fixed marker 1003A on the selector user interface element 1004 is 1.5GB. Similarly, fixed markers 1003B, 1003C, and 1003D correspond to the values ​​0.375, 0.75, and 1.125, respectively, indicating the corresponding amounts of data associated with fixed markers 1003B, 1003C, and 1003D on the selector user interface element 1004. Therefore, if the selection indicator 1008 moves to, for example, fixed position 1003A, and the device initiates data deletion (e.g., in response to detecting a selection of the now-delete-enabled indicator 1016), 1.5GB of data is deleted. Similarly, if the selection indicator 1008 moves to fixed position 1003B, and the now-delete-enabled indicator 1016 is selected, 0.375GB of data is deleted, and so on.

[0326] In some embodiments, the data deletion user interface 1002 includes a post-deletion enablement 1014 for scheduling the deletion of a quantity of data (e.g., standard data) from a computer storage resource (e.g., automatically) associated with a user account (e.g., a computer storage account) at a future time. In some embodiments, the data deletion user interface 1002 includes a "Delete Now" enablement 1016 for initiating the deletion of a selected quantity of data (e.g., selected via selector user interface element 1004 and selection indicator 1008) from a computer storage resource associated with a user account (e.g., a computer storage account). In some embodiments, the data deletion user interface 1002 includes a keyboard enablement 1018 for enabling manual input (e.g., using numerical values ​​on the keyboard or numeric keypad) of the quantity of data to be deleted from a computer storage resource associated with a user account (e.g., a computer storage account) on a keyboard or numeric keypad.

[0327] In some implementations (for example, see...) Figure 10F The data deletion user interface 1002 includes a detail instruction 1013 that provides additional details associated with the deletion process based on the currently selected amount of data.

[0328] In some implementations, the data deletion user interface 1002 includes a message area 1012 that displays information about different amounts of data that are recommended to be deleted from computer storage resources associated with a user account (e.g., a computer storage account). Figure 10BIn the message area 1012, there is an indication of a suggested amount corresponding to the amount currently selected via the selector user interface element 1004 and the selection indicator 1008—the total amount of standard data that should be deleted from the computer storage resources associated with the user account (e.g., computer storage account) within the corresponding time period (e.g., the previous month) to completely avoid penalties for reducing the user account's usage quota.

[0329] exist Figure 10C In this process, selection indicator 1008 moves on selector user interface element 1004 (e.g., via input 1005) to a position on the user interface element corresponding to the suggested amount indicator 1006A. In some embodiments, because the suggested amount indicator 1006A corresponds to a suggested optional amount of data to be deleted from computer storage resources associated with a user account (e.g., a computer storage account), this would allow avoidance of basic usage quota reduction penalties, but would still result in periodic usage quota reduction penalties (for the full amount corresponding to suggested amount indicator 1006D that has not yet been deleted), electronic device 100 displays a penalty indication 1020 in data deletion user interface 1002 showing the amount of usage quota reduction penalty that will be caused by deleting the currently selected amount of data (in this example, 0.5GB, as indicated by indicator 1010).

[0330] In some implementations, in response to detecting that the selection indicator 1008 has moved on the selector user interface element 1004, the electronic device 100 updates the message displayed in the message area 1012 accordingly based on the newly selected amount of data. In this example, in response to detecting that the selection indicator 1008 has moved to a position on the selector user interface element 1004 corresponding to the suggested amount indicator 1006A, the electronic device 100 displays in the message area 1012 an indication that the currently selected amount is greater than the amount of data deleted from computer storage resources associated with the user account (e.g., computer storage account) during a previous deletion period (e.g., the previous month).

[0331] exist Figure 10DIn this embodiment, device 100 displays a selector user interface element 1004 with a selection indicator 1008 in a data deletion user interface 1002. This selection indicator is positioned at a second endpoint of the defined path of the selector user interface element 1004 (e.g., the position of the maximum selectable value at the top of a loop). In some embodiments, because the selection indicator 1008 is positioned at the top of the loop, the selector user interface element 1004 indicates a selection of a data amount corresponding to the maximum amount of data (e.g., standard data) that can be deleted using the current instance of the selector user interface element 1004. In some embodiments, in response to detecting (or determining) that the selection indicator 1008 is located at the second endpoint, device 100 displays a visual indication (e.g., a symbol such as a star) in the selection indicator 1008 indicating that the current position of the selection indicator 1008 corresponds to the maximum amount of data (e.g., all standard data) that can be deleted using the current instance of the selector user interface element 1004 from computer storage resources (e.g., a computer storage account) associated with a user account.

[0332] exist Figure 10D In the process, device 100 detects input 1009 on cancellation enable indicator 1011 and, in response, cancels (e.g., aborts) the process of initiating the deletion of data stored in computer storage resources associated with a user account (e.g., computer storage account).

[0333] Now for reference Figure 10E Device 100 displays the block data management user interface 1022. In this implementation, the user account manages the data as described above. Figures 10A to 10D In addition to the 1.5GB standard data discussed, the user account now also manages 2.4GB of block data stored on computer storage resources, totaling 3.9GB of data. The block data management user interface 1022 is a user interface for managing various aspects of the block data currently stored (or previously stored) on computer storage resources associated with the user account (e.g., the computer storage account) according to a data retention policy for block data. For example, the block data management user interface 1022 includes a conversion status user interface element 1024, which indicates the current status of the block data and the portions of the block data scheduled to be converted to standard data, wherein these portions are available for deletion according to a data retention policy for standard data. Figure 10E In the embodiment shown, the conversion status user interface element 1024 includes conversion amount 1024-1, remaining amount 1024-2, progress bar 1024-3, next conversion information 1024-4, and total amount 1024-5.

[0334] In some implementations, the conversion amount 1024-1 indicates the cumulative amount of block data that has been converted to standard data. In some implementations, the remaining amount 1024-2 indicates the remaining amount of block data scheduled to be converted to standard data in the future (e.g., monthly). In some implementations, the progress bar 1024-3 provides a visual representation of the ratio of the conversion amount to the remaining amount. In some implementations, the next conversion information 1024-4 indicates the date on which the next portion of the block data is scheduled to be converted to standard data, and the amount scheduled to be converted. In some implementations, the total amount 1024-5 indicates the amount of original block data stored at computer storage resources associated with a user account (e.g., a computer storage account) according to a data retention policy for the block data. Therefore, in Figure 10E In the illustrated implementation, the conversion status user interface element 1024 indicates that the block data initially stored on the computer storage resources associated with the user account, according to the data retention policy for block data, is 2.4GB. Additionally, 100MB of block data has been converted to standard data, and 2.3GB of block data remains stored on the computer storage resources, with the next conversion of the 100MB scheduled to occur on February 29th. Therefore, the current amount of standard data managed by the user account is 1.6GB (relative to...). Figures 10A to 10D The discussion covers the sum of the previous 1.5GB plus 100MB of converted block data.

[0335] The block data management user interface 1022 also includes a conversion history 1026, which provides a summary of previous conversions of block data to standard data. For example, First Conversion 1026-1 indicates that 100MB of block data was converted to standard data on January 31, 2020 (e.g., ten hours ago). First Conversion 1026-1 also indicates that this conversion is the first of a series of twenty-four conversions from block data (e.g., 100MB) to standard data.

[0336] The block data management user interface 1022 also includes an early deletion enablement 1028, which can be selected to initiate a process for deleting at least a portion of the block data before a scheduled time.

[0337] exist Figure 10E In the process, device 100 detects input 1029 on the early deletion indication display 1028 and, in response, displays the data deletion user interface 1002, such as... Figure 10F As shown, the data deletion user interface 1002 is configured to allow users to select standard data and chunked data for deletion. In some implementations, user accounts are configured so that users are only allowed to delete chunked data after all standard data has been deleted (e.g., to avoid penalties for standard data), such as... Figure 10F As shown.

[0338] exist Figure 10F In the illustrated implementation, the user account currently manages 1.6GB of standard data and 2.3GB of bulk data stored on computer storage resources, totaling 3.9GB of data (as indicated by indicator 1007). When the data deletion user interface 1002 is displayed, the selection indicator 1008 is positioned at the suggested amount indicator 1006D, which is positioned at the value corresponding to the remaining amount of standard data (e.g., 1.6GB) along the selector user interface element 1004, as shown. Figure 10F As shown. Therefore, instruction 1010 indicates the selection of 1.6GB of data to be deleted, and detail instruction 1013 indicates that the 1.6GB selected for deletion consists of 1.6GB of standard data.

[0339] exist Figure 10F In the text, fixed marker 1003A corresponds to the value 3.9, indicating that the amount of data associated with the position of fixed marker 1003A on the selector user interface element 1004 is 3.9 GB. Similarly, fixed markers 1003B, 1003C, and 1003D correspond to the values ​​0.7, 1.4, and 2.5, respectively, indicating the corresponding amount of data associated with fixed markers 1003B, 1003C, and 1003D on the selector user interface element 1004.

[0340] exist Figure 10F In this embodiment, the selector user interface element 1004 is shown having a first portion 1004-1 and a second portion 1004-2. In this embodiment, the first portion 1004-1 represents a portion of the selector user interface element 1004 corresponding to a standard amount of data stored on computer storage resources, and the second portion 1004-2 represents a portion of the selector user interface element 1004 corresponding to a block of data stored on computer storage resources. In this embodiment, the selection indicator 1008 is positioned at a suggested quantity indicator 1006D corresponding to the remaining amount of the stored standard data (e.g., 1.6 GB). Therefore, the first portion 1004-1 is shown in shaded (e.g., indicating that it has been selected for deletion), and the second portion 1004-2 is shown unshaded (e.g., indicating that it has not been selected for deletion).

[0341] exist Figure 10F In the process, device 100 detects input 1030 on selection indicator 1008 and, in response, moves selection indicator 1008 along selector user interface element 1004. Figure 10G The location shown.

[0342] like Figure 10GAs shown, the selection indicator 1008 is positioned along the selector user interface element 1004 at a location corresponding to the value of 2.6GB, as indicated by indicator 1010. Detail indicator 1013 shows that the selected 2.6GB value consists of 1.6GB of standard data and 1.0GB of block data. Therefore, for example, as indicated by the shaded area, the current selection is for deletion of both 1.6GB of standard data and 1.0GB of block data.

[0343] exist Figure 10G In the process, device 100 detects input 1031 on selection indicator 1008 and, in response, moves selection indicator 1008 along selector user interface element 1004. Figure 10H The location shown.

[0344] like Figure 10H As shown, the selection indicator 1008 is positioned at the top of the selector user interface element 1004, corresponding to the value of 3.9GB, as indicated by indicator 1010. Detail indicator 1013 shows that the selected 3.9GB value consists of 1.6GB of standard data and 2.3GB of block data. Therefore, the current selection is for deleting 1.6GB of standard data and 2.3GB of block data. Because the entire amount of stored data is selected for deletion, the selection indicator 1008 changes to a star shape, as shown... Figure 10H As shown.

[0345] exist Figure 10H In the process, device 100 detects input 1032 on the current deletion enable display 1016 and, in response, initiates the deletion of selected data from computer storage resources. The selected data is all of the standard data (e.g., 1.6 GB) and all of the block data (e.g., 2.3 GB).

[0346] Figures 11A to 11R An exemplary user interface for managing balance transfers in a user account, according to some implementation schemes, is shown. Figures 11A to 11R User accounts are similar to those mentioned above. Figures 8A to 8AK The user account described (e.g., a transfer account). For the sake of brevity, redundant details will not be repeated below. The user interface in these figures is used to illustrate the processes described below, including the process in Figure 12.

[0347] Figure 11A An electronic device 100 with a display 112 is shown. Figure 11A In the image, device 100 displays the summary user interface 810 shown on December 15, 2019. The summary user interface 810 is similar to... Figure 8D The interface shown and described above differs in that... Figure 11AIn the implementation shown, the user account (e.g., a transfer account) does not currently include an installment balance (e.g., there are no installment purchases associated with the account, or there are no currently unpaid installment balances associated with the user account).

[0348] like Figure 11A As shown, device 100 detects input 1101 on indicator 816A.

[0349] exist Figure 11B In response to the detection of input 1101 on indicator 816A, device 100 displays a balance transfer user interface 1102 on display 112 corresponding to the transfer account (e.g., a first-party credit account; a points account).

[0350] In some embodiments, the balance transfer user interface 1102 includes an indication 1115 of the balance transfer due date (e.g., the previous bill due date if the bill balance is not fully paid; the current bill due date). In some embodiments, the balance transfer user interface 1102 includes a selector user interface element 1104 for selecting the amount of the balance transfer (e.g., the balance payment amount) by moving the selection indicator 1108 along a predefined path (e.g., a closed-loop path such as a circle) of the selector user interface element 1104. The selected balance transfer amount (e.g., the selected balance payment amount) is based on the position of the selection indicator 1108 along the predefined path of the selector user interface element 1104. The device 100 detects (or determines) the balance transfer amount (e.g., the balance payment amount) based on the position of the selection indicator 1108 along the predefined path (e.g., a closed-loop path such as a circle) of the selector user interface element 1104. In some implementations, device 100 moves selection indicator 1108 along selector user interface element 1104 in response to detecting input (e.g., touching and dragging input such as input 1105) that moves (e.g., drags, slides) towards selection indicator 1108 along a predefined path (e.g., clockwise or counterclockwise) of selector user interface element 1104.

[0351] In some implementations, the selector user interface element 1104 includes a minimum selectable value location (e.g., a first endpoint adjacent to or near the top region of the closed loop shape of the user interface element (e.g., located at or near the 12 o'clock position)) that corresponds to the minimum balance transfer amount selectable using the current example of the selector user interface element 1104. That is, in some implementations, if the selection indicator 1108 is located at the first endpoint (e.g., the minimum value location) of a predefined path of the selector user interface element 1104, the currently selected balance transfer amount corresponds to the minimum balance transfer amount (e.g., a possible minimum balance payment amount or a minimum balance payment amount that will avoid penalties such as late fees).

[0352] In some implementations, the selector user interface element 1104 includes a maximum selectable value position (e.g., a second endpoint located in the top region of the closed loop shape of the user interface element (at the 12 o'clock position)) that corresponds to the maximum selectable transfer amount available for the current example using the selector user interface element 1104. That is, in some implementations, if the selection indicator 1108 is located at the second endpoint of a predefined path (e.g., the maximum value position), the currently selected balance transfer amount corresponds to the maximum selectable transfer amount (e.g., the full amount of the unresolved balance).

[0353] In some implementations, points along a defined path between two endpoints of the selector user interface element 1104 correspond to balance transfer amounts distributed along a predefined path between the minimum balance transfer amount and the maximum selectable balance transfer amount. In some implementations, a portion of a predefined path from the first endpoint (e.g., the minimum point corresponding to the minimum balance payment amount) to the position of the selection indicator 1108 along a predefined path is displayed with visual features (e.g., a specific color or hue, such as green), wherein the type of visual feature (e.g., the type of color or hue) is determined based on the currently selected balance transfer amount (e.g., the selected balance payment amount) and the amount of a penalty (e.g., interest) that can be accumulated based on the selected balance transfer amount.

[0354] In some implementations, the predefined path of the selector user interface element 1104 also includes a plurality of proposed amount indicators 1106A to 1106E corresponding to the proposed balance transfer amount (e.g., the proposed balance payment amount). In some implementations, the proposed amount indicator 1106A corresponds to the minimum balance transfer amount. In some implementations, the proposed amount indicator 1106A corresponds to an amount greater than the minimum balance transfer amount (e.g., and equal to or greater than the previous balance transfer amount) but still a relatively small amount. In some implementations, the proposed amount indicator 1106D corresponds to a balance transfer amount (e.g., the entire bill amount) that will completely avoid penalties (e.g., interest) for the corresponding balance transfer period (e.g., the corresponding billing period). In some implementations, the proposed amount indicator 1106E corresponds to an amount greater than the balance transfer amount that will completely avoid penalties for the corresponding balance transfer period (e.g., greater than the entire bill amount) but less than the maximum balance transfer amount (e.g., less than the entire current balance). In some implementations, the plurality of proposed amount indicators include one or more additional proposed amount indicators (e.g., proposed amount indicators 1106B, 1106C) corresponding to a balance transfer amount (e.g., a balance payment amount), which is determined based on the full amount of the remaining balance of the transfer account, past balance transfer history (e.g., past balance payment history), and / or will be provided to completely reduce the remaining balance of the transfer account (e.g., fully pay the account balance) for a given period of time (e.g., 3 months or 6 months).

[0355] In some embodiments, the proposed amount indicators 1106A-1106E may have different locations (e.g., positions) on the selector user interface element 1104, which vary depending on various factors (e.g., the total selectable balance transfer amount represented by the full range of the predefined path of the selector user interface element 1104). Therefore, in the embodiments disclosed herein, the drawings illustrating the selector user interface element 1104 are shown as having fixed markers 1103A-1103D (similar to fixed markers 1003A-1003D) positioned at fixed locations along the selector user interface element 1104. The selector user interface element 1104 has a range of values ​​for expenditures along its predefined path, and the fixed markers 1103A-1103D provide an indication of the numerical value (e.g., the balance transfer amount) associated with the fixed position along the selector user interface element 1104. In other words, fixed markers 1103A-1103D show samples of expenditure values ​​along a predefined path (at fixed positions) of selector user interface element 1104, and portions of selector user interface element 1104 located between fixed markers have values ​​between the values ​​of the shown fixed markers. In some embodiments, the value range is proportionally distributed along selector user interface element 1104. However, in some embodiments, the value range is not proportionally distributed along selector user interface element 1104. If the selection indicator 1108 moves to a fixed position corresponding to a corresponding fixed marker among the fixed markers, and the device initiates a balance transfer (e.g., in response to detecting a selection of the current transfer capability indication 1116), a balance transfer corresponding to the amount shown by the corresponding fixed marker is initiated as described herein.

[0356] In some embodiments, fixed marker 1103A is positioned at the 12 o'clock position along selector user interface element 1104, fixed marker 1103B is positioned at the 3 o'clock position, fixed marker 1103C is positioned at the 6 o'clock position, and fixed marker 1103D is positioned at the 9 o'clock position. In some embodiments, fixed marker 1103A represents the maximum value within a range of values ​​represented by a predefined path of selector user interface element 1104. In some embodiments, the minimum value within a range of values ​​represented by a predefined path of selector user interface element 1104 is zero. In some embodiments, the minimum value within a range of values ​​represented by a predefined path of selector user interface element 1104 is a value associated with the position of the proposed amount indicator 1106A. Fixed markers 1103A-1103D provide indications of numerical values ​​(e.g., balance transfer amounts) associated with fixed positions along selector user interface element 1104. As the range of values ​​represented by selector user interface element 1104 changes, the values ​​indicated by fixed markers 1103A-1103D also change, but the positions of the fixed markers 1103A-1103D remain constant along the selector user interface element 1104. Fixed markers 1103A-1103D (and their corresponding values) are not included in the user interface. Instead, providing them is beneficial to the reader and better illustrates the changes in values ​​associated with their fixed positions along the selector user interface element 1104.

[0357] In some implementations, a portion of the predefined path of the selector user interface element 1104 from the start and end positions of the predefined path (e.g., the 12 o'clock position of the defined path if the defined path is a closed loop path such as a circle) to the current position of the selection indicator 1108 is displayed with visual features (e.g., a specific color), wherein the type of visual feature displayed depends on the position of the selection indicator 1108 along the predefined path and the corresponding value of the selected transfer amount when the selection indicator 1108 is in its current position.

[0358] For example, if the selection indicator 1108 is located at a position on a predefined path corresponding to the proposed amount indicator 1106A, or at a position corresponding to a value smaller than the value corresponding to the proposed amount indicator 1106A on the defined path (e.g., a position closer to the start and end positions of the predefined path), the electronic device 100 displays a portion of the predefined path (e.g., the 12 o'clock position of the predefined path if the defined path is a closed path such as a circle) from the start and end positions of the predefined path (e.g., the 12 o'clock position of the predefined path) to the position of the selection indicator 1108 having a first visual characteristic (e.g., a first color, such as red). In some embodiments, the device prevents the user from moving the selector indicator 1108 to a position on the predefined path corresponding to a value smaller than the value of the amount indicator 1106A. For example, if the selection indicator 1108 is located on a predefined path at a position corresponding to a value that is less than the position value of the proposed amount indicator 1106D but greater than the position value of the proposed amount indicator 1106A (e.g., a position on the predefined path between the proposed amount indicator 1106A and the proposed amount indicator 1106D), the device 100 displays a portion of the predefined path (e.g., the 12 o'clock position defining the path) from the start and end positions of the predefined path (e.g., the 12 o'clock position defining the path if the predefined path is a closed path such as a circle) to the position of the selection indicator 1108 having a second visual characteristic (e.g., a second color, such as yellow). For example, if the selection indicator 1108 is located on a predefined path at a position corresponding to the proposed amount indicator 1106D, the device 100 displays a portion of the predefined path (e.g., the 12 o'clock position of the predefined path) from the start and end positions of the predefined path (e.g., the 12 o'clock position of the predefined path if the predefined path is a closed path such as a circle) to the position of the selection indicator 1108 having a third visual feature (e.g., a third color, such as green). For example, if the selection indicator 1108 is located at a position on a predefined path corresponding to a value on the predefined path that is greater than the position value on the predefined path of the proposed amount indicator 1106D (e.g., a position further away from the start and end positions of the predefined path than the proposed amount indicator 1106D), the device 100 displays a portion of the predefined path (e.g., the 12 o'clock position of the predefined path) from the start and end positions of the predefined path (e.g., the 12 o'clock position of the predefined path if the predefined path is a closed path such as a circle) to the position of the selection indicator 1108 having a fourth visual feature (e.g., a fourth color, such as blue) (e.g., the selection indicator itself).

[0359] like Figure 11B (and Figure 11C and Figure 11DAs shown, fixed marker 1003A corresponds to the value 100.00, indicating that the potential balance transfer amount associated with the position of fixed marker 1103A on selector user interface element 1104 is $100.00. Similarly, fixed markers 1103B, 1103C, and 1103D correspond to the values ​​25.00, 50.00, and 75.00, respectively, indicating the corresponding potential balance transfer amounts associated with the corresponding positions associated with fixed markers 1103B, 1103C, and 1103D on selector user interface element 1104. In some embodiments, such as Figure 11B As shown, the value range is proportionally distributed along the selection user interface element 1104. However, in some implementations, such as Figure 11N As shown, the value range is not proportionally distributed along the selected user interface element 1104.

[0360] In some embodiments, the electronic device 100 also displays an indication 1107 in the balance transfer user interface 1102 of the maximum selectable balance transfer amount in the current instance of the balance transfer user interface 1102. In some embodiments, indication 1107 represents the current total balance of the transfer account (e.g., a first-party credit account; a points account), excluding any installment payment balances (regardless of whether an installment payment plan is associated with the transfer account). In some embodiments, indication 1107 represents the current total balance of the transfer account, including installment payment balances of any installment payment plans associated with the transfer account.

[0361] In some implementations, the electronic device 100 also displays an indication 1110 of the currently selected balance transfer amount in the balance transfer user interface 1102 based on the position of the selection indicator 1108 on a predefined path of the selector user interface element 1104.

[0362] In some implementations, the electronic device 100 also displays a detail indication 1113 in the balance transfer user interface 1102, which provides additional details associated with the balance transfer based on the currently selected balance transfer amount. For example, in Figure 11B In the details, Instruction 1113 indicates that interest charges will not be shown for the currently selected balance transfer (e.g., payment) amount.

[0363] In some implementations (for example, see...) Figure 11C The electronic device 100 also displays an instruction 1120 in the balance transfer user interface 1102 to impose (e.g., charge) a penalty (e.g., interest) on the transfer account based on the currently selected balance transfer amount.

[0364] In some implementations, the electronic device 100 also displays an information area 1112 in the balance transfer user interface 1102, which describes the effect or result of making a balance transfer (e.g., balance payment) based on the currently selected balance transfer amount.

[0365] In some implementations, the electronic device 100 also displays in the balance transfer user interface 1102 a later transfer capability 1114 for scheduling further balance transfers (e.g., for setting the date and / or time of future automatic balance payments), a current transfer capability 1116 for initiating an immediate balance transfer (e.g., for continuing an immediate balance payment), and a keyboard display capability 1118 for displaying a keypad or keyboard that can be used to manually enter the balance transfer amount (e.g., manually enter the balance payment amount) without using the selector user interface element 1104.

[0366] like Figure 11B As shown, the total balance available for payment is $100 (as indicated in instruction 1107). Figure 11B In the implementation shown, a $100 balance corresponds to Figure 11A The card balance shown in the balance summary user interface element 812 includes the balance of the transfer account that does not include any installment transfers. Therefore, indication 1107 represents the card balance associated with the transfer account that does not include any installment transfers. Thus, the card balance consists of the billing balance (e.g., the amount currently due on the transfer account—$65.77 in this embodiment) and subsequent transfer balances, which correspond to the balance of transfers applied to the transfer account after the billing balance was generated. In this embodiment, the subsequent transfer balance is $34.23, and the card balance (e.g., $100) represents all unpaid transfers applied to the transfer account, which also excludes any installment transfers.

[0367] like Figure 11BAs shown, selection indicator 1108 is positioned at the proposed amount indicator 1106D corresponding to a balance transfer of $65.77 (as indicated by indicator 1110). The $65.77 amount corresponds to the billing balance of the account to which the transfer is due by December 31. In some embodiments, based on determining that selection indicator 1108 is located at the proposed amount indicator 1106D (e.g., corresponding to the entire billing balance; corresponding to a balance transfer amount that will completely avoid penalties (e.g., interest) for the current balance transfer cycle), device 100 displays a visual indication (e.g., a symbol, such as a checkmark) in selection indicator 1108 indicating the location of the selection indicator corresponding to the balance transfer amount that will completely avoid penalties (e.g., interest) for the current balance transfer cycle. Therefore, selection indicator 1108 includes a checkmark, as shown in the diagram. Figure 11B As shown. Additionally, the portion of the selector user interface element 1104 from the first endpoint to the selection indicator 1108 has a first hue (e.g., green) indicating the selection of the entire bill balance for payment.

[0368] exist Figure 11B In this process, device 100 detects input 1105 on selection indicator 1108 (e.g., a touch and drag gesture following a predefined path of selector user interface element 1104), and in response, moves selection indicator 1108 along the predefined path of selector user interface element 1104. Figure 11C The location shown.

[0369] exist Figure 11C In this context, device 100 displays (e.g., in response to input 1105) a selection indicator 1108 that moves along selector user interface element 1104 to a position on the user interface element corresponding to the proposed amount indicator 1106A. Indication 1110 indicates that the selected transfer amount (e.g., minimum selectable transfer balance) is $5.00, and indication 1020 indicates a penalty (e.g., interest) of $9.89 that can be imposed (e.g., charged) on the transfer account based on the currently selected balance transfer amount associated with the proposed amount indicator 1106A. Therefore, in Figure 11C In the balance transfer user interface 1102, it is shown that for a transfer account without installment transfers and a bill balance of $65.77, the minimum balance transfer amount is $5.00.

[0370] exist Figure 11C In this process, device 100 detects input 1122 (e.g., a touch and drag gesture following a predefined path of selector user interface element 1104) on selection indicator 1108, and in response, moves selection indicator 1108 along the predefined path of selector user interface element 1104. Figure 11D The location shown.

[0371] exist Figure 11D In this context, device 100 displays (e.g., in response to input 1122) a selection indicator 1108 that moves along selector user interface element 1104 to a position on the user interface element corresponding to a second endpoint (e.g., the 12 o'clock position). Indicator 1110 indicates that the selected transfer amount (e.g., the maximum selectable transfer balance) is $100.00. Therefore, the balance transfer user interface 1102 in... Figure 11D The total balance of the selected transfer account is shown for payment. In response to detecting (or determining) that the selection indicator 1108 is located at the second endpoint, the device 100 provides a visual indication (e.g., a symbol such as a star) in the selection indicator 1108, indicating that the current position of the selection indicator 1108 corresponds to a balance transfer (e.g., payment) of the total balance of the transfer account.

[0372] exist Figure 11D In this process, device 100 detects input 1123 on the current transfer capability display 1116 and, in response, initiates a balance transfer to clear the selected balance (e.g., the total balance of the transfer account). The following section discusses... Figures 11P to 11Q It discusses the details of the balance transfer process (e.g., payment).

[0373] Now for reference Figure 11E Device 100 displays the summary user interface 810 shown on December 25, 2019. The summary user interface 810 is similar to... Figure 11A The interface shown differs in that the summary user interface 810 is updated to display new transfers applied to the transfer account. For example, the transfer item list 820 shows transfer item 820-X, and transfer item 820-Y has been added to the transfer account. Transfer item 820-X corresponds to a balance transfer initiated in response to input 1123 on the current transfer capability display 1116. Thus, transfer item 820-X shows a $100 credit applied to the transfer account on December 15, 2019 (corresponding to a $100 balance transfer). Transfer item 820-Y corresponds to the initial purchase of an item associated with an installment plan. Transfer item 820-Y is similar to transfer item 820A. Therefore, transfer item 820-Y represents an initial transfer (e.g., tax payment) associated with goods (e.g., a phone) purchased through an installment plan.

[0374] exist Figure 11EIn the implementation shown, an installment purchase has been initiated (e.g., via transfer project 820-Y), but the first installment has not yet been applied to the transfer account. Balance Summary user interface element 812 includes an indication 812-1 of the installment balance (e.g., $511) associated with the transfer account, which is the total installment balance (e.g., the total balance of the installment plan (loan amount)) used for the phone purchase. The $65.77 balance in the transfer account (shown in Balance Summary user interface element 812) corresponds to the tax purchase associated with transfer project 820-Y, excluding the installment plan portion. Because the total balance of the transfer account was paid on December 15, 2019 (e.g., via transfer project 820-X), and there are no subsequent transfers applied to the transfer account (other than transfer project 820-Y) (as indicated in transfer project list 820), the $65.77 balance from transfer project 820-Y represents the current balance of the transfer account. Because an installment purchase has been initiated, the installment balance (e.g., $511) is associated with the transfer account; however, the installment transfer has not been added to the transfer account, and therefore, the current balance of the transfer account (e.g., $65.77) is excluded from the installment plan.

[0375] like Figure 11E As shown, device 100 detects input 1124 on indicator 816B and, in response, displays balance transfer user interface 1102, as follows. Figure 11F As shown. In some implementations, indicator 816B causes a process for paying at least a portion of the transfer account balance to be initiated before the billing balance of the transfer account is generated. That is, indicator 816B allows the user to prepay the transfer account balance.

[0376] like Figure 11F As shown, fixed marker 1003A corresponds to the value 65.77, indicating that the potential balance transfer amount associated with the position of fixed marker 1103A on selector user interface element 1104 is $65.77. Similarly, fixed markers 1103B, 1103C, and 1103D correspond to the values ​​49.33, 32.88, and 16.44, respectively, indicating the corresponding potential balance transfer amounts associated with the corresponding positions of fixed markers 1103B, 1103C, and 1103D on selector user interface element 1104.

[0377] exist Figure 11FIn the device 100, a balance transfer user interface 1102 is displayed, where a selection indicator 1108 is positioned on a selector user interface element 1104 at a second endpoint. As indicated by fixed mark 1103A, the value range represented by selector user interface element 1104 terminates at 65.77 (e.g., $65.77), which corresponds to the balance of the transfer account (excluding any installment transfers). Indicator 1110 indicates that the selected transfer amount (e.g., the maximum selectable transfer balance) is $65.77. Therefore, the balance transfer user interface 1102 in... Figure 11F The total balance of the selected transfer account is shown for payment. In response to detecting (or determining) that the selection indicator 1108 is located at the second endpoint, the device 100 provides a visual indication (e.g., a symbol such as a star) in the selection indicator 1108, indicating that the current position of the selection indicator 1108 corresponds to a balance transfer (e.g., payment) of the total balance of the transfer account.

[0378] exist Figure 11F In the process, device 100 detects input 1125 on the cancellation enable indicator 1111 and, in response, cancels (e.g., aborts) the process for selecting the balance transfer amount.

[0379] Now for reference Figure 11G Device 100 displays a summary user interface 810 as shown on December 31, 2019, the date when the first installment payment was added to the transfer account and...

Claims

1. A method comprising: At an electronic device that communicates with a display device and one or more input devices: Receive a request to display the numerical selection user interface; as well as In response to receiving the request to display the numerical selection user interface, a numerical selection user interface for selecting a value of a corresponding parameter is displayed, wherein the numerical selection user interface includes: A predefined path with a corresponding size and shape, wherein the predefined path of the numerical selection user interface corresponds to a numerical range associated with the payment amount used to reduce the balance of the transfer account. Value selectors, and A selectable user interface object is used to initiate a process that performs a predefined operation using a value associated with the value selector; The user interface for displaying the numerical selection includes: Based on the determination that the request to display the numerical selection user interface satisfies a first criterion, a predefined path having the corresponding size and shape is displayed, wherein the first criterion includes a criterion satisfied when the request to display the numerical selection user interface occurs simultaneously with the display of a first user interface associated with the corresponding parameter, wherein a first point on the predefined path corresponds to a first numerical value, and a second point on the predefined path corresponds to a second numerical value, and wherein the predefined path represents a first numerical range corresponding to a payment amount for the balance of the transfer account, wherein the balance of the transfer account includes a first balance and an installment payment balance of the transfer account, the first balance including non-installment transfers, and the installment payment balance including installment transfers associated with an installment payment plan; and Based on the determination that the request to display the numerical selection user interface meets a second criterion, a predefined path having the corresponding size and shape is displayed, wherein the second criterion includes a criterion that is met when the request to display the numerical selection user interface occurs simultaneously with the display of a second user interface different from the first user interface and associated with the corresponding parameter, wherein the first point on the predefined path corresponds to a third value different from the first value, and the second point on the predefined path corresponds to a fourth value different from the second value, and wherein the predefined path represents a second numerical range corresponding to a payment amount for the balance of the transfer account, wherein the balance of the transfer account includes a second balance, the second balance excluding any installment payment transactions associated with the installment payment plan; When displaying the numerical selection user interface, detect input corresponding to activation of the selectable user interface object; and In response to detecting the input corresponding to activation of the selectable user interface object: Based on the fact that the request to display the value selection user interface satisfies the first criterion, a process is initiated to perform the predefined operation using the first value. Based on the fact that the request to display the value selection user interface satisfies the first criterion, a process is initiated to perform the predefined operation using the second value. Based on the second criterion that the request to display the value selection user interface satisfies the second criterion by determining that the value selector is at the first point on the predefined path, the process of performing the predefined operation using the third value is initiated; and Based on the fact that the request to determine that the value selector is at the second point on the predefined path and to display the value selection user interface satisfies the second criterion, a process is initiated to perform the predefined operation using the fourth value.

2. The method according to claim 1, wherein the predefined operation is an adjustment of the balance of the transfer account.

3. The method according to any one of claims 1-2, wherein: The first user interface associated with the corresponding parameter is a user interface for managing one or more aspects of the installment plan associated with the transfer account; and The second user interface associated with the corresponding parameter is a user interface not associated with the installment payment plan of the transfer account.

4. The method according to any one of claims 1-2, wherein the first balance further includes installment payment transfers previously included in the installment payment balance.

5. The method according to any one of claims 1-2, wherein: The first point on the predefined path corresponds to the maximum payment amount for the first balance; and The process of performing the predefined operation using the first value includes applying the maximum payment amount for the first balance to the balance of the transfer account, but not applying the payment amount for the installment payment balance.

6. The method according to any one of claims 1-2, wherein displaying the numerical selection user interface comprises: The request to display the numerical selection user interface is displayed based on the determination that the first criterion is met, wherein the second point on the predefined path corresponds to the maximum payment amount for the balance of the transfer account, the balance including the first balance and the installment payment balance; and The process of performing the predefined operation using the second value includes applying the maximum payment amount for the balance of the transfer account to the balance of the transfer account.

7. The method according to any one of claims 1-2, wherein displaying the numerical selection user interface comprises: If the request to display the numerical selection user interface is satisfied according to the first criterion, a visual representation of the first balance and a visual representation of the installment payment balance are displayed in the numerical selection user interface.

8. The method according to any one of claims 1-2, wherein: Based on the determination that the request to display the numerical selection user interface meets the first criterion, the predefined path includes a first portion having a value range corresponding to the payment amount for the installment payment balance of the transfer account.

9. The method according to any one of claims 1-2, further comprising: When displaying the numerical selection user interface and before detecting the input corresponding to activation of the selectable user interface object: Detect one or more inputs directed to the numerical selection user interface; as well as In response to detecting one or more inputs directed to the value selection user interface, the position of the value selector within the predefined path of the value selection user interface is adjusted.

10. The method according to any one of claims 1-2, wherein the numerical selection user interface further includes a representation of the selected value of the corresponding parameter displayed at the center position relative to the predefined path having the corresponding size and shape.

11. The method according to any one of claims 1-2, wherein the predefined path having the corresponding size and shape is circular.

12. The method according to any one of claims 1-2, wherein the predefined path is a closed path.

13. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device in communication with a display device and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 1-12.

14. An electronic device configured to communicate with a display device and one or more input devices, the electronic device comprising: 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 performing the method according to any one of claims 1-12.

15. An electronic device configured to communicate with a display device and one or more input devices, the electronic device comprising: Apparatus for performing the method according to any one of claims 1-12.

16. A computer program product comprising one or more programs configured to be executed by one or more processors of an electronic device in communication with a display device and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1-12.

Images