Content scroll bar with real time indication

Abstract

In some embodiments, an electronic device displays a playback user interface configured to playback content on the electronic device. When displaying the playback user interface configured to playback the content on the electronic device, the electronic device displays a swipe bar for navigating in the content, wherein the swipe bar includes: a visual indication of the current playback position within the content; and one or more playback time indications, the one or more playback time indications including a time value based on the current playback position within the content. The corresponding playback time indication in the one or more playback time indications is based on the time of day at the electronic device, and the amount of time it takes to play the content from the current playback position to the end of the content at the corresponding content playback speed.

Description

[0001] Description of the case

[0002] This application is a divisional application of the invention patent application with international application number PCT / US2017 / 029454, international application date April 25, 2017, and Chinese national application number 201780034115.4. Technical Field

[0003] The present invention generally relates to electronic devices that allow navigation within and playback of content, and user interaction with such devices. Background Art

[0004] In recent years, the interaction between users and electronic devices has increased significantly. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, etc.

[0005] In some cases, such devices may access content (e.g., music, movies, etc.), and user interaction with such devices requires viewing and using a swipe bar to navigate through the content. Enhancing these interactions may improve the user's experience with the device and reduce user interaction time, which is particularly important when the input device is battery powered. Summary of the invention

[0006] The embodiments described in the present disclosure relate to one or more electronic devices that display a swipe bar for browsing content items, which includes one or more time indications about the "real" time that the electronic device is in, and one or more operations related to the above that the electronic device optionally performs. A comprehensive description of the embodiments is provided in the drawings and detailed description, and it should be understood that the invention content provided above does not limit the scope of the present disclosure in any way. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, in which like reference numerals designate corresponding parts throughout the several views.

[0008] Figure 1A is a block diagram illustrating a multifunction device with a touch-sensitive display according to some embodiments of the present disclosure.

[0009] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments of the present disclosure.

[0010] Figure 2 A multifunction device with a touch screen according to some embodiments of the present disclosure is shown.

[0011] Figure 3is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments of the present disclosure.

[0012] Figure 4 An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to some embodiments of the present disclosure.

[0013] FIG. 5A to FIG. 5B A block diagram is shown of an exemplary architecture for a device according to some embodiments of the present disclosure.

[0014] Figures 6A to 6Z An exemplary method is shown in which a swipe bar is presented with an indication of an “actual” playback time in accordance with some embodiments of the present disclosure.

[0015] FIG. 7A to FIG. 7G is a flow chart illustrating a method of presenting a swipe bar with an indication of “actual” playback time according to some embodiments of the present disclosure.

[0016] Figure 8 is a functional block diagram of an electronic device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0017] In the following description of the embodiments, reference will be made to the accompanying drawings, which form a part of the following description and in which specific embodiments of optional implementation are shown by way of example. It should be understood that other embodiments are optionally used and structural changes are optionally made without departing from the scope of the disclosed embodiments. In addition, although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch 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. Both the first touch and the second touch are touches, but they are not the same touch.

[0018] The terms used in the description of various embodiments described herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various embodiments described and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the items listed in association. It will also be understood that the terms "including" and / or "comprising" are used in this specification to specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0020] Exemplary Devices

[0021] 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 communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Other portable electronic devices are optionally used, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer or television with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the device does not have a touch screen display and / or a touch pad, but is capable of outputting display information (such as a user interface of the present disclosure) for display on an independent display device, and is capable of receiving input information from an independent input device with one or more input mechanisms (such as one or more buttons, a touch screen display and / or a touch pad). In some embodiments, the device has a display, but is capable of receiving input information from an independent input device with one or more input mechanisms (such as one or more buttons, a touch screen display and / or a touch pad).

[0022] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, a mouse, and / or a joystick. In addition, as described above, it should be understood that the described electronic device, display, and touch-sensitive surface are optionally distributed among two or more devices. Therefore, as used in the present disclosure, information displayed on or by an electronic device is optionally used to describe information output by the electronic device for display on an independent display device (touch-sensitive or non-touch-sensitive). Similarly, as used in the present disclosure, input received on an electronic device (e.g., touch input received on a touch-sensitive surface of an electronic device) is optionally used to describe input received on an independent input device, and the electronic device receives input information from the independent input device.

[0023] The device typically supports a variety of applications, such as one or more of the following applications: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, a television channel browsing application, and / or a digital video player application.

[0024] Various applications executed 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 and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

[0025] Attention is now directed to embodiments of a portable or non-portable device having a touch-sensitive display, although the device need not include a touch-sensitive display or a general display as described above. Figure 1A 1 is a block diagram showing a portable or non-portable multifunction device 100 with a touch-sensitive display 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a touch-sensitive display system. The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0026] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in pressure units). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0027] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. While such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when tactile outputs are described as corresponding to a particular sensory perception of a user (e.g., "release click," "press click," "roughness"), unless otherwise stated, the generated tactile outputs correspond to physical displacements of the device or a component thereof that would generate the described sensory perceptions for a typical (or average) user.

[0028] It should be understood that device 100 is only one example of a portable or non-portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown in the embodiment are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits. Figure 1A The various components shown in are optionally implemented on two or more devices; for example, a display and audio circuitry on a display device, a touch-sensitive surface on an input device, and the remaining components on device 100. In such embodiments, device 100 optionally communicates with the display device and / or input device to facilitate operation of the system as described in the present disclosure, and the various display and / or input-related components described herein remain in device 100, or are optionally included in the display and / or input device as appropriate.

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

[0030] Peripheral interface 118 may be used to couple the device's input and output peripherals to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.

[0031] In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0032] RF (radio frequency) circuit 108 receives and transmits RF signals, also called electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memory, etc. RF circuit 108 optionally communicates with networks and other devices through wireless communications, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communication (NFC) fields, such as by detecting through a short-range communication radio component. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0033] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to the human ear. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headphone jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0034] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile 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 or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include a push button (e.g., Figure 2 206).

[0035] A quick press of the push button optionally unlocks the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0036] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. As described above, the touch-sensitive operation and display operation of the touch-sensitive display 112 are optionally separated from each other, so that the display device is used for display purposes, and the touch-sensitive surface (whether it is a display or not) is used for input detection purposes, and the components and functions described are modified accordingly. However, for the sake of brevity, the following description is provided with reference to the touch-sensitive display. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual outputs or all of the visual outputs correspond to user interface objects.

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

[0038] The 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. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as the . iPod and Discovery technology.

[0039] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive touch pad 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) and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while a touch-sensitive track pad does not provide visual output.

[0040] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 051,964, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application Ser. No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0041] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0043] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault 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 a portable or non-portable device.

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

[0045] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the rear of device 100 opposite to touch screen display 112 located on the front of device 100.

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

[0047] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

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

[0049] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

[0050] The 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 facilitating communication between various hardware components and software components.

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

[0052] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on a touch pad.

[0053] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen display can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0054] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press 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 press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0055] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. 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.

[0056] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application program, etc., and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to be output to the display controller 156.

[0057] Haptic feedback module 133 includes various software components for generating instructions used by one or more tactile output generators 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

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

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

[0060] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0061] Contacts module 137 (sometimes called address book or contact list);

[0062] Telephone module 138;

[0063] Video conferencing module 139;

[0064] Email client module 140;

[0065] Instant messaging (IM) module 141;

[0066] Fitness support module 142;

[0067] A camera module 143 for still images and / or video images;

[0068] Image management module 144;

[0069] Video player module;

[0070] Music player module;

[0071] Browser module 147;

[0072] Calendar module 148;

[0073] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and a user-created widget 149-6;

[0074] A widget creator module 150 for forming a user-created widget 149-6;

[0075] Search module 151;

[0076] Video and music player module 152, which merges the video player module and the music player module;

[0077] Notepad module 153;

[0078] Map module 154; and / or

[0079] Online video module 155.

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

[0081] In conjunction with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating telephone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or instant messaging 141; and the like.

[0082] 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, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0083] In combination with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, touch / motion module 130, graphics module 132, text input module 134, contact module 137 and telephone module 138, video conferencing module 139 includes executable instructions for initiating, executing and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0084] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0085] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and / or received instant message optionally includes graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging service (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0086] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0087] In conjunction with the touch screen 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, touch / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, or deleting still images or videos from memory 102.

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

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

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

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

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

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

[0094] 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 a 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), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

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

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

[0097] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on 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 on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

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

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

[0100] A predefined set of functions that are performed exclusively through a touch screen and / or a touch pad optionally includes navigation between user interfaces. In some embodiments, the touch pad, when touched by a user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, a home menu, or a root menu. In such embodiments, a touch pad 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 touch pad.

[0101] Figure 1B 1 is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370( Figure 3 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

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

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

[0104] 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 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

[0106] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.

[0107] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

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

[0109] Hit view determination module 172 receives information related to sub-events of touch-based gestures. 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 where the sub-events should be processed. 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 that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source identified as the hit view.

[0110] 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 the sub-event are actively participating views, and thereby determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0111] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

[0112] 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 (such as contact / motion module 130) stored in memory 102.

[0113] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit (not shown) or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

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

[0115] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (e.g., from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

[0117] In some embodiments, event definition 187 includes definitions of events for associated 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 displaying 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 corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object that triggered the hit test.

[0118] In some embodiments, the definition of the corresponding event 187 also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0119] When a corresponding event recognizer 180 determines that a series of sub-events does not match any event in event definition 186, the corresponding 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.

[0120] In some embodiments, the corresponding event identifier 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event identifiers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event identifiers interact or can interact with each other. In some embodiments, 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.

[0121] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 issues a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.

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

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

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

[0125] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input using input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0126] Figure 2 A portable or non-portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. As described above, the multifunction device 100 is described as having various illustrated structures (such as a touch screen 112, a speaker 111, an accelerometer 168, a microphone 113, etc.); however, it should be understood that these structures optionally reside on separate devices. For example, display-related structures (e.g., a display, a speaker, etc.) and / or functions optionally reside on a separate display device, input-related structures (e.g., a touch-sensitive surface, a microphone, an accelerometer, etc.) and / or functions optionally reside on a separate input device, and the remaining structures and / or functions optionally reside on the multifunction device 100.

