WO2024196564A1

WO2024196564A1 - Contactless account information transfer user interface

Info

Publication number: WO2024196564A1
Application number: PCT/US2024/018035
Authority: WO
Inventors: Trevor W. Young; Noah J. HOROWITZ
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2023-03-20
Filing date: 2024-03-01
Publication date: 2024-09-26
Anticipated expiration: 2025-09-20
Also published as: EP4684343A1; CN120883234A

Abstract

Indications related to a contactless account information transfer are displayed in a user interface.

Description

CONTACTLESS ACCOUNT INFORMATION TRANSFER USER INTERFACE

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63/453,426, entitled “CONTACTLESS ACCOUNT INFORMATION TRANSFER USER INTERFACE,” filed March 20, 2023, and to U.S. Patent Application No. 18/407,943, entitled “CONTACTLESS ACCOUNT INFORMATION TRANSFER USER INTERFACE,” filed January 9, 2024. The contents of each of these applications are incorporated herein by reference in its entirety.

FIELD

[0002] The present disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying indications related to contactless account information transfers.

BACKGROUND

[0003] Computer systems use various techniques to transfer data from one device to another. Such techniques often require a user to provide various inputs to facilitate the transfer, without the computer system providing sufficient user feedback about the transfer.

BRIEF SUMMARY

[0004] Some techniques for providing feedback about contactless account information transfers using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

[0005] Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for providing feedback about contactless account information transfers. Such methods and interfaces optionally complement or replace other methods for providing feedback about contactless account information transfers. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and with one or more input devices is described. The method comprises: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximitybased error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

[0007] In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity-based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

[0008] In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity-based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

[0009] In accordance with some embodiments, a computer system that is configured to communicate with a display generation component and with one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximitybased error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

[0010] In accordance with some embodiments, a computer system that is configured to communicate with a display generation component and with one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: means, while displaying a user interface corresponding to a request for account information, for: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximitybased error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

[0011] In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity -based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

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

[0013] Thus, devices are provided with faster, more efficient methods and interfaces for contactless account information transfers, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for contactless account information transfers.

DESCRIPTION OF THE FIGURES

[0014] For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

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

[0016] FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

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

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

[0019] FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. [0020] FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

[0021] FIG. 5 A illustrates a personal electronic device in accordance with some embodiments.

[0022] FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0023] FIG. 5C illustrates exemplary devices connected via one or more communication channels, in accordance with some embodiments.

[0024] FIGS. 6A-6C illustrate exemplary user interfaces for displaying an indication related to completing a request for account information, in accordance with some embodiments.

[0025] FIGS. 7A-7I illustrate exemplary user interfaces for displaying an indication related to completing a request for account information, in accordance with some embodiments.

[0026] FIG. 8 is a flow diagram illustrating for displaying an indication related to completing a request for account information, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

[0027] The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

[0028] There is a need for electronic devices that provide efficient methods and interfaces for contactless account information transfers. For example, there is a need to provide efficient methods and interfaces for completing requests for account information. Such techniques can reduce the cognitive burden on a user who completes contactless account information transfers, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. [0029] Below, FIGS. 1 A-1B, 2, 3, 4A-4B, and 5A-5C provide a description of exemplary devices for performing the techniques for displaying indications related to completing a request for account information. FIGS. 6A-6C and FIGS. 7A-7I illustrate exemplary user interfaces for displaying indications related to completing a request for account information. FIG. 8 is a flow diagram illustrating methods of displaying indications related to completing a request for account information, in accordance with some embodiments. The user interfaces in FIGS. 6A-6C and 7A-7I are used to illustrate the processes described below, including the processes in FIG. 8.

[0030] The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.

[0031] In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.

[0032] Although the following description uses 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. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, the first touch and the second touch are both touches, but they are not the same touch.

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

[0034] The term “if’ is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

[0035] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch- sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.

[0036] In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

[0037] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

[0038] The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch- sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

[0039] Attention is now directed toward embodiments of portable devices with touch- sensitive displays. FIG. 1 A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch- sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (VO) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch- sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch- sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0040] As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure- sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch- sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch- sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch- sensitive surface, or a physical/mechanical control such as a knob or a button).

[0041] As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user’s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch- sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

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

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

[0044] Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.

[0045] RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.1 In, and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

[0047] I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and/or one or more depth camera sensors 175), such as for tracking a user’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 independently of an input element that is a part of the device) and is based on detected motion of a portion of the user’s body through the air including motion of the user’s body relative to an absolute reference (e.g., an angle of the user’s arm relative to the ground or a distance of the user’s hand relative to the ground), relative to another portion of the user’s body (e.g., movement of a hand of the user relative to a shoulder of the user, movement of one hand of the user relative to another hand of the user, and/or movement of a finger of the user relative to another finger or portion of a hand of the user), and/or absolute motion of a portion of the user’s body (e.g., a tap gesture that includes movement of a hand in a predetermined pose by a predetermined amount and/or speed, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user’s body).

[0048] A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. Patent Application 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed December 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0049] Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

[0050] Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

[0051] Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

[0052] A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

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

[0054] Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylusbased input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. [0055] In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0056] Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

