Displaying and updating application view groups

Abstract

The present disclosure relates to displaying and updating sets of application views. The present disclosure generally relates to viewing and updating application views. A device receives a user input that, when received, initiates display of a plurality of application views of a set of application views. The device displays the plurality of application views of the set of application views in response to receiving the user input, where the set of application views includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

Description

[0001] This application is a divisional application of Invention Patent Application No. 201780033771.2, filed May 31, 2017, entitled "Displaying and Updating Sets of Application Views", which is incorporated by reference in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for managing application views. BACKGROUND

[0003] Many modern electronic devices provide the ability to select and open an application for accessing the content and functionality of the application. Some techniques for selecting and opening an application are based on scrolling through a plurality of applications. These techniques can be cumbersome and inefficient. SUMMARY

[0004] However, some techniques for selecting and opening an application with an electronic device are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface that can include multiple key presses or keystrokes. Existing techniques require more time than is necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0005] Accordingly, the present disclosure provides faster, more efficient methods and interfaces for viewing and updating sets of application views for accessing corresponding applications with an electronic device. Such methods and interfaces optionally supplement or replace other methods for selecting and opening an application. Such methods and interfaces reduce the cognitive burden placed on the user and produce a more efficient human-machine interface. For battery- powered computing devices, such methods and interfaces conserve power and increase the time between battery charges.

[0006] In some embodiments, a method includes: at a device with one or more processors and memory, receiving a user input that, when received, initiates display of a plurality of application views of a set of application views; and in response to receiving the user input, displaying the plurality of application views of the set of application views, wherein the set of application views includes a preselected application view and an adaptive view that corresponds to a most recently opened application that is not one of the preselected application views.

[0007] In some embodiments, an electronic device, comprising: a display; one or more processors; one or more input devices; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, includes instructions for: receiving a user input that, when received, initiates display of a plurality of application views of a group of application views; and in response to receiving the user input, displaying the plurality of application views of the group of application views, wherein the group of application views includes a preselected application view and an adaptive view that is not one of the preselected application views and that corresponds to a most recently opened application.

[0008] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to: receive a user input that, when received, initiates display of a plurality of application views of a group of application views; and in response to receiving the user input, display the plurality of application views of the group of application views, wherein the group of application views includes a preselected application view and an adaptive view that is not one of the preselected application views and that corresponds to a most recently opened application.

[0009] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to: receive a user input that, when received, initiates display of a plurality of application views of a group of application views; and in response to receiving the user input, display the plurality of application views of the group of application views, wherein the group of application views includes a preselected application view and an adaptive view that is not one of the preselected application views and that corresponds to a most recently opened application.

[0010] In some embodiments, a method includes, at a device with one or more processors and memory: receiving a first user input, the first user input, when received, eliciting display of a plurality of application views of a group of application views, wherein the group of application views includes preselected application views, the plurality of application views of the group of application views being displayed in respective first states; automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state; updating the at least one application view of the group of application views to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied; receiving a second user input, the second user input, when received, eliciting display of the plurality of application views of the group of application views; and in response to receiving the second user input, displaying the plurality of application views of the group of application views including the updated at least one application view updated to the second state.

[0011] In some embodiments, an electronic device, comprising: a display; one or more processors; one or more input devices; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a first user input, the first user input, when received, eliciting display of a plurality of application views of a group of application views, wherein the group of application views includes preselected application views, the plurality of application views of the group of application views being displayed in respective first states; automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state; updating the at least one application view of the group of application views to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied; receiving a second user input, the second user input, when received, eliciting display of the plurality of application views of the group of application views; and in response to receiving the second user input, displaying the plurality of application views of the group of application views including the updated at least one application view updated to the second state.

[0012] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs that include instructions for one or more processors of an electronic device with a display and one or more input devices to: receive a first user input that, when received, causes display of a plurality of application views of a group of application views, wherein the group of application views includes a preselected application view, the plurality of application views of the group of application views being displayed in respective first states; automatically determine, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state; update the at least one application view of the group of application views to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied; receive a second user input that, when received, causes display of the plurality of application views of the group of application views; and display, in response to receiving the second user input, the plurality of application views of the group of application views including the updated at least one application view updated to the second state.

[0013] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs that include instructions for one or more processors of an electronic device with a display and one or more input devices to: receive a first user input that, when received, causes display of a plurality of application views of a group of application views, wherein the group of application views includes a preselected application view, the plurality of application views of the group of application views being displayed in respective first states; automatically determine, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state; update the at least one application view of the group of application views to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied; receive a second user input that, when received, causes display of the plurality of application views of the group of application views; and display, in response to receiving the second user input, the plurality of application views of the group of application views including the updated at least one application view updated to the second state.

[0014] In some embodiments, a method includes, at a device with one or more processors and memory: displaying a watch face; receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view; in response to receiving the first user input, displaying the plurality of application views of the application view group; receiving a second user input on an application view of the plurality of application views that is displayed, the second user input, when received, initiating launch of an application corresponding to the application view selected by the second user input; and in response to receiving the second user input, replacing the plurality of application views that are displayed by displaying a user interface of the launched application.

[0015] In some embodiments, an electronic device, comprising: a display; one or more processors; one or more input devices; memory; one or more programs, wherein the one or more programs are stored in the memory and configured to, with the processing of the one or more processors, cause the device to: display a watch face; receive a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view; in response to receiving the first user input, display the plurality of application views of the application view group; receive a second user input on an application view of the plurality of application views that is displayed, the second user input, when received, initiating launch of an application corresponding to the application view selected by the second user input; and in response to receiving the second user input, replace the plurality of application views that are displayed by displaying a user interface of the launched application.

[0016] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs that include instructions for one or more processors of an electronic device with a display and one or more input devices to: display a watch face; receive a first user input that, when received, triggers display of a plurality of application views of a group of application views, wherein the group of application views includes a preselected application view; in response to receiving the first user input, display the plurality of application views of the group of application views; receive a second user input on an application view of the displayed plurality of application views that, when received, triggers launching of an application corresponding to the application view selected by the second user input; and in response to receiving the second user input, replace the displayed plurality of application views by displaying a user interface of the launched application.

[0017] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs that include instructions for one or more processors of an electronic device with a display and one or more input devices to: display a watch face; receive a first user input that, when received, triggers display of a plurality of application views of a group of application views, wherein the group of application views includes a preselected application view; in response to receiving the first user input, display the plurality of application views of the group of application views; receive a second user input on an application view of the displayed plurality of application views that, when received, triggers launching of an application corresponding to the application view selected by the second user input; and in response to receiving the second user input, replace the displayed plurality of application views by displaying a user interface of the launched application.

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

[0019] Thus, devices are provided with faster, more efficient methods and interfaces for displaying and updating application views, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace other methods for viewing and updating application views. BRIEF DESCRIPTION OF DRAWINGS

[0020] For a better understanding of the various described implementations, reference should be made to the following detailed description in connection with the accompanying drawings in which like numerals refer to corresponding parts throughout the views.

[0021] Figure 1A FIG. 1C is a block diagram illustrating portable multifunction device 100 in accordance with some embodiments. As shown in FIG. 1C, portable multifunction device 100 can include memory 980, memory controller 950, storage 965, I / O controller 970, display 910, and display controller 960.

[0022] Figure 1B FIG. 1G is a block diagram illustrating example components of a multifunction device for event processing in accordance with some embodiments.

[0023] Figure 2 FIG. 1H illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

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

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

[0026] Figure 4B FIG. IK illustrates an example user interface for a multifunction device having a display that is separate from a touch-sensitive surface in accordance with some embodiments.

[0027] Figure 5A FIG. 1L illustrates a personal electronic device in accordance with some embodiments.

[0028] Figure 5B FIG. 1M is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0029] Figures 5C to 5D FIG. 1N illustrates example components of a personal electronic device having a touch-sensitive display and an intensity sensor in accordance with some embodiments.

[0030] Figures 5E to 5H FIG. 1O illustrates example components and user interfaces of a personal electronic device in accordance with some embodiments.

[0031] Figures 6A to 6N FIG. 1P illustrates an example user interface in accordance with some embodiments.

[0032] Figures 7A to 7L FIG. 1Q illustrates an example user interface in accordance with some embodiments.

[0033] Figures 8A to 8C FIG. 1R illustrates an example user interface in accordance with some embodiments.

[0034] Figures 9A to 9I FIG. 1S illustrates an example user interface in accordance with some embodiments.

[0035] Figures 10A to 10Q A flow diagram illustrating a method for operating an electronic device in accordance with some embodiments is shown.

[0036] Figure 11 An example functional block diagram of an electronic device in accordance with some embodiments is shown.

[0037] Figures 12A to 12G An example user interface in accordance with some embodiments is shown.

[0038] Figure 13 A flow diagram illustrating a method for operating an electronic device in accordance with some embodiments is shown.

[0039] Figure 14 An example functional block diagram of an electronic device in accordance with some embodiments is shown.

[0040] Figures 15A to 15C An example user interface in accordance with some embodiments is shown.

[0041] Figure 16 A flow diagram illustrating a method for operating an electronic device in accordance with some embodiments is shown.

[0042] Figure 17 An example functional block diagram of an electronic device in accordance with some embodiments is shown. DETAILED DESCRIPTION

[0043] The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is included merely for illustrative purposes.

[0044] There is a need to provide electronic devices with efficient methods and interfaces for displaying and updating application views corresponding to respective applications. For example, some embodiments of the interfaces and techniques described below provide an efficient and simple user interface for selecting an application for launching. Such techniques can reduce the cognitive burden on a user to browse through various applications and select one of the multiple applications for launching, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

[0045] The following Figures 1A to 1B , Figure 2 , Figure 3 , Figures 4A to 4B and Figures 5A to 5H provides a description of an example device for performing techniques for managing event notifications. Figures 6A to 9IAn example user interface for displaying a set of application views is shown. FIG. 10 is a flow diagram illustrating a method of displaying a set of application views in accordance with some embodiments. Figures 6A to 9I The user interface in FIG. 10 is used to illustrate the processes described below, including the processes in FIG. 10. Figures 12A to 12G An example user interface for updating a set of application views is shown. Figure 13 FIG. 10 is a flow diagram illustrating a method of updating a set of application views in accordance with some embodiments. Figures 12A to 12G The user interface in FIG. 10 is used to illustrate the processes described below, including the processes in FIG. 10. Figure 13 The user interface in FIG. 10 is used to illustrate the processes described below, including the processes in FIG. 10. Figures 15A to 15C An example user interface for displaying a set of application views is shown. Figure 16 FIG. 10 is a flow diagram illustrating a method of displaying a set of application views in accordance with some embodiments. Figures 15A to 15C The user interface in FIG. 10 is used to illustrate the processes described below, including the processes in FIG. 10. Figure 16 The user interface in FIG. 10 is used to illustrate the processes described below, including the processes in FIG. 10.

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

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

[0048] The term "if' is optionally interpreted as meaning "when," "while," or "in response to a determination," or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" is optionally interpreted as meaning "upon being determined," or "in response to determining," or "upon detecting [the stated condition or event]," or "in response to detecting [the stated condition or event]," depending on the context.

[0049] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other exemplary embodiments can include a device, an iPod device, and a device. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and / or a touch pad).

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

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

[0052] Various application programs executing on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as corresponding information displayed on the device, are optionally adjusted and / or varied

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

[0054] As used in the specification and claims, the term "intensity" of a contact on a touch- sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch- sensitive surface, or a proxy for the force or pressure of the contact on the touch- sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath (or adjacent to) the touch- sensitive surface optionally are used to measure force at various points on the touch- sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force. Similarly, a pressure- sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch- sensitive surface. Alternatively, the size of the contact area (or an change in the size of the contact area) detected on the touch- sensitive surface, the capacitance of the touch- sensitive surface proximate to the contact (or a change in the capacitance of the touch- sensitive surface), and / or the resistance of the touch- sensitive surface proximate to the contact (or a change in the resistance of the touch- sensitive surface) are, optionally, used as a substitute for the force or pressure of the contact on the touch- sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that would not be accessible by a user utilizing only a size-restricted number of device inputs (e.g., a reduced number of device inputs available on a size-restricted device, such as a smart watch, that is used to, for example, display a user interface and / or receive user input).

[0055] As used in the specification and claims, the term "tactile output" refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (for example, a touch-sensitive surface) of a device relative to another component (for example, a housing) of the device, or displacement of a component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface (for example, a surface of a user that is sensitive to touch), tactile outputs generated by physical displacement will be interpreted by the user as a tactile sensation that the user feels. For example, movement of a touch-sensitive surface (for example, a touch-sensitive display or trackpad) that is moved by the user's finger will be interpreted by the user as a "down click" or "up click" of a physical button even if the touch-sensitive surface does not move and even if there is no physical button. Similarly, movement of a touch-sensitive surface that is associated with a graphical user interface element, such as a button of a graphical user interface, will be interpreted by the user as an "up click" or "down click" of the button even if there is no physical button in direct contact with the user's body. As another example, a user will sense tactile sensations such as "down clicks," "up clicks," "roughness," and "friction" even if there is no physical button or touch-sensitive surface of any kind that moves in response to the user's interaction with the device. In these situations, the tactile outputs are generated by physical displacement of components of the device relative to one another, by physical displacement of components of the device relative to a center of mass of the device, or by physical displacement of components of the device relative to a housing of the device. By using force sensors, tactile sensors, or touch-sensitive surfaces, the device is able to generate

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

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

[0058] The peripheral interface 118 can be used to couple the device's input and output peripherals to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral interface 118, CPU 120, and 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.

[0059] RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to / from electromagnetic signals and communicates with communications networks and other communications devices, via the electromagnetic signals. The RF circuitry 108, optionally, includes well-known circuitry for detecting near-field communications (NFC) fields and performing NFC transactions, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Wideband-CDMA (W-CDMA), Long Term Evolution (LTE), Near Field Communication (NFC), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.1 lb, IEEE 802.1 lg, IEEE 802.1 In, and / or IEEE 802.1 lac), Wi-MAX, a protocol for e-mail (e.g., Internet Message Access Protocol (IMAP) and / or

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

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

[0062] ​​​A quick press of the lower button optionally unlocks the touch screen 112 or, optionally, begins a process that unlocks the device, as described in U.S. Patent Application 11 / 322,549, "Unlocking a Device by Performing Gestures on an Unlock Image," filed on December 23, 2005 (now U.S. Patent No. 7,657,849); this patent is hereby incorporated by reference in its entirety. A longer press of the lower button (e.g., 206) optionally turns the device on or off. The functionality of one or more of the buttons is, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

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

[0064] Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and / or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and / or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the

[0065] Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally use and iPod Techniques used in the middle.

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

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

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

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

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

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

[0072] Device 100 optionally also includes one or more contact intensity sensors 165. Figure 1A A contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106 is shown. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact

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

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

[0075] Device 100 optionally also includes one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to peripherals interface 118 is shown. Alternatively, accelerometer 168 is coupled to an input controller 160 in I / O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received by one or more accelerometers. Device 100 optionally includes a magnetometer (not shown) and GPS (or GLONASS or other global navigation system) receivers (not shown), which are used

[0076] In some embodiments, software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact / motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Further, in some embodiments, memory 102 Figure 1A ) or 370 Figure 3 ) store device / global internal state 157, as shown in Figure 1A and Figure 3 Device / global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what, if anything, is currently being displayed by the touch screen display 112; sensor state, including information from the device’s various sensors and input control devices 116; and location information regarding the device’s location and / or attitude.

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

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

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

[0080] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether operations have been performed (e.g., whether a user has "clicked" an icon). In some embodiments, at least a sub-set of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, without changing the touchpad or touch screen display hardware, mouse "click" thresholds of the touchpad or touch screen can be set to any one of a large range of predefined thresholds. Additionally, in some implementations, software settings are provided to users of devices to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-wide click on an "intensity" parameter).

[0081] Contact / motion module 130 optionally detects gestures on touch-sensitive surface. Different gestures on the touch-sensitive surface have different motion pattern (e.g., different trajectories of detected contact, timing, and / or intensity of the detected contact). Accordingly, the gesture is optionally detected by detecting a particular motion pattern. For example, detecting a finger tap gesture includes detecting a finger-down event, followed by 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-dragging events, and followed by a finger-up (lift off) event.

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

[0083] In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed, and then generates screen image data for a

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

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

[0086] GPS module 135 determines the location of the device and provides this information for various applications (e.g., to telephone 138 for use in

[0087] Applications 136, optionally, include the following modules (or sets of instructions):

[0088] • a contacts module 137 (sometimes referred to as an address book or contact list);

[0089] • a telephone module 138;

[0090] • a video conference module 139;

[0091] • an e-mail client module 140;

[0092] • an instant messaging (IM) module 141;

[0093] • a fitness support module 142;

[0094] • a camera module 143 for still and / or video images;

[0095] • an image management module 144;

[0096] • a video player module;

[0097] • a music player module;

[0098] • a browser module 147;

[0099] • a calendar module 148;

[0100] • a widget module 149, which optionally includes one or more of the following widgets: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, a clock widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user and a user-created widget 149-6;

[0101] • a widget creator module 150 for making the user-created widget 149-6;

[0102] • a search module 151;

[0103] • a video and music player module 152, which merges video player module and music player module;

[0104] • a notepad module 153;

[0105] • a map module 154; and / or

[0106] • an online video module 155.

[0107] Examples of other applications 136 that can optionally be stored on the storage 102 include other word processing applications, other image editing applications, a drawing application, a presentation application, a JAVA-enabled application, an encryption, a digital rights management, a voice recognition and a voice replication.

[0108] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding one or more new names; deleting one or more existing names; associating one or more telephone numbers with a name; associating one or more e-mail addresses with a name; associating one or more physical addresses with a name; associating one or more user IDs with a name; pushing / flowing contacts of a

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

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

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

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

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

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

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

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

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

[0118] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop app module 149 are mini-applications (e.g., weather desktop app 149-1, stocks desktop app 149-2, calculator desktop app 149-3, alarm clock desktop app 149-4, and dictionary desktop app 149-5) that are optionally downloaded and used by a user (e.g., from an application store 193) and / or created by the user (e.g., from a desktop app creator module 150). In some embodiments, desktop apps include HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheet) files, and JavaScript files. In some embodiments, desktop apps include XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! Desktop apps).

[0119] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop app creator module 150 are optionally used by a user to create desktop apps (e.g., user- specified portions of web pages).

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

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

