A user interface for managing media

Abstract

To provide, generally, computer user interfaces, and more specifically, techniques for managing media.SOLUTION: The present disclosure generally relates to user interfaces for managing exposure compensation when capturing media (e.g., an image or video), for displaying representations of media (an image or video), and for displaying a status indicator (e.g., a status indicator indicating that media is and / or has been captured).SELECTED DRAWING: Figure 6B

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE This disclosure relates generally to computer user interfaces, and more specifically to techniques for managing media. [Background technology]

[0002] Users of smart phones and other personal electronic devices are increasingly capturing, storing, and editing media to keep memories safe and share with friends. Several existing technologies allow users to capture media, such as images, audio, and / or video. Users can manage such media, for example, by capturing, storing, and editing the media. Summary of the Invention

[0003] However, some user interfaces for managing media using electronic devices are generally cumbersome and inefficient. For example, some existing technologies use complex and time-consuming user interfaces that may involve multiple key presses or keystrokes. Existing technologies take more time than necessary, wasting the user's time and the device's energy. The latter problem is particularly acute in battery-operated devices.

[0004] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing media. Such methods and interfaces optionally complement or replace other methods for managing media. Such methods and interfaces reduce the cognitive burden on users and create a more efficient human-machine interface. For battery-operated computing systems, such methods and interfaces conserve power and extend the time between battery charges.

[0005] In some examples, the techniques allow users of computer systems to capture and display captured media in a time- and input-efficient manner, thereby reducing the amount of processing the device needs to perform. In some examples, the techniques manage the brightness of areas of the user interface, thereby conserving battery life.

[0006] According to some embodiments, a method is described. The method is executed in a computer system having one or more cameras and in communication with a display generation component and one or more input devices. The method includes receiving a request to display a camera user interface, and displaying the camera user interface via the display generation component in response to receiving the request to display the camera user interface while the one or more cameras are configured to capture images based on a first exposure compensation value, the camera user interface including displaying via the display generation component a first representation of a field of view of the one or more cameras, and displaying an exposure compensation indicator concurrently with the representation of the field of view of the one or more cameras in accordance with a determination that a set of exposure compensation criteria is satisfied, the set of exposure compensation criteria including criteria satisfied when an exposure compensation mode is enabled, the exposure compensation indicator including a representation of the first exposure compensation value and a visual indication that the computer system has determined that clipping is predicted to occur in response to receiving the request to capture media corresponding to the representation of the field of view of the one or more cameras.

[0007] According to some embodiments, a non-transitory computer readable storage medium is described. The non-transitory computer readable storage medium includes instructions for storing one or more programs configured to be executed by one or more processors of a computer system having one or more cameras, the computer system communicating with a display generating component and one or more input devices, the one or more programs receiving a request to display a camera user interface, displaying, via the display generating component, the camera user interface in response to receiving the request to display the camera user interface while the one or more cameras are configured to capture images based on a first exposure compensation value, displaying, via the display generating component, a first representation of a field of view of the one or more cameras, and displaying, in accordance with a determination that a set of exposure compensation criteria is satisfied, including criteria that are satisfied when an exposure compensation mode is enabled, simultaneously with the representation of the field of view of the one or more cameras, an exposure compensation indicator including a representation of the first exposure compensation value and a visual indication that the computer system has determined that clipping is predicted to occur in response to receiving a request to capture media corresponding to the representation of the field of view of the one or more cameras.

[0008] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium includes instructions for storing one or more programs configured to be executed by one or more processors of a computer system having one or more cameras, the computer system communicating with a display generating component and one or more input devices, the one or more programs receiving a request to display a camera user interface, displaying, via the display generating component, the camera user interface in response to receiving the request to display the camera user interface while the one or more cameras are configured to capture images based on a first exposure compensation value, displaying, via the display generating component, a first representation of a field of view of the one or more cameras, and displaying, in accordance with a determination that a set of exposure compensation criteria is satisfied, including criteria that are satisfied when an exposure compensation mode is enabled, simultaneously with the representation of the field of view of the one or more cameras, an exposure compensation indicator including a representation of the first exposure compensation value and a visual indication that the computer system has determined that clipping is predicted to occur in response to receiving a request to capture media corresponding to the representation of the field of view of the one or more cameras.

[0009] According to some embodiments, a computer system is described that includes one or more cameras, one or more processors, the computer system in communication with a display generation component and one or more input devices, and a 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 a camera user interface, including: receiving a request to display a camera user interface, and in response to receiving the request to display the camera user interface, displaying, via the display generation component, the camera user interface while the one or more cameras are configured to capture images based on a first exposure compensation value, displaying, via the display generation component, a first representation of a field of view of the one or more cameras, and, pursuant to a determination that a set of exposure compensation criteria is satisfied, including criteria that are satisfied when an exposure compensation mode is enabled, simultaneously with the representation of the field of view of the one or more cameras, an exposure compensation indicator including a representation of the first exposure compensation value and a visual indication that the computer system has determined that clipping is predicted to occur in response to receiving a request to capture media corresponding to the representation of the field of view of the one or more cameras.

[0010] According to some embodiments, a computer system is described that includes: means for receiving a request to display a camera user interface; and means for displaying the camera user interface via a display generation component in response to receiving the request to display the camera user interface while one or more cameras are configured to capture images based on a first exposure compensation value, the means for displaying via the display generation component a first representation of a field of view of the one or more cameras, and means for displaying an exposure compensation indicator including a representation of the first exposure compensation value concurrently with the representation of the field of view of the one or more cameras pursuant to a determination that a set of exposure compensation criteria is satisfied, the set of criteria including criteria satisfied when an exposure compensation mode is enabled, and a visual indication that the computer system has determined that clipping is predicted to occur in response to receiving a request to capture media corresponding to the representation of the field of view of the one or more cameras.

[0011] According to some embodiments, a method is described. The method is executed in a computer system in communication with a display generation component and one or more input devices. The method comprises: displaying, via the display generation component, a media viewer user interface including a first portion including a representation of a first previously captured media item and a second portion having a first visual appearance and different from the first portion of the media viewer user interface; receiving, while displaying, via the display generation component, a media viewer user interface including the second portion of the media viewer user interface having the first visual appearance, a request to display a representation of a second previously captured media item different from the first previously captured media item; in response to receiving the request to display the representation of the second previously captured media item, in accordance with a determination that a first set of criteria is satisfied, the criteria including criteria satisfied when the representation of the second previously captured media item is a high dynamic range (HDR) media item, displaying the representation of the second previously captured media item; and updating the second portion of the media viewer user interface to have the second visual appearance different from the first visual appearance.

[0012] According to some embodiments, a non-transitory computer readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system, the computer system being in communication with a display generation component and one or more input devices, the one or more programs displaying, via the display generation component, a media viewer user interface including a first portion including a representation of a first previously captured media item and a second portion having a first visual appearance different from the first portion of the media viewer user interface, and displaying, via the display generation component, a media viewer user interface including the second portion of the media viewer user interface having the first visual appearance. and, while displaying the media viewer user interface, receiving a request to display a representation of a second previously captured media item that differs from the first previously captured media item; and, in response to receiving the request to display the representation of the second previously captured media item, displaying the representation of the second previously captured media item in accordance with a determination that a first set of criteria is satisfied including criteria that are satisfied when the representation of the second previously captured media item is a high dynamic range (HDR) media item; and updating a second portion of the media viewer user interface to have a second visual appearance that differs from the first visual appearance.

[0013] According to some embodiments, a temporary computer-readable storage medium is described that stores one or more programs configured to be executed by one or more processors of a computer system, the computer system being in communication with a display generation component and one or more input devices, the one or more programs displaying, via the display generation component, a media viewer user interface including a first portion including a representation of a first previously captured media item and a second portion having a first visual appearance different from the first portion of the media viewer user interface, and displaying, via the display generation component, a media viewer user interface including the second portion of the media viewer user interface having the first visual appearance. While displaying the interface, receiving a request to display a representation of a second previously captured media item that differs from the first previously captured media item; and in response to receiving the request to display the representation of the second previously captured media item, displaying the representation of the second previously captured media item in accordance with a determination that a first set of criteria is satisfied, the criteria including criteria that are satisfied when the representation of the second previously captured media item is a high dynamic range (HDR) media item; and updating a second portion of the media viewer user interface to have a second visual appearance that differs from the first visual appearance.

[0014] According to some embodiments, a computer system is described that includes one or more processors in communication with a display generation component and one or more input devices, and a memory that stores one or more programs configured to be executed by the one or more processors, the one or more programs displaying, via the display generation component, a media viewer user interface including a first portion including a representation of a first previously captured media item and a second portion having a first visual appearance different from the first portion of the media viewer user interface, and displaying, via the display generation component, a media viewer user interface including the second portion of the media viewer user interface having the first visual appearance. The method includes, while displaying the media viewer user interface, receiving a request to display a representation of a second previously captured media item that is different from the first previously captured media item; and in response to receiving the request to display the representation of the second previously captured media item, displaying the representation of the second previously captured media item in accordance with a determination that a first set of criteria is satisfied, the criteria including criteria that are satisfied when the representation of the second previously captured media item is a high dynamic range (HDR) media item; and updating a second portion of the media viewer user interface to have a second visual appearance that is different from the first visual appearance.

[0015] According to some embodiments, a computer system is described comprising: means for displaying, via a display generation component, a media viewer user interface including a first portion including a representation of a first previously captured media item and a second portion having a first visual appearance and different from the first portion of the media viewer user interface, means for receiving, while displaying, via the display generation component, a media viewer user interface including the second portion of the media viewer user interface having the first visual appearance, a request to display a representation of a second previously captured media item different from the first previously captured media item, and means for, in response to receiving the request to display the representation of the second previously captured media item, updating the second portion of the media viewer user interface to have a second visual appearance different from the first visual appearance in accordance with a determination that a first set of criteria is satisfied, the first set of criteria including criteria that are satisfied when the representation of the second previously captured media item is a high dynamic range (HDR) media item.

[0016] According to some embodiments, a method is described that is executed in a computer system having a first media capture device, the computer system in communication with a display generation component and one or more input devices, the method comprising: receiving an indication that the first media capture device is activated; in response to receiving the indication that the first media capture device is activated, displaying, via the display generation component, a graphical indicator indicating activation of the first media capture device in accordance with a determination that the first media capture device has recorded a first type of data; and ceasing to display the graphical indicator indicating activation of the first media capture device in accordance with a determination that, while activated, the first media capture device has recorded a second type of data without recording the first type of data.

[0017] According to some embodiments, a non-transitory computer-readable storage medium is described, the non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system having a first media capture device, the computer system communicating with a display generation component and one or more input devices, the one or more programs including instructions for receiving an indication that the first media capture device is activated, displaying, via the display generation component, a graphical indicator indicating activation of the first media capture device in response to receiving the indication that the first media capture device is activated, in accordance with a determination that the first media capture device has recorded a first type of data, and ceasing to display the graphical indicator indicating activation of the first media capture device in accordance with a determination that, while activated, the first media capture device has recorded a second type of data without recording the first type of data.

[0018] According to some embodiments, a temporary computer-readable storage medium is described, the temporary computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system having a first media capture device, the computer system communicating with a display generation component and one or more input devices, the one or more programs including instructions for receiving an indication that the first media capture device is activated, displaying, via the display generation component, a graphical indicator indicating activation of the first media capture device in response to receiving the indication that the first media capture device is activated, in accordance with a determination that the first media capture device has recorded a first type of data, and ceasing to display the graphical indicator indicating activation of the first media capture device in accordance with a determination that, while activated, the first media capture device has recorded a second type of data without recording the first type of data.

[0019] According to some embodiments, a computer system is described that includes a first media capture device, the computer system in communication with a display generation component and one or more input devices, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to: receive an indication that the first media capture device is activated, and in response to receiving the indication that the first media capture device is activated, display, via the display generation component, a graphical indicator indicating activation of the first media capture device in accordance with a determination that the first media capture device has recorded a first type of data, and cease displaying the graphical indicator indicating activation of the first media capture device in accordance with a determination that, while activated, the first media capture device has recorded a second type of data without recording the first type of data.

[0020] According to some embodiments, a computer system is described that includes first media capture device means for receiving an indication that a first media capture device is activated, and means for, in response to receiving the indication that the first media capture device is activated, displaying, via a display generation component, a graphical indicator indicating activation of the first media capture device in accordance with a determination that the first media capture device has recorded a first type of data, and ceasing to display the graphical indicator indicating activation of the first media capture device in accordance with a determination that, while activated, the first media capture device has recorded a second type of data without recording the first type of data.

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

[0022] Thus, devices are provided with faster, more efficient methods and interfaces for managing media, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for managing media.

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

[0024] [Figure 1A] FIG. 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments. [Figure 1B] FIG. 2 is a block diagram illustrating example components for event processing in accordance with some embodiments. [Diagram 2] 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments. [Diagram 3] 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments. [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. [Figure 4B]1 illustrates an exemplary user interface of a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments. [Figure 5A] 1 illustrates a personal electronic device according to some embodiments. [Figure 5B] FIG. 1 is a block diagram illustrating a personal electronic device in accordance with some embodiments. [Figure 6A] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6B] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6C] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6D] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6E] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6F] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6G] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6H] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6I] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6J] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6K] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6L] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6M] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6N] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6O] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6P] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6Q] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6R] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6S] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6T] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6U] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 6V] 1 illustrates an example user interface for managing exposure compensation according to some embodiments. [Figure 7] 4 is a flow diagram illustrating an example method for managing exposure compensation in accordance with some embodiments. [Figure 8A] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8B] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8C] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8D]1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8E] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8F] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8G] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8H] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8I] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8J] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8K] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 8L] 1 illustrates an exemplary user interface for viewing media according to some embodiments. [Figure 9] 1 is a flow diagram illustrating an example method for displaying media according to some embodiments. [Figure 10A] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10B] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10C] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10D] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10E]1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10F] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10G] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10H] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10I] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10J] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10K] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10L] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10M] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10N] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10O] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10P] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10Q] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10R] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10S] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10T] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10U] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10V] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10W] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10X] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10Y] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10Z] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10AA] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10AB] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 10AC] 1 illustrates an example user interface for displaying status indicators according to some embodiments. [Figure 11] 1 is a flow diagram illustrating an example method for displaying a status indicator according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0026] There is a need for electronic devices that provide efficient methods and interfaces for managing media, such as the methods described herein for exposure compensation, capturing media using a display medium, and displaying indicators of the state of the media. Such techniques can reduce the cognitive burden on users of managing media, thereby increasing productivity. Furthermore, such techniques can reduce processor and battery power that is otherwise wasted on redundant user input.

[0027] 1A-1B, 2, 3, 4A-4B, and 5A-5H below provide descriptions of example devices for performing the techniques for managing media.

[0028] 6A-6V illustrate example user interfaces for managing exposure compensation, according to some embodiments. FIG 7 is a flow diagram illustrating an example method for managing exposure compensation, according to some embodiments. The user interfaces of FIGS. 6A-6V are used to illustrate the processes described below, including the process of FIG 7.

[0029] 8A-8L illustrate example user interfaces for displaying media, according to some embodiments. FIG 9 is a flow diagram illustrating an example method for displaying media, according to some embodiments. The user interfaces of FIGS. 8A-8L are used to illustrate the processes described below, including the process of FIG 9.

[0030] 10A-10AC illustrate example user interfaces for displaying status indicators, according to some embodiments. FIG 11 is a flow diagram illustrating an example method for displaying status indicators, according to some embodiments. The user interfaces of FIGS 10A-10AC are used to illustrate processes described below, including the process of FIG 11.

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

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

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

[0034] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Optionally, other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide a visual output, such as a display via a CRT display, a display via an LED display, or a 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 the content (e.g., video data rendered or decoded by display controller 156) to be displayed by transmitting data (e.g., image data or video data) via a wired or wireless connection to an integrated or external display generation component to visually generate the content.

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

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

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

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

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

[0040] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of 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 a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, a user feels a tactile sensation such as a "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 action. As another example, movement of a touch-sensitive surface is optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a 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 noted, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

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

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

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

