Devices, methods, and graphical user interfaces for providing home button replacement

Abstract

Devices, methods, and graphical user interfaces for providing home button replacement are disclosed. In one embodiment, a method includes detecting a sequence of one or more activations of a button of a device when the device is in an unlocked state, where a first activation of the button is detected when a respective application user interface other than a home screen of the device is displayed on a display; and in response to detecting the sequence of one or more activations of the button: in accordance with determining that the first activation of the button is detected and that a second activation of the button is not detected before a respective threshold amount of time elapses since the detection of the first activation of the button, replacing display of the respective application user interface with display of the home screen, meanwhile, the equipment is kept in an unlocking state; and switching the device from an unlocked state displaying a respective application user interface to a locked state in accordance with a determination that a first activation of the button is detected and a second activation of the button is detected before a respective threshold amount of time elapses since the detection of the first activation of the button.

Description

[0001] Division Statement

[0002] This application is a divisional application of a Chinese invention patent application with an application date of May 2, 2018, an invention name of “Device, method and graphical user interface for providing home button replacement” and an application number of 201880031259.9. Technical Field

[0003] This document generally relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that provide a home button replacement. Background Art

[0004] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touch screen displays. Such surfaces are widely used to manipulate user interfaces on displays and objects therein. Exemplary user interface objects include digital images, videos, text, icons, and control elements (such as buttons) and other graphics.

[0005] Some electronic devices, such as handheld devices, include a permanent home button on the front of the device that, when activated in a predetermined manner (e.g., when pressed once), exits the currently displayed user interface and displays the device's home screen. However, a home button on the front of the device reduces the space available for a touch-sensitive surface (e.g., a touch screen display) on the device, but removing the home button from the front of the device removes a convenient way for the user to access the home screen and other functions associated with the home button. Summary of the invention

[0006] Therefore, there is a need for electronic devices with improved methods and interfaces for providing home button replacement. Such methods and interfaces optionally supplement or replace conventional methods for using a permanent home button on the front of the device. Such methods and interfaces reduce the amount, degree and / or nature of input from the user and produce a more efficient human-computer interface. For battery-powered devices, such methods and interfaces can save power and increase the time between battery charges.

[0007] The above-mentioned defects and other problems associated with the user interface of an electronic device with a touch-sensitive surface can be reduced or eliminated by means of the disclosed device. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, a tablet computer, or a handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or a "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, a memory, and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI mainly through stylus and / or finger contact and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentation, word processing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, fitness support, digital photography, digital video recording, web browsing, digital music playback, note-taking and / or digital video playback. 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.

[0008] According to some embodiments, a method is performed at a device having a touch-sensitive surface and a display. The method includes: when the device is in an unlocked state, detecting a sequence of one or more activations of a button of the device, the sequence including at least a first activation of the button, wherein the first activation of the button is detected when a corresponding application user interface other than the home screen of the device is displayed on the display; and in response to detecting the sequence of one or more activations of the button of the device: based on determining that the first activation of the button is detected and a second activation of the button is not detected before a corresponding threshold amount of time has passed since the first activation of the button is detected, replacing the display of the corresponding application user interface with the display of the home screen of the device while keeping the device in the unlocked state; and based on determining that the first activation of the button is detected and the second activation of the button is detected before a corresponding threshold amount of time has passed since the first activation of the button is detected, switching the device from an unlocked state in which the corresponding application user interface is displayed to a locked state.

[0009] According to some embodiments, a method is performed at a device having a touch-sensitive surface and a display. The method includes: displaying a home screen on the display, wherein the home screen includes a plurality of application launch icons corresponding to a plurality of applications installed on the device; while displaying the home screen, detecting a first input satisfying an application launch standard on a first application launch icon by a first contact; in response to detecting the first input satisfying the application launch standard on the first application launch icon, replacing the home screen with a first user interface of a first application corresponding to the first application launch icon; while displaying the first user interface, detecting a second input by a second contact, the second input including movement on the display in a first direction; and in response to detecting the second input: displaying a user interface object superimposed on a portion of the first user interface based on determining that the second input satisfies a taskbar display standard, wherein the taskbar display standard requires that the second input includes movement of a movement parameter magnitude of the second contact that is higher than a first movement threshold value in order to satisfy the taskbar display standard, wherein the user interface object includes a first subset of application launch icons from a plurality of application launch icons; and replacing the display of the first user interface with the display of the home screen based on determining that the second input satisfies the home display standard, wherein the home display standard requires that the second input includes movement of a movement parameter magnitude of the second contact that is higher than a second movement threshold value that is greater than the first movement threshold value.

[0010] According to some embodiments, a method is performed at a device having a touch-sensitive surface and a display. The method includes: displaying a home screen on a display, wherein the home screen includes a plurality of application launch icons corresponding to a plurality of applications installed on a device; while displaying the home screen, detecting a first input satisfying an application launch criterion on a first application launch icon by a first contact; in response to detecting the first input satisfying the application launch criterion on the first application launch icon, replacing the home screen with a first user interface of a first application corresponding to the first application launch icon; while displaying the first user interface, detecting a sequence of one or more inputs performed by a second contact; and in response to detecting the sequence of one or more inputs performed by the second contact: enabling, based on determining that the sequence of one or more inputs includes a second input satisfying a home button display criterion by a second contact, wherein the home button display criterion requires that the second input includes an initial movement of the second contact along a first direction on a touch-sensitive surface in order to satisfy the home button display criterion, a device for displaying a user interface object superimposed on the first user interface, wherein the user interface object includes a home button associated with a home screen of the display device; and replacing display of the first user interface with display of the home screen, based on determining that the sequence of one or more inputs includes a third input satisfying a display home criterion by a second contact, wherein the display home criterion requires that a characteristic intensity of the second contact increase to be above a first intensity threshold in order to satisfy the display home criterion.

[0011] According to some embodiments, an electronic device includes a display, a touch-sensitive surface, a memory, one or more processors, one or more programs, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface; one or more programs are stored in the memory and configured to be executed by one or more processors, and the one or more programs include instructions for performing or causing the execution of any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium stores therein instructions, which, when executed by an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface, cause the device to perform the operations of any of the methods described herein or cause the operations of any of the methods described herein to be performed. According to some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, one or more sensors for detecting the intensity of contact with the touch-sensitive surface, a memory, and one or more processors executing one or more programs stored in the memory includes one or more elements displayed in any of the methods described herein, which are updated in response to input, as described in any of the methods described herein. According to some embodiments, an electronic device includes: a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface; and a device for performing or causing the execution of the operations of any of the methods described herein. According to some embodiments, an information processing device for an electronic device having a display and a touch-sensitive surface and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface includes a device for performing the operations of any of the methods described herein or causing the operations of any of the methods described herein to be performed.

[0012] Thus, electronic devices having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface are provided with improved methods and interfaces for providing a home button replacement, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace conventional methods for using a permanent home button on the front face of the device. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0016] Figure 1C is a block diagram showing a tactile output module according to some embodiments.

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

[0018] Figure 2B-2C An exploded view of a force-sensitive input device according to some embodiments is shown.

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

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

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

[0022] Figure 4C-4E Examples of dynamic intensity thresholds according to some embodiments are shown.

[0023] Figure 5A1-Figure 5A7 An exemplary user interface is shown for displaying different user interfaces and / or locking a device in response to different activations of a button according to some embodiments.

[0024] Figure 5B1-Figure 5B22 An exemplary user interface is shown for displaying a device's taskbar and / or home screen in response to a multi-stage gesture in accordance with some embodiments.

[0025] Figure 5C1-Figure 5C50 An exemplary user interface is shown for displaying an on-demand virtual home button and activating the virtual home button to display a home screen in response to a continuous gesture in accordance with some embodiments.

[0026] Figure 6A-6E is a flow chart illustrating a method for displaying a home screen without locking the device or with the device locked based on different activations of a button according to some embodiments.

[0027] Figure 7A-7C is a flow chart illustrating a method for displaying a device's taskbar and / or home screen in response to a multi-stage gesture, according to some embodiments.

[0028] Figure 8A-8Dis a flow chart illustrating a method for displaying an on-demand virtual home button and activating the virtual home button to display a home screen in response to a continuous gesture, according to some embodiments. DETAILED DESCRIPTION

[0029] Some electronic devices, such as handheld devices, include a permanent home button on the front of the device that, when activated in a predetermined manner (e.g., when pressed once), exits the currently displayed user interface and displays the device's home screen. However, the home button on the front of the device reduces the space available for touch-sensitive surfaces (e.g., touch screen displays) on the device, but removing the home button from the front of the device removes a convenient way for the user to access the home screen and other functions associated with the home button. The following embodiments address this problem by providing an alternative way to access and activate the home button without having a permanent home button on the front of the device.

[0030] under, Figure 1A-1B , Figure 2 and Figure 3 A description of an exemplary apparatus is provided. Figure 4A-4B , Figure 5A1-Figure 5A7 , Figure 5B1-Figure 5B22 and Figure 5C1-Figure 5C50 An exemplary user interface for providing a home button replacement is shown. Figure 6A-6E A flow chart of a method for displaying a home screen without locking a device or with a locked device based on different activations of a button is shown. Figure 7A-7C is a flow chart illustrating a method for displaying a taskbar and / or a home screen of a device in response to a multi-stage gesture. Figure 8A-8D A flow chart of a method for displaying an on-demand virtual home button and activating the virtual home button to display a home screen in response to a continuous gesture is shown. Figure 5A1-Figure 5A7 , Figure 5B1-Figure 5B22 as well as Figure 5C1-Figure 5C50 The user interface in Figure 6A-6E , Figure 7A-7C and Figure 8A-8D process.

[0031] Exemplary Devices

[0032] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Many specific details are shown in the following detailed description in order to provide a full understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments can be practiced without these specific details. In other cases, well-known methods, processes, components, circuits, and networks are not described in detail, so as not to unnecessarily obscure various aspects of the embodiments.

[0033] It will also be understood that, although in some cases, the terms "first", "second", etc. are used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first contact can be named as the second contact, and similarly, the second contact can be named as the first contact without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact unless the context clearly indicates otherwise.

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

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

[0036] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). iPod and Device. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

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

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

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

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

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

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

[0043] The memory 102 optionally includes high-speed random access memory, and optionally also includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to the memory 102 by other components of the device 100 (such as one or more CPUs 120 and peripheral device interface 118) is optionally controlled by a memory controller 122.

[0044] Peripherals interface 118 may be used to couple the device's input and output peripherals to memory 102 and CPU(s) 120. Processor(s) 120 runs or executes various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.

[0045] In some embodiments, peripherals interface 118, one or more CPUs 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.

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

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

[0048] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch-sensitive display system 112 and other input or control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from or send electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the one or more input controllers 160 are optionally coupled to any one of the following (or not to any one of the following): a keyboard, an infrared port, a USB port, a stylus, and / or a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include an up / down button for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in FIG. 2).

[0049] The touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch-sensitive display system 112 and / or sends electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual outputs or all of the visual outputs correspond to user interface objects. As used herein, the term "indicator" is a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input directed to a graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

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

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

[0052] The touch-sensitive display system 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi or greater). The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0054] The device 100 also includes a power system 162 for powering the 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., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0055] Device 100 optionally also includes one or more optical sensors 164 . Figure 1A An optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. One or more optical sensors 164 optionally include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. One or more optical sensors 164 receive light projected through one or more lenses from the environment and convert the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), one or more optical sensors 164 optionally capture static images and / or videos. In some embodiments, an optical sensor is located on the rear portion of the device 100 opposite to the touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for static image and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to obtain an image of the user (e.g., for self-portraits, for video conferencing when the user is watching other video conference participants on the touch screen, etc.).

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

[0057] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is coupled to the input controller 160 in the I / O subsystem 106. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch-sensitive display system 112.

[0058] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A tactile output generator coupled to a tactile feedback controller 161 in the I / O subsystem 106 is shown. One or more tactile output generators 167 optionally include one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile outputs on the device). One or more tactile output generators 167 receive tactile feedback generation instructions from the tactile feedback module 133 and generate tactile outputs on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in juxtaposition or proximity to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on a rear portion of the device 100 opposite the touch-sensitive display system 112 located on the front of the device 100.

[0059] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on an analysis of data received from the one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0060] 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 tactile feedback module (or instruction set) 133, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 stores device / global internal state 157, as shown in FIG. 1A and FIG. Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch-sensitive display system 112; a sensor state, including information obtained from the device's various sensors and other input or control devices 116; and position and / or orientation information about the device's position and / or posture.

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

[0062] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a device that is compatible with some of Apple Inc. (Cupertino, California). iPod A multi-pin (e.g., 30-pin) connector that is the same as or similar to and / or compatible with the 30-pin connector used in iPod devices. In some embodiments, the external port is compatible with some of Apple Inc. (Cupertino, California) iPod A Lightning connector that is the same as, similar to, and / or compatible with the Lightning connector used in iPod devices.

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

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

[0065] In some embodiments, detecting a finger tap gesture depends on detecting the length of time between a finger press event and a finger lift event, but is independent of the strength of the finger contact between the finger press event and the finger lift event. In some embodiments, a tap gesture is detected based on determining that the length of time between the finger press event and the finger lift event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the strength of the finger contact during the tap reaches a given strength threshold (greater than a nominal contact detection strength threshold), such as a light press or deep press strength threshold. Therefore, a finger tap gesture can meet a specific input criterion that does not require the characteristic strength of the contact to meet a given strength threshold to meet the specific input criterion. For clarity, the finger contact in a tap gesture is generally required to meet a nominal contact detection strength threshold to detect a finger press event, and the contact will not be detected below the nominal contact detection strength threshold. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In the case where the device is capable of detecting contact with a finger or stylus hovering over the touch-sensitive surface, the nominal contact detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0066] The same concepts apply in a similar manner to other types of gestures. For example, a swipe gesture, a pinch gesture, an expand gesture, and / or a long press gesture may be optionally detected based on satisfying criteria that are independent of the strength of the contacts included in the gesture or that do not require one or more contacts performing the gesture to reach a strength threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts; a zoom gesture is detected based on the movement of two or more contacts toward each other; a zoom gesture is detected based on the movement of two or more contacts away from each other; and a long press gesture is detected based on the duration of a contact on a touch-sensitive surface having less than a threshold amount of movement. Therefore, the statement that a particular gesture recognition criterion does not require the strength of the contacts to satisfy a corresponding strength threshold in order to satisfy the particular gesture recognition criterion means that the particular gesture recognition criterion can be satisfied when the contacts in the gesture do not reach the corresponding strength threshold, and can also be satisfied when one or more contacts in the gesture reach or exceed the corresponding strength threshold. In some embodiments, a tap gesture is detected based on determining that a finger down event and a finger up event are detected within a predefined time period, regardless of whether the contact is above or below a corresponding strength threshold during the predefined time period, and a swipe gesture is detected based on determining that the contact moves greater than a predefined amount, even if the contact is above the corresponding strength threshold at the end of the contact movement. Even in specific implementations where detection of gestures is affected by the strength of the contact performing the gesture (e.g., the device detects a long press more quickly when the strength of the contact is above the strength threshold, or the device delays detection of a tap input when the strength of the contact is higher), detection of these gestures does not require the contact to reach a particular strength threshold (e.g., even if the amount of time required to recognize the gesture varies), as long as the criteria for recognizing the gesture can be met without the contact reaching the particular strength threshold.

[0067] In some cases, the contact intensity threshold, duration threshold, and movement threshold are combined in various combinations to create a heuristic algorithm to distinguish between two or more different gestures for the same input element or area, so that multiple different interactions with the same input element can provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria does not require the intensity of the contact to meet the corresponding intensity threshold to meet the particular gesture recognition criteria does not exclude the simultaneous evaluation of other intensity-related gesture recognition criteria to identify other gestures with criteria that are met when the gesture includes a contact with an intensity above the corresponding intensity threshold. For example, in some cases, a first gesture recognition criterion for a first gesture (which does not require the intensity of the contact to meet the corresponding intensity threshold to meet the first gesture recognition criterion) competes with a second gesture recognition criterion for a second gesture (which depends on the contact reaching the corresponding intensity threshold). In such a competition, if the second gesture recognition criterion for the second gesture is met first, the gesture is optionally not recognized as meeting the first gesture recognition criterion for the first gesture. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predefined amount of movement, a deep press gesture is detected instead of a swipe gesture. Conversely, if the contact moves the predefined amount of movement before the contact reaches the corresponding intensity threshold, a swipe gesture is detected instead of a deep press gesture. Even in such cases, the first gesture recognition criteria for the first gesture still does not require the intensity of the contact to satisfy the corresponding intensity threshold to satisfy the first gesture recognition criteria because if the contact remains below the corresponding intensity threshold until the gesture ends (e.g., a swipe gesture with an intensity of the contact that does not increase above the corresponding intensity threshold), the gesture will be recognized as a swipe gesture by the first gesture recognition criteria. Thus, a particular gesture recognition criterion that does not require the intensity of the contact to satisfy the corresponding intensity threshold to satisfy the particular gesture recognition criterion will (A) in some cases ignore the intensity of the contact relative to the intensity threshold (e.g., for a tap gesture) and / or (B) in some cases fail to satisfy the particular gesture recognition criterion (e.g., for a long press gesture) if a set of competing intensity-related gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-related gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input, and in this sense still depends on the intensity of the contact relative to the intensity threshold (e.g., for a long press gesture competing with the deep press gesture for recognition).

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

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

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

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

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

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

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

[0075] Telephone module 138;

[0076] Video conferencing module 139;

[0077] Email client module 140;

[0078] Instant messaging (IM) module 141;

[0079] Fitness support module 142;

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

[0081] Image management module 144;

[0082] Browser module 147;

[0083] Calendar module 148;

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

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

[0086] Search module 151;

[0087] A video and music player module 152, optionally consisting of a video player module and a music player module;

[0088] Notepad module 153;

[0089] Map module 154; and / or

[0090] Online video module 155.

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

[0092] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting one or more names from the address book; associating one or more telephone numbers, one or more email addresses, one or more physical addresses, or other information with a name; associating images with names; categorizing and classifying names; providing telephone numbers and / or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing 139, email 140, or instant messaging 141; and the like.

