MULTI-TYPE MEDIA USER INTERFACE

Information

  • Patent Application
  • 20240361898
  • Publication Number
    20240361898
  • Date Filed
    April 10, 2024
    7 months ago
  • Date Published
    October 31, 2024
    a month ago
Abstract
The present disclosure generally relates to capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras. In some embodiments, a method for capturing and/or editing media that can be presented as multiple different media types is described. In some embodiments, a method for capturing and/or editing media that was captured using multiple different cameras is described. In some embodiments, a method for selecting a subset of cameras with which to capture media is described.
Description
FIELD

The present disclosure relates generally to computer user interfaces, and more specifically to techniques and user interfaces for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras.


BACKGROUND

Many electronic devices incorporate one or more cameras for capturing visual media items, such as still photos, videos, and the like. Such devices typically include user interfaces to allow users to configure one or more parameters of media capture and to perform the media capture itself. Such devices may also provide user interfaces to edit or modify media, after capture.


BRIEF SUMMARY

Some techniques for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Some existing techniques require users to select a single media type (e.g., photo or video) prior to capturing media, with the resulting media remaining fixed to that media type, after capture and/or requiring extensive modification (e.g., via dedicated editing programs) to change from one media type to another. Thus, existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.


Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras. Such methods and interfaces optionally complement or replace other methods for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Such methods can also reduce the cognitive burden on a user associated with having to select a single media type, while also reducing the risk that a transient event is captured using an incorrect media type (e.g., capturing a still photo for an action-oriented event where a user might prefer video).


In some embodiments, an exemplary method is described. The method is performed at a computer system that is in communication with a display generation component and one or more input devices. The method includes: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; while displaying the editing user interface, detecting, via the one or more input devices, a first input; and in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, an exemplary non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; while displaying the editing user interface, detecting, via the one or more input devices, a first input; and in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, an exemplary transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; while displaying the editing user interface, detecting, via the one or more input devices, a first input; and in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, a computer system that configured to communicate with a display generation component and one or more input devices is described. The computer system includes one or more processors and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; while displaying the editing user interface, detecting, via the one or more input devices, a first input; and in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, a computer system that configured to communicate with a display generation component and one or more input devices is described. The computer system includes: means for displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; means for, while displaying the editing user interface, detecting, via the one or more input devices, a first input; and means for, in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, a computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media; while displaying the editing user interface, detecting, via the one or more input devices, a first input; and in response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.


In some embodiments, an exemplary method is described. The method is performed at a computer system that is in communication with a display generation component, one or more input devices a first camera, and a second camera. The method includes: detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; detecting, via the one or more input devices, a second input directed to the selectable user interface object; in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, an exemplary non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, one or more input devices a first camera, and a second camera is described. The programs including instructions for: detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; detecting, via the one or more input devices, a second input directed to the selectable user interface object; in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, an exemplary transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, one or more input devices a first camera, and a second camera is described. The programs including instructions for: detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; detecting, via the one or more input devices, a second input directed to the selectable user interface object; in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, a computer system that configured to communicate with a display generation component, one or more input devices a first camera, and a second camera is described. The computer system includes one or more processors and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; detecting, via the one or more input devices, a second input directed to the selectable user interface object; in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, a computer system that configured to communicate with a display generation component, one or more input devices a first camera, and a second camera is described. The computer system includes: means for detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; means for, in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; means for, subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; means for, detecting, via the one or more input devices, a second input directed to the selectable user interface object; means for, in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and means for, detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and means for, in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, a computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, one or more input devices a first camera, and a second camera is described. The one or more programs including instructions for: detecting, via the one or more input devices, a first input that corresponds to a request to capture media corresponding to at least a portion of a field of view of at least one of the first camera and the second camera; in response to detecting the first input, capturing a media item corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing first data from the first camera and second data from the second camera; subsequent to capturing the media item, displaying, via the display generation component, a selectable user interface object for editing the media item; detecting, via the one or more input devices, a second input directed to the selectable user interface object; in response to detecting the second input directed to the selectable user interface object, displaying an editing user interface that includes a first representation of the media item based primarily on the first data from the first camera and a camera option selectable user interface object for displaying a second representation of the media item that is based primarily on the second data from the second camera; and detecting, via the one or more input devices, a third input directed to the camera option selectable user interface object; and in response to detecting the third input: ceasing to display the first representation of the media item that is based primarily on the first data from the first camera; and displaying the second representation of the media item that is based primarily on the second data from the second camera.


In some embodiments, an exemplary method is described. The method is performed at a computer system that is in communication with a display generation component, one or more input devices and a plurality of cameras that includes at least three cameras. The method includes: detecting, via the one or more input devices, an input directed to capturing a media item; in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


In some embodiments, an exemplary non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, one or more input devices and a plurality of cameras that includes at least three cameras is described. The programs including instructions for: detecting, via the one or more input devices, an input directed to capturing a media item; in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


In some embodiments, an exemplary transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, one or more input devices and a plurality of cameras that includes at least three cameras is described. The programs including instructions for: detecting, via the one or more input devices, an input directed to capturing a media item; in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


In some embodiments, a computer system that configured to communicate with a display generation component, one or more input devices and a plurality of cameras that includes at least three cameras is described. The computer system includes one or more processors and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: detecting, via the one or more input devices, an input directed to capturing a media item; in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


In some embodiments, a computer system that configured to communicate with a display generation component, one or more input devices and a plurality of cameras that includes at least three cameras is described. The computer system includes: means for, detecting, via the one or more input devices, an input directed to capturing a media item; means for, in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


In some embodiments, a computer program product, comprising one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs including instructions for: detecting, via the one or more input devices, an input directed to capturing a media item; in response to detecting the input directed to capturing the media item: in accordance with a determination that a first set of context criteria are met, capturing the media item using a first subset of cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras; and in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria, capturing the media item using a second subset of cameras of the plurality of cameras, wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different.


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


Thus, devices are provided with faster, more efficient methods and interfaces for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras.





DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.



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



FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.



FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.



FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.



FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.



FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.



FIG. 5A illustrates a personal electronic device in accordance with some embodiments.



FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.



FIGS. 6A-6S illustrate exemplary user interfaces for capturing and/or editing media that can be presented as multiple different media types and/or that was captured using multiple different cameras.



FIG. 7 is a flow diagram of a method for capturing and/or editing media that can be presented as multiple different media types.



FIG. 8 is a flow diagram of a method for capturing and/or editing media that was captured using multiple different cameras.



FIGS. 9A-9F illustrate exemplary user interfaces for selecting a subset of cameras with which to capture media.



FIG. 10 is a flow diagram of a method for selecting a subset of cameras with which to capture media.





DESCRIPTION OF EMBODIMENTS

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


There is a need for electronic devices that provide efficient methods and interfaces for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras. In particular, there is a need for electronic devices for capturing and/or editing media that can be presented as multiple different media types, for capturing and/or editing media that was captured using multiple different cameras, and/or for selecting a subset of cameras with which to capture media. Such techniques can reduce the cognitive burden on a user who capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.


Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of exemplary devices for performing the techniques for capturing and/or editing media items that can correspond to multiple media types and/or multiple cameras. FIGS. 6A-6S illustrate exemplary user interfaces for capturing and/or editing media that can be presented as multiple different media types and/or that was captured using multiple different cameras. FIG. 7 is a flow diagram illustrating methods for capturing and/or editing media that can be presented as multiple different media types in accordance with some embodiments. FIG. 8 is a flow diagram of a method for capturing and/or editing media that was captured using multiple different cameras in accordance with some embodiments. The user interfaces in FIGS. 6A-6S are used to illustrate the processes described below, including the processes in FIGS. 7 and 8. FIGS. 9A-9F illustrate exemplary user interfaces for selecting a subset of cameras with which to capture media. FIG. 10 is a flow diagram illustrating methods for selecting a subset of cameras with which to capture media in accordance with some embodiments. The user interfaces in FIGS. 9A-9F are used to illustrate the processes described below, including the processes in FIG. 10.


The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.


In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.


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


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


The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.


Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.


In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.


The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.


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


Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.


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


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


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


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


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


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


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