[0122] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like using a format similar to "sticky" notes. In some embodiments, notes module 153 includes executable instructions to send reminder messages in accordance with a scheduled time or location.

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

[0124] Incorporating touchscreen 112, display controller 156, touch / 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, the online video module 155 includes instructions for performing the following operations: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0125] Each of the above modules and applications corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the above-described modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0126] In some embodiments, device 100 is a device for which a predefined set of functions on the device are operated exclusively through the touch screen and / or touchpad. By using the touch screen and / or touchpad as the primary input control devices for operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.

[0127] The predefined set of functions that are operated exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main menu, home menu, or root menu. In such embodiments, the touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

[0128] Figure 1B FIG. 1 is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (e.g., memory 102 of device 100 of FIG. 1) or 370 (e.g., memory 370 of device 300 of FIG. 3) includes an event classifier 170 (e.g., in operating system 126) and corresponding application programs 136-1 (e.g., any of the aforementioned application programs 137-151, 155, 380-390). Figure 1A ) or 370 ( Figure 3 ) includes an event classifier 170 (e.g., in operating system 126) and corresponding application programs 136-1 (e.g., any of the aforementioned application programs 137-151, 155, 380-390).

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

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

[0131] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch- sensitive display 112 that are 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 168, and / or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or touch- sensitive surface.

[0132] In some embodiments, event monitor 171 sends a request 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., when a high noise threshold is received and / or when an input is received that exceeds a predetermined duration).

[0133] In some embodiments, event categorizer 170 also includes hit view determination module 172 and / or active event recognizer determination module 173.

[0134] When touch-sensitive display 112 displays more than one view, hit view determination module 172 provides a software procedure for determining where a sub-event has occurred within one or more views. A view is made up of controls and other elements that a user is able to see on the display.

[0135] Another aspect of a user interface associated with an application is a set of views, also 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 a touch is detected optionally corresponds to a programmed level within the application's programmed or view hierarchy. For example, the lowest level view in which a touch is detected is optionally referred to as the hit view, and the set of events that are recognized as being correctly entered is optionally determined based at least in part on the hit view of an initial touch that begins a touch-based gesture.

[0136] Hit view determination module 172 receives information related to touch-based gesture sub-events. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the 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 that is identified as the hit view.

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

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

[0139] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In another embodiment, event classifier 170 is a standalone module, or is part of another module stored in memory 102, such as contact / motion module 130.

[0140] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, where each application view includes instructions for handling touch events that occur within a respective view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a standalone module, such as a user interface toolkit (not shown) or a higher level object from which the application 136-1 inherits methods and other attributes. In some embodiments, a respective event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls for related data 180 from event sorter 170, device controller 952, and / or event router 956. Event handler 190

[0141] A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and recognizes the 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 (which optionally include sub-event delivery instructions).

[0142] Event receiver 182 receives event information from event sorter 170. The event information includes information about the sub-event, e.g., a touch or touch movement. Additionally, the event information also includes information about other aspects such as location of the sub-event. When the sub-event involves a touch by a finger, event information additionally includes information about which finger touched the touch screen, as well as a location of the touch by the finger. In some embodiments, event information additionally includes a

[0143] Event comparator 184 compares event information to predefined event or sub-event definitions and determines an event or sub-event, or a status of an event or sub-event, based on the comparison. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events 187 include, for example, touch begin, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double tap on a displayed object. For example, a double tap includes a first touch (touch begin) on a displayed object for a predetermined duration, a first lift off (touch end) for a predetermined duration, a second touch (touch begin) on the displayed object for a predetermined duration, and a second lift off (touch end) for a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, a drag includes a touch (or contact) on a displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and a lift off of the touch (touch end). In some embodiments, events also include information for one or more associated event handlers 190.

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

[0145] In some embodiments, the definition of a respective event 187 also includes a deferred action that delays delivery of event information until it has been determined that a sequence of sub-events does or does not correspond to an event type of the event recognizer.

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

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

[0148] In some embodiments, when a particular sub-event of an event is recognized, the respective event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the respective event recognizer 180 delivers event information associated with the event to the event handler 190. Activating an event handler 190 is distinct from sending (and deferring sending) a sub-event to a respective hit view. In some embodiments, an event recognizer 180 emits a flag associated with the recognized event, and an event handler 190 associated with the flag picks up the flag and performs a pre-defined process.

[0149] 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 the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with the actively participating view receives the event information and performs a pre-determined process.

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

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

[0152] It should be understood that the above discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to the multi-function device 100 not all of which are touch-based. For example, mouse movements and mouse button presses, optionally coordinated with single or multi-key presses or holds, are also optionally used as user input. Other user input can include touch screen movements, touch pad movements, touch pen input, device movements, voice input, eye movements, biometric input, and / or any combination thereof.

[0153] Figure 2The portable multifunction device 100 with touch screen 112 is, according to some embodiments, shown. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as in other embodiments described below, a user is capable of selecting one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or with one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the graphics. In some embodiments, a gesture is, optionally, a one or more taps, one or more swipes (from left to right, right to left, upward and / or downward) and / or a rolling of a finger (from right to left, left to right, upward and / or downward) that has made contact with the device 100. In some implementations or in some situations, an inadvertent or unsolicited touch of a graphic does not select the graphic. For example, when a gesture is a tap, a swipe gesture that begins on the graphics and ends outside the graphics optionally does not select the graphic. In some embodiments, a swipe gesture that begins on the graphics and ends on the graphics optionally does not select the graphic.

[0154] The device 100 optionally also includes one or more physical buttons, such as a home or menu button 204. As described previously, the menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that is, optionally, executed by the device 100. Alternatively, the menu button is, optionally, implemented as a soft key in a GUI displayed by the touch screen.

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

[0156] Figure 3is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an education device (such as a child's learning toy), a gaming device, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPU's) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input / output (I / O) interface 330 comprising display 340, which is typically a touch screen display. I / O interface 330 also optionally includes keyboard and / or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs (e.g., similar to the tactile output generator(s) 167 described above with reference to Figure 1A the one or more contact intensity sensors 165 described above with reference to Figure 1A the one or more contact intensity sensors 165 described above with reference to Figure 1A the one or more contact intensity sensors 165 described above with reference to Figure 1A the one or more contact intensity sensors 165 described above with reference to

[0157] Figure 3Each of the above identified elements can optionally be stored on one or more of the aforementioned memory devices 370. Each of the above identified modules corresponds to a set of instructions for performing a certain task. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules can optionally be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0158] Attention is now directed towards embodiments of user interfaces that are optionally implemented on portable multifunction devices 100.

[0159] Figure 4A An exemplary user interface that shows a menu of applications on portable multifunction device 100 in accordance with some embodiments is illustrated. Similar user interfaces are optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0160] • One or more signal strength indicators 402 for one or more wireless communications, such as cellular signals and Wi-Fi signals;

[0161] • Time 404;

[0162] • Bluetooth indicator 405;

[0163] • Battery status indicator 406;

[0164] • Tray 408 with icons for frequently used applications, such as:

[0165] • Icon 416 for telephone module 138 that is labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemail messages;

[0166] • Icon 418 for email client module 140 that is labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

[0167] • Icon 420 for browser module 147 that is labeled "Browser"; and

[0168] • Icon 422 for video and music player module 152, also referred to as iPod (Apple Inc.'s trademark) module 152 that is labeled "iPod"; and

[0169] • Icons for other applications, such as:

[0170] Icon 424 of the οIM module 141, labeled "Message";

[0171] The icon 426 of the calendar module 148 is labeled "Calendar";

[0172] The icon 428 of the image management module 144 is labeled "photo";

[0173] The icon 430 of the camera module 143 is labeled "camera";

[0174] The icon 432 of the online video module 155 is labeled "Online Video";

[0175] The icon 434 in the Stock Market Desktop Mini Program 149-2 is labeled "Stock Market";

[0176] The icon 436 of the map module 154 is labeled "map";

[0177] The icon 438 in the Weather Desktop Mini Program 149-1 is marked as "Weather".

[0178] The icon labeled "Clock" in the alarm clock desktop mini-program 149-4 is 440;

[0179] The icon 442 of the fitness support module 142 is labeled "fitness support";

[0180] The notepad module 153 has an icon 444 labeled "Notepad"; and

[0181] An icon 446 labeled "Settings" is used to set the settings of an application or module, providing access to settings for the device 100 and its various applications 136.

[0182] It should be noted that Figure 4A The icon labels shown are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0183] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices such as tablets or touchpads (e.g., 355) Figure 3FIG. 1C shows an example user interface that is displayed on device 300). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more sensors 359 in FIG. 3) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of device 300.

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

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

[0186] Figure 5A ​​​​​​​​An example personal electronic device 500 is shown. The device 500 includes a body 502. In some embodiments, the device 500 can include some or all of the features described with respect to the devices 100 and 300 (e.g., Figure 1A-4B ) described above. In some embodiments, the device 500 has a touch-sensitive display 504, which is referred to hereafter as a touchscreen 504. The device 500 has a display and a touch-sensitive surface, alternatively or in addition to the touchscreen 504. As with the devices 100 and 300, in some embodiments, the touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors to detect intensity of contacts (e.g., touches) made with the touchscreen 504. The one or more intensity sensors of the touchscreen 504 (or touch-sensitive surface) can provide output data that is indicative of intensity of touches. User interfaces of the device 500 can respond to touches based on intensity of the touches, which means that touches of different intensities can invoke different user interface operations on the device 500.

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

[0188] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include a depressible button and a rotatable mechanism. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow the device 500 to be attached to, for example, a hat, glasses, earrings, a necklace, a shirt, a jacket, a bracelet, a watchband, a necklace, pants, a belt, shoes, a purse, a backpack, etc. These attachment mechanisms allow the user to wear the device 500.

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

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

[0191] Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage media that stores computer-executable instructions for execution by one or more computer processors 516, which, when executed, can cause the computer processors to perform the techniques described below, including processes 1000, 1300, and 1600 (FIGS. 10, Figure 13 and Figure 16 ). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, and Figure 5B In some examples, the storage media is a transitory computer-readable storage medium. In some examples, the storage media 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 storages. Examples of such storage include magnetic disks, optical disks based on CD, DVD, or Blu-ray technologies, and persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration described herein, but can include various configurations of other components or additional components not shown.

[0192] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 (Figure 1, ...). Figure 3 The user-interactive graphical user interface objects displayed on the screen (as shown in Figure 5). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0193] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of enabling direct interaction with user interface elements on the touchscreen display) Figure 1A The touch-sensitive display system 112 or Figure 4A In some embodiments of the touchscreen 112, the detected touch on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) 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, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user's expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0194] As used in the specification and claims, the term "feature strength" of a contact refers to a characteristic of the contact that is based on one or more strengths of the contact. In some embodiments, the feature strength is based on a plurality of strength samples. The feature strength is optionally based on a predefined number of strength samples or a set of strength samples that are acquired during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) with respect to a predefined event (e.g., after detecting the contact, before detecting liftoff of the contact, before or after detecting the contact starting to move, before detecting the end of the contact, before detecting an increase in strength of the contact, before detecting a decrease in strength of the contact, and / or the like). The feature strength of a contact is optionally based on one or more of: a maximum value of the strength of the contact, a mean value of the strength of the contact, a median value of the strength of the contact, a value at the 10th percentile of the strength of the contact, a half-maximum value of the strength of the contact, a 90th maximum value of the strength of the contact, and / or the like. In some embodiments, the duration of the contact is used in determining the feature strength (e.g., when the feature strength is a mean value of the strength of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact with a feature strength that does not exceed the first threshold results in a first operation, a contact with a feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact with a feature strength that exceeds the second threshold results in a third operation. In some embodiments, the comparison between the feature strength and the one or more thresholds is used to determine whether one or more operations are to be performed (e.g., whether to perform or forego performing a respective operation) rather than to determine whether to perform a first operation or a second operation.

[0195] Figure 5C Detection of multiple contacts 552A-552E on the touch-sensitive display 504 is shown using multiple intensity sensors 524A-524D. Figure 5C An intensity plot is additionally included, which shows the current intensity measurements of the intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some embodiments, each contact is assigned a respective intensity, which is a fraction of the cumulative intensity. Figure 5DThe cumulative intensities are shown assigned to the contacts 552A-552E based on their distance from the center of force 554. In this example, each of the contacts 552A, 552B, and 552E are assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of the contacts 552C and 552D are assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a fraction of the cumulative intensity A according to a predefined mathematical function Ij = A-(Dj / ∑Di), where Dj is the distance of the respective contact j from the center of force, and ∑Di is the sum of the distances of all respective contacts (e.g., i = 1 to last) from the center of force. The operations described with reference to FIGS. 5A-5D can be performed with an electronic device similar to or identical to the electronic device 100, 300, or 500. In some embodiments, the feature intensity of a contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single feature intensity (e.g., a single feature intensity of a single contact). It is noted that the intensity map is not part of the displayed user interface, but is included in the Figures 5C to 5D described for the purpose of helping the reader. Figures 5C to 5D

[0196] In some embodiments, a portion of a gesture is identified for use in determining a feature intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting location and reaches an ending location at which the contact intensity increases. In this example, the feature intensity of the contact at the ending location is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending location). In some embodiments, a smoothing algorithm is optionally applied to the intensities of the swipe contact prior to determining the feature intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for the purpose of determining the feature intensity.

[0197] The contact intensity on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or touchpad.

[0198] In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from an operation typically associated with clicking a button of a physical mouse or touchpad. ​

[0199] In some embodiments, when a contact of a feature intensity below the light press intensity threshold (e.g., and above the nominal contact detection intensity threshold, below which contacts are no longer detected) is detected, the device will move the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with the light press intensity threshold or the deep press intensity threshold. Generally, these intensity thresholds are consistent across different sets of user interface figures unless otherwise stated.

[0200] An increase in contact feature intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting liftoff of a 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.

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

[0202] Figures 5E to 5H Detection of a gesture is shown that includes an increase in intensity of contact 562 from an intensity below the light press intensity threshold (e.g., "IT Figure 5E ") to an intensity between the light press intensity threshold and the deep press intensity threshold (e.g., "IT L ") to an intensity above the deep press intensity threshold (e.g., "IT Figure 5H ") to an intensity below the deep press intensity threshold (e.g., "IT Dcorresponding to the intensity of the press input. While displaying the cursor 576 over the application icon 572B corresponding to application 2 on the displayed user interface 570 including the application icons 572A-572D displayed in the predefined area 574, a gesture performed with the contact 562 is detected on the touch- sensitive surface 560. In some embodiments, the gesture is detected on the touch- sensitive display 504. An intensity sensor detects the intensity of the contact on the touch- sensitive surface 560. The device determines that the intensity of the contact 562 peaks above a deep press intensity threshold (e.g., "IT D "). The contact 562 is maintained on the touch- sensitive surface 560. In response to detecting the gesture, and in accordance with the contact 562 having an intensity that rises above the deep press intensity threshold (e.g., "IT D ") during the gesture, a scaled down representation 578A-578C (e.g., thumbnails) of documents that were recently opened for application 2 are displayed, as shown in Figures 5F to 5H . In some embodiments, the intensity is a characteristic intensity of the contact as compared to one or more intensity thresholds. It should be noted that the intensity graph of the contact 562 is not part of the displayed user interface, but is included in Figures 5E to 5H to help the reader.

[0203] In some embodiments, the display of the representations 578A-578C includes an animation. For example, the representation 578A is initially displayed near the application icon 572B, as shown in Figure 5F . As the animation progresses, the representation 578A moves up and the representation 578B is displayed near the application icon 572B, as shown in Figure 5G . Then, the representation 578A moves up, 578B moves up toward the representation 578A, and the representation 578C is displayed near the application icon 572B, as shown in Figure 5H . The representations 578A-578C form an array above the icon 572B. In some embodiments, the animation progresses in accordance with the intensity of the contact 562, as shown in Figures 5F to 5G , where the representations 578A to 578C appear and move up as the intensity of the contact 562 increases toward the deep press intensity threshold (e.g., "IT D "). In some embodiments, the intensity in accordance with which the animation progresses is a characteristic intensity of the contact. The operations described with reference to Figures 5E to 5H may be performed with an electronic device similar to or identical to the device 100, 300, or 500.

[0204] In some embodiments, the device employs intensity hysteresis to avoid an unintended input sometimes referred to as "bouncing," in which the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in intensity of a respective contact above the press input intensity threshold and a subsequent decrease in intensity of that contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a respective operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity depending on the circumstances).

[0205] For ease of explanation, optionally, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input are triggered in response to detecting any of a variety of conditions: an increase in contact intensity above the press input intensity threshold, an increase in contact intensity from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in contact intensity below the press input intensity threshold, and / or a decrease in contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which an operation is described as being performed in response to detecting a decrease in intensity of a contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to and less than the press input intensity threshold.

[0206] 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 be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application with an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the operating system of the computer system.

[0207] As used herein, the term "open application" or "application in execution" refers to a software application that has state information retained (e.g., as part of the device / global internal state 157 and / or application internal state 192). An open or application in execution is optionally any of the following types of applications:

[0208] • an active application that is currently displayed on a display screen of a device on which the application is being used;

[0209] • a background application (or background process) that is not currently displayed but one or more processes of the application are being processed by one or more processors; and

[0210] • a suspended or hibernating application that is not running but has state information stored in memory (respectively, volatile and non-volatile) and available to resume execution of the application.

[0211] As used herein, the term "closed application" refers to a software application that does not have state information maintained (e.g., state information for the closed application is not stored in memory of the device). Thus, closing an application includes stopping and / or removing the application process of the application and removing state information of the application from memory of the device. Generally, opening a second application while in a first application does not close the first application. The first application becomes a background application when the second application is displayed and the first application stops being displayed.

[0212] Attention is now directed to embodiments of user interfaces ("UIs") and associated processes implemented on electronic devices, such as portable multifunctional device 100, device 300, device 500, device 600, or device 900.

[0213] Figures 6A to 9I Exemplary user interfaces for displaying application views in an application view group are shown in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 10.

[0214] Figure 6A Device 600 has a touch-sensitive display 602. In some embodiments, device 600 can be device 100, 300, or 500. A user interface 604 is displayed on touch-sensitive display 602. User interface 604 includes a watch face application's watch face 608, as shown. Figure 6A

[0215] Device 600 includes various input mechanisms that receive user input, such as a rotatable input mechanism 610 that is capable of receiving rotatable input (and can also receive push input), and an input mechanism 612 that is capable of receiving push user input.

