CAPTURING AND DISPLAYING IMAGES WITH MULTIPLE FOCAL PLANES

[0001] This application claims priority to U.S. Provisional Application No. 62/739,093, filed Sep. 28, 2018, entitled “CAPTURING AND DISPLAYING IMAGES WITH MULTIPLE FOCAL PLANES”, the content of which is hereby incorporated by reference in its entirety.

[0002] The present disclosure relates generally to user interfaces, and more specifically to techniques for capturing and displaying images with multiple focal planes.

[0003] Users are increasingly using electronic devices to capture images and virtually communicate with others for personal and business reasons. Most electronic devices are capable of capturing images for live communication between users. As an example, some electronic devices provide interactive interfaces to display and control the live communication.

[0004] Some techniques for capturing and displaying images, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface to capture or display images with different focal planes, which may include multiple key presses or other physical inputs. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

[0005] Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for capturing and displaying images with multiple focal planes. Such methods and interfaces optionally complement or replace other methods for capturing and displaying images. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] In some embodiments, a method is performed at an electronic device with a display. The method includes: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.

[0007] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.

[0008] In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.

[0009] In some embodiments, an electronic device includes a display, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.

[0010] In some embodiments, an electronic device includes: a display; means for displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, means for, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and means for, while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and means for, in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.

[0011] In some embodiments, a method is performed at an electronic device with a camera. The method includes: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.

[0012] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a camera. The one or more programs include instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.

[0013] In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a camera. The one or more programs include instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.

[0014] In some embodiments, an electronic device includes a camera, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.

[0015] In some embodiments, an electronic device includes: a camera; means for detecting activation of a shutter button that is associated with capturing still images; and means for, in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: means for capturing first image data with the camera focused at a first focal plane; and means for after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.

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

[0017] Thus, devices are provided with faster, more efficient methods and interfaces for capturing and displaying images with multiple focal planes, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for capturing and displaying images.

[0033] The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

[0034] There is a need for electronic devices that provide efficient methods and interfaces for capturing and displaying images with multiple focal planes. Such techniques can reduce the cognitive burden on a user who participates in live communication sessions or edits images, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.

[0035] Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of exemplary devices for performing the techniques for capturing and displaying images with multiple focal planes. FIGS. 6A-6H illustrate exemplary user interfaces for displaying video for a live communication session with multiple focal planes. FIGS. 7A-7B are a flow diagram illustrating methods of displaying the video for the live communication session in accordance with some embodiments. The user interfaces in FIGS. 6A-6H are used to illustrate the processes described below, including the processes in FIGS. 7A-7B. FIGS. 8A-8E illustrate exemplary user interfaces for capturing images with multiple focal planes. FIG. 9 is a flow diagram illustrating methods of capturing the images in accordance with some embodiments. The user interfaces in FIGS. 8A-8E are used to illustrate the processes described below, including the processes in FIG. 9.

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

[0037] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses 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,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0038] The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed 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.

[0039] 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 communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

[0040] In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, 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.

[0041] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout 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.

[0042] The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

[0043] Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), 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 control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs 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 over one or more communication buses or signal lines 103.

[0044] As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (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 of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath 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., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).

[0045] As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the 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 “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” 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 movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

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

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

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

[0049] RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

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

[0052] A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0053] Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

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

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

[0056] A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

[0057] A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

[0058] Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

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

[0060] Device 100 also includes power system 162 for powering 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, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

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

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

[0063] In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

[0064] Device 100 optionally also 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 165 optionally includes 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 165 receives 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 collocated with, or proximate to, a 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 touch screen display 112, which is located on the front of device 100.

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

[0066] Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

[0067] Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

[0068] In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

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

[0070] Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

[0071] Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

[0072] In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, 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 a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

[0073] Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position 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-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

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

[0075] 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, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

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

[0077] Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

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

[0079] Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

• • [0080] Contacts module 137 (sometimes called an address book or contact list);
  • [0081] Telephone module 138;
  • [0082] Video conference module 139;
  • [0083] E-mail client module 140;
  • [0084] Instant messaging (IM) module 141;
  • [0085] Workout support module 142;
  • [0086] Camera module 143 for still and/or video images;
  • [0087] Image management module 144;
  • [0088] Video player module;
  • [0089] Music player module;
  • [0090] Browser module 147;
  • [0091] Calendar module 148;
  • [0092] Widget modules 149, which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
  • [0093] Widget creator module 150 for making user-created widgets 149-6;
  • [0094] Search module 151;
  • [0095] Video and music player module 152, which merges video player module and music player module;
  • [0096] Notes module 153;
  • [0097] Map module 154; and/or
  • [0098] Online video module 155.

[0099] Examples of other applications 136 that are, 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 replication.

[0100] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.

[0101] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.

[0102] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

[0103] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

[0104] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0105] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.

[0106] In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

[0107] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

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

[0109] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

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

[0111] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

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

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

[0114] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

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

[0116] In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

[0117] Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

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

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

[0120] FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

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

[0122] 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 that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

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

[0124] In some embodiments, event monitor 171 sends requests to the 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 more than a predetermined duration).

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

[0126] Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

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

[0128] 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 a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

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

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

[0132] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of 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 properties. In some embodiments, a respective 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 the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

[0133] A respective 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 event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).

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

[0135] Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

[0137] In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

[0138] When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

[0139] In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

[0140] In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

[0141] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

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

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

[0144] It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

[0145] FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others 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 in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0147] In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

[0148] FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with 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 industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, 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, acceleration, proximity, touch-sensitive, 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 remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, 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, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0149] Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0150] Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.

[0151] FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

• • [0152] Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
  • [0153] Time 404;
  • [0154] Bluetooth indicator 405;
  • [0155] Battery status indicator 406;
  • [0156] Tray 408 with icons for frequently used applications, such as:
    • [0157] Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
    • [0158] Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
    • [0159] Icon 420 for browser module 147, labeled “Browser;” and
    • [0160] Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
  • [0161] Icons for other applications, such as:
    • [0162] Icon 424 for IM module 141, labeled “Messages;”
    • [0163] Icon 426 for calendar module 148, labeled “Calendar;”
    • [0164] Icon 428 for image management module 144, labeled “Photos;”
    • [0165] Icon 430 for camera module 143, labeled “Camera;”
    • [0166] Icon 432 for online video module 155, labeled “Online Video;”
    • [0167] Icon 434 for stocks widget 149-2, labeled “Stocks;”
    • [0168] Icon 436 for map module 154, labeled “Maps;”
    • [0169] Icon 438 for weather widget 149-1, labeled “Weather;”
    • [0170] Icon 440 for alarm clock widget 149-4, labeled “Clock;”
    • [0171] Icon 442 for workout support module 142, labeled “Workout Support;”
    • [0172] Icon 444 for notes module 153, labeled “Notes;” and
    • [0173] Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.

