User interface for sharing account with another user identity

Abstract

The invention relates to a user interface for sharing an account with another user identity. The present disclosure generally relates to displaying a user interface for sharing an account associated with a first user identity with a second user identity. The user interface includes a first sharing option and a second sharing option. One or more inputs corresponding to a request to share the account are detected. Where the one or more inputs include a selection of the first sharing option, a request is sent to invite the second user identity to be a common owner of the account. Where the one or more inputs include a selection of the second sharing option, a request is sent to invite the second user identity to be a participant of the account and not to be a common owner of the account.

Description

[0001] This application is a divisional application of the invention patent application with the application date of January 30, 2022, application number 202210113526.5, and name “User interface for sharing an account with another user identity”. Technical Field

[0002] The present disclosure relates generally to computer user interfaces and, more particularly, to user interfaces and techniques for sharing an account with another user identity. Background Art

[0003] The computer system can be used to configure various aspects of an account, such as an account provided on the computer system. Typically, an account is associated with a user of the computer system. Summary of the invention

[0004] Some conventional techniques for configuring accounts using a computer system are often cumbersome and inefficient. For example, some prior art techniques cannot share an account with another user identity. In addition, some prior art techniques for configuring accounts use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. As a result, some prior art techniques for configuring accounts require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0005] Thus, the present technology provides a faster, more efficient method and interface for configuring and sharing an account for use with another user identity for a computer system. Such methods and interfaces optionally supplement or replace other methods for configuring accounts. Such methods and interfaces reduce the cognitive burden imposed on the user and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0006] Example methods are disclosed herein. An example method includes at a computer system associated with a first user identity in communication with a display generation component and one or more input devices: displaying, via the display generation component, a user interface for sharing an account associated with the first user identity with a second user identity, the user interface including a first sharing option and a second sharing option; detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account; and in response to detecting the one or more inputs corresponding to the request to share the account: based on determining that the one or more inputs include a selection of the first sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account; and based on determining that the one or more inputs include a selection of the second sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account.

[0007] An example non-transitory computer-readable storage medium is described herein. An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system associated with a first user identity in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying, via the display generation component, a user interface for sharing an account associated with the first user identity with a second user identity, the user interface including a first sharing option and a second sharing option; detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account; and in response to detecting the one or more inputs corresponding to the request to share the account: based on determining that the one or more inputs include a selection of the first sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account; and based on determining that the one or more inputs include a selection of the second sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account.

[0008] An example transient computer-readable storage medium is described herein. An example transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system associated with a first user identity in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a user interface for sharing an account associated with the first user identity with a second user identity, the user interface including a first sharing option and a second sharing option; detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account; and in response to detecting the one or more inputs corresponding to the request to share the account: based on determining that the one or more inputs include a selection of the first sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account; and based on determining that the one or more inputs include a selection of the second sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account.

[0009] An example computer system is described herein. An example computer system associated with a first user identity includes a display generation component; one or more input devices; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: displaying, via the display generation component, a user interface for sharing an account associated with the first user identity with a second user identity, the user interface including a first sharing option and a second sharing option; detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account; and in response to detecting the one or more inputs corresponding to a request to share the account: based on determining that the one or more inputs include a selection of the first sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account; and based on determining that the one or more inputs include a selection of the second sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account.

[0010] An example computer system associated with a first user identity includes a display generating component; one or more input devices; a device for displaying, via the display generating component, a user interface for sharing an account associated with the first user identity with a second user identity, the user interface including a first sharing option and a second sharing option; a device for detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account; and in response to detecting the one or more inputs corresponding to a request to share the account, a device for the following operations: based on determining that the one or more inputs include a selection of the first sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account; and based on determining that the one or more inputs include a selection of the second sharing option, sending a request to invite the second user identity to become a participant in the account without becoming a co-owner of the account.

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

[0012] Thus, a faster, more efficient method and interface for configuring and sharing an account for use with another user identity is provided for a computer system, thereby increasing the effectiveness, efficiency, and user satisfaction of such computer systems. Such methods and interfaces may supplement or replace other methods for configuring accounts. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0014] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0015] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0016] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0017] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0018] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

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

[0020] Figure 5A A personal electronic device according to some embodiments is shown.

[0021] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.

[0022] FIG. 6A to FIG. 6G An exemplary user interface for sharing an account with another user identity according to some embodiments is shown.

[0023] FIG. 7A to FIG. 7BA An exemplary user interface for sharing an account with another user identity and viewing / configuring the shared account is shown according to some embodiments.

[0024] Figure 8 is a flow chart illustrating a method for sharing an account with another user identity using a computer system according to some embodiments. DETAILED DESCRIPTION

[0025] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0026] A computer system that provides an efficient method and interface for sharing an account with another user identity is needed. For example, a user is needed to share an account with a family member (e.g., a child or a spouse) of the user, wherein the user can select account information and / or account funds available to the family member. Such techniques can reduce the cognitive burden of the user who is sharing the account, thereby improving productivity. Such techniques can also reduce the need for resources (e.g., computer resources, such as memory) by enabling sharing of resources between multiple users. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0027] under, Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an example device for performing techniques for sharing an account with another user identity is provided. FIG. 6A to FIG. 6G An exemplary user interface for sharing an account with another user identity according to some embodiments is shown. FIG. 7A to FIG. 7BA An exemplary user interface for sharing an account with another user identity and viewing / configuring the shared account is shown according to some embodiments. Figure 8 is a flow diagram illustrating a method for sharing an account with another user identity according to some embodiments. FIG. 6A to FIG. 6G and FIG. 7A to FIG. 7BA The user interface in the figure is used to illustrate the process described below, including Figure 8 process.

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

[0029] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0031] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally use other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).

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

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

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

[0035] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1Ais a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0036] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0037] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

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

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

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

[0041] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution-Data-only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not yet been developed as of the filing date of this document.

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

[0043] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures) 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.

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

[0045] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

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

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

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

[0049] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application 11 / 086, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application Ser. No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0050] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

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

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

[0054] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0055] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0056] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent applications: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0057] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

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

[0059] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

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

[0061] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

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

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

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

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

[0066] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application program, etc., and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to be output to the display controller 156.

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

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

[0069] 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 picture / video metadata; and to applications that provide location-based services, such as the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0070] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0071] Contacts module 137 (sometimes called address book or contact list);

[0072] Telephone module 138;

[0073] Video conferencing module 139;

[0074] Email client module 140;

[0075] Instant messaging (IM) module 141;

[0076] Fitness support module 142;

[0077] A camera module 143 for still images and / or video images;

[0078] Image management module 144;

[0079] Video player module;

[0080] Music player module;

[0081] Browser module 147;

[0082] Calendar module 148;

[0083] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user and a widget 149-6 created by the user;

[0084] A widget creator module 150 for forming a user-created widget 149-6;

[0085] Search module 151;

[0086] Video and music player module 152, which merges the video player module and the music player module;

[0087] Notepad module 153;

[0088] Map module 154; and / or

[0089] Online video module 155.

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

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

[0092] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0093] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

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

[0095] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, sending a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0096] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0097] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

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

[0099] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0100] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

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

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

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

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

[0105] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

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

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

[0108] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0109] In some embodiments, the device 100 is a device on which operation of a predefined set of functions is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

[0110] A predefined set of functions that are performed exclusively through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using a trackpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

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

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

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

[0114] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

[0116] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.

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

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

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

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

[0121] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

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

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

[0125] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

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

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

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

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

[0131] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

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

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

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

[0135] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0136] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user interrupts contact with the one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

[0138] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0139] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference). Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or sensors similar to those described above) Figure 1A The memory 370 may include a high-speed random access memory, such as a DRAM, SRAM, DDR RAM, or other random access solid-state memory device; and may optionally include a non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

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

[0141] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0142] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is shown. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0143] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0144] Time 404;

[0145] Bluetooth indicator 405;

[0146] Battery status indicator 406;

[0147] A tray 408 with icons for commonly used applications, such as:

[0148] o An icon 416 of the phone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemail messages;

[0149] o An icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;

[0150] o An icon 420 labeled "Browser" of the browser module 147; and

[0151] ○ Video and music player module 152 (also known as iPod (trademark of Apple Inc.)

[0152] module 152) and an icon 422 labeled "iPod"; and

[0153] Icons for other apps, such as:

[0154] o Icon 424 labeled "Message" of IM module 141;

[0155] o An icon 426 labeled “Calendar” of the calendar module 148;

[0156] o Icon 428 labeled “Photos” of the image management module 144;

[0157] o An icon 430 labeled “Camera” of the camera module 143;

[0158] ○ Icon 432 labeled “Online Video” of the online video module 155;

[0159] ○ Icon 434 labeled “Stock Market” of the Stock Market Desktop Applet 149-2;

[0160] o An icon 436 labeled “Map” of the map module 154;

[0161] ○ Icon 438 labeled “Weather” of the Weather widget 149-1;

[0162] ○ Icon 440 labeled as “Clock” of the alarm clock desktop applet 149-4;

[0163] o An icon 442 labeled “Fitness Support” of the fitness support module 142;

[0164] o An icon 444 labeled "Notepad" of the Notepad module 153; and

[0165] o An icon 446 labeled “Settings” for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

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

[0167] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0168] Although some of the subsequent embodiments will be given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 452 in ), which corresponds to the main axis on the display (e.g., 450) (e.g., Figure 4B According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., Figure 4B 460 and 462 in FIG. 4 ), the location of the contact corresponds to a corresponding location on the display (e.g., in FIG. Figure 4B 460 corresponds to 468, and 462 corresponds to 470). Thus, when a touch-sensitive surface (e.g., Figure 4B 451) and the display of a multi-function device ( Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0170] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more strength sensors for detecting the intensity of contact (e.g., touch) applied. One or more strength sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

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

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

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

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

[0175] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including process 800 ( Figure 8 ). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0176] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0177] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other positional marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the specific user interface element is adjusted according to the detected input. In a touch screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4A In some implementations of the touch screen 112 in FIG. 1 , a detected contact on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0178] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0179] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

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

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

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

[0183] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold in a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units less than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or less than the hysteresis intensity threshold to an intensity equal to or greater than the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or less than the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0184] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0185] Attention is now turned to implementations of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, device 500, device 600a and / or 600b, and device 700a and / or device 700b.

[0186] FIG. 6A to FIG. 6G An exemplary user interface for sharing an account with another user identity according to some embodiments is shown. The user interfaces in these figures are used to illustrate the process described below, including Figure 8 process.

