Displaying representation of card with layered structure

Abstract

To provide displaying representation of a card with a layered structure.SOLUTION: In a computer system that displays a user interface which includes representation of a card 606, the representation of the card includes a plurality of layers 608a to 608e that are concurrently displayed. The plurality of layers include a first layer 608a with a first visual asset, and a second layer 608b with a second visual asset. A first set of visual effects is applied to the first visual asset without applying the first set of visual effects to the second visual asset. A second set of visual effects, different from the first set of visual effects, is applied to the second visual asset.SELECTED DRAWING: Figure 6A

Description

[Technical Field]

[0001] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for displaying representations of cards using layered structures in computer user interfaces. [Background technology]

[0002] The computer system can be used to access information related to the card, pass, or account. The information can then be used to provide goods or services to the user, for example, to gain entry to a venue or to complete a transaction. Typically, the information related to the card, pass, or account is associated with the user of the computer system. Summary of the Invention

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

[0004] The present techniques thus provide computer systems with faster, more efficient methods and interfaces for using cards, passes, or accounts, along with representations of the cards, passes, or accounts. Such methods and interfaces optionally complement or replace other methods for using cards, passes, or accounts. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0005] An exemplary method is disclosed herein in a computer system in communication with a display generation component, the exemplary method including: displaying, via the display generation component, a user interface including a representation of a card, the representation of the card including multiple simultaneously displayed layers including a first layer having a first visual asset and a second layer having a second visual asset; applying a first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset; and applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects.

[0006] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs including instructions for displaying, via the display generation component, a user interface including a representation of a card, the representation of the card including multiple layers displayed simultaneously, the multiple layers including a first layer having a first visual asset and a second layer having a second visual asset, applying a first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset, and applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects.

[0007] An exemplary non-transitory computer-readable storage medium is described herein. The exemplary non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs including instructions for displaying, via the display generation component, a user interface including a representation of a card, the representation of the card including multiple layers displayed simultaneously, the multiple layers including a first layer having a first visual asset and a second layer having a second visual asset, applying a first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset, and applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects.

[0008] An exemplary computer system is described herein. The exemplary computer system includes a display generation component, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to: display, via the display generation component, a user interface including a representation of a card, the representation of the card including multiple layers displayed simultaneously, the multiple layers including a first layer having a first visual asset and a second layer having a second visual asset; apply a first set of visual effects to the first visual assets without applying the first set of visual effects to the second visual assets; and apply a second set of visual effects to the second visual assets, the second set of visual effects being different from the first set of visual effects.

[0009] An exemplary computer system includes a display generation component; means for displaying, via the display generation component, a user interface including a representation of a card, the representation of the card including multiple layers displayed simultaneously, the multiple layers including a first layer having a first visual asset and a second layer having a second visual asset; means for applying a first set of visual effects to a first visual asset without applying the first set of visual effects to the second visual asset; and means for applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects.

[0010] Executable instructions to perform these functions are optionally included on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally included on a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0011] Thus, computer systems are provided with faster, more efficient methods and interfaces for using cards, passes, or accounts, along with representations of the cards, passes, or accounts, thereby improving the effectiveness, efficiency, and user satisfaction of such computer systems. Such methods and interfaces can complement or replace other methods for using cards, passes, or accounts. [Brief explanation of the drawings]

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

[0013] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments. [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments. [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments. [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments. [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface that is separate from the display in accordance with some embodiments. [Figure 5A] 1 illustrates a personal electronic device according to some embodiments. [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device according to some embodiments. [Figure 6A] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6B] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6C] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6D] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6E] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6F] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6G] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6H] 1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 6I]1 illustrates an example of a representation of a card using a layered structure, according to some embodiments. [Figure 7] FIG. 1 is a flow diagram illustrating a method for displaying representations of cards using a computer system, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] A need exists for an electronic device that provides an efficient method and interface for sharing and using a card, pass, or account. For example, a representation of a card is displayed by the electronic device when completing a transaction using card information associated with the electronic device. A need exists for a user to easily and efficiently recognize that the representation of the card corresponds to the card selected for use in the transaction and to be able to verify that the representation of the card is authentic. Such techniques can reduce the cognitive burden on users who use cards, passes, or accounts for transactions, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0016] 1A-1B, 2, 3, 4A-4B, and 5A-5B below provide a description of an example device for performing techniques for managing event notifications. FIGS. 6A-6I illustrate an example technique and user interface for displaying representations of cards. FIG. 7 is a flow diagram illustrating a method for displaying representations of cards, according to some embodiments. The user interfaces of FIGS. 6A-6I are used to illustrate processes described below, including the process of FIG. 7.

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

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

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

[0020] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system in communication (e.g., via wired communication, via wireless communication) with a display generation component. The display generation component is configured to provide a 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 displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) over a wired or wireless connection to an integrated or external display generation component to visually generate the content.

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

[0022] The device typically supports a variety of applications, such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training 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.

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

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

[0025] As used in this specification and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or a surrogate (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 (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimate of the contact force. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is stated in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible by the user on reduced-size devices with limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0026] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user will feel a tactile sensation such as a “downclick” or “upclick” 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 movement. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

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

[0028] 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.

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

[0030] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to and from electromagnetic signals and communicates with communication networks and other communication devices via 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, etc. RF circuitry 108 optionally communicates via wireless communication with networks and other devices, such as the Internet, also called the World Wide Web (WWW), intranets, and / or cellular telephone networks, wireless networks such as wireless local area networks (LANs), and / or metropolitan area networks (MANs). RF circuitry 108 optionally includes known circuitry for detecting a near field Communication (NFC) field, such as by a short-range radio. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LTE), and other standards.evolution (LTE), near field communications (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

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

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

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

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

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

[0036] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption of that contact, 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 touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

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

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

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

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

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

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

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

[0044] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, 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 surrogate for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is located on or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display 112 located on the front of device 100.

[0045] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 within I / O subsystem 106. Proximity sensor 166 optionally functions as described in U.S. patent application Ser. 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 incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

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

[0047] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 optionally functions as described in U.S. Patent Publication No. 20050190059, "Acceleration-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 entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape orientation based on an analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information about the location and orientation (e.g., portrait or landscape) of device 100.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] Videoconferencing module 139 includes executable instructions to cooperate with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138 to initiate, conduct, and end a videoconference between a user and one or more other participants according to the user's instructions.

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

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

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

[0067] Camera module 143 includes executable instructions to cooperate with touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144 to capture and store still images or video (including video streams) in memory 102, modify characteristics of the still images or video, or delete the still images or video from memory 102.

[0068] Image management module 144 includes executable instructions to cooperate with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143 to arrange, modify (e.g., edit) or otherwise manipulate, label, delete, present (e.g., in a digital slideshow or album), and store still images and / or videos.

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

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

[0071] Widget module 149, in conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, optionally provides mini-applications (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) downloaded and used by a user, or mini-applications created by a 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).

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

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

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

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

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

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

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

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

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

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

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

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

