Media Capture Lock Affordance for Graphical User Interfaces

Abstract

To provide a graphical user interface of a media capture application.SOLUTION: The disclosed embodiments are directed to a media capture lock affordance of a graphical user interface displayed by a media capture device. The media capture lock affordance allows the user to lock and unlock the capturing state of the media capture device using simple and intuitive touch gestures that can be applied by the user's finger (e.g., the user's thumb) while holding the media capture device with one hand.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 62 / 628,825, entitled "Media Capture Lock Affordance for Graphical User Interface," filed February 9, 2018, U.S. Provisional Patent Application No. 15 / 995,040, entitled "Media Capture Lock Affordance for Graphical User Interface," filed May 31, 2018, and U.S. Provisional Patent Application No. 62 / 802,603, entitled "Media Capture Lock Affordance for Graphical User Interface," filed February 7, 2019, the contents of which are incorporated herein by reference in their entireties.

[0002] TECHNICAL FIELD This disclosure relates generally to graphical user interfaces for media capture applications. [Background technology]

[0003] Media capture devices (e.g., smartphones, tablet computers) include applications that allow users to record media clips (e.g., video clips, audio clips) using one or more built-in cameras and microphones. The user captures a media clip by pressing and holding a virtual record button. Once the user has recorded, the user can drag the media clip into a desired order with other media clips and add filters, emojis, animated icons, and titles. Media clips can be shared indirectly through social networks and / or sent directly to friends, for example, through an instant messaging application. Summary of the Invention

[0004] However, some techniques for performing media capture using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing techniques take longer than necessary, wasting the user's time and the device's energy. The latter consideration is particularly critical in battery-operated devices.

[0005] Thus, the present techniques provide electronic devices with faster, more efficient methods and interfaces for performing gesture-based media capture. Such methods and interfaces optionally complement or replace other methods for performing gesture-based media capture. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and extend the time between battery charges. Additionally, such methods and interfaces reduce the number of unnecessary or non-essential user inputs to perform media capture, thereby saving user time and device energy.

[0006] Disclosed embodiments are directed to a media capture lock affordance for a graphical user interface. In one embodiment, a method of capturing media includes detecting, by a media capture device, a tap-and-hold gesture input directed to a media capture affordance displayed at a first location on a graphical user interface presented on a display screen of the media capture device; initiating, by the media capture device, a media capture session on the media capture device in an unlocked state in response to the tap-and-hold gesture input; and in response to the media capture device detecting a first lift gesture in which the tap-and-hold gesture input lifts from the first location on the graphical user interface during the media capture session, and, in response to the media capture device detecting a slide gesture input during the media capture session in which the media capture affordance slides from a first location to a second location on the graphical user interface, changing, by the media capture device, the media capture affordance to a media capture lock affordance; and, in response to the media capture device detecting a second lift gesture during the media capture session in which the slide gesture input lifts from the graphical user interface at the second location, transitioning, by the media capture device, the media capture session to a locked state.

[0007] Other embodiments may include an apparatus, a computing device, and a non-transitory computer-readable storage medium.

[0008] According to some embodiments, a non-transitory computer-readable storage medium is described that stores instructions that, when executed by a media capture device, cause the media capture device to: detect, by the media capture device, a tap-and-hold gesture input targeted to a media capture affordance displayed at a first location on a graphical user interface presented on a display screen of the media capture device; in response to the tap-and-hold gesture input, initiate, by the media capture device, a media capture session on the media capture device in an unlocked media session capture state; and, when the media capture device detects a first lift gesture during the media capture session, the tap-and-hold gesture input lifts the media capture affordance from the first location on the graphical user interface. in response to the media capture device detecting a slide gesture input in which the media capture affordance slides from a first location to a second location on the graphical user interface during the media capture session, changing, by the media capture device, the media capture affordance to a media capture lock affordance; and in response to the media capture device detecting a second lift gesture in which the slide gesture input lifts from the graphical user interface at the second location during the media capture session, transitioning, by the media capture device, the media capture session to a locked media capture session state.

[0009] According to some embodiments, a non-transitory computer-readable storage medium is described that stores instructions that, when executed by a media capture device, cause the media capture device to detect a tap-and-hold gesture input directed to a media capture affordance displayed at a first location on a graphical user interface presented on a display screen of the media capture device, and in response to the tap-and-hold gesture input, initiate, by the media capture device, a media capture session on the media capture device in an unlocked media session capture state, and in response to the media capture device detecting a first lift gesture in which the tap-and-hold gesture input lifts the media capture affordance from the first location on the graphical user interface during the media capture session, and causing the media capture device to perform operations including: ending the media capture session; changing, by the media capture device, the media capture affordance to a media capture lock affordance in response to the media capture device detecting a slide gesture input in which the media capture affordance slides from a first location to a second location on the graphical user interface during the media capture session; and transitioning, by the media capture device, the media capture session to a locked media capture session state in response to the media capture device detecting a second lift gesture in which the slide gesture input lifts from the graphical user interface at the second location during the media capture session.

[0010] According to some embodiments, a media capture device is described that includes a touchscreen, one or more processors, and a memory coupled to the one or more processors and configured to store instructions that, when executed by the one or more processors, cause the one or more processors to: detect, by the touchscreen, a tap-and-hold gesture input targeted to a media capture affordance displayed at a first location on a graphical user interface presented on the touchscreen of the media capture device; in response to the tap-and-hold gesture input, initiate a media capture session on the media capture device in an unlocked media capture session state; and, during the media capture session, trigger the tap-and-hold gesture input to activate the graphical user interface. In response to the touch screen detecting a first lift gesture input in which the media capture affordance is lifted from a first location on the graphical user interface, terminating the media capture session; in response to the touch screen detecting a slide gesture input in which the media capture affordance is slid from a first location to a second location on the graphical user interface during the media capture session, changing the media capture affordance to a media capture lock affordance; and in response to the touch screen detecting a second lift gesture input in which the slide gesture input is lifted from the graphical user interface at the second location during the media capture session, transitioning the media capture session to a locked media capture session state.

[0011] According to some embodiments, an electronic device is described. The electronic device comprises a display screen; means for detecting a tap and hold gesture input targeted at a media capture affordance displayed at a first location on a graphical user interface presented on the display screen of the media capture device; means for initiating a media capture session on the media capture device in an unlocked media capture session state in response to the tap and hold gesture input; means for terminating the media capture session in response to the media capture device detecting a first lift gesture in which the tap and hold gesture input lifts the media capture affordance from the first location on the graphical user interface during the media capture session; means for changing the media capture affordance to a media capture lock affordance in response to the media capture device detecting a slide gesture input in which the media capture affordance slides from the first location to a second location on the graphical user interface during the media capture session; and means for transitioning the media capture session to a locked media capture session state in response to the media capture device detecting a second lift gesture in which the slide gesture input lifts the media capture affordance from the graphical user interface at the second location during the media capture session.

[0012] Certain embodiments disclosed herein may provide one or more of the following advantages: A media capture lock affordance allows a user to lock and unlock the capture state of a media capture device using simple and intuitive touch gestures that can be applied by the user's fingers (e.g., the user's thumb) while holding the media capture device in one hand.

[0013] The details of one or more implementations of the subject matter are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, drawings, and claims.

[0014] According to some embodiments, a method is described in a device having a display, a touch-sensitive surface, and one or more media capture components, the method including: displaying a first user interface element on the display; detecting a touch input via the touch-sensitive surface starting at a location on the touch-sensitive surface corresponding to the first user interface element; in response to detecting the touch input, capturing a first type of media in accordance with a determination that the touch input was lifted from the touch-sensitive surface before satisfying a movement criterion and before a threshold time has elapsed since the touch input was detected; capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input meets the movement criterion and includes movement in a first direction, and continuing to capture the second type of media after detecting liftoff of the touch input from the touch-sensitive surface.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. 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 having a display, a touch-sensitive surface, and one or more media capture components, the one or more programs including instructions for displaying a first user interface on the display; instructions for detecting touch input via the touch-sensitive surface beginning at a location on the touch-sensitive surface corresponding to a first user interface element; instructions for capturing a first type of media in response to detecting the touch input in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input satisfies a movement criterion and before a threshold time has elapsed since the touch input was detected; instructions for capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input satisfies the movement criterion and includes movement in a first direction, and instructions for continuing to capture the second type of media after detecting liftoff of the touch input from the touch-sensitive surface.

[0016] According to some embodiments, a temporary computer-readable storage medium is described. A temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, and one or more media capture components, the one or more programs including instructions for displaying a first user interface on the display; instructions for detecting touch input via the touch-sensitive surface beginning at a location on the touch-sensitive surface corresponding to the first user interface element; instructions for capturing a first type of media in response to detecting the touch input in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input satisfies a movement criterion and before a threshold time has elapsed since the touch input was detected; instructions for capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input satisfies the movement criterion and includes movement in a first direction, and instructions for continuing capturing the second type of media after detecting liftoff of the touch input from the touch-sensitive surface.

[0017] According to some embodiments, an electronic device is described. The electronic device comprises a display, a touch-sensitive surface, one or more media capture components, one or more processors, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for displaying a first user interface on the display; instructions for detecting touch input via the touch-sensitive surface beginning at a location on the touch-sensitive surface corresponding to a first user interface element; instructions for capturing a first type of media in response to detecting the touch input in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input met a movement criterion and before a threshold time had elapsed since the touch input was detected; instructions for capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input met the movement criterion and included movement in a first direction, and instructions for continuing capturing the second type of media after detecting liftoff of the touch input from the touch-sensitive surface.

[0018] According to some embodiments, an electronic device is described that includes a display, a touch-sensitive surface, one or more media capture components, means for displaying a first user interface on the display, means for detecting touch input via the touch-sensitive surface beginning at a location on the touch-sensitive surface corresponding to a first user interface element, and means for, in response to detecting the touch input, capturing a first type of media in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input met a movement criterion and before a threshold time had elapsed since the touch input was detected, capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input met the movement criterion and included movement in a first direction, and continuing to capture the second type of media after detecting liftoff of the touch input from the touch-sensitive surface.

[0019] Executable instructions to perform these functions are optionally contained in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. Executable instructions to perform these functions are optionally contained in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0020] In this manner, devices are provided with faster, more efficient methods and interfaces for performing gesture-based media capture, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may optionally complement or replace other methods for performing gesture-based media capture.

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

[0022] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display according to some embodiments. [Figure 1B] FIG. 1 is a block diagram illustrating exemplary components for event processing, according to some embodiments. [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments. [Figure 3] 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments. [Figure 4A] 1 illustrates an exemplary user interface of a menu of applications on a portable multifunction device according to some embodiments. [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface that is separate from the display, in accordance with some embodiments. [Figure 5A] 1 illustrates a personal electronic device according to some embodiments. [Figure 5B] 1 is a block diagram illustrating a personal electronic device according to some embodiments. [Figure 5C] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor according to some embodiments. [Figure 5D] 1 illustrates exemplary components of a personal electronic device having a touch-sensitive display and intensity sensor according to some embodiments. [Figure 5E] 1 illustrates exemplary components and a user interface of a personal electronic device, according to some embodiments. [Figure 5F]1 illustrates exemplary components and a user interface of a personal electronic device, according to some embodiments. [Figure 5G] 1 illustrates exemplary components and a user interface of a personal electronic device, according to some embodiments. [Figure 5H] 1 illustrates exemplary components and a user interface of a personal electronic device, according to some embodiments. [Figure 6A] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6B] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6C] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6D] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6E] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6F] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6G] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 6H] 10 illustrates the operation of a media capture lock affordance, according to one embodiment. [Figure 7] FIG. 7 is a flow diagram of an animation process for the media capture lock affordance shown in FIGS. 6A-6H, according to one embodiment. [Figure 8] 3 illustrates an exemplary device architecture for a media capture device that implements the media capture lock affordance described with reference to FIGS. 1-2, according to one embodiment. [Figure 9-1] FIG. 9A illustrates an exemplary user interface for performing gesture media capture according to some embodiments. [Figure 9-2]9B and 9C show exemplary user interfaces for performing gesture-based media capture, according to some embodiments. [Figure 9-3] Figure 9D shows an exemplary user interface for performing gesture media capture according to some embodiments. Figure 9E shows an exemplary user interface for performing gesture media capture according to some embodiments. Figure 9F shows an exemplary user interface for performing gesture media capture according to some embodiments. [Figure 9-4] 9G and 9H show exemplary user interfaces for performing gesture media capture according to some embodiments. [Figure 9-5] 9I and 9J show exemplary user interfaces for performing gesture-based media capture, according to some embodiments. [Figure 9-6] FIG. 9K illustrates an exemplary user interface for performing gesture media capture according to some embodiments. [Figure 9-7] FIG. 9L illustrates an exemplary user interface for performing gesture media capture according to some embodiments. [Figure 9-8] 9M and 9N show exemplary user interfaces for performing gesture media capture according to some embodiments. [Figure 9-9]Figure 9O shows an exemplary user interface for performing gesture media capture according to some embodiments. Figure 9P shows an exemplary user interface for performing gesture media capture according to some embodiments. [Figure 10A] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 10B] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 10C] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 10D] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 10E] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 10F] 1 illustrates an exemplary user interface for performing gesture-based media capture, according to some embodiments. [Figure 11A] FIG. 10 is a flow diagram for performing gesture-based media capture according to some embodiments. [Figure 11B] FIG. 10 is a flow diagram for performing gesture-based media capture according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0023] The following description describes example methods, parameters, etc. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of example embodiments.

