User interface for accessing an account

Abstract

The present disclosure provides a user interface for accessing an account. The present disclosure generally relates to creating an account for a service. 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 an input selecting the first login option is detected, a request to create an account for the first service using first contact information of a user is transmitted. If an input selecting the second login option is detected, a request to create an account for the first service using second contact information of the user is transmitted. The second contact information is automatically generated for the service and does not reveal the first contact information of the user.

Description

[0001] Division Statement

[0002] This application is a divisional application of the China Invention Patent Application No. 202080040618.4, with the title of “User Interface for Accessing an Account”, filed on May 30, 2020. TECHNICAL FIELD

[0003] The present disclosure relates generally to computer user interfaces, and more particularly to user interfaces for creating an account for a service. BACKGROUND

[0004] Services, such as applications or websites, use user accounts to identify users using the application or website. In many cases, the application or website provides customized information to the user based on the user account. SUMMARY

[0005] However, some techniques for creating an account for a service using an electronic device are often cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that can include manually entering a user’s contact information in multiple keystrokes or key presses. As another example, some existing techniques expose a user’s personal information, such as the user’s email address, to the service. Existing techniques require more time than is necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0006] Accordingly, the present technology provides electronic devices with faster, more efficient methods and interfaces for creating an account for a service. Such methods and interfaces optionally supplement or replace other methods for creating an account. Such methods and interfaces reduce the cognitive burden placed on the user and produce a more efficient human-machine interface. For battery- powered computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0007] Example methods are disclosed herein. One example method includes, at an electronic device with a display device: receiving a request to create an account for a first service; in response to receiving the request to create the account for the first service, concurrently 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: in accordance with a determination that the set of one or more inputs corresponds to a selection of the first login option, transmitting a request to create the account for the first service using first contact information of a user; and in accordance with a determination that the set of one or more inputs corresponds to a selection of the second login option, transmitting a request to create the 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 expose 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 with a display, the one or more programs including instructions for: receiving a request to create an account for a first service; in response to receiving the request to create the account for the first service, concurrently displaying, via the display: 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: in accordance with a determination that the set of one or more inputs corresponds to a selection of the first login option, transmitting a request to create the account for the first service using first contact information of the user; and in accordance with a determination that the set of one or more inputs corresponds to a selection of the second login option, transmitting a request to create the 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 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 with a display, the one or more programs including instructions for: receiving a request to create an account for a first service; in response to receiving the request to create the account for the first service, concurrently displaying, via the display: 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: in accordance with a determination that the set of one or more inputs corresponds to a selection of the first login option, transmitting a request to create the account for the first service using first contact information of the user; and in accordance with a determination that the set of one or more inputs corresponds to a selection of the second login option, transmitting a request to create the 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] This document describes an example electronic device. 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 selecting 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 selecting the second login option, transmitting a request to create an account for the first service using a 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.

[0011] An example electronic device includes a display device; means for receiving a request to create an account for a first service; means 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; means for detecting a group of one or more inputs; and means for performing the following operations in response to detecting the group of one or more inputs: transmitting a request to create an account for the first service using a user's first contact information based on determining that the group of one or more inputs corresponds to selecting the first login option; and transmitting a request to create an account for the first service using a user's second contact information based on determining that the group of one or more inputs corresponds to selecting the second login option, 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.

[0013] Therefore, faster and more efficient methods and interfaces are provided for devices to create accounts for services, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. These methods and interfaces can complement or replace other methods used for account creation. Attached Figure Description

[0014] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals indicate corresponding parts in all the drawings.

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

[0016] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0017] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0018] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

[0019] Figure 4A An exemplary user interface for a menu on an application on a portable multifunction device, according to some implementation schemes, is shown.

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

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

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

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

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

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

[0026] Figure 9 This is a flowchart illustrating a method for creating an account for a service using an electronic device, according to some implementation schemes. Detailed Implementation

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

[0028] There is a need for electronic devices that provide 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 using multiple keystrokes or button presses. In contrast, the technology disclosed herein can improve productivity by reducing the cognitive burden on users by decreasing the amount of information required to create an account. Furthermore, such technologies can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0029] under Figures 1A-1B , Figure 2 , Figure 3 , Figures 4A-4B and Figures 5A-5B A description is provided of an exemplary device used to perform techniques for creating accounts for services. Figures 6A-6W An exemplary user interface for creating an account for the service is shown. Figures 7A-7B An exemplary user interface for managing contact information associated with a service is shown. Figures 8A-8G An exemplary user interface for viewing and managing settings for the service is shown. Figure 9 This is a flowchart illustrating a method for creating an account for a service according to some implementation schemes. Figures 6A-6W , Figures 7A-7B ,and Figures 8A-8G The user interface in the document is used to illustrate the processes described below, including... Figure 9 The process in.

[0030] Although the following description uses the terms "first," "second," etc., to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. 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 described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

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

[0032] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "in response to," or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determining..." or "in response to detecting [the stated condition or event]."

[0033] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). In some embodiments, the electronic device is a computer system that communicates with a display generating component (e.g., via wireless or wired communication). The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate from the computer system. As used herein, “display” content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) to an integrated or external display generating component via a wired or wireless connection to visually generate content.

[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 may optionally include 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: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0036] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the 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 device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0037] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral 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 an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 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 contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of 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 tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on smaller devices with limited physical space, such smaller devices being used (e.g., on a touch-sensitive display) to display power indications 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 "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific 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 its components that will generate the sensory perception of a typical (or ordinary) user.

[0040] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

[0041] Memory 102 optionally includes high-speed random access memory and also 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 other components of device 100 to access memory 102.

[0042] Peripheral interface 118 can 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, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0043] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, 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 circuit 108 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ 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, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit 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), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE...). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

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

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

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

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

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

[0049] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that from Apple Inc. (Cupertino, California). and iPod The technology used.

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

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

[0052] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally interact with touchscreen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

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

[0054] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0055] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an 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, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0056] The 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 I / O subsystem 106. Depth camera sensor 175 receives data from the environment to create a 3D model of an object (e.g., a face) within the scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 may optionally be used to determine depth maps of different portions of an image captured by imaging module 143. In some embodiments, the depth camera sensor is located at the front of device 100, such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touchscreen display, and selfies with depth map data are captured. In some embodiments, depth camera sensor 175 is located at the rear of the device, or both the rear and front of device 100. In some embodiments, the position of depth camera sensor 175 may be changed by the user (e.g., by rotating a lens and sensor within the device housing), such that depth camera sensor 175 is used in conjunction with a touchscreen display for both video conferencing and still image and / or video image acquisition.

[0057] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1AA contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0058] The device 100 optionally also includes one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform 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", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0059] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic 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 haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0060] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform 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 on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of 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 program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or orientation.

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

[0063] The communication module 128 facilitates communication with other devices via one or more external ports 124 and 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 adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

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

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