[0084] Event monitor 171 receives event information from peripherals interface 118. The 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 I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0085] In some embodiments, event monitor 171 sends requests to 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).

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

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

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

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

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

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

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

[0093] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple 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, each 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 invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 includes one or more corresponding event handlers 190. In some embodiments, one or more of a data updater 176, an object updater 177, and a GUI updater 178 are also included in the corresponding application view 191.

[0094] Each 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 (optionally including sub-event delivery instructions).

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

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

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

[0098] In some embodiments, the definition of each event 187 also includes a delay action that delays transmission of the event information until it is determined whether the sequence of sub-events corresponds or does not correspond to the event type of the event recognizer.

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

[0100] In some embodiments, each 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 participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are allowed to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to various levels in the view or programmatic hierarchy.

[0101] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag captures the flag and performs a predetermined action.

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

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

[0104] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

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

[0106] FIG. 2 illustrates portable multifunction device 100 having touchscreen 112, according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of the graphics by performing a gesture on the graphic, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics 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 (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

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

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

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

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

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

[0113] 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "music" or "music player," although other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

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

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

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

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

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

[0119] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, may 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, may allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

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

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

[0122] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media that store computer-executable instructions that, when executed by one or more computer processors 516, can cause the computer processors to perform techniques described below, including process 700 (FIG. 7), for example. A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions used by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, 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 and may include other or additional components in multiple configurations.

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

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

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

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

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

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

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

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

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

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

[0133] 6A-6I show examples of card representations using layered structures, according to some embodiments. These figures are used to illustrate the processes described below, including the process of FIG.

[0134] FIG. 6A shows a layered structure for a representation of a card 606. In some embodiments, the representation of the card 606 includes five layers 608a-608e. The first layer 608a is a background layer that is displayed behind the other layers of the representation of the card 606. In some embodiments, the first layer 608a is a single (e.g., uniform) color. In some embodiments, the first layer 608a includes a color gradient. In some embodiments, the first layer 608a includes an image. In some embodiments, the first layer 608a is a static layer that does not include visual effects (e.g., movement, motion, animation).

[0135] The second layer 608b is displayed above the first layer 608a. As shown in FIG. 6A, the second layer 608b is assigned assets 610b (e.g., images of stars). In some embodiments, the assets 610b assigned to the second layer 608b have visual effects applied to them (e.g., the stars appear to twinkle). In some embodiments, the visual effects applied to the assets 610b are different from the visual effects applied to the assets assigned to the other layers.

[0136] The third layer 608c is displayed above the first layer 608a and the second layer 608b. As shown in FIG. 6A , the third layer 608c is assigned an asset 610c (e.g., an image of a ship). By assigning different assets to each layer, the assets assigned to each layer can be displayed superimposed on one another (e.g., the image of a ship assigned to the third layer 608c is displayed superimposed on the image of a star assigned to the second layer 608b). For example, the image of a ship assigned to the third layer 608c optionally obstructs the display of the opening portion assigned to the second layer 608b. In some embodiments, the asset 610c assigned to the third layer 608c has a visual effect applied to it (e.g., animation and / or movement such as a ship moving up and down). In some embodiments, the visual effect applied to the asset 610c is different from the visual effects applied to the assets assigned to the other layers.

[0137] A fourth tier 608d is displayed above the first, second, and third tiers 608a-608c. As shown in FIG. 6A, the fourth tier 608d is assigned an asset 610d (e.g., an image of a cartoon character). In some embodiments, the asset 610d assigned to the fourth tier 608d has a visual effect applied to it (e.g., a cartoon character animating between different poses). In some embodiments, the visual effect applied to the asset 610d is different from the visual effects applied to the assets assigned to the other tiers.

[0138] The fifth tier 608e is displayed above the first, second, third, and fourth tiers 608a-608d. As shown in FIG. 6A , the fifth tier 608e is assigned assets 610e (e.g., text describing a service provider associated with the representation of the card 606 (e.g., "Amusement Park")) and identifying information associated with the representation of the card 606 (e.g., "Amy"). In some embodiments, the fifth tier 608e is a static layer that does not include visual effects. By displaying the assets 610e assigned to the fifth tier 608e above the other layers, the assets 610e are always visible (not obstructed by any assets in other lower layers) when displaying the representation of the card 606.

[0139] In some embodiments, dynamic data structures (e.g., dynamic JSON objects) are used to assign colors, assets, and text to corresponding layers. In some embodiments, dynamic data structures are also used to assign visual effects to assets. For example, the dynamic data structure specifies a color to be assigned to the first layer 608a, a first image file (e.g., a star image) to be assigned to the second layer 608b as the second asset 610b (e.g., specifying the size and / or position of the star image), a second image file (e.g., a ship image) to be assigned to the third layer 608c as the third asset 610c, a third image file (e.g., a cartoon character image) to be assigned to the fourth layer 608d as the fourth asset 610d, and text to be assigned to the fifth layer 608e as asset 610e. For layers that have visual effects, the dynamic data structure also specifies the visual effects to be applied to the assets. In this manner, the visual characteristics of a representation of the card 606 can be stored in an easily reconfigurable format for use with different service providers and / or users.

[0140] In some embodiments, the dynamic data structure is a JSON object that includes key-value pairs that represent attributes of the representation of the card 606 and values ​​associated with those attributes. In some embodiments, the JSON object includes a key for a parallax effect, with a value that indicates whether a parallax effect is enabled for the representation of the card 606 (e.g., whether the second layer 608b and the fourth layer 608d move in opposite directions based on the orientation of the device 600). In some embodiments, there is a key-value pair that describes the visual effects (e.g., sparkle) of assets located in the background parallax layer (e.g., the second layer 608b). These assets may have their own visual effects (e.g., sparkle) in addition to the movement defined by the parallax effect. In some embodiments, there is a key-value pair that describes the visual effects of assets assigned to layers between the parallax layers (e.g., the third layer 608c). In some embodiments, there is a key-value pair that describes the visual effects of assets assigned to the foreground parallax layer (e.g., the fourth layer 608d). These assets may have their own visual effects in addition to the movement defined by the parallax effect. In some embodiments, there are key-value pairs that describe the visual effects of assets located above all other layers (e.g., fifth layer 608e). In some embodiments, there are key-value pairs that describe the visual effects of additional assets that are displayed in response to a successful transaction. Although described as a JSON object with key-value pairs, in other implementations, the card may be represented in other ways using variables and attributes that represent one or more of the above characteristics.

[0141] FIG. 6B shows device 600 including a display 602 (e.g., a touchscreen display). In some embodiments, device 600 is a portable multifunction device such as a smartphone. In some embodiments, device 600 is a wearable device such as a smartwatch. In FIG. 6B, device 600 displays a user interface 604 including a representation of a card 606. In some embodiments, the representation of card 606 is a digital pass associated with data that can be transmitted (e.g., to a pass reader terminal) to use or redeem a pass at a service provider (e.g., an "amusement park"). In some embodiments, the representation of card 606 is associated with a financial account (e.g., a bank account, a credit card account, a debit card account, a payment account, and / or a cash account). In some embodiments, the service provider is a business that provides access to a service (e.g., an amusement park, a concert venue, a merchant with a membership). In some embodiments, the service provider is a different entity (e.g., a company, a third party) from the entity (e.g., a first party) that developed and / or provides the device 600 and / or the operating system running on the device 600. In some embodiments, the user interface 604 is a user interface for a vendor application (e.g., a third party application), a vendor website (e.g., a third party website), or a wallet application (e.g., a first party wallet application included in the operating system of the device 600). In some embodiments, the representation of the card 606 is an electronic ticket, a membership card, an access badge, a credit card, a debit card, a store card, and / or another digital representation of a physical card. In the embodiment shown in FIG. 6B, the representation of the card 606 is a digital pass that provides access to a venue called an amusement park.

[0142] As shown in FIG. 6B , the first, second, third, fourth, and fifth layers 608a-608e (shown in FIG. 6A ) are displayed simultaneously, overlapping one another, to create a representation of the card 606. The assets 610b-610e assigned to layers 608b-608e, respectively, are at least partially visible while the layers are displayed simultaneously. In some embodiments, the background color assigned to the first layer 608a is visible behind the other layers. In some embodiments, the assets 610b-610e assigned to layers 608b-608e, respectively, can be scaled to different sizes to display the representation of the card 606 on screens of various sizes (e.g., on the screen of a wearable device such as a watch).

[0143] In some embodiments, while a representation of card 606 is displayed in user interface 604, visual effects are applied to assets assigned to a subset of layers. For example, a particle effect is applied to asset 610b without applying particle effects to assets assigned to other layers. In some embodiments, the particle effect includes one or more (e.g., all) of a behavior component, a density component, and a physics component. The behavior component defines how an asset moves or changes over time. In some embodiments, the behavior component includes shimmering, falling, blooming, rising, and / or flowing (e.g., moving in an arcing path). The density component defines the number of copies of an asset that appear on an assigned layer. In some embodiments, the density component also defines the size of the asset (e.g., smaller assets are used at a higher density, so more copies of an asset will fit on an assigned layer). The physics component defines simulated forces that affect the movement of an asset. For example, simulated wind forces may cause an asset to move more roughly (e.g., when combined with a falling behavior). In some embodiments, each of the components of a visual effect is specified in a dynamic data structure. The dynamic data structure allows the components of the visual effect, and therefore the visual appearance of the card 606 representation, to be easily modified.

[0144] FIG. 6C shows device 600 displaying a parallax effect. The parallax effect is applied to asset 610b (e.g., an image of a star) assigned to second layer 608b and asset 610d (e.g., an image of a cartoon character) assigned to fourth layer 608d. The parallax effect is optionally not applied to other layers of the representation of card 606. When device 600 is tilted in a first orientation relative to a reference point (e.g., the device is tilted to the right relative to a user viewing display 602), asset 610b moves to the right and asset 610d moves to the left, as shown in the left illustration of FIG. 6C. When device 600 is tilted in a second orientation relative to a reference point (e.g., the device is tilted to the left relative to a user viewing display 602), asset 610b moves to the left and asset 610d moves to the right, as shown in the right illustration of FIG. 6C. Assets 610c and 610e remain stationary as device 600 changes orientation. A parallax effect is applied to the representation of the card 606, giving the representation of the card 606 the appearance of enhanced depth (or three-dimensionality) by moving assets in opposite directions based on the orientation of the device 600 relative to a reference point. The parallax effect also provides visual feedback to the user that the representation of the card 606 is not a static object, thereby indicating to the user that the representation of the card 606 corresponds to an account.

[0145] In some embodiments, the parallax effect is applied to the asset in conjunction with another visual effect, for example, both a parallax effect and a particle effect are applied (e.g., simultaneously) to asset 610b.

[0146] 6D illustrates a modification of a visual effect applied to asset 610b. As shown in FIG. 6D, the particle effect applied to asset 610b has been modified to cause asset 610b to appear more dense, which also reduces the size of asset 610b (e.g., a smaller star image and more stars displayed). In some embodiments, the visual effect is modified by changing a component of the visual effect in a dynamic data structure. For example, the density component of the particle effect is changed to a higher density. Thus, the configuration of the representation of card 606 allows for various density levels of assets and / or effects.

[0147] 6E illustrates a modification to an asset assigned to a layer. As shown in FIG. 6E, an asset 610b assigned to a second layer 608b (e.g., as shown in FIG. 6D) is changed to a different asset 610g (e.g., an image of a star is changed to an image of a flower). In some embodiments, the asset 610b is changed to asset 610g by changing the image file specified in the dynamic data structure for the second layer 608b (e.g., the dynamic data structure is updated to reference the new image file assigned to the second layer 608b).

[0148] FIG. 6F illustrates an additional, sixth layer 608f added to the layered structure of the representation of the card 606. The sixth layer 608f is added in response to detecting data associated with the representation of the card 606 being used in a transaction (e.g., when the device 600 is held in proximity to a pass reader terminal). The sixth layer 608f is displayed above the first, second, third, fourth, and fifth layers 608a-608e. As shown in FIG. 6F, the sixth layer 608f is assigned an asset 610f (e.g., an image of stars arranged in a heart shape). In some embodiments, an additional visual effect is applied to the asset 610f in response to detecting a transaction (e.g., in response to submitting a credential for use in the transaction and / or in response to completing the transaction) without applying the additional effect to assets assigned to other layers (as described with respect to FIGS. 6G-6I). In some embodiments, a dynamic data structure is used to specify the assets and / or visual effects to be added to the sixth layer 608f when a transaction is detected.

[0149] 6G shows device 600 being held in proximity to a pass reader terminal 614. In FIG. 6G, device 600 detects that data associated with a representation of card 606 (e.g., account credentials) has been provided by device 600 to pass reader terminal 614 and / or that data associated with the representation of card 606 (e.g., account credentials) has been accepted by pass reader terminal 614 (e.g., indicating a successful transaction). In some embodiments, the data associated with the representation of card 606 is provided by device 600 via a signal from an NFC transceiver and / or optical scan. In some embodiments, a communication received by device 600 (e.g., a confirmation message from a remote server) indicates that a visual element corresponding to the representation of card 606, such as a barcode or QR code, has been optically scanned (and, optionally, accepted in a successful transaction). In some embodiments, device 600 provides data associated with a representation of card 606 to pass reader terminal 614 in response to receiving (e.g., detecting) a user input at device 600 (e.g., approval, contact on display 602, movement of device 600, rotation of a rotatable input device, biometric information or authentication (e.g., fingerprint data, face data, and / or iris data), and / or pressing of a hardware button on device 600).

[0150] After (e.g., in response to) detecting that data associated with a representation of card 606 has been provided by device 600 to pass reader terminal 614 and / or that data associated with the representation of card 606 (e.g., account credentials) has been accepted by pass reader terminal 614 (e.g., indicating a successful transaction), device 600 displays the representation of card 606 along with assets 610f assigned to an additional, sixth tier 608f (as shown in FIG. 6F ) simultaneously displayed above the assets assigned to the other tiers. The display of assets 610f provides notification that data associated with a representation of card 606 has been provided by device 600 to pass reader terminal 614 and / or that data associated with the representation of card 606 has been accepted by pass reader terminal 614. In some embodiments, when assets 610f assigned to an additional, sixth tier 608f are displayed (e.g., in response to detecting a transaction), the other tiers (and their assigned assets) are dimmed (or otherwise de-highlighted), as shown in FIG. 6G .

[0151] In some embodiments, an additional confirmation icon 616 (e.g., a check mark icon) is also displayed on user interface 604 to indicate that data associated with the representation of card 606 has been provided by device 600 to pass reader terminal 614 and / or that data associated with the representation of card 606 has been accepted by pass reader terminal 614. In some embodiments, after (e.g., in response to) detecting that data associated with the representation of card 606 has been provided by device 600 to pass reader terminal 614 and / or that data associated with the representation of card 606 has been accepted by pass reader terminal 614, device 600 provides a tactile and / or audible output, as indicated by the wavy lines around the corners of device 600 in FIG. 6G .

[0152] In some embodiments, a visual effect is applied to the asset 610f in response to detecting a transaction. In some embodiments, the visual effect applied to the asset 610f is a path effect. The path effect specifies one or more predefined paths for the asset 610f to move over time. For example, as shown in FIGS. 6G-6I, the predefined paths move the assets 610f away from each other to create a zoom effect of a heart formed by the assets 610f. In some embodiments, the path effect also defines the size of the asset over time (e.g., the assets 610f get larger as they move along the predefined path to enhance the zoom effect). In some embodiments, the path effect is specified in a dynamic data structure. The dynamic data structure allows for easy modification of the visual effect applied to the asset when a transaction is detected.

[0153] 6G-6I, while a path effect is applied to assets 610f, other layers of the representation of card 606 (and their assigned assets) transition from a dark state to their original brightness, thereby providing additional notification that a transaction has been detected by device 600. By providing various types of visual feedback to the user before the transaction is detected (e.g., by applying a parallax effect when device 600 detects, via one or more motion sensors, that the orientation of device 600 has changed), and after (e.g., in response to) the transaction is detected (e.g., by submitting credentials and / or completing the transaction), device 600 provides notification to the user that the representation of card 606 is associated with a valid account and that a transaction has been detected (e.g., is being securely performed).

[0154] 7 is a flow diagram illustrating a method for displaying representations of cards using a computer system, according to some embodiments. Method 700 is performed on a computer system (e.g., 100, 300, 500, and / or 600) having a display generation component. Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0155] As described below, method 700 provides an intuitive way to display a card representation. This method reduces the cognitive burden on the user to recognize the card representation and to verify that the card representation is authentic, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to recognize card representations faster and more efficiently conserves power and extends the time between battery charges.

