Device and method for interacting with an application switching user interface

Abstract

To provide an electronic device and a method for interacting with an application switching user interface.SOLUTION: A method displays an application on a display, detects an input corresponding to a request for displaying an application switching user interface, displays an application switching user interface containing an expression of a plurality of recently used applications, detects a touch gesture caused by a contact on a touch detection surface, closes a displayed application according to various determinations following to the touch gesture, stops display of the application switching user interface, and displays an application starting user interface different from the application switching user interface (for instance, a home screen user interface).SELECTED DRAWING: Figure 6A

Description

[Technical Field]

[0001] This application relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that provide application-switching user interfaces, and more particularly to devices and methods for interacting with application-switching user interfaces. [Background technology]

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touchscreen displays. Such surfaces are widely used for selecting, launching, and managing software applications.

[0003] For portable electronic devices, existing methods for managing multiple recently used applications are cumbersome and inefficient. For example, portable devices with small screens (e.g., smartphones and other pocket-sized devices) typically display a single application at a time. On such devices, it can be difficult for a user to view and manage multiple recently used applications. This situation creates a significant cognitive burden for the user. Furthermore, existing methods for managing recently used applications waste energy by taking longer than necessary. The latter problem is particularly acute in battery-operated devices. Summary of the Invention

[0004] Therefore, there is a need for a computing device with a faster, more efficient method and interface for managing recently used applications. Such a method and interface can complement or replace conventional methods for managing recently used applications. Such a method and interface reduces the cognitive burden on a user and creates a more efficient human-machine interface. For battery-operated computing devices, such a method and interface conserves power and extends the time between battery charges.

[0005] The application switching user interface displays representations of multiple recently used applications, arranged, for example, according to the relative recency of the last use of each of the applications. Existing methods of interacting with application switching user interfaces are very limited, for example, allowing a user to only select an application to display the application, remove an application from the application switching user interface, or close the application switching user interface to return to the last displayed user interface. The above-mentioned disadvantages and other challenges associated with managing recently used applications using conventional application switching user interfaces are reduced or eliminated by the disclosed electronic device.

[0006] In some embodiments, the device comprises a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a handheld device). In some embodiments, the device comprises a personal electronic device (e.g., a wearable electronic device such as a watch). In some embodiments, the device has (and / or is in communication with) a display generating component and one or more input devices. In some embodiments, the device has (and / or is in communication with) a touchpad. In some embodiments, the device has (and / or is in communication with) a touch-sensitive display (also known as a "touchscreen" or "touchscreen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in the memory for performing multiple functions. In some embodiments, a user interacts with the GUI, in part, through contacts and gestures with a stylus and / or fingers on a touch-sensitive surface. In some embodiments, the functionality optionally includes game playing, image editing, drawing, presenting, word processing, spreadsheet creation, telephony, video conferencing, email, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0007] According to some embodiments, a method is performed on an electronic device with a touch-sensitive display. The method includes displaying applications on the display. The method further includes, while displaying the applications on the display, detecting an input corresponding to a request to display an application switching user interface, and, in response to detecting the input corresponding to the request to display the application switching user interface, displaying the application switching user interface including representations of a plurality of recently used applications, including a first application representation corresponding to a first application and a second application representation corresponding to a second application. The method further includes, while displaying the application switching user interface, detecting a touch gesture by contact on the touch-sensitive surface; and, in response to detecting the touch gesture, closing the first application in accordance with a determination that the touch gesture includes movement by contact in a first direction and initiated at a location corresponding to the first application representation; closing the second application in accordance with a determination that the touch gesture includes movement by contact in the first direction and initiated at a location corresponding to the second application representation; and ceasing display of the application switching user interface and displaying an application launching user interface different from the application switching user interface in accordance with a determination that the touch gesture includes movement by contact in the first direction and initiated at a location corresponding to a predefined region within the application switching user interface that is outside the first application representation and the second application representation.

[0008] According to some embodiments, an electronic device includes a display, an optional touch-sensitive surface, one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface, one or more processors, a memory, and one or more programs. 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 include instructions for performing any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium has instructions stored therein that, when executed by an electronic device including a display, an optional touch-sensitive surface, and one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface, cause the device to perform any of the operations of the methods described herein. According to some embodiments, a graphical user interface on an electronic device including a memory and one or more processors executing one or more programs stored in the memory includes one or more of the 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, an optional touch-sensitive surface, one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface, and means for performing the operations of any of the methods described herein. According to some embodiments, an information processing apparatus for use in an electronic device including a display, an optional touch-sensitive surface, and one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface includes means for performing the operations of any of the methods described herein.

[0009] Thus, electronic devices are provided with faster, more efficient methods and interfaces for integrating video with user interface navigation, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for integrating video with user interface navigation. [Brief explanation of the drawings]

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

[0011] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0012] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.

[0013] [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

[0014] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0015] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0016] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0017] [Figure 4C] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4D] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4E] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments.

[0018] [Figure 5A] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5B] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5C] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5D] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5E] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5F] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5G] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5H] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5I] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5J] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5K]1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5L] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5M] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5N] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5O] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5P] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5Q] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5R] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5S] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5T] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5U] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5V]1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5W] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5X] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5Y] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments. [Figure 5Z] 1 illustrates an exemplary user interface for integrating an application switching user interface according to some embodiments.

[0019] [Figure 6A] FIG. 1 is a flow diagram illustrating a method for interacting with an application switching user interface according to some embodiments. [Figure 6B] FIG. 1 is a flow diagram illustrating a method for interacting with an application switching user interface according to some embodiments. [Figure 6C] FIG. 1 is a flow diagram illustrating a method for interacting with an application switching user interface according to some embodiments. [Figure 6D] FIG. 1 is a flow diagram illustrating a method for interacting with an application switching user interface according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0020] The methods, devices, and GUIs described herein improve the interaction and functionality of application switching user interfaces in several ways.

[0021] In some embodiments, a swipe gesture by a contact detected on the touch-sensitive surface of the device while the application switching user interface is displayed causes the device to perform different actions depending on various characteristics of the swipe gesture (e.g., the direction of the swipe gesture, the speed and / or distance of movement of the contact, and / or the starting and / or ending location of the swipe gesture). Specifically, in some embodiments, an upward swipe gesture initiated from a position corresponding to a representation of a respective application in the application switching user interface causes the device to close the respective application, while an upward swipe initiated from a position not occupied by a representation of any application in the application switching user interface causes the device to navigate to an application launch user interface (e.g., a home screen user interface). Furthermore, in some embodiments, a sideways swipe gesture detected on the application switching user interface (e.g., the movement of the contact corresponds to movement across the representation(s) of one or more applications) causes the device to scroll the representations of applications in the application switching user interface. In some embodiments, a downward swipe gesture at a location on the touch-sensitive surface corresponding to the representation of the respective application in the application switching user interface causes the device to display the respective application in a default mode (e.g., full-screen mode) (e.g., if a first criterion is met by the downward swipe gesture) or in an expanded reachable mode (e.g., shifted down on the display) (e.g., if a second criterion is met by the downward swipe gesture).

[0022] Below, Figures 1A, 1B, 2, and 3 provide an example device description. Figures 5A-5Z show example user interfaces for interacting with the application switching user interface. Figures 6A-6D are flow diagrams illustrating a method of the application switching user interface. The user interfaces of Figures 5A-5Z are used to explain the process of Figures 6A-6D. Exemplary Devices

[0023] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0024] In this specification, terms such as "first," "second," etc. are used to describe various elements in some examples, but it will be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first contact can be referred to as a second contact, and similarly, a second contact can be referred to as a first contact, without departing from the scope of the various embodiments being described. Although a first contact and a second contact are both contacts, they are not the same contact unless the context clearly dictates otherwise.

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

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

[0027] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

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

[0029] The device typically supports a variety of applications such as one or more of a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

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

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

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

[0033] Memory 102 optionally includes high-speed random access memory, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and peripherals interface 118, is optionally controlled by memory controller 122.

[0034] A peripheral interface 118 may be used to couple input and output peripherals of the device with the CPU(s) 120 and memory 102. The one or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions and process data for the device 100.

[0035] In some embodiments, peripheral interface 118, CPU(s) 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.

[0036] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. Radio options include Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), and code division multiple access (CDMA).Wireless technologies include, but are not limited to, standard 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, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP)), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and Instant Messaging and Presence Services (IMP). The present invention may use any of a number of communication standards, protocols, and technologies, including, but not limited to, Intermediate Message Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

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