[0127] Touch screen 112 optionally displays one or more graphics within user interface (UI) 200. In this embodiment and in other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the accompanying drawings) or using one or more stylus 203 (not drawn to scale in the accompanying drawings). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select a graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

[0129] In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on and off and locking the device for power, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button pressed for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through the microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0130] Figure 3300 is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to some embodiments. As described above, the device 300 does not have to include a display and a touch-sensitive surface, on the contrary, in some embodiments, it is optionally communicated with the display and the touch-sensitive surface on other devices. In addition, the device 300 does not have to be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device (such as a TV or a set-top box), a navigation device, an educational device (such as a children's learning toy), a game system or a control device (for example, a home or industrial controller). The device 300 typically includes one or more processing units (CPU) 310, one or more network or other communication interfaces 360, a memory 370 and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes a circuit (sometimes called a chipset) that interconnects system components and controls the communication between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touch pad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to the above referenced Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or contact intensity sensors (similar to the above referenced Figure 1A The one or more contact force sensors 165 described herein)). The memory 370 includes a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes a non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located away from the one or more CPUs 310. In some embodiments, the memory 370 stores programs, modules, and data structures, or subsets thereof, which are similar to those of the portable or non-portable multifunction device 100 ( Figure 1A ) stored in the memory 102 of the portable or non-portable multifunction device 100. In addition, the memory 370 optionally stores additional programs, modules, and data structures that are not present in the memory 102 of the portable or non-portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable or non-portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0131] Figure 3 Each of the above-mentioned identified elements in is optionally stored in one or more of the previously mentioned memory devices. Each module in the above-mentioned identified module corresponds to a group of instructions for performing the above-mentioned functions. The above-mentioned identified modules or programs (that is, instruction sets) need not be implemented as independent software programs, processes or modules, so the various subsets of these modules are optionally combined in various embodiments or otherwise rearranged. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0132] Figure 4 A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3 Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors) for detecting intensity of contacts on touch-sensitive surface 451, and / or one or more tactile output generators for generating tactile output for a user of device 300.

[0133] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4 In some embodiments, the touch-sensitive surface (e.g., Figure 4 451) has a main axis (e.g., Figure 4 452 in ), which corresponds to the main axis on the display (e.g., 450) (e.g., Figure 4 According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., Figure 4 460 and 462 in FIG. 4 ), the location of the contact corresponds to a corresponding location on the display (e.g., in FIG. Figure 4 460 corresponds to 468, and 462 corresponds to 470). Thus, when a touch-sensitive surface (e.g., Figure 4 451) and the display of a multi-function device ( Figure 4 When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0134] In addition, 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 input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of 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 detecting contact, followed by ceasing to detect 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 contact are optionally used simultaneously.

[0135] 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 implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor rests over a particular user interface element (e.g., a button, window, slider, or other user interface element), a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4 In the case where an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, a particular user interface element is adjusted according to the detected input. In the case where a touch-sensitive surface 451 in the display is included that enables direct interaction with user interface elements on the touch-sensitive surface 451, a touch-sensitive surface 451 in the display is configured to adjust the specific user interface element according to the detected input. Figure 1AIn some implementations of a touch-sensitive display system 112 in a touchscreen, a contact detected on the touch screen acts as a "focus selector" such that when input (e.g., a press input by a contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touchscreen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touchscreen display) that is controlled by the user to convey the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0136] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity 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 whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0137] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0138] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a 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 the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding 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).

[0139] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0140] Figure 5A A block diagram of an exemplary architecture for a device 500 according to some embodiments of the present disclosure is shown. Figure 5A In the embodiment of the present invention, media content or other content is optionally received by the device 500 via a network interface 502, which is optionally a wireless connection or a wired connection. One or more processors 504 optionally execute any number of programs stored in the memory 506 or storage device, which optionally include instructions for performing one or more of the methods and / or processes (e.g., method 700) described herein.

[0141] In some embodiments, the display controller 508 causes various user interfaces of the present disclosure to be displayed on the display 514. In addition, input to the device 500 is optionally provided by a remote control 510 via a remote control interface 512, which is optionally a wireless or wired connection. In some embodiments, the input to the device 500 is provided by a multifunction device 511 (e.g., a smart phone) on which a remote application is running that configures the multifunction device to simulate remote control functionality, as described in more detail below. In some embodiments, the multifunction device 511 corresponds to Figure 1A and Figure 2 The device 100 and Figure 3 One or more devices in the device 300 in the device. It should be understood that Figure 5A The embodiments are not meant to limit the features of the device disclosed herein, and other components that facilitate other features described in the present disclosure are optionally included in the Figure 5A In some embodiments, the device 500 optionally corresponds to Figure 1A and Figure 2 The multifunctional device 100 and Figure 3 One or more devices in the device 300; the network interface 502 optionally corresponds to Figure 1A and Figure 2 RF circuit 108, external port 124 and peripheral device interface 118 in Figure 3 One or more of the network communication interfaces 360 in; the processor 504 optionally corresponds to one or more of the following: Figure 1A One or more processors 120 and Figure 3 The one or more CPUs 310 in the display controller 508 optionally correspond to one or more of the following: Figure 1A The display controller 156 and Figure 3 The I / O interface 330 in the memory 506 optionally corresponds to one or more of the following: Figure 1A The memory 102 and Figure 3 The memory 370 in the remote control interface 512 optionally corresponds to one or more of the following: Figure 1A The peripheral device interface 118 and the I / O subsystem 106 (and / or its components) in Figure 3 The I / O interface 330 in the remote control 510 optionally corresponds to and / or includes one or more of the following: Figure 1Aspeakers 111, touch-sensitive display system 112, microphone 113, one or more optical sensors 164, one or more contact intensity sensors 165, one or more tactile output generators 167, other input control devices 116, one or more accelerometers 168, proximity sensor 166, and I / O subsystem 106, and Figure 3 The keyboard / mouse 350, the touch pad 355, the one or more tactile output generators 357 and the one or more contact intensity sensors in Figure 4 ; and display 514 optionally corresponds to one or more of the following: Figure 1A and 2 a touch-sensitive display system 112 in FIG. 1 , and Figure 3 Display 340 in.