[0187] Fig. 6ADevice 600a (e.g., "first device") associated with a first user identity (e.g., the primary owner of an account) is shown. Device 600a displays a user interface 6004 on display 602a for viewing a summary of an account associated with the first user identity. In some embodiments, the account is used for data services (e.g., a data storage account). User interface 6004 includes a notification 606 that an account can be shared with another user identity (e.g., a family member). In some embodiments, a family member is a second user who has established a relationship with the user of device 600a. In some embodiments, a relationship is established by adding the second user to a list of family members associated with device 600a. In some embodiments, a request to be added to the list of family members is sent to the second user, and the second user is required to confirm the request before being added to the list of family members. In some embodiments, family members include immediate family members, extended family members, friends, colleagues, or any other person who has been added to the list of family members. After the second user is added to the list of family members, one or more features (e.g., photos, videos, music, data storage, applications, financial accounts) accessed using device 600a can be shared with the second user.

[0188] In some embodiments, the user interface 6004 for viewing an overview of an account also includes an enabling representation 608 for viewing detailed information and settings for the account.

[0189] Figure 6B Device 600a is shown displaying a user interface 6010 for viewing account details and settings on display 602a. In some embodiments, user interface 6010 is displayed in response to detecting input 601 (e.g., a tap gesture) corresponding to a location of affordance 608 on display 602a, such as Fig. 6A User interface 6010 includes an affordance 612 for sharing an account with another user identity.

[0190] Figure 6C Device 600a is shown displaying a user interface 6014 for sharing an account on display 602a. In some embodiments, user interface 6014 is displayed in response to detecting input 603 (e.g., a tap gesture) corresponding to a location of notification 606 on display 602a, such as Fig. 6A In some embodiments, in response to detecting input 605 (e.g., a tap gesture) corresponding to the location of affordance 612 on display 602a, user interface 6014 is displayed, such as Figure 6B The user of device 600a may have at least two channels for initiating a process for sharing an account with a second user identity - as shown in FIG. Fig. 6AThe notification 606 shown and Figure 6B The indication shown indicates 612.

[0191] The user interface 6014 includes a first family member user interface object 616a, a second family member user interface object 616b, and a third family member user interface object 616c. Figure 6C 600a, but the number of family member user interface objects can vary based on the number of family members who have established a relationship with the user of device 600a. In some embodiments, the family member user interface objects included in user interface 6014 are a subset (e.g., less than) of all family members who have established a relationship with the user of device 600a. For example, in some embodiments, the family member user interface objects included in user interface 614 include family members who do not have personal accounts for the service. In some embodiments, the family member user interface objects included in user interface 614 include all family members who have established a relationship with the user of device 600a.

[0192] Fig.6D Device 600a is shown displaying a user interface 6016 for sharing accounts on display 602a. User interface 6016 includes a first sharing option 618a and a second sharing option 618b for respective family members. In some embodiments, first and second sharing options 618a and 618b are displayed in response to detecting input 607 (e.g., a tap gesture) corresponding to a location of affordance 616a (e.g., affordance of “Hugo Parker”) on display 602a, such as Figure 6C shown.

[0193] In some embodiments, if you select Fig.6D The first sharing option 618a shown, corresponding family members (such as Figure 6C ) will be invited as co-owners of the account. Fig.6D In the second sharing option 618b shown, the corresponding family member will be invited as a participant of the account, which has fewer account features than the co-owner. In some embodiments, the co-owner of the account is allowed to obtain all detailed information of the account, such as account data storage and data usage information of the account. In some embodiments, the participant of the account is allowed to obtain a limited amount of detailed information of the account, such as only the amount of available data storage and only the participant's data usage.

[0194] Fig. 6EDevice 600a is shown displaying a user interface 6018 for sharing an account on display 602a. User interface 6018 includes a send invitation enable representation 620. In some embodiments, in response to detecting input 609 (e.g., a tap gesture) corresponding to a location of a first sharing option 618a on display 602a, send invitation enable representation 620 is displayed, such as Fig.6D The send invitation enable representation 620 allows the user of device 600a to confirm the invitation that should be sent to the selected family members and to review the terms and conditions for the shared account before sending the invitation.

[0195] Fig. 6F Device 600b (e.g., “second device”) associated with a corresponding user identity (e.g., “Hugo Parker”) is shown. Device 600b receives an indication that the corresponding user identity has been invited to become a co-owner of the account. In response to receiving the indication, device 600b displays a notification 624 on display 602b that an invitation to become a shared user of the account has been received. In some embodiments, notification 624 is displayed on lock screen interface 622 when device 600b is in a locked state.

[0196] Figure 6G Device 600b is shown displaying a user interface 6026 on display 602b for becoming a shared user of an account. In some embodiments, user interface 6026 is displayed after receiving an indication that the corresponding family member has approved becoming a co-owner of the account. In some embodiments, user interface 6026 is displayed in response to detecting selection of notification 624 (e.g., a tap gesture or a long press on notification 624), such as Fig. 6F In some embodiments, the user interface 6026 is displayed in response to detecting a request to access a service associated with the account (e.g., in response to launching an application associated with the service). The user interface 6026 includes information about the type of account sharing provided (e.g., a joint account, in which the corresponding user identity associated with the device 600b will become a co-owner of the account) and detailed information about the account. In some embodiments, the detailed information about the account includes the account amount, balance, and terms and conditions.

[0197] User interface 6026 also includes an acceptance indication 628 and a rejection indication 630. If acceptance indication 628 is selected (e.g., using a tap gesture), the corresponding user identity associated with device 600b will become a co-owner of the account. In some embodiments, after selecting acceptance indication 628, device 600b will be allowed to obtain all account data storage and data usage information of the account. If rejection indication 630 is selected, the corresponding user identity associated with device 600b will not become a co-owner of the account and will not be allowed to obtain account data or data storage information of the account.

[0198] FIG. 7A to FIG. 7BA An exemplary user interface for sharing an account with another user identity and viewing / configuring the shared account according to some embodiments is shown. The user interface in these figures is used to illustrate the process described below, including Figure 8 process.

[0199] Fig. 7A Device 700a (e.g., "first device") associated with a first user identity (e.g., the primary owner of an account) is shown. Device 700a displays a user interface 7004 on display 702a for viewing a summary of an account associated with the first user identity. In some embodiments, the account is used for financial services (e.g., a bank account and / or a credit card account). User interface 7004 includes a notification 708 that an account can be shared with another user identity (e.g., a family member). In some embodiments, a family member is a second user who has established a relationship with a user of device 700a. In some embodiments, a relationship is established by adding the second user to a list of family members associated with device 700a. In some embodiments, a request to be added to a list of family members is sent to the second user, and the second user is required to confirm the request before being added to the list of family members. In some embodiments, family members include immediate family members, extended family members, friends, colleagues, or any other person who has been added to the list of family members. After the second user is added to the list of family members, one or more features (e.g., photos, videos, music, data storage, applications, financial accounts) accessed using device 700a can be shared with the second user.

[0200] In some embodiments, the user interface 7004 for viewing an overview of an account also includes an enabling representation 706 for viewing detailed information and settings for the account.

[0201] Figure 7BDevice 700a is shown, which displays a user interface 7010 for viewing account details and settings on display 702a. In some embodiments, user interface 7010 is displayed in response to detecting input 701 (e.g., a tap gesture) corresponding to the location of enable representation 706 on display 702a, such as Fig. 7A User interface 7010 includes an affordance 712 for sharing an account with another user identity.

[0202] Figure 7C Device 700a is shown displaying a user interface 7014 for sharing an account on display 702a. In some embodiments, user interface 7014 is displayed in response to detecting input 703 (e.g., a tap gesture) corresponding to a location of notification 708 on display 702a, such as Fig. 7A In some embodiments, in response to detecting input 705 (e.g., a tap gesture) corresponding to the location of the affordance 712 on the display 702a, a user interface 7014 is displayed, such as Figure 7B The user of device 700a may have at least two channels for initiating a process for sharing an account with a second user identity - as shown in FIG. Fig. 7A The notification 708 shown and Figure 7B The indication shown indicates 712.

[0203] The user interface 7014 includes a first family member user interface object 716a, a second family member user interface object 716b, and a third family member user interface object 716c. Although three family member user interface objects are shown in 7C, the number of family member user interface objects can vary based on the number of family members who have established a relationship with the user of device 700a. In some embodiments, the family member user interface objects included in the user interface 7014 are a subset (e.g., less than) of all family members who have established a relationship with the user of device 700a. For example, in some embodiments, the family member user interface objects included in the user interface 7014 include family members who do not have a personal account for the service. In some embodiments, the family member user interface objects included in the user interface 7014 include all family members who have established a relationship with the user of device 700a.

[0204] Fig.7DDevice 700a is shown displaying a user interface 7016a for sharing accounts on display 702a. User interface 7016a includes a first sharing option 718a and a second sharing option 718b for respective family members. In some embodiments, first and second sharing options 718a and 718b are displayed in response to detecting input 707 (e.g., a tap gesture) corresponding to a location of affordance 716a (e.g., affordance of “Hugo Parker”) on display 702a, such as Figure 7C shown.

[0205] In some embodiments, if you select Fig.7D The first sharing option 718a shown, corresponding family members (such as Figure 7C ) will be invited as co-owners of the account. Fig.7D In the second sharing option 718b shown, the corresponding family member will be invited as a participant of the account, which has fewer account features than the co-owner. In some embodiments, the co-owner of the account will be allowed to obtain transaction and balance information of all participants and owners of the account. In some embodiments, a participant of the account will be allowed to obtain transaction information of the participant's account, but not the transaction and balance information of other participants or owners of the account.

[0206] Fig. 7E Device 700a is shown displaying a user interface 7018 for sharing an account on display 702a. User interface 7018 includes an income input field 722. In some embodiments, income input field 722 is displayed in response to detecting input 709 (e.g., a tap gesture) corresponding to a location of a first sharing option 718a on display 702a (e.g., an option for inviting another user to become a co-owner), such as Fig.7D In some embodiments, when inviting a respective family member to become a co-owner of an account, if the respective family member accepts the invitation, the service may request the first user identity (e.g., the primary account owner) to confirm their income in order to determine the co-credit limit for the account. In some embodiments, after entering the income amount in income input field 722, the next affordance 720 is enabled.

[0207] Figure 7F Device 700a is shown displaying user interface 7020 for sharing accounts on display 702a. User interface 7020 includes send invitation enable representation 724. In some embodiments, send invitation enable representation 724 is displayed in response to detecting input 709 (e.g., a tap gesture) corresponding to the position of first sharing option 718a (e.g., an option for inviting co-owners) on display 702a, such as Fig.7D In some embodiments, in response to detecting input 711 (e.g., a tap gesture) corresponding to the position of next enable indication 720 on display 702a, a send invitation enable indication 724 is displayed, such as Fig. 7E Send invitation enable representation 724 allows the user of device 700a to confirm the invitation that should be sent to the selected family members and review the terms and conditions for sharing the account before sending the invitation.