[0039] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives electrical signals from and / or sends electrical signals to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed towards the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, a hyperlink, or other user interface control.

[0040] Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contacts (and any movement or disruption of contact) on touch-sensitive display system 112 and translate the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch-sensitive display system 112. In some embodiments, the point of contact between touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

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

[0042] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on a touchscreen than that of a stylus. In some embodiments, the device translates coarse finger input into precise pointer / cursor positions or commands to perform actions desired by the user.

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

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

[0045] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), light sensor(s) 164 optionally capture still images and / or video. In some embodiments, the light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touchscreen can be used as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device so that an image of the user is captured (e.g., for a selfie, for a video conference while the user is viewing other video conference participants on the touchscreen, etc.).

[0046] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display system 112, which is located on the front of device 100.

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

[0048] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. In some embodiments, tactile output generator(s) 167 include one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear movement, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generate tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

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

[0050] In some embodiments, software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic 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 applications (or instruction sets) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information occupy various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or location information regarding the device's position and / or orientation.

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

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

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

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

[0055] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger-down event and detecting a finger-up event, but is not related to the intensity of the finger contact between detecting the finger-down event and detecting the finger-up event. In some embodiments, a tap gesture is detected according to determining that the length of time between the finger-down event and the finger-up 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 intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light or deep pressure intensity threshold. Thus, a finger tap gesture can satisfy certain input criteria that do not require the characteristic intensity of the contact to meet a given intensity threshold for the particular input criteria to be met. For clarity, finger contacts in a tap gesture generally need to meet a nominal contact-detection intensity threshold below which the contact is not detected in order to detect a finger-down event. A similar analysis applies to detecting a stylus tap gesture or other contact. In cases where the device is capable of detecting contact of 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.

[0056] In a similar manner, the same concepts apply to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts included in the gesture or that do not require the contacts performing the gesture to reach an intensity 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 pinch gesture is detected based on the movement of two or more contacts toward each other, a de-pinch 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 contact on the touch-sensitive surface that is less than a threshold amount of movement. Thus, a statement that a particular gesture recognition criterion does not require the intensity of a contact(s) to meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be met means that the particular gesture recognition criterion can be met when the contact(s) in the gesture do not reach the corresponding intensity threshold, and can also be met in situations where one or more of the contacts in the gesture reach or exceed the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on a determination that a finger-down event and a finger-up event are detected within a predetermined time period, regardless of whether the contacts are above or below the respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on a determination that a movement of the contact is greater than a predetermined magnitude, even if the contacts exceed the respective intensity thresholds at the end of the movement of the contacts. Even in implementations in which gesture detection is affected by the intensity of the contact performing the gesture (e.g., the device detects long presses more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slow to detect tap inputs when the intensity of the contact is higher), detection of those gestures does not require the contact to reach a particular intensity threshold, as long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach the particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies).

[0057] The contact intensity threshold, duration threshold, and movement threshold may, in some circumstances, be combined in various different combinations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require the intensity of the contact(s) to meet a respective intensity threshold for that particular gesture recognition criterion does not preclude simultaneously evaluating other intensity-dependent gesture recognition criteria to identify other gestures with criteria that are met when the gesture includes a contact having an intensity exceeding a respective intensity threshold. For example, in some circumstances, a first gesture recognition criterion for a first gesture that does not require the intensity of the contact(s) to meet a corresponding intensity threshold for the first gesture recognition criterion to be met competes with a second gesture recognition criterion for a second gesture that relies on the contact(s) reaching a corresponding intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the corresponding intensity threshold before moving a predetermined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves a predetermined amount of movement before reaching the corresponding intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the corresponding intensity threshold for the first gesture recognition criteria to be satisfied, because if the contact remained below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase in intensity above the corresponding intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture.In this way, certain gesture recognition criteria that do not require the intensity of the contact(s) to meet a corresponding intensity threshold for the particular gesture recognition criterion to be satisfied are still dependent on the intensity of the contact with respect to an intensity threshold, in the sense that (A) in some circumstances, they ignore the intensity of the contact with respect to the intensity threshold (e.g., for a tap gesture), and / or (B) in some circumstances, the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input (e.g., for a long press gesture that competes with a deep press gesture for recognition).

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

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

[0060] The haptic feedback module 133 includes various software components that generate instructions (e.g., instructions used by the haptic feedback controller 161) that use the tactile output generator(s) 167 to create tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0061] Text input module 134 is optionally a component of graphics module 132 and 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).

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

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

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

[0065] Contacts module 137, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370) for managing an address book or contact list, including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conference 139, email 140, or IM 141, etc.

[0066] In cooperation 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, telephone module 138 includes executable instructions for entering a series of characters corresponding to a telephone number, accessing one or more telephone numbers in address book 137, modifying an entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is completed. As noted above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0067] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 164, light 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 to initiate, conduct, and terminate video conferences between a user and one or more other participants according to the user's commands.

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

[0069] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for entering a series of characters corresponding to an instant message, modifying previously entered characters, sending each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-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, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0070] In cooperation with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the training support module 142 includes executable instructions to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smartwatch), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.

[0071] Camera module 143, along with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, includes executable instructions to capture still images or video (including video streams) and store them in memory 102, change characteristics of the still images or video, and / or delete the still images or video from memory 102.

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

[0073] Browser module 147, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

[0075] Widget modules 149, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are optionally mini-applications downloaded and used by a user (e.g., weather widget 149-1, stock quotes widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by a user (e.g., user-created widget 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include Extensible Markup Language (XML) files and JavaScript files (e.g., Yahoo! Widgets).

[0076] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

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

[0078] In cooperation 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 enable a user to download and play recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play video (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0079] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0080] In conjunction 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 can be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0081] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), and play (e.g., on touchscreen 112 or on an external display connected wirelessly or via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails with links to particular online videos. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0082] Each of the above-identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

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

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

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

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

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

[0088] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user's 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, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

[0089] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

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

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

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

[0093] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. 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 that should process the sub-events. In most situations, the hit view is the lowest-level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). 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 was identified as the hit view.

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

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

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

[0097] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Instead, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

[0098] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

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

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

[0101] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view in which three user interface objects are displayed 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 respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0102] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether a set of sub-events corresponds to the event recognizer's event type.

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

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

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

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

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

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

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

[0110] FIG. 2 illustrates portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A ) according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In these embodiments, as well as embodiments described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

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

[0112] In some embodiments, device 100 includes a touchscreen display, a menu button 204 (sometimes referred to as a home button 204), a push button 206 for powering the device on / off and locking the device, volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In some embodiments, device 100 also accepts verbal input through microphone 113 to activate or deactivate some features. Device 100 also optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on touch-sensitive display system 112 and / or one or more tactile output generators 167 that generate a tactile output for a user of device 100.

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

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

[0115] Attention is now directed to embodiments of a user interface (“UI”) that is optionally implemented on portable multifunction device 100.

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

[0117] 4A are merely examples. For example, other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

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

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

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

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

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

[0123] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the following: a maximum intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% of the maximum intensity of the contact, a value generated by low-pass filtering the intensity of the contact starting over a predefined period or at a predefined time, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity not exceeding the first threshold results in a first action being performed, a contact having a characteristic intensity above the first intensity threshold but not above the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity above the second intensity threshold results in a third action being performed. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform a first operation or a second operation, but rather to determine whether to perform one or more operations (e.g., whether to perform a respective option or refrain from performing a respective operation).

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

[0125] The user interface diagrams described herein optionally include various intensity diagrams showing the current intensity of a contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact-detection intensity threshold ITO, a light pressure intensity threshold ITL, a deep pressure intensity threshold ITD (e.g., at least initially higher than ITL), and / or one or more other intensity thresholds (e.g., an intensity threshold ITH lower than TIL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in interpretation of the diagram. In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity at which the device performs an action different from an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below a light pressure intensity threshold (e.g., above a nominal contact-detection intensity threshold IT0 below which contact is no longer detected), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing any action associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across the various sets of user interface diagrams.

[0126] In some embodiments, the device's response to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact during the input that exceeds a first intensity threshold triggers a first response. In some embodiments, the device's response to an input detected by the device depends on criteria including both the intensity of the contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input that exceeds a second intensity threshold that is greater than the first intensity threshold for a light press triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps avoid accidental recognition of deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the first intensity threshold is met. During the period of decreased sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. For other deep pressure inputs, the response to deep pressure input detection does not depend on a time-based criterion.

[0127] In some embodiments, one or more of the input intensity threshold and / or corresponding output vary based on one or more factors, such as user settings, contact movement, input timing, running application, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), position of focus selector, etc. Exemplary factors are described in U.S. Patent Application Publication Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0128] For example, FIG. 4C illustrates a dynamic intensity threshold 480 that varies 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 predetermined delay time p1 from when touch input 476 is first 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. The second component 478 reduces unintentional triggering of a "deep press" response due to gradual intensity variations of the touch input. In some embodiments, a "deep press" response is triggered when touch input 476 meets dynamic intensity threshold 480 (e.g., at point 481 in FIG. 4C ).

