User interface for accessing accounts

Abstract

The present disclosure provides a user interface for accessing accounts. The present disclosure as a whole relates to creating accounts for services. A request to create an account for a first service is received. In response to receiving the request to create the account for the first service, a first login option and a second login option are displayed. If input selecting the first login option is detected, a request to create an account for the first service using a user's first contact information is transmitted. If input selecting the second login option is detected, a request to create an account for the first service using the user's second contact information is transmitted. The second contact information is automatically generated for the service and does not reveal the user's first contact information.

Description

[0001] Division Statement

[0002] This application is a divisional application of the Chinese invention patent application with the application date of May 30, 2020, the invention name of which is “User Interface for Accessing Accounts” and the application number is: 202080040618.4. Technical Field

[0003] The present disclosure relates generally to computer user interfaces and, more particularly, to user interfaces for creating accounts for services. Background Art

[0004] Services such as applications or websites use user accounts to identify users who use the application or website. In many cases, applications or websites provide customized information to users based on user accounts. Summary of the Invention

[0005] However, some techniques for creating accounts for services using electronic devices are often cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces, which may include manually entering the user's contact information with multiple keystrokes or keystrokes. As another example, some existing techniques expose the user's personal information (such as the user's email address) to the service. Existing techniques require more time than necessary, which results in a waste of user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0006] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for creating accounts for services. Such methods and interfaces optionally supplement or replace other methods for creating accounts. Such methods and interfaces reduce the cognitive burden on users and produce more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0007] An exemplary method is disclosed herein. One exemplary method includes, at an electronic device having a display device: receiving a request to create an account for a first service; in response to receiving the request to create an account for the first service, simultaneously displaying via the display device: a first login option; and a second login option; detecting a set of one or more inputs; and in response to detecting the set of one or more inputs: upon determining that the set of one or more inputs corresponds to selection of the first login option, transmitting a request to create an account for the first service using first contact information of a user; and upon determining that the set of one or more inputs corresponds to selection of the second login option, transmitting a request to create an account for the first service using second contact information of the user, wherein the second contact information is automatically generated for the service and does not reveal the first contact information of the user.

[0008] 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 an electronic device having a display device, the one or more programs including instructions for performing the following operations: receiving a request to create an account for a first service; in response to receiving the request to create an account for the first service, simultaneously displaying, via the display device: a first login option; and a second login option; detecting a set of one or more inputs; and in response to detecting the set of one or more inputs: based on determining that the set of one or more inputs corresponds to selection of the first login option, transmitting a request to create an account for the first service using first contact information of a user; and based on determining that the set of one or more inputs corresponds to selection of the second login option, transmitting a request to create an account for the first service using second contact information of the user, wherein the second contact information is automatically generated for the service and does not reveal the first contact information of the user.

[0009] 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 an electronic device having a display device, the one or more programs including instructions for performing the following operations: receiving a request to create an account for a first service; in response to receiving the request to create an account for the first service, simultaneously displaying, via the display device: a first login option; and a second login option; detecting a set of one or more inputs; and in response to detecting the set of one or more inputs: based on determining that the set of one or more inputs corresponds to selection of the first login option, transmitting a request to create an account for the first service using first contact information of a user; and based on determining that the set of one or more inputs corresponds to selection of the second login option, transmitting a request to create an account for the first service using second contact information of the user, wherein the second contact information is automatically generated for the service and does not reveal the first contact information of the user.

[0010] An example electronic device is described herein. An example electronic device includes a display device; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request to create an account for a first service; in response to receiving the request to create an account for the first service, simultaneously displaying via the display device: a first login option; and a second login option; detecting a set of one or more inputs; and in response to detecting the set of one or more inputs: based on determining that the set of one or more inputs corresponds to selection of the first login option, transmitting a request to create an account for the first service using first contact information of a user; and based on determining that the set of one or more inputs corresponds to selection of the second login option, transmitting a request to create an account for the first service using second contact information of the user, wherein the second contact information is automatically generated for the service and does not reveal the first contact information of the user.

[0011] An example electronic device includes a display device; a device for receiving a request to create an account for a first service; a device for simultaneously displaying a first login option and a second login option via the display device in response to receiving the request to create an account for the first service; a device for detecting a set of one or more inputs; and a device for performing the following operations in response to detecting the set of one or more inputs: based on determining that the set of one or more inputs corresponds to selection of the first login option, transmitting a request to create an account for the first service using a user's first contact information; and based on determining that the set of one or more inputs corresponds to selection of the second login option, transmitting a request to create an account for the first service using the user's second contact information, wherein the second contact information is automatically generated for the service and does not reveal the user's first contact information.

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

[0013] Thus, a faster, more efficient method and interface for creating accounts for services is provided for devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for creating accounts. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

[0023] Figures 6A to 6W An exemplary user interface for creating an account for a service is shown according to some embodiments.

[0024] 7A to 7B An exemplary user interface for managing contact information associated with a service is shown according to some embodiments.

[0025] Figures 8A to 8G An exemplary user interface for viewing and managing settings for a service is shown according to some embodiments.

[0026] Figure 9 is a flowchart illustrating a method for creating an account for a service using an electronic device according to some embodiments. DETAILED DESCRIPTION

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

[0028] There is a need for an electronic device that provides an efficient method and interface for creating accounts for services. For example, some existing technologies use complex and time-consuming user interfaces, which may involve manually entering a user's contact information with multiple keystrokes or keystrokes. In contrast, the techniques of the present disclosure can reduce the user's cognitive burden by reducing the amount of information required to create an account, thereby improving productivity. Furthermore, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0029] under Figure 1A to Figure 1B 、 Figure 2 、 Figure 3 、 Figures 4A to 4B and Figures 5A to 5B A description of an example device to perform techniques for creating an account for a service is provided. Figures 6A to 6W An exemplary user interface for creating an account for a service is shown. 7A to 7B An exemplary user interface for managing contact information associated with a service is shown. Figures 8A to 8G An exemplary user interface for viewing and managing settings for a service is shown. Figure 9 is a flow chart illustrating a method of creating an account for a service according to some embodiments. Figures 6A to 6W 、 7A to 7B ,and Figures 8A to 8G The user interface in is used to illustrate the processes described below, which include Figure 9 in the process.

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

[0031] The terms used in the description of the various embodiments described herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a" and "the" are intended to also include plural forms unless the context clearly indicates otherwise. It will also be understood that the terms "and / or" used herein refer to and encompass any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "comprise" and / or "comprising" when used in this manual specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.

[0032] 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 [stated condition or event] is detected" are optionally interpreted to mean "upon determining," or "in response to determining that," or "upon detecting [stated condition or event]," or "in response to detecting [stated condition or event]," depending on the context.

[0033] Embodiments of electronic devices, user interfaces for such devices, and processes associated with 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 music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod equipment, and Device. Optionally, other portable electronic devices are used, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads). 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 trackpads). 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).

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

[0035] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a rendering 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.

[0036] 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 the touch-sensitive surface) optionally supports the various applications with a user interface that is intuitive and clear to the user.

[0037] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. 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." Device 100 includes 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, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile 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.

[0038] 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) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four 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 surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some embodiments, the surrogate measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold 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 functionality that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0039] 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 a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (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 that corresponds 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" on 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 was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While 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.

[0040] 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 in the EMBODIMENTS 100 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

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

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

[0043] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with communication networks and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known 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 circuitry 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via a short-range communication radio. The 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 ... 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 Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0044] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the 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 with both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0045] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripherals 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 / to 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 (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 up / down button for volume control of the speaker 111 and / or 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 (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a 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.

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

[0047] 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 112. 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.

[0048] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from the 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 that 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 the user's finger.

[0049] 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

[0050] 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, whereas a touch-sensitive trackpad does not provide visual output.

[0051] 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 No. 11 / 381,313, filed on May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; (5) U.S. patent application No. 11 / 050,264, filed on January 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive and (9) U.S. patent application 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.

[0052] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or appendage, such as a stylus, a finger, or the like, 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 ​​a 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 user's desired action.

[0053] In some embodiments, in addition to the touch screen, 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 a touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0054] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, 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.

[0055] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor is shown coupled to the optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses 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 still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, facing away from the touch screen display 112 on the front of the device, enabling the touch screen display to be used as a viewfinder for still and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing the user to optionally capture an image of the user for video conferencing while viewing 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), allowing a single optical sensor 164 to be used with the touch screen display for both video conferencing and still and / or video image acquisition.