[0156] In method 700, a computer system (e.g., 600) (e.g., a smart device, mobile device such as a smartphone or smartwatch) displays (702) via a display generation component (e.g., 602) a user interface (e.g., 604) (e.g., for a wallet application) including a representation (e.g., 606) of a card (e.g., a payment card, an access pass), where the representation of the card includes multiple layers (e.g., 608a-608e) displayed simultaneously. The multiple layers include (704) a first layer (e.g., 608b) having a first visual asset (e.g., 610b) (e.g., an image used on the first layer, a star) and (706) a second layer (e.g., 608d) having a second visual asset (e.g., 610d) (e.g., an image used on the second layer, a cartoon character).

[0157] The computer system applies (708) the first set of visual effects (e.g., instructions defining the behavior of the asset, twinkling stars) to the first visual asset (e.g., 610b) without applying the first set of visual effects to the second visual asset (e.g., 610d).

[0158] The computer system applies (710) a second set of visual effects (e.g., instructions defining the behavior of the asset, parallax movement) that differ from the first set of visual effects to a second visual asset (e.g., 610d).

[0159] Applying different sets of visual effects to different assets provides visual feedback to the user that the card representation is authentic (e.g., a card representation without visual effects may indicate that the card is fraudulent). Applying different sets of visual effects to different assets also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to the user and enhancing security improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0160] In some embodiments, a dynamic data structure (e.g., a dynamic JSON object) specifies that a first visual asset is assigned to a first tier and a second visual asset is assigned to a second tier. Using a dynamic data structure to specify which tiers a visual asset is assigned to provides the user with additional control over the appearance of the card's representation. Providing the user with additional control of the computer system improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0161] In some embodiments, the dynamic data structure specifies that a first set of visual effects is assigned to a first tier and a second set of visual effects is assigned to a second tier. Using the dynamic data structure to specify which tier's set of visual effects is assigned provides the user with additional control over the appearance of the card's representation. Providing the user with additional control of the computer system improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0162] In some embodiments, the dynamic data structure is a JSON object that includes key-value pairs representing attributes of the card representation (e.g., 606) and values ​​associated with those attributes. In some embodiments, the JSON object includes a parallax effect key with a value indicating whether parallax effects are enabled for the card representation (e.g., whether the second layer 608b and the fourth layer 608d move in opposite directions based on the orientation of the device 600). In some embodiments, there is a key-value pair that describes the visual effects (e.g., sparkle) of assets located in the background parallax layer (e.g., the second layer 608b). These assets may have their own visual effects (e.g., sparkle) in addition to the movement defined by the parallax effect. In some embodiments, there is a key-value pair that describes the visual effects of assets assigned to layers between the parallax layers (e.g., the third layer 608c). In some embodiments, there is a key-value pair that describes the visual effects of assets assigned to the foreground parallax layer (e.g., the fourth layer 608d). These assets may have their own visual effects in addition to the movement defined by the parallax effect. In some embodiments, there are key-value pairs that describe the visual effects of assets located above all other layers (e.g., fifth layer 608e). In some embodiments, there are key-value pairs that describe the visual effects of additional assets that are displayed in response to a successful transaction. Although described as a JSON object with key-value pairs, in other implementations, the card may be represented in other ways using variables and attributes that represent one or more of the above characteristics.