[0044] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. The RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices, by wireless communication. RF circuitry 108 optionally includes well known circuitry for detecting near field Communication (NFC) fields, such as by short-range radios. Wireless communication optionally includes, but is not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), Long Term Evolution (LDO), and other standard cellular technologies.Examples of technologies that may be used include, but are not limited to, wireless technology (IoT), wireless LAN (LAN), wireless LAN (LANG ... The present invention may use any of a number of communications standards, protocols, and technologies, including Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (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 communications protocol, including communications protocols not yet developed as of the filing date of this application.

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

[0046] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a 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 the 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, etc. In some embodiments, the input controller(s) 160 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include up and down buttons for volume control of speaker 111 and / or microphone 113. The one or more buttons optionally include push buttons (e.g., 206 in FIG. 2). In some embodiments, the electronic device is a computer system in communication with one or more input devices (e.g., via wireless communication, via wired communication). 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 user gestures (e.g., hand 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.

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

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

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

[0050] Touchscreen 112 optionally uses LCD (Liquid Crystal Display), LPD (Light Emitting Polymer Display), or LED (Light Emitting Diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a number of now known or later developed touch sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

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

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

[0053] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. A user optionally contacts the touch screen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to primarily handle finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touch screen. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

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

[0056] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still images or video. In some embodiments, the light sensor is located on the back side of device 100, as opposed to touchscreen display 112, which is on the front side of the device, so that the touchscreen display is effective for use as a viewfinder for acquisition of still and / or video images. In some embodiments, the light sensor is located on the front of the device so that an image of the user is, optionally, obtained for videoconferencing and the user sees other videoconference participants on the touchscreen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing) so that a single light sensor 164 is used for both videoconferencing and still and / or video image capture, along with the touchscreen display.

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

[0058] In some embodiments, a depth map (e.g., a depth map image) contains information (e.g., values) regarding the distance of objects in a scene from a viewpoint (e.g., a camera, light sensor, depth camera sensor). In one embodiment of a depth map, each depth pixel defines a location in the Z-axis of the viewpoint where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels, each pixel defined by a value (e.g., 0-255). For example, a value of "0" represents a pixel located furthest in a "3D" scene, and a value of "255" represents a pixel located closest to the viewpoint (e.g., a camera, light sensor, depth camera sensor) in the "3D" scene. In other embodiments, a depth map represents a distance between objects in a scene and the plane of the viewpoint. In some embodiments, a depth map contains information regarding the relative depth of various features of an object of interest as seen by a depth camera (e.g., the relative depth of the eyes, nose, mouth, and ears on a user's face). In some embodiments, the depth map contains information that enables the device to determine the contour of the object of interest in the z-direction.

[0059] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical 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 juxtaposed 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 touchscreen display 112 located on the front of device 100.

[0060] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to an input controller 160 within I / O subsystem 106. The proximity sensor 166 optionally functions 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 incorporated herein by reference in their entireties. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

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

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

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

[0064] 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 that control and manage common system tasks (e.g., memory management, control of storage devices, power management, etc.) and facilitate communication between various hardware and software components.

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

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

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

[0068] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are 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 (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by detecting a finger up (lift off) event.

[0069] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, characters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

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

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

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

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

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

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

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

[0077] 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 is optionally used to enter character sequences corresponding to telephone numbers, access one or more telephone numbers in contacts module 137, modify entered telephone numbers, dial respective telephone numbers, conduct a conversation, and terminate or hang up when the conversation is completed. As previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0078] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with user commands.

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

[0080] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering character sequences corresponding to instant messages, modifying previously entered characters, sending respective instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephony-based instant messaging, or XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0081] In conjunction with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 contains executable instructions for creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (sports devices), receiving training sensor data, calibrating sensors used to monitor the workouts, selecting and playing music for the workouts, and displaying, storing, and transmitting the workout data.

[0082] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions for capturing and storing still images or video (including video streams) in memory 102, modifying characteristics of the still images or video, or deleting still images or video from memory 102.

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

[0084] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

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

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

[0088] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, search module 151 contains executable instructions for searching for text, music, sound, images, 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 commands.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] 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 is part of another module stored in memory 102, such as contact / motion module 130.

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

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

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

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

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

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

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

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

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

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

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

[0119] 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.

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

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

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

[0123] 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 control button 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external port 124 for docking / charging. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predefined period of time, to lock the device by pressing and releasing the button before the predefined time has elapsed, and / or to unlock the device or initiate an unlocking process. In alternative embodiments, device 100 also accepts verbal input via microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 for generating a tactile output to a user of device 100.

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

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

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

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

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

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

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

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

[0132] FIG. 5A illustrates an exemplary personal electronic device 500. Device 500 includes a 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 a 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. Similar to devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of a contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representative of the intensity of the touch. A user interface of device 500 can respond to a touch based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface actions on device 500.

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

[0134] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical mechanisms. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow device 500 to be attached to, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

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

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

[0137] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, can cause the computer processors to perform the techniques described below, including processes 700, 900, and 1100 (FIGS. 7, 9, and 11). 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 an instruction execution system, apparatus, or device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media can include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CDs, DVDs, or Blu-ray technology, as well as resident solid-state memory such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in multiple configurations.

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

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

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

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

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

[0143] An increase in the characteristic intensity of a contact from an intensity below the light pressure intensity threshold to an intensity between the light pressure intensity threshold and the deep pressure intensity threshold may be referred to as inputting a "light press." An increase in the characteristic intensity of a contact from an intensity below the deep pressure intensity threshold to an intensity above the deep pressure intensity threshold may be referred to as inputting a "deep press." An increase in the characteristic intensity of a contact from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressure intensity threshold may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as detecting a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

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

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

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

[0147] As used herein, an "installed application" refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and / or 500) and is ready to run (e.g., opened) on the device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the computer system's operating system.

[0148] As used herein, the terms "open application" or "running application" refer to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is, optionally, any one of the following types of applications: ● the active application currently displayed on the display screen of the device on which the application is being used; Background applications (or background processes) that are not currently displayed, but for which one or more processes are being processed by one or more processors; and - Suspended or hibernated applications that are not running but have state information stored in memory (volatile and non-volatile respectively) and that can be used to resume execution of the application.

[0149] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process for the application and removing state information for the application from the device's memory. Generally, opening a second application during a first application does not close the first application. When the second application is displayed and the first application is taken off the display, the first application becomes a background application.

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

[0151] 6A-6V show example user interfaces for managing exposure compensation using an electronic device, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0152] 6A shows electronic device 600 displaying a camera user interface, including a live preview 630 that optionally extends from the top of the display to the bottom of the display. Device 600 optionally includes one or more features of device 100, device 300, or device 500.

[0153] Live preview 630 shows a particular scene (e.g., the sky in FIG. 6A ) within the field of view of one or more cameras. Live preview 630 is a representation of the (e.g., partial) field of view ("FOV") of one or more cameras of device 600. Live preview 630 is based on images detected in the FOV. In some embodiments, device 600 captures images using multiple camera sensors and combines them to display live preview 630. In some embodiments, device 600 captures images using a single camera sensor and displays live preview 630.

[0154] The camera user interface of Figure 6A includes an indicator region 602 and a control region 606. The indicator region 602 and the control region 606 are overlaid on the live preview 630 such that the indicators and controls can be displayed simultaneously with the live preview 630. The camera viewing region 604 is sandwiched between the indicator region 602 and the control region 606 and does not substantially overlap the indicators or controls.

[0155] As shown in FIG. 6A, indicator area 602 includes indicators such as a flash indicator 602a and an animated image indicator 602b. Flash indicator 602a indicates whether the flash is on, off, or in another mode (e.g., automatic mode). In FIG. 6A, flash indicator 602a indicates to the user that the flash is off. Animated image indicator 602b indicates whether the camera is configured to capture a single image or multiple images (e.g., in response to detecting a request to capture media). In some embodiments, indicator area 602 includes an overlay superimposed on live preview 630, optionally colored (e.g., gray, semi-transparent).

[0156] 6A, camera viewing area 604 includes live preview 630 and zoom affordance 622. Here, the "1x" zoom affordance is selected, indicating that live preview 630 is presented at a 1x zoom level.

[0157] As shown in FIG. 6A, the control area 606 includes a shutter affordance 610, a camera switcher affordance 614, a representation of a media collection 612, and a camera settings affordance 626. The shutter affordance 610, when activated, causes the device 600 to capture media (e.g., a photo) using one or more camera sensors based on the current state of the live preview 630 and the current state of the camera application. The captured media is stored locally on the electronic device 600 and / or transmitted to a remote server for storage. The camera switcher affordance 614, when activated, causes the device 600 to switch to show a different camera's field of view in the live preview 630, such as by switching between a rear camera sensor and a front camera sensor. The representation of the media collection 612 shown in FIG. 6A is a representation of media (images, videos) most recently captured by the device 600. In some embodiments, in response to detecting a gesture on the media collection 612, the device 600 displays a user interface similar to the user interface shown in FIG. 8A (described below). As shown in FIG. 6A, the camera settings affordances 626 include a flash settings affordance 626a, an animated image capture settings affordance 626b, an aspect ratio settings affordance 626c, an exposure compensation settings affordance 626d, a timer settings affordance 626e, and a filter settings affordance 626f. The camera settings affordances 626, when selected (e.g., via a gesture detected on a particular camera settings affordance), cause the device 600 to change (or initiate a process to change) a camera setting associated with a particular camera mode. For example, the flash settings affordance 626a, when activated, causes the device 600 to turn the flash mode on / off, and the timer affordance 626d, when selected, causes the device to initiate a process to set a self-delay timer.In some embodiments, the control area 606 includes an optionally colored (e.g., gray, semi-transparent) overlay superimposed on the live preview 630. In Figure 6A, the device 600 detects a tap gesture 650a on (e.g., at a location corresponding to) the exposure compensation settings affordance 626d.

[0158] 6B , in response to detecting the tap gesture 650a, the device 600 displays an exposure compensation indicator 602d in the indicator area 602 simultaneously with the live preview 630. In some embodiments, in response to detecting the tap gesture 650a, the device 600 displays the exposure compensation indicator 602d in the indicator area 602 because the device 600 activates an exposure compensation mode.

[0159] The exposure compensation indicator 602d includes an exposure compensation value representation 602d1 and a clipping indication 602d2. Each of the exposure compensation value representation 602d1 and the clipping indication 602d2 is displayed outside the camera viewing area 604. In some embodiments, the live preview 630 extends into the indicator area 602 and / or the control area 606, and in response to receiving a request to display a captured media representation representing the live preview 630, the device 600 displays a representation of the portion of the live preview 630 shown in the camera viewing area 604 without displaying a representation of the portion of the live preview 630 in the indicator area 602 and the control area 606. Thus, in some embodiments, the exposure compensation value representation 602d1 and the clipping indication 602d2 are displayed outside the camera viewing area 604 such that the portion of the live preview 630 (e.g., in the camera viewing area 604) that is shown in response to receiving a request to display captured media representing the live preview 630 is not obscured.

[0160] As shown in FIG. 6B, exposure compensation value representation 602d1 is a numeric value ("0" in FIG. 6B) that indicates a level of exposure that device 600 uses to capture media in response to receiving a request to capture media (e.g., in response to detecting a gesture on shutter affordance 610). In some embodiments, the exposure level indicated by exposure compensation value representation 602d1 can be combined with one or more other exposure compensation values ​​(e.g., exposure compensation bias values). In some embodiments, device 600 is configured to capture media using a total compensation value (e.g., a combination of the exposure compensation level indicated by exposure compensation value representation 602d1 combined with other exposure compensation values) in response to receiving a request to capture media, as described below (e.g., in FIGS. 6F-6I).

[0161] In FIG. 6B, the clipping indication 602d2 indicates the predicted magnitude and type of clipping predicted to occur in response to detecting a request to capture the current media. As used herein, the "current media" is (1) the media representing the live preview 630, and (2) the media captured (or to be captured) in response to detecting a request to capture the media while the device 600 is configured to capture the media at an exposure level indicated by the exposure compensation value representation 602d1 and / or the total level of exposure compensation. As described in more detail below, the predicted magnitude of clipping is represented by the size (e.g., length, width), thickness, and / or opacity of the clipping indication 602d2. Furthermore, the type of predicted clipping is represented by the position of the clipping indication 602d2. As shown in FIG. 6B and FIG. 6J, the clipping indication 602d2 can indicate the predicted occurrence of two types of clipping: highlight clipping and shadow clipping. In some embodiments, highlight clipping is predicted to occur when a determination is made that a set of luminance intensity values ​​(e.g., white values ​​or highlights of an image (e.g., to be captured)) within the FOV (or current media) exceeds a range of luminance intensity values ​​(e.g., a non-zero range) that can be accurately captured and / or represented within the current media. In other words, the set of luminance intensity values ​​is too bright to be accurately captured and / or represented by device 600 (e.g., in the current media). In some embodiments, shadow clipping is predicted to occur when a determination is made that a luminance intensity value (e.g., black values ​​or shadows of an image (e.g., to be captured)) within the FOV (or current media) falls below a range of luminance intensity values ​​that can be accurately captured and / or represented within the current media. In other words, the set of luminance intensity values ​​is too dark to be accurately captured and / or represented by device 600 (e.g., in the current media).In Figure 6B, the clipping indication 602d2 indicates that highlight clipping is predicted to occur because the clipping indication 602d2 is positioned to be the rightmost tick of the exposure compensation indicator 602d. However, the clipping indication 602d2 in Figure 6J indicates that shadow clipping is predicted to occur because the clipping indication 602d2 is positioned to be the leftmost tick of the exposure compensation indicator 602d in Figure 6J (or the opposite side as the clipping indication 602d2 is illustrated in Figure 6A).

[0162] As shown in FIG. 6B, in response to detecting the tap gesture 650a, the device 600 also replaces the camera settings affordance 626 with an exposure compensation control 636 in the control area 606. The exposure compensation control 636 is a slider displayed with a value indication 636a positioned at a scale on the slider. The positioning of the value indication 636a represents a current exposure compensation level value (e.g., 0), which corresponds to the exposure compensation value indicated by the exposure compensation value representation 602d1. During the transition between FIG. 6B and FIG. 6C, the environment becomes brighter and the device 600 detects a change in FOV indicating that the environment of the scene in the FOV is brighter.

[0163] In FIG. 6C, in response to detecting a change in FOV, a determination is made that a second amount (or level) of highlight clipping is predicted to occur. In FIG. 6C, the second amount of highlight clipping predicted to occur is greater than the amount of highlight clipping predicted to occur in FIG. 6B. In FIG. 6C, the second amount is greater than the amount of highlight clipping predicted to occur in FIG. 6B because the luminance level in the environment increased (e.g., as seen when comparing live preview 630 shown in FIG. 6B-FIG. 6C) and the current exposure compensation level remained the same (e.g., as shown by exposure compensation value representation 602d1). Thus, in FIG. 6C, device 600 detects a greater luminance intensity value above the range of luminance intensity values ​​than device 600 detected in FIG. 6B (e.g., to display live preview 630).

[0164] As shown in FIG. 6C, in response to detecting a change in FOV, a determination is made that a second amount of highlight clipping is predicted to occur, and thus the device 600 increases the size of the clipping indication 602d2, indicating that greater highlight clipping is predicted to occur in FIG. 6C than was predicted to occur in FIG. 6B. Thus, in FIG. 6C, the clipping indication 602d2 indicates the type and amount of clipping predicted to occur. Specifically, the clipping indication 602d2 in FIG. 6C is longer and wider than the clipping indication 602d2 in FIG. 6B. During the transition between FIG. 6C and FIG. 6D, the environment becomes brighter, and the device 600 detects more changes in the FOV, indicating that the environment of the scene within the FOV is brighter.

[0165] In FIG. 6D, a determination is made that a third amount of highlight clipping is predicted to occur. In FIG. 6D, the third amount of highlight clipping predicted to occur is greater than the second amount of highlight clipping predicted to occur in FIG. 6C. Here, the third amount of highlight clipping is greater than the second amount of highlight clipping because the luminance level in the environment (e.g., as seen when comparing the live preview 630 shown in FIG. 6C-FIG. 6D) has increased and the current exposure compensation level (e.g., as shown by the exposure compensation value representation 602d1) has remained the same. In FIG. 6D, a determination is made that a third amount of highlight clipping is predicted to occur using one or more similar techniques such as those described above in connection with FIG. 6C.

[0166] As shown in FIG. 6D, in response to detecting a change in FOV (e.g., in FIG. 6C), a determination is made that a third amount of highlight clipping will occur, and thus the device 600 increases the size 602d2 of the clipping indication to indicate that the third amount of highlight clipping predicted to occur is greater than the second amount of highlight clipping predicted to occur in FIG. 6C (e.g., using one or more similar techniques as described above in connection with FIG. 6C). Thus, in FIG. 6D, the clipping indication 602d2 indicates the type and amount of clipping predicted to occur. In some embodiments, the device 600 displays an animation of the clipping indication 602d2 increasing in size from the size of the clipping indication 602d2 in FIG. 6B to the size of the clipping indication 602d2 in FIG. 6D. In FIG. 6D, the device 600 detects a rightward swipe gesture 650d on the exposure compensation control 636.

[0167] As shown in Figure 6E, in response to detecting a right swipe gesture 650d, the device 600 updates the exposure compensation control 636 such that the value indication 636a is positioned at a value (e.g., -0.2) that represents the updated exposure compensation level. In addition, the device 600 also updates the exposure compensation value representation 602d1 to reflect the value (e.g., -0.2) that represents the updated exposure compensation level. Compared to Figure 6D, the value of the updated exposure compensation level is decreased in Figure 6E.

[0168] In FIG. 6E, a determination is made that a fourth amount of highlight clipping is predicted to occur because the current exposure compensation level has changed (e.g., from 0 to −0.2). In FIG. 6E, the fourth amount of highlight clipping predicted to occur is less than the third amount of highlight clipping predicted to occur in FIG. 6D. In FIG. 6E, the fourth amount is less than the third amount because the exposure compensation level that device 600 uses to capture the current media has decreased (e.g., from 0 to −0.2). When device 600 captures the current media using a lower exposure compensation value, device 600 is configured to capture lower luminance intensity values ​​(e.g., less white) in response to receiving a request to capture the media. Capturing the effectively lower luminance values ​​results in device 600 capturing lower luminance intensity values ​​above a range of luminance intensity values. As shown in Figure 6E, because a determination is made that a fourth amount of clipping is predicted to occur, the device 600 reduces the size of the clipping indication 602d2, which indicates that the fourth amount of clipping predicted to occur is less than the third amount of clipping predicted to occur. Thus, in Figure 6E, the clipping indication 602d2 indicates the type and amount of clipping predicted to occur.

[0169] As shown in Figure 6E, device 600 also darkens live preview 630 to reflect the media that will be captured based on the updated exposure compensation level. Here, live preview 630 is darker (compared to live preview 630 of Figure 6D) because device 600 is configured to capture a lower brightness intensity value in response to receiving a request to capture media (e.g., based on a lower exposure compensation value). In Figure 6E, device 600 detects a downward swipe gesture 650e within camera viewing area 604.

[0170] As shown in FIG. 6F, in response to detecting a downward swipe gesture 650e, the device 600 replaces the exposure compensation control 636 with the camera mode affordance 620 in the control area 606. The camera mode affordance 620 indicates which camera mode is currently selected and allows the user to change the camera mode. In FIG. 6F, the camera mode affordances 620a-620e are displayed. The camera mode affordances 620 indicate that the photo camera mode is active, as indicated by the photo camera mode affordance 620c and the bolded "Photo." As shown in FIG. 6F, the device 600 also ceases to display the exposure compensation control 636 but continues to display the exposure compensation indicator 602d. In FIG. 6F, continuing to display the exposure compensation indicator 602d includes maintaining the exposure compensation value representation 602d1 at the same size and with the same exposure compensation value (e.g., -0.2) and clipping instructions 602d2 as displayed in FIG. 6E. Thus, in Figure 6F, turning off display of compensation control 636 did not affect the current exposure compensation value (e.g., as indicated by exposure compensation value representation 602d1) or the determination of predicted clipping (e.g., as indicated by clipping indication 602d2). In Figure 6F, device 600 detects a press and hold gesture 650f in (at a location corresponding to) camera display area 604.