I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and/or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and/or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independently of an input element that is a part of the device) and is based on detected motion of a portion of the user's body through the air including motion of the user's body relative to an absolute reference (e.g., an angle of the user's arm relative to the ground or a distance of the user's hand relative to the ground), relative to another portion of the user's body (e.g., movement of a hand of the user relative to a shoulder of the user, movement of one hand of the user relative to another hand of the user, and/or movement of a finger of the user relative to another finger or portion of a hand of the user), and/or absolute motion of a portion of the user's body (e.g., a tap gesture that includes movement of a hand in a predetermined pose by a predetermined amount and/or speed, or a shake gesture that includes a predetermined speed or amount of rotation of a portion of the user's body).


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


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


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


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


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


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


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


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


Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.


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


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


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


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


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


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


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


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


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


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


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


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


Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.


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


In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.


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


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


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


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

    • Contacts module 137 (sometimes called an address book or contact list);
    • Telephone module 138;
    • Video conference module 139;
    • E-mail client module 140;
    • Instant messaging (IM) module 141;
    • Workout support module 142;
    • 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;
    • Widget modules 149, which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
    • Widget creator module 150 for making user-created widgets 149-6;
    • Search module 151;
    • Video and music player module 152, which merges video player module and music player module;
    • Notes module 153;
    • Map module 154; and/or
    • Online video module 155.


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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



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


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


In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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


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



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


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


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



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


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


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



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

    • 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 for frequently used applications, such as:
      • Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
      • Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
      • Icon 420 for browser module 147, labeled “Browser;” and
      • Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
    • Icons for other applications, such as:
      • Icon 424 for IM module 141, labeled “Messages;”
      • Icon 426 for calendar module 148, labeled “Calendar;”
      • Icon 428 for image management module 144, labeled “Photos;”
      • Icon 430 for camera module 143, labeled “Camera;”
      • Icon 432 for online video module 155, labeled “Online Video;”
      • Icon 434 for stocks widget 149-2, labeled “Stocks;”
      • Icon 436 for map module 154, labeled “Maps;”
      • Icon 438 for weather widget 149-1, labeled “Weather;”
      • Icon 440 for alarm clock widget 149-4, labeled “Clock;”
      • Icon 442 for workout support module 142, labeled “Workout Support;”
      • Icon 444 for notes module 153, labeled “Notes;” and
      • Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.


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



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


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


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



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


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


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



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


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


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


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


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


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


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



FIGS. 6A-6S illustrate exemplary user interfaces for capturing and editing media data, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes of FIGS. 7 and 8.



FIG. 6A depicts three different views (600A, 600B, and 600C) of computer system 600 (e.g., a smartphone, tablet, digital camera, or other computer system). View 600A illustrates the back of computer system 600 and includes cameras 602A, 602B, and 602C. In some embodiments computer system 600 includes fewer than three cameras (e.g., one camera or two cameras). In some embodiments, computer system 600 includes more than three cameras (e.g., four, five, or ten). In some embodiments, computer system 600 includes one or more features of devices 100, 300, and/or 500.


View 600B of FIG. 6A depicts the front of computer system 600. As shown in view 600B, computer system 600 includes front facing camera 602D and display 604, which is a touch-sensitive display. In some embodiments, computer system 600 includes multiple front-facing cameras. Also shown in view 600B, computer system 600 displays camera user interface 605 of a camera application. Camera user interface 605 includes digital viewfinder 606 in a portion of camera user interface 605. In view 600B of FIG. 6A, digital viewfinder 606 displays a preview of data from camera 602B, as computer system 600 is currently configured to capture media using camera 602B. Digital viewfinder 606 includes a representation of first subject 614A and second subject 614B. Digital viewfinder 606 further includes magnification selection graphical objects 608A, 608B, and 608C. Each magnification selection graphical object 608A, 608B, and 608C corresponds to cameras 602A, 602B, and 602C, respectively. Digital viewfinder 606 displays the selected magnification selection graphical object 608B in a larger format than unselected magnification selection graphical objects 608A and 608C. In some embodiments, the magnification selection graphical objects are displayed at the same size. Digital viewfinder 606 further includes camera swap graphical object 611 for switching the camera used in the preview in digital viewfinder 606 from one of the cameras (602A, 602B, or 602C) on the back of computer system 600 to camera 602D on the front of computer system 600, and vice versa.


In view 600B, computer system 600 also displays mode selection menu 616, which includes selectable graphical objects (e.g., 616A, 616B, 616C, 616D, and 616E) corresponding to various selectable camera modes. The selectable graphical objects of camera mode selection menu 616 can be selected to configure computer system 600 to capture media using different camera modes. For example, when computer system 600 detects selection of portrait (e.g., “PORTRAIT”) mode graphical object 616E, computer system 600 configures the camera application to capture media with a synthetic depth-of-field effect that can help to emphasize a subject. In view 600B, computer system 600 is currently configured to capture media in a multi-format capture mode, as indicated by multi-format graphical object 616C being centered and emphasized. While the multi-format capture mode is selected, computer system 600 captures sufficient media data for the captured media data to be presented in multiple media types (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media) at a later point (e.g., in an edit mode).


View 600C depicts an alternative view of the front of computer system 600. Unlike view 600B, view 600C does not include camera mode selection menu 616, because computer system 600 in view 600C defaults to capturing data in the multi-format capture mode. In view 600C, computer system 600 captures media data (e.g., photo or video) in the multi-format capture mode when a request to capture media (e.g., a tap or long press on shutter icon 610) is detected. In some embodiments of view 600C, while in the multi-format capture mode, computer system 600 detects input (e.g., a tap or long press) on record button 612 to initiate capture of video data. In view 600C, digital viewfinder 606 further includes camera swap graphical object 611 for switching the camera used in the preview in digital viewfinder 606 from one of the cameras (602A, 602B, or 602C) on the back of computer system 600 to camera 602D on the front of computer system 600, and vice versa.


Returning to view 600B of FIG. 6A, computer system 600 detects input 620A (e.g., long press) and detects lateral movement 624A (e.g., movement of the computer system 600 to the right). In some embodiments, computer system 600 initiates capturing photo data in response to input 620A (e.g., tap or long press) on shutter icon 610. In some embodiments, computer system 600 initiates capturing video data in response to input 620A on shutter icon 610.


In FIG. 6B, in response to input 620A (e.g., a long press) in FIG. 6A, computer system 600 initiates media data capture, which has progressed for three seconds, as indicated by time indicator 618. Further, as a result of lateral movement input 624A in FIG. 6A, digital viewfinder 606 displays a different view of the environment as compared to view 600B of FIG. 6A, as computer system 600 has been panned to the right (e.g., subject 614B is more towards the left as compared to FIG. 6A and subject 614A is no longer visible). In some embodiments, the movement includes vertical and/or diagonal movement. In FIG. 6B, computer system 600 detects lateral movement input 624B to the right. In some embodiments, computer system 600 detects an input on magnification selection graphical objects 608A and/or 608C to change the preview of media data in digital viewfinder 606 to a representations of media data captured via the respective camera corresponding to magnification selection graphical objects 608A and/or 608C. In some embodiments, camera swap graphical object 611 is displayed in the digital viewfinder 606 during the capturing process. In some embodiments, computer system 600 detects an input on camera swap graphical object 611 to change the preview in digital viewfinder 606 to a representation of media data captured via front facing camera 602D.


In FIG. 6C, in response to lateral movement 624B, computer system 600 updates digital viewfinder 606 and neither first subject 614A nor second subject 614B are visible within digital viewfinder 606. At this point, computer system 600 captured an additional four seconds of video data, as indicated by time indicator 618. Moreover, in response to computer system 600 determining that enough video data has been captured to later display the captured video data in a panoramic mode (e.g., a panoramic photo mode), a panoramic graphical object 622 is displayed on display 604. In some embodiments, computer system 600 does not display panoramic graphical object 622 even though sufficient amount of data has been captured to display the captured video data in a panoramic mode. Panoramic graphical object 622 is visually emphasized within the digital viewfinder. In some embodiment, the visual emphasis includes highlighting, color fill, typeface, and/or a change in size. In some embodiments, panoramic graphical object (e.g., 622) is displayed outside of digital viewfinder 606.


In FIG. 6D, computer system 600 displays gallery user interface 627 for viewing previously captured media data. Computer system 600 displays gallery user interface 627 in response to computer system 600 detecting activation of a photos application associated with computer system 600. Gallery user interface 627 includes chronologically organized thumbnail representations of previously captured media items (e.g., photos and/or videos), including first media item representation 626A1 that was captured in FIGS. 6A-6C as well as second media item representation 626B, third media item representation 626C, fourth media item representation 626D, and fifth media item representation 626E, each of which was previously captured (e.g., either via computer system 600 or a different device).


Gallery user interface 627 includes multi-media indicators 630A, 630B, 630C, and 630D for each respective media item that includes sufficient media data for the respective media item to be presented in multiple media types (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media). In some embodiments, even though a respective media item includes sufficient media data for the respective media item to be presented in multiple media types (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media), computer system 600 does not display a corresponding multi-media indicator.


In FIG. 6D, gallery user interface 627 further includes favorite indicator 628A corresponding to first media item representation 626A1 and favorite indicator 628B corresponding to fifth media item representation 626E. Favorite indicators 628A and 628B indicate that the respective media items were previously designated (e.g., via an input) as favorites. In some embodiments, for favorited respective media items, computer system 600 preserves (e.g., not deletes after a predetermined time) additional data that allows the respective media items to be presented in multiple media types. For example, because the fourth media item corresponding to fourth media item representation 626D was not favorited, even though fourth media item was captured with additional data that allowed for fourth media item to be presented in multiple media types, computer system 600 deleted the additional data that allowed for fourth media item to be presented in multiple media types, after a period of time. This is exemplified by the fact that fourth media item representation 626D lacks a multi-media indicator, even though it is a more recently captured media item than media item 626E. As a result, fourth media item representation 626D does not include a multi-media indicator. In some embodiments, computer system 600 deletes the additional data that allows a respective media item to be presented in multiple media types after a predetermined period of time. In some embodiments, computer system 600 deletes the additional data that allows a respective media item to be presented in multiple media types when storage capacity on computer system 600 decreases below a threshold amount.



FIG. 6D further depicts that, because sufficient time has not passed since the second media item corresponding to second media item representation 626B and the third media item corresponding to third media item representation 626C were captured, while not favorited, second media item and third media item still retain additional data that allows them to be presented in multiple media types. However, because the fifth media item that corresponds to fifth media item representation 626E was previously favorited, as indicated via favorite indicator 628B, even though the fifth media item was captured prior to the third media item and the fourth media item, computer system 600 preserved the additional data that allows for the fifth media item to be presented in multiple media types. Accordingly, fifth media item representation 626E includes multi-media indicator 630D. In some embodiments, computer system 600 preserves (e.g., saves and/or does not delete) the additional data that allows for a respective media item to be presented in multiple media types and also does not display a respective multi-media indicator corresponding to the respective media item. In some embodiments, even though a respective media item is favorited, computer system 600 deletes the additional data that allows for a respective media item to be presented in multiple media types after a second set of delete conditions are met. For example, in a situation where the first set of delete conditions is a week after capture, computer system 600 would delete additional data corresponding to unfavorited media item a week after capture, but retain the additional data for favorited media items past the week threshold. However, if the second delete condition was set to a month threshold, computer system 600 would delete the additional data corresponding to favorited media item a month after capture. In FIG. 6D, computer system 600 detects input 620B (e.g., a tap or long press) on first media item representation 626A1.


In response to input 620B, in FIG. 6E computer system 600 displays gallery user interface 627 that includes first media item representation 626A2, which is a larger representation of first media item representation 626A1. Gallery user interface 627 includes multi-media indicator 630A, because the first media item corresponding to first media item representation 626A2 includes additional data that allows for the first media item to be presented in multiple media types.


Gallery user interface 627 further includes edit graphical objects 632A and 632B displayed concurrently with first media item representation 626A2. In response to detecting activation of edit graphical object 632A, computer system 600 applies a slow loop effect to the first media item to provide a slower version of video data corresponding to first media item. Alternatively, in response to detecting activation of quick edit graphical object 632B, computer system 600 applies a quick loop effect to first media item to provide a faster version of media data corresponding to first media item. In some embodiments, additional edit graphical objects will include a loop effect, a bounce effect, and/or a long exposure effect, all of which can be applied to the first media item. Accordingly, the first media item can be edited while in gallery user interface 627 without entering a respective editing user interface, as shown in FIG. 6F, or needing to go into any submenus in gallery user interface 627. In some embodiments, computer system 600 detects an input on favorite indicator 628A to change the favorite status (e.g., make favorite or unfavorited) of the first media item. In FIG. 6E, computer system 600 detects input 620C (e.g., a tap or long press) on edit graphical object 636 to enter an editing user interface.


In FIG. 6F, in response to input 620C, computer system 600 displays video editing user interface 642A including first media item representation 626A3. Because the first media item includes additional data that allows for the first media item to be presented in multiple media types, video editing user interface 642A includes edit selection menu 634, which includes selectable graphical objects (e.g., 634A, 634B, 634D, 634E, and/or 634F) corresponding to various selectable media edit modes. Each respective selectable graphical object displayed within edit selection menu 634 can be selected to change the media edit type (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media) for the first media item. Computer system 600 displays the currently active media mode in a central position within edit selection menu 634. In some embodiments, computer system 600 does not displays the currently active media mode in a central position within edit selection menu 634. In some embodiments, edit selection menu 634 is similar to camera mode selection menu 616, described in FIG. 6A (e.g., includes objects with similar functions as described for camera mode selection menu 616).


In FIG. 6F, computer system 600 displays video (e.g., “VIDEO”) mode graphical object 634B in the central position within edit selection menu 634. Because video edit mode is currently active, video editing user interface 642A includes editing options corresponding to the video media type including filmstrip 640. Filmstrip 640 includes representations 641 of the first media item over time. Video Editing user interface 642A further includes completion button 638. In response to detecting activation of completion button 638, computer system 600 saves (e.g., preserves and/or does not delete) any edits made to the first item. In FIG. 6F, because no edits have yet been made to the first item, completion button 638 is disabled and, consequently, visually distinguished (e.g., grayed out or made translucent) to signify that it is not selectable.


In some embodiments, when a respective media item (e.g., the media item that corresponds to fourth media item representation 626D) does not include additional data that allows for the respective media item to be presented in multiple media types (e.g., computer system 600 deleted the additional data or the respective media item was not initially captured while in the multi-media capture mode), computer system 600 would not display edit selection menu 634 within the video editing user interface 642A. Instead, a respective set of edit options for the respective media type for the respective media item would be displayed within video editing user interface 642A without edit selection menu 634. In FIG. 6F, computer system 600 detects input (e.g., tap or long press) 620E on cinematic (e.g., “CINEMETIC”) mode and input 620D (e.g., tap or long press) on slo-mo (e.g., “SLO-MO” (e.g., a slow motion capture mode)) mode graphical object 634F.


In FIG. 6G, in response to input 620E, computer system 600 displays cinematic editing user interface 642B for the cinematic media data type. Thus, in response to input 620E, computer system 600 transitions from displaying video editing user interface 642A in FIG. 6F for a video data type to cinematic editing user interface 642B in FIG. 6G for a cinematic data type. While in the cinematic editing user interface 642B for the cinematic media data type, a synthetic depth-of-field effect is applied to first media item representation 626A3 automatically (e.g., not in response to one or more inputs) and/or in response to a user input. When the synthetic depth-of-field effect is applied automatically, computer system 600 makes one or more determinations based on a set of criteria to determine how the synthetic depth-of-field effect is applied and applies the synthetic depth-of-field effect (e.g., without detecting an input to apply the synthetic depth-of-field effect). When the synthetic depth-of-field effect is applied in response to a user input, computer system 600 detects an input and applies the synthetic depth-of-field effect based on the type of input that was detected. In some embodiments, first media item representation 626A3 corresponds to a representation of a video media type that includes synthetic depth-of-field data.


Cinematic editing user interface 642B further includes cinematic media data indicator 650 to signify that the cinematic media edit mode is active and first media item representation 626A3. In some embodiments, a different media data indicators is displayed for different media edit modes (e.g., “video” is displayed for video edit mode, and/or “portrait” is displayed for portrait edit mode). Because the video data type for the first media item changed from video data type to cinematic data type, computer system 600 displays completion button 638 as selectable (e.g., not grayed out or otherwise visually indicated as available for input). At this point, computer system 600 can detect an input on completion button 638 and save the first media item as a cinematic media item instead of a video item.


While in the edit mode for a cinematic media data type, computer system 600 can detect an input to change a synthetic depth-of-field effect in the media item. In FIG. 6G, cinematic editing user interface 642B further includes focus bar 648 that depicts various focus transitions for the first media item. First media item representation 626A3 depicts second subject 614B in focus, as indicated via focus indicator 652. The background of first media item representation 626A3, including first subject 614A, is not in focus (e.g., blurry, hazy, and/or dim). In FIG. 6G, computer system 600 detects input 620F (e.g., a tap or long press) on first subject 614A to change focus.


In FIG. 6H, in response to detecting input 620F, computer system 600 changes the focus within first media item representation 626A3. Specifically, computer system 600 blurs out the foreground of first media item representation 626A3 including second subject 614B and brings part of the background of first media item representation 626A3 including first subject 614B in focus (e.g., unblurs and/or sharpens), as indicated via focus indicator 652. Accordingly, computer system 600 updates focus bar 648 to reflect the changes in the focus of first media item. In FIG. 6G, computer system 600 detects input 620G (e.g., tap or long press) on completion button 638 to save the editing changes and input 620H (e.g., tap or long press) on slo-mo (e.g., “SLO-MO”) mode graphical object 634F to change the editing mode to the slo-mo editing mode.


In FIG. 6I, in response to detecting input 620G, computer system 600 redisplays gallery user interface 627. Gallery user interface 627 includes first media item representation 626A2. However, now first media item representation 626A2 reflects the changes to the focus applied to the first media item in FIG. 6H. Because computer system 600 detected input 620G while in an edit mode for a cinematic media data type (e.g., last used edit mode), gallery user interface 627 includes first media item representation 626A2 as a cinematic media data type, as represented via cinematic indicator 656.


In FIG. 6J, in response to input 620D in FIG. 6F or input 620H in FIG. 6H, computer system 600 displays slo-mo editing user interface 642C for slo-mo media data type. Editing user interface 642C includes first media item representation 626A3 that corresponds to the first media item that includes portions of video data that can be played back in slow motion. Additionally, slo-mo editing user interface 642C includes “SLO-MO” graphical object 634F centrally located within edit selection menu 634 to indicate that it is presently selected. The remaining respective edit modes within edit selection menu 634 have shifted to the right, accordingly. Slo-mo editing user interface 642C further includes slow mode bar 660 for changing which portions of first media item will be presented in slow motion. In response to detecting drag gesture 620J within slow mode bar 660 to the left, computer system 600 changes the starting position of when slow motion video content will commence upon playback of the first media item. Computer system 600 also updates slow mode bar 660 accordingly to reflect the changes. As a result of the change, when computer system 600 plays back the media corresponding to the first media item, slow motion video content corresponding to the first media item will be played sooner that it would have been played had the change not been made. In some embodiments, a right drag gesture within slow mode bar 660 changes the starting position of when slow motion video content will commence upon playback of the first media item such that slow motion video data is played back later. In some embodiments, computer system 600 can detect an input (e.g., drag, swipe, or tap) at any portion of slow mode bar 660 to increase/decrease the amount of video content displayed in slow motion. In FIG. 6J, computer system 600 detects input 6201 (e.g., tap or long press) on “TIME LAPSE” graphical object 634G.


In FIG. 6K, in response to input 6201, computer system 600 displays time-lapse editing user interface 642D for a time-lapse edit mode. Time-lapse editing user interface 642D includes first media item representation 626A2 that includes a time lapse effect. In FIG. 6K, computer system 600 detects input 620K (e.g., tap or long press) on video (e.g., “VIDEO”) mode graphical object 634B to change the selected edit mode type.


In FIG. 6L, in response to detecting input 620K, computer system 600 displays video editing user interface 642A. Video Editing user interface 642A includes edit selection menu 634 that includes panoramic mode graphical object 634I (e.g., “PA”) that corresponds to the panoramic media data type in which media data can be stitched together to display a media item in wide (e.g., ultra-wide or ultra-ultra wide) format. Computer system 600 determines that additional data that allows first media item to be presented in panoramic mode is not available. As a result, computer system 600 displays panoramic mode graphical object 634H as inactive (e.g., grayed out and/or not selectable). In some embodiments, computer system 600 determines that data that allows first media item to be presented in panoramic mode is not available when the data has not been fully processed by computer system 600 or when the data has not been fully saved (e.g., downloaded and/or transferred) at computer system 600. FIG. 6L further depicts scrubber cursor 662 within filmstrip 640 to navigate (e.g., rewind or advance forward) through the video data corresponding to first media item. The position of scrubber cursor 662 correspond to the current position of the video corresponding to the first media item. In FIG. 6K, computer system 600 detects drag gesture 620L to advance the video content for first media item from first position 662A to second position 662B.


In FIG. 6M, computer system 600 determines that additional data that allows first media item to be presented in panoramic mode is now available. As a result, computer system 600 displays panoramic mode graphical object 634H as active (e.g., not grayed out and/or selectable). Video editing user interface 642A further includes magnification selection graphical objects 609A, 609B, and 609C. In FIG. 6M, each magnification selection graphical object 609A, 609B, and 609C corresponds to media data captured via cameras 602A, 602B, and 602C, respectively. In some embodiments, computer system 600 includes other magnification selection graphical objects that do not correspond to any of the cameras of computer system 600. For example, a magnification selection graphical object can correspond to media data captured by a camera on a device different from computer system 600. Computer system 600 displays second magnification selection graphical object 609B more prominently than first magnification selection graphical object 609A and third magnification selection graphical object 609C, because magnification selection graphical object 609B is presently selected. Because magnification selection graphical object 609B is presently selected, the displayed first media item representation 626A3 corresponds to the media data captured via camera 602B at the 1× magnification level. Video Editing user interface 642A further includes camera swap graphical object 613 for switching the media data used to display first media item representation 626A3 from one of the media data captured via cameras (602, 602B, or 602C) on the back of computer system 600 to media data captured via camera 602D on the front of computer system 600, and vice versa. In FIG. 6M, computer system 600 detects input 620M (e.g., a tap or long press) on third magnification selection graphical object.


In FIG. 6N, in response to input 620M, computer system 600, starting from second position 662B, updates the video corresponding to first media item to use the media data captured via camera 602C at the 3× magnification level. As a result, video editing user interface 642A displays second subject 614B at a larger size compared to second subject 614B in FIG. 6M. Additionally, to reflect the updated changes, computer system 600 visually updates the representations 641 of first media item over time within filmstrip 640. As a result, filmstrip representation 664A of the video corresponding to the first media item to the left of scrubber cursor 662 remains unchanged. However, filmstrip representation 664B of the video corresponding to the first media item to the right of scrubber cursor 662 is updated (e.g., displayed larger and/or displayed with greater magnification) to reflect media data captured via camera 602C at the 3× magnification level. In some embodiments computer system 600 updates the video corresponding to the first media item and the filmstrip 640 to reflect change in the media item starting at second position 622B until the next predetermined point (e.g., edit position and/or location) in the video (e.g., not until the end of video corresponding the first media item). In FIG. 6N, computer system 600 detects drag gesture 620N on scrubber cursor 662 to move the scrubber cursor 662 to third position 662C, as shown in FIG. 6O.


In FIG. 6O, in response to drag gesture 620N, computer system 600 updates first media item representation 626A3 to corresponds to third position 662C within the video data of the first media item. Consequently, FIG. 6O depicts the video corresponding to the first media item advancing further in the video to third position 662C. In FIG. 6O, computer system 600 detects input (e.g., tap or long press) 6200 on camera swap graphical object 613.


In FIG. 6P, in response to input 6200, computer system 600, starting from third position 662C, updates the video corresponding to first media item to use the media data captured via camera 602D (e.g., front facing camera). As a result, video editing user interface 642A now displays third subject 614C that was captured as part of the additional data while capturing the first media item in FIGS. 6A-6C. Moreover, video editing user interface 642A stops displaying magnification selection graphical objects 609A, 609B, and 609C that correspond to media data captured via cameras 602A, 602B, and 602C, because the first media item does not include additional data that would allow for optically zooming in on third subject 614C displayed with first media item representation 626A3. In some embodiments, video editing user interface 642A continues to display magnification selection graphical objects 609A, 609B, and 609C that correspond to media data captured via cameras 602A, 602B, and 602C, respectively, and/or other magnification selection graphical objects (e.g., digital zoom) that do not correspond to any specific camera, after selection of camera swap graphical object 613.


Additionally, in response to detecting input 6200, computer system 600 updates filmstrip 640 to reflect the editing changes. Consequently, fourth filmstrip representation 664BB of the video corresponding to the first media item to the right of scrubber cursor 662 is updated to reflect media data captured via camera 602D. However, filmstrip representation 664A of the video corresponding to the first media item to the left of scrubber cursor 662 as well as filmstrip representation 664BA of the video corresponding to the first media item to the left of scrubber cursor 662 remain unchanged. In some embodiments, in response to detecting input 6200, computer system 600 updates the video and the filmstrip 640 to reflect change in the first media item starting at third position 662C until the next predetermined point (e.g., edit position and/or location) in the video (e.g., not until the end of video corresponding the first media item). FIG. 6N, further depicts computer system 600 detecting input 620P (e.g., tap or long press) and swipe gesture 620Q.


In FIG. 6Q, in response to detecting input 620P, computer system 600 displays slo-mo editing user interface 642C. Slo-mo editing user interface 642C includes the previously edited media item, as depicted via filmstrip 640. Because computer system 600 detected drag gesture 620J in FIG. 6J, slow mode bar 660 reflects the change in FIG. 6Q. FIG. 6Q further includes input 620R (e.g., tap or long press) on photo graphical object 634D corresponding to photo edit mode.


In FIG. 6R, in response to detecting input 620R in FIG. 6Q or in response to detecting swipe gesture 620Q in FIG. 6P, computer system 600 displays photo editing user interface 642E for the photo media data type. Photo editing user interface 642E includes first media item representation 626A3 that is now represented as a still image, as evident by the lack of filmstrip 640 that was visible while computer system 600 displayed video editing user interface 642A. Additionally, computer system 600 is in an editing mode for a photo media data type, photo editing user interface 642E includes various photo specific editing tools 670A, 670B, 670C. Computer system 600 does not display editing tools 670A, 670B, 670C while computer system 600 displays video editing user interface 642A. In some embodiments editing tools 670A, 670B, 670C are also displayed in other editing modes (e.g., video media data type, portrait media data type, time lapse media data type, and/or cinematic media data type). In FIG. 6R, computer system 600 further detects swipe gesture 620S at an area corresponding to edit selection menu 634 to change the selected media edit mode. In some embodiments, a swipe gesture (e.g., 620S) is detected outside of edit selection menu 634 to change the selected edit mode.


In FIG. 6S, in response to detecting input 620S, computer system 600 displays portrait editing user interface 642F for portrait media data type. Portrait editing user interface 642F includes first media item representation 626A3 that is represented as a still image. In response to entering the portrait editing user interface 642F, computer system 600 applied (e.g., automatically and/or without detecting a specific input) a depth of field effect to first media item representation 626A3. As a result, the background of first media item representation 626A3 is blurred out, while the foreground, which includes third subject 614C, is in focus. Portrait editing user interface 642F further includes various portrait specific editing tools 672A, 672B, 672C for changing a property of the depth effect applied to first media item representation 626A3. Computer system 600 does not display editing tools 672A, 672B, 672C when a non-portrait editing user interface is displayed. In some embodiments editing tools 672A, 672B, 672C are displayed in other media data editing modes (e.g., video media data type, portrait media data type, time lapse media data type, and/or cinematic media data type). In some embodiments, in response to detecting an input on completion graphical object 638, computer system 600 saves the changes/edits made to first media item and computer system 600 redisplays gallery user interface 627, which would include a representation of first media item in the state it was at the time computer system 600 detected selection of completion graphical object 638. For example, if first media item was represented as a video media item at the time computer system 600 detected selection of completion graphical object 638, computer system 600 would display a representation of first media data as a video media item in gallery user interface 627. On the other hand, if first media item was represented as a still image media item at the time computer system 600 detected selection of completion graphical object 638, computer system 600 would display a representation of first media data as a still image media item in gallery user interface 627.



FIG. 7 is a flow diagram illustrating a method for capturing and/or editing media that can be presented as multiple different media types using a computer system in accordance with some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, and/or 600) that is in communication with display generation component (e.g., 604) (e.g., a display controller and/or a touch-sensitive display system) and one or more input devices (e.g., touch-sensitive portion of display 604) (e.g., a touch-sensitive surface, a touchscreen, a button, and/or a microphone). Some operations in method 700 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.