[0066] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event and then detecting a finger lift-off (lift-away) event at the same (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 a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

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

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

[0069] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0070] Optionally, the text input module 134, a component of the 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 that requires text input).

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

[0072] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets 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] • Camera module 143 for still images 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] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user, and desktop mini-programs created by the user 149-6;

[0086] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0087] • Search module 151;

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

[0089] • Notepad module 153;

[0090] • Map module 154; and / or

[0091] • Online video module 155.

[0092] Examples of other applications 136 that may be 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, speech recognition, and speech duplication.

[0093] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., in the application internal state 192 of the contact module 137 stored 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] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0095] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0096] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / 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 commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0097] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0098] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0099] In conjunction with the touchscreen 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: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

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

[0101] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

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

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

[0104] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

[0105] In conjunction with the touchscreen 112, display controller 156, touch / 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) according to user instructions.

[0106] Incorporating touchscreen 112, display controller 156, touch / 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 allowing users to download and play 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 touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0107] Combining the touchscreen 112, display controller 156, touch / 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 items, etc., according to user instructions.

[0108] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

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

[0110] Each of the above modules and applications 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., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the aforementioned modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0111] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or 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 can be optionally reduced.

[0112] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu. In such embodiments, a touchpad 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 touchpad.

[0113] Figure 1B This 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 This includes an event classifier 170 (e.g., in 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 application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information should be delivered.

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

[0116] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device 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 circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

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

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

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

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

[0121] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which 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 forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0122] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0123] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the 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 (such as contact / motion module 130) stored in memory 102.

[0125] In some implementations, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring 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 a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are 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 implementations, 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 handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more 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] The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0127] Event receiver 182 receives event information from event classifier 170. The event information includes information about sub-events, such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves touch movement, 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 longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0128] Event comparator 184 compares event information with predefined event or sub-event definitions 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, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as 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 of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0129] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the 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 the event handler associated with the sub-event and the object that triggered the hit test.

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

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

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

[0133] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

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

[0135] In some implementations, 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 implementations, 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 touch-sensitive display.

[0136] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, 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 implementations, they are included in two or more software modules.

[0137] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0138] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen 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 graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0140] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed 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 another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0141] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one mentioned above)) are described. Figure 1A The contact strength sensor 165 is described above. 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 disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

[0142] Figure 3Each of the elements described above is optionally stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to an instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subgroup of the modules and data structures described above. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0143] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

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

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

[0146] • Time 404;

[0147] Bluetooth indicator 405;

[0148] • Battery status indicator 406;

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

[0150] The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages.

[0151] The email client module 140 has an icon 418 labeled "Mail" which optionally includes an indicator 410 for the number of unread emails.

[0152] The browser module 147 has an icon 420 labeled "Browser"; and

[0153] o Video and music player module 152 (also known as iPod module 152, a trademark of Apple Inc.) with icon 422 marked "iPod"; and

[0154] • Icons of other applications, such as:

[0155] o IM module 141's icon 424 labeled "Message";

[0156] The calendar module 148 has an icon 426 labeled "Calendar";

[0157] The image management module 144 has an icon 428 labeled "Photo".

[0158] The icon 430 of the camera module 143 is labeled "camera";

[0159] o The icon 432 of the online video module 155, which is labeled "Online Video";

[0160] The icon 434 in the oStock Market Desktop Mini Program 149-2 is labeled "Stock Market";

[0161] The icon 436 labeled "map" in the map module 154;

[0162] The icon 438 in the oWeather desktop mini-program 149-1 is labeled "Weather";

[0163] The icon labeled "Clock" in the o alarm clock desktop mini-program 149-4;

[0164] The icon 442 of the fitness support module 142 is labeled "fitness support";

[0165] The notepad module 153 has an icon 444 labeled "Notepad"; and

[0166] o A settings icon 446 labeled "Settings" is used to set up applications or modules, providing access to settings for device 100 and its various applications 136.

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

[0168] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0169] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450)). Figure 4B The spindle corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the middle, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 5A (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figures 1A-4B 451) and the display of a multi-functional device (e.g., Figure 5B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 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 may optionally be used for other user interfaces described herein.

[0170] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0171] Figure 1AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figure 1B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 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, meaning 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 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 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 incorporated herein by reference in its entirety.

[0173] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

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

[0175] In some examples, the input mechanism 508 is optionally a microphone. The personal electronic device 500 optionally includes various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which are operatively connected to the I / O section 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, which, when executed by one or more computer processors 516, cause the computer processor to perform the techniques described below, including process 900. Figure 3A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. 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 can 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 discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. Personal electronic devices are not limited to... Figures 5A-5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0177] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figure 3 , Figure 4B and Figure 1A A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[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 specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 4A The touchpad 355 or Figures 6A-6W When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of enabling direct interaction with user interface elements on the touchscreen display) Figures 7A-7B The touch-sensitive display system 112 or Figures 8A-8GIn some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's 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 over 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 away, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0180] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, a touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position is optionally based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0181] Optionally, the contact intensity on a touch-sensitive surface is characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button on a physical mouse or touchpad.

[0182] In some implementations, the deep press strength threshold corresponds to an intensity at which the device will perform an operation different from that typically associated with clicking a button on a physical mouse or touchpad. In some implementations, when a contact with a characteristic intensity lower than the light press strength threshold (e.g., and higher than the nominal contact detection strength threshold, where contacts lower than the nominal contact detection strength threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface, without performing the operation associated with the light press strength threshold or the deep press strength threshold. Generally, unless otherwise stated, these strength thresholds are consistent across different groups of user interface figures.

[0183] An increase in contact intensity from 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 intensity from 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 intensity from 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 intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

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

[0185] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with 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 percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact below the 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 below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, 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 the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0186] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0187] Now let’s turn our attention to the implementation of user interfaces (“UIs”) and associated processes on electronic devices (such as portable multifunction devices 100, 300 or 500).

[0188] Figure 9 An exemplary user interface for creating an account for a service, according to some implementation schemes, is shown. Figure 6A An exemplary user interface for managing contact information associated with a service, according to some implementation schemes, is shown. Figure 6A Exemplary user interfaces for viewing and managing settings for services, according to some implementation schemes, are shown. The user interfaces in these figures are used to illustrate the following descriptions, including… Figure 6B The process of...