[0171] As shown in Figure 6G, in response to detecting a press and hold gesture 650f, the device 600 locks an autofocus setting on the device 600 such that the device 600 focuses one or more of its cameras to a particular focal distance (e.g., position) within the FOV. In Figure 6G, the position corresponds to the area of ​​a box of a compensation bias control 644 displayed in the camera viewing area 604 of Figure 6G. The compensation bias control 644 is displayed with a value indication 644a located at a position on the compensation bias control 644 that corresponds to a current exposure compensation bias value that the device 600 is currently configured to capture the current media (e.g., in response to receiving a request to capture media).

[0172] In Figure 6G, device 600 detects a downward swipe gesture 650g in camera viewing area 604. Figures 6H-6I show alternative user interfaces that may be displayed in response to detecting downward swipe gesture 650g.

[0173] As shown in FIG. 6H, in response to detecting the downward swipe gesture 650g, the device 600 updates the compensation bias control 644 such that a value indication 644a is displayed at a new location on the compensation bias control 644 to indicate that an updated exposure compensation bias value has been updated. The updated exposure compensation bias value of FIG. 6H is lower than the exposure compensation bias value of FIG. 6G. Thus, as shown in FIG. 6H, the live preview 630 becomes darker due to the lower compensation bias value. In FIG. 6H, the device 600 is configured to capture media based on a total compensation value (e.g., the sum of the exposure compensation value represented by the exposure compensation value representation 602d1 and the updated exposure compensation bias value). However, as shown in FIG. 6H, the device 600 does not update the exposure compensation indicator 602d to reflect the change in the total exposure compensation. 6H , the device 600 displays a representation of the total exposure compensation simultaneously with the exposure compensation indicator 602d (e.g., because the compensation indicators are displayed with the same exposure compensation value representation (e.g., −0.2) and the clipping indication 602d2 are the same size). In some embodiments, the representation of the total exposure compensation is displayed in the camera viewing area 604 while the exposure compensation indicator 602d remains displayed in the indicator area 602.

[0174] As an alternative to Fig. 6H, as shown in Fig. 6I, device 600 updates compensation bias control 644 and live preview 630 in response to detecting downward gesture 650g using a technique similar to that described above in Fig. 6H. However, in Fig. 6I, device 600 updates exposure compensation indicator 602d (e.g., not updated in Fig. 6H) to reflect a change in total exposure compensation. For example, device 600 updates exposure compensation value representation 602d1 such that total exposure compensation is -0.3 in response to a request to capture current media, and updates clipping indication 602d2 to reflect that lower predicted clipping is predicted to occur (e.g., due to a lower total exposure compensation value using the technique described above). In Fig. 6H or Fig. 6I, device 600 detects a change in FOV.

[0175] In Figure 6J, in response to detecting a change in the FOV (e.g., in Figure 6H or Figure 6I), a determination is made that the scene within the FOV has changed. As shown in Figure 6J, the live preview 630 shows a pair of shoes on a dark surface, while the live preview 630 of Figure 6I shows sky. In comparison to the live preview 630 of Figure 6I, the live preview 630 of Figure 6J is significantly darker as the scene within the FOV is significantly darker.

[0176] In FIG. 6J, because a determination is made that the scene has changed within the FOV, device 600 resets the exposure compensation bias value to a default exposure compensation bias value (e.g., the compensation bias value set prior to detecting gesture 650f of FIG. 6F or gesture 650g of FIG. 6G). As shown in FIG. 6J, device 600 also ceases displaying compensation bias indicator 644 due to this scene change determination. Notably, in FIG. 6J, device 600 remains configured to capture the current media via the exposure compensation level (e.g., −0.2) indicated by exposure compensation value indication 602d2 of FIG. 6F (e.g., before the compensation bias value was displayed and / or adjusted (e.g., in FIGS. 6F-6G)). Thus, the set compensation bias value is eliminated (e.g., reverted to a default value) when the scene within the FOV changes, whereas the exposure compensation value set (e.g., via exposure compensation control 636) is maintained regardless of the determination that the scene has changed within the FOV.

[0177] In Figure 6J, a determination is also made that shadow clipping is predicted to occur because the luminance level in the environment in the new scene (e.g., shoes on a dark surface) is significantly reduced. Specifically, a determination is made that shadow clipping is predicted to occur because a set of luminance intensity values ​​(e.g., black values ​​or shadows of an image (e.g., to be captured)) in the FOV (or current media) is determined to be below a range of luminance intensity values ​​that can be accurately represented or captured. The determination that shadow clipping is predicted to occur is based on the luminance level in the environment and the current exposure compensation level (e.g., -0.2 as shown by exposure compensation value representation 602d1).

[0178] As shown in Figure 6J, because a determination is made that shadow clipping is predicted to occur, device 600 displays clipping indication 602d2 as the leftmost tick mark of exposure compensation indicator 602d (e.g., instead of being displayed as the rightmost tick mark of exposure compensation indicator 602 as in Figure 6F when highlight clipping is predicted to occur). In Figure 6J, the size of clipping indication 602d2 has also changed to reflect the magnitude (e.g., amount or level) of shadow clipping predicted to occur when device 600 is configured to capture media at the current exposure compensation level (e.g., -0.2). In Figure 6J, device 600 detects a change in the FOV.

[0179] In Figure 6K, in response to detecting a change in the FOV, a determination is made that the scene has changed in the FOV. In comparison to the live preview 630 of Figure 6J, the live preview 630 of Figure 6K is significantly darker because the scene in the FOV of Figure 6K is significantly darker. In Figure 6K, a determination is also made that a second amount of shadow clipping is predicted to occur using one or more techniques such as those described above (e.g., in Figures 6B-6J). In Figure 6K, the second amount of shadow clipping is greater than the amount of shadow clipping predicted to occur in Figure 6J because a darker scene was in one or more cameras' FOVs and the current exposure compensation level remained the same.

[0180] As shown in FIG 6K, because a determination is made that a second amount of shadow clipping is predicted to occur, the device 600 increases the size of the clipping indication 602d2 while maintaining the display of the clipping indication 602d2 to the left of the exposure compensation indicator 602d. Thus, in FIG 6K, the clipping indication 602d2 indicates the type and amount of clipping predicted to occur. Additionally, the live preview 630 is updated to show the new scene. In FIG 6K, the device 600 detects a tap gesture 650k on the exposure compensation indicator 602d.

[0181] As shown in Figure 6L, in response to detecting a tap gesture 650k, the device 600 replaces the display of the camera affordance 620 with a display of the exposure compensation control 636, which includes a value indication 636a. In Figure 6L, the device 600 detects a leftward swipe gesture 650l on the exposure compensation control 636.

[0182] As shown in Figure 6M, in response to detecting a left swipe gesture 650l, the device 600 updates the level of exposure compensation, indicated via a new value (e.g., 1.0) represented by the exposure compensation value representation 602d1 and also displayed above the value indication 636a on the exposure compensation control 636. The new exposure compensation level (e.g., 1.0 in Figure 6M) is higher than the previous exposure compensation level (e.g., -0.2 in Figure 6L).

[0183] In FIG. 6M, a determination is made that minimal (or no clipping) is predicted to occur (or clipping below a (e.g., non-zero) threshold level is predicted to occur) using one or more techniques similar to those described above. Thus, in other words, a determination is made that the device 600 can accurately represent or capture the current media with less than a (e.g., non-zero) threshold amount of clipping. As shown in FIG. 6M, due to a determination that minimal or no clipping is predicted to occur (e.g., or clipping below a (e.g., non-zero) threshold level is predicted to occur), the device 600 stops displaying the clipping indication 602d2. In FIG. 6M, the device 600 detects a left swipe gesture 650m on the exposure compensation control 636a.

[0184] As shown in FIG. 6N, in response to detecting the left swipe gesture 650m, the device 600 updates the exposure compensation level, indicated via a new value (e.g., 1.5) represented by the exposure compensation value representation 602d1 and displayed above the value indication 636a on the exposure compensation control 636. The new exposure compensation level (e.g., 1.5 in FIG. 6M) is higher than the previous exposure compensation level (e.g., 1.0 in FIG. 6L). In FIG. 6N, a determination is made that a fifth amount of highlight clipping is predicted to occur (e.g., the exposure compensation level is adjusted sufficiently that highlight clipping is predicted to occur) using one or more similar techniques described above. As shown in FIG. 6N, because a determination is made that a fifth amount of highlight (and no shadow) clipping is predicted to occur, the device 600 displays a clipping indication 602d2 to the right of the exposure compensation indicator 602d. Thus, in FIG. 6N, the clipping indication 602d2 indicates the type and amount of clipping predicted to occur. In FIG. 6N, the device 600 detects an upward swipe gesture 650n from the bottom of the control area 606.

[0185] In FIG. 6O, in response to detecting the upward swipe gesture 650n, a determination is made that a session associated with use of the camera application (e.g., an application corresponding to a camera user interface) has ended, for example, because the device 600 has stopped displaying (or closed from) the camera application. In some embodiments, a session associated with use of the camera application ends when the device 600 has stopped displaying or closed the camera application for a predetermined period of time. In some embodiments, a session associated with use of the camera application ends when a determination is made that the camera application has stopped operating on the device 600. In some embodiments, a session associated with use of the camera application ends at a particular time (at the end of the day (a particular time of the day) when the camera application is not being used or when the camera application is interacted with by a user). In some embodiments, a session associated with use of the camera application ends after the device 600 has been in a locked state for a predetermined period of time. Further, as shown in FIG. 6O, the device 600 stops displaying the camera user interface and displays a user interface with application icons 690. The application icons 690 include application icons, such as the camera application icon 690a. In FIG. 6O, device 600 detects a tap gesture 650o on camera application icon 690a.

[0186] As shown in Figure 6P, in response to detecting a tap gesture 650o, the device 600 stops displaying the user interface with the application icons and displays the camera user interface. As shown in Figure 6P, the exposure compensation indicator 602d is in the same state as it was in Figure 6N. For example, in Figure 6P, the exposure compensation value representation 602d1 indicates a current exposure level of 1.5, which is the same as the exposure level when the camera user interface was last displayed in Figure 6N. In Figure 6P, the device 600 detects a left swipe gesture 650p at the bottom of the control region 606.

[0187] As shown in FIG. 6Q, in response to detecting a left swipe gesture 650p, the device 600 displays a camera user interface including settings 692, such as an exposure control setting 692a. In FIG. 6Q, the exposure control setting 692a is set to on, indicating that the current exposure level is maintained and not automatically reset. Additionally, the exposure control setting 692a indicates that the exposure compensation indicator 602d continues to be displayed (e.g., after exposure compensation is initially set via the exposure compensation control 644). In some embodiments, the control setting 692a indicates that the exposure compensation indicator 602d is always displayed (e.g., regardless of whether exposure compensation is initially set). Referring again to FIGS. 6N-6P, the device 600 maintained the exposure compensation indicator 602d in the same state as in FIG. 6P (e.g., after determining that the session associated with using the camera application has ended) because the control setting 692a is set to on. In FIG. 6Q, the device 600 detects a tap gesture 650q on the exposure control setting 692a.

[0188] In response to detecting a tap gesture 650q, the device 600 toggles the exposure control setting 692a from an on state to an off state, as shown in Figure 6R, in which the device 600 detects an upward swipe gesture 650r at the bottom of the control area 606.

[0189] As shown in Figure 6S, in response to detecting the upward swipe gesture 650r, the device 600 redisplays the user interface with the application icon 690a. In Figure 6S, in response to detecting the upward swipe gesture 650r, a determination is made that a session associated with use of the camera application has ended using a technique similar to that described above with respect to Figure 6O. In Figure 6S, the device 600 detects a tap gesture 650s on the camera application icon 690a.

[0190] As shown in FIG. 6T, in response to detecting the tap gesture 650s, the device 600 displays the camera user interface without the exposure compensation indicator 602d because the exposure control setting 692a is set to on (as opposed to displaying the exposure compensation indicator 602d when the exposure control setting 692a is set to off, as described above).

[0191] FIG. 6U shows a camera user interface with an exposure compensation indicator 602d displayed while device 600 is operating in video mode, as indicated by the video camera mode affordance 602b and the bolded "video" in FIG. 6U.

[0192] FIG. 6V shows a camera user interface with an exposure compensation indicator 602d displayed while the device 600 is operating in portrait mode, as indicated by the portrait camera mode affordance 602e and the bolded “Portrait” in FIG. 6V.

[0193] 7 is a flow diagram illustrating a method for managing exposure compensation using a computer system, according to some embodiments. Method 700 is executed in a computer system (e.g., 100, 300, 500, 600). The computer has one or more cameras (e.g., one or more cameras (e.g., dual camera, triple camera, quad camera, etc.) on the same or different sides (e.g., front camera, rear camera) of the computer system) and communicates with a display generation component (e.g., a display controller, a touch-sensitive display system) and one or more input devices (e.g., a touch-sensitive surface). Some operations of method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0194] As described below, method 700 provides an intuitive way to manage exposure compensation. The method reduces the cognitive burden on the user in managing exposure compensation, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing the user to manage exposure compensation faster and more efficiently conserves power and increases the time between battery charges.

[0195] The computer system receives (702) a request to display a camera user interface (eg, the user interface in FIG. 6B) (eg, a request to display a camera application or to switch to a media capture mode within the camera application).

[0196] In response to receiving a request to display a camera user interface, the one or more cameras are configured to capture an image (e.g., video, photo) based on a first exposure compensation value (e.g., a value representing an amount of exposure used to capture media corresponding to a representation of the field of view of the one or more cameras) (e.g., as indicated by 602d1), and the computer system, via a display generation component, displays (704) the camera user interface (e.g., the user interface of FIG. 6B).

[0197] As part of displaying the camera user interface via the display generation component, the computer system displays (706) via the display generation component a first representation (e.g., 630) (e.g., a time-lapse representation, a live preview feed of data from the camera) of the field of view (e.g., the open observable area that is visible to the camera, the horizontal (or vertical or diagonal) length of the image at a given distance from the camera lens) of one or more cameras. In some embodiments, the value is a default exposure compensation value used to capture media regardless of whether exposure compensation mode is enabled or not. In some embodiments, the representation of the field of view of the one or more cameras is displayed in the camera viewing area.

[0198] As part of displaying to the camera user, and pursuant to a determination that a set of exposure compensation criteria have been met (708), including criteria that are met when an exposure compensation mode is enabled (e.g., active) (e.g., active), the computer system displays (710), concurrently with the representations of the one or more cameras' fields of view (e.g., 630), an exposure compensation indicator (e.g., 602d) that includes: a representation of a first exposure compensation value (e.g., a numerical representation (e.g., 1.5, -1.5), symbolic retransitions) (e.g., as indicated by 602d1); and, in response to receiving a request to capture media corresponding to the representations of the one or more cameras' fields of view (e.g., receiving an input in 610), a visual indication (e.g., 602d2) that the computer system has determined that clipping (e.g., one or more areas of the captured media that lose detail as a result of the exposure compensation setting) is predicted to occur. In some embodiments, one or more cameras are configured to capture images based on a first exposure compensation value, and a representation of the first exposure compensation value is displayed (or, alternatively, not displayed) (e.g., displayed simultaneously with, adjacent to, and / or on top of) a representation of the field of view of the one or more cameras. In some embodiments, the exposure compensation mode is enabled when the computer system is configured to maintain exposure adjustments when displaying different representations of the field of view of the one or more cameras (e.g., representations captured over time or representations of different scenes) and / or when the computer system is configured to show an exposure adjustment indicator. In some embodiments, the exposure compensation mode is enabled when a selection is made on the exposure compensation indicator and / or when a new exposure compensation is set (e.g., via an exposure adjustment control). In some embodiments, when clipping occurs, the clipped area can be represented by a minimum or maximum brightness within the representation of the captured media.In some embodiments, the clipped area in the representation of the captured media has a different level of brightness, highlights, shadows, and / or a different level of detail (e.g., less detail) than an area corresponding to the clipped area in the representation of the field of view of the one or more cameras. In some embodiments, a representation of exposure compensation and a visual indication (e.g., that the computer system has determined that clipping is predicted to occur) are displayed simultaneously. In some embodiments, the exposure compensation indicator is displayed within a camera indicator area. In some embodiments, the camera indicator area includes a number of indicators (e.g., affordances, selectable user interface objects) that configure the computer system to capture media based on one or more camera settings (e.g., exposure settings, flash settings, low light mode settings, timer settings, etc.). In some embodiments, a representation of the exposure compensation value is over the visual indication. In some embodiments, pursuant to a determination that a set of exposure compensation criteria is not met, the computer system ceases displaying the exposure compensation indicator. In some embodiments, in response to a determination that the set of exposure compensation criteria is not met, the first representation is displayed with a default exposure compensation value (e.g., a zero value), and the computer system is configured to capture media using the default exposure compensation value when the exposure compensation mode is not enabled. In some embodiments, the computer system determines that clipping is predicted to occur based on one or more determinations that clipping is predicted to occur in response to receiving a request to capture media corresponding to a representation of the one or more camera fields of view by receiving one or more instructions or bases, or in response to receiving a request to capture media corresponding to a representation of the one or more camera fields of view created by one or more external devices.Displaying the exposure compensation indicator, including the exposure compensation value and an indicator of predicted clipping, provides a user with feedback regarding the relationship between the current exposure compensation value, the current scene within the field of view of the system's cameras, and the predicted clipping that may occur when media corresponding to the current scene is captured. Thus, displaying the exposure compensation indicator allows a user to visually see how adjustments to the current exposure compensation value and / or changes to the scene within the field of view of at least one camera will affect the predicted clipping. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves the battery life of the system by allowing the user to use the system more quickly and efficiently. Displaying an exposure compensation indicator, including an exposure compensation value and an indicator of predicted clipping, provides feedback to a user regarding the relationship between the current exposure compensation value, the current scene within the field of view of the system's camera, and the predicted clipping that may occur when media corresponding to the current scene is captured, which reduces the number of times media needs to be captured to obtain an image with reduced (or little to no) clipping, improves usability of the system by reducing the number of operations that need to be performed, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and also reduces power usage and improves the battery life of the system by allowing the user to use the system more quickly and efficiently.