[0163] In some embodiments, a second set of visual effects (e.g., parallax movement) is applied to the first visual asset (e.g., 610b). Applying different sets of visual effects to different assets provides visual feedback to the user that the card representation is authentic (e.g., a card representation without visual effects may indicate that the card is fraudulent). Applying different sets of visual effects to different assets also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to the user and enhancing security improves the usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0164] In some embodiments, the second set of visual effects is a subset of the first set of visual effects (e.g., both the first and second sets of visual effects are applied to the first asset (e.g., 610b)). Applying different sets of visual effects to different assets provides visual feedback to the user that the card representation is authentic (e.g., a card representation without visual effects may indicate that the card is fraudulent). Applying different sets of visual effects to different assets also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to the user and enhancing security improves the usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and also reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0165] In some embodiments, the first set of visual effects includes particle effects that specify animated visual characteristics of the visual assets. Applying particle effects to particular assets provides visual feedback to the user that the card representation is authentic (e.g., a card representation without particle effects may indicate that the card is fraudulent). Applying particle effects to particular assets also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to the user and enhancing security improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0166] In some embodiments, the particle effect includes at least one of a behavioral component (e.g., a style of asset movement: sparkle, fall, bloom, rise, and / or flow (e.g., moving in an arcing path)), a density component (e.g., the number of copies of the asset that appear as part of an assigned tier). In some embodiments, the density component also defines the size of the asset (e.g., smaller assets are used at a higher density, so more copies of the asset will fit in an assigned tier), or a physics component (e.g., a simulated force affecting the movement of the asset (e.g., wind)). Applying particle effects along with behavioral, density, and / or physics components for a particular asset provides visual feedback to the user that the card representation is authentic (e.g., a card representation without particle effects may indicate that the card is fraudulent). Applying particle effects along with behavioral, density, and / or physics components for a particular asset also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to users and enhancing security improves the usability of the computer system, makes the user-device interface more efficient (e.g., by assisting users in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing users to use the computer system more quickly and efficiently.

[0167] In some embodiments, the second set of visual effects includes a parallax effect (e.g., as shown in FIG. 6C ), and the computer system applies the parallax effect to visual assets assigned to a subset of the multiple layers (e.g., parallax is applied to assets assigned to the second layer 608b and the fourth layer 608d). Applying the parallax effect to certain assets provides visual feedback to the user that the card representation is authentic (e.g., a card representation without the parallax effect may indicate that the card is fraudulent). Applying the parallax effect to certain assets also enhances security by making it more difficult to copy the card representation. Providing improved visual feedback to the user and enhancing security improves the usability of the computer system and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), as well as reducing power usage and improving the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0168] In some embodiments, the visual assets assigned to the subset of the plurality of layers include at least a second visual asset (e.g., 610b). In some embodiments, applying the parallax effect includes detecting a change in orientation of the display generating component (e.g., 602) while displaying a representation of the card (e.g., 606). In some embodiments, in response to determining that the change in orientation is in a first orientation, the computer system moves the second visual asset (e.g., 610b) in a first direction and moves at least one visual asset (e.g., 610d) different from the second visual asset in a second direction opposite the first direction (e.g., as shown on the left side of FIG. 6C ). In some embodiments, in response to determining that the change in orientation is in a second orientation, the computer system moves the second visual asset (e.g., 610b) in a second direction and moves at least one visual asset (e.g., 610d) different from the second visual asset in a first direction opposite the second direction (e.g., as shown on the left side of FIG. 6D ). Moving certain assets in opposite directions with the parallax effect provides visual feedback to the user that the representation of the card is authentic (e.g., a representation of the card without the parallax effect may indicate that the card is fraudulent). Moving certain assets in opposite directions with the parallax effect also enhances security by making it more difficult to copy the representation of the card. Providing improved visual feedback to the user and enhancing security improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0169] In some embodiments, at least one layer (e.g., 608e) (e.g., an upper layer) of the plurality of layers includes at least one visual asset (e.g., 610e) (e.g., a company logo and / or a user's name). In some embodiments, at least one layer is displayed without visual effects applied to the visual assets assigned to the at least one layer (e.g., the visual assets on the at least one layer are displayed statically over the assets of other layers, without animation, movement, and / or other visual effects applied to the assets on the at least one layer). Not applying visual effects to the at least one layer provides a user with visual feedback that the card representation is authentic. Not applying visual effects to the at least one layer also improves the visibility of text or other visual assets included on the at least one layer, improving the user experience when viewing the card representation. Providing improved visual feedback to the user improves the usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0170] In some embodiments, the computer system detects (712) that data associated with a representation of a card (e.g., 606) has been used to complete a transaction (e.g., device 600 was held in proximity to pass reader 614 and data was successfully transferred and verified for the transaction). In some embodiments, in response to detecting that data associated with the representation of the card has been used to complete a transaction, the computer system displays (714) the representation of the card with an additional layer (e.g., 608f), where the additional layer is assigned additional visual assets (e.g., 610f) (e.g., one or more images arranged in a shape (e.g., smiley face, heart)). In some embodiments, a request to display the representation of the card is received. In some embodiments, in accordance with a determination that the request to display the representation of the card corresponds to the completion of a transaction, the computer system displays the representation of the card with the additional layer. In some embodiments, in accordance with a determination that the request to display the representation of the card does not correspond to the completion of a transaction, the computer system displays the representation of the card without the additional layer. Displaying the additional layer with the additional visual assets in response to completing the transaction provides the user with visual feedback confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader). Providing improved visual feedback increases usability of the computer system and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0171] In some embodiments, in response to detecting that the data associated with the representation of the card (e.g., 606) has been used to complete the transaction, the computer system applies a third set of visual effects (e.g., an animated zoom effect) to an additional visual asset (e.g., 610f) without applying the third set of visual effects to the first and second visual assets (e.g., 610b and 610d). In some embodiments, a request to display a representation of the card is received. In some embodiments, in accordance with a determination that the request to display the representation of the card corresponds to completing the transaction, the computer system displays the representation of the card with the additional layer and applies the third set of visual effects to the additional asset. In some embodiments, in accordance with a determination that the request to display the representation of the card does not correspond to completing the transaction, the computer system displays the representation of the card without the additional layer and / or applies the third set of visual effects to the additional asset. In response to completing the transaction, applying the third set of visual effects to the additional asset provides visual feedback to the user confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader). Providing improved visual feedback can improve usability of a computer system, make user device interfaces more efficient (e.g., by assisting users in making appropriate inputs and reducing user errors when operating / interacting with a computer system), and further reduce power usage and improve battery life of a computer system by allowing users to use the device more quickly and efficiently.

[0172] In some embodiments, the third set of visual effects includes a path effect that specifies a predefined path for moving additional visual assets (e.g., 610f) over time. Applying the path effect to the additional assets in response to completing the transaction provides the user with visual feedback confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader terminal). Providing improved visual feedback increases usability of the computer system and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0173] In some embodiments, the predefined path for the additional visual asset (e.g., 610f) is a path that creates a zoom effect (e.g., the additional asset moves away from the other assets and / or the additional asset is enlarged as the asset moves along the path over time). Applying the zoom effect to the additional asset in response to completing the transaction provides the user with visual feedback confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader terminal). Providing improved visual feedback increases usability of the computer system and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0174] In some embodiments, a dynamic data structure (e.g., a dynamic JSON object) specifies that the predefined path is assigned to additional visual assets (e.g., 610f). Using a dynamic data structure to specify that the predefined path is assigned to additional assets provides the user with additional control over the appearance of the card's representation. Providing the user with additional control of the computer system improves usability of the computer system, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the computer system and reducing user errors), and additionally reduces power usage and improves the battery life of the computer system by allowing the user to use the computer system more quickly and efficiently.