In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system is optionally in communication (e.g., wired communication and/or wireless communication) with a display generation component (e.g., 604) and with one or more input devices (e.g., touch-sensitive portion of display 604). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.


As described below, method 700 provides an intuitive way for capturing and/or editing media that can be presented as multiple different media types. The method reduces the cognitive burden on a user for capturing and/or editing media that can be presented as multiple different media types, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to capture and/or edit media that can be presented as multiple different media types faster and more efficiently conserves power and increases the time between battery charges.


The computer system (e.g., 600) displays (702), via the display generation component (e.g., 604), an editing user interface (e.g., 642A) for editing a respective media item (e.g., 626A1) that was previously captured (e.g., the respective media item has data sufficient for it to be presented in multiple media types: e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media) (in some embodiments the respective media item is simultaneously captured media of multiple types. In some embodiments the respective media item is media of multiple types captured on the computer system in response to detecting a input to capture the media.), wherein the editing user interface includes a first set of one or more edit options (e.g., 640 and other options shown in FIG. 6F) to edit (e.g. modify) a first type of media (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media) (e.g., the first set of one or more edit options are media item editing options for the first type of media presented: a video length edit option for videos, slow-motion length edit option for slow motion videos, and/or markup option for photos) (in some embodiments the editing user interface includes a representation of the respective media item).


While displaying the editing user interface, the computer system detects (704), via the one or more input devices, a first input (e.g., 620E) (e.g., a selection of an option (e.g., an affordance, button, graphical element, graphical object, and/or icon) that, when selected via the one or more input devices, initiates a process for displaying a second set of one or more edit options (e.g., an option that corresponds to the second type of media)).


In response to detecting the first input, the computer system displays (706), via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options (e.g., 642B, 648, and other options shown in FIG. 6G) (e.g., the second set of one or more edit options are media item editing options for the second type of media presented: a video length edit option for videos, slow-motion length edit option for slow motion videos, markup options for photos) to edit a second type of media (e.g., photo, video, slow-motion media, variable frame rate media, time-lapse media, portrait media, panoramic media, and/or cinematic media), different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options (e.g., the first set of one or more edit options includes an option that is not included in the second set of one or more edit options or vice versa (e.g., the first set of one or more edit options includes a photo markup option not present in the video edit options)) (in some embodiments the editing user interface maintains display of a representation of the previously captured media item as the editing interface displays the first set of one or more edit options and the second set of one or more edit options.). Providing different sets of editing options for different types of media for the same respective media item provides the user with the ability to access different editing options that correspond to different media types for the same respective media item, which provides the user with the flexibility to edit different types of media for that same respective media item. Doing so provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Moreover, displaying respective edit controls for each respective media type provides for a limited number (e.g., only the controls associated for the respective media type) of edit controls to be displayed at a time, and, in turn, reduces the total clutter on the display. Displaying only the necessary controls for each of the respective media types enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Additionally, providing a user with the ability to change a media type of a respective media item allows the user with greater flexibility of not needing to decide which camera mode to use during capture. As a result, a user is able to focus on framing a scene and be concerned with specific system settings for the capture (e.g., frame rate, zoom level, and/or media type) as these setting, and others, can be eddied post capture. Additionally, allowing a user to focus on capturing the scene without worrying about the capture mode type allows the user to not worry about possibly missing a transient/fleeting moment as the user will be able to edit the media/mode type after the capture.