[0199] In some embodiments, while displaying the exposure compensation indicator (e.g., 602d) and pursuant to a determination that the clipping predicted to occur is a first type of clipping, a visual indication is displayed at a first location (e.g., 602d2 of FIG. 6B) (e.g., on a display generation component (e.g., a location adjacent the exposure compensation indicator)). In some embodiments, while displaying the exposure compensation indicator and pursuant to a determination that the clipping predicted to occur is a second type of clipping that is different from the first type of clipping, a visual indication is displayed at a second location (e.g., 602d2 of FIG. 6J) (e.g., on a display generation component (e.g., a location adjacent the exposure compensation indicator)) that is different from the first location. In some embodiments, a first type of clipping is clipping based on a value of a parameter of the media (e.g., luminance intensity) that exceeds a range of values ​​of the parameter (e.g., a captureable range (e.g., the range of luminance intensity values ​​that can be captured by a computer system), a representable range (e.g., the range of luminance intensity values ​​that can be represented by a computer system) (e.g., clipping of highlights, clipping of brighter / white areas)) (e.g., clipping that is predicted to occur in response to receiving a request to capture the media (e.g., clipping that is predicted to occur when brighter areas (e.g., white areas) of a scene are represented with less detail than other areas of the scene)).In some embodiments, the second type of clipping is clipping based on a value of a parameter of the media (e.g., luminance intensity) falling below a range of values ​​of the parameter (e.g., a captureable range (e.g., a range of luminance intensity values ​​that can be captured by the computer system), a representable range (e.g., a range of luminance intensity values ​​that can be represented by the computer system) (e.g., crushing blacks, clipping of darker / black areas) of luminance intensity values ​​(e.g., in response to receiving a request to capture media (e.g., indicating clipping that is predicted to occur when darker areas (e.g., black areas) of a scene are represented with less detail than other areas of the scene)). In some embodiments, the computer system may perform a clipping operation while displaying the visual indication displayed at the first location and pursuant to a determination that a second (e.g., new, subsequent) clipping is predicted to occur in response to receiving a request to capture media corresponding to a representation of the field of view of one or more cameras and that the second clipping is the first type of clipping. The system displays a visual indication at a first location, and while displaying the visual indication at the first location, and pursuant to a determination that a second (e.g., new, subsequent) clipping is predicted to occur in response to receiving a request to capture media corresponding to a representation of the field of view of the one or more cameras and the second clipping is a second type of clipping, the computer system displays a visual indication at a second location. In some embodiments, the visual indication moves from the first location to the second location, or vice versa. In some embodiments, the first location is on one side (e.g., right / left / up / down) of the exposure compensation indicator and the second location is on the opposite side (e.g., left / right / down / up) to the side on which the first location is on. Displaying an indicator of predicted clipping at different locations on the exposure compensation indicator, where each location corresponds to a type of clipping predicted to occur, provides feedback to the user on how to adjust the current exposure compensation value and / or changes in the scene in the field of view of the cameras to affect (e.g., reduce) the predicted clipping.Providing improved visual feedback to the user improves operability of the system, makes the user-system interface more efficient (e.g., by assisting the user to provide appropriate inputs when operating / interacting with the system and reducing user errors), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently. Displaying an indicator of predicted clipping at one location where highlight clipping is predicted to occur and where shadow clipping is predicted to occur provides feedback to the user on how to adjust the current exposure compensation value and / or scene changes within the camera's field of view to affect (e.g., reduce) the predicted clipping. Providing improved visual feedback to the user improves operability of the system, makes the user-system interface more efficient (e.g., by assisting the user to provide appropriate inputs when operating / interacting with the system and reducing user errors), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0200] In some embodiments, prior to the first time (e.g., while displaying the exposure compensation indicator), the visual indication is displayed having a first visual appearance (e.g., 602d2 of FIG. 6B) (e.g., thickness, size, length, color, thickness, and / or opacity). In some embodiments, at the first time while displaying the exposure compensation indicator, and pursuant to a determination that clipping predicted to occur has been changed (e.g., the amount of clipping has been changed, the type of clipping has been changed), the computer system displays a visual indication (e.g., 602d2 of FIG. 6C) having a second visual appearance (e.g., thickness, size, length, color, thickness, and / or opacity) that is different from the first visual appearance (e.g., 602d2 of FIG. 6B). In some embodiments, pursuant to a determination that the predicted clipping to occur has increased (or, alternatively, decreased), the visual indicator has an appearance (e.g., a second appearance) that is thicker (e.g., in width) (e.g., thicker, more opaque) and / or longer (e.g., in height) (or, alternatively, thinner (e.g., in width) and / or shorter (e.g., in height) than the visual indicator previously had (e.g., a first appearance). In some embodiments, displaying the visual indication in a second appearance that is different from the first visual appearance includes animating (e.g., gradually animating) a change (e.g., thickening or thinning) of the visual indication from the first visual appearance to the second visual appearance. In some embodiments, it is determined that the predicted clipping to occur changes when the field of view of one or more cameras and / or objects within the field of view of the one or more cameras changes. In some embodiments, the predicted clipping changes in response to a change from a first compensation value to a second exposure compensation value (e.g., via a selectable exposure compensation control (e.g., a slider)). In some embodiments, the predicted clipping changes in response to a change in the field of view of one or more cameras (e.g., a change in the scene in the field of view of one or more cameras).Displaying an indicator of predicted clipping based on the magnitude of the predicted clipping provides feedback to the user on how to adjust current exposure compensation values ​​and / or scene changes within the field of view of one or more cameras to affect (e.g., reduce) the predicted clipping. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0201] In some embodiments, the visual indication (e.g., 602d2) is displayed via a display generation component at a location outside (e.g., away from, not on, not overlapping with) the first representation. In some embodiments, the exposure compensation indicator is at a location outside the first representation. Displaying an indicator of predicted clipping away from the representation of the scene provides the user with feedback regarding the relationship between the current exposure compensation values ​​and the current scene within the field of view of the system's cameras, and predicted clipping that may occur when media corresponding to the current scene is captured while allowing the representation of the scene within the field of view of at least one camera of the computer system to be viewed with fewer visual elements superimposed on the representation of the scene, which may reduce the amount of time it takes to capture the intended scene. Improves usability of the system by reducing the number of inputs required to perform operations, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the system), plus reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0202] In some embodiments, while displaying an exposure compensation indicator (e.g., 602d) including a representation of the first exposure compensation value (e.g., as shown by 602d1 in FIG. 6B ), the computer system detects a change in the field of view of one or more cameras. In some embodiments, in response to detecting the change in the field of view of one or more cameras, the computer system continues to display the first exposure compensation value (e.g., as shown by 602d1 in FIG. 6C ) (e.g., the exposure compensation value is maintained regardless of the detected change in the field of view (and / or a change in the scene) of the one or more cameras). In some embodiments, pursuant to a determination that the change in the field of view of one or more cameras exceeds a threshold value (e.g., a non-zero threshold value) (the threshold value indicating the amount of change in the field of view is comparable to a change in the scene), the computer system continues to display the exposure compensation indicator including the first exposure compensation value. In some embodiments, pursuant to a determination that the change in the field of view of one or more cameras exceeds a threshold value, the computer system continues to display the exposure compensation indicator including the first exposure compensation value. Maintaining the exposure compensation value as the scene changes reduces (or eliminates) the number of inputs it takes to reset the compensation value each time the scene changes, and also reduces the number of times the exposure compensation is reset when the scene changes temporarily in the field of view of one or more cameras. Reducing the number of inputs required to perform an operation improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the system), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0203] In some embodiments, one or more cameras are configured to capture images based on a cumulative exposure compensation value that is based on the sum of a first exposure compensation value (e.g., as shown by 602d1) and a compensation bias value (e.g., 644a in FIG. 6H).

[0204] In some embodiments, following a determination that the set of exposure compensation criteria is satisfied, the computer system simultaneously displays (712) (e.g., displays a value, displays a graphical representation corresponding to a value) an indication of the cumulative exposure compensation value (e.g., as shown by 602d1 in FIG. 6I ) along with an exposure compensation indicator (e.g., 602d) (e.g., includes a representation of the first compensation value at a first time when the one or more cameras are configured to capture an image based on the first exposure compensation value). In some embodiments, while displaying the exposure compensation indicator (e.g., includes a representation of the first exposure compensation value), the computer system receives one or more user inputs (e.g., a tap input followed by a drag input), and in response to receiving the one or more user inputs, the computer system displays the cumulative exposure compensation value simultaneously with the exposure compensation indicator including the representation of the first compensation value. Displaying the indication of the cumulative exposure compensation value provides a user with feedback regarding how the exposure compensation value and the bias compensation value affect the cumulative amount of exposure used to capture media in response to a request to capture media. By providing improved feedback, it improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0205] In some embodiments, while displaying an exposure compensation indicator (e.g., 602d) including a representation of the first exposure compensation value (e.g., as shown by 602d1 in FIG. 6G), the computer system detects one or more user inputs (e.g., 650f, 650g, 650h) (e.g., a tap input followed by a drag input, such as on a viewfinder of one or more cameras' fields of view) via one or more input devices. In some embodiments, in response to detecting the one or more inputs, the computer system changes the compensation bias value from a default compensation bias value (e.g., 644a in FIG. 6G) (e.g., a default compensation value (e.g., a value of zero)) to a new compensation bias value (e.g., 644a in FIG. 6H) (e.g., a non-zero value, new compensation value). In some embodiments, the computer system is configured to capture an image based on a cumulative compensation based on a sum of the first exposure compensation value and the bias compensation value, and continues to display the representation of the first exposure compensation value. In some embodiments, while displaying the exposure compensation indicator including a representation of the first exposure compensation value and the compensation bias value that are changed to new compensation values, the computer system detects a change in the field of view of one or more cameras (e.g., a scene change). In some embodiments, in response to detecting the change in the field of view of one or more cameras and in accordance with a determination that the change in the field of view of one or more cameras exceeds a threshold value (e.g., a non-zero threshold value) (the threshold value indicating the amount of change in the field of view is comparable to the amount of change in the scene), the computer system updates (e.g., resets) the compensation bias value to a default compensation bias value and continues to display the representation of the first exposure compensation value (e.g., 602d2 of FIG. 6J). In some embodiments, in response to detecting the change in the field of view of one or more cameras and in accordance with a determination that the change in the field of view of one or more cameras exceeds a threshold value, the computer system continues to display the exposure compensation indicator including an indication of the first exposure compensation value (e.g., the exposure compensation value is not changed), refrains from updating (e.g., resetting) the compensation value to the default bias compensation value, and / or maintains the bias compensation value (e.g., the bias compensation value is not changed).Maintaining the exposure compensation value as the scene changes and updating the bias value reduces the number of inputs it takes to reset the compensation value each time the scene changes, and also reduces the number of times the exposure compensation is reset when the scene changes temporarily in the field of view of one or more cameras. Reducing the number of inputs required to perform operations improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the system), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0206] In some embodiments, following a determination that the set of reset criteria is met, the computer system sets the first exposure compensation value to a default compensation value (e.g., as shown by 602d1 in FIG. 6T). In some embodiments, the set of reset criteria includes a first criterion that is met upon termination of the media capture session and a second criterion that is met when the exposure compensation save mode is not enabled (e.g., 692a in FIG. 6R). In some embodiments, following a determination that the set of reset criteria is not met, the computer system refrains from setting the first exposure compensation value to the first (e.g., default) compensation value (e.g., as shown by 602d1 in FIG. 6P). In some embodiments, the computer system maintains the first exposure compensation value as the value the first exposure compensation value was before termination of the media capture session.

[0207] In some embodiments, the set of exposure compensation criteria includes criteria that are met when the exposure compensation save mode is enabled (e.g., 692a in FIG. 6Q). In some embodiments, the set of exposure compensation criteria includes criteria that are met when the first exposure compensation value is not equal to the default compensation value. In some embodiments, the set of exposure compensation criteria includes criteria that are met when the exposure compensation save mode is enabled and the exposure compensation is at the default value. In some embodiments, the set of exposure compensation criteria includes criteria that are met when the first exposure compensation value is not equal to the default compensation value, the exposure compensation save mode is enabled and the exposure compensation is at the default value. Automatically displaying the exposure compensation indicator only when a predefined condition is met allows for the display of the indicator without requiring additional user input. Taking action when a set of conditions is met without requiring further user input enhances the operability of the system, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), plus reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently.

[0208] In some embodiments, following a determination that the set of exposure compensation criteria is not met, the computer system ceases displaying the exposure compensation indicator (e.g., 602 in FIG. 6M). In some embodiments, after displaying the exposure compensation indication, the computer system receives one or more inputs that deactivate the exposure compensation mode (e.g., receives an input of one of the selectable user interface objects for configuring the exposure compensation mode), and in response to receiving the one or more inputs, the computer system stops displaying the (e.g., previously displayed) exposure compensation indicator. Automatically displaying the exposure compensation indicator when a predefined condition is met allows for the display of the indicator without requiring additional user input. Taking action when a set of conditions is met without requiring further user input enhances the operability of the system, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), as well as reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently.

[0209] In some embodiments, at a second time while displaying the exposure compensation indicator, pursuant to a determination that the predicted clipping to occur has changed, the computer system displays an animation (e.g., 602 in FIGS. 6B-6D ) of the exposure compensation indication transitioning from a first visual state (e.g., a first position and / or visual appearance (e.g., thickness, size, color, thickness, opacity) of the indication, a visual state of the first compensation value) to a second visual state (e.g., a first position and / or visual appearance (e.g., thickness, size, color, thickness, opacity) of the indication, a visual state of the second compensation value) that is different from the first visual state. In some embodiments, the animation includes moving the visual indication to a different position, thinning / thickening the visual indication, and / or displaying the first compensation value changed to the second compensation value. Displaying an animation of the exposure compensation indicator that changes as the predicted clipping to occur changes provides feedback to the user regarding adjustments to the current exposure compensation value and / or changes in the scene in the field of view of the at least one camera that affect (e.g., reduced) the predicted clipping. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0210] In some embodiments, while displaying an exposure compensation indicator (e.g., 602d), the computer system receives a selection (e.g., 650k) (e.g., a tap on the exposure compensation indicator) of the exposure compensation indicator (e.g., 602d) (e.g., a selectable user interface object). In some embodiments, in response to receiving the selection (e.g., 650k) of the exposure compensation indicator, the computer system displays a control (e.g., 636) (e.g., an adjustable control, slider) for adjusting exposure compensation that, when selected (e.g., 650l), causes the exposure compensation indicator to be updated (e.g., as shown by 602d1 in FIG. 6M). In some embodiments, the adjustable control includes tick marks, each tick mark representing a value of the adjustable control. In some embodiments, while displaying the control for adjusting exposure compensation, the computer system displays a first indication (e.g., a number, a slider knob (e.g., a bar) on a slider track) of a current exposure compensation value, and in response to receiving a request to adjust the control for adjusting exposure compensation (e.g., a drag gesture (e.g., dragging the indication from one respective position (e.g., tick marks) on the adjustable control to another corresponding position on the adjustable control (e.g., a slide bar)))), (and while displaying the control for adjusting exposure compensation), the computer system replaces the display of the first indication of the first exposure compensation value with a display of a second indication of a second exposure compensation value, and / or captures media based on the second exposure compensation value (e.g., without capturing media based on the first exposure compensation value). In some embodiments, updating the exposure compensation indicator includes displaying a representation of a second exposure compensation value that differs from the representation of the first exposure compensation value (and ceasing to display the representation of the first exposure compensation value). In some embodiments, updating the exposure compensation indicator includes displaying a visual indication (eg, of predicted clipping) with a different visual appearance and / or in a different location.

[0211] In some embodiments, while displaying the exposure compensation indicator (e.g., 602d) and pursuant to a determination that clipping is not expected to occur (e.g., unlikely to occur) in response to receiving a request to capture media corresponding to a representation of the field of view of the one or more cameras, the computer system stops displaying the visual indication (e.g., 602d2 of FIG. 6M) (e.g., while continuing to display the exposure compensation indicator including a representation of the exposure compensation value). In some embodiments, clipping is not expected to occur after a first compensation value changes to a second compensation value. In some embodiments, clipping is not expected to occur after a change in the field of view of the one or more cameras is detected (e.g., after a scene in the field of view of the one or more cameras changes). In some embodiments, while displaying the exposure compensation indicator and pursuant to a determination that clipping is expected to occur in response to receiving a request to capture media corresponding to a representation of the field of view of the one or more cameras, the computer system continues to display the visual indication. Ceasing to display an indication of the predicted clipping when a predetermined condition is met provides a user with feedback regarding changes in the scene within the field of view of at least one camera that have affected (e.g., reduced) the adjustment of the current exposure compensation value and / or the predicted clipping. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0212] It should be noted that the processing details described above in connection with method 700 (e.g., FIG. 7) may be applied in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, the method 700 described above may be used to configure a computer system to capture media with respective amounts of exposure compensation that may be displayed using the methods described below with respect to method 900. For the sake of brevity, these details will not be repeated below.

[0213] 8A-8L show example user interfaces for viewing media using an electronic device according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0214] FIG. 8A illustrates electronic device 600 displaying a media gallery user interface 810 that includes thumbnail media representations 812. Thumbnail media representations 812 include thumbnail media representations 812a-812g, each of which represents a different media item (e.g., a media item captured at a different instance in time). In FIG. 8A, media representations 812 include thumbnail media representations that represent at least two types of media items. For example, thumbnail media representations 812a, 812b, and 812g represent media items that do not include high dynamic range ("HDR") content, and thumbnail media representations 812c-812h represent media items that include HDR content. In FIG. 8A, thumbnail media representations 812c-812h represent media items that include HDR content, but are displayed without the HDR content in media gallery user interface 810.