[0175] In some embodiments, an additional layer (e.g., 608f) is displayed above multiple layers (e.g., assets on an additional layer at least partially block the display of assets on lower layers that appear in the same location on the display). Displaying an additional layer above other layers in response to completing a transaction provides the user with visual feedback confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader terminal). Providing improved visual feedback increases usability of the computer system and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0176] In some embodiments, in response to detecting that data associated with a representation of a card (e.g., 606) has been used to complete a transaction, the computer system displays the visual assets (e.g., 610b-610e) assigned to each of the multiple layers (e.g., 608a-608e) in a dimmed state. In some embodiments, the assets assigned to the multiple layers transition from a dimmed state to their original intensity over time. Displaying the assets in a dimmed state in response to completing a transaction provides the user with visual feedback confirming that the data corresponding to the card was successfully provided (e.g., successfully transmitted to the pass reader terminal). Providing improved visual feedback improves usability of the computer system and makes the user device interface more efficient (e.g., by helping the user make appropriate inputs and reducing user errors when operating / interacting with the computer system), which in turn reduces power usage and improves battery life of the computer system by allowing the user to use the device more quickly and efficiently.

[0177] In some embodiments, a computer system receives a request to display a visual asset, and characteristics (e.g., size and / or resolution) of a display generation component are determined. In some embodiments, the computer system displays the visual asset at a first size according to the characteristic being a first characteristic (e.g., a first display size and / or a first resolution, a smartphone display). In some embodiments, the computer system displays the visual asset at a second size different from the first size according to a second characteristic different from the first characteristic (e.g., a second display size and / or a second resolution, a watch display) (e.g., the asset is scaled based on the size of the display).