[0142] Figure 5B An exemplary structure of a remote controller 510 according to some embodiments of the present disclosure is shown. In some embodiments, the remote controller 510 optionally corresponds to Figure 1A and Figure 2 The multifunctional device 100 and Figure 3 The remote control 510 optionally includes a touch-sensitive surface 451. In some embodiments, the touch-sensitive surface 451 is edge-to-edge (e.g., it extends to the edge of the remote control 510, so that there is little or no surface of the remote control 510 between the touch-sensitive surface 451 and one or more edges of the remote control 510, such as Figure 5BAs described previously in this disclosure, touch-sensitive surface 451 is optionally capable of sensing contact and contact intensity (e.g., clicking on touch-sensitive surface 451). In addition, touch-sensitive surface 451 optionally includes a mechanical actuator for providing physical button click functionality (e.g., touch-sensitive surface 451 is "clickable" to provide corresponding input to device 500). Remote control 510 also optionally includes buttons 516, 518, 520, 522, 524, and 526. Buttons 516, 518, 520, 522, 524, and 526 are optionally mechanical buttons or mechanical button alternatives that are capable of sensing contact or pressing with such buttons to initiate one or more corresponding actions, for example, on device 500. In some embodiments, a user's selection of a "menu" button 516 navigates the device 500 backward in a currently executed application or currently displayed user interface (e.g., backward to a user interface displayed before the currently displayed user interface), or navigates the device 500 to a user interface one level higher than the currently displayed user interface. In some embodiments, a user's selection of a "home" button 518 navigates the device 500 from any user interface displayed on the device 500 to a main, home, or root user interface (e.g., to the home screen of the device 500, which optionally includes one or more applications accessible on the device 500). In some embodiments, a user's selection of a "play / pause" button 520 switches back and forth between playing and pausing a currently playing content item on the device 500 (e.g., if a content item is playing on the device 500 when the "play / pause" button 520 is selected, the content item is optionally paused, and if a content item is paused on the device 500 when the "play / pause" button 520 is selected, the content item is optionally played). In some embodiments, user selection of the "+" 522 or "-" 524 buttons increases or decreases the volume of audio reproduced by the device 500 (e.g., the volume of a content item currently playing on the device 500), respectively. In some embodiments, user selection of the "audio input" button 526 allows the user to provide audio input (e.g., voice input) to the device 500, optionally to a voice assistant on the device. In some embodiments, the remote control 510 includes a microphone via which the user provides audio input to the device 500 when the "audio input" button 526 is selected. In some embodiments, the remote control 510 includes one or more accelerometers for detecting information about the motion of the remote control.

[0143] User interface and associated processes

[0144] Content scroll bar

[0145] Users interact with electronic devices in a variety of different ways, including interacting with content (e.g., music, movies, etc.) available (e.g., stored or otherwise accessible) on electronic devices. In some cases, users want to know the current playback position in the content they are watching, the end time of the content, and / or expect to skip (e.g., fast forward, rewind, etc.) the content item. The swipe bar for browsing content optionally provides such information and functions. However, the swipe bar is usually displayed as having a time indication relative to the content played on the electronic device (e.g., with reference to the beginning of the content, the end of the content, the current playback position in the content, etc.). Therefore, for example, the swipe bar optionally indicates that the content has 90 minutes remaining. The embodiment described below provides an electronic device displaying a swipe bar with one or more time indications relative to the actual time on the electronic device (rather than relative to the content played on the electronic device), so that the user can more easily determine how the various positions in the content are related to the time of the day at the electronic device, thereby enhancing the interaction between the user and the electronic device. Enhancing the interaction with the device reduces the amount of time required for the user to perform the operation, thereby reducing the power consumption of the device and extending the battery life of the battery-powered device. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.

[0146] Figures 6A to 6Z An exemplary method in which a swipe bar is presented with an "actual" playback time indication according to some embodiments of the present disclosure is shown. The embodiments in these figures are used to illustrate the process described below, including reference to FIG. 7A to FIG. 7G Describe the process.

[0147] It should be noted that Figures 6A to 6Z The examples shown in the relate to electronic devices that display information on a non-touch-sensitive display, but it should be understood that the electronic device may instead display information on a display with touch-sensitive capabilities (e.g., a touch screen). For example, the electronic device may include a touch screen, or the electronic device may be capable of outputting display information for display on a separate touch screen, as described earlier in this disclosure—in which case the display described below optionally corresponds to the above-described touch screen, and the input described below is optionally detected on the touch screen.

[0148] Fig. 6A An exemplary display 514 is shown. Display 514 optionally displays one or more user interfaces including various content. Fig. 6A In the example shown, the display 514 displays on the electronic device (e.g., Figure 5AThe content playback application user interface 602 of the content playback application running on the electronic device 500 of the embodiment of the present invention is shown, and the display 514 is part of the electronic device or the display 514 is connected to the electronic device. The content playback user interface 602 is configured to play back one or more content items on the electronic device in various playback states (e.g., pause, rewind, fast forward, play, etc.). Fig. 6A In the example of FIG. 6 , the content playback user interface 602 is displaying a content item that is played back at a 1× playback speed.

[0149] Fig. 6A Also shown in FIG. 6 is a touch-sensitive surface 451 and a clock 604. Touch-sensitive surface 451 is optionally a touch-sensitive surface on a second electronic device that is configured to control the electronic device, such as a touch-sensitive surface configured to control the electronic device (e.g., Figure 1A Device 100, Figure 3 300 and / or Figure 5A 500) remote control (for example, FIG. 5A to FIG. 5B However, as previously described, in the case where the display 514 is a touch screen (e.g., Figure 2 In the case of a touch screen 112 in FIG. 4 , the touch-sensitive surface 451 is optionally combined with the display 514. The clock 604 optionally represents the "real" time at the electronic device (e.g., the current time of the electronic device) and is not displayed by the electronic device. Fig. 6A The “real” time on the electronic device is 3:30 PM.

[0150] Figure 6B The display of a swipe bar 606 on the display 514 is shown. Specifically, contact 603 is detected on the touch-sensitive surface 451. Contact 603 optionally corresponds to a tap (in some embodiments, a click) of a finger on the touch-sensitive surface 451. In response to detecting contact 603 on the touch-sensitive surface 451, the electronic device displays a swipe bar 606 overlaid on the content item on the display 514. The swipe bar 606 includes a play pointer 608, which is a visual indication of the current playback position within the content item. The swipe bar 606 also includes one or more playback time indications, which include a time value based on the current playback position within the content item and relative to the time of day at the electronic device (e.g., the "actual" time at the electronic device), rather than, for example, relative to the start / end time of the content item itself. Specifically, the swipe bar 606 includes a playback time indication 610, which is displayed at the play pointer 608 and includes a time value that reflects the current time of the electronic device (in Figure 6B3:30 p.m. in the example, rather than a relative time relative to the start / end time of the content item. The swipe bar 606 also includes a playback time indication 612, which is displayed at the right end of the swipe bar 606 and includes a time value reflecting the "actual" time when playback of the content item will end at the current playback speed 1x. Figure 6B , playback of the content item at 1x speed will optionally end 80 minutes from the current time, so playback time indication 612 shows 4:50 p.m. (e.g., 80 minutes from the current time 3:30 p.m.). In some cases, some swipe bars display such playback time indications using a time relative to the current playback position in the content item (e.g., playback time indication 612 may indicate 80 minutes instead of indicating 4:50 p.m.) - however, as shown in reference Figure 6B As described, displaying the playback time indication 612 as “actual” time quickly and easily indicates to the user when the content item will end, rather than requiring the user to make such a determination themselves, thereby enabling the user to more easily make plans about viewing the content item (e.g., determining whether they have enough time to view the content item before having to leave or go to bed), which creates a more efficient human-computer interface and enables the user to use the device more quickly and efficiently.

[0151] Since the "actual" time at which the content item will end optionally depends on the playback speed of the content item, a change in the playback speed of the content item causes the playback time indication 612 to change. Figure 6C shows that the playback speed of the content item changes from 1x speed ( Figure 6B ) to 2x speed ( Figure 6C Other changes in playback state are similarly contemplated (e.g., changing from 1x speed to 0.5x speed, changing from 1x speed to pause, etc.). In response, the playback time indication 612 is optionally updated. Specifically, in Figure 6C In the example, the remaining time in the content item at 2x playback speed is 40 minutes (e.g., 80 minutes at 1x speed and 40 minutes at 2x speed). Thus, playback of the content item will optionally end 40 minutes after the current time of the electronic device, which is Figure 6C Therefore, the playback time indication 612 is updated to indicate 4:10 pm - the updated "actual" time at which playback of the content item will end at 2x the current playback speed. Figure 6C As shown, in response to a change in playback speed from 1x to 2x, playback time indication 612 changes by 40 minutes (e.g., moves back from 4:50 p.m. to 4:10 p.m.) This change in playback time indication 612 occurs immediately after the playback speed change and is greater than the amount of time that has elapsed using the updated playback speed (e.g., less than one second).

[0152] As mentioned above, in Figure 6B and Figure 6C , the “actual” time value indicated by playback time indication 612 is based on the playback speed of the content item (e.g., Figure 6B 1x speed in , and Figure 6C In some examples, the “actual” time value indicated by the playback time indication 612 is more generally based on the playback state of the content item (e.g., different playback states are associated with their own unique or non-unique ways of determining the time value indicated by the playback time indication 612). For example, a 1x speed playback state causes the playback time indication 612 to be determined under the assumption that the content item will be played back from the current playback position at 1x speed, a 2x speed playback state causes the playback time indication 612 to be determined under the assumption that the content item will be played back from the current playback position at 2x speed, and a paused playback state causes the playback time indication 612 to be determined under the assumption that the content item will be played back from the current playback position at 1x speed, even though the content item is currently paused, as shown. Fig.6D Specifically, Fig.6D , playback of the content item has been paused, and playback time indication 612 has been updated to indicate 4:50 p.m. as the “actual” time at which playback of the content item will end (e.g., in contrast to Figure 6B The same playback time indication 612 in and Figure 6C ) because, as previously described, the content item has 80 minutes remaining at 1x playback speed, and in some embodiments, when the content item is paused, the playback time indication 612 will be determined assuming that the content item will be played back at 1x playback speed.

[0153] Reference FIG. 6E to FIG. 6G The behavior of playback time indications 610 and 612 during a swipe operation is described. Fig. 6E In FIG. 6 , the content item is played at a speed of 1x, and the time of day of the electronic device is 3:30 p.m. The swipe bar 606 is displayed, the playback time indication 610 shows 3:30 p.m., and the playback time indication 612 shows 4:50 p.m., as previously described with reference to FIG. Figure 6B described.

[0154] exist Fig. 6F In the example, an input for swiping back through the content items is detected on touch-sensitive surface 451. For example, a swipe of contact 603 from right to left is detected on touch-sensitive surface 451, such as Fig. 6F In response, the current playback position in the content item is rewound based on the detected swipe. Fig. 6FAs shown, the play pointer 608 moves to the left in the swipe bar 606 according to the swipe, and the playback time indication 610 follows the movement of the play pointer 608 along the swipe bar 606. The playback time indication 610 is updated with the time advancing to 3:31 pm because the time of day at the electronic device has advanced from 3:30 pm to 3:31 pm as shown by the clock 604. Finally, the playback time indication 612 is also updated with the time advancing - in Fig. 6F In the example of , the playback time indication 612 is advanced from 4:50 PM to 5:06 PM because the current playback position in the content item has been moved back (e.g., it now takes longer to reach the end of the content item at the 1x playback speed in effect when the swipe was initiated). Specifically, the swipe detected on the touch-sensitive surface 451 moves the current playback position in the content item back 15 minutes. Therefore, the playback time indication 612 is updated to reflect the remaining playback time of 80 minutes + 15 minutes from the current time of the electronic device; specifically, the playback time indication 612 is updated to indicate 5:06 PM.

[0155] exist Figure 6G In the example, an input for swiping forward through content items is detected on touch-sensitive surface 451. For example, a swipe of contact 603 from left to right is detected on touch-sensitive surface 451, such as Figure 6G In response, the current playback position in the content item is advanced in accordance with the detected swipe. Additionally, the play pointer 608 moves to the right in the swipe bar 606 in accordance with the swipe, and the playback time indication 610 follows the movement of the play pointer 608 along the swipe bar 606. The playback time indication 610 is updated to advance the time to 3:34 PM because the time of day at the electronic device has advanced from 3:31 PM to 3:34 PM as shown by the clock 604. Finally, the playback time indication 612 is updated to rewind the time - in Figure 6G In the example of , the playback time indication 612 is rewound from 5:06 PM to 4:39 PM because the current playback position in the content item has been advanced (e.g., it now takes less time to reach the end of the content item at the 1x playback speed in effect when the swipe was initiated). Specifically, the swipe detected on the touch-sensitive surface 451 advances the current playback position in the content item by 30 minutes. Therefore, the playback time indication 612 is updated to reflect the remaining playback time of 95 minutes-30 minutes from the current time of the electronic device; specifically, the playback time indication 612 is updated to indicate 4:39 PM.

[0156] Reference FIG. 6H to FIG. 6I The behavior of playback time indications 610 and 612 during playback operation is described. Figure 6H, the electronic device has exited the swipe mode and the content item is playing at 1x speed. As shown by clock 604, the time of day at the electronic device has advanced to 3:38 PM, and playback time indication 610 has been updated to indicate 3:38 PM. Figure 6G Initially, playback time indication 612 continues to indicate 4:39 PM, because Figure 6G In other words, based on the current playback position in the content item and the time required for playback of the content item to end (e.g., Figure 6H ), playback of the content item will still end at 4:39.

[0157] exist Fig.6I In the playback of content items, Figure 6H Continues, uninterrupted, for 32 minutes at 1x speed. The time of day at the electronic device has thus been advanced to 4:10 PM, and the playback time indication 610 has been updated to indicate 4:10 PM. Figure 6H , the play pointer 608 also advances 32 minutes in the swipe bar 606, and the playback time indication 610 follows the movement of the play pointer 608 along the swipe bar 606. Figure 6H Initially, playback time indication 612 continues to indicate 4:39 PM, because Figure 6H In other words, based on the current playback position in the content item and the time required for playback of the content item to end (e.g., Figure 6H ), playback of the content item will still end at 4:39.

[0158] In some embodiments, the swipe bar 606 alternates between displaying a time indication relative to "real" time and a time indication relative to content or relative time. Figures 6J to 6K Shown. Figure 6J In, as reference Figure 6B As described above, swiping bar 606 is displayed in response to detecting contact 603 on touch-sensitive surface 451. Figure 6B As described, swipe bar 606 includes playback time indication 610 and playback time indication 612, which are relative to "real" time.

[0159] In some embodiments, after a predetermined time (e.g., 3, 5, or 10 seconds) has passed since the swipe bar 606 was displayed on the display 514, the swipe bar 606 switches from displaying the "actual" playback time indications 610 and 612 to displaying the "relative time" playback time indications. Figure 6K In, from Figure 6J A predetermined amount of time has passed since the beginning. Figure 6K, the swipe bar 606 is shown with a playback time indication 616 at the play pointer 608 and a playback time indication 618 at the right end of the swipe bar 606. The playback time indications 616 and 618 are "relative" playback time indications relative to one or more positions in the content item. For example, the playback time indication 616 indicates the current playback position in the content item, which has a time value relative to the beginning of the content item (e.g., the distance into the content item the current playback position is). Figure 6K , the current playback position is 30 minutes into the content item, so playback time indication 616 indicates 30 minutes. Playback time indication 618 indicates the end of the content item, which has a time value relative to the current playback position in the content item (e.g., the distance of the end of the content item from the current playback position). Figure 6K , the end of the content item is 80 minutes from the current playback position at 1x playback speed, and thus the playback time indication 618 indicates 1 hour and 20 minutes (eg, 80 minutes).

[0160] In some embodiments, when swipe mode is initiated at the electronic device, the swipe bar 606 switches from displaying an "actual" playback time indication to displaying a relative time indication, rather than alternating between displaying a time indication relative to "actual" time and displaying a time indication relative to content or relative time, where the content or relative time is based on the passage of a predetermined amount of time. This will refer to Figure 6L to Figure 6Q Shown. Figure 6L In the embodiment of the present invention, when the swipe bar 606 is displayed, an input for initiating the swipe mode on the electronic device is received. The input is a click of the touch-sensitive surface 451, through Figure 6L In response to detecting a click on the touch-sensitive surface 451, the electronic device enters a swipe mode, such as Figure 6M In swipe mode, as shown in Figure 6K As shown, the swipe bar 606 is shown with "relative" playback time indications 616 and 618, rather than Figure 6L In some embodiments, the swipe bar 606 includes “relative” playback time indications 616 and 618 only when the electronic device is in swipe mode, and does not include any “actual” playback time indication when the electronic device is in swipe mode.

[0161] exist Figure 6N In FIG. 4 , while the electronic device is in swiping mode, contact 603 is detected on touch-sensitive surface 451 and swipes from left to right. In response, the current playback position in the content has been advanced by 25 minutes (e.g., from Figure 6M 30 minutes to move to Figure 6NTherefore, playback time indication 616 (e.g., indicating the current playback time) has been updated from indicating 55 minutes to indicating 30 minutes, and playback time indication 618 has been updated from indicating a remaining playback time of 80 minutes (e.g., 1 hour and 20 minutes) to indicating a remaining playback time of 55 minutes.

[0162] In some embodiments, when the electronic device is in swipe mode, the swipe bar 606 includes both one or more "actual" playback time indications and one or more "relative" playback time indications. Fig.6O , the swipe bar 606 includes an "actual" playback time indication 610 (at the play pointer 608) and 612 (at the right end of the swipe bar 606). The characteristics of the playback time indications 610 and 612 are as described above with reference to FIG. 6A to FIG. 6I In addition, the swipe bar 606 is shown with a "relative" playback time indication 616 at the play pointer 608 (e.g., above the play pointer 608, while the playback time indication 610 is displayed below the play pointer 608), which has a reference Figure 6K and Figures 6M to 6N Features described. A playback time indication 616 is displayed within an image (eg, a thumbnail) of the content item at the current playback position in the content.

[0163] exist Figure 6P , while the electronic device is in swipe mode, contact 603 is detected on touch-sensitive surface 451 as further swiping from left to right. Thus, in accordance with the swipe detected on touch-sensitive surface 451, play pointer 608 has been advanced in swipe bar 606, and the current playback position of the content has been advanced. Playback time indication 610 has been updated in accordance with the passage of time at the electronic device (e.g., from Fig.6O 3:32 PM to Figure 6P 3:35 pm, as referenced FIG. 6F to FIG. 6I ), the playback time indication 612 has been updated according to the change in the current playback position caused by the swipe (e.g., as shown in reference FIG. 6F to FIG. 6G ), and the playback time indication 616 has been updated according to the change in the current playback position caused by the swipe (e.g., as shown in reference Figures 6M to 6N In addition, Figure 6P As shown, the playback time indication 616 and the image in which the playback time indication 616 is displayed have moved along the swipe bar 606 together with the play pointer 608.

[0164] exist Figure 6Q, an input for exiting the swipe mode of the electronic device is detected at touch-sensitive surface 451. For example, a click of touch-sensitive surface 451 is detected, as indicated by contact 603. In response, swipe bar 606 is displayed with "actual" playback time indications 610 and 612, without displaying "relative" playback time indications 616 or 618.

[0165] Reference FIG. 6R to FIG. 6T The behavior of playback time indications 610 and 612 when a content item is paused is described. Figure 6R In the example of FIG. 1 , the content item is paused and a swipe bar 606 with “actual” playback time indications 610 and 612 is displayed, with features as described above with reference to FIG. FIG. 6A to FIG. 6I The time at the electronic device is 3:35 p.m., as indicated by clock 604. Therefore, playback time indication 610 shows 3:35 p.m. In addition, if the content item is to be played at 1x speed starting from the current playback position, there are 40 minutes remaining. Therefore, playback time indication 612 indicates 4:15 p.m., which is 40 minutes from the current time at the electronic device.

[0166] exist Figure 6S in, from Figure 6R Since the situation in , the content item has remained paused. Since the content item continues to be paused, the current playback position in the content item has not changed, and the play pointer 608 has not moved. However, as shown by the clock 604, the playback time indication 610 has been updated from 3:35 PM to 3:40 PM based on the passage of time at the electronic device. Therefore, the play time indication 610 has been updated to indicate 3:40 PM. The playback time indication 612 has also been updated based on the passage of time at the electronic device because time has passed on the electronic device without any progress being made in the process of advancing through the content item. Specifically, the playback time indication 612 has been updated from indicating 3:35 PM to indicating 3:40 PM. Figure 6R Updated to instructions at 4:15 PM Figure 6S , because if playback of the content item is started at 1x playback speed, it is now determined that the content item ends at 4:20 PM.

[0167] exist Figure 6T in, from Figure 6R to Figure 6S The content item continues to remain paused from the situation in . The current playback position in the content item has not changed, and the play pointer 608 has not moved. However, as described above, as shown by the clock 604, the playback time indication 610 has been updated from 3:40 p.m. to 3:45 p.m. based on the passage of time at the electronic device. Therefore, the play time indication 610 has been updated to indicate 3:45 p.m. The playback time indication 612 has also been updated based on the passage of time at the electronic device. Specifically, the playback time indication 612 has been updated from Figure 6S Updated at 4:20 pm Figure 6T4:25 p.m. FIG. 6R to FIG. 6T As shown, the “actual” playback time indications 610 and 612 are updated even when the content item is paused, while the relative playback time indications (e.g., Figure 6K The time indications 616 and 618 in FIG. 10A ) will not be updated while the content item is paused (eg, because the “relative” or “content” time does not change while the content is paused).

[0168] In some embodiments, the swipe bar 606 includes hints of different actions that can be accessed from the touch-sensitive surface 451, as well as information to the user about the identities of those actions and / or about how to access those actions. Figure 6U to Figure 6Z Description. Figure 6U , swipe bar 606 is displayed on display 514. While swipe bar 606 is displayed, an input is detected requesting display of visual indications of actions accessible from touch-sensitive surface 451. For example, contact 603 corresponding to a finger detected on touch-sensitive surface 451 is detected as having less movement than a movement threshold (e.g., 0.5 or 1 mm) and lasting longer than a time threshold (e.g., 0.5, 1, or 2 seconds). In response, visual indications 622, 624, and 626 are displayed on display 514 - in Figure 6U In the example of , visual indications 622, 624, and 626 are displayed (e.g., around and above) play pointer 608. Visual indications 622, 624, and 626 correspond to different actions accessible from touch-sensitive surface 451. For example, visual indication 622 corresponds to a reverse jump action (e.g., a 15-second reverse jump), visual indication 624 corresponds to a play action (e.g., because the content item is currently paused - if the content item is currently playing, visual indication 624 will correspond to a pause action), and visual indication 626 corresponds to a forward jump action (e.g., a 15-second forward jump). Additional or alternative actions accessible from touch-sensitive surface 451 are also within the scope of the present invention and correspond to visual indications displayed on display 514.

[0169] In some embodiments, visual indications 622, 624, and 626 can be selected by navigating current selection cursor 628 (indicated by a dashed box) to one of the visual indications using directional input detected on touch-sensitive surface 451, and then detecting a selection input on touch-sensitive surface 451 (e.g., a click of touch-sensitive surface 451). Figure 6U , a current selection cursor 628 is over visual indication 624. When a visual indication has a current selection, its appearance is changed to be different from the appearance of a visual indication that does not have a current selection. For example, visual indication 624 is highlighted, while visual indications 622 and 626 are not highlighted. Figure 6V, a downward, leftward swipe is detected on touch-sensitive surface 451 (e.g., indicated by movement of contact 603), which causes current selection cursor 628 to move to visual indication 622. Figure 6W In the example, a click on the touch-sensitive surface 451 is detected. Thus, an action corresponding to the visual indication 622 (e.g., a rewind or reverse jump action) is performed at the electronic device, and the current playback position is jumped back in the content item (e.g., in Figure 6W The playback pointer 608 is rewound along the swipe bar 606 according to the rewind jump in the content item, and the playback time indication 612 is updated to reflect the rewind jump in the content item. The visual indications 622, 624 and 626 move as the playback pointer 608 moves, such as Figure 6W As shown. Figure 6W In response to the selection of visual indication 622, the current playback position in the content item has been rewound 15 minutes. Therefore, playback time indication 612 has been updated to indicate 4:40 p.m. (with Figure 6V The other of visual indications 622, 624, and 626 are similarly selectable via direction and click input detected on touch-sensitive surface 451. In this way, actions accessible from touch-sensitive surface 451 are known to and selectable by a user of the electronic device.

[0170] In some embodiments, rather than being selectable as a result of navigating the current selection cursor 628 to actions accessible from the touch-sensitive surface 451, these actions are associated with and selectable from corresponding areas on the touch-sensitive surface 451. Figure 6X to Figure 6Z In Figure 6X , the touch-sensitive surface 451 includes multiple predefined areas 630. One or more of the predefined areas 630 correspond to actions accessible from the touch-sensitive surface 451, as described below. A swipe bar 606 is displayed on the display 514. While the swipe bar 606 is displayed, an input is detected requesting display of visual indications of actions accessible from the touch-sensitive surface 451. For example, contact 603 corresponding to a finger detected on the touch-sensitive surface 451 is detected as having less movement than a movement threshold (e.g., 0.5 or 1 mm), having less force than a force threshold (e.g., a tap and hold, rather than a click and hold), and lasting longer than a time threshold (e.g., 0.5, 1, or 2 seconds). In response, visual indications 622, 624, and 626 are displayed on the display 514, as described in reference to FIG. Figure 6U In some embodiments, contact 603 must be detected in a specific area of ​​touch-sensitive surface 451 (e.g., area 630e) in order for visual indications 622, 624, and 626 to be displayed; otherwise, visual indications 622, 624, and 626 are not displayed.

[0171] exist Figure 6X to Figure 6Z In the example of , the actions associated with visual indications 622, 624, and 626 are associated with corresponding areas on touch-sensitive surface 451, so that selection of a particular area on touch-sensitive surface 451 selects and causes performance of a particular action corresponding to the selected area on the touch-sensitive surface. Figure 6X , region 630d corresponds to visual indication 622 and thus corresponds to a backward jump action; region 630b corresponds to visual indication 624 and thus corresponds to a play action (or, if the content item is playing rather than paused, a pause action); and region 630f corresponds to visual indication 626 and thus corresponds to a forward jump action. Thus, selection (e.g., clicking) of region 630d causes a content item to be skipped backward, selection (e.g., clicking) of region 630b causes a content item to begin playing, and selection (e.g., clicking) of region 630f causes a content item to be skipped forward.

[0172] A contact detected in one of regions 630d, 630b, and 630f causes the corresponding visual indication to be highlighted (e.g., having a current selection) to indicate to a user of the electronic device that selecting (e.g., clicking) the region that the user is touching will cause an action corresponding to the highlighted visual indication to be performed, such as Figure 6Y Specifically, Figure 6Y , contact 603 has moved from area 630e to area 630d on the touch-sensitive surface. As a result, visual indication 622 becomes highlighted (e.g., has a current selection), as shown by the dashed box. Figure 6Z , a click on touch-sensitive surface 451 is detected when contact 603 is in region 630d. Thus, the current playback position has moved backward in the content item, and as shown in reference Figure 6W The update swipe bar 606 (and its associated elements, such as play pointer 608, playback time indication 612, etc.) is shown. Visual indications 624 and 626 are similarly highlighted and / or selected as a result of detecting contact 603 and / or clicking on touch-sensitive surface 451 in regions 630b and 630f, respectively.

[0173] In some embodiments, time passes when a swipe or other content navigation operation is performed, and a relative time indicator is adjusted based on the passage of time and navigation in the content (e.g., actual time advances 1 minute and the user swipes back through 30 minutes of content in the content, resulting in an increase of 31 minutes in the estimated end time of content playback at a 1x playback rate; or actual time advances 5 minutes and the user swipes forward through 30 minutes of content, resulting in a decrease of 25 minutes in the estimated end time of content playback at a 1x playback rate). Similarly, adjustments to the estimated end time of content playback can be calculated based on a combination of changes in playback rate and navigation and / or passage of time in the content. By considering various factors that affect the end time of content playback and displaying the estimated end time of content playback, the device creates a more effective human-computer interface by enabling the user to see the estimated end time of content playback and adjust their use of the device accordingly.

[0174] FIG. 7A to FIG. 7G 700 is a flowchart illustrating a method for displaying a swipe bar having one or more time indications associated with a real-world time at an electronic device according to some embodiments of the present disclosure. Method 700 is optionally performed on an electronic device (such as device 100, device 300, or device 500), as described above in conjunction with Figure 1A to Figure 1B , Figures 2 to 3 and FIG. 5A to FIG. 5B Some operations in method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0175] As described below, method 700 provides a way to display a swipe bar with one or more time indications related to the actual time at the electronic device. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

[0176] In some embodiments, method 700 is performed in conjunction with a display (e.g., a television, a computer monitor, such as Fig. 6A 514 in the display) and one or more input devices (e.g., a remote control, a smart phone configured to control the electronic device, a wearable device configured to control the electronic device, etc., such as Fig. 6A An electronic device (e.g., a set-top box, a computer, such as the one referenced above) having a touch-sensitive surface 451 in the Figure 1A to Figure 1B , Figures 2 to 3 and FIG. 5A to FIG. 5BIn some embodiments, the method is performed at an electronic device including a display and / or one or more input devices, such as an electronic device having a touch screen (e.g., a tablet computer, a smart phone, etc.), or an electronic device including a display and communicating with an input device (e.g., a mouse or a trackpad) (e.g., a computer). In some embodiments, the electronic device displays (702) on the display a playback user interface (e.g., a content player, such as a movie player) configured to play back content on the electronic device, such as Fig. 6A In some embodiments, when displaying a playback user interface configured to play back content on an electronic device, the electronic device displays (706) a swipe bar on the display for navigating through the content, such as a swipe bar that can be used to navigate through the content. Figure 6B Like in.

[0177] In some embodiments, the swipe bar includes (704) a visual indication (708) of a current playback position within the content (e.g., a user interface element that visually depicts the location of the current playback position within the content, such as a play pointer or a thumbnail of a preview of the content at a location corresponding to the location of the play pointer along the swipe bar), and one or more playback time indications (710) that include a time value based on the current playback position within the content, wherein a corresponding playback time indication in the one or more playback time indications is determined based on the time of day at the electronic device (e.g., the “actual time” at the electronic device; for example, if the current time at the electronic device is 8:30 PM, then based on 8:30 PM rather than a relative time, such as relative to the start / end time of the content, and an amount of time taken to play the content from the current playback position to the end of the content at a corresponding content playback speed (e.g., if the content is being played back, then the current playback speed such as 1x, 2x, if the content is paused, then the standard 1x playback speed, or optionally the 1x playback speed, regardless of whether the content is paused or being played back at any speed), such as Figure 6B In this way, the user can easily and quickly determine the actual time when the playback of the content will end, thereby facilitating a more effective human-computer interface. In some embodiments, the corresponding playback time indication is displayed at the end of the swipe bar corresponding to the end of the content, and displays the "actual time" when the playback of the content will end, such as Figure 6BThat way (e.g., if the current time is 8:30 PM and 15 minutes remain in the content, it will be 8:45 PM). In this way, the user of the electronic device can easily determine the time of day that playback of the content will end if the content is played back at the current playback speed (or 1x playback speed) or if the content is paused, or the time of day that playback of the content will end if playback of the content begins at the current time.

[0178] In some embodiments, a corresponding content playback speed for determining the amount of time it takes to play back the content from a current playback position is selected (712) based on the playback state of the content, such as in FIG. 6B to FIG. 6D (e.g., if the content is played back at 1x speed, the current playback speed is, for example, 1x, or if the content is played back at 2x speed, the current playback speed is, for example, 2x, or if the content is paused, the current playback speed is 1x playback speed). In this way, the electronic device indicates the accurate playback end time to the user, because the end time will change according to the playback speed of the content, thereby facilitating a more effective human-computer interface. In some embodiments, the corresponding playback time indication is represented (714) as a future time of the day when the content will reach the end at the corresponding content playback speed, such as FIG. 6B to FIG. 6D (e.g., if the current time at the electronic device is 5 p.m., and the content will reach the end at 6 p.m. at the corresponding content playback speed, the corresponding playback time indication may optionally indicate 6 p.m. in the swipe bar.) In this way, the user can easily and quickly determine the actual time when the playback of the content will end, thereby facilitating a more efficient human-computer interface. The corresponding playback time indication may optionally be displayed at or near the end of the swipe bar corresponding to the end of the content, such as Figure 6B Like in.

[0179] In some embodiments, before displaying the swipe bar on the display, the electronic device receives (716) input at one or more input devices to display the swipe bar while displaying the playback user interface on the display (e.g., a tap detected on a touch-sensitive surface of one or more input devices, a click on the touch-sensitive surface, or a contact detected on the touch-sensitive surface with an intensity greater than an intensity threshold, etc.). In some embodiments, in response to receiving the input, the electronic device displays (718) the swipe bar on the display, such as Figure 6B Like in.

[0180] In some embodiments, the one or more playback time indications include (720) a second corresponding playback time indication displayed at a visual indication of a current playback position within the content, such as Figure 6B In some embodiments, the second corresponding playback time indication displays (722) the current time at the electronic device, such as Figure 6BIn some embodiments, when a swipe bar and a second corresponding playback time indication are displayed on the display (e.g., an indication of the current time at the electronic device displayed at the visual indication of the current playback position), the electronic device receives (724) input at one or more input devices for swiping through the content, such as FIG. 6F to FIG. 6G In some embodiments, in response to receiving (726) an input for swiping over the content: the electronic device updates (728) the current playback position within the content based on the input for swiping over the content, including updating the position of a visual indication of the current playback position within the swipe bar (e.g., moving forward or backward in the content based on the detected input), and updates (730) a second corresponding playback time indication based on the advancement of the time of day at the electronic device, such as FIG. 6F to FIG. 6G The user is thus able to quickly and easily determine the current time at the electronic device, and the electronic device maintains an accurate representation of the current time at the electronic device, thereby facilitating a more efficient human-computer interface.

[0181] In some embodiments, when the swipe bar and a second corresponding playback time indication (e.g., an indication of the current time at the electronic device displayed at the visual indication of the current playback position) are displayed on the display, the electronic device plays (732) the content at the second corresponding content playback speed, such as Figure 6H In some embodiments, while playing (734) the content at the second corresponding content playback speed, the electronic device updates (736) the current playback position within the content based on the playback progress through the content at the second corresponding content playback speed, including updating the position of a visual indication of the current playback position within the swipe bar (e.g., forward or backward through the content based on the playback speed of the content), and updating (738) the second corresponding playback time indication based on the advancement of the time of day at the electronic device, such as FIG. 6H to FIG. 6IAs a result, the user is able to quickly and easily determine the current time at the electronic device, and the electronic device maintains an accurate representation of the current time at the electronic device, thereby facilitating a more effective human-computer interface.

[0182] In some embodiments, when the current playback position within the content changes, the position of the second corresponding playback time indication on the display moves according to the movement of the visual indication of the current playback position within the content (740), such as FIG. 6F to FIG. 6I The second corresponding playback time indication is optionally together with the visual indication of the current playback position within the content, such as FIG. 6F to FIG. 6I In some embodiments, a corresponding playback time indication (e.g., an indication showing the "actual time" at which playback of the content will end) is displayed (742) at the end of the scrub bar corresponding to the end of the content, such as Figure 6B Thus, the user can quickly and easily associate the corresponding playback time indication with the end of playback of the content, thereby facilitating a more efficient human-computer interface. In some embodiments, the corresponding playback time indication displays (744) the time of day at the electronic device at which playback of the content will end at the corresponding content playback speed, such as Figure 6B as in the example above (e.g., the corresponding playback time indication is displayed at the far right end of the swipe bar).

[0183] In some embodiments, while displaying the swipe bar and corresponding playback time indication on the display (e.g., an indication of the “actual time” at which playback of the displayed content will end), the electronic device receives (746) input at one or more input devices for swiping the content, such as FIG. 6F to FIG. 6G In some embodiments, in response to receiving (748) input for swiping through content, the electronic device updates (750) the current playback position within the content, including updating the position of a visual indication of the current playback position within the swipe bar in accordance with the input for swiping through the content (e.g., moving forward or backward in the content based on the detected input), and updating (752) a corresponding playback time indication based on the updated current playback position within the content, the updated corresponding playback time being displayed at the corresponding content playback speed, and an updated time of day at the electronic device at which content playback will end, starting from the updated current playback position within the content, such as FIG. 6F to FIG. 6GIn this way (e.g., if starting from a new position within the content caused by the swipe, the time of day at which content playback will end is updated). Therefore, the user can quickly and easily see the effects of various playback state changes, including changing the current playback position at the time when content playback will end, thereby creating a more effective human-computer interface. If the swipe is to swipe backward through the content, the corresponding playback time indication is optionally moved forward in time, such as Fig. 6F If the swipe is forward through the content, the corresponding playback time indication may optionally be moved backward in time, such as Figure 6G (e.g., playback of the content will end earlier in the day due to moving the current playback position forward in the content).

[0184] In some embodiments, when the swipe bar and the corresponding playback time indication (e.g., an indication of the "actual time" at which playback of the content will end) are displayed on the display, the electronic device plays (754) the content at a second corresponding content playback speed, such as FIG. 6H to FIG. 6I In some embodiments, while playing (756) the content at the second corresponding content playback speed, the electronic device updates (758) the current playback position within the content based on the playback progress through the content at the second corresponding content playback speed, including updating the position of a visual indication of the current playback position within the swipe bar (e.g., forward or backward through the content based on the playback speed of the content), and maintaining (760) the corresponding playback time indication while playing the content at the second corresponding content playback speed, such as FIG. 6H to FIG. 6I (e.g., as long as playback of the content continues at the corresponding content playback speed, the corresponding playback time indication optionally does not change because the time at which playback of the content will end, i.e., the time reflected by the corresponding playback time indication optionally does not change.) If playback of the content is interrupted in some way (e.g., paused, speed changed, etc.), the corresponding playback time indication is optionally updated to reflect an updated time at which playback of the content will end in view of the interrupted content playback, such as Figure 6C Thus, the user can quickly and easily determine when playback of the content will end, thereby contributing to a more efficient human-machine interface.

[0185] In some embodiments, when one or more playback time indications are displayed in the swipe bar, the electronic device determines (762) that one or more relative time criteria for displaying one or more second playback time indications in the swipe bar are met, wherein the one or more second playback time indications include time values ​​based on relative content time, such as Figures 6J to 6KIn some embodiments, in response to determining that one or more relative time criteria are met, the electronic device displays (764) one or more second playback time indicators in the swipe bar, such as Figure 6K A second playback time indication is optionally displayed at the visual indication of the current playback position in the content and displays the time that has elapsed in the content from the beginning of the content to the current playback position in the content, such as Figure 6K Another second playback time indicator is optionally displayed at the far right end of the swipe bar and displays the remaining time from the current playback position in the content to the end of the content, such as Figure 6K Like in.

[0186] In some embodiments, the one or more second playback time indications (766) are relative to a starting position in the content (e.g., the current playback position shows how far in content time the current playback position is from the beginning of the content, and the end position shows how far in content time the end of the content is from the current playback position in the content (e.g., how much time is left in the content)). In some embodiments, the one or more relative time criteria (768) are met when a predetermined amount of time (e.g., 3, 5, or 10 seconds) has passed since the swipe bar was displayed on the display, such as Figures 6J to 6K In some embodiments, the electronic device optionally redisplays the “actual time” playback indication in the swipe bar after another predetermined amount of time (e.g., 3, 5, or 10 seconds) has passed since displaying the “relative time” second playback time indication.

[0187] In some embodiments, when a swipe bar and one or more playback time indications (e.g., a “real time” indication) are displayed on the display, when an input is received to initiate a swipe mode on the electronic device (e.g., a click or tap on a touch-sensitive surface of one or more input devices), the one or more relative time criteria (770) are met, such as Figure 6L In some embodiments, when one or more second playback time indications (e.g., “relative time” indications) are displayed in the swipe bar and when the electronic device is in swipe mode, the electronic device receives (772) input for swiping content, such as FIG. 6N to FIG. 6OIn some embodiments, in response to receiving an input for swiping over the content, the electronic device updates (774) the one or more second playback time indications based on the input for swiping over the content, such as a left or right swipe detected on a touch-sensitive surface of one or more input devices. FIG. 6N to FIG. 6O If the swipe is swiping backward through the content, the current position time indication optionally becomes smaller (e.g., indicating that the current position is now at an earlier time in the content), and the end position time indication optionally becomes larger (e.g., indicating that the end of the content is now a greater amount of time from the current position in the content). Similarly, if the swipe is swiping forward through the content, the current position time indication optionally becomes larger, and the end position time indication optionally becomes smaller, such as Figure 6N Like in.

[0188] In some embodiments, when the electronic device is in swipe mode, the swipe bar simultaneously includes (776) the one or more playback time indications (e.g., the "actual" playback time indication at the current playback position and the end position in the content), and the one or more second playback time indications, such as Fig.6O In some embodiments, when the electronic device is in swipe mode, the swipe bar includes (778) the one or more second playback time indications (e.g., “relative time” time indications at the current play position and end position in the content), but does not include the one or more playback time indications (e.g., “actual” playback time indications), such as Figure 6N Thus, in some embodiments, the swipe bar displays only a “relative time” time indication while swiping, allowing the user to quickly and easily determine various relative time quantities within the content (e.g., how far the current playback position is from the beginning of the content), which is optionally what the user is most interested in when the user swipes through the content to locate a given position in the content, thereby creating a more effective human-computer interface.

[0189] In some embodiments, when the electronic device is in the swipe mode, the electronic device receives (780) an input at one or more input devices for exiting the swipe mode, such as Figure 6QIn some embodiments, in response to receiving an input for exiting the swipe mode, the electronic device displays (782) a swipe bar on the display having one or more playback time indications (e.g., an “actual” playback time indication at the current play position and the end position in the content) and without the one or more second playback time indications (e.g., a “relative time” time indication), such as Figure 6Q In some embodiments, after exiting the swipe mode, the electronic device returns to displaying the swipe bar with an "actual" playback time indication rather than a "relative time" time indication, such as Figure 6Q Therefore, likewise, the user can quickly and easily determine when playback of the content will end, thereby facilitating a more efficient human-machine interface.

[0190] In some embodiments, when content is paused on the electronic device and a swipe bar and a corresponding playback time indication (e.g., an indication showing the “actual time” at which playback of the content will end) are displayed on the display, the electronic device updates (784) the corresponding playback time indication based on the advancement of the time of day at the electronic device, such as FIG. 6R to FIG. 6T In the example of FIG. 1 , the electronic device maintains the accuracy of the time at which content playback ends, which helps to improve the efficiency of the human-computer interface.

[0191] In some embodiments, while content is being played on the electronic device (e.g., at 1x speed, 2x speed, etc.) and while a swipe bar and a corresponding playback time indication are displayed on the display (e.g., an “actual time” indication showing when playback of the content will end), the electronic device detects (786) a change in the content playback speed of the content, such as Figure 6C In some embodiments, in response to detecting a change in the content playback speed of the content, the electronic device updates (788) the corresponding playback time indication by an amount that is greater than the amount of content played at the changed content playback speed, such as Figure 6C(For example, if the playback speed is changed from 1x to 2x, and the corresponding playback time indication shows 6pm (e.g., 60 minutes from the current time) before the playback speed is changed, the corresponding playback time indication is optionally updated to show 5:30pm, i.e., reduced by 30 minutes, which is greater than the amount of content played at the changed content playback speed, which is optionally on the order of seconds). Therefore, the electronic device maintains the accuracy of the time when content playback ends, which helps to improve the efficiency of the human-computer interface.

[0192] In some embodiments, while the swipe bar is displayed on the display, the electronic device detects (790) input at a touch-sensitive surface of one or more input devices (e.g., a touch-sensitive surface of a remote control, separate from the electronic device and the display) that corresponds to a request to display multiple visual indications of different actions accessible from the touch-sensitive surface (e.g., rewinding the content, skipping back a predetermined amount such as 10 seconds, 20 seconds, or 30 seconds in the content, fast forwarding the content, skipping forward a predetermined amount such as 10 seconds, 20 seconds, or 30 seconds in the content, pausing the content if it is playing, playing the content if it is paused, etc.), such as in Figure 6U In some embodiments, in response to detecting an input corresponding to a request to display multiple visual indications of different actions accessible from the touch-sensitive surface, the electronic device displays (792) multiple visual indications on the display (e.g., in a swipe bar; in some embodiments, at a visual indication of the current playback position in the content). Figure 6U In this way, the user can quickly and easily determine the actions that can be accessed from the touch-sensitive surface, which helps to improve the efficiency of the human-computer interface. In some embodiments, different actions are associated with corresponding areas on the touch-sensitive surface, so that selecting a specific area on the touch-sensitive surface selects and causes the execution of a specific action corresponding to the selected area on the touch-sensitive surface, such as in Figure 6X Like in.

[0193] In some embodiments, directional input detected on the touch-sensitive surface (e.g., input that moves the current selection from one visual indication to another) can be used to navigate multiple visual indications, and when a selection input is detected at the touch-sensitive surface when a particular visual indication is currently selected (e.g., independent of any area of ​​the touch-sensitive surface where the selection input is detected), the electronic device performs a specific action corresponding to the selected visual indication, such as in Figure 6UIn some embodiments, while displaying multiple visual indications corresponding to different actions accessible from the touch-sensitive surface, the electronic device detects (794) additional input on the touch-sensitive surface that indicates a possible selection of a corresponding visual indication in the multiple visual indications, the visual indication corresponding to the corresponding action in the different actions (e.g., detecting a finger in an area of ​​the touch-sensitive surface corresponding to the corresponding visual indication and / or the corresponding action, or detecting navigation input at the touch-sensitive surface, such as a swipe up / down / left / right that moves the current selection to the corresponding visual indication). In some embodiments, in response to detecting the additional input, the electronic device changes (796) the appearance of the corresponding visual indication relative to the appearance of other visual indications in the multiple visual indications, such as in Figure 6U to Figure 6V and Figure 6Y Other visual indications are optionally not highlighted or otherwise displayed in a different manner than the currently selected visual indication, such as in Figure 6U to Figure 6V and Figure 6Y In this way, the user can quickly and easily determine the action currently selected from the touch-sensitive surface (e.g., the action to be performed in response to the selection input detected on the touch-sensitive surface), which helps to improve the efficiency of the human-computer interface.

[0194] In some embodiments, when a possible selection of a corresponding visual indication is indicated (e.g., when a finger is in an area of ​​the touch-sensitive surface corresponding to the corresponding visual indication and / or the corresponding action, or when the corresponding visual indication has a current selection), the electronic device receives (798) input at the touch-sensitive surface of one or more input devices to select the visual indication, such as in Figure 6W and Figure 6Z In some embodiments, in response to receiving input selecting a visual indication, the electronic device performs (798-2) a corresponding action corresponding to the corresponding visual indication at the electronic device, such as in Figure 6W and Figure 6Z Like in.

[0195] It should be understood that FIG. 7A to FIG. 7GThe specific order in which the operations are described in the information processing method is merely exemplary and is not intended to indicate that the order is the only order in which the operations can be performed. A person skilled in the art will be able to think of many ways to reorder the operations described herein. Therefore, the operations in the above information processing method can be optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above in conjunction with Figure 1A , Figure 3 , Figure 5A and Figure 8 In addition, the above reference FIG. 7A to FIG. 7G The described operation is optionally performed by Figure 1A to Figure 1B . For example, display operations 702, 704, and 718 and receiving operation 716 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive surface 451, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how to update the content displayed by the application based on the GUI updater 178. Figure 1A to Figure 1B The components depicted in the figure are used to implement other processes.

[0196] According to some embodiments, Figure 8 An electronic device 800 (eg, Figure 1A The device 100, Figure 3 Device 300 and / or Figure 5A The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software that implements the principles of the various described embodiments. It should be understood by those skilled in the art that Figure 8 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.

[0197] like Figure 8 As shown, the electronic device 800 optionally includes a receiving unit 808 configured to receive input, and a processing unit 802 coupled to the receiving unit 808. In some embodiments, the processing unit 802 includes a display enabling unit 804, a determining unit 806, an updating unit 810, a playing unit 812, a detecting unit 814, and an executing unit 816.

[0198] In some embodiments, the processing unit (802) is configured to display a playback user interface on a display (e.g., using a display enabling unit 804), which is configured to playback content on an electronic device. In some embodiments, the processing unit is configured to display a swipe bar for navigating in the content on a display (e.g., using a display enabling unit 804) when displaying a playback user interface configured to playback content on an electronic device. In some embodiments, the swipe bar includes a visual indication of the current playback position in the content; and one or more playback time indications, the one or more playback time indications including a time value based on the current playback position in the content. In some embodiments, the corresponding playback time indication in the one or more playback time indications is based on the time of the day at the electronic device, and the amount of time it takes to play the content from the current playback position to the end of the content at the corresponding content playback speed. In some embodiments, based on the playback state of the content, a corresponding content playback speed is selected to determine the amount of time it takes to play the content from the current playback position (e.g., using a determination unit 806). In some embodiments, the corresponding playback time indication is represented as a future time of day at which the end of the content will be reached at the corresponding content playback speed.

[0199] In some embodiments, the receiving unit (808) is configured to receive input to display a swipe bar while displaying the playback user interface on the display (e.g., using the display enabling unit 804) before displaying the player bar on the display. In some embodiments, the processing unit (802) is further configured to display the swipe bar on the display (e.g., using the display enabling unit 804) in response to receiving the input (e.g., using the receiving unit 808). In some embodiments, the one or more playback time indications include a second corresponding playback time indication displayed at the visual indication of the current playback position in the content (e.g., using the display enabling unit 804), the second corresponding playback time indication displaying the current time of day at the electronic device.

[0200] In some embodiments, the receiving unit (808) is further configured to receive input for swiping the content when the swipe bar and the second corresponding playback time indication are displayed on the display (e.g., using the display enabling unit 804). In some embodiments, the processing unit (802) is further configured to respond to receiving input for swiping the content (e.g., using the receiving unit 808): update the current playback position in the content (e.g., using the updating unit 810), including updating the position of the visual indication of the current playback position within the swipe bar according to the input for swiping the content; update the second corresponding playback time indication (e.g., using the updating unit 810) according to the advancement of the time of day at the electronic device.

[0201] In some embodiments, the processing unit (802) is further configured to: when the swipe bar and the second corresponding playback time indication are displayed on the display (e.g., using the display enabling unit 804), play the content at the second corresponding content playback speed (e.g., using the playing unit 812). In some embodiments, the processing unit (802) is further configured to update the current playback position in the content (e.g., using the updating unit 810) according to the playback progress through the content at the second corresponding content playback speed, including updating the position of the visual indication of the current playback position within the swipe bar, and updating the second corresponding playback time indication according to the advancement of the time of day at the electronic device (e.g., using the updating unit 810).

[0202] In some embodiments, when the current playback position in the content changes, the position of the second corresponding playback time indication on the display moves according to the movement of the visual indication of the current playback position in the content. In some embodiments, the corresponding playback time indication is displayed at the end of the swipe bar corresponding to the end of the content, and the corresponding playback time indication displays the time of day at the electronic device, and the playback of the content will end at the time of the day at the corresponding content playback speed.

[0203] In some embodiments, the receiving unit (808) is further configured to receive input for swiping the content while displaying the swipe bar and the corresponding playback time indication on the display. In some embodiments, the processing unit (802) is further configured to respond to receiving input for swiping the content (e.g., using the receiving unit 808): (e.g., using the updating unit 810) updating the current playback position in the content, including updating the position of the visual indication of the current playback position within the swipe bar according to the input for swiping the content, and updating the corresponding playback time indication according to the updated current playback position in the content (e.g., using the updating unit 810). In some embodiments, the updated corresponding playback time indication displays an updated time of day at the electronic device, and the playback of the content will end at the updated time of day starting from the updated current playback position in the content at the corresponding content playback speed.

[0204] In some embodiments, the processing unit (802) is further configured to: when the swipe bar and the corresponding playback time indication are displayed on the display (e.g., using the display enabling unit 804), play the content at the second corresponding content playback speed (e.g., using the playback unit 812). In some embodiments, the processing unit (802) is further configured to update the current playback position in the content (e.g., using the update unit 810) according to the playback progress through the content at the second corresponding content playback speed (e.g., using the playback unit 812); including updating the position of the visual indication of the current playback position within the swipe bar; and maintain the corresponding playback time indication while playing back the content at the second corresponding content playback speed (e.g., using the display enabling unit 804).

[0205] In some embodiments, the processing unit 802 is further configured to, when displaying one or more playback time indications in the brush bar (e.g., using the display enabling unit 804), determine (e.g., using the determination unit 806) that one or more relative time standards for displaying one or more second playback time indications in the brush bar are met, wherein the one or more second playback time indications include a time value based on the relative content time. In some embodiments, the processing unit (802) is further configured to: in response to determining (e.g., using the determination unit 806) that one or more relative time standards are met, display one or more second playback time indications in the brush bar (e.g., using the display enabling unit 804). In some embodiments, the one or more second playback time indications are relative to a starting position in the content. In some embodiments, one or more relative time standards are met when a predetermined amount of time has passed since the brush bar was displayed on the display. In some embodiments, when a swipe bar and one or more playback time indicators are displayed on a display (e.g., using a display enabling unit 804), one or more relative time criteria are met and input for initiating a swipe mode on the electronic device is received (e.g., using a receiving unit 808).

[0206] In some embodiments, the receiving unit (808) is further configured to: receive input for swiping content when one or more second playback time indications in the swipe bar are displayed (e.g., using the display enabling unit 804) and the electronic device (800) is in the swipe mode. In some embodiments, the processing unit (802) is further configured to, in response to receiving input for swiping content, update one or more second playback time indications according to the input for swiping content (e.g., using the updating unit 810). In some embodiments, when the electronic device (800) is in the swipe mode, the swipe bar includes one or more playback time indications, and one or more second playback time indications. In some embodiments, when the electronic device (800) is in the swipe mode, the swipe bar includes one or more second playback time indications, but does not include one or more playback time indications.

[0207] In some embodiments, the receiving unit (808) is further configured to receive input for exiting the swipe mode when the electronic device (800) is in the swipe mode, and the processing unit (802) is further configured to: in response to receiving the input for exiting the swipe mode, display a swipe bar with one or more playback time indications and without one or more second playback time indications on the display (e.g., using the display enabling unit 804). In some embodiments, the processing unit 802 is further configured to update the corresponding playback time indication according to the advancement of the time of day on the electronic device (800) (e.g., using the updating unit 810) when the content is paused on the electronic device and the swipe bar and the corresponding playback time indication are displayed on the display (e.g., using the display enabling unit 804).

[0208] In some embodiments, the processing unit (802) is further configured to detect a change in the content playback speed of the content (e.g., using the detection unit 814) while playing the content on the electronic device (e.g., using the playback unit 812) and displaying the swipe bar and the corresponding playback time indication on the display (e.g., using the display enabling unit 804). In some embodiments, the processing unit (802) is further configured to, in response to detecting (e.g., using the detection unit 814) a change in the content playback speed of the content, update the corresponding playback time indication by an amount (e.g., using the update unit 810) that is greater than the amount of the content played at the changed content playback speed.

[0209] In some embodiments, the receiving unit (808) is further configured to: while displaying the swipe bar on the display (e.g., using the display enabling unit 804), detect an input at the touch-sensitive surface corresponding to a request to display multiple visual indications of different actions accessible from the touch-sensitive surface (e.g., using the display enabling unit 804). In some embodiments, the processing unit (802) is further configured to, in response to detecting an input corresponding to a request to display multiple visual indications of different actions accessible from the touch-sensitive surface, display multiple visual indications on the display (e.g., using the display enabling unit 804). In some embodiments, the receiving unit (808) is further configured to, while displaying multiple visual indications corresponding to different actions accessible from the touch-sensitive surface (e.g., using the display enabling unit 804), detect additional input on the touch-sensitive surface indicating a possible selection of a corresponding visual indication from the multiple visual indications, the visual indication corresponding to a corresponding action from the different actions. In some embodiments, the processing unit (802) is further configured to: in response to detecting additional input, change the appearance of the corresponding visual indication relative to the appearance of other visual indications in the plurality of visual indications (e.g., using the display enabling unit 804).

[0210] In some embodiments, the receiving unit (808) is further configured to: receive input at the touch-sensitive surface to select the visual indication when (e.g., using the display enabling unit 804) a possible selection of the corresponding visual indication is indicated. In some embodiments, the processing unit (802) is further configured to: in response to (e.g., using the receiving unit 808) receiving input to select the visual indication, perform (e.g., using the execution unit 816) a corresponding action corresponding to the corresponding visual indication at the electronic device.

[0211] Reference above FIG. 7A to FIG. 7G The operation described may be optionally performed by Figure 1A to Figure 1B or Figure 8 . For example, display operations 702, 704, and 718 and receiving operation 716 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on the touch-sensitive surface or touch screen, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186, and determines whether the first contact at the first position on the touch-sensitive surface or touch screen corresponds to a predefined event or sub-event, such as the selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how to update the content displayed by the application based on the GUI updater 178. Figure 1A to Figure 1B or Figure 8 The components depicted in the figure are used to implement other processes.

[0212] For the purpose of explanation, the foregoing description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. The embodiments are selected and described in order to best illustrate the principles of the present invention and its practical application, so that other technical personnel in the field can best use the present invention and the various described embodiments with various modifications suitable for the specific purpose contemplated.

Claims

1. A method for displaying content, comprising: At an electronic device in communication with a display and one or more input devices: Displaying a playback user interface via the display, the playback user interface being configured to play back content on the electronic device, the playback user interface displaying a swipe bar for navigating through the content, wherein the swipe bar comprises: a visual indication of a current playback position within a content item currently displayed in the playback user interface; and One or more playback time indications, where: A respective playback time indication of the one or more playback time indications displays a current time of day at the electronic device; and the corresponding playback time indication being displayed at a location corresponding to the visual indication of the current playback position within the content item; receiving, via the one or more input devices, an input corresponding to a request to swipe the content item while displaying the playback user interface configured to play back content on the electronic device; and In response to receiving the input: updating the current playback position within the content item based on the input; and Based on determining that the current time at the electronic device has advanced since receiving the input, updating the corresponding playback time indication to display an updated current time of day based on the advancement of the current time at the electronic device, regardless of changes in the current playback position caused by the received input, wherein the corresponding playback time indication is displayed at a position corresponding to the visual indication of the updated current playback position within the content item.

2. The method according to claim 1, further comprising: Prior to displaying the swipe bar on the display, while the playback user interface is displayed on the display, receiving input corresponding to a request to display the swipe bar via the one or more input devices; as well as In response to receiving the input corresponding to a request to display the swipe bar, the swipe bar is displayed on a display.

3. The method of claim 1 , wherein updating the current playback position within the content item based on the input comprises: updating the position of the visual indication of the current playback position within the swipe bar; as well as When the current playback position within the content item changes, the position of the corresponding playback time indication on the display is updated according to the movement of the visual indication of the current playback position within the content item.

4. The method according to claim 1, wherein the content item currently displayed in the playback user interface is played at a corresponding content playback speed, the method further comprising: while displaying the swipe bar and the corresponding playback time indication on the display, playing the content item at a second corresponding content playback speed different from the corresponding content playback speed; as well as While playing the content item at the second corresponding content playback speed: Updating the current playback position within the content item includes: updating a position of the visual indication of the current playback position within the swipe bar based on playback progress through the content item at the second corresponding content playback speed; as well as The corresponding playback time indication is updated based on a second advancement of the current time of day at the electronic device.

5. The method according to claim 1, further comprising: while displaying the one or more playback time indications in the swipe bar, determining that one or more relative time criteria for displaying one or more second playback time indications in the swipe bar are satisfied, wherein the one or more second playback time indications include time values ​​based on relative content time; as well as In response to determining that the one or more relative time criteria are satisfied, the one or more second playback time indications are displayed in the swipe bar.

6. The method of claim 5, wherein the one or more second playback time indications include a corresponding second playback time indication corresponding to the current playback position within the content item relative to a start position in the content item.

7. The method of claim 6, wherein the corresponding second playback time indication is displayed within an image corresponding to the current playback position within the content item during the input corresponding to the request to swipe the content item.

8. The method according to claim 5, wherein the swiping bar also comprises: the one or more playback time indications; as well as The one or more second playback time indications.

9. The method according to claim 1, wherein: The one or more playback time indications include a second respective playback time indication displayed at the end of the swipe bar corresponding to the end of the content item; and The second corresponding playback time indication is based on: the current time of day at the electronic device; as well as The remaining duration of the content item, wherein the remaining duration comprises an amount of time taken to play the content item from the current playback position to an end of the content item at a corresponding content playback speed.

10. The method according to claim 9, further comprising: receiving, via the one or more input devices, a second input for swiping through the content item while displaying the swipe bar and the second corresponding playback time indication on the display; as well as In response to receiving the second input for swiping the content item: updating the current playback position within the content item, comprising updating a position of the visual indication of the current playback position within the swipe bar based on the second input for swiping through the content item; updating the corresponding playback time indication based on a second advancement of the current time of day at the electronic device; as well as The second corresponding playback time indication is updated according to the updated current playback position within the content item, the updated second corresponding playback time indication displays the updated time at the electronic device, and the playback of the content item starting from the updated current playback position within the content item at the electronic device will end at the corresponding content playback speed.

11. The method according to claim 9, further comprising: When the content item is played on the electronic device, and when the swipe bar and the corresponding playback time indication are displayed on the display, detecting a change in a content playback speed of the content item; as well as In response to detecting a change in a content playback speed of the content item: updating the second corresponding playback time indication by an amount greater than the amount of content that has been played at the changed playback speed of the content; and The corresponding playback time indication is updated based on a second advancement of the current time of day at the electronic device.

12. The method according to claim 9, further comprising: When the content item is paused on the electronic device and the swipe bar and the corresponding playback time indication are displayed on the display, the corresponding playback time indication and the second corresponding playback time indication are updated according to a second advancement of the current time of day at the electronic device.

13. The method according to claim 1, further comprising: When the content item is paused on the electronic device and the swipe bar and the corresponding playback time indication are displayed on the display, the corresponding playback time indication is updated according to a second advancement of the current time of day at the electronic device.

14. An electronic device comprising: one or more processors in communication with the display and one or more input devices; Memory; as well as 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 for performing the method of any one of claims 1 to 13.

15. A non-transitory computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions that, when executed by one or more processors of an electronic device that communicates with a display and one or more input devices, cause the electronic device to perform a method according to any one of claims 1 to 13.

16. A computer product comprising one or more programs, the one or more programs comprising instructions which, when executed by one or more processors of an electronic device in communication with a display and one or more input devices, cause the electronic device to perform the method according to any one of claims 1 to 13.

Images