[0215] As shown in FIG. 8A, thumbnail media representations 812a-812g are each labeled with a "non-HDR" or "HDR" label. It should be understood that the "non-HDR" and "HDR" labels are included to allow a reader of the subject matter herein to quickly identify whether a particular thumbnail media representation represents a media item that does not include HDR content (a "non-HDR media item") or a media item that includes HDR content (an "HDR media item"). Thus, the "non-HDR" and "HDR" labels should not be considered to be displayed as part of the user interface, as part of thumbnail media representations 812a-812g, and / or as part of a particular media item represented by a particular thumbnail media representation. In FIG. 8A, device 600 detects a tap gesture 850a on thumbnail media representation 812a.

[0216] As shown in FIG. 8B, in response to detecting the tap gesture 850a, the device 600 displays a media viewer user interface 820 and stops displaying the media gallery user interface 810. The media viewer user interface 820 includes a media viewer area 824 positioned between an application control area 822 and an application control area 826. The media viewer area 824 includes an enlarged media representation 824a that represents the same media item as the thumbnail media representation 812a. Thus, the enlarged media representation 824a represents a non-HDR media item, as indicated by the "Non-HDR" label in FIG. 8B. The media viewer user interface 820 is not substantially overlaid with the controls, while the application control area 822 and the application control area 826 are substantially overlaid with the controls.

[0217] Application control area 822 optionally includes an indicator of the current time (e.g., "10:20" in FIG. 8B), the current date ("April 18, 2019" in FIG. 8B), a cellular signal status indicator 820a indicating the status of the cellular signal, and a battery level status indicator 820b indicating the status of the remaining battery life of device 600. Application control area 822 also includes a back affordance 822a (e.g., that, when selected, causes device 600 to re-display the media gallery user interface 810) and an edit affordance 824b (e.g., that, when selected, causes device 600 to display a media editing user interface including one or more controls for editing a representation of the media item represented by the currently displayed enlarged media representation).

[0218] The application control area 826 includes a portion of the thumbnail media representations 812 (e.g., 812a-812f) that are displayed in a row. The thumbnail media representation 812a is displayed as selected because the enlarged media representation 824a is displayed. Specifically, the thumbnail media representation 812a is displayed as selected in FIG. 8B by being the only thumbnail media representation displayed with a gap (e.g., a space between the thumbnail media representation 812a and the thumbnail media representation 812b). Additionally, the application control area 826 includes a send affordance 826b (e.g., which, when selected, causes the device 600 to initiate a process to send the media item represented by the enlarged media representation), a favorite affordance 826c (e.g., which, when selected, causes the device 600 to mark / not mark the media item represented by the enlarged representation as a favorite media), and a trash affordance 826d (e.g., which, when selected, causes the device 600 to delete (or initiate a process to delete) the media item represented by the enlarged media representation).

[0219] As shown in Figure 8B, application control area 822 and application control area 826 ("application control area") are background portions of the area of ​​media viewer user interface 820. In Figure 8B, the application controls are on the edges of media viewer user interface 820. Application control area 822 is the header of the media viewer user interface, and application control area 826 is the footer of media viewer user interface 820.

[0220] As shown in FIG. 8B, the application control area includes a light-colored (e.g., light gray, light colored) overlay. The light-colored overlay indicates that the device 600 is not operating in dark mode. In some embodiments, when the device 600 is operating in dark mode, the application control area includes a dark-colored overlay (e.g., dark gray, black), as described below in connection with FIGS. 8K-8L. For illustrative purposes, the application control area includes hatching that indicates how dark or shaded the application control area is. For example, an application control area depicted with a higher line density (e.g., lines that are closer together) has a visual appearance that is darker than the visual appearance of an application control area depicted with a lower line density (e.g., lines that are not close together). Thus, the hatching depicted in the application control area of ​​FIGS. 8B-8K indicates the darkness / brightness or color of the corresponding portion of the media viewer user interface 820.

[0221] As shown in Figure 8B, the application control area is displayed in a default color (e.g., a shade level of color) as indicated by the hatching displayed in Figure 8B. In Figure 8B, device 600 displays the application control area in a default color (and / or a default brightness level) because the augmented media representation 824a represents a non-HDR media item. In Figure 8B, device 600 detects a left swipe gesture 850b within media viewer area 824.

[0222] As shown in FIG. 8C, in response to detecting the left swipe gesture 850b, the device 600 replaces the enlarged media representation 824a with the enlarged media representation 824b. The enlarged media representation 824b represents the same media item as the thumbnail media representation 812b. Thus, the enlarged media representation 812b represents the non-HDR media item indicated by the "Non-HDR" label in FIG. 8C (e.g., as described above with respect to the thumbnail media representation 812b in FIG. 8A). In response to detecting the left swipe gesture 850b, the device 600 updates the thumbnail media representation 812 to indicate that the media item corresponding to the thumbnail media representation 812b is displayed as an enlarged media representation in the media viewer area 824.

[0223] As shown in Figure 8C, in response to detecting a left swipe gesture 850b, device 600 continues to display the application control area in a default color, as indicated by the hatching displayed in Figure 8C having the same density as the hatching in Figure 8B. In Figure 8C, device 600 continues to display the application control area in a default color because enlarged media representation 824a represents a non-HDR media item. In Figure 8C, device 600 detects a left swipe gesture 850c within media viewer area 824.

[0224] As shown in FIG. 8D, in response to detecting the left swipe gesture 850c, the device 600 replaces the enlarged media representation 824b with the enlarged media representation 824c. The enlarged media representation 824c represents the same media item as the thumbnail media representation 812c. Thus, the enlarged media representation 812c represents the HDR media item indicated by the "HDR" label in FIG. 8D (e.g., as described above with respect to the thumbnail media representation 812c in FIG. 8A). Notably, the thumbnail media representation 812c in FIG. 8A did not include visually displayed HDR content, whereas the enlarged media representation 824b in FIG. 8D does include visually displayed HDR content. As shown in FIG. 8D, the device 600 also updates the thumbnail media representation 812 to show its thumbnail 812c using similar techniques and for similar reasons as described above (e.g., in FIGs. 8B-8C).

[0225] As shown in Figure 8D, in response to detecting a left swipe gesture 850c, device 600 updates the application control area to have a lighter color (e.g., a lighter, whiter color) than the color of the application control area of ​​Figure 8C (e.g., as indicated by the hatching in Figure 8D having a lower level of density as the hatching in Figure 8C). In Figure 8D, device 600 updates the application control area to have the color displayed in Figure 8D based on the luminance of the HDR content within the respective media item (e.g., the media item represented by the currently displayed magnified media representation).

[0226] In FIG. 8E, the device 600 continues to display the enlarged media representation 824c. As the device continues to display the enlarged media representation 824c (e.g., in FIG. 8E), a determination is made that the enlarged media representation 824c has been displayed for longer than a predetermined period of time. As shown in FIG. 8E, because a determination is made that the enlarged media representation 824c has been displayed for longer than a predetermined period of time, the device 600 updates the application control region to have a lighter color than the color of the application control region displayed in FIG. 8D (e.g., as shown as hatching in FIG. 8E with a lower density level as the hatching in FIG. 8D). The lighter color of the application control region in FIG. 8D is based on the brightness of the HDR content within the respective media item (e.g., the media item represented by the currently displayed enlarged media representation). Thus, in FIG. 8E, the device 600 lightens the color of the application control region based on the amount of time the enlarged media representation 824c has been displayed. In some embodiments, device 600 does not lighten the color of the application control area any more than the color of the application control area displayed in FIG. 8E, regardless of the amount of time the augmented media representation 824c is displayed. In some embodiments, device 600 does not lighten the color of the application control area any more because a determination is made that the color has reached a maximum brightness level based on the level of HDR content in the HDR media represented by augmented media representation 824c. In some embodiments, with reference to FIGS. 8C-8E, device 600 displays an animation of the application control area gradually lightening from the color of the application control area in FIG. 8C to the color of the application control area in FIG. 8E after augmented media representation 824c is displayed.

[0227] In some embodiments, device 600 lightens (or darkens) the color of the application control region based on the speed of a gesture (e.g., swipe gesture 850c, or the time to transition through the displayed augmented media representation) received before the augmented media representation is displayed (e.g., additionally or alternatively based on the time the augmented media representation is displayed). In some embodiments, device 600 lightens (or darkens) the color of the application control region more when a gesture is detected for a longer duration and lightens (or darkens) the color of the application control region less when a gesture is detected for a shorter duration. In some embodiments, device 600 lightens (or darkens) the color of the application control region based on the average speed of a gesture (e.g., gestures 850b and 850c) received before the augmented media representation is displayed. In some embodiments, device 600 lightens (or darkens) the color of the application control region more when the average velocity of the gesture is lower and lightens (or darkens) the color of the application control region less when the average velocity of the gesture is higher. In Figure 8E, device 600 detects a tap gesture 850e on thumbnail representation 812d.

[0228] As shown in FIG. 8F, in response to detecting the tap gesture 850e, the device 600 replaces the enlarged media representation 824c with the enlarged media representation 824d. The enlarged media representation 824d represents the same media item as the thumbnail media representation 812d (e.g., an HDR media item), as indicated by the "HDR" label in FIG. 8F. In response to detecting the tap gesture 850e, the device 600 also updates the thumbnail media representation 812 to indicate that the media item corresponding to the thumbnail media representation 812d is displayed as an enlarged media representation in the media viewer area 824. Comparing the enlarged media representation 824c (e.g., FIGS. 8D-8E) and the enlarged media representation 824d (e.g., FIG. 8F), the enlarged media representation 824d is visually darker than the enlarged media representation 824c. In FIG. 8F, a determination is made that the media item represented by the enlarged media representation 824d includes HDR content having a second amount of luminance. The second amount of brightness of the HDR content in the media item represented by the augmented media representation 824d is darker than the amount of brightness of the HDR content in the media item represented by the augmented media representation 824c of Figures 8D-8E.

[0229] As shown in FIG. 8F, in response to detecting tap gesture 850e, and because a determination is made that the media item represented by magnified media representation 824d includes content having a second amount of luminance, device 600 updates the color of the application control area. Specifically, device 600 updates the color of the application control area of ​​FIG. 8F to be darker than the application control area of ​​FIG. 8E. In FIG. 8F, because the second amount of luminance of the HDR content in the media item represented by magnified media representation 824d (e.g., shown in FIG. 8F) is darker than the amount of luminance of the HDR content in the media item represented by magnified media representation 824c (e.g., shown in FIG. 8E), device 600 updates the color of the application control area of ​​FIG. 8F to be visually darker than the application control area of ​​FIG. 8E. Thus, device 600 updates the color of the application control area based on the luminance of the HDR content in the media item currently displayed on device 600 (e.g., via the magnified media representation). In some embodiments, the brightness level of the HDR content in a media item is based on the number of bright portions in the media item, the overall brightness of the media item, the brightest portion of the media item, and / or the brightness of a particular portion of the media item. In some embodiments, device 600 uses one or more techniques to determine how much to darken the color of the application control area, as described above. In FIG. 8F, device 600 detects a left swipe gesture 850f in media viewer area 824.

[0230] As shown in FIG. 8G, in response to detecting the left swipe gesture 850f, the device 600 replaces the enlarged media representation 824d with the enlarged media representation 824e. The enlarged media representation 824e represents the same media item as the thumbnail media representation 812e (e.g., an HDR media item), as indicated by the "HDR" label in FIG. 8G. In response to detecting the left swipe gesture 850f, the device 600 also updates the thumbnail media representation 812 to indicate that the media item corresponding to the thumbnail media representation 812e is displayed as an enlarged media representation in the media viewer area 824. Comparing the enlarged media representation 824d (e.g., FIG. 8F) and the enlarged media representation 824e (e.g., FIG. 8F), the enlarged media representation 824e is visually darker than the enlarged media representation 824d (e.g., as described above and the enlarged media representation 824c). 8G, a determination is made that the media item represented by augmented media representation 824e includes HDR content having a third amount of luminance using one or more of the techniques described above, where the third amount of luminance of the HDR content in the media item represented by representation 824e is brighter than the second amount of luminance of the HDR content in the media item representation by representation 824d.

[0231] As shown in FIG. 8G, in response to detecting a left swipe gesture 850f and because the media item represented by the enlarged media representation 824e includes HDR content having a third amount of luminance, device 600 updates the color of the application control region. In FIG. 8G, device 600 updates the color of the application control region such that the application control region of FIG. 8G is brighter than the application control region of FIGS. 8E-8D (e.g., because the third amount of luminance (e.g., FIG. 8G) is greater than the second amount of luminance (e.g., FIG. 8D)). Device 600 updates the color of the application region of FIG. 8G using one or more techniques, as described above. In FIG. 8G, device 600 detects a left swipe gesture 850g in media viewer region 824.

[0232] 8H-8I illustrate media viewer user interfaces 820 that may be displayed in response to device 600 detecting a left swipe gesture 850g. In some embodiments, media viewer user interface 820 of FIG. 8H is displayed in response to device 600 detecting a left swipe gesture 850g, and media viewer user interface 820 of FIG. 8I is displayed after media viewer user interface 820 is displayed for a predetermined period of time (e.g., using the techniques described above in connection with FIGS. 8D-8E). In some embodiments, media viewer user interface 820 of FIG. 8H is not displayed in response to detecting a left swipe gesture 850g, and media viewer user interface 820 of FIG. 8I is displayed in response to detecting a left swipe gesture 850g.

[0233] As shown in FIG. 8H (and FIG. 8I), in response to detecting the tap gesture 850g, the device 600 replaces the enlarged media representation 824e with the enlarged media representation 824f. The enlarged media representation 824f represents the same media item as the thumbnail media representation 812f (e.g., an HDR media item), as indicated by the "HDR" label in FIG. 8H (and FIG. 8I). In response to detecting the tap gesture 850g, the device 600 also updates the thumbnail media representation 812 to indicate that the media item corresponding to the thumbnail media representation 812f is displayed as an enlarged media representation in the media viewer area 824. Comparing the enlarged media representation 824e (e.g., FIG. 8G) and the enlarged media representation 824f (e.g., FIG. 8H), the enlarged media representation 824f is visually brighter than the enlarged media representation 824e. In FIG. 8H (or FIG. 8I), a determination is made that the media item represented by the enlarged media representation 824f has HDR content that is above a brightness threshold.

[0234] As shown in FIG. 8I, since a determination is made that the media item (e.g., represented by enlarged media representation 824f) exceeds the brightness threshold (e.g., and in response to detecting swipe gesture 850g), device 600 darkens the HDR content of enlarged media representation 824f (as shown by enlarged media representation 824f of FIG. 8I having lines darker than the lines of enlarged media representation 824f of FIG. 8H). Additionally, device 600 updates the color of the application control region such that the application control region of FIG. 8I is brighter than the application control region of FIG. 8G. Device 600 updates the color of the application region of FIG. 8I using one or more techniques, as described above. Thus, in FIG. 8I, since a determination is made that the media item exceeds the brightness threshold, device 600 modifies both the enlarged media representation of the media item and the application control region such that the brightness of the enlarged media representation is closer to the brightness of the application control region. In some embodiments, device 600 displays a visually less distracting media user interface by displaying the application control region having a brightness close to the brightness of the enlarged representation. In FIG. 8I, the device 600 detects a left swipe gesture 850i within the media viewer area 824.

[0235] As shown in Figure 8J, in response to detecting left swipe gesture 850i, device 600 replaces enlarged media representation 824f with enlarged media representation 824g, which represents the same media item as thumbnail media representation 812g (e.g., a non-HDR media item), as indicated by the "Non-HDR" label in Figure 8J. As shown in Figure 8J, in response to detecting left swipe gesture 850i, and because the respective media item is a non-HDR media item, device 600 updates the color of the application control area to a default color (e.g., by the hatching displayed in Figure 8J having the same density as the hatching in Figure 8B).

[0236] 8K-8L illustrate device 600 when operating in a dark mode and / or displaying a dark overlay within an application region. As shown in FIG 8K, device 600 displays an application control region with a dark overlay (e.g., dark gray, black; non-transparent) and an enlarged media representation 824b displayed within media viewer region 824. In FIG 8K, device 600 detects a left swipe gesture 850k within media viewer region 824.

[0237] As shown in FIG. 8L, in response to detecting left swipe gesture 850k, device 600 replaces enlarged media representation 824b with enlarged media representation 824c. Enlarged media representation 824c represents the same media item as thumbnail media representation 812c. Thus, enlarged media representation 812c represents the HDR media item indicated by the "HDR" label in FIG. 8D (e.g., as described above with respect to thumbnail media representation 812c in FIG. 8A). As shown in FIG. 8K, device 600 continues to display the application control area having the same visual appearance as the application control area displayed in FIG. 8K, but enlarged media representation 812c represents the HDR media item. Thus, when device 600 displays an overly dark application area, device 600 does not update the visual appearance of the application control area based on the luminance of the HDR content in the media item (as opposed to, for example, when device 600 updates the visual appearance of the application control area in FIGS. 8C-8D when device 600 displays the application control area with a light overlay).

[0238] 9 is a flow diagram illustrating a method for displaying media using a computer system, according to some embodiments. Method 900 is performed in a computer system (e.g., 100, 300, 500, 600) in communication with a display generation component (e.g., a display controller, a touch-sensitive display system) and one or more input devices (e.g., a touch-sensitive surface). Some operations of method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0239] As described below, the method 900 provides an intuitive way to display media. The method reduces the cognitive burden on the user when viewing media, thereby creating a more efficient human-machine interface. For battery-operated computing systems, it enables users to view media more quickly and efficiently, thereby conserving power and extending the time between battery charges.