[0024] There is a need for electronic devices that provide efficient methods and interfaces for performing gesture-based media capture. Such techniques can reduce the cognitive burden on users who use the device to capture media, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0025] Below, Figures 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of an example device for performing techniques for managing event notification. Figures 6A-6H illustrate example user interfaces for performing gesture-based media capture. Figure 7 is a flow diagram illustrating a method for performing gesture-based media capture, according to some embodiments. The user interfaces of Figures 6A-6H are used to illustrate processes described below, including the process of Figure 7. Figures 9A-10F illustrate example user interfaces for performing gesture-based media capture. Figures 11A-11B are flow diagrams illustrating a method for performing gesture-based media capture, according to some embodiments. The user interfaces of Figures 9A-10F are used to illustrate processes described below, including the process of Figures 11A-11B.

[0026] In the following description, terms such as "first" and "second" are used to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first touch can be referred to as a second touch, and similarly, a second touch can be referred to as a first touch, without departing from the scope of the various embodiments described. Although a first touch and a second touch are both touches, they are not the same touch.

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

[0028] The term "if" is interpreted, optionally, depending on the context, to mean "when" or "upon," or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are interpreted, optionally, depending on the context, 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]."

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

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

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

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

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

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

[0035] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

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

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

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

[0039] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates wirelessly with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range radios. Wireless communication is optionally supported by, but is 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-HSPA), Long Term Evolution (LTE), and other standards.Wireless technology includes, but is not limited to, technology such as: LTE evolution (LTE), near field communications (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®, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol), and the like. The present invention may use any of a number of communication standards, protocols, and technologies, including the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (XMPP), the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), the Instant Messaging and Presence Service (IMPS), and / or the Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this application.

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

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

[0042] A quick press of a push button optionally disengages a lock on the touchscreen 112 or optionally initiates a process to unlock the device using a gesture on the touchscreen, as described in U.S. Patent Application Serial No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image," U.S. Patent No. 7,657,849, which is incorporated herein by reference in its entirety. A longer press of a push button (e.g., 206) optionally turns power on or off to the device 100. The functionality of one or more of the buttons is optionally customizable by the user. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

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

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

[0045] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 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, California.

[0046] The touch-sensitive display in some embodiments of touchscreen 112 is optionally similar to the multi-touch-sensing touchpad described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication No. 2002 / 0015024 A1, each of which is incorporated by reference herein in its entirety. However, touchscreen 112 displays visual output from device 100, whereas a touch-sensitive touchpad does not provide visual output.

[0047] The touch-sensitive display in some embodiments of touchscreen 112 may be any of the touch-sensitive displays described in U.S. patent application Ser. No. 11 / 381,313, filed May 2, 2006, entitled "Multipoint Touch Surface Controller," (2) U.S. patent application Ser. No. 10 / 840,862, filed May 6, 2004, entitled "Multipoint Touchscreen," (3) U.S. patent application Ser. No. 10 / 903,964, filed July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices," (4) U.S. patent application Ser. No. 11 / 048,264, filed January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices," and (5) U.S. patent application Ser. No. 11 / 038,590, filed January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices." No. 11 / 228,758, filed September 16, 2005, entitled "Virtual Input Device Placement On A Touch Screen User Interface," (7) U.S. Patent Application No. 11 / 228,700, filed September 16, 2005, entitled "Operation Of A Computer With A Touch Screen Interface," (8) U.S. Patent Application No. 11 / 228,737, filed September 16, 2005, entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard," and (9) U.S. Patent Application No. 11 / 367,749, filed March 3, 2006, entitled "Multi-Functional Hand-Held Device," all of which are incorporated herein by reference in their entirety.

[0048] Touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. A user optionally contacts touchscreen 112 using any suitable object or accessory, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to primarily handle finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates the coarse finger-based input into precise pointer / cursor positions or commands to perform actions desired by the user.

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

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

[0051] Device 100 also optionally 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 a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Optical sensor 164 optionally interfaces with imaging module 143 (also referred to as a camera module) to capture still images or video. In some embodiments, the optical sensor is located on the back of device 100, opposite touchscreen display 112 on the front of the device, thereby enabling the touchscreen display to be used as a viewfinder for capturing still and / or video images. In some embodiments, the optical sensor is located on the front of the device so that an image of the user is optionally captured for video conferencing while the user views other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that a single optical sensor 164 is used for both video conferencing and capturing still and / or video images, along with the touchscreen display.

[0052] Device 100 also optionally 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 and creates a three-dimensional model of an object (e.g., a face) in a scene from a viewpoint (e.g., the depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also referred to as a camera module), depth camera sensor 175 is optionally used to determine a depth map of various portions of an image captured by imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that an image of a user with depth information is optionally obtained for a video conference, such as capturing a selfie image with depth map data while the user views other video conference participants on a touchscreen display. In some embodiments, depth camera sensor 175 is located on the back of the device or on both the back and front of device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), so that the depth camera sensor 175 is used for both video conferencing and capturing still and / or video images in conjunction with a touchscreen display.

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

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

[0055] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. 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 motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is co-located with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output in response to moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touchscreen display 112, which is located on the front of device 100.

[0056] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 within I / O subsystem 106. Accelerometer 168 optionally functions 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 herein by reference in their entireties. In some embodiments, information is displayed on the touchscreen display in portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information about the location and orientation (e.g., vertical or horizontal) of device 100.

[0057] In some embodiments, software components stored in memory 102 include operating system 126, communication module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 (FIG. 1A) or memory 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 which applications, views, or other information occupy various areas of touchscreen display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the location and / or orientation of the device.

[0058] Operating system 126 (e.g., an embedded operating system such as Darwin®, RTXC®, LINUX®, UNIX®, OS X®, iOS®, WINDOWS®, or VxWorks®) includes various software components and / or drivers that control and manage normal system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

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

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

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

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

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

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

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

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

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

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

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

[0070] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contacts module 137 is used to manage an address book or contact list (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370), optionally including adding name(s) to the address book, deleting name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication by phone 138, videoconferencing module 139, email 140, or IM 141, and the like.

[0071] Telephone module 138, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct conversations, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0072] 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, touch / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

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

[0074] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or 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).

[0075] In conjunction with the RF circuitry 108, touchscreen 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, the training support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0076] 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 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting the still images or video from memory 102.

[0077] 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 contains executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0078] 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 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0079] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

[0080] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a mini-application 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 a mini-application created by a 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).

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

[0082] 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 for searching memory 102 for text, music, sound, images, video, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user commands.

[0083] In conjunction with touchscreen 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 contains executable instructions that enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

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

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

[0086] In conjunction with touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are incorporated herein by reference in their entireties.

[0087] The above-identified modules and applications each correspond to a set of executable instructions that perform one or more of the functions described above and methods described herein (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; thus, in various embodiments, various subsets of these modules are optionally combined or otherwise rearranged. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

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

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

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

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

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

[0093] Event monitor 171 receives event information from peripherals interface 118. The 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 sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via 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.

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

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

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

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

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

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

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

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

[0102] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a User Interface Kit or a higher-level object from which application 136-1 inherits methods and other attributes. In some embodiments, each event handler 190 includes one or more of data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update 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 the data updater 176, object updater 177, and GUI updater 178 are included in each application view 191.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0117] In some embodiments, device 100 includes touchscreen 112, menu button 204, pushbuttons 206 for powering the device on / off and locking the device, volume control buttons 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 may optionally be used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined period of time has elapsed, and / or to unlock the device or initiate the unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

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

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

[0120] Attention is now directed to embodiments of user interfaces, optionally implemented on portable multifunction device 100, for example.

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

[0122] 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled "Music" or "Music Player," although other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0123] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 357 that generate a tactile output for a user of device 300.

[0124] Although some of the following examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display 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). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., in FIG. 4B , 460 corresponds to 468 and 462 corresponds to 470). In this way, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

[0125] Additionally, while the following examples are given primarily with reference to finger input (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., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a contact) followed by movement of a cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting a contact and subsequently ceasing contact detection). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger contacts are optionally used simultaneously.

[0126] FIG. 5A shows an exemplary personal electronic device 500. Device 500 includes a main body 502. In some embodiments, device 500 may 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 a touch-sensitive display screen 504, hereafter touchscreen 504. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data representing the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

[0127] Exemplary techniques for detecting and processing touch intensity can be found, for example, in International Patent Application No. PCT / US2013 / 040061, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application," published as International Patent Application No. WO / 2013 / 169849, and related applications, including International Patent Application No. PCT / US2013 / 069483, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships," published as International Patent Application No. WO / 2014 / 105276, each of which is incorporated herein by reference in its entirety.

[0128] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. 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 allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow device 500 to be worn by a user.

[0129] FIG. 5B illustrates an exemplary personal electronic device 500. In some embodiments, device 500 may include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 operably coupling an I / O section 514 to one or more computer processors 516 and memory 518. I / O section 514 may be connected to a display 504, which may have touch-sensing components 522 and, optionally, an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, I / O section 514 may be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication techniques. Device 500 may 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. In some examples, input mechanism 508 is optionally a button.

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

[0131] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including process 700 and process 1100 (FIGS. 7 and 11). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and resident 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 and may include other or additional components in multiple configurations.

[0132] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each, optionally, constitute an affordance.

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

[0134] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action, and a contact having a characteristic intensity that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic intensity and the one or more thresholds is not used to determine whether the first action or the second action should be performed, but rather is used to determine whether one or more actions should be performed (e.g., whether to perform the respective action or to refrain from performing the respective action).

[0135] FIG. 5C illustrates detecting multiple contacts 552A-552E on the touch-sensitive display screen 504 by multiple intensity sensors 524A-524D. FIG. 5C additionally includes an intensity diagram illustrating the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, intensity sensors 524A and 524D each measure 9 intensity units, and intensity sensors 524B and 524C each measure 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple 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 fraction of the aggregate intensity. FIG. 5D illustrates assigning aggregate intensities to contacts 552A-552E based on their distance from the center of force 554. In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of aggregate intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a fraction of the aggregate intensity A, according to a predetermined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance from the center of force to the respective contact j, and ΣDi is the sum of the distances from the center of force to all respective contacts (e.g., from i=1 to the end). The operations described with reference to FIGS. 5C-5D can be performed using electronic devices similar to or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). Note that the intensity diagrams are not part of the displayed user interface, but are included in FIGS. 5C-5D as an aid to the reader.

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

[0137] The intensity of the contact on the touch-sensitive surface is optionally characterized with respect to one or more intensity thresholds, such as a contact-detection intensity threshold, a light pressure intensity threshold, a deep pressure intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light pressure intensity threshold (e.g., above a nominal contact-detection intensity threshold below which the contact is not detected), the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across the various sets of user interface diagrams.

[0138] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as a "light press" input. An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as a "deep press" input. An increase in the characteristic intensity of a contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold may be referred to as detecting a lift-off 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.

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

[0140] Figures 5E to 5H show the results of the light pressure intensity threshold (e.g., "IT" in Figure 5E). L " ) to the deep press intensity threshold (e.g., "IT D5 illustrates the detection of a gesture including a press input corresponding to an increase in the intensity of contact 562 to an intensity above a deep pressure intensity threshold (e.g., "IT 1"). The gesture performed by contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to app2 on display user interface 570, which includes application icons 572A-572D displayed within predetermined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. An intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device detects when the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT 1"). D Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, a deep pressure intensity threshold (e.g., "IT") is detected during the gesture. D "), a reduced-scale representation 578A-578C (e.g., thumbnail) of the recently opened document is displayed for app2, as shown in FIGS. 5F-5H. In some embodiments, this intensity, which is compared to one or more intensity thresholds, is the characteristic intensity of the contact. Note that the intensity diagram for contact 562 is not part of the displayed user interface, but is included in FIGS. 5E-5H as an aid to the reader.

[0141] In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in FIG. 5F, representation 578A is first displayed adjacent to application icon 572B. As the animation progresses, representation 578A moves upward and representation 578B is displayed adjacent to application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves upward and representation 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIGS. 5F-5G, as the intensity of contact 562 exceeds a deep pressure intensity threshold (e.g., "IT D"), representations 578A-578C appear and move upward. In some embodiments, the intensity on which the animation progression is based is a characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using electronic devices similar to or identical to device 100, 300, or 500.

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

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

[0144] Attention is now directed to embodiments of user interfaces (“UIs”) and related processes implemented on an electronic device such as portable multifunction device 100 , device 300 , or device 500 .

[0145] 6A-6H illustrate exemplary user interfaces for performing gesture-based media capture, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0146] Exemplary Media Lock Affordances