[0208] Figure 7G Device 700a is shown displaying user interface 7022 on display 702a. User interface 7022 includes confirmation notification 726 indicating that the corresponding family member has been invited to become a co-owner of the account. In some embodiments, confirmation notification 726 is displayed in response to detecting input 713 (e.g., a tap gesture) corresponding to the location of send invitation enable representation 724 on display 702a, such as Figure 7F shown.

[0209] Figure 7H Device 700a is shown displaying a user interface 7010 on display 702a for viewing account details and settings. Figure 7H As shown, after sending an invitation to the corresponding family member, the family member user interface object 728a is included in the user interface 7010. In some embodiments, the family member user interface object 728a includes an indication of the invitation status of the corresponding family member (e.g., "invitation pending"). After the corresponding family member accepts the invitation, the invitation status changes to indicate the current status (e.g., "co-owner", such as Figure 7AB shown).

[0210] Fig.7I Device 700b (e.g., “second device”) associated with a second user identity (e.g., “Hugo Parker”) is shown. Device 700b receives an indication that the second user identity has been invited to become a co-owner of an account. In response to receiving the indication, device 700b displays on display 702b a notification 732b that an invitation to become a co-owner of the account has been received. In some embodiments, notification 732b is displayed on lock screen interface 7030b when device 700b is in a locked state.

[0211] Figure 7J Device 700b is shown, which displays a user interface 7034a for becoming a shared user of an account on display 702b. In some embodiments, user interface 7034a is displayed in response to detecting selection of notification 732b (e.g., a tap gesture or a long press on notification 732b), such as Fig.7IIn some embodiments, user interface 7034a is displayed in response to detecting a request to access a service associated with an account (e.g., in response to launching an application associated with the service, such as a wallet application).

[0212] like Figure 7J As shown, user interface 7034a includes a continue enable indication 736 and a decline enable indication 738 (e.g., "No, thanks"). If the continue enable indication 736 is selected, the process for becoming a co-owner of the account will continue. If the decline enable indication 738 is selected, the process for becoming a co-owner of the account will stop and the second user identity associated with device 700b will not become a co-owner of the account.

[0213] Figures 7K to 7N Device 700b is shown, which displays user interfaces 7036a to 7036d on display 702b. User interfaces 7036a to 7036d include a series of information input fields. In some embodiments, the series of information input fields are displayed in response to detecting input 715 (e.g., a tap gesture) corresponding to the position of the continue enable indication 736 on display 702a, such as Figure 7J The series of information fields is used to obtain information from the service to verify the identity of the second user identity and determine whether the second user identity qualifies as a co-owner of the account. In some embodiments, the series of information fields includes fields for name, date of birth, telephone number, social security number, nationality, address, and / or income of the second user identity.

[0214] Fig.7O Device 700b is shown displaying user interface 7038 on display 702b. User interface 7038 includes terms and conditions that apply to becoming a co-owner of an account. In some embodiments, the terms and conditions are displayed after the information is entered into Figures 7K to 7N The series information fields shown in the display are displayed after that.