In some embodiments, the second type of media includes (e.g., includes upon playback) a synthetic depth-of-field effect applied to a plurality of frames of the respective media item (e.g., as seen in FIG. 6G) (e.g., image and/or video data), wherein the first type of media does not include the synthetic depth-of-field effect (e.g., as seen in FIG. 6F) applied to the plurality of frames of the respective media item. In some embodiments the synthetic (e.g., computer-generated), depth-of-field effect adjusts captured video such that it appears that the one or more frames of the video have been captured with a camera that has a different aperture (e.g., physical aperture and/or effective aperture) and/or focal length (e.g., physical focal length and/or effective focal length) than the aperture and/or focal length of the one or more cameras (e.g., the one or more cameras that actually captured the video). In some embodiments applying the synthetic depth-of-field effect to emphasize the first subject in video relative to a second subject in the plurality of frames of the video includes applying an amount of blur (or synthetic bokch) to the second subject that is greater than the amount of blur (or synthetic bokch) applied to the first subject. In some embodiments when playing back the captured media, the second subject appears to be blurred more than the first subject. In some embodiments the changes in the synthetic depth of field effect over time are representative of changes in video recorded that capture the movement of the first subject over time. Providing the user with the capability to change the editing mode from a standard type of media (e.g., video and/or photo) editing mode to a cinematic type of media editing mode provides the user with greater flexibility when editing the respective media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first set of one or more edit options to edit (e.g. modify) the first type of media (e.g., video or photo) does not include an option to modify a speed (e.g., rate and/or frame rate) of playback of at least a portion (e.g., less than the whole) of the respective media item (e.g., as seen in FIG. 6F), and wherein the second set of one or more edit options to edit the second type of media (e.g., slow motion media) includes an option (e.g., 660) to modify the speed of playback of at least a portion of the respective media item (e.g., as seen in FIG. 6J). Providing the user with the capability to change the editing mode from a standard type of media (e.g., video or photo) editing mode to a slow motion (e.g., slo-mo) type of media editing mode provides the user with greater flexibility when editing respective media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first set of one or more edit options to edit (e.g. modify) the first type of media (e.g., video or photo) includes a first playback selectable user interface object (e.g., 640 in FIG. 6F) (e.g., an affordance), that when activated, initiates playback of a first set of a plurality of portions (e.g., frames, and/or data) of the respective media item at a first time interval (e.g., 00001 seconds, 0.01 seconds, 0.1 seconds, 1 second, 2 seconds, or 5 minutes), and wherein the second set of one or more edit options to edit (e.g. modify) the second type of media (e.g., time lapse) includes a second playback selectable user interface object, that when activated, causes playback of at least a second set of a plurality of portions (e.g., frames, data) of the respective media item at a second time interval (e.g., 0.001 seconds, 0.01 seconds, 0.1 seconds, 1 second, 2 seconds, or 5 minutes), different from the first time interval (e.g., 640 in FIG. 6K). In some embodiments the first set of the plurality of portions (e.g., frames and/or data) of the respective media item at least partially overlap the second set of the plurality of portions (e.g., frames and/or data) of the respective media item. In some embodiments the first set of the plurality of portions (e.g., frames) of the respective media item is fully distinct from the second set of the plurality of portions (e.g., frames) of the respective media item. Providing the user with the capability to change the editing mode from a standard type of media (e.g., video) editing mode to a time lapse type of media editing mode provides the user with greater flexibility when editing respective media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, subsequent to detecting the first input and while displaying the editing user interface, the computer system detects, via the one or more input devices, a second input (e.g., 620H) (e.g., a selection of an option (e.g., an affordance, button, graphical element, graphical object, and/or icon) that, when selected via the one or more input devices, initiates a process for displaying a second set of one or more edit options (e.g., an option that corresponds to the second type of media)); and in response to detecting the second input, the computer system displays, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a third set of one or more edit options (e.g., 660 and other options of FIG. 6J) (e.g., the third set of one or more edit options are media item editing options for the third type of media presented: a video length edit option for videos, slow-motion length edit option for slow motion videos, markup options for photos) to edit a third type of media (e.g., time-lapse, slow motion, cinematic, video, photo, portrait, and/or panoramic), different from the first type of media and the second type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options and the third set of one or more edit options (e.g., compare options of FIGS. 6J, 6F, and 6K) (e.g., the first set of one or more edit options includes an option that is not included in the second set of one or more edit options or vice versa (e.g., the first set of one or more edit options includes a photo markup option not present in the video edit options)), the first set of one or more edit options includes an option that is not included in the third set of one or more edit options or vice versa (e.g., the first set of one or more edit options includes a photo markup option not present in the cinematic edit options)) (in some embodiments the second set of one or more edit options and the third set of one or more edit options include the same set of options. In some embodiments the second set of one or more edit options includes an option that is not included in the third set of one or more edit options or vice versa. In some embodiments the editing user interface maintains display of a representation of the respective media item as the editing interface displays the first set of one or more edit options and the second set of one or more edit options.). Providing the user with the capability to change the editing mode to a third type of editing mode provides the user with greater flexibility when editing respective media item, which enhances the operability of the system and makes the user interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, in accordance with a determination that a set of discarding criteria is satisfied, the computer system discards (e.g., deleting) a portion of additional data (e.g., data that is sufficient for the media item to be presented in multiple media types: e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) corresponding to the respective media item (e.g., as discussed with reference to FIG. 6D); and in accordance with a determination that the set of discarding criteria is not satisfied, forgoing discarding the portion of additional data corresponding to the respective media item (e.g., as discussed with reference to FIG. 6D). In some embodiments a media gallery user interface includes a set of one or more representations (e.g., thumbnails) corresponding to a set of previously captured media items (e.g., video and/or photo). In some embodiments a media gallery user interface includes a thumbnail representation (among a plurality of thumbnail representations that represent a plurality of media items) that corresponds to previously captured photos and/or videos. In some embodiments the media gallery user interface includes a first representation (e.g., thumbnail) of a first previously captured media item (e.g., the respective media item), wherein: in accordance with a determination that the set of discarding criteria is satisfied, the first representation of the first previously captured media item does not include a first visual indicator (e.g., an affordance, button, graphical element (e.g., square, triangle, and/or any graphical shape), graphical object, and/or icon) that designates (e.g., indicates and/or specifics) that additional data (e.g., data that is sufficient for the media item to be presented in multiple media types: e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) corresponding to the first previously captured media item is available; and in accordance with a determination that the set of discarding (e.g., deleting and/or removing) criteria is not satisfied, the first representation of the first previously captured media item includes a first visual indicator (e.g., an affordance, button, graphical element (e.g., square triangle and/or any graphical shape), graphical object, and/or icon) that additional data (e.g., data that is sufficient for the media item to be presented in multiple media types: e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) corresponding to the first previously captured media item is available. In some embodiments accordance with a determination that the set of discarding criteria is satisfied, the system discards/deletes the additional data corresponding to the respective media item from a memory of the computer system (e.g., not the remote storage device). In some embodiments in accordance with a determination that the set of discarding criteria is satisfied, system discards/deletes the additional data corresponding to the respective media item from the memory of a computer system in addition to the remote storage. Discarding or deleting unnecessary (e.g., no longer needed) capture data corresponding to the respective media item enhances the operability of the system by reducing the necessary storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, the set of discarding criteria includes a first criterion that is satisfied when a predetermined amount of time (e.g., 1 second, 1 minute, 5 minutes, 10 minutes, 1 hour, 2 hours, 10 hours, 1 day, 5 days, 10 days, 1 week, 4 weeks, 1 month, 4 months, 1 year, 10 years, or 20 years) has elapsed subsequent to (e.g., since and/or after) capturing the respective media item (e.g., as discussed with reference to FIG. 6D). Discarding or deleting unnecessary (e.g., no longer needed) capture data corresponding to the respective media data after a time period enhances the operability of the system by reducing the necessary total storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, the set of discarding criteria includes a second criterion that is satisfied when the respective media item was not edited (in some embodiments was not selected for editing (e.g., whether edits were made and/or saved or not) (e.g., a characteristic (e.g., size, color, and/or type) of the media item has been changed) within a respective amount of time (e.g., 1 second, 1 minute, 5 minutes, 10 minutes, 1 hour, 2 hours, 10 hours, 1 day, 5 days, 10 days, 1 week, 4 weeks, 1 month, 4 months, 1 year, 10 years, or 20 years) after capturing the respective media item (e.g., as discussed with reference to FIG. 6D). Discarding or deleting unnecessary (e.g., no longer needed) capture information corresponding to the respective media item after only if the user has not edited the media item within a time period enhances the operability of the system by reducing the necessary storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, one or more media items that have been edited within the respective amount of time continue to be associated with additional data corresponding to the respective media item (e.g., data that is sufficient for the media item to be presented in multiple media types: e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) after the respective amount of time (e.g., as discussed with reference to FIG. 6D) (e.g., because the additional data corresponding to the respective media item is not deleted in accordance with the discarding criteria). Preserving/saving additional capture data corresponding to the respective media item for an extend time period only if a user has edited the media item enhances the operability of the system by reducing the necessary total storage capacity for the system (e.g., the system will retain only the data that is necessary) as well as improves the operability of the system by freeing up additional storage space which can be used to capture/store addition media data.


In some embodiments, the set of discarding criteria includes a fourth criterion that is satisfied when the respective media item is not marked (e.g., user identified and/or selected) as a favorite (e.g., selected, via an input on an affordance, as being liked) (e.g., as discussed with reference to FIG. 6D). In some embodiments a user identifies (e.g., marks) a media item as a favorite within the media gallery user interface via a user input on a graphical object (e.g., heart, square, circle, and/or any graphical object) corresponding to the first previously captured media. In some embodiments when a time threshold is reached since the media item was captured if the media item has been marked as a favorite, the corresponding additional data is retained (e.g., to allow for more flexible future editing of the media item) while if the media item has not been marked as a favorite, the corresponding additional data is discarded (e.g., to reduce the amount of data that is being stored and free up additional storage space for other purposes). Discarding or deleting unnecessary (e.g., no longer needed and/or necessary) capture information corresponding to a respective media item that has not been marked as favorite enhances the operability of the system by reducing the necessary storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, the set of discarding criteria includes a fifth criterion that is satisfied when the respective media item does not meet a view frequency threshold (e.g., as discussed with reference to FIG. 6D) (e.g., 1 view, 3 views, 5 views, 10 views, or 100 views within a predetermined period of time). In some embodiments the view frequency is incremented in response to the respective media item being accessed and/or displayed within the media gallery user interface. In some embodiments the view frequency is incremented in response to the respective media item being accessed and/or displayed via a first application different from the media gallery (e.g., not the media gallery). In some embodiments when a time threshold is reached since the media item was captured if the media item has been viewed more than a threshold amount (e.g., based on a number of distinct times the media item has been opened, a duration for which the media item has been viewed, or some other media item viewing metric), the corresponding additional data is retained (e.g., to allow for more flexible future editing of the media item) while if the media item has not been viewed more than the threshold amount, the corresponding additional data is discarded (e.g., to reduce the amount of data that is being stored and free up additional storage space for other purposes). Discarding or deleting unnecessary (e.g., no longer needed) capture information corresponding to a respective media item that has not been accessed (e.g., viewed and/or selected) a predetermined amount of timed within a predetermined amount of time enhances the operability of the system by reducing the necessary storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, the additional data includes data from a first camera (e.g., 602A) and data from a second camera (e.g., 602B) different from the first camera, and wherein discarding the portion of additional data includes discarding the data from the second camera (e.g., while retaining the data from the first camera). In some embodiments the computer system includes a plurality of cameras including the first camera and the second camera. In some embodiments each of the plurality of cameras have fixed, but different, focal lengths. In some embodiments the focal length, field of view, and optical magnification properties of an optical system is fixed for each of the plurality of cameras, but one or more of the fixed focal lengths, the fixed field of view, and/or the optical magnification properties are different between a first camera and a second camera of the plurality of cameras. In some embodiments a first camera of the plurality of cameras is positioned on the front side of computer system and the second camera of the plurality of cameras is positioned on the back side of the computer system. In some embodiments the first camera and the second camera correspond to a second (e.g., auxiliary and/or remote) computer system deafferent from the computer system. The respective media item including additional information from a plurality of cameras provides the user with greater flexibility when editing the respective media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the additional data includes first data for presenting the respective media item at a first frame rate and second data for presenting the respective media item at a second frame rate that is higher than the first frame rate, and wherein discarding the portion of additional data includes discarding the second data for presenting the respective media item at the second frame rate that is higher than the first frame rate (e.g., as discussed with reference to FIG. 6D) (e.g., while retaining the first data for presenting the respective media item at a first frame rate). The respective media item including data for presenting the respective media item at a first frame rate and data for presenting the respective media item at a second frame different from the first frame rate provides the user with greater flexibility when editing the respective media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Discarding or deleting unnecessary (e.g., no longer needed) data corresponding to the second frame rate that corresponds to a higher frame rate than the data for presenting the respective media item at the first frame rate enhances the operability of the system by reducing the necessary storage capacity for the system as well as improves the operability of the system by freeing up additional storage space that can be used to capture/store addition media data.


In some embodiments, the editing user interface includes a mode selection graphical object (e.g., 634) (e.g., wheel, cube, sphere, circle, ribbon, carousel, or any other graphical form), that, when selected (e.g., tap, swipe, or long press), initiates a change of an editing mode (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) for the respective media item from a first type of editing mode (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) to a second type of editing mode (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) that is different from the first type of editing mode (e.g., as shown in the transition from FIG. 6F to 6G based on input 620E). In some embodiments the mode selection graphical object is a representations of a wheel, cube, sphere, circle, ribbon, carousel, or any other graphical form. In some embodiments the mode selection graphical object includes selectable representations of different editing modes (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic). In some embodiments in response to an input (e.g., tap, swipe, or long press) directed to one of the selectable representations of editing modes, a set of one or more edit options for the respective image type is displayed. In some embodiments the first type of editing mode corresponds to the first type of media that includes the first set of one or more edit options or the second type of media that includes the second set of one or more edit options. In some embodiments the second type of editing mode corresponds to the first type of media that includes the first set of one or more edit options or the second type of media that includes the second set of one or more edit options. Displaying a graphical object that a user can use to transition between various edit modes provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. In some embodiments, the first input (e.g., tap, swipe, or long press) corresponds to an input on the mode selection graphical object (e.g., as shown in FIG. 6F). In some embodiments the input starts on the mode selection graphical object that and terminates outside of the mode selection graphical object. In some embodiments the input starts on the mode selection graphical object that and terminates within the boundaries of the mode selection graphical object. Detecting inputs on the displayed a graphical object to transition between various edit modes provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, prior to detecting the first input (in some embodiments prior to performing editing operations using the editing user interface), displaying the editing user interface for editing the respective media item that was previously captured without displaying the mode selection graphical object. In some embodiments while displaying the editing user interface without the mode selection graphical object, detecting an input that initiates the display of the mode selection graphical object. Forgoing to display the graphical object to change the edit modes prior to entering the edit mode provides the user with greater flexibility when editing the media item and reduces clutter on the display, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the mode selection graphical object: in accordance with a determination that a dynamic mode criteria are satisfied, includes a respective mode type graphical indication (634I) ((e.g., an affordance, button, graphical element, graphical object, and/or icon) that, when selected via the one or more input devices, initiates a process for displaying edit options corresponding to the respective mode type (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic)); and in accordance with a determination that the dynamic mode criteria are not satisfied, does not include the respective mode type graphical indication (e.g., as discussed with reference to FIG. 6L for 634I). In some embodiments the dynamic mode criteria include a first criterion that is satisfied subsequent to a time period (e.g., 1 second, 3 second, 5 second, 1 minute, 10 minutes, or any other time period) lapsing. In some embodiments the dynamic mode criteria include a second criterion that is satisfied in accordance with a determination that image analysis (e.g., processing) of the respective media item has completed (e.g., at the computer system and/or at an auxiliary device). In some embodiments the dynamic mode criteria include a third criterion that is satisfied in accordance with a determination that a software update has occurred, wherein the software update adds a new media type (e.g., hyper slow motion, night mode, and/or sky mode) for editing. Providing dynamic edit modes after meeting a predetermined criteria enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs, reducing user mistakes when operating/interacting with the system, allows the user to work with new edit modes) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, in accordance with a determination that a first media item (e.g., video) includes a first threshold amount of lateral (e.g., horizontal/vertical data and/or data that corresponds to lateral movement of the capturing capture during capture (e.g., capture of a video that includes lateral movement of the camera) data, the computer system displays, via the display generation component, a panoramic graphical object (e.g., 634H as seen in FIG. 6S or 622 as seen in FIG. 6C) ((e.g., an affordance, button, graphical element, and/or icon) that indicates that a sufficient amount of data is present for a panoramic image (e.g., panoramic mode type); and in accordance with a determination that the first media item (e.g., video) does not include the first threshold amount of lateral (e.g., horizontal or vertical) data, forgoing displaying the panoramic graphical object. In some embodiments the first threshold amount of lateral (e.g., horizontal or vertical) data is data that is sufficient to create and/or edit a panoramic image. In some embodiments the panoramic graphical object is part of the mode selection graphical object (e.g., wheel, cube, sphere, circle, ribbon, carousel, or any other graphical form). In some embodiments while displaying, via the display generation component, the panoramic graphical object, detecting an input corresponding to the panoramic graphical object; and in response to detecting the input corresponding to the panoramic graphical object, displaying an editing user interface for a panoramic media (e.g., mode) type. In some embodiments the editing user interface for the panoramic media type include a representation of the first media item as a panoramic media type (e.g., a media item that has more lateral (e.g., horizontal or vertical) data than a photo media item). Displaying an indication that respective media item includes sufficient lateral data for a panoramic image data type enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, displaying the panoramic graphical object includes displaying an animation of (e.g., visually transitioning) the panoramic graphical object from a first graphical state to a second graphical state (e.g., 622 as discussed with reference to FIG. 6C). In some embodiments the first graphical state and/or the second graphical state correspond to at least one of the shape, color, border, outline, hue, contrast, highlighting, shading, and/or font). In some embodiments the animation is displayed to indicate that the respective media item is being analyzed to generate a panoramic media type for the item. Displaying an animation of the graphical indication being created provides the user with improved feedback about the status of the media capture. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, the panoramic graphical object is displayed while displaying the editing user interface for editing the respective media item that was previously captured. In some embodiments the respective media item corresponds to the first media item. Displaying the graphical object in an editing view provides the user with improved feedback about the status of the media item while editing. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, while displaying a capture user interface (e.g., digital viewfinder) for capturing a second media item (e.g., video): in accordance with a determination that the second media item includes a second threshold amount of lateral (e.g., horizontal/vertical data and/or data that corresponds to lateral movement of the capturing capture during capture (e.g., capture of a video that includes lateral movement of the camera); In some embodiments the first and second amounts of lateral data are the same) data, the computer system displays, via the display generation component, a second panoramic graphical object (e.g., 622 of FIG. 6C) ((e.g., an affordance, button, graphical element, and/or icon); In some embodiments the panoramic graphical object and the second panoramic graphical object are the same and/or have the same appearance) that indicates that a second sufficient amount of data is present for a second panoramic image (e.g., panoramic mode type); and in accordance with a determination that the second media item (e.g., video) does not include the second threshold amount of lateral (e.g., horizontal or vertical) data, forgoing displaying the second panoramic graphical object (e.g., as discussed with reference to FIG. 6B in comparison to FIG. 6C). In some embodiments the second threshold amount of lateral (e.g., horizontal or vertical) data is data that is sufficient to create and/or edit a panoramic image. In some embodiments the second panoramic graphical object is part of the mode selection graphical object (e.g., wheel, cube, sphere, circle, ribbon, carousel, or any other graphical form). In some embodiments the second threshold amount of lateral data corresponds the first threshold amount of lateral data. In some embodiments the second media item corresponds to the respective media item. In some embodiments the panoramic graphical object includes the textual suggestion (e.g., “Panorama”) that indicates that the second sufficient amount of data is present for a panoramic image. In some embodiments the second sufficient amount of data corresponds to the first sufficient amount of data. Displaying the graphical object in a capture view provides the user with improved feedback about the status of the media item during capture. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, displaying a representation (e.g., 626A1) (e.g. preview) of the respective media item (in some embodiments in a media gallery user interface that includes representations of a plurality of media items that includes the respective media item), wherein the representation of the respective media item includes an indication (e.g., 630A) (e.g., an icon, text, outline, highlighting, and/or shading) that the respective media item includes additional data (e.g., data that is sufficient for the media item to be presented in multiple media types: e.g., photo, video, and/or slow-motion media). In some embodiments the representation of the respective media item is displayed without displaying representations of other media items. In some embodiments the representation of the respective media item is displayed prior to displaying the editing user interface. Displaying the indication that the respective media item includes additional data, data that is sufficient for the media item to be presented in multiple media types, provides the user with improved feedback about the status of the media item. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, while capturing (e.g., recording, storing in memory, displaying a representation of the third media item via a digital viewfinder, and/or being configured to capture) a third media item: in accordance with a determination that third media item is being captured (e.g., recorded, stored in memory, and/or a representation of the third media item being displayed via a digital viewfinder) in a first mode (e.g., non multi-capture mode, one of time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic), the computer system displays a multi-capture graphical object (616C) (e.g., an affordance, button, graphical element, and/or icon), that when activated, initiates a process to capture (e.g., store in memory, record, and/or display via the digital viewfinder) the third media item in a second mode, different from the first mode, wherein capturing the third media item in the second mode includes capturing data sufficient for the third media item to be presented as multiple media types (e.g., non multi-capture mode, one of time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) during an edit mode. In some embodiments capturing item in the first mode does not include capturing data (e.g., data not captured) sufficient for the third media item to be presented in multiple media types during an edit mode. In some embodiments the third media item corresponds to the respective media item. In some embodiments capturing the third media item in the first mode occurs subsequent to activation of a shutter/record graphical object. In some embodiments capturing the third media item in the first mode occurs prior to activation of a shutter/record graphical object while the displaying a representation of data in a digital viewfinder. In some embodiments the multi-capture graphical object is displayed in the second mode/and or the first mode. In some embodiments the multi-capture graphical object continues to be displayed when the system changes from the first mode to the second mode. Displaying the multi-capture graphical object in a capture user interface enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs, reducing user mistakes when operating/interacting with the system, and notifying the user multi capture mode is available) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, while capturing the third media item: in accordance with the determination that third media item is being captured in the first mode (e.g., non multi-capture mode, one of time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic), displaying, via the display generation component (e.g., a display controller and/or a touch-sensitive display system), a first set of configuration graphical objects for modifying a first set of one or more settings (e.g., controls and/or parameters) corresponding to capturing media in the first mode; and in accordance with a determination that third media item is being captured in second mode (e.g., multi-capture mode), different from the first mode, displaying, via the display generation component (e.g., a display controller and/or a touch-sensitive display system), a second set of configuration graphical objects for modifying a first set of one or more settings (e.g., controls and/or parameters) corresponding to capturing media in the second mode, wherein the second set of configuration graphical objects includes fewer graphical objects than the first set of configuration graphical objects. In some embodiments the second set of configuration graphical objects includes no graphical objects that cause a modification of the capturing. In some embodiments while displaying, via the display generation component (e.g., the display controller and/or the touch-sensitive display system), settings (e.g., controls and/or parameters) corresponding to capturing media in the first mode, detecting a first respective input corresponding to a first configuration graphical object from the first set of configuration graphical objects, and in response to detecting the first respective input, modifying a first respective setting (e.g., control and/or parameter) corresponding to capturing media in the first mode. In some embodiments while displaying, via the display generation component (e.g., the display controller and/or the touch-sensitive display system), settings (e.g., controls and/or parameters) corresponding to capturing media in the second mode, detecting a second respective input corresponding to a second configuration graphical object from the second set of configuration graphical objects, and in response to detecting the second respective input, modifying a second respective setting (e.g., control and/or parameter) corresponding to capturing media in the second mode. In some embodiments while displaying, via the display generation component (e.g., the display controller and/or the touch-sensitive display system), settings (e.g., controls and/or parameters) corresponding to capturing media in the first mode, detecting a third respective input corresponding to a third configuration graphical object from the first set of configuration graphical objects, and in response to detecting the third respective input, displaying a third set of configuration graphical objects for modifying a third set of one or more settings (e.g., controls and/or parameters) corresponding to capturing media in the first mode. In some embodiments while displaying, via the display generation component (e.g., the display controller and/or the touch-sensitive display system), settings (e.g., controls and/or parameters) corresponding to capturing media in the second mode, detecting a fourth respective input corresponding to a fourth configuration graphical object from the second set of configuration graphical objects, and in response to detecting the fourth respective input, displaying a fourth set of configuration graphical objects for modifying a fourth set of one or more settings (e.g., controls and/or parameters) corresponding to capturing media in the second mode. Displaying fewer configuration graphical objects while in the second capture mode compared to the graphical objects displayed while in the first capture mode, enhances the operability of the system and makes the user-system interface less cluttered and more efficient (e.g., by helping the user to provide proper inputs, reducing user mistakes when operating/interacting with the system, and notifying the user multi capture mode is available) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the third media item, when captured in the first mode (e.g., a mode corresponding to video mode 616B), includes data sufficient for presenting the third media item (e.g., presenting in the editing user interface) as a first media type (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic) without including data sufficient for presenting the third media item as a second media type (e.g., as any additional media types other than the first media type), different from the first media type. In some embodiments data captured in a first mode is captured with image data from one, two, three, five, and/or all of the cameras of the computer system. Capturing data in a specific data mode (e.g., first mode, non-multi-capture mode, one of time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic), without including data sufficient for presenting the third media item as a second media type the enhances the operability of the system by reducing the necessary storage capacity.