[0129] FIG. 4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold ID). FIG. 4D also illustrates two other intensity thresholds: a first intensity threshold IH and a second intensity threshold IL. In FIG. 4D, a touch input 484 satisfies the first intensity threshold IH and the second intensity threshold IL before time p2, but no response is provided until delay time p2 has elapsed at time 482. Also in FIG. 4D, the dynamic intensity threshold 486 decays over time, beginning at time 488 after a predetermined delay time p1 has elapsed from time 482 (when the response associated with the second intensity threshold IL is triggered). This type of dynamic intensity threshold reduces the accidental triggering of a response associated with the dynamic intensity threshold ID immediately after or simultaneously with triggering a response associated with a lower intensity threshold, such as the first intensity threshold IH or the second intensity threshold IL.

[0130] 4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold ID). In FIG. 4E, a response associated with intensity threshold ID is triggered after a delay time p2 from when touch input 490 is first detected. At the same time, dynamic intensity threshold 492 decays after a predetermined delay time p1 from when touch input 490 is first detected. Thus, a decrease in the intensity of touch input 490 after triggering a response associated with intensity threshold ID, followed by an increase in the intensity of touch input 490 without releasing touch input 490, can trigger a response associated with intensity threshold ID (e.g., at time 494) even when the intensity of touch input 490 falls below another intensity threshold, e.g., intensity threshold ID.

[0131] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold ITL to an intensity between the light pressure intensity threshold ITL and the deep pressure intensity threshold ITD may be referred to as a “light press” input. An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold ITD to an intensity above the deep pressure intensity threshold ITD may be referred to as a “deep press” input. An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold IT0 to an intensity between the contact detection intensity threshold ITL and the light pressure intensity threshold ITL may be referred to as a detection of a contact on the touch surface. 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 may be referred to as a detection of a lift-off of the contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some examples, a shaded circle or ellipse is used to represent the intensity of a contact on the touch-sensitive surface. In some examples, an unshaded circle or ellipse is used to represent each contact on the touch-sensitive surface without specifying the intensity of each contact.

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

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

[0134] For ease of explanation, descriptions of operations performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including a pressure input are, optionally, triggered in response to detecting an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold. As noted above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time elapsed between the first intensity threshold being met and the second intensity threshold being met).

[0135] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.Using tactile output to provide haptic feedback to the user improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0136] In some embodiments, the tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the movement waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0137] When tactile outputs having different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile outputs can cause different tactile sensations when a user holds or touches the device. When a user's sensations are based on the user's perception of the tactile output, most users are able to distinguish changes in waveform, frequency, and amplitude of the tactile output generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions have been performed. Thus, in some situations, tactile output having a tactile output pattern designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behaviors (e.g., vibration, displacement, acceleration, rotation, expansion, etc.), and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment having virtual boundaries and virtual objects, an actual physical environment having physical boundaries and physical objects, and / or any combination of the above) provides useful feedback to a user that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, the tactile output is optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile output provides useful feedback to a user that reduces input errors and increases the efficiency of the user's operation of the device.

[0138] In some embodiments, a tactile output having a suitable tactile output pattern serves as a cue to the occurrence of an event of interest behind the scenes within a user interface or device. Examples of events of interest include activation of an affordance provided on the device or within the user interface (e.g., a real button, a virtual button, or a toggle switch), success or failure of a requested action, reaching or crossing a boundary within the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, a tactile output is provided to serve as a warning or alert of an impending event or outcome that will occur unless a redirection or interrupting input is detected in a timely manner. Tactile output is also used in other contexts to enhance the user experience, improve the accessibility of a device for users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. The tactile output, optionally accompanied by an audio output and / or a change in the visible user interface, further enhances the user's experience when interacting with the user interface and / or device, facilitates better communication of information about the state of the user interface and / or device, reduces input errors, and increases the efficiency of the user's operation of the device. User Interface and Related Processes

[0139] Attention is now directed to embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, that includes a display, a touch-sensitive surface, (optionally) one or more tactile output generators for generating tactile output, and (optionally) one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0140] 5A-5Z show exemplary user interfaces for interacting with an application switching user interface, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the processes in FIGS. 6A-6D . For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the face centroid of each contact or a point associated with each contact), or the face centroid of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and a separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0141] 5A-5D illustrate an upward swipe gesture that causes a device to navigate from an application's user interface to an application launch user interface, according to some embodiments.

[0142] 5A, the device displays a user interface (e.g., user interface 5002) of a map application in a default full-screen mode (e.g., user interface 5002 occupying substantially all of touchscreen 112). The device detects a contact (e.g., contact 5004) in a bottom edge region of touchscreen 112. Before the contact is detected, the device displays an indicator (e.g., home affordance 5006) in the bottom edge region of touchscreen 112 to indicate the location of the bottom edge region of touchscreen 112 for detecting an edge swipe gesture.

[0143] 5A-5B, the device detects an upward movement of contact 5004 from the bottom edge of touchscreen 112, and in accordance with the upward movement of contact 5004, the device reduces the size of user interface 5002 of a map application and transforms user interface 5002 into an application representation of the map application (e.g., card 5010 including a snapshot of user interface 5002). Card 5010 is displayed on a background (e.g., background 5008 (e.g., a blurred image of home screen user interface 5014 (FIG. 5D))) within a navigation user interface having multiple possible destination states (e.g., destination states corresponding to different user interfaces, such as an application switching user interface, an application launch user interface, an application user interface for a previous / next application, or a current application). The device moves card 5010 together with contact 5004 on background 5008 of the navigation user interface. Following a determination that the criteria for navigating to the application switching user interface are met by movement of contact 5004 (e.g., a movement parameter of the movement of contact 5004 exceeds a first threshold (e.g., a first threshold distance in an upward direction, or greater than movement followed by an interruption of contact 5004)), the device displays another card 5012 (e.g., an application representation of the Settings application) next to card 5010 on background 5008 to indicate that the criteria for navigating to the application switching user interface have been met and that if lift-off of contact 5004 is detected at this point, the device will navigate to the application switching user interface. As contact 5004 moves upward on touchscreen 112, cards 5010 and 5012 move upward in unison with contact 5004 and reduce in size according to the card's (or contact's) distance from the bottom edge of the touchscreen. Card 5012 represents the application last opened before the maps application.

[0144] 5B-5C , as contact 5004 continues to move upward, dragging cards 5010 and 5012 across background 5008 within the navigation user interface, the device detects that the criteria for navigating to an application launching user interface (e.g., a home screen user interface) have been met (e.g., a movement parameter of the movement of contact 5004 exceeds a second threshold (e.g., greater than a second threshold distance that is greater than a first threshold distance in the upward direction, or the velocity of movement of contact 5004 exceeds a threshold velocity)). Following a determination that the criteria for navigating to an application launching user interface have been met, the device removes card 5012 from the display, leaving only card 5010, which continues to move with contact 5004 on background 5008. As contact 5004 drags card 5010 across the navigation user interface, card 5010 resizes according to its distance from a bottom edge of the touchscreen (e.g., shrinking as the distance from the edge increases).

[0145] 5C-5D, the device detects lift-off of contact 5004 while card 5010 is still the only card present on the touchscreen (e.g., in the state shown in FIG. 5C ) (e.g., the criteria for navigating to the application launch user interface are still met, and the criteria for navigating to the application switching user interface are no longer met). In response to detecting lift-off of contact 5004 (e.g., in FIG. 5D , the lift-off position of contact 5004 is indicated by a dashed line on home screen user interface 5014), the device stops displaying the navigation user interface (e.g., in the state shown in FIG. 5C ) and displays an application launch user interface (e.g., home screen user interface 5014) (e.g., as shown in FIG. 5D ). The application launch user interface displays a plurality of application icons representing respective applications installed on the device. The plurality of application icons are arranged in a predetermined manner (e.g., listed alphabetically, by category, or according to user configuration) on the application launch user interface, regardless of the relative recency of when the applications corresponding to the application icons (or for at least some of them) were last used (e.g., last displayed or interacted with by a user) on the device. Each application icon, when selected and activated by user input (e.g., a tap input or a double-tap input), causes the device to open (e.g., display) the application corresponding to the application icon.