[0147] This disclosure relates to a media record feature of a media capture device that locks a media capture affordance on a graphical user interface (GUI) to a locked media capture state for continuous media capture. In one embodiment, to start a media capture session for a media clip (e.g., a video clip, an audio clip), a user taps and holds (tap-and-hold) a media capture affordance (e.g., a virtual record button). As long as the user holds their touch on the media capture affordance, media continues to be captured by the media capture device. If the user removes their touch during a media capture session, the media capture session ends. If the user maintains their touch on the media capture affordance while performing a sliding gesture with their finger, the media capture affordance visually changes to a locked media capture affordance, and the media capture session is maintained, resulting in continuous media recording. In one embodiment, the locked media capture affordance moves beneath the user's finger so that it is not obscured by the user's finger. The user can remove their finger from the locked media capture affordance and the media capture session will be maintained until the user taps the locked capture button, after which the media capture session will end.

[0148] 6A-6H illustrate the operation of a media capture lock affordance, according to one embodiment. Referring to FIG. 6A, media capture device 600 presents GUI 601 on a display screen. GUI 601 includes media capture affordance 602. Media capture device 600 is shown as a smartphone in this exemplary embodiment. However, media capture device 600 may be any electronic device capable of capturing media, including a tablet computer, a wearable computer, a digital camera, a video recorder, and an audio recording device. In some embodiments, media capture device 600 includes one or more features of device 100, device 300, or device 500. Media capture affordance 602 can have any desired shape, size, or color. In the illustrated example, media capture affordance 602 is an oval-shaped button. GUI 601 also includes a display area for displaying live media and playing captured media. The media can be any type of media that can be captured, including video, still images, and audio, or any combination thereof.

[0149] Referring to FIG. 6B , a user taps and holds 603 (shown as a dashed circle) on media capture affordance 602 with a finger (e.g., with a thumb while holding media capture device 600) to initiate a media capture session in the “unlocked” state. During the media capture session, the built-in video camera and / or one or more microphones capture media (e.g., capture video and audio). The media capture session is “unlocked,” meaning that when the user lifts their finger from media capture affordance 602 (lifting their finger off the display screen), the media capture session ends and the media is stored in media capture device 600 (e.g., stored in cache memory). A visual directional indicator 604a (e.g., an arrowhead) is displayed on GUI 601 to indicate the direction the user can slide their finger to transition the media capture session to the “locked” state. While in the “locked” state, media is captured continuously without interruption. For example, video and audio continue to record, and still images will be taken in “burst” mode. Text is also displayed on GUI 601 instructing the user to "Slide up for continuous recording."

[0150] In some embodiments, additional affordances (not shown) are included on GUI 601 to allow a user to play, reorder, filter, and add emojis, animated icons, and titles to the captured media (hereinafter also referred to as "media clips"). Other affordances allow a user to indirectly share media clips on social networking websites and directly with friends and family through various communication means (e.g., instant messaging, email, tweets). In the illustrated embodiment, a navigation bar that allows a user to select operational modes such as camera, library, and poster is located below the media display area.

[0151] 6C, a user slide gesture input is shown, which results in the media capture affordance 602 sliding up towards the media capture area. Note that during the slide gesture input, the user's finger does not break contact with the display screen.

[0152] 6D-6G, when the user slides the media capture affordance 602 up a predetermined distance, the media capture affordance 602 changes or morphs into a media capture lock affordance 605, visually indicating a "locked" state, as shown in FIG. 6F. The text below the media display area also changes to instruct the user on how to stop the "locked" state, such as, for example, "Tap to stop recording." The media capture lock affordance 605 may be any size, shape, or color. In the illustrated example, the media capture lock affordance 605 is a square button. If, after changing or morphing from the media capture affordance 602 to the media capture lock affordance 605, the user lifts their finger and breaks contact with the display screen, the media capture session transitions to a "locked" state. In the "locked" state, the media capture session continues capturing media until the user taps 606 the media capture lock affordance 605 (FIG. 6G), in which case the media capture session ends. In an alternative embodiment, the visual direction indicator 604a is replaced with a button track 604b (FIG. 6H) that can indicate to the user how far they should slide the media capture affordance 602 to transition to the “locked” state.

[0153] In other embodiments, multiple taps may be used instead of a single tap. The direction of the slide gesture input may be any direction on the GUI 601, including up, down, right, and left. Sound effects, such as a “click” sound effect, may be played in synchronization with the tap-and-slide gesture to indicate when the media capture session is locked and unlocked. In one embodiment, force feedback (e.g., vibration) may be provided by a haptic engine to indicate when the media capture session is locked and unlocked. The affordances 602, 606 may be placed in any desired location on the GUI 601 and may change position, size, and / or shape depending on the orientation of the media capture device 600, such as portrait and landscape orientations. In one embodiment, a user may transition into or out of a locked media capture state using voice commands, which are processed by a speech detection / recognition engine implemented within the media capture device 600.

[0154] Example Process

[0155] Figure 7 is a flow diagram of an animation process for the media capture lock affordance shown in Figures 6A-6H, according to one embodiment. Process 700 can be implemented using device architecture 800 described with reference to Figure 8. Process 700 is executed on a device (e.g., 100, 300, 500, 800). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0156] Process 700 begins by receiving a tap-and-hold gesture input targeted to a media capture affordance at a first location of a GUI presented on a display device of a media capture device (701). The media capture affordance may be of any size, shape, or color. The first location may be any desired location on the GUI. In response to the tap-and-hold gesture input, process 700 initiates a media capture session on the media capture device, where the media capture session begins in an "unlocked" state (702). In response to a first lift gesture at the first location, process 700 terminates the media capture session (703).

[0157] In response to a slide gesture input from a first location to a second location on the GUI, process 700 changes the media capture affordance to a media capture lock affordance (704). The media capture lock affordance may be of any size, shape, or color. The second location may be any desired location on the GUI other than the first location. The slide gesture may be in any desired direction, including up, down, left, and right.

[0158] In response to detecting a second lift gesture at the second location, process 700 transitions the media capture session from an unlocked state to a locked state (705). In the locked state, the media capture device continuously captures media until the user taps the media capture lock affordance to end the media capture session. In one embodiment, the user can tap anywhere on the GUI or press a mechanical button on the media capture device (e.g., the home button on a smartphone) to end the media capture session after the second lift gesture.

[0159] It should be noted that the processing details described above with respect to method 700 (e.g., FIG. 7) are applicable in a similar manner to the methods described below. For example, method 700 optionally includes one or more of the features of the various methods described below with reference to method 1100. For the sake of brevity, these details will not be repeated below.

[0160] Exemplary Mobile Device Architecture

[0161] Figure 8 shows an example media capture device architecture 800 for a mobile device that implements the media capture lock affordance described with reference to Figures 6 and 7. Architecture 800 may include a memory interface 802, one or more data processors, image processors, and / or processors 804, and a peripherals interface 806. Memory interface 802, one or more processors 804, and / or peripherals interface 806 may be separate components or may be integrated into one or more integrated circuits. The various components in architecture 800 may be coupled by one or more communication buses or signal lines.

[0162] Coupling sensors, devices, and subsystems to the peripheral interface 806 can facilitate multi-functionality. For example, one or more motion sensors 810, light sensors 812, and proximity sensors 814 can be coupled to the peripheral interface 806 to facilitate motion sensing (e.g., acceleration, rotational speed), light, and proximity functions of the mobile device. A position processor 815 is connected to the peripheral interface 806 and can provide wireless positioning. In some implementations, the position processor 815 can be a GNSS receiver, such as a Global Positioning System (GPS) receiver chip. An electronic magnetometer 816 (e.g., an integrated circuit chip) is also connected to the peripheral interface 806 and can provide data that can be used to determine the direction of magnetic north. The electronic magnetometer 816 can provide data to an electronic compass application. The motion sensor(s) 810 can include one or more accelerometers and / or gyros configured to determine changes in speed and direction of movement of the mobile device. A barometer 817 can be configured to measure atmospheric pressure around the mobile device.

[0163] A camera subsystem 820 and an optical sensor 822, such as a charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) optical sensor, may be utilized to facilitate camera functions such as capturing photographs and recording video clips.

[0164] Communications functions can be facilitated through one or more wireless communications subsystems 824, which can include radio frequency (RF) receivers and transmitters (or transceivers) and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of communications subsystems 824 can depend on the communications network(s) over which the mobile device is intended to operate. For example, architecture 800 can include communications subsystems 824 designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi™ or Wi-Max™ network, and a Bluetooth™ network. In particular, wireless communications subsystem 824 can include hosting protocols that enable the mobile device to be configured as a base station for other wireless devices.

[0165] The audio subsystem 826 may be coupled to a speaker 828 and a microphone 830 to facilitate voice-enabled functions such as voice recognition, voice duplication, digital recording, and telephone functions. The audio subsystem 826 may be configured to receive voice commands from a user.

[0166] The I / O subsystem 840 may include a touch surface controller 842 and / or other input controller(s) 844. The touch surface controller 842 may be coupled to a touch surface 846 or pad. The touch surface 846 and touch surface controller 842 may detect contact and movement, or the cessation of contact and movement, using, for example, any of a number of touch sensitivity technologies. Touch sensitivity technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch surface 846. The touch surface 846 may include, for example, a touch screen. The I / O subsystem 840 may include a haptic engine or device for providing tactile feedback (e.g., vibration) in response to commands from the processor.

[0167] Other input controller(s) 844 may be coupled to other input / control devices 848, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointer devices such as styluses. One or more buttons (not shown) may include up and down buttons for volume control of speaker 828 and / or microphone 830. Touch surface 846 or other controllers 844 (e.g., buttons) may include or be coupled to fingerprint identification circuitry for use with fingerprint authentication applications to authenticate a user based on fingerprint(s).

[0168] In one implementation, the touch surface 846 can be unlocked by pressing a button for a first duration, and power to the mobile device can be turned on / off by pressing the button for a second duration longer than the first duration. A user can customize the functionality of one or more of the buttons. The touch surface 846 can also be used to implement, for example, virtual or soft buttons and / or a virtual touch keyboard.

[0169] In some implementations, the mobile device can present recorded audio and / or video files, such as MP3 files, AAC files, and MPEG files. In some implementations, the mobile device can include MP3 player functionality. Other input / output and control devices can also be used.

[0170] The memory interface 802 can be coupled to memory 850. The memory 850 can include high-speed random-access memory and / or non-volatile memory such as one or more magnetic disk storage devices, one or more optical storage devices, and / or flash memory (e.g., NAND, NOR). The memory 850 can store an operating system 852, such as an embedded operating system such as iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks. The operating system 852 can include instructions for handling basic system services and for performing hardware-dependent tasks. In some implementations, the operating system 852 can include a kernel (e.g., a UNIX kernel).

[0171] Memory 850 may also store communications instructions 854 for facilitating communications with one or more additional devices, one or more computers, and / or one or more servers, such as instructions for implementing a software stack for wired or wireless communication with other devices. Memory 850 may also include graphical user interface instructions 856 for facilitating graphical user interface processing described with reference to Figures 6 and 7, sensor processing instructions 858 for facilitating sensor-related processing and functions, telephony instructions 860 for facilitating telephony-related processing and functions, electronic messaging instructions 862 for facilitating electronic messaging-related processing and functions, web browsing instructions 864 for facilitating web browsing-related processing and functions, media processing instructions 866 for facilitating media processing-related processing and functions, GNSS / location instructions 868 for facilitating generic GNSS- and location-related processing and instructions, camera instructions 870 for facilitating camera-related processing and functions described with reference to Figures 6 and 7, and other application 872 instructions. Memory 850 may also store other software instructions (not shown), such as security instructions, web video instructions for facilitating web video-related processes and functions, and / or web shopping instructions for facilitating web shopping-related processes and functions. In some implementations, media processing instructions 866 may be divided into audio processing instructions for facilitating audio processing-related processes and functions and video processing instructions for facilitating video processing-related processes and functions, respectively.

[0172] 6 and 7 are detected using a touch event model implemented in software on media capture device 800. An exemplary touch event model is described in U.S. Patent No. 8,560,975, entitled "Touch Event Model," issued October 15, 2013, which is incorporated herein by reference in its entirety.

[0173] Each of the above-identified instructions and applications may correspond to a set of instructions that perform one or more of the functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 850 may include additional or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and / or software, including one or more signal processing and / or application specific integrated circuits.

[0174] The described functionality may advantageously be implemented in one or more computer programs executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used directly or indirectly in a computer to perform a particular action or bring about a particular result. Computer programs may be written in any form of programming language (e.g., SWIFT, Objective-C, C#, Java), including compiled or interpreted languages, and may be distributed in any form, including as a standalone program or module, component, subroutine, browser-based web application, or other unit suitable for use in a computing environment.

[0175] Processors suitable for executing a program of instructions include, by way of example, both general-purpose and special-purpose microprocessors, as well as the sole processor or one of multiple processors or cores of any kind of computer. Typically, a processor receives instructions and data from a read-only memory or a random-access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer also includes, or is operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks, magneto-optical disks, and optical disks. Suitable storage devices for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including, by way of example, semiconductor memory devices, such as EPROMs, EEPROMs, flash memory devices, magnetic disks, such as internal hard disks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).

[0176] To interact with a user, features can be implemented in a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, or a retina display device for displaying information to a user. The computer can have a touch surface input device (e.g., a touch screen) or keyboard, and a pointing device such as a mouse or trackball that allows the user to provide input to the computer. The computer can have a voice input device for receiving voice commands from a user.