[0093] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 includes executable instructions for entering a character sequence corresponding to a phone number, accessing one or more phone numbers in address book 137, modifying an entered phone number, dialing a corresponding phone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communications optionally use any of a variety of communication standards, protocols, and technologies.

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

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

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

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

[0098] In conjunction with touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, and / or deleting still images or videos from memory 102.

[0099] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, displaying (e.g., in a digital slide show or album), and storing still images and / or video images.

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

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

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

[0103] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget creator module 150 includes executable instructions for creating a desktop widget (e.g., transferring a user-specified portion of a web page to a desktop widget).

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

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

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

[0107] In combination with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with the maps (e.g., driving routes; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

[0108] In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes executable instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on touch screen 112 or on an external display connected wirelessly or via external port 124), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video.

[0109] Each module and application identified above corresponds to a set of executable instructions for performing one or more functions and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). These modules (i.e., instruction sets) do not have to be implemented with independent software programs, processes or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above modules and data structures. In addition, memory 102 optionally stores other modules and data structures not described above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0137] Figure 1C 1 is a block diagram showing a tactile output module according to some embodiments. In some embodiments, the I / O subsystem 106 (e.g., the tactile feedback controller 161 ( Figure 1A ) and / or one or more other input controllers 160 ( Figure 1A ))include Figure 1C At least some of the example components shown. In some embodiments, the peripheral device interface 118 includes Figure 1C At least some of the example components shown.

[0138] In some embodiments, the tactile output module includes a tactile feedback module 133. In some embodiments, the tactile feedback module 133 aggregates and combines tactile outputs from software applications on the electronic device for user interface feedback (e.g., feedback in response to user input corresponding to the displayed user interface and prompts and other notifications indicating the execution of operations or the occurrence of events in the user interface of the electronic device). The tactile feedback module 133 includes one or more of a waveform module 123 (for providing a waveform for generating tactile output), a mixer 125 (for mixing waveforms, such as waveforms in different channels), a compressor 127 (for reducing or compressing the dynamic range of the waveform), a low-pass filter 129 (for filtering out high-frequency signal components in the waveform), and a thermal controller 131 (for adjusting the waveform according to thermal conditions). In some embodiments, the tactile feedback module 133 is included in a tactile feedback controller 161 ( Figure 1A In some embodiments, a separate unit of the tactile feedback module 133 (or a separate specific implementation of the tactile feedback module 133) is also included in the audio controller (e.g., the audio circuit 110, Figure 1A ) and used to generate an audio signal. In some embodiments, a single tactile feedback module 133 is used to generate an audio signal and to generate a waveform for a tactile output.

[0139] In some embodiments, the tactile feedback module 133 also includes a trigger module 121 (e.g., a software application, operating system, or other software module that determines that a tactile output is to be generated and triggers a process for generating the corresponding tactile output). In some embodiments, the trigger module 121 generates a trigger signal for triggering (e.g., by the waveform module 123) the generation of a waveform. For example, the trigger module 121 generates a trigger signal based on a preset timing standard. In some embodiments, the trigger module 121 receives a trigger signal from outside the tactile feedback module 133 (e.g., in some embodiments, the tactile feedback module 133 receives a trigger signal from a hardware input processing module 146 located outside the tactile feedback module 133) and relays the trigger signal to other components within the tactile feedback module 133 (e.g., the waveform module 123) or a software application that triggers an operation (with the trigger module 121) based on the activation of a hardware input device (e.g., a home button). In some embodiments, the trigger module 121 also (e.g., from the tactile feedback module 133, Figure 1A and Figure 3 ) receives a tactile feedback generation instruction. In some embodiments, the trigger module 121 responds to the tactile feedback module 133 (or the trigger module 121 in the tactile feedback module 133) (e.g., from the tactile feedback module 133, Figure 1A and Figure 3 ) receives tactile feedback instructions and generates a trigger signal.

[0140] Waveform module 123 receives a trigger signal as input (e.g., from trigger module 121) and provides a waveform for generating one or more tactile outputs (e.g., a waveform selected from a predefined set of waveforms assigned for use by waveform module 123) in response to receiving the trigger signal.

[0141] The mixer 125 receives waveforms as input (e.g., from the waveform module 123) and mixes the waveforms together. For example, when the mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform in a second channel that at least partially overlaps the first waveform), the mixer 125 outputs a combined waveform corresponding to the sum of the two or more waveforms. In some embodiments, the mixer 125 also modifies one or more of the two or more waveforms to emphasize a particular waveform relative to the rest of the two or more waveforms (e.g., by increasing the scale of the particular waveform and / or reducing the scale of the other waveforms in the waveforms). In some cases, the mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., when waveforms from more than three sources have been requested to be output simultaneously by the tactile output generator 167, the waveform from the oldest source is discarded).