In some embodiments, while displaying an editing interface for editing a respective media item that was previously captured, the computer system detects, via the one or more input devices, a fourth input (e.g., 620G) (e.g., a selection of an option (e.g., an affordance, button, graphical element, graphical object, and/or icon) that, when selected via the one or more input devices, initiates a process for displaying a second set of one or more edit options (e.g., an option that corresponds to the second type of media)); in response to detecting the fourth input: in accordance with a determination that the fourth input is detected while displaying the editing user interface that includes the first set of one or more edit options to edit the first type of media (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic), the computer system displays a representation (e.g., preview) of the respective media item, wherein the representation of the media item corresponds to the first type of media (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic); and in accordance with a determination that the fourth input is detected while displaying the editing user interface that includes the second set of one or more edit options to edit the second type of media, the computer system displays a representation of the respective media item, wherein the representation of the respective media item corresponds to the second type of media (e.g., as shown in the difference between how media item 626A1 is shown in FIG. 6E and FIG. 6I) (e.g., time-lapse, slow-motion, cinematic, video, photo, portrait, and/or panoramic). In some embodiments in response to detecting the fifth input, ceasing displaying the editing user interface. Displaying a representation of the respective media item based on type of media that was being edited at the time exit request was detected, enhances the predictability and operability of the system, enhances the visual feedback to the user and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs, reducing user mistakes when operating/interacting with the system, and allows the user to see the representation of the respective edited image) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


Note that details of the processes described above with respect to method 700 (e.g., FIG. 7) are also applicable in an analogous manner to the methods described below. For example, a media item captured using method 800 can be edited using one or more techniques of method 700. For another example, a media item edited according to method 700 can have been captured using method 1000. For brevity, these details are not repeated below.



FIG. 8 is a flow diagram illustrating a method for capturing and/or editing media that was captured using multiple different cameras using a computer system in accordance with some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, and/or 600) that is in communication with display generation component (e.g., 604) (e.g., a display controller and/or a touch-sensitive display system), one or more input devices (e.g., touch-sensitive surface of 604) (e.g., a touch-sensitive surface, a touchscreen, a button, and/or a microphone), a first camera (e.g., 602A), and a second camera (e.g., 602B, 602C, or 602D). In some embodiments the first camera and the second camera have fixed, but different, focal lengths. In some embodiments the focal length, field of view, and optical magnification properties of an optical system is fixed for each of the cameras, but the fixed focal length is different between the first camera and the second camera. In some embodiments the first camera is positioned on the front side of computer system and the second camera is positioned on the back side of the computer system. In some embodiments the computer system has more than two cameras (e.g., three, five, or ten)). Some operations in method 800 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.


In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component (e.g., 604) and with one or more input devices (e.g., touch-sensitive portion of display 604). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.


As described below, method 800 provides an intuitive way for capturing and/or editing media that was captured using multiple different cameras. The method reduces the cognitive burden on a user for capturing and/or editing media that was captured using multiple different cameras, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to capture and/or edit media that was captured using multiple different cameras faster and more efficiently conserves power and increases the time between battery charges.


The computer system (e.g., 600) detects (802), via the one or more input devices (e.g., touch-sensitive portion of display 604), a first input (e.g., 620A) (e.g., a tap gesture, long press, double-tap gesture, or a hand gesture) that corresponds to a request to capture (e.g., store in memory) media corresponding to at least a portion of a field of view (e.g., the field of view corresponding to 606) of at least one of the first camera (e.g., 602A) and the second camera (e.g., 602D) (in some embodiments the media item has data sufficient for it to be presented in multiple media types: e.g., photo, video, and/or slow-motion media) (in some embodiments the media item is simultaneously captured media of multiple types) (in some embodiments a media item stored as a single file that includes data from the first and second cameras).


In response to detecting the first input, the computer system captures (804) a media item (e.g., media item corresponding to 626A1) corresponding to at least a portion of the field of view of at least one of the first camera and the second camera, wherein capturing the media item includes capturing (e.g., concurrently, simultaneously, and/or at the same time) first data (e.g., media data) from the first camera (e.g., 602A) and second data (e.g., media data) from the second camera (e.g., 602D); (in some embodiments the first input is detected at a selectable user interface object. In some embodiments the first input is detected as a result of the user making a hand and/or finger gesture in the air.).


Subsequent to capturing the media item, the computer system displays (806), via the display generation component, a selectable user interface object (e.g., 636) (e.g., an edit affordance) for editing (e.g., modifying, changing the appearance of, and/or revising) the media item.