[0057] Device 100 optionally also includes one or more optical sensors 164. FIG. 1 A shows an optical sensor coupled to optical sensor controller 158 in EO subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user’s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

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

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

[0060] Device 100 optionally also includes one or more proximity sensors 166. FIG. 1 A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is, optionally, coupled to input controller 160 in VO subsystem 106. Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity Detector In Handheld Device”; 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).

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

[0062] Device 100 optionally also includes one or more accelerometers 168. FIG. 1 A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in VO subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Accel eration -based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100. [0063] In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1 A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device’s various sensors and input control devices 116; and location information concerning the device’s location and/or attitude.

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

[0065] Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0066] Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface.

Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

[0067] In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

[0068] Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

[0069] Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.

[0070] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

[0071] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

[0072] Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts module 137, e-mail client module 140, IM module 141, browser module 147, and any other application that needs text input).

[0073] GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in locationbased dialing; to camera module 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

[0074] Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

• Contacts module 137 (sometimes called an address book or contact list);

• Telephone module 138;

• Video conference module 139;

E-mail client module 140; Instant messaging (IM) module 141;

• Workout support module 142;

• Camera module 143 for still and/or video images;

• Image management module 144;

• Video player module;

• Music player module;

• Browser module 147;

• Calendar module 148;

• Widget modules 149, which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;

• Widget creator module 150 for making user-created widgets 149-6;

• Search module 151;

• Video and music player module 152, which merges video player module and music player module;

• Notes module 153;

• Map module 154; and/or

• Online video module 155.

[0075] Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. [0076] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone module 138, video conference module 139, e-mail client module 140, or IM module 141; and so forth.

[0077] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.

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

[0079] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143. [0080] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony -based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both tel ephony -based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

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

[0082] In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

[0083] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. [0084] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0085] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

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

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

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

[0089] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0090] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

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

[0092] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed June 20, 2007, and U.S. Patent Application No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed December 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

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

[0094] In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.

[0095] The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

[0096] FIG. IB is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

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

[0098] In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

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

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

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

[0102] Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch- sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

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

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

[0105] Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

[0106] Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.

[0107] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130. [0108] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application’s user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater

176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater

177, and GUI updater 178 are included in a respective application view 191.

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

[0110] Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

[OHl] Event comparator 184 compares the event information to predefined event or subevent definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187- 2), and others. In some embodiments, sub-events in an event (e.g., 187-1 and/or 187-2) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0112] In some embodiments, event definitions 186 include a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

[0113] In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer’s event type.

[0114] When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

[0115] In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

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

[0117] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

[0118] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch- sensitive display. [0119] In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0120] It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

[0121] FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0122] Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112. [0123] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

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

[0125] Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The aboveidentified modules or computer programs (e.g., sets of instructions or including instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0126] Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.

[0127] FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

• Signal strength indicator(s) 402 for wireless communi cation(s), such as cellular and Wi-Fi signals;

• Time 404;

• Bluetooth indicator 405;

Battery status indicator 406; Tray 408 with icons for frequently used applications, such as: o Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages; o Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails; o Icon 420 for browser module 147, labeled “Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and

• Icons for other applications, such as: o Icon 424 for IM module 141, labeled “Messages;” o Icon 426 for calendar module 148, labeled “Calendar;” o Icon 428 for image management module 144, labeled “Photos;” o Icon 430 for camera module 143, labeled “Camera;” o Icon 432 for online video module 155, labeled “Online Video;” o Icon 434 for stocks widget 149-2, labeled “Stocks;” o Icon 436 for map module 154, labeled “Maps;” o Icon 438 for weather widget 149-1, labeled “Weather;” o Icon 440 for alarm clock widget 149-4, labeled “Clock;” o Icon 442 for workout support module 142, labeled “Workout Support;” o Icon 444 for notes module 153, labeled “Notes;” and o Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.

[0128] It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

[0129] FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

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

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

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

[0133] Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No.

PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.

[0134] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user. [0135] FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1 A, IB, and 3. Device 500 has bus 512 that operatively couples VO section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display screen 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 is, optionally, a button, in some examples.

[0136] Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

[0137] Memory 518 of personal electronic device 500 can include one or more non- transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including process 800 (FIG. 8). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non- transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu- ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

[0138] As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1 A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

[0139] As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1 A or touch screen 112 in FIG. 4 A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

[0140] As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.

[0141] FIG. 5C illustrates exemplary devices connected via one or more communication channels to participate in a transaction in accordance with some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., a particular user input, an 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 be NFC-enabled. [0142] The electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes, for example, one or more of a person’s or company’s name, a billing address, a login, 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, payment account information includes include an image, such as a picture of a payment card (e.g., taken by the device and/or received at the device). In some embodiments, the electronic devices receive user input including at least some payment account information (e.g., receiving user-entered credit, debit, account, or gift card number and expiration date). In some embodiments, the electronic devices detect 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 devices receive 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 for which an account for a user or user device previously made a purchase or identified payment account data (e.g., an app for renting or selling audio and/or video files).

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