[0178] The foregoing has been described with reference to specific embodiments for purposes of explanation. However, the exemplary discussion above is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments have been chosen and described in order to best explain the principles of the present technique and their practical application. This will enable others skilled in the art to best utilize the present technique and various embodiments with various modifications as suited to the particular applications intended.

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

[0180] As mentioned above, one aspect of the present technology is to collect and use data available from various sources to display a representation of a card and use the data associated with the card for a transaction. This disclosure contemplates that, in some examples, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone number, email address, Twitter ID, home address, data or records regarding the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.

[0181] This disclosure recognizes that the use of such personal information data in the present technology may be used to the benefit of the user. For example, personal information data may be used to display customized renderings of cards. Moreover, other uses of personal information data that benefit the user are also contemplated by this disclosure. For example, health and fitness data may be used to provide insight into the user's overall wellness, or may be used as proactive feedback to individuals using the technology in pursuit of wellness goals.

[0182] This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data adhere to robust privacy policies and / or privacy practices. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining the strict confidentiality of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use changes. Personal information from users should be collected for the entity's lawful and legitimate uses and should not be shared or sold except for those lawful uses. Furthermore, such collection / sharing should be carried out only after the user's informed consent is obtained. Furthermore, such entities should consider taking all necessary measures to protect and secure access to such personal information data and to ensure that others with access to that personal information data comply with the entity's privacy policies and procedures. Furthermore, such entities may be able to undergo third-party assessments to demonstrate their adherence to widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal data collected and / or accessed and should comply with applicable laws, regulations, and standards, including jurisdiction-specific considerations. For example, in the United States, the 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), while health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained in each country with respect to different types of personal data.