[0177] Features may be implemented in a computer system including back-end components such as a data server, or middleware components such as an application server or an Internet server, or front-end components such as a client computer having a graphical user interface or an Internet browser, or any combination thereof. The components of the system may be connected by any form or medium of digital data communication, such as a communications network. Examples of communications networks include, for example, a LAN, a WAN, and the computers and networks forming the Internet.

[0178] A computer system may include clients and servers. Generally, clients and servers are remote from each other and typically interact through a communication network. The relationship of client and server arises through computer programs running on the respective computers and having a client-server relationship to each other. In some embodiments, a server sends data (e.g., HTML pages) to a client device (e.g., for purposes of displaying the data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., the results of user interaction) can be received at the server from the client device.

[0179] One or more computer systems can be configured to perform particular actions by installing software, firmware, hardware, or a combination thereof into a running system and causing the system to perform the actions. One or more computer programs can be configured to perform particular actions by comprising instructions that, when executed by a data processing device, cause the device to perform the actions.

[0180] One or more features or steps of the disclosed embodiments may be implemented using an application programming interface (API). An API may define one or more parameters passed between a calling application and other software code (e.g., an operating system, a library routine, a function) that provides data or a service that performs an operation or calculation. An API may be implemented as one or more calls in program code that send or receive one or more parameters via a parameter list or other structure based on a calling convention defined in an API specification. A parameter may be a constant, a key, a data structure, an object, an object class, a variable, a data type, a pointer, an array, a list, or another call. API calls and parameters may be implemented in any programming language. The programming language may define the vocabulary and calling conventions that a programmer uses to access functions that support the API. In some implementations, API calls may report to the application the capabilities of the device running the application, such as input capabilities, output capabilities, processing capabilities, power capabilities, and communication capabilities.

[0181] While the specification contains numerous specific implementation details, these should not be construed as limitations on the scope of any invention or the scope that may be claimed, but rather as descriptions of features that are specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented separately in multiple embodiments, or in any suitable subcombination. Furthermore, while features may be described above as working in a particular combination, or even originally claimed as such, in some instances, one or more features of a claimed combination can be deleted from that combination. Claimed combinations can also be directed to subcombinations or variations of subcombinations.

[0182] Similarly, although operations are depicted in the figures in a particular order, this should not be understood as requiring the operations to be performed in the order shown, or sequentially, or that all of the operations shown be performed to achieve desirable results. In certain situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together into a single software product or packaged into multiple software products.

[0183] 9A-9P and 10A-10F show example user interfaces for performing gesture-based media capture, according to some embodiments, and are used to illustrate the processes described below, including the processes in FIGS.

[0184] 9A shows an exemplary media capture user interface 904. In some embodiments, device 900 includes one or more features of device 100, 300, or 500. In this example, device 900 includes a touchscreen display 902 that displays media capture interface 904. In some embodiments, the media capture interface is used to capture one or more types of media in response to user input (e.g., touch input). For example, the media capture interface may be a graphical user interface that can be used to capture one or more of a still image, a video (e.g., including audio), and a sequence of images (e.g., burst image capture). Media capture interface 904 includes a viewfinder area 906 that includes a representation of a scene being captured by a media capture component, such as, for example, an image sensor (e.g., optical sensor 164) passing through a view of the scene for display in the media capture interface (e.g., so that a user can determine an appropriate time to capture a media item). The media capture interface 904 also includes a mode selector 908 that can be used (e.g., via touch input, swipe input) to change the media capture mode (e.g., from "photo" to "video," or to "panorama," "time lapse," "slow motion," etc.). The media capture interface 904 also includes a media capture affordance 910. The media capture affordance may also be referred to as a "shutter," "shutter affordance," etc.

[0185] In some embodiments, touch input (e.g., a tap gesture, also referred to as a tap) on the media capture affordance causes the device to capture a media item (e.g., according to the current media capture mode). For example, in the example shown in FIG. 9A , the current media capture mode is “photo,” so a user can expect the device 900 to capture a still image in response to a tap on the media capture affordance 910. The media capture interface 904 also includes a camera selector affordance 912 that can be used to change (e.g., in response to user input) the image sensor (e.g., front camera, rear camera) of the device 900 used to capture media. The media capture interface 904 also includes a last captured media item area 914 that displays a preview (e.g., a thumbnail, a single frame of a video) of the last captured media item. In some embodiments, in response to touch input associated with the last captured media item area (e.g., 914), the device (e.g., 900) displays one or more recently captured media items, a plurality of media items (e.g., a camera roll), and / or a media library.

[0186] As described above, a device (e.g., 900) typically responds to user input on a media capture affordance (e.g., 910) based on the current media capture mode. Techniques for gestural capture of media are described herein. Gesture reliance can cause different types of media to be captured based on the particular gesture used. The particular gestures available for capturing media can have different characteristics based on user input characteristics (e.g., duration, movement, and / or various combinations thereof). As shown in the following examples in FIGS. 9A-9P, the type of media captured does not have to correspond to the media capture mode active when touch input is received.

[0187] Among other things, input characteristic boxes 901 are included throughout FIGS. 9A-9P to indicate characteristics of a touch input (e.g., detected by electronic device 900) in the corresponding figure and are provided as a visual representation of the touch input characteristics (e.g., in the memory of device 900) in each exemplary scenario depicted in each figure. The input characteristics associated with a touch input can be used by the device (e.g., 900) to determine whether the touch input meets criteria to be considered a particular gesture (e.g., that can cause a media capture-related action to be performed). The input characteristic boxes 901 are provided solely as a visual aid to facilitate reader understanding and are not necessarily displayed on the device (e.g., 900). Additionally, unless otherwise noted in the figures or herein, the input characteristic boxes 901 indicate characteristics of the touch input (e.g., lift-off of the touch input) after device 900 receives the depicted touch input in the respective figure (e.g., 920 in FIG. 9B ) and before ceasing to detect such input.

[0188] 9A-9B illustrate the capture of a first type of media item. In the example shown in FIGS. 9A-9B, device 900 captures a first type of media item corresponding to the current media capture mode (e.g., “Photo”). In FIG. 9B, device 900 receives user input 920, which is a touch input at a location on touchscreen display 902 corresponding to media capture affordance 910. As shown in input characteristic box 901 in FIG. 9B, user input 920 (also referred to as touch input 920) does not meet the movement criteria (movement criteria: not met) and has not been detected for longer than a threshold time (threshold time: not elapsed). In this example, device 900 ceases detecting touch input 920 (e.g., due to input lift-off) before the movement criteria is met and before the threshold time has elapsed. Thus, in this example, touch input 920 is a tap input gesture. FIG. 9C illustrates device 900 after lift-off of touch input 920. In FIG. 9C , the media capture interface 904 returns to the same state as shown in FIG. 9A , except that the last captured media item area 914 now includes a representation of the current scene shown in the viewfinder area 906, indicating that the device 900 has captured a media item. In this example, the device 900 has captured a still image (e.g., an exemplary first type of media). In some embodiments, the device 900 captures a second type of media item in addition to the first type of media item in response to a user input (e.g., a tap input) that does not meet the movement criteria and is not detected for more than a threshold time. In some embodiments, the second type of media has a duration that is independent of the duration of the touch input. For example, the device 900 can additionally (or instead) capture a video clip (e.g., including audio) of fixed duration (e.g., 3 seconds long) or variable duration (e.g., 2-5 seconds long) regardless of the duration of the touch input (e.g., 0.5 seconds).

[0189] 9D-9F illustrate the capture of a second type of media item. In the examples shown in FIGS. 9D-9F, device 900 captures a second type of media item (e.g., a video) that does not correspond to the current media capture mode (e.g., "photo") using a touch input that does not meet the movement criterion but meets the time criterion (e.g., is detected for more than a threshold time). In FIG. 9D, device 900 receives user input 930, which is a touch input at a location on touchscreen display 902 that corresponds to media capture affordance 910. As shown in input characteristic box 901 in FIG. 9D, user input 930 does not meet the movement criterion (movement criterion: not met) and has not been detected for longer than a threshold time (threshold time: not elapsed).

[0190] FIG. 9E shows that device 900 continues to detect touch input 930 after the threshold time has elapsed but before the movement criterion is met. Thus, input characteristic box 901 in FIG. 9E indicates that user input 930 does not meet the movement criterion (movement criterion: not met), but has been detected for longer than the threshold time (threshold time: elapsed). Thus, in this example, touch input 930 is a tap-and-hold input gesture (e.g., a tap held for the threshold time). In response to touch input 930 being detected for more than the threshold time, device 900 begins capturing (e.g., recording) video (e.g., an exemplary second type of media). As shown in FIG. 9E, device 900 is currently capturing video. In this example, the elapsed video time (00:00:08, or 8 seconds) is indicated during video capture, and media capture affordance 910 has been replaced with stop affordance 934. Additionally, in FIG. 9E, device 900 displays media capture lock affordance 932, discussed in more detail below (e.g., replacing camera selector affordance 912).

[0191] FIG. 9F shows the device 900 after liftoff of the touch input 930. In FIG. 9F, in response to the liftoff of the touch input 930, the media capture interface 904 returns to the same state as shown in FIG. 9D, except that the last captured media item area 914 now includes a representation of the current scene shown in the viewfinder area 906 indicating that the device 900 has captured a media item. In this example, the device 900 has captured a video (e.g., an exemplary second type of media). In some embodiments, the device 900 captures a first type of media item in addition to a second type of media item in response to a user input (e.g., a tap-and-hold gesture, touch input 930) that does not meet the movement criteria but is detected for more than a threshold time. For example, in addition to capturing a video, the device 900 can additionally capture a still image. In some embodiments, the second type of media (e.g., captured in response to the touch input 930) has a duration based on the duration of the touch input (e.g., 930). For example, device 900 may capture a video clip (e.g., including audio) having a duration based on the duration that touch input 930 was detected. Thus, if touch input 930 was detected on touchscreen display 902 for 8 seconds, the resulting captured second type of media may be an 8-second long video. In some embodiments, the duration of the second type of media is based on the duration of the touch input, but video recording begins after touch input is detected for more than the threshold duration. Thus, if the threshold duration is 1 second and touch input is detected for 8 seconds, the resulting video is 7 seconds long (e.g., lift-off ends the recording of the video, which is then stored by device 900 in a media library).

[0192] 9G-9J illustrate the use of a gesture to initiate capture of a second type of media that continues after detection of the gesture ceases. In the example shown in FIGS. 9G-9J, device 900 captures a second type of media item (e.g., video) that does not correspond to the current media capture mode (e.g., "photo") using touch input 940 that meets the movement criterion (e.g., in a first direction) (and also meets the time criterion). In FIG. 9G, device 900 receives user input 940, which is a touch input at a location on touchscreen display 902 that corresponds to media capture affordance 910. As shown in input characteristic box 901 in FIG. 9D, user input 940 does not meet the movement criterion (movement criterion: not met) and has not been detected for longer than a threshold time (threshold time: not elapsed).

[0193] 9G-9J, touch input 940 is detected for longer than the threshold duration, but meeting the threshold duration is not a requirement for transitioning the media capture session to a locked media capture state. Rather, in this example, the only requirement is that the movement criteria be met. In some embodiments, a threshold time may additionally be required to lock the media capture session.

[0194] FIG. 9H shows that device 900 continues to detect touch input 940 after the threshold time has elapsed but before the movement criterion is met. Thus, input characteristic box 901 in FIG. 9H indicates that user input 940 does not meet the movement criterion (Movement Criteria: Not Met), but has been detected for longer than the threshold time (Threshold Time: Elapsed). Similar to the examples described above in FIGS. 9D-9F, in response to touch input detected for longer than the threshold period, device 900 begins capturing (e.g., recording) video (e.g., an exemplary second type of media). In this example, touch input 940 is a touch input that has been dragged from the initial position of contact (e.g., location 910). As used herein, a "dragged" touch input is also referred to as a "sliding" touch input. In FIG. 9H, touch input 940 has been dragged to the right of media capture affordance 910. As shown in FIG. 9H, device 900 is currently capturing video. In this example, the elapsed time of the video (00:00:08, or 8 seconds) is shown, and the media capture affordance 910 has been replaced with a stop affordance 934. The stop affordance is also referred to herein as a "locked state capture button" (e.g., when it replaces the media capture affordance during a locked media capture session). In some embodiments, the stop affordance (e.g., 934) replaces the media capture affordance (e.g., 910) in response to lift-off of a touch input (e.g., transitioning the media capture session to a locked media capture state). Additionally, in FIG. 9H , the device 900 displays a media capture lock affordance 932, discussed in more detail below (e.g., replacing the camera selector affordance 912).

[0195] Notably, the scenario shown in Figure 9H is similar to that of Figure 9E, except that touch input (940) in Figure 9H has moved slightly to the right, while touch input (930) in Figure 9E has not moved. Thus, if detection of touch input 940 were to cease at the moment shown in Figure 9H (e.g., due to liftoff of touch input 940) because touch input 940 does not meet the movement criterion but has been detected for longer than the threshold time, a similar result would occur as shown in Figure 9F, in which device 900 would capture video having a duration based on the duration that touch input 940 was detected. However, in this example, touch input 940 continues to be detected, as shown in Figures 9I and 9J, described below.