[0240] A computer system (e.g., 600) (e.g., a smart phone, a smart watch), via a display generation component, displays (902) a media viewer user interface (e.g., 820) (e.g., an interface for displaying one or more representations (e.g., enlarged or thumbnail representations) of previously captured media) that includes: a first portion (e.g., 824) that includes a representation (e.g., 824a-824f) of a first previously captured media item (e.g., image, video); and a second portion (e.g., 822 and / or 826) of the user interface that has a first visual appearance and is distinct (e.g., separate, independent) from the first portion (e.g., 824) of the media viewer user interface (e.g., 820) (e.g., a chrome portion of the user interface (e.g., a header, footer, a menu section of the user interface), a portion of the user interface that partially or completely surrounds the visual content of the user interface (e.g., the first portion)). In some embodiments, the representations of the previously captured media have been captured by one or more cameras of the computer system. In some embodiments, the first previously captured media is high dynamic range (HDR) media. In some embodiments, the first previously captured media is not high dynamic range media. In some embodiments, the second portion of the media viewer user interface is outside of the first portion of the media viewer user interface. In some embodiments, the second portion of the media viewer user interface is above and / or below the first portion of the media viewer user interface. In some embodiments, the second portion includes a third portion of the media user interface and a fourth portion of the media user interface separated by the first portion of the media user interface.In some embodiments, the second portion includes a plurality of affordances (e.g., an affordance that, when selected, causes the computer system to share a representation of the previously captured media via one or more applications; an affordance that, when selected, causes the computer system to display a user interface for editing the representation of the previously captured media; an affordance that, when selected, causes the computer system to delete the displayed representation of the previously captured media; an affordance that, when selected, causes the computer system to include the representation of the previously captured media in a particular group of representations (e.g., a favorite representation, a "like" representation, etc.); an affordance that, when selected, causes the computer system to simultaneously display multiple representations (e.g., a media gallery having multiple photos in a grid); an affordance that, when selected, causes the computer system to stop displaying a media viewer user interface and display a user interface different from the media viewer user interface). In some embodiments, the representation of the previously captured media has been captured by one or more cameras of the computer system. In some embodiments, the first previously captured media is high dynamic range media. In some embodiments, the first previously captured media is not high dynamic range media.

[0241] While displaying a media viewer user interface including a second portion (e.g., 822 and / or 826) of a media viewer user interface (e.g., 820) (and the first portion including a representation of the first previously captured media item) having a first visual appearance (e.g., 822 and / or 826 in FIG. 8F) via the display generation component, the computer system receives a request (e.g., a swipe gesture on the media viewer user interface (e.g., 820)) to display a representation (e.g., 824e) of a second previously captured media item (e.g., a still image, a video) that is different from the first previously captured media item (e.g., 824d) (e.g., to replace the display of the representation of the first previously captured media item with the representation of the second previously captured media item) (904) (e.g., 850f).

[0242] In response to receiving (906) a request to display a representation of a second previously captured media item, and pursuant to determining (908) that a first set of criteria is met, including criteria that are met when the representation of the second previously captured media item (e.g., 824e) (or a different media item) is a high dynamic range (HDR) media item, the computer system displays (910) the representation of the second previously captured media item (e.g., replaces the display of the representation of the first previously captured media item with the representation of the second previously captured media item) and updates (912) a second portion (e.g., 822 and / or 826) of the media viewer user interface (e.g., 820) to have a second visual appearance (e.g., 822 and / or 826 in FIG. 8G) that is different from the first visual appearance (e.g., 822 and / or 826 in FIG. 8F). In some embodiments, pursuant to determining that the first set of criteria is met, the first previously captured media item is no longer displayed. In some embodiments, the second visual appearance is brighter / less bright (or whiter) than the first visual appearance. In some embodiments, the second visual appearance is based on a brightness level of the second previously captured representation of the media item. In some embodiments, the brightness level can include the brightness of each of the particular elements in the previously captured representation of the media, and / or can be based on the number of bright elements in the previously captured representation of the media, and / or can be based on the overall brightness of the previously captured representation of the media. By updating a portion (e.g., image border, chrome) of the media viewer user interface (e.g., 820) when a predetermined condition is met (e.g., when displaying an HDR photo), the portion of the updated media portion more closely matches the elements in the HDR photo, making the user interface less visually intrusive when the HDR photo is displayed.Performing an action when a set of conditions is met without requiring further user input enhances the usability of the system and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), as well as reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently.

[0243] In some embodiments, as part of updating the second portion (e.g., 822 and 826) of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with a determination that a portion of the media item (e.g., 824d in FIG. 8F) (e.g., HDR content) has a first level of brightness, the computer system displays the second portion (e.g., 822 and / or 826 in FIG. 8F) of the media viewer user interface (e.g., 820) having a first amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)). In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with determining that the portion of the media item has a second level of luminance (e.g., 824e of FIG. 8G), the computer system displays the second portion of the media viewer user interface (e.g., 822 and / or 826 in FIG. 8G) having a second amount of visual characteristics (e.g., luminance level, opacity, color (e.g., whiteness)) different from the first amount of visual characteristics. In some embodiments, the second portion of the media viewer user interface is updated to have the second visual appearance based on the luminance of content (e.g., HDR content) within the media item. In some embodiments, the second amount is higher than the first amount when the second luminance level is higher (or alternatively lower) than the first luminance level. In some embodiments, when the media item is HDR content and a portion of the media item is configured to be displayed at a luminance above a first level of luminance, a second portion of the media viewer user interface is displayed with a first amount of visual characteristics, and when the media item is HDR content and a portion of the media item is configured not to be displayed at a luminance above the first level of luminance, the second portion of the media viewer user interface is displayed with a second amount of visual characteristics (e.g., luminance level, opacity, color (e.g., whiteness)) that is different from the first amount of visual characteristics.By dynamically updating portions of the media viewer user interface (e.g., chrome) differently based on the brightness of the HDR content of different media items, the user interface is less visually cluttered when displaying each media item (e.g., when the HDR content of the media is brighter, the portion of the media viewer user interface is brighter). By taking action when a set of conditions is met without requiring further user input, the usability of the system is enhanced, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), as well as allowing the user to use the system more quickly and efficiently, thereby reducing system power usage and improving battery life.

[0244] In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with determining that the media item (e.g., 824c) has been displayed for the first amount of time, the computer system displays the second portion of the media viewer user interface (e.g., 822 and / or 826 in FIG. 8D ) having a third amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)). In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with determining that the media item (e.g., 824c) was displayed for a second amount of time different from the first amount of time, the computer system displays the second portion of the media viewer user interface (e.g., 822 and / or 826 of FIG. 8E) having a fourth amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)) different from the third amount of visual characteristics. In some embodiments, the second portion of the media viewer user interface is updated to have the second visual appearance based on the amount of time the media item was displayed. In some embodiments, the visual appearance of the second portion can change over time (e.g., gradually, multiple times) while displaying the media item (e.g., over a period of 0.5, 1, 2, 5, or 10 seconds, then optionally stop changing while the same media item continues to be displayed). In some embodiments, when the media item is displayed for a second amount of time that is longer (or alternatively shorter) than the first amount of time, the fourth amount of the visual characteristic is higher than the third amount of the visual characteristic. In some embodiments, the second portion of the media viewer user interface is displayed with a predetermined amount (or degree) of the visual characteristic, the amount of the visual characteristic being based on an amount of elapsed time (e.g., the amount of time the first previously captured media item was displayed, the amount of time the second previously captured media item was displayed).Dynamically updating portions of the media viewer user interface (e.g., chrome) differently based on the amount of time the HDR media is displayed makes the user interface less visually intrusive when displaying media (e.g., less changes if the media is displayed for less time) and reduces the amount of different levels of brightness that portions of the media viewer user interface are updated to. Taking action when a set of conditions is met without requiring further user input enhances system usability and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), plus reduces system power usage and improves battery life by allowing the user to use the system more quickly and efficiently.

[0245] In some embodiments, as part of displaying the representation of the second previously captured media item (e.g., 824c-824f), the computer system replaces the representation of the first previously captured media item with the representation of the second previously captured media. In some embodiments, as part of updating the second portion of the media viewer user interface to have a second visual appearance that is different from the first visual appearance, and in accordance with a determination that the representation of the first previously captured media item was displayed for at least the first amount of time before being replaced with the representation of the second previously captured media, the computer system displays the second portion of the media viewer user interface (e.g., 820) having a fifth amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)). In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with determining that the first previously captured representation of the media item content has been replaced with the second previously captured representation of the media for a second amount of time different from the first amount of time, the computer system displays the second portion of the media viewer user interface (e.g., 820) having a sixth amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)) different from the fifth amount of visual characteristics. In some embodiments, the second portion of the media viewer user interface is updated to have the second visual appearance based on the duration of the transition between the previously displayed representations. In some embodiments, the amount of change in visual appearance is smaller (larger) when the duration of the transition between the representations is smaller (larger).Dynamically updating portions of the media viewer user interface (e.g., borders, chrome) differently based on the transition time between two media items makes the user interface less visually intrusive when displaying media (e.g., less change when media is transitioned more quickly) and less blunt in the amount of brightness change when transitioning quickly between media. Taking action when a set of conditions is met without requiring further user input enhances the usability of the system and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), plus reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently.

[0246] In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and in accordance with a determination that an average rate of requests (e.g., 850f, 850g) to display previously captured media items (e.g., the previous five requests) is below a first threshold (e.g., or a first number of multiple requests to display multiple representations of a previously captured media item were received within a predetermined time prior to displaying a second representation of a previously captured media item), the computer system displays the second portion of the media viewer user interface (e.g., 820) having a seventh amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)). In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 820) to have a second visual appearance different from the first visual appearance, and pursuant to determining that the average rate of requests to display previously captured media items is not below a first threshold (e.g., a second number of requests to display a plurality of representations of a previously captured media item are received within a predetermined time prior to displaying a second previously captured media item representation), the computer system displays the second portion of the media viewer user interface (e.g., 820) with an eighth amount of visual characteristics (e.g., brightness level, opacity, color (e.g., whiteness)) different from the seventh amount of visual characteristics. In some embodiments, the second number is different from the first number. In some embodiments, the second portion of the media viewer user interface is updated to have the second visual appearance based on an average rate of input (e.g., swipe rate or velocity). In some embodiments, when the average rate of input is high, the second portion changes less than when the average rate of subsequent input is lower. In some embodiments, the second portion of the media viewer user interface is displayed with a predetermined amount (or degree) of the visual characteristic, the amount of the visual characteristic being based on the rate (e.g., number of images per unit time) at which content is displayed within the first portion of the media browser interface.Dynamically updating portions of the media viewer user interface (e.g., borders, chrome) differently based on the transition time between media items makes the user interface less visually intrusive when displaying media (e.g., less change when speed is faster) and less blunt in the amount of brightness change when transitioning quickly between media. Taking action when a set of conditions is met without requiring further user input enhances the usability of the system and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), plus reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently.

[0247] In some embodiments, while displaying, via the display generation component, a media viewer user interface including a second portion of the media viewer user interface (e.g., 820) having a first visual appearance (and the first portion including a representation of the first previously captured media item), the computer system receives a request to display a representation of a third previously captured media item that is different from the first previously captured media item and the second previously captured media item. In some embodiments, in response to receiving the request to display the representation of the third previously captured media item, and in accordance with a determination that the first set of criteria is met, the computer displays the representation of the third previously captured media item (e.g., by replacing the representation of the second previously captured media item) and updates the second portion (e.g., 822 and / or 826) of the media viewer user interface (e.g., 820) to have a third visual appearance that is different from the first visual appearance and the second visual appearance. In some embodiments, the first set of criteria includes a criterion that is met when the third previously captured media representation is an HDR media item. In some embodiments, if the third media item has a higher brightness level of content than the previously displayed media item (e.g., the brightness level may be based on the number of bright elements in the image and / or may include the brightness of each of the particular elements in the image, which may be based on the overall brightness of the image), then the second portion (e.g., 822 and / or 826) of the media viewer user interface (e.g., 820) may be brighter (or have a whiter color) while the third media item is displayed than when the previous media item was displayed.By dynamically updating portions of the media viewer user interface (e.g., chrome) differently based on the brightness of the HDR content of different media items, the user interface is less visually cluttered when displaying each media item (e.g., when the HDR content of the media is brighter, the portion of the media viewer user interface is brighter). By taking action when a set of conditions is met without requiring further user input, the usability of the system is enhanced, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), as well as allowing the user to use the system more quickly and efficiently, thereby reducing system power usage and improving battery life.

[0248] In some embodiments, the second previously captured media item is an HDR media item (e.g., 824c-824f). In some embodiments, a representation of the second previously captured media item is displayed in HDR. In some embodiments, for a media item (e.g., an image or video) having at least a portion intended to be displayed at a particular brightness level above the standard dynamic range for brightness, a representation of the media item is displayed at a brightness level (e.g., the particular brightness level) above the standard dynamic range.

[0249] In some embodiments, the first set of criteria includes criteria that are met when the second portion (e.g., 822 and / or 826) is a first color (e.g., a color (e.g., white or light), a color that is not a second color (e.g., black or dark), a light color (e.g., a color that is whiter than black)) (or is within a threshold value (e.g., red-blue-green values, hexadecimal values)). In some embodiments, the first set of criteria includes criteria that are met when the second portion (e.g., 822 and / or 826) is not a second color (e.g., black or dark). In some embodiments, the computer system receives user input selecting from among two or more optional selections for a color range of the second portion (e.g., 822 and / or 826), and the first set of criteria includes criteria that are met when a current color range selection for the second portion (e.g., 822 and / or 826) is a first color range (not a second color or the second color range).

[0250] In some embodiments, as part of updating the second portion of the media viewer user interface (e.g., 822 and / or 826) to have the second visual appearance, the computer system displays an animation that gradually transitions (e.g., fades over a predetermined period of time (e.g., 1, 2, 3 seconds)) the second portion of the media viewer user interface (e.g., 822 and / or 826) from the first visual appearance to the second visual appearance. By gradually updating a portion of the media viewer user interface (e.g., chrome) when HDR media items are displayed, the user interface is made less visually intrusive when displaying HDR media items and the change of a portion of the media viewer interface is made less blunt. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0251] In some embodiments, the representation of the previously captured media item (e.g., a first previously captured media item, a second previously captured media item, etc.) includes an amount of luminance (e.g., average luminance, percentage of bright areas). In some embodiments, the representation of the previously captured media item is displayed with an altered amount of luminance (e.g., reduced) (e.g., reduced average luminance, reduced luminance in some parts while maintaining luminance in other parts, reduced luminance evenly across the image) pursuant to a determination that the amount of luminance (e.g., average luminance, percentage of bright areas) exceeds the luminance threshold. In some embodiments, the representation of the previously captured media item is displayed with an amount of luminance (e.g., without reducing the average luminance, without reducing the luminance evenly across the image) pursuant to a determination that the amount of luminance does not exceed the luminance threshold. In some embodiments, the content underlying the media item remains the same (e.g., has an amount of luminance above the luminance threshold), but the media item is displayed with an altered amount of luminance (e.g., reduced). Dynamically varying HDR media items displayed differently based on the brightness of the HDR content of different media items makes the user interface less visually intrusive when displaying each media item (e.g., as the HDR content of a photo becomes brighter, the photo appears darker, reducing the visual difference between the chrome and the photo). Taking action when a set of conditions is met without requiring further user input enhances system usability and makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), plus reduces system power usage and improves battery life by allowing the user to use the system more quickly and efficiently.

[0252] In some embodiments, the first previously captured media item (e.g., 824a-824b, 824g) is not an HDR media item. In some embodiments, the second previously captured media item (e.g., 824c-824f) is an HDR media item. In some embodiments, prior to displaying, via the display generation components, the media viewer user interface including the first and second portions (e.g., 822 and / or 826), the computer system displays, via the display generation components, a user interface (e.g., 810) including multiple representations of the media items (e.g., 812a-812g). In some embodiments, the multiple representations of the media items include displaying a second representation (e.g., 812a-812b, 812g) (e.g., thumbnails) of the first previously captured media item without HDR content, and a second representation (e.g., 812c-812f) (e.g., thumbnails) of the second previously captured media item without HDR content. In some embodiments, thumbnails (e.g., images) of media items are displayed using standard dynamic range luminance, regardless of whether the media item is intended to be displayed at a particular luminance level that exceeds the standard dynamic range for luminance.In some embodiments, while displaying multiple representations of a media item, the computer system receives a request to display a first (or alternatively, any of the second or other representations) previously captured media item (e.g., a selection (e.g., a tap) of the second representation of the first (or alternatively, any of the second or other representations) previously captured media item), and in response to receiving the request to display the first (or alternatively, any of the second or other representations), the computer system displays a media interface including a first portion (e.g., having a representation of the first (or alternatively, any of the second or other representations) previously captured media item) and a second portion (e.g., having a first visual appearance (or alternatively, a second visual appearance when the second previously captured media item is displayed in the first portion)) (e.g., 822 and / or 826).

[0253] In some embodiments, in response to receiving a request to display a representation of the second previously captured media item (906), and in accordance with a determination that the first set of criteria is not met, the computer system ceases updating (914) a second portion (e.g., 822 and / or 826) of the media viewer user interface (e.g., 820) to have a second visual appearance that is different from the first visual appearance (e.g., displaying (or continuing to display) the second portion (e.g., 822 and / or 826) of the media viewer user interface (e.g., 820) having the first visual appearance). In some embodiments, the first set of criteria is not met if the representation of the second previously captured media item is not an HDR media item. In some embodiments, the chrome (the area surrounding the displayed image) does not change when the non-HDR photograph is displayed. In some embodiments, pursuant to a determination that the first set of criteria is not met, the computer system transitions the display of the second portion (e.g., 822 and / or 826) to a predetermined visual appearance (e.g., independent of the brightness of the second previously captured media item). Thus, unless the image is an HDR image, the second portion (e.g., 822 and / or 826) is displayed using the predetermined appearance regardless of the amount of brightness / darkness of the non-HDR image. By dynamically withdrawing the change of a portion of the media user interface when the media is not HDR media, the user interface is made less visually intrusive when displaying the respective non-HDR capable media item. By performing an action when a set of conditions is met without requiring further user input, the operability of the system is enhanced, the user-system interface is made more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and in addition, by allowing the user to use the system more quickly and efficiently, the system uses less power and improves battery life.