[0189] Figure 6C An electronic device 600a is shown, including 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 devices 100, 300, or 500. The electronic device 600a is configured to display a user interface provided by a first-party service (e.g., an application, website, or other service owned and / or operated by an entity attached to the electronic device) and a user interface provided by a third-party service (e.g., an application, website, or other service owned and / or operated by a second entity not attached to the electronic device). Figure 6B As 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 in to the 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 a capability representation 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 the first-party authentication provider 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. Furthermore, users can use the same authentication process as the first-party authentication provider (e.g., logging into the same account as the first-party provider and / or verifying the user's identity using biometric information known to the first-party authentication provider) to authenticate for multiple third-party services. In response to detecting input 603 corresponding to the indication 608 (e.g., a tap gesture), the user interface for the first-party authentication provider (e.g., such as...) Figure 6A or Figure 6B The user interface 610 shown is displayed.

[0190] Figure 6CA user interface 610a for a first-party authentication provider is shown, which includes information describing the first-party authentication provider (e.g., "Security and Protection", "Quick Login", "Subscription Email Management"). User interface 610a is displayed over a user interface 604 for third-party services (e.g., a portion of user interface 604 continues to be displayed concurrently with user interface 610a). In response to detecting input requesting the first-party authentication provider to create an account for third-party services (e.g., ... Figure 6B Input 603 is shown, which displays user interface 610a. In some embodiments, user interface 604 is the user interface of a first computer application, and user interface 610 is the 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 6C As shown. In some implementations, 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; instead, it is displayed in response to detecting input requesting the first-party authentication provider to create or log in to an account used for the third-party service. Figure 6A The user interface 610b shown is shown.

[0191] like Figure 6C As shown, the user interface 610a includes an accept enable indicator 612 and a cancel enable indicator 614. In response to detecting input 605 corresponding to the accept enable indicator 612, information describing the first-party authentication provider stops displaying, and the following is displayed: Figure 6A The user interface 610b is shown. In response to detecting input 607 corresponding to the cancellation indication 614, the user interface 610a stops displaying and displays the user interface 604 for third-party services, such as... Figure 6C As shown (for example, user interface 610a stops covering user interface 604).

[0192] Figure 6B A user interface 610b for a first-party authentication provider is shown, including instructions for 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 6C The input 603 shown will display as follows: Figure 6D The user interface 610b is shown. In some embodiments, the information describing the first-party authentication provider is displayed in response to detection. Figure 6CAfter inputting 605 as shown and stopping the display, user interface 610b is displayed.

[0193] like Figure 6D As shown, user interface 610b includes a capability representation 616 for continuing the creation process with the indicated first-party authentication provider account. In some embodiments, user interface 610b also includes a capability representation 618 for changing to another first-party authentication provider account. In response to detecting input 609 corresponding to capability representation 616 (e.g., tap input), electronic device 600a continues the process for creating an account for third-party services using the first-party authentication provider. In some embodiments, in response to detecting input 609, electronic device 600a authenticates the user as an authorized user of the indicated first-party authentication provider account (e.g., the user is authorized to use an 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 implementations (e.g., when using facial recognition or fingerprint recognition to authenticate a user), device 600a remains logged into a first-party authentication provider account. For example, device 600a is logged into the first-party authentication provider account before the creation process begins, and remains logged into the first-party authentication provider account throughout the creation process.

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

[0195] In some implementations, in response to the detection of input 611 corresponding to the enable display 618 (e.g., a tap input), 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, the user interface 610b, as...Figure 6C The information shown includes, but also includes, instructions that another account is being used in conjunction with a first-party authentication provider (e.g., displaying another email address).

[0196] Figure 6C A notification 620 is shown requesting the user to correct the security issue after a security problem is detected with the indicated first-party authentication provider's account (e.g., unverified email address, invalid password, two-factor authentication not enabled, or failure to accept terms and conditions). In some implementations, in response to the detection of... Figure 6E The input 609 shown (and optionally, after authenticating the user) verifies the security of the indicated first-party authentication provider account. Notification 620 includes a enable indicator 622 and a disable indicator 624. In response to detecting input corresponding to the disable indicator 624 (e.g., a tap), notification 620 stops displaying, and a message such as... Figure 6E The user interface 610 is shown. From Figure 6F The user interface 610 shown allows access to another first-party authentication provider account (e.g., an account without security issues) or the cancellation of the process of creating an account for third-party services using a first-party authentication provider. In response to detecting input 613 corresponding to a setting enablement indicator (e.g., a tap), a security interface for correcting security issues (e.g., such as...) is displayed. Figure 6A The security interface shown is 626.

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

[0198] Figure 6B A user interface 610c for a first-party authentication provider, including login options 628 and 630, is shown. In some embodiments, in response to detecting input requesting the first-party authentication provider to create or log in to an account for third-party services (e.g., Figure 6C The input 603 shown will display as follows: Figure 6C The user interface 610c is shown. In some embodiments, the information describing the first-party authentication provider is displayed in response to detection. Figure 6FAfter the display stops upon input 605, user interface 610c is displayed. In some embodiments, user interface 610c is displayed in response to the detection of input 609 corresponding to a capability indicator 616 for continuing the creation process with the indicated first-party authentication provider account, such as... Figure 6G As shown. In some implementations, in response to detecting a request for contact information (e.g., the user's email) from a third-party service, the user interface 610c is displayed instead of... Figure 6F The user interface 610b shown is shown.

[0199] like Figure 6G As shown, user interface 610c includes login option 628 (e.g., "Share my email" option) and login option 630 (e.g., "Hide my email" option). User interface 610c also includes a power indicator 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, power indicator 632 is disabled (e.g., input on power indicator 632 will not continue the account creation process). In some embodiments, power indicator 632 is displayed in another manner to indicate that power indicator is disabled (e.g., displayed in a different color than when power indicator is enabled). If input corresponding to login option 628 is detected (e.g., tap input), the indication of that 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 an input corresponding to login option 630 is detected (e.g., 615, tap input), an indication of that selection is displayed, and as the account creation process continues, obscured contact information (e.g., an automatically generated proxy email address that does not reveal the user's personal email address) is transmitted to a third-party service.

[0200] Figure 6F This shows that when input 615 corresponding to login option 630 is detected (e.g., ... Figure 6H The user interface 610c follows (as shown). Figure 6A As shown, in response to the detection of input 615, an indication 634 of the selected login option is displayed. In some implementations, if the first-party authentication provider has previously been used to create an account for third-party services, one of the login options 628 or 630 is pre-selected based on which login option was selected during the previous creation process (e.g., not displaying such an option). Figure 6HThe user interface 610c is shown. After login option 628 or 630 is selected, the power indicator 632 is enabled (e.g., input on the power indicator 632 continues the account creation process). In some embodiments, the power indicator 632 is displayed in another manner to indicate that the power indicator is enabled (e.g., displayed in a different color than when the power indicator is disabled). In response to detecting input 617 corresponding to the power indicator 632 (e.g., tap input), the electronic device 600a uses contact information corresponding to the selected login option to continue the process for creating an account for third-party services. In some embodiments, in response to detecting input 617, the electronic device 600a authenticates the user as 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 implementations, electronic device 600a authenticates a 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.

[0201] Figure 6B 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 third-party services (e.g., ...), Figure 6C The input 603 shown will display as follows: Figure 6C The user interface 610d is shown. In some embodiments, the information describing the first-party authentication provider is displayed in response to detection. Figure 6F After the input 605 is displayed and the display stops, the user interface 610d is displayed. In some embodiments, the user interface 610d is displayed in response to the detection of input 609 corresponding to the enablement indicator 616, which is used to continue the creation process with the indicated first-party authentication provider account, such as... Figure 6H As shown. In some implementations, in response to detecting a request from a third-party service for contact information (e.g., the user's email address) and the user's name, user interface 610d is displayed instead of... Figure 6I and Figure 6J The user interface shown is 610b or 610c.

[0202] like Figure 6JAs shown, in addition to login options 628 (e.g., "Share my email" option) and login options 630 (e.g., "Hide my email" option), the user interface 610d also includes a name field 636. The user interface 610d also includes a clear enablement 638 for clearing the account's name. When the user interface 610d is initially displayed, the name field 636 includes a default name (e.g., the user's name) associated with the user's first-party authentication provider account. If input corresponding to the name field 636 (e.g., input 621) or the clear enablement 638 (e.g., input 619) is detected (e.g., tap input), a user interface for editing the name (e.g., as shown) is displayed. Figure 6I and Figure 6I The interface 610e is shown. In some implementations, in response to detecting input 621 corresponding to name field 636, a default name is pre-populated in the user interface 610e, such as... Figure 6H As shown. In contrast, in some implementations, in response to detecting input 619 corresponding to clearing the enable display 638, the default name is cleared from the user interface 610e, such as... Figure 6J As shown.

[0203] Figure 6H User interface 610e is shown, in which the default name is cleared from the first name field 640 and the last name field 642. In some embodiments, the default name is cleared from user interface 610e in response to the detection of input 619 corresponding to the clear enable representation 638, such as... Figure 6H As shown. When no text is present in the first name field 640 and the last name field 642, the enablement representation 644, which is used to continue the account creation process for third-party services, is disabled (e.g., input on enablement representation 644 will not continue the account creation process until text is entered in the first name field 640 and the last name field 642). In some embodiments, enablement representation 644 is displayed in another way to indicate that the enablement representation is disabled (e.g., displayed in a different color than when the enablement representation is enabled).

[0204] Figure 6K 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 first name field 636, the default name is pre-populated in the first name field 640 and the last name field 642, as shown. Figure 6KAs shown. Pre-populating the first name field 640 and last name field 642 with a default name allows editing the default name without re-entering the entire name. When text is included in the first name field 640 and last name field 642, a power indicator 644 for continuing the account creation process for third-party services is enabled (e.g., input on the power indicator 644 will continue the account creation process). In some embodiments, the power indicator 644 is displayed in another way to indicate that the power indicator is enabled (e.g., displayed in a different color than when the power indicator is disabled). In response to detecting input 623 corresponding to the power indicator 644, the display of the user interface 610e stops, and the name entered in the first name field 640 and last name field 642 is displayed as shown. Figure 6L The user interface shown is 610d.

[0205] Figure 6K The user interface 610d is shown after detecting input corresponding to login option 628 (e.g., the "Share my email" option). In some implementations, such as Figure 6L 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 login option 628 (e.g., the "Share My Email" option is expanded to list alternative email address 646). In some implementations, an indication (e.g., a checkmark) is displayed to indicate which email address is currently selected for login option 628. In response to input 625 corresponding to alternative email address 646 (e.g., tapping the input), the email address to be used for login option 628 is changed.

[0206] Figure 6M The following is an example of how input 625, corresponding to an alternative email address, was detected. Figures 6A-6L (As shown in the image) The user interface 610d follows. Figures 6A-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 input corresponding to enable display 632, electronic device 600a continues the process of creating an account for third-party services using the contact information (e.g., alternative email address) corresponding to login option 628.

[0207] Figures 6A-6LAn electronic device 600b (e.g., a watch) is shown, including 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 devices 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 third-party services using a first-party authentication provider, as referenced. Figure 6N As described above. In some embodiments, the user interface 610f includes... Figure 6N Versions of the user interfaces 610a-610e shown have been modified for display via a small-format display device such as display device 602b. For example, user interfaces 610a-610e have been modified to be scrollable using a rotatable input device 675 and include elements selectable using the rotatable input device 675, but are otherwise provided for reference. Figures 6A-6L The same function.

[0208] Figures 6A-6L An electronic device 600c (e.g., a laptop computer) including a display device 602c is shown. In some embodiments, the electronic device 600c includes one or more features of devices 100, 300, or 500. The electronic device 600c displays a user interface 610g via the display device 602c, overlaying a user interface 604 for third-party services (e.g., a website). Figures 6A-6L 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 a web browser-native interface that overlays user interface 604 in the web browser. User interface 610g allows users to create accounts using the first-party authentication provider for third-party services (e.g., websites corresponding to user interface 604), as referenced. Figure 6O As described above. In some embodiments, the user interface 610g includes... Figure 6P Versions of user interfaces 610a-610e shown have been modified to display as a native interface for a web browser. For example, user interfaces 610a-610e have been modified to include elements selectable using a mouse and / or keyboard, but otherwise provided in accordance with the reference. Figure 6O The same function is described above. In some implementations, in response to the detection of an authorized fingerprint by a fingerprint sensor, an enablement representation 632 is activated for continuing the process of creating an account for third-party services using a first-party authentication provider.

[0209] Figure 6PAn electronic device 600c is shown displaying a 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 a display device 602c. The user interface 652 is displayed in response to a detected 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 before the user interface 652 is displayed, and the user interface 652 is displayed in response to a detected authorized login to an account with the authentication provider. The user interface 652 includes a capability representation 654 for continuing the process of creating an account for the service using the authentication provider. In response to the detection of input corresponding to the capability representation 654 (e.g., tapping an input, selection using a cursor), a verification code is transmitted to the device associated with the authentication provider account.

[0210] Figures 6A-6L This shows the detection of the corresponding indicator 654 (in Figure 6Q The user interface 652 follows the input (as shown in the image). Figure 6R As shown, user interface 652 includes a field 656 for entering a verification code transmitted to the device associated with the authentication provider's account. If the verification code authorizes the user, user interface 652 stops displaying, and the process for creating an account for the service using the authentication provider continues, as shown in the reference. Figure 6R As stated above.

[0211] Figure 6S An electronic device 600d (e.g., a television) is shown displaying a user interface 604 for third-party services (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. The user interface 604 includes a capability 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 the display device 602d, a user interface is displayed on a separate device (e.g., an electronic device 600a) associated with the user's authentication provider account. In response to detecting input corresponding to the capability representation 608 (e.g., 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.

[0212] Figure 6T The user interface 604 is shown after a 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 6TAs shown, the user interface 604 includes a notification 658 for continuing the process of creating an account with a third-party service using the authentication provider with the use of a separate device (e.g., electronic device 600a).

[0213] Figure 6T An electronic device 600a is shown displaying a notification 660 via a display device 602a regarding a request received from a separate device (e.g., electronic device 600d) to create an account with a third-party service using an authentication provider. In response to detecting input 627 corresponding to the notification 660 (e.g., a tap input), the electronic device displays a user interface 610h (such as...). Figure 6S (As shown), this is the process used on this separate device to continue creating accounts with third-party services using the authentication provider.

[0214] Figures 6A-6L A user interface 610h for an authentication provider is shown, which includes instructions for a separate device (e.g., electronic device 600d) requesting authentication from the provider, which is used to create an account for services on that separate device (e.g., “Log in to the streaming service on your TV using 'j.appleseed@email.com'”). In some implementations, such as Figures 6A-6L The user interface 610h shown responds to the detection of input 627 in a notification displayed in response to a request received from the separate device. Figures 6A-6L As shown in the figure. The user interface 610h allows users to utilize, as shown in the reference Figure 6U The authentication provider creates an account for services (e.g., video streaming applications) on that individual device. In some implementations, the user interface 610h includes a reference... Figure 6A The user interfaces 610a-610e have the same elements and provide the same reference. Figure 6U The user interfaces 610a-610e have the same functions.

[0215] Figure 6C An electronic device 600a is shown displaying a user interface 662a for a first-party authentication provider via a display device 602a. This is in response to detecting input requesting the first-party authentication provider to create or log in to an account for third-party services (e.g., ...). Figure 6VThe user interface 662a is displayed in response to the detection that the current user's first-party authentication provider account has previously been used to create an account for third-party services (e.g., the user previously created an account for third-party services using the first-party authentication provider on another device). The user interface 662a includes an indication of the first-party authentication provider account previously used to create the account for third-party services (e.g., "'j.appleseed@email.com' was previously used with this Unicorn application, would you like to log in?"). The user interface 662a also includes a capability indication 664 for continuing the login process using the indicated first-party authentication provider account and a capability indication 618 for changing to another first-party authentication provider account. In response to the detection of input 631 corresponding to capability indication 664 (e.g., tapping the input), the electronic device 600a continues the process of logging into the account previously created using the first-party authentication provider for third-party services. In some implementations, in response to the detection of input 631, electronic device 600a authenticates the user as 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 implementations, electronic device 600a uses facial recognition to authenticate the user. In some implementations, electronic device 600a uses fingerprint recognition to authenticate the user. In some implementations, 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 implementations, (e.g., when using facial recognition or fingerprint recognition to authenticate the user) device 600a remains logged into the first-party authentication provider account.

[0216] In some implementations, in response to the detection of input 633 corresponding to the enable input 618 (e.g., a tap input), 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 previously been used to create an account for third-party services, user interface 662a is displayed, such as... Figure 6W As shown, but including instructions for another account used with the first-party authentication provider (e.g., displaying another email address). If the new first-party authentication provider account has not been previously used to create an account for third-party services, user interface 610b is displayed, as shown. Figure 6V As shown, but includes instructions for another account used by the first-party authentication provider (e.g., displaying another email address).

[0217] In some implementation schemes, such asFigure 7A As shown, if multiple accounts are detected to have previously been used to log in to or create accounts for third-party services (e.g., the user previously created an account for third-party services on another device using a first-party authentication provider and / or previously logged in to an account for third-party services using credentials stored at (or accessible by) device 600a), then user interface 662b is displayed. User interface 662b includes account option 666 corresponding to the first-party authentication provider account previously used to create an account for third-party services. User interface 662b also includes account option 668 corresponding to credentials previously used to log in to an account for third-party services. User interface 662a also includes a capability representation 664 for continuing the login process using the indicated first-party authentication provider account or previously used login credentials. In some embodiments, capability representation 664 is disabled when account option 666 or 668 is not selected (e.g., input on capability representation 664 will not continue the account login process). In some implementations, the power indicator 664 is displayed in another manner to indicate that the power indicator is disabled (e.g., displayed in a different color than when the power indicator is enabled).

[0218] like Figure 6F As shown, in response to detecting input 635 corresponding to account option 666 (e.g. Figure 6G (As shown) (e.g., tapping the input), an indication 670 of the selected account option is displayed. In some embodiments, after selecting account option 666 or 668, the power indicator 664 is enabled (e.g., input on power indicator 632 will continue the account login process). In some embodiments, power indicator 664 is displayed in another manner to indicate that the power indicator is enabled (e.g., displayed in a different color than when the power indicator is disabled). In response to detecting input corresponding to power indicator 664, electronic device 600a logs in to an account for third-party services using the selected account option 666 or 668.

[0219] Figure 7B An electronic device 600a is shown displaying a contact information interface 704a via a display device 602a for accessing third-party services using a first-party authentication provider account. The contact information interface 704a includes a forwarding field 706, which indicates the email address to which an email received by a proxy email address is forwarded. During the creation process for the third-party service, when login option 630 (such as...) is used... Figure 7A and Figure 7AWhen the option (e.g., "Hide my email") is selected, a proxy email address is provided to a third-party service. In some implementations, all emails received by the proxy email address provided to the third-party service are forwarded to the email address indicated by the forwarding field 706. The email address to which the email is forwarded can be changed in response to an input 703 corresponding to the forwarding field 706 (e.g., a tap). Therefore, even though each third-party service receives a different obfuscated email address from the user, the user receives emails from each third-party service at a single email address (e.g., as indicated in the forwarding field 706).

[0220] like Figure 8A 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, forwarding email options 708 and 710 are displayed (e.g., ...). Figure 8B (As shown). 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 for the selected forward email option. In response to input 705 (e.g., 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 8C (As shown) is updated to indicate the currently selected email forwarding option 710. In response to selecting another email forwarding option 710, the proxy email address provided to the third-party service is updated to forward the email to the newly selected email address.

[0221] Figure 8B An 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 a capability indicator 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 input 803 (e.g., a swipe input) corresponding to the capability indicator 806a, the corresponding third-party service (such as...) can be removed from the settings interface 804. Figure 8A (As shown). In response to input 807 corresponding to the indication display 806b (e.g., tap input), additional settings and information for the corresponding third-party service are displayed (such as...). Figure 8C (As shown).

[0222] like Figure 8A As shown, in response to input 803 corresponding to the indicator 806a ( Figure 8DAs shown in the diagram (e.g., swiping input), a deletion enablement 808 for the corresponding third-party service is displayed. In response to input 805 corresponding to deletion enablement 808 (e.g., tapping input), the corresponding third-party service (e.g., "App1") is removed from the settings interface 804. In some implementations, removing the third-party service deletes any stored credentials used for the third-party service, preventing the first-party authentication provider from using them to log in to the account used for the third-party service without re-entering credentials or creating a new account. In some implementations, removing the third-party service stops emails from the third-party service from being forwarded to the user's email address (e.g., when the "Hide my email" option was selected during the account creation process for the third-party service).

[0223] Figure 8C An electronic device 600a is shown displaying a settings interface 810 for a third-party service (e.g., a "Unicorn application") via a display device 602a. In response to an input 807 corresponding to the power indicator 806b... Figure 8E (As shown in the image) (e.g., tapping the input field), a settings interface 810 is displayed. In some embodiments, the settings interface 810 includes a privacy capability representation 812, a terms capability representation 814, an option 816 for enabling or disabling first-party authentication providers, an indication 818 for a proxy email address for third-party services, and an option 820 for enabling or disabling the forwarding of emails sent to the proxy email address. In response to detecting input corresponding to privacy capability representation 812 (e.g., tapping the input field), information about the privacy policy for third-party services is displayed. In response to detecting input corresponding to terms capability representation 814 (e.g., tapping the input field), information about the terms and conditions for using third-party services is displayed. In some embodiments, in response to detecting input 809 corresponding to the indication 818 for a proxy email address for third-party services (e.g., tapping the input field, long press), the proxy email address is copied for pasting into a text field. In response to detecting input 811 corresponding to the option 816 for enabling or disabling first-party authentication providers (e.g., tapping the input field), the use of first-party authentication for third-party services is enabled or disabled. In response to the detection of input 815 (e.g., tapping input) corresponding to option 820 for enabling or disabling the forwarding of emails sent to the proxy email address by a third-party service, the forwarding of emails sent to the proxy email address is enabled or disabled.

[0224] like Figure 8E As shown, in some implementations, if the first-party authentication provider is enabled for third-party services, then in response to detecting input 811 corresponding to option 816 (…), Figure 8FAs shown), notification 822 confirms that the first-party authentication provider is disabled for the third-party service. Notification 822 includes a confirmation enablement expression 824 (e.g., "Delete") and a deactivation expression 826. In response to detecting input 813 corresponding to the confirmation enablement expression 824 (e.g., tapping the input), 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 used for the third-party service, preventing the first-party authentication provider from being used to log in to the account used for the third-party service without re-entering 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 the "Hide my email" option is selected during the account creation process for the third-party service).

[0225] Figure 8C The settings interface 810 is shown after disabling first-party authentication providers for third-party services. (Example) Figure 8G As shown, option 816 has a modified appearance to indicate that first-party authentication providers have been disabled for third-party services, and other settings for third-party services have stopped being displayed.

[0226] like Figure 8G As shown, in some implementations, if forwarding of emails sent to a proxy email address is enabled, then in response to detecting input 815 corresponding to option 820... Figure 9 As shown in the diagram, notification 828 disables the forwarding of emails sent by a third-party service to the proxy email address. Notification 828 includes a confirmation enablement expression 830 (e.g., "Stop") and a deactivation expression 832. In response to detecting input 817 corresponding to the confirmation enablement expression 830 (e.g., tap input), the forwarding of emails sent by the third-party service to the proxy email address is disabled.

[0227] ​ The settings interface 810 shows that forwarding of emails sent to the proxy email address by third-party services is disabled. (For example...) ​ As shown, option 820 has a modified appearance to indicate that email forwarding has been disabled.

[0228] ​This is a flowchart 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 (e.g., 100, 300, 500, 600a, 600b, 600c, 600d) having a display device. Some operations in method 900 are optionally combined, some operations are optionally changed in order, and some operations are optionally omitted.

[0229] In some embodiments, the electronic device is a computer system. The computer system optionally communicates with a display generating component (e.g., a monitor, a touch-sensitive display) and one or more input devices (e.g., touch-sensitive surfaces) using wired or wireless communication. The display generating component is configured to provide visual output, such as a display via a CRT monitor, a display via an LED monitor, or a display via image projection. In some embodiments, the display generating component is integrated with the computer system. In some embodiments, the display generating component is separate 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 separate from the computer system. Therefore, the computer system can transmit data (e.g., image data or video data) via wired or wireless connections to an integrated or external display generating component to visually generate content (e.g., using a display device), and can receive input from one or more input devices via wired or wireless connections.

[0230] As described below, Method 900 provides an intuitive way to create accounts for services. This method reduces the cognitive burden on users by decreasing the amount of information required to create an account, thus creating a more efficient human-computer interface. For battery-powered computing devices, it allows users to input less information, saving power and increasing the time between battery charges.

[0231] 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 display 608, input 605 on display 612, input 609 on display 616) (e.g., a tap on the “Continue” display).

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

[0233] Electronic device detects (906) a group of one or more inputs (e.g., 615) (e.g., a tap on one of the options, and optionally, a subsequent tap on the continued enable display).

[0234] In response to (908) detecting one or more inputs from the group, and based on determining that the group of one or more inputs corresponds to selecting the 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., email address).

[0235] In response to (908) detecting one or more inputs (e.g., 615), and based on determining that the one or more inputs correspond 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 a proxy email address). Selectively transmitting the user's personal contact information or automatically generated contact information that does not reveal the user's personal contact information allows 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 device security by preventing the sharing of the user's personal contact information with unintended recipients. Furthermore, selectively transmitting the user's personal contact information to approved recipients, while transmitting automatically generated contact information to other recipients, reduces the need for the user to manually enter different contact information for different recipients, thereby reducing the amount of input required to perform the operation. Reducing the amount of input enhances device operability and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, and by reducing negative authentication errors). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0236] In some embodiments, in response to (or subsequently) receiving a request to create an account for the first service, the electronic device displays the default name of the account (e.g., 636) via a display device (e.g., the user's name 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 a name. In some embodiments, while displaying the default name of 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, and based on determining that the second set of one or more inputs corresponds to the selection of 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 the alphabetical keyboard to modify the default name) and / or selection 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 user names allows the device to selectively share a user's real name only with authorized recipients, thereby enhancing security. Selectively sharing a user's real name with authorized recipients improves device security by preventing sharing the user's real name with unauthorized recipients.

[0237] In some implementations, in response to (or subsequently) receiving a request to create an account for the first service, the electronic device simultaneously displays a power indicator (e.g., 638) (e.g., an "x" icon) for clearing the name used for the account, along with the account's default name (e.g., 636) (e.g., the user's real name). In some implementations, 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 a 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 the name field (e.g., 640, 642) of the editing interface as part of the editing interface for the account name (e.g., 610a). In some implementations, in response to the detection of a second set of one or more inputs, and based on the determination that the second set of one or more inputs corresponds to a selection of a power indicator for clearing the name used for the account (e.g., 638) (e.g., a tap on an "x" icon), the electronic device displays an editing interface for the account name, instead of displaying a default name in the name field of the editing interface (e.g., 640, 642) (e.g., the editing interface displays an empty field for entering a new name). Providing an interface for editing a user's name allows 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 sharing of the user's real name with unintended recipients.

[0238] In some implementations, in response to detecting a first portion of the group of one or more inputs and before transmitting a request to create an account for a first service using first or second contact information, the electronic device displays multiple pieces of the user's contact information (e.g., 646) (e.g., multiple email addresses of the user, a first contact information with one or more other contact information, and an alternative email address) based on determining that the first portion of the group of one or more inputs corresponds to the selection of the first contact information while displaying the user's multiple contact information.

[0239] 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, and based on determining that a request to create an account for the first service using the user's first contact information has been 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 highlighted, with a checkmark indicating the option to share my email) and a second login option without a selection indicator (e.g., the second login option is not highlighted). In some embodiments, the second login option for creating an account for the second service corresponds to an option to request the creation of an account for the first service using the user's third contact information (different from the first and 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 a proxy email address). In some implementations, in response to receiving a second request to create an account for a second service, and 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 a first login option without a selection indicator and a second login option with a selection indicator (e.g., 634) (e.g., the second login option is highlighted, with a checkmark indicating the option to hide my email is pre-selected). Pre-selecting login options based on which login option was previously selected reduces the need for the user to manually select a login option, thereby reducing the amount of input required to perform the operation. Reducing the amount of input 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 negative false identifications during authentication), which in turn reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0240] In some implementations, a request to access (e.g., log in to the first service, create a new account for the first service) is received before a request to create an account for the first service is received. In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying a first login option and a 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 used for the first service). In some implementations, 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 for a login on a website, whether the credential was saved for a login in a specific application, whether the credential is stored in a local / remote credential repository). In some implementations, a request to create an account for the first service is received while the alternative account information is being displayed.

[0241] In some implementations, 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 a user request to access a settings interface) displays (e.g., for the first service) a settings interface (e.g., 810), which includes the user's second contact information (e.g., 818) (e.g., "Application received: [scrambled]@domain.com"). (In some implementations, the second contact information may be copied to another interface (e.g., tapping the second contact information saves the second contact information to the device's clipboard).