[0144] In some embodiments, communication among electronic devices 100, 300, and 500 facilitates transactions (e.g., generally or specific transactions). For example, a first electronic device (e.g., 100) can serve as a provisioning or managing device, and can send notifications of new or updated payment account data (e.g., information for a new account, updated information for an existing account, and/or an alert pertaining to an existing account) to a second electronic device (e.g., 500). In another example, a first electronic device (e.g., 100) can send data to a second election device, wherein the data reflects information about payment transactions facilitated at the first electronic device. The information optionally includes one or more of: a payment amount, an account used, a time of purchase, and whether a default account was changed. The second device (e.g., 500) optionally uses such information to update a default payment account (e.g., based on a learning algorithm or explicit user input).

[0145] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 558 (e.g., which includes a traditional Bluetooth connection or a Bluetooth Low Energy connection) or using a WiFi network 556. Communications among user devices are, optionally, conditioned to reduce the possibility of inappropriately sharing information across devices. For example, communications relating to payment information requires that the communicating devices be paired (e.g., be associated with each other via an explicit user interaction) or be associated with a same user account.

[0146] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point-of-sale (POS) payment terminal 550, which is optionally NFC- enabled. The communication optionally occurs using a variety of communication channels and/or technologies. In some embodiments, electronic device (e.g., 100, 300, 500) communicates with payment terminal 550 using an NFC channel 560. In some embodiments, payment terminal 550 communicates with an electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. Electronic device (e.g., 100, 300, 500) is optionally configured transmit a signal to payment terminal 550 that includes payment information for a payment account (e.g., a default account or an account selected for the particular transaction).

[0147] In some embodiments, proceeding with a transaction includes transmitting a signal that includes payment information for an account, such as a payment account. In some embodiments, proceeding with the transaction includes reconfiguring the 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 credentials of the account via NFC, such as to payment terminal 550. In some embodiments, subsequent to transmitting credentials of the account via NFC, the electronic device reconfigures to not respond as a contactless payment card (e.g., requiring authorization before again reconfigured to respond as a contactless payment card via NFC). [0148] In some embodiments, generation of and/or transmission of the signal is controlled by a secure element in the electronic device (e.g., 100, 300, 500). The secure element optionally requires a particular user input prior to releasing payment information. For example, the secure element optionally requires detection that the electronic device is being worn, detection of a button press, detection of entry of a passcode, detection of a touch, detection of one or more option selections (e.g., received while interacting with an application), detection of a fingerprint signature, detection of a voice or voice command, and or detection of a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) with another device (e.g., payment terminal 550) is established within a defined time period from detection of the input, the secure element releases payment information to be transmitted to the other device (e.g., payment terminal 550). In some embodiments, the secure element is a hardware component that controls release of secure information. In some embodiments, the secure element is a software component that controls release of secure information.

[0149] In some embodiments, protocols related to transaction participation depend on, for example, device types. For example, a condition for generating and/or transmitting payment information can be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generation and/or transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after a security verification), while a corresponding condition for a phone does not require button-depression and instead requires detection of particular interaction with an application. In some embodiments, a condition for transmitting and/or releasing payment information includes receiving particular input on each of multiple devices. For example, release of payment information optionally requires detection of a fingerprint and/or passcode at the device (e.g., device 100) and detection of a mechanical input (e.g., button press) on another device (e.g., device 500).

[0150] Payment terminal 550 optionally uses the payment information to generate a signal to transmit to a 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 to determine whether a proposed purchase is authorized. In some embodiments, payment server 554 includes a server of an issuing bank. Payment terminal 550 communicates with payment server 554 directly or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and/or a server of a card network).

[0151] Payment server 554 optionally uses at least some of the payment information to identify a user account from among a database of user accounts (e.g., 552). For example, each user account includes payment information. An account is, optionally, located by locating an account with particular payment information matching that from the POS communication. In some embodiments, a payment is denied when provided payment information is not consistent (e.g., an expiration date does not correspond to a credit, debit or gift card number) or when no account includes payment information matching that from the POS communication.

[0152] In some embodiments, data for the user account further identifies one or more restrictions (e.g., credit limits); 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, a payment server denies a payment when a purchase amount added to a current balance would result in exceeding an account limit, when an account is frozen, when a previous transaction amount exceeds a threshold, or when a previous transaction count or frequency exceeds a threshold.

[0153] In some embodiments, payment server 554 responds to POS payment terminal 550 with an indication as to whether a proposed purchase is authorized or denied. In some embodiments, POS payment terminal 550 transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, POS payment terminal 550 sends a receipt to the electronic device (e.g., 100, 300, 500) when a purchase is authorized (e.g., via a transaction-coordination server that manages a transaction app on the user device). In some instances, POS payment terminal 550 presents an output (e.g., a visual or audio output) indicative of the result. Payment can be sent to a merchant as part of the authorization process or can be subsequently sent.

[0154] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involvement of POS payment terminal 550. For example, upon detecting that a mechanical input has been received, a secure element in the electronic device (e.g., 100, 300, 500) releases payment information to allow an application on the electronic device to access the information (e.g., and to transmit the information to a server associated with the application). In some embodiments, computer system 600 and computer system 700 optionally include some or all features of devices 100, 300, and/or 500.

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

[0156] FIGS. 6A-6C illustrate exemplary user interfaces for providing an indication related to completing a request for account information, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in FIG. 8.