[0146] Figure 5B, followed by Figure 5E, shows that if lift-off of contact 5004 is detected when the navigation user interface is in the configuration shown in Figure 5B (e.g., the lift-off position of contact 5004 is shown by a dashed line in Figure 5E), the device navigates to an application switching user interface rather than launching a user interface (e.g., home screen user interface 5014).

[0147] As shown in Figure 5E, the application switching user interface includes application representations corresponding to multiple recently used applications (e.g., a stack of open applications or applications in a held state). The application representations (e.g., card 5010 corresponding to a maps application, card 5012 corresponding to a settings application, and card 5016 corresponding to a location sharing application) are arranged in the application switching user interface (e.g., overlaid on background 5008) in an order based on the relative recency of when the applications were last used (e.g., viewed or interacted with by the user). For example, the most recently used applications are arranged at the top of the stack, and the least recently used applications are arranged at the bottom of the stack. As shown in Figure 5E, in the application switching user interface, the application representations (e.g., cards 5010, 5012, and 5016) of the applications are overlapped and displayed in a manner that indicates their relative order within the stack of recently used applications.

[0148] 5E depicts the starting state of multiple scenarios in which a user interacts with the application switching user interface in different ways. Multiple contacts 5018, 5024, and 5026 are shown in FIG. 5E, each of which is detected independently at different times and not simultaneously. Each of contacts 5018, 5024, and 5026 is part of a different gesture that is detected separately in different scenarios.

[0149] 5E-5G illustrate that a swipe gesture with a contact across the application switching user interface (e.g., initiated on an application representation of an application) causes the device to scroll through the application representations within the application switching user interface.

[0150] 5E-5G, the device detects contact 5018 (in FIG. 5E) on card 5012, detects horizontal movement of contact 5018 toward the right edge of the touchscreen (as indicated by the horizontal arrow in FIGS. 5F and 5G), and detects liftoff of contact 5012 from the touchscreen after the movement (e.g., the liftoff position of contact 5018 is indicated by the dashed line in FIG. 5G). In response to the horizontal swipe by contact 5018, the device moves cards 5010, 5012, and 5016 rightward to reveal card 5020 (e.g., an application representation for a weather application) beneath card 5016, as shown in FIGS. 5F and 5G.

[0151] FIG. 5E, which is followed by FIGS. 5H-5K, illustrates that when an upward swipe gesture is detected on an application representation, the device closes the application corresponding to the application representation from which the upward swipe gesture is initiated.

[0152] As shown in Figure 5E, contact 5018 is detected on card 5012 shown in the application switching user interface. In Figure 5H, after contact 5018 remains substantially stationary for a threshold amount of time (e.g., a long press-time threshold), the device expands card 5012 to indicate that card 5012 has been selected. In some embodiments, the device expands card 5012 upon detecting touchdown of contact 5018 on card 5012 without first requiring the contact to remain stationary for the threshold amount of time.

[0153] 5I-5J continue from either the state shown in FIG. 5E (e.g., for embodiments not requiring an initial touch-hold of contact 5018) or the state shown in FIG. 5H (e.g., for embodiments requiring an initial touch-hold of contact 5018), where an upward movement of contact 5018 drags card 5012 upward across background 5008 within the application switching user interface. As shown in FIGS. 5I-5J, the size of card 5012 remains constant while card 5012 is dragged upward by contact 5018. In some embodiments, the size of card 5012 during the upward movement is the same as the size of other cards in the application switching user interface (e.g., if card 5012 was expanded by a touch-hold of contact 5018 in FIG. 5H, the size of card 5012 is reduced back to its original size before being dragged out of the stack). In some embodiments, the size of card 5012 during the upward movement is the expanded size of card 5012 (e.g., as shown in FIG. 5H).

[0154] 5J-5K, the device detects lift-off of contact 5018 at the end of contact 5018's upward movement, and in response to the lift-off of contact 5018 (e.g., the lift-off position of contact 5018 is shown by a dashed line in FIG. 5K), in accordance with a determination that the contact has moved more than a threshold distance beyond its original position, the device stops displaying card 5012 and shifts cards 5010, 5016 to newly reveal card 5020 in the configuration shown in FIG. 5E. When card 5012 is removed from the application launching user interface, the device closes the application (e.g., the Settings application) corresponding to card 5012. The next time the application switching user interface is displayed, the device removes stored information regarding the last-displayed state of the Settings application associated with the application switching user interface, so that card 5012 is not included in the stack of application representations of other recently used applications.

[0155] Figure 5L follows either Figure 5E or Figure 5H. Figures 5E and 5L (or Figures 5H and 5L) show that if contact 5018 does not move from its starting position by more than a threshold amount (e.g., remains substantially stationary) for a threshold amount of time before being lifted off the touchscreen, the device processes the detected input (e.g., a tap input by contact 5018 on card 5012) as a request to switch to the application corresponding to card 5012. As shown in Figure 5L (e.g., the lift-off position of contact 5018 is shown in dashed lines), the device stops displaying the application switching user interface shown in Figure 5E (or Figure 5H) and displays the last displayed user interface of the settings application (e.g., user interface 5022). In other words, in the process shown in the sequence of Figures 5A, 5B, 5E, and 5L, the user switched from displaying a maps application to a settings application using the application switching user interface.

[0156] Figure 5M is continued from Figure 5E. Figure 5E, which is continued from Figures 5M-5O, shows that when an upward swipe gesture is detected over another application representation, the device closes the application corresponding to the application representation from which the upward swipe gesture is initiated.

[0157] As shown in Figure 5E, contact 5024 is detected on card 5010 shown in the application switching user interface. In Figure 5M, after contact 5024 remains substantially stationary for a threshold amount of time (e.g., a long press-time threshold), the device expands card 5010 to indicate that card 5010 has been selected. In some embodiments, the device expands card 5010 upon detecting touchdown of contact 5024 on card 5010 without first requiring the contact to remain stationary for the threshold amount of time.

[0158] 5N continues from either the state shown in FIG. 5E (e.g., for embodiments not requiring an initial touch-hold of contact 5024) or the state shown in FIG. 5M (e.g., for embodiments requiring an initial touch-hold of contact 5024), where an upward movement of contact 5024 drags card 5010 upward across background 5008 within the application switching user interface. As shown in FIG. 5N, the size of card 5010 remains constant while card 5010 is dragged upward by contact 5024. In some embodiments, the size of card 5010 during the upward movement is the same as the size of other cards in the application switching user interface (e.g., if card 5010 was expanded by a touch-hold of contact 5024 in FIG. 5M, the size of card 5010 is reduced back to its original size before being dragged out of the stack). In some embodiments, the size of card 5010 during the upward movement is the expanded size of card 5010 (e.g., as shown in FIG. 5M).

[0159] 5N-5O, the device detects lift-off of contact 5024 at the end of the upward movement of contact 5024, and in response to the lift-off of contact 5024 (e.g., the lift-off position of contact 5024 is shown by a dashed line in FIG. 5O), the device stops displaying card 5010 and shifts cards 5012, 5016 to newly reveal card 5020 in the configuration shown in FIG. 5E. When card 5010 is removed from the application launching user interface, the device closes the application corresponding to card 5010 (e.g., a map application). The next time the application switching user interface is displayed, the device removes stored information about the last displayed state of the map application associated with the application switching user interface so that card 5010 is not included in the stack of application representations of other recently used applications.

[0160] Figure 5P is a continuation of Figure 5N. In Figures 5N and 5P, contact 5024 drags card 5010 upward, away from the stack of cards in the application switching user interface (e.g., as shown in Figure 5N), and then in the opposite direction of movement (e.g., downward, toward the original position of contact 5024). As shown in Figure 5P, after lift-off of contact 5024 is detected (e.g., the lift-off position of contact 5024 is shown by a dashed line in Figure 5P), the device moves card 5010 back into the stack of cards in the application switching user interface, and the configuration of the application switching user interface in Figure 5E is restored.