[0242] In some implementations, 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., to the first contact information). In some implementations, when a user has multiple email addresses, emails are forwarded to the user's primary email address.

[0243] In some implementations, the electronic device (e.g., in response to a user request to access a settings interface) displays a settings interface (e.g., 704a, 704b) with an intermediate email address (e.g., a proxy email address) configured to forward received emails to the user (e.g., 706) via email (e.g., first contact information). In some implementations, the electronic device detects a fourth set of one or more inputs (e.g., 703, 705) modifying the user's email address. In some implementations, the electronic device (e.g., in response to a user request (e.g., a tap on an enabled icon)) transmits a request to update the intermediate email address (e.g., a proxy email address) to forward emails to the user's modified email address (instead of forwarding them to the user's initial email address). In some implementations, all intermediate email addresses associated with the user (e.g., proxy email addresses used with other services or accounts) are updated to forward emails to the modified email address. Updating all intermediate email addresses to forward emails to the modified email address reduces the need for the user to manually change email settings for each service, thereby reducing the amount of input required to perform the operation. Reducing the amount of input enhances device operability and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, and by reducing negative authentication errors). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0244] In some implementations, 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 a sequence of one or more inputs including a user request to access a settings interface and optionally a request to navigate within the settings interface) displays a settings interface (e.g., 810) with a disabled indication (e.g., 820). In some implementations, the electronic device detects input corresponding to the disabled indication (e.g., 815). In some implementations, in response to detecting input corresponding to the disabled indication, the electronic device transmits a request to stop using the user's second contact information (e.g., a proxy email address) for the account for the first service (and optionally, (e.g., alternatively) use the user's first contact information (e.g., the user's email address) for the account for the first service). Stopping the use of a proxy email address for emails sent for the first service reduces 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 amount of input required to perform the operation. Reducing the amount of input enhances device operability and makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device, and by reducing negative authentication errors). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0245] In some implementations, the electronic device displays information (e.g., 804, 810) corresponding to the first service (e.g., 806b) (e.g., application list, application settings page). In some implementations, the electronic device (e.g., while displaying information corresponding to the first service) detects one or more fifth group inputs (e.g., 803, 808, 811) corresponding to a request to disable an account used for the first service (e.g., swipe gesture, disabling the ability to switch between display options). In some implementations, in response to detecting one or more fifth group inputs, the electronic device disables an account used for the first service (e.g., permanently deletes the account, temporarily disables the account, deletes information corresponding to the first service (e.g., no longer displays information corresponding to the first server, transmits an instruction to no longer forward emails).

[0246] In some implementations, 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 implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying a first login option and a second login option), the electronic device displays a change account capability representation (e.g., 618). In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying a first login option and a second login option), the electronic device detects input corresponding to the change account capability representation (e.g., 611). In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying a first login option and a second login option), and in response to detecting input corresponding to the change account capability representation, the electronic device displays an interface for selecting a login account for the user (e.g., another email address of the user). In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying a first login option and a second login option), and in response to detecting input corresponding to the change account capability representation: 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, password, authentication code for another ID). In some implementations, after detecting one or more sixth sets of inputs for selecting a login account for the user, a request to create an account for the first service is received. In some implementations, the first contact information corresponds to the contact information of the selected login account (e.g., the email address of the newly selected account).