[0215] Figure 7P Device 700b is shown, which displays a user interface 7040 on display 702b. User interface 7040 includes instructions for inputting information into the series of information input fields (such as Figures 7K to 7N In some embodiments, a notification is displayed in response to detecting acceptance of the terms and conditions that apply to becoming a co-owner of an account, such as Fig.7O shown.

[0216] Figure 7QDevice 700b is shown, which displays a user interface 7042a for becoming a shared user of an account on display 702b. In some embodiments, after receiving an indication that the second user identity has been approved to become a co-owner of the account (e.g., Figures 7K to 7N , after submitting the information entered into the series of information input fields) displays user interface 7042a. In some embodiments, in response to detecting a request to access a service associated with an account (e.g., in response to launching an application associated with the service, such as a wallet application) and as Figures 7K to 7N User interface 7042a is shown displayed after submitting information entered into the series of information input fields.

[0217] User interface 7042a includes information about the type of account sharing provided (e.g., a joint account, in which the second user identity associated with device 700b will become a co-owner of the account) and detailed information about the account. In some embodiments, the detailed information about the account includes a credit line, account balance, percentage, and / or terms and conditions of the account.

[0218] User interface 7042a also includes acceptance indication 738b-1 and rejection indication 740b-1. If acceptance indication 738b-1 is selected (e.g., using a tap gesture), the second user identity associated with device 700b will become a co-owner of the account. In some embodiments, after selecting acceptance indication 738b-1, device 700b will be allowed to obtain transaction and balance information of all participants and owners of the account. If rejection indication 740b-1 is selected, the second user identity associated with device 700b will not become a co-owner of the account.

[0219] Figure 7R Device 700b is shown, which displays user interface 7044 on display 702b. User interface 7044 includes status indicators 742a and 742b. In some embodiments, status indicators 742a and 742b are displayed simultaneously in response to detecting input 717 (e.g., a tap gesture) corresponding to the position of acceptance indication 738a on display 702a, such as Figure 7QAs shown. Status indicator 742a indicates the current acceptance status (e.g., "accepted") of the second user identity associated with device 700b. Status indicator 742b indicates the current acceptance status (e.g., "pending") of the first user identity (e.g., the primary account owner) associated with device 700a. Status indicator 742b provides an indication that the first user identity still needs to approve the second user identity to become a co-owner of the account after the second user identity has accepted. In some embodiments, the credit limit, percentage and / or terms and conditions for the account can be changed based on information associated with the second user identity (e.g., credit record). In some embodiments, due to possible changes in the account, the first user identity has the opportunity to view the changes and accept or reject the second user identity as a co-owner of the account after the second user identity has accepted.

[0220] Figure 7S Device 700b is shown, which displays a user interface 7034b for becoming a shared user of an account on display 702b. In some embodiments, user interface 7034b is displayed in response to detecting input 715 (e.g., a tap gesture) corresponding to the position of the continue enable indication 736 on display 702a, such as Figure 7J As shown, bypassing Figures 7K to 7N In some embodiments, when the second user identity associated with device 700b is already an account holder using the service (e.g., when the second user identity already has a credit card with the same bank as the account and / or is the primary account owner associated with device 700a), the user ID is bypassed. Figures 7K to 7N The series of information input fields are shown. Figure 7S As shown, user interface 7034b includes a notification that the second user identity already has an account using the service, and a notification that the second user identity's existing account will be merged with the account of the first user identity associated with device 700a.

[0221] Figure 7T Device 700a is shown, which displays user interface 7046 on display 702a. User interface 7046 includes an income input field for a second user identity that already has an account using the service. In some embodiments, when a second user identity that already has an account using the service is invited to become a co-owner of an account of a first user identity (e.g., the primary account owner associated with device 700a), the service can request the second user identity (e.g., the user associated with device 700b) to confirm its income to determine a common credit line for the combined account.

[0222] Figure 7UDevice 700b is shown, which displays a user interface 7042b on display 702b for becoming a shared user of the account when the second user identity has an account using the service. In some embodiments, user interface 7042b is displayed as Figure 7T In some embodiments, in response to detecting that Figure 7S 4. In some embodiments, after receiving an invitation to become a co-owner of an account of a first user identity associated with device 700a, user interface 7042b is displayed in response to detecting a request to access a service associated with the account (e.g., in response to launching an application associated with the service, such as a wallet application).

[0223] User interface 7042b includes information about the type of account sharing provided (e.g., a joint account, in which an account of a secondary user identity associated with device 700b is to be merged with an account of a primary account owner associated with device 700a) and detailed information about the merged account. In some embodiments, the detailed information about the merged account includes a credit line, account balance, percentage, and / or terms and conditions of the merged account.

[0224] User interface 7042b also includes a merge enable indication 744 and a reject enable indication 740b-2. If the merge enable indication 744 is selected (e.g., using a tap gesture), the process for merging the account of the second user identity associated with device 700b and the account of the first user identity associated with device 700a will continue (e.g., the accounts will be merged). In some embodiments, after selecting the merge enable indication 744 (e.g., after merging the accounts), device 700b will be allowed to obtain transaction and balance information for all participants and owners of the merged account. If the reject enable indication 740b-2 is selected, the account of the second user identity associated with device 700b will not be merged with the account of the first user identity associated with device 700a.

[0225] Figure 7V A device 700a (e.g., "first device") associated with a first user identity (e.g., a primary account owner) is shown displaying a notification 746 on a display 702a that a second user identity has accepted an invitation to become a co-owner of an account. In some embodiments, notification 746 is displayed in response to receiving an indication that the second user identity has accepted the invitation and has been approved by the service to become a co-owner of the account. In some embodiments, notification 746 is displayed on a lock screen interface 7030a when the device 700a is in a locked state.

[0226] Figure 7W Device 700a is shown displaying a user interface 7048 on display 702a for accepting co-ownership of an account. In some embodiments, user interface 7048 is displayed after receiving an indication that the second user identity has accepted the invitation and has been approved to become a co-owner of the account. In some embodiments, in response to detecting a selection of notification 746 (e.g., a tap gesture, a swipe gesture, a long press gesture on notification 746), such as Figure 7V As shown, user interface 7048 is displayed. In some embodiments, user interface 7048 is displayed in response to detecting a request to access a service associated with an account (e.g., in response to launching an application associated with the service, such as a wallet application).

[0227] User interface 7048 includes information about the type of account sharing provided to the second user identity (e.g., a joint account, in which the second user identity associated with device 700b will become a co-owner of the account) and detailed information about the account. In some embodiments, the detailed information about the account includes a credit line, an account balance, a percentage, and / or terms and conditions of the account.

[0228] User interface 7048 also includes an acceptance indication 738a and a rejection indication 740a. If acceptance indication 738a is selected (e.g., using a tap gesture), the second user identity associated with device 700b will become a co-owner of the account (e.g., if the second user identity has an account using the service, the account will be merged). In some embodiments, after selecting acceptance indication 738a, device 700b will be allowed to obtain transaction and balance information for all participants and owners of the account. If rejection indication 740a is selected, the second user identity associated with device 700b will not become a co-owner of the account.

[0229] Figure 7X A device 700b (e.g., "second device") associated with a second user identity is shown displaying a user interface 7050 for a wallet application on a display 702b. The user interface 7050 includes a representation of a card 775 corresponding to an account. In some embodiments, the representation of the card 775 is displayed in the user interface 7050 after both the first user identity associated with the device 700a and the second user identity associated with the device 700b have accepted the second user identity as a co-owner of the account.

[0230] Figure 7YDevice 700a (e.g., "first device") associated with a first user identity (e.g., a primary account owner) is shown displaying a user interface 7016b for sharing accounts on display 702a. User interface 7016b includes a first sharing option 718a and a second sharing option 718b for respective family members. In some embodiments, first and second sharing options 718a and 718b are displayed in response to detecting input 719 (e.g., a tap gesture) corresponding to a location of an affordance 716c (e.g., an affordance of "Jane Parker") on display 702a, such as Figure 7C shown.

[0231] Figure 7Z Device 700a is shown displaying user interface 7052 on display 702a. User interface 7052 includes transaction limit field 748. In some embodiments, transaction limit field 748 is displayed in response to detecting input 721 (e.g., a tap gesture) corresponding to a location of second sharing option 718b on display 702a (e.g., an option for inviting a user to become a participant in an account without becoming a co-owner of the account), such as Figure 7Y In some embodiments, before inviting the corresponding family member to become a participant in the account, the device 700a receives a limit on the amount of money that the corresponding family member can spend using the account from the first user identity associated with the device 700a (e.g., the primary account owner). In some embodiments, the limit is per transaction (e.g., the maximum amount that can be spent on a single transaction). In some embodiments, the limit is for a predetermined time period (e.g., the maximum amount that can be spent in a week or a month).

[0232] Figure 7AA Device 700a is shown displaying user interface 7054 on display 702a. User interface 7054 includes a confirmation notification indicating that the corresponding family member has been invited to become a participant in the account without becoming a co-owner of the account. In some embodiments, in response to detecting input 723 (e.g., a tap gesture) corresponding to the position of next enable representation 758 on display 702a, a user interface 7054 is displayed. Figure 7AA The confirmation notice shown is Figure 7Z shown.

[0233] Figure 7AB Device 700a is shown displaying a user interface 7010 on display 702a for viewing account details and settings. Figure 7ABAs shown, after sending an invitation that enables the corresponding family member to become a participant in the account without becoming a co-owner of the account, the family member user interface object 728b is included in the user interface 7010. In some embodiments, the family member user interface object 728b includes an indication of the invitation status of the corresponding family member (e.g., "invite pending"). After the corresponding family member accepts the invitation, the invitation status changes to indicate the current status (e.g., "spending only", such as Figure 7AF shown).

[0234] Figure 7AC Device 700c (e.g., "third device") associated with a third user identity (e.g., "Jane Parker") is shown. Device 700c receives an indication that the third user identity has been invited to become a participant in the account. In response to receiving the indication, device 700c displays on display 702c a notification 732c that an invitation to become a participant in the account has been received. In some embodiments, notification 732c is displayed on lock screen interface 7030c when device 700c is in a locked state.

[0235] Figure 7AD Device 700c is shown displaying on display 702c a user interface 7056 for becoming a shared user of an account. In some embodiments, user interface 7056 is displayed after receiving an indication that a third user identity has been invited to become a participant of the account. In some embodiments, in response to detecting a selection of notification 732c (e.g., a tap gesture, a swipe gesture, a long press gesture on notification 732c), such as Figure 7AC , to display user interface 7056. In some embodiments, user interface 7056 is displayed in response to detecting a request to access a service associated with the account (e.g., in response to launching an application associated with the service, such as a wallet application). In contrast to becoming a co-owner of an account (as shown in reference Figure 7K to Figure 7P As described above), no additional information needs to be provided in order for the third user to accept the invitation and become a participant in the account.

[0236] User interface 7056 includes information about the type of account sharing provided (e.g., a participant account, in which a third user identity associated with device 700c can use the account without being a co-owner of the account). User interface 7056 also includes an acceptance indication 752 and a rejection indication 754. If acceptance indication 752 is selected (e.g., using a tap gesture), the third user identity associated with device 700c will become a participant in the account. In some embodiments, as opposed to becoming a co-owner of the account (e.g., referring to Figure 7K to Figure 7PAs described above, no additional information needs to be provided so that the third user identity accepts the invitation and becomes a participant of the account. If the rejection indication 754 is selected, the third user identity associated with device 700c will not become a participant of the account.

[0237] Figure 7AE A device 700a (e.g., "first device") associated with a first user identity (e.g., a primary account owner) is shown displaying a notification 756 on a display 702a that a third user identity has accepted an invitation to become a participant in an account. In some embodiments, notification 756 is displayed in response to receiving an indication that the third user identity has accepted the invitation to become a co-owner of the account. In some embodiments, notification 756 is displayed on a lock screen interface 7030a when the device 700a is in a locked state.

[0238] Figure 7AF Device 700a is shown displaying a user interface 7010 on display 702a for viewing account details and settings. Figure 7AF As shown, the status of the second user identity associated with the family member user interface object 728a is "co-owner", and the status of the third user identity associated with the family member user interface object 728b is "spending only". The "co-owner" status indicates that the second user identity is a co-owner of the account and has access to all account funds and account information. The "spending only" status indicates that the third user identity is a participant (not a co-owner) of the account and does not have access to all account funds or account information (e.g., does not have permission to view transactions performed by other user entities using the account).

[0239] Figure 7AG Device 700a is shown displaying a user interface 7060a on display 702a for viewing settings for co-owners of an account (e.g., settings for “Hugo Parker”). In some embodiments, user interface 7060a is displayed in response to detecting input 727 (e.g., a tap gesture) corresponding to a location of a family member user interface object 728a on display 702a (e.g., a user interface object corresponding to the second user identity “Hugo Parker”), such as Figure 7AF As shown. Figure 7AGAs shown, user interface 7060a includes option 762a for enabling notification for second user identity (e.g., for co-owner of account). In some embodiments, when (e.g., each time) account is used by second user identity, option 762a is enabled to provide notification. In some embodiments, when (e.g., each time) second user identity uses account to carry out transaction exceeding transaction amount threshold, option 762a is enabled to provide notification. In some embodiments, transaction amount threshold is the threshold amount of single transaction (e.g., if single transaction exceeds $10, exceeds $20, exceeds $50, exceeds $100 or exceeds another custom amount, notification is provided). In some embodiments, transaction amount threshold is the total amount of expenditure during a specific time period (e.g., one day, one week, one month), for example, if transaction causes the total amount of expenditure during a specific time period to exceed transaction amount threshold (e.g., $10, $20, $50, $100 or another custom amount), notification is provided. In some embodiments, transaction amount threshold is set or modified by selecting transaction threshold user interface object 764a.

[0240] Figure 7AH Device 700a is shown displaying a user interface 7062 for selecting a transaction amount threshold on display 702a. In some embodiments, user interface 7062 is displayed in response to detecting input 729 (e.g., a tap gesture) corresponding to a location of a transaction threshold user interface object 764a, such as Figure 7AG In some embodiments, Figure 7AH As shown, user interface 7062 includes multiple transaction amount threshold options. Each threshold option corresponds to a different transaction amount threshold (e.g., more than $10, more than $20, more than $50, more than $100, more than a custom amount). In some embodiments, after detecting user input corresponding to the selection of a transaction amount threshold, when (e.g., each time) a transaction exceeding the selected transaction amount threshold is completed (e.g., when a single transaction exceeds the threshold and / or when the total amount spent within a specific time period exceeds the threshold), a notification will be provided. In some embodiments, transactions that do not exceed the selected transaction amount threshold will not result in a notification being provided.

[0241] Figure 7AI Device 700a is shown displaying a user interface 7060b on display 702a for viewing settings for a participant of an account (e.g., settings for "Jane Parker"). In some embodiments, user interface 7060b is displayed in response to detecting input 731 (e.g., a tap gesture) corresponding to a location of a family member user interface object 728b (e.g., a user interface object corresponding to a third user identity "Jane Parker") on display 702a, such as Figure 7AF In some embodiments, Figure 7AI As shown, user interface 7060b includes an indication 768 of the transaction limit (e.g., $100) of the third user identity using the account. In some embodiments, if the third user identity attempts to complete the transaction of the amount exceeding the transaction limit, the transaction will not be completed. In some embodiments, user interface 7060b also includes an option 762b for enabling the notification for the third user identity (e.g., for the participant of the account). In some embodiments, when (e.g., each time) the account is used by the third user identity, option 762b is enabled to enable notification. In some embodiments, when (e.g., each time) the third user identity uses the account to carry out the transaction (e.g., exceeding $10, exceeding $20, exceeding $50, exceeding $100, exceeding a custom amount) exceeding the transaction amount threshold, option 762b is enabled to enable notification. In some embodiments, the transaction amount threshold is set or modified by selecting the transaction threshold user interface object 764b.

[0242] Figure 7AJ 700a is shown, which displays an additional portion of the user interface 7060b on the display 702a. In some embodiments, in response to detecting an input 733 (e.g., a swipe gesture) on the user interface 7060b, the additional portion of the user interface 7060b is displayed, such as Figure 7AI In some embodiments, Figure 7AJ As shown, an additional portion of user interface 7060b includes a lock option 770, which, when selected, prohibits a third user identity (e.g., a participant in the account) from using the account to conduct transactions while continuing to share the account with the third user identity. In some embodiments, after detecting a selection of lock option 770 (e.g., a tap gesture on lock option 770), the third user identity is prevented from using the account to complete transactions without removing the third user identity as a participant in the account (e.g., the third user identity can view previous transaction information, but cannot use the account to complete new transactions; the account is locked for the third user identity). In some embodiments, as Figure 7AJ As shown, the additional portion of user interface 7060b also includes a stop sharing option 772, which stops sharing the account with the third user identity when selected (e.g., removing the third user identity as a participant in the account). In some embodiments, after detecting the selection of the stop sharing option 772 (e.g., a tap gesture on the stop sharing option 772), the account is stopped from being shared with the third user identity (e.g., the third user identity cannot view previous transactions or conduct new transactions using the account; the third user identity is removed as a participant in the account).

[0243] Figure 7AK Device 700a is shown, which displays a confirmation enable representation 774 on display 702a overlaying user interface 7060b. In some embodiments, in response to detecting an input 735 (e.g., a tap gesture) corresponding to the stop sharing option 772 on display 702a, the confirmation enable representation 774 is displayed, such as Figure 7AJ In some embodiments, confirmation enable representation 774 is displayed to confirm that the account will stop being shared with the third user identity. In some embodiments, after detecting the selection of confirmation enable representation 774 (e.g., a tap gesture on confirmation enable representation 774), the account is stopped from being shared with the third user identity (e.g., the third user identity cannot view previous transactions or use the account for new transactions; the third user identity is removed as a participant in the account).

[0244] Figure 7AL Device 700c (e.g., “third device”) associated with a third user identity (e.g., “Jane Parker”) is shown displaying a notification 776a on display 702c that account sharing has been stopped. In some embodiments, notification 776a is displayed after receiving an indication that the owner of the account has requested to stop sharing the account with the third user identity (e.g., after input 737 (e.g., a tap gesture) corresponding to confirmation affordance 774 is detected by device 700a on display 702a, such as Figure 7AK In some embodiments, when the device 700c is in a locked state, the notification 776a is displayed on the lock screen interface 7030c. In some embodiments, the notification 776a indicates that the third user identity as a participant in the account has been removed and can no longer view previous transactions or complete new transactions using the account.

[0245] Figure 7AM Device 700c is shown displaying a user interface 7064 for a wallet application on display 702c. In some embodiments, user interface 7064 is displayed in response to detecting an input (e.g., a tap gesture, a swipe gesture, a long press gesture) on notification 776a, such as Figure 7AL In some embodiments, user interface 7064 includes notification 776b that account sharing has been stopped. In some embodiments, notification 776b is displayed after receiving an indication that the owner of the account has requested to stop sharing the account with the third user identity (e.g., after device 700a detects input 737 (e.g., a tap gesture) corresponding to confirmation enable indication 774 on display 702a, such as Figure 7AKIn some embodiments, notification 776b indicates that the third user identity as a participant in the account has been removed and can no longer view previous transactions or complete new transactions using the account. In some embodiments, notification 776b includes a removal enable indication 778 for removing a representation of the account (e.g., a representation of a card associated with the account) from the wallet application.

[0246] Figure 7AN Device 700a (e.g., "first device") associated with a first user identity (e.g., primary account owner) is shown displaying a notification 780a on display 702a indicating that a transaction has been completed. In some embodiments, notification 780a is displayed after a transaction has been completed that exceeds a transaction limit (e.g., a total spending limit within a set duration (e.g., a per-transaction limit, a daily limit, a weekly limit, and / or a monthly limit)). In some embodiments, notification 780a is displayed after a transaction has been completed that exceeds a transaction amount threshold (e.g., as set in user interface 766, such as Figure 7AH In some embodiments, notification 780a is displayed when a transaction is completed (as shown). In some embodiments, notification 780a is displayed on lock screen interface 7030a. In some embodiments, notification 780a includes a summary of the transaction (e.g., by the first user identity, by the second user identity, by the third user identity, by the participants and / or by the co-owner). In some embodiments, the summary of the transaction includes the merchant name, the transaction amount, and / or an indication of the user identity that completed the transaction. In some embodiments, in response to detecting user input (e.g., a tap gesture, a swipe gesture) on notification 780a, an application associated with the account (e.g., a wallet application) is displayed.

[0247] Figure 7AO Device 700a is shown displaying notification 780b including details of a transaction on display 702a. In some embodiments, notification 780b is displayed in response to detecting input 739 (e.g., a long press gesture) corresponding to the location of notification 780a on display 702a, such as Figure 7AN As shown. In some embodiments, notification 780b is displayed on the lock screen interface 7030a. In some embodiments, the details of the transaction include the merchant name, the transaction amount, the transaction time, an indication of the identity of the user who completed the transaction, merchant location information (e.g., the merchant's address and / or the merchant's address on a map), and / or an indication of the total amount of expenditure within a predetermined time (e.g., within a day, within a week, within a month). In some embodiments, in response to detecting user input (e.g., a tap gesture, a swipe gesture, a long press gesture) on notification 780b, an application associated with the account (e.g., a wallet application) is displayed.

[0248] Figure 7AP Device 700a is shown, which displays a user interface 7004 for viewing detailed information and settings of an account on display 702a. In some embodiments, user interface 7004 includes multiple transactions 782a-782c (e.g., a list) of an account. In some embodiments, multiple transactions 782a-782c (e.g., a list) include transactions completed by all user identities associated with the account (e.g., a first user identity, a second user identity, a third user identity, a participant and / or a co-owner). In some embodiments, each transaction in multiple transactions 782a-782c (e.g., a list) includes an indication of the user identity (e.g., the name of a family member) that completed the transaction (e.g., based on a transaction initiated by the corresponding user identity). In some embodiments, the indication of the user identity (e.g., the name of a family member) is omitted from the transaction completed by the first user identity associated with device 700a, for example, the name of the primary account owner associated with device 700a is not shown.

[0249] In some embodiments, such as Figure 7AP As shown, user interface 7004 also includes active user interface object 796a and / or search icon 793.

[0250] Figure 7AQ Device 700a is shown displaying a user interface 7066 for viewing a payment transaction on display 702a. In some embodiments, user interface 7066 is displayed in response to detecting input 741 (e.g., a tap gesture) corresponding to transaction 782c on display 702a, such as Figure 7AP As shown. In some embodiments, the user interface 7066 includes multiple payment transactions 786a-786c (e.g., a list) for the account. In some embodiments, the multiple payment transactions 786a-786c (e.g., a list) include transactions completed by all user identities associated with the account (e.g., a first user identity, a second user identity, a third user identity, a participant, and / or a co-owner). In some embodiments, each transaction in the multiple payment transactions 786a-786c (e.g., a list) includes an indication of the user identity (e.g., the name of a family member) that completed the transaction (e.g., based on a transaction initiated by the corresponding user identity). In some embodiments, the indication of the user identity (e.g., the name of a family member) is omitted from the payment transaction completed by the first user identity associated with the device 700a, for example, the name of the primary account owner associated with the device 700a is not shown.

[0251] Figure 7ARDevice 700a is shown displaying a user interface 7068 on display 702a for viewing transactions associated with a corresponding merchant. In some embodiments, user interface 7068 is displayed in response to detecting input 743 (e.g., a tap gesture) corresponding to transaction 782b on display 702a, such as Figure 7AP In some embodiments, the user interface 7068 includes a plurality of transactions 790a-790e (e.g., a list) associated with a corresponding merchant (e.g., a "package store"). In some embodiments, the corresponding merchant corresponds to a completed transaction 782b (e.g., Figure 7AP In some embodiments, the plurality of transactions 790a-790e (e.g., a list) associated with the respective merchant includes transactions completed by all user identities associated with the account (e.g., a first user identity, a second user identity, a third user identity, participants, and / or co-owners). In some embodiments, each transaction in the plurality of transactions 790a-790e (e.g., a list) associated with the respective merchant includes an indication of the user identity (e.g., the name of a family member) that completed the transaction (e.g., based on a transaction already initiated by the respective user identity). In some embodiments, the indication of the user identity (e.g., the name of a family member) is omitted from the transactions associated with the respective merchant completed by the first user identity associated with the device 700a, for example, the name of the primary account owner associated with the device 700a is not shown.

[0252] Figure 7AS Device 700a is shown displaying a user interface 7070 including detailed information 794 of a transaction on display 702a. In some embodiments, user interface 7070 is displayed in response to detecting input 745 (e.g., a tap gesture) corresponding to a location of transaction 790e on display 702a, such as Figure 7AR In some embodiments, the details 794 of the transaction include the merchant name, the transaction amount, the cash back amount (e.g., a percentage of the transaction amount that will be returned to a cash account), an indication of the user identity that completed the transaction, and / or an indication of the card number used for the transaction. In some embodiments, if the transaction is completed by the first user identity associated with the device 700a, the indication of the user identity (e.g., the name of a family member) is omitted, for example, the name of the primary account owner associated with the device 700a is not shown.

[0253] Figure 7ATDevice 700a is shown displaying an active interface 7072 for all user identities associated with an account (e.g., a first user identity, a second user identity, a third user identity, participants, and / or co-owners) on display 702a. In some embodiments, active interface 7072 is displayed in response to detecting input 747 (e.g., a tap gesture) corresponding to a location of active user interface object 796a on display 702a, such as Figure 7AP In some embodiments, the activity interface 7072 includes an activity chart 798 indicating the amount of money spent per day by all user identities (e.g., first user identity, second user identity, third user identity, participants, and / or co-owners) associated with the account. In some embodiments, the activity interface 7072 includes user identity user interface objects 799a-799c for multiple user identities associated with the account. In some embodiments, each of the user identity user interface objects 799a-799c includes an indication of the amount (e.g., daily expenditures, weekly expenditures, monthly expenditures) spent by the corresponding user identity within a predetermined time period.

[0254] Figure 7AU Device 700a is shown displaying an active interface 7074 for a third user identity associated with an account on display 702a. In some embodiments, active interface 7074 is displayed in response to detecting input 749 (e.g., a tap gesture) corresponding to a location of a user identity user interface object 799b (e.g., corresponding to the third user identity "Jane Parker") on display 702a, such as Figure 7AT In some embodiments, the activity interface 7074 includes an activity chart 795 indicating the amount of daily expenditures of the third user identity. In some embodiments, the activity chart 795 indicates the amount of daily expenditures of the third user identity by highlighting (e.g., using a different color) the amount of expenditures of the third user identity while not highlighting the amount of expenditures of other user identities (e.g., the first user identity, the second user identity, the participants, and / or the co-owners). In some embodiments, the activity chart 795 indicates the amount of daily expenditures of the third user identity by showing only the amount of expenditures of the third user identity and omitting the amount of expenditures of other user identities (e.g., the first user identity, the second user identity, the participants, and / or the co-owners).

[0255] Figure 7AV Device 700a is shown, which displays a search interface 7076 on display 702a. In some embodiments, search interface 7076 is displayed in response to detecting input 751 (e.g., a tap gesture) corresponding to the location of search icon 793, such as Figure 7APAs shown. In some embodiments, the search interface 7076 includes family member user interface objects 789a-789c. Although three family member user interface objects are shown in 7AV, the number of family member user interface objects can vary based on the number of family members who have established a relationship with the user of device 700a. In some embodiments, the family member user interface objects included in the search interface 7076 include all family members who have established a relationship with the user of device 700a. In some embodiments, the family member user interface objects included in the search interface 7076 include all family members who have shared an account with it (e.g., all participants and owners of the account).

[0256] Figure 7AW Device 700a is shown displaying a search interface 7078 on display 702a. In some embodiments, search interface 7078 is displayed in response to detecting input 753 (e.g., a tap gesture) corresponding to a location of a family member user interface object 789c (e.g., corresponding to a third user identity "Jane Parker"), such as Figure 7AV In some embodiments, selecting a family member user interface object, such as Figure 7AV As shown, the name of the selected family member is entered into the search field of the search interface 7078, such as Figure 7AW In some embodiments, a family member user interface object is selected, such as Figure 7AV As shown, multiple transactions (e.g., lists) associated with the selected family member are displayed in the search interface 7078, such as Figure 7AW shown.

[0257] Figure 7AX A device 700c (e.g., "third device") associated with a third user identity (e.g., "Jane Parker") is shown displaying a user interface 7080a on a display 702c for viewing details and settings of an account. In some embodiments, the user interface 7080a includes a plurality of transactions (e.g., a list) associated with the third user identity, but does not include transactions associated with other user identities (e.g., the first user identity, the second user identity, other owners of the account, other participants in the account). In some embodiments, the user interface 7080a also includes a spending summary 785a. In some embodiments, the spending summary 785a includes an indication of the amount of money that the third user identity has spent over a predetermined time period (e.g., a day, a week, a month).

[0258] Figure 7AYDevice 700c is shown displaying a user interface 7082a on display 702c for viewing account details of a third user identity. In some embodiments, user interface 7082a is displayed in response to detecting input 755 (e.g., a tap gesture) corresponding to a location of expense summary 785a on display 702c, such as Figure 7AX In some embodiments, user interface 7082a includes an amount of money that the third user identity has spent within a predetermined time period (e.g., one day, one week, one month) and / or an indication of a transaction limit 781 for the third user identity (e.g., a per-transaction limit; a limit on the total amount that can be spent using an account within a predetermined time period (e.g., one day, one week, one month)).

[0259] Figure 7AZ A device 700c (e.g., "third device") associated with a third user identity (e.g., "Jane Parker") is shown, which displays a user interface 7080b on a display 702c for viewing the details and settings of an account. In some embodiments, the user interface 7080b includes multiple transactions (e.g., a list) associated with the third user identity, but does not include transactions associated with other user identities (e.g., the first user identity, the second user identity, other owners of the account, other participants in the account). In some embodiments, the user interface 7080b also includes a spending summary 785b. In some embodiments, the spending summary 785b includes an indication of the amount of money that the third user identity has spent within a predetermined time period (e.g., one day, one week, one month) and / or the available credit amount of the account. In some embodiments, when the third user identity is over 18 years old, the available credit amount of the account is included in the spending summary 785b. In some embodiments, when an option allowing the account's available credit amount to be displayed to a third user identity has been enabled (e.g., when the owner of the account (e.g., the first user identity and / or the second user identity) causes the account's available credit amount to be displayed to a third user identity), the account's available credit amount is included in the spending summary 785b.

[0260] Figure 7BA Device 700c is shown displaying a user interface 7082b on display 702c for viewing account details of a third user identity. In some embodiments, user interface 7082b is displayed in response to detecting input 757 (e.g., a tap gesture) corresponding to a location of expense summary 785b on display 702c, such as Figure 7AZAs shown. In some embodiments, the user interface 7082b includes an indication of the amount that the third user identity has spent within a predetermined time period (e.g., one day, one week, one month), the transaction limit 781 of the third user identity (e.g., a per-transaction limit; a limit on the total amount that can be spent using the account within a predetermined time period (e.g., one day, one week, one month)), and / or the balance information 779 of the account. In some embodiments, the balance information 779 indicates the credit limit of the account, the total balance of the account (for all users), and / or the available remaining credit of the account. In some embodiments, when the third user identity is over 18 years old, the balance information 779 is included in the user interface 7082b. In some embodiments, when an option to allow the balance information 779 to be displayed to the third user identity has been enabled (e.g., when the owner of the account (e.g., the first user identity and / or the second user identity) causes the balance information 779 to be displayed to the third user identity), the balance information 779 is included in the user interface 7082b.

[0261] Figure 8 800 is a flow chart illustrating a method for sharing an account with another user identity using a computer system according to some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600a, 700a) associated with a first user identity (e.g., a primary account owner) that communicates with a display generation component (e.g., 602a, 702a, a display) and one or more input devices (e.g., a touch-sensitive surface). Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0262] As described below, method 800 provides an intuitive way to share an account with another user identity. The method reduces the cognitive burden on the user sharing the account, thereby creating a more efficient human-computer interface. The method also reduces the need for resources (e.g., computer resources, such as memory) by enabling sharing of resources between multiple users. For battery-powered computing devices, enabling users to share accounts more quickly and more efficiently saves power and increases the time interval between battery charges.

[0263] In method 800, a computer system (e.g., 600a, 700a) (e.g., a smart device, such as a smart phone or smart watch; a mobile device) displays (802) via a display generation component (e.g., 602a, 702a) a user interface (e.g., such as a user interface 802) for sharing an account (e.g., a data storage account, a bank account, and / or a credit account) associated with a first user identity with a second user identity (e.g., a family member and / or another user who has established a relationship with a user of the computer system). Fig.6D 6014 shown; Fig.7D7014 shown). The user interface includes a first sharing option (e.g., 618a, 718a) and a second sharing option (e.g., 618b, 718b).

[0264] The computer system detects (804) via one or more input devices one or more inputs (e.g., 609, 611, 709, 711, 713, 721) corresponding to a request to share an account (e.g., selection of a share option and a "send invite" affordance on a user interface).

[0265] In response to detecting at (806) one or more inputs corresponding to a request to share an account and determining at (808) that the one or more inputs include a selection of a first sharing option (e.g., 618a, 718a), the computer system sends a request to invite the second user identity to become a co-owner of the account (e.g., the second user will have access to all account data storage and data usage information; and / or the second user will have access to all account resources and transaction information). In some embodiments, after selecting the first sharing option, a user interface for confirming the first user identity's income (e.g., such as Fig. 7E ) is displayed before sending a request to invite a second user identity to become a co-owner of the account.

[0266] In some embodiments, after sending a request to invite the second user identity to become a co-owner of the account, the computer system associated with the second user identity (e.g., 600b, 700b) displays a notification (e.g., such as a notification that an invitation to become a co-owner of the account has been received) via a display generating component (e.g., 602b, 702b). Fig. 6F 624 as shown; Fig.7I In some embodiments, after sending a request to invite the second user identity to become a co-owner of the account, if the second user identity has never been (and / or is not currently) associated with the service that provides accounts (e.g., the second user identity was not previously the owner of any account using the service), the computer system associated with the second user identity (e.g., 700b) displays information about the features and responsibilities of becoming a co-owner of the account (e.g., such as information displayed on the display generation component (e.g., 702b)). Figure 7J In some embodiments, after sending a request to invite a second user identity to become a co-owner of an account, a computer system (e.g., 700b) associated with the second user identity displays, via a display generation component (e.g., 702b), a series of information input fields (e.g., as shown) for verifying the identity of the second user identity and / or determining whether the second user identity is eligible to become a co-owner of the account. Figures 7K to 7N), for example, fields for name, date of birth, phone number, social security number, nationality, address, and / or income. In some embodiments, after sending a request to invite a second user identity to become a co-owner of an account, a computer system (e.g., 600 b, 700 b) associated with the second user identity displays detailed information about the account (e.g., as shown in FIG. 602 b, 702 b) via a display generation component (e.g., 602 b, 702 b). Figure 6G The user interface 6026 shown; Figure 7Q User interface 7042a shown; Figure 7U In some embodiments, detailed information about the account includes a credit line, an account balance, a percentage, and / or terms and conditions of the account. In some embodiments, the percentage and / or credit line is based on the combined credit value of the first user identity and the second user identity.

[0267] In response to detecting one or more inputs corresponding to a request to share an account at (806) and determining, based on (810), that the one or more inputs include a selection of a second sharing option (e.g., 618b, 718b), the computer system (e.g., 600a, 700a) sends a request to invite a second user identity to become a participant in the account without becoming a co-owner of the account (e.g., the second user will have access to a limited amount of data storage and will only see their data usage; and / or the second user will have access to a limited amount of account resources and will only see their own transactions).

[0268] Displaying a sharing option that invites another user identity to become a co-owner of the account or a participant in the account when selected provides enhanced control over how the account is used by the other user identity (e.g., having access to all account information and funds, or having limited access to account information and funds). Providing enhanced control improves the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0269] In some embodiments, after accepting the invitation to become a participant of the account, the computer system (e.g., 700c) associated with the second user identity displays an offer of a refund (e.g., cash back on certain types of transactions) via the display generation component (e.g., 702c). In some embodiments, the computer system (e.g., 700a) displays an indication confirming that a request to invite the second user identity to become a participant or co-owner has been sent (e.g., an indication that the invitation is currently pending or has been accepted) (e.g., as shown in FIG. 1 ). Figure 7G726 as shown; Figure 7H 728a shown; Figure 7AB 728b) shown.