[0196] In FIG. 9H , device 900 displays touch input indicator 942, which is a representation of the current location of touch input 940. In this example, the touch input indicator is displayed in response to movement of touch input 940 (e.g., movement of the touch input away from the area associated with media capture affordance 910 ( FIG. 9G ) / stop affordance 934 ( FIG. 9H )). A movement path indicator 943 is also shown, displayed between stop affordance 934 (or media capture 910, if not replaced by stop affordance 934) and media capture lock affordance 932. Touch input indicator 942 moves along the indicated movement path in response to dragging (also called “sliding”) of touch input 904 (e.g., left or right, or in either direction).

[0197] 9I and 9J, techniques for continuing to capture media after ceasing to detect user input are illustrated. As described above in connection with FIGS. 9B-9C, the device optionally captures a first type of media in response to a user input (e.g., a gesture) having certain characteristics (e.g., no movement detected for less than a threshold time). As described above in connection with FIGS. 9D-9F, the device optionally captures a second type of media (e.g., video) based on the duration of the user input if the user input has other characteristics (e.g., no movement (or movement does not meet the criteria) and is detected for more than a threshold time). In some embodiments, the device continues to capture the second type of media so that it continues even after detection of touch input has ceased.

[0198] In FIG. 9I , touch input 940 has moved further to the right and is now at a location corresponding to media capture lock affordance 932. In this example, the movement criterion is met when the touch input (e.g., 940) moves (e.g., drags) from the location of media capture affordance 910 (e.g., with a touch down) (or from the location of the stop affordance (e.g., 934) that replaced the media capture affordance) to the location of media capture lock affordance 932. In some embodiments, the device determines whether the movement criterion is met in response to the user input ceasing to be detected (e.g., upon liftoff of the touch input). Thus, the input characteristic box 901 in FIG. 9I indicates that the movement criterion would be met if user input 940 occurred at the current location (movement criterion: met (liftoff)), and also indicates that the touch input has been detected for longer than a threshold time (threshold time: elapsed). As shown in FIG. 9I , movement indicator 942 does not cover / obscure media capture lock affordance 932 while the touch remains at the corresponding location and is detected. In some embodiments, the movement indicator (e.g., 942) covers / obscures the media capture lock affordance (e.g., 932) while the contact remains in the corresponding location and is detected. As shown in FIG. 91, the media capture interface 904 remains in the video recording state. The stop affordance 934 continues to be displayed, and the elapsed time for video capture (00:00:10, or 10 seconds) continues to be displayed.

[0199] FIG. 9J shows device 900 after liftoff of touch input 940. In response to ceasing detection of touch input 940, device 900 continues capturing a second type of media (e.g., video recording) because liftoff of touch input 940 occurred after satisfying the movement criteria (e.g., liftoff on affordance 932). Continuing to capture media is also referred to herein as “maintaining” the media capture session. In this example, device 900 continues capturing a second type of media because the media capture session (e.g., capturing video) transitioned from an unlocked media capture state to a locked media capture state. A media capture state is also referred to herein as a “media capture session state.” As used herein, a media capture session in an unlocked media capture state is also referred to as an “unlocked” media capture session. As used herein, a media capture session in a locked media capture state is also referred to as a “locked” media capture session. In some embodiments, when a media capture session is in a locked media capture state, the media session continues (e.g., after cessation of detection of a touch input gesture that would initiate the media session). As shown in FIG. 9J , the media capture interface 904 remains in a video recording state. The stop affordance 934 continues to be displayed, and the elapsed time of the video capture (00:00:12, or 12 seconds) continues to be displayed (e.g., and progresses as more time passes during capture). Also shown in FIG. 9J , the device 900 displays an image capture affordance 944 that can be used to capture a first type of media (e.g., a still image and / or a fixed duration clip) while continuing to capture a second type of media (e.g., video). In this example, the device 900 continues capturing video (e.g., an exemplary second type of media).

[0200] In some embodiments, device 900 captures media items of a first type in addition to media items of a second type in response to user input that meets a movement criterion and is detected for more than a threshold time. For example, in addition to capturing video, device 900 may additionally capture a still image in response to touch input 940. In some embodiments, the still image is discarded. For example, in response to touchdown of a touch input, a first type of media (e.g., a still image) may be acquired, but the device may discard the first type of media if a second type of media is captured (e.g., the touch input continues for a threshold time or meets the movement criterion).

[0201] In some embodiments, the device determines whether a movement criterion is met while detection of the user input continues. For example, the device 900 may determine that the movement criterion is met when the touch input 940 reaches a particular location, such as the location of the media capture lock affordance 932 in FIG. 9I. In such an example, in response to the user input meeting the movement criterion, the device may transition the current media capture session to a locked media capture state (e.g., as shown in FIG. 9J) without first requiring lift-off (e.g., even if the touch input 940 is still detected). Thus, the device 900 may continue capturing the second type of media despite further movement of the touch input 940 (e.g., back toward the media capture affordance 910, to a location as shown in FIG. 9H) and lift-off at a location other than the media capture lock affordance 932. In some embodiments, lift-off (e.g., of touch input 940) on a media capture affordance (e.g., 910) or on a stop affordance (e.g., 934) causes the device (e.g., 900) to cease capturing media (e.g., media capture does not continue after lift-off).

[0202] In some embodiments, the movement criterion is met when the touch input is dragged toward the media capture lock affordance (e.g., 932) by at least a predetermined amount (e.g., a percentage, a certain distance). For example, the movement criterion may be met (e.g., immediately or upon liftoff) if the touch input 940 drags the movement indicator 942 at least 50% of the distance between the location of the media capture affordance 910 in FIG. 9G (e.g., the same location as the stop affordance 934 in FIG. 9H) and the media capture lock affordance 932. This is illustrated in the examples shown in FIGS. 10A-10F and is described in more detail below.

[0203] In some embodiments, the movement criterion requires (e.g., to be satisfied) movement in a particular direction (e.g., right, left, down, up). For example, Figures 9G-9J show movement (of the media capture affordance 910) to the right required to satisfy the movement criterion. In some embodiments, the movement criterion is satisfied by movement in more than one direction (e.g., movement to the left or right can satisfy the movement criterion).

[0204] 9K shows an example technique for stopping the capture of a second type of media while the media session is in a locked media capture state. Because media continues to be captured when touch input 940 is lifted off, touch input 950 to stop affordance 934 can be used to cause device 900 to stop capturing video. For example, in response to touch input 950, device 900 can stop recording video and display media capture interface 904 (e.g., indicating that nothing is currently being recorded), as shown in FIG. 9F.

[0205] 9L shows an example technique for capturing a first type of media while a media session is in a locked media capture state. In FIG. 9L, device 900 receives user input 960 on image capture affordance 944, which can be used to cause device 900 to capture a first type of media (e.g., a still image and / or a fixed duration clip) while recording a second type of media (e.g., a video). In this example, device 900 continues capturing video (e.g., an example second type of media) after touch input 960. In response to touch input 960, device 900 captures a still image from a video frame (e.g., including storing the still image in a media library).

[0206] 9M-9P illustrate capturing a sequence of media items of a first type using touch input gestures. In the example shown in FIGS. 9M-9P, device 900 captures a sequence of media items of a first type (e.g., still images) using touch input that satisfies a second movement criterion. In some embodiments, the device determines whether the user input (e.g., touch input) satisfies one or more different movement criteria (e.g., a first movement criterion and a second movement criterion). For example, the exemplary first movement criterion may be the movement criterion described above with respect to FIGS. 9B-9K, in which case, upon meeting the criterion, the device changes the media capture session to a locked media capture state. In some embodiments, upon meeting the second movement criterion, device 900 takes a different media capture action (e.g., different from the action taken in response to the first movement criterion being met). In this example, device 900 performs burst media capture in response to detecting touch input that satisfies a second movement criterion, which will be discussed in more detail below.

[0207] 9M, device 900 receives user input 970, which is a touch input at a location on touchscreen display 902 that corresponds to media capture affordance 910. As shown in input characteristic box 901 in FIG. 9D, user input 970 does not meet the movement criteria (Movement Criteria: Not Met) and has not been detected for longer than a threshold time (Threshold Time: Not Elapsed).

[0208] FIG. 9N shows that the device 900 continues to detect the touch input 970 until after the threshold time has elapsed and the movement criteria have been met. Thus, the input characteristic box 901 in FIG. 9H indicates that the user input 940 does not meet the movement criteria (movement criteria: not met), but has been detected for longer than the threshold time (threshold time: elapsed). In the example of FIG. 9N, the movement criteria that has been met is the second movement criteria. In this example, the second movement criteria is different from the (first) movement criteria described above with respect to FIGS. 9B-9K. In this example, the second movement criteria includes movement of a threshold amount (e.g., any amount, a minimum amount) in a second direction. In the example of FIG. 9N, the touch input 970 has moved a minimum amount (e.g., a minimum number of pixels) in a second direction (e.g., left) that is different from the first direction (e.g., right). In response to detecting touch input 970 satisfying a second movement criterion in a second direction, device 900 begins capturing a sequence of media items of the first type of media items (e.g., begins capturing images in a "burst" image capture mode). In this example, device 900 continues capturing the sequence of media items until it ceases detecting touch input 970. In some embodiments, the device transitions to a locked media capture state while capturing the sequence of media items. For example, device 900 optionally provides the ability to lock a media capture session into burst mode, where burst capture continues upon liftoff of touch input 970, similar to that described above with respect to the video of FIGS. 9G-9J. Similar to the above, burst mode may be locked based on touch input satisfying one or more movement criteria (e.g., a third movement criterion).

[0209] It should be noted that the detailed description of the first and second movement criteria is not intended to be limiting or characteristic to any one of them (e.g., in implementations of the techniques herein that differ from the examples used herein). Thus, the specific details described with respect to specific movement criteria herein are merely exemplary, and one of ordinary skill in the art will understand that a movement criteria may have one or more characteristics of any of the movement criteria described herein.

[0210] As shown in FIG. 9N, while continuing to detect touch input 970, device 900 continues capturing the sequence of media items. While continuing to capture the sequence of media items, device 900 displays touch input indicator 974 representing the location of touch input 970. Touch input indicator 974 moves along exemplary movement path indicator 975 (FIG. 9O). Device 900 also displays sequence count 972 indicating the number of media items captured during the ongoing (burst) media capture session capturing the sequence of media items. As shown in FIG. 9N, one media item has been captured so far since device 900 began capturing the current sequence (e.g., in response to user input 970), as indicated by the number "1" in sequence count 972.

[0211] 9O and 9P show that the device 900 continues capturing a sequence of media items while continuing to detect touch input. In FIG. 9O, detection of the touch input 970 continues and is further dragged to the left, and the sequence count 976 now shows "10" (e.g., 10 media items of a first type have been captured). In FIG. 9O, the touch input indicator 974 moves along an exemplary movement path indicator 975 (shown as a solid line). In some embodiments, the device (e.g., 900) moves the sequence count in response to the movement of the touch input (e.g., creates a copy and repositions and displays a new user interface element containing it). For example, in FIG. 9O, in response to the touch input 970 moving toward (e.g., approaching or reaching) the location of the sequence count 972 (in FIG. 9N), the device 900 displays the number of media items captured at the new location in the sequence count 976 (corresponding to the original location of the media capture affordance 910). In some embodiments, the device (e.g., 900) ceases displaying the sequence count (e.g., 972) at its initial display location as the sequence count moves (e.g., to 976). In this way, the device 900 prevents the dragged touch input from obscuring the sequence count. In some embodiments, the sequence count does not move in response to movement of the touch input. For example, the sequence count may be displayed in a single location (e.g., either 972, 976, or another location) and not move in response to the touch input moving to the corresponding location. In some embodiments, the sequence count moves again in response to further movement. For example, if the touch input returns to the location of sequence count 976, the sequence may move again (e.g., may be displayed as sequence count 972 again).

[0212] In FIG. 9P , touch input 970 continues to be detected and dragged further to the left, and sequence count 976 now shows “20” (e.g., 20 media items of the first type have been captured). In some embodiments, the device (e.g., 900) stops capturing the sequence of media items in response to ceasing to detect the touch input. For example, if device 900 were to stop detecting touch input 970 at the moment shown in FIG. 9P , capturing the sequence of media items would cease (e.g., after capturing 20 media items of the first type). In such an example, in response to lift-off of touch input 970, device 900 may display a media capture interface 904 similar to that shown in FIG. 9F , where last captured media item area 914 includes a representation of one of the 20 media items captured in the sequence of media items.

[0213] In some embodiments, the amount and / or speed of movement of a touch input affects the capture characteristics of the sequence of media items of the first type. For example, a touch input having movement above a threshold speed (e.g., the speed of movement on a touchscreen display) can increase the rate of burst image capture (e.g., faster than a similar touch input moving more slowly) and / or can transition at a faster rate (e.g., than a similar touch input moving more slowly). As another example, a touch input that moves a greater distance from an initial position (e.g., 910) can increase the rate of burst image capture than a touch that moves a shorter distance.

[0214] 10A-10F illustrate example interfaces for transitioning a media capture session from an unlocked media capture state to a locked media capture state. In particular, FIGS. 10A-10F illustrate example detailed views of touch inputs interacting with one or more affordances to transition a media session to a locked media capture state, as described above with respect to FIGS. 6A-6F and 9A-9P. The interfaces illustrated in FIGS. 10A-10F may be displayed by device 900 (e.g., in one or more of the interfaces illustrated in FIGS. 9A-9P).