[0254] In some embodiments, while displaying a representation of the second previously captured media item and the second portion (e.g., 822 and / or 826) having the second visual appearance, the computer system receives a request to display a representation of a fourth previously captured media item (e.g., 850g, 850i). In some embodiments, in response to receiving a request to display the third previously captured media item (e.g., 850g, 850i) and following a determination that the first set of criteria is met, the computer system displays a representation of the fourth previously captured media item (e.g., by replacing the display of the second previously captured media item) without updating the visual appearance of the second portion (e.g., 822 and / or 826) and updates the second portion of the media (e.g., 822 and / or 826) to have a visual appearance (e.g., 822 and / or 826 of FIGS. 8E-8I) based on being different from the first visual appearance and the second visual appearance. In some embodiments, in response to receiving a request to display the third previously captured media item, and following a determination that the first set of criteria is not met (e.g., the fourth previously captured media item is not an HDR media item), the computer system displays a representation of the fourth previously captured media item and updates a second portion of the media (e.g., 822 and / or 826) to have a predetermined visual appearance (e.g., independent of the brightness of the second previously captured media item) that is different from the second visual appearance (e.g., 822 and / or 826 of FIGS. 8C-8D and 8J). In some embodiments, so long as the fourth previously captured media item is not HDR, the second portion (e.g., 822 and / or 826) is displayed using the predetermined visual appearance regardless of how bright / dark the non-HDR image is.In some embodiments, when a non-HDR image is requested to be displayed, the second portion (e.g., 822 and / or 826) is displayed using a predetermined visual appearance (e.g., the same color and / or brightness for all non-HDR images) regardless of how bright / dark the non-HDR images are, and when an HDR image is requested to be displayed, the second portion (e.g., 822 and / or 826) is displayed using a variable visual appearance based on how bright / dark the HDR image is.

[0255] It should be noted that the process details described above with respect to method 900 (e.g., FIG. 9) are also applicable in a similar manner to the methods described below / above. For example, method 700 and method 1100 optionally include one or more of the characteristics of the various methods described above with reference to method 900. For example, method 900 may display media captured using a computer system configured to capture media at particular exposure compensation values ​​using one or more steps of method 700 (described above). For the sake of brevity, these details will not be repeated below.

[0256] 10A-10AC show example user interfaces for displaying status indicators using an electronic device, according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including the process of FIG.

[0257] In FIGS. 10A-10AC, device 600 may record (or capture) media using one or more media capture devices, such as a microphone (e.g., FIGS. 10B, 10E) and / or a camera (e.g., FIGS. 10Q, 10W). FIGS. 10A-10AC illustrate example scenarios in which device 600 displays or does not display a recording status indicator based on the type of data being recorded by at least one of the media capture devices. As used in conjunction with FIGS. 10A-10C, the type of data refers to how the data is used (e.g., whether the data is available for playback; whether the data is being passed to a trusted or untrusted application), rather than the format of the data. As used herein in conjunction with FIGS. 10A-10AC, a first type of data (e.g., a type of data for which a capture status indicator is displayed) refers to data that is determined to be used (or potentially used) in a first manner, and a second type of data (e.g., a type of data for which a capture status indicator is not displayed) refers to data that is determined not to be used in a first manner. In some embodiments, the first type of data (e.g., the type of data for which a capture status indicator is displayed) corresponds to data that is available (e.g., stored) for later playback, and the second type of data (e.g., the type of data for which a capture status indicator is not displayed) corresponds to data that is not available for playback.In some embodiments, the first type of data (e.g., the type of data for which a capture status indicator is displayed) corresponds to data passed to an untrusted application (e.g., a non-first party voice assistant application, a non-first party authentication application), and the second type of data (e.g., the type of data for which a capture status indicator is not displayed) corresponds to data used by one or more trusted applications (e.g., components of the operating system or trusted first and / or third party applications) to control various features of the device without being passed to an untrusted application (e.g., a non-first party voice assistant application, a non-first party third party authentication application) and without being retained as media that can be played at a later time (e.g., by the device or by another device). Thus, the determination is based on whether an untrusted application has access to the recorded data (e.g., audio or video content). In some embodiments, the recording status indicator is displayed regardless of whether an indicator of recording is displayed by the application that records the data.

[0258] FIG. 10A shows device 600 displaying a user interface with icon 690. In FIG. 10A, device 600 detects voice input 1050a (e.g., "Yes, Assistant") via a microphone of device 600. As shown in FIG. 10B, in response to detecting voice input 1050a, device 600 displays user interface 1004. User interface 1004 is a user interface for a voice assistant application. User interface 1004 includes the phrase "What can I do?", which indicates that device 600 is waiting to receive voice input corresponding to a command.

[0259] In particular, in Figs. 10A-10B, the device 600 records data via the microphone of the device 600 to identify a command (e.g., spoken by a user of the device 600). However, in Figs. 10A-10B, the device 600 does not display a recording status indicator (e.g., recording status indicator 1042 shown in Fig. 10E) because it has been determined that the device 600 is not recording the first type of data. In Figs. 10A-10B, the device 600 is not recording the first type of data because it has been determined that the recorded data is not available for later playback. Specifically, because the device 600 records data to identify a voice command that enables a native assistant (or trusted) voice application to cause the device 600 to perform one or more actions (e.g., provide directions to a location, provide an answer to a query from a user), the data recorded in Figs. 10A-10B is not available for later playback, passed to the trusted application.

[0260] At some point after displaying the user interface 1010, the device 600 redisplays the user interface with the application icons 690, including the voice memo application icon 690b. In FIG. 10C, the device 600 detects a tap gesture 1050c on the voice memo application icon 690b. As shown in FIG. 10D, in response to detecting the tap gesture 1050c, the device 600 launches the voice memo application corresponding to the voice memo application icon 690b and displays a start record user interface (e.g., for the voice memo application) including the audio record affordance 1010. Because it is determined that the first type of data is not being recorded, the device 600 does not display the record status indicator 1042 in FIG. 10C. In FIG. 10D, the device 600 detects a tap gesture 1050d on the audio record affordance 1010.

[0261] As shown in FIG. 10E, in response to detecting the tap gesture 1050d, the device 600 displays an audio record user interface including a stop affordance 1016 indicating that the device 600 is recording data (e.g., the audio record affordance 1010 has stopped being displayed). In FIG. 10E, in response to detecting the tap gesture 1050d, the device 600 causes one or more of the microphones of the device 600 to record data (e.g., audio data). The data recorded in FIG. 10E (e.g., in response to detecting the tap gesture 1050d) is data recorded for a voice memo application (e.g., that can be accessed by and / or initiated by a voice memo application). In FIG. 10E, the data recorded for the voice memo application is determined to be the first type of data. The data recorded for the voice memo application is determined to be the first type of data because it is determined that the data is recorded so that it is available for later playback.

[0262] As shown in FIG. 10E, because it is determined that the data being recorded for the voice memo application is a first type of data, the device 600 displays a recording status indicator 1042 in place of the cellular signal status indicator 820a. Thus, in some embodiments, the recording status indicator 1042 indicates to the user that one or more media capture devices (e.g., microphone, camera) of the device 600 are recording the first type of data so that the user can stop the device 600 from recording the data if desired. In some embodiments, the user may not be aware that the first type of data is being recorded, such as if the application initiating the recording does not provide an appropriate indication. Thus, in some embodiments, displaying the recording status indicator 1042 can provide the user with information related to the user's privacy (e.g., whether the user's voice or a photo or image of the user has been recorded and is available for later playback on one or more devices). While continuing to record the first type of data for the voice memo application, the device 600 receives an indication of an incoming call via the web calling application.

[0263] As shown in FIG. 10F, in response to receiving an indication of an incoming call, the device 600 displays a web calling user interface including an acceptance affordance 1032 and an indication that an incoming call is being received from an external device associated with "John." As shown in FIG. 10F, the device 600 continues to display the recording status indicator 1042 while displaying the web calling user interface. The device 600 continues to display the recording status indicator 1042 because the device 600 continues to record audio data for the voice memo application as described above in connection with FIG. 10E (e.g., audio recording was not stopped in FIGs. 10E-10F). In FIG. 10F, the device 600 detects a tap gesture 1050f on the acceptance affordance 1032.