[0161] Figure 5Q is a continuation of Figure 5E. Figures 5Q-5T, which follow Figure 5E, illustrate that an upward swipe gesture is detected in a portion of the application switching user interface outside of the application representation of any application (e.g., a portion of background 5008 that is not blocked by any cards (e.g., the bottom or top of background 5008)) and a process that is not within the bottom edge of the touchscreen causes the device to navigate from the application switching user interface to an application launch user interface (e.g., home screen user interface 5014).

[0162] 5E and 5Q, contact 5026 is initially detected below the stack of cards in the application switching user interface (e.g., the initial position of contact 5026 is shown by a dashed line in FIG. 5Q) and then moves upward on the touchscreen. In response to the upward movement of contact 5026, the device changes the display configuration of the application representations in the application switching user interface. For example, stacked cards 5010, 5012, and 5016 move away from each other (and optionally resize) and stop overlapping each other in response to the upward movement of contact 5026, as shown in FIG. 5Q.

[0163] 5Q-5R show that as contact 5026 continues to move upward, cards 5010, 5012, and 5016 move upward in unison with contact 5026. As cards 5010, 5012, and 5016 move upward with contact 5026, the size of cards 5010, 5012, and 5016 dynamically decreases in size as contact 5026 moves upward.

[0164] In some embodiments, while the movement of contact 5026 still meets the criteria for navigating back to the application switching user interface (e.g., if a movement parameter of the movement of contact 5026 is below a threshold (e.g., the movement distance is below a threshold distance or the movement speed is below a threshold speed before lift-off)) (e.g., the criteria for navigating back to the application launch user interface are not met), the three cards 5010, 5012, and 5016 remain displayed side by side below contact 5026, as shown in Figures 5Q-5R.

[0165] In FIG. 5S, once the movement of contact 5026 meets the criteria for navigating to an application launch user interface (e.g., home screen user interface 5014), the device stops displaying cards 5016 and 5010 and displays only card 5012, which is the center card shown in the navigation user interface, indicating that if lift-off of contact 5026 is detected at this point, the device will display the application launch user interface.

[0166] 5S-5T, lift-off of contact 5026 is detected while the criteria for navigating to an application launching user interface are met (e.g., the lift-off location of contact 5026 is shown with a dashed line in FIG. 5T). In response to detecting lift-off of contact 5026, in accordance with a determination that the criteria for navigating to an application launching user interface have been met, the device stops displaying the navigation user interface (e.g., as shown in FIG. 5S) and displays an application launching user interface (e.g., the home screen user interface 5014 shown in FIG. 5T).

[0167] In some embodiments, home affordance 5006 is not displayed within the application switching user interface or the navigation user interface, but an upward edge swipe gesture detected (e.g., initiated from the bottom edge region of the touchscreen) while the application switching user interface is displayed also causes the device to navigate to the application launch user interface, optionally displaying the navigation user interface animation shown in Figures 5Q-5S. This is in contrast to the navigation scenarios shown in Figures 5A-5D. For example, the navigation user interfaces in Figures 5Q and 5R do not include a representation of the application switching user interface (e.g., there is no card representing the application switching user interface shown in Figure 5E within the navigation user interfaces shown in Figures 5Q and 5R), but instead include cards representing recently opened applications that were not displayed when contact (e.g., contact 5026) was initially detected in the bottom edge region of the touchscreen. Thus, in some embodiments, in response to an upward edge swipe gesture, in accordance with a determination that the respective user interface currently displayed at the start of the gesture is an application user interface, the device displays a navigation user interface that includes a representation of the respective user interface, and in accordance with a determination that the respective user interface currently displayed at the start of the gesture is a system-level user interface (e.g., an application switching user interface or an application launching user interface), the device displays a navigation user interface that does not include a representation of the respective user interface.

[0168] 5E, which is followed by Figures 5Q-5T, the visual feedback is continuous and fluid according to the upward and lateral movement of contact 5026. The movement of contact 5026 is continuously evaluated against criteria for navigating to a different user interface (e.g., an application switching user interface or an application launching user interface), and corresponding visual feedback is provided to indicate the current target state of the user interface navigation (e.g., if the movement of contact 5026 were reversed before liftoff of contact 5026, a reversal of the changes shown in Figures 5S-5Q would be indicated).

[0169] Figure 5U is followed by Figure 5E or Figure 5H. The sequence of Figures 5U-5X, which follows Figure 5E, and the sequences of Figures 5U-5V and 5Z, illustrate that a downward swipe gesture initiated from a location on the application representation of the respective application in the application switching user interface causes the device to display the respective application in either the expanded reachable mode or the default full-screen mode, depending on whether the criteria for navigating to the application in the expanded reachable mode or the criteria for navigating to the application in the default full-screen mode are met.

[0170] First, the sequence of FIG. 5E (or FIG. 5H ), followed by FIGS. 5U and 5V , shows that after contact 5018 is detected on card 5012 within an application-switching user interface (e.g., in the configuration shown in FIG. 5E (or FIG. 5H )), downward movement of contact 5018 causes cards 5010, 5012, and 5016 to increase in size in accordance with the downward movement of contact 5018. As card 5012 continues to increase in size with the downward movement of contact 5018, cards 5010 and 5016 are pushed out of view (e.g., as shown in FIG. 5V ). In FIG. 5V , once only card 5012 is displayed on background 5008, the criteria for navigating to the application corresponding to card 5012 in default full-screen mode are met (e.g., the distance of the downward movement of contact 5018 is greater than a first threshold distance and less than a second threshold distance, or the movement speed of the downward movement of contact 5018 is less than a threshold speed). If lift-off of contact 5018 occurs at the time shown in FIG. 5V, the device will display user interface 5022 (e.g., as shown in FIG. 5Z) for the Settings application in the default full-screen mode.

[0171] If lift-off of contact 5018 does not occur at the time shown in Figure 5V and downward movement of contact 5018 continues (e.g., as shown in Figure 5W), the full-width displayed card 5012 is shifted downward along with contact 5018 to reveal a portion of background 5008 above card 5012 on the touchscreen. In some embodiments, the display of the pull-up tab (e.g., chevron 5028) is gradually revealed to indicate that the criteria for displaying the application in expanded reachable mode will soon be met.

[0172] 5W-5X illustrate that in response to detecting lift-off of contact 5018 after the contact has crossed a threshold position on the touchscreen (e.g., reaching a lower edge region of the touchscreen, as indicated by the lift-off position of contact 5018 shown in dashed lines in FIG. 5X), the device displays a user interface (e.g., user interface 5032) for a Settings application in an extended reachable mode (e.g., user interface 5032 shows only the top portion of user interface 5022, as if user interface 5022 had been shifted partway down on the touchscreen). In some embodiments, a pull-up tab (e.g., tab 5030 having a chevron-shaped indicator) is displayed adjacent to the top of user interface 5032. Displaying the application's user interface in an extended reachable mode (e.g., as shown in FIG. 5X) allows a user to easily access the top portion of the user interface (e.g., using their thumb) while holding the device in their hand.

[0173] 5X-5Z illustrate the process of returning to displaying an application's user interface in the default full-screen mode (e.g., user interface 5022 in FIG. 5Z) based on input detected while the application's user interface (e.g., user interface 5032 in FIG. 5X) is displayed in the extended reachable mode.

[0174] In Figure 5X, multiple contacts (e.g., contacts 5034, 5036, and 5038) are shown on the touchscreen. These contacts are not simultaneously detected. They represent contacts detected separately in different example scenarios that result in the display of the Settings application user interface in the default full-screen mode.

[0175] 5X-5Z, the device detects contact 5036 on tab 5030 and detects movement of contact 5036 pulling upward on tab 5030, dragging the user interface of the settings application upward. In FIG. 5Z, once contact 5036 moves beyond a threshold position or lifts off (e.g., with a rapid flick gesture) above a threshold velocity (e.g., the lift-off position of contact 5036 is shown by a dashed line in FIG. 5Z), the device displays user interface 5022 of the settings application in a default full-screen mode.

[0176] In Figure 5X, which is followed by Figure 5Z, the device detects a tap input by contact 5034 in a region of background 5008 above user interface 5032 of the Settings application displayed in the expanded reachable mode (e.g., the lift-off position of contact 5034 is shown in dashed line in Figure 5Z). In response to detecting the tap input by contact 5034, the device stops displaying the Settings application in the expanded reachable mode and displays the Settings application in the default full-screen mode (as shown in Figure 5Z).