[0157] At FIG. 6A computer system 600 displays, via display 602, user interface 604a for completing a request for personal information. User interface 604a includes request element 604b, area 604c, and instruction 606a. In some embodiments, request element 604b includes additional information about the request for personal information, such as a name of a form (e.g., a customs form). Instruction 606a is a default instruction indicating where a user should hold an identification card (e.g., passport, passport card, national identification card, and/or driver’s license) to complete the request for personal information shown in request element 604b. At FIG. 6B, a user attempts to complete the request for personal information by placing card 660 near computer system 600. Card 660 is placed near computer system 600 in a vertical (or other non-horizontal) orientation with respect to computer system 600. Computer system 600 detects that card 660 has been placed near computer system 600 (e.g., in a vertical orientation) and that personal information (e.g., from the card 660) has not been detected (e.g., received). In response to detecting that card 660 is near computer system 600 and that personal information has not been detected, computer system 600 ceases displaying instruction 606a and displays updated instruction 606b, as shown in FIG. 6B. Updated instruction 606b includes indications to hold card 660 in a horizontal orientation with respect to computer system 600. At FIG. 6C, the user places card 660 near computer system 600 in a horizontal orientation (e.g., based on updated instructions 606b). Computer system 600 detects card 660 is near computer system 600 (e.g., in a horizontal orientation) and that personal information has been detected (e.g., received). In response to detecting the personal information, the request for personal information is completed, and computer system 600 displays success indication 606c. In some embodiments, computer system 600 uses various sensors (e.g., proximity sensor 610, NFC reader/sensor, card reader, and/or camera sensor 608) to determine that although payment information has not been received, an attempt has been made to provide payment information using a payment method. In some embodiments, camera sensor 608 includes some or all features of optical sensors 164 and/or one or more depth camera sensors 175.

[0158] FIGS. 7A-7I illustrate exemplary user interfaces for providing an indication related to completing a request for account information, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in FIG. 8.

[0159] At FIG. 7A, computer system 700 displays, via display 702, user interface 704a for completing a request for payment. User interface 704a includes request element 704b, area 704c, and instruction 706a. In some embodiments, area 704c indicates where an NFC reader and/or other card reader (e.g., a short-range communication radio and/or a hardware radio antenna) is located in computer system 700. In some embodiments, area 704c forms the shape of (e.g., outline of) a rectangle to mimic the shape of a card (e.g., identification card, account card, and/or credit card) which is to be placed (e.g., tapped, brought close to) near the reader, indicated by user interface element 704c. Request element 704b indicates the amount that is being requested in the current payment transaction. In some embodiments, request element 704b includes additional transaction information, such as a merchant name and/or product name. For example, at FIG. 7A, the merchant “Coffee Co.” is requesting $24. Instruction 706a is a default instruction indicating where a buyer should hold a method of payment (e.g., account card, credit card, and/or electronic device (e.g., an NFC-enabled smart phone)) to complete the request for payment shown in request element 704b. In some embodiments, request element 704b and instruction 706a are displayed at a first location within user interface 704a that is a first distance from area 704c. Completing the request for payment optionally includes a method of payment (e.g., account card, credit card, and/or electronic device (e.g., an NFC-enabled smart phone)) to be placed near proximity sensor 710, NFC reader and/or other card reader so that account and/or payment information associated with the method of payment may be detected (e.g., received) by computer system 700. The successful detection and reception of account and/or payment information by computer system 700 requires a method of payment to be placed near computer system 700 at a predetermined orientation, for more than a predetermined duration, and/or within a predetermined distance of computer system 700.

[0160] In some embodiments, computer system 700 uses various sensors (e.g., proximity sensor 710, NFC reader/sensor, card reader, and/or camera sensor 708) to determine that although payment information has not been received, an attempt has been made to provide payment information using a payment method. For example, proximity sensor 710 detects an object within a proximity range, the short-range communication radio detects a payment chip nearby (e.g., via communication with the payment chip), camera sensor 708 detects a change (e.g., reduction) in amount of light (and/or visually detects a form of payment), and/or the NFC sensor detects an NFC card. In some embodiments, camera sensor 708 includes some or all features of optical sensors 164 and/or one or more depth camera sensors 175.

[0161] At FIG. 7B, a buyer attempts to complete the request for payment by placing account card 760 near (e.g., tapped and/or moved near) computer system 700. Account card 760 is held in a vertical orientation with respect to computer system 700 and placed near (e.g., tapped on or moved near) area 704c. Computer system 700 detects, via proximity sensor 710, a short-range communication radio, an NFC radio, and/or an NFC receiver, that account card 760 has been placed near computer system 700, and computer system 700 does not detect (e.g., receive) account and/or payment information from account card 760 (e.g., the request for payment has not been completed). In some embodiments, computer system 700 detects a payment card chip (e.g., a contactless payment chip) via an NFC radio and/or an NFC receiver, but computer system 700 does not detect (e.g., receive) account information associated with the payment card chip. In some embodiments, account card 760 is placed near computer system 700 in such a way that portions of area 704c, instruction 706a, and/or request element 704b are obscured from the view of the merchant and/or buyer by account card 760.