[0216] Reference is now made to Figures 6A to 6C ​In response to receiving user input 614 at input mechanism 612, multiple application views of application view group 630 are displayed. The application view group is an ordered list of application views corresponding to a specific application. Figures 6B to 6C As shown, in some embodiments, the application view group 630 includes a first application view 631 corresponding to a first application (e.g., a friends application), a second application view 632 corresponding to a second application (e.g., a stock application, a weather application), a third application view 633 corresponding to a third application, a fourth application view 634 corresponding to a fourth application, and a fifth application view 635 corresponding to a fifth application. It should be noted that, as... Figures 6A to 6C As shown, the application view group may include one or more application views that are not displayed on the display 602 at a given time.

[0217] In some implementation schemes, see Figures 6A to 6B In response to user input 614, device 600 displays subgroups of the application view group, such as a first application view 631 and a second application view 632. Alternatively, in some embodiments, see [link to relevant documentation]. Figure 6A and Figure 6C In response to user input 614, device 600 displays subgroups of the application view group, such as application view 633, application view 634 and application view 635.

[0218] like Figures 6A to 6C As shown, the application view is a screenshot of the corresponding application. Each application view in the application view group 630 is a display representation of the application corresponding to that application view that is selected. For example, selecting application view 631 corresponding to the Friends application (e.g., touch input on the display) launches the Friends application. Similarly, selecting application view 634 corresponding to the Music application launches the Music application.

[0219] In some implementations, applications corresponding to the application view groups 630 (e.g., pre-selected application views and adaptive application views) are stored in memory (e.g., volatile memory). Therefore, in response to the selection of a corresponding application view, the application corresponding to that application view in the application view group 630 is quickly and easily accessed (e.g., launched instantly).

[0220] In some implementations, device 600 displays various application view markers (or page points) 640 simultaneously with the application view group. Each application view marker corresponds to a specific application view in the application view group. For example, application view marker 641 corresponds to application view 631, and application view marker 642 corresponds to application 632 (e.g., ...). Figure 6B As shown), and application view markers 643, 644, and 645 respectively correspond to application views 633, 634, and 635 in the application view group (as shown). Figure 6C As shown). Figures 6B to 6C As shown, five individual application view tags (e.g., application view tags 641, 642, 643, 644, and 645) correspond to five individual application views in the application view group 630, respectively. However, the application view group 630 may include any number of predefined application views corresponding to the corresponding number of application view tags (e.g., ten predefined application views in the application view group).

[0221] The application view group 630 includes pre-selected application views. A pre-selected application view is an application view corresponding to a specific application, wherein the application has been pre-selected such that its corresponding application view is displayed in response to user input 614. Therefore, the application view group 630 provides quick and convenient access to applications corresponding to the application views in the application view group 630. In one example, application views 631-634 are pre-selected application views because they have been definitively selected as part of the application view group 630. In some embodiments, the user of device 600 definitively selects an application (or application view) as part of the application view group 630, which will be described in further detail below. In other embodiments, a party other than the user selects one or more applications (or application views) before the device is shipped for commercial sale or before the user's initial use.

[0222] In some embodiments, the preselected application views (and the adaptive application view) remain in the application view group regardless of the operational state of the respective application. The various operational states of an application can be an application that is launched (e.g., made open), an application that is open or executing, or an application that is closed. In particular, an application that is open or executing can be, but is not limited to, (1) an active application that is currently displayed on a display screen of a device on which the application is being used, (2) a background application (or background process) that is not currently displayed, but one or more processes of the application are being processed by one or more processors, and (3) a suspended or hibernating application that is not running, but has state information stored in memory (respectively, volatile and non-volatile) that can be used to resume execution of the application.

[0223] Thus, in some embodiments, the preselected application views can be displayed regardless of the operational state of the application. Moreover, in some embodiments, the preselected application views remain in the application view group until affirmatively removed by the user, which is described in further detail below.

[0224] As shown, the application view group 630 also includes an adaptive application view 635. The adaptive application view corresponds to a most recently opened application that is not one of the preselected application views. The adaptive application view includes a screenshot of the most recently opened application regardless of the operational state of the most recently opened application (e.g., running, suspended, not launched). Figure 6D

[0225] Referring back to FIG. 6B, the application view 635 is an adaptive application view corresponding to the Stocks application. In this example, the Stocks application is the most recently opened application, and the Stocks application has not been affirmatively added to the preselected application views (e.g., application views 631-634) of the application view group 630. Figure 6D

[0226] In some embodiments, the Stocks application is an open application on the device, and is not a view in the application view group. During the Stocks application is open (and displayed in the user interface 604), the device 600 receives the user input 614 received for displaying the application view group. In response to receiving the user input 614, the device 600 displays the adaptive application view corresponding to the Stocks application because the Stocks application is the most recently opened application.

[0227] ​​In some embodiments, device 600 displays an adaptive application view at the terminal (e.g., beginning or end) of the sequence of the set of application views. Alternatively, an adaptive application view is not displayed at the terminal of the sequence of application views. In some embodiments, the set of application views includes more than one adaptive application view that respectively correspond to the most recently opened application.

[0228] In some embodiments, referring to Figure 6D application views 634 and 635 of the set of application views 630, the set of application view icons 640 are displayed, where each of the application view icons corresponds to a respective application view of the set of application views. In particular, the application view icon 645 corresponding to the adaptive view 635 is visually distinguished from the application view icons corresponding to the preselected application views. In Figure 6D the illustrated embodiment, when the adaptive application view 635 is centered, the application view icon 645 is a hollow icon (in a highlighted state). In contrast, the application view icons corresponding to the preselected application views are highlighted as solid page dots when their respective preselected application views are centered, as illustrated, for example, in Figure 6B .

[0229] Further as illustrated in Figure 6D application view 635 includes an affordance 639 ("Add to Dock" button) that corresponds to adding the adaptive view to the preselected application views of the set of application views. In response to receiving user input 649 (e.g., a tap gesture) to select the affordance, an adaptive application view (e.g., application view 635) corresponding to the most recently opened application (e.g., the Stocks application) is added to the preselected application views. For example, referring to Figure 6E application view 635 to the preselected application views of the set of application views such that application view 635 is no longer an adaptive application view. In some embodiments, when an adaptive application view (e.g., the Stocks application) is added to the preselected application views via selection of affordance 639, the adaptive application view remains in the set of application views and a new preselected application view (e.g., the Stocks application) is created.

[0230] In some embodiments, the adaptive application view adjustment is such that it corresponds to the most recently opened application that is not one of the preselected application views that already exist. For example, when the stocks application is launched, it is the most recently opened application. Accordingly, the adaptive application view corresponds to the stocks application, as shown in Figure 6D

[0231] Further, a subsequent new application can be launched (or opened) that is not associated with a preselected application view. In response to detecting the launch of a new application that is not associated with a preselected application view, the adaptive view is again updated to correspond to the new most recently opened application. For example, see Figure 6F When the weather application is the most recently opened application (and is not associated with a preselected application view), the device 600 updates the adaptive application view 635 so that it corresponds to the weather application (rather than the previously most recently opened application such as the stocks application). In some embodiments, the adaptive application view allows the user to quickly access the most recently used application without having to perform the steps necessary to add that application to the preselected application view group.

[0232] In some embodiments, the application view of the most recently opened application is centered focused when the display of the application view is elicited. For example, see Figure 6C In response to user input at the input mechanism 612, the device 600 displays a subset of the group of application views. Specifically, the device 600 displays a portion of the preselected application view 633, the full view of the preselected application view 634, and a portion of the adaptive application view 635. The full view of the preselected application view 634 corresponding to the music application is displayed in full and centered because the music application corresponding to the preselected application view 634 is the most recently opened application.

[0233] Additionally, in some embodiments, the centered focused application view is more brightly illuminated than the one or more application views adjacent to it. For example, the application view 634 is more brightly illuminated than the sequentially adjacent views 633 and 635 that are displayed in part. Specifically, in some embodiments, the one or more views sequentially adjacent to the centered focused application view are dimmed relative to the centered focused application view.

[0234] As another example, see Figure 6F ​In response to user input at input mechanism 612, a subset of the application view group is displayed. Specifically, a portion of the preselected application view 634 and the full view of the adaptive application view 635 are displayed. The full view of the adaptive application view 635 corresponding to the weather application is displayed in its entirety and centered because the weather application corresponding to the adaptive application view 635 is the most recently opened application (and is not associated with a pre-view).

[0235] Referring to Figures 6F to 6G The weather application associated with the adaptive application view 635 can be opened in response to selecting the adaptive application view. For example, while the weather application associated with the adaptive view is not open, the device 600 receives user input 650 on the adaptive application view. In response to receiving the user input 650, the device 600 launches (or opens) the weather application, as shown in Figure 6G