[0247] In some implementations, 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 implementations, in response to receiving a 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., unverified email, two-factor authentication not enabled, terms and conditions not accepted). In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device (e.g., based on the detected security issue) displays an interface for correcting the security issue (e.g., 626). In some implementations, in response to receiving a request to access the first service (e.g., and before simultaneously displaying the first login option and the second login option), the electronic device (after displaying the interface for correcting the security issue) detects one or more seventh sets of inputs for correcting the security issue.

[0248] In some implementations, after detecting one or more seventh group of inputs for correcting security issues, a request to create an account for the first service is received (e.g., a tap on the “Continue” enablement after correcting the security issue).

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

[0250] In some implementations, a request to create an account for the first service is received from a web browser (e.g., 648) displaying the website (e.g., 604). In some implementations, a first login option and a second login option are displayed as an overlay (e.g., obscuring) of at least a portion of the website (e.g., the login option is not received as part of the website page). In some implementations, the overlay includes instructions for providing biometric authentication information (e.g., 632) (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).

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

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

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

[0254] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit this disclosure to the precise form disclosed. Many modifications and variations are possible based on the foregoing teachings. These embodiments were chosen 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 particular intended use.

[0255] While this 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 this disclosure and examples as defined by the claims.

[0256] As described above, one aspect of this technology is the collection and use of data available from various sources to create accounts for the service. This disclosure anticipates that, in some instances, this collected data may include personal information that uniquely identifies or can be used to contact or locate specific individuals. Such personal information may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, dates of birth, or any other identifying or personal information.