[0162] At FIG. 7C, in response to computer system 700 detecting account card 760 (e.g., in a vertical orientation) near computer system 700 without detecting (e.g., receiving) account and/or payment information from account card 760, computer system 700 ceases displaying instruction 706a and displays updated instruction 706b. Updated instruction 706b includes indications to hold account card 760 horizontally with respect to computer system 700 (as shown in FIG. 7C). In some embodiments, updated instruction 706b includes text, icons, animations, and/or video clips depicting how to hold (e.g., orientation of account card 760, distance of account card 760 from computer system 700, and/or duration that account card is placed near computer system 700) account card 760 to complete the request for payment. Further in response to computer system 700 detecting account card 760, computer system 700 displays updated instruction 706b and request element 704b at a second location (e.g., a second distance from area 704c that is larger than the first distance from area 704c) within user interface 704a, via display 702. Displaying updated instruction 706b and request element 704b at a second location decreases the amount that updated instruction 706b and request element 704b are obscured by account card 760 when account card 760 is placed near computer system 700. For example, in FIG. 7C, updated instruction 706b and request element 704b are shifted (e.g., moved and/or translated) down within user interface 704a (e.g., away from the location of proximity sensor 710), increasing the distance between area 704c, updated instruction 706b, and request element 704b to avoid or reduce account card 760 obscuring updated instruction 706b and request element 704b from view when account card 760 is placed near computer system 700. In some embodiments, computer system 700 ceases detecting account card 760 near computer system 700 and continues displaying request element 704b and updated instruction 706b at the second location. In some embodiments, computer system 700 ceases detecting account card 760 near computer system 700, and in response, computer system 700 displays request element 704b and updated instruction 706b at the first location.

[0163] At FIG. 7D, the buyer makes a second attempt to complete the request for payment. The buyer holds account card 760 horizontally with respect to computer system 700 while moving account card 760 in and out (e.g., once or multiple times) of range of proximity sensor 710, NFC radio, and/or NFC receiver (e.g., the buyer rapidly taps account card 760 near computer system 700). Computer system 700 detects account card 760 moving in and out of proximity via proximity sensor 710, NFC radio, and/or NFC receiver without detecting (e.g., receiving) account and/or payment information from account card 760 (e.g., the request for payment is not completed). At FIG. 7E, in response to computer system 700 detecting account card 760 moving in and out of proximity (e.g., detecting an account card moving into and out of proximity a threshold number of times within a threshold duration of time), computer system 700 displays updated instruction 706b with indications to hold account card 760 horizontally for a longer duration. [0164] At FIG. 7F, the buyer makes a third attempt to complete the request for payment. The buyer follows the instructions indicated by updated instruction 706b (e.g., holding account card 760 horizontally for a longer duration) while placing account card 760 more than a predetermined distance from computer 700. Computer system 700 detects (e.g., using proximity sensor 710 and/or camera sensor 708, but not using the short-range communication radio and/or NFC radio) account card 760 but does not detect (e.g., receive) account and/or payment information from account card 760 because account card 760 is more than a predetermined distance (e.g., outside the range of detection of the NFC radio, NFC receiver, and/or other card reader) from computer system 700.

[0165] At FIG. 7G, in response to computer system 700 detecting that account card 760 is more than a predetermined distance from computer system 700, computer system 700 displays updated instruction 706b with indications to hold account card 760 closer to computer system 700. In some embodiments, in response to computer system 700 detecting that account card 760 is more than a predetermined distance from computer system 700, computer system 700 displays updated instruction 706b with indications to hold account card 760 against computer system 700 (e.g., against display 702 and/or substantially in the same plane as computer system 700), as shown at FIG. 7H. In some embodiments, updated instruction 706b indicating to hold account card 760 against computer system 700 (as described with respect to FIG. 7H) is displayed after computer system 700 displays updated instruction 706b indicating to hold account card 760 closer to computer system 700 (as described with respect to FIG. 7G). For example, after computer system 700 detects a first attempt to complete the request for payment in which account card 760 is too far from computer system 700 for computer system 700 to receive account and/or payment information, computer system 700 displays updated instruction 706b (as in FIG. 7G), indicating to the buyer to hold account card 760 closer to computer system 700, and after a second attempt to complete the request for payment in which account card 760 is too far from computer system 700, computer system 700 displays updated indication 706b with an indication to hold account card 760 against the device (as in FIG. 7H).

[0166] At FIG. 71, computer system 700 detects the account and/or payment information of account card 760 (e.g., based on account card 760 being held horizontally within a predetermined distance from computer system 700 for more than the predetermined duration), and the request for payment is completed. At FIG. 71, in response to receiving the account/payment information and/or completing the request for payment, computer system 700 displays success message 706c, indicating that the request for payment has been completed.

[0167] FIG. 8 is a flow diagram illustrating a method for completing a request for account information using a computer system (e.g., a smartphone, a smartwatch, a wearable electronic device, a desktop computer, a laptop, and/or a tablet) that is in communication with a display generation component (e.g., a display controller and/or a touch-sensitive display system) and with one or more input devices, (e.g., a button, a rotatable input mechanism, a speaker, a camera sensor (e.g., 608 and/or 708), a motion detector (e.g., an accelerometer and/or gyroscope), a proximity sensor (e.g., 610 and/or 710), an NFC radio and/or receiver, and/or a touch-sensitive surface) in accordance with some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600 and/or 700) that is in communication with a display generation component (e.g., 602 and/or 702) and with one or more input devices. Some operations in method 800 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

