User interface for initiating transactions
By simultaneously displaying and receiving visual representations of the selected two asset accounts on a computer system, the transaction initiation process is simplified, solving the problems of complex interfaces and low efficiency in existing technologies. This enables a faster and more efficient transaction initiation method while saving battery power.
Patent Information
- Application Number
- CN202380032803.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-06-04
- Filing Date
- 2023-04-04
- Publication Date
- 2024-11-29
AI Technical Summary
Existing technologies for initiating transactions using electronic devices have complex and inefficient interfaces, wasting user time and device energy, especially in battery-powered devices.
By simultaneously displaying visual representations of two asset accounts on a computer system and receiving selections and inputs to initiate transfer requests, the transaction process is simplified, reducing user input and interface operations.
It provides a faster and more efficient way to initiate transactions, reduces cognitive load, saves power for battery-powered devices, and improves device efficiency and user satisfaction.
Smart Images

Figure CN119053979A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Patent Application Serial No. 63 / 327,751, entitled “USER INTERFACES FOR INITIATING TRANSACTIONS,” filed on April 5, 2022, and U.S. Provisional Patent Application Serial No. 63 / 349,074, entitled “USER INTERFACES FOR INITIATING TRANSACTIONS,” filed on June 4, 2022. The contents of each of these patent applications are incorporated herein by reference in their entirety. Technical Field
[0003] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for initiating transactions. Background Art
[0004] Using electronic devices to initiate transactions such as resource transfers provides a convenient and efficient method for initiating resource exchanges between accounts. Specifically, initiating transactions in this manner enables users to use electronic devices to quickly and easily request that resources be transferred to or from a user's account. Summary of the invention
[0005] However, some techniques for initiating transactions using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.
[0006] Thus, the present technology provides a faster, more efficient method and interface for initiating transactions for electronic devices. Such methods and interfaces optionally supplement or replace other methods for initiating transactions. Such methods and interfaces reduce the cognitive burden imposed on users and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.
[0007] An exemplary method is described herein. An exemplary method includes: at a computer system in communication with a display generation component and one or more input devices: displaying via the display generation component a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account simultaneously; while displaying the portion of the first visual representation and the portion of the second visual representation simultaneously, receiving via the one or more input devices a selection of the first visual representation corresponding to the first asset account; in response to receiving the selection of the first visual representation corresponding to the first asset account, displaying via the display generation component an option for initiating a transfer request using the first asset account; while displaying the option for initiating a transfer request using the first asset account, receiving via the one or more input devices a selection of the option for initiating a transfer request using the first asset account; in response to receiving the selection of the option for initiating a transfer request using the first asset account, displaying via the display generation component representations of one or more users; and while displaying the representations of the one or more users, receiving via the one or more input devices a selection of a first representation corresponding to a first user of the one or more users who is a recipient of the transfer request using the first asset account.
[0008] Example non-transitory computer-readable storage media are described herein. An exemplary non-transitory computer-readable storage medium stores one or more programs that are configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and includes instructions for the following operations: simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation, receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account; in response to receiving the selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; while displaying the option for initiating a transfer request using the first asset account, receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account; in response to receiving the selection of the option for initiating a transfer request using the first asset account, displaying, via the display generation component, representations of one or more users; and while displaying the representations of the one or more users, receiving, via the one or more input devices, a selection of a first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
[0009] Example transitory computer-readable storage media are described herein. An exemplary non-transitory computer-readable storage medium stores one or more programs that are configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and includes instructions for the following operations: simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation, receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account; in response to receiving the selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; while displaying the option for initiating a transfer request using the first asset account, receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account; in response to receiving the selection of the option for initiating a transfer request using the first asset account, displaying, via the display generation component, representations of one or more users; and while displaying the representations of the one or more users, receiving, via the one or more input devices, a selection of a first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
[0010] An exemplary computer system is described herein. An exemplary computer system is configured to communicate with a display generation component and one or more input devices, including: 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 following operations: displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously, receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account; in response to receiving to a selection of a first visual representation corresponding to a first asset account, displaying, via the display generating component, an option for initiating a transfer request using the first asset account; when the option for initiating a transfer request using the first asset account is displayed, receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account; in response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying, via the display generating component, representations of one or more users; and when displaying the representations of the one or more users, receiving, via the one or more input devices, a selection of a first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
[0011] An exemplary computer system is configured to communicate with a display generation component and one or more input devices, and includes: a component for simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; a component for receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account when the portion of the first visual representation and the portion of the second visual representation are simultaneously displayed; a component for displaying, via the display generation component, an option for initiating a transfer request using the first asset account in response to receiving a selection of the first visual representation corresponding to the first asset account; a component for receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; a component for performing the following operations: in response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying, via the display generation component, representations of one or more users; and when displaying the representations of the one or more users, receiving, via the one or more input devices, a selection of a first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
[0012] Example computer program products are described herein. An exemplary computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for: simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; while simultaneously displaying the portion of the first visual representation and the portion of the second visual representation, receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account; in response to receiving the selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; while displaying the option for initiating a transfer request using the first asset account, receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account; in response to receiving the selection of the option for initiating a transfer request using the first asset account, displaying, via the display generation component, representations of one or more users; and while displaying the representations of the one or more users, receiving, via the one or more input devices, a selection of a first representation corresponding to a first user of the one or more users who is a recipient of the transfer request using the first asset account.
[0013] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.
[0014] Thus, devices are provided with faster, more efficient methods and interfaces for initiating transactions, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for initiating transactions. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.
[0016] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.
[0017] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.
[0018] Figure 2 A portable multifunction device with a touch screen according to some embodiments is illustrated.
[0019] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.
[0020] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments is illustrated.
[0021] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.
[0022] Figure 5A Personal electronic devices according to some embodiments are illustrated.
[0023] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.
[0024] Figure 6 Example devices connected via one or more communication channels are shown in accordance with some embodiments.
[0025] 7A to 7I An exemplary user interface for initiating a transaction with a remote data store associated with a user account is illustrated according to some embodiments.
[0026] FIG. 8A to FIG. 8AE An exemplary user interface for initiating a transaction on a user account according to some embodiments is illustrated.
[0027] Fig. 9 is a flow chart illustrating a method for initiating a transaction according to some embodiments. DETAILED DESCRIPTION
[0028] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.
[0029] Electronic devices need to provide more efficient methods and interfaces for initiating transactions. Such techniques can reduce the cognitive burden on users initiating transactions, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.
[0030] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device for performing techniques for management event notifications is provided. 7A to 7I An exemplary user interface for initiating a transaction with a remote data store associated with a user account is illustrated. FIG. 8A to FIG. 8AE An exemplary user interface for initiating a transaction on a user account is illustrated. Fig. 9 is a flow chart illustrating a method of initiating a transaction for a user account according to some embodiments. 7A to 7I and FIG. 8A to FIG. 8AE The user interface in is used to illustrate the process described below, including Fig. 9 process.
[0031] The processes described below enhance the operability of the device and make 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) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional display controls, performing an operation without further user input when a set of conditions have been met, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and more efficiently.
[0032] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.
[0033] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, both the first touch and the second touch are touches, but they are not the same touch.
[0034] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "including" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their grouping.
[0035] The term "if" is optionally interpreted to mean "when," "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]," or "in response to detecting [a stated condition or event]," depending on the context.
[0036] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment and Device. Optionally use other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).
[0037] 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 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.
[0038] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.
[0039] Various applications executed 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 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 common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.
[0040] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The 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 device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.
[0041] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute 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 the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). 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 the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).
[0042] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a particular 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 a component thereof that would generate that sensory perception for a typical (or average) user.
[0043] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.
[0044] Memory 102 optionally includes high-speed random access memory, and optionally also 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.
[0045] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.
[0046] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits 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, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communication radio components. Wireless communication optionally uses 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, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.
[0047] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).
[0048] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and / or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or is independent of an input element that is part of the device) and is based on detected movement of a part of the user's body through the air, including movement of the user's body relative to an absolute reference (for example, the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (for example, movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (for example, a tap gesture involving a hand moving a predetermined amount and / or speed in a predetermined position, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).
[0049] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
[0050] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.
[0051] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.
[0052] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in
[0053] The touch-sensitive display in some embodiments of touch screen 112 is optionally similar to the 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 hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while a touch-sensitive touchpad does not provide visual output.
[0054] The touch-sensitive display in some embodiments of the touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, “Multipoint Touch Surface Controller”; (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, “Multipoint Touchscreen”; (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, “Gestures For Touch Sensitive Input Devices”; (5) U.S. Patent Application No. 11 / 038,590, filed January 18, 2005, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. Patent Application No. 11 / 228,758, filed September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard” and (9) U.S. patent application Ser. No. 11 / 367,749, filed Mar. 3, 2006, for "Multi-Functional Hand-Held Device." All of these applications are incorporated herein by reference in their entirety.
[0055] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.
[0056] In some embodiments, in addition to the touch screen, the 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 touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.
[0057] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuits, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.
[0058] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. 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 the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that when the user views other video conference participants on the touch screen display, the image of the user is optionally obtained for video conferencing. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.
[0059] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the positioning of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.
[0060] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.
[0061] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent application numbers: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which U.S. patent applications are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.
[0062] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.
[0063] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripherals interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 optionally performs as described in the following U.S. Patent Publication Nos.: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 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 in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. Device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to accelerometer 168 for obtaining information about the position and orientation (eg, portrait or landscape) of device 100 .
[0064] 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 (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: active application state, which indicates which application (if any) is 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 related to the device's position and / or posture.
[0065] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.
[0066] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.
[0067] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the 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 contact disconnection). 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 the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.
[0068] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. Additionally, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).
[0069] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). 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 (lift-off) event at the same location (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 the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.
[0070] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.
[0071] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application or the like, along with coordinate data and other graphic attribute data if necessary, and then generates screen image data to be output to the display controller 156.
[0072] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .
[0073] The text input module 134, which is optionally a component of the graphics module 132, provides a soft keyboard for entering text in various applications (e.g., the contacts module 137, email client module 140, IM module 141, browser module 147, and any other application requiring text input).
[0074] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone module 138 for use in location-based dialing; to the camera module 143 as picture / video metadata; and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a map / navigation widget).
[0075] Application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:
[0076] Contacts module 137 (sometimes called address book or contact list);
[0077] Telephone module 138;
[0078] Video conferencing module 139;
[0079] Email client module 140;
[0080] Instant messaging (IM) module 141;
[0081] Fitness support module 142;
[0082] A camera module 143 for still images and / or video images;
[0083] Image management module 144;
[0084] Video player module;
[0085] Music player module;
[0086] Browser module 147;
[0087] Calendar module 148;
[0088] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;
[0089] A widget creator module 150 for forming a user-created widget 149 - 6 ;
[0090] Search module 151;
[0091] Video and music player module 152, which merges the video player module and the music player module;
[0092] Note module 153;
[0093] Map module 154; and / or
[0094] Online video module 155.
[0095] Examples of other applications 136 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, voice recognition, and voice replication.
[0096] In combination with the touch screen 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 (for example, stored in the application internal state 192 of the contact module 137 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 the like.
[0097] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.
[0098] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.
[0099] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / 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 instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.
[0100] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
[0101] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.
[0102] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.
[0103] In conjunction with touch screen 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, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.
[0104] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
[0105] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.
[0106] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application that is optionally downloaded and used by a user (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm widget 149-4, and dictionary widget 149-5) or a mini-application created by a user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).
[0107] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the widget creator module 150 is optionally used by a user to create widgets (e.g., converting a user-specified portion of a web page into a widget).
[0108] In combination with the touch screen 112, display controller 156, contact / 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) in accordance with user instructions.
[0109] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 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 (trademark of Apple Inc.).
[0110] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the note module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.
[0111] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 is optionally used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
[0112] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications may be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on 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 on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.
[0113] Each of the modules and applications described above 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., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs (such as computer programs (e.g., including instructions)), processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.
[0114] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.
[0115] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.
[0116] Figure 1B 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 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).
[0117] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor 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 is to be delivered.
[0118] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by application 136-1, a state queue for enabling a user to return to a previous state or view of application 136-1, and a repeat / undo queue of previous actions taken by the user.
[0119] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
[0120] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).
[0121] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.
[0122] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.
[0123] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events that are identified as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.
[0124] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-events. 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 that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it is identified as the hit view.
[0125] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.
[0126] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.
[0127] 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 is part of another module stored in memory 102, such as contact / motion module 130.
[0128] In some embodiments, application 136-1 includes multiple 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 user interface of the application. Each application view 191 of application 136-1 includes one or more event identifiers 180. Typically, the corresponding application view 191 includes multiple event identifiers 180. In other embodiments, one or more event identifiers in event identifiers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.
[0129] The corresponding event identifier 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 identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).
[0130] Event receiver 182 receives event information from event classifier 170. 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 the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).
[0131] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sub-event sequence), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (e.g., 187-1 and / or 187-2) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
[0132] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view 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 an event handler associated with a sub-event and the object that triggered the hit test.
[0133] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.
[0134] When a corresponding event recognizer 180 determines that a sequence of sub-events 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 of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.
[0135] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.
[0136] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, 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 deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and executes a predefined process.
[0137] In some embodiments, the event delivery instructions 188 include 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 a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.
[0138] In some embodiments, 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 embodiments, 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 positioning 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 a touch-sensitive display.
[0139] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
[0140] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events that define the event to be distinguished.
[0141] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is illustrated. The touch screen 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 of these graphics by, for example, making gestures on the graphics 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, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. 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 rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.
[0142] The device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.
[0143] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.
[0144] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), the sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch sensitive sensor, and / or a contact intensity sensor (similar to the above reference Figure 1A Memory 370 optionally includes one or more storage devices located away from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.
[0145] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be realized with independent software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.
[0146] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.
[0147] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is illustrated. 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:
[0148] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;
[0149] Time 404;
[0150] Bluetooth indicator 405;
[0151] Battery status indicator 406;
[0152] A tray 408 with icons for commonly used applications, such as:
[0153] o An icon 416 of the phone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemails;
[0154] o an icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;
[0155] o An icon 420 labeled "Browser" of the browser module 147; and
[0156] o An icon 422 labeled “iPod” for the video and music player module 152 (also referred to as the iPod (trademark of Apple Inc.) module 152); and
[0157] Icons for other apps, such as:
[0158] o Icon 424 labeled "Message" of IM module 141;
[0159] o An icon 426 labeled “Calendar” of the calendar module 148;
[0160] o Icon 428 labeled “Photos” of the image management module 144;
[0161] o An icon 430 labeled “Camera” of the camera module 143;
[0162] ○ Icon 432 labeled “Online Video” of the online video module 155;
[0163] ○ Icon 434 labeled “Stock Market” of the Stock Market Widget 149 - 2 ;
[0164] o An icon 436 labeled “Map” of the map module 154;
[0165] ○ Icon 438 labeled “Weather” of the weather widget 149-1;
[0166] ○ Icon 440 labeled as “Clock” of the alarm clock widget 149 - 4 ;
[0167] o An icon 442 labeled “Fitness Support” of the fitness support module 142;
[0168] o An icon 444 labeled "Notes" of the notes module 153; and
[0169] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .
[0170] It should be noted that Figure 4A The illustrated icon labels are exemplary only. For example, the icon 422 of the video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.
[0171] Figure 4B The example embodiment has a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.
[0172] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.
[0173] Additionally, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.
[0174] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components related to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. Alternatively, or in addition to touch screen 504, device 500 also has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of contact (e.g., touch) applied. One or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.
[0175] 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 on 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 on 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 hereby incorporated by reference in its entirety.
[0176] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.
[0177] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include information about Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, I / O portion 514 may be connected to a 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 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.
[0178] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.
[0179] 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 that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including process 900 ( Fig. 9). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. 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 may 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 disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.
[0180] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.
[0181] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position 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), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).
[0182] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 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 off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, 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 intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.
[0183] Figure 6 Exemplary devices connected via one or more communication channels to participate in a transaction according to some embodiments are shown. 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.
[0184] 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. The payment account information includes, for example, one or more of the following: a person's name or company name, a billing address, a login name, a password, an account number, an expiration 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, the payment account information includes an image, such as a photo of a payment card (e.g., a photo taken by the device and / or received by the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receiving a credit card number, a debit card number, an account number or a gift card number and an expiration date input by the user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user or user device's account has previously made purchases or identified payment account data.
[0185] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500) so that the payment account information is securely stored on the electronic device. In some embodiments, 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 operated by the account's payment network (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program the account's payment information onto a secure element.
[0186] In some embodiments, the communication between the electronic devices 100, 300 and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, the first electronic device (e.g., 100) can be used as a configuration device or a management device, and can 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 the second electronic device (e.g., 500). As another example, the first electronic device (e.g., 100) can send data to the second electronic device, wherein the data reflects information about the payment transaction facilitated at the first electronic device. The information optionally includes one or more of the following: the payment amount, the account used, the purchase time, and whether to change the default account. The second device (e.g., 500) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).
[0187] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 558 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 556. Communications between user devices are optionally adjusted to reduce the possibility of improper sharing of information between devices. For example, communication regarding payment information requires that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.
[0188] In some embodiments, the electronic device (e.g., 100, 300, 500) is used to communicate with a point of sale (POS) payment terminal 550, which optionally supports NFC. The communication is optionally carried out using various communication channels and / or technologies. In some embodiments, the electronic device (e.g., 100, 300, 500) uses an NFC channel 560 to communicate with the payment terminal 550. In some embodiments, the payment terminal 550 uses a peer-to-peer NFC mode to communicate with the electronic device (e.g., 100, 300, 500). The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 550, which includes payment information of a payment account (e.g., a default account or an account selected for a specific transaction).
[0189] In some embodiments, conducting a transaction includes transmitting a signal including payment information of an account (such as a payment account). In some embodiments, conducting a transaction includes reconfiguring an electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (such as an NFC-enabled contactless payment card) and then transmitting the credentials of the account via NFC to, for example, a payment terminal 550. In some embodiments, after transmitting the credentials of the account via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before being reconfigured again to respond as a contactless payment card via NFC).
[0190] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 100, 300, 500). Before issuing payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting the electronic device being worn, detecting button presses, detecting password input, detecting touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting fingerprint signatures, detecting voice or voice commands, and / or detecting gestures or movements (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., NFC communication channel) with another device (e.g., payment terminal 550) is established within a defined time period from when the input is detected, the security element releases payment information so that it is transmitted to another device (e.g., payment terminal 550). In some embodiments, the security element is a hardware component that controls the release of security information. In some embodiments, the security element is a software component that controls the release of security information.
[0191] In some embodiments, the protocol associated with transaction participation depends on, for example, the device type. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generation condition and / or a transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after security verification), while a corresponding condition for a phone does not require a button press, but requires detection of a specific interaction with an application. In some embodiments, conditions for transmitting and / or publishing payment information include receiving specific input on each of a plurality of devices. For example, the release of payment information optionally requires detection of a fingerprint and / or password at a device (e.g., device 100), as well as detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).
[0192] Payment terminal 550 optionally uses the payment information to generate a signal for transmission to payment server 554 to determine whether the payment is authorized. Payment server 554 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether the proposed purchase is authorized. In some embodiments, payment server 554 includes a server of an issuing bank. Payment terminal 550 communicates directly with payment server 554 or indirectly via one or more devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).
[0193] Payment server 554 optionally uses at least some of the payment information to identify the user account from a database of user accounts (e.g., 552). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the information from the POS communication. In some embodiments, payment is rejected when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, debit card number, or gift card number) or when no account includes payment information that matches the information from the POS communication.
[0194] In some embodiments, the user account data further identifies one or more constraints (e.g., credit limit); current or previous balances; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 554) uses such data to determine whether to authorize a payment. For example, the payment server denies payment when the purchase amount added to the current balance would cause the account limit to be exceeded, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.
[0195] In some embodiments, the payment server 554 responds to the POS payment terminal 550 with an indication of whether the proposed purchase is authorized or rejected. In some embodiments, the POS payment terminal 550 transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, when the purchase is authorized (e.g., via a transaction coordination server that manages a transaction application on a user device), the POS payment terminal 550 sends a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminal 550 presents an output (e.g., a visual output or an audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process, or may be transmitted later.
[0196] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in transactions that are completed without involving the POS payment terminal 550. For example, upon detecting that the mechanical input has been received, the secure element in the electronic device (e.g., 100, 300, 500) releases the payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).
[0197] In some embodiments, the electronic device (e.g., 100, 300, 500) is in a locked state or an unlocked state. In the locked state, the electronic device is powered on and is operable, but it is blocked from performing a predefined set of operations in response to user input. The 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 unconscious or unauthorized use of some functions of the electronic device, or to activate or deactivate some functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and is operable, and is not blocked from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.
[0198] When the device is in the locked state, the device is said to be locked. In some embodiments, the device in the locked state can respond to a restricted set of user inputs, including inputs corresponding to attempts to convert the device to the unlocked state or inputs corresponding to shutting down the device.
[0199] In some embodiments, the security element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the security element provides (or publishes) payment information (e.g., account number and / or transaction-specific dynamic security code). In some embodiments, the security element provides (or publishes) payment information in response to the device receiving authorization, and the authorization is, for example, user authentication (e.g., fingerprint authentication; password authentication; when the device is in an unlocked state, and optionally when the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, a double press of the hardware button is detected, wherein the device is determined to be in contact with the user's skin by periodically checking that the device is in contact with the user's skin. The device detects a fingerprint at the fingerprint sensor of the device (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint is consistent with the registered fingerprint. Based on determining that the fingerprint is consistent with the registered fingerprint, the security element provides (or publishes) payment information. Based on determining that the fingerprint is inconsistent with the registered fingerprint, the security element abandons providing (or publishing) payment information.
[0200] As used herein, an "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 (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application using an installer that extracts program portions from a downloaded software package and integrates the extracted portions with the operating system of a computer system.
[0201] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
[0202] 7A to 7I Illustrated are exemplary user interfaces for initiating a transfer of a remote data store associated with a user account (e.g., a computer storage management account) according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig. 9 In some cases, a computer storage management account may be referred to herein as a computer storage account, a data storage management account, a data storage account, etc.
[0203] Fig. 7A An electronic device 700 is illustrated. Fig. 7A In the embodiment, electronic device 700 is a portable multifunction device and has one or more components described above with respect to one or more of devices 100, 300 and 500.
[0204] exist Fig. 7A , the electronic device 700 displays a user interface 710 of a transfer application (e.g., an electronic wallet application) on a display 702 (e.g., a touch screen 702). In some embodiments, the user interface 710 includes representations 712 (or portions thereof) corresponding to different accounts (e.g., transfer accounts) configured on the electronic device 700. As shown, the representation 712 includes, for example, a representation 712a corresponding to a computer storage management account and a representation 712b corresponding to a transportation account. In some embodiments, the representation 712a corresponds to a computer storage management account issued (or branded) by a first-party manufacturer. In some embodiments, the user interface 710 includes representations 714 (e.g., representations 714a-714c) corresponding to various other accounts (e.g., transfer accounts, points cards, and / or reward cards) configured on the electronic device 700 or otherwise linked to the electronic device, identification cards (e.g., student identification cards and / or government-issued identification cards), and / or tickets (e.g., event tickets and / or boarding passes).
[0205] In some embodiments, the user account is a computer storage management account that provides access to (e.g., cloud-based) computer storage resources. In some embodiments, the user account allows the user to store data to and delete data from a computer storage resource accessible via the account (e.g., a remote, cloud-based computer storage space that is not local to the electronic device 100). In some embodiments, the data may be different types of data, 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.
[0206] In some embodiments, the amount of computer storage resources of a computer storage management account may be modified. For example, as described in further detail below, in some cases, the computer storage resources of the account are transferred to or received from another computer storage management account, such that the amount of computer storage resources associated with the account is reduced or increased, respectively.
[0207] When displaying user interface 710, device 700 detects selection of representation 712a corresponding to a computer storage management account. The selection is a tap gesture 701 on representation 712a. Figure 7B As shown in , in response to detecting tap gesture 701 , device 700 displays storage account interface 720 .
[0208] In some embodiments, the storage account interface 720 includes a storage transfer history 722, which shows a plurality of recent account activities corresponding to a request to transfer a computer storage resource. As an example, the storage transfer history 722 includes a first transfer 722a corresponding to a request to transfer a certain amount (e.g., 50MB) of computer storage resources from another user account to a computer storage management account. As another example, the storage transfer history 722 includes a second transfer 722b corresponding to a request to transfer a certain amount (e.g., 150MB) of computer storage resources from a computer storage management account to another user account. As shown, each of the transfers 722 includes a date indicating the date on which the transfer request was made (or when the corresponding operation was completed).
[0209] In some embodiments, the storage account interface 720 also includes a filter indicator 724 that, when selected, filters the storage transfer history 722 so that a user can view a select set of transfers (e.g., transfers corresponding to requests to transfer computer storage resources to a computer storage management account) of the storage transfer history 722 in the storage account interface 720.
[0210] In some embodiments, storage account interface 720 also includes transfer affordance 726, which, when selected, initiates a process for requesting a transfer of computer storage resources associated with a computer storage management account. For example, when storage account interface 720 is displayed, device 700 detects a selection of request affordance 726. In some embodiments, the selection is a tap gesture 728 on affordance 726. Figure 7C As shown in , in response to detecting tap gesture 728, device 700 displays selection interface 730. In some embodiments, selection interface 730 is overlaid on storage account interface 720.
[0211] In general, selection interface 730 allows a user of device 700 to select a contact (e.g., a contact stored on device 700) as the recipient of the transfer request. For example, when selection interface 730 is displayed, device 700 detects a selection of contact 732b (e.g., "Jane Appleseed") in contacts 732. In some embodiments, the selection is a tap gesture 734 on contact 732b. Fig.7D As shown in , once a contact has been selected and optionally confirmed (e.g., by selecting Figure 7C The next indicator in the figure indicates 736), and the device 700 displays the quantity user interface 740.
[0212] In some embodiments, the quantity user interface 740 can be used to specify the amount of computer storage resources to be transferred. For example, when the quantity user interface 740 is displayed, the device 700 detects a set of inputs specifying the amount of computer storage resources. FIG. 7D to FIG. 7E As shown in , device 700 detects a set of inputs (eg, inputs 748a, 748b) that specify an amount of 20MB.
[0213] In some embodiments, quantity user interface 740 may also be used to specify the type of transfer request. For example, in response to detecting input specifying an amount of computer storage resources, device 700 modifies the visual characteristics of request enable indication 744 and transfer enable indication 746 to indicate that request enable indication 744 and transfer enable indication 746 have become selectable (e.g., transitioned from an unselectable state to a selectable state). In some embodiments, modifying the visual characteristics of the enable indication in this manner includes changing the color of the enable indication, the shape of the enable indication, the size of the enable indication, or any combination thereof. Thereafter, device 700 detects a selection of request enable indication 744 or transfer enable indication 746. In response to selection of request enable indication 744, device 700 initiates a process for requesting that computer storage resources be transferred from the account of the selected contact to a computer storage management account.
[0214] In response to selection of transfer affordance 746, device 700 initiates a process for requesting a transfer of computer storage resources from a computer storage management account to an account of the selected contact. For example, while displaying quantity user interface 740, device 700 detects selection of transfer affordance 746. In some embodiments, the selection is a tap gesture 750 on transfer affordance 746. Figure 7F As shown in , in response to detecting selection of the transmit enable indication 746, the device 700 displays a messaging interface 760 (e.g., of a messaging application).
[0215] In some embodiments, the message interface 760 includes a request 762 (displayed as a transfer message object) that is a request to transfer an indicated amount of computer storage resources (e.g., 20 MB) to the selected contact. In some embodiments, the request 762 is displayed in the composition area of the message interface 760 to indicate that the request to transfer computer storage resources has not yet been sent to the selected contact. In some embodiments, the request 762 indicates an amount specified by the user. In some embodiments, the message interface 760 also includes an input box 768 in which comments (e.g., "movie storage space") and / or other information describing the request can be provided. Figure 7G As shown in Figure 7F In response to selection of transmit affordance 764 (e.g., tap gesture 766 on transmit affordance 764), device 700 displays confirmation interface 770. In some embodiments, confirmation interface 770 is overlaid on at least a portion of messaging interface 760.
[0216] Confirmation interface 770 includes an account indicator 772, a transfer summary 774, and input instructions 776. Account indicator 772 identifies the computer storage management account and optionally lists the amount of computer storage resources currently associated with the computer storage management account. In some embodiments, transfer summary 774 indicates the type of request to be provided (e.g., transfer, request), the selected contact, and / or the amount of computer storage resources to be transferred. Input instructions 776 indicate that in response to a double press (e.g., "double-click") of button 704, the request will be provided (e.g., to the selected contact). Figure 7G At , device 700 detects a double press input 778 on button 704 .
[0217] In response to detecting double press input 778, device 700 provides a request to transfer computer storage resources to the selected contact. Figure 7HAs shown in , after providing the request, the device 700 adds the request to the storage transfer history 722 in the storage account interface 720 (e.g., as transfer 722c). Because the selected contact has not yet accepted the request, the request is indicated as "pending". Fig.7I As shown in , once the selected contact accepts the request, the request is fulfilled (eg, 20 MB of computer storage resources are transferred from the computer storage management account to Jane Appleseed's user account) and the transfer 722c is no longer indicated as "pending."
[0218] Although the present invention is related to responding to detecting a double-click input 728 ( Figure 7G ), it should be understood that the request to transfer computer storage resources may be provided in response to a plurality of other inputs detected during the process of providing the transfer request. As an example, in some cases, the request to transfer ( Fig.7D , Fig. 7E ). In this manner, device 700 may optionally forgo displaying message interface 760 and / or user confirmation (eg, as provided by double-click input 728) prior to transmitting the request.
[0219] In some embodiments, the manner in which one or more elements of the user interface described herein are presented may vary. As an example, in some embodiments, the transfer affordance 726 ( Figure 7B ) may be replaced by both a request affordance that, when selected, initiates a process for requesting the transfer of computer storage resources from another user account to a computer storage management account, and a transfer affordance that, when selected, initiates a process for requesting the transfer of computer storage resources from a computer storage management account to another user account. Additionally or alternatively, in some embodiments, request affordance 744 and transfer affordance 746 ( Fig.7D , Fig. 7E ) may be replaced by a confirmation indication which, when selected, confirms the amount of computer storage resources indicated by the user.
[0220] FIG. 8A to FIG. 8AE Illustrated are exemplary user interfaces for initiating transactions between user accounts (e.g., transferring accounts) according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig. 9 process.
[0221] In some embodiments, the user account is a transfer account. In some embodiments, the transfer account is a first-party transfer account (e.g., a transfer account issued or branded by, for example, an electronic device manufacturer), and optionally provides rewards (e.g., cash back rewards, additional points rewards) based on the amount of transfers (e.g., payment transactions and / or points transfers) made using the transfer account and / or made using different accounts (e.g., cash back rewards based on a specific percentage of the value of each transaction). In some embodiments, the transfer account is a points account (e.g., for dining points, printer credits, and / or loyalty points) that provides rewards (e.g., points rewards) based on the amount of points used using the transfer account.
[0222] FIG. 8A to FIG. 8I An example is illustrated in which a user provides a request to transfer funds from a transfer account to another user's account.
[0223] Fig. 8A An electronic device 800 is illustrated. Fig. 8A In the embodiment, electronic device 800 is a portable multifunction device and has one or more components described above with respect to one or more of devices 100 , 300 , and 500 .
[0224] exist Fig. 8A , the electronic device 800 displays a user interface 810 of a transfer application (e.g., an electronic wallet application) on a display 802 (e.g., a touch screen 802). In some embodiments, the user interface 810 includes representations 812 corresponding to different transfer accounts (e.g., payment accounts, such as third-party credit card accounts, debit card accounts, and / or stored value accounts; points accounts; and / or rewards accounts) configured on the electronic device. As shown, the representation 812 includes, for example, a representation 812a corresponding to a transfer account and a representation 812b corresponding to a transportation account. In some embodiments, the representation 812a corresponds to a first-party transfer account. In some embodiments, the user interface 810 includes representations 814 (e.g., representations 814a-814c) corresponding to various other accounts (e.g., transfer accounts, points cards, and / or rewards cards) configured on the electronic device 800 or otherwise linked to the electronic device, identification cards (e.g., student identification cards and / or government-issued identification cards), and / or tickets (e.g., event tickets and / or boarding passes).
[0225] When displaying user interface 810, device 800 detects selection of representation 812a corresponding to the transfer account. In some embodiments, selection of representation 812a is a tap gesture 801 on representation 812a of the transfer account. Figure 8B As shown in , in response to detecting tap gesture 801 , device 800 displays a transfer account interface 820 .
[0226] In some embodiments, the transfer account interface 820 includes a transfer history 822 that shows a plurality of recent account activities corresponding to previously requested transfers (e.g., fund transfers) associated with the transfer account. As an example, the transfer history 822 includes a first transfer 822a corresponding to a request to transfer a specified amount (e.g., $50.00) to the transfer account. As another example, the transfer history 822 includes a second transfer 822b corresponding to a request to transfer a specified amount (e.g., $156.91) from the transfer account. As shown, the first transfer 822a and the second transfer 822b of the transfer 822 include corresponding dates, which indicate, for example, the date on which the transfer request was made (or when the corresponding operation was completed).
[0227] In some embodiments, the transfer account interface 820 also includes a filter indicator 824, which, when selected, filters the transfer history 822 so that a user can view a select set of transfers in the transfer history 822 (e.g., transfers corresponding to requests to transfer funds to a transfer account).
[0228] In some embodiments, transfer account interface 820 also includes transfer enable representation 826, which, when selected, initiates a process for requesting a transfer using a transfer account. For example, when transfer account interface 820 is displayed, device 800 detects a selection of transfer enable representation 826. In some embodiments, the selection is a tap gesture 828 on transfer enable representation 826. Figure 8C As shown in , in response to detecting the tap gesture 828, the device 800 displays a selection interface 830. In some embodiments, the selection interface 830 is overlaid on the transfer account interface 820.
[0229] In general, selection interface 830 allows a user of device 800 to select a contact (e.g., a contact stored on device 800) as the recipient of the transfer request. For example, when selection interface 830 is displayed, device 800 detects a selection of contact 832b (e.g., "Jane Appleseed") in contacts 832. In some embodiments, the selection is a tap gesture 834 on contact 832b. Fig.8D As shown in , once a contact has been selected and optionally confirmed (e.g., by selecting next enable indication 836), device 800 displays quantity user interface 840.
[0230] In some embodiments, the amount user interface 840 may be used to specify an amount of funds to be transferred. For example, when the amount user interface 840 is displayed, the device 800 detects a set of inputs specifying an amount. FIG. 8D to FIG. 8EAs shown, device 800 detects a set of inputs (eg, inputs 848a and 848b) at keyboard 842 specifying an amount (eg, $20.00).
[0231] In some embodiments, the amount user interface 840 can also be used to specify the type of transfer request. For example, in response to detecting a set of inputs specifying an amount to be transferred, the device 800 modifies the visual characteristics of the request enable indication 844 and the payment enable indication 846 to indicate that the request enable indication 844 and the payment enable indication 846 have become selectable. In some embodiments, modifying the visual characteristics of the enable indication in this manner includes changing the color of the enable indication, the shape of the enable indication, the size of the enable indication, or any combination thereof. Thereafter, the device 800 detects a selection of the request enable indication 844 or the payment enable indication 846. In response to the selection of the request enable indication 844, the device 800 initiates a process for requesting that funds be transferred from the account of the selected contact to the transfer account.
[0232] In response to the selection of payment enabling representation 846, device 800 initiates a process for requesting to transfer funds from the transfer account to the account of the selected contact. For example, when amount user interface 840 is displayed, device 800 detects the selection of payment enabling representation 846. The selection is a tap gesture 850 on payment enabling representation 846. Figure 8F As shown in , in response to detecting selection of payment enable indication 846, device 800 displays a messaging interface 860 (e.g., of a messaging application).
[0233] In some embodiments, the message interface 860 includes a request 862 (displayed as a transfer message object) that is a request to transfer an indicated amount of funds (e.g., $20.00) to the account of the selected contact. In some embodiments, the request 862 is displayed in the composition area of the message interface 860 to indicate that the request to transfer funds has not yet been sent to the selected contact. In some embodiments, the request 862 indicates an amount specified by the user. In some embodiments, the message interface 860 also includes an input box 868 in which information describing the request (e.g., "movie tickets") can be provided. Figure 8G As shown in , in response to selection of transmit affordance 864 (e.g., tapping gesture 866 on transmit affordance 864), device 800 displays confirmation interface 870. In some embodiments, confirmation interface 870 is overlaid on at least a portion of messaging interface 860.
[0234] Confirmation interface 870 includes account indicator 872, transfer summary 874, and input instructions 876. Account indicator 872 identifies the transfer account and optionally lists the balance currently associated with the transfer account. In some embodiments, transfer summary 874 indicates the type of request to be provided (e.g., transfer or request), the selected contact, and / or the amount of funds to be transferred. Input instructions 876 indicate that in response to a double press (e.g., "double-click") of button 804, the request will be provided to the selected contact. Figure 8G , device 800 detects a double press input 878 on button 804 .
[0235] In response to detecting the double press input 878, the device 800 provides a request to transfer funds to the selected contact. Figure 8H As shown in , after providing the request, the device 800 adds the request to the transfer history 822 in the transfer account interface 820 (e.g., as transfer 822c). In some embodiments, the display is displayed in response to detecting the double press input 878. Figure 8H user interface (e.g., without displaying the request as part of a transcript of a conversation between the user of device 800 and the selected contact, or after displaying the request as part of the conversation). Figure 8H , the request is indicated as "pending" because the selected contact has not yet accepted the request. Fig.8I As shown in , once the selected contact receives and accepts the request, the request is fulfilled (eg, $20.00 is transferred to Jane Appleseed's account) and the transfer 822c is no longer indicated as "pending."
[0236] In some embodiments, after the selected contact accepts the request, the selected contact's device provides (e.g., displays) one or more notifications corresponding to the transaction. Fig.8I , after the selected contact has accepted the request, a device 880 (e.g., Jane Appleseed's device) associated with the selected contact displays notification 884 and / or notification 886. In some embodiments, notification 884 indicates the amount (e.g., $20.00) that has been transferred to the selected contact's account as a result of the transfer, and optionally information describing one or more aspects of the transfer, such as a note (e.g., "movie tickets") originally provided with the request. In some embodiments, notification 886 indicates that the selected contact's account has received the funds, and optionally indicates the new balance of the account (e.g., $25.00). In some embodiments, displaying notifications corresponding to 804 and 806 at device 800 provides feedback to the user of device 800 that the request has been accepted and the new balance of the transfer account of the user of device 800.
[0237] Although the present disclosure is directed to responding to detecting a double-click input 828 ( Figure 8G ) is described as providing a request to transfer funds, but it should be understood that the request to transfer funds may optionally be provided in response to a plurality of other inputs detected during the process of providing the request. As an example, in some cases, the request ( Fig.8D , Fig. 8E ). In this manner, device 800 may optionally forgo displaying message interface 860 and / or user confirmation (eg, as provided by double-click input 828) prior to transmitting the request.
[0238] In some embodiments, the manner in which one or more elements of the user interface described herein are displayed can vary. As an example, in some embodiments, the transfer affordance 826 ( Figure 8B ) may be replaced by both a request enable indication and a payment enable indication, wherein the request enable indication, when selected, initiates a process for requesting to transfer funds from another user account to the transfer account, and the payment enable indication, when selected, initiates a process for requesting to transfer funds from the transfer account to another user account. Additionally or alternatively, in some embodiments, request enable indication 844 and payment enable indication 846 ( Fig.8D , Fig. 8E ) may be replaced by a confirmation indicator which, when selected, confirms the amount of funds indicated by the user.
[0239] In some embodiments, Figure 8B (as well as Figure 8T ) when selected causes device 800 to display two options for making a transfer request: an option for transferring funds and an option for requesting funds. In some embodiments, these two options are overlaid on transfer account interface 820. In response to detecting a selection of one of the two options (e.g., a selection of the option for transferring funds or a selection of the option for requesting funds), device 800 displays selection interface 830 and continues the technique. In some embodiments, because the user has selected whether to transfer or request funds, request enable representation 844 and payment enable representation 846 ( FIG. 8D to FIG. 8E and / or Figure 8V to Figure 8W ) may be replaced by a confirmation indicator which, when selected, confirms the amount of funds displayed.
[0240] Reference again Fig.8I In some embodiments, the user can filter the display of the transfer history, such as transfer history 822 ( Figure 8B ). For example, Fig.8IAs shown in , when the transfer account interface 820 is displayed, the device 800 detects a selection of the filter enable representation 824. In some embodiments, the selection is a tap gesture 892 on the filter enable representation 824. Figure 8J As shown in , in response to detecting the tap gesture 892, the device 800 displays the filter menu 890. In some embodiments, the filter menu 890 is overlaid on the transfer account interface 820.
[0241] The filter menu 890 includes filter options 890a-890f, each of which corresponds to a particular way in which the transfer history 822 can be filtered. Filter option 890a (e.g., "All") causes the device 800 to filter the transfer history so that all transfers are included in the results (e.g., remove any existing filters so that no filters are applied) and / or so that no transfers are excluded from the results (e.g., the displayed results). Filter option 890b ("Requested") causes the device 800 to filter the transfer history 822 so that only transfers corresponding to pending requests to transfer funds from a transfer account to another account are included in the results (e.g., the displayed results). Filter option 890d ("Daily Cash") causes the device 800 to filter the transfer history 822 so that only transfers corresponding to rewards (e.g., cash rewards) earned for the transfer account are included in the results (e.g., the displayed results). Filter option 890e ("Pending Requests") causes device 800 to filter transfer history 822 so that only pending requests to transfer funds from another account to the transfer account are included in the results (e.g., displayed results). Filter option 890f ("Purchases") causes device 800 to filter transfer history 822 so that only transfers corresponding to purchases made using funds from the transfer account are included in the results (e.g., displayed results).
[0242] Filter option 890c ("Paid") causes device 800 to filter transfer history 822 so that only transfers corresponding to completed requests to transfer funds from a transfer account to another account are included in the results (e.g., displayed results). Figure 8J As shown in , when the filter menu 890 is displayed, the device 800 detects a selection of the filter option 890c. In some embodiments, the selection of the filter option 890c is a tap gesture 892. Figure 8KAs shown in , in response to detecting tap gesture 892, device 800 filters transfer history 822 according to a "paid" filter (e.g., only completed transfers of funds transfers from a transfer account to another user account are included in the results). In some embodiments, when a filter is applied to transfer history 822, device 800 modifies one or more visual characteristics of filter indicator 824 (e.g., darkens or highlights), for example, to indicate that transfer history 822 is filtered.
[0243] In some embodiments, transfer account interface 820 includes a search affordance that can be used to search transfer history 822. For example, while transfer account interface 820 is displayed, device 800 detects a selection of search affordance 894. In some embodiments, the selection is a tap gesture 896 on search affordance 894. Figure 8L As shown in , in response to detecting selection of search enable indication 894, device 800 displays search interface 800A.
[0244] Search interface 800A includes multiple affordances, according to which transfer history 822 can be searched. As an example, search interface 800A includes filter affordances 802A, which correspond to filter options 890b-890f, respectively. In response to detecting selection of filter affordances 802A, device 800 filters transfer history 822 in the manner previously described with respect to filter options 890b-890f.
[0245] As another example, search interface 800A includes contact affordances 804A, each of which corresponds to a contact (e.g., a friend, family member, and / or colleague) stored at device 800. In some examples, contact affordances 804A additionally or alternatively include affordances corresponding to user accounts that have been transferred within a threshold amount of time (e.g., within the last 10 days, within the last 30 days). In some embodiments, contact affordances 804A additionally or alternatively include affordances corresponding to user accounts that have been recently transferred (e.g., contacts that have been transferred the last 6 times). In response to detecting a selection of contact affordance 804A, device 800 filters transfer history 822 based on the selected contact affordance 804A. For example, if device 800 detects a selection of contact affordance 804Aa corresponding to contact "John Appleseed," device 800 filters transfer history 822 so that only transfers associated with (e.g., from and / or to) contact "John Appleseed" are displayed.
[0246] As yet another example, search interface 800A includes merchant affordances 806A, each of which corresponds to a merchant. In some embodiments, merchant affordances 806A correspond to a predetermined group of merchants (e.g., as determined by the manufacturer of device 800) and / or merchants with which transfers have been made within a threshold amount of time. In response to detecting a selection of merchant affordance 806A, device 800 filters transfer history 822 based on the selected merchant affordance 806A. For example, if device 800 detects a selection of merchant affordance 806A corresponding to merchant "W," device 800 filters transfer history 822 so that only transfers associated with merchant "W" are displayed.
[0247] Figure 8M to Figure 8S An example operation is illustrated in which a user has received a request to transfer funds from a transfer account to another user's account.
[0248] FIG. 8M to FIG. 8O Various notifications are described that indicate that a request has been received to transfer funds from a transfer account. Figure 8M , device 800 displays a notification 810A on the lock screen interface indicating that another user (e.g., "Annie Fuji") has provided a request to transfer a specified amount of funds (e.g., "$8.50") from a transfer account. In some embodiments, notification 810A also includes information about the requested transfer, such as a note indicating the reason for the request ("Sunday brunch").
[0249] In some cases, a user associated with a transfer account may not approve a funds transfer request upon receipt of the request. The user may choose not to approve the request (but not reject it), or may simply forget to approve the request despite their intent to do so. Thus, if a predetermined amount of time has passed since receipt of the funds transfer request (e.g., 14 days or 29 days) and / or a predetermined amount of time remains before the request expires (e.g., 1 day or 1 week), device 800 displays one or more notifications reminding the user of the previous request. In some embodiments, such a notification is displayed on a lock screen interface (e.g., Figure 8N 814A) and / or displayed in the user interface of the transfer application (e.g., Fig.8O Notice 820A). Figures 8N to 8O As shown in , a notification displayed in this manner indicates the date of the request to transfer funds and, optionally, when the request will expire.
[0250] In some embodiments, selecting a notification displayed by device 800 indicating that a funds transfer has been requested initiates a process for accepting or declining the request. As an example, in response to detecting a selection of notification 810A (or either of notifications 814A, 820A), device 800 displays transfer account interface 820, such as Figure 8P . Because a request to transfer funds is pending, the transfer account interface 820 includes request 830A. In some embodiments, request 830A is displayed above the transfer history 822 so that request 830A is displayed in a prominent manner. Request 830A includes a release option 832A, which can be used to remove request 830A from the transfer account interface 820 and optionally reject request 830A. For example, when the transfer account interface 820 is displayed, the device 800 detects a selection of the release option 832A. In some embodiments, the selection is a tap gesture 834A on the release option 832A. Figure 8Q As shown in , in response to detecting tap gesture 834A, device 800 displays rejection interface 840A. In some embodiments, rejection interface 840A is overlaid on at least a portion of transfer account interface 820.
[0251] The rejection interface 840 includes a release enable indication 842A, which when selected causes the device 800 to remove the request 830A from the transfer account interface 820. In some embodiments, the request 830A is permanently removed. In other embodiments, the request 830A is removed for a period of time so that the user is reminded about the pending request later. The rejection interface 840A also includes a rejection enable indication 844A, which when selected causes the device 800 to remove the request 830A from the transfer account interface 820 and reject the request to transfer funds from the transfer account. In some embodiments, rejecting the request causes the transfer history 822 to be updated to reflect that the request is rejected (e.g., by including request information with a crossed-out font style).
[0252] refer to Figure 8P , request 830A also includes an acceptance indication 836A, which can be used to initiate the process of accepting the request to transfer funds associated with request 830A. For example, when the transfer account interface 820 is displayed, the device 800 detects a selection of the acceptance indication 836A. In some embodiments, the selection is a tap gesture 832A on the acceptance indication 836A. In some embodiments, in response to detecting the tap gesture 836A, the device 800 displays a confirmation interface 860A (e.g., Figure 8S 820) to authorize the transfer. Figure 8RAs shown in , in response to detecting tap gesture 838A, device 800 displays message interface 850A (eg, of a messaging application).
[0253] In some embodiments, the message interface 850A includes an approval 852A (displayed as a transfer message object) that, when activated, approves (e.g., accepts) the transfer of funds (e.g., $8.50) from the transfer account in accordance with the received request. In some embodiments, the approval 852A is displayed within the composition field of the message interface 850A to indicate that the approval has not yet been transmitted. In some embodiments, the approval 852A indicates the amount of funds to be transferred from the transfer account. Figure 8S As shown in , in response to selection of transmit affordance 854A (e.g., tap gesture 856A on transmit affordance 854A), device 800 displays confirmation interface 860A. In some embodiments, confirmation interface 860A is overlaid on at least a portion of messaging interface 850A.
[0254] Confirmation interface 860A includes account indicator 862A, transfer summary 864A, and input instructions 866A. Account indicator 862A identifies the transfer account and optionally lists the balance currently associated with the transfer account. In some embodiments, transfer summary 864A provides details of the transfer, including the amount of funds to be transferred. Input instructions 866A indicates that the request will be accepted in response to a double press (e.g., "double-click") on button 804. Figure 8S At , device 800 detects double press input 868A on button 804.
[0255] In response to detecting double press input 868A, device 800 approves the request to transfer funds. Figure 8T As shown in , after accepting the request, device 800 adds the corresponding transfer to transfer history 822 in account summary interface 820 (eg, as transfer 822d).
[0256] Figures 8T to 8Y An example is shown in which a user provides a request to transfer funds from another user's account to a transfer account.
[0257] exist Figure 8T , device 800 displays transfer account interface 820. When transfer account interface 820 is displayed, device 800 detects a selection of transfer enable representation 826. The selection is a tap gesture 870A on transfer enable representation 826. Figure 8U As shown in , in response to detecting tap gesture 870A, device 800 displays selection interface 830.
[0258] As depicted, selection interface 830 allows a user to select a contact as a recipient of a transfer request. For example, when selection interface 830 is displayed, device 800 detects a selection of contact 832c (e.g., “Sam Jones”) in contacts 832. The selection is a tap gesture 872A on contact 832c. Figure 8V As shown in , once a contact has been selected and optionally confirmed (e.g., by selecting next enable indication 836), device 800 displays quantity user interface 840.
[0259] When the quantity user interface 840 is displayed, the device 800 detects a set of inputs specifying an amount. Figure 8V to Figure 8W As shown, device 800 detects a set of inputs at keyboard 842 (eg, inputs 874A, 876A) specifying an amount of $35.00.
[0260] like Figure 8W As shown in , in response to detecting a set of inputs specifying an amount to be transferred, device 800 modifies the visual characteristics of request enable indication 844 and payment enable indication 846 to indicate that request enable indication 844 and payment enable indication 846 have become selectable. Thereafter, device 800 detects a selection of payment enable indication 846. In response to the selection of request enable indication 844 (e.g., a tap gesture 878A on request enable indication 844), device 800 initiates a process for requesting that funds be transferred from an account of a selected contact (e.g., “Sam Jones”) to a transfer account. For example, as Figure 8X As shown in , in response to detecting selection of request enable indication 844, device 800 displays a messaging interface 860 (e.g., of a messaging application).
[0261] In some embodiments, the message interface 860 includes a request 880A (displayed as a transfer message object) to transfer an indicated amount of funds (e.g., $35.00) from the account of the selected contact to the transfer account. In some embodiments, the request 880A is displayed in the composition bar of the message interface 860 to indicate that the request has not yet been transmitted to the selected contact. In some embodiments, the request 880A indicates an amount specified by the user. In some embodiments, the message interface 860 also includes an input box 868, in which information describing the request (e.g., "team expenses") can be provided. In response to the selection of the transmission enable representation 864 (e.g., a tap gesture 882A on the transmission enable representation 864), the device 800 provides the request to the selected contact.
[0262] Thereafter, the request is added to the transfer account interface 820 as a pending request. Figure 8Y, transfer account interface 820 includes request 882A, which corresponds to a request to transfer funds from an account of a selected contact (e.g., "Sam Jones") to a transfer account. In some embodiments, request 882A indicates the time when the request expires.
[0263] In some embodiments, the user can cancel the request after it has been provided (e.g., it is still pending). For example, when the transfer account interface 820 is displayed, the device 800 detects a selection of the request 882A. In some embodiments, the selection is a tap gesture 890A on the request 882A. Figure 8Z As shown in , in response to detecting tap gesture 890A, device 800 displays contacts interface 892A.
[0264] Contacts interface 892A includes transfer history 894A, which shows a number of recent account activities corresponding to requests to transfer funds between a transfer account and an account of a selected contact (e.g., "Sam Jones"). Contacts interface 892A also includes pending requests 896A, which shows pending requests to transfer funds between a transfer account and an account of a selected contact. As shown, pending requests 896A include request 882A.
[0265] When displaying contact interface 892A, device 800 detects selection of request 882A. In some embodiments, the selection is a tap gesture 898A on request 882A. Figure 8AA As shown in , in response to detecting tap gesture 890A, device 800 displays transfer details interface 800B.
[0266] Transfer details interface 800B includes various information about request 882A, such as the time the request was made, the time the request expires, and / or the amount specified by the request. Transfer details interface 800B also includes a cancel affordance 802B, which cancels request 882A when selected.
[0267] In some cases, a user may provide a request to transfer funds from another user account to a transfer account, but the request has not been processed within a period of time (e.g., 15 days or 30 days). In response, device 800 displays a notification reminding the user that the request has not been processed. Figure 8AB As shown in, for example, device 800 displays notification 804B indicating that a previously provided request will expire (or be automatically rejected) at a specific date and / or time (e.g., "tomorrow"). In some embodiments, notification 804B indicates that a reminder about the request has been provided to the selected contact.
[0268] If the request is not accepted within a predetermined period or time, the request expires (or is rejected). Figure 8AC , after request 882A is rejected (e.g., due to expiration), device 800 adds transfer 822c to transfer history 822. In some embodiments, requests that are not accepted or rejected within a predetermined time period are identified as "expired." In this example, transfer 822c indicates that the transfer was rejected, and optionally, the amount of funds to be transferred is shown with a middle strikethrough, further indicating that the transfer request was rejected and no transfer occurred.
[0269] In some cases, a user may retransmit an expired request. For example, when the transfer account interface 820 is displayed, the device 800 detects a selection of request 822C. The selection is a tap gesture 806B on transfer 822e. Figure 8AD As shown in , in response to detecting tap gesture 806B, device 800 displays contacts interface 892A.
[0270] Because the request expires, transfer history 894A of contacts interface 82A includes transfer 894Aa corresponding to the expiration request. In response to selection of transfer 894Aa (eg, tap gesture 810B on transfer 894Aa), device 800 displays transfer details interface 812B.
[0271] Transfer details interface 800B includes various information about due request 882A, such as the time when the request was made, the time when the request expires, and / or the amount specified by the request. Transfer details interface 812B also includes a retransmission enabling indication 814B, which retransmits request 882A to the selected contact when selected.
[0272] Fig. 9 900 is a flowchart illustrating a method for initiating a transfer of a user account using an electronic device according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 700, 800) (e.g., a smart watch, a smart phone, and / or a personal computer) that communicates with a display generation component (e.g., an integrated display and / or a display controller) and one or more input devices (e.g., a touch-sensitive surface (e.g., a touch screen), a mouse, and / or a keyboard). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0273] As described below, method 900 provides an intuitive way to initiate transactions. The method reduces the cognitive burden of a user initiating a transaction, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to initiate transactions faster and more efficiently saves power and increases the time interval between battery charges.
[0274] A computer system (e.g., 700, 800) simultaneously displays (902) via a display generation component (e.g., 702, 802) a portion (e.g., all or less than all) of a first visual representation (e.g., 712a, 812a) corresponding to a first asset account (e.g., a computer storage management account, a transfer account, a memory allocation account, a print allocation account, a transportation system account, a payment account, or a store credit account) and a portion (e.g., all or less than all) of a second visual representation (e.g., 712b, 812b) different from the first visual representation corresponding to a second asset account different from the first asset account (e.g., a memory allocation account, a print allocation account, a transportation system account, a payment account, or a store credit account). In some embodiments, the portion of the first visual representation and the portion of the second visual representation are displayed as part of an electronic wallet application of the computer system. In some embodiments, the first asset account and the second asset account belong to a user of the computer system and / or are configured on the computer system. In some embodiments, one or more details of the asset account are stored in a secure element of the computer system. In some embodiments, a security element is a hardware component (e.g., a computer system) configured to securely store data or an algorithm so that the computer system cannot access securely stored data without the correct authentication information from the user of the computer system (e.g., a secure microcontroller chip). The securely stored data is kept in a security element separate from other storage devices on the computer system to prevent access to the securely stored data, even if other storage locations on the computer system are compromised (e.g., by malicious code or other attempts to compromise the information stored on the computer system). In some embodiments, the security element provides (or publishes) account information (e.g., account number and / or transaction-specific dynamic security code). In some examples, the security element provides (or publishes) account information in response to the computer system receiving authorization, such as user authentication (e.g., biometric authentication (e.g., fingerprint authentication; facial authentication; iris authentication; password authentication)).
[0275] While the portion of the first visual representation (e.g., 712a, 812a) and the portion of the second visual representation (e.g., 712b, 812b) are displayed simultaneously, the computer system receives (904) via the one or more input devices a selection of the first visual representation (e.g., 701a, 801a) corresponding to the first asset account (e.g., via a tap input on the option and / or via pressing and holding on the option).
[0276] In response to receiving a selection of a first visual representation corresponding to a first asset account, the computer system displays (906) via a display generation component (e.g., 702, 802) an option (e.g., 726, 826) for initiating a transfer request (e.g., a transfer request for an asset, such as a storage allocation, a print allocation, a traffic pass, and / or a fund transfer) using the first asset account (e.g., to begin the process of requesting a transfer).
[0277] When an option for initiating a transfer request using a first asset account is displayed, the computer system receives (908) a selection (728, 828) of the option for initiating a transfer request using a first asset account via the one or more input devices (e.g., via a tap input on the option and / or via a press and hold on the option).
[0278] In response to receiving a selection of an option for initiating a transfer request using the first asset account, the computer system displays (910) via a display generation component representations of one or more users (e.g., 732, 732b, 832, 832b) (e.g., a representation of one user other than the user of the computer system, representations of two users other than the user of the computer system, representations of 10 users other than the user of the computer system, a first representation of the first user and a second representation of the second user, multiple representations of multiple users). In some embodiments, the representations of the users are displayed as part of a user selection user interface (e.g., of an electronic wallet application of the computer system) for selecting a recipient of a request corresponding to the first asset account.
[0279] While displaying representations of the one or more users, the computer system receives (912) via the one or more input devices a selection (e.g., 734, 834) of a first representation (e.g., 732b, 832b) that corresponds to a first user among the one or more users who is a recipient of a transfer request using a first asset account (e.g., receiving / accepting a request for an asset from the first user or transferring an asset to the first user).
[0280] In some embodiments, in response to receiving a selection of an option for initiating a transfer request using a first asset account, a computer system displays (e.g., overlaid on an existing user interface (as a pop-up window) and / or without displaying representations of one or more users) multiple options for initiating a transfer. In some embodiments, the multiple options for initiating a transfer include a first option for transmitting an asset and a second option for requesting an asset. In some embodiments, the computer system detects a selection of the first option or the second option and, in response, displays representations of one or more users who may be selected as recipients of a transfer using the first asset account (e.g., to transmit if the first option is selected or to request if the second option is selected). Enabling a user to initiate a transfer request after selecting an asset account from a plurality of asset accounts reduces the number of inputs required to perform a transfer request operation.
[0281] In some embodiments, the computer system receives (e.g., instead of or after selecting a first representation corresponding to a first user) a search input (e.g., a text string and / or an audio input such as a name and / or a phone number). The computer system displays (e.g., in response to receiving the search input) one or more representations of one or more searched users based on the search input. The computer system receives a selection of a first representation of a first searched user of the one or more searched users via the one or more input devices, and uses the first searched user as a recipient of a transfer request using a first asset account.
[0282] In some embodiments, in response to receiving a selection of a first representation corresponding to a first user who is a recipient of a transfer request using a first asset account, the computer system displays, via a display generation component, a quantity user interface for selecting the quantity of assets to be transferred based on the transfer request (e.g., 740, 840). Displaying a user interface for selecting the quantity of assets to be transferred to a user enables the user to control the details of the transfer request, thereby improving the human-computer interface.
[0283] In some embodiments, the amount user interface includes the available balance of the first account (e.g., Fig. 7E 20MB as shown in Fig. 8E 00) (e.g., the total assets of the first account and / or the assets of the first account available for transfer). Displaying the available balance enables the user to select an amount of assets less than the available balance for transfer without requiring the user to provide additional input to find the available balance, thereby reducing the number of required inputs.
[0284] In some embodiments, the computer system receives (e.g., when displaying a quantity user interface) via the one or more input devices a user input selecting a quantity of assets to be transferred as part of a transfer request (e.g., a set of inputs including inputs 748a and 748b, a set of inputs including inputs 848a and 848b). In some embodiments, after receiving the user input selecting the quantity of assets, the computer system receives input via the one or more input devices (e.g., 750, 850, 878A) to perform a process for sending a request to transfer the quantity of assets (e.g., selection of a "request" button specifying that the transfer request is a request by the first user to transfer the quantity of assets to the first asset account, selection of a "transfer" button specifying that the transfer request is a request by the first user to accept the transfer of the quantity of assets from the first asset account, and / or selection of a button indicating that the quantity has been specified by the user). In some embodiments, in response to receiving the input to initiate a process for sending a request to transfer the quantity of assets, the computer system performs a process for sending a request to transfer the quantity of assets. Performing a process for sending a request based on the user input provides feedback to the user that the input was received and the process is ongoing, thereby providing improved feedback to the user.
[0285] In some embodiments, performing the process for sending the request to transfer the amount of assets includes displaying a draft message (762, 862, 852A and / or notes and information provided in a compose field of a messaging interface) for a conversation (e.g., a displayed conversation) between a user of the computer system and a first user (e.g., an instant message, a chat message). In some embodiments, performing the process for sending the request to transfer the amount of assets includes sending the request to the first user without displaying the draft message (e.g., in the background and / or without showing the sent message as part of the conversation between the user of the computer system and the first user). Displaying the draft message provides feedback to the user that the input is being received and the process is ongoing, thereby providing improved feedback to the user.
[0286] In some embodiments, after receiving a selection of the first user as a recipient of the transfer request (e.g., in response to or after receiving additional required intervention user input), the computer system sends a transfer request to the first user using the first asset account (e.g., a request to receive / accept assets from the first asset account or a request to transfer assets to the first asset account). In some embodiments, the transfer request is sent in response to receiving user input to transmit a draft message in a conversation. In some embodiments, the transfer request is sent in response to receiving input to initiate a process for sending a request to transfer the amount of assets.
[0287] In some embodiments, after transmitting the transfer request to the first user using the first asset account, the computer system receives an update on the status of the transfer request. In some embodiments, the computer system displays a transfer history (e.g., 722, 822) via a display generation component, the transfer history including a plurality of transfers (e.g., 722a-722c, 822a-822e) using the first account, including: based on determining that the update on the status of the transfer request indicates that the first user has rejected the transfer request, displaying an indication that the transfer request has been rejected (e.g., Figures 8AC to 8AD In some embodiments, based on determining that an update to the status of the transfer request indicates that the first user has accepted the transfer request, an indication that the transfer request has been accepted is displayed (e.g., as indicated in transfers 722c, 822c). In some embodiments, based on determining that an update to the status of the transfer request indicates that the transfer request has expired, an indication that the transfer request has expired is displayed (e.g., as indicated in transfers 722c, 822c). Figures 8AC to 8AD Displaying an indication that the transfer request has been denied provides visual feedback to the user regarding the status of the computer system, and in particular, regarding the status of the transfer request.
[0288] In some embodiments, when displaying an indication that the transfer request has been denied, the computer system detects, via the one or more input devices, one or more inputs (e.g., a tap on the indication that the transfer has been denied to display information about the transfer, and a subsequent tap on the transfer when the information about the transfer is displayed) including a selection of the indication that the transfer has been denied (e.g., 806B). In some embodiments, in response to receiving the one or more inputs including a selection of the indication that the transfer has been denied, the computer system displays an option (e.g., 814B) for re-requesting the transfer (e.g., using the same amount of assets, using the same first account to transfer to the same first user). In some embodiments, the computer system receives, via the one or more input devices, a selection of the option for re-requesting the transfer. In some embodiments, in response to receiving a selection of the option for re-requesting the transfer, the computer system initiates a process of sending a request to the first user to transfer the amount of assets using the first account. Providing the user with the option to re-request a transfer enables the user to quickly initiate another request (e.g., without having to re-enter the requested amount and / or recipient), thereby reducing the number of inputs required to perform an operation.
[0289] In some embodiments, after sending a transfer request using a first asset account to a first user, the computer system simultaneously displays via a display generation component: an indication that the transfer request is pending (e.g., before the first user has accepted / rejected the transfer request) (e.g., as indicated in transfer 722c or transfer 822c); and an option (e.g., 726, 826) for initiating a second transfer request different from the transfer request (e.g., a transfer request for an asset, such as a transfer request for memory allocation, print allocation, traffic access, and / or funds) using the first asset account (e.g., to be transmitted to the first user, the second user, and / or another user). In some embodiments, the computer system also optionally displays a first visual representation corresponding to the first asset account and / or one or more transfers performed using the first asset account (e.g., other requests to transmit / receive assets using the first asset account to, such as, the first user, the second user, and / or other users) simultaneously with the indication that the transfer request is pending and the option to initiate the second transfer request. In some embodiments, pending (e.g., not yet accepted, rejected, or expired) transfer requests are displayed above transactions that were completed after the transfer request was sent (e.g., in a list format) (e.g., transfer 722c is displayed above transfers 722a and 722b, and transfer 822c is displayed above transfers 822a and 822b). Displaying an indication that a transfer request is pending provides visual feedback to the user regarding the status of the transfer request, thereby providing improved visual feedback to the user.
[0290] In some embodiments, while displaying an indication that a transfer request is pending, the computer system receives, via the one or more user inputs, a selection of the indication that a transfer request is pending (e.g., 890A, 898A) (e.g., a tap input and / or a swipe gesture on the indication that a transfer request is pending). In some embodiments, in response to receiving a selection of the indication that a transfer request is pending, the computer system displays, via the display generation component, information about the first user (because the transfer request is being sent to the first user) (e.g., Figure 8Z894A), the information including: information about transfer requests; and information about multiple transfers (e.g., completed, accepted, rejected and / or expired) of assets with the first user (e.g., previous transfers (sent and / or received) using the first asset account and / or other asset accounts), wherein the information about the transfer requests is displayed above the information about multiple transfers of assets with the first user. In some embodiments, the details of the first user include a transaction history such as pending and completed transfers with the first user using the first asset account and / or other asset accounts, and including pending transfer requests. In some embodiments, information about the first user is displayed without displaying transaction information of the second user (or other users). The computer system displays multiple transfers of assets corresponding to the first user, so that a user of the computer system can quickly see the transfer history with the first user without scrolling through a list of transactions from multiple users, thereby providing the user with improved visual feedback (e.g., concise feedback) and reducing the amount of user input required to review the transfer history.
[0291] In some embodiments, the computer system receives a selection of information about the transfer request via the one or more input devices (e.g., 898A). In some embodiments, in response to receiving the selection of information about the transfer request, the computer system displays a transaction detail user interface for the transfer request (e.g., 800B) via the display generation component, the transaction detail user interface including: expiration information for the transfer request (e.g., number of days until expiration and / or expiration date); and a cancel option (e.g., 802B) that initiates the process of canceling the transfer request when activated (e.g., so that the first user can no longer accept / reject the transfer). In some embodiments, the computer system receives the selection of the cancel option and cancels the transfer request. In some embodiments, the computer system receives the selection of the cancel option and requires the user to confirm the selection before continuing to cancel the transfer request. In some embodiments, the transaction detail user interface also includes a display of the status of the transfer request (e.g., pending, rejected, accepted, expired), the name of the recipient (e.g., the name of the first user), the expiration information of the transfer request, the transfer amount of the transfer request, and / or an option to cancel the transfer request. Displaying the expiration information along with the cancel option enables the user to know how much time remains before the request expires and to cancel the transfer request if it is no longer needed, thereby reducing the amount of input required to perform the operation.
[0292] In some embodiments, the computer system displays (e.g., on a lock screen and / or as part of a user interface of an electronic wallet application) a notification (e.g., 814A, 820A) for a transfer request with expiration information (e.g., days until expiration and / or expiration date). In some embodiments, the notification indicates that the transfer request expires the next day. In some embodiments, the notification indicates that the transfer request expires the next week. In some embodiments, the computer system receives a selection (e.g., 816A, 822A) of the notification with expiration information via the one or more input devices (e.g., a tap input and / or a swipe input on the notification). In some embodiments, in response to receiving a selection of the notification, the computer system displays a transaction details user interface (e.g., 800B) for the transfer request via the display generation component. In some embodiments, the transaction details user interface for the transfer request includes: expiration information (e.g., days until expiration and / or expiration date) for the transfer request; and a cancel option (e.g., 802B) that initiates a process of canceling the transfer request when activated (e.g., so that the first user can no longer accept / reject the transfer). In some embodiments, the computer system receives a selection of the cancel option and cancels the transfer request. In some embodiments, the computer system receives a selection of the cancel option and requires the user to confirm the selection before continuing to cancel the transfer request. In some embodiments, the notification with expiration information is a notification (e.g., via a notification on the first user's computer system) that reminds the recipient (the first user) of the transfer request (and optionally when the transfer request expires). Providing the user with a notification with expiration information of the transfer request provides the user with feedback on the status of the transfer request (e.g., how much time is left before the request expires), thereby providing improved visual feedback.
[0293] In some embodiments, after the asset has been added to the first asset account (e.g., via a second transfer request from the first user and / or from the second user): the computer system displays (e.g., on a lock screen of the computer system) via a display generation component a first notification (e.g., 884) that the asset (and optionally the amount of the asset) has been added to the first asset account. Providing notification to the user that the asset has been added to the asset account provides visual feedback to the user regarding the status of the asset account and the computer system, thereby providing improved visual feedback.
[0294] In some embodiments, after the asset has been added to the first asset account (e.g., via a second transfer request from the first user and / or from the second user): the computer system displays (e.g., on the lock screen of the computer system, before or after displaying the first notification that the asset has been added to the first account) via the display generation component a second notification (e.g., 886) including an indication (e.g., a numerical value) of the amount of assets (e.g., balance, available asset amount) of the first asset account (e.g., simultaneously with the first notification). Providing notification of the balance of the asset account to the user provides visual feedback to the user about the status of the asset account and the computer system, thereby providing improved visual feedback.
[0295] In some embodiments, in response to receiving a selection of a first visual representation corresponding to a first asset account, the computer system displays the first visual representation (e.g., 712a, 812a) via a display generation component and simultaneously with an option for initiating a transfer request (e.g., a transfer request for an asset, such as a storage allocation, a print allocation, a transit pass, and / or a transfer request for funds) using the first asset account (e.g., a visual representation of a card for an account, such as a storage account, a bank account, and / or a cash account), and a transfer history (e.g., 722, 822) of one or more (e.g., one, two, 10, more) transfers (e.g., complete or incomplete) performed using the first asset account (e.g., without displaying the second visual representation and / or without displaying the transfer history of the second asset account). Displaying the first visual representation together with the transfer history of the first asset account provides the user with visual feedback about the account with which the user is interacting and the history of the account, thereby providing improved visual feedback to the user.
[0296] In some embodiments, in response to receiving a selection of a first visual representation corresponding to a first asset account, the computer system displays filter options (e.g., 724, 824) for filtering the transfer history of the first asset account via a display generation component and simultaneously with options for initiating a transfer request (e.g., a transfer request for an asset, such as a transfer request for a storage allocation, a print allocation, a traffic pass, and / or funds) using the first asset account and a transfer history of one or more (e.g., one, two, 10, more) transfers (e.g., complete or incomplete) performed using the first asset account.
[0297] In some embodiments, in response to receiving a selection of a filter option, the computer system displays one or more (e.g., some or all) of the following options (e.g., 890a-890f) for filters: all transfers, requested transfers, paid transfers, transfers to an account based on the amount paid (e.g., cash back), pending transfer requests, and purchases. Selection of an option for a filter causes the computer system to limit the transfer history to the selected transfer type.
[0298] In some embodiments, in response to receiving a selection of a first visual representation corresponding to a first asset account, the computer system displays a search option (e.g., 894) via a display generation component and simultaneously with an option for initiating a transfer request. In response to receiving a selection of the search option (e.g., 896), a search input box and one or more options (e.g., 802A, 804A, 806A) are simultaneously displayed for filtering (e.g., all transfers, requested transfers, paid transfers, transfers to an account based on an amount paid (e.g., cash back), pending transfer requests, and purchases); wherein selection of the option for filtering causes the computer system to limit the search results (and / or transfer history) to the selected transfer type.
[0299] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.
[0300] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.
[0301] As described above, one aspect of the present technology is to collect and use data available from various sources to improve transfer. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.
[0302] The present disclosure recognizes that the use of such personal information data in the present invention technology can be used to benefit users. For example, personal information data can be used to prevent assets from being accidentally transferred to unintended recipients. In addition, the present disclosure also anticipates other uses of personal information data that benefit users.
[0303] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.
[0304] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates hardware elements and / or software elements to prevent or block access to such personal information data. For example, with respect to transfer services, the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" to participate in the collection of personal information data at any time during or after registration for the service. In addition to providing "opt-in" and "opt-out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.
[0305] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and data deletion. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data between users), and / or other methods when appropriate.
[0306] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, a transfer may be performed using a minimal amount of personal information or publicly available information.
Claims
1. A method comprising: At a computer system in communication with a display generation component and one or more input devices: concurrently displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously; in response to receiving a selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; as well as In response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying representations of one or more users via the display generating component; and while displaying the representations of the one or more users, receiving a selection of a first representation via the one or more input devices, the first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
2. The method according to claim 1, further comprising: In response to receiving a selection of the first representation, a quantity user interface for selecting a quantity of assets to be transferred based on the transfer request is displayed via the display generation component, the first representation corresponding to the first user who is the recipient of the transfer request using the first asset account. The method of claim 2 , wherein the quantity user interface includes an available balance of the first asset account.
4. The method according to any one of claims 2 to 3, further comprising: receiving, via the one or more input devices, user input selecting an amount of the asset to be transferred as part of the transfer request; as well as receiving, after receiving user input selecting the amount of the asset, input via the one or more input devices to conduct a process for sending a request to transfer the amount of the asset; as well as In response to receiving the input initiating the process for sending the request to transfer the amount of the asset, the process for sending the request to transfer the amount of the asset is performed.
5. The method of claim 4, wherein performing the process for sending the request to transfer the amount of the asset includes displaying a draft message for a conversation between the user of the computer system and the first user.
6. The method according to any one of claims 1 to 5, further comprising: After receiving a selection of the first user as the recipient of the transfer request, the transfer request using the first asset account is sent to the first user.
7. The method according to claim 6, further comprising: After sending the transfer request to the first user using the first asset account, receiving an update on a status of the transfer request; as well as Displaying, via the display generation component, a transfer history including a plurality of transfers using the first asset account, comprises: Based on determining that the update to the status of the transfer request indicates that the first user has rejected the transfer request, displaying an indication that the transfer request has been rejected.
8. The method according to claim 7, further comprising: while displaying the indication that the transfer request has been denied, detecting, via the one or more input devices, one or more inputs including a selection of the indication that the transfer request has been denied; in response to receiving the one or more inputs including a selection of the indication that the transfer request has been denied, displaying an option for re-requesting the transfer; receiving, via the one or more input devices, a selection of the option for re-requesting the transfer; as well as In response to receiving a selection of the option to re-request the transfer, a process is initiated to send a request to the first user to transfer an amount of assets using the first asset account.
9. The method according to any one of claims 1 to 8, further comprising: After sending the transfer request to the first user using the first asset account, the display generation component simultaneously displays: an indication that the transfer request is pending; and An option to initiate a second transfer request different from the transfer request using the first asset account.
10. The method according to claim 9, further comprising: receiving, via the one or more input devices, a selection of the indication that the transfer request is pending while the indication that the transfer request is pending is displayed; as well as In response to receiving a selection of the indication that the transfer request is pending, displaying, via the display generation component, information about the first user, the information comprising: information regarding the transfer request; and Information regarding a plurality of asset transfers with the first user, wherein information regarding the transfer request is displayed above the information regarding the plurality of asset transfers with the first user.
11. The method according to claim 10, further comprising: receiving, via the one or more input devices, a selection of the information regarding the transfer request; as well as In response to receiving a selection of the information regarding the transfer request, displaying, via the display generation component, a transaction detail user interface for the transfer request, the transaction detail user interface comprising: expiration information of the transfer request; and A cancel option which when activated initiates the process of cancelling the transfer request.
12. The method according to any one of claims 1 to 11, further comprising: displaying, via the display generation component, a notification having expiration information of the transfer request; receiving, via the one or more input devices, a selection of the notification having expiration information; as well as In response to receiving a selection of the notification, a transaction detail user interface for the transfer request is displayed via the display generation component.
13. The method according to any one of claims 1 to 12, further comprising: After the assets have been added to the first asset account: A first notification is displayed, via the display generation component, that an asset has been added to the first asset account.
14. The method according to any one of claims 1 to 13, further comprising: After the assets have been added to the first asset account: A second notification including an indication of an asset amount of the first asset account is displayed via the display generation component.
15. The method according to any one of claims 1 to 14, further comprising: In response to receiving a selection of the first visual representation corresponding to the first asset account, the first visual representation and a transfer history of one or more transfers performed using the first asset account are displayed via the display generation component and simultaneously with the option for initiating a transfer request using the first asset account.
16. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 15.
17. A computer system configured to communicate with a display generation component and one or more input devices, the computer system 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 comprising instructions for executing the method according to any one of claims 1 to 15.
18. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for carrying out the method according to any one of claims 1 to 15.
19. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 15.
20. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: concurrently displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously; in response to receiving a selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; as well as In response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying representations of one or more users via the display generating component; and while displaying the representations of the one or more users, receiving a selection of a first representation via the one or more input devices, the first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
21. A computer system configured to communicate with a display generation component and one or more input devices, the computer system 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: concurrently displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously; in response to receiving a selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; as well as In response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying representations of one or more users via the display generating component; and while displaying the representations of the one or more users, receiving a selection of a first representation via the one or more input devices, the first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
22. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: means for simultaneously displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; means for receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously; means for displaying, via the display generation component, an option for initiating a transfer request using the first asset account in response to receiving a selection of the first visual representation corresponding to the first asset account; means for receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; and A component for performing the following operations: in response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying representations of one or more users via the display generating component; and while displaying the representations of the one or more users, receiving a selection of a first representation via the one or more input devices, the first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
23. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: concurrently displaying, via the display generation component, a portion of a first visual representation corresponding to a first asset account and a portion of a second visual representation different from the first visual representation corresponding to a second asset account different from the first asset account; receiving, via the one or more input devices, a selection of the first visual representation corresponding to the first asset account while the portion of the first visual representation and the portion of the second visual representation are displayed simultaneously; in response to receiving a selection of the first visual representation corresponding to the first asset account, displaying, via the display generation component, an option for initiating a transfer request using the first asset account; receiving, via the one or more input devices, a selection of the option for initiating a transfer request using the first asset account when the option for initiating a transfer request using the first asset account is displayed; as well as In response to receiving a selection of the option for initiating a transfer request using the first asset account, displaying representations of one or more users via the display generating component; and while displaying the representations of the one or more users, receiving a selection of a first representation via the one or more input devices, the first representation corresponding to a first user among the one or more users who is a recipient of the transfer request using the first asset account.