[0174] It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

[0175] FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

[0176] Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

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

[0178] FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.

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

[0180] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.

[0181] FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 is, optionally, a button, in some examples.

[0182] Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

[0183] Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 and 900 (FIGS. 7A-7B and 9). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

[0184] As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

[0185] As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an 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 in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a 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 in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

[0186] As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. 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 operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.

[0187] FIG. 5C illustrates detecting a plurality of contacts 552A-552E on touch-sensitive display screen 504 with a plurality of intensity sensors 524A-524D. FIG. 5C additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors 524A-524D relative to units of intensity. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 units of intensity, and the intensity measurements of intensity sensors 524B and 524C are each 7 units of intensity. In some implementations, an aggregate intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. 5D illustrates assigning the aggregate intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E are assigned an intensity of contact of 8 intensity units of the aggregate intensity, and each of contacts 552C and 552D are assigned an intensity of contact of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the aggregate intensity, A, in accordance with a predefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is the distance of the respective contact j to the center of force, and ΣDi is the sum of the distances of all the respective contacts (e.g., i=1 to last) to the center of force. The operations described with reference to FIGS. 5C-5D can be performed using an electronic device similar or identical to device 100, 300, or 500. In some embodiments, a characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity diagrams are not part of a displayed user interface, but are included in FIGS. 5C-5D to aid the reader.

[0188] In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

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

[0190] An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

[0191] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).

[0192] FIGS. 5E-5H illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact 562 from an intensity below a light press intensity threshold (e.g., “IT_L”) in FIG. 5E, to an intensity above a deep press intensity threshold (e.g., “IT_D”) in FIG. 5H. The gesture performed with contact 562 is detected on touch-sensitive surface 560 while cursor 576 is displayed over application icon 572B corresponding to App 2, on a displayed user interface 570 that includes application icons 572A-572D displayed in predefined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. The intensity sensors detect the intensity of contacts on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaked above the deep press intensity threshold (e.g., “IT_D”). Contact 562 is maintained on touch-sensitive surface 560. In response to the detection of the gesture, and in accordance with contact 562 having an intensity that goes above the deep press intensity threshold (e.g., “IT_D”) during the gesture, reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents for App 2 are displayed, as shown in FIGS. 5F-5H. In some embodiments, the intensity, which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact. It should be noted that the intensity diagram for contact 562 is not part of a displayed user interface, but is included in FIGS. 5E-5H to aid the reader.

[0193] In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in FIG. 5F. As the animation proceeds, representation 578A moves upward and representation 578B is displayed in proximity of application icon 572B, as shown in FIG. 5G. Then, representations 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed in proximity of application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses in accordance with an intensity of contact 562, as shown in FIGS. 5F-5G, where the representations 578A-578C appear and move upwards as the intensity of contact 562 increases toward the deep press intensity threshold (e.g., “IT_D”). In some embodiments, the intensity, on which the progress of the animation is based, is the characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using an electronic device similar or identical to device 100, 300, or 500.

[0194] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).

[0195] For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.

[0196] Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0197] FIGS. 6A-6H illustrate exemplary user interfaces displaying video for a live communication session with multiple focal planes, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 7A-7B.

[0198] FIG. 6A illustrates a first device 600a with first touch-sensitive display 602a. In some embodiments, first device 600a includes one or more features of devices 100, 300, and 500. First device 600a also includes first camera 603a, which, at a minimum, includes an image sensor that is capable of capturing data representing a portion of the light spectrum (e.g., visible light, infrared light, or ultraviolet light). First camera 603a includes at least one focal lens capable of being adjusted to focus first camera 603a on different focal planes (e.g., distances from first camera 603a at which the sharpest focus is attained). In some embodiments, first camera 603a includes a single focal lens for adjusting the focal plane. In some embodiments, the focal plane is adjusted by modifying the shape of the single focal lens. First camera 603a is capable of being adjusted to focus on different focal planes and capture images at different focal planes within a brief amount of time (e.g., less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20 ms). The images are captured at each of the different focal planes at a speed such that the multiple images with different focal planes can be associated with a single frame of video (e.g., the images are captured within a time period less than the time period of a frame of video). The content of the images associated with a frame of video appears substantially the same except for the difference in focal planes between the images. In some embodiments, one or more photographic properties of first camera 603a other than the focal plane (e.g., exposure, zoom level, white balance, contrast, ISO value) are kept constant during the capture of the multiple images.

[0199] In some embodiments, first camera 603a includes multiple image sensors and/or other types of sensors. In addition to capturing data representing sensed light, in some embodiments, first camera 603a is capable of capturing other types of data, such as depth data. For example, in some embodiments, first camera 603a also captures depth data using techniques based on speckle, time-of-flight, parallax, or focus. Image data that first device 600a captures using first camera 603a includes data corresponding to a portion of the light spectrum for a scene within the field of view of the camera. Additionally, in some embodiments, the captured image data also includes depth data for the light data. In some other embodiments, the captured image data contains data sufficient to determine or generate depth data for the data for the portion of the light spectrum.

[0200] In some examples, first device 600a includes a depth camera (e.g., as part of first camera 603a), such as an infrared camera, a thermographic camera, or a combination thereof. In some examples, first device 600a further includes a light-emitting device (e.g., light projector), such as an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the subject during capture of the image by a visible light camera and a depth camera (e.g., an IR camera) and the information from the depth camera and the visible light camera are used to determine a depth map of different portions of a subject captured by the visible light camera. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint.) In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