[0270] In some embodiments, before displaying the first sharing option and the second sharing option, the computer system (e.g., 600a, 700a) displays, via a display generation component (e.g., 602a, 702a), one or more identity user interface objects (e.g., such as user interfaces) corresponding to one or more user identities that can be used to share an account with (e.g., family members and / or other users who have established relationships with users of the computer system). Figure 6C 616a-616c shown; Figure 7C 716a-716c shown), wherein the one or more identity user interface objects include an identity user interface object corresponding to the second user identity (and not corresponding to the first user identity). In some embodiments, while displaying the one or more identity user interface objects, the computer system (e.g., 600a, 700a) detects user input (e.g., 607, 707, 719) involving a corresponding identity user interface object of the one or more identity user objects via one or more input devices. In some embodiments, a user interface (e.g., such as a user interface for sharing an account (e.g., a data storage account, a bank account, and / or a credit account) with a second user identity is provided. Fig.6D as shown; Fig.7D as shown; Figure 7Y In some embodiments, one or more identity user interface objects (e.g., 616a-616c; 716a-716c) include a second identity user interface object corresponding to a third user identity. In some embodiments, a user interface for sharing an account with a third user identity (not the second user identity) (e.g., as shown in FIG. 1 ) is displayed in response to receiving user input related to the corresponding identity user interface object and based on determining that the corresponding identity user interface object corresponds to the second user identity. In some embodiments, one or more identity user interface objects (e.g., 616a-616c; 716a-716c) include a second identity user interface object corresponding to a third user identity. Figure 7Y ) is displayed in response to receiving user input (e.g., 719) related to a second identity user interface object. Displaying identity user interface objects corresponding to one or more user identities with which an account can be shared provides enhanced control over with whom the account is shared. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, being able to share the resources of an account between two user identities makes the computer system more efficient. For example, two user identities can share the same memory space, thereby reducing the need for the computer system to manage two separate memory spaces.