The computer system detects (808), via the one or more input devices, a second input (e.g., 620C) (e.g., a tap gesture, long press, double-tap gesture, or a hand gesture) directed to the selectable user interface object.


In response to detecting the second input directed to the selectable user interface object, the computer system displays (810) an editing user interface (e.g., 642A) that includes (e.g., that concurrently includes) a first representation (e.g., 626A3 of FIG. 6O) (e.g., an image, photograph, or video displayed via the display generation component) of the media item based primarily on the first data from the first camera (e.g., 602A) (e.g., more than 50%, 60%, 70%, 80%, or 80% the first representation is based on the first data from the first camera and/or a primary region (e.g., a central region and/or a center) of the first representation is based on the first data from the first camera) (in some embodiments the first representation is not primarily based on the second data from the second camera and/or less than 50%, 40%, 30%, 20%, or 10% of the data of the first representation is based on the second data from the second camera; In some embodiments the first representation is not based on any data from the second data from the second camera; In some embodiments a primary region (e.g., a central region and/or a center) of the first representation is not based on the second data from the second camera) and a camera option selectable user interface object (e.g., 613) (in some embodiments the camera option selectable user interface object can be a set of one, two, four, or any number of selectable user interface objects) for displaying a second representation (e.g., 626A3 of FIG. 6P) (e.g., an image, photograph, or video displayed via the display generation component) of the media item that is based primarily on the second data from the second camera (e.g., 602D) (e.g., more than 50%, 60%, 70%, 80%, or 80% the second representation is based on the second data from the second camera and/or a primary region (e.g., a central region or a center) of the second representation is based on the second data from the second camera) (in some embodiments the second representation is not primarily based on the first data from the first camera and/or less than 50%, 40%, 30%, 20%, or 10% of the data of the second representation is based on the first data from the first camera; In some embodiments the second representation is not based on any data from the first data from the first camera; In some embodiments a primary region (e.g., a central region, or a center) of the second representation is not based on the first data from the first camera).


The computer system detects (812), via the one or more input devices, a third input (e.g., 6200) (e.g., a tap gesture, long press, double-tap gesture, or a hand gesture) directed to the camera option selectable user interface object.