[0201] As illustrated in FIG. 6A, first device 600a displays outgoing notification 604 of a live communication application (e.g., a video chat application). The outgoing notification 604 is displayed in response to sending a request to a second device (e.g., second device 600b described in reference to FIG. 6B) to join a live communication session (e.g., a video chat). Outgoing notification 604 includes cancel affordance 606 for canceling the request to join the live communication session (e.g., to immediately end the live communication session). In some embodiments, outgoing notification 604 also includes a name 608 of a second participant being requested to join the live communication session and/or an avatar 610 for the second participant. Outgoing notification 604 also includes an image 612 (e.g., a frame of video) of the first participant sending the request (e.g., a user of first device 600a) (e.g., as a preview of video being sent to second device 600b, as described in reference to FIG. 6B). Image 612 is captured via first camera 603a and corresponds to an environment within the field-of-view of first camera 603a. In this example, the environment within the field-of-view of first camera 603a includes the first participant sending the request.

[0202] In some embodiments, first device 600a captures image 612 such that the first participant appears out-of-focus (as illustrated by the dashed lines shown in FIG. 6A). In some embodiments, first device 600a identifies a first focal region where a predefined portion of the first participant (e.g., the first participant's face) would be captured with a sharp focus, and sets a focal plane of first camera 603a to be outside of that first focal region (e.g., the focal plane of first camera 603a is set such that the first participant's face is captured out-of-focus). In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to be outside of the first focal region (e.g., the first participant's face is captured out-of-focus in at least one of the images). In some embodiments, one or more of the images captured by first camera 603a are transmitted to the second device with the request to join the live communication session.

[0203] FIG. 6B illustrates a second device 600b with second touch-sensitive display 602b. In some embodiments, second device 600b includes one or more features of devices 100, 300, 500, and 600a. In some embodiments, second device 600b also includes second camera 603b. In some embodiments, second camera 603b includes one or more features of first camera 600a (e.g., at least one focal lens capable of being adjusted to focus second camera 603b on different focal planes).

[0204] As illustrated in FIG. 6B, second device 600b displays incoming notification 614 of a live communication application (e.g., a video chat application, such as a video chat application that is the same as, or compatible with, the video chat application generating notification outgoing notification 604 on device 600a). Incoming notification 614 is displayed in response to receiving a request to join a live communication session (e.g., a video chat) from first device 600a. Incoming notification 614 includes answer affordance 616 for joining the live communication session (e.g., to immediately join the live communication session or display a menu with options for joining the live communication session). In some embodiments, incoming notification 614 also includes a name 618 of the first participant sending the request and/or an avatar 620 for the first participant. Incoming notification 614 also includes an image 622 (e.g., a frame of video) of the first participant (e.g., the user of first device 600a).

[0205] While the request to join the live communication session is pending (e.g., before answer affordance 616 is selected), image 622 is displayed such that the first participant sending the request appears out-of-focus (e.g., blurry). In some embodiments, the first participant is displayed out-of-focus as a result of first device 600a setting the focal plane of first camera 603a to a focal region where the first participant is out-of-focus. In some embodiments, the participant is displayed out-of-focus as a result of second device 600b sending a request to first device 600a to set the focal plane of first camera 603a to a focal region where the first participant is out-of-focus. In some embodiments, the video data being sent by first device 600a to second device 600b includes image data of the first participant at multiple focal planes. Second device 600b then selects image data with a focal plane where the first participant is out-of-focus for display as image 622 in the incoming notification 614.

[0206] As illustrated in FIG. 6C, while the request to join the live communication session continues to be pending, image 622 is displayed by second device 600b such that the first participant continues to appear out-of-focus after the distance of the first participant from first camera 600a changes (e.g., the first participant moves closer to or further away from first camera 600a capturing image 622). In some embodiments, as first device 600a detects that the distance of the first participant from first camera 600a is changing, first device 600a modifies the focal plane of first camera 603a such that the first participant remains out-of-focus. In some embodiments, second device 600b detects that the distance of the first participant from the first camera 603a is changing, and sends a request to first device 600a to modify the focal plane of first camera 603a to keep the first participant out-of-focus. In some embodiments, the video data being sent by first device 600a to second device 600b includes image data of the first participant at multiple focal planes. Second device 600b then selects image data with a focal plane where the first participant is out-of-focus for display as the participant moves closer to or further away from first camera 603a.

[0207] In some embodiments, the live communication session is accepted in response to an input 617 (e.g., a contact on second touch-sensitive display 602b) on answer affordance 616. In response to second device 600b accepting the request to join the live communication session, image 622 changes to display the first participant in-focus (e.g., the first participant's face appears sharp), as shown in FIG. 6D.

[0208] FIG. 6D illustrates second device 600b displaying live communication interface 624 on second touch-sensitive display 602b. Live communication interface 624 is displayed in response to an acceptance (e.g., input 617) of the request to join the live communication session sent by first device 600a. In response to second device 600b joining the live communication session, image 622 changes to display the first participant in-focus (e.g., the first participant's face appears sharp, as illustrated by the solid lines in FIG. 6D). Live communication interface 624 further includes a preview image 626 of the second participant.

[0209] In some embodiments, in response to second device 600b accepting the request to join the live communication session, first device 600a sets the focal plane of first camera 603a such that the first participant is captured in-focus. In some embodiments, first device 600a sets the focal plane in response to a request from second device 600b. Video data with the first participant captured in-focus is then transmitted to second device 600b for display as image 622 in live communication interface 624. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624.

[0210] As illustrated in FIG. 6E, after the request to join the live communication session has been accepted, image 622 is displayed by second device 600b such that the first participant continues to appear in-focus after the distance of the first participant from first camera 600a changes (e.g., the first participant moves closer or further away from first camera 600a capturing image 622). In some embodiments, as first device 600a detects that the distance of the first participant from first camera 600a is changing, first device 600a modifies the focal plane of first camera 603a such that the first participant remains in-focus. In some embodiments, second device 600b detects that the distance of the first participant from the first camera 603a is changing, and sends a request to first device 600a to modify the focal plane of first camera 603a to keep the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus at the changed distance from first camera 603a. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus at the changed distance from first camera 603a for display in the live communication interface 624.

[0211] As illustrated in FIG. 6F, after the request to join the live communication session has been accepted, the first participant partially exits the frame of first camera 603a (as shown in FIG. 6A). When the first participant partially exits the camera frame (e.g., at least a portion of the first participant's face is out of view of first camera 603a), a lack of attention is detected. In response to detecting the lack of attention, image 622 is displayed by second device 600b such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant out-of-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant out-of-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured out-of-focus for display in the live communication interface 624 when the lack of attention is detected.

[0212] When the first participant returns to the camera frame (e.g., the first participant's face is fully in view of first camera 603a), a return of attention is detected. In response to the return of attention, image 622 is displayed by second device 600b such that the first participant appears in-focus again, as shown in FIG. 6D. In some embodiments, the return of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears in-focus. In some embodiments, the return of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624 when the return of attention is detected.

[0213] As illustrated in FIG. 6G, after the request to join the live communication session has been accepted, the first participant looks away from first device 600a (as shown in FIG. 6A) (e.g., the first participant turns their head away from first device 600a or the first participant's eyes gaze in a direction other than toward first device 600a). When the first participant looks away from first device 600a, a lack of attention is detected. In response to detecting the lack of attention, image 622 is displayed by second device 600b such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant out-of-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant out-of-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured out-of-focus for display in the live communication interface 624 when the lack of attention is detected.

[0214] When the first participant looks back toward first device 600a (e.g., the first participant turns their head toward first device 600a or the first participant's eyes gaze in a direction toward first device 600a), a return of attention is detected. In response to the return of attention, image 622 is displayed by second device 600b such that the first participant appears in-focus again, as shown in FIG. 6D. In some embodiments, the return of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears in-focus. In some embodiments, the return of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624 when the return of attention is detected.

[0215] As illustrated in FIG. 6H, in response to an input 628 (e.g., a contact on second touch-sensitive display 602b), the focal plane of image 622 is modified. In some embodiments, in response to input 628, non-visual feedback (e.g., audio/tactile) is provided in conjunction with (e.g., at the same time or near the same time as) modifying the focal plane of image 622.

[0216] In some embodiments, the focal plane of image 622 is modified in response to input 628 being on a location of image 622 having a different depth (e.g., the location of an object in the background of image 622). In response to input 628, second device 600b displays image 622 such that a portion of the image at the location selected with input 628 is displayed in-focus (e.g., the focal plane is changed to correspond to the background object). In some examples, as a result of changing the focal plane, first participant is displayed out-of-focus in image 622. In some embodiments, second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the portion of the image at the location selected with input 628 in-focus. In some embodiments, first device 600a captures multiple images with different focal planes. The multiple images are transmitted to second device 600b, and second device 600b selects image 622 where the portion of the image at the location selected with input 628 is captured in-focus for display in the live communication interface 624.

[0217] In some embodiments, the focal plane of image 622 is modified based on a characteristic intensity of input 628 (e.g., a contact on second touch-sensitive display 602b having a characteristic intensity). For example, an input 628 having a characteristic intensity at or below the light press intensity threshold changes the focal plane of image 622 to correspond to a minimum focal plane of first camera 603a (e.g., a shallow focal plane where objects near first camera 603a are displayed in-focus). As the characteristic intensity of input 628 increases, the focal plane of image 622 is changed to correspond to deeper focal planes of first camera 603a (e.g., the focal planes shift further away from first camera 603a as the characteristic intensity of input 628 increases). In this way, a user can vary the focal plane of image 622 by changing the characteristic intensity of input 628.

[0218] In some embodiments, the focal plane of image 622 is modified based on a duration of input 628 (e.g., the length of time a contact is held on second touch-sensitive display 602b). For example, when input 628 is initially detected on second touch-sensitive display 602b, the focal plane of image 622 is changed to correspond to a minimum focal plane of first camera 603a (e.g., a shallow focal plane where objects near first camera 603a are displayed in-focus). As the duration of input 628 increases, the focal plane of image 622 is changed to correspond to deeper focal planes of first camera 603a (e.g., the focal planes gradually shift further away from first camera 603a as the duration of the contact increases). When input 628 ceases to be detected, the focal plane of image 622 is maintained at the last focal plane displayed for image 622. In this way, a user can vary the focal plane of image 622 by changing the duration of input 628.

[0219] FIGS. 7A-7B are a flow diagram illustrating a method for displaying video for a live communication session with different focal planes, in accordance with some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, 600b) with a display. Some operations in method 700 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

[0220] As described below, method 700 provides, among other things, an intuitive way for displaying video for a live communication session. The method reduces the cognitive burden on a user viewing the live communication session, thereby creating a more efficient human-machine interface.

[0221] The device (e.g., second device 600b) displays (702) video for a live communication session (e.g., an audio/video communication session with a live data stream transmitted by a capture device (e.g. first device 600a)). The video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region (e.g., a focal region where the head or face of a participant of the live communication session is in focus). In some embodiments, the video for the live communication session includes first image data corresponding to a focal plane outside of the first focal region and second image data corresponding to a focal plane inside the first focal region (e.g., video data stream from first device 600a includes data for multiple focal depths). In some embodiments, the first image data and second image data are transmitted/received at different periods of time in the video data, or at the same (e.g., approximately the same) period of time (e.g. the video data includes two discrete channels/streams of data for the same time period, having different focal planes). In some embodiments, the device (e.g., second device 600b) selects the image data with the focal plane outside the first focal region (e.g., to display the subject out-of-focus).

[0222] In accordance with a determination that a set of one or more conditions is met, the device displays (704) the video with a focal plane of the video selected to be outside of the first focal region (e.g., the head/face of a participant of the live communication session is out of focus in the video). In some embodiments, the video is captured by a capture device (e.g., first device 600a) with a lens set outside the first focal region. In some embodiments, the video includes video data at multiple focal depths and the device (e.g., second device 600b) selects the video data with a focal plane outside the first focal region for display. Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether one or more conditions are met improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session (e.g., whether the live communication session has been joined and/or whether another participant is engaged in the live communication session). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0223] In some embodiments, the video for the live communication session is captured by a camera of a capture device (e.g., first device 600a with first camera 603a), and in accordance with the determination that the set of one or more conditions is met, the focal plane of the camera has been set (e.g. mechanically set/adjusted, set/adjusted via software) outside of the first focal region. In some embodiments, the device (e.g., second device 600b) sends a request to the capture device (e.g., first device 600a) to set the focal plane of the camera (e.g., first camera 603a) of the capture device outside of the first focal region.

[0224] Optionally, while (710) displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region and while the set of one or more conditions is met, the device (e.g., second device 600b) detects (712) a change in position of the predefined portion of the subject (e.g., the head/face of the participant moves forward or backward). The device then modifies (714) the first focal region based on the change in position of the predefined portion of the subject. The device then displays (716) the video for the live communication session with the focal plane of the video adjusted to continue being outside of the first focal region (e.g., the focal plane is changed to keep the head/face of the participant out-of-focus). Continually changing the focal plane for the live communication session to be outside of a focal region of the subject as the subject changes position improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session as the subject moves. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0225] While displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, the device determines (706) that the set of one or more conditions is no longer met.

[0226] In response to the determination that the set of one or more conditions is no longer met, the device displays (708) the video for the live communication session with the focal plane of the video selected to be inside of the first focal region (e.g., a focal region where the head/face of the participant of the live communication session is no longer out of focus in the video). In some embodiments, the video is captured by another device (e.g., first device 600a) with a camera lens set at a focal plane inside the first focal region. In some embodiments, the video includes video data at multiple focal depths and the device (e.g., second device 600b) selects the video data with a focal plane inside the first focal region for display.

[0227] Optionally, while (718) the set of one or more conditions is no longer met and while displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region, the device (e.g., second device 600b) detects (720) a change in position of the predefined portion of the subject (e.g., the head/face of the participant moves forward or backward). The device then modifies (722) the first focal region based on the change in position of the predefined portion of the subject. The device then displays (724) the video for the live communication session with the focal plane of the video adjusted to continue being inside the first focal region (e.g., the focal plane is changed to keep the head/face of the participant in-focus). Continually changing the focal plane for the live communication session to be inside of a focal region of the subject as the subject changes position improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session as the subject moves. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0228] In some embodiments, the device (e.g., second device 600b) receives a request to participate in the live communication session, and the set of one or more conditions includes a condition that is met while the request is pending (e.g., when receiving an incoming video call, video of the participant initiating the call is displayed with the participant's head/face out-of-focus). In some embodiments, the request is pending when the request remains unaccepted (e.g., the device receiving the request is not transmitting video back to the requesting device). In some embodiments, in response to detecting an acceptance (e.g., 617) of the request to participate in the live communication session (e.g., an input (e.g., a finger contact) on an acceptance affordance (e.g., 616) displayed on a touch-sensitive display), the device determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus until the live communication session is accepted, and then the subject is displayed in-focus). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether a request to join the live communication session is pending improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0229] In some embodiments, the set of one or more conditions includes a condition that is met when a lack of attention from the subject of the live communication session has been detected (e.g., subject of video call appears out-of-focus when they are not paying attention to the video call) (e.g. detected via face and/or gaze detection techniques that are, optionally, based on analysis of the video data (e.g., analysis performed at second device 600b, or analysis performed by first device 600a providing the video data along with attention detection data, to the second device 600b)). In some embodiments, the lack of attention is detected based at least in part on the predefined portion of the subject (e.g., the subject's head/face) at least partially exiting an image boundary of the live communication session (e.g., the camera frame of the capture device) for a predetermined amount of time. In some embodiments, in response to a detection that the predefined portion of the subject (e.g., the subject's head/face) reenters the image boundary of the live communication session (e.g., the camera frame of the capture device), the device determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus if their head/face partially moves out of the camera frame, and then the subject is displayed in-focus when their head/face returns to the camera frame). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether a lack of attention is detected improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Displaying video for the live communication session with the focal plane of the video selected to be at different focal regions based on whether a lack of attention is detected also improves privacy by obfuscating the identity and/or activities of a participant when they are not paying attention to the live communication session. Providing improved visual feedback and privacy to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Furthermore, user inputs are not required to change the focal plane of the video for the live communication, which allows the live communication session to quickly and easily continue when a return of attention is detected. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0230] In some embodiments, the lack of attention is detected based at least in part on an eye gaze of the subject being directed in a direction other than toward a capture device (e.g., first device 600a) capturing the live communication session for a predetermined amount of time (e.g., the subject is displayed out-of-focus while they look away from the first camera 603a). In some embodiments, the subject's head/face remains in the camera frame at the same focal plane while they look away from the capture device. In some embodiments, in response to a detection that the eye gaze of the subject is directed toward the capture device (e.g., first device 600a) capturing the live communication session, the device (e.g., second device 600b) determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus while they look away from first camera 603a, and then the subject is displayed in-focus when their gaze returns to first camera 603a). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on a participant's eye gaze improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Displaying video for the live communication session with the focal plane of the video selected to be at different focal regions based on a participant's eye gaze also improves privacy by obfuscating the identity and/or activities of a participant when they are not paying attention to the live communication session. Providing improved visual feedback and privacy to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Furthermore, user inputs are not required to change the focal plane of the video for the live communication, which allows the live communication session to quickly and easily continue when a return of attention is detected. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0231] Optionally, while displaying the video for the live communication session on a touch-sensitive display, the device (e.g., second device 600b) detects (726) an input (e.g., 628) (e.g., a finger contact) on the touch-sensitive display. The device then displays (728) the video for the live communication session with the focal plane of the video selected based on one or properties of the input (e.g., location, duration, and/or pressure of the finger contact).

[0232] In some embodiments, the device (e.g., second device 600b) sends a request to the capture device (e.g., first device 600a) to set the focal plane of the camera (e.g., first camera 603a) based on the one or more properties of the input (e.g., first device 600a is instructed to capture images having the desired focus, and to send video data including the images to second device 600b). In some embodiments, the video for the live communication session includes image data for two or more focal planes (e.g., video stream from the first device 600a includes data for multiple focal depths (e.g., for the same time period (e.g., providing two channels of video data, having different focal planes)), and the device (e.g., second device 600b) selects image data having a respective focal plane of the two or more focal planes for display based on the one or more properties of the input. In some embodiments, the one or more properties of the input includes a characteristic intensity of the input. In some embodiments, the one or more properties of the input includes a duration of the input (e.g., long press). In some embodiments, the one or more properties of the input includes a location of the input on the touch-sensitive display (e.g., if input location corresponds to a location of an object in the live communication session, focal plane changes to a focal region of the object). In some embodiments, the device (e.g., second device 600b) provides non-visual feedback (e.g., audio/tactile) in conjunction with (e.g., at the same time or near the same time as) the video for the live communication session is displayed with the focal plane of the video selected based on the one or properties of the input (e.g., non-visual feedback occurs when the focal plane of the video changes in response to the input).

[0233] Note that details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in an analogous manner to the methods described below. For example, method 700 optionally includes one or more of the characteristics of the various methods described below with reference to method 900. For example, a plurality of still images with a plurality of different focal planes as described below with respect to method 900 can used in a live communication session described above with respect to method 700. For brevity, these details are not repeated below.

[0234] FIGS. 8A-8E illustrate exemplary user interfaces for capturing images with multiple focal planes, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 9.

[0235] FIG. 8A illustrates a front-view 800a and a rear-view 800b of device 800 with touch-sensitive display 802. In some embodiments, device 800 includes one or more features of devices 100, 300, and 500. Device 800 also includes an input device 804 (e.g., a mechanical input button, a press-able input button) and a camera 808. Camera 808, at a minimum, includes an image sensor that is capable of capturing data representing a portion of the light spectrum (e.g., visible light, infrared light, or ultraviolet light). Camera 808 includes at least one focal lens capable of being adjusted to focus camera 808 on different focal planes (e.g., distances from camera 808 at which the sharpest focus is attained). In some embodiments, camera 808 includes a single focal lens for adjusting the focal plane. In some embodiments, the focal plane is adjusted by modifying the shape of the single focal lens. Camera 808 is capable of being adjusted to focus on different focal planes and capture images at each of the different focal planes within a brief amount of time (e.g., less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20 ms). The images are captured at each of the different focal planes at a speed such that the multiple images with different focal planes can be associated with approximately the same moment in time. The content of the images appear substantially the same except for the difference in focal planes between the images. In some embodiments, one or more photographic properties of camera 808 other than the focal plane (e.g., exposure, zoom level, white balance, contrast, ISO value) are kept constant during the capture of the multiple images.

[0236] In some embodiments, camera 808 includes multiple image sensors and/or other types of sensors. In addition to capturing data representing sensed light, in some embodiments, camera 808 is capable of capturing other types of data, such as depth data. For example, in some embodiments, camera 808 also captures depth data using techniques based on speckle, time-of-flight, parallax, or focus. Image data that device 800 captures using camera 808 includes data corresponding to a portion of the light spectrum for a scene within the field of view of the camera. Additionally, in some embodiments, the captured image data also includes depth data for the light data. In some other embodiments, the captured image data contains data sufficient to determine or generate depth data for the data for the portion of the light spectrum.

[0237] In some examples, device 800 includes a depth camera (e.g., as part of camera 808), such as an infrared camera, a thermographic camera, or a combination thereof. In some examples, camera 808 further includes a light-emitting device (e.g., light projector), such as an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the subject during capture of the image by a visible light camera and a depth camera (e.g., an IR camera) and the information from the depth camera and the visible light camera are used to determine a depth map of different portions of a subject captured by the visible light camera. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint.) In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

[0238] In FIG. 8A, electronic device 800 displays, on touch-sensitive display 802, a user interface 806 (e.g., a lock-screen user interface) that includes an affordance 812 for launching an image capture application (e.g., a camera application, an image/photo capturing and editing application). While displaying user interface 806, device 800 detects (e.g., via touch-sensitive display 802) an activation 801 of affordance 812 (e.g., a tap gesture on affordance 812).

[0239] In FIG. 8B, in response to detecting activation 801 (or in response to other image capture requests), device 800 displays, on touch-sensitive display 802, a user interface 814 of the image capture application. In this example, image capture application is in a photo mode. While displaying user interface 814 of the image capture application, device 800 receives, via camera 808, image data corresponding to the environment within the field-of-view of camera 808.

[0240] Device 800 displays a preview image 818 corresponding to the image data received via camera 808 in the user interface 814 of the image capture application. In this example, preview image 818 includes multiple objects, including a foreground object 820a (e.g., a dog), a middleground object (e.g., a person), and a background object 820c (e.g., a plant). As illustrated in FIG. 8B, the focal plane of camera 808 is set such that middlegound object 820b and background object 820c are displayed out-of-focus (as illustrated by dashed lines) while foreground object 820a is displayed in-focus (as illustrated by solid lines) in preview image 818.

[0241] User interface 814 of the image capture application also includes a shutter affordance 822 (e.g., a virtual shutter button). While displaying preview image 818 in user interface 814, device 800 detects an activation 805 of shutter affordance 822 (e.g., a single tap gesture on shutter affordance 822). In response to detecting activation 805, device 800 captures multiple still images corresponding to the environment currently in the field-of-view of camera 808 (e.g., multiple still images of objects 820a-820c included in preview image 818). The still images are captured with multiple different focal planes in response to the activation 805. The multiple different focal planes are selected without reference to changes in objects in the field of view of the camera during the capture of the multiple still images (e.g., the different focal planes are predefined or are selected at the same time and do not change based on movement of the camera or movement of objects toward or away from the camera during the capture of the multiple still images).

[0242] In some embodiments, the multiple still images are captured in response to an activation of input device 804 (e.g., a single press of a physical input button). In some embodiments, after capturing the multiple still images with multiple different focal planes, the preview image 818 continues to be displayed. In some embodiments, after capturing the multiple still images with multiple different focal planes, one of the captured still images corresponding to the preview image 818 is displayed (e.g., image 826 shown in FIG. 8D).

[0243] In some embodiments, device 800 detects an input 807 (e.g., a contact on touch-sensitive display 802) at a location in preview image 818 corresponding to middleground object 820b. In response to detecting input 807, device 800 captures multiple still images with different focal planes and then displays one of the captured still images (e.g., image 824 shown in FIG. 8C) having a focal plane corresponding to middleground object 820b, as shown in FIG. 8C (e.g., tapping on an object in the preview image 818 causes multiple images with different focal planes to be captured, and an image with that object in-focus to be displayed).

[0244] As illustrated in FIG. 8C, image 824 is displayed in user interface 814. Image 824 includes middleground object 820b displayed in-focus, and foreground object 820a and background object 820c displayed out-of-focus. Image 824 is displayed in response to input 807 on the location in preview image 818 corresponding to middleground object 820b, as described in reference to FIG. 8B. While displaying image 824, device 800 detects input 809. In some embodiments, input 809 is at a location in image 824 corresponding to foreground object 820a. In response to input 809 at the location corresponding to foreground object 820a, device 800 displays an image (e.g., image 826 shown in FIG. 8C) having a focal plane corresponding to foreground object 820a, as shown in FIG. 8C (e.g., tapping on an object in image 824 causes an image to be displayed with that object in-focus, without capturing additional images).

[0245] In some embodiments, input 809 has a corresponding characteristic intensity. Based on the characteristic intensity of input 809, device 800 displays an image (e.g., image 826 shown in FIG. 8C) having a different focal plane (e.g., a light press causes an image with a shallow focal plane to be displayed, while a deep press causes an image with a deep focal plane to be displayed, without capturing additional images). In some embodiments, device 800 maintains display of image 824 unless input 809 has a corresponding characteristic intensity greater than a threshold intensity. In some embodiments, the threshold intensity is based at least in part on a focal plane of an object captured in the multiple still images (e.g., the characteristic intensity of input 809 pushes the focal plane deeper into image 824 until the focal plane is at a depth corresponding to an object in the image). When the characteristic intensity of input 809 is greater than the threshold intensity, device 800 provides feedback indicating the threshold intensity has been exceeded (e.g., audio/tactile/visual feedback occurs when focal plane is pushed to a depth corresponding to an object in the image).

[0246] In some embodiments, input 809 has a corresponding duration (e.g., a long or short press). Based on the duration of input 809, device 800 displays an image (e.g., image 826 shown in FIG. 8C) having a different focal plane (e.g., a short press causes an image with a shallow focal plane to be displayed, while a long press causes an image with a deep focal plane to be displayed, without capturing additional images).

[0247] As illustrated in FIG. 8D, image 826 is displayed in user interface 814. Image 826 includes foreground object 820a displayed in-focus, and middleground object 820b and background object 820c displayed out-of-focus. Image 826 is displayed in response to input 809, as described in reference to FIG. 8C. In some embodiments, image 826 is displayed in response to activation 805 of shutter affordance 822 or activation of input device 804, as described in reference to FIG. 8B.

[0248] Image 826 is one of the multiple still images captured as described in reference to FIG. 8B. While displaying image 826, device 800 detects input 811 at a location in image 826 corresponding to background object 820c. In response to input 811, device 800 displays an image (e.g., image 828 shown in FIG. 8E) with background object 820c displayed in-focus while foreground object 820a continues to be displayed in-focus, as shown in FIG. 8E (e.g., tapping on another object in the image causes an image to be displayed with that object in-focus and the previously selected object also in-focus, without capturing additional images).

[0249] As illustrated in FIG. 8E, image 828 is displayed in user interface 814. Image 828 includes foreground object 820a and background object 820c displayed in-focus, and middleground object 820b displayed out-of-focus. Image 828 is displayed in response to input 811 on the location in image 824 corresponding to background object 820c, as described in reference to FIG. 8C. Input 811 is detected after another input 809 selected foreground object 820a to be displayed in-focus. Image 828 is a composite of a first image captured with foreground object 820a in-focus and a second image captured with background object 820c in-focus. Both the first image and second image were captured in response to input 807 described in reference to FIG. 8B. The composite image 828 includes at least the foreground object 820a from the first image and the background object 820c from the second image. Other portions of the composite image 828 (e.g., middleground object 820b) can be from the first image, the second image, or from other captured still images, such that the other portions of image 828 are displayed out-of-focus.

[0250] In some embodiments, device 800 receives a request to display an animation including two or more of the captured still images. For example, the animation includes displaying a first image (e.g., image 824 shown in FIG. 8C) with a first focal plane for a predetermined amount of time, followed by a second image (e.g., image 826 shown in FIG. 8D) with a different focal plane for a predetermined amount of time. In some embodiments, the animation continues indefinitely, cycling between the first image and the second image, until a cancellation input is received. In some embodiments, the animation continues cycling between the first image and the second image as long as an input is maintained (e.g., as long as contact is detected on the touch-sensitive display).

[0251] In some embodiments, device 800 determines depth information of the scene being captured in the multiple still images based on image data of the still images. For example, device identifies objects in the scene, and based on the focal planes of the objects, determines the depth of the object in the scene. In some embodiments, an operation is performed on at least one of the still images using the depth information, such as applying a simulated depth effect (e.g., a visual effect having a depth component), inserting an object into the scene, making a measurement, etc. In some embodiments, applying the simulated depth effect includes adjusting areas of the image that correspond to a selected depth to have different degrees of blurriness/sharpness, sizes, degrees of brightness, degrees of saturation, and/or degrees of shape-distortion in order to simulate the depth effect, such as a bokeh effect. In some embodiments, the simulated depth effect is “simulated” in that the effect is (artificially) generated based on a manipulation of the underlying image data for the area of the image to create and apply the effect to the image (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).

[0252] FIG. 9 is a flow diagram illustrating a method for displaying capturing a plurality of still images with a plurality of different focal planes, in accordance with some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500, 800) with a camera (e.g., 808). In some embodiments, the camera includes a single lens for adjusting the focal length of the camera. In some embodiments, the focal length changes by modifying the shape of the lens. Some operations in method 900 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

[0253] As described below, method 900 provides, among other things, an intuitive way for capturing images of an environment with different focal planes. The method reduces the cognitive burden on a user capturing an image of the environment, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to capture images with different focal planes faster and more efficiently conserves power and increases the time between battery charges.

[0254] The device (e.g., 800) detects (902) activation (e.g., 805, 807) of a shutter button (e.g., 804, 822, preview image 818) (e.g., a physical or virtual shutter button) that is associated with capturing still images.

[0255] In response to the activation of the shutter button, the device captures (904) a plurality of still images with a plurality of different focal planes. In some embodiments, at least one photographic property of the camera (e.g., exposure, zoom level, white balance, contrast, ISO value) other than the focal plane is maintained during the capture of the plurality of still images.

[0256] Capturing the plurality of still images includes capturing (906) first image data with the camera focused at a first focal plane (e.g., the image is captured with a lens of the camera set at a first focal length).

[0257] After capturing the first image data with the camera focused at the first focal plane, the device captures (908) second image data with the camera focused at a second focal plane. The second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data (e.g., the first focal plane and the second focal plane are predefined or are selected at the same time in response to the activation of the shutter button and do not change based on movement of the camera or movement of objects toward or away from the camera between the capture of the first image data and the capture of the second image data). In some embodiments, the lens is changed to the second focal plane by modifying the shape of the lens. In some embodiments, the second image data is captured at a second time, later than a first time at which the first image data is captured. In some embodiments, the first image data and the second image data are consolidated into a single data file. Capturing a plurality of still images with a plurality of different focal planes in response to a single activation of a shutter button allows the still images to be captured more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0258] In some embodiments, detecting the activation of the shutter button includes detecting an input (e.g., 807) on a touch-sensitive display. In response to detecting the input, the device selects a respective image of the plurality of still images based on one or more properties of the input and displays the respective image of the plurality of still images (e.g., a single finger contact triggers capture of the plurality of still images and selects the focal plane for an image to be displayed). In some embodiments, the one or properties of the input include a characteristic intensity of the input. In some embodiments, the one or more properties of the input (e.g., 807) includes a location (e.g., on middleground object 820b) of the input on the touch-sensitive display. In some embodiments, if the input location corresponds to a location of an object being captured in the plurality of still images (e.g., on middleground object 820b), the focal plane of the image being displayed corresponds to the focal plane of the object). Capturing a plurality of still images with a plurality of different focal planes and then displaying one of the still images in response to a single input allows the still images to be captured and displayed more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0259] Optionally, after capturing the plurality of still images, the device displays (910) on a touch-sensitive display (e.g., 802), a first image (e.g., 824) of the plurality of still images corresponding to the first image data. The device then detects (912) a first input (e.g., 809) (e.g., a finger contact) at a location (e.g., 820a) on the touch-sensitive display corresponding to the first image. In response to the first input, the device displays (914) a second image (e.g., 826) of the plurality of still images corresponding to the second image data. Selecting a second image with a different focal plane for display based on a single input on a touch-sensitive display allows the second image to be displayed more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