[0271] In some embodiments, based on determining that the one or more inputs (e.g., 721) include a selection of a second sharing option (e.g., 718b), the computer system (e.g., 700a) displays, via the display generation component (e.g., 702a), an option to configure a transaction limit for the second user identity (e.g., as Figure 7Z In some embodiments, a series of one or more inputs corresponding to the input of the amount of the transaction limit for the second user identity are detected. The option of displaying the transaction limit for configuring another user identity provides enhanced control over how much the second user identity can spend using the account. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, transaction limits enable the computer system to limit over-consumption of computer resources. For example, a user may be limited in how much memory they can consume per file and / or over a period of time.

[0272] In some embodiments, after sending the request to invite the second user identity to become a co-owner of the account, the computer system (e.g., 600a, 700a) receives an indication that the second user identity has accepted the invitation to become a co-owner of the account. In some embodiments, after receiving the indication (e.g., in response to detecting activation of a displayed notification (e.g., 746) corresponding to the indication), the computer system (e.g., 700a) displays a confirmation user interface (e.g., such as 746) via the display generation component (e.g., 702a). Figure 7W40 ), including: an accept option (e.g., 738a) that accepts the second user identity as a co-owner of the account when selected, and a reject option (e.g., 740a) that rejects the second user identity as a co-owner of the account when selected. In some embodiments, an input corresponding to the selection of the accept option is detected (e.g., a tap gesture), and in response to detecting the input, a process is initiated to make the second user identity a co-owner of the account. In some embodiments, an input corresponding to the selection of the reject option is detected (e.g., a tap gesture), and in response to detecting the input, the second user identity is not made a co-owner of the account. Displaying the option to accept or reject another user identity as a co-owner of the account provides enhanced control over whether to allow other user identities to become co-owners (e.g., after reviewing new terms, credit limits, and / or percentages of the jointly owned account). Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, providing the user with the option to continue or deny joint ownership enables the computer system to receive user confirmation before providing two accounts with joint access to the same resources, thereby making the accounts more secure. This is particularly beneficial when the resources include private information, such as private files or private spending details.