[0142] Mixer 127 receives waveforms (e.g., combined waveforms from mixer 125) as input and modifies these waveforms. In some embodiments, compressor 127 reduces these waveforms (e.g., based on tactile output generator 167 ( Figure 1A ) or 357( Figure 3 ) such that the tactile output corresponding to these waveforms is reduced. In some embodiments, compressor 127 limits the waveforms, such as by imposing a predefined maximum amplitude on the waveforms. For example, compressor 127 reduces the amplitude of the waveform portion that exceeds the predefined amplitude threshold, while maintaining the amplitude of the waveform portion that does not exceed the predefined amplitude threshold. In some embodiments, compressor 127 reduces the dynamic range of the waveform. In some embodiments, compressor 127 dynamically reduces the dynamic range of the waveform so that the combined waveform remains within the performance specifications of tactile output generator 167 (e.g., force and / or movable mass displacement limits).

[0143] Low-pass filter 129 receives a waveform (e.g., a compressed waveform from compressor 127) as input and filters (e.g., smoothes) the waveform (e.g., removes or reduces high-frequency signal components in the waveform). For example, in some cases, compressor 127 includes extraneous signals (e.g., high-frequency signal components) in the compressed waveform that interfere with tactile output generation and / or exceed the performance specifications of tactile output generator 167 when generating tactile output based on the compressed waveform. Low-pass filter 129 reduces or removes such extraneous signals in the waveform.

[0144] Thermal controller 131 receives a waveform (e.g., a filtered waveform from low pass filter 129) as input and adjusts the waveform based on a thermal condition of device 100 (e.g., based on an internal temperature detected within device 100, such as the temperature of haptic feedback controller 161, and / or an external temperature detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies based on temperature (e.g., in response to receiving the same waveform, haptic feedback controller 161 generates a first tactile output when haptic feedback controller 161 is at a first temperature and generates a second tactile output when haptic feedback controller 161 is at a second temperature different from the first temperature). For example, the magnitude (or amplitude) of the tactile output may vary based on temperature. To reduce the effects of temperature changes, the waveform is modified (e.g., the amplitude of the waveform is increased or decreased based on temperature).

[0145] In some embodiments, the tactile feedback module 133 (e.g., trigger module 121) is coupled to the hardware input processing module 146. In some embodiments, Figure 1A The one or more other input controllers 160 in the embodiment include a hardware input processing module 146. In some embodiments, the hardware input processing module 146 receives input from a hardware input device 145 (e.g. Figure 1A In some embodiments, the hardware input device 145 is any input device described herein, such as a touch-sensitive display system 112 ( Figure 1A )、Keyboard / Mouse 350( Figure 3 )、Touchpad 355( Figure 3 ), one of the other input or control devices 116 ( Figure 1A ), or intensity-sensitive home buttons (e.g. Figure 2B As shown or Figure 2C In some embodiments, the hardware input device 145 consists of a strength-sensitive home button (e.g., Figure 2B as shown, or Figure 2C ) rather than being comprised of a touch-sensitive display system 112 ( Figure 1A )、Keyboard / Mouse 350( Figure 3 ) or touchpad 355( Figure 3 ). In some embodiments, in response to input from the hardware input device 145, the hardware input processing module 146 provides one or more trigger signals to the tactile feedback module 133 to indicate that a user input that meets the predefined input criteria has been detected, such as an input corresponding to a home button "click" (e.g., a "press click" or a "release click"). In some embodiments, the tactile feedback module 133 provides a waveform corresponding to a home button "click" in response to the input corresponding to the home button "click", thereby simulating the tactile feedback of pressing the physical home button.

[0146] In some embodiments, the tactile output module includes a tactile feedback controller 161 (eg, Figure 1A 145 ) which controls the generation of tactile output. In some embodiments, the tactile feedback controller 161 is coupled to a plurality of tactile output generators, and selects one or more tactile output generators from the plurality of tactile output generators and sends a waveform to the selected one or more tactile output generators for generating a tactile output. In some embodiments, the tactile feedback controller 161 coordinates a tactile output request corresponding to activation of the hardware input device 145 and a tactile output request corresponding to a software event (e.g., a tactile output request from the tactile feedback module 133), and modifies one or more of the two or more waveforms to emphasize a particular waveform relative to the remaining waveforms of the two or more waveforms (e.g., by increasing the scale of a particular waveform and / or reducing the scale of the remaining waveforms of the waveforms to prioritize the tactile output corresponding to the activation of the hardware input device 145 over the tactile output corresponding to the software event).

[0147] In some embodiments, such as Figure 1C As shown, the output of the tactile feedback controller 161 is coupled to the audio circuit of the device 100 (eg, the audio circuit 110, Figure 1A ), and provides the audio signal to the audio circuit of device 100. In some embodiments, tactile feedback controller 161 provides both a waveform for generating a tactile output and an audio signal for providing an audio output together with generating the tactile output. In some embodiments, tactile feedback controller 161 modifies the audio signal and / or the waveform (for generating the tactile output) so that the audio output and the tactile output are synchronized (e.g., by delaying the audio signal and / or the waveform). In some embodiments, tactile feedback controller 161 includes a digital-to-analog converter for converting a digital waveform into an analog signal, which is received by amplifier 163 and / or tactile output generator 167.

[0148] In some embodiments, the tactile output module includes an amplifier 163. In some embodiments, the amplifier 163 receives a waveform (e.g., from the tactile feedback controller 161), amplifies the waveform, and then sends the amplified waveform to the tactile output generator 167 (e.g., the tactile output generator 167 ( Figure 1A ) or 357( Figure 3 )). For example, amplifier 163 amplifies the received waveform to a signal level that meets the physical specifications of tactile output generator 167 (e.g., amplifies to the voltage and / or current required by tactile output generator 167 to generate a tactile output so that the signal sent to tactile output generator 167 generates a tactile output corresponding to the waveform received from tactile feedback controller 161) and sends the amplified waveform to tactile output generator 167. In response, tactile output generator 167 generates a tactile output (e.g., by shifting the movable mass back and forth in one or more dimensions relative to the neutral position of the movable mass).

[0149] In some embodiments, the tactile output module includes a sensor 169 coupled to the tactile output generator 167. The sensor 169 detects the state or state change (e.g., mechanical position, physical displacement, and / or movement) of the tactile output generator 167 or one or more components of the tactile output generator 167 (e.g., one or more moving components, such as a membrane, for generating a tactile output). In some embodiments, the sensor 169 is a magnetic field sensor (e.g., a Hall effect sensor) or other displacement and / or motion sensor. In some embodiments, the sensor 169 provides information (e.g., the position, displacement, and / or movement of one or more components in the tactile output generator 167) to the tactile feedback controller 161, and based on the information about the state of the tactile output generator 167 provided by the sensor 169, the tactile feedback controller 161 adjusts the waveform output from the tactile feedback controller 161 (e.g., the waveform sent to the tactile output generator 167, optionally via the amplifier 163).

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

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

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

[0153] Figure 2B-2C Shown suitable for Figure 1A , Figure 2A , Figure 3 and / or Figure 4A0 is an exploded view of a first input device (eg, as a home button 204) used in an electronic device shown in FIG. Figure 2B An example of an intensity-sensitive home button with a capacitive sensor for determining a range of intensity values ​​corresponding to a force applied to the intensity-sensitive home button is shown. Figure 2C An example of a home button having a mechanical switch element is shown. Figure 2B , the input device stack 220 includes a cover element 222 and a trim 224. In the illustrated embodiment, the trim 224 completely surrounds the sides of the cover element 222 and the perimeter of the top surface of the cover element 222. Other embodiments are not limited to this configuration. For example, in one embodiment, the sides and / or top surface of the cover element 222 may be partially surrounded by the trim 224. Alternatively, the trim 224 may be omitted in other embodiments.

[0154] Both the cover element 222 and the rim 224 can be made of any suitable opaque, transparent and / or translucent material. For example, the cover element 222 can be formed of glass, plastic, or sapphire, and the rim 224 can be formed of metal or plastic. In some embodiments, one or more additional layers (not shown) can be located below the cover element 222. For example, when the cover element 222 is formed of a transparent material, an opaque ink layer can be disposed below the cover element 222. The opaque ink layer can hide other components in the input device stack 220 so that the other components cannot be seen through the transparent cover element 222.

[0155] A first circuit layer 226 may be disposed below the cover element 222. Any suitable circuit layer may be used. For example, the first circuit layer 226 may be a circuit board or a flexible circuit. The first circuit layer 226 may include one or more circuits, signal lines, and / or integrated circuits. In one embodiment, the first circuit layer 226 includes a biometric sensor 228. Any suitable type of biometric sensor may be used. For example, in one embodiment, the biometric sensor is a capacitive fingerprint sensor that captures at least one fingerprint when a user's finger approaches and / or contacts the cover element 222.

[0156] The first circuit layer 226 may be attached to the bottom surface of the cover element 222 by an adhesive layer 230. Any suitable adhesive may be used for the adhesive layer. For example, a pressure sensitive adhesive layer may be used as the adhesive layer 230.

[0157] The conformal layer 232 is disposed below the first circuit layer 226. In one embodiment, the conformal layer 232 includes an opening 234 formed in the conformal layer 232. When the device stack 220 is assembled, the opening 234 exposes the top surface of the first circuit layer 226 and / or the biometric sensor 228. In the illustrated embodiment, the conformal layer 232 is positioned around the inner perimeter of the trim 224 and / or around the peripheral edge of the cover element 222. Although illustrated in a circular shape, the conformal layer 232 can have any given shape and / or dimensions, such as a square or an oval. The conformal layer 232 is formed in Figure 2B and 2C 234, but other embodiments are not limited to this configuration. In some embodiments, multiple discrete compliant layers can be used in the device stack 220. In some other embodiments, the compliant layer 232 does not include the opening 234, and the compliant layer 232 extends across at least a portion of the input device stack 220. For example, the compliant layer 232 can extend across the bottom surface of the cover element 222, the bottom surface of the first circuit layer 226, or a portion of the bottom surface of the cover element 222 (e.g., around the peripheral edge of the cover element) and the bottom surface of the first circuit layer 226.

[0158] The second circuit layer 238 is positioned below the first circuit layer 226. Flexible circuits and circuit boards are examples of circuit layers that can be used in the second circuit layer 238. In some embodiments, the second circuit layer 238 can include a first circuit section 240 and a second circuit section 242. The first circuit section 240 and the second circuit section 242 can be electrically connected to each other.

[0159] First circuit section 240 may include a first set of one or more intensity sensor components included in an intensity sensor. In some embodiments, first circuit section 240 may be electrically connected to first circuit layer 226. For example, when first circuit layer 226 includes biometric sensor 228, biometric sensor 228 may be electrically connected to first circuit section 240 of second circuit layer 238.

[0160] The second circuit section 242 may include additional circuits, such as signal lines, circuit components, integrated circuits, and the like. In one embodiment, the second circuit section 242 may include a board-to-board connector 244 for electrically connecting the second circuit layer 238 to other circuits in the electronic device. For example, the second circuit layer 238 may be operably connected to a processing device using the board-to-board connector 244. In addition or alternatively, the second circuit layer 238 may be operably connected to a circuit that transmits a signal (e.g., a sensing signal) received from the intensity sensor component in the first circuit section 240 to a processing device. In addition or alternatively, the second circuit layer 238 may be operably connected to a circuit that provides a signal (e.g., a drive signal, a reference signal) to one or more of the intensity sensor components in the first circuit section 240.

[0161] In some implementations, the first circuit section 240 of the second circuit layer 238 can be attached to the bottom surface of the first circuit layer 226 using the adhesive layer 236. In a non-limiting example, the first circuit section 240 can be attached to the bottom surface of the first circuit layer 226 using a die attach film.

[0162] A third circuit layer 246 is disposed below the first circuit section 240 of the second circuit layer 238. The third circuit layer 246 may include a second set of one or more intensity sensor components included in the intensity sensor. The third circuit layer 246 is supported by and / or attached to a support element 248. In one embodiment, the support element 248 is attached to the trim 224 to create a housing for other components in the device stack 220. The support element 248 may be attached to the trim 224 using any suitable attachment mechanism.

[0163] The first set of one or more intensity sensor components in first circuit section 240 and the second set of one or more intensity sensor components in third circuit layer 246 together form an intensity sensor. The intensity sensor may use any suitable intensity sensing technology. Exemplary sensing technologies include, but are not limited to, capacitive, piezoelectric, piezoresistive, ultrasonic, and magnetic.

[0164] exist Figure 2B and 2C In the example shown, the force sensor is a capacitive force sensor. For a capacitive force sensor, the first set of one or more force sensor components may include a first set of one or more electrodes 250, and the second set of one or more force sensor components may include a second set of one or more electrodes 252. Figure 2B and 2CAlthough illustrated in a square shape, each electrode in the first group and the second group of one or more electrodes 250, 252 may have any given shape (e.g., rectangle, circle). In addition, the one or more electrodes in the first group 250 and the second group 252 may be arranged in any given pattern (e.g., one or more rows and one or more columns).

[0165] Figure 2B and 2C Two electrodes in the first group and the second group of one or more electrodes 250, 252 are shown. However, other embodiments are not limited to this configuration. The first group and the second group of one or more electrodes 250, 252 may each be a single electrode or a plurality of discrete electrodes. For example, if the first group of one or more electrodes is a single electrode, the second group of one or more electrodes includes a plurality of discrete electrodes. In some embodiments, the second group of one or more electrodes may be a single electrode and the first group includes a plurality of discrete electrodes. Alternatively, the first group and the second group of one or more electrodes may each include a plurality of discrete electrodes.

[0166] Each electrode in the first group of one or more electrodes 250 is aligned in at least one direction (e.g., vertically) with a corresponding electrode in the second group of one or more electrodes 252 to generate one or more capacitors. When a force input is applied to the cover element 222 (e.g., an input surface of an input device), at least one electrode in the first group 250 moves closer to a corresponding electrode in the second group 252, which changes the capacitance of the capacitor. The capacitance signal sensed from each capacitor represents a capacitance measurement of the capacitor. A processing device (not shown) is configured to receive the capacitance signal and relate the capacitance signal to the amount of strength applied to the cover element 222. In some embodiments, the force sensor can replace the switch element, and different intensity thresholds can be used to determine an activation event.

[0167] In some embodiments, such as Figure 2C In the illustrated embodiment, the switch element 254 may be located below the support element 248. The switch element 254 registers user input when the force input applied to the cover element 222 exceeds a given amount of force (e.g., a force threshold of the distance between the closed first circuit section 240 and the third circuit layer 246). Any appropriate switch element may be used. For example, the switch element 254 may be a dome switch that collapses when the force input applied to the cover element 222 exceeds the force threshold. When collapsed, the dome switch completes a circuit that is detected by the processing device and is identified as a user input (e.g., selecting an icon, function, or application). In one embodiment, the dome switch is arranged so that the vertex of the dome that can collapse is adjacent to the bottom surface of the support plate 248. In another embodiment, the base of the collapsible dome may be adjacent to the bottom surface of the support plate 248.

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

[0169] Figure 3Each element in the above-mentioned identified element is optionally stored in one or more memory devices in the previously mentioned memory device. Each module in the above-mentioned identified module corresponds to a group of instructions for performing the above-mentioned functions. The above-mentioned identified module or program (that is, instruction set) need not be implemented as a separate software program, process or module, so the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subgroup of the above-mentioned modules and data structures. In addition, memory 370 optionally stores other modules and data structures not described above.

[0170] Attention is now turned to an embodiment of a user interface (“UI”) that is optionally implemented on portable multifunction device 100 .

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

[0172] One or more signal strength indicators 402 of one or more wireless communications such as cellular signals and Wi-Fi signals;

[0173] Time 404;

[0174] Bluetooth indicator 405;

[0175] Battery status indicator 406;

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

[0177] o An icon 416 of the phone module 138 labeled "Phone," the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

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

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

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

[0181] Icons for other apps, such as:

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

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

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

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

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

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

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

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

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

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

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

[0193] ○ An icon 446 for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

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

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

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

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

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

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

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

[0201] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact begins to move, before contact ends, before or after contact intensity increases and / or before or after contact intensity decreases). The characteristic intensity of a 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, the value generated by low-pass filtering the contact intensity over a predefined time period or starting from a predefined time, etc. In some embodiments, the duration of the contact is used in determining the feature strength (e.g., when the feature strength is the average of the strength of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds may include a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more strength thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding option or give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

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

[0203] The user interface diagrams described herein optionally include various intensity diagrams that illustrate the intensity of contacts on the touch-sensitive surface relative to one or more intensity thresholds (e.g., contact detection intensity threshold IT0, light press intensity threshold IT1, and light touch intensity threshold IT2). L , Deep compression intensity threshold IT D (For example, it is at least partially higher than I L ) and / or one or more other intensity thresholds (e.g., ratio I L Lower intensity threshold I H )). This intensity graph is not typically part of the displayed user interface, but is provided to help explain the graph. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold IT0, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing operations associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0204] In some embodiments, the response of the device to the input detected by the device depends on a criterion based on the contact strength during the input. For example, for some "light press" inputs, the strength of the contact exceeding the first strength threshold during the input triggers a first response. In some embodiments, the response of the device to the input detected by the device depends on a criterion including both the contact strength during the input and a time-based criterion. For example, for some "deep press" inputs, as long as a delay time passes between satisfying the first strength threshold and satisfying the second strength threshold, the strength of the contact exceeding the second strength threshold greater than the first strength threshold of the light press during the input triggers a second response. The duration of the delay time is typically less than 200ms (e.g., 40ms, 100ms, or 120ms, depending on the magnitude of the second strength threshold, where the delay time increases as the second strength threshold increases). The delay time helps avoid accidental deep press inputs. As another example, for some "deep press" inputs, a period of reduced sensitivity will occur after reaching the first strength threshold. During this period of reduced sensitivity, the second strength threshold increases. This temporary increase in the second strength threshold also helps avoid accidental deep press inputs. For other deep press inputs, the response to detecting the deep press input is not dependent on time-based criteria.

[0205] In some embodiments, one or more of the input intensity thresholds and / or corresponding outputs vary based on one or more factors such as user settings, contact motion, input timing, application running, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, etc. Example factors are described in U.S. patent applications 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entirety.

[0206] For example, Figure 4C A dynamic intensity threshold 480 is shown that changes over time based in part on the intensity of touch input 476 over time. Dynamic intensity threshold 480 is the sum of two components: a first component 474 that decays over time after a predefined delay time p1 from when touch input 476 is initially detected, and a second component 478 that tracks the intensity of touch input 476 over time. The initial high intensity threshold of first component 474 reduces accidental triggering of a “deep press” response while still allowing an immediate “deep press” response if touch input 476 provides sufficient intensity. Second component 478 reduces unintentional triggering of a “deep press” response through gradual intensity fluctuations of the touch input. In some embodiments, when touch input 476 satisfies dynamic intensity threshold 480 (e.g., at Figure 4C ), triggering a "deep press" response.

[0207] Figure 4D Another dynamic intensity threshold 486 (eg, intensity threshold I D ). Figure 4D Two other intensity thresholds are also shown: a first intensity threshold I H and the second intensity threshold I L .exist Figure 4D Although the touch input 484 satisfies the first intensity threshold I before time p2, H and the second intensity threshold I L , but no response is provided until a delay time p2 has elapsed at time 482. Similarly, Figure 4D , the dynamic intensity threshold 486 decays over time, wherein the decay is from time 482 (triggering the second intensity threshold I L This type of dynamic intensity threshold reduction begins at time 488 after a predefined delay time p1 has elapsed when the trigger is associated with a lower threshold intensity (such as the first intensity threshold I H Or the second intensity threshold I L ) is triggered after or simultaneously with the response associated with the dynamic intensity threshold I D The associated response.

[0208] Figure 4E Another dynamic intensity threshold 492 (eg, intensity threshold I D ).exist Figure 4E In the example, after a delay time p2 has passed since the touch input 490 was initially detected, the trigger is triggered with the intensity threshold I L At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 has passed since the touch input 490 was initially detected. L The associated response then decreases the intensity of the touch input 490, and then increases the intensity of the touch input 490 without releasing the touch input 490, which may trigger the touch input 490 to be in accordance with the intensity threshold I. D The associated response (e.g., at time 494) may be performed even when the intensity of touch input 490 is below another intensity threshold (e.g., intensity threshold I L ) is also the case.

[0209] The contact characteristic strength is below the light press strength threshold IT L The intensity increases to between the light pressure intensity threshold IT L and deep compression intensity threshold IT D The intensity between IT and the deep press intensity threshold is sometimes referred to as a "light press" input. D The intensity of the deep compression increases to above the deep compression intensity threshold IT DThe intensity of the contact feature increases from an intensity below the contact detection intensity threshold IT0 to an intensity between the contact detection intensity threshold IT0 and the light press intensity threshold IT0. L A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold IT0 to an intensity below the contact detection intensity threshold IT0 is sometimes referred to as detecting a contact lifted off the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some examples, shaded circles or ellipses are used to represent the intensity of a contact on the touch-sensitive surface. In some examples, unshaded circles or ellipses are used to represent corresponding contacts on the touch-sensitive surface without specifying the intensity of the corresponding contacts.

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

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

[0212] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input are optionally triggered in response to detecting that the intensity of the contact increases above the press input intensity threshold, the intensity of the contact increases from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreases below the press input intensity threshold, or the intensity of the contact decreases below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold. As described above, in some embodiments, triggering of these operations is also dependent on satisfying a time-based criterion (e.g., a delay time has elapsed between satisfying the first intensity threshold and satisfying the second intensity threshold).

[0213] User interface and associated processes

[0214] Attention now turns to embodiments of a user interface ("UI") and associated processes that may be implemented on an electronic device such as portable multifunction device 100 or device 300 having a display, a touch-sensitive surface, and (optionally) one or more sensors for detecting intensity of contacts with the touch-sensitive surface.

[0215] Figure 5A1-Figure 5A71 shows exemplary user interfaces for displaying different user interfaces and / or locking a device in response to different activations of a button (e.g., a combined physical home / lock button) according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figure 6A-6E . For ease of explanation, some embodiments in the implementation scheme will be discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on touch-sensitive display system 112. However, in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface on display 450 and the focus selector shown in the figure, similar operations are optionally performed on a device with display 450 and a separate touch-sensitive surface 451.

[0216] For ease of explanation, some of the embodiments will be discussed with reference to operations performed on a device having a mechanical slider button (e.g., button 501). Figure 5A1-Figure 5A7 , a button (e.g., button 501) is shown as a mechanical slider button located on one side of device 100 that can be pressed, moved up, and / or moved down. Figure 5A1-Figure 5A7 100, but in some embodiments, button 501 is a mechanical button at another location on device 100 (e.g., on the top of device 100, on the surface of device 100, etc.), a virtual button (e.g., a virtual home button on touch screen 112), or a solid-state button (e.g., a solid-state home button located below touch screen 112). Optionally, similar operations are performed on devices with alternative buttons. In some embodiments, Figure 5A1-Figure 5A7 Button 501 replacement in Figure 4A The home button 204 and / or the push button 206 of the device 100 are displayed.

[0217] Figure 5A1 It is shown that the home screen is displayed without locking the device, or the device is locked, depending on whether a second activation of button 501 is detected after the initial activation of button 501. In addition, Figure 5A1 1 shows that, depending on whether a second activation of button 501 is detected within a threshold time T of the initial activation of button 501, the home screen is displayed before the device is locked or the display of the home screen is skipped before the device is locked. Figure 5A1As shown, the device 100 initially displays the application user interface (e.g., user interface 502). First, as shown in the path "1" of the lock screen (e.g., user interface 506), when the first click and the second click are detected on the button 501 within time T, the device 100 replaces the display of the application user interface (e.g., user interface 502) with the display of the lock screen (e.g., user interface 506) without displaying the home screen. Alternatively, when the first click is detected on the button 501 and the second click is not detected within time T, the device 100 replaces the display of the application user interface (e.g., user interface 502) with the display of the home screen (e.g., user interface 504). Then, as shown in the path "2" of the lock screen (e.g., user interface 506), when the second click is detected on the button 501 after time T, the device 100 replaces the display of the home screen (e.g., user interface 504) with the display of the lock screen (e.g., user interface 506).

[0218] Figure 5A2 The unlocking of the device 100 is shown to display the user interface that was most recently displayed before locking. Figure 5A1 502 is locked, then when device 100 is unlocked from user interface 506, user interface 502 is displayed. Alternatively, if device 100 is unlocked by Figure 5A2 If path “2” in (eg, from user interface 504 ) is locked, then when device 100 is unlocked from user interface 506 , user interface 504 is displayed.

[0219] Figure 5A3 The process of initiating the shutdown of the device 100 in response to a long press on the button 501 is shown (eg, when the long press time threshold T LP Then, when the contact is lifted off the button 501). Figure 5A3 As shown, when the device 100 displays the application user interface (eg, user interface 502), when the button 501 is pressed for at least T LP , the device 100 initiates the process of shutting down the device (e.g., by displaying a user interface 508, a confirmation request for the user to confirm shutting down the power). Although not shown here, in some embodiments, when the button 501 is pressed for at least T LP , device 100 is immediately turned off without first displaying user interface 508.

[0220] Figure 5A4The previous application is shown being displayed in response to movement input on button 501. In one example, when device 100 displays an application user interface (e.g., user interface 502 of a first application), contact 511 slides button 501 upward along a predefined track, and in response, device 100 replaces the application user interface with another user interface (e.g., user interface 510 of a second application that was just active on device 100 before the first application). In another example, when device 100 displays an application user interface (e.g., user interface 502 of a first application), contact 513 slides button 501 downward along a predefined track, and in response, device 100 replaces the application user interface with another user interface (e.g., user interface 512 of a third application that was just active on device 100 before the second application). Although not shown here, in some embodiments, when contact 513 slides button 501 downward, device 100 stops displaying the current user interface and displays the home screen.

[0221] Figure 5A5 It is shown that according to different activations of button 501, a home screen (e.g., user interface 504) is displayed, a previous application (e.g., user interface 510) is displayed, or an application switching user interface (e.g., user interface 514) is displayed. Figure 5A5 As shown, device 100 initially displays an application user interface (e.g., user interface 502). When a press input is detected on button 501, device 100 replaces the display of the application user interface (e.g., user interface 502) with the display of the home screen (e.g., user interface 504). Alternatively, when a slide input is detected on button 501, device 100 replaces the display of the application user interface (e.g., user interface 502) with the display of the previous application (e.g., user interface 510). In another alternative, when a slide and hold input (or alternatively, a press and hold input) is detected on button 501, device 100 replaces the display of the application user interface (e.g., user interface 502) with the display of an application switching user interface (e.g., user interface 514).

[0222] Figure 5A6 5. It is shown that a preview of the application is displayed upon initial activation of button 501, and then the application is displayed upon completion of activation of button 501. Figure 5A6As shown, the device 100 is initially in a locked state (e.g., the screen is off). When an initial portion of input is detected on button 501 (e.g., an initial portion of an upward sliding input on button 501), the device 100 displays a preview of the last active application on the device (e.g., preview user interface 509). When the input on button 501 is completed (e.g., the sliding input on button 501 is completed (e.g., the button has reached a threshold position along the slider track before it is released)), the device 100 replaces the preview of the last active application (e.g., preview user interface 509) with the last active application (e.g., user interface 510). On the other hand, if the input on button 501 is not completed (e.g., the sliding input on button 501 is not completed (e.g., the button has not reached a threshold position along the slider track before it is released)), the device 100 stops displaying the preview of the last active application (e.g., preview user interface 509) and returns to the locked state (e.g., the screen is off).

[0223] Alternatively, Figure 5A7 5. The preview of the lock screen is shown when the activation of button 501 is initially performed, and then the lock screen is displayed when the activation of button 501 is completed. Figure 5A7 As shown, the device 100 is initially in a locked state (e.g., the screen is off). When the initial portion of the input is detected on button 501 (e.g., the initial portion of the upward sliding input on button 501), the device 100 displays a preview of the lock screen (e.g., preview user interface 505). When the input on button 501 is completed (e.g., the sliding input on button 501 is completed), the device 100 replaces the preview of the lock screen (e.g., preview user interface 505) with the lock screen (e.g., user interface 506). On the other hand, if the input on button 501 is not completed (e.g., the sliding input on button 501 is not completed), the device 100 stops displaying the preview of the lock screen (e.g., preview user interface 505) and returns to the locked state (e.g., the screen is off).

[0224] Figure 5B1-Figure 5B22 An exemplary user interface for displaying a taskbar and / or home screen of a device in response to a multi-stage gesture is shown according to some embodiments. The user interfaces in these figures are used to illustrate the process described below, including Figure 7A-7C. For ease of explanation, some embodiments in the implementation scheme will be discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on touch-sensitive display system 112. However, in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface on display 450 and the focus selector shown in the figure, similar operations are optionally performed on a device with display 450 and a separate touch-sensitive surface 451.

[0225] Figure 5B1-Figure 5B9 In response to detecting a multi-stage gesture, an application is opened from the home screen and then the device's taskbar (e.g., a container that includes a predefined set of application launch icons and is typically displayed at the bottom of the home screen) and / or the home screen are displayed. Figure 5B4-Figure 5B9 As shown, when the multi-stage gesture satisfies a first movement threshold (e.g., a short upward swipe), the taskbar is displayed, and when the multi-stage gesture satisfies a second movement threshold (e.g., a longer and / or faster upward swipe) that is greater than the first movement threshold, the home screen is displayed.

[0226] exist Figure 5B1-Figure 5B3 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 518, which launches the instant messaging application (e.g., user interface 520, Figure 5B3 ).

[0227] Figure 5B4-Figure 5B9 Contact 522 is shown moving from the bottom edge of device 100 (e.g., in a swipe gesture) and moving in an upward direction across touch screen 112. Figure 5B4-Figure 5B6 In FIG. 5 , when contact 522 moves upward, task bar 540 moves onto user interface 520 along with the movement of contact 522. Figure 5B7-Figure 5B9 , as the movement of contact 522 continues upward, the home screen (e.g., user interface 504) slides behind taskbar 540 and replaces the display of the instant messaging application (e.g., user interface 520). Figure 5B4-Figure 5B6 In the example, when the task bar 540 is superimposed on the instant messaging application, the task bar 540 is semi-transparent and Figure 5B7-Figure 5B9 In , when the taskbar 540 is superimposed on the home screen, the taskbar 540 is opaque. Figure 5B9In some embodiments, when the taskbar 540 is superimposed on the home screen, the application launch icons in the taskbar 540 are updated to include the most recently used applications on the device (e.g., instant messaging applications).

[0228] Figure 5B10 An example of a control center user interface object 542 is shown superimposed on a portion of the home screen (e.g., user interface 504). Figure 5B10 In the example of , control center user interface object 542 includes a set of standard controls for controlling different functions of device 100 (e.g., controls for turning on / off airplane mode, WiFi, Bluetooth, do not disturb mode, a screen brightness slider, etc.). In some embodiments, control center user interface object 542 is displayed when the multi-stage gesture satisfies a third movement threshold that is greater than the second movement threshold (e.g., a longer and / or faster swipe upward than the gesture to display the home screen). In some embodiments, after the home screen (e.g., user interface 504) is displayed, control center user interface object 542 is displayed in response to another swipe gesture, such as a swipe gesture similar to or the same as the swipe gesture performed by contact 522.

[0229] Figure 5B11 An alternative example of a control center user interface object 544 is shown superimposed on a portion of the home screen (e.g., user interface 504). Figure 5B11 In the example of FIG. 5 , the control center user interface object 544 includes a set of standard controls for controlling different functions of the device 100 (e.g., similar to the control center user interface object 542, Figure 5B10 ), and the control center user interface object 544 also includes a row for the taskbar. In some embodiments, the control center user interface object 544 is displayed when the multi-stage gesture satisfies a third movement threshold that is greater than the second movement threshold (e.g., a swipe upward that is longer and / or faster than the gesture to display the home screen). In some embodiments, after the home screen (e.g., user interface 504) is displayed, in response to another swipe gesture, such as a swipe gesture similar to or the same as the swipe gesture performed by contact 522, the control center user interface object 544 is displayed.

[0230] Figure 5B12 An example of a control center user interface object 546 is shown superimposed on a portion of an application user interface (e.g., user interface 504 of an instant messaging application). Figure 5B12 In the example of FIG. 5 , the control center user interface object 546 includes a set of standard controls for controlling different functions of the device 100 (e.g., similar to the control center user interface object 542, Figure 5B10), and the control center user interface object 546 also includes a row for the taskbar. In some embodiments, the taskbar is displayed when the multi-stage gesture satisfies a first movement threshold (e.g., a short upward swipe), and the control center user interface object 546 is displayed when the multi-stage gesture satisfies a third movement threshold greater than the first movement threshold (e.g., a longer and / or faster upward swipe). In some embodiments, after the taskbar 540 is displayed, the control center user interface object 546 is displayed in response to another swipe gesture, such as a swipe gesture similar to or the same as the swipe gesture performed by contact 522.

[0231] Figure 5B13-Figure 5B15 It is shown that according to some embodiments, (for example, in Figure 5B6 , after contact 522-c is lifted from device 100), an application user interface (e.g., user interface 520) with a taskbar 540 is displayed, and in response to contact 548 moving in an upward direction on touch screen 112 from a bottom edge of device 100 (e.g., with a swipe gesture), display of application user interface 520 is replaced with display of a home screen (e.g., user interface 504).

[0232] Figure 5B15-Figure 5B17 The home screen (e.g., user interface 504) is shown displayed, and in response to movement of contact 550 in a downward direction on touch screen 112 (e.g., in a swipe gesture), display of the home screen (e.g., user interface 504) is replaced with display of the user interface of the last active application on the device (e.g., user interface 520). Figure 5B17 As shown, in some embodiments, when the user interface of the last active application is displayed in response to a swipe down gesture, taskbar 540 is not superimposed on the user interface of the last active application (e.g., user interface 520). In some embodiments, when the user interface of the last active application is displayed in response to a swipe down gesture, taskbar 540 remains displayed and is superimposed on the user interface of the last active application (e.g., user interface 520).

[0233] Figure 5B18-Figure 5B20 The home screen (e.g., user interface 504) is shown displayed, and in response to movement of contact 552 in an upward direction on touch screen 112 (e.g., in a swipe gesture), display of the home screen (e.g., user interface 504) is replaced with display of the user interface of the last active application on the device (e.g., user interface 520). Fig.5B20As shown, in some embodiments, when the user interface of a previously active application is displayed in response to an upward swipe gesture, a taskbar 540 (e.g., having a translucent appearance) is displayed superimposed on the user interface of the previously active application (e.g., user interface 520).

[0234] Figure 5B20-Figure 5B22 An application user interface (eg, user interface 520 ) is shown displayed with a taskbar 540 , and in response to movement of contact 554 in a downward direction on touch screen 112 (eg, in a swipe gesture), the taskbar ceases to be displayed.

[0235] Figure 5C1-Figure 5C50 An exemplary user interface for displaying an on-demand virtual home button and activating the virtual home button to display a home screen in response to a continuous gesture is shown in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including FIG. 8A to FIG. 8D . For ease of explanation, some embodiments in the implementation scheme will be discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on touch-sensitive display system 112. However, in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface on display 450 and the focus selector shown in the figure, similar operations are optionally performed on a device with display 450 and a separate touch-sensitive surface 451.

[0236] Figure 5C1-Figure 5C9 The application is shown to be opened from the home screen, and then the taskbar including the home screen (e.g., a container including a predefined set of application launch icons and usually displayed at the bottom of the home screen) is displayed and the home button is activated. Figure 5C4-Figure 5C9 As shown, when the contact satisfies the home button display criteria (e.g., the contact moves upward from the bottom edge beyond a threshold position on the display), a taskbar with a home button is displayed, and when the contact satisfies the display home criteria (e.g., the characteristic intensity of the contact increases to above an intensity threshold after the contact moves upward), the home screen is displayed.

[0237] exist Figure 5C1-Figure 5C3 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 555, which launches the instant messaging application (e.g., user interface 520, Fig.5C3 ).

[0238] Figure 5C4-Figure 5C7 Contact 556 is shown moving from the bottom edge of device 100 (e.g., in a swipe gesture) and in an upward direction on touch screen 112. As contact 556 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 556 moves.

[0239] When device 100 detects contact 556 (e.g., Figure 5C8 The intensity of the contact 556-e in the embodiment exceeds the intensity threshold (e.g., the light press intensity threshold IT L ), the home screen (eg, user interface 504, Fig.5C9 In this example, contact 556-e (at Figure 5C8 (center) when on home button 559, exceeds the intensity threshold to activate home button 559.

[0240] Figure 5C9-Figure 5C16 The application is shown opened from the home screen, and then the taskbar including the home button is displayed and the home button is activated. Figure 5C12-Figure 5C16 As shown, when the contact satisfies the home button display criteria (e.g., the contact moves upward from the bottom edge beyond a threshold position on the display), a taskbar with a home button is displayed, and when the contact satisfies the display home criteria (e.g., the characteristic intensity of the contact increases to above an intensity threshold after upward movement of the contact, even if the contact is not on the home button), the home screen is displayed.

[0241] exist Figure 5C9-Figure 5C11 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 560, which launches the instant messaging application (e.g., user interface 520, Fig.5C11 ).

[0242] Figure 5C12-Figure 5C14 Contact 562 is shown moving from the bottom edge of device 100 (e.g., in a swipe gesture) and in an upward direction on touch screen 112. As contact 562 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 562 moves.

[0243] When device 100 detects contact 562 (e.g., Fig.5C15 The intensity of the contact 562-d in the embodiment exceeds the intensity threshold (e.g., the light press intensity threshold IT L ), the home screen (eg, user interface 504, Fig.5C16 ). Note that in this example, at contact 562-d (at Fig.5C15After moving beyond home button 559, the contact exceeds the intensity threshold. However, in response to a continued gesture of contact 562 (e.g., swiping up to display the home button and pressing without lifting off), device 100 displays the home screen (e.g., Fig.5C16 504) in the user interface without having to touch the home button to activate it.

[0244] Figure 5C16-Figure 5C24 The application is shown opened from the home screen, and then the taskbar including the home button is displayed and the home button is activated. Figure 5C19-Figure 5C24 As shown, when the contact satisfies the home button display criteria (e.g., the contact moves upward from the bottom edge beyond a threshold position on the display), a taskbar with a home button is displayed, and when the contact satisfies the display home criteria (e.g., the characteristic intensity of the contact increases to above an intensity threshold after upward movement of the contact, even if the home button is not yet fully revealed), the home screen is displayed.

[0245] exist Figure 5C16-Figure 5C18 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 564, which launches the instant messaging application (e.g., user interface 520, Fig.5C18 ).

[0246] Figure 5C19-Figure 5C20 Contact 566 is shown moving from the bottom edge of device 100 (e.g., in a swipe gesture) and in an upward direction on touch screen 112. As contact 566 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 566 moves.

[0247] When device 100 detects contact 566 (e.g., Fig.5C21 The intensity of the contact 566-c in the embodiment exceeds the intensity threshold (e.g., the light press intensity threshold IT L ), the home screen (eg, user interface 504, Figure 5C22-Figure 5C24 ). Figure 5C22-Figure 5C23 504) slides in behind the taskbar 568 to replace the display of the instant messaging application (e.g., user interface 520). In some embodiments, such as Figure 5C22-Figure 5C24 As shown, when the home screen is displayed, the home button 559 is not displayed in the taskbar 568. Note that in this example, before the home button 559 is fully revealed, contact 566-c (at Fig.5C21However, in response to a continued gesture of contact 566 (e.g., swiping up to display the home button and pressing without lifting off), device 100 displays the home screen (e.g., Fig.5C24 504) without fully revealing the home button to activate it.

[0248] In some embodiments, if contact 566 (e.g., contact 566-b, Fig.5C20 ) is lifted (e.g., contact 566 includes an initial upward movement to begin displaying the taskbar, but does not include sufficient distance and / or velocity to satisfy home button display criteria to fully reveal the home button), the taskbar 558 with the home button 559 retracts (e.g., a reverse animation of the animated transition is performed to display the taskbar), and only the user interface 520 is displayed.

[0249] Figure 5C24-Figure 5C32 The application is shown opened from the home screen, and then the taskbar including the home button is displayed and the home button is activated. Figure 5C19-Figure 5C24 As shown, when a contact satisfies the home button display criteria (e.g., the contact moves upward from the bottom edge to a threshold position on the display), a taskbar with a home button is displayed, and the home screen is displayed in response to an independent input (e.g., a tap input by another contact).

[0250] exist Figure 5C24-Figure 5C26 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 569, which launches the instant messaging application (e.g., user interface 520, Fig.5C26 ).

[0251] Figure 5C27-Figure 5C29 Contact 570 is shown moving from the bottom edge of device 100 and in an upward direction on touch screen 112 (e.g., in a swipe gesture). As contact 570 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 570 moves. Fig.5C30 , contact 570 is lifted off and task bar 558 with home button 559 remains displayed superimposed on user interface 520.

[0252] exist Figure 5C31-Figure 5C32 , device 100 detects input on home button 559, such as a tap gesture by contact 572, and displays a home screen (e.g., user interface 504, Figure 5C32 ).

[0253] Figure 5C32-Figure 5C40It is shown that an application is opened from the home screen, and then a task bar including a home button is displayed and an operation is performed in response to an independent input (e.g., a press input by another contact). Figure 5C35-Figure 5C40 As shown, when a first contact satisfies a home button display criteria (e.g., the contact moves upward from a bottom edge to a threshold position on the display), a taskbar with a home button is displayed, and in response to detecting a press input by a second contact (e.g., after the first contact is lifted off) (e.g., without an initial upward swipe), a photo preview is displayed.

[0254] exist Figure 5C32-Figure 5C34 , device 100 detects input on instant messaging application launch icon 524, such as a tap gesture by contact 574, which launches the instant messaging application (e.g., user interface 520, Fig.5C34 ).

[0255] Figure 5C35-Figure 5C36 Contact 576 is shown moving from the bottom edge of device 100 and in an upward direction on touch screen 112 (e.g., in a swipe gesture). As contact 576 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 576 moves. Figure 5C37 , contact 570 is lifted and task bar 558 with home button 559 remains displayed superimposed on user interface 520.

[0256] exist Figure 5C38-Figure 5C39 , device 100 detects input on photo thumbnail 579, such as a press input by contact 578-a, and displays a preview of the photo (e.g., photo preview 581, Fig.5C39 ). When contact 578 is lifted off, device 100 stops displaying photo preview 580 and displays the instant messaging application (e.g., user interface 520) (e.g., Fig.5C40 ). Figure 5C9-Figure 5C16 In contrast, in response to a continuous gesture of contact 562 (e.g., swiping up to display the home button and pressing without lifting off), device 100 displays the home screen, while Fig.5C38 In response to contact 562-d ( Fig.5C15 ) exceeds the intensity threshold and while on photo 579, contact 578-a is a separate contact from the contact that displays the taskbar (and is not Figure 5C9-Figure 5C16 For illustrative purposes, Fig.5C39 The position of contact 578 in Fig.5C15 The locations of contacts 562 in are the same, but because the press inputs for these contacts are part of different gestures, they produce different results.

[0257] Figure 5C40-Figure 5C50 Shown is a task bar including a home button, a control center including the task bar, and activating a control in the control center. Figure 5C40-Figure 5C47 As shown, when the contact meets the home button display criteria (e.g., the contact includes an upward swipe), a taskbar with a home button is displayed, and when the contact meets the swipe control center display criteria (e.g., the contact includes a continuous movement greater than the home button display criteria), the control center is displayed.

[0258] Figure 5C41-Figure 5C44 Contact 582 is shown moving from the bottom edge of device 100 (e.g., in a swipe gesture) and in an upward direction on touch screen 112. As contact 582 moves upward, taskbar 558 (with home button 559) moves onto user interface 520 as contact 582 moves.

[0259] like Figure 5C45 As shown, when the device 100 detects that the contact 582 continues to swipe upward (e.g., above a movement threshold, such as 1 / 7 of the display height) after the task bar 558 (with the home button 559) is displayed, the control center 584 (which optionally includes the task bar 558) is displayed superimposed on the user interface 520. In some embodiments, as Figure 5C46 As shown, when contact 582 moves upward (e.g., continuing the swipe gesture), control center 584 moves to user interface 520 as contact 582 moves. Figure 5C47 , contact 582 is lifted off, and control center 584 remains displayed superimposed on user interface 520.

[0260] exist Figure 5C48-Figure 5C50 , device 100 detects input on the Wi-Fi control settings in control center 584, such as by contact 586-a ( Fig.5C48 ), which opens the Wi-Fi settings menu ( Fig.5C49 ), and in response to selecting to turn off Wi-Fi for one hour (e.g., by lifting the Fig.5C49 Contact 586-b), turn Wi-Fi off ( Fig.5C50 middle).

[0261] Figure 6A-6E 600 is a flowchart illustrating a method 600 for displaying a home screen without locking the device or without locking the device based on different activations of a button according to some embodiments. The method 600 is performed on an electronic device (e.g., device 300, Figure 3 ; or a portable multifunction device 100, Figure 1A) is performed on a touch-sensitive surface. In some embodiments, the electronic device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the touch-sensitive surface and the display are integrated into a touch-sensitive display. In some embodiments, the display is a touch screen display, and the touch-sensitive surface is on the display or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 600 are optionally combined, and / or the order of some operations is optionally changed.

[0262] This method involves displaying a home screen without locking the device, or locking the device, depending on whether a second activation of the button is detected after the initial activation of the button. Specifically, after the initial activation of the button, if the second activation of the button is not detected within a threshold amount of time, the home screen is displayed without locking the device; if the second activation of the button is detected within the threshold amount of time, the device is locked (e.g., without first displaying the home screen). Responding to different activations of a single button to display the home screen without locking the device (e.g., when the button is activated in a first manner) and to lock the device without displaying the home screen (e.g., when the button is activated in a second manner) provides an intuitive and efficient way for users to access these commonly used functions and avoid accidentally locking the device when going to the home screen and unnecessary user interface switching when locking the device, thereby enhancing the operability of the device and making the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0263] Device (e.g., device 100, Fig.5A1 ) When the device is in an unlocked state, detecting (602) a button of the device (e.g., button 501, Fig.5A1 , or in other embodiments, the button is a virtual home button, a solid-state home button, or a mechanical home button) (e.g., when activated in a predetermined manner (e.g., upon a single press), the device's home button releases a currently displayed user interface and displays the device's home screen, such as user interface 504, Fig.5A1 ), the sequence including at least a first activation of a button (e.g., a tap or light press input), wherein a corresponding application user interface (e.g., user interface 502, Fig.5A1) when the first activation of the button is detected (e.g., a state in which one or more functions disabled in the device locked state are enabled). In some embodiments, the locked state of the device is a state in which the device is prevented from performing one or more functions, such as displaying the home screen, launching an application, accessing personal information (such as a photo gallery, electronic messages, electronic documents, contact information). In some embodiments, the unlocked state of the device is a state in which the device is enabled to perform one or more functions that are prevented when the device is in the locked state. In some embodiments, the device is limited to providing limited access to a class of information in the locked state (e.g., the subject and / or fragment of the most recently received electronic message, the photo taken when the device is in the locked state, the upcoming calendar event), while the device provides access (e.g., full access) to more than limited access to the type of information in the unlocked state (e.g., the complete content of a larger group of electronic messages, all photos stored on the device, all calendar events stored on the electronic device, etc.). In some embodiments, destructive operations permitted in the unlocked state are blocked in the locked state (e.g., in the locked state, electronic messages, photos, contacts, and / or electronic documents cannot be deleted from the device, while in the unlocked state, electronic messages, photos, contacts, and / or electronic documents can be deleted from the device). In some embodiments, the device requires user authentication (e.g., biometric authentication, such as fingerprint, facial detection, iris scan, or input mode authentication, such as a password, passcode, or touch input mode) in order to transition from a locked state to an unlocked state. In some embodiments, the locked state is used to prevent accidental input rather than or in addition to preventing unauthorized access to the device, and a predefined unlock input is required to unlock the device (e.g., placing a finger on a fingerprint sensor, pressing a hardware button, swiping across a display, activating an intensity-sensitive input element, etc.). The device responds to detecting a sequence of one or more activations of a button of the device (604): based on determining that a first activation of the button has been detected, after a corresponding threshold amount of time has passed since the first activation of the button has been detected (e.g., a double-click time threshold, such as a threshold time threshold). Fig.5A1 If a second activation of the button is not detected before the time T in the corresponding threshold time amount, the corresponding application user interface (e.g., user interface 502, Fig.5A1 ) is replaced by the display of the device home screen (eg, user interface 504, Fig.5A1 ), while keeping the device unlocked (e.g., a single press input on the home button causes the home button to be displayed, such as Fig.5A1 and based on determining that a first activation of the button is detected and a second activation of the button is detected before a corresponding threshold amount of time has passed since the first activation of the button is detected, the device displays a corresponding application user interface (e.g., user interface 502, Fig.5A1) is switched from an unlocked state to a locked state (eg, user interface 506, Fig.5A1 ) (For example, detecting two presses within the double-click time threshold causes the device to turn off the screen or lock the screen instead of going to the home screen first, such as Fig.5A1 In some embodiments, detecting a first activation of a button includes (606) detecting a button (e.g., button 501, Fig.5A1 ) on a first press input that satisfies a first click criterion (e.g., the first click criterion includes a requirement that is satisfied when the contact intensity in the first input is above a first intensity threshold (e.g., a down click intensity threshold). In some embodiments, the first click criterion also requires that the contact in the first activation is substantially stationary (e.g., the contact moves less than a threshold amount of movement) before lift-off of the contact is detected or within a threshold amount of time after the contact is initially detected. In some embodiments, the first click criterion also requires that the contact is not maintained for more than a second threshold amount of time (e.g., as Figure 5A3 The long press time threshold shown, such as T LP ), the second threshold amount of time being greater than the first threshold amount of time (e.g., Fig.5A1 In some embodiments, the first click criterion further requires that after the intensity of the contact increases to above the first intensity threshold (e.g., when both a downward click and an upward click are detected), the intensity of the contact decreases to below a second intensity threshold that is equal to or less than (e.g., lighter) the first intensity threshold. Displaying the device's home screen in response to a first way of activating a button (e.g., using a downward click) (and locking the device in response to a second way of activating a button) enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating the need for the user to find and activate additional buttons / indications, and by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0264] In some embodiments, detecting a second activation of a button includes (608) detecting a button (eg, button 501, Fig.5A1) on a button that satisfies a second click criterion. In some embodiments, the second click criterion is the same as the first click criterion, or has a lower strength requirement than the first click criterion (e.g., the second press input is a lighter press input than the first press input), or has a higher strength requirement than the first click criterion (e.g., the second press input is a heavier press input than the first press input). In some embodiments, the first activation and the second activation of the button are performed by the same continuous contact. In some embodiments, the first activation and the second activation of the button are performed by two independent contacts. In some embodiments, the first click criterion requires detection of both a downward click and an upward click, while the second click criterion does not require detection of an upward click of the second click. Locking the device in response to a second manner of activating a button (e.g., using a double press or double click) (and displaying the home screen in response to a first manner of activating the button) enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating the need for the user to locate and activate additional buttons / indications, and by helping the user achieve desired results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0265] In some embodiments, switching the device from an unlocked state in which a corresponding application user interface is displayed to a locked state includes (610) switching from displaying the corresponding application user interface (e.g., user interface 502, Fig.5A1 ) switches to displaying a lock screen user interface (eg, user interface 506, Fig.5A1 ) without displaying the device's home screen (e.g., when switching from a corresponding application user interface to displaying a lock screen user interface, the corresponding application user interface does not transition to the home screen before displaying the lock screen, such as Fig.5A1 By displaying a lock screen user interface without displaying the device's home screen to lock the device, the visual feedback provided to the user is improved (e.g., by making the device appear more responsive to user input), the operability of the device is enhanced, and the user-device interface is made more efficient (e.g., by helping the user achieve desired results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0266] In some embodiments, switching the device from an unlocked state in which a corresponding application user interface is displayed to a locked state includes (612) turning off the display without displaying the device's home screen (e.g., when switching from the corresponding application user interface to turning off the display, the corresponding application user interface does not transition to the home screen until the display is turned off). Locking the device by turning off the display without displaying the device's home screen improves visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results with required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0267] In some embodiments, in response to detecting one or more activations of a button of the device, a sequence (614) is performed: based on determining that a first activation of the button is detected and a corresponding threshold amount of time (e.g., time T, Fig.5A1 ), the device displays the home screen in response to detecting the first activation of the button, and while the device home screen is displayed on the display, the device switches the device from an unlocked state to a locked state in response to detecting the second activation of the button (e.g., two separate clicks on the home button cause the device to display the home screen after the first click and then enter the locked state (e.g., display the lock screen or turn off the display) after the second click, as described above Fig.5A1 ). In some embodiments, detecting the second activation of the button includes detecting a downward click on the button without detecting an upward click on the button. In some embodiments, the second activation of the button includes both a downward click and an upward click on the button. When two independent clicks on the button are detected, the home screen is displayed after the first click and the device is locked after the second click, improving the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhancing the operability of the device, and making the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0268] In some embodiments, after detecting the second activation of the button and while the device is in a locked state, the device detects (616) a third activation of a button to unlock the device (e.g., Figure 5A2) (e.g., detecting a third activation of the button includes detecting a third press input that satisfies the first click criteria and satisfies the authentication criteria (e.g., contact matches the authentication fingerprint)); in response to detecting a third activation of the button that unlocks the device: detecting a second activation of the button after a corresponding threshold amount of time has passed since the first activation of the button was detected (e.g., displaying the home screen of the device just before locking the device, as shown in FIG. 1 ); Fig.5A1 ), the device unlocks the device to display the home screen of the device (e.g., as shown in path "2" of Figure 5A2 ) (e.g., if the user has used a slow double-click (interrupted by two separate single-click inputs) to lock the device, then, upon unlocking by a third activation of the button, displaying the home screen); and based on determining that a second activation of the button is detected before a corresponding threshold amount of time has passed since a first activation of the button was detected (e.g., displaying a corresponding application user interface immediately before locking the device, such as Fig.5A1 ), the device unlocks the device to display a corresponding application user interface (e.g., as shown in path “1” of Figure 5A2 ) (e.g., if the user had used a quick double-click (interpreted as a single double-click input) to lock the device, then the user interface of the last active application is displayed upon the third activation of the button). Unlocking the device to display the most recently displayed user interface (before locking) allows the user to quickly return to the home screen or application without further user input. Performing operations when a set of conditions have been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0269] In some embodiments, in response to detecting one or more activations of a button of the device, a sequence (618) is performed: detecting a first activation of the button satisfies a long press criterion based on determining that the first activation of the button satisfies a long press criterion, wherein the long press criterion requires that the first activation of the button is maintained for at least a threshold duration (e.g., a long press time threshold, such as Figure 5A3 T LP , which is longer than the double-click time threshold) without detecting a second activation so that the long press criteria are met (e.g., the contact is maintained for more than a threshold amount of time after the contact intensity exceeds the first intensity threshold or while the contact intensity remains above the first intensity threshold for more than a threshold amount of time, or a physical button mechanism is pressed for a threshold duration), the device initiates a process to turn off the device (e.g., as Figure 5A3Turning off the device in response to a third way of activating a button (e.g., using a long press) (e.g., turning off the device immediately or displaying a confirmation request for the user to confirm before turning off the device). Turning off the device in response to a third way of activating a button (e.g., using a long press) (and displaying a home screen or locking the device in response to a different way of activating the button) enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating the need for the user to find and activate additional buttons / indications, and by helping the user achieve the desired results with the required inputs and reducing user errors in operating the device / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0270] In some embodiments, in response to detecting one or more activations of a button of the device, the sequence (620) includes: the device displays, in response to detecting a first activation of the button (e.g., activation by a first press input that satisfies a first click criterion), an application user interface (e.g., user interface 502, Fig.5A1 ) to the device home screen (e.g., user interface 504, Fig.5A1 ); and after displaying the start of the animated transition from the corresponding application user interface to the device home screen, the device pauses the animated transition from the corresponding application user interface to the device home screen, wherein: based on determining that a second activation of the button is not detected before a corresponding threshold amount of time has passed since the first activation of the button was detected, replacing the display of the corresponding application user interface with the display of the device home screen includes continuing the animated transition from the corresponding application user interface to the device home screen after the corresponding threshold amount of time has passed (e.g., resuming the animated transition when a second click is not detected within the double-click interval); and based on determining that the second activation of the button is detected before a corresponding threshold amount of time has passed since the first activation of the button was detected, switching the device from an unlocked state in which the corresponding application user interface is displayed to a locked state includes locking the device (e.g., displaying user interface 506, Fig.5A1 ) without resuming the animation transition (e.g., not resuming the animation transition when a second click is detected within the double-click interval). Starting the animation transition before the sequence of activation of the button is fully determined improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0271] In some embodiments, in response to detecting one or more activations of a button of the device, a sequence (622) is performed: according to determining that a corresponding threshold amount of time (e.g., time T, Fig.5A1 ) before detecting a second activation of the button, the corresponding application user interface (e.g., user interface 502, Fig.5A1 ) is replaced by the display of the device home screen (e.g., user interface 504, Fig.5A1 ) includes displaying an animated transition from a corresponding application user interface to a device home screen that begins after a corresponding threshold amount of time has elapsed (e.g., starting the animated transition after the device determines that a second click has not been detected within the double-click interval), and based on determining that a second activation of the button is detected before a corresponding threshold amount of time has elapsed since a first activation of the button was detected, the device locks the device (e.g., displays user interface 506, Fig.5A1 ) without displaying an animated transition (e.g., without displaying an animated transition when a second tap is detected within the double-tap interval). Displaying an animated transition to the home screen (when accessing the home screen) or locking the device (when locking the device) without displaying an animated transition improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0272] In some embodiments, in response to detecting a sequence of one or more activations of a button of the device (624): based on determining that detecting one or more activations of the button includes detecting a first movement input that satisfies an application switching criterion (e.g., the application switching criterion requires that the home button moves along a predefined track exceeding a first threshold distance (e.g., 20 pixels or 5 mm)) in order to satisfy the application switching criterion; or the application switching criterion requires that contact on the home button moves in a corresponding direction exceeding a threshold distance in order to satisfy the application switching criterion, the device displays a corresponding application user interface (e.g., user interface 502, Figure 5A4 ) is replaced with a second user interface (eg, user interface 510, Figure 5A4 ), the second user interface corresponds to another application that was active on the device immediately before the application corresponding to the corresponding application user interface (e.g., Figure 5A4 In some embodiments, detecting the first movement input includes detecting a button (eg, button 501, Figure 5A4) along a predefined track on the device. For example, the first movement input slides the home button upward along a predefined track of a slider button (e.g., disposed on an edge of the device adjacent to the display) (e.g., as Figure 5A4 In some embodiments, movement of the button is not necessary, and movement of the contact on the button or along an edge of the device (e.g., a side of the device adjacent to the display) (e.g., swiping up along a touch-sensitive (e.g., capacitive) edge of the device) performs the same function. In some embodiments, swiping down on the button (e.g., as shown in FIG. 5 ) performs the same function. Figure 5A4 513 in the figure) or swiping along a touch-sensitive (e.g., capacitive) edge of the device so that the device stops displaying the current user interface (e.g., user interface 502, Figure 5A4 ) and display another user interface (eg, user interface 512, Figure 5A4 ) or display the home screen. In some embodiments, when an upward swipe on the home button or along a touch-sensitive (e.g., capacitive) edge of the device is detected, the currently displayed application user interface shrinks toward its corresponding application icon to display the home screen (a reverse animation of the animation played when the application icon is clicked to launch the application). Displaying the previous application in response to movement input on the button (and displaying another application or displaying the home screen or locking the device in response to different ways of activating the button) enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating the need for the user to find and activate additional buttons / indications, and by helping the user achieve the desired results with the required input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0273] In some embodiments, (before displaying a corresponding user interface (e.g., a user interface other than the home screen, such as user interface 502, Figure 5A5 ) or when the device is in a locked state (e.g., when the screen is turned off or a lock screen user interface is displayed)), the device detects (626) a fourth activation of the button; in response to detecting the fourth activation of the button: according to determining that the detection of the fourth activation of the button includes detecting a fourth input on the button that satisfies a go-to-home criterion, wherein the go-to-home criterion requires that the fourth input satisfies the first click criterion and the home screen of the device is not displayed when the fourth input is detected so as to satisfy the go-to-home criterion (e.g., the go-to-home criterion requires that the fourth input is a press input detected on the home button when the display is turned off or when a user interface other than the home screen is displayed): the device displays the home screen of the device (e.g., user interface 504, Figure 5A5) (and optionally, unlocking the device if the device is locked); based on determining that detecting a fourth activation of the button includes detecting that a fifth input on the button satisfies a go-to-application criterion, wherein the go-to-application criterion requires that the fifth input satisfies a first movement criterion (e.g., the go-to-application criterion requires that the fifth input is the home button moving upward along a slider track of the home button exceeding a first threshold distance, or the fifth input is moving upward on the home button exceeding a threshold distance), so that the go-to-application criterion is satisfied: the device displays a user interface of a last active application on the device (e.g., user interface 510, Figure 5A5 ) (e.g., the application that was active just before the screen was turned off, or the application that was active just before switching to the application corresponding to the currently displayed user interface, or if the home screen is the currently displayed user interface, the application that was active just before switching to the home screen) (and optionally, unlocking the device if it is locked). In some embodiments, the go-to-application criterion can also be met by swiping upward along a touch-sensitive (e.g., capacitive) edge of the device for more than a corresponding threshold distance. In some embodiments, in response to detecting the release of a button (e.g., by reducing the intensity of the contact to below a release threshold intensity, or by lifting the contact), or detecting that the button has been restored to its default position, the device maintains displaying the user interface of the last active application. Displaying the device's home screen in response to a first manner of activating a button (e.g., using a downward click) and displaying the last active application on the device in response to a different manner of activating a button (e.g., using a movement input) enhances the device's operability and makes the user-device interface more efficient (e.g., by eliminating the need for the user to find and activate additional buttons / indicators, and by helping the user achieve intended results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the device's battery life by enabling the user to use the device more quickly and efficiently.

[0274] In some embodiments, in response to detecting a fourth activation of the button: based on determining that detecting the fourth activation of the button includes detecting an initial portion of a fifth input that satisfies a preview criterion, wherein the preview criterion requires that the initial portion of the fifth input satisfies a second movement criterion (e.g., the second movement criterion requires a threshold movement (e.g., 5 pixels or 2 mm) that is less than the first movement criterion) in order to satisfy the preview criterion, the device displays (628) a preview of the user interface of the last active application on the device (e.g., preview user interface 509, Figure 5A6) (e.g., displaying at least a portion of a snapshot of the last active application on the device) (if the device is not locked, or, optionally, unlocking the device if the device is locked). Displaying a preview of the last active application upon activation of a button that would initiate the last active application improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input and allowing the user to decide whether to continue with the current input after seeing the preview), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0275] In some embodiments, in response to detecting a fourth activation of the button: based on determining that detecting the fourth activation of the button includes detecting an initial portion of a fifth input that satisfies a preview criterion, wherein the preview criterion requires that the initial portion of the fifth input satisfies a second movement criterion (e.g., the second movement criterion requires a smaller threshold movement (e.g., 5 pixels or 2 mm) than the first movement criterion) in order to satisfy the preview criterion, if the device is locked, the device displays (630) a preview of the lock screen interface (e.g., preview user interface 505, Figure 5A7 ) (e.g., displaying at least a portion of the lock screen user interface). Displaying a preview of the lock screen user interface upon activation of a button that would lead to the lock screen user interface improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input and allowing the user to decide whether to continue with the current input after seeing the preview), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0276] In some embodiments, while displaying the preview, the device detects (632) termination of the fifth input on the button (e.g., detecting the release of the home button, where the contact strength decreases to below the corresponding threshold strength (e.g., the release strength threshold or the up-click strength threshold) or the contact is lifted); in response to detecting the termination of the fifth input on the button: based on determining that the fifth input satisfies the preview criteria and does not meet the go-to-application criteria (e.g., the fifth input does not meet the first move criteria), the device stops displaying the preview (e.g., a preview of the user interface of the last active application on the device, or a preview of the lock screen user interface when the fifth input is terminated) when the fifth input is terminated (e.g., as described above, respectively). Figure 5A6 and Figure 5A7In some embodiments, in response to detecting termination of the fifth input on the button, based on determining that the fifth input satisfies the go-to-application criteria after the preview criteria are met, the device stops displaying the preview and displays the user interface of the last active application (e.g., user interface 510, Figure 5A6 ) or lock screen (eg, user interface 506, Figure 5A7 Displaying a preview of the user interface at the beginning of activation of a button that will lead to the user interface and ceasing to display the preview when the button activation is not completed improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input and allowing the user to decide whether to continue with the current input after seeing the preview), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0277] In some embodiments, in response to detecting termination of the fifth input on the button: based on determining that the fifth input satisfies the preview criteria and does not satisfy the transition to application criteria, the device turns off (634) the display when the fifth input terminates (e.g., Figure 5A6 and Figure 5A7 509 and the return arrows from preview user interface 505 to user interface 516). In some embodiments, in response to detecting termination of the fifth input on the button, the device stops displaying the preview and turns off the display based on determining that the fifth input satisfies the transition to application criteria after the preview criteria are met. Turning off the display on the device when the button is not activated improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input and allowing the user to decide whether to continue with the current input after seeing the preview), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0278] In some embodiments, in response to detecting a fourth activation of the button: based on determining that detecting the fourth activation of the button includes detecting a sixth input that satisfies the application switching criteria, wherein the application switching criteria requires that the sixth input includes a movement input that satisfies the first movement criteria and the first duration criteria (e.g., the home button is held at or above a threshold position (e.g., 20 pixels or 5 mm) away from its default position for more than a threshold amount of time (e.g., 1 second)) in order to satisfy the application switching criteria: optionally, the device stops displaying the user interface of the last active application (e.g., user interface 502, Figure 5A5 ); the device displays (636) an application switching user interface (e.g., user interface 514, Figure 5A5 ), which includes representations (e.g., optionally reduced-size live previews or snapshots) of currently active applications and one or more suspended applications on the device (and optionally a representation of the home screen). Displaying an application switching user interface in response to movement input on a button that meets movement and duration criteria (and displaying a home screen or locking the device in response to different ways of activating the button) enhances the operability of the device and makes the user-device interface more efficient (e.g., by eliminating the need for the user to find and activate additional buttons / affordances, and by helping the user achieve desired results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0279] It should be understood that Figure 6A-6E The specific order in which the operations in the description are described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., method 700 and method 800) are also applicable in a similar manner to the details of the processes described above in conjunction with Figure 6A-6E Method 600 is described. For example, the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described above with reference to method 600 optionally have one or more of the characteristics of the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described herein with reference to other methods described herein (e.g., methods 700 and 800). For the sake of brevity, these details are not repeated here.

[0280] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to Figure 1A and Figure 3 described) or application-specific chips.

[0281] References Figure 6A-6E The operation described may be optionally performed by Figure 1A-1B . For example, the detection operation 602 and the replacement / switching operation 604 are optionally implemented by the event classifier 170, the event identifier 180, and the event handler 190. The event monitor 171 in the event classifier 170 detects contact on the touch-sensitive display 112, and the event distributor module 174 transmits the event information to the application 136-1. The corresponding event identifier 180 of the application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface (or whether the rotation of the device) corresponds to a predefined event or sub-event, such as the selection of an object on the user interface, or the rotation of the device from one orientation to another orientation. When the corresponding predefined event or sub-event is detected, the event identifier 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally uses or calls the data updater 176 or the object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know that based on Figure 1A to Figure 1B How the components depicted in the figure can implement other processes.

[0282] Figure 7A-7C 700 is a flowchart illustrating a method 700 for displaying a taskbar and / or a home screen of a device in response to a multi-stage gesture according to some embodiments. The method 700 is performed on an electronic device (e.g., device 300, Figure 3 ; or a portable multifunction device 100, Figure 1A ) is performed on a touch-sensitive surface. In some embodiments, the electronic device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the touch-sensitive surface and the display are integrated into a touch-sensitive display. In some embodiments, the display is a touch screen display, and the touch-sensitive surface is on the display or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0283] The method involves displaying a taskbar (e.g., a container that includes a predefined set of application launch icons and is typically displayed at the bottom portion of a home screen) and / or a home screen of a device in response to detecting a multi-stage gesture, wherein the taskbar is displayed when the multi-stage gesture satisfies a first movement threshold (e.g., a short upward swipe), and the home screen is displayed when the multi-stage gesture satisfies a second movement threshold greater than the first movement threshold (e.g., a longer and / or faster upward swipe). The gesture for bringing up the taskbar and the home screen is optionally two separate gestures or a single continuous gesture. Providing the taskbar or the home screen according to movement parameters of a movement input allows a user to reach a desired user interface state (e.g., displaying only the taskbar or displaying the home screen) by controlling the movement parameters of a single movement input. Reducing the number of inputs required to perform these operations (e.g., displaying the taskbar or displaying the home screen) enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0284] Device (e.g., device 100, Figure 5B1 ) on a display (e.g., touch screen 112, Figure 5B1 ) displays (702) a home screen (eg, user interface 504, Figure 5B1 ), wherein the home screen includes a plurality of application launch icons corresponding to a plurality of applications installed on the device (e.g., application launch icons 524-538, Figure 5B1 ) (e.g., multiple application launch icons are arranged in a grid on the home screen, and optionally, the home screen also includes one or more desktop applets). When the home screen is displayed, the device selects the first application launch icon (e.g., the instant messaging application launch icon 524, Figure 5B2 ) detects (704) a first input by a first contact that satisfies the application launch criteria (e.g., a tap gesture by contact 518, Figure 5B2 )(For example, the first input is a tap on the first application launch icon, such as Figure 5B2 In response to detecting a first input (e.g., an input such as a tap input) that satisfies the application launch criteria on the first application launch icon, the device displays the home screen (e.g., user interface 504, Figure 5B2 ) is replaced (706) with a first user interface of the first application corresponding to the first application launch icon (eg, user interface 520, Figure 5B3 ). When displaying the first user interface (eg, user interface 520, Figure 5B4 ), the device detects (708) a second contact (eg, contact 522, Figure 5B4-Figure 5B9 ), the second input comprising movement on the display in a first direction (e.g., upward). In response to detecting the second input (710): in accordance with determining that the second input satisfies the taskbar display criteria, wherein the taskbar display criteria requires that the second input comprises movement of a movement parameter (e.g., distance and / or speed) of the second contact having a magnitude greater than a first movement threshold (e.g., a distance greater than 1 / 10 of the screen height, or a speed greater than 200 pixels per second) in order to satisfy the taskbar display criteria, the device displays an image superimposed on the first user interface (e.g., user interface 520, Figure 5B5-Figure 5B6 ) on a portion of a user interface object (e.g., taskbar 540, Figure 5B5-Figure 5B6 ), wherein the user interface object (e.g., a taskbar) includes a first subset of application launch icons from a plurality of application launch icons (excluding a virtual home button); and based on determining that the second input satisfies the home display criteria, wherein the home display criteria requires that the second input includes movement of a movement parameter (e.g., distance and / or speed) of the second contact having a magnitude greater than a second movement threshold (e.g., a distance greater than 1 / 5 of the screen height, or a speed greater than 400 pixels per second) that is greater than the first movement threshold, the device displays the first user interface (e.g., user interface 520, Figure 5B7-Figure 5B8 ) is replaced with the home screen (eg, user interface 504, Figure 5B9 ) (e.g., while continuing to display user interface objects, Figure 5B7-Figure 5B9 In some embodiments, the taskbar display criteria and the home display criteria are satisfied by the same input (e.g., a swipe input starting from the bottom or bottom edge of the touch-sensitive display or some other predefined location and moving in a predefined direction (e.g., upward) more than a first threshold distance, such as by Figure 5B4-Figure 5B9 In some embodiments, an input satisfies the taskbar display criteria but does not satisfy the home display criteria (e.g., a swipe input starting from the bottom or bottom edge of the touch-sensitive display or some other predefined location and moving in a predefined direction (e.g., upward) beyond a second threshold distance that is less than the first threshold distance, such as a swipe input made by contact 522 in the touch-sensitive display). Figure 5B4-Figure 5B6In some embodiments, when the input satisfies the speed requirement (e.g., a swipe input that starts from the bottom or bottom edge of the touch-sensitive display or some other predefined location and moves in a predefined direction (e.g., upward) more than a second threshold distance that is less than the first threshold distance), the input satisfies both the taskbar display criteria and the home display criteria without satisfying the distance requirement. In some embodiments, both a long upward swipe and a short quick flick may satisfy both the taskbar display criteria and the home display criteria. In some embodiments, when the second input does not satisfy the taskbar display criteria, a portion of the taskbar may optionally be displayed in response to movement of the second contact, but when termination of the second input is detected and the taskbar display criteria is not satisfied, the portion of the taskbar is stopped from being displayed (e.g., retracted). In some embodiments, if the second input satisfies the taskbar display criteria and does not satisfy the home display criteria, the taskbar is displayed and the home screen is not displayed (e.g., as shown in FIG. 1 ). Figure 5B4-Figure 5B6 When the taskbar is displayed, a third input by a third contact that satisfies the home display criteria (e.g., an upward swipe on the taskbar) may also bring up the home screen from behind the taskbar and above the first user interface (e.g., as shown in FIG. Figure 5B13-Figure 5B15 In some embodiments, once the taskbar is displayed simultaneously with the home screen, it becomes part of the home screen and is dismissed along with the home screen when a gesture for dismissing the home screen is detected (e.g., as shown in FIG. Figure 5B15-Figure 5B17 shown).

[0285] In some embodiments, displaying the user interface object superimposed on a portion of the first user interface includes (712) displaying the user interface object superimposed on a portion of the first user interface based on the second contact (e.g., contacts 522-b and 522-c, Figure 5B5-Figure 5B6 ) (e.g., the taskbar slider slides over the first user interface at a rate based on the movement of the second contact) to move the user interface object (e.g., the taskbar 540, Figure 5B5-Figure 5B6 ) moves to a first user interface (eg, user interface 520, Figure 5B5-Figure 5B6) on that portion of the first user interface. For example, when the movement of the second contact is faster, the taskbar slides faster, and when the movement of the second contact is slower, the taskbar slides slower. In some embodiments, the lift-off of the second contact is detected before the taskbar is fully revealed, and after the lift-off of the second contact is detected, the taskbar continues to slide above the first user interface due to simulated inertia. The initial speed of the taskbar after the second contact is lifted is based on the speed of the second contact before the second contact is lifted. Moving the taskbar above the first user interface at a rate based on the movement of the second contact improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0286] In some embodiments, replacing display of the first user interface with display of the home screen includes (714): displaying a user interface object superimposed on the portion of the first user interface; and displaying an animated transition of the home screen replacing display of the first user interface while continuing to display the user interface object (e.g., the taskbar remains on the display and the home screen slides behind the taskbar) (e.g., as shown in FIG. 7 ). Figure 5B5-Figure 5B8 The animated transition of displaying the home screen in place of the first user interface while continuing to display the taskbar improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0287] In some embodiments, according to the second contact (e.g., contact 522, Figure 5B7-Figure 5B9) is displayed (716) with an animated transition of the home screen replacing the display of the first user interface at a rate of movement of the second contact (e.g., the home screen slides onto the display at a rate based on the movement of the second contact). For example, when the movement of the second contact is faster, the home screen slides faster, and when the movement of the second contact is slower, the home screen slides slower. In some embodiments, the movement rate of the home screen is selected to simulate direct manipulation of the home screen so that the home screen slides onto the display at the same rate as the second contact moves on the display. In some embodiments, the lift-off of the second contact is detected before the home screen is fully revealed, and after the lift-off of the second contact is detected, the home screen continues to slide over the first user interface due to simulated inertia. In some embodiments, the lift-off of the second contact is detected before the home screen is fully revealed, and after the lift-off of the second contact is detected, the home screen slides in over the first user interface (e.g., when the second contact has a speed greater than a predetermined threshold speed (e.g., 400 pixels per second) before the lift-off). In some embodiments, the initial speed of the home screen sliding in after the second contact is lifted off is based on the speed of the second contact before the second contact is lifted off. In some embodiments, the home screen slides upward relative to the second contact (e.g., once the taskbar is fully revealed, the home screen moves upward from behind the taskbar faster than the second contact moves upward) (e.g., as Figure 5B7-Figure 5B9 The animated transition of displaying the home screen instead of the first user interface at a rate based on the movement of the second contact improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0288] In some embodiments, in response to detecting a second input (718): based on determining that the second input satisfies a control center criterion, wherein the control center criterion requires that the second input includes movement of a movement parameter (e.g., distance and / or speed) of the second contact having a magnitude greater than a third movement threshold (e.g., a distance greater than 1 / 3 of the screen height, or a speed greater than 500 pixels per second) that is greater than the second movement threshold, the device displays a control center user interface object (e.g., at Figure 5B10-Figure 5B12, which includes a control center user interface object 542, 544, or 546 in the home screen that includes multiple controls for controlling different functions of the device (e.g., controls for turning on / off WiFi, Bluetooth, flash, do not disturb mode, airplane mode, a screen brightness slider, and other controls that can also be accessed through a settings user interface or application on the device). In some embodiments, before replacing the display of the first user interface with the display of the home screen (e.g., as shown in FIG. Figure 5B10 In some embodiments, the control center user interface is superimposed on a portion of the home screen (e.g., on top of the taskbar) after the second input is displayed. When the control center appears above the home screen, the home screen remains displayed. In some embodiments, when the movement of the second contact has satisfied the second movement threshold, the home screen slides from behind the taskbar over the first user interface at a speed faster than the movement speed of the second contact, and as the movement of the second contact continues and satisfies the third movement threshold (e.g., the home screen is fully revealed at this time), the control center slides from the bottom edge of the display over the taskbar and then over a portion of the home screen. In some embodiments, if the second input ends after the home screen is revealed and before the third movement threshold is met, the control center can be introduced from the bottom edge of the display by a third input starting from the bottom or bottom edge of the display rather than from a position above the bottom edge of the display. In some embodiments, a second input with a sustained contact that starts at a predetermined location (e.g., at or below the bottom edge of the display) and moves in a predetermined direction (e.g., upward) can pull up objects in different display layers (e.g., the taskbar, home screen, and control center are all on different display layers (on different z-layers relative to the surface of the display)) during its movement, whereas if independent inputs with independent contacts were to pull up these different objects, the inputs would all have to start from a predetermined location (e.g., at or below the bottom edge of the display). Displaying the control center in response to detecting a multi-stage gesture that satisfies a third movement threshold (where the third movement threshold is greater than a second movement threshold for displaying the home screen, which is greater than the first movement threshold for displaying the taskbar) enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing the number of user inputs required to access the control center, and by helping the user achieve the desired results with the required inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0289] In some embodiments, the user interface object includes (720) a virtual home button, and the user interface object is superimposed on a portion of the first user interface (e.g., Figure 5C7), wherein the virtual home button, when selected, causes the device to stop displaying the first user interface and display the device's home screen; and when the user interface object is superimposed on a portion of the home screen (e.g., as Figure 5C22-Figure 5C23 In some embodiments, if the second input only meets the taskbar display criteria and does not meet the home display criteria (e.g., Figure 5C27-Figure 5C32 ), the tap input on the virtual home button also causes the first user interface to be replaced with display of the home screen. The home button is displayed on the taskbar if the taskbar is accessed in an application (e.g., a first application with a first user interface), and the home button is not displayed on the taskbar if the taskbar is accessed in the home screen, providing additional control options for the home button when needed (e.g., in an application), and not cluttering the taskbar with additional control options for the home button when not needed (e.g., when already on the home screen). Providing control options only when needed reduces clutter on the taskbar, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0290] In some embodiments, the user interface object includes (722) application launch icons corresponding to one or more recently used applications on the device (e.g., Figure 5B7-Figure 5B9 As shown, Figure 5B9 The taskbar 540 in is updated to include a recently used instant messaging application (e.g., the taskbar includes the N most recent applications used on the device, the taskbar includes N favorite applications specified by the user, or the taskbar includes a combination of favorite applications and recent applications and / or suggested applications). Including one or more recently used applications on the taskbar provides improved accessibility to applications, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0291] In some embodiments, the user interface object may be configured (724) by the user to include one or more of the following: a virtual home button, one or more control affordances for controlling corresponding system or device settings, and / or one or more application launch icons. In some embodiments, in response to detecting a touch and hold input on a particular item in the user interface object and a drag input corresponding to the movement of the item away from the user interface object and then lifting the contact from the touch-sensitive surface, the device removes one or more of the above from the user interface object. Allowing the user to configure the taskbar provides improved accessibility to control affordances and / or applications selected by the user, and provides an efficient way for the user to access commonly used functions. Providing improved accessibility enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0292] In some embodiments, while displaying the user interface object, the device detects (726) a third input by a third contact that satisfies the user interface switching criteria (e.g., a swipe gesture by contact 548, Fig.5B14 ), wherein the user interface switching criteria require that the third input includes movement on the display of a movement parameter (e.g., distance and / or speed) of the third contact having a magnitude greater than a third movement threshold (e.g., exceeding 1 / 3 of the screen height, or a speed greater than 500 pixels per second) in order to satisfy the user interface switching criteria (in some embodiments, the user interface switching criteria also require that the movement be in a first direction (e.g., upward) and / or that the movement start from a predetermined position (e.g., at or below the bottom edge of the display)); and in response to detecting the third input: based on determining that the corresponding application user interface (e.g., not the home screen) is displayed when the third contact is detected, the device replaces the display of the corresponding application user interface with the display of the home screen (e.g., as Figure 5B14-Figure 5B15 In some embodiments, the swipe gesture may be used to swipe the user interface of the application to a desired location (e.g., as the swipe progresses, the size of the corresponding application user interface decreases, first to make room for the taskbar and then to make room for the home screen). In response to detecting another swipe while the taskbar is displayed, replacing the display of the application with the display of the home screen provides an efficient way to access the home screen, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results with required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0293] In some embodiments, in response to detecting a third input (728): based on determining that upon detecting a third contact (e.g., a swipe gesture made by contact 552, Fig.5B19 ), the device replaces display of the home screen with display of the user interface of the last active application on the device (e.g., the previous application that was active just before the home screen was displayed) (e.g., Figure 5B19-Figure 5B20 In some embodiments, in response to the first upward swipe gesture, the home screen slides downward and the UI for the most recently used application is presented to the user from the bottom edge of the display to occupy the entire screen (e.g., as shown in FIG. 1 ). Figure 5B19-Figure 5B20 ), and in response to the next upward swipe gesture, the home screen slides back up and the application UI retreats from the screen and toward the bottom of the screen (e.g., as shown in FIG. Figure 5B14-Figure 5B15 In response to detecting another swipe while the taskbar is displayed, replacing the display of the home screen with the display of the last active application provides an efficient way to access recently used applications, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0294] In some embodiments, while displaying the user interface object, the device detects (730) a fourth input by a fourth contact that satisfies the user interface dismissal criteria (e.g., a swipe gesture by contact 554, Figure 5B21 ), wherein the user interface dismissal criteria require that the fourth input includes movement of the fourth contact on the display in a second direction (downward) that is different from the first direction; and in response to detecting the fourth input: based on determining that the corresponding application user interface is displayed when the fourth contact is detected (for example, not the home screen), the device stops displaying the user interface object (for example, swiping down to hide the taskbar when the taskbar is displayed), while maintaining display of the corresponding application user interface (for example, as Figure 5B21-Figure 5B22 In response to detecting an input in a second direction (e.g., swiping down) when the taskbar is displayed, the taskbar is stopped from being displayed, providing an effective way to dismiss the taskbar, enhancing the operability of the device, and making the user-device interface more efficient (e.g., by reducing the number of inputs required to perform an operation, and by helping the user achieve the expected result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0295] In some embodiments, in response to detecting a fourth input (732): based on determining that upon detecting a fourth contact (e.g., a swipe gesture made by contact 550, Figure 5B16 ), the device replaces display of the home screen with display of the user interface of the last active application on the device (e.g., the previous application that was active just before the home screen was displayed) (e.g., Figure 5B16-Figure 5B17 In response to detecting an input in a second direction (e.g., swiping down) when the taskbar is displayed, the display of the home screen is replaced with the display of the last active application, providing an efficient way to access recently used applications, enhancing the operability of the device, and making the user-device interface more efficient (e.g., by reducing the number of inputs required to perform operations, and by helping users achieve expected results with required inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0296] In some embodiments, in response to detecting the fourth input, when the display of the user interface of the last active application has replaced the display of the home screen (e.g., Figure 5B17 ), the device stops (734) displaying the user interface object. Stopping display of the taskbar when display of the last active application replaces display of the home screen can provide immediate access to the full user interface of the application without requiring additional user input to dismiss the taskbar. Performing operations when a set of conditions have been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0297] In some embodiments, displaying a user interface object (e.g., a taskbar) includes (736): based on determining that the user interface object is superimposed on a portion of the home screen, displaying the user interface object having a first appearance (e.g., the first appearance is opaque and obscures a portion of the home screen or forms a portion of the home screen, such as Figure 5B15 and based on determining that the user interface object is superimposed on a portion of the first user interface (e.g., not the home screen), displaying the user interface object with a second appearance (where the second appearance allows the portion of the first user interface to be partially visible from behind the user interface object (e.g., the taskbar is semi-transparent, such as Fig.5B14Displaying a taskbar having a first appearance (e.g., opaque) above the home screen and displaying a taskbar having a second appearance (e.g., translucent) above the application user interface provides improved visual feedback to the user and allows the user to see the complete user interface of the application. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0298] It should be understood that Figure 7A-7C The specific order in which the operations in the description are described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., method 600 and method 800) are also applicable in a similar manner to the details of the processes described above in conjunction with Figure 7A-7C Method 700 is described. For example, the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described above with reference to method 700 optionally have one or more of the characteristics of the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described herein with reference to other methods described herein (e.g., methods 600 and 800). For the sake of brevity, these details are not repeated here.

[0299] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to Figure 1A and Figure 3 described) or application-specific chips.

[0300] References Figure 7A-7C The operation described may be optionally performed by Figure 1A-1B. For example, display operation 702, detection operation 704, replacement operation 706, detection operation 708, and display operation 710 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface (or the rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another orientation. When a corresponding predefined event or sub-event is detected, event identifier 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand that based on Figure 1A to Figure 1B How the components depicted in the figure can implement other processes.

[0301] Figure 8A-8D 800 is a flowchart illustrating a method 800 for displaying an on-demand virtual home button and activating the virtual home button to display a home screen in response to a continuous gesture, according to some embodiments. The method 800 is performed on an electronic device (e.g., device 300, Figure 3 ; or a portable multifunction device 100, Figure 1A ) is performed on a touch-sensitive surface. In some embodiments, the electronic device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the touch-sensitive surface and the display are integrated into a touch-sensitive display. In some embodiments, the display is a touch screen display, and the touch-sensitive surface is on the display or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method 800 are optionally combined, and / or the order of some operations is optionally changed.

[0302] The method involves displaying an on-demand virtual home button in response to detecting an initial movement of an input (e.g., an upward swipe), and activating the virtual home button to display a home screen (e.g., without requiring an input on the virtual home button) in response to detecting an increase in a characteristic intensity of the input above an intensity threshold. Displaying the on-demand virtual home button and activating the virtual home button to display the home screen in response to a continuous gesture provides an efficient way to access the home screen. Reducing the number of inputs required to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0303] Device (e.g., device 100, Fig.5C1 ) on a display (e.g., touch screen 112, Fig.5C1 ) displays (802) a home screen (eg, user interface 504, Fig.5C1 ), wherein the home screen includes a plurality of application launch icons (e.g., application launch icons 524-538) corresponding to a plurality of applications installed on the device (e.g., the plurality of application launch icons are arranged in a grid on the home screen, and optionally, the home screen also includes one or more desktop applets). When the home screen is displayed, the device selects the first application launch icon (e.g., instant messaging application launch icon 524, Fig.5C2 ) detects (804) a first input by a first contact that satisfies the application launch criteria (e.g., a tap gesture by contact 555, Fig.5C2 )(For example, the first input is a tap on the first application launch icon, such as Fig.5C2 In response to detecting a first input (e.g., an input such as a tap input) that satisfies the application launch criteria on the first application launch icon, the device displays the home screen (e.g., user interface 504, Fig.5C2 ) is replaced (806) with a first user interface of the first application corresponding to the first application launch icon (eg, user interface 520, Fig.5C3 ). When displaying the first user interface (eg, user interface 520, Fig.5C4 ), the device detects (808) a second contact (e.g., a contact that is continuously detected on the touch-sensitive surface during the sequence of one or more inputs and is different from the first contact) (e.g., contact 556, Figure 5C4-Figure 5C8In response to detecting the sequence of one or more inputs performed by the second contact (810): based on determining that the sequence of one or more inputs includes a second input by the second contact that satisfies a home button display criterion, wherein the home button display criterion requires that the second input includes an initial movement of the second contact on the touch-sensitive surface in a first direction (e.g., upward) in order to satisfy the home button display criterion, the device displays an overlay on the first user interface (e.g., Figure 5C5-Figure 5C7 54 , 550 , 551 , 552 , 553 , 554 , 555 , 556 , 557 , 558 , 559 ... Figure 5C6-Figure 5C7 ) (e.g., the home button dismisses the currently displayed user interface regardless of what the currently displayed user interface is, and displays the home screen); and based on determining that the sequence of one or more inputs includes a third input by a second contact that satisfies a display home criterion, wherein the display home criterion requires that a characteristic intensity of the second contact increase above a first intensity threshold in order to satisfy the display home criterion (e.g., above an IT L ,like Figure 5C8 ), the device replaces the display of the first user interface with the display of the home screen (for example, as shown Figure 5C8-Figure 5C9As shown). In some embodiments, the home button display standard requires that the second input includes an initial movement of a movement parameter (e.g., distance and / or speed) of the second contact with a magnitude greater than the first movement threshold in order to meet the home button display standard. For example, in some embodiments, a swipe input starting from the bottom or bottom edge of the touch-sensitive display or some other predefined position and moving in a predefined direction (e.g., upward) exceeding a first threshold distance (e.g., 1 / 10 of the display height) meets the home button display standard. In some embodiments, when the second input meets the threshold speed requirement (e.g., greater than 200 pixels per second), the movement requirement can be lowered (e.g., to 1 / 15 of the display height). For example, in some embodiments, a swipe input starting from the bottom or bottom edge of the touch-sensitive display or some other predefined position and moving in a predefined direction (e.g., upward) exceeding a second threshold distance (e.g., 1 / 15 of the display height) less than the first threshold distance at a speed exceeding the first threshold (e.g., exceeding 200 pixels per second) also meets the home button display standard. In some embodiments, both a long upward swipe and a short quick flick meet the home button display standard. In some embodiments, when the second input does not meet the home button display criteria or the show home criteria, a portion of the user interface object with the home button may be displayed according to the movement of the second contact, but when the termination of the second input (e.g., the lift-off of the second contact) is detected without meeting the home button display criteria or the show home criteria, the portion of the user interface object with the home button will stop being displayed (e.g., retracted). In some embodiments, if the home button display criteria are met and the show home criteria are not met, the user interface object with the home button remains displayed, and the transition to the home screen is not displayed after the lift-off of the second contact is detected. In this case, when the user interface object with the home button is displayed, another input made by an independent contact to activate the home button may also bring out the home screen (e.g., from behind the user interface object and above the first user interface).

[0304] In some embodiments, the display home criteria further requires (812) that the third input includes initial movement of the second contact on the touch-sensitive surface in the first direction before the characteristic intensity of the second contact increases above the first intensity threshold in order to satisfy the display home criteria (e.g., Figure 5C4-Figure 5C8 For example, the user swipes upward from a predetermined location (e.g., at or below the bottom edge of the display) to bring up at least a portion of a user interface object including a virtual home button (e.g., task bar 558 with home button 559, Figure 5C6-Figure 5C7), and then press on the touch-sensitive display to activate the virtual home button without lifting your finger from the touch-sensitive display (e.g., Figure 5C8 ). In response to the swipe-press gesture, the home screen replaces the first user interface before the lift-off of the second contact is detected. In some embodiments, after the lift-off of the second contact is detected, the device replaces the first user interface with the home screen. Displaying the home screen in response to the swipe-press gesture provides an efficient way to access the home screen, enhances the operability of the device, and makes the user-device interface more efficient (for example, by reducing the number of inputs required to perform an operation, and by helping the user achieve the expected results with the required inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0305] In some embodiments, replacing display of the first user interface with display of the home screen includes (814) initiating a transition from the first user interface to the home screen before a user interface object including the home button is fully revealed on the display (e.g., as shown in FIG. 8 ). Figure 5C21-Figure 5C22 For example, when a user swipes upward from the bottom of a touch-sensitive display, and after at least a threshold portion of a user interface object including a virtual home button is revealed in accordance with upward movement of a second contact (or after at least the second contact reaches a predefined threshold position on the display), when the user's input satisfies the first intensity threshold, the transition to displaying the home screen can begin at any time, regardless of whether the user interface object or home button is fully revealed (e.g., as shown in the example of FIG. 1 ). Fig.5C21 In some embodiments, after the transition to the home screen has begun, the user interface object including the home button is fully revealed (e.g., as shown in FIG. Fig.5C23 Initiating the transition from the first user interface to the home screen before the user interface object including the home button is fully revealed on the display improves visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results with required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0306] In some embodiments, when the second input satisfies the display home criterion (optionally, before the first position is occupied by a home button or a user interface object having a home button), a user interface corresponding to the first user interface (e.g., user interface 520, Fig.5C38 ) in a first user interface object (e.g., photo thumbnail 579, Fig.5C38 In some embodiments, while the first user interface is displayed and before detecting a sequence of one or more inputs performed by the second contact: the device detects an input satisfying the press object activation criteria by the third contact when detecting the third contact at the first position on the display (e.g., a press input by contact 578, Fig.5C38 ), where the press object activation criteria require that the input by the third contact does not include the third contact satisfying the home button display criteria and the characteristic intensity of the third contact exceeds a first intensity threshold (e.g., a light press intensity threshold IT L ) so as to satisfy the pressed object activation criteria; and in response to detecting input by a third contact that satisfies the pressed object activation criteria, the device performs an operation corresponding to the first user interface object (e.g., displaying a preview of the object, such as Fig.5C39 ) (not showing the home button or home screen). In other words, if the user input is a press input without an initial swipe (e.g., Figure 5C38-Figure 5C39 ), a press input detected at a first location corresponding to a first user interface object triggers performance of an operation corresponding to the first user interface object (e.g., displaying a preview of an object, such as a portion of an email corresponding to the user interface object, or a menu corresponding to the first user interface object, such as a quick action menu with multiple selectable options associated with the first user interface object), or, if the user input is a press input preceded by an initial swipe to bring up a taskbar (e.g., as shown in Figure 5C15-Figure 5C16 ), then the home screen is displayed (even if the taskbar is not fully revealed to cover the first position when the press input is detected, such as Fig.5C21 Performing actions in response to a press input (and displaying the home screen in response to a swipe-press input) provides additional control options without cluttering the user interface with additional displayed controls, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0307] In some embodiments, the display home standard requirement (818) is displayed when the characteristic intensity of the second contact increases to above the first intensity threshold (e.g., the light press intensity threshold IT L), the second contact satisfies the home button display criteria before the second contact satisfies the display home criteria (e.g., Figure 5C4-Figure 5C8 As shown). For example, if the home button display criteria require that the initial movement of the second contact exceeds a predetermined threshold distance and / or a threshold position on the display and / or a threshold speed, and / or starts from a predetermined position (e.g., below the bottom edge of the display) in order to meet the home button display criteria, the show home criteria include these requirements and an additional requirement, namely that after the home button display criteria are met, the characteristic intensity of the second contact exceeds a predetermined intensity threshold. Requiring that the home button display criteria be met before the characteristic intensity of the second contact increases in order to meet the show home criteria provides improved visual feedback to the user (e.g., by displaying a home button and indicating that a heavier press will cause the device to go to the home screen), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0308] In some embodiments, the display home criterion does not require (820) that the characteristic intensity of the second contact increases above the first intensity threshold (e.g., the light press intensity threshold IT L ), the second contact satisfies the home button display criteria before the second contact satisfies the display home criteria (e.g., Figure 5C19-Figure 5C21 For example, if the home button display criteria require that the initial movement of the second contact exceeds a predetermined threshold distance (e.g., 1 / 10 of the display height) and / or a threshold position on the display (e.g., 1 / 10 of the display height from the bottom edge of the display) and / or a threshold speed (e.g., 200 pixels per second), and / or starts from a predetermined position (e.g., below the bottom edge of the display) in order to satisfy the home button display criteria, the display home criteria may be satisfied by a second contact that satisfies these requirements as well as an additional requirement, namely that, after the home button display criteria is satisfied, the characteristic intensity of the second contact exceeds a predetermined intensity threshold (e.g., a light press intensity threshold IT L However, when the second contact does not meet all requirements of the home button display standard, but meets some requirements of the home button display standard or meets a relaxed version of some requirements, the display home standard may also be met as long as the characteristic strength of the second contact exceeds a predetermined strength threshold (for example, Fig.5C21). In some embodiments, if the user's input does not end in a press input that triggers display of the home screen (e.g., the user's input does not end with an increase in intensity above the required threshold intensity), the user will need to swipe a little more (e.g., 1 / 15 of the screen height) or a little faster (e.g., 300 pixels per second) to bring out the user interface object including the home button after the second contact is lifted and keep the user interface object and the home button displayed on the screen. Not requiring the home button display standard to be met before the characteristic intensity of the second contact increases, but allowing some flexibility to meet the display home standard, provides improved feedback and reduces the number of inputs required to perform operations (e.g., by displaying the home screen when the input is close enough to a swipe-press gesture), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0309] In some embodiments, in response to detecting a sequence of one or more inputs performed by a second contact (822): based on determining that the sequence of one or more inputs includes a second input performed by the second contact that satisfies the home button display criteria and does not include a third input performed by the second contact that satisfies the display home criteria, the device maintains display of a user interface object including a home button superimposed on the first user interface (without replacing the display of the first user interface with the display of the home screen) (for example, as Figure 5C27-Figure 5C30 For example, when a user swipes up from the bottom edge of the screen to bring up a user interface object including a home button, if the user does not provide a press input that meets the intensity requirement of the home display standard, the user interface object including the home button remains displayed after the second contact is lifted off (e.g., as shown in FIG. 1 ). Fig.5C30). In some embodiments, the lift-off of the second contact is detected before the user interface object is fully revealed, and the user interface object with the home button continues to slide onto the display after the lift-off of the second contact with movement due to simulated inertia, and remains displayed after it is fully revealed on the display. Maintaining the display of the user interface object including the home button when the second contact does not meet the display home criteria improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the expected results with the required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0310] In some embodiments, while the user interface object including the home button remains displayed, the device detects (824) a fourth input by a fourth contact on the home button (e.g., the fourth input is a tap on the home button by the third contact after lifting off from the second contact, such as Fig.5C31 and in response to detecting a fourth input: the device replaces the display of the first user interface with the display of the home screen (for example, as Figure 5C31-Figure 5C32 In some embodiments, when the home screen is displayed, the device stops displaying the home button in the user interface object (e.g., as shown in the figure below). Figure 5C32 Displaying the home screen in response to activating the virtual home button improves visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve desired results with required inputs and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0311] In some embodiments, in response to detecting a sequence of one or more inputs performed by a second contact (826): based on determining that the sequence of one or more inputs includes a fifth input performed by a second contact that satisfies the swipe control center display criteria, wherein the swipe control center display criteria require that the fifth input includes continued movement of a movement parameter (e.g., distance and / or speed) of the second contact with a magnitude greater than a first movement threshold (e.g., 1 / 7 of the display height) after the home button display criteria are satisfied so that the swipe control center display criteria are satisfied, the device displays a control center user interface object (e.g., control center 584, Figure 5C45 )(For example, Figure 5C45-Figure 5C47 ). In some embodiments, the control center user interface object includes one or more affordances for controlling one or more applications and / or settings on the device. For example, in some embodiments, affordances in the control center user interface object include brightness controls, orientation controls, volume controls, do not disturb settings, Bluetooth settings, Wi-Fi settings, and / or airplane mode controls, as well as other controls that can also be accessed through the device settings user interface or application. In some embodiments, the control user interface also includes one or more quick launch icons for launching one or more applications without going to the home screen. In some embodiments, the control center user interface object is displayed as an extension of a user interface object with a home button. In some embodiments, the control center user interface slides in over the user interface object with the home button and blurs at least a portion of the user interface object with the home button. In some embodiments, the control center user interface slides in at a rate based on the movement of the second contact and is directly manipulated by the second contact (e.g., as Figure 5C45-Figure 5C46 ). In some embodiments, once the second contact has satisfied the swipe control center display criteria, the control center user interface exceeds the movement of the second contact when it reaches its final position. Displaying the control center in response to detecting a gesture after displaying a user interface object with a home button enhances the operability of the device and makes the user-device interface more efficient (for example, by reducing the amount of user input required to access the control center, and by helping the user achieve the desired results with the required input and reducing user errors when operating the device / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0312] In some embodiments, the display home standard requires (828) that the characteristic intensity of the second contact increases to above the first intensity threshold (e.g., the light press intensity threshold IT L), the swipe control center display criteria are not met before the swipe control center display criteria are met so as to meet the display home criteria. For example, in response to detecting that the characteristic intensity of the second contact has increased to above the first intensity threshold, the device begins a transition from the first user interface to the home screen based on determining that the home button display criteria have been met and the swipe control center display criteria have not been met. Based on determining that both the home button display criteria and the swipe control center display criteria have been met, the device does not begin a transition from the first user interface to the home screen, and optionally, in response to the press input, performs a function associated with the control center user interface (e.g., activates a control in the control center user interface). Displaying the home screen in response to the characteristic intensity of the second contact increasing to above the first intensity threshold only when the swipe control center display criteria are not met improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0313] In some embodiments, in response to detecting a sequence of one or more inputs performed by a second contact (830): based on determining that the sequence of one or more inputs includes a sixth input performed by the second contact, wherein the sixth input includes movement in a first direction after the home button display criteria have been met and includes lifting of the second contact: the device displays the beginning of an animated transition to display a control center user interface object; and based on determining that the sixth input performed by the second contact does not meet the swipe control center display criteria (for example, the sixth input includes movement beyond the initial movement of the second contact to display the taskbar, but not sufficient distance and / or speed to meet the swipe control center display criteria to fully reveal the control center user interface): the device displays a reverse animation of the animated transition to display the control center user interface object (for example, the control center user interface object slides back out of the display); and the device continues to display the user interface object including the home button. Displaying an animated transition to display a control center user interface object and then reversing the animated transition when a second touch does not meet the swipe control center display criteria improves the visual feedback provided to the user (e.g., by making the device appear more responsive to user input), enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user achieve intended results with required input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0314] In some embodiments, the device displays (832) a status bar on the display (e.g., along the bottom edge of the display or next to the upper left or right corner of the display) (e.g., the status bar includes status information such as the current time, WiFi and cellular signal strengths, and battery level); while the status bar is displayed on the display, the device detects a seventh input by a fifth contact on the status bar; and in response to detecting the seventh input by the fifth contact on the status bar: based on determining that the seventh input by the fifth contact satisfies the press control center display criteria, wherein the press control center display criteria requires that the characteristic intensity of the fifth contact increase to above a first intensity threshold in order to satisfy the press control center display criteria, the device displays a control center user interface object (e.g., control center 584, Figure 5C47 ). In some embodiments, based on determining that the seventh input made by the fifth contact does not meet the press control center display standard (for example, the characteristic intensity of the fifth contact does not increase to above the first intensity threshold), the control center user interface object is not displayed. In some embodiments, the control center user interface object includes a home button associated with the home screen of the display device. In some embodiments, the home button is separate from the control center user interface object and is brought out by swiping up from the bottom edge of the display (for example, as described above in 810). In some embodiments, the control center user interface object is superimposed on a portion of the application user interface (for example, when the application user interface is displayed when the seventh input made by the fifth contact is detected on the status bar). In some embodiments, the control center user interface object is superimposed on a portion of the home screen (for example, when the home screen is displayed when the seventh input made by the fifth contact is detected on the status bar). Displaying the control center in response to a force press input on the status bar enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing the amount of user input required to access the control center, and by helping users achieve intended results with required inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0315] In some embodiments, while the home button is displayed (e.g., in a user interface object or independently of a user interface object), the device detects (834) an eighth input by a sixth contact on the home button; and in response to detecting the eighth input by the sixth contact: based on determining that the eighth input by the sixth contact meets the home button activation criteria (e.g., detecting lift-off of the sixth contact, with movement to the left or right less than a threshold amount, or before being maintained for more than a threshold amount of time, or before a second strength threshold is met, etc.), the device dismisses the currently displayed user interface and displays the home screen; and based on determining that the eighth input by the sixth contact does not meet the home button activation criteria, the device In some embodiments, when the eighth input satisfies the home button option criteria, the device simultaneously displays the first enable representation (e.g., on the left side of the home button) and the second enable representation (e.g., on the right side of the home button), which, when activated, displays another user interface other than the home screen (e.g., the first enable representation is used to display a multitasking UI, a desktop widget screen, a voice-activated digital assistant screen, or a lock screen). In some embodiments, while displaying the home button, the first enable representation, and the second enable representation, the device detects a ninth input, the ninth input comprising movement of the sixth contact and lift-off of the sixth contact. In response to detecting the ninth input by the sixth contact, based on determining that the ninth input comprises movement of the sixth contact toward the first enable representation, the device transitions to a second user interface (e.g., a digital assistant user interface), and based on determining that the ninth input comprises movement of the sixth contact toward the second enable representation, the device displays a third user interface (e.g., a multitasking user interface). Displaying an enable representation for accessing a user interface other than the home screen (e.g., a multitasking user interface, a desktop widget screen, a voice-activated digital assistant screen, or a lock screen) in response to a contact that meets the home button option criteria enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing the number of user inputs required to access alternative user interfaces, and by helping users achieve desired results with required inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling users to use the device more quickly and efficiently.

[0316] In some embodiments, when displaying a home button superimposed on the corresponding user interface of a current application (e.g., as part of a taskbar or independent of a taskbar) (836) (e.g., at a later time after a user interacts with the device to display a user interface for another application): based on determining that the current application is an application of a first type (e.g., a map application) (e.g., an application whose user interface includes interactive elements or variable content at the location occupied by the home button when the taskbar or home button is not displayed), the device displays the home button with a first transparency (e.g., the home button is substantially transparent over the map application UI to reveal content in a portion of the map application UI below the home button); and based on determining that the current application is an application of a second type (e.g., a voice-based digital assistant) (e.g., an application whose user interface does not include interactive elements or variable content at the location occupied by the home button when the taskbar or home button is not displayed), the device displays the home button with a second transparency different from the first transparency (e.g., the home button is substantially solid over the digital assistant's user interface). Displaying a home button with a first transparency (e.g., transparent) over a first type of application (e.g., an application with interactive elements, such as a map application) and displaying the home button with a second transparency (e.g., substantially solid) over a second type of application (e.g., an application without interactive elements, such as a voice-based digital assistant) can provide improved visual feedback to the user and allow the user to see the complete user interface of the interactive application. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user achieve the desired result with the required input and reducing user errors in operating / interacting with the device), which in turn reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0317] It should be understood that Figure 8A-8D The specific order in which the operations in the description are described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 600 and 700) are also applicable in a similar manner to the details of the processes described above in conjunction with Figure 8A-8DMethod 800 is described. For example, the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described above with reference to method 800 optionally have one or more of the characteristics of the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and / or animations described herein with reference to other methods described herein (e.g., methods 600 and 700). For the sake of brevity, these details are not repeated here.

[0318] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to Figure 1A and Figure 3 described) or application-specific chips.

[0319] Reference above FIG. 8A to FIG. 8D The described operations are optionally performed by Figure 1A to Figure 1B . For example, display operation 802, detection operation 804, replacement operation 806, detection operation 808, and display operation 810 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch-sensitive surface (or the rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another orientation. When a corresponding predefined event or sub-event is detected, event identifier 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand that based on Figure 1A to Figure 1B How the components depicted in the figure can implement other processes.

[0320] For the purpose of explanation, the foregoing description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. The embodiments are selected and described in order to best illustrate the principles of the present invention and its practical application, so that other technical personnel in the field can best use the present invention and the various described embodiments with various modifications suitable for the specific purpose contemplated.

Claims

1. A method comprising: At an electronic device including a display generating component and one or more input devices: While displaying the first user interface, detecting a first user input comprising a first movement; In response to detecting the first user input comprising the first movement followed by termination of the first user input: displaying a first plurality of selectable objects after said termination of said first user input based on determining that said first movement satisfies a first input threshold, wherein said first plurality of selectable objects includes at least a first control corresponding to a first device function of a computer system; as well as Based on determining that the first movement satisfies a second input threshold greater than the first input threshold, a second plurality of optional objects are displayed after the termination of the first user input, wherein the second plurality of optional objects includes at least the first control corresponding to the first device function and a second control corresponding to the second device function, and wherein the second control is not included in the first plurality of optional objects. The method of claim 1 , wherein the first movement is in a first direction and starts from a first edge of the device. 3 . The method of claim 1 , wherein the first movement satisfies the first input threshold when the first movement satisfies a first threshold speed, and wherein the first movement satisfies the second input threshold when the first movement satisfies a second threshold speed greater than the first threshold speed.

4. The method of claim 1 , wherein the first movement satisfies the first input threshold when the first movement satisfies a first threshold distance, and wherein the first movement satisfies the second input threshold when the first movement satisfies a second threshold distance greater than the first threshold distance.

5. The method of claim 1 , wherein the first plurality of selectable objects are displayed based on the determination that the first movement satisfies the first input threshold, and the method comprises: detecting a second user input comprising a second movement while displaying the first plurality of selectable objects after the termination of the first user input; as well as In response to detecting the second user input including the second movement, the second plurality of selectable objects are displayed.

6. The method of claim 1, wherein the second plurality of selectable objects includes the first plurality of selectable objects and one or more additional controls not included in the first plurality of selectable objects. The method of claim 1 , wherein the first user interface is an application user interface.

8. The method according to claim 1, comprising: In response to detecting the first user input: Based on determining that the first movement satisfies a third threshold different from the first input threshold and the second input threshold, a third plurality of selectable objects different from the first plurality of selectable objects and the second plurality of selectable objects are displayed.

9. The method according to claim 1, comprising: While displaying the first plurality of selectable objects, detecting a third user input directed to the first control; as well as In response to detecting the third user input directed to the first control, the first device function corresponding to the first control is performed.

10. The method of claim 1, wherein the first plurality of selectable objects are configurable to include one or more controls for controlling corresponding system or device settings and / or one or more application launch icons.

11. The method according to claim 1, comprising: while displaying the second plurality of selectable objects, detecting a fourth user input directed to the second control; as well as In response to detecting the fourth user input directed to the second control, a third plurality of selectable objects corresponding to the second device function are displayed.

12. The method according to claim 1, comprising: In response to detecting the first user input comprising the first movement: The first plurality of selectable objects are displayed during a first portion of the first movement before detecting the termination of the first user input, and a second plurality of selectable user interface objects are displayed during a second portion of the first movement after the first portion of the first movement.

13. An electronic device comprising: Display generated components; one or more input devices; one or more processors; A memory comprising instructions, wherein the instructions, when executed by the one or more processors, cause the electronic device to perform the method according to any one of claims 1 to 12.

14. A computer-readable medium comprising one or more programs, wherein the one or more programs comprise instructions which, when executed by an electronic device having a display generating component and one or more input devices, cause the electronic device to perform a method according to any one of claims 1 to 12.

15. A method comprising: On devices with touch-sensitive surfaces and displays: detecting, while the device is in an unlocked state, a sequence of one or more activations of a button of the device, the sequence comprising at least a first activation of the button, wherein the first activation of the button is detected while a corresponding application user interface is displayed on the display; and In response to detecting the sequence of one or more activations of the button of the device: in response to determining that the sequence of one or more activations of the button satisfies a first criterion, replacing display of the corresponding application user interface with display of a different user interface while maintaining the device in the unlocked state; as well as Based on determining that the sequence of one or more activations of the button satisfies a second criterion different from the first criterion, the device is switched from the unlocked state in which the corresponding application user interface is displayed to a locked state, wherein the first criterion is distinguished from the second criterion based on the number and / or time of button activations in the sequence of one or more activations of the button. 16 . The method of claim 15 , wherein detecting the first activation of the button comprises detecting a first press input on the button that satisfies a first click criterion. 17 . The method of claim 16 , wherein detecting a second activation of the button comprises detecting a second press input on the button that satisfies a second click criterion.

18. The method of claim 15, wherein switching the device from the unlocked state in which the corresponding application user interface is displayed to the locked state comprises switching from displaying the corresponding application user interface to displaying a lock screen user interface.

19. The method of claim 15, wherein switching the device from the unlocked state in which the corresponding application user interface is displayed to the locked state comprises turning off the display.

20. The method according to claim 15, comprising: In response to detecting the sequence of one or more activations of the button of the device: Based on determining that the sequence of detecting one or more activations of the button satisfies a third criterion different from the first criterion and the second criterion, a process of shutting down the device is initiated.

21. The method according to claim 15, comprising: In response to detecting the sequence of one or more activations of the button of the device: Based on determining that detecting the one or more activations of the button includes detecting a first movement input that meets application switching criteria, replacing the corresponding application user interface with a second user interface corresponding to another application that was active on the device immediately before the application corresponding to the corresponding application user interface.

22. The method according to claim 15, comprising: In response to detecting said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button satisfies a go-to-application criterion, wherein the go-to-application criterion requires that the sequence of one or more activations of the button satisfies a first movement criterion in order to satisfy the go-to-application criterion, displaying a user interface of a last active application on the device.

23. The method according to claim 22, comprising: In response to detecting said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button satisfies preview criteria, wherein the preview criteria requires that an initial portion of the one or more activations of the button satisfy a second movement criterion in order to satisfy the preview criteria, displaying a preview of the user interface of the last active application on the device.

24. The method according to claim 22, comprising: In response to detecting said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button satisfies a preview criterion, wherein the preview criterion requires that an initial portion of the one or more activations of the button satisfies a second movement criterion in order to satisfy the preview criterion, a preview of a lock screen user interface is displayed if the device is locked.

25. The method according to claim 24, comprising: detecting termination of the sequence of one or more activations of the button while displaying the preview; as well as In response to detecting said termination of said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button meets the preview criteria but does not meet the go-to-application criteria, ceasing to display the preview once the sequence of one or more activations of the button terminates.

26. The method according to claim 25, comprising: In response to detecting said termination of said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button meets the preview criteria but does not meet the go-to-application criteria, turning off the display once the sequence of one or more activations of the button terminates.

27. The method of claim 22, comprising: In response to detecting said sequence of one or more activations of said button: Based on determining that the sequence of one or more activations of the button satisfies an application switching criterion, wherein the application switching criterion requires that the sequence of one or more activations of the button include movement input that satisfies the first movement criterion and a first duration criterion in order to satisfy the application switching criterion: An application switching user interface is displayed on the device including representations of a currently active application and one or more suspended applications.

28. An electronic device comprising: Touch-sensitive surfaces; monitor; one or more input devices; one or more processors; Memory; as well as One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 15 to 27.

29. A computer-readable storage medium comprising one or more programs, the one or more programs comprising instructions which, when executed by an electronic device having a touch-sensitive surface and a display, cause the device to perform a method according to any one of claims 15 to 27.

30. A method comprising: At an electronic device having a display and an embedded fingerprint sensor: displaying a lock screen on the display; while displaying the lock screen, detecting a first touch input on the embedded fingerprint sensor; In response to detecting the first touch input on the embedded fingerprint sensor: Based on determining that the first time criterion is met, displaying the content of the plurality of messages; as well as Based on determining that a second time standard different from the first time standard is met, the lock screen is stopped from being displayed and a home screen usage interface of the electronic device having a plurality of application icons is displayed.

31. The method of claim 30, wherein the first movement is in a first direction and begins from a first edge of the device.

32. The method of claim 30, wherein the first movement satisfies the first input threshold when the first movement satisfies a first threshold speed, and wherein the first movement satisfies the second input threshold when the first movement satisfies a second threshold speed greater than the first threshold speed.

33. The method of claim 30, wherein the first movement satisfies the first input threshold when the first movement satisfies a first threshold distance, and wherein the first movement satisfies the second input threshold when the first movement satisfies a second threshold distance greater than the first threshold distance.

34. The method of claim 30, wherein the first plurality of selectable objects are displayed based on determining that the first movement satisfies the first input threshold, and the method comprises: detecting a second user input comprising a second movement while displaying the first plurality of selectable objects after the termination of the first user input; as well as In response to detecting the second user input including the second movement, the second plurality of selectable objects are displayed.

35. The method of claim 30, wherein the second plurality of selectable objects includes the first plurality of selectable objects and one or more additional controls not included in the first plurality of selectable objects.

36. The method of claim 30, wherein the first user interface is an application user interface.

37. The method of claim 30, comprising: In response to detecting the first user input: Based on determining that the first movement satisfies a third threshold different from the first input threshold and the second input threshold, a third plurality of selectable objects different from the first plurality of selectable objects and the second plurality of selectable objects are displayed.

38. The method of claim 30, comprising: While displaying the first plurality of selectable objects, detecting a third user input directed to the first control; as well as In response to detecting the third user input directed to the first control, the first device function corresponding to the first control is performed.

39. The method of claim 30, wherein the first plurality of selectable objects are configurable to include one or more controls for controlling corresponding system or device settings and / or one or more application launch icons.

40. The method of claim 30, comprising: while displaying the second plurality of selectable objects, detecting a fourth user input directed to the second control; as well as In response to detecting the fourth user input directed to the second control, a third plurality of selectable objects corresponding to the second device function are displayed.

41. The method of claim 30, comprising: In response to detecting the first user input comprising the first movement: The first plurality of selectable objects are displayed during a first portion of the first movement before detecting the termination of the first user input, and the second plurality of selectable user interface objects are displayed during a second portion of the first movement after the first portion of the first movement.

42. An electronic device comprising: monitor; Embedded fingerprint sensor; one or more processors; A memory comprising instructions, wherein the instructions, when executed by the one or more processors, cause the electronic device to perform a method according to any one of claims 30 to 41.

43. A computer-readable storage medium comprising one or more programs, wherein the one or more programs include instructions that, when executed by an electronic device having a display and an embedded fingerprint sensor, cause the electronic device to perform a method according to any one of claims 30 to 41.

44. A method comprising: At a computer system having a display and an input mechanism: displaying a first user interface on the display; While displaying the first user interface, detecting a first user input via the input mechanism; In response to the first user input detected via the input mechanism: replacing display of the first user interface with display of a second user interface different from the first user interface based on determining that the first user input includes a first type of interaction with the input mechanism; Based on determining that the first user input includes a second type of interaction with the input mechanism, wherein the second type of interaction is different from the first type of interaction, a process of shutting down the computer system is initiated.

45. The method of claim 44, wherein the button is a power button.

46. ​​The method of claim 44, wherein the first type of interaction with the input mechanism comprises a touch gesture on the input mechanism.

47. The method of claim 44, wherein the first type of interaction with the input mechanism comprises a sliding input on the input mechanism.

48. The method of claim 44, wherein the second type of interaction with the input mechanism comprises a press input on the input mechanism.

49. The method of claim 44, wherein the first user interface is an application user interface.

50. The method of claim 44, wherein the second user interface is an application user interface corresponding to a previously displayed application.

51. The method of claim 44, wherein the first user interface corresponds to a locked state of the computer system.

52. The method of claim 44, wherein replacing display of the first user interface with display of the second user interface comprises switching a device from a locked state to an unlocked state.

53. The method of claim 44, wherein: The first user interface corresponds to a locked state of the computer system; and The second user interface corresponds to an unlocked state of the computer system.

54. The method according to any one of claims 44 and 53, wherein: The first user interface corresponds to a locked state of the computer system; and The second user interface corresponds to a home screen user interface, wherein the home screen user interface includes a plurality of application launch icons.

55. The method according to any one of claims 44 and 53, wherein: The first user interface corresponds to a locked state of the computer system; and The second user interface corresponds to an application user interface.

56. The method of claim 44, wherein: The first type of interaction with the input mechanism comprises a touch gesture on the input mechanism; and The second type of interaction with the input mechanism comprises a press input on the input mechanism.

57. The method of claim 44, wherein: The first user interface is a first application user interface; and The second user interface is a second application user interface corresponding to a previously displayed application, and the second application user interface is different from the first application user interface.

58. An electronic device comprising: monitor; Input institution; one or more processors; A memory comprising instructions, wherein the instructions, when executed by the one or more processors, cause the electronic device to perform a method according to any one of claims 44 to 57.

59. A computer-readable storage medium comprising one or more programs, wherein the one or more programs comprise instructions which, when executed by an electronic device having a display and an input mechanism, cause the electronic device to perform a method according to any one of claims 44 to 57.

Images