[0056] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor is shown coupled to a depth camera controller 169 in the I / O subsystem 106. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of objects (e.g., faces) within the scene from a viewpoint (e.g., the 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 for different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located on the front of the device 100, enabling the user to optionally capture an image of the user with depth information for video conferencing while viewing other video conference participants on the touchscreen display, and to capture selfies with depth map data. In some embodiments, the depth camera sensor 175 is located on the rear of the device, or on 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), enabling the depth camera sensor 175 to be used in conjunction with the touchscreen display for both video conferencing and still and / or video image acquisition.

[0057] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to force sensor controller 159 in 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 a 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 with 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 touch screen display 112 located on the front of device 100.

[0058] 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: No. 11 / 241,839, entitled “Proximity Detector In Handheld Device”; No. 11 / 240,788, entitled “Proximity Detector In Handheld Device”; No. 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output”; No. 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices”; and No. 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entireties. 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.

[0059] 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 speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile outputs on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth 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.

[0060] 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 optionally performs as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed 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.

[0061] 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, which includes information obtained from the device's various sensors and input control devices 116; and position information regarding the device's position and / or posture.

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

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

[0064] 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 down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been 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 ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single-finger contact) or multiple points of contact simultaneously (e.g., "multi-touch" / multiple-finger contact). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touchpad.

[0065] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without changing the physical hardware of the device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, 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).

[0066] 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). Thus, 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.

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

[0068] 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 specifying the graphics to be displayed from an application program or the like, along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 156.

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

[0070] 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).

[0071] 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 yellow pages widget, and the map / navigation widget).

[0072] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

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

[0074] Telephone module 138;

[0075] Video conferencing module 139;

[0076] Email client module 140;

[0077] Instant messaging (IM) module 141;

[0078] Fitness support module 142;

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

[0080] Image management module 144;

[0081] Video player module;

[0082] Music player module;

[0083] Browser module 147;

[0084] Calendar module 148;

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

[0086] A widget creator module 150 for forming user-created widgets 149-6;

[0087] Search module 151;

[0088] Video and music player module 152, which combines the video player module and the music player module;

[0089] Notepad module 153;

[0090] Map module 154; and / or

[0091] Online video module 155.

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

[0093] In combination with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contacts module 137 is optionally used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contacts 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 so on.

[0094] 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 character sequence corresponding to a phone number, access one or more phone numbers in contacts module 137, modify an entered phone number, dial the 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.

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

[0096] In conjunction with RF circuitry 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.

[0097] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging 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 Service (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).

[0098] 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 workout (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 a workout; and displaying, storing, and transmitting fitness data.

[0099] In combination 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.

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

[0101] 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 for, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0102] 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 a calendar and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0103] 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).

[0104] 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).

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

[0106] 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.).

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

[0108] In combination with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and 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.

[0109] 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 allowing a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video. Additional descriptions 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.

[0110] 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 separate software programs, processes, or modules, and thus 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.

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

[0112] A predefined set of functions that are exclusively performed 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 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such embodiments, the trackpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

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

[0114] 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 an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that 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.

[0115] 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 the user to return to a previous state or view of the application 136-1, and a redo / undo queue of previous actions taken by the user.

[0116] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via 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.

[0117] 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).

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

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

[0120] 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 programmatic levels within the application's programmatic or view hierarchy. 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 based at least in part on the hit view of the initial touch that started the touch-based gesture.

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

[0122] 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, views higher in the hierarchy will still remain actively participating views.

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

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

[0125] 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 that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 is part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application's internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

[0127] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as touches or touch movements. 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 a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape 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).

[0128] The event comparator 184 compares the event information with a predefined event or sub-event definition and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 184 includes an event definition 186. The 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, the 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 the displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the 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.

[0129] 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 that is associated with the sub-event and the object that triggered the hit test.

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

[0131] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definitions 186, the corresponding event recognizer 180 enters the 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.

[0132] In some embodiments, 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 for 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.

[0133] 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 an event handler 190 is different from sending (and deferred sending) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.

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

[0135] 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 location of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

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

[0137] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 100, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a trackpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken 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.

[0138] Figure 2A portable multifunction device 100 with a touch screen 112 is shown according to some embodiments. 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 the 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 the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of a finger that has made 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 does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0140] 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 subscriber identity module (SIM) card slot 210, a headset 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 holding it in the depressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions via the microphone 113. The device 100 also optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for the user of the device 100.

[0141] Figure 33 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the 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 gaming system, or a control device (e.g., a home controller or an industrial controller). The 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. The device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or 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 referenced device). Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1A The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores data 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.

[0142] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the memory device mentioned previously.Each module in the above-mentioned modules corresponds to the instruction set for performing the above-mentioned functions.Above-mentioned modules or programs (for example, instruction sets) need not 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 above-mentioned modules and data structures.In addition, memory 370 optionally stores additional modules and data structures not described above.

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

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

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

[0146] Time 404;

[0147] Bluetooth indicator 405;

[0148] Battery status indicator 406;

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

[0150] o An icon 416 labeled “Phone” for the phone module 138 , which optionally includes an indicator 414 of the number of missed calls or voicemails;

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

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

[0153] o An icon 422 labeled “iPod” for the video and music player module 152 (also referred to as the iPod (trademark of Apple Inc.) module 152); and

[0154] Icons for other apps, such as:

[0155] o Icon 424 labeled “Messages” of IM module 141;

[0156] o Icon 426 labeled “Calendar” of calendar module 148;

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

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

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

[0160] o Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

[0161] o Icon 436 labeled “Map” of the map module 154;

[0162] o Icon 438 labeled “Weather” of the weather widget 149-1;

[0163] o Icon 440 labeled “Clock” of the alarm clock widget 149-4;

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

[0165] o Icon 444 labeled "Notepad" of the Notepad module 153; and

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

[0167] It should be pointed out that Figure 4A The icon labels shown are exemplary only. For example, icon 422 for video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective 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.

[0168] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 tablet or trackpad 355) of the 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.

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

[0170] 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). For 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 the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

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

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

[0173] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, 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.

[0174] Figure 5B An exemplary personal electronic device 500 is shown. 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. The I / O portion 514 can be connected to a display 504, which can have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, the I / O portion 514 can be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, the input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

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

[0177] As used herein, the term "indicator" refers to an indication that is optionally provided on device 100, 300, and / or 500 ( Figure 1A 、 Figure 3 and Figures 5A to 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.

[0178] 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 position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in FIG, the particular user interface element is adjusted according to the detected input. In the case of a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display Figure 1A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG, 2 , a contact detected on the touch screen acts as a “focus selector” such that when 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 generally 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).

[0179] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 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 begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). 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 in 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.

[0180] In some embodiments, a portion of a gesture is identified for determining the 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 intensity of the swipe contact before determining the characteristic strength of the contact. For example, the 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 dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic strength.

[0181] The intensity of the 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 action typically associated with clicking a button of a physical mouse or trackpad.

[0182] In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an action different from that typically associated with clicking a button of a physical mouse or trackpad.

[0183] In some embodiments, when a contact is detected with a characteristic intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below which are no longer detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing operations associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface figures.

[0184] 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 a 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 a 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.

[0185] 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 an increase in the intensity of the contact (or multiple contacts) to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact to above the press input intensity threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the 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 the press input intensity threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0186] 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 that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable 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 "upstroke" 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 below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below 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).

[0187] For ease of explanation, 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 optionally triggered in response to detecting any of the following: contact intensity increasing 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 below the press input intensity threshold, and / or contact intensity decreasing 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.

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

[0189] Figures 6A to 6W An exemplary user interface for creating an account for a service is shown according to some embodiments. 7A to 7B An exemplary user interface for managing contact information associated with a service is shown according to some embodiments. Figures 8A to 8G An exemplary user interface for viewing and managing settings for a service is shown according to some embodiments. The user interface in these figures is used to illustrate the following description of the Figure 9 The process of the process.