In response to detecting the third input: the computer system ceases (814) to display the first representation of the media item (e.g., 626A3 of FIG. 6O) that is based primarily on the first data from the first camera; and the computer system displays (816) the second representation of the media item (e.g., 626A3 of FIG. 6P) that is based primarily on the second data from the second camera. In some embodiments the first representation of the media item is displayed concurrently with the camera option selectable user interface object for displaying the second representation of the media item. In some embodiments the camera option selectable user interface object for displaying the second representation of the media item corresponds to a selectable user interface object to flip between the first camera and the second camera. In some embodiments the selectable user interface object for displaying the second representation of the media item corresponds to an optical zoom level which corresponds to a fixed focal length camera (e.g., the first camera corresponds to a first zoom level and the second camera corresponds to a different zoom level). In some embodiments the media item is captured by a second computer system (e.g., an external electronic device) and is then sent/transmitted/saved to the computer system for editing.). Capturing a media item with data from both a first and second camera and then providing a camera option selectable user interface object that causes a transition from a first representation of the media item that is primarily based on the first data from the first camera to a second representation of the media item that is primarily based on the second data from the second camera provides the user with more robust media capture that includes data from multiple cameras and allows the user to access different representations of the captured media data, which provides additional control options without cluttering the UI with additional displayed controls. Doing so also assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a first camera that can be different from the characteristics of the second camera, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Doing so also provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first camera (e.g., 602A) is oriented in a first direction (e.g., a direction directed away from the back of the computer system (e.g., a back-facing camera)); and the second camera (e.g., 602D) is oriented in a second direction, different from the first direction (e.g. a direction directed away from a front of the computer system (e.g., a front-facing camera) (in some embodiments the first direction and the second direction differ by at least 45°, 90°, 135°, or 180° (e.g., are opposite directions)). In some embodiments selecting the selectable user interface object causes the representation of the media item to switch between data from cameras having different orientations (e.g., front to back). In some embodiments the first camera is first respective camera of a first set of cameras (e.g., one or more) positioned (e.g., oriented) on the opposite side (e.g., back side) of the computer system relative to a primary display and/or a touch-sensitive display of the computer system. In some embodiments the second camera is a second respective camera of a second set of cameras (e.g., one or more) positioned (e.g., oriented and/or located) on the same side of the computer system relative to the primary display and/or the touch-sensitive display of the computer system. Capturing a media item with data from cameras with different orientations assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to misorientation of a camera. Doing so also provides the user with greater flexibility when editing the media item, by providing an option to display a representation of the media item from a different orientation.


In some embodiments, the media item includes video data (e.g., as shown in FIGS. 6O and 6P) (e.g., moving visual data captured over time); and the editing user interface includes a video position user interface object (e.g., 640 at the position corresponding to 662C in FIG. 6P) (e.g., a filmstrip, a position scrubber bar, and/or a playback position bar) that indicates a plurality of points in time (e.g., timestamps within the video data (e.g., 1 minute or 1 minute and 30 seconds)) within the video data (in some embodiments including an indication of a current playback position within the video data). In such embodiments, after detecting the third input (in some embodiments in response to detecting the third input), the computer system displays a graphical indication (e.g., an icon, border effect, and/or thumbnails that transition from one representation to another) of a first point in time of the plurality of points in time within the video data that corresponds to a transition from displaying the first representation of the media item to displaying the second representation of the media item. In some embodiments the graphical indication of the first point in time is overlaid on a portion of the video position user interface object; In some embodiments the graphical indication of the first point in time is integrated into (e.g., a part of) the video position user interface object; In some embodiments the graphical indication of the first point in time is transition within a visual filmstrip from representations that are based on the first data from the first camera to representations that are based on the second data from the second camera.


Displaying a graphical indication of a first point in time of the plurality of points in time within the video data that corresponds to a transition from displaying the first representation of the media item to displaying the second representation of the media item provides improved visual feedback regarding the point of transition within the video (e.g., allowing the user to reverse the transition).


In some embodiments, the first representation of the media item includes a depth-of-field effect (e.g., as seen in FIG. 6H) (e.g., a simulated depth effect and/or a bokch effect (e.g., an effect that presents elements (e.g., a subject and/or a background) within the representation that are at different depths with different levels of sharpness and/or blurring)) that is not included in the second representation of the media item (e.g., as seen in FIG. 6P). In some embodiments the second representation of the media item includes a depth-of-field effect (e.g., a simulated depth effect) that is not included in the first representation of the media item. In some embodiments the first representation of the media item includes a simulated lighting effect (e.g., simulated studio lighting, spot lighting, and/or contour lighting) that is not included in the second representation of the media item. Transitioning between a representation that includes a depth-of-field effect and one that does not provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the depth-of-field effect is a simulated depth-of-field effect that is based on data from a plurality of cameras (e.g., 602A and 602B) (e.g., the first camera and the second camera) that are in communication with the computer system. In some embodiments the simulated depth-of-field effect is based on the first data from the first camera and the second data from the second camera. Providing the user with the capability to display the media item with a representation that includes a simulated depth-of-field effect that is based on data from a plurality of cameras provides the user with greater flexibility when editing representations of the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first data from the first camera includes data captured at a first zoom level (e.g., 1× corresponding to 609B) (e.g., 1×, 2×, or 10×) (in some embodiments the first camera is a fixed focal length camera that captures data with a first level of optical zoom; In some embodiments the first zoom level is a digital zoom level); the second data from the second camera includes data captured at a second zoom level that is different from the first zoom level (e.g., 3X corresponding to 609C) (in some embodiments the second camera is a fixed focal length camera that captures data with a second level of optical zoom; In some embodiments the second zoom level is a digital zoom level); and the first representation of the media item is at the first zoom level and the second representation of the media item is at the second zoom level. Capturing a media item with data from cameras with different zoom levels assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to an improper zoom level of a camera. Doing so also provides the user with greater flexibility when editing the media item, by providing an option to display a representation of the media item at a different zoom level.


In some embodiments, the media item includes video data (e.g., moving visual data captured over time); and displaying the second representation of the media item includes displaying a transition (e.g., a gradual transition and/or an animated transition) that progresses over a first period of time (e.g., 0.25 seconds, 0.5 seconds, 1 second, or 2 seconds) from the first zoom level of the first representation of the media item to the second zoom level of the second representation of the media item, wherein the transition includes displaying a third representation of the media item that is at a third zoom level that is between the first zoom level and the second zoom level (e.g., as discussed with reference to FIGS. 6M and 6N) (e.g., the first zoom level is 1× and the second zoom level is 3×, with the third zoom level being 2×, or the first zoom level is 2× and the second zoom level is 1× and the third zoom level is 1.5×). Displaying a progressive transition of zoom levels provides the user with improved visual feedback as to the selected transition (e.g., by extending the period over a more noticeable duration of time), which provides improved visual feedback.


In some embodiments, the media item includes video data (e.g., moving visual data captured over time); the first representation of the media item is a representation of the video data in a first video playback mode (e.g., as in FIG. 6F) (e.g., standard speed playback, timelapse playback, slow-motion playback, and/or cinematic video playback (e.g., video playback with depth-of-field effects)); and the second representation of the media item is a representation of the video data in a second video playback mode (e.g., as in FIG. 6G different from the first video playback mode (e.g., as discussed with reference to the transition between FIGS. 6F and 6G). Providing the user with the capability display the media item with representations in different video modes provides the user with greater flexibility when editing representations of the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, prior to detecting the first input, the computer system displays via the display generation component, a media capture user interface (e.g., 605) that includes: a still media capture selectable user interface object (e.g., 616A) that, when selected, causes the computer system to be configured to capture still media (e.g., a still image or a photograph); and a video media capture selectable user interface object (e.g., 616B) that, when selected, causes the computer system to be configured to capture video media (e.g., moving visual data captured over time (e.g., standard video, timelapse video, slow motion video, and/or cinematic video (e.g., video one depth-of-field effects)). In some embodiments when the computer system is configured to capture still media, the computer system captures the media with a first set of cameras and when the computer system is configured to capture video media, the computer system captures the media with a second set of cameras that is different from (e.g., that includes or excludes one or more cameras that are in or not in the first set of cameras) the first set of cameras. Providing the user with selectable objects to configure media capture in a still or video mode, prior to initiating capture, assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to the computer system being improperly configured, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, after capturing the media item (e.g., corresponding to 626A1) (e.g., before displaying the first representation and/or the second in the editing user interface), displaying a fourth representation of the media item (e.g., 626A1) (in some embodiments in a media gallery user interface that includes representations of a plurality of media items that includes the media item), wherein the fourth representation of the media item includes an indication (e.g., 630A) (e.g., an icon or text) that the media item includes data that can be used to perform a first type of editing operation (e.g., an operation corresponding to input 6200) (e.g., a camera transition operation and/or a mode transition operation (e.g., still to video or a 1st video mode to a 2nd video mode)) on the media item (in some embodiments a second media item of the plurality of media items in the media gallery user interface that does not include data that can be used to perform the first type of editing operation on the second media item does not include the indication). Displaying an indication (e.g., an icon or text) that the media item includes data that can be used to perform a first type of editing operation indicates to the user that the operation can be performed on the media item, which provides improved visual feedback.


In some embodiments, the computer system is in communication with a third camera (e.g., 602C) (e.g., a camera having an orientation, a zoom level, and/or a sensor size that is different than that of the first camera and/or the second camera); and capturing the media item includes capturing (e.g., concurrently, simultaneously, and/or at the same time as the first data and/or the second data is captured) third data from the third camera. In some embodiments the first camera and second camera are rear-facing cameras, and the third camera is a front-facing camera. Capturing a media item with data from a first, second, and third cameras provides the user with more robust media capture that includes data from at least three cameras and allows the user to access different representations of the captured media data, which provides additional control options without cluttering the UI with additional displayed controls. Doing so also assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a first camera that can be different from the characteristics of the second camera or a third camera, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Doing so also provides the user with greater flexibility when editing the media item, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, after capturing the media item (e.g., before displaying the first representation and/or the second in the editing user interface), displaying a media viewer user interface (e.g., 627) (e.g., a user interface accessible from a gallery view that includes representations of a plurality of media items, including the first media item) that concurrently includes: a fifth representation of the media item (e.g., 626A2); and an editing selectable user interface object (e.g., 632A or 632B) that, when selected, causes a second type of editing operation (e.g., a playback speed increase or decrease operation, a camera transition operation, and/or a mode transition operation (e.g., still to video or a 1st video mode to a 2nd video mode)) to be performed on the media item. In some embodiments the selectable user interface object for editing the media item is displayed in the media viewer user interface. Providing the user with one or more editing options from a media viewer user interface (e.g., without having to access the editing user interface) reduces the number of inputs needed to perform an operation and provides feedback as to the availability of those editing options.


Note that details of the processes described above with respect to method 800 (e.g., FIG. 8) are also applicable in an analogous manner to the methods described above and below. For example, a media item captured using method 800 can be edited using one or more techniques of method 700. For another example, a media item can be captured using both the techniques of method 800 and 1000. For brevity, these details are not repeated below.



FIGS. 9A-9F illustrate exemplary user interfaces for capturing media data, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes of FIG. 10.



FIG. 9A depicts the front of computer system 600. Computer system 600 displays camera user interface 904 of a camera application. Camera user interface 904 includes digital viewfinder 906 in a portion of camera user interface 904. Digital viewfinder 906 displays a preview of data from a first camera (e.g., camera 602B in FIG. 6A) of computer system 600 that is currently configured to capture media using the camera. Digital viewfinder 906 includes a representation of first subject 914A and second subject 914B. Digital viewfinder 906 further includes magnification selection graphical objects 908A, 908B, and 908C. Each magnification selection graphical object 908A, 908B, and 908C corresponds to three different cameras (e.g., cameras 602A, 602B, or 602C in FIG. 6A) of computer system 600. Computer system 600 also includes front camera 602D on the front of computer system 600. In some examples, the first camera (e.g., 602A), a second camera (e.g., 602B), a third camera (e.g., 602C), and front camera 602D have fixed, but different, focal lengths. In some examples, the focal length, field of view, and/or optical magnification properties of the optical system is fixed for each of the four cameras. In some embodiments, in addition to having different fixed focal lengths, the four cameras have different fixed fields of view and different fixed optical magnification properties.



FIG. 9A further depicts three different fields of view of the physical environment for each respective camera of the three different cameras (e.g., cameras 602A, 602B, or 602C in FIG. 6A) on the back of computer system 600. Field of view 910A corresponds to the first camera (e.g., 602A) of computer system 600 (e.g., a 0.5× magnification). Field of view 910B corresponds to the second camera (e.g., 602B) of computer system 600 (e.g., a 1× magnification). Field of view 910C corresponds to the third camera (e.g., 602C) (e.g., 3× magnification). Furthermore, digital viewfinder 906 displays the selected magnification selection graphical object 908B in a larger format than unselected magnification selection graphical objects 908A and 908C. In some embodiments, the magnification selection graphical objects are displayed at the same size. In some embodiments, the respective field of views of at least two of the cameras of the respective cameras (e.g., cameras 602A and 602D) do not overlap.


In FIG. 9A, table 918A illustrates which respective cameras of computer system 600 are actively capturing data (e.g., at the point in time corresponding to FIG. 9A). In some embodiments, computer system 600 continually detects (e.g., before and after detecting selection of shutter icon 916), via one or more sensors of computer system 600, environment data and context data corresponding to computer system 600 as well as content data captured within respective fields of view (e.g., 910A, 910B, and/or 910C) of the respective cameras of computer system 600. Based on all or some of this detected information, in some embodiments, computer system 600 automatically (e.g., without user input and/or selection) selects cameras for media capture. As indicated in table 918A, computer system 600 selected respective cameras that correspond to the 0.5×, 1×, and 3× magnifications (e.g., cameras 602A, 602B, and 602C in FIG. 6A) for media capture. In some embodiments, computer system 600 captures media data from front camera 602D concurrently with data from the one or more respective cameras (e.g., cameras 602A, 602B, and/or 602C in FIG. 6A) on the back of computer system 600.


In FIG. 9A, computer system 600 captures media data in the background from the respective cameras (e.g., cameras 602A, 602B, and 602C in FIG. 6A) on the back of computer system 600 even before computer system 600 detects an input on shutter icon 916. In some embodiments, computer system 600 captures media data from all the available cameras on computer system 600 prior to selection of shutter icon 916 regardless of the context or environment of computer system 600. In some embodiments, computer system 600 captures media data from at least one camera of the respective cameras (e.g., cameras 602A, 602B, 602C, in FIGS. 6A and 602D) of computer system 600 before the camera application is displayed (e.g., before the camera application has been started/launched). In some embodiments, computer system 600 automatically (e.g., without detecting a user input) selects which respective cameras (e.g., one or a plurality) to use to capture media data based on the content within a respective field of view (e.g., 910A, 910B, and/or 910C) of the respective cameras of computer system 600 (e.g., cameras 602A, 602B, and/or 602C in FIGS. 6A and 602D). In FIG. 9A, computer system 600 detects input 912A on shutter icon 916 to initiate capture of media data.


In FIG. 9B, in response to detecting input 912A, computer system 600 initiates media data capture. As computer system 600 captures the media data, computer system 600 detects third subject 914C entering field of view 910C. In response to detecting subject entering field of view 910C, computer system 600 changes which cameras are selected for media data capture. Because magnification level 1× is selected in camera user interface 904, as depicted in table 918B, computer system 600 continues to capture media data corresponding to the camera that corresponds to the 1× magnification. Also, because computer system 600 detected third subject 914C entering the scene, computer system 600 selects a respective camera corresponding to 0.5× magnification for media capture, as depicted in table 918B. In some embodiments, including the embodiment of FIG. 9B, computer system 600 does not select a respective camera corresponding to 3× to save storage space. In some embodiments, computer system 600 continues to capture media data using all available respective cameras of computer system 600. In some embodiments, computer system 600 selects cameras corresponding to the 0.5× magnification and 3× magnification of computer system 600 for media data capture.


In FIG. 9C, computer system 600 detects that first subject 914A, subject 914B, and subject 914 are progressively getting further away from computer system 600. As a result, computer system 600 changes which respective cameras of computer system 600 captures media data. Because computer system 600 detected that magnification level 1× is selected in camera user interface 904, computer system 600 continues to capture media data corresponding to the camera that corresponds to the 1× magnification, as depicted in table 918C. Also, because computer system 600 detected first subject 914A, second subject 914B, and third subject 914C progressively getting further away from computer system 600, computer system 600 selects a respective camera corresponding to 3× magnification for media capture, as depicted in table 918B. In some embodiments, computer system 600 selects a respective camera corresponding to a higher magnification level for media data capture in response to computer system 600 detecting that the media data being captured is of a sporting event or another event where it is desirable to capture data with a higher magnification (e.g., concert and/or theater). In FIG. 9C, computer system 600 does not select the camera that corresponds to 0.5× magnification because no subjects are detected in the field of view 810C that are not also in field of view 810B and/or in order to save space. In FIG. 9C, computer system 600 further detects input 912B on magnification selection graphical object 908A that corresponds to a respective camera with a 0.5× magnification.


In FIG. 9D, in response to detecting input 912B, computer system 600 changes which respective cameras of computer system 600 captures media data. As illustrated in table 918D, in FIG. 9D computer system 600 captures media data with respective cameras that correspond to the 0.5× magnification and the 1× magnification. Computer system 600 selects the respective camera corresponding to the 0.5× magnification level in response to detecting activation of graphical objects 908A. Computer system 600 selects the camera corresponding to 1× magnification to capture media data in response to detecting a greater number of subjects within field of view 910B than in 910C. In some embodiments, computer system 600 selects camera corresponding to 1× magnification to capture media data because it was selected (e.g., user selected or automatically selected) prior to detecting input 912B on magnification selection graphical objects 908A.


In FIG. 9E, computer system 600 detects that first subject 914A is closer to computer system 600 than in FIG. 9D. In response to detecting first subject 914A closer to computer system 600, computer system 600 changes which respective cameras of computer system 600 captures media data. As illustrated in table 918E, in FIG. 9E computer system 600 captures media data with respective cameras that correspond to the 0.5× magnification and the 3× magnification. Computer system 600 selects the respective camera corresponding to the 3× magnification level in response to detecting that first subject 914A has moved closer to computer system 600. Computer system 600 selects the respective camera corresponding to 0.5× magnification to capture media data based on a determination that magnification selection graphical object 908A that corresponds to magnification level 0.5× is currently selected in camera user interface 904. In some embodiments, computer system 600 selects the respective camera corresponding to 3× magnification to capture media data in response to computer system 600 detecting that first subject 914A moves progressively closer to computer system 600. In some embodiments, computer system 600 selects the respective camera corresponding to the 3× magnification to capture media data, because computer system 600 determines, based on the context of the environment, that it may be desirable to later edit the captured media data in the portrait editing mode, which preferably uses the media data captured at 3× magnification. In FIG. 9E, computer system 600 further detects input 912C on magnification selection graphical object 908B that corresponds to a respective camera with a 1× magnification.


In FIG. 9F, in response to detecting input 912C, computer system 600 changes which respective cameras of computer system 600 captures media data. As illustrated in table 918F, in FIG. 9F computer system 600 captures media data with a respective camera that corresponds to the 1× magnification. Computer system 600 selects the respective camera corresponding to the 1× magnification level in response to detecting activation of graphical object 908B. Computer system 600 does not select other respective cameras, because it detects that it is undesirable and/or unnecessary to capture media data with other cameras based on the content of the captured media data. In some embodiments, computer system 600 selects a single camera for media capture to conserve storage space. In some embodiments, in response to computer system 600 detecting an input to stop the capture of media data, computer system 600 saves the captured media. In some embodiments, the saved media data includes the media data that was captured before (10 seconds, 20 seconds, 1 minute, and/or 5 minutes) computer system 600 detected input 912A on shutter icon 916 in FIG. 9A. In some embodiments, computer system 600 selects camera 602D for media data capture either alone or in conjunction with one or more of the respective cameras (e.g., cameras 602A, 602B, and/or 602C in FIG. 6A) based on detected information regarding the environment and context of computer system 600 as well as detected content within a respective field of view of any of the cameras of computer system 600.



FIG. 10 is a flow diagram illustrating a method for selecting a subset of cameras with which to capture media using a computer system in accordance with some embodiments. Method 1000 is performed at a computer system (e.g., 100, 300, 500, and/or 600) that is in communication with a display generation component (e.g., 604) (e.g., a display controller and/or a touch-sensitive display system) one or more input devices (e.g., a touch-sensitive portion of 604) (e.g., a touch-sensitive surface, a touchscreen, a button, and/or a microphone), and a plurality of cameras that includes at least three cameras (e.g., 602A, 602B, 602C, and/or 602D). In some embodiments the focal length, field of view, and optical magnification properties of an optical system is fixed for each of the plurality of cameras, but one or more of the fixed focal lengths, the fixed field of view, and/or the optical magnification properties are different between a first camera and a second camera of the plurality of cameras. In some embodiments a first camera of the plurality of cameras is positioned on the front side of computer system and the second camera of the plurality of cameras is positioned on the back side of the computer system.). Some operations in method 1000 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.


In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system is optionally in communication (e.g., wired communication and/or wireless communication) with a display generation component (e.g., 604) and with one or more input devices (e.g., touch-sensitive portion of display 604). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.


As described below, method 1000 provides an intuitive way for selecting a subset of cameras with which to capture media. The method reduces the cognitive burden on a user for selecting a subset of cameras with which to capture media, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to use a device that selects a subset of cameras with which to capture media faster and more efficiently conserves power and increases the time between battery charges.


The computer system (e.g., 600) detects (1002), via the one or more input devices (e.g., a touch-sensitive portion of 604), an input (912A) (e.g., (e.g., a tap gesture, long press, double-tap gesture, or a hand gesture) directed to capturing (e.g., storing in memory) a media item (e.g., the media item has data sufficient for it to be presented in multiple media types: e.g., photo, video, and/or slow-motion media) (in some embodiments the media item is simultaneously captured media of multiple types.).


In response to detecting the input directed to capturing the media item: in accordance with a determination (e.g., made by the computer system and/or an external device in communication with the computer system) that a first set of context criteria are met, the computer system captures (e.g., 1004) the media item using a first subset of (e.g., not all or fewer than all) cameras of the plurality of cameras, wherein the first subset of cameras includes at least two cameras of the plurality of cameras (e.g., 60AB and 602B and/or cameras corresponding to 0.5× and 1× magnifications as shown in FIG. 9B); and (in some embodiments the first subset of cameras used to capture the media item are chosen automatically and/or based on predetermined settings) (in some embodiments the set of context criteria includes a criterion based on the state of the computer system. In some embodiments the set of context criteria includes a criterion based on the environment (e.g., geographic location and/or environmental conditions). In some embodiments the set of context criteria includes a criterion based on data captured from at least one of the plurality of cameras. In some embodiments the set of context criteria includes a criterion based on an electronic sensor (i.e., not the camera) of the computer system.) in accordance with a determination that a second set of context criteria are met, wherein the second set of context criteria are different from the first set of context criteria (e.g., the second set of context criteria includes at least one criterion not included in the first set of context criteria or vice versa), the computer system captures (1006) the media item using a second subset of cameras of the plurality of cameras (e.g., 602B and 602C and/or cameras corresponding to 1× and 3× magnifications as shown in FIG. 9C), wherein the second subset of cameras includes at least two cameras of the plurality of cameras, and wherein the first subset of cameras and the second subset of cameras are different (e.g., the first subset of cameras includes at least one camera that is not included in the second subset of cameras or vice versa). Capturing media using a first subset or a second subset of cameras based on context criteria, performs an operation when a set of conditions has been met without requiring further user input. Doing so also assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a camera in one subset that can be different from the characteristics of cameras in the second subset, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the second subset of cameras (e.g., as shown in 918B) includes at least one camera (e.g., 602B or a camera corresponding to 1× magnification) (e.g., a first camera) that is included in the first subset of cameras (e.g., as shown in 918C). In some embodiments the second subset of cameras includes all of the cameras included in the first subset of cameras, as well as one or more additional cameras that are not included in the first subset of cameras. Having at least one camera in common between the two subsets provides the subsets with overlapping capabilities, which can assist the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to camera characteristics (e.g., orientation, zoom level, and/or sensor size) not having sufficient overlap to reduce the risk of miscapture, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the second subset of cameras (e.g., as shown in 918C) includes at least one camera (e.g., 602C or a camera corresponding to 3× magnification) (e.g., a second camera) that is not included in the first subset of cameras (e.g., as shown in 918B). In some embodiments the second subset of cameras and the first subset of cameras includes at least one camera common to both sets, but each subset also includes one or more cameras that are not included in the other subset of cameras. Having at least one camera in in the second subset that is not in the first subset provides the second subset with captured capabilities that are not provided by the first subset, which can assist the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to camera characteristics (e.g., orientation, zoom level, and/or sensor size) not being sufficient to reduce the risk of miscapture, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first set of context criteria includes a first criterion that is met based on a preselected zoom level (e.g., 1× as shown in FIG. 9B) (e.g., a currently selected zoom level or a previously selected zoom value (e.g., a last used and/or a most used zoom level)). In some embodiments the first set of context criteria includes a criterion that is met when the computer system is configured to capture media with a preselected zoom level (e.g., a specific zoom level (1×, 2×, 3×, or 10×), an optical zoom level, and/or a digital zoom level) (in some embodiments a set of predetermined zoom levels (e.g., zoom levels between 1× and 3×, a zoom level greater than a specific zoom level (e.g., 3× or more), and/or a zoom level that is less than a specific zoom level (e.g., less than 3×)) when the input directed to capturing the media item is detected (e.g., a media capture application is currently set to the preselected zoom level). In some embodiments when the computer system is configured to capture media with a preselected zoom level (e.g., 3×), the first subset of cameras includes cameras with optical zoom levels (e.g., one or more of the cameras are fixed focal length cameras) that are at and below the preselected zoom level (e.g., the first subset of cameras includes a camera with a 3× zoom and a camera with a 1× zoom). Having a criterion based on the zoom level provides for camera subset selection based on a degree of zoom that affects the content that will be captured, which can assist the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to a zoom level being inadequate to properly capture intended content (e.g., content is cropped out due to excessive zoom or content is lacking detail due to insufficient zoom), which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first set of context criteria includes a second criterion that is met based on a classification (e.g., the content is classified as moving content, still content, a person, an animal, an inanimate object, and/or content relating to a type of event (e.g., a sporting event, an artistic performance, and/or a speech)) of content being captured (e.g., as discussed with reference to FIG. 9C) (e.g., content to be captured). In some embodiments the classification of the content being captured is based on user input (e.g., a setting manually selected by the user (e.g., a capture mode setting such as sport, portrait, action, and/or still life and/or a capture setting such as aperture/depth-effect value, white balance, and/or focal point)). In some embodiments the classification of the content being captured is based on a determination made by the computer system (e.g., based on data from one or more sensors (e.g., one or more cameras of the plurality of cameras and/or microphones) that are in communication with the computer system (e.g., based on image data being captured matching a predetermined pattern) and/or based on data regarding an appropriate set of cameras to be used based on the time of day and/or previously selected by the user in similar conditions). Selecting which subset of cameras to use for media capture based on classification of the content (e.g., after the classification is selected and/or determined), performs an operation when a set of conditions has been met without requiring further user input. Doing so also assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed or miscaptured due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a camera subset being inappropriate for a the classification of the content, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first set of context criteria are met when the content being captured is classified as content that includes a degree of motion of one or subjects that exceeds a predetermined threshold (e.g., as discussed with reference to FIG. 9D) (e.g., the content being captured is a sporting event and/or action-related event); and (in some embodiments the first subset of cameras includes at least one camera configured to capture high-speed motion and/or reduced blurring (e.g., the camera has low shutter speed value (e.g., a fast shutter speed setting)) and/or a camera having a rapid focusing speed and/or a camera having a wide field-of-view.) (in some embodiments the content is classified based on the distance and/or number of subjects within the content (e.g., a sporting event captured from a distance that includes multiple subjects or a portrait of a single subject captured at a close distance) the first set of context criteria are not met when the content being captured is classified as content that does not include a degree of motion of one or subjects that exceeds the predetermined threshold (e.g., as discussed with reference to FIG. 9E) (e.g., the content being captured is a portrait of a subject and/or a still life composition). In some embodiments the second subset of cameras includes at least one camera configured to capture a high amount of light and/or with a high amount of depth effect (e.g., a camera with a low f-stop value) and/or with a larger sensor size to capture a high amount of data/details.) Selecting a subset of cameras based on a degree of motion of the one or more subjects assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed or miscaptured due to characteristics (e.g., shutter speed, orientation, zoom level, and/or sensor size) of a camera subset being inappropriate for a the degree of motion, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the classification of the content being captured is based on movement (e.g., movement away from the computer system) of a plurality of objects (in some embodiments the objects are identified as potential subjects of interest (e.g., players, balls, and/or vehicles in a sporting event) detected by at least one camera of the plurality of cameras (e.g., as discussed with reference to FIG. 9C). In some embodiments movement of a plurality of objects causes the computer system to select a subset of cameras for media capture that includes at least one camera configured to capture high-speed motion and/or reduced blurring (e.g., the camera has low shutter speed value (e.g., a fast shutter speed setting)) and/or a camera having a rapid focusing speed and/or a camera having a wide field-of-view. Classifying content being captured based on the movement of a plurality of objects allows for automatic selection of an appropriate subset of cameras based on that movement, performs an operation when a set of conditions has been met without requiring further user input. Doing so also assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a camera in one subset that can be different from the characteristics of cameras in the second subset and that are more appropriate for capturing movement, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the determination of whether the first set of context criteria are met is made (e.g., made by the computer system and/or an external device in communication with the computer system) prior to detecting the input (e.g., prior to 912A) directed to capturing the media item. In some embodiments the computer system is periodically or continually evaluating whether the first subset or second subset of cameras should be used and adjusting accordingly. In some embodiments the computer system can switch, during a capturing of the media item (e.g., when the media item is video captured over time), from using the first subset of cameras to using the second subset of cameras based on a determination of whether a second set of context criteria are met (e.g., when the context changes during capture). Making a determination prior to detecting the input reduces the risk that the wrong subset of cameras are selected for media capture, which assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to characteristics (e.g., orientation, zoom level, and/or sensor size) of a camera in one subset that can be different from the characteristics of cameras in the second subset and that are more appropriate for capturing movement, which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


In some embodiments, the first subset of cameras includes a first camera (e.g., 602A or a camera corresponding to 0.5× magnification) that has a first field-of-view that is different than a second field-of-view of a second camera (e.g., 602B or a camera corresponding to 1× magnification) that is included in the second set of cameras. In some embodiments the first field-of-view is wider than the field-of-view of one or more cameras or all cameras in the second subset of cameras. In some embodiments the first field-of-view is narrower than the field-of-view of one or more cameras or all cameras in the second subset of cameras. In some embodiments cameras within a subset of cameras have different fields-of-view (e.g., the first subset of cameras includes a third camera that has a third field-of-view and a fourth camera that has a fourth field-of-view that is different than the third field-of-view) (e.g., the first subset of cameras includes a wide and a telephoto camera). Employing cameras with different fields-of-view in the first and second subsets of cameras assists the user with composing media capture events and reduces the risk that transient media capture opportunities are missed due to camera having the wrong field-of-view to properly capture the content (e.g., content is cropped out due to excessive zoom and/or content is lacking detail due to insufficient zoom and/or content being missed because the field-of-view is not oriented in a direction to capture the content), which enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating and/or interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.


Note that details of the processes described above with respect to method 1000 (e.g., FIG. 10) are also applicable in an analogous manner to the methods described above. For example, a media item can be captured using both the techniques of method 1000 and 800. For another example, a media item captured according to method 1000 can be edited using one or more techniques of method 700. For brevity, these details are not repeated below.


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


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


As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve capture and/or editing of media items. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, social network IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.


The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to improve the capture and/or editing of media items. Accordingly, use of such personal information data enables users to have calculated control of the capture and/or editing of media items. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.


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


Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of contextual data to improve the capture of media items, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide contextual data to improve the capture of media items. In yet another example, users can select to limit the length of time contextual data is maintained or entirely prohibit the development of a contextual data to improve the capture of media items. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.


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


Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, media items can be captured and/or cameras can be selected for capture by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to camera application, or publicly available information.

Claims
  • 1. A computer system configured to communicate with a display generation component and one or more input devices, comprising: one or more processors; andmemory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media;while displaying the editing user interface, detecting, via the one or more input devices, a first input; andin response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.
  • 2. The computer system of claim 1, wherein the second type of media includes a synthetic depth-of-field effect applied to a plurality of frames of the respective media item, wherein the first type of media does not include the synthetic depth-of-field effect applied to the plurality of frames of the respective media item.
  • 3. The computer system of claim 1, wherein the first set of one or more edit options to edit the first type of media does not include an option to modify a speed of playback of at least a portion of the respective media item, and wherein the second set of one or more edit options to edit the second type of media includes an option to modify the speed of playback of at least a portion of the respective media item.
  • 4. The computer system of claim 1, wherein the first set of one or more edit options to edit the first type of media includes a first playback selectable user interface object, that when activated, initiates playback of a first set of a plurality of portions of the respective media item at a first time interval, and wherein the second set of one or more edit options to edit the second type of media includes a second playback selectable user interface object, that when activated, causes playback of at least a second set of a plurality of portions of the respective media item at a second time interval, different from the first time interval.
  • 5. The computer system of claim 1, the one or more programs further including instructions for: subsequent to detecting the first input and while displaying the editing user interface, detecting, via the one or more input devices, a second input; andin response to detecting the second input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a third set of one or more edit options, different from the first type of media and the second type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options and the third set of one or more edit options.
  • 6. The computer system of claim 1, the one or more programs further including instructions for: in accordance with a determination that a set of discarding criteria is satisfied, discarding a portion of additional data corresponding to the respective media item; andin accordance with a determination that the set of discarding criteria is not satisfied, forgoing discarding the portion of additional data corresponding to the respective media item.
  • 7. The computer system of claim 6, wherein the set of discarding criteria includes a first criterion that is satisfied when a predetermined amount of time has elapsed subsequent to capturing the respective media item.
  • 8. The computer system of claim 6, wherein the set of discarding criteria includes a second criterion that is satisfied when the respective media item was not edited within a respective amount of time after capturing the respective media item.
  • 9. The computer system of claim 8, wherein one or more media items that have been edited within the respective amount of time continue to be associated with additional data corresponding to the respective media item after the respective amount of time.
  • 10. The computer system of claim 6, wherein the set of discarding criteria includes a fourth criterion that is satisfied when the respective media item is not marked as a favorite.
  • 11. The computer system of claim 6, wherein the set of discarding criteria includes a fifth criterion that is satisfied when the respective media item does not meet a view frequency threshold.
  • 12. The computer system of claim 6, wherein the additional data includes data from a first camera and data from a second camera different from the first camera, and wherein discarding the portion of additional data includes discarding the data from the second camera.
  • 13. The computer system of claim 6, wherein the additional data includes first data for presenting the respective media item at a first frame rate and second data for presenting the respective media item at a second frame rate that is higher than the first frame rate, and wherein discarding the portion of additional data includes discarding the second data for presenting the respective media item at the second frame rate that is higher than the first frame rate.
  • 14. The computer system of claim 1, wherein the editing user interface includes a mode selection graphical object, that, when selected, initiates a change of an editing mode for the respective media item from a first type of editing mode to a second type of editing mode that is different from the first type of editing mode.
  • 15. The computer system of claim 14, wherein the first input corresponds to an input on the mode selection graphical object.
  • 16. The computer system of claim 14, wherein prior to detecting the first input, displaying the editing user interface for editing the respective media item that was previously captured without displaying the mode selection graphical object.
  • 17. The computer system of claim 14, wherein the mode selection graphical object: in accordance with a determination that a dynamic mode criteria are satisfied, includes a respective mode type graphical indication; andin accordance with a determination that the dynamic mode criteria are not satisfied, does not include the respective mode type graphical indication.
  • 18. The computer system of claim 1, the one or more programs further including instructions for: in accordance with a determination that a first media item includes a first threshold amount of lateral data, displaying, via the display generation component, a panoramic graphical object that indicates that a sufficient amount of data is present for a panoramic image; andin accordance with a determination that the first media item does not include the first threshold amount of lateral data, forgoing displaying the panoramic graphical object.
  • 19. The computer system of claim 18, wherein displaying the panoramic graphical object includes displaying an animation of the panoramic graphical object from a first graphical state to a second graphical state.
  • 20. The computer system of claim 18, wherein the panoramic graphical object is displayed while displaying the editing user interface for editing the respective media item that was previously captured.
  • 21. The computer system of claim 18, the one or more programs further including instructions for: while displaying a capture user interface for capturing a second media item: in accordance with a determination that the second media item includes a second threshold amount of lateral data, displaying, via the display generation component, a second panoramic graphical object that indicates that a second sufficient amount of data is present for a second panoramic image; andin accordance with a determination that the second media item does not include the second threshold amount of lateral data, forgoing displaying the second panoramic graphical object.
  • 22. The computer system of claim 1, the one or more programs further including instructions for: displaying a representation of the respective media item, wherein the representation of the respective media item includes an indication that the respective media item includes additional data.
  • 23. The computer system of claim 1, the one or more programs further including instructions for: while capturing a third media item: in accordance with a determination that third media item is being captured in a first mode, displaying a multi-capture graphical object, that when activated, initiates a process to capture the third media item in a second mode, different from the first mode, wherein capturing the third media item in the second mode includes capturing data sufficient for the third media item to be presented as multiple media types during an edit mode.
  • 24. The computer system of claim 23, the one or more programs further including instructions for: while capturing the third media item: in accordance with the determination that third media item is being captured in the first mode, displaying, via the display generation component, a first set of configuration graphical objects for modifying a first set of one or more settings corresponding to capturing media in the first mode; andin accordance with a determination that third media item is being captured in second mode, different from the first mode, displaying, via the display generation component, a second set of configuration graphical objects for modifying a first set of one or more settings corresponding to capturing media in the second mode, wherein the second set of configuration graphical objects includes fewer graphical objects than the first set of configuration graphical objects.
  • 25. The computer system of claim 23, wherein the third media item, when captured in the first mode, includes data sufficient for presenting the third media item as a first media type without including data sufficient for presenting the third media item as a second media type, different from the first media type.
  • 26. The computer system of claim 1, the one or more programs further including instructions for: while displaying an editing interface for editing a respective media item that was previously captured, detecting, via the one or more input devices, a fourth inputin response to detecting the fourth input: in accordance with a determination that the fourth input is detected while displaying the editing user interface that includes the first set of one or more edit options to edit the first type of media, displaying a representation of the respective media item, wherein the representation of the respective media item corresponds to the first type of media; andin accordance with a determination that the fourth input is detected while displaying the editing user interface that includes the second set of one or more edit options to edit the second type of media, displaying a representation of the respective media item, wherein the representation of the respective media item corresponds to the second type of media.
  • 27. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media;while displaying the editing user interface, detecting, via the one or more input devices, a first input; andin response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.
  • 28. A method, comprising: at a computer system that is in communication with a display generation component and one or more input devices: displaying, via the display generation component, an editing user interface for editing a respective media item that was previously captured, wherein the editing user interface includes a first set of one or more edit options to edit a first type of media;while displaying the editing user interface, detecting, via the one or more input devices, a first input; andin response to detecting the first input, displaying, via the display generation component, the editing user interface for editing the respective media item, wherein the editing user interface includes a second set of one or more edit options to edit a second type of media, different from the first type of media, of the respective media item, wherein the first set of one more edit options is different from the second set of one or more edit options.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 63/462,213, entitled “MULTI-TYPE MEDIA USER INTERFACE,” filed on Apr. 26, 2023, the entire contents of which are hereby incorporated by reference in its entirety.

Provisional Applications (1)
Number Date Country
63462213 Apr 2023 US