[0215] 10A shows an exemplary media capture affordance 1000. For example, media capture affordance 1000 can include the same functionality as described above with respect to media capture affordance 602 or 910.

[0216] 10B , user input 1002 (also referred to as touch input 1002) is received at a location associated with media capture affordance 1000 (e.g., the user input is detected by a device displaying affordance 1000). In this example, similar to that described above with respect to touch input 930 in FIGS. 9D and 9E , touch input 1002 is detected for more than a threshold time, and therefore, capture of media (e.g., video) begins (e.g., in response to the device detecting touch input 1002 or in response to touch input 1002 being detected for more than a threshold duration). As the arrow in FIG. 10B indicates, touch input 1002 includes a translation component to the right of media capture affordance 1000. As also shown in FIG. 10B , media capture lock affordance 1004 is displayed to the right of media capture affordance 1000. For example, media capture lock affordance 1004 may include the same functionality as that described above with respect to media capture lock affordance 932. 10B also shows a movement path indicator 1005 connecting the media capture affordance 1000 and the media capture lock affordance 1004, which indicates the direction of movement toward the media capture lock affordance 1004. The movement path indicator is also referred to as a "visual direction indicator" as used herein.

[0217] In FIG. 10C , the touch input 1002 has moved slightly to the right from FIG. 10B , and in FIG. 10D , the touch input 1002 has moved further to the right from FIG. 10C . In FIG. 10D , the touch input indicator 1006 has not yet passed the lock distance marker 1008. The touch input indicator 1006 may include one or more features of the touch input indicator 942 described above. In some embodiments, the lock distance marker (e.g., 1008) may be displayed (e.g., on the movement path indicator 1005) indicating a location associated with (e.g., sufficient to meet) the movement criteria. In FIG. 10D , the lock distance marker 1008 indicates a distance that meets the movement criteria for locking the media capture session state. In FIGS. 10C and 10D , video continues to be captured as the touch input 1002 continues to be detected.

[0218] In FIG. 10E , touch input 1002 has moved to the right and passed lock distance marker 1008. In this example, the movement criteria do not require liftoff of the touch input (e.g., 1002) to satisfy the movement criteria for transitioning the media capture session to a locked media capture state. Thus, in FIG. 10E , the media capture session (e.g., recording video) has been transitioned to a locked media capture state. For example, as shown in FIG. 10F , after liftoff of touch input 1002 at the location depicted in FIG. 10E , video capture continues (e.g., stop affordance 1010 is displayed, indicating that video is being recorded). Also shown in FIG. 10E , media capture lock affordance 1004 has been replaced with the display of image capture affordance 1012 (e.g., similar to image capture affordance 944), which can be used to capture media (e.g., a first type, such as a still image and / or a fixed duration clip) while recording a second type of media (e.g., video).

[0219] 10F , the device has ceased detecting touch input 1002 but continues capturing media (e.g., recording video) in a manner similar to that described above with respect to FIG. 9J . In this example, lift-off of touch input 1002 occurred while at the location shown in FIG. 10E (e.g., before reaching the location associated with media capture lock affordance 1004), but the media capture session would still continue because movement of touch input 1002 moved past lock distance marker 1008 (as represented by touch input indicator 1006). In some embodiments, the device does not display one or more of the touch input indicator (e.g., 1006), the lock distance marker (e.g., 1008), and the movement path indicator (e.g., 1005). For example, referring to FIG. 10E, the device may not display all (or none) of the touch input indicator 1006, the lock distance marker 1008, and the travel path indicator 1005 and still perform the same actions in response to lift-off as described with respect to FIGS. 10E and 10F.

[0220] In the above description, touch inputs 920, 930, 940, 970, and 1002 are indicated by different reference numerals. However, these touch inputs are intended to represent multiple potential gestures and / or results that can occur based on whether the touch input ultimately results in one or more gesture inputs. That is, each of touch inputs 920, 930, 940, 970, and 1002 represents a different possible result for a single touch input. For example, touch inputs 920 and 930 initiate at the same location and during the same device conditions and represent a common starting point for the touch input. However, one results in a tap gesture (920) and one results in a tap-and-hold gesture (930), resulting in different media capture actions. Thus, a user may have control over multiple media capture actions of the device based on the gesture the user performs with the touch input.

[0221] Additionally, the above examples are illustrative and not intended to be limiting with respect to various combinations of gestures, media actions, movement criteria, and threshold times. For example, while video capture is described with respect to a movement to the right, burst media capture may instead be performed in response to a movement to the right. Similarly, a movement to the left may result in the capture of a first type of media (e.g., a still image) instead of resulting in a burst media capture as described above. Those skilled in the art will recognize that various combinations of gestures, media actions, movement criteria, and threshold times may be combined and / or arranged in any combination to create a user interface in accordance with the scope of the present disclosure. All such interfaces are intended to be within the scope of the present disclosure.

[0222] 11 is a flow diagram illustrating a method for performing gesture-based media capture using an electronic device according to some embodiments. Method 1100 is performed on a device (e.g., 100, 300, 500, 800) having a display, a touch-sensitive surface, and one or more media capture components (e.g., image sensor, camera). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0223] As described below, method 1100 provides an intuitive way to perform gestural media capture. This method reduces the cognitive burden on a user performing media capture, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing users to perform media capture more quickly and efficiently conserves power and extends the time between battery charges.

[0224] An electronic device (e.g., 600, 900) displays (1102) (e.g., at 601, 904) a first user interface element (e.g., 910, 602, 1000) on a display (e.g., touchscreen display 902). The electronic device detects (1104) via the touch-sensitive surface (e.g., touchscreen display 902) a touch input (e.g., 603, 920, 930, 940, 970, 1002) that initiates a touch-down event (of an object on the touch-sensitive surface) at a location on the touch-sensitive surface (e.g., at location 910, location 602, location 1000) that corresponds to the first user interface element.

[0225] In response to detecting the touch input (1106), the electronic device (e.g., 600, 900) captures (1108) a first type of media (e.g., a single image and / or a video having a fixed duration) pursuant to a determination that the touch input (e.g., 920) was lifted from the touch-sensitive surface (e.g., 902) before the touch input (e.g., 920) met the movement criteria and before a threshold time (e.g., 1 second) (e.g., the time before video automatically begins recording) has elapsed since the touch input (e.g., a touch down event of the touch input on the touch screen display 902) was detected. For example, FIGS. 9B-9C illustrate device 900 capturing a first type of media pursuant to a determination that an example touch input 920 (a tap input gesture) was lifted from the touch screen 902 before the touch input met the movement criteria and before a threshold time has elapsed since the touch input was detected.

[0226] In some embodiments, determining that the touch input (e.g., 920) was lifted from the touch-sensitive surface (e.g., 902) before the touch input satisfied the movement criteria includes determining that the touch input was lifted before detecting a movement amount that exceeds a threshold (e.g., sufficient movement to transition (e.g., cause) the media capture session to transition from an unlocked media capture state to a locked media capture state). For example, the threshold amount may be a predetermined distance from the location of touch down (e.g., the media capture affordance) or a distance from the location of touch down (e.g., the media capture affordance) to a predetermined region / area / location. In some embodiments, determining that the touch input was lifted from the touch-sensitive surface before the touch input satisfied the movement criteria includes determining that the touch input was lifted before the touch input moved out of a first region (e.g., area, location) corresponding to the media capture affordance (e.g., 910, 602, 1000) and / or before the touch input moved into a second region (e.g., area, location) associated with continuing capture of a second type of media after detecting lift-off. For example, the first region can be the location of the media capture icon affordance 910 (or the stop affordance 934 if it replaces the media capture icon affordance 910 pursuant to starting recording of a second type of media), and the second region can be the media capture lock affordance 932. In a further example, the second region can be a region along a travel path indicator (e.g., 974, 1005) (e.g., a region past a particular point or distance from affordance 1000 or 1010, such as to the right of lock distance marker 1008 in FIG. 10E).

[0227] In some embodiments, capturing media includes one or more of recording one or more images (e.g., a single image, a video including a series of images) using one or more media capture components (e.g., an image sensor, a camera), recording audio (e.g., using one or more microphones) (e.g., during video recording), and storing a media item (e.g., a still image during recording, a recorded video) in a media library. For example, capturing a media item may include starting recording a video clip, stopping recording the video clip, and storing the video clip so that it is associated with (e.g., accessible to) a media library (e.g., a camera roll) associated with the device. As another example, "starting capture" may refer to a device starting to record a video. As another example, "stopping capture" may refer to a device ceasing to record a video (e.g., stopping the video recording). In some embodiments, a video captured as a result of "stopping capture" is stored in a media library (e.g., automatically following the video recording being stopped). In some embodiments, a device (e.g., 600, 900) captures the first type of media in response to detecting touchdown of touch input on the touch-sensitive surface. In some embodiments, the device captures the first type of media at any time during detection of the touch input (e.g., starting with touchdown) and during detection of liftoff of the touch input on the touch-sensitive surface. In some embodiments, the device captures the first type of media in response to liftoff of the touch input from the touch-sensitive surface. In some embodiments, the first type of media is captured (or begins capturing) before touchdown of the touch input on the touch-sensitive surface.For example, a device (e.g., 600, 900) may be recording prior to (e.g., in anticipation of) a touch input, and in response to the touch input, capture one or more media items that were captured or whose capture (e.g., for video) began before the touch input (e.g., 603, 920, 930, 940, 970, 1002) was actually detected by the device.

[0228] In response to detecting 1106 a touch input, in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input (e.g., 930) satisfies a movement criterion (e.g., before a threshold amount of movement is detected, before the touch input moves outside a first region corresponding to a capture affordance (e.g., 910, 602, 1000), and / or before the touch input moves into a second region associated with capture of a second type of media that continues after lift-off detection (e.g., at affordance 932)), and after a threshold time (e.g., 1 second) has elapsed since the touch input (e.g., a touch-down event on touchscreen 902) was detected, the electronic device (e.g., 600, 900) captures 1110 media of a second type (e.g., video with audio) having a duration based on the duration of the touch input on the touch-sensitive surface. For example, in response to exemplary tap-and-hold gesture input 930, device 900 captures video having a length based on (e.g., equal to) the duration of the touch input. In some embodiments, the duration of the second type of media is the same as the duration that the touch input was detected on the touch-sensitive surface. For example, if the touch input duration is 8 seconds, the resulting video is 8 seconds. In some embodiments, the duration of the second type of media is the duration from when the touch input exceeds the threshold time to liftoff of the touch input from the touch-sensitive surface. For example, if the touch input duration is 8 seconds and the threshold time is 1 second, the resulting video is 7 seconds. In some embodiments, the touch input includes movement that does not meet the movement criteria for transitioning the media capture session to a locked media capture state, and the device (e.g., 600, 900) begins capturing the second type of media anyway (e.g., in response to the touch input meeting the threshold time or in response to movement of the touch input (e.g., a particular amount of movement in a particular direction)).In some embodiments, the touch input is not detected for a threshold time before the touch input meets a movement criterion (e.g., the same as or different from the criteria that enable the media capture lock state) that causes the device (e.g., 600, 900) to begin capturing media of the second type (e.g., in response to movement of the touch input (e.g., a minimal amount) toward the media capture lock affordance). 9D-9F show device 900 capturing media of the second type pursuant to a determination that example touch input 930 was lifted from the touch-sensitive surface before the touch input met the movement criterion and after the threshold time has elapsed since the touch input was detected, with the duration based on the duration of the touch input on the touch-sensitive surface.