[0273] In some embodiments, when sending a request to invite a second user identity to become a participant in the account without becoming a co-owner of the account (e.g., Figure 7AA , after receiving the indication, the computer system (e.g., 700a) receives an indication that the second user identity has accepted the invitation to become a participant of the account. In some embodiments, after receiving the indication, the computer system (e.g., 700a) displays a notification (e.g., 756) that the account is shared with the second user identity via a display generation component (e.g., 702a). The notification that the account is shared with another user identity provides feedback on the state of the account. For example, a user of the computer system knows that another user has access rights to the resources of the account. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0274] In some embodiments, a co-owner of an account has access to transaction and balance information for all participants and owners of the account (e.g., Figure 7AP to Figure 7ARIn some embodiments, a co-owner of an account has access to a payment interface (e.g., by selecting a payment affordance) to make payments to the account. Providing co-owners of an account access to transaction and balance information for all participants and owners of the account provides enhanced control over the co-owner's account and improved feedback about the status of the account. Providing enhanced control and improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0275] In some embodiments, a respective participant of an account who is not a co-owner of the account has access to the respective participant's transaction information but does not have access to the transaction information (and, in some embodiments, balance information) of other participants or owners (e.g., sole owner, multiple co-owners) of the account (e.g., Figure 7AX and Figure 7AY As shown), for example, when a user becomes a participant of an account, the user can access his own past transactions, but not the transactions of other participants or owners. In some embodiments, participants of an account who are not co-owners of an account have access to an installment payment option that allows the participant to pay for transactions using installment payments. In some embodiments, co-owners of an account have access to information about installment payments. Providing access to the transaction information of the corresponding participant to the corresponding participant without providing access to the transaction information of other participants or owners of the account provides enhanced control of the information available to the corresponding participant. In addition, limited access further implements the security of the account, especially when the content / resources of the account include private information, such as private files or private spending details. Providing enhanced control enhances the operability of the device and makes the user-device interface safer and more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0276] In some embodiments, a respective participant of an account who is not a co-owner of the account has access to the respective participant's transaction information and available credit information of the account but does not have access to transaction information of other participants or owners (e.g., sole owner, multiple co-owners) of the account (e.g., Figure 7AZ and Figure 7BA , for example, when a user becomes a participant of an account (and in some embodiments, is over 18 years of age), the user can access his or her own past transactions and view the available credit of the account, but cannot view the transactions of other participants or owners). In some embodiments, the computer system (e.g., 700a) displays user-selectable options (e.g., switches) to enable / disable available credit information (e.g., balance of the account, remaining resources of the account) provided to participants of the account. While displaying the user-selectable options, the computer system (e.g., 700a) receives input related to the user-selectable options. Based on determining that the input related to the user-selectable options corresponds to a request to disable available credit information provided to participants of the account, the computer system (e.g., 700a) causes the available credit information to be not provided to participants of the account. Based on determining that the input related to the user-selectable options corresponds to a request to provide available credit information to participants of the account, the computer system (e.g., 700a) causes the available credit information to be provided to participants of the account. Providing access to the transaction information of the corresponding participant and the available credit information of the account to the corresponding participant without providing access to the transaction information of other participants or owners of the account provides enhanced control over the information available to the corresponding participant. Providing enhanced controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0277] In some embodiments, a computer system (e.g., 700a) simultaneously displays, via a display generation component (e.g., 702a), spending information (e.g., daily spending, weekly spending, monthly spending) of multiple user identities associated with an account (e.g., participants and owners of the account) within a predetermined time period (e.g., as shown in FIG. Figure 7AP , Figure 7AR and Figure 7ATAs shown). In some embodiments, simultaneously displaying spending information for multiple user identities associated with an account within a predetermined time period includes displaying a first transaction (and optionally a second transaction) initiated by a first user identity (using the account) and a third transaction (and optionally a fourth transaction) initiated by a second user identity (using the account). In some embodiments, based on displaying the first transaction, the second transaction, the third transaction, and the fourth transaction within the selected predetermined time period. In some embodiments, the computer system receives user input selecting a second predetermined time period and simultaneously displays multiple transactions of the account (initiated by the first and second user identities), without displaying transactions of the account that were not initiated within the second predetermined time period. In some embodiments, a selection of a corresponding user identity (e.g., 749) is detected (e.g., a tap input on a corresponding identity user interface object), and in response to detecting the selection, spending information for the corresponding user identity within the predetermined time period is displayed, without displaying spending information for other user identities associated with the account (e.g., as Figure 7AU In some embodiments, a search interface is displayed (e.g., Figure 7AV ), where the search interface includes simultaneously displaying spending information for multiple user identities associated with an account (e.g., participants and owners of the account). Simultaneously displaying spending information for multiple user identities associated with an account provides improved visual feedback about the status of the account (e.g., by indicating the amount spent by each user identity). Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0278] In some embodiments, a computer system (e.g., 700a) displays a setup interface (e.g., such as Figure 7AG 7060a shown; Figure 7AI7060b shown), the settings interface includes an option (e.g., 762a, 762b) that, when enabled, enables notifications to be provided when the account is used (e.g., by the first user identity, by the second identity, by the participant, and / or by the co-owner) (e.g., each time). In some embodiments, when the option is disabled, the computer system detects user input to enable the option (e.g., a tap or swipe gesture on the option), and in response to detecting the user input to enable the option, the computer system enables the display of notifications via the display generation component when the account is used (e.g., by the first user identity, by the second user identity, by the participant, and / or by the co-owner) (e.g., each time). Displaying the option to enable the display of notifications when the account is used provides enhanced control over what information is provided to the account owner. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. Additionally, enabling notifications when an account is used reduces or eliminates the need for a user to navigate various user interfaces and provide user input to view transactions, thereby reducing the number of inputs required to determine a transaction for use. Reducing the number of inputs required to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0279] In some embodiments, a computer system (e.g., 700a) displays a setup interface (e.g., such as Figure 7AH 7062 shown), the settings interface includes an option for selecting a transaction amount threshold (e.g., over $10, over $50, over $100, over a custom amount, no threshold (e.g., all transactions cause notification)), where transaction amounts exceeding the transaction amount threshold will cause a notification to be provided. In some embodiments, the computer system detects user input corresponding to the selection of the corresponding transaction amount threshold. In some embodiments, after detecting user input corresponding to the selection of the corresponding transaction amount threshold and based on determining that a transaction exceeding the transaction amount threshold has been completed, the computer system provides a notification corresponding to the transaction (e.g., the amount of the transaction and the merchant at which the transaction occurred) (e.g., as shown in FIG. 7063). Figure 7AN780a shown). In some embodiments, after detecting a user input corresponding to the selection of the corresponding transaction amount threshold and based on determining that the transaction that has not exceeded the transaction amount threshold has been completed, the computer system abandons providing a notification corresponding to the transaction. Displaying the option for selecting the transaction amount threshold provides enhanced control over what information is provided to the account owner. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, enabling the receipt of notifications when the account is used in a transaction that exceeds the threshold reduces or eliminates the need for the user to navigate various user interfaces and provide user input to view the transaction, thereby reducing the number of inputs required to determine the use of the transaction. Reducing the number of inputs required to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0280] In some embodiments, a computer system (e.g., 700a) displays a notification (e.g., such as a notification message) including a summary of the transaction via a display generation component (e.g., 702a). Figure 7AN In some embodiments, the computer system detects a request to view details of the transaction (e.g., 739) via one or more input devices (e.g., long pressing the notification), and in response to detecting the request to view details of the transaction, the computer system displays the details of the transaction (e.g., as shown in 780a). Figure 7AO 780b shown) (e.g., merchant information, card information, and / or total expenses for a month). In some embodiments, a tap gesture on the notification is detected (e.g., Figure 7AN 780a shown), and in response to detecting the tap gesture, displaying an application associated with the account (e.g., a wallet application). Displaying a notification including a summary of the transaction and displaying details of the transaction provides improved visual feedback about the status of the account (e.g., by indicating that a transaction with the account has occurred). Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0281] In some embodiments, a computer system (e.g., 700a) displays, via a display generating component (e.g., 702a), a notification indicating that a transaction limit for an account has been exceeded (e.g., a per-transaction spending limit and / or a total spending limit for a set duration (e.g., a daily limit, a weekly limit, and / or a monthly limit)). Displaying a notification indicating that a transaction limit for an account has been exceeded provides improved visual feedback about the status of the account (e.g., by indicating that a transaction with the account has occurred). Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0282] In some embodiments, a computer system (e.g., 700a) displays a setup interface (e.g., such as Figure 7AI and Figure 7AJ 7060b shown), the settings interface includes an option (e.g., lock option 770) that, when selected, prohibits the corresponding participant of the account from using the account for transactions while continuing to share the account with the corresponding participant. In some embodiments, the computer system detects a user input corresponding to the selection of the option (e.g., a tap gesture on the option), and in response to detecting the user input corresponding to the selection of the option, the computer system prohibits the corresponding participant of the account from using the account for transactions while continuing to share the account with the corresponding participant (e.g., the corresponding participant can view previous transactions, but cannot use the account for new transactions). Displaying an option for prohibiting the corresponding participant of the account from using the account for transactions while continuing to share the account with the corresponding participant provides enhanced control over how the corresponding participant uses the account. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. Additionally, prohibiting a corresponding participant of an account from using an account without removing the participant as a participant in the account enables the computer system to secure the account (by not allowing transactions) while continuing to provide the participant with reduced access, such as viewing the participant's past transactions, thereby making the account more secure.