[0183] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, when displaying a representation of a card, the present disclosure may be configured to allow a user to select "opt-in" or "opt-out" of participating in the collection of personal information data during registration for the service or at any time thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notice regarding the access or use of personal information. For example, the user may be notified upon downloading an app that will access the user's personal information data, and then again immediately before the app accesses the user's personal information data.

[0184] Furthermore, it is the intent of this disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data when it is no longer needed. Furthermore, where applicable, de-identification of data can be used to protect user privacy, including in certain health-related applications. De-identification can be facilitated where appropriate by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.

[0185] Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more various disclosed embodiments, this disclosure contemplates that the various embodiments may also be implemented without requiring access to such personal information data. That is, various embodiments of the present technology are not rendered inoperable by the absence of all or part of such personal information data. For example, a card representation may be displayed based only on a minimal amount of non-personal information or personal information, such as content requested by a device associated with a user, other non-personal information available at a service provider, or publicly available information.

Claims

1. 1. A computer system comprising: a display generation component; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising: displaying, via the display generation component, a user interface including a representation of a digital card for conducting a transaction, the representation of the digital card including multiple layers displayed simultaneously, the multiple layers comprising: a first tier having a first visual asset; a second tier having second visual assets; applying the first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset; applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects; Detecting that data associated with the representation of the digital card has been used to complete a transaction; in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction; displaying the representation of the digital card with an additional layer, the additional layer having additional visual assets assigned to it; 11. A computer system comprising: instructions for applying a third set of visual effects to the additional visual asset without applying the third set of visual effects to the first and second visual assets, the third set of visual effects comprising a path effect that specifies a predefined path for moving the additional visual asset over time.

2. The computer system of claim 1 , wherein a dynamic data structure specifies that the first visual asset is assigned to the first tier and the second visual asset is assigned to the second tier.

3. 3. The computer system of claim 2, wherein the dynamic data structure specifies that the first set of visual effects is assigned to the first tier and the second set of visual effects is assigned to the second tier.

4. The computer system of claim 1 , wherein the second set of visual effects is applied to the first visual asset.

5. 2. The computer system of claim 1, wherein the second set of visual effects is a subset of the first set of visual effects.

6. The computer system of claim 1 , wherein the first set of visual effects includes particle effects that specify animated visual characteristics of a visual asset.

7. The computer system of claim 6 , wherein the particle effect includes at least one of a behavioral component, a density component, or a physical component.

8. the second set of visual effects includes a parallax effect, and the one or more programs: The computer system of claim 1 , further comprising instructions for applying the parallax effect to visual assets assigned to a subset of the plurality of layers.

9. The visual assets assigned to the subset of the plurality of layers include at least the second visual asset, and applying the parallax effect includes: detecting a change in orientation of the display generating component while displaying the representation of the digital card; in response to determining that the change in orientation is in a first orientation, moving the second visual asset in a first direction; moving at least one visual asset different from the second visual asset in a second direction opposite to the first direction; upon determining that the change in orientation is in a second orientation, moving the second visual asset in the second direction; 10. The computer system of claim 8, further comprising: moving at least one visual asset different from the second visual asset in the first direction opposite the second direction.

10. 2. The computer system of claim 1, wherein at least one layer of the plurality of layers includes at least one visual asset, and the at least one layer is displayed without visual effects applied to a visual asset assigned to the at least one layer.

11. The computer system of claim 1 , wherein the predefined path for the additional visual assets is a path that creates a zoom effect.

12. The computer system of claim 1 , wherein a dynamic data structure specifies that the predefined paths are assigned to the additional visual assets.

13. The computer system of claim 1 , wherein the additional layer is displayed above the plurality of layers.

14. the one or more programs 10. The computer system of claim 1, further comprising instructions for displaying visual assets assigned to each layer of the plurality of layers in a dimmed state in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction.