[0168] As described below, method 800 provides an intuitive way for completing a request for account information. The method reduces the cognitive burden on a user for completing a request for account information, thereby creating a more efficient humanmachine interface. For battery-operated computing devices, enabling a user to complete a request for account information faster and more efficiently conserves power and increases the time between battery charges.

[0169] In method 800, while displaying (802) a user interface (e.g., 604a and/or 704a) corresponding to a request for account (e.g., transaction) information (e.g., a request for payment, a transaction user interface, and/or a verification user interface), the computer system (e.g., 600 and/or 700) detects (804), via the one or more input devices, an input corresponding to an attempt to complete the request for account information (e.g., a card payment and/or an NFC payment). In response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity-based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) have been met, the computer system displays (806), via the display generation component (e.g., 602 and/or 702), one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close to the device accepting payment). In some embodiments, the set of one or more proximity-based error conditions includes a condition that is met when the computer system does not receive the account information. Displaying one or more indications indicating how to complete the request for account information in accordance with a determination that a set of one or more proximity -based error conditions have been met allows the user to quickly recognize that the attempt to complete the request for account information was unsuccessful (e.g., that one or more errors have occurred) and enables the user to view instructions to complete the request for account information without requiring the user to provide additional input, thereby improving visual feedback and performing a step automatically.

[0170] In some embodiments, the account information (e.g., the account information corresponding to the request for account information) includes (e.g., is) identification information (e.g., name, birthdate, address, eye color, and/or hair color), and detecting the input corresponding to the attempt to complete the request for account information includes detecting (e.g., via proximity sensor 610, proximity sensor 710 and/or an NFC radio) an identification card (e.g., 660) (e.g., government-issued identification).

[0171] In some embodiments, the account information (e.g., the account information corresponding to the request for account information) includes (e.g., is) payment information (e.g., an account number, an expiration date of a payment card, and/or security information of a payment card), and detecting the input corresponding to the attempt to complete the request for account information includes detecting (e.g., via proximity sensor 610, proximity sensor 710 and/or an NFC radio) a payment card (e.g., 760) (e.g., a debit card, a credit card, an ATM card, and/or a gift card).

[0172] In some embodiments, in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that the set of one or more proximity -based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) have not been met (e.g., proximity based errors occurred, the transaction was successful, and/or nothing was detected via proximity sensor 610 and/or proximity sensor 710), the computer system (e.g., 600 and/or 700) forgoes displaying, via the display generation component (e.g., 602 and/or 702), the one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close the device accepting payment). Forgoing displaying the one or more indications indicating how to complete the request for account information in accordance with a determination that the set of one or more proximity -based error conditions have not been met allows the user to quickly recognize that no proximity -based errors occurred while attempting to complete the transaction, thereby providing improved visual feedback.

[0173] In some embodiments, the one or more input devices include a proximity sensor (e.g., 610 and/or 710), wherein the set of one or more proximity-based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) include a condition that is met when the proximity sensor detects an object (e.g., a payment card and/or an identification card). Displaying one or more indications indicating how to complete the request for account information in accordance with a determination that a set of one or more proximity-based error conditions have been met, including a condition that is met when the proximity sensor detects an object, allows the user to quickly recognize that the attempt to complete the request for account information was unsuccessful and enables the user to view instructions related to the detected object to complete the request for account information without requiring the user to provide additional input, thereby improving visual feedback and performing a step automatically.

[0174] In some embodiments, the one or more input devices include a proximity sensor (e.g., 610 and/or 710), wherein the set of one or more proximity-based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) include a condition that is met when the proximity sensor detects multiple instances (e.g., 2, 3, 4, or more) of an object (e.g., proximity sensor 610 and/or proximity sensor 710 is covered and/or detects an object within a predetermined range) coming into and out of proximity (e.g., proximity sensor 710 detecting the object and subsequently proximity sensor 710 ceases detecting the object (e.g., proximity sensor 710 is uncovered and/or does not detect an object within a predetermined range) one or more times) within a predetermined time period (e.g., 0.1, 0.5, 1, 2, 3, 4, 5, 10, and/or 30 seconds) (e.g., as illustrated by the moving hand in FIG. 7D). Displaying one or more indications indicating how to complete the request for account information in accordance with a determination that a set of one or more proximity -based error conditions have been met, including a condition that is met when the proximity sensor detects multiple instances of an object coming into and out of proximity within a predetermined time period, allows the user to quickly recognize that the attempt to complete the request for account information was unsuccessful and enables the user to view instructions relating to the object coming into and out of proximity to complete the request for account information without requiring the user to provide additional input, thereby improving visual feedback and performing a step automatically.

[0175] In some embodiments, the one or more input devices include a proximity sensor (e.g., 610 and/or 710), wherein the set of one or more proximity-based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) include a condition that is met when the proximity sensor detects an object for (e.g., less than) a predetermined time period. In some embodiments, the proximity sensor (e.g., 610 and/or 710) detects that an object is within proximity of the computer system (e.g., 600 and/or 700) for at least a predetermined amount of time (1 second, 2 seconds, or 3 seconds) (while the computer system does not receive the account information). In some embodiments, the proximity sensor (e.g., 610 and/or 710) detects that an object is within proximity of the computer system for less than a predetermined time (e.g., 1 second, 2 seconds, or 3 seconds) (e.g., while the computer system does not receive the account information). Displaying one or more indications indicating how to complete the request for account information in accordance with a determination that a set of one or more proximitybased error conditions have been met, including a condition that is met when the proximity sensor detects an object for a predetermined time period, allows the user to quickly recognize that the attempt to complete the request for account information was unsuccessful and enables the user to view instructions to complete the request for account information related to detecting the object for the predetermined time period without requiring the user to provide additional input, thereby improving visual feedback and performing a step automatically.