[0177] In Figure 5X, which is followed by Figure 5Z, the device detects an upward edge swipe input (e.g., upward movement of contact 5038) initiated from a bottom edge region of the touchscreen (e.g., as indicated by the location of home affordance 5006). Pursuant to a determination that the upward edge swipe input meets predetermined criteria (e.g., having a lift-off velocity that exceeds a threshold velocity or a movement distance that exceeds a threshold distance from the bottom edge of the touchscreen), the device stops displaying the Settings application in the expanded reachable mode (e.g., as shown in Figure 5X) and displays the Settings application in the default full-screen mode (e.g., as shown in Figure 5Z).

[0178] 6A-6D are flow diagrams illustrating methods of interacting with an application switching user interface, according to some embodiments. Although some of the examples below are described with reference to input on a touch-sensitive display that combines the touch-sensitive surface and display, in some embodiments, the device detects input on touch-sensitive surface 451 that is separate from display 450, as shown in FIG.

[0179] In some embodiments, method 6000 is performed by an electronic device (e.g., portable multifunction device 100, FIG. 1A ) and / or one or more components of the electronic device (e.g., I / O subsystem 106, operating system 126, etc.). In some embodiments, method 6000 is governed by instructions stored on a non-transitory computer-readable storage medium and executed by one or more processors of the device, such as one or more processors 122 of device 100 ( FIG. 1A ). For ease of explanation, method 6000 is described below as being performed by device 100. In some embodiments, with reference to FIG. 1A , the operations of method 6000 are performed or used, at least in part, by operating system 126, communications module 128, and / or graphics module 132, and a touch-sensitive display (e.g., touch screen 112). Some operations of method 6000 are optionally combined and / or the order of some operations is optionally changed.

[0180] As described below, method 6000 (and associated interface) provides an intuitive way to perform operations in an application switching user interface, such as closing an application, navigating to an application launch user interface (e.g., a home screen), or navigating to a different application. The method reduces the number, range, and / or nature of inputs from a user when performing operations in an application switching user interface, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, allowing a user to perform application switching user interface operations faster and more efficiently conserves power and extends the time between battery charges.

[0181] In method 6000, a device displays (6002) an application on a display (e.g., as shown in FIG. 5A , the device displays user interface 5002 of a map application). While displaying the application on the display (e.g., as opposed to a system-level user interface such as a home screen user interface or an application launch user interface, or a control panel user interface), the device detects (6004) an input corresponding to a request to display an application switching user interface (e.g., an upward swipe with contact 5004 initiated from the bottom edge of the touchscreen, as shown in FIGS. 5A-5B ). In response to detecting an input corresponding to a request to display an application switching user interface, the device displays an application switching user interface (e.g., a user interface listing multiple recently used applications as shown in FIG. 5B followed by FIG. 5E ) including a representation of multiple recently used applications (e.g., applications most recently used on a device, such as a predetermined number (e.g., 2, 3, 4, 5, 6) of recently viewed or used applications on the device), including a first application representation corresponding to the first application (e.g., card 5010 corresponding to a maps application) and a second application representation corresponding to a second application (e.g., card 5012 corresponding to a settings application) (6006). While displaying the application switching user interface, the device detects a touch gesture (e.g., a touch-and-drag gesture by the contact, including an initial touchdown of the contact and a subsequent movement of the contact, and optionally a liftoff of the contact) by a contact on the touch-sensitive surface (e.g., contact 5018, 5024, or 5026 in FIG. 5B followed by FIG. 5E ) (6008). In response to detecting the touch gesture (6010), the device performs one or more actions according to various decisions (e.g., actions 6012, 6014, 6016, 6020, 6022, 6024, 6032, 6034, and 6036).Pursuant to a determination that the touch gesture includes movement by contact (e.g., contact 5018) in a first direction (e.g., a direction on the touch-sensitive surface corresponding to a vertically upward direction across the display) and initiated from a location corresponding to a first application representation (e.g., the Settings application), the device closes (6012) the first application (e.g., regardless of the duration of the contact on the touch-sensitive surface prior to detecting movement of the contact in the first direction). This is shown in Figures 5I-5K, which follow Figure 5E or Figure 5H, in which the Settings application is closed (e.g., associated with the application switching user interface and removed from the list of recently opened applications) after an upward swipe gesture by contact 5018 is detected on card 5012. The other application representation applications and the application switching user interface remain displayed after the upward swipe gesture by contact 5018 ends. Pursuant to determining that the touch gesture included movement by the contact (e.g., contact 5024) in the first direction and initiated at a location corresponding to the second application representation (e.g., a maps application), the device closes (6014) the second application (e.g., regardless of the duration of the contact on the touch-sensitive surface prior to detecting movement of the contact in the first direction). This is shown in Figures 5N-5O, which follow Figure 5E or Figure 5M, in which the maps application is closed (e.g., removed from the list of recently opened applications associated with the application switching user interface) after an upward swipe gesture by contact 5024 is detected on card 5010. The other application representation applications and the application switching user interface remain displayed after the upward swipe gesture by contact 5018 ends.In accordance with a determination that the touch gesture includes movement by the contact (e.g., contact 5026) in a first direction and initiated at a location (e.g., a location outside of the application representations) corresponding to a predefined region within the application switching user interface that is outside (e.g., below) the first and second application representations, the device stops displaying (6016) the application switching user interface and displays an application launching user interface (e.g., home screen user interface 5014, shown in FIG. 5T) that is distinct from the application switching user interface (e.g., home screen user interface). This is illustrated in FIGS. 5Q-5T, which follow FIG. 5E, in which the device displays home screen user interface 5014 in response to an upward swipe gesture (as opposed to an upward edge swipe gesture) by contact 5026 detected on background 5008 that is not covered by any cards in the application switching user interface. In some embodiments, the application launching user interface is a home screen user interface that includes application icons and / or widgets displayed in a predetermined arrangement (e.g., an arrangement that is independent of the relative recency of the applications when last used for at least some of the applications). In some embodiments, the application launch user interface is an application drawer user interface that includes application icons displayed in a predetermined arrangement. In some embodiments, the application icons are icons that, when activated (e.g., by a tap gesture on the icon), launch the corresponding application (e.g., cause the device to open the application and display the application's default start user interface). In some embodiments, the recently used application is an opened application.As used herein and in the claims, the term "open application" refers to a software application for which state information is maintained (e.g., as part of device / global internal state 157 and / or application internal state 192). An open application can be any of the following types of applications: an active application that is currently displayed on display 112 (or for which a corresponding application view is currently displayed on a display); a background application (or background process) that is not currently displayed on display 112 but for which one or more application processes (e.g., instructions) for the corresponding application are being processed (i.e., running) by one or more processors 120; a suspended application that is not currently running and is stored in volatile memory (e.g., DRAM, SRAM, DDR, RAM, or other volatile random access semiconductor memory devices of memory 102); and a dormant application that is not running and is stored in non-volatile memory (e.g., one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile semiconductor storage devices of memory 102). As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application within a first application does not close the first application.When a second application is displayed and the display of a first application is discontinued, the first application, which was the active application when displayed, may become a background application, a suspended application, or a paused application, but the first application remains an open application while its state information is maintained by the device.

[0182] In some embodiments, while detecting the touch gesture, the device determines (6018) that a contact (e.g., contact 5018 or contact 5024 in FIG. 5E ) was initially detected at a location corresponding to a respective application representation (e.g., a settings application or a maps application as shown in FIG. 5E ). In response to determining that a contact was initially detected at a location corresponding to the respective application representation, the device enlarges the respective application representation. This is shown, for example, in FIGS. 5H and 5M , where the device enlarges cards 5012 and 5010, respectively, upon detecting contacts 5018 and 5024, respectively. Enlarging a particular application representation provides the user with visual feedback indicating that the contact in the touch gesture is at a location that will cause the electronic device to perform an action associated with the particular application representation. Providing improved feedback improves device usability (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) and makes the user-device interface more efficient.

[0183] In some embodiments, in response to detecting 6010 a touch gesture with the contact, following a determination that the touch gesture began on a respective application representation (e.g., the first application representation or the second application representation) and ended (e.g., after contact lift-off or a predetermined timeout) with the contact (e.g., contact 5018) moving less than a threshold amount from the contact's starting location on the touch-sensitive surface, the device replaces the display of the application switching user interface with a user interface (e.g., a full-screen user interface) for the respective application (e.g., the Settings application). This is shown in Figures 5U-5V and 5Z, which follow Figure 5E, where a downward swipe gesture on card 5018 (e.g., a short downward swipe that does not pass a threshold location on the touchscreen) causes the device to display user interface 5022 of the Settings application in full-screen mode. This is also shown in Figure 5L, which follows Figure 5E, where a tap gesture with contact 5018 causes the device to display the Settings application and stop displaying the application switching user interface. Instead of closing a particular application with a move gesture, navigating to a particular application with a stay gesture provides additional operations that can be performed within the application switching user interface. Providing additional control options without cluttering the user interface with additional display controls improves usability of the device (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) and makes the user-device interface more efficient.

[0184] In some embodiments, in method 6000, in response to detecting a touch gesture by the contact (6010), the device maintains (6022) the display of an application switching user interface in accordance with determining that the touch gesture includes movement of the contact in a second direction different (e.g., opposite) from the first direction. In any of the processes shown in Figures 5F, 5H-5J, 5M-5N, 5Q-5S, and 5U-5W following Figure 5E, if movement of the contact (e.g., contact 5018, 5024, or 5026) reverses back to its starting position (or is within a threshold distance of the starting position) and then lifts off, the device restores the display of the application switching user interface to the configuration shown in Figure 5E. Maintaining the application switching user interface in response to the contact moving in a direction different from the first direction provides a way to avoid or cancel an action that would have occurred if the contact had continued to move in the first direction. Providing additional control options without cluttering the user interface with additional display controls (e.g., undo or cancel icons) improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device).