15. 1. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs comprising: displaying, via the display generation component, a user interface including a representation of a digital card for conducting a transaction, the representation of the digital card including multiple layers displayed simultaneously, the multiple layers comprising: a first tier having a first visual asset; a second tier having second visual assets; applying the first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset; applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects; Detecting that data associated with the representation of the digital card has been used to complete a transaction; in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction; displaying the representation of the digital card with an additional layer, the additional layer having additional visual assets assigned to it; A non-transitory computer-readable storage medium comprising instructions for applying a third set of visual effects to the additional visual asset without applying the third set of visual effects to the first and second visual assets, the third set of visual effects comprising a path effect that specifies a predefined path for moving the additional visual asset over time.

16. 1. A method comprising: A computer system in communication with a display generation component, comprising: displaying, via the display generation component, a user interface including a representation of a digital card for conducting a transaction, the representation of the digital card including multiple layers displayed simultaneously, the multiple layers comprising: a first tier having a first visual asset; a second tier having second visual assets; and applying the first set of visual effects to the first visual asset without applying the first set of visual effects to the second visual asset; applying a second set of visual effects to the second visual asset, the second set of visual effects being different from the first set of visual effects; detecting that data associated with the representation of the digital card has been used to complete a transaction; in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction; displaying the representation of the digital card with an additional layer, the additional layer being assigned additional visual assets; and applying a third set of visual effects to the additional visual asset without applying the third set of visual effects to the first and second visual assets, the third set of visual effects including a path effect that specifies a predefined path for moving the additional visual asset over time.

17. 16. The non-transitory computer-readable storage medium of claim 15, wherein a dynamic data structure specifies that the first visual asset is assigned to the first tier and the second visual asset is assigned to the second tier.

18. 20. The non-transitory computer-readable storage medium of claim 17, wherein the dynamic data structure specifies that the first set of visual effects is assigned to the first tier and the second set of visual effects is assigned to the second tier.

19. The non-transitory computer-readable storage medium of claim 15 , wherein the second set of visual effects is applied to the first visual asset.

20. 16. The non-transitory computer-readable storage medium of claim 15, wherein the second set of visual effects is a subset of the first set of visual effects.

21. 20. The non-transitory computer-readable storage medium of claim 15, wherein the first set of visual effects includes particle effects that specify animated visual characteristics of a visual asset.

22. 22. The non-transitory computer-readable storage medium of claim 21, wherein the particle effect includes at least one of a behavioral component, a density component, or a physical component.

23. the second set of visual effects includes a parallax effect, and the one or more programs: The non-transitory computer-readable storage medium of claim 15 , further comprising instructions for applying the parallax effect to visual assets assigned to a subset of the plurality of layers.

24. The visual assets assigned to the subset of the plurality of layers include at least the second visual asset, and applying the parallax effect includes: detecting a change in orientation of the display generating component while displaying the representation of the digital card; in response to determining that the change in orientation is in a first orientation, moving the second visual asset in a first direction; moving at least one visual asset different from the second visual asset in a second direction opposite to the first direction; upon determining that the change in orientation is in a second orientation, moving the second visual asset in the second direction; and moving at least one visual asset different from the second visual asset in the first direction opposite the second direction.

25. 16. The non-transitory computer-readable storage medium of claim 15, wherein at least one layer of the plurality of layers includes at least one visual asset, and the at least one layer is displayed without visual effects applied to the visual asset assigned to the at least one layer.

26. The non-transitory computer-readable storage medium of claim 15 , wherein the predefined path for the additional visual assets is a path that creates a zoom effect.

27. The non-transitory computer-readable storage medium of claim 15 , wherein a dynamic data structure specifies that the predefined paths are assigned to the additional visual assets.

28. The non-transitory computer-readable storage medium of claim 15 , wherein the additional layer is displayed above the plurality of layers.

29. the one or more programs 16. The non-transitory computer-readable storage medium of claim 15, further comprising instructions for displaying visual assets assigned to each layer of the plurality of layers in a dimmed state in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction.

30. The method of claim 16 , wherein a dynamic data structure specifies that the first visual asset is assigned to the first tier and the second visual asset is assigned to the second tier.

31. 31. The method of claim 30, wherein the dynamic data structure specifies that the first set of visual effects is assigned to the first tier and the second set of visual effects is assigned to the second tier.

32. The method of claim 16 , wherein the second set of visual effects is applied to the first visual asset.

33. The method of claim 16 , wherein the second set of visual effects is a subset of the first set of visual effects.

34. The method of claim 16 , wherein the first set of visual effects includes particle effects that specify animated visual characteristics of a visual asset.

35. The method of claim 34 , wherein the particle effect includes at least one of a behavioral component, a density component, or a physical component.

36. the second set of visual effects includes a parallax effect, and the method further comprises: The method of claim 16 , further comprising applying the parallax effect to visual assets assigned to a subset of the plurality of layers.

37. The visual assets assigned to the subset of the plurality of layers include at least the second visual asset, and applying the parallax effect includes: detecting a change in orientation of the display generating component while displaying the representation of the digital card; in response to determining that the change in orientation is in a first orientation, moving the second visual asset in a first direction; moving at least one visual asset different from the second visual asset in a second direction opposite to the first direction; upon determining that the change in orientation is in a second orientation, moving the second visual asset in the second direction; 37. The method of claim 36, comprising: moving at least one visual asset different from the second visual asset in the first direction opposite the second direction.

38. 17. The method of claim 16, wherein at least one layer of the plurality of layers includes at least one visual asset, and the at least one layer is displayed without visual effects applied to the visual asset assigned to the at least one layer.

39. The method of claim 16 , wherein the predefined path for the additional visual assets is a path that creates a zoom effect.

40. The method of claim 16 , wherein a dynamic data structure specifies that the predefined paths are assigned to the additional visual assets.

41. The method of claim 16 , wherein the additional layer is displayed above the plurality of layers.

42. 17. The method of claim 16, further comprising displaying visual assets assigned to each layer of the plurality of layers in a dimmed state in response to detecting that the data associated with the representation of the digital card has been used to complete the transaction.

Images