[0229] In response to detecting the touch input (1106), pursuant to a determination that the touch input (e.g., 940, 603) meets the movement criteria and includes movement in a first direction (e.g., as shown in FIGS. 9G-9I) (e.g., the touch input includes two or more threshold amounts of movement (e.g., movement from the location of media capture affordance 910 to the location of media capture lock affordance 932) in the first direction (e.g., toward a first edge of the touch-sensitive surface, from media capture affordance 910 toward media capture lock affordance 932), or when the touch input is moving within a second region associated with capturing a second type of media that continues after detecting lift-off (e.g., at affordance 932), the electronic device (e.g., 600, 900) initiates capture of a second type of media (e.g., video) and continues capturing the second type of media after detecting lift-off of the touch input from the touch-sensitive surface (1112). 9G-9J illustrate device 900 initiating and continuing (after liftoff) capture of a second type of media pursuant to a determination that example touch input 940 meets the movement criteria (e.g., liftoff at the location of affordance 932) and includes movement in a first direction (e.g., toward affordance 932). In a further example, FIGS. 10A-10F illustrate example touch input 1002 that meets the movement criteria (e.g., movement past lock distance marker 1008 in the first direction) and includes movement in a first direction (e.g., to the right). In some embodiments, the device performs the actions described above in response to a touch input that meets the movement criteria and includes movement in a first direction, regardless of whether a threshold time has elapsed and / or when the movement of the touch input began or ended relative to the threshold time. For example, device 900 may begin recording video in response to a touch input (e.g., where the threshold time is 1 second), and two minutes after detecting that the touch input is a stationary tap and hold (and recording the video), the device may detect that the touch input has moved to meet the lock criteria for the media capture session, and in response, the device will continue recording after liftoff.

[0230] In some embodiments, continuing to capture media includes transitioning the media capture session from an unlocked media capture state to a locked media capture state (e.g., also referred to as a “locked media capture session state”). In some embodiments, the electronic device (e.g., 600, 900) displays a user interface element (e.g., marker 1008, affordance 932 or 1004) or other graphical indication of the amount of touch input movement that satisfies the movement criterion. In some embodiments, the device displays two or more user interface elements. In some embodiments, each user interface element can correspond to the same or different movement criterion (e.g., associated with a different media capture-related action). For example, the device transitions the media capture session to the media capture state and therefore displays a graphical user interface element (e.g., 932, 1008) that indicates an area (e.g., the area of ​​932, the area to the right of 1008) that indicates the amount of movement that continues after liftoff of the touch input (e.g., 1002). In some embodiments, the movement criterion is movement less than (e.g., a portion of) the distance between a first user interface element (e.g., 1000) and another user interface element (e.g., 1004) (e.g., as shown and described with respect to FIGS. 10A-10F). For example, movement of touch input 1002 at least 50% of the distance from exemplary first user interface element 1000 to exemplary user interface element 1004 and liftoff may be sufficient to continue capturing media after liftoff of the touch input.

[0231] Using one or more combinations of a movement criterion and a threshold time to determine whether to capture a first type of media, a second type of media having a particular duration, and continue capturing the second type of media provides additional control options without cluttering the user interface (e.g., GUI) with additional displayed controls. Providing additional control options without cluttering the UI with additional displayed controls enhances device usability, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and also reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently. Furthermore, a user can start a video recording using a single technique and, after starting the video recording, perform different continuation gestures that indicate whether the device should end the recording quickly or extend the recording. Furthermore, a user can start a recording quickly and, after starting the recording, decide whether to capture a photo, a short video, or a long video. This also reduces the number of controls that need to be displayed on the display (e.g., not needing both a still photo button and a video button, or three different buttons for different types of media). Saving screen space is especially important when the rest of the screen may be used to display a camera preview of the content the user is capturing.

[0232] Using one or more combinations of movement criteria and a threshold time to determine whether to capture a first type of media, a second type of media having a particular duration, and the second type of media that continues to be captured reduces the number of inputs required to perform one or more of these operations when initiated from a particular user interface. Reducing the number of inputs required to perform operations enhances usability of the device and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0233] Using the movement criteria of the touch input on a user interface element can be used to trigger / initiate capture of a (e.g., second) type of media to control whether that type of media continues to be captured after liftoff of the captured touch input, providing additional control options without cluttering the user interface (e.g., GUI) with additional displayed controls. Providing additional control options without cluttering the UI with additional displayed controls enhances usability of the device and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0234] In some embodiments, pursuant to a determination that the touch input (e.g., 930 in FIGS. 9D-9F ) was lifted from the touch-sensitive surface (e.g., 902) before the touch input met the movement criteria and after a threshold time had elapsed since the touch input was detected, the electronic device (e.g., 600, 900) stops capturing the second type of media (e.g., video) (e.g., stops recording the video and stores the resulting video in a media library) (e.g., as shown in FIGS. 9D-9F ) in response to detecting lift-off of the touch input (e.g., the end of the recorded video duration occurred at the lift-off).

[0235] In some embodiments, the first type of media has a duration that is independent of the duration of the touch input (e.g., 920) on the touch-sensitive surface (e.g., 902). For example, the first type of media may be a video having a fixed length (e.g., 3 seconds long) that is not affected by the duration of the touch input (e.g., on touchscreen display 902), or a still photograph accompanied by another photograph or sequence of media, such as audio content, for a predetermined duration before and / or after the still photograph.

[0236] In some embodiments, the movement criterion is a first movement criterion, and in response to detecting (1106) the touch input (e.g., 970), the electronic device (e.g., 600, 900) detects a media capture of a first type of media (e.g., a still photograph) in response to determining that the touch input satisfies the second movement criterion (e.g., movement outside of the area / location of the media capture affordance 910 in FIGS. 9M-9N) and includes movement in a second direction (e.g., to the left of the location of the media capture affordance 910 (or stop affordance 934) in FIGS. 9M-9N) that is different from the first direction (e.g., to the right in FIGS. 9M-9N). The touch-sensitive surface begins capturing (1114) a sequence of media items (e.g., begins burst image capture mode), and the number of captured media items is determined based on the duration of the touch input on the touch-sensitive surface (e.g., the duration of the touch input while exceeding a threshold distance from the location of a user interface element (e.g., 910, 602, 1000, 934, 605) or while the touch input is in a predefined area associated with capturing a sequence of media items of the first type of media (e.g., the area to the left of affordance 910, 934, 602, 1000, or 605)). For example, the touch input can meet the second movement criterion if it includes a movement amount greater than a threshold (e.g., sufficient to enable burst mode) in a second direction different from the first direction (e.g., to the right in FIGS. 9M-9N) (e.g., oppositely, toward a second edge of the touch-sensitive surface) or includes movement into a predefined region associated with capturing a sequence of media items of a first type of media (e.g., the region to the left of media capture affordance 910 in FIGS. 9M-9N). Capturing a sequence of media items is sometimes referred to as burst mode, burst image capture mode, continuous shooting mode, etc.

[0237] In some embodiments, movement that satisfies the second movement criterion occurs before a threshold time. For example, the movement criterion may require that movement in the second direction must occur within the threshold time for the device to begin capturing a sequence of media items. In some embodiments, the movement begins before the threshold time. For example, the movement criterion may require that movement in the second direction must begin before a threshold time (e.g., even if the movement ends after the threshold time) for the device to begin capturing a sequence of media items. In some embodiments, the second movement criterion may be satisfied by movement that begins after a threshold duration has elapsed. In some embodiments, the second movement criterion includes any movement (e.g., any movement in a particular (e.g., second) direction). In some embodiments, the second movement criterion includes a threshold amount of movement (e.g., a minimum distance) (e.g., in the second direction). In some embodiments, the second movement criterion includes a requirement that the touch input be moving outside of a first region corresponding to a media capture affordance (e.g., 910, 602, 1000). In some embodiments, the second movement criterion includes a requirement that the touch input be moving within a second region (e.g., location) associated with capturing a sequence of media items of the first type. In some embodiments, the first movement criterion and the second movement criterion are the same but in different directions (e.g., same distance requirement but opposite directions).

[0238] Using one or more combinations of a first type of media, a second type of media having a particular duration, the second type of media that continues to be captured, and a movement criterion and a threshold time to determine whether to capture a sequence of first type media items provides additional control options without cluttering the user interface (e.g., GUI) with additional displayed controls. Providing additional control options without cluttering the UI with additional displayed controls enhances usability of the device and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0239] Using one or more combinations of movement criteria and a threshold time to determine whether to capture a first type of media, a second type of media having a particular duration, and the second type of media that continues to be captured, and a sequence of first type media items, when starting from a particular user interface, reduces the number of inputs required to perform one or more of these operations. Reducing the number of inputs required to perform operations enhances usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0240] In some embodiments, pursuant to a determination that the touch input (e.g., 970) satisfies the second movement criterion and includes movement (e.g., sufficient to enable burst mode) in a second direction different from the first direction (e.g., opposite thereto, toward a second edge of the touch-sensitive surface), the electronic device (e.g., 600, 900) ceases capturing the sequence of media items of the first type of media (e.g., the end of the duration occurs at the time of lift-off) in response to detecting lift-off of the touch input (e.g., in response to lift-off of 970 in FIG. 9P). For example, in response to lift-off of the touch input 970, the device 900 stops performing burst image capture (e.g., recording still images in rapid succession) (e.g., stores the captured images).

[0241] In some embodiments, while continuing to capture the sequence of media items of the first type of media (e.g., as shown in FIGS. 9N-9P), the electronic device (e.g., 600, 900) displays on the display (e.g., 902) the number of media items of the first type of media (e.g., 972 in FIG. 9N, 976 in FIGS. 9O-9P) that have been captured since the start of the capture of the sequence of media items (e.g., the number of media items increases as the sequence capture continues). In some embodiments, the number of media items is displayed at the location of the first user interface element on the display (e.g., the location of the media capture affordance 910 as shown in FIG. 9M). In some embodiments, the number of displayed media items is based on the number of media items that have been captured since detecting the touch input.

[0242] In some embodiments, displaying on the display (e.g., 902) the number of media items of the first type of media that have been captured since the beginning of the capture of the sequence of media items includes displaying on the display the number of media items of the first type of media that the electronic device (e.g., 600, 900) captured at an initial position on the display (e.g., location 972 in FIG. 9N). Pursuant to determining that the touch input (e.g., 970) includes movement to a location on the touch-sensitive surface corresponding to the initial position on the display (e.g., touch input 970 moves as shown in FIGS. 9N-9O), the electronic device displays on the display the number of media items of the first type of media (e.g., 976 in FIGS. 9O-9P) at the location of the first user interface element on the display (e.g., in FIG. 9O, 976 appears at the same location as media capture affordance 910 shown in FIG. 9M). The electronic device ceases to display the number of media items of the first type of media in the initial location on the display (eg, 972 is no longer displayed in Figures 9O-9P).

[0243] Improved visual feedback prevents information from being obscured by the touch input by displaying the number of media items captured at the new location as the touch input moves towards the initial position. Improved feedback improves usability of the device (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device) and provides a more efficient user-device interface, thereby allowing the user to use the device more quickly and efficiently, further reducing power usage and improving the device's battery life.

[0244] In some embodiments, the electronic device (e.g., 600, 900) displays (1116) a second user interface element (e.g., an icon, affordance, or distance marker) (e.g., media capture lock affordance 932, media capture lock affordance 1004, lock distance marker 1008) on the display (e.g., 902), and movement of the touch input (e.g., 940, 603) from the first user interface element (e.g., location 910, location 934, location 1000, location 602, location 605) to the second user interface element (e.g., 932, 1004, 1008) satisfies a movement criterion (e.g., the movement criterion includes detecting a threshold amount of movement toward (e.g., in a direction) the second user interface element or movement into a first region (e.g., a region of the second user interface element) associated with capturing a second type of media that continues to be captured after lift-off). In some embodiments, lift-off of the touch input at a location corresponding to the second user interface element (e.g., in the area to the right of marker 1008, at locations 932 or 1004) is required so that the second type of media continues to be recorded after lift-off.

[0245] Displaying user interface elements that meet the movement criteria provides improved visual feedback regarding the input movement required to perform an action. Providing improved feedback improves usability of the device (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device) and provides a more efficient user-device interface, thereby allowing the user to use the device more quickly and efficiently, and additionally reduces power usage and improves the device's battery life.

[0246] In some embodiments, after detecting liftoff of the touch input (e.g., 940, 603) from the touch-sensitive surface (e.g., 902), in accordance with continuing to capture the second type of media, the electronic device (e.g., 600, 900) changes the second user interface element (e.g., 932 in FIG. 9I) to a third user interface element (e.g., 944 in FIG. 9I) that is different from the second user interface element. In some embodiments, the second user interface element changes in response to movement of the touch input. In some embodiments, the second user interface element changes in response to liftoff of the touch input (e.g., at the location of the media capture lock affordance). In some embodiments, the second user interface element changes in response to the media capture session transitioning to a locked media capture state.

[0247] In some embodiments, in response to an interaction between the touch input (e.g., 940, 603) and a location on the touch-sensitive surface corresponding to the second user interface element (e.g., the location of user interface element 932), the second user interface element (e.g., 932) changes to a third user interface element (e.g., 944). For example, the interaction can occur when the touch input 940 is dragged to the location of media capture lock affordance 932. In a further example, the interaction can occur when the touch input 940 is lifted off while at the location of media capture lock affordance 932.

[0248] In some embodiments, the touch input (e.g., 940, 603) is a first touch input, and while continuing to capture media of a second type (e.g., video), the electronic device (e.g., 600, 900) detects a second touch input (e.g., 960) via the touch-sensitive surface (e.g., 902) at a location on the touch-sensitive surface that corresponds to a third user interface element (e.g., 944). In response to detecting the second touch input, the electronic device captures media of the first type (e.g., takes a still photograph) (e.g., while continuing to capture media of the second type).

[0249] In some embodiments, while detecting a touch input (e.g., 940, 603) on the touch-sensitive surface (e.g., immediately after touchdown or immediately after movement of the touch input in a first direction), the electronic device (e.g., 600, 900) displays (1118) on the display (e.g., 902) a directional indicator (e.g., 943, 975, 1005, 604a, 604b) from the location of the first user interface element on the display (e.g., location 910, location 934, location 1000, location 602, location 605) to the first direction.

[0250] In some embodiments, the directional indicator (e.g., 943, 975, 1005, 604a, 604b) may include one or more of a directional line (e.g., solid, dotted, dashed), arrow, animation, and other graphical representation (e.g., to meet the movement criteria). In some embodiments, the directional indicator indicates the amount of movement (e.g., movement path indicator 1005 with lock distance marker 1008) required to meet the movement criteria. In some embodiments, the directional indicator indicates the area or location (e.g., movement path indicator 1005 with lock distance marker 1008) to which the touch input needs to be moved (e.g., with or without requiring liftoff of the touch input) to meet the movement criteria.