[0257] This disclosure recognizes that the use of such personal information data in the techniques disclosed herein can benefit users. For example, personal information data can be used to improve the process for creating accounts for services. Furthermore, this disclosure also anticipates other uses of personal information data that benefit users.

[0258] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. Therefore, different privacy practices should be maintained for different types of personal information data in each country.

[0259] Regardless of the foregoing, this disclosure also anticipates implementation schemes for users to selectively block the use or access to their personal information data. That is, this disclosure anticipates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to a user's name or email address, the technology disclosed herein can be configured to allow a user to opt-in or opt-out at any time during or after registering for the service to share their personal information data. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users may be notified when creating an account for the service that their personal information data will be shared with the service.

[0260] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, 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 among users), and / or other methods.

[0261] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the technology disclosed herein will not be rendered inoperable due to the absence of all or part of such personal information data.

Claims

1. A method for setting up an account for a service, comprising: In an electronic device having a display device, one or more processors, and memory: Receive a request to set up an account for a service that uses an intermediate email address, wherein: The intermediate email address is automatically generated for the service when the account is set up for the service. The intermediate email address will not disclose the user's contact information to the service, and The intermediate email address is an email address generated for the user to serve as an email address for receiving emails directed to the user from the service; Upon receiving the request to set up the account for the service using the intermediate email address, a settings interface is displayed, including a display of the user's email address to which the intermediate email address is configured to forward received emails. Detecting one or more inputs that modify the user's email address; and In response to detecting one or more inputs that modify the user's email address, a request is sent to forward mail sent from the service to the intermediate email address to the user's modified email address.