[0283] In some embodiments, a computer system (e.g., 700a) displays a setup interface (e.g., such as Figure 7AI and Figure 7AJ7060b shown), the settings interface includes an option (e.g., stop sharing option 772) that stops sharing the account with the corresponding participant when selected. In some embodiments, the computer system detects a user input (e.g., 735) corresponding to the selection of the option (e.g., a tap gesture on the option), and in response to detecting the user input corresponding to the selection of the option, the computer system stops sharing the account with the corresponding participant (e.g., the corresponding participant cannot view previous transactions or use the account for new transactions and / or is no longer a participant in the account). Displaying the option to stop sharing the account with the corresponding participant provides enhanced control over how the corresponding participant uses the account. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, stopping sharing the account with the corresponding participant enables the computer system to make the account secure (e.g., by not allowing the participant and / or other people's transactions that the participant wants to access), thereby making the account more secure.

[0284] In some embodiments, a computer system (e.g., 700a) displays a setup interface (e.g., such as Figure 7AG 7060a shown), the settings interface includes an option to stop sharing the account with the corresponding co-owner when selected. In some embodiments, the computer system detects user input corresponding to the selection of the option (e.g., a tap gesture on the option), and in response to detecting the user input corresponding to the selection of the option, the computer system stops sharing the account with the corresponding co-owner (e.g., the corresponding co-owner cannot view previous transactions or use the account for new transactions and / or is no longer a co-owner of the account). In some embodiments, stopping sharing the account with the co-owner closes the accounts of all users. Displaying the option to stop sharing the account with the corresponding co-owner provides enhanced control over how the corresponding co-owner uses the account. Providing enhanced control enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, stopping sharing the account with the corresponding co-owner enables the computer system to make the account secure (e.g., by not allowing the co-owner and / or other people's transactions that the co-owner wants to access), thereby making the account more secure.

[0285] In some embodiments, a computer system (e.g., 700a) displays, via a display generation component (e.g., 702a), one or more affordances corresponding to one or more user identities with which an account is shared (e.g., Figure 7AT 799a-799c shown). In some embodiments, the computer system detects, via one or more input devices, an input (e.g., 749) corresponding to a selection of a corresponding enable representation (e.g., 799b) of one or more enable representations, the corresponding enable representation corresponding to a corresponding user identity. In some embodiments, in response to detecting an input corresponding to a selection of a corresponding enable representation, the computer system displays transaction information associated with the corresponding user identity (e.g., transaction information of transactions initiated by it) (e.g., a list of transactions within a set time period (e.g., one day, one week, one month)) via a display generation component, for example, Figure 7AU As shown. Displaying transaction information associated with the corresponding user identity provides improved visual feedback about the account status (e.g., by indicating what transactions the corresponding user identity has performed). Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0286] In some embodiments, a computer system (e.g., 700a) displays a plurality of transactions (e.g., a list) of an account via a display generation component (e.g., 702a) (e.g., as shown in FIG. Figure 7AP to Figure 7AR In some embodiments, a first transaction in a plurality of transactions includes an indication of a corresponding user identity (e.g., a name of a family member) corresponding to the first transaction (e.g., based on a first transaction that has been initiated by the corresponding user identity), and a second transaction in a plurality of transactions includes an indication of a corresponding user identity (different from a user identity corresponding to the first transaction) corresponding to the second transaction (e.g., based on the second transaction that has been initiated by the corresponding user identity). In some embodiments, based on a third transaction that has been initiated by the first user identity (e.g., an owner of a computer system and / or an account), a third transaction in a plurality of transactions abandons an indication of the corresponding user identity corresponding to the third transaction. Displaying an indication of the corresponding user identity corresponding to each transaction provides improved visual feedback about each transaction (e.g., by indicating who performed the transaction). Providing improved visual feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, this can also reduce power usage and extend the battery life of the device.

[0287] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

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

[0289] As described above, one aspect of the present technology is to collect and use data from various sources to share an account with another user identity and view / configure a shared account. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.

[0290] The present disclosure recognizes that the use of such personal information data in the present invention technology can be used to benefit users. For example, personal information data can be used to view account information and available user identities with which accounts can be shared. In addition, the present disclosure also anticipates other uses of personal information data that benefit users.

[0291] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0292] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to a shared account, the technology of the present invention may be configured to allow a user to choose to "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 notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.

[0293] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0294] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, an account may be shared with another user identity based on non-personal information data or an absolute minimum of personal information (such as content requested by a device associated with the user, other non-personal information available to a service provider of the account, or publicly available information).

Claims

1. A method comprising: At a computer system associated with a first user identity in communication with a display generating component and one or more input devices: receiving an invitation to become a participant of an account without becoming a co-owner of the account, wherein a respective participant of the account who is not a co-owner of the account has access rights to view expenditure transactions completed by the respective participant using funds from the account without having access rights to view expenditure transactions completed by other participants or owners of the account; detecting, via the one or more input devices, one or more inputs corresponding to accepting the invitation to become a participant of the account; and After detecting the one or more inputs corresponding to acceptance of the invitation to become a participant in the account, an account details user interface is displayed via the display generating component, the account details user interface simultaneously including multiple expenditure transactions completed by the first user identity using funds from the account but not including expenditure transactions completed by other participants or owners of the account.

2. The method according to claim 1, wherein: The invitation to become a participant in the account without becoming a co-owner of the account is provided by a device associated with an owner of the account.

3. A method according to claim 1 or 2, wherein the account is configured with a transaction limit for the first user identity.

4. The method according to any one of claims 1 to 3, wherein the account is configured with a transaction amount threshold for the first user identity, and wherein the method further comprises: Upon detecting the one or more inputs corresponding to accepting the invitation to become a participant of the account: Based on a determination that a transaction completed by the first user identity exceeds the transaction amount threshold, providing a notification corresponding to the transaction to a device associated with an owner of the account; as well as Based on a determination that the completed transaction has not exceeded the transaction amount threshold, providing a notification corresponding to the transaction to the device associated with the owner of the account is forgone.

5. The method according to claim 1 or 2, further comprising: After detecting the one or more inputs corresponding to acceptance of the invitation to become a participant of the account, providing an indication to a device associated with an owner of the account that the first user identity has accepted the invitation to become a co-owner of the account.

6. The method according to claim 1 or 2, further comprising: After detecting the one or more inputs corresponding to accepting the invitation to become a participant in the account, a notification is provided to a device associated with an owner of the account when the account is used by the first user identity to complete a transaction.

7. The method according to claim 1 or 2 further comprises:. After detecting the one or more inputs corresponding to accepting the invitation to become a participant of the account, access to available credit information for the account is provided.

8. The method according to claim 1 or 2, further comprising: receiving, after detecting the one or more inputs corresponding to acceptance of the invitation to become a participant in the account, a notification that sharing of the account with the first user identity has ceased; and In response to receiving the notification that sharing of the account with the first user identity has ceased, displaying, via the display generating component, an affordance representation for removing a representation of the account from the computer system.

9. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the computer system being associated with a first user identity in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for executing the method of any one of claims 1-8.

10. A computer system associated with a first user identity configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 8.

11. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: An apparatus for performing the method according to any one of claims 1 to 8.

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

13. A method comprising: At a computer system associated with a first user identity in communication with a display generating component and one or more input devices: displaying, via a display generating component, a user interface for sharing an account associated with the first user identity with a second user identity; detecting, via the one or more input devices, one or more inputs corresponding to a request to share the account with the second user identity; in response to detecting the one or more inputs corresponding to the request to share the account with the second user identity, displaying, via the display generating component, an option for configuring limits on transactions conducted using the account by the second user identity; detecting, via the one or more input devices, one or more inputs specifying an amount for the limit on transactions conducted using the account by the second user identity; as well as After detecting the one or more inputs specifying the amount of the limit on transactions performed by the second user identity using the account, sending a request to invite the second user identity to become a participant of the account, wherein after becoming a participant of the account, the second user identity is allowed to perform transactions using the account according to the specified amount.

14. The method of claim 13, wherein after becoming a participant of the account, the second user identity has access to transaction information of the second user identity but does not have access to transaction information of other participants or owners of the account.

15. The method according to claim 13 or 14, further comprising: prior to displaying the user interface for sharing the account associated with the first user identity with the second user identity, displaying, via the display generating component, one or more identity user interface objects corresponding to one or more user identities with which the account may be shared, wherein the one or more identity user interface objects include an identity user interface object corresponding to the second user identity; detecting, via the one or more input devices, a user input directed to a corresponding identity user interface object of the one or more identity user interface objects while displaying the one or more identity user interface objects, wherein in response to receiving the user input directed to the corresponding identity user interface object and based on a determination that the corresponding identity user interface object corresponds to the second user identity, a user interface for sharing the account associated with the first user identity with the second user identity is displayed.

16. The method according to claim 13 or 14, further comprising: After sending the request to invite the second user identity to become a participant of the account, receiving an indication that the second user identity has accepted the invitation to become a participant of the account; and After receiving the indication, a notification of sharing the account with the second user identity is displayed via the display generation component.

17. The method according to claim 16, further comprising: Upon receiving the indication that the second user identity has accepted the invitation to become a participant of the account: providing a notification corresponding to the transaction based on a determination that the completed transaction exceeds the amount specified by the limit on transactions using the account by the second user identity; as well as Based on a determination that the completed transaction has not exceeded the amount specified regarding the limit on transactions using the account by the second user identity, the transaction does not exceed the specified amount of the transaction limit using the account, and waives providing notification corresponding to the transaction.

18. The method according to claim 13 or 14, further comprising: displaying, via the display generating component, a settings interface including an option that, when selected, prohibits the second user identity from using the account for transactions while continuing to share the account with the second user identity; detecting user input corresponding to selection of the option; as well as In response to detecting the user input corresponding to a selection of the option, the second user identity is prohibited from using the account for transactions while continuing to share the account with the corresponding participant.

19. The method according to claim 13 or 14, wherein: The limit on transactions conducted using the account by the second user identity is a per-transaction limit.

20. The method according to claim 13 or 14, wherein: The limit on transactions using the account by the second user identity is a total spending limit for a predetermined duration.

21. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system, the computer system being associated with a first user identity in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for executing the method of any one of claims 13-20.

22. A computer system associated with a first user identity configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 13-20.

23. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Apparatus for performing the method according to any one of claims 13-20.

24. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method of any one of claims 13-20.

Images