[0190] Figure 6A An electronic device 600a is shown that includes a display device 602a (e.g., integrated with a touch-sensitive surface). In some embodiments, the electronic device 600a includes one or more features of device 100, 300, or 500. The electronic device 600a is configured to display user interfaces provided by first-party services (e.g., applications, websites, or other services owned and / or operated by an entity affiliated with the electronic device) and user interfaces provided by third-party services (e.g., applications, websites, or other services owned and / or operated by a second entity not affiliated with the electronic device). Figure 6AAs shown, electronic device 600a displays a user interface 604 for a third-party service (e.g., an application or website) via display device 602a. User interface 604 is used to log in to the third-party service or create an account with the third-party service. User interface 604 includes a login field 606 for logging into an account with the third-party service using a username and password created for the third-party service (e.g., a username and password used to authenticate the user to the third-party service by transmitting the username and password to the third-party service). User interface 604 also includes an enablement 608 for creating an account with the third-party service using a first-party authentication provider (e.g., a "login ID") without entering a username and password for the third-party service. Instead, the first-party authentication provider authenticates the user independently of the third-party service (e.g., by logging into an account with the first-party authentication provider and / or verifying the user's identity using biometric information known to the first-party authentication provider), and then communicates with the third-party service to create and log in to the account with the third-party service without the user entering a username and password for the third-party service. In addition, the user can authenticate to multiple third-party services using the same authentication process with the first-party authentication provider (e.g., logging into the same account with the first-party provider and / or verifying the user's identity using biometric information known to the first-party authentication provider). In response to detecting input 603 (e.g., a tap gesture) corresponding to affordance 608, a user interface for the first-party authentication provider (e.g., Figure 6B or Figure 6C The user interface 610 shown is displayed.

[0191] Figure 6B A user interface 610a for a first-party authentication provider is shown, the user interface including information describing the first-party authentication provider (e.g., "Security and Protection," "Quick Login," "Subscription Email Management"). The user interface 610a is displayed overlaying the user interface 604 for the third-party service (e.g., a portion of the user interface 604 continues to be displayed simultaneously with the user interface 610a). In response to detecting input requesting the first-party authentication provider to create an account for the third-party service (e.g., Figure 6A In some embodiments, user interface 604 is a user interface of a first computer application, and user interface 610 is a user interface of a second computer application different from the first computer application. In some embodiments, when a first-party authentication provider is first used to create an account for a third-party service, information describing the first-party authentication provider is included in user interface 610a, such as Figure 6BIn some embodiments, if an account has previously been created for a third-party service using a first-party authentication provider, information describing the first-party authentication provider is not included, but is instead displayed in response to detecting input requesting the first-party authentication provider to create or log in to an account for the third-party service. Figure 6C User interface 610b is shown.

[0192] like Figure 6B As shown, user interface 610a includes an accept affordance 612 and a cancel affordance 614. In response to detecting input 605 corresponding to the accept affordance 612, the information describing the first-party authentication provider ceases to be displayed, and a screen such as the one shown in FIG. Figure 6C In response to detecting input 607 corresponding to canceling affordance 614, user interface 610a ceases to be displayed and user interface 604 for the third-party service is displayed, such as Figure 6A As shown (eg, user interface 610a stops overlaying user interface 604).

[0193] Figure 6C A user interface 610b for a first-party authentication provider is shown, including an indication of an account being used with the first-party authentication provider (e.g., "Log in to the Unicorn application using 'j.appleseed@email.com' and create an account with the Unicorn application"). In some embodiments, in response to detecting input requesting the first-party authentication provider to create or log in to an account for a third-party service (e.g., Figure 6A Input 603 shown), displayed as Figure 6C In some embodiments, the information describing the first-party authentication provider is provided in response to detecting Figure 6B After input 605 is shown and the display is stopped, user interface 610b is displayed.

[0194] like Figure 6CAs shown, user interface 610b includes an enable indication 616 for continuing the creation process with the indicated first-party authentication provider account. In some embodiments, user interface 610b also includes an enable indication 618 for changing to another first-party authentication provider account. In response to detecting input 609 corresponding to enable indication 616 (e.g., a tap input), electronic device 600a continues the process of creating an account for a third-party service using the first-party authentication provider. In some embodiments, in response to detecting input 609, electronic device 600a authenticates that the user is an authorized user of the indicated first-party authentication provider account (e.g., the user is authorized to use the account associated with "j.appleseed@email.com" at the first-party authentication provider). In some embodiments, electronic device 600a uses facial recognition to authenticate the user. In some embodiments, electronic device 600a uses fingerprint recognition to authenticate the user. In some embodiments, electronic device 600a authenticates the user by requesting a username and password (and optionally, a second authentication factor) and verifying that the username and password correspond to the indicated first-party authentication provider account. In some embodiments, (e.g., when using facial recognition or fingerprint recognition to authenticate the user) the device 600a remains logged into the first-party authentication provider account. For example, the device 600a is logged into the first-party authentication provider account before starting the creation process, and the device 600a remains logged into the first-party authentication provider account throughout the creation process.

[0195] In some embodiments, in response to detecting the input 609 (and optionally after authenticating the user), the security parameters associated with the indicated first-party authentication provider account are verified. If an issue with the security of the indicated first-party authentication provider account is detected (e.g., an email address is not verified, the password does not meet the requirements, two-factor authentication is not enabled, the terms and conditions are not accepted), a notification is displayed requesting the user to correct the security issue (e.g., Figure 6D Notification 620 is shown. If no issues with the security of the indicated first-party authentication provider account are detected (and optionally, the user is authenticated), the process for creating an account for the third-party service using the first-party authentication provider continues.

[0196] In some embodiments, in response to detecting input 611 (e.g., a tap input) corresponding to affordance 618, one or more interfaces for changing to another first-party authentication provider account (e.g., a login interface for a first-party authentication provider) are displayed. After the first-party authentication provider account has been changed, user interface 610b may be displayed as shown in FIG. Figure 6C The account is displayed, but includes an indication that another account is being used with the first-party authentication provider (e.g., another email address is displayed).

[0197] Figure 6D A notification 620 is shown requesting the user to correct the security issue after detecting an issue with the security of the indicated first-party authentication provider account (e.g., email address not verified, password does not meet requirements, two-factor authentication not enabled, terms and conditions not accepted). In some embodiments, in response to detecting Figure 6C 609 (and optionally after authenticating the user), verify the security of the indicated first-party authentication provider account. Notification 620 includes a set enable indication 622 and a cancel enable indication 624. In response to detecting an input corresponding to the cancel enable indication 624 (e.g., a tap input), notification 620 ceases to be displayed and a screen is displayed as shown. Figure 6C The user interface 610 is shown. Figure 6C In the user interface 610 shown, another first-party authentication provider account (e.g., an account without security questions) can be accessed, or the process of creating an account for a third-party service using the first-party authentication provider can be canceled. In response to detecting an input 613 corresponding to a setup affordance (e.g., a tap input), a security interface for correcting security questions (e.g., as shown in FIG. 6 ) is displayed. Figure 6E Security interface 626 shown).

[0198] like Figure 6E As shown, security interface 626 includes security settings associated with the first-party authentication provider account. In some embodiments, security interface 626 is displayed in response to detecting a security issue with the indicated first-party authentication provider account (e.g., email address not verified, password does not meet requirements, two-factor authentication not enabled, terms and conditions not accepted). From security interface 626, the detected security issue can be corrected by the user providing the necessary information and / or input for the detected security issue.

[0199] Figure 6F A user interface 610c for a first-party authentication provider is shown including login options 628 and 630. In some embodiments, in response to detecting input requesting the first-party authentication provider to create or log in to an account for a third-party service (e.g., Figure 6A Input 603 shown), displayed as Figure 6F In some embodiments, the information describing the first party authentication provider is provided in response to detecting Figure 6B After the display stops due to the input 605 shown, the user interface 610c is displayed. In some embodiments, the user interface 610c is displayed in response to detecting the input 609 corresponding to the enable indication 616, which is used to continue the creation process with the indicated first-party authentication provider account, such as Figure 6C In some embodiments, in response to detecting a request for contact information (e.g., a user's email) from a third-party service, user interface 610c is displayed instead of Figure 6C User interface 610b is shown.

[0200] like Figure 6F As shown, user interface 610c includes a login option 628 (e.g., a "share my email" option) and a login option 630 (e.g., a "hide my email" option). User interface 610c also includes an enablement representation 632 for continuing the account creation process for the third-party service. When user interface 610c is initially displayed, neither login option 628 nor 630 is selected. When neither login option 628 nor 630 is selected, enablement representation 632 is disabled (e.g., input on enablement representation 632 will not continue the account creation process). In some embodiments, enablement representation 632 is displayed in another manner to indicate that the enablement representation is disabled (e.g., displayed in a different color than when the enablement representation is enabled). If input corresponding to login option 628 is detected (e.g., a tap input), an indication of the selection is displayed, and as the account creation process continues, the user's contact information (e.g., the user's personal email address associated with the user's first-party authentication provider account) is transmitted to the third-party service. If input corresponding to the login option 630 is detected (e.g., 615, a tap input), an indication of that selection is displayed and, as the account creation process continues, obfuscated contact information (e.g., a proxy email address that is automatically generated and does not reveal the user's personal email address) is transmitted to the third-party service.

[0201] Figure 6G Shown is a screen shot of a user detecting an input 615 corresponding to a login option 630 (e.g., Figure 6F As shown in FIG) the user interface 610c after. Figure 6G As shown, in response to detecting input 615, an indication 634 of the selected login option is displayed. In some embodiments, if the first-party authentication provider has been previously used to create an account for a third-party service, one of login options 628 or 630 is pre-selected based on which login option was selected during the previous creation process (e.g., not displayed as shown). Figure 6FUser interface 610c shown). After login option 628 or 630 is selected, enable indication 632 is enabled (e.g., input on enable indication 632 will continue the account creation process). In some embodiments, enable indication 632 is displayed in another manner to indicate that the enable indication is enabled (e.g., displayed in a different color than when the enable indication is disabled). In response to detecting input 617 corresponding to enable indication 632 (e.g., a tap input), electronic device 600a uses contact information corresponding to the selected login option to continue the process of creating an account for the third-party service. In some embodiments, in response to detecting input 617, electronic device 600a authenticates that the user is an authorized user of the indicated first-party authentication provider account (e.g., the user is authorized to use the account "j.appleseed@email.com"). In some embodiments, electronic device 600a uses facial recognition to authenticate the user. In some embodiments, electronic device 600a uses fingerprint recognition to authenticate the user. In some embodiments, the electronic device 600a authenticates the user by requesting a username and password (and optionally, a second authentication factor) and verifying that the username and password correspond to the indicated first-party authentication provider account.

[0202] Figure 6H A user interface 610d for a first-party authentication provider is shown, including login options 628 and 630 and a name field 636. In some embodiments, in response to detecting input requesting the first-party authentication provider to create or log in to an account for a third-party service (e.g., Figure 6A Input 603 shown), displayed as Figure 6H In some embodiments, the information describing the first party authentication provider is provided in response to detecting Figure 6B After the display stops due to the input 605 shown, the user interface 610d is displayed. In some embodiments, the user interface 610d is displayed in response to detecting the input 609 corresponding to the enable indication 616, which is used to continue the creation process with the indicated first-party authentication provider account, such as Figure 6C In some embodiments, in response to detecting a request from a third-party service for contact information (e.g., the user's email) and the user's name, user interface 610d is displayed instead of Figure 6C and Figure 6F User interface 610b or 610c is shown.

[0203] like Figure 6HAs shown, user interface 610d includes a name field 636 in addition to login options 628 (e.g., a "share my email" option) and login options 630 (e.g., a "hide my email" option). User interface 610d also includes a clear affordance 638 for clearing the name of the account. When user interface 610d is initially displayed, name field 636 includes a default name associated with the user's first-party authentication provider account (e.g., the user's name). If input corresponding to name field 636 (e.g., input 621) or clear affordance 638 (e.g., input 619) is detected (e.g., tapping enter), a user interface for editing the name (e.g., as shown in FIG. 6 ) is displayed. Figure 6I and Figure 6J In some embodiments, in response to detecting input 621 corresponding to the name field 636, a default name is pre-populated in the user interface 610e, such as Figure 6J In contrast, in some embodiments, in response to detecting input 619 corresponding to clearing affordance 638, the default name is cleared from user interface 610e, as shown. Figure 6I shown.

[0204] Figure 6I User interface 610e is shown with the default name cleared from first name field 640 and last name field 642. In some embodiments, in response to detecting input 619 corresponding to clear affordance 638, the default name is cleared from user interface 610e, such as Figure 6H When first name field 640 and last name field 642 do not include text, affordance 644 for continuing the account creation process for the third-party service is disabled (e.g., input on affordance 644 will not continue the account creation process until text is entered in first name field 640 and last name field 642). In some embodiments, affordance 644 is displayed in another manner to indicate that the affordance is disabled (e.g., displayed in a different color than when the affordance is enabled).

[0205] Figure 6J A user interface 610e is shown with a default name pre-populated in the first name field 640 and the last name field 642. In some embodiments, in response to detecting input 621 corresponding to the name field 636, a default name is pre-populated in the first name field 640 and the last name field 642, such as Figure 6Has shown. Pre-populating the first name field 640 and the last name field 642 with default names allows the default names to be edited without re-entering the entire name. When text is included in the first name field 640 and the last name field 642, an enable indication 644 for continuing the account creation process for the third-party service is enabled (e.g., input on the enable indication 644 will continue the account creation process). In some embodiments, the enable indication 644 is displayed in another manner to indicate that the enable indication is enabled (e.g., displayed in a different color than when the enable indication is disabled). In response to detecting input 623 corresponding to the enable indication 644, the user interface 610e stops being displayed, and the user interface 610e is displayed using the names as entered in the first name field 640 and the last name field 642. Figure 6H User interface 610d is shown.

[0206] Figure 6K The user interface 610d is shown after detecting input corresponding to a login option 628 (e.g., a "share my email" option). Figure 6K As shown, if the alternative email address 646 is known to the user, the alternative email address is displayed in response to detecting input corresponding to the login option 628 (e.g., the "Share My Email" option expands to list the alternative email addresses 646). In some embodiments, an indication (e.g., a check mark) is displayed to indicate which email address is currently selected for the login option 628. In response to input 625 (e.g., tapping Enter) corresponding to the alternative email address 646, the email address to be used for the login option 628 is changed.

[0207] Figure 6L Shown is a diagram of a process where an input 625 ( Figure 6K ) after the user interface 610d. Figure 6L As shown, the email address associated with login option 628 is changed to correspond to the alternative email address selected by input 625. After selecting login option 628, and in response to detecting the input corresponding to affordance 632, electronic device 600a continues the process for creating an account for the third-party service using the contact information corresponding to login option 628 (e.g., the alternative email address).

[0208] Figure 6MAn electronic device 600b (e.g., a watch) is shown that includes a display device 602b (e.g., integrated with a touch-sensitive surface). In some embodiments, the electronic device 600b includes one or more features of the device 100, 300, or 500. The electronic device 600b displays a user interface 610f via the display device 602b. The user interface 610f allows a user to create an account for a third-party service using a first-party authentication provider, such as a reference. Figures 6A to 6L In some embodiments, the user interface 610f includes Figures 6A to 6L 6. The illustrated versions of user interfaces 610a-610e are modified for display via a small format display device such as display device 602b. For example, user interfaces 610a-610e are modified to be scrollable using rotatable input device 675 and include elements that are selectable using rotatable input device 675, but are otherwise provided with reference to Figures 6A to 6L Same functionality as described above.

[0209] Figure 6N An electronic device 600c (e.g., a laptop) is shown including a display device 602c. In some embodiments, the electronic device 600c includes one or more features of the device 100, 300, or 500. The electronic device 600c displays a user interface 610g via the display device 602c, overlaying a user interface 604 for a third-party service (e.g., a website). Figure 6N As shown, user interface 604 is displayed in a first-party web browser 648 (e.g., a web browser owned and / or operated by the same entity as the authentication provider), and user interface 610g is an interface native to the web browser that overlays user interface 604 in the web browser. User interface 610g allows a user to create an account for a third-party service (e.g., a website corresponding to user interface 604) with the first-party authentication provider, as described with reference to FIG. Figures 6A to 6L In some embodiments, the user interface 610g includes Figures 6A to 6L The user interfaces 610a-610e are modified to be displayed as native interfaces of a web browser. For example, the user interfaces 610a-610e are modified to include elements that can be selected using a mouse and / or keyboard, but are otherwise provided with reference to Figures 6A to 6L In some embodiments, in response to detecting an authorized fingerprint with the fingerprint sensor, an affordance 632 is activated for continuing the process for creating an account for the third-party service with the first-party authentication provider.

[0210] Figure 6OElectronic device 600c is shown displaying user interface 652 in a third-party web browser 650 (e.g., a web browser provided, owned, and / or operated by an entity different from the authentication provider) via display device 602c. User interface 652 is displayed in response to detecting a request to create an account for a service (e.g., a website) using the authentication provider. In some embodiments, one or more login pages for the authentication provider are displayed prior to displaying user interface 652, and user interface 652 is displayed in response to detecting an authorized login to an account with the authentication provider. User interface 652 includes an enablement representation 654 for continuing the process for creating an account for the service using the authentication provider. In response to detecting an input corresponding to enablement representation 654 (e.g., a tap input, a selection using a cursor), a verification code is transmitted to a device associated with the authentication provider account.

[0211] Figure 6P shows that when the corresponding enabling indication 654 (in Figure 6O ) after the input of the user interface 652. Figure 6P As shown, user interface 652 includes a field 656 for entering a verification code that is transmitted to a device associated with the authentication provider account. If the verification code authorizes the user, then display of user interface 652 ceases, and the process for creating an account for the service with the authentication provider continues, as described with reference to FIG. Figures 6A to 6L As stated.

[0212] Figure 6Q An electronic device 600d (e.g., a television) is shown displaying a user interface 604 for a third-party service (e.g., an interface for a video streaming application) via a display device 602d. In response to detecting a request to create an account for a service (e.g., a website) using an authentication provider, a user interface 652 is displayed. User interface 604 includes an enablement representation 608 for creating an account with the third-party service using the authentication provider (e.g., a "login ID") without entering a username and password for the third-party service. Instead of displaying the user interface for creating an account with the third-party service using the authentication provider on display device 602d, the user interface is displayed on a separate device (e.g., electronic device 600a) associated with the user's authentication provider account. In response to detecting an input corresponding to the enablement representation 608 (e.g., a selection using a remote control), a process for creating an account with the third-party service using the authentication provider is initiated on the separate device.

[0213] Figure 6R 6. User interface 604 is shown after the process for creating an account with a third-party service using an authentication provider has been initiated on a separate device (e.g., electronic device 600a). Figure 6RAs shown, the user interface 604 includes a notification 658 for continuing the process for creating an account with the third-party service using the separate device (eg, electronic device 600a ).

[0214] Figure 6S The electronic device 600a is shown displaying a notification 660 via the display device 602a that a request has been received from a separate device (e.g., the electronic device 600d) to create an account with a third-party service using an authentication provider. In response to detecting an input 627 (e.g., a tap input) corresponding to the notification 660, the electronic device displays a user interface 610h (e.g., Figure 6T ), for continuing the process of creating an account with the third-party service using the authentication provider on that separate device.

[0215] Figure 6T A user interface 610h for an authentication provider is shown, which includes an indication of a separate device (e.g., electronic device 600d) requesting an authentication provider to be used to create an account for a service on the separate device (e.g., "Sign in to the streaming service on your TV using 'j.appleseed@email.com'"). In some embodiments, such as Figure 6T The user interface 610h is shown in response to detecting input 627 ( Figure 6S The user interface 610h allows the user to use the Figures 6A to 6L The authentication provider creates an account for the service (e.g., a video streaming application) on the individual device. In some embodiments, the user interface 610h includes a Figures 6A to 6L The user interfaces 610a-610e described above have the same elements and provide the same references as those in the referenced Figures 6A to 6L The user interfaces 610a-610e have the same functions.

[0216] Figure 6U The electronic device 600a is shown displaying a user interface 662a for a first-party authentication provider via the display device 602a. In response to detecting an input requesting the first-party authentication provider to create or log in to an account for a third-party service (e.g., Figure 6AIn response to detecting input 631 (e.g., a tap input) corresponding to the enable indication 664, the electronic device 600a continues the process for logging into the account for the third-party service that was previously created using the first-party authentication provider. In some embodiments, in response to detecting input 631, the electronic device 600a authenticates that the user is an authorized user of the indicated first-party authentication provider account (e.g., the user is authorized to use the account "j.appleseed@email.com"). In some embodiments, the electronic device 600a uses facial recognition to authenticate the user. In some embodiments, the electronic device 600a uses fingerprint recognition to authenticate the user. In some embodiments, the electronic device 600a authenticates the user by requesting a username and password (and optionally, a second authentication factor) and verifying that the username and password correspond to the indicated first-party authentication provider account. In some embodiments, (e.g., when using facial recognition or fingerprint recognition to authenticate the user) the device 600a remains logged in to the first-party authentication provider account.

[0217] In some embodiments, in response to detecting input 633 (e.g., a tap input) corresponding to affordance 618, one or more interfaces for changing to another first-party authentication provider account (e.g., a login interface for a first-party authentication provider) are displayed. After the first-party authentication provider account has been changed, if the new first-party authentication provider account has been previously used to create an account for a third-party service, user interface 662a is displayed, such as Figure 6U , but includes an indication that another account is used with the first-party authentication provider (e.g., another email address is displayed). If the new first-party authentication provider account has not been previously used to create an account for the third-party service, user interface 610b is displayed, such as Figure 6C as shown, but includes an indication that another account is used with the first-party authentication provider (e.g., showing another email address).

[0218] In some embodiments, as Figure 6V As shown, if it is detected that multiple accounts have been previously used to log in to or create accounts for a third-party service (e.g., the user has previously created an account for a third-party service using a first-party authentication provider on another device and / or has previously logged in to an account for a third-party service using credentials stored at device 600a (or accessible to device 600a)), user interface 662b is displayed. User interface 662b includes an account option 666 corresponding to the first-party authentication provider account that was previously used to create an account for the third-party service. User interface 662b also includes an account option 668 corresponding to the credentials that were previously used to log in to the account for the third-party service. User interface 662a also includes an enablement 664 for continuing the login process using the indicated first-party authentication provider account or credentials that were previously used to log in. In some embodiments, when account option 666 or 668 is not selected, enablement 664 is disabled (e.g., input on enablement 664 will not continue the account login process). In some embodiments, the enable indication 664 is displayed in another manner to indicate that the enable indication is disabled (e.g., displayed in a different color than when the enable indication is enabled).

[0219] like Figure 6W As shown, in response to detecting input 635 corresponding to account option 666 (as Figure 6V , the electronic device 600a logs in to the account for the third-party service using the selected account option 666 or 668.

[0220] Figure 7A The electronic device 600a is shown displaying a contact information interface 704a via a display device 602a for accessing a third-party service using a first-party authentication provider account. The contact information interface 704 includes a forwarding field 706 that indicates the email address to which emails received by the proxy email address are forwarded. During the creation process for the third-party service, when the login option 630 (e.g., Figure 6F and Figure 6G706) is selected, a proxy email address is provided to the third-party service. In some embodiments, all emails received by the proxy email address provided to the third-party service are forwarded to the email address indicated by forwarding field 706. In response to input 703 corresponding to forwarding field 706 (e.g., tapping enter), the email address to which the emails are forwarded can be changed. Thus, even if the various third-party services each receive a different obfuscated email address of the user, the user receives emails from the various third-party services at a single email address (e.g., as indicated in forwarding field 706).

[0221] like Figure 7B As shown, the contact information interface 704b includes forwarding email options 708 and 710. In response to input 703 corresponding to the forwarding field 706, the forwarding email options 708 and 710 are displayed (as shown in FIG. Figure 7A ). Forward email options 708 and 710 correspond to email addresses associated with the user of electronic device 600a. Contact information interface 704b also includes an indication 712 of the selected forward email option. In response to input 705 (e.g., a tap input) corresponding to forward email option 710 (e.g., "jane@work.com"), the position of indication 712 is changed to indicate forward email option 710, and forward field 706 ( Figure 7A ) is updated to indicate the currently selected forward email option 710. In response to selecting another forward email option 710, the proxy email address provided to the third party service is updated to forward emails to the newly selected email address.

[0222] Figure 8A The electronic device 600a is shown displaying a settings interface 804 for a third-party service created using a first-party authentication provider via a display device 602a. The settings interface 804 includes an affordance 806 corresponding to a third-party service (e.g., a website or application) with an account created using the first-party authentication provider. In response to an input 803 (e.g., a swipe input) corresponding to affordance 806a, the corresponding third-party service (e.g., a website or application) may be removed from the settings interface 804. Figure 8B In response to input 807 (e.g., a tap input) corresponding to affordance 806b, additional settings and information for the corresponding third-party service are displayed (e.g., Figure 8C shown).

[0223] like Figure 8B As shown, in response to input 803 ( Figure 8A) (e.g., a swipe input), a delete enable indication 808 for the corresponding third-party service is displayed. In response to input 805 corresponding to the delete enable indication 808 (e.g., a tap input), the corresponding third-party service (e.g., "App1") is removed from the settings interface 804. In some embodiments, removing the third-party service deletes any stored credentials for the third-party service so that the first-party authentication provider cannot be used to log in to the account for the third-party service without re-entering the credentials or creating a new account. In some embodiments, removing the third-party service stops emails from the third-party service from being forwarded to the user's email address (e.g., when a "hide my email" option was selected during the account creation process for the third-party service).

[0224] Figure 8C Electronic device 600a is shown displaying a settings interface 810 for a third-party service (e.g., "Unicorn Application") via display device 602a. In response to input 807 ( Figure 8A In some embodiments, in response to detecting input 809 (e.g., tap input, long press) corresponding to the indication 818 of the proxy email address for the third-party service, the proxy email address is copied for pasting into the text field. In response to detecting input 811 (e.g., tap input) corresponding to the option 816 for enabling or disabling the first-party authentication provider, the use of first-party authentication for the third-party service is enabled or disabled. In response to detecting input 815 (e.g., a tap input) corresponding to option 820 for enabling or disabling forwarding of emails sent to the proxy email address, forwarding of emails sent by the third-party service to the proxy email address is enabled or disabled.

[0225] like Figure 8D As shown, in some embodiments, if the first party authentication provider is enabled for the third party service, then in response to detecting input 811 ( Figure 8C), a notification 822 confirming that the first party authentication provider will be disabled for the third-party service. Notification 822 includes a confirmation enable indication 824 (e.g., "delete") and a cancellation enable indication 826. In response to detecting input 813 (e.g., a tap input) corresponding to the confirmation enable indication 824, the first party authentication provider is disabled for the third-party service. In some embodiments, disabling the first party authentication provider for the third-party service deletes any stored credentials for the third-party service so that the first party authentication provider cannot be used to log in to an account for the third-party service without re-entering the credentials or creating a new account. In some embodiments, disabling the first party authentication provider for the third-party service stops emails from the third-party service from being forwarded to the user's email address (e.g., when a "hide my email" option was selected during the account creation process for the third-party service).

[0226] Figure 8E The settings interface 810 is shown after disabling the first-party authentication provider for third-party services. Figure 8E As shown, option 816 has a changed appearance to indicate that the first-party authentication provider has been disabled for the third-party service, and other settings for the third-party service have ceased to be displayed.

[0227] like Figure 8F As shown, in some embodiments, if forwarding of emails sent to a proxy email address is enabled, then in response to detecting input 815 ( Figure 8C ), notification 828 confirming the forwarding of emails sent by the third-party service to the proxy email address will be disabled. Notification 828 includes a confirmation affordance 830 (e.g., "Stop") and a cancellation affordance 832. In response to detecting input 817 (e.g., a tap input) corresponding to confirmation affordance 830, forwarding of emails sent by the third-party service to the proxy email address is disabled.

[0228] Figure 8G The settings interface 810 is shown, and the forwarding of emails sent by third-party services to the proxy email address has been disabled. Figure 8G As shown, option 820 has a changed appearance to indicate that forwarding of emails has been disabled.

[0229] Figure 9900 is a flow chart illustrating a method for creating an account for a service using an electronic device according to some embodiments. Method 900 is performed at a device having a display device (e.g., 100, 300, 500, 600a, 600b, 600c, 600d). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0230] In some embodiments, the electronic device is a computer system. The computer system optionally communicates (e.g., wired communication, wireless communication) with a display generation component (e.g., display, touch-sensitive display) and one or more input devices (e.g., touch-sensitive surface). 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. One or more input devices are configured to receive input, such as a touch-sensitive surface that receives user input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separated from the computer system. Therefore, the computer system can send 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 (e.g., using a display device), and can receive input from one or more input devices via a wired or wireless connection.

[0231] As described below, method 900 provides an intuitive way to create an account for a service. This method reduces the user's cognitive burden by reducing the amount of information required to create an account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to enter less information saves power and increases the time between battery charges.

[0232] The electronic device receives (902) a request to create an account for a first service (e.g., a website, an application) (e.g., input 603 on enable indication 608, input 605 on enable indication 612, input 609 on enable indication 616) (e.g., a tap on a “Continue” enable indication).

[0233] In response to receiving a request to create an account for a first service, the electronic device simultaneously displays (904) a first login option (e.g., 628) (e.g., a “Share my email” option) and a second login option (e.g., 630) (e.g., a “Hide my email” option) via a display device.

[0234] The electronic device detects (906) a set of one or more inputs (e.g., 615) (e.g., a tap on one of the options and, optionally, a subsequent tap on the continue enable indication).

[0235] In response to (908) detecting the set of one or more inputs, based on determining that the set of one or more inputs corresponds to selection of a first login option, the electronic device transmits (910) a request to create an account for the first service using the user's first contact information (e.g., an email address).

[0236] In response to detecting the set of one or more inputs (e.g., 615) at (908), based on determining that the set of one or more inputs corresponds to selecting a second login option, the electronic device transmits (912) a request to create an account for the first service using the user's second contact information (e.g., a proxy email address), wherein the second contact information is automatically generated for the service and does not reveal the user's first contact information (e.g., the user's email address is hidden behind the proxy email address). Selectively transmitting the user's personal contact information or the automatically generated contact information that does not reveal the user's personal contact information enables the device to selectively share the user's personal contact information only with approved recipients, thereby improving security. Selectively transmitting the user's personal contact information to approved recipients improves the security of the device by preventing the user's personal contact information from being shared with unintended recipients. In addition, selectively transmitting the user's personal contact information to approved recipients while transmitting the automatically generated contact information to other recipients alleviates the need for the user to manually enter different contact information for different recipients, thereby reducing the number of inputs required to perform an operation. Reducing the number of inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, by reducing false negatives in authentication), 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.

[0237] In some embodiments, in response to (or subsequently to) receiving a request to create an account for a first service, the electronic device displays a default name for the account (e.g., 636) via a display device (e.g., the name of the user retrieved from the user's contact profile (locally or from a remote server), i.e., the user's real name). In some embodiments, the default name is not displayed unless the first service requests the name. In some embodiments, while displaying the default name for the account, the electronic device detects a second set of one or more inputs (e.g., 619, 621) (e.g., a tap on the default name). In some embodiments, in response to detecting the second set of one or more inputs, based on determining that the second set of one or more inputs corresponds to selecting the default name, the electronic device displays an editing interface for the name of the account (e.g., 610e). In some embodiments, while in the editing interface for the name of the account, the device receives user input to modify the name for the account (e.g., using an alphabetic keyboard to modify the default name) and / or user input to select from a predetermined list of name options for the account (e.g., different abbreviations of the user's name (e.g., Jane Appleseed, J. Appleseed, Jane A.)). Providing an interface for editing a user's name enables the device to selectively share the user's real name only with approved recipients, thereby improving security. Selectively sharing the user's real name with approved recipients improves device security by preventing the user's real name from being shared with unintended recipients.

[0238] In some embodiments, in response to (or subsequently to) receiving a request to create an account for a first service, the electronic device displays an affordance (e.g., 638) (e.g., an "x" icon) for clearing the name used for the account simultaneously with a default name for the account (e.g., 636) (e.g., the user's real name). In some embodiments, in response to detecting a second set of one or more inputs (e.g., 619, 621), based on determining that the second set of one or more inputs corresponds to selecting the default name (e.g., 636) (e.g., a tap on the default name), the electronic device displays the default name (e.g., the default name is pre-populated in the editing interface and can be edited) in a name field (e.g., 640, 642) of the editing interface as part of an editing interface for the name of the account (e.g., 610a). In some embodiments, in response to detecting the second set of one or more inputs, based on determining that the second set of one or more inputs corresponds to an affordance (e.g., 638) selected to clear the name used for the account (e.g., a tap on an "x" icon), the electronic device displays an editing interface for the name of the account without displaying a default name in the name field (e.g., 640, 642) of the editing interface (e.g., the editing interface displays an empty field for entering a new name). Providing an interface for editing the user's name enables the device to selectively share the user's real name only with approved recipients, thereby improving security. Selectively sharing the user's real name with approved recipients improves the security of the device by preventing the user's real name from being shared with unintended recipients.

[0239] In some embodiments, in response to detecting the first portion of the set of one or more inputs and before transmitting a request to create an account for the first service using the first contact information or the second contact information, based on determining that the first portion of the set of one or more inputs corresponds to selecting a first login option, the electronic device displays multiple contact information of the user (e.g., 646) (e.g., multiple email addresses of the user, the first contact information with one or more other contact information, an alternative email address). In some embodiments, while displaying the multiple contact information of the user, a second portion of the set of one or more inputs is detected, the second portion of the set of one or more inputs corresponding to selecting the first contact information (e.g., corresponding to a tap on an enable representation of the first contact information, the enable representation being displayed simultaneously with one or more other enable representations for one or more other corresponding alternative contact information (e.g., an alternative email address)).

[0240] In some embodiments, the electronic device receives a second request to create an account for a second service (e.g., a second website, a second application). In some embodiments, in response to receiving the second request to create an account for the second service, based on determining that a request to create an account for the first service using the user's first contact information was transmitted in response to receiving the request to create an account for the first service, the electronic device simultaneously displays a first login option with a selection indicator (e.g., 634) (e.g., the first login option is emphasized, a check mark for the Share My Email option is pre-selected) and a second login option without a selection indicator (e.g., the second login option is not emphasized). In some embodiments, the second login option for creating an account for the second service corresponds to an option for requesting to create an account for the first service using the user's third contact information (different from the first contact information and the second contact information) (e.g., a proxy email address). In some embodiments, the third contact information is automatically generated for the second service and does not reveal the user's first contact information (e.g., the user's email address is hidden behind the proxy email). In some embodiments, in response to receiving a second request to create an account for a second service, based on determining that a request to create an account for the first service using the user's second contact information was transmitted in response to receiving a request to create an account for the first service, the electronic device simultaneously displays the first login option without a selection indicator and the second login option with a selection indicator (e.g., 634) (e.g., the second login option is emphasized and a check mark for the Hide My Email option is pre-selected). Preselecting a login option based on which login option was previously selected alleviates the need for the user to manually select a login option, thereby reducing the number of inputs required to perform an operation. Reducing the number of inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, by reducing false negatives of authentication), 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.

[0241] In some embodiments, before receiving a request to create an account for the first service, a request to access (e.g., log in to the first service, create a new account for the first service) the first service is received. In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device displays alternative account information for the first service (e.g., 668) (e.g., other email addresses previously used to log in to the service, existing accounts for the first service). In some embodiments, the alternative account information includes: an indication of the credential type of the alternative account information (e.g., account login name, account email address) and an indication of the credential source of the alternative account information (e.g., whether the credential was saved due to logging in on a website, whether the credential was saved due to logging in in a specific application, whether the credential is stored in a local / remote credential repository). In some embodiments, while displaying the alternative account information, a request to create an account for the first service is received.

[0242] In some embodiments, after transmitting a request to create an account for the first service using the user's second contact information (e.g., a proxy email address), the electronic device (e.g., in response to the user's request to access a settings interface) displays a settings interface (e.g., 810) (e.g., for the first service) that includes the user's second contact information (e.g., 818) (e.g., "The application receives: [scrambled]@domain.com") (in some embodiments, the second contact information can be copied to other interfaces (e.g., tapping the second contact information to save the second contact information to the device's clipboard).

[0243] In some embodiments, the second contact information is an intermediate email address (e.g., a proxy email address) configured to forward received emails to the user's email address (e.g., forwarded to the first contact information). In some embodiments, when the user has multiple email addresses, emails are forwarded to the user's primary email address.

[0244] In some embodiments, the electronic device (e.g., in response to a user request to access a settings interface) displays a settings interface (e.g., 704a, 704b) having an intermediate email address (e.g., a proxy email address) configured to forward the received email to the email address (e.g., first contact information) of a user (e.g., 706). In some embodiments, the electronic device detects a fourth set of one or more inputs (e.g., 703, 705) to modify the user's email address. In some embodiments, the electronic device (e.g., in response to a user request (e.g., a tap of an enable indication)) transmits a request to update the intermediate email address (e.g., a proxy email address) to forward the email to the user's modified email address (instead of forwarding it to the user's initial email address). In some embodiments, all intermediate email addresses associated with the user (e.g., proxy email addresses used with other services or accounts) are updated to forward the email to the modified email address. Updating all intermediate email addresses to forward the email to the modified email address alleviates the need for the user to manually change the email settings for each service, thereby reducing the number of inputs required to perform the operation. Reducing the number of inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, by reducing false negatives in authentication), 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.

[0245] In some embodiments, after transmitting a request to create an account for the first service using the user's second contact information (e.g., a proxy email address), the electronic device displays a settings interface (e.g., 810) with a disable enable indication (e.g., 820) (e.g., in response to a sequence of one or more inputs including a user request to access the settings interface and, optionally, a request to navigate within the settings interface). In some embodiments, the electronic device detects an input corresponding to the disable enable indication (e.g., 815). In some embodiments, in response to detecting the input corresponding to the disable enable indication, the electronic device transmits a request to stop using the user's second contact information (e.g., the proxy email address) for an account with the first service (and optionally, (e.g., alternatively) using the user's first contact information (e.g., the user's email address) for an account with the first service). Stopping the use of the proxy email address for emails sent for the first service alleviates the need for the user to log in to the service to change email preferences or opt out of receiving emails from the first service, thereby reducing the number of inputs required to perform the operation. Reducing the number of inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, by reducing false negatives in authentication), 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.

[0246] In some embodiments, the electronic device displays information (e.g., 804, 810) corresponding to the first service (e.g., 806b) (e.g., an application list, an application settings page). In some embodiments, the electronic device (e.g., while displaying information corresponding to the first service) detects a fifth set of one or more inputs (e.g., 803, 808, 811) that corresponds to a request to disable the account used for the first service (e.g., a swipe gesture, disabling the switching indication). In some embodiments, in response to detecting the fifth set of one or more inputs, the electronic device disables the account used for the first service (e.g., permanently deleting the account, temporarily disabling the account, deleting information corresponding to the first service (e.g., no longer displaying information corresponding to the first server, transmitting an instruction to no longer forward emails).

[0247] In some embodiments, prior to receiving a request to create an account for the first service, the electronic device receives a request to access the first service (e.g., log in to the first service, create a new account for the first service). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device displays a change account affordance (e.g., 618). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device detects input corresponding to the change account affordance (e.g., 611). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), in response to detecting the input corresponding to the change account affordance, the electronic device displays an interface for selecting a login account for the user (e.g., another email address for the user). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), in response to detecting the input corresponding to the change account affordance: the electronic device detects a sixth set of one or more inputs for selecting a login account for the user (e.g., entering a user ID, a password, an authentication code for another ID). In some embodiments, after detecting a sixth set of one or more inputs selecting a login account for the user, a request to create an account for the first service is received. In some embodiments, the first contact information corresponds to contact information of the selected login account (e.g., an email address of the newly selected account).

[0248] In some embodiments, before receiving a request to create an account for the first service, the electronic device receives a request to access (e.g., log in to the first service, create a new account for the first service) the first service. In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device detects a security issue (e.g., email not verified, two-factor authentication not enabled, terms and conditions not accepted). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device displays (e.g., based on detecting the security issue) an interface for correcting the security issue (e.g., 626). In some embodiments, in response to receiving the request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device detects (after displaying the interface for correcting the security issue) a seventh set of one or more inputs for correcting the security issue.

[0249] In some embodiments, after detecting a seventh set of one or more inputs to correct the security questions, a request to create an account for the first service is received (e.g., tapping on a "Continue" enable indication after correcting the security questions).

[0250] In some embodiments, the request to create an account for the first service is received from the second device (e.g., 600d) (e.g., transmitted from a television).

[0251] In some embodiments, a request to create an account for a first service is received from a web browser (e.g., 648) displaying a website (e.g., 604). In some embodiments, the first login option and the second login option are displayed as an overlay (e.g., obscuring) at least a portion of the website (e.g., the login options are not received as part of the website page). In some embodiments, the overlay includes instructions (e.g., 632) for providing biometric authentication information (e.g., presenting a fingerprint to a fingerprint reader or presenting a face to a facial detection sensor such as a visible light camera and / or a depth camera).

[0252] In some embodiments, a request to create an account for the first service is received from a web browser displaying a website (e.g., 650). In some embodiments, the first login option and the second login option are displayed on a second website (e.g., a website with separate login pages). In some embodiments, the second website is owned and / or operated by the same entity or a related entity as the entity that provided the user's contact information to the first service, and the first login option and the second login option authenticate the user with the entity.

[0253] In some embodiments, the electronic device detects a request to access the first service (e.g., logging into a page of an application or website). In some embodiments, in response to detecting the request to access the first service, the electronic device displays an enable indication for logging into the first service (e.g., 664). In some embodiments, the electronic device detects an input corresponding to an enable indication for logging into the first service (e.g., 631). In some embodiments, in response to detecting an input corresponding to an enable indication for logging into the first service, the electronic device accesses the first service (e.g., accesses account-specific information) using an account created for the first service.

[0254] In some embodiments, before transmitting the request to use the first contact information or the second contact information, the electronic device performs user authentication. In some embodiments, user authentication is performed using facial recognition. In some embodiments, user authentication is performed using fingerprint recognition. In some embodiments, user authentication is performed using a password (e.g., when using a watch or other wearable device).

[0255] For the purpose of explanation, the foregoing description is described with reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Many modifications and variations are possible based on the above teachings. These embodiments have been selected and described in order to best explain the principles of these techniques and their practical applications. Others skilled in the art will thus be able to best utilize these techniques and various embodiments with various modifications suitable for the specific purposes contemplated.

[0256] Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will 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 present disclosure and examples defined by the claims.

[0257] As mentioned above, one aspect of the present technology is the collection and use of data that can be obtained from various sources to create accounts for services. The present disclosure contemplates that, in some instances, such 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 number, email address, Twitter ID, home address, date of birth, or any other identifying or personal information.

[0258] The present disclosure recognizes that the use of such personal information data in the disclosed technology can be used to benefit users. For example, personal information data can be used to improve the process for creating accounts for services. In addition, the present disclosure also anticipates other uses of personal information data that benefit users.

[0259] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or 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. Such policies should be easily accessible to users and updated as the collection and / or use of data changes. Personal information collected from users should be used for the entity's legitimate and reasonable purposes and not shared or sold beyond those legitimate uses. Furthermore, such collection / sharing should be conducted with the user's informed consent. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to such personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific type of personal information collected and / or accessed, and to applicable laws and standards, including jurisdiction-specific considerations. Therefore, different privacy practices should be maintained for different types of personal information in each country.

[0260] Regardless of the foregoing, the present disclosure also contemplates implementations in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with respect to a user's name or email address, the disclosed technology can be configured to allow a user to "opt in" or "opt out" of sharing personal information data at any time during or after registration for a service. 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 can be notified when creating an account for a service that their personal information data will be shared with the service.

[0261] Furthermore, 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. Risk can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, 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 the address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods, where appropriate.

[0262] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that various embodiments may be implemented without access to such personal information data. That is, various embodiments of the disclosed technology will not be unable to function properly due to the lack of all or part of such personal information data.

Claims

1. A method comprising: At a computer system in communication with a display generating component and one or more input devices: concurrently displaying, via the display generating component, a plurality of representations corresponding to a plurality of applications using a login service, the plurality of representations including a representation of a first application and a representation of a second application different from the first application; detecting, while displaying representations of the plurality of applications, via the one or more input devices, an input directed to a respective one of the plurality of representations, wherein the respective one of the plurality of applications corresponds to a respective one of the plurality of applications; In response to detecting the input directed to the corresponding representation: displaying a user interface for the first application for managing the login service based on determining that the input is a first gesture directed to the first application; Based on determining that the input is a second gesture different from the first gesture directed to a representation of the first application, a process of stopping the first application from utilizing the login service is initiated.

2. The method according to claim 1, further comprising: In response to detecting the input directed to the corresponding representation: Based on determining that the input is the first gesture directed to the representation of the second application, a user interface for the second application for managing the login service is displayed.

3. The method according to any one of claims 1 to 2, further comprising: while displaying the user interface for the first application for managing the login service, detecting a second input directed to a selectable user interface element in the user interface for the first application for managing the login service; as well as In response to detecting the second input, a process is initiated to stop the first application from using the login service.

4. The method according to any one of claims 1 to 2, wherein: The plurality of representations also includes a representation of a third application; and The process of starting and stopping the first application from using the login service includes: An enabling representation for stopping the first application from using the login service is displayed, while maintaining the display of the representation of the second application and the representation of the third application.

5. The method according to any one of claims 1 to 2, wherein: The first gesture is a tap gesture; and The second gesture is a swipe gesture.

6. The method according to any one of claims 1 to 2, wherein The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping the first application from using the login service.

7. The method according to any one of claims 1 to 2, wherein The user interface for the first application for managing the login service includes an email address associated with an account for the first application.

8. The method according to claim 7, wherein: The user interface for the first application for managing the login service also includes a proxy email address that is different from the email address, the proxy email address associated with the account for the first application.

9. The method according to claim 8, wherein The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping forwarding emails received at the proxy email address to the email address.

10. The method according to any one of claims 1 to 2, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process for reviewing a privacy policy associated with the first application.

11. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: concurrently displaying, via the display generating component, a plurality of representations corresponding to a plurality of applications using a login service, the plurality of representations including a representation of a first application and a representation of a second application different from the first application; While displaying representations of the plurality of applications, detecting, via the one or more input devices, input directed to a corresponding representation of the plurality of representations, wherein the respective representations corresponding to respective applications among the plurality of applications; In response to detecting the input directed to the corresponding representation: displaying a user interface for the first application for managing the login service based on determining that the input is a first gesture directed to the first application; Based on determining that the input is a second gesture different from the first gesture directed to a representation of the first application, a process of stopping the first application from utilizing the login service is initiated.

12. The computer-readable storage medium of claim 11, wherein: The one or more programs also include instructions for: In response to detecting the input directed to the corresponding representation: Based on determining that the input is the first gesture directed to the representation of the second application, a user interface for the second application for managing the login service is displayed.

13. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The one or more programs also include instructions for: while displaying the user interface for the first application for managing the login service, detecting a second input directed to a selectable user interface element in the user interface for the first application for managing the login service; as well as In response to detecting the second input, a process is initiated to stop the first application from using the login service.

14. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The plurality of representations also includes a representation of a third application; and The process of starting and stopping the first application from using the login service includes: An enabling representation for stopping the first application from using the login service is displayed, while maintaining the display of the representation of the second application and the representation of the third application.

15. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The first gesture is a tap gesture; and The second gesture is a swipe gesture.

16. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping the first application from using the login service.

17. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The user interface for the first application for managing the login service includes an email address associated with an account for the first application.

18. The computer-readable storage medium according to claim 17, wherein: The user interface for the first application for managing the login service also includes a proxy email address that is different from the email address, the proxy email address associated with the account for the first application.

19. The computer-readable storage medium according to claim 18, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping forwarding emails received at the proxy email address to the email address.

20. The computer-readable storage medium according to any one of claims 11 to 12, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process for reviewing a privacy policy associated with the first application.

21. A computer system comprising: Display generated components; 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 performing the following operations: concurrently displaying, via the display generating component, a plurality of representations corresponding to a plurality of applications using a login service, the plurality of representations including a representation of a first application and a representation of a second application different from the first application; detecting, while displaying representations of the plurality of applications, via the one or more input devices, an input directed to a respective one of the plurality of representations, wherein the respective one of the plurality of applications corresponds to a respective one of the plurality of applications; In response to detecting the input directed to the corresponding representation: displaying a user interface for the first application for managing the login service based on determining that the input is a first gesture directed to the first application; Based on determining that the input is a second gesture different from the first gesture directed to a representation of the first application, a process of stopping the first application from utilizing the login service is initiated.

22. The computer system of claim 21, wherein: The one or more programs also include instructions for: In response to detecting the input directed to the corresponding representation: Based on determining that the input is the first gesture directed to the representation of the second application, a user interface for the second application for managing the login service is displayed.

23. The computer system according to any one of claims 21 to 22, wherein: The one or more programs also include instructions for: while displaying the user interface for the first application for managing the login service, detecting a second input directed to a selectable user interface element in the user interface for the first application for managing the login service; as well as In response to detecting the second input, a process is initiated to stop the first application from using the login service.

24. The computer system according to any one of claims 21 to 22, wherein: The plurality of representations also includes a representation of a third application; and The process of starting and stopping the first application from using the login service includes: An enabling representation for stopping the first application from using the login service is displayed, while maintaining the display of the representation of the second application and the representation of the third application.

25. The computer system according to any one of claims 21 to 22, wherein: The first gesture is a tap gesture; and The second gesture is a swipe gesture.

26. The computer system according to any one of claims 21 to 22, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping the first application from using the login service.

27. The computer system according to any one of claims 21 to 22, wherein: The user interface for the first application for managing the login service includes an email address associated with an account for the first application.

28. The computer system according to any one of claims 27, wherein: The user interface for the first application for managing the login service also includes a proxy email address that is different from the email address, the proxy email address associated with the account for the first application.

29. The computer system according to any one of claims 28, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process of stopping forwarding emails received at the proxy email address to the email address.

30. The computer system according to any one of claims 21 to 22, wherein: The user interface for the first application for managing the login service includes a selectable option for initiating a process for reviewing a privacy policy associated with the first application.

31. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Device for carrying out the method according to any one of claims 1 to 10.

32. 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 according to any one of claims 1 to 10.

Images