[0236] Figures 6H to 6K The reordering of the application views in the application view group 630 is shown. Referring to Figure 6H (as similar to Figure 6C As described above, the device 600 receives user input 652 (e.g., a force press) on the preselected application view 634 corresponding to the music application. The user input 652 is to select and reorder the preselected application view in the sequence of application views in the application view group.

[0237] Referring to Figure 6I In response to the user input 652, the device 600 visually distinguishes the selected preselected view 634 corresponding to the music application from the other views in the application view group. The visual distinction of the selected application view can include a change in size (e.g., larger than the other application views), a change in location (e.g., vertically offset relative to the other application views), a change to be semi-transparent, a change to be darkened, and the like. In some embodiments, the device 600 reduces the size of each of the displayed application views in response to the user input 652 so that more application views can be displayed simultaneously to assist in reordering the selected application view.

[0238] In some embodiments, a textual index 655 is displayed in association with the selected application view. The textual index 655 indicates the current order of the selected application view in the sequence of the application view group (e.g., 4th of 5).

[0239] Referring to Figure 6J ​In response to detecting user input 652 movement (e.g., a swipe left) to a new position in the sequence of application views, the selected application view 634 is translated to the new position in the sequence of application views in accordance with the detected user input 652 movement. As shown in Figure 6J FIG. 6B, device 600 translates the selected application view to a new position between application view 631 and application view 632 in the sequence of application views 630. As indicated by text reference 655, in response to the movement of user input 652, the selected application view is translated to a new position in the sequence of application views (e.g., 2nd of 5).

[0240] Referring to Figure 6K In response to the break in contact of user input 652, device 600 places the selected application view 634 between application views 631 and 632 such that the selected application view 634 is reordered in the sequence of application views. In particular, application view 634 is reordered from the fourth application view to the second application view in the sequence of application views. In addition, application views move to make room for the newly reordered application view. For example, device 600 moves application view 631 leftward and / or application views 632 and 633 rightward to provide room for application view 634 to be reordered to its new position between application view 631 and application view 632.

[0241] It is contemplated that the techniques for reordering shown and described with reference to Figures 6H to 6K FIG. 6B can be applied to reorder other items. For example, such techniques can be used to reorder context-specific user interfaces or watch faces configured for display on device 600. Exemplary user interfaces and techniques for editing and / or selecting the same are provided in International Patent Application Serial No. PCT / US2015 / 034607, entitled "Context-Specific User Interfaces," published as WIPO Pub. No. WO / 2016 / 022205, filed June 7, 2015, which is incorporated by reference herein in its entirety. In this example, Figures 6H to 6KA mode for reordering a sequence of saved user interfaces for display on device 600 is shown. The reordering mode of device 600 can be entered, for example, by a touch gesture on the touch-sensitive display such as a force press or long press. 633, 634, 635 depict preview images representing user interfaces in the sequence that are specific to the context of the library. In some embodiments, preview image 634 represents the active user interface, e.g., the user interface that was displayed on device 600 prior to entering the reordering mode, which is visually distinguished on the display as described above. In response to detecting user input 652 moving (e.g., swiping left) to a new position in the sequence of user interface preview images, the selected preview image 634 is translated to the new position in the sequence of application view groups according to the movement of the detected user input 652 (e.g., as shown in Figure 6J In some embodiments, the stored user interface library is also reordered accordingly, e.g., such that the user interface represented by preview image 634 is reordered to position 2 of 5 user interfaces in the library, between the user interfaces represented by preview images 631 and 632. In other embodiments, rather than showing the translation of 634 under the sequence of user interface preview images (with other images of the sequence arranged in a linear sequence behind and / or above 634), device 600 enlarges the display of preview image 634 more than 633 and 635, and increases the transparency of 634, such that the user can perceive preview image 634 as well as the sequence of other preview images behind it on the display. In response to detecting user input 652 moving (e.g., swiping left) to a new position in the sequence of user interface preview images, the sequence of preview images translates behind the enlarged and transparent 634 such that it occupies position 2 of 5 as shown in Figure 6J and then 634 returns to its previous size and transparency after the user input stops.

[0242] Figures 6L to 6N An application view is shown being removed from application view group 630. Referring to Figure 6L , device 600 detects user input 653 (e.g., an upward swipe gesture) on application view 634 corresponding to the music application. In response to user input 653 corresponding to removing an application view from application view group 630, device 600 displays an application view removal user interface 656 Figure 6M ). Application view removal user interface 656 includes an application view removal affordance 657 and a cancel affordance 658. Application view removal affordance 657, when selected, removes or deletes the selected application view (e.g., application view 634) from application view group 630. Cancel affordance 658 cancels the process of removing the application view (e.g., application view 634) from the application view group.

[0243] Referring Figure 6N In response to selecting the application view removal affordance 657, the device 600 removes the selected application view 634 (which is currently in the second application view in the application view group 630) from the application view group.

[0244] In addition, the application views are moved to close the space left by the removed application view. For example, the device 600 moves the application view 631 to the right and / or moves the application view 632 (and the rest of the application views of the sequence of the application view group 630) to the left to close the idle space that once held the removed application view.

[0245] As a result of removing the application view, the application view group 630 (from five application views) is reduced to four application views, as shown in Figures 6L to 6N Similarly, the number of application view labels (or page dots) 640 (from five labels) is reduced to four labels, which respectively correspond to each of the application views in the application view group.

[0246] Figures 7A to 7D Scrolling through the application view group is shown. Referring to Figure 7A During the time that the application view 631 is the focused and centered application view in the application view group 630, a swipe gesture 710 is received for scrolling through the application view group 630. In response to receiving the swipe gesture 710, the device 600 scrolls the application views (from the application view 631) to the adjacent application view 632 in accordance with the swipe gesture’s speed being below a predetermined speed, as shown in Figure 7B

[0247] ​Alternatively, in response to receiving the swipe gesture 710, the application view scrolls through the plurality of application views (from the application view 631) according to a speed of the swipe gesture being above a predetermined speed (e.g., 1 m / s), for example, to the adaptive application view 635. In particular, the greater the speed of the swipe gesture (above the predetermined speed), the further the scroll through the application views. For example, during the application view 631 being the centered and focused application view, the device 600 can scroll to the application view 633 when the swipe gesture 710 has a first speed VI that is slightly above the predetermined threshold. Similarly, during the application view 631 being the centered and focused application view, the device 600 can scroll to the application view 634 when the swipe gesture 710 has a second speed V2 that is greater than VI. Similarly, during the application view 631 being the centered and focused application view, the device 600 can scroll (from the application view 631) to the adaptive application view 635 when the swipe gesture 710 has a third speed V3 that is greater than V2.

[0248] Referring now to Figure 7D During the application view 631 being the focused and centered application view in the application view group 630, a rotational input 712 to scroll to an adjacent application view is received at the rotatable input mechanism 610. In response to receiving the rotational input 712 at the rotatable input mechanism 610, the application view scrolls (from the application view 631) to the adjacent application view 632, as shown in Figure 7B In some embodiments, the scrolling to the adjacent application view includes a speed reduction based on a predetermined coefficient of friction. For example, the speed of the scroll from the application view 631 to the application view 632 is slowed until the application view 632 is the new focused and centered application view, where the speed of the scroll is slowed based on the coefficient of friction.

[0249] Figures 7E to 7I Scrolling through the application view group 630 is shown. Referring to Figure 7E During the display of the application views 631 and 632 in the display area (e.g., the user interface 604), the device 600 receives an input 714 (e.g., a press-and-hold gesture) at an edge 715 of the display area (e.g., near the bottom edge of the user interface 604, or near the bottom bezel 716 of the touch display screen). Referring to Figure 7FIn response to receiving input 714, device 600 moves the displayed application views away from edge 715 of the display area 715. In this example, the application views are translated upward and toward the top edge of the display area opposite the bottom edge 715. In some embodiments, the application views are moved away from edge 715 to provide sufficient area for a user's finger to touch the bottom edge. Thus, the user is able to touch on or around edge 715 without visually obstructing the displayed application views.

[0250] Referring to Figures 7F to 7I , movement of input 714 along edge 715 is detected (e.g., a rightward horizontal scroll gesture). In response to detecting movement of the input along the bottom edge of the display area, the set of application views is scrolled. For example, referring to Figure 7G , as input 714 is detected toward the center of the length of edge 715, device 600 displays application views in the middle of the sequence of the set of application views (e.g., application views 632, 634, and 635). Similarly, referring to Figure 7H , as input is detected toward the end of the length of edge 715, device 600 displays application views at the end of the sequence of the set of application views (e.g., application views 634 and 635). In some embodiments, see Figure 7I , in response to the interruption of input 714, device moves the application views back down toward edge 715 to their original position (prior to input 714).

[0251] In some embodiments, in response to a touch from one end of edge 715 to the opposite end of edge 715, the user can scroll through each of the application views regardless of the number of application views in the set of application views. Additionally, the initial position of input 714 can be any position along the length of edge 715. For example, the initial position of input 714 can be toward the middle of the length of edge 715, as shown in Figure 7G .

[0252] Figures 7J to 7L Dynamic highlighting of application view icon 640 is shown. The dynamic highlighting of the application view icon corresponds to scrolling from application view 631 (corresponding to application view icon 641) to application view 632 (corresponding to application view icon 641), as shown in Figures 7L to 7J , such as described with reference to Figures 7A to 7B .

[0253] See Figure 7J (and Figure 7A), a set of application view indicia 640 are displayed, where each of the application view indicia (e.g., indicia 641-645) corresponds to a respective application view in the set of application views 630. Indium 641, which corresponds to the displayed application view 631 that is centered in focus, is highlighted. In response to receiving a user input (e.g., a scroll input) to scroll to an adjacent application view 632 such that application view 632 is centered in focus, application view indicium 642 is highlighted to indicate that application view 632 is the application view that is centered in focus. The highlighting of application view indicium 642 includes an initial brightness and a final highlight brightness, where the brightness of the highlight increases during a transition from the initial highlight brightness to the final highlight brightness. See Figure 7K At the time that application view 642 initially transitions into the centered in focus position, indicium 642 includes an initial brightness. See Figure 7L Indium 642 includes a transition to a final highlight brightness that is greater than the initial highlight brightness, as shown in Figure 7K In some embodiments, the dynamic highlighting works as if a backlight moves between the indicia (e.g., the backlight moves from indicium 641 to 642).

[0254] Figures 8A to 8B A generic audio application control interface is shown. See Figure 8A When an audio application is playing audio content (e.g., a third-party music application is playing a song), device 600 updates the set of application views 630 with a generic audio application control interface view 636 that corresponds to a generic audio application control interface for controlling playback of the currently playing audio content. When the set of application views 630 does not correspond to an audio application that is currently playing audio content, the set of application views 630 is updated with the generic audio application control interface view 636. For example, the audio application that is playing the audio content is not a preselected application view in the set of application views.

[0255] The audio application that is playing the audio content includes an application-specific control interface that is specific to that audio application for controlling audio playback. The generic audio application control interface is different and distinct from the application-specific control interface. For example, the generic audio application control interface is able to control playback of various third-party music applications (e.g., Pandora, Spotify, SoundCloud) that are not associated with a preselected application view.

[0256] User input 810 on the universal audio application control interface view 635 is received. The user input 810 is for initiating the universal audio application control interface.

[0257] Referring to Figure 8B , in response to receiving the user input 810, the device 600 initiates and displays the universal audio application control interface. Thus, the audio content that is currently being played by the audio application can be controlled via the universal audio application control interface, rather than an application-specific control interface.

[0258] Referring now to Figure 8A and Figure 8C , the universal audio application control interface view 636 includes an affordance 639 for adding the universal audio application control interface view 636 to the preselected application view. In response to user input 812 for adding the universal audio application control interface view 636 to the preselected application view, the device 600 positively adds the universal audio application control interface view 636 to the preselected application view, as shown in Figure 8C .

[0259] Figures 9A to 9I A companion device 900 paired with the device 600 is shown. The companion device 900 includes a touch-sensitive display 902. A user interface 904 is displayed on the touch-sensitive display 902. The companion device 900, when paired with the device 600, can display application views and perform at least some of the same processes as the device 600, as described herein.

[0260] Referring to Figures 9A to 9B , application views can be added to the application view group 630 via the companion device 900 in the same manner described with respect to the device 600, as described herein.

[0261] Referring to Figure 9A , at the companion device 900, the adaptive application view (e.g., application view 635) includes an affordance 639 (e.g., an “Add to Dock” button) corresponding to adding the adaptive view to the preselected application view of the application view group. In response to receiving user input 649 (e.g., a tap gesture) for selecting the affordance, the adaptive application view (e.g., application view 635) corresponding to the most recently opened application (e.g., the Stocks application) is added to the preselected application view of the application view group. For example, referring to Figure 9B , in response to the user input 649, the device 900 adds the application view 635 to the preselected application view of the application view group and is no longer an adaptive application view.

[0262] Referring to Figures 9C to 9FThe application views can be reordered via the companion device 900 in the same manner as described with respect to device 600, as described herein.

[0263] Figures 9C to 9F Reordering of the application views in the application view group 630 via the companion device 900 is shown (similar to the reordering shown in Figures 6H to 6K . Referring to Figure 9C , a user input 652 (e.g., a force press) is received on the preselected application view 634 corresponding to the music application. The user input 652 is for selecting and reordering the preselected application view in the sequence of application views in the application view group.

[0264] Referring to Figure 9D , in response to the user input 652, the device 900 visually distinguishes the selected preselected view 634 corresponding to the music application from the other views in the application view group. The visual distinction of the selected application view can include a change in size (e.g., larger than the other application views), a change in position (e.g., vertically offset relative to the other application views), a change to be translucent, a change to be darkened, and the like. In some embodiments, each of the displayed application views is reduced in size in response to the user input 652, such that more application views can be displayed simultaneously to assist in reordering the selected application view.

[0265] In some embodiments, a text cue 655 is displayed in association with the selected application view. The text cue 655 indicates the current order of the selected application view in the sequence of the application view group (e.g., 4th of 5).

[0266] Referring to Figure 9E , in response to detecting the user input 652 moving (e.g., swiping left) to a new position in the sequence of the application view group, the device 900 translates the selected application view 634 according to the detected user input 652 moving to the new position in the sequence of the application view group. As shown in Figure 9E , the selected application view is translated to a new position in the application view group 630 between the application view 631 and the application view 632. As indicated by the text cue 655, the selected application view is translated to a new position in the sequence of the application view group (e.g., 2nd of 5) in response to the movement of the user input 652.

[0267] Referring to Figure 9FIn response to the interruption of the contact of user input 652, device 900 places the selected application view 634 between application views 631 and 632 such that the selected application view 634 is reordered in the sequence of the group of application views. In particular, application view 634 is reordered in the sequence of the group of application views (from the fourth application view) to the second application view. In addition, the application views move to make room for the newly reordered application view. For example, device 900 moves application view 631 to the left and / or moves application views 632 and 633 to the right to provide room for application view 634 to be reordered to its new position between application view 631 and application view 632.

[0268] Figures 9G to 9I application views from the group of application views 630 via companion device 900 (similar to Figures 6L to 6N Referring to Figure 9G A user input 653 (e.g., an upward swipe gesture) is detected on application view 634 corresponding to the music application. User input 653 (e.g., the upward swipe gesture) is for removing an application view from the group of application views.

[0269] Referring to Figure 9H In response to user input 653 corresponding to removing an application view from the group of application views 630, an application view removal user interface 656 is displayed. Application view removal user interface 656 includes an application view removal affordance 657 and a cancel affordance 658. Application view removal affordance 657, when selected, removes or deletes the selected application view (e.g., application view 634) from the group of application views 630. Cancel affordance 658 cancels the selection of the application view (e.g., application view 634) for deletion from the group of application views.

[0270] Referring to Figure 9I In response to the selection of application view removal affordance 657, the selected application view 634 (which is currently in the second application view in the group of application views 630) is removed from the group of application views.

[0271] In addition, the application views move to close the space left by the removed application view. For example, application view 631 moves to the right and / or application view 632 (and the remaining application views of the sequence of the group of application views 630) move to the left to close the free space that once held the removed application view.

[0272] As a result of removing the application view, as Figures 9G to 9I As shown, the set of application views 630 (from five application views) is reduced to four application views. Similarly, the number of application view indicia (or page dots) 640 (from five indicia) is reduced to four indicia, which respectively correspond to each of the application views in the set of application views.

[0273] FIG. 10 is a flow diagram illustrating a method for displaying application views in a set of application views with an electronic device in accordance with some embodiments. The method 1000 is performed at a device (e.g., 100, 300, 500, 600, or 900) with a display, one or more processors, and memory. Some operations in method 1000 are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted.

[0274] As described below, method 1000 provides an intuitive way for displaying application views in a set of application views. This method reduces the cognitive burden on a user for viewing application views in a set of application views, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to view application views in a set of application views faster and more efficiently conserves power and increases the time between battery charges.

[0275] At block 1002, a user input (e.g., user input 614) is received at the device, which, when received, initiates display of a plurality of application views of a set of application views.

[0276] At block 1004, in response to receiving the user input, a plurality of application views of a set of application views (e.g., set of application views 630) are displayed (e.g., Figure 6B ). The set of application views includes a preselected application view and an adaptive view that does not correspond to one of the preselected application views and that corresponds to a most recently opened application.

[0277] In some embodiments, as Figure 6E shown, the adaptive view (e.g., adaptive view 635) that corresponds to the most recently opened application is displayed, where the adaptive view includes an affordance (e.g., affordance 639) for adding the adaptive view to the preselected application views (1010). A user input (e.g., input 649) corresponding to a selection of the affordance is received (1012). In response to receiving the user input for selecting the affordance, the adaptive view that corresponds to the most recently opened application is added to the preselected application views (1014).

[0278] In some embodiments, as Figure 6DAs shown, the application view group is displayed in a sequence, and the adaptive view is displayed at a terminal of the sequence of the application view group (1006).

[0279] In some embodiments, as Figure 6E As shown, user input (e.g., user input 614) is received while displaying an open application that is not one of the preselected application views that was most recently opened (1015), and further in response to receiving the user input, an adaptive view that is not one of the preselected application views that corresponds to the most recently opened application is displayed (1016). The adaptive view includes an affordance (e.g., affordance 639) to add the adaptive view to the preselected application views. User input (e.g., input 649) corresponding to a selection of the affordance is received (1017). In response to receiving the user input to select the affordance, the adaptive view that corresponds to the most recently opened application is added to the preselected application views (1018).

[0280] In some embodiments, as Figure 6F As shown, a launch of an application is detected, where the adaptive view and the preselected application views of the application view group do not correspond to the launched application (1020). In response to detecting the launch of the application, the adaptive view corresponding to the launched application is updated (1021).

[0281] In some embodiments, as Figure 6H As shown, the application view group is displayed in a sequence. In response to receiving user input corresponding to a display of the sequence of the application view group, a subset of application views (e.g., application views 633, 634, and 635) of the sequence of the application view group is displayed. The display of the subset of application views includes displaying an application view of a most recently opened application at a center of the sequence of the subset of application views (1005).

[0282] In some embodiments, as Figure 6HAs shown, a sequence of application view groups is displayed (1002). A user input corresponding to display of a sequence of application view groups is received (1003), and in response to receiving the user input corresponding to display of a sequence of application view groups, a sequence of application views of the application view group is displayed (1004). The display of the sequence of application views includes displaying a first application view in the sequence of application views in the center of the sequence of application views (e.g., application view 634), and displaying at least a partial view of a second application view in the sequence of application views that is sequential to the first application view (e.g., application view 633 or 635), where the second application view is dimmed relative to the first application view (1006).

[0283] In some embodiments, as shown, a sequence of application view groups is displayed (1025). As shown, an input on an application view in a first position in the sequence of application view groups is received (1026). As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031). Figure 6G As shown, an adaptive view is displayed when an application associated with the adaptive view is not open (1022). A user input corresponding to the adaptive view is received (1023), and in response to receiving the user input corresponding to the adaptive view, the associated application is launched (1024).

[0284] In some embodiments, as shown, a sequence of application view groups is displayed (1025). As shown, an input on an application view in a first position in the sequence of application view groups is received (1026). As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031). Figure 6H As shown, an adaptive view is displayed when an application associated with the adaptive view is not open (1022). A user input corresponding to the adaptive view is received (1023), and in response to receiving the user input corresponding to the adaptive view, the associated application is launched (1024). Figure 6I As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031). Figure 6J As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031). Figure 6J As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031).

[0285] In some embodiments, as shown, a sequence of application view groups is displayed (1025). As shown, an input on an application view in a first position in the sequence of application view groups is received (1026). As shown, in response to the input on the application view, the selected application view is visually distinguished from other application views in the sequence of application view groups (1027). A movement of the input on the application view to a second position in the sequence of application view groups is detected (1028). As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1029). As shown, a discontinuation of the input on the application view is detected, and in response to the detected discontinuation of the input on the application view, the application view is reordered to the second position in the sequence of application view groups (1031). Figure 6L As shown, an input on an application view of the plurality of application views is received, and the input, when received, initiates deletion of the application view from the application view group (1032). As shown, in response to the input on the application view, the application view is deleted from the application view group (1033). Figures 6M to 6N As shown, an input on an application view of the plurality of application views is received, and the input, when received, initiates deletion of the application view from the application view group (1032). As shown, in response to the input on the application view, the application view is deleted from the application view group (1033).

[0286] In some embodiments, as shown Figure 7A a swipe gesture is received for scrolling through the set of application views (1034). As shown Figures 7B to 7C In response to receiving the swipe gesture: in accordance with a speed of the swipe gesture being below a predetermined speed threshold, scrolling to an adjacent application view, and in accordance with the speed of the swipe gesture being above the predetermined speed threshold, scrolling through a plurality of application views of the set of application views (1035).

[0287] In some embodiments, as shown Figure 7D a user input is received, the user input, when received, initiating scrolling to an adjacent application view in the set of application views (1036). As shown Figure 7E In response to receiving the user input, scrolling to the adjacent application view in the set of application views, wherein the scrolling to the adjacent application view includes a speed reduction based on a predetermined coefficient of friction (1037).

[0288] In some embodiments, as shown Figure 7E While displaying the plurality of application views in the display area, an input at a bottom edge of the display area is received, the input, when received, initiating scrolling of an application view (1038). As shown Figure 7F In response to the input at the edge of the display area, moving the application view away from the bottom edge of the display area (1039). As shown Figure 7G Detecting movement of the input along the bottom edge of the display area (1040). As shown Figures 7G to 7H In response to the detected movement of the input along the bottom edge of the display area, scrolling through the set of application views (1041).

[0289] In some embodiments, as shown Figure 6F While displaying the plurality of application views of the set of application views, a set of application view icons (e.g., icons 640) is displayed. Each of the application view icons corresponds to a respective application view in the set of application views. An application view icon corresponding to an adaptive view is visually distinguished from application view icons corresponding to preselected application views (1042).

[0290] In some embodiments, as shown Figure 7J During display of the plurality of application views of the set of application views, a set of application view icons is displayed, wherein each of the application view icons corresponds to a respective application view in the set of application views (1043). As shown Figure 7JAs shown, a badge corresponding to the displayed application view is highlighted (1044). A user input is received, the user input, when received, to scroll to another application view in the group of application views (1045). In response to receiving the user input, the other application view is scrolled to (1046). As shown, Figures 7K to 7L As shown, in accordance with scrolling to the other application view, the application view badge corresponding to the other application view is highlighted, where the highlighting corresponding to the other application view includes an initial highlight intensity and a final highlight intensity, where the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity (1047).

[0291] In some embodiments, while an audio application is playing audio content, where the audio application includes an application-specific control interface and the group of application views does not include an application view corresponding to the audio application (1046): As shown, Figure 8A As shown, the group of application views is updated with a universal audio application control interface view corresponding to a universal audio application control interface, where the universal audio application control interface is different from the application-specific control interface that is not part of the taskbar (1047). A user input on the universal audio application control interface view is received (e.g., input 810), the user input, when received, initiates launching the universal audio application control interface (1048). As shown, Figure 8B As shown, in response to receiving the user input, the universal audio application control interface for controlling playback of the audio content playing on the audio application is displayed (1049).

[0292] In some embodiments, as shown, Figure 8A As shown, where the universal audio application control interface view includes an affordance corresponding to adding the universal audio application control interface view to the group of application views (1050). As shown, Figure 8C As shown, a user input to select the affordance is received (1051), and in response to receiving the user input to select the affordance, the universal audio application control interface view is added to the group of application views (1052).

[0293] In some embodiments, as shown, Figure 9A As shown, at a companion device (e.g., device 900) having one or more processors and memory paired with the device (e.g., device 600), an adaptive view corresponding to a most recently opened application is displayed, where the adaptive view includes an affordance corresponding to adding the adaptive view to a preselected application view (1053). As shown, Figure 9BAs shown, user input to select the affordance is received (1054), and in response to receiving user input to select the affordance, an adaptive view corresponding to the most recently opened application is added to the preselected application view (1055).

[0294] In some embodiments, as Figure 9C As shown, at a companion device (e.g., device 900) having one or more processors, a touchscreen, and memory paired with the device (e.g., device 600), a portion of the sequence of application view groups is displayed (1056). Input is received at a location on the touchscreen of an application view in a first position in the sequence of application view groups (1057). As Figure 9D As shown, in response to the input, the selected application view is visually distinguished from other application views in the sequence of application view groups (1058). The input on the application view is detected moving to a second position in the sequence of application view groups without interruption of contact with the touchscreen (1059). As Figure 9E As shown, in response to the detected movement of the input on the application view, the selected application view is moved to the second position in the sequence of application view groups (1060). As Figure 9F As shown, the interruption of the input with the touchscreen is detected, and in response to the detected interruption of the input with the touchscreen, the application view is reordered to the second position in the sequence of application view groups (1062).

[0295] In some embodiments, as Figure 9G As shown, at a companion device (e.g., device 900) of the device (e.g., device 600), where the companion device paired with the device includes one or more processors and memory, input is received on an application view of the plurality of application views, the input when received causes the application view to be deleted from the application view group (1063). As Figure 9I As shown, in response to the input on the application view, the application view is deleted from the application view group (1064).

[0296] It should be noted that details of the processes described above in reference to method 1000 (e.g., FIG. 10) are also applicable in an analogous manner to the methods described below. For example, method 1300 optionally includes one or more of the characteristics of the various methods described above with reference to method 1000. For example, method 1300 includes updating application views, which can optionally be implemented in method 1000. For the sake of brevity, these details are not repeated below.

[0297] According to some embodiments, Figure 11 An exemplary functional block diagram of an electronic device 1100 configured according to the principles of various embodiments is shown. According to some embodiments, functional blocks of the electronic device 1100 are configured to perform the techniques described above. The functional blocks of the device 1100 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various examples described. Those skilled in the art will understand that... Figure 11 The functional blocks described herein may be optionally combined or separated into sub-blocks to implement the principles of the various instances described herein. Therefore, the description herein may optionally support any possible combination or separation or further limitation of the functional blocks described herein.

[0298] like Figure 11 As shown, the electronic device 1100 includes a display unit 1102 configured to display a graphical user interface, a touch-sensitive surface unit 1104 optionally configured to receive contact, and a processing unit 1106 coupled to the display unit 1102 and the optional touch-sensitive surface unit 1104. In some embodiments, the processing unit 1106 includes a receiving unit 1110, an adding unit 1112, an updating unit 1114, a reordering unit 1116, a deleting unit 1118, a scrolling unit 1120, a highlighting unit 1122, a detection unit 1124, a startup unit 1126, a visual differentiation unit 1128, and a moving unit 1130.

[0299] Processing unit 1106 is configured to (e.g., using receiving unit 1110) receive user input at the device, which, upon receipt, triggers the display of multiple application views in an application view group. In response to receiving the user input, (e.g., using display unit 1102) the multiple application views of application view group 630 are displayed. The application view group includes pre-selected application views and adaptive views corresponding to the most recently opened application that are not among the pre-selected application views.

[0300] In some implementations, processing unit 1106 is configured to: (e.g., using display unit 1102) display an adaptive view corresponding to the most recently opened application, wherein the adaptive view includes a capability representation corresponding to adding the adaptive view to a pre-selected application view. It receives user input corresponding to a selection of the capability representation. In response to receiving user input for selecting the capability representation, it adds the adaptive view corresponding to the most recently opened application to the pre-selected application view (e.g., using adding unit 1112).