[0260] In some embodiments, displaying the second image (e.g., 826) includes selecting the second image from the plurality of still images based on one or properties of the first input, the one or more properties including a characteristic intensity of the first input. In some embodiments, in accordance with a determination that the characteristic intensity of the first input is greater than a threshold intensity, the device maintains display of the second image after the first input ceases to be detected by the device, and in accordance with a determination that the characteristic intensity of the first input is less than the threshold intensity, the device displays the first image after the first input ceases to be detected by the device. In some embodiments, the threshold intensity is based at least in part on a focal plane of an object being captured in the plurality of still images (e.g., the characteristic intensity of input 809 pushes the focal plane deeper into image 824 until the focal plane is at a depth corresponding to an object in the image). In some embodiments, after changing to the focal plane of the object, focus is maintained on the object for subsequent activations of the shutter button. In some embodiments, in accordance with the determination that the characteristic intensity of the first input is greater than the threshold intensity, the device provides feedback indicating the threshold intensity is exceeded (e.g., audio/tactile/visual feedback occurs when the characteristic intensity of the first input exceeds the threshold).

[0261] In some embodiments, the one or properties of the first input include a duration of the input (e.g., long press, short press).

[0262] In some embodiments, the one or more properties of the first input includes the location (e.g., on foreground object 820a) of the first input on the touch-sensitive display. The device identifies an object in the first image corresponding to the location of the first input, where the object is associated with a respective focal plane. The device then displays an image (e.g., 826) of the plurality of still images captured with the respective focal plane (e.g., when the input location corresponds to a location of an object being captured in the plurality of still images, the focal plane changes to the respective focal plane of the object). In some embodiments, after the object is selected with the first input, focus is maintained on the object for subsequent activations of the shutter button.