[0176] In some embodiments, the set of one or more proximity-based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) include a condition that is met when the computer system (e.g., 600 and/or 700) detects (e.g., one or more input devices and/or via an NFC radio) (e.g., the presence of) a payment card chip without receiving account information. In some embodiments, the computer system detects that a payment card chip is within communication range but does not receive account information from the payment card chip for a threshold amount of time. Displaying one or more indications indicating how to complete the request for account information in accordance with a determination that a set of one or more proximity -based error conditions have been met, including a condition that is met when the computer system detects a payment card chip without receiving account information, allows the user to quickly recognize that the attempt to complete the request for account information was unsuccessful and enables the user to view instructions to complete the request for account information without requiring the user to provide additional input, thereby improving visual feedback and performing a step automatically.

[0177] In some embodiments, the user interface (e.g., 604a and/or 704a) corresponding to the request for account information includes a user interface object (e.g., 604b and/or 704b) (e.g., corresponding to the request for account information, wherein the user interface object is displayed at a first location on the display generation component). In response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with the determination that the set of one or more proximity -based error conditions (e.g., proximity conditions and/or transaction conditions (e.g., the transaction was unsuccessful)) have been met, the computer system (e.g., 600 and/or 700) shifts (e.g., moving or translating) a display location (e.g., displaying the user interface object at a second location) of the user interface object (e.g., corresponding to the request for account information) on the display generation component (e.g., 602 and/or 702), within the user interface corresponding to the request for account information (e.g., displaying the request for account information at a second location, wherein the second location does not overlap with the location of the proximity sensor (e.g., 610 and/or 710) within the computer system so that the request for account information is not obscured by a payment and/or identification card). Shifting a display location of the user interface object in accordance with a determination that the set of one or more proximity -based error conditions have been met allows the user to view the displayed indication indicating how to complete the request for account information while an account card is held up to the computer system without requiring input from the user to move the user interface object or remove the account card, thereby performing a step automatically. [0178] In some embodiments, in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that the attempt to complete the request for account (e.g., transaction) information (e.g., a request for payment, a transaction user interface, and/or a verification user interface) has been successful (e.g., as illustrated in FIGS. 6C and 71) (e.g., the account information has been received and/or the transaction has been completed), the computer system (e.g., 600 and/or 700) forgoes displaying, via the display generation component (e.g., 602 and/or 702), the one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close the device accepting payment). Forgoing displaying the one or more indications indicating how to complete the request for account information in accordance with a determination that the set of one or more proximity -based error conditions have not been met allows the user to quickly recognize that the attempt to complete the request for account information has been successful without further input from the user, thereby performing a step automatically and providing improved visual feedback.

[0179] In some embodiments, the one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close the device accepting payment) include an indication of where to place (e.g., an indication of the optimal location of the account card with respect to the computer system, and/or how the account card should be held with respect to the computer system) an account card (e.g., an identification card, a payment card, a debit card, a credit card, an ATM card, and/or a gift card) to complete the request for account information. Indicating where to place an account card to complete the request for account information allows the user to quickly recognize how to complete the request for account information without requiring the user to find the correct placement location via trial and error, thereby reducing the number of inputs needed to perform an operation.

[0180] In some embodiments, the indication of where to place the account card (e.g., an identification card, a payment card, a debit card, a credit card, an ATM card, and/or a gift card) (e.g., an indication of the optimal location of the account card with respect to the computer system and/or how the account card should be held with respect to the computer system) to complete the request for account information includes an indication of an orientation of the account card (e.g., a horizontal orientation with respect to the display generation component and/or computer system, a vertical orientation with respect to the display generation component and/or computer system, and/or a flat orientation) (e.g., as illustrated in FIGS. 6B and 7C). Indicating where to place an account card to complete the request for account information, including an indication of orientation of the account card, allows the user to quickly recognize how to complete the request for account information without requiring the user to find the correct placement orientation via trial and error, thereby reducing the number of inputs need to perform an operation.

[0181] In some embodiments, the one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close the device accepting payment) include an indication to hold an account card (e.g., an identification card, a payment card, a debit card, a credit card, an ATM card, and/or a gift card) within a predetermined distance of the computer system (e.g., 600 and/or 700) for a predetermined duration (e.g., a duration longer than a previously detected duration) (e.g., as illustrated in FIGS. 7E-7F). Indicating where to place an account card to complete the request for account information, including an indication to hold the account card within a predetermined distance of the computer system for a predetermined duration, allows the user to quickly recognize what steps to take to complete the request for account information without requiring the user to find the correct placement location via trial and error, thereby reducing the number of inputs need to perform an operation.