[0301] In some embodiments, processing unit 1106 is configured to display (e.g., with display unit 1102) a set of application views in a sequence and display (e.g., with display unit 1102) an adaptive view at a terminal of the sequence of the set of application views.

[0302] In some embodiments, processing unit 1106 is configured to receive (e.g., with receiving unit 1110) the user input while displaying an open application that is a most recently opened application that is not one of the preselected application views, and further in response to receiving the user input, an adaptive view corresponding to the most recently opened application that is not one of the preselected application views is displayed. The adaptive view includes an affordance to add the adaptive view to the preselected application views. User input corresponding to selection of the affordance is received (e.g., with receiving unit 1110). In response to receiving the user input to select the affordance, the adaptive view corresponding to the most recently opened application is added (e.g., with adding unit 1112) to the preselected application views.

[0303] In some embodiments, processing unit 1106 is configured to detect (e.g., with detecting unit 1124) launch of an application where the adaptive view and the preselected application views of the set of application views do not correspond to the launched application. In response to detecting the launch of the application, the adaptive view is updated (e.g., with updating unit 1114) to correspond to the launched application.

[0304] In some embodiments, processing unit 1106 is configured to display (e.g., with display unit 1102) a set of application views in a sequence. In response to receiving user input corresponding to display of the sequence of the set of application views, a subset of application views of the sequence of the set of application views is displayed (e.g., with display unit 1102). Processing unit 1106 is further configured to display (e.g., with display unit 1102) an application view of a most recently opened application in a center of the sequence of the subset of application views.

[0305] In some embodiments, processing unit 1106 is configured to display a sequence of application view groups (e.g., with display unit 1102). In response to receiving user input corresponding to the display of the sequence of application view groups, processing unit 1106 is configured to display a sequence of application view subgroups of the sequence of application view groups (e.g., with display unit 1102). The display of the sequence of application view subgroups includes displaying a first application view in the sequence of application view groups at a center of the sequence of application view subgroups, and displaying at least a partial view of a second application view in the sequence of application view groups that is sequential to the first application view, where the second application view is dimmed relative to the first application view.

[0306] In some embodiments, processing unit 1106 is configured to display an adaptive view (e.g., with display unit 1102) when an application associated with the adaptive view is not open. Processing unit 1106 is configured to receive user input corresponding to the adaptive view (e.g., with receiving unit 1110), and in response to receiving the user input corresponding to the adaptive view, processing unit 1106 is configured to launch the associated application (e.g., with launching unit 1126).

[0307] In some embodiments, processing unit 1106 is configured to display a portion of a sequence of application view groups (e.g., with display unit 1102). Processing unit 1106 is configured to receive input on an application view in a first position in the sequence of application view groups (e.g., with receiving unit 1110). In response to the input on the application view, processing unit 1106 is configured to visually distinguish the selected application view relative to other application views in the sequence of application view groups (e.g., with visual distinguishing unit 1128). Processing unit 1106 is configured to detect movement of the input on the application view to a second position in the sequence of application view groups (e.g., with detecting unit 1124). In response to the detected movement of the input on the application view, processing unit 1106 is configured to move the selected application view to the second position in the sequence of application view groups (e.g., with moving unit 1130). Processing unit 1106 is configured to detect an interruption of the input on the application view (e.g., with detecting unit 1124), and in response to the detected interruption of the input on the application view, processing unit 1106 is configured to reorder the application view to the second position in the sequence of application view groups (e.g., with reordering unit 1116).

[0308] In some embodiments, processing unit 1106 is configured to receive (e.g., with receiving unit 1110) an input on an application view of the plurality of application views that, when received, initiates (e.g., with deleting unit 1118) deletion of the application view from the group of application views. In response to the input on the application view, the application view is deleted (e.g., with deleting unit 1118) from the group of application views.

[0309] In some embodiments, processing unit 1106 is configured to receive (e.g., with receiving unit 1110) a swipe gesture for scrolling through the group of application views. In response to receiving the swipe gesture: in accordance with a speed of the swipe gesture being below a predetermined speed threshold, scrolling (e.g., with scrolling unit 1120) to an adjacent application view, and in accordance with the speed of the swipe gesture being above the predetermined speed threshold, scrolling (e.g., with scrolling unit 1120) through a plurality of application views of the group of application views.

[0310] In some embodiments, processing unit 1106 is configured to receive (e.g., with receiving unit 1110) a user input that, when received, initiates scrolling to an adjacent application view in the group of application views. In response to receiving the user input, scrolling (e.g., with scrolling unit 1120) to the adjacent application view in the group of application views, wherein the scrolling to the adjacent application view includes a speed reduction based on a predetermined coefficient of friction.

[0311] In some embodiments, processing unit 1106 is configured to, while displaying the plurality of application views in a display area, receive (e.g., with receiving unit 1110) an input at a bottom edge of the display area that, when received, initiates scrolling of the application views. In response to the input at the edge of the display area, moving (e.g., with moving unit 1130) the application views away from the bottom edge of the display area. Detecting movement of the input along the bottom edge of the display area. In response to the detected movement of the input along the bottom edge of the display area, scrolling (e.g., with scrolling unit 1120) through the group of application views.

[0312] In some embodiments, processing unit 1106 is configured to, while displaying the plurality of application views of the group of application views, display (e.g., with displaying unit 1102) a set of application view indicia. Each of the application view indicia corresponds to a respective application view in the group of application views. An application view indicium corresponding to an adaptive view is visually distinguished from an application view indicium corresponding to a preselected application view.

[0313] In some embodiments, processing unit 1106 is configured to: while displaying the plurality of application views of the application view group, display (e.g., with display unit 1102) a set of application view badges, where each of the application view badges corresponds to a respective application view of the application view group. Highlight (e.g., with highlighting unit 1122) the badge corresponding to the displayed application view. Receive (e.g., with receiving unit 1110) a user input that, when received, is used to scroll to another application view of the application view group. In response to receiving the user input, scroll (e.g., with scrolling unit 1120) to the other application view. In accordance with scrolling to the other application view, highlight (e.g., with highlighting unit 1122) the application view badge corresponding to the other application view, where the highlighting of the application view badge corresponding to the other application view includes an initial highlight intensity and a final highlight intensity, where the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity.

[0314] In some embodiments, processing unit 1106 is configured to: while the audio application is playing audio content, where the audio application includes an application-specific control interface and the application view group does not include an application view corresponding to the audio application, update (e.g., with updating unit 1114) the application view group with a universal audio application control interface view corresponding to a universal audio application control interface, where the universal audio application control interface is different from the application-specific control interface that is not part of the taskbar. Receive (e.g., with receiving unit 1110) a user input on the universal audio application control interface view that, when received, causes launching of the universal audio application control interface. In response to receiving the user input, display (e.g., with display unit 1102) the universal audio application control interface for controlling playback of the audio content playing on the audio application.

[0315] In some embodiments, processing unit 1106 is configured to: where the universal audio application control interface view includes a affordance corresponding to adding the universal audio application control interface view to the application view group. Receive (e.g., with receiving unit 1110) a user input to select the affordance, and in response to receiving the user input to select the affordance, add (e.g., with adding unit 1112) the universal audio application control interface view to the application view group.

[0316] In some embodiments, processing unit 1106 is configured to, at a companion device paired with the device that includes one or more processors and memory, display (e.g., with display unit 1102) an adaptive view corresponding to a most recently opened application, where the adaptive view includes an affordance to add the adaptive view to a preselected application view. Receive (e.g., with receiving unit 1110) user input to select the affordance, and in response to receiving the user input to select the affordance, add (e.g., with adding unit 1112) the adaptive view corresponding to the most recently opened application to the preselected application view.

[0317] In some embodiments, processing unit 1106 is configured to, at a companion device paired with the device that includes one or more processors, a touchscreen, and memory, display (e.g., with display unit 1102) a portion of a sequence of application view groups. Receive (e.g., with receiving unit 1110) input on the touchscreen at a location of an application view in a first position in the sequence of application view groups that is displayed. In response to the input, visually distinguish (e.g., with visually distinguishing unit 1128) the selected application view relative to other application views in the sequence of application view groups. Detect (e.g., with detecting unit 1124) movement of the input on the application view to a second position in the sequence of application view groups without interruption of contact with the touchscreen. In response to the detected movement of the input on the application view, move (e.g., with moving unit 1130) the selected application view to the second position in the sequence of application view groups. Detect (e.g., with detecting unit 1124) interruption of the input from the touchscreen, and in response to the detected interruption of the input from the touchscreen, reorder (e.g., with reordering unit 1116) the application view to the second position in the sequence of application view groups.

[0318] In some embodiments, processing unit 1106 is configured to, at a companion device of the device, where the companion device paired with the device includes one or more processors and memory, receive (e.g., with receiving unit 1110) input on an application view of the plurality of application views that, when received, initiates deletion of the application view from the application view group. In response to the input on the application view, delete (e.g., with deleting unit 1119) the application view from the application view group.

[0319] The operations described above with reference to FIG. 10 are, optionally, performed by Figures 1A to 1B or Figure 11The components depicted are used to implement this. For example, receiving operation 1002 and display operation 1004 are optionally implemented by an event classifier 170, an event recognizer 180, and an event handler 190. An event monitor 171 in the event classifier 170 detects a touch on the touch-sensitive display 112, and an event dispatcher module 174 transmits the event information to the application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first touch at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as activation of a power indication on the user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. The event handler 190 optionally utilizes or invokes a data updater 176 or an object updater 177 to update the application's internal state 192. In some embodiments, the event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand how it can be based on Figures 1A to 1B The components depicted in the diagram are used to perform other processes.

[0320] Figures 12A to 12G Exemplary user interfaces for updating views in an application view group, according to some embodiments, are shown. The user interfaces in these figures are used to illustrate the processes described below, including... Figure 13 The process in.

[0321] Figure 12A A device 600 with a touch-sensitive display 602 is shown. A user interface 604 is displayed on the touch-sensitive display 602. The user interface 604 is as follows: Figure 12A The watch face shown is 608, which includes the watch application.

[0322] The device 600 includes various input mechanisms for receiving user input, such as a rotatable input mechanism 610 capable of receiving rotatable input (and also capable of receiving push input), and a push input mechanism 612 capable of receiving push input.

[0323] See now Figures 12A to 12B In response to receiving user input 1210 at input mechanism 612, device 600 displays multiple application views of application view group 630. The application view group is an ordered list of application views corresponding to respective applications. Application view group 630 includes pre-selected application views. In some embodiments, the application view group includes adaptive application views that are not among the application views but correspond to the most recently opened application.

[0324] In some implementation schemes, such as Figure 12B As shown, in response to user input 1210, device 600 displays application views 633, 634, and 635.

[0325] As Figure 12B shown, application views 633, 634, and 635 are displayed in respective first states. In some embodiments, application views 633, 634, and 635 are the most recently viewed screens of the respective applications. For example, application view 634 is the most recently viewed screen of the stock application.

[0326] Referring to Figure 12C In some embodiments, application view group 630 is no longer displayed. For example, an application is opened (e.g., the clock application) and, in response to the opened application, application view group is no longer displayed.

[0327] In some embodiments, device 600 automatically determines, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the application view group to a second state. In accordance with the automatic determination, without user input, that the predetermined criterion is satisfied, device 600 updates at least one application view of the application view group. In some embodiments, the predetermined criterion is a periodic timeout (e.g., every three minutes). For example, at the end of each periodic timeout, one or more of the application views are updated to an updated second state. In such examples, application view 634 of the stock application is updated with current stock information.

[0328] In some embodiments, the predetermined criterion is a change in data associated with an application view. For example, for a stock application, stock information can change frequently. Accordingly, the application view corresponding to the stock application is updated in response to a change in the stock information displayed in the application view. In some embodiments, each of the application views is updated in the background when the predetermined condition is satisfied (e.g., the periodic timeout ends, or the information displayed in the respective application view changes).

[0329] In some embodiments, the application view updating in response to the preselected criteria being met can occur with the corresponding application being in one of various states, such as an application that is ready to launch (e.g., becomes open), an open or executing application, or an application that is closed. Specifically, an open or executing application can be, but is not limited to, an active application that is currently displayed on a display screen of a device on which the application is being used, a background application (or background process) that is not currently displayed but one or more processes of the application are being processed by one or more processors, and a suspended or hibernating application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and can be used to resume execution of the application.

[0330] In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is not currently displayed. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is launched. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is un-launched. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is inactive.

[0331] As described above, the applications associated with the application view group are stored in memory. Accordingly, the updated application view of the respective application is also stored in memory.

[0332] Referring to Figures 12C to 12D , a second user input 1212 is received, the second user input, when received, initiates display of the plurality of application views of the application view group 630. In response to receiving the second user input 1212, the device 600 displays the plurality of application views of the application view group 630 including the updated at least one application view 634 updated to a second state. For example, the device 600 displays the application view 634 in an updated second state including current stock information updated from the first state, as shown in Figure 12B .

[0333] In some embodiments, referring to Figure 12D , the displaying the plurality of application views of the application view group in the second state further includes displaying a first application view in the application view area (e.g., user interface 604), where the first application view (e.g., application 634) is the updated application view that is focused and centered in the application view area.

[0334] Additionally, in some embodiments, at least a portion of a second application view (e.g., application views 633 and 635) is displayed in the application view area, wherein the second application view is sequential relative to the first application view, and the second application view is not updated. For example, when application view 634 is updated to the second state, application views 633 and 635 are not updated to the second state. Therefore, when the updated application view 634 is displayed in the second application state, application views 633 and 635 are not displayed in the second updated state.

[0335] In some implementation schemes, see FIG. 12E The updated application view of the stock application is an adaptive application view, and a set of application view markers is also displayed, each of which corresponds to a corresponding application view in the application view group. In particular, the application view marker 645 corresponding to the adaptive application view is visually distinguishable from the application view markers corresponding to the preselected application view.

[0336] In some implementations, the plurality of application views (e.g., when displaying a group of application view groups) FIG. 12D During application views 633, 634, and 635, a set of application view markers 640 are displayed, each of which corresponds to a corresponding application view in the application view group. The marker corresponding to the displayed application view is highlighted. User input is received, which, when received, is used to scroll to another application view in the application view group (e.g., ...). FIG. 7A Input 710 in the middle). In response to receiving the user input, the application view is scrolled to the other application view (e.g., FIG. 7B As you scroll to the other application view, highlight the application view marker corresponding to that other application view, where the highlighting of the application view corresponding to the other application view includes an initial highlight brightness (e.g., ...). FIG. 7K ) and final highlight brightness, wherein the highlight brightness varies from the initial highlight brightness to the final highlight brightness (e.g. FIG. 7L The transition period increases.

[0337] In some implementations, it is determined whether a first timeout has expired since the application view's most recent update. In response to the first timeout expiring, the application view is displayed in a dimmed state. See, for example, [link to relevant documentation]. FIG. 12FIf the application view 634 cannot be updated before the end of the first time period (e.g., five minutes), the application view is dimmed (or visually distinguished) to indicate that the application view cannot be updated. Depending on the selection of the application view in the dimmed state, the application corresponding to the selected application view is launched. For example, in response to the selection of the application view 634, the stock application is launched when in the dimmed state.

[0338] In addition, it is determined whether a second timeout (e.g., 30 minutes) has expired since the most recent update of the application view, where the duration of the second timeout is longer than the duration of the first timeout. In response to the expiration of the second timeout, the application view is displayed that does not include a screenshot of the corresponding application. For example, see FIG. 12G If the application view 634 cannot be updated before the end of the second time period (e.g., 30 minutes), the displayed application view does not include a screenshot of the stock application. Depending on the selection of the application view that does not include a screenshot of the corresponding application, the corresponding application is launched. For example, in response to the selection of the application view 634 that does not include a screenshot of the stock application, the stock application is launched.

[0339] FIG. 13 is a flow diagram illustrating a method for updating application views in a set of application views with an electronic device in accordance with some embodiments. The method 1300 is performed at a device (e.g., 100, 300, 500, 600, or 900) with a display, one or more processors, and memory. Some operations in method 1300 are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted.

[0340] As described below, method 1300 provides an intuitive way for updating application views in a set of application views. This method reduces the cognitive burden on a user for selecting an application via an updated application view in a set of application views, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to select an application via an updated application view in a set of application views more quickly and efficiently conserves power and increases the time between battery charges.

[0341] At block 1302, a first user input (e.g., user input 1210) is received, the first user input, when received, initiates display of a plurality of application views of a set of application views 630, where the set of application views includes a preselected application view, the plurality of application views of the set of application views being displayed in respective first states (e.g., FIG. 12A ).

[0342] At block 1304, it is automatically determined, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to the second state. In some embodiments, the predetermined criterion is an end of a predetermined timeout. In some embodiments, the predetermined criterion is a change in data displayed on the application view.

[0343] At block 1306, in accordance with the automatic determination that the predetermined criterion is satisfied, without user input, the at least one application view of the group of application views (e.g., application view 634 in FIG. 6B) is updated to the second state. FIG. 12D

[0344] At block 1308, a second user input (e.g., input 1212) is received, the second user input, when received, initiates display of the plurality of application views of the group of application views.

[0345] At block 1310, in response to receiving the second user input (e.g., input 1212), the plurality of application views of the group of application views, including the updated at least one application view, are updated to the second state (e.g., FIG. 6B). FIG. 12D

[0346] In some embodiments, the group of application views further includes an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0347] In some embodiments, the automatic updating of the application view, without user input, occurs when the corresponding application is not currently displayed. In some embodiments, the automatic updating of the application view, without user input, occurs when the corresponding application is launched. In some embodiments, the automatic updating of the application view, without user input, occurs when the corresponding application is unlaunched. In some embodiments, the automatic updating of the application view, without user input, occurs when the corresponding application is inactive.

[0348] In some embodiments, wherein displaying the plurality of application views of the group of application views in the second state includes displaying a first application view in an application view region (e.g., user interface 604), wherein the first application view is the updated application view that is focused and centered in the application view region (e.g., FIG. 6B). FIG. 12D ​​application view in the application view region, where the second application view is sequential with respect to the first application view, where the second application view is not updated (e.g., FIG. 12D application views 633 and 635 in the application view region).

[0349] In some embodiments, in response to determining that the predetermined criteria are satisfied, each of the application views in the application view group is updated. For example, each of the application views is updated at the end of the timeout.