[0263] In some embodiments, while displaying the second image (e.g., 826) of the plurality of still images, the device detects a second input (e.g., 811) (e.g., a finger contact) at a location (e.g., on background object 820c) on the touch-sensitive display corresponding to the second image. In response to the second input, the device displays a composite image (e.g., 828) on the touch-sensitive display. The composite image includes a portion of the second image associated with the first input (e.g., a portion of the image selected to be displayed in focus by the first input) and a portion of the second image associated with the second input (e.g., a portion of the image selected to be displayed in focus by the second input, such that multiple planes (e.g., foreground and background) are displayed in-focus, while other planes (e.g., a middleground) are displayed out-of-focus).

[0264] In some embodiments, after capturing the plurality of still images, the device receives a request (e.g., a single request, a single input) to display two or more images of the plurality of still images. In response to receiving the request, the device displays a first image of the plurality of still images and displays a second image of the plurality of still images a predetermined time after displaying the first image, where the first image and the second image were captured with different focal planes. In some embodiments, additional images having different focal depths are also displayed. In some embodiments, the sequence of images with different focal planes are automatically played through in a loop or back and forth (e.g., “boomerang”) animation. In some embodiments, the sequence of images is displayed in response to a user input, and continues to be displayed either while the user's input is maintained or until a cancellation input is received.