[0182] In some embodiments, the one or more indications (e.g., 606b and/or 706b) (e.g., text instructions, icons, thumbnails, and/or video clips) indicating how to complete the request for account information (e.g., using a payment card, how to hold the payment card, and/or duration of holding the payment card close to the device accepting payment) include an indication to hold an account card within a predetermined distance (e.g., as illustrated in FIGS. 7F-7G) of the computer system (e.g., 600 and/or 700). Indicating where to place an account card to complete the request for account information, including an indication to hold the account card within a predetermined distance of the computer system, allows the user to quickly recognize how to complete the request for account information without requiring the user to find the correct placement location and distance from the computer system via trial and error, thereby reducing the number of inputs needed to perform an operation.

[0183] In some embodiments, the indication to hold the account card within a predetermined distance of the computer system includes an indication (e.g., as illustrated in FIG. 7G) to hold the account card against (e.g., touching) (e.g., the account card is lying flat on the computer system in an approximately parallel plane with the computer system) the computer system (e.g., 600 and/or 700). Indicating where to place an account card to complete the request for account information, including an indication to hold the account card against the computer system, allows the user to quickly recognize how to complete the request for account information without requiring the user to find the correct placement location and distance from the computer system via trial and error, thereby reducing the number of inputs needed to perform an operation.

[0184] The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

[0185] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

[0186] As described above, one aspect of the present technology is the gathering and use of data available from various sources to complete a transaction. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, social network IDs, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0187] The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to complete a transaction. Accordingly, use of such personal information data enables users to have calculated control of transaction information. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.

[0188] The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

[0189] Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

[0190] Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user’s privacy. Deidentification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

[0191] Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.

Claims

CLAIMS What is claimed is:

1. A method, comprising: at a computer system that is communication with a display generation component and with one or more input devices: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity-based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

2. The method of claim 1, wherein the account information includes identification information; and wherein detecting the input corresponding to the attempt to complete the request for account information includes detecting an identification card.

3. The method of any one of claims 1-2, wherein the account information includes payment information; and wherein detecting the input corresponding to the attempt to complete the request for account information includes detecting a payment card.

4. The method of any one of claims 1-3, the method further comprising: in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that the set of one or more proximity -based error conditions have not been met, forgo displaying, via the display generation component, the one or more indications indicating how to complete the request for account information.

5. The method of any one of claims 1-4, wherein the one or more input devices include a proximity sensor, and wherein the set of one or more proximity -based error conditions include a condition that is met when the proximity sensor detects an object.

6. The method of any one of claims 1-5, wherein the one or more input devices include a proximity sensor, and wherein the set of one or more proximity -based error conditions include a condition that is met when the proximity sensor detects multiple instances of an object coming into and out of proximity within a predetermined time period.

7. The method of any one of claims 1-6, wherein the one or more input devices include a proximity sensor, and wherein the set of one or more proximity -based error conditions include a condition that is met when the proximity sensor detects an object for a predetermined time period.

8. The method of any one of claims 1-7, wherein the set of one or more proximity -based error conditions include a condition that is met when the computer system detects a payment card chip without receiving account information.

9. The method of any one of claims 1-8, wherein the user interface corresponding to the request for account information includes a user interface object, the method further comprising: in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with the determination that the set of one or more proximity -based error conditions have been met, shifting a display location of the user interface object on the display generation component, within the user interface corresponding to the request for account information.

10. The method of any one of claims 1-9, the method further comprising: in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that the attempt to complete the request for account information has been successful, forgo displaying, via the display generation component, the one or more indications indicating how to complete the request for account information.

11. The method of any one of claims 1-10, wherein the one or more indications indicating how to complete the request for account information include an indication of where to place an account card to complete the request for account information.

12. The method of claim 11, wherein the indication of where to place the account card to complete the request for account information includes an indication of an orientation of the account card.

13. The method of any one of claims 1-12, wherein the one or more indications indicating how to complete the request for account information include an indication to hold an account card within a predetermined distance of the computer system for a predetermined duration.

14. The method of any one of claims 1-13, wherein the one or more indications indicating how to complete the request for account information include an indication to hold an account card within a predetermined distance of the computer system.

15. The method of claim 14, wherein the indication to hold the account card within a predetermined distance of the computer system includes an indication to hold the account card against the computer system.

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 is configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for performing the method of any one of claims 1-15.

17. A computer system that is configured to communicate with a display generation component and with one or more input devices, the computer system comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 1-15.

18. A computer system that is configured to communicate with a display generation component and with one or more input devices, the computer system comprising: means for performing the method of any one of claims 1-15.

19. A computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for performing the method of any one of claims 1-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 that is configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity -based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

21. A computer system that is configured to communicate with a display generation component and with one or more input devices, the computer system comprising: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity-based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

22. A computer system that is configured to communicate with a display generation component and with one or more input devices, the computer system comprising: means, while displaying a user interface corresponding to a request for account information, for: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity -based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.

23. A computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is configured to communicate with a display generation component and with one or more input devices, the one or more programs including instructions for: while displaying a user interface corresponding to a request for account information: detecting, via the one or more input devices, input corresponding to an attempt to complete the request for account information; and in response to detecting the input corresponding to the attempt to complete the request for account information, and in accordance with a determination that a set of one or more proximity -based error conditions have been met, displaying, via the display generation component, one or more indications indicating how to complete the request for account information.