[0350] In some embodiments, it is determined whether a first timeout has expired since a most recent update of the application view. In response to the first timeout expiring, the application view is displayed in a dimmed state (e.g., FIG. 12F ). In accordance with a selection of the application view in the dimmed state, an application corresponding to the selected application view is launched (e.g., in response to a selection of the application view 634, the stock application is launched). It is determined whether a second timeout has expired since a most recent update of the application view, where the duration of the second timeout is longer than the duration of the first timeout. In response to the second timeout expiring, an application view that does not include a screenshot of the corresponding application is displayed (e.g., FIG. 12G ), and in accordance with a selection of the application view that does not include a screenshot of the corresponding application, the corresponding application is launched (e.g., in response to a selection of the application view 634, the stock application is launched).

[0351] In some embodiments, while displaying the plurality of application views of the application view group, a set of application view icons is displayed (e.g., FIG. 12B ), where each of the application view icons corresponds to a respective application view in the application view group, where the application view icon corresponding to the adaptive view is visually distinguished from the application view icons corresponding to the preselected application views (e.g. FIG. 12E ).

[0352] In some embodiments, during display of the plurality of application views of the application view group, a set of application view icons is displayed, where each of the application view icons corresponds to a respective application view in the application view group (e.g., FIG. 12B ), and a displayed application view is highlighted. A user input is received, the user input, when received, is to scroll to another application view in the application view group (e.g., FIG. 7A ). In response to receiving the user input, the other application view is scrolled to (e.g., FIG. 7B). As you scroll to the other application view, highlight the application view marker corresponding to that other application view (e.g., FIG. 7B The application view corresponding to the highlighting of the other application view includes an initial highlight brightness (e.g., ...). FIG. 7K ) and final highlight brightness, wherein the highlight brightness varies from the initial highlight brightness to the final highlight brightness (e.g. FIG. 7L The transition period increases.

[0353] Note that the above reference method 1300 (for example, FIG. 13 The details of the process described above also apply in a similar manner to the methods described above. For example, method 1300 optionally includes one or more features of the various methods described above with reference to method 1000. For example, viewing the application view according to method 1100 may include viewing the updated application view according to method 100. For the sake of brevity, these details will not be repeated below.

[0354] According to some implementation plans FIG. 14 An exemplary functional block diagram of an electronic device 1400 configured according to the principles of various described embodiments is shown. According to some embodiments, functional blocks of the electronic device 1400 are configured to perform the techniques described above. The functional blocks of the device 1400 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described examples. Those skilled in the art will understand that... FIG. 14 The functional blocks described herein may be optionally combined or separated into sub-blocks to implement the principles of the various instances described herein. Therefore, the description herein may optionally support any possible combination or separation or further limitation of the functional blocks described herein.

[0355] like FIG. 14 As shown, the electronic device 1400 includes a display unit 1402 configured to display a graphical user interface, a touch-sensitive surface unit 1404 optionally configured to receive contact, and a processing unit 1406 coupled to the display unit 1402 and the optional touch-sensitive surface unit 1404. In some embodiments, the processing unit 1406 includes a receiving unit 1410, a determining unit 1412, an updating unit 1414, a starting unit 1416, a highlighting unit 1418, and a scrolling unit 1420.

[0356] Processing unit 1406 is configured to (e.g., using receiving unit 1410) receive a first user input, which, upon being received, triggers the display of multiple application views in an application view group, wherein the application view group includes pre-selected application views, and the multiple application views in the application view group are displayed in corresponding first states (e.g., ...).FIG. 12B ) (e.g., with determination unit 1412) automatically determine, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state. In accordance with the automatic determination, without user input, that the predetermined criterion is satisfied, (e.g., with update unit 1414) update the at least one application view of the group of application views to the second state. (e.g., with receiving unit 1410) receive a second user input, the second user input, when received, causing display of the plurality of application views of the group of application views (e.g., FIG. 12D ). In response to receiving the second user input, (e.g., with display unit 1402) display the plurality of application views of the group of application views including the updated at least one application view updated to the second state (e.g., FIG. 12D ).

[0357] Processing unit 1406 is configured to: (e.g., with display unit 1402) display the plurality of application views of the group of application views in the second state, including display of the first application view in the application view region, wherein the first application view is the updated application view that is focused and centered in the application view region (e.g., FIG. 12D ), and (e.g., with display unit 1402) display at least a partial view of the second application view in the application view region, wherein the second application view is sequential relative to the first application view, wherein the second application view is not updated (e.g., FIG. 12D ).

[0358] Processing unit 1406 is configured to: in response to determining that the predetermined criterion is satisfied, (e.g., with update unit 1414) update each of the application views in the group of application views.

[0359] Processing unit 1406 is configured to: (e.g., with determination unit 1412) determine whether a first timeout has expired since a most recent update of an application view. In response to the first timeout expiring, (e.g., with display unit 1402) display the application view in a dimmed state (e.g., FIG. 12F). In accordance with a selection of an application view in the dimmed state, (e.g., with launch unit 1416) launching an application corresponding to the selected application view. (e.g., with determination unit 1412) determining whether a second timeout has expired since a most recent update of the application view, where the second timeout has a duration that is longer than a duration of the first timeout. In response to the second timeout expiring, (e.g., with display unit 1402) displaying an application view that does not include a screenshot of the corresponding application (e.g., FIG. 12G ), and in accordance with a selection of the application view that does not include the screenshot of the corresponding application, (e.g., with launch unit 1416) launching the corresponding application.

[0360] Processing unit 1406 is configured to, while displaying the plurality of application views of the application view group, (e.g., with display unit 1402) display a set of application view markers (e.g., FIG. 12B ), where each of the application view markers corresponds to a respective application view of the application view group, where an application view marker corresponding to an adaptive view is visually distinguished from an application view marker corresponding to a preselected application view (e.g. FIG. 12E ).

[0361] Processing unit 1406 is configured to, while displaying the plurality of application views of the application view group, (e.g., with display unit 1402) display a set of application view markers, where each of the application view markers corresponds to a respective application view of the application view group (e.g., FIG. 12B ), and (e.g., with highlight unit 1418) highlight a marker corresponding to a displayed application view. (e.g., with receive unit 1410) receive a user input that, when received, is used to scroll to another application view of the application view group (e.g., FIG. 7A ). In response to receiving the user input, (e.g., with scroll unit 1420) scroll to the other application view (e.g., FIG. 7B ). In accordance with scrolling to the other application view, (e.g., with highlight unit 1418) highlight an application view marker corresponding to the other application view (e.g., FIG. 7B ), where the highlighting of the application view corresponding to the other application view includes an initial highlight intensity (e.g. FIG. 7K ) and a final highlight intensity, where the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity (e.g. FIG. 7L ).

[0362] In some embodiments, the application view group also includes an adaptive view corresponding to the most recently opened application that is not one of the preselected application views (e.g., FIG. 12E ).

[0363] In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is currently not being displayed. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is launched. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is un-launched. In some embodiments, the automatic updating of the application view without user input occurs when the corresponding application is inactive.

[0364] The operations described above with reference to FIG. 13 are optionally implemented by the components depicted in FIG. 1A to FIG. 1B or FIG. 14 . For example, receiving operation 1302, determining operation 1304, determining operation 1306, receiving operation 1308, and display operation 1310 are optionally implemented by the event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in the event sorter 170 detects a contact on the touch-sensitive display 112, and event dispatcher module 174 delivers the event information to the application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch- sensitive surface corresponds to a predefined event or sub-event, such as activation of an affordance on the user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the relevant user interface elements of the application 136-1. Similarly, but for a different event, event handler 190 accesses one or more other event handlers 190 to update the application state 192 as appropriate and terminates the event recognition process if the event recognition process is completed. FIG. 1A to FIG. 1B Other processes can be implemented based on the components depicted in .

[0365] FIG. 15A to FIG. 15C Example user interfaces for displaying views in an application view group are shown in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 16 .

[0366] FIG. 15AA device 600 with a touch-sensitive display 602 is shown. A user interface 604 is displayed on the touch-sensitive display 602. The user interface 604 is as follows: FIG. 15A The watch face shown is 608, which includes the watch application.

[0367] The device 600 includes various input mechanisms for receiving user input, such as a rotatable input mechanism 610 capable of receiving rotatable input (and also capable of receiving push input), and a push input mechanism 612 capable of receiving push input.

[0368] See now FIG. 15A to FIG. 15C Device 600 display dial ( FIG. 15A The first user input 1510 is received, and the first user input, upon being received, triggers the display of multiple application views (e.g., application views 633, 634, and 635) in the application view group 630, wherein the application view group includes pre-selected application views.

[0369] See FIG. 15B In response to receiving a first user input, device 600 displays the plurality of application views in a first state. For example, application view 634 corresponding to a weather application is centered and displayed. Furthermore, at least a portion of application views 633 and 635 are displayed adjacent to application view 634.

[0370] See still FIG. 15B A second user input (e.g., input 1512) on application view 634 of the plurality of application views is received, and the second user input triggers the launch of the application corresponding to the application view selected by the second user input when it is received.

[0371] See FIG. 15C In response to receiving a second user input, the device replaces the displayed plurality of application views by displaying the user interface of the launched application. For example, device 600 displays a weather application and replaces the display of application views 633, 634, and 635.

[0372] In some implementation schemes, see FIG. 15B The device receives a swipe gesture 1514 (e.g., a right swipe gesture) for scrolling through application view group 630. In response to receiving swipe gesture 1514, the device scrolls through application view group 630 and replaces the initially displayed plurality of application views 633, 634, and 635 with a second application view group such as application views 631 and 632 (e.g., ...). FIG. 6B ).

[0373] In some embodiments, the displaying the plurality of application views of the application view group in the second state replaces the displayed watch face (e.g., FIG. 15B ). FIG. 15A ).

[0374] FIG. 16 is a flow diagram illustrating a method for viewing application views of an application view group with an electronic device in accordance with some embodiments. The method 1600 is performed at a device (e.g., 100, 300, 500, 600, or 900) with a display, one or more processors, and memory. Some operations in method 1600 are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted.

[0375] As described below, method 1600 provides an intuitive way to view application views of an application view group. This method reduces the cognitive burden on a user for viewing application views of an application view group, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to view application views of an application view group faster and more efficiently conserves power and increases the time between battery charges.

[0376] At block 1602, a watch face is displayed (e.g., FIG. 15A ).

[0377] At block 1604, a first user input is received (e.g., user input 1510), the first user input, when received, triggers display of a plurality of application views of an application view group, where the application view group includes a preselected application view.

[0378] At block 1606, in response to receiving the first user input, the plurality of application views of the application view group are displayed (e.g., FIG. 15B ).

[0379] At block 1608, a second user input (e.g., user input 1512) on a displayed application view of the plurality of application views is received, the second user input, when received, triggers launch of an application corresponding to the application view selected by the second user input (e.g., FIG. 15B ).

[0380] At block 1610, in response to receiving the second user input, the displayed plurality of application views are replaced by displaying a user interface of the launched application (e.g., FIG. 15C ).

[0381] In some embodiments, see FIG. 15B, receiving a swipe gesture 1514 (e.g., a rightward swipe gesture) to scroll through the application view groups 630. In response to receiving the swipe gesture 1514, the application view groups are scrolled and the plurality of application views 633, 634, and 635 initially displayed are replaced with a second application view group such as application views 631 and 632 (e.g., FIG. 6B ) in the second application view group.

[0382] In some embodiments, the displaying of the plurality of application views of the application view group in the second state (e.g., FIG. 15B ) replaces the displayed watch face (e.g., FIG. 15A ).

[0383] Note that details of processes described above in reference to method 1600 (e.g., FIG. 16 ) are also applicable in an analogous manner to the methods described above. For example, method 1600 optionally includes one or more of the characteristics of the various methods described above in reference to methods 1000 and 1300. For example, the viewing of application views according to method 1600 can include embodiments of the viewing of updated application views according to method 1000 and embodiments of the updating of application views according to method 1300. These details are not repeated below for the sake of brevity.

[0384] According to some embodiments, FIG. 17 An example functional block diagram of an electronic device 1700 configured in accordance with the principles of the various described embodiments is shown. The functional blocks of the electronic device 1700 are configured to perform the techniques described above, according to some embodiments. The functional blocks of the device 1700 are optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described examples. Those skilled in the art will understand that the functional blocks of the device 1700 described in FIG. 17 the functional blocks described above are optionally combined or separated into sub-blocks to implement the principles of the various described examples. Accordingly, the description herein optionally supports any possible combination or separation of the functional blocks described herein or further limitations.

[0385] As shown in FIG. 17 , the electronic device 1700 includes a display unit 1702 configured to display a graphical user interface, an optional touch-sensitive surface unit 7404 configured to receive contacts, and a processing unit 1706 coupled to the display unit 1702 and the optional touch-sensitive surface unit 1704. In some embodiments, the processing unit 1706 includes a receiving unit 1710, a replacing unit 1712, and a scrolling unit 1720.

[0386] The processing unit 1706 is configured to display a watch face (e.g., FIG. 15A) receiving (e.g., with receive unit 1710) a first user input that, when received, initiates display of a plurality of application views of an application view group, where the application view group includes a preselected application view (e.g., FIG. 15B ).

[0387] In response to receiving the first user input, displaying (e.g., with display unit 1702) the plurality of application views of the application view group (e.g., FIG. 15B ). receiving (e.g., with receive unit 1710) a second user input on an application view of the displayed plurality of application views (e.g., FIG. 15B ), the second user input, when received, initiating launch of an application corresponding to the application view selected by the second user input. In response to receiving the second user input, replacing (e.g., with replace unit 1712) the displayed plurality of application views with display of a user interface of the launched application (e.g., FIG. 15C ).

[0388] Receive unit 1710 is configured to receive (e.g., with receive unit 1710) a swipe gesture for scrolling through an application view group (e.g., FIG. 15B ). In response to receiving the swipe gesture, scrolling (e.g., with scroll unit 1714) through the application view group and replacing (e.g., with replace unit 1712) the initially displayed plurality of application views with a second application view group (e.g., FIG. 6B ).

[0389] Replace unit 1712 is configured to replace (e.g., with replace unit 1712) the displayed watch face with the display of the plurality of application views of the application view group (e.g., FIG. 15B ).

[0390] The operations described above with reference to FIGS. 1 through 8 are, optionally, performed by FIG. 16 one or more processors 1704 of FIG. 1A to FIG. 1B or FIG. 17The depicted components are implemented, for example, by the event sorter 170, event recognizer 180 and event handler 190. The event monitor 171 in the event sorter 170 detects a contact with the touch-sensitive display 112, and the event dispatcher module 174 delivers the event information to the application 136-1. The respective event recognizer 180 of the application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch- sensitive surface corresponds to a predefined event or sub-event, such as activation of an affordance on the user interface. When a respective predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, the event handler 190 accesses a respective GUI updater 178 to update the GUI. Where multiple events are detected by event monitor 171, event dispatcher 174, event recognizer 180, or FIG. 1A to FIG. 1B Other processes can be implemented in the components depicted.

[0391] The preceding description is presented to enable any person skilled in the art to practice the applications as described in the preceding specific embodiments. The description is not intended to limit the applications to the precise forms or embodiments disclosed. Obviously, many modifications and variations are possible in view of the above teachings. The specific embodiments were chosen for

[0392] While the present disclosure and examples have been described with reference to certain embodiments thereof, it is to be understood that variations and modifications will be obvious to those skilled in the art. It is the intent, therefore, to be limited only as described by the appended claims.

[0393] As described above, one aspect of the present technology is the collection and use of data from a variety of sources to improve the delivery of enlightening content or any other content to users that can be of interest to them. The present disclosure contemplates that in some instances, this collected data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.

[0394] This disclosure recognizes that the use of such personal information data in the present invention can benefit users. For example, the personal information data can be used to deliver targeted content that is of interest to the user. Therefore, the use of such personal information data enables planned control over the delivered content. Furthermore, this disclosure also anticipates other uses of the personal information data that are beneficial to the user.

[0395] This disclosure also envisions that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. Furthermore, such collection should only be conducted with the user's informed consent. Additionally, such entities should take any necessary steps to safeguard and protect access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and procedures. Furthermore, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices.

[0396] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with respect to advertising delivery services, the technology of this invention can be configured to allow users to choose to "join" or "opt out" of the collection of personal information data during service registration. As another example, users can choose not to provide location information for a targeted content delivery service. Yet another example is that users can choose not to provide precise location information but allow the transmission of location area information.

[0397] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, preferences can be inferred based on non-personal information data or an absolute minimum of personal information, such as content requested by a device associated with a user, other non-personal information available to the content delivery service, or publicly available information, thereby selecting content and delivering it to the user.

[0398] Exemplary methods, non-transitory computer-readable storage media, systems, and electronic devices are given in the following:

[0399] 1. A method comprising:

[0400] At a device with one or more processors and memory:

[0401] receiving user input that, when received, initiates display of a plurality of application views of an application view group; and

[0402] in response to receiving the user input, displaying the plurality of application views of the application view group, wherein the application view group includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0403] 2. The method of item 1, further comprising:

[0404] displaying the adaptive view corresponding to the most recently opened application, wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application views;

[0405] receiving user input corresponding to selection of the affordance; and

[0406] in response to receiving the user input to select the affordance, adding the adaptive view corresponding to the most recently opened application to the preselected application views.

[0407] 3. The method of item 1 or 2, wherein the application view group is displayed in a sequence, the method further comprising:

[0408] displaying the adaptive view at a terminal end of the sequence of the application view group.

[0409] 4. The method of any of items 1-3, wherein the user input is received while displaying an open application that is not one of the preselected application views that is a most recently opened application, the method further comprising:

[0410] in further response to receiving the user input, displaying the adaptive view corresponding to the most recently opened application that is not one of the preselected application views,

[0411] wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application views,

[0412] receiving user input corresponding to selection of the affordance; and

[0413] in response to receiving the user input to select the affordance, adding the adaptive view corresponding to the most recently opened application to the preselected application views.

[0414] 5. The method of any of items 1-4, further comprising:

[0415] detecting launch of an application, wherein the adaptive view and the preselected application view of the application view group do not correspond to the launched application; and

[0416] in response to detecting the launch of the application, updating the adaptive view to correspond to the launched application.

[0417] 6. The method of any of items 1-5, wherein the application view group is displayed in a sequence, the method further comprising:

[0418] in response to receiving user input corresponding to display of the sequence of the application view group, displaying a subset of application views of the sequence of the application view group, wherein the displaying the subset of application views comprises:

[0419] displaying an application view of a most recently opened application at a center of the sequence of the subset of application views.