2. The method according to claim 1, wherein, The set of one or more inputs for modifying the user's email address includes inputs corresponding to the displayed email address of the user to which the intermediate email address is configured to forward received emails.

3. The method according to any one of claims 1 to 2, further comprising: Detect the first input; as well as In response to detecting the first input, one or more available forwarded email options are displayed via the display device.

4. The method according to claim 3, wherein, The one or more available forwarding email options are associated with the user of the electronic device.

5. The method according to claim 3, wherein, The one or more available forwarding email options include a first email address associated with the user of the electronic device and a second email address associated with the user of the electronic device that is different from the first email address.

6. The method according to claim 3, wherein, The one or more available forwarding email options include an indication that the intermediate email address is configured to forward received emails to the user's email address.

7. The method according to claim 3, wherein, Modifying the user's email address includes one or more inputs, including a second input corresponding to the selection of one or more available forwarding email options.

8. The method according to claim 6, further comprising: Detect the second input corresponding to the selection of one or more available forwarded email options; as well as In response to detecting the second input corresponding to the selection of one or more available forwarding email options, the indication to which the intermediate email address is configured to forward received emails is updated to indicate the selected forwarding email option.

9. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display device, one or more processors, and a memory, the one or more programs including instructions for performing the following operations: Receive a request to set up an account for a service that uses an intermediate email address, wherein: The intermediate email address is automatically generated for the service when the account is set up for the service. The intermediate email address will not disclose the user's contact information to the service, and The intermediate email address is an email address generated for the user to serve as an email address for receiving emails directed to the user from the service; Upon receiving the request to set up the account for the service using the intermediate email address, a settings interface is displayed, including a display of the user's email address to which the intermediate email address is configured to forward received emails. Detect one or more inputs that modify the user's email address; as well as In response to detecting one or more inputs that modify the user's email address, a request is sent to forward mail sent from the service to the intermediate email address to the user's modified email address.