[0251] Displaying a directional indicator provides improved visual feedback regarding the input movement required to perform an action. Improved feedback improves usability of the device (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors) and provides a more efficient user-device interface, thereby allowing the user to use the device more quickly and efficiently, which in turn reduces power usage and improves the device's battery life.

[0252] In some embodiments, a directional indicator (e.g., 943, 975, 1005, 604a, 604b) is displayed pursuant to a determination that the touch input (e.g., 940, 603) includes movement in a first direction. For example, the movement path indicator 943 is not displayed until the touch input 940 begins to move (e.g., toward the media capture lock affordance 932). In some embodiments, the device displays the movement path indicator in response to detecting the touch input or in response to detecting the touch input for a threshold time.

[0253] In some embodiments, after detecting liftoff of the touch input from the touch-sensitive surface (e.g., 902) (e.g., liftoff of 940, liftoff of 603 in FIGS. 9I-9J), the electronic device (e.g., 600, 900) changes (1120) the first user interface element (e.g., 910, 602, 1000) to a fourth user interface element (e.g., 934 in FIG. 9J, 605 in FIGS. 6D-6F) in accordance with continuing to capture media of a second type (e.g., video). In some embodiments, the first user interface element changes to the fourth user interface element in accordance with starting to capture media of a second type (e.g., as shown in FIG. 9H). In some embodiments, the first user interface element changes to the fourth user interface element in accordance with movement of the touch input (e.g., out of the area corresponding to the first user interface element (e.g., as shown in FIGS. 10A-10D)). In some embodiments, the electronic device changes the first user interface element to a fourth user interface element in response to lift-off of the touch input.

[0254] Modifying the user interface elements in accordance with continuing to capture the second type of media provides relevant alternative control options without cluttering the user interface (e.g., GUI) with additional displayed controls. Providing additional control options without cluttering the UI with additional displayed controls enhances usability of the device and makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0255] In some embodiments, the touch input (e.g., 940, 603) is a first touch input, and after detecting lift-off of the touch input (e.g., 940, 603) from the touch-sensitive surface (e.g., 902), while continuing to capture media of the second type, the electronic device (e.g., 600, 900) detects a third touch input (e.g., 950, 606) through the touch-sensitive surface at a location on the touch-sensitive surface that corresponds to a fourth user interface element (e.g., 934, 605). In response to detecting the third touch input, the electronic device ceases capturing media of the second type (e.g., stops recording video and stores the recorded video in a media library).

[0256] In some embodiments, the first type of media is one or more of a still image and a video (eg, a video clip having a fixed duration and / or a duration independent of the duration of the touch input).

[0257] In some embodiments, capturing the first type of media by one or more media capture components (e.g., camera, image sensor) occurs in response to detecting touch input (e.g., 603, 920, 930, 940, 970, 1002) on the touch-sensitive surface (e.g., touch down on 902) or in response to lift-off of the touch input from the touch-sensitive surface. In some embodiments, capturing the first type of media occurs while touch input is detected on the touch-sensitive surface.

[0258] In some embodiments, the second type of media is video (eg, having a duration related to the length of the touch input, or until a stop affordance (eg, 934, 605) is selected).

[0259] In some embodiments, capturing the second type of media by one or more media capture components (e.g., camera, image sensor) includes initiating video recording in response to touch input being detected on the touch-sensitive surface for more than a threshold time (e.g., 1 second).

[0260] In some embodiments, pursuant to a determination that the touch input (e.g., 930) was lifted from the touch-sensitive surface before the touch input met the movement criteria (e.g., the media capture session was not in a locked media capture state) and after a threshold time (e.g., 1 second) had elapsed since the touch input was detected (e.g., the device had started recording video), the electronic device (e.g., 600, 900) captures a first type of media (e.g., a still image) and discards the captured first type of media (e.g., deletes the first type of media before or after adding it to a media library). For example, the electronic device may capture a first type of media item pursuant to receiving the touch input (e.g., in response to touching down of the touch input 930). After the touch input met the criteria for capturing a second type of media, the device may discard the captured first type of media (e.g., because characteristics of the touch input gesture indicate that capture of the first media item was not still intended).

[0261] Capturing first media but automatically deleting it so that it is available in case the user lifts off conserves storage space when the user begins recording other content (e.g., second media such as video) that indicates the first media (e.g., photos) is not needed. Additionally, automatically discarding first media based on other media being captured (e.g., beginning to record video) reduces the number of user inputs required to discard the media. Reducing the number of inputs required to perform actions enhances device usability and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing device power usage and improving battery life by allowing the user to use the device more quickly and efficiently.

[0262] It should be noted that the process details described above with respect to method 1100 (e.g., FIG. 11) are also applicable in a similar manner to the methods described below / above. For example, method 1100 optionally includes one or more of the features of the various methods described above with reference to method 700. For the sake of brevity, these details will not be repeated below.

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

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

[0265] As mentioned above, one aspect of the present technology is the collection and use of data available from various sources to perform gesture-based media capture. The present disclosure contemplates that, in some examples, this collected data may include personal information data that uniquely identifies a particular person or that can be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records regarding a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth date, or any other identifying or personal information.

[0266] This disclosure recognizes that the use of such personal information data in the present technology may be for the benefit of the user. Moreover, other uses of personal information data that benefit the user are also contemplated by this disclosure. For example, health and fitness data may be used to provide insight into the user's overall wellness or as proactive feedback to individuals using the technology to pursue wellness goals.

[0267] This disclosure contemplates that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to robust privacy policies and / or privacy practices. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining the strict confidentiality of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use changes. Personal information from users should be collected for the entity's lawful and legitimate use and should not be shared or sold except for those lawful uses. Furthermore, such collection / sharing should be carried out after the user's informed consent is obtained. Furthermore, such entities should consider taking all necessary measures to protect and secure access to such personal information data and to ensure that others with access to that personal information data comply with their privacy policies and procedures. Furthermore, such entities may be able to undergo third-party assessments to demonstrate their adherence to widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal data collected and / or accessed and should comply with applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, the 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), while health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained with respect to different types of personal data in each country.

[0268] Notwithstanding the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, in the case of a media capture application, the present technology may be configured to allow a user to select "opt-in" or "opt-out" of participating in the collection of personal information data during registration for the service or at any time thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notice regarding the access or use of personal information. For example, the user may be notified upon downloading an app that will access the user's personal information data, and then again immediately before the app accesses the user's personal information data.

[0269] Furthermore, it is the intent of this disclosure that personal information data should be managed and handled in a manner that minimizes the risk of unintentional or unauthorized access or use. Risk can be minimized by limiting data collection and deleting data when it is no longer needed. Furthermore, where applicable, de-identification of data can be used to protect user privacy in certain health-related applications. De-identification can be facilitated, where appropriate, by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data at a city level rather than a street address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.

[0270] Thus, while this disclosure broadly encompasses the use of personal information data to implement one or more various disclosed embodiments, this disclosure also contemplates that the various embodiments may be implemented without requiring access to such personal information data. That is, various embodiments of the present technology are not rendered inoperable by the absence of all or part of such personal information data. For example, media content may be captured and stored by inferring a user's intent based only on a minimal amount of non-personal information or personal information, such as content requested by a device associated with the user, other non-personal information available to a media capture interface application, or publicly available information.

Claims

1. In an electronic device having a display, a touch-sensitive surface, and one or more media capture components, Displaying a first user interface element at a first location on the touch-sensitive surface on the display; Detecting a touch input via the touch-sensitive surface beginning at the first location on the touch-sensitive surface corresponding to the first user interface element; In response to detecting a first portion of the touch input, displaying a second user interface element at a second location on the touch-sensitive surface that is different from the first location; In response to detecting the touch input, capturing a first type of media in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input meets a movement criterion and before a threshold time has elapsed since the touch input was detected; capturing a second type of media having a duration based on a duration of the touch input on the touch-sensitive surface in accordance with a determination that the touch input was lifted from the touch-sensitive surface before the touch input met the movement criterion and after the threshold time has elapsed since the touch input was detected; according to a determination that the touch input satisfies the movement criterion and includes movement in a first direction, wherein determining that the movement criterion is satisfied includes determining that the touch input includes movement of the touch input from the first user interface element to the second user interface element; initiating capture of the second type of media and continuing capture of the second type of media after detecting lift-off of the touch input from the touch-sensitive surface; displaying a third user interface element at the second location, the third user interface element being different from the second user interface element, without displaying the second user interface element at the second location while continuing to capture the second type of media after detecting lift-off of the touch input from the touch-sensitive surface; A computer-implemented method comprising:

2. in response to a determination that the touch input was lifted from the touch-sensitive surface before the touch input met the movement criterion and after the threshold time has elapsed since the touch input was detected, ceasing capture of the second type of media in response to detecting lift-off of the touch input. The computer-implemented method of claim 1 further comprising:

3. The computer-implemented method of claim 1 , wherein the first type of media has a duration that is independent of the duration of the touch input on the touch-sensitive surface.

4. The movement criterion is a first movement criterion, and the computer-implemented method, in response to detecting the touch input, comprises: Initiating capture of a sequence of media items of the first type of media in accordance with a determination that the touch input meets a second movement criterion and includes movement in a second direction different from the first direction, wherein a number of media items to be captured is determined based on the duration of the touch input on the touch-sensitive surface. The computer-implemented method of claim 1 further comprising:

5. in response to determining that the touch input satisfies the second movement criterion and includes movement in a second direction different from the first direction; ceasing to capture the sequence of media items of the first type of media in response to detecting lift-off of the touch input. The computer-implemented method of claim 4 further comprising:

6. while continuing to capture the sequence of media items of the first type of media; displaying on the display the number of media items of the first type that have been captured since the start of capturing the sequence of media items, the number of media items being displayed in place of the first user interface element on the display; The computer-implemented method of claim 4 further comprising:

7. Displaying on the display the number of media items of the first type captured since the start of capture of the sequence of media items comprises: displaying on the display the number of media items of the first type captured at an initial position on the display; upon determining that the touch input includes movement to a location on the touch-sensitive surface corresponding to the initial position on the display; displaying, on the display, a number of the media items of the first type of media at the location of the first user interface element on the display; ceasing to display the number of media items of the first type of media in the initial position on the display; and 7. The computer-implemented method of claim 6, comprising:

8. 2. The computer-implemented method of claim 1, wherein the second user interface element changes to the third user interface element in response to an interaction between the touch input and the second location on the touch-sensitive surface that corresponds to the second user interface element.

9. the touch input is a first touch input; The computer-implemented method further comprises, while continuing to capture the second type of media: Detecting a second touch input via the touch-sensitive surface at the second location on the touch-sensitive surface corresponding to the third user interface element; capturing the first type of media in response to detecting the second touch input; The computer-implemented method of claim 1 further comprising:

10. displaying, on the display, a directional indicator from a location of the first user interface element on the display to the first direction while detecting the touch input on the touch-sensitive surface. The computer-implemented method of claim 1 further comprising:

11. The computer-implemented method of claim 10 , wherein the directional indicator is displayed pursuant to a determination that the touch input includes movement in the first direction.

12. displaying a fourth user interface element, different from the first user interface element, in the first location and selectable to perform an action without displaying the first user interface element while continuing to capture the second type of media after detecting lift-off of the touch input from the touch-sensitive surface. The computer-implemented method of claim 1 further comprising:

13. the touch input is a first touch input, and the computer-implemented method includes: while continuing to capture the second type of media after detecting lift-off of the touch input from the touch-sensitive surface, detecting a third touch input through the touch-sensitive surface at a location on the touch-sensitive surface corresponding to the fourth user interface element; ceasing capture of the second type of media in response to detecting the third touch input; The computer-implemented method of claim 12 further comprising:

14. The computer-implemented method of claim 1 , wherein the first type of media is one or more of a still image and a video.

15. 15. The computer-implemented method of claim 14, wherein capturing the first type of media with the one or more media capture components occurs in response to detecting the touch input on the touch-sensitive surface or in response to lift-off of the touch input from the touch-sensitive surface.

16. The computer-implemented method of claim 1 , wherein the second type of media is video.

17. 17. The computer-implemented method of claim 16, wherein capturing the second type of media with the one or more media capture components includes initiating recording of the video in response to the touch input being detected on the touch-sensitive surface for more than the threshold time.

18. in response to a determination that the touch input was lifted from the touch-sensitive surface before the touch input met the movement criterion and after a threshold time has elapsed since the touch input was detected, capturing the first type of media; discarding the captured media of the first type; The computer-implemented method of claim 1 further comprising:

19. displaying the second user interface element at the second location on the touch-sensitive surface that is different from the first location in response to detecting the touch input and in accordance with a determination that the touch input is maintained on the touch-sensitive surface after the threshold time has elapsed since the touch input was detected. The computer-implemented method of claim 1 further comprising:

20. in response to detecting the touch input and before the threshold time has elapsed since the touch input was detected, capturing the second type of media in accordance with determining that the touch input meets a movement criterion. The computer-implemented method of claim 1 further comprising:

21. A computer program causing a computer to carry out the method according to any one of claims 1 to 20.

22. a memory for storing the computer program of claim 21; one or more processors capable of executing the computer programs stored in the memory; An electronic device comprising:

23. Means for carrying out the method according to any one of claims 1 to 20, An electronic device comprising:

Images