[0420] 7. The method of any of items 1-6, wherein the application view group is displayed in a sequence, the method further comprising:

[0421] in response to receiving user input corresponding to display of the sequence of the application view group, displaying a subset of application views of the sequence of the application view group, wherein the displaying the subset of application views comprises:

[0422] displaying a first application view of the sequence of the application view group at a center of the sequence of the subset of application views; and

[0423] displaying at least a partial view of a second application view of the sequence of the application view group in sequence relative to the first application view, wherein the second application view is dimmed relative to the first application view.

[0424] 8. The method of any of items 1-7, further comprising:

[0425] displaying the adaptive view when an application associated with the adaptive view is not open;

[0426] receiving user input corresponding to the adaptive view; and

[0427] in response to receiving the user input corresponding to the adaptive view, launching the associated application.

[0428] 9. The method of any of items 1-8, further comprising:

[0429] displaying a portion of the sequence of the set of application views;

[0430] receiving an input on an application view in a first position in the sequence of the set of application views;

[0431] in response to the input on the application view, visually distinguishing the selected application view relative to other application views in the sequence of the set of application views;

[0432] detecting movement of the input on the application view to a second position in the sequence of the set of application views;

[0433] in response to the detected movement of the input on the application view, moving the selected application view to the second position in the sequence of the set of application views;

[0434] detecting an interruption of the input on the application view; and

[0435] in response to the detected interruption of the input on the application view, reordering the application view to the second position in the sequence of the set of application views.

[0436] 10. The method of any of items 1-9, further comprising:

[0437] receiving an input on an application view of the plurality of application views, the input, when received, instigating deletion of the application view from the set of application views; and

[0438] in response to the input on the application view, deleting the application view from the set of application views.

[0439] 11. The method of any of items 1-10, further comprising:

[0440] receiving a swipe gesture to scroll through the set of application views; and

[0441] in response to receiving the swipe gesture:

[0442] in accordance with a speed of the swipe gesture being below a predetermined speed threshold, scrolling to an adjacent application view; and

[0443] scroll through a plurality of application views of the application view group based on a predetermined coefficient of friction.

[0444] 12. The method of any of items 1-11, further comprising:

[0445] receiving a user input that, when received, initiates scrolling to an adjacent application view in an application view group; and

[0446] in response to receiving the user input, scrolling to the adjacent application view in the application view group, wherein the scrolling to the adjacent application view includes a velocity reduction based on a predetermined coefficient of friction.

[0447] 13. The method of any of items 1-12, further comprising:

[0448] while displaying the plurality of application views in a display area, receiving an input at a bottom edge of the display area that, when received, initiates scrolling of the application views;

[0449] in response to the input at the edge of the display area, moving the application views away from the bottom edge of the display area;

[0450] detecting movement of the input along the bottom edge of the display area; and

[0451] in response to the detected movement of the input along the bottom edge of the display area, scrolling through the application view group.

[0452] 14. The method of any of items 1-13, further comprising:

[0453] while displaying the plurality of application views of the application view group, displaying a set of application view icons, wherein each of the application view icons corresponds to a respective application view in the application view group, wherein the application view icon corresponding to the adaptive view is visually distinguished from the application view icon corresponding to the preselected application view.

[0454] 15. The method of any of items 1-14, further comprising:

[0455] while displaying the plurality of application views of the application view group, displaying a set of application view icons, wherein each of the application view icons corresponds to a respective application view in the application view group;

[0456] highlighting an application view marker corresponding to the displayed application view;

[0457] receiving user input, the user input, when received, to scroll to another application view in the group of application views;

[0458] in response to receiving the user input, scrolling to the other application view;

[0459] in accordance with scrolling to the other application view, highlighting an application view marker corresponding to the other application view, wherein the highlighting of the application view corresponding to the other application view includes:

[0460] an initial highlight intensity; and

[0461] a final highlight intensity, wherein the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity.

[0462] 16. The method of any of items 1-15, further comprising:

[0463] while an audio application is playing audio content, wherein the audio application includes an application-specific control interface, wherein the group of application views does not include an application view corresponding to the audio application:

[0464] updating the group of application views with a universal audio application control interface view corresponding to a universal audio application control interface, wherein the universal audio application control interface is different from the application-specific control interface;

[0465] receiving user input on the universal audio application control interface view, the user input, when received, to initiate launching the universal audio application control interface; and

[0466] in response to receiving the user input, displaying the universal audio application control interface for controlling playback of the audio content playing on the audio application.

[0467] 17. The method of any of items 1-16, wherein the universal audio application control interface view includes an affordance corresponding to adding the universal audio application control interface view to the group of application views;

[0468] receiving user input to select the affordance; and

[0469] in response to receiving the user input to select the affordance, adding the universal audio application control interface view to the application view group.

[0470] 18. The method of any of items 1-17, further comprising:

[0471] at a companion device paired with the device having a memory and one or more processors:

[0472] displaying the adaptive view corresponding to a most recently opened application, wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application view;

[0473] receiving user input to select the affordance; and

[0474] in response to receiving the user input to select the affordance, adding the adaptive view corresponding to the most recently opened application to the preselected application view.

[0475] 19. The method of any of items 1-18, further comprising:

[0476] at a companion device paired with the device having a touchscreen, a memory, and one or more processors:

[0477] displaying a portion of the sequence of the application view group;

[0478] receiving input at a location on the touchscreen where an application view is displayed;

[0479] in response to the input, visually distinguishing the selected application view relative to other application views in the sequence of the application view group;

[0480] detecting movement of the input on the application view that does not interrupt contact with the touchscreen;

[0481] in response to detecting the movement of the input on the application view, moving the selected application view to the second location in the sequence of the application view group;

[0482] detecting interruption of the input with the touchscreen; and

[0483] in response to detecting the interruption of the input with the touchscreen, reordering the application view to the second location in the sequence of the application view group.

[0484] 20. The method of any of items 1-19, further comprising:

[0485] At a companion device of the device, wherein the companion device is paired with the device includes memory and one or more processors:

[0486] receiving input on an application view of the plurality of application views, the input when received causing deletion of the application view from the application view group; and

[0487] in response to the input on the application view, deleting the application view from the application view group.

[0488] 21. An electronic device, comprising:

[0489] a display;

[0490] one or more processors;

[0491] one or more input devices;

[0492] memory; and

[0493] one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, including instructions for:

[0494] receiving user input, the user input when received causing display of a plurality of application views of an application view group; and

[0495] in response to receiving the user input, displaying the plurality of application views of the application view group, wherein the application view group includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0496] 22. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the electronic device to:

[0497] receive user input, the user input when received causing display of a plurality of application views of an application view group; and

[0498] in response to receiving the user input, display the plurality of application views of the application view group, wherein the application view group includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0499] 23. An electronic device, comprising:

[0500] a display;

[0501] one or more input devices;

[0502] means for receiving a user input that, when received, initiates display of a plurality of application views of an application view group; and

[0503] means for displaying the plurality of application views of the application view group in response to receiving the user input, wherein the application view group includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0504] 24. An electronic device, comprising:

[0505] a display;

[0506] one or more processors;

[0507] memory; and

[0508] one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of any of the items 1-20.

[0509] 25. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions which, when executed by one or more processors of an electronic device with a display and one or more input devices, cause the electronic device to perform any of the methods of any of the items 1-20.

[0510] 26. An electronic device, comprising:

[0511] a display;

[0512] means for performing any of the methods of any of the items 1-20.

[0513] 27. An electronic device, comprising:

[0514] a display unit;

[0515] an input unit;

[0516] a display unit configured to display a graphical user interface; and

[0517] a processing unit coupled to the memory unit, the input unit, and the display unit, the processing unit configured to:

[0518] receiving input with the input unit, the input, when received, causing display of a plurality of application views of a group of application views; and

[0519] in response to receiving the user input, displaying the plurality of application views of the group of application views on the display unit, wherein the group of application views includes a preselected application view and an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0520] 28. The electronic device of item 27, wherein the processing unit is further configured to:

[0521] displaying the adaptive view corresponding to the most recently opened application with the display unit, wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application views;

[0522] receiving user input corresponding to selection of the affordance with the input unit; and

[0523] in response to receiving the user input to select the affordance, adding the adaptive view corresponding to the most recently opened application to the preselected application views with the display unit.

[0524] 29. The electronic device of any of items 27 or 28, wherein the group of application views is displayed in a sequence, the processing unit is further configured to:

[0525] displaying the adaptive view at a terminal end of the sequence of the group of application views with the display unit.

[0526] 30. The electronic device of any of items 27-29, wherein the user input is received while displaying an open application that is not one of the preselected application views as a most recently opened application, the processing unit is further configured to:

[0527] in further response to receiving the user input, displaying the adaptive view corresponding to the most recently opened application that is not one of the preselected application views with the display unit,

[0528] wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application views,

[0529] receiving user input corresponding to selection of the affordance with the input unit; and

[0530] in response to receiving the user input to select the affordance, adding, with the display unit, the adaptive view corresponding to the most recently opened application to the preselected application view.

[0531] 31. The electronic device of any of clauses 27-30, wherein the processing unit is further configured to:

[0532] wherein the processing unit is further configured to: detect launching of an application, wherein the adaptive view and the preselected application view of the application view group do not correspond to the launched application; and

[0533] in response to detecting the launching of the application, updating, with the display unit, the adaptive view to correspond to the launched application.

[0534] 32. The electronic device of any of clauses 27-31, wherein the application view group is displayed in a sequence, the processing unit is further configured to:

[0535] in response to receiving user input corresponding to display of the sequence of the application view group, displaying, with the display unit, a subset of application views of the sequence of the application view group, wherein the displaying the subset of application views includes:

[0536] displaying, with the display unit, an application view of a most recently opened application at a center of the sequence of the subset of application views.

[0537] 33. The electronic device of any of clauses 27-32, wherein the application view group is displayed in a sequence, the processing unit is further configured to:

[0538] in response to receiving user input corresponding to display of the sequence of the application view group, displaying, with the display unit, a subset of application views of the sequence of the application view group, wherein the displaying the subset of application views includes:

[0539] displaying, with the display unit, a first application view of the sequence of the application view group at a center of the sequence of the subset of application views; and

[0540] displaying, with the display unit, at least a partial view of a second application view of the sequence of the application view group relative to the first application view in sequence, wherein the second application view is dimmed relative to the first application view.

[0541] 34. The electronic device of any of items 27-33, wherein the processing unit is further configured to:

[0542] display the adaptive view when an application associated with the adaptive view is not open;

[0543] receive, with the input unit, user input corresponding to the adaptive view;

[0544] and

[0545] in response to receiving the user input corresponding to the adaptive view, launch the associated application.

[0546] 35. The electronic device of any of items 27-34, wherein the processing unit is further configured to:

[0547] display, with the display unit, a portion of the sequence of the set of application views;

[0548] receive, with the input unit, input on an application view in a first position in the sequence of the set of application views;

[0549] in response to the input on the application view, visually distinguish the selected application view relative to other application views in the sequence of the set of application views;

[0550] detect, with the input unit, movement of the input on the application view to a second position in the sequence of the set of application views;

[0551] in response to the detected movement of the input on the application view, move, with the display unit, the selected application view to the second position in the sequence of the set of application views;

[0552] detect, with the input unit, an interruption of the input on the application view; and

[0553] in response to the detected interruption of the input on the application view, reorder the application view to the second position in the sequence of the set of application views.

[0554] 36. The electronic device of any of items 27-35, wherein the processing unit is further configured to:

[0555] receive input on an application view of the plurality of application views, the input, when received, causing deletion of the application view from the set of application views; and

[0556] delete the application view from the set of application views in response to the input on the application view.

[0557] 37. The electronic device of any of items 27-36, wherein the processing unit is further configured to:

[0558] receive, with the input unit, a swipe gesture for scrolling through the set of application views; and

[0559] in response to receiving the swipe gesture:

[0560] in accordance with a speed of the swipe gesture being below a predetermined speed threshold, scroll to an adjacent application view; and

[0561] in accordance with the speed of the swipe gesture being above the predetermined speed threshold, scroll through a plurality of application views of the set of application views.

[0562] 38. The electronic device of any of items 27-37, wherein the processing unit is further configured to:

[0563] receive, with the input unit, a user input that, when received, initiates scrolling to an adjacent application view in a set of application views; and

[0564] in response to receiving the user input, scroll to the adjacent application view in the set of application views, wherein the scrolling to the adjacent application view includes a speed reduction based on a predetermined friction coefficient.

[0565] 39. The electronic device of any of items 27-38, wherein the processing unit is further configured to:

[0566] while displaying the plurality of application views in a display area, receive, with the input unit, an input at a bottom edge of the display area that, when received, initiates scrolling of the application views;

[0567] in response to the input at an edge of the display area, move, with the display unit, the application views away from the bottom edge of the display area;

[0568] detect, with the input unit, movement of the input along the bottom edge of the display area; and

[0569] in response to the detected movement of the input along the bottom edge of the display area, scroll through the set of application views.

[0570] 40. The electronic device of any of items 27-39, wherein the processing unit is further configured to:

[0571] while displaying the plurality of application views of the application view group, display, with the display unit, a set of application view markers, wherein each of the application view markers corresponds to a respective application view of the application view group, wherein the application view marker corresponding to the adaptive view is visually distinguished relative to the application view marker corresponding to the preselected application view.

[0572] 41. The electronic device of any of items 27-40, wherein the processing unit is further configured to:

[0573] while displaying the plurality of application views of the application view group, display, with the display unit, a set of application view markers, wherein each of the application view markers corresponds to a respective application view of the application view group;

[0574] highlight, with the display unit, the marker corresponding to the displayed application view;

[0575] receive, with the input unit, a user input, the user input, when received, to scroll to another application view of the application view group;

[0576] in response to receiving the user input, scroll, with the display unit, to the other application view;

[0577] in accordance with scrolling to the other application view, highlight, with the display unit, an application view marker corresponding to the other application view, wherein the highlighting of the application view marker corresponding to the other application view comprises:

[0578] an initial highlight intensity; and

[0579] a final highlight intensity, wherein the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity.

[0580] 42. The electronic device of any of items 27-41, wherein the processing unit is further configured to:

[0581] while an audio application is playing audio content, wherein the audio application includes an application-specific control interface, wherein the application view group does not include an application view corresponding to the audio application:

[0582] update the application view group with a universal audio application control interface view corresponding to a universal audio application control interface, wherein the universal audio application control interface is different from the application-specific control interface;

[0583] receive, with the input unit, a user input on the universal audio application control interface view, the user input, when received, causing initiation of the universal audio application control interface; and

[0584] in response to receiving the user input, display, with the display unit, the universal audio application control interface for controlling playback of the audio content playing on the audio application.

[0585] 43. The electronic device of any of clauses 27-42, wherein the universal audio application control interface view includes an affordance corresponding to adding the universal audio application control interface view to the application view group;

[0586] receive, with the input unit, a user input for selecting the affordance; and

[0587] wherein the processing unit is further configured to, in response to receiving the user input for selecting the affordance, add the universal audio application control interface view to the application view group.

[0588] 44. The electronic device of any of clauses 27-43, wherein the processing unit is further configured to:

[0589] at a companion device having a memory and one or more processors paired with the electronic device:

[0590] display, with the display unit, the adaptive view corresponding to a most recently opened application, wherein the adaptive view includes an affordance corresponding to adding the adaptive view to the preselected application view;

[0591] receive, with the input unit, a user input for selecting the affordance; and

[0592] in response to receiving the user input for selecting the affordance, add the adaptive view corresponding to the most recently opened application to the preselected application view.

[0593] 45. The electronic device of any of clauses 27-44, wherein the processing unit is further configured to:

[0594] at a companion device having a touchscreen, a memory, and one or more processors paired with the electronic device:

[0595] displaying, with the display unit, a portion of the sequence of the set of application views;

[0596] receiving, with the input unit, an input at a location on the touchscreen at which an application view is displayed;

[0597] in response to the input, visually distinguishing, with the display unit, the selected application view from other application views in the sequence of the set of application views;

[0598] detecting, with the input unit, movement of the input on the application view that does not interrupt contact with the touchscreen;

[0599] in response to the detected movement of the input on the application view, moving, with the display unit, the selected application view to the second location in the sequence of the set of application views;

[0600] detecting, with the input unit, interruption of the input with the touchscreen; and

[0601] in response to the detected interruption of the input with the touchscreen, reordering, with the display unit, the application view to the second location in the sequence of the set of application views.

[0602] 46. The electronic device of any of items 27-45, wherein the processing unit is further configured to:

[0603] at a companion device of the electronic device, wherein the companion device paired with the electronic device includes a memory and one or more processors:

[0604] receiving, with the input unit, an input on an application view of the plurality of application views that, when received, initiates deletion of the application view from the set of application views; and

[0605] in response to the input on the application view, deleting, with the display unit, the application view from the set of application views.

[0606] 47. A method comprising:

[0607] at a device having a memory and one or more processors:

[0608] receiving a first user input, the first user input, when received, causing display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view, the plurality of application views of the application view group being displayed in respective first states;

[0609] automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the application view group to a second state;

[0610] updating the at least one application view of the application view group to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied;

[0611] receiving a second user input, the second user input, when received, causing display of the plurality of application views of the application view group; and

[0612] in response to receiving the second user input, displaying the plurality of application views of the application view group including the updated at least one application view updated to the second state.

[0613] 48. The method of item 47, wherein the application view group further includes an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0614] 49. The method of item 47, wherein the updating the at least one application view of the application view group occurs when an application corresponding to the at least one application view is not currently displayed.

[0615] 50. The method of item 47, wherein the updating the at least one application view of the application view group occurs when an application corresponding to the at least one application view is launched.

[0616] 51. The method of item 47, wherein the updating the at least one application view of the application view group occurs when an application corresponding to the at least one application view is inactive.

[0617] 52. The method of item 47, wherein the updating the at least one application view of the application view group occurs when an application corresponding to the at least one application view is unlaunched.

[0618] 53. The method of any of items 47-52, wherein displaying the plurality of application views of the application view group in the second state comprises:

[0619] displaying a first application view in an application view area, wherein the first application view is an updated application view that is focused and centered in the application view area; and

[0620] displaying at least a partial view of a second application view in the application view area, wherein the second application view is sequential relative to the first application view, wherein the second application view is not updated.

[0621] 54. The method of any of items 47-53, further comprising:

[0622] in response to determining that the predetermined criteria is satisfied, updating each of the application views in the application view group.