[0264] As shown in FIG. 10G, in response to detecting the tap gesture 1050f, the device 600 responds with an incoming call readout and displays a user interface having an end affordance 1034. In FIG. 10G, after the incoming call is answered, the device 600 causes the microphone of the device 600 (e.g., the same or a different microphone as the microphone currently recording data for the voice memo application) to record data for the web calling application. In FIG. 10G, the device 600 is simultaneously recording data for the voice memo application and data for the web calling application (e.g., via the microphone of the device 600). In FIG. 10G, the device 600 determines that the data recorded for the web calling application is a first type of data (e.g., because the data recorded for the web calling application is available to be played by John's device) using one or more techniques similar to those described above. As shown in FIG. 10G, the device 600 does not display an additional recording status indicator. The device 600 does not display an additional recording status indicator because the recording status indicator 1042 is already displayed (e.g., a predetermined number of recording status indicators are displayed) due to the first type of data being recorded in the voice memo application. In some embodiments, if the device 600 was not displaying the recording status indicator 1042 before data was recorded for the web calling application, the device 600 displays the recording status indicator 1042 in response to detecting a tap gesture 1050f. In FIG. 10G, the device 600 detects a downward swipe gesture 1050g.

[0265] As shown in FIG. 10H, in response to detecting the downward swipe gesture 1050g, the device 600 displays the control user interface 1038. The control user interface 1038 includes device controls 1046 for changing the state of the device 600, such as connectivity settings (e.g., wireless, cellular, Bluetooth settings). Additionally, the control user interface 1038 includes a web calling recording status indicator 1044a and a voice memo recording status indicator 1044b because the device 600 is simultaneously capturing a first type of data for a web calling application (e.g., a third party application) and a voice memo application. Because the device 600 is displaying the control user interface 1038, the web calling recording status indicator 1044a and the voice memo recording status indicator 1044b are displayed. The recording status indicators in FIG. 10H each include more visual content than the recording status indicator 1042 shown in FIG. 10G. Additionally, the device 600 displays multiple record state indicators on the control user interface 1038 while displaying only one record state indicator when the control user interface 1038 was not displayed (e.g., in FIG. 10G). In some embodiments, in response to detecting a downward swipe gesture 1050g, the device 600 displays an animation of the record state indicator 1042 transitioning to one or both of the record state indicator 1044a and the voice memo record state indicator 1044b.

[0266] The web calling recording status indicator 1044a includes an application indication 1044a1, a device indication 1044a2, and a configuration indication 1044a3. The application indication 1044a1 indicates an application (e.g., a web calling application) for which the device 600 is recording a first type of data. The device indication 1044a2 indicates that the microphone of the device 600 is being used to record the first type of data for the web calling application. Furthermore, the configuration indication 1044a3 indicates that the web calling recording status indicator 1044a is selectable. The voice memo recording status indicator 1044b includes similar indications, such as an application indication 1044b1 (e.g., indicating that the first type of data for the voice memo application is being recorded) and a device indication 1044b2 (e.g., indicating that the microphone of the device 600 is being used to record the first type of data for the voice memo application). However, as shown in FIG. 10H, the voice memo recording status indicator 1044b does not include a configuration indication.

[0267] In FIG. 10H, the voice memo recording state indicator 1044b does not include a configuration instruction because it is determined that the voice memo application is configurable via the control user interface 1038 (e.g., does not have configurable permission to enable / disable access to the media capture device). Meanwhile, the web calling recording state indicator 1044a includes a configuration instruction 1044a3 because it is determined that the web calling application is a type of application that is configurable via the control user interface 1038. In some embodiments, the device 600 detects a tap gesture 1050h1 on the voice memo recording state indicator 1044b. In some embodiments, in response to detecting the tap gesture 1050h1, the device 600 continues to display the control user interface 1038 without displaying any additional content because the voice memo recording state indicator 1044b is not selectable. In FIG. 10H, the device 600 detects a tap gesture 1050h2 on the web calling recording state indicator 1044a.

[0268] 10I, in response to detecting the tap gesture 1050h2, the device 600 stops displaying the control user interface 1038 and displays a permission management user interface for the Web calling application that includes permission controls 1052. In particular, because the control user interface 1038 has stopped being displayed, the device 600 also stops displaying separate recording status indicators for the Web calling and voice memo applications (e.g., the Web calling recording status indicator 1044a and the voice memo recording status indicator 1044b) and displays a single or combined recording status indicator for the applications (e.g., the recording status indicator 1042).

[0269] As shown in FIG. 10I, the permission control 1052 includes a microphone access affordance 1052a and a camera access affordance 1052b that are both active (e.g., "on"). In some embodiments, in response to detecting a tap gesture on the microphone access affordance 1052a, the device 600 stops allowing data of the web calling application to be recorded via the microphone of the device 600 and stops recording a first type of data of the web calling application that starts recording in response to detecting the input gesture 1050f. In some embodiments, in response to detecting a tap gesture on the camera access affordance 1052a, the device 600 stops allowing data of the web calling application to be recorded via the camera of the device 600. In FIG. 10I, the device 600 detects a right swipe gesture 1050i at the bottom of the permission management user interface.

[0270] As shown in Figure 10J, in response to detecting the right swipe gesture 1050i, the device 600 re-displays the user interface with the exit affordance 1034. In Figure 10J, the device 600 detects a tap gesture 1050j on the exit affordance 1034.

[0271] As shown in FIG. 10K, in response to detecting the tap gesture 1050j, the device 600 stops recording the first type of data of the web calling application (e.g., via the microphone of the device 600) and displays a user interface of the web calling application indicating that the call has ended. In particular, in FIG. 10K, the device 600 continues to display the recording status indicator 1042 as the first type of data continues to be recorded for the voice memo application, but the first type of data has been stopped from being recorded for the web calling application. In FIG. 10K, the device 600 detects an upward swipe gesture 1050k on the user interface of the web calling application indicating that the call has ended.

[0272] As shown in FIG. 10L, in response to detecting an upward swipe gesture 1050k, the device 600 displays a user interface having icons 690 while continuing to display the recording state indicator 1042 using one or more similar techniques as described above (e.g., in FIG. 10E). As shown in FIG. 10L, the icons 690 include a camera application icon 690a. In FIG. 10L, the device 600 detects a tap gesture 1050l on the camera application icon 690a.

[0273] As shown in FIG. 10M, in response to detecting a tap gesture 1050l, the device 600 displays a camera user interface. The camera user interface shown in FIG. 10M is displayed using one or more similar techniques as described above with respect to the camera user interface of FIG. 6A. For example, the camera user interface of FIG. 10M includes an indicator area 602, a camera display area 604, and a control area 606. The camera display area 604 includes a live preview 630, and the control area 604 includes a camera mode affordance 620 and a shutter affordance 610. As shown in FIG. 10M, the video camera mode affordance 620b is centered (e.g., "video" is bolded), indicating that the device 600 is configured to record data representing video media in response to receiving a selection of the shutter affordance 610. In FIG. 10M, the device 600 detects a tap gesture 1050m on the shutter affordance 610.

[0274] As shown in FIG. 10N, in response to detecting a tap gesture 1050m, the device 600 begins recording data for a camera application via one or more cameras of the device 600. In FIG. 10N, a determination is made that the data being recorded for the camera application is a first type of data (e.g., because the recorded data is available for later playback) using one or more similar techniques described above. In FIG. 10N, the device 600 is not displaying any additional recording status indicators (e.g., in addition to the recording status indicator 1042) because the device 600 is not simultaneously displaying the control user interface 1038 (e.g., for similar reasons as described above in connection with FIG. 10G). In FIG. 10N, the device 600 detects a downward swipe gesture 1050n starting near the top of the camera user interface.

[0275] As shown in FIG. 10O, in response to detecting the downward swipe gesture 1050n, the device 600 redisplays the control user interface 1038. The control user interface 1038 includes a voice memo recording status indicator 1044b and a camera recording status indicator 1044c. The camera recording status indicator 1044c includes a device identifier 1044c2 that is different from the device identifier 1044b2 (e.g., of the voice memo recording status indicator 1044b) because the device 600 is using one or more cameras to record the first type of data for the camera application as opposed to using a microphone to record the first type of data. The voice memo recording status indicator 1044b and the camera recording status indicator 1044c are displayed simultaneously because the device 600 is simultaneously recording the first type of data for both applications (e.g., using one or more similar techniques as described above with respect to FIG. 10H).

[0276] FIG. 10P illustrates different versions of the control user interface 1038 that can be displayed in response to detecting a downward swipe gesture 1050n. The control user interface 1038 of FIG. 10P includes an additional indication (e.g., "currently using") of the current state of the use of each application (e.g., voice memo application, camera application) of each device (e.g., microphone, camera). However, the control user interface 1038 does not include the additional indication. In some embodiments, since the additional indication takes up more space in the control user interface, the device 600 can display the additional indication while the first type of data is less than a threshold number (e.g., 1, 2) of applications (and / or devices) or when a threshold number of recording status indicators are displayed simultaneously. Returning to FIG. 10O, the device 600 detects an upward swipe gesture 1050o on the control user interface 1038.

[0277] As shown in Figure 10Q, in response to detecting the swipe gesture 1050o, the device 600 re-displays the camera user interface including the stop affordance 614. In Figure 10Q, the device 600 detects a tap gesture 1050q on the stop affordance 614. As shown in Figure 10R, in response to detecting the tap gesture 1050q, the device 600 stops recording data representing the video media. In Figure 10R, the device 600 detects a swipe gesture 1050r on the camera user interface.

[0278] As shown in FIG. 10S, in response to detecting the swipe gesture 1050r, the device 600 displays the control user interface 1038. As shown in FIG. 10S, the control user interface 1038 continues to display the camera recording status indicator 1044c, but the device 600 is no longer recording the first type of data for the camera application. In FIG. 10S, the device 600 updates the camera recording status indicator 1044c to indicate that the camera application has been recently used (e.g., "Recent" in FIG. 10S), as opposed to the camera recording status indicator 1044c displayed without additional indication in FIG. 10O and / or with additional indication ("Currently Using") in FIG. 10P. Furthermore, in FIG. 10S, the device 600 continues to display the voice memo recording status indicator 1044b because the device 600 is still recording the first type of data for the voice memo application (e.g., using one or more techniques described above and / or for similar reasons). In FIG. 10S, the device 600 detects a right swipe gesture 1050s at the bottom of the control user interface 1038.

[0279] As shown in FIG. 10T, in response to detecting a right swipe gesture 1050s, device 600 displays an audio recording user interface that includes a stop affordance 1016. In FIG. 10S, device 600 detects a tap gesture 1050t on the stop affordance 1016. In some embodiments, in response to detecting the tap gesture 1050t, device 600 stops recording the first type of data of the voice memo application. In some embodiments, after stopping recording the first type of data of the voice memo application, device 600 stops displaying the recording status indication 1042 because device 600 is no longer recording the first type of data.

[0280] As shown in Figure 10U (e.g., some period of time after displaying the audio record user interface), device 600 displays a camera user interface. In Figure 10U, device 600 is operating in a "photo" camera mode, as indicated by the centered photo camera mode affordance 620c and the bolded "Photo."

[0281] As described above with respect to FIG. 6A, device 600 displays live preview 630 by recording data within a field of view ("FOV") of one or more cameras of device 600. Thus, in FIG. 10U, device 600 uses one or more techniques as described above to determine that the data device 600 is recording to display live preview 630 is a first type of data (e.g., because the data being recorded to display live preview 630 can be made available for later playback as indicated by live preview 630). As shown in FIG. 10U, device 600 displays recording status indicator 1042 because it is determined that the data device 600 is recording to display live preview 630 is a first type of data. In some embodiments, device 600 does not display recording status indicator 1042 in FIG. 10U. In some embodiments, device 600 does not display recording state indicator 1042 because a different determination has been made using one or more techniques similar to those described above that the data it is recording to display live preview 630 is not the first type of data (e.g., because the recorded data is not available for playback at a later time). In FIG. 10U, device 600 detects a tap gesture 1050u on shutter affordance 610.

[0282] As shown in Figure 10V, in response to detecting a tap gesture 1050u, device 600 records an image representing live preview 630 and updates media collection 612 to show a representation of the recorded image (see, e.g., the difference between media collection 612 in Figures 10U and 10V). In Figure 10V, device 600 detects an upward swipe gesture 1050v on the camera user interface.

[0283] As shown in FIG. 10W, in response to detecting the swipe gesture 1050v, the device 600 displays a user interface having an icon 690. While displaying the user interface of FIG. 10W, the device 600 continues to display the recording status indicator 1042, even though the device 600 is not simultaneously capturing the first type of data of the camera application. In FIG. 10W, the device 600 displays the recording status indicator 1042 because the recording status indicator 1042 is displayed for at least a minimum period of time after the device 600 records the first type of data of the camera application (e.g., data corresponding to the photograph recorded in FIG. 10W). In other words, the device 600 displays the recording status indicator 1042 for a minimum period of time and / or after the camera stops recording the first type of data, because the device 600 activates the camera for less than a predetermined period of time by recording data corresponding to the recorded photograph (e.g., causes the camera to record media). The user is aware that the application is recording the first type of data, even when the application only records the first type of data for a short period of time. As shown in Figure 10W, a recording status indicator 1042 is displayed near (or adjacent to) one of the cameras (e.g., 1008) of device 600. In Figure 10W, device 600 detects a downward swipe gesture 1050w on a user interface having icon 690.

[0284] As shown in FIG. 10X, in response to detecting the swipe gesture 1050w, the device 600 displays the control user interface 1338. As shown in FIG. 10X, the control user interface 1338 includes a camera recording status indicator 1044c that indicates that the camera was recently used to record a first type of data. In FIG. 10X, the control user interface 1338 includes the camera recording status indicator 1044c because the control user interface 1338 was displayed within a predetermined period of time (e.g., 1-45 seconds) after recording the first type of data of the camera application (e.g., a photo recorded in response to detecting the tap gesture 1050u). Thus, in some embodiments, when the control user interface 1338 is not displayed within a predetermined period of time after finishing recording the first type of data of the camera application, the control user interface 1338 does not include the camera recording status indicator 1044c.

[0285] Fig. 10Y shows the device 600 displaying the device 600 in a locked state, which is indicated by a lock icon 1078a. In Fig. 10Y, the device 600 detects (e.g., via a camera having an FOV) a scene (e.g., a scene including a user's face, a particular object) within the FOV that corresponds to data that unlocks the device 600. As shown in Fig. 10Z, in response to detecting a scene within the FOV that corresponds to data that unlocks the device 600, the device 600 changes from the locked state to an unlocked state, which is indicated by an unlock icon 1078b.

[0286] In particular, in Figs. 10Y-10Z, the device 600 is recording data via the device 600's camera (e.g., using a first trusted application) to identify a portion of the scene that allows the device 600 to change to an unlocked state. However, in Figs. 10Y-10Z, a determination is made that the data being recorded by the device 600 is not a first type of data, and therefore the device 600 does not display the recording state indicator 1042. In Figs. 10A-10B, the device 600 is not recording the first type of data, and therefore the recorded data is determined to be data that is not available for later playback. Specifically, the data recorded in Figs. 10Y-10Z is not available for later playback, because the device 600 is recording data to identify a portion of the scene within the FOV that allows the device 600 to change to an unlocked state.

[0287] 10AA-10AC show device 1000 displaying a user interface that includes a capture state indicator 1042. Device 1000 optionally includes one or more components of device 100, device 300, and device 500 described above.

[0288] As shown in FIG. 10AA, device 1000 displays a user interface that includes status bar 1022. Because in FIG. 10AA device 1000 displays a user interface that includes status bar 1022, device 1000 displays capture status indicator 1042 in status bar 1022 along with status indicators 1022a-1022e. Capture status indicator 1042 is the leftmost status indicator 1022a-1022e. In some embodiments, when a status indicator is removed from status bar 1022, such as status bar indicator 1022c, the remaining status bar indicators move to the right to fill in the space vacated by the removed status indicator, and capture status indicator 1042 remains the leftmost status indicator in the status bar. In some embodiments, when a status indicator is added to status bar 1022, capture status indicator 1042 moves to the left and remains the leftmost status indicator in status bar 1022.

[0289] Figure 10AB shows device 1000 displaying a user interface that does not include a status bar. In Figure 10AA, device 1000 does not display a status bar, so device 1000 displays capture status indicator 1042 in the upper right corner of the user interface, a different location than where capture status indicator 1042 was displayed in Figure 10AA (e.g., when status bar 1022 is displayed).

[0290] FIGURE 10AC illustrates device 1000 displaying a user interface that does not include a status bar when device 1000 is in a different orientation than device 1000 in FIGURE 10AB. As shown in FIGURE 10AC, device 600 is in a different orientation in FIGURE 10AC compared to device 1000 in FIGURE 10AB, yet device 1000 captures status indicator 1042 in the upper right of the user interface. Thus, looking at FIGURES 10AB-10AC, when the status bar is not displayed, device 1000 displays the capture status indicator in the same position regardless of the orientation of device 600.

[0291] 11 is a flow diagram illustrating a method for providing a status indicator using a computer system, according to some embodiments. Method 1100 is performed in a computer system (e.g., 100, 300, 500, 600) having a first media capture device (e.g., one or more cameras (e.g., dual camera, triple camera, quad camera, etc.) on the same or different sides (e.g., front camera, rear camera), and / or one or more microphones, etc.) in communication with a display generation component (e.g., a display controller, a touch-sensitive display system) and one or more input devices (e.g., a touch-sensitive surface). Some operations of method 1100 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0292] As described below, the method 1100 provides an intuitive way of providing a status indicator to a user of a computer system. The method reduces the cognitive burden on the user to determine the status of one or more media capture devices, thereby creating a more efficient human-machine interface. In the case of battery-operated computing devices, it conserves power and increases the time between battery charges by allowing a user to manage one or more media capture devices faster and more efficiently.

[0293] A computer system (e.g., 600) (e.g., a smart phone, a smart watch) receives an indication (1102) that a first media capture device has been activated (e.g., has been recently activated (e.g., has been activated within a predetermined time (e.g., 1 or 2 seconds) prior to receiving the indication). In some embodiments, the computer system receives the indication that the first media capture device has been activated by detecting that the first media capture device is active or has actively recorded data (e.g., data representing one or more different types of media (e.g., audio, video, images (e.g., still images))). In some embodiments, the computer system receives the indication that the first media capture device (e.g., a video camera) is currently being (or is using) a camera or microphone to capture or record media by detecting one or more applications.

[0294] In response to receiving an indication that the first media capture device is activated (1104), and pursuant to a determination that the first media capture device has recorded (1106) the first type of data (e.g., within a first predetermined time period) while activated (e.g., regardless of (e.g., independently of, without regard to) whether the media capture device has recorded a second type of data), the computer system displays (1108) via the display generation component a graphical indicator (e.g., 1042, 1044a-1044d) indicating activation of the first media capture device. In some embodiments, the first type of data is data that has been recorded, stored, retained, or is otherwise available (e.g., available to one or more applications that cause the media capture device to record the data) as a media item to be played at a later time. In some embodiments, the first type of data is data that is readably accessible (e.g., via one or more programs or applications on the system) to be selected and played by a user via one or more user inputs on a touch-sensitive display of the computer system. In some embodiments, pursuant to a determination that the first media capture device recorded the first type of data while activated (e.g., regardless of whether the media capture device recorded the second type of data (e.g., independently of, without regard to)). In some embodiments, the computer system, pursuant to a determination that the first media capture device recorded the first type of data while activated, replaces the graphical indicator indicating that the other media capture device is activated with a graphical indicator indicating activation of the first media capture device.In some embodiments, the first type of data is data that has not been captured and / or processed to determine whether one or more trigger events (e.g., an audible phrase, presenting / not presenting a user's gaze) have occurred. In some embodiments, the first type of data (e.g., the type of data for which a capture status indicator is displayed) corresponds to data passed to an untrusted application (e.g., a non-first party voice assistant application, a non-first party authentication application). In some embodiments, the recording status indicator is displayed independent of whether an indicator of recording is displayed by the application recording the data. Displaying a graphical indicator when a predetermined condition is met (e.g., when a media capture device records a first type of data (e.g., multimedia data)) allows a user to quickly recognize when a particular type of data is being (or has been) recorded and allows a user to take a particular action based on the type of data being (or has been) recorded. Taking an optimized action when a set of conditions is met without requiring further user input enhances the usability of the system, making the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), as well as reducing system power usage and improving battery life by allowing the user to use the system more quickly and efficiently. Displaying a graphical indicator when the media capture device records a first type of data (e.g., multimedia data) provides feedback to the user that the first media capture device is active and recording the first type of data, thereby allowing the user to be alerted to the recording of the first type of data.Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and additionally reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0295] In some embodiments, the first media capture device is a second type of media capture device. In some embodiments, the computer system displays (1110) a third graphical indicator (e.g., 1044c) different from the graphical indicator (e.g., 1044b) simultaneously with the graphical indicator. In some embodiments, the graphical indicator includes an indication of the second type of media capture device, and the third graphical indicator includes an indication of a third type of media capture device different from the second type of media capture device. In some embodiments, a fourth graphical indicator is displayed along with the graphical indicator. In some embodiments, the fourth graphical indicator is associated with the same media capture device (e.g., the second type of media capture device) as the graphical indication. In some embodiments, the graphical indicator includes content indicating that the first application is using or has used the first type of media capture device, while the graphical indicator includes content indicating that a second application different from the first application is using or has used the first type of media capture device. In some embodiments, the third graphical indicator is displayed pursuant to determining that the computer system is displaying the first user interface (e.g., a settings configuration user interface). In some embodiments, pursuant to a determination that the computer system is displaying a second user interface that is not the first user interface (e.g., a settings configuration user interface), the third graphical indicator is not displayed. In some embodiments, the graphical indicator and the third graphical indicator are displayed simultaneously (e.g., in response to receiving a first input (e.g., a drag input) and / or when displaying a user interface that includes multiple settings (e.g., for controlling one or more settings of the computer system)).Displaying a graphical indicator indicating that a first type of media capture device (e.g., a microphone) is capturing a first type of data and a graphical indication indicating that a second type of media capture device (e.g., a camera) is capturing a second type of data provides feedback to a user as to whether the first type of media capture device and the second type of media capture device are being used simultaneously to capture the first type of data. Providing improved visual feedback to the user improves usability of the system, makes the user-system interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the system and reducing user errors), and also reduces power usage and improves battery life of the system by allowing the user to use the system more quickly and efficiently.

[0296] In response to receiving an indication that the first media capture device is activated (1104), and in accordance with a determination that while activated, the first media capture device recorded a second type of data (e.g., different from the first type) (e.g., FIGS. 10A-10B, 10Y-10Z) without recording the first type of data (e.g., within a predetermined time period), the computer system ceases displaying (1112) a graphical indicator (e.g., 1042, 1044a-1044d) indicating activation of the first media capture device. In some embodiments, the second type of data is data that has been acquired and / or processed to determine whether one or more trigger events (e.g., an audible phrase, presentation / non-presentation of a user's gaze) have occurred. In some embodiments, the second type of data is data that has not been stored (and / or is not available) as a media item (e.g., audio, video media) to be played at a later time. In some embodiments, the second type of data is data that is not readably accessible (e.g., via one or more programs or applications on the system) to be selected and played by a user via one or more user inputs on a touch-sensitive display of the computer sy...

Claims

1. 1. A method comprising:

1. A computer system in communication with one or more media capture devices, a display generation component, and one or more input devices, comprising: receiving a request to display a respective user interface while at least one of the one or more media capture devices is activated; displaying the respective user interface in response to receiving the request to display the respective user interface while at least one of the one or more media capture devices is activated; and and displaying the respective user interface comprises: pursuant to determining that at least one of the one or more media capture devices has been activated by a first application, displaying the respective user interface simultaneously with a first graphical indicator indicating activation of the at least one of the one or more media capture devices and including an indication of the first application; pursuant to a determination that at least one of the one or more media capture devices has been activated by a second application distinct from the first application, displaying the respective user interface concurrently with a second graphical indicator indicating activation of the at least one of the one or more media capture devices and including an indication of the second application; A method comprising:

2. detecting a first input while displaying the respective user interface; In response to detecting the first input, displaying, via the display generation component, a first user interface including content of the first application in accordance with determining that the first input is directed to the first graphical indicator; displaying, via the display generation component, a first user interface including content of the second application in accordance with determining that the first input is directed to the second graphical indicator; 2. The method of claim 1, further comprising: wherein the first user interface including content of the first application is different from the first user interface including content of the second application.

3. The method of claim 1 or 2, wherein the first graphical indicator is displayed simultaneously with the second graphical indicator.

4. 4. The method of claim 1, wherein the first graphical indicator includes an indication of a first type of media capture device corresponding to at least one of the one or more media capture devices, and the second graphical indicator includes an indication of a second type of media capture device corresponding to at least one of the one or more media capture devices.

5. 5. The method of claim 1, wherein at least one of the instructions of the first application and the instructions of the second application are instructions of an application that is currently recording data via the one or more media capture devices.

6. 6. The method of claim 1 , wherein at least one of the instructions of the first application and the instructions of the second application are instructions of an application that previously recorded data via the one or more media capture devices.

7. detecting a second input while displaying the respective user interface; In response to detecting the second input, displaying, via the display generation component, additional information corresponding to the first graphical indicator in response to determining that the second input is directed to the first graphical indicator; and displaying, via the display generation component, additional information corresponding to the second graphical indicator in response to determining that the second input is directed to the second graphical indicator; and The method of claim 1 , further comprising: wherein the additional information corresponding to the second graphical indicator is different from the additional information corresponding to the first graphical indicator.

8. detecting a third input directed at the first graphical indicator while displaying the respective user interface; and in response to detecting the third input directed at the first graphical indicator, displaying, via the display generation component, additional information corresponding to the first graphical indicator.

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

9. 9. The method of claim 8, wherein the additional information corresponding to the first graphical indicator includes a settings control that, when selected, causes settings related to at least one of the one or more media capture devices and the first application to be changed.

10. detecting a fourth input while displaying, via the display generation component, the additional information corresponding to the first graphical indicator; and in response to detecting the fourth input, displaying, via the display generation component, a second user interface including content of the first application.

10. The method of claim 9.

11. detecting a fifth input while the first graphical indicator is displayed simultaneously with the second graphical indicator; in response to detecting the fifth input, ceasing display of the first graphical indicator and the second graphical indicator while displaying a third graphical indicator; The method of claim 1 , further comprising: a third graphical indicator corresponding to at least one of the first graphical indicator and the second graphical indicator.

12. The method of claim 11 , wherein the third graphical indicator does not include either the indication of the first application or the indication of the second application.

13. detecting a sixth input directed at the first graphical indicator while displaying the respective user interface; and in response to detecting the sixth input directed at the first graphical indicator, displaying, via the display generation component, additional information corresponding to the first graphical indicator.

13. The method according to any one of claims 1 to 12.

14. A computer program product configured to cause a computer system in communication with one or more media capture devices, a display generation component and one or more input devices to perform the method of any one of claims 1 to 13.

15. 1. A computer system comprising: A memory for storing a computer program according to claim 14; one or more processors capable of executing the computer programs stored in the memory; in communication with one or more media capture devices, a display generation component, one or more input devices, and one or more tactile output generators.

16. 1. A computer system configured to communicate with one or more media capture devices, a display generation component, and one or more input devices, comprising: A computer system comprising means for carrying out the method according to any one of claims 1 to 13.

Images