[0185] In some embodiments, in response to detecting a touch gesture with the contact (e.g., contact 5018), according to a determination that the touch gesture initiated at a location corresponding to the respective application representation (e.g., card 5012) and includes movement of the contact in a second direction (e.g., downward) different from (e.g., opposite to) the first direction, the device replaces (6024) the display of the application switching user interface with a user interface for the respective application, where the user interface for the respective application is shifted in a predetermined direction (e.g., downward so that a top of the user interface for the respective application is closer to the bottom edge of the electronic device). This is shown in Figures 5U-5X following Figure 5E, where a downward swipe gesture with contact 5018 on card 5012 causes the device to display the user interface of the Settings application in an extended reachable mode (e.g., shifted partway downward on the touchscreen). Instead of closing a particular application with a gesture moving in another direction (e.g., upward), the user interface may shift (e.g., downward) to navigate to the particular application as the gesture moves in one direction (e.g., downward), thereby providing additional operations that can be performed in the application-switching user interface by making it easier for a user to operate a particular application with one hand (e.g., by improving the reachability of controls at the top of the particular application's user interface).Improve device usability and make the user-device interface more efficient by providing additional control options without cluttering the user interface with additional display controls (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device).

[0186] In some embodiments, displaying the user interface for each application shifted in the default direction includes removing (6026) the user interface for the respective application from a default portion of the display (e.g., the top of the touchscreen does not display any portion of user interface 5022, but instead displays a portion of background 5008, as shown in FIG. 5X). In method 600, while displaying the user interface for each application shifted in the default direction, the device detects a gesture (e.g., a drag gesture with contact 5036 or 5038) at a location corresponding to the default portion of the display (e.g., a drag gesture initiated on the touch-sensitive surface corresponding to a drag affordance (e.g., chevron 5030 in FIG. 5X) displayed in or with the shifted user interface for the respective application). The device returns the user interface for the respective application (e.g., user interface 5022) to the default portion of the display in accordance with the gesture (e.g., gradually moving the application back into the default portion of the display as the gesture progresses). This is shown, for example, in Figures 5X-5Y (e.g., showing an upward swipe gesture on tab 5030 causing the device to exit extended reachable mode), and also shown, for example, in Figure 5Z, which follows Figure 5X (e.g., showing an upward swipe gesture from the bottom edge of the touchscreen causing the device to exit extended reachable mode).

[0187] In some embodiments, while displaying the user interface for the respective application shifted in a predetermined direction, in response to detecting a tap gesture within a predetermined portion of the display, the device shifts the user interface for the respective application back into the predetermined portion of the display. This is shown, for example, in FIG. 5Z, which follows FIG. 5X (e.g., showing a tap gesture with contact 5034 causing the device to exit extended reachability mode). Shifting the application's user interface back to its unshifted position in response to another gesture (e.g., when the application is displayed full screen on the display) allows the user to interact with the lower portion of the user interface and allows the user to interact with the upper portion of the user interface using one-handed operation. Providing additional control options without cluttering the user interface with additional display controls improves device usability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device).

[0188] In some embodiments, in response to detecting a touch gesture (6010), following a determination that the touch gesture includes movement of the contact in a third direction (e.g., leftward or rightward) different from the first direction (e.g., vertically), the device maintains (6028) display of the application switching user interface and scrolls the application representations displayed within the application switching user interface (e.g., regardless of the duration of the contact on the touch-sensitive surface before detecting movement of the contact in the third direction). This is shown, for example, in FIGS. 5E-5G where a rightward swipe gesture with contact 5018 scrolls cards within the application switching user interface, revealing new cards deeper within a stack of cards representing recently used applications. Scrolling the application representations with a movement gesture in the third direction (e.g., rightward or leftward) displays additional application representations for selection within the application switching user interface, instead of closing a particular application with a movement gesture in the first direction (e.g., upward). Improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input when operating / interacting with the device and reducing user errors) by providing additional control options without cluttering the user interface with additional display controls.

[0189] In some embodiments, in response to detecting 6010 a touch gesture, in accordance with determining that the touch gesture initiated at a location corresponding to a respective application representation and includes movement of the contact, the device moves 6030 the respective application representation in accordance with the movement of the contact (e.g., on a touch-sensitive display, moving the application representation upward if the contact moves upward across the display, moving the application representation downward if the contact moves downward across the display, moving the application representation left if the contact moves left across the display, and / or moving the application representation right if the contact moves right across the display). This is shown, for example, in FIGS. 5F, 5I, 5N, and 5U-5W. Moving a particular application representation in accordance with the movement of the contact provides visual feedback to the user indicating that the touch gesture will cause the electronic device to perform an operation associated with the particular application representation. Providing improved feedback improves device usability (e.g., by helping users provide appropriate input when operating / interacting with the device and reducing user errors) and makes the user-device interface more efficient.

[0190] In some embodiments, in response to detecting 6010 a touch gesture, in accordance with a determination that the touch gesture initiated at a location corresponding to a respective application representation (e.g., the first or second application representation) and includes movement of the contact in the first direction, the device moves 6032 the respective application representation in the first direction (e.g., as shown in FIGS. 5I-5J) without moving the other application representations in the first direction (e.g., the amount of movement of the respective application increases as the amount of movement of the contact in the first direction increases), and in accordance with a determination that the touch gesture initiated at a location corresponding to a location outside the predetermined region and includes movement of the contact in the first direction, the device simultaneously moves the respective application representation and the one or more other application representations in the first direction (e.g., as shown in FIGS. 5Q-5R) (e.g., the amount of movement of the respective application and the one or more other application representations increases as the amount of movement of the contact in the first direction increases). Moving only a specific application representation in a first direction without moving other application representations in the first direction provides visual feedback to the user indicating that an action will be performed only on the application corresponding to the specific application representation (e.g., closing the corresponding application without closing other open applications). Moving multiple application representations simultaneously in the first direction provides visual feedback to the user indicating that an action not specific to a specific application (e.g., going to a home screen user interface) will be performed. Providing improved feedback improves device operability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device).

[0191] In some embodiments, in response to detecting 6010 a touch gesture, in accordance with determining that the touch gesture initiated at a location corresponding to a respective application representation (e.g., the first or second application representation) and includes movement of the contact in a first direction, the device moves 6034 the respective application representation in accordance with the movement of the contact in the first direction without changing the size of the respective application representation (e.g., as shown in FIGS. 5I-5J , the size of card 5012 remains constant during the upward movement caused by contact 5018). In accordance with determining that the touch gesture initiated at a location corresponding to a location outside the predefined region and includes movement of the contact in the first direction, the device simultaneously moves the respective application representations and resizes (e.g., increases or decreases in size) the respective application representations in accordance with the movement of the contact in the first direction (e.g., the amount of change in size of the respective application representations increases as the amount of movement of the contact in the first direction increases) (e.g., as shown in FIGS. 5Q-5R, the size of card 5012 decreases as it is dragged upward by contact 5026). In some embodiments, the device simultaneously resizes one or more other application representations in accordance with the movement of the contact in the first direction. For example, as shown in FIGS. 5Q-5R, the sizes of cards 5010, 5012, and 5016 change in unison during the upward movement of the cards caused by movement of contact 5026. Moving a particular application representation in a first direction without changing its size provides the user with visual feedback indicating that an action will be performed on the application corresponding to the particular application representation (e.g., closing the corresponding application without closing other open applications). Moving multiple application representations in a first direction provides the user with visual feedback indicating that an action not specific to a particular application (e.g., going to a home screen user interface) will be performed while changing their size.Providing improved feedback improves device usability (e.g., by helping users provide appropriate input when operating / interacting with the device and reducing user errors) and makes the user-device interface more efficient.