[0623] 55. The method of any of items 47-54, further comprising:

[0624] determining whether a first timeout has expired since a most recent update of an application view;

[0625] in response to the first timeout expiring, displaying the application view in a dimmed state;

[0626] in accordance with a selection of the application view in the dimmed state, launching an application corresponding to the selected application view;

[0627] determining whether a second timeout has expired since the most recent update of the application view, wherein a duration of the second timeout is longer than a duration of the first timeout;

[0628] in response to the second timeout expiring, displaying an application view that does not include a screenshot of a corresponding application; and

[0629] in accordance with a selection of the application view that does not include the screenshot of the corresponding application, launching the corresponding application.

[0630] 56. The method of any of items 47-55, further comprising:

[0631] while displaying the plurality of application views of the group of application views, displaying a set of application view markers, wherein each of the application view markers corresponds to a respective application view of the group of application views, wherein the application view marker corresponding to the adaptive view is visually distinguished relative to the application view marker corresponding to the preselected application view.

[0632] 57. The method of any of the items 47-56, further comprising:

[0633] while displaying the plurality of application views of the group of application views, displaying a set of application view markers, wherein each of the application view markers corresponds to a respective application view of the group of application views;

[0634] highlighting a marker corresponding to the displayed application view;

[0635] receiving user input, the user input, when received, to scroll to another application view of the group of application views;

[0636] in response to receiving the user input, scrolling to the other application view;

[0637] in accordance with scrolling to the other application view, highlighting an application view marker corresponding to the other application view, wherein the highlighting of the application view corresponding to the other application view comprises:

[0638] an initial highlight intensity; and

[0639] a final highlight intensity, wherein the intensity of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity.

[0640] 58. An electronic device, comprising:

[0641] a display;

[0642] one or more processors;

[0643] one or more input devices;

[0644] memory; and

[0645] one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:

[0646] receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view, the plurality of application views of the application view group being displayed in respective first states;

[0647] automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the application view group to a second state;

[0648] updating, in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied, the at least one application view of the application view group to the second state;

[0649] receiving a second user input that, when received, initiates display of the plurality of application views of the application view group; and

[0650] in response to receiving the second user input, displaying the plurality of application views of the application view group including the updated at least one application view updated to the second state.

[0651] 59. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the electronic device to:

[0652] receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view, the plurality of application views of the application view group being displayed in respective first states;

[0653] automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the application view group to a second state;

[0654] updating, in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied, the at least one application view of the application view group to the second state;

[0655] receiving a second user input that, when received, initiates display of the plurality of application views of the application view group; and

[0656] in response to receiving the second user input, display the plurality of application views of the application view group including the updated at least one application view updated to the second state.

[0657] 60. An electronic device, comprising:

[0658] a display;

[0659] one or more input devices;

[0660] means for receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view, the plurality of application views of the application view group being displayed in respective first states;

[0661] means for automatically determining, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the application view group to a second state;

[0662] means for updating the at least one application view of the application view group to the second state in accordance with the automatic determination, without user input, that the predetermined criterion is satisfied;

[0663] means for receiving a second user input that, when received, initiates display of the plurality of application views of the application view group; and

[0664] in response to receiving the second user input, display the plurality of application views of the application view group including the updated at least one application view updated to the second state.

[0665] 61. An electronic device, comprising:

[0666] a display;

[0667] one or more processors;

[0668] memory; and

[0669] one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of any of the items 47-57.

[0670] 62. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the electronic device to perform any of the methods of 47-57.

[0671] 63. An electronic device, comprising:

[0672] a display;

[0673] means for performing any of the methods of 47-57.

[0674] 64. An electronic device, comprising:

[0675] a display unit;

[0676] an input unit;

[0677] a display unit configured to display a graphical user interface; and

[0678] a processing unit coupled to the memory unit, the input unit, and the display unit, the processing unit configured to:

[0679] receive, with the input unit, a first user input that, when received, initiates display of a plurality of application views of a group of application views, wherein the group of application views includes a preselected application view, the plurality of application views of the group of application views being displayed in respective first states;

[0680] automatically determine, without user input, whether a predetermined criterion is satisfied for updating at least one application view of the group of application views to a second state;

[0681] update the at least one application view of the group of application views to the second state in accordance with the automatic determination that the predetermined criterion is satisfied without user input;

[0682] receive, with the input unit, a second user input that, when received, initiates display of the plurality of application views of the group of application views; and

[0683] in response to receiving the second user input, display, with the display unit, the plurality of application views of the group of application views including the updated at least one application view updated to the second state.

[0684] 65. The electronic device of clause 64, wherein the set of application views further includes an adaptive view corresponding to a most recently opened application that is not one of the preselected application views.

[0685] 66. The electronic device of clause 64, wherein the updating the at least one application view of the set of application views occurs when an application corresponding to the at least one application view is not currently displayed.

[0686] 67. The electronic device of clause 64, wherein the updating the at least one application view of the set of application views occurs when an application corresponding to the at least one application view is launched.

[0687] 68. The electronic device of clause 64, wherein the updating the at least one application view of the set of application views occurs when an application corresponding to the at least one application view is inactive.

[0688] 69. The electronic device of clause 64, wherein the updating the at least one application view of the set of application views occurs when an application corresponding to the at least one application view is unlaunched.

[0689] 70. The electronic device of any of clauses 64-69, wherein displaying the plurality of application views of the set of application views in the second state includes:

[0690] displaying, with the display unit, a first application view in an application view area, wherein the first application view is an updated application view that is focused and centered in the application view area; and

[0691] displaying, with the display unit, at least a partial view of a second application view in the application view area, wherein the second application view is sequential relative to the first application view, wherein the second application view is not updated.

[0692] 71. The electronic device of any of clauses 64-70, the processing unit is further configured to:

[0693] update each of the application views in the set of application views in response to determining that the predetermined criteria is satisfied.

[0694] 72. The electronic device of any of clauses 64-71, the processing unit is further configured to:

[0695] determine whether a first timeout has expired since a most recent update of an application view;

[0696] in response to the first timeout expiring, display the application view in a dimmed state with the display unit;

[0697] in accordance with a selection of the application view in the dimmed state, launch an application corresponding to the selected application view;

[0698] determine whether a second timeout has expired since the most recent update of the application view, wherein the second timeout has a duration that is longer than a duration of the first timeout;

[0699] in response to the second timeout expiring, display an application view that does not include a screenshot of a corresponding application with the display unit; and

[0700] in accordance with a selection of the application view that does not include the screenshot of the corresponding application, launch the corresponding application.

[0701] 73. The electronic device of any of items 64-72, the processing unit further configured to:

[0702] while displaying the plurality of application views of the group of application views, display a set of application view icons, wherein each of the application view icons corresponds to a respective application view of the group of application views, wherein the application view icon corresponding to the adaptive view is visually distinguished from the application view icons corresponding to the preselected application views.

[0703] 74. The electronic device of any of items 64-73, the processing unit further configured to:

[0704] while displaying the plurality of application views of the group of application views, display a set of application view icons, wherein each of the application view icons corresponds to a respective application view of the group of application views;

[0705] highlight the icon corresponding to the displayed application view;

[0706] receive a user input, the user input, when received, to scroll to another application view of the group of application views;

[0707] in response to receiving the user input, scroll to the other application view;

[0708] highlighting an application view corresponding to the other application view, wherein the highlighting the application view corresponding to the other application view includes:

[0709] an initial highlight intensity; and

[0710] a final highlight intensity, wherein the highlight of the highlighting increases during a transition from the initial highlight intensity to the final highlight intensity.

[0711] 75. A method, comprising:

[0712] at a device with one or more processors and memory:

[0713] displaying a watch face;

[0714] receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view;

[0715] in response to receiving the first user input, displaying the plurality of application views of the application view group;

[0716] receiving a second user input on an application view of the displayed plurality of application views that, when received, initiates launch of an application corresponding to the application view selected by the second user input; and

[0717] in response to receiving the second user input, replacing the displayed plurality of application views with display of a user interface of the launched application.

[0718] 76. The method of item 75, further comprising:

[0719] receiving a swipe gesture for scrolling through the application view group; and

[0720] in response to receiving the swipe gesture, scrolling through the application view group and replacing the initially displayed plurality of application views with a second application view group.

[0721] 77. The method of item 75 or 76, further comprising:

[0722] replacing a displayed watch face with the display of the plurality of application views of the application view group.

[0723] 78. An electronic device, comprising:

[0724] a display;

[0725] one or more processors;

[0726] one or more input devices;

[0727] memory; and

[0728] one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:

[0729] displaying a watch face;

[0730] receiving a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view;

[0731] in response to receiving the first user input, displaying the plurality of application views of the application view group;

[0732] receiving a second user input on an application view of the displayed plurality of application views that, when received, initiates launch of an application corresponding to the application view selected by the second user input; and

[0733] in response to receiving the second user input, replacing the displayed plurality of application views by displaying a user interface of the launched application.

[0734] 79. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the electronic device to:

[0735] display a watch face;

[0736] receive a first user input that, when received, initiates display of a plurality of application views of an application view group, wherein the application view group includes a preselected application view;

[0737] in response to receiving the first user input, display the plurality of application views of the application view group;

[0738] receive a second user input on an application view of the displayed plurality of application views that, when received, initiates launch of an application corresponding to the application view selected by the second user input; and

[0739] In response to receiving the second user input, the displayed plurality of application views are replaced by displaying the user interface of the launched application.

[0740] 80. An electronic device comprising:

[0741] monitor;

[0742] One or more input devices;

[0743] Device for displaying the dial;

[0744] A device for receiving first user input, which, when received, triggers the display of multiple application views in an application view group, wherein the application view group includes pre-selected application views.

[0745] A means for displaying the plurality of application views of the application view group in response to receiving the first user input;

[0746] A means for receiving a second user input on an application view of the plurality of displayed application views, wherein the second user input, upon being received, triggers the launch of an application corresponding to the application view selected by the second user input; and

[0747] A means for replacing the displayed plurality of application views by displaying the user interface of the launched application in response to receiving the second user input.

[0748] 81. An electronic device, comprising:

[0749] monitor;

[0750] One or more processors;

[0751] Memory; and

[0752] One or more programs, wherein the one or more programs are stored in memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods described according to items 75 to 77.

[0753] 82. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of an electronic device having a display and one or more input devices, cause the electronic device to perform any of the methods described in items 75-77.

[0754] 83. An electronic device, comprising:

[0755] monitor;

[0756] An apparatus for performing any of the methods of embodiments 75-77.

[0757] 84. An electronic device, comprising:

[0758] a display unit;

[0759] an input unit;

[0760] a display unit configured to display a graphical user interface; and

[0761] a processing unit coupled to the memory unit, the input unit, and the display unit, the processing unit configured to:

[0762] display a watch face with the display unit;

[0763] receive a first user input with the input unit, the first user input, when received, eliciting display of a plurality of application views of an application view group, wherein

[0764] the application view group includes a preselected application view;

[0765] in response to receiving the first user input, display the plurality of application views of the application view group with the display unit;

[0766] receive a second user input on an application view of the displayed plurality of application views with the input unit, the second user input, when received, eliciting launch of an application corresponding to the application view selected by the second user input; and

[0767] in response to receiving the second user input, replace the displayed plurality of application views by displaying a user interface of the launched application.

[0768] 85. The electronic device of claim 84, the processing unit further configured to:

[0769] receive a swipe gesture for scrolling through the application view group; and

[0770] in response to receiving the swipe gesture, scroll through the application view group and replace the initially displayed plurality of application views with a second application view group.

[0771] 86. The electronic device of either of embodiments 84 or 85, the processing unit further configured to:

[0772] by the display of the plurality of application views of the application view group.

Claims

1. A method, comprising: at a device with one or more processors and memory: displaying a set of ordered graphical objects, the set of ordered graphical objects including a first graphical object positioned at a first position between a second graphical object and a third graphical object, wherein the first graphical object positioned at the first position is fully displayed, the second graphical object is partially displayed, and the third graphical object is partially displayed; while displaying the set of ordered graphical objects: receiving an input on the first graphical object positioned at the first position; in response to receiving the input on the first graphical object: fully displaying the second graphical object and the third graphical object; and removing the first graphical object from the set of ordered graphical objects; while a contact on the first graphical object is maintained, detecting movement of the input; in response to detecting the movement of the input, displacing the set of ordered graphical objects to display a fourth graphical object in the set of ordered graphical objects; detecting an end of the input; and in response to detecting the end of the input: displaying the first graphical object at a second position adjacent to the fourth graphical object in the set of ordered graphical objects; and stopping display of at least a portion of the fourth graphical object while maintaining display of at least a remaining portion of the fourth graphical object.

2. The method of claim 1, wherein selecting the first graphical object includes visually distinguishing the first graphical object relative to at least one of the second graphical object and the third graphical object.

3. The method of claim 1, further comprising: in response to receiving the input on the graphical object further includes reducing a size of at least one of the second graphical object and the third graphical object.

4. The method of claim 1, further comprising: while displacing the set of ordered graphical objects, displaying a representation of the first graphical object with a marker indicating an ordinal position of the first graphical object among the set of ordered graphical objects.

5. The method of claim 1, further comprising: in response to receiving the input on the first graphical object further includes increasing a transparency of the first graphical object relative to at least one of the second graphical object and the third graphical object.

6. The method of claim 1, further comprising: in response to receiving the input on the first graphical object further includes vertically offsetting the first graphical object relative to at least one of the second graphical object and the third graphical object.

7. The method of claim 1, further comprising: in response to receiving the input on the first graphical object further includes fully displaying a fifth graphical object.

8. The method of claim 7, further comprising: in response to detecting the end of the input further includes stopping display of at least a portion of the fifth graphical object while maintaining display of at least a remaining portion of the fifth graphical object.

9. An electronic device, comprising: a display; one or more processors; one or more input devices; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: ​ displaying a set of ordered graphical objects, the set of ordered graphical objects including a first graphical object positioned at a first location between a second graphical object and a third graphical object, wherein the first graphical object positioned at the first location is fully displayed, the second graphical object is partially displayed, and the third graphical object is partially displayed; while displaying the set of ordered graphical objects: receiving an input on the first graphical object positioned at the first location; in response to receiving the input on the first graphical object: fully displaying the second graphical object and the third graphical object; and removing the first graphical object from the set of ordered graphical objects; while maintaining contact on the first graphical object, detecting movement of the input; in response to detecting the movement of the input, displacing the set of ordered graphical objects to display a fourth graphical object in the set of ordered graphical objects; detecting an end of the input; and in response to detecting the end of the input: displaying the first graphical object at a second location adjacent to the fourth graphical object in the set of ordered graphical objects; and stopping display of at least a portion of the fourth graphical object while maintaining display of at least a remaining portion of the fourth graphical object.

10. The electronic device of claim 9, wherein selecting the first graphical object includes visually distinguishing the first graphical object relative to at least one of the second graphical object and the third graphical object.

11. The electronic device of claim 9, the one or more programs including instructions for: in response to receiving the input on the graphical object further including reducing a size of at least one of the second graphical object and the third graphical object.

12. The electronic device of claim 9, the one or more programs including instructions for: while displacing the set of ordered graphical objects, displaying a representation of the first graphical object with a marker indicating an ordinal position of the first graphical object among the set of ordered graphical objects.

13. The electronic device of claim 9, the one or more programs including instructions for: in response to receiving the input on the first graphical object further including increasing a transparency of the first graphical object relative to at least one of the second graphical object and the third graphical object.

14. The electronic device of claim 9, the one or more programs including instructions for: in response to receiving the input on the first graphical object further including vertically offsetting the first graphical object relative to at least one of the second graphical object and the third graphical object.

15. The electronic device of claim 9, the one or more programs including instructions for: in response to receiving the input on the first graphical object further including fully displaying a fifth graphical object.

16. The electronic device of claim 15, the one or more programs including instructions for: in response to detecting the end of the input further including stopping display of at least a portion of the fifth graphical object while maintaining display of at least a remaining portion of the fifth graphical object. ​ 17. A computer-readable storage medium storing one or more programs for execution by one or more processors of an electronic device with a display and one or more input devices, the one or more programs comprising instructions to: display a ranked set of graphical objects, the ranked set of graphical objects including a first graphical object positioned at a first location between a second graphical object and a third graphical object, wherein the first graphical object positioned at the first location is fully displayed, the second graphical object is partially displayed, and the third graphical object is partially displayed; while displaying the ranked set of graphical objects: receive an input on the first graphical object positioned at the first location; in response to receiving the input on the first graphical object: fully display the second graphical object and the third graphical object; and remove the first graphical object from the ranked set of graphical objects; while the contact on the first graphical object is maintained, detect movement of the input; in response to detecting the movement of the input, shift the ranked set of graphical objects to display a fourth graphical object in the ranked set of graphical objects; detect an end of the input; and in response to detecting the end of the input: display the first graphical object at a second location adjacent to the fourth graphical object in the ranked set of graphical objects; and stop displaying at least a portion of the fourth graphical object while maintaining display of at least a portion of the fourth graphical object.

18. The computer-readable storage medium of claim 17, wherein selecting the first graphical object includes visually distinguishing the first graphical object relative to at least one of the second graphical object and the third graphical object.

19. The computer-readable storage medium of claim 17, the one or more programs comprising instructions to: in response to receiving the input on the graphical object further includes reducing a size of at least one of the second graphical object and the third graphical object.

20. The computer-readable storage medium of claim 17, the one or more programs comprising instructions to: while shifting the ranked set of graphical objects, display a representation of the first graphical object with a marker indicating an ordinal position of the first graphical object among the ranked set of graphical objects.

21. The computer-readable storage medium of claim 17, the one or more programs comprising instructions to: in response to receiving the input on the first graphical object further includes increasing a transparency of the first graphical object relative to at least one of the second graphical object and the third graphical object.

22. The computer-readable storage medium of claim 17, the one or more programs comprising instructions to: in response to receiving the input on the first graphical object further includes vertically offsetting the first graphical object relative to at least one of the second graphical object and the third graphical object.

23. The computer-readable storage medium of claim 17, the one or more programs comprising instructions to: ​ ​ ​ In response to receiving the input on the first graphical object, further comprising fully displaying a fifth graphical object.

24. The computer-readable storage medium of claim 23, the one or more programs including instructions for: In response to detecting an end of the input, further comprising ceasing display of at least a portion of the fifth graphical object while maintaining display of at least a remaining portion of the fifth graphical object.

25. An electronic device, comprising: a display; means for performing any of the methods of claims 1-8.

Images