[0265] In some embodiments, the device determines depth information of a scene captured in the plurality of still images with the plurality of different focal planes. The depth information is determined based on image data of the plurality of still images. In some embodiments, an operation is performed on at least one of the plurality of still images using the depth information, such as applying a simulated depth effect (e.g., a visual effect having a depth component), inserting an object into the scene, making a measurement, etc. In some embodiments, applying the simulated depth effect includes adjusting areas of the image that correspond to a selected depth to have different degrees of blurriness/sharpness, sizes, degrees of brightness, degrees of saturation, and/or degrees of shape-distortion in order to simulate the depth effect, such as a bokeh effect. In some embodiments, the simulated depth effect is “simulated” in that the effect is (artificially) generated based on a manipulation of the underlying image data for the area of the image to create and apply the effect to the image (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).

[0266] Note that details of the processes described above with respect to method 900 (e.g., FIG. 9) are also applicable in an analogous manner to the methods described above. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, a plurality of still images with a plurality of different focal planes as described above with respect to method 900 can used in a live communication session described above with respect to method 700. For brevity, these details are not repeated below.

[0267] The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

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

[0269] As described above, one aspect of the present technology is the gathering and use of data available from various sources to change the focal plane of stored images or a live video communication. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0270] The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to can be used to recognize a person or subject within a captured image or video. Accordingly, use of such personal information data enables users to more easily recognize the content of a captured image or live video communication. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.

[0271] The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

[0272] Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of detection and recognition of a person or subject within an image or live video communication, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

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

[0274] Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, images or live video communications can be displayed based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the device, or publicly available information.