[0192] In some embodiments, the application switching user interface includes (6036) multiple application representations that overlap each other (eg, as shown in FIG. 5E, cards 5010, 5012, and 5016 overlap each other). In method 6000, in response to detecting a touch gesture (6010), in accordance with a determination that the touch gesture initiated at a location corresponding to a respective application representation (e.g., a first or second application representation) and includes movement of contact in a first direction, the device moves (6038) the respective application representation while maintaining at least a portion of the overlap of the multiple application representations (e.g., as shown in Figures 5I-5J, card 5012 continues to overlap with cards 5010 and 5016 during its upward movement), and in accordance with a determination that the touch gesture initiated at a location corresponding to a location outside the predetermined region and includes movement of contact in the first direction, the device moves the respective application representation and moves and / or resizes one or more of the application representations to eliminate overlap between the multiple application representations (e.g., as shown in Figures 5Q-5I, cards 5012, 5010, and 5016 are spread apart, resized, and move upward in parallel without overlapping). Moving a particular application representation in a first direction while maintaining at least some overlap of other application representations provides visual feedback to the user indicating that an action will be performed on the application corresponding to the particular application representation (e.g., closing the corresponding application without closing other open applications). Moving and / or resizing multiple application representations to eliminate overlap between the application representations provides visual feedback to the user indicating that an action not specific to a particular application (e.g., going to a home screen user interface) will be performed.Providing improved feedback improves device usability (e.g., by helping users provide appropriate input when operating / interacting with the device and reducing user errors) and makes the user-device interface more efficient.

[0193] 6A-6D are merely examples, and it should be understood that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In some embodiments, one or more operations of method 6000 are combined with, supplemented by, or replaced by one or more operations of other methods described herein.

[0194] 6A-6D are optionally implemented by the components depicted in FIGS. 1A-1B. For example, display operations 6002, 6006, and 6016, detect operations 6004 and 6008, and close operations 6012 and 6014 are optionally performed by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 of event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. Corresponding event recognizer 180 of application 136-1 compares the event information with corresponding event definition 186 to determine whether a first contact at a first position on the touch-sensitive surface (or a rotation of device 100) corresponds to a predetermined event or sub-event, such as selecting an object on a user interface or rotating device 100 from one orientation to another. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. The event handler 190 optionally uses or invokes 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 what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes may be implemented based on the components depicted in FIGS. 1A-1B.

[0195] The foregoing has been described with reference to specific embodiments for purposes of explanation. However, the exemplary discussion above is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. These embodiments were chosen and described in order to best explain the principles of the invention and its practical application, and thereby enable others skilled in the art to best utilize the invention and the various described embodiments with various modifications suited to the particular uses contemplated.

Claims

1. A method comprising:

1. A computer system in communication with a display generation component and one or more sensors for detecting user input, comprising: detecting a first user input comprising a first movement via the one or more sensors while a first user interface object corresponding to a first application and a second user interface object corresponding to a second application are simultaneously displayed at their respective depths and a first portion of a background behind the first user interface object and the second user interface object is viewable via the display generation component; In response to detecting the first user input including the first movement, responsive to determining that the first user input is made directly to the first user interface object corresponding to the first application and that the first movement satisfies first criteria; maintaining display of the second user interface object corresponding to the second application while at least the first portion of the background remains viewable through the display generation component; ceasing display of the first user interface object corresponding to the first application; responsive to determining that the first user input is made directly to the second user interface object corresponding to the second application and that the first movement satisfies the first criterion; maintaining display of the first user interface object corresponding to the first application while at least the first portion of the background remains viewable through the display generation component; ceasing display of the second user interface object corresponding to the second application; and A method comprising:

2. In response to detecting the first user input including the first movement, 2. The method of claim 1, further comprising: ceasing display of the first user interface object and the second user interface object in accordance with a determination that the first user input is not made directly to the first user interface object and the second user interface object and that the first movement satisfies the first criterion; and displaying a first system user interface including respective application icons corresponding to a plurality of applications.

3. In response to detecting the first user input including the first movement, pursuant to a determination that the first user input is made directly to the first user interface object corresponding to the first application and the first movement satisfies the first criterion, moving the first user interface object according to a first portion of the first movement while maintaining a position of the second user interface object relative to the background; pursuant to a determination that the first user input is made directly to the second user interface object corresponding to the second application and that the first movement satisfies the first criterion, moving the second user interface object according to a second portion of the first movement while maintaining a position of the first user interface object relative to the background; 3. The method of claim 1 or 2, comprising:

4. Unlike the first portion of the background visible through the display generation component, the first user interface object corresponding to the first application is displayed at a first depth and the second user interface object corresponding to the second application is displayed at a second depth different from the first depth.

4. The method according to any one of claims 1 to 3.

5. In response to detecting the first user input including the first movement, and in accordance with a determination that the first user input is made directly to the first user interface object corresponding to the first application and that the first movement satisfies a second criterion different from the first criterion, moving the first user interface object according to a third portion of the first movement to reveal a portion of a third user interface object corresponding to a third application.

5. The method of claim 1, comprising:

6. The first criterion requires that the first movement satisfy a first directional criterion in order for the first criterion to be satisfied, and the second criterion requires that the first movement satisfy a second directional criterion that is different from the first directional criterion in order for the second criterion to be satisfied. The method of claim 5.

7. The first user interface object corresponding to the first application includes a unique identifier for the first application and unique content from the first application, and the second user interface object corresponding to the second application includes a unique identifier for the second application and unique content from the second application.

7. The method according to any one of claims 1 to 6.

8. A display generation component; one or more sensors for detecting user input; one or more processors; Memory and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: detecting a first user input comprising a first movement via the one or more sensors while a first user interface object corresponding to a first application and a second user interface object corresponding to a second application are simultaneously displayed at their respective depths and a first portion of a background behind the first user interface object and the second user interface object is viewable via the display generation component; In response to detecting the first user input including the first movement, responsive to determining that the first user input is made directly to the first user interface object corresponding to the first application and that the first movement satisfies first criteria; maintaining display of the second user interface object corresponding to the second application while at least the first portion of the background remains viewable through the display generation component; ceasing display of the first user interface object corresponding to the first application; responsive to determining that the first user input is made directly to the second user interface object corresponding to the second application and that the first movement satisfies the first criterion; maintaining display of the first user interface object corresponding to the first application while at least the first portion of the background remains viewable through the display generation component; ceasing display of the second user interface object corresponding to the second application; and 20. A computer system comprising:

9. A computer system as described in claim 8, wherein the one or more programs include instructions for executing a method described in any one of claims 2 to 7.

10. One or more programs, when executed by a computer system having a display generation component and one or more sensors for detecting user input, that cause the computer system to: detecting, via the one or more sensors, a first user input comprising a first movement while a first user interface object corresponding to a first application and a second user interface object corresponding to a second application are simultaneously displayed at their respective depths and a first portion of a background behind the first user interface object and the second user interface object is viewable through the display generation component; In response to detecting the first user input including the first movement, responsive to determining that the first user input is made directly to the first user interface object corresponding to the first application and that the first movement satisfies first criteria; maintaining the display of the second user interface object corresponding to the second application while at least the first portion of the background remains viewable through the display generation component; ceasing the display of the first user interface object corresponding to the first application; responsive to determining that the first user input is made directly to the second user interface object corresponding to the second application and that the first movement satisfies the first criterion; maintaining the display of the first user interface object corresponding to the first application while at least the first portion of the background remains viewable through the display generation component; ceasing the display of the second user interface object corresponding to the second application; One or more programs containing instructions.

11. One or more programs as described in claim 10, which, when executed by the computer system, include instructions that cause the computer system to perform the method described in any one of claims 2 to 7.

Images