10. The computer-readable storage medium according to claim 9, wherein, The set of one or more inputs for modifying the user's email address includes inputs corresponding to the displayed email address of the user to which the intermediate email address is configured to forward received emails.

11. The computer-readable storage medium according to any one of claims 9 to 10, wherein the one or more programs include instructions for performing the following operations: Detect the first input; and In response to detecting the first input, one or more available forwarded email options are displayed via the display device.

12. The computer-readable storage medium according to claim 11, wherein, The one or more available forwarding email options are associated with the user of the electronic device.

13. The computer-readable storage medium according to claim 11, wherein, The one or more available forwarding email options include a first email address associated with the user of the electronic device and a second email address associated with the user of the electronic device that is different from the first email address.

14. The computer-readable storage medium of claim 11, wherein, The one or more available forwarding email options include an indication that the intermediate email address is configured to forward received emails to the user's email address.

15. The computer-readable storage medium according to claim 11, wherein, Modifying the user's email address includes one or more inputs, including a second input corresponding to the selection of one or more available forwarding email options.

16. The computer-readable storage medium of claim 14, wherein the one or more programs include instructions for performing the following operations: Detect the second input corresponding to the selection of one or more available forwarding email options; and In response to detecting the second input corresponding to the selection of one or more available forwarding email options, the indication to which the intermediate email address is configured to forward received emails is updated to indicate the selected forwarding email option.

17. An electronic device comprising: Display devices; One or more processors; as well as The memory stores 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: Receive a request to set up an account for a service that uses an intermediate email address, wherein: The intermediate email address is automatically generated for the service when the account is set up for the service. The intermediate email address will not disclose the user's contact information to the service, and The intermediate email address is an email address generated for the user to serve as an email address for receiving emails directed to the user from the service; Upon receiving the request to set up the account for the service using the intermediate email address, a settings interface is displayed, including a display of the user's email address to which the intermediate email address is configured to forward received emails. Detecting one or more inputs that modify the user's email address; and In response to detecting one or more inputs that modify the user's email address, a request is sent to forward mail sent from the service to the intermediate email address to the user's modified email address.

18. The electronic device according to claim 17, wherein, The set of one or more inputs for modifying the user's email address includes a first input corresponding to the displayed email address of the user to which the intermediate email address is configured to forward received emails.

19. The electronic device according to any one of claims 17 to 18, wherein the one or more programs include instructions for performing the following operations: Detect the first input; and In response to detecting the first input, one or more available forwarded email options are displayed via the display device.

20. The electronic device according to claim 19, wherein, The one or more available forwarding email options are associated with the user of the electronic device.

21. The electronic device according to claim 19, wherein, The one or more available forwarding email options include a first email address associated with the user of the electronic device and a second email address associated with the user of the electronic device that is different from the first email address.

22. The electronic device according to claim 19, wherein, The one or more available forwarding email options include an indication that the intermediate email address is configured to forward received emails to the user's email address.

23. The electronic device according to claim 19, wherein, Modifying the user's email address includes one or more inputs, including a second input corresponding to the selection of one or more available forwarding email options.

24. The electronic device of claim 22, wherein the one or more programs include instructions for performing the following operations: Detect the second input corresponding to the selection of one or more available forwarding email options; and In response to detecting the second input corresponding to the selection of one or more available forwarding email options, the indication to which the intermediate email address is configured to forward received emails is updated to indicate the selected forwarding email option.

25. An electronic device configured to communicate with a display device, the electronic device comprising: Apparatus for performing the method according to any one of claims 1 to 8.

26. A computer program product comprising one or more programs executed by one or more processors of a computer system configured to communicate with a display device, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 8.

Images