Providing user interface and managing playback of media based on usage context

Abstract

The invention relates to providing a user interface and managing playback of media based on usage context. The present disclosure generally relates to providing a user interface based on a usage context. An electronic device in communication with the display may cause a user interface to be displayed on the display screen. The user interface includes a first interface element having a map and a second interface element having a media playback control. In accordance with a determination that the device is in the first usage context, the user interface includes a third element that includes a first control that, when selected, performs a first function selected based on the first usage context. In accordance with a determination that the device is in a second usage context different from the first usage context, the user interface includes a third interface element including a second control and not including the first control, the second control when selected performing a second function selected based on the second usage context.

Description

[0001] This application is a divisional application of the application with international application number PCT / US2020 / 031528, international application date May 5, 2020, date of entry into the Chinese national phase November 3, 2021, national application number 202080033401.0, and invention name “Providing user interface based on usage context and managing media playback”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Patent Application No. 16 / 533,540, filed on August 6, 2019, entitled “PROVIDING USER INTERFACES BASED ONUSE CONTEXTS AND MANAGING PLAYBACK OF MEDIA,” which claims priority to U.S. Provisional Patent Application Serial No. 62 / 844,111, filed on May 6, 2019, entitled “PROVIDING USER INTERFACES BASED ONUSE CONTEXTS AND MANAGING PLAYBACK OF MEDIA,” the contents of which are hereby incorporated by reference in their entirety. Technical Field

[0004] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for user interfaces. Background Art

[0005] The user interface may provide information to the user and access to computing applications in multiple environments, including while driving. In the driving environment, the user interface may provide access to driving-related applications. Summary of the invention

[0006] Currently, there are some technologies for providing applications to users. However, these technologies are generally cumbersome and inefficient. In addition, they are also dangerous when users must interact with these systems when participating in activities such as driving. For example, some prior art uses complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art requires more time than required, which results in wasting the user's time and device energy. This latter consideration is particularly important in battery-powered devices. The latter consideration is also particularly relevant in driving situations when the user has limited time and attention to devote to user interface interaction and therefore requires an interface that is both time-efficient and attention-efficient.

[0007] Thus, the present technology provides a faster, more efficient method and interface for electronic devices to provide the functionality of an application to a user who is engaged in an activity such as driving. Such methods and interfaces optionally supplement or replace other methods for providing the functionality of an application to a user. Such methods and interfaces reduce the cognitive burden on the user and produce a more efficient human-computer interface while requiring less time and attention. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0008] In some embodiments, a method is disclosed for execution at an electronic device in communication with a display screen. The method includes receiving an input corresponding to a request to display a user interface on the display screen. The method also includes, in response to receiving the input, causing the user interface to be displayed on the display screen. Based on determining that the electronic device is in a first usage context, the user interface caused to be displayed on the display screen includes: a first interface element, the first interface element including a map selected based on the current location of the electronic device; a second interface element, the second interface element including a media playback control; and a third interface element, the third interface element including a first control, the first control when selected performs a first function selected based on the first usage context. Based on determining that the electronic device is in a second usage context different from the first usage context, the user interface caused to be displayed on the display screen includes: the first interface element, the first interface element including the map selected based on the current location of the electronic device; the second interface element, the second interface element including a media playback control; and the third interface element, the third interface element including a second control but not including the first control, the second control when selected performs a second function selected based on the second usage context.

[0009] In some embodiments, a non-transitory computer-readable storage medium is disclosed, which stores one or more programs, and the one or more programs are configured to be executed by one or more processors of an electronic device that communicates with a display screen. The one or more processors include instructions for receiving input, the input corresponding to a request to display a user interface on the display screen. The one or more processors also include instructions for causing the user interface to be displayed on the display screen in response to receiving the input. According to determining that the electronic device is in a first usage context, the user interface that is caused to be displayed on the display screen includes: a first interface element, the first interface element includes a map selected based on the current location of the electronic device; a second interface element, the second interface element includes a media playback control; and a third interface element, the third interface element includes a first control, and the first control performs a first function selected based on the first usage context when selected. According to determining that the electronic device is in a second usage context different from the first usage context, the user interface that is caused to be displayed on the display screen includes: the first interface element, the first interface element includes the map selected based on the current location of the electronic device; the second interface element, the second interface element includes a media playback control; and the third interface element, the third interface element includes a second control but does not include the first control, and the second control performs a second function selected based on the second usage context when selected.

[0010] In some embodiments, a transient computer-readable storage medium is disclosed, which stores one or more programs, and the one or more programs are configured to be executed by one or more processors of an electronic device that communicates with a display screen. The one or more processors include instructions for receiving input, the input corresponding to a request to display a user interface on the display screen. The one or more processors also include instructions for causing the user interface to be displayed on the display screen in response to receiving the input. According to determining that the electronic device is in a first usage context, the user interface that is caused to be displayed on the display screen includes: a first interface element, the first interface element includes a map selected based on the current location of the electronic device; a second interface element, the second interface element includes a media playback control; and a third interface element, the third interface element includes a first control, and the first control performs a first function selected based on the first usage context when selected. According to determining that the electronic device is in a second usage context different from the first usage context, the user interface that is caused to be displayed on the display screen includes: the first interface element, the first interface element includes the map selected based on the current location of the electronic device; the second interface element, the second interface element includes a media playback control; and the third interface element, the third interface element includes a second control but does not include the first control, and the second control performs a second function selected based on the second usage context when selected.

[0011] In some embodiments, an electronic device that communicates with a display screen is disclosed. The electronic device includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors. The one or more processors include instructions for receiving input corresponding to a request to display a user interface on the display screen. The one or more processors also include instructions for causing the user interface to be displayed on the display screen in response to receiving the input. According to determining that the electronic device is in a first usage context, the user interface that is caused to be displayed on the display screen includes: a first interface element, the first interface element includes a map selected based on the current location of the electronic device; a second interface element, the second interface element includes a media playback control; and a third interface element, the third interface element includes a first control, and the first control performs a first function selected based on the first usage context when selected. According to determining that the electronic device is in a second usage context different from the first usage context, the user interface that is caused to be displayed on the display screen includes: the first interface element, the first interface element includes the map selected based on the current location of the electronic device; the second interface element, the second interface element includes a media playback control; and the third interface element, the third interface element includes a second control but does not include the first control, and the second control performs a second function selected based on the second usage context when selected.

[0012] In some embodiments, an electronic device that communicates with a display screen is disclosed. The electronic device includes a device for receiving an input corresponding to a request to display a user interface on the display screen. The electronic device includes a device for causing the user interface to be displayed on the display screen in response to receiving the input. According to determining that the electronic device is in a first usage context, the user interface that is caused to be displayed on the display screen includes: a first interface element, the first interface element includes a map selected based on the current location of the electronic device; a second interface element, the second interface element includes a media playback control; and a third interface element, the third interface element includes a first control, and the first control performs a first function selected based on the first usage context when selected. According to determining that the electronic device is in a second usage context different from the first usage context, the user interface that is caused to be displayed on the display screen includes: the first interface element, the first interface element includes the map selected based on the current location of the electronic device; the second interface element, the second interface element includes a media playback control; and the third interface element, the third interface element includes a second control but does not include the first control, and the second control performs a second function selected based on the second usage context when selected.

[0013] In some embodiments, a method performed at a first electronic device having one or more antennas is disclosed. The method includes, when the first electronic device is connected to an accessory including one or more output devices, providing information to a second electronic device via the one or more antennas indicating that the first electronic device is available to retransmit content from the second electronic device to the accessory. The method also includes, after providing the information to the second electronic device, receiving media from the second electronic device via the one or more antennas. The method also includes transmitting the media to the accessory for presentation via one or more output devices of the accessory. Additionally, the method includes, after transmitting the media to the accessory for presentation via the one or more output devices, detecting that the first electronic device is no longer connected to the accessory. The method includes, in response to detecting that the first electronic device is no longer connected to the accessory, removing the availability of information indicating that the first electronic device is available to retransmit content from a remote device to the accessory.

[0014] In some embodiments, a non-transitory computer-readable storage medium is disclosed, which stores one or more programs configured to be executed by one or more processors of a first electronic device having one or more antennas. The one or more processors include instructions for performing the following operations: when the first electronic device is connected to an accessory including one or more output devices, provide information indicating that the first electronic device can be used to retransmit content from the second electronic device to the accessory via one or more antennas to a second electronic device. The one or more processors also include instructions for performing the following operations: after providing the information to the second electronic device, receive media from the second electronic device via one or more antennas. The one or more processors also include instructions for performing the following operations: transferring the media to the accessory for presentation via one or more output devices of the accessory. In addition, the one or more processors include instructions for performing the following operations: after transferring the media to the accessory for presentation via one or more output devices, detecting that the first electronic device is no longer connected to the accessory. The one or more processors include instructions for performing the following operations: in response to detecting that the first electronic device is no longer connected to the accessory, removing the availability of information indicating that the first electronic device can be used to retransmit content from a remote device to the accessory.

[0015] In some embodiments, a transient computer-readable storage medium is disclosed that stores one or more programs configured to be executed by one or more processors of a first electronic device having one or more antennas. The one or more processors include instructions for performing the following operations: when the first electronic device is connected to an accessory including one or more output devices, providing information indicating that the first electronic device can be used to retransmit content from the second electronic device to the accessory via one or more antennas to a second electronic device. The one or more processors also include instructions for performing the following operations: after providing the information to the second electronic device, receiving media from the second electronic device via one or more antennas. The one or more processors also include instructions for performing the following operations: transferring the media to the accessory for presentation via one or more output devices of the accessory. In addition, the one or more processors include instructions for performing the following operations: after transferring the media to the accessory for presentation via one or more output devices, detecting that the first electronic device is no longer connected to the accessory. The one or more processors include instructions for performing the following operations: in response to detecting that the first electronic device is no longer connected to the accessory, removing the availability of information indicating that the first electronic device can be used to retransmit content from a remote device to the accessory.

[0016] In some embodiments, a first electronic device having one or more antennas is disclosed. The first electronic device includes one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more processors include instructions for performing the following operations: when the first electronic device is connected to an accessory including one or more output devices, provide information indicating that the first electronic device can be used to retransmit content from the second electronic device to the accessory via one or more antennas to the second electronic device. The one or more processors also include instructions for performing the following operations: after providing the information to the second electronic device, receive media from the second electronic device via one or more antennas. The one or more processors also include instructions for performing the following operations: transferring the media to the accessory for presentation via one or more output devices of the accessory. In addition, the one or more processors include instructions for performing the following operations: after transferring the media to the accessory for presentation via one or more output devices, detecting that the first electronic device is no longer connected to the accessory. The one or more processors also include instructions for performing the following operations: in response to detecting that the first electronic device is no longer connected to the accessory, removing the availability of information indicating that the first electronic device can be used to retransmit content from a remote device to the accessory.

[0017] In some embodiments, a first electronic device having one or more antennas is disclosed. The first electronic device includes a device for performing the following operations: when the first electronic device is connected to an accessory including one or more output devices, providing information to a second electronic device via one or more antennas indicating that the first electronic device can be used to retransmit content from the second electronic device to the accessory. The first electronic device also includes a device for performing the following operations: after providing the information to the second electronic device, receiving media from the second electronic device via one or more antennas. The first electronic device also includes a device for performing the following operations: transferring the media to the accessory for presentation via one or more output devices of the accessory. In addition, the first electronic device includes a device for performing the following operations: after transferring the media to the accessory for presentation via one or more output devices, detecting that the first electronic device is no longer connected to the accessory. The first electronic device includes a device for performing the following operations: in response to detecting that the first electronic device is no longer connected to the accessory, removing the availability of information indicating that the first electronic device can be used to retransmit content from a remote device to the accessory.

[0018] In some embodiments, a method is disclosed that is performed at a first electronic device having a display device and one or more input devices. The method includes receiving a request to display available wireless media receiver devices via one or more input devices. The method also includes, in response to receiving the request, displaying a user interface for selecting a wireless media receiver for media from the first electronic device via the display device, including: based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, displaying an enable representation for selecting an accessory to receive wireless media, wherein the enable representation for selecting an accessory to receive wireless media establishes a connection between the first electronic device and a second electronic device connected to the accessory; and based on determining that a wireless connection with an accessory for receiving media via a wireless connection is unavailable, abandoning displaying an enable representation for selecting an accessory to receive wireless media, wherein when no device is connected to the accessory, the connection with the accessory for receiving media via a wireless connection is unavailable.

[0019] In some embodiments, a non-transitory computer-readable storage medium is disclosed, which stores one or more programs, and the one or more programs are configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices. The one or more processors include instructions for performing the following operations: receiving a request to display available wireless media receiver devices via one or more input devices. The one or more processors also include instructions for performing the following operations: in response to receiving the request, displaying a user interface for selecting a wireless media receiver for media from a first electronic device via a display device, including: displaying an enable representation for selecting an accessory to receive wireless media based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, wherein the enable representation for selecting an accessory to receive wireless media establishes a connection between the first electronic device and a second electronic device connected to the accessory; and abandoning displaying an enable representation for selecting an accessory to receive wireless media based on determining that a wireless connection with an accessory for receiving media via a wireless connection is unavailable, wherein when no device is connected to the accessory, the connection with the accessory for receiving media via a wireless connection is unavailable.

[0020] In some embodiments, a transient computer-readable storage medium is disclosed, which stores one or more programs, and the one or more programs are configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices. The one or more processors include instructions for performing the following operations: receiving a request to display available wireless media receiver devices via one or more input devices. The one or more processors also include instructions for performing the following operations: in response to receiving the request, displaying a user interface for selecting a wireless media receiver for media from a first electronic device via a display device, including: displaying an enable representation for selecting an accessory to receive wireless media based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, wherein the enable representation for selecting an accessory to receive wireless media establishes a connection between the first electronic device and a second electronic device connected to the accessory; and abandoning displaying an enable representation for selecting an accessory to receive wireless media based on determining that a wireless connection with an accessory for receiving media via a wireless connection is unavailable, wherein when no device is connected to the accessory, the connection with the accessory for receiving media via a wireless connection is unavailable.

[0021] In some embodiments, a first electronic device having a display device and one or more input devices is disclosed. The first electronic device includes one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The one or more processors include instructions for performing the following operations: receiving a request to display available wireless media receiver devices via one or more input devices. The one or more processors also include instructions for performing the following operations: in response to receiving the request, displaying a user interface for selecting a wireless media receiver for media from the first electronic device via a display device, including: displaying an enable representation for selecting an accessory to receive wireless media based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, wherein the enable representation for selecting an accessory to receive wireless media establishes a connection between the first electronic device and a second electronic device connected to the accessory; and based on determining that a wireless connection with an accessory for receiving media via a wireless connection is unavailable, abandoning displaying an enable representation for selecting an accessory to receive wireless media, wherein when no device is connected to the accessory, the connection with the accessory for receiving media via a wireless connection is unavailable.

[0022] In some embodiments, a first electronic device having a display device and one or more input devices is disclosed. The first electronic device includes a device for performing the following operations: receiving a request to display available wireless media receiver devices via one or more input devices. The first electronic device also includes a device for performing the following operations: in response to receiving the request, displaying a user interface for selecting a wireless media receiver for media from the first electronic device via the display device, including: based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, displaying an enablement representation for selecting an accessory to receive wireless media, wherein the enablement representation for selecting an accessory to receive wireless media establishes a connection between the first electronic device and a second electronic device connected to the accessory; and based on determining that a wireless connection with an accessory for receiving media via a wireless connection is unavailable, abandoning displaying an enablement representation for selecting an accessory to receive wireless media, wherein when no device is connected to the accessory, the connection with the accessory for receiving media via a wireless connection is unavailable.

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

[0024] Thus, a faster, more efficient method and interface is provided for devices for providing the functionality of an application to a user engaging in an activity such as driving, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for providing the functionality of an application to a user engaging in an activity. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] 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, wherein like reference numerals designate corresponding parts throughout the several views.

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

[0027] Figure 1B is a block diagram illustrating exemplary components for event handling according to some embodiments.

[0028] Figure 2 A portable multifunction device with a touch screen is shown in accordance with some embodiments.

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

[0030] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown in accordance with some embodiments.

[0031] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface that is separate from the display is shown in accordance with some embodiments.

[0032] Figure 5A A personal electronic device is shown in accordance with some embodiments.

[0033] Figure 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0034] FIG. 6A to FIG. 6AE An exemplary user interface for managing applications for different usage scenarios according to various embodiments presented herein is shown.

[0035] FIG. 7A to FIG. 7B is a flow chart illustrating a method for providing a user interface to manage applications for different usage scenarios.

[0036] FIG. 8A to FIG. 8T An exemplary user interface for managing connections between computing devices is shown.

[0037] FIG. 9A to FIG. 9B is a flow chart illustrating a method for managing connections between computing devices.

[0038] Fig.10 is a flow chart illustrating a method for managing connections between computing devices. DETAILED DESCRIPTION

[0039] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0040] There is a need for electronic devices to provide efficient methods and interfaces for managing applications for different usage scenarios. In one example, a user may be engaged in an activity such as driving, where such techniques may reduce the cognitive burden on the user accessing applications while driving, thereby increasing productivity. In addition, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0041] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an exemplary device of techniques for executing applications for different usage scenarios is provided. FIG. 6A to FIG. 6AE An exemplary user interface for managing applications for different usage scenarios according to various embodiments presented herein is shown. FIG. 7A to FIG. 7B is a flow chart illustrating a method for managing applications for different usage scenarios. FIG. 6A to FIG. 6AE The user interface in is used to illustrate the process described below, including FIG. 7A to FIG. 7B process. FIG. 8A to FIG. 8T An exemplary user interface and transitions thereof for managing connections between computing devices 800A, 800B, 800C, and 800D are shown. FIG. 9A to FIG. 9B is a flow chart illustrating a method for managing connections between computing devices. Fig.10 is a flow chart illustrating a method for managing connections between computing devices. FIG. 8A to FIG. 8T The user interface and its transitions in are used to illustrate the process described below, including FIG. 9A to FIG. 9B and Fig.10 process.

[0042] 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 element. 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.

[0043] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limiting. As used in the description of various described embodiments 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 associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0045] Embodiments of electronic devices, user interfaces for such devices, and processes associated with 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 Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or trackpads).

[0046] 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, mouse and / or joystick.

[0047] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk 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, and / or a digital video player application.

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

[0049] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. 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." Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral device interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 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.

[0050] 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 into 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 units of pressure). 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).

[0051] 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 corresponding 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, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although 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 a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

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

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

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

[0055] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as 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, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to 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 communications (NFC) fields, such as through short-range communications radio components. 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.

[0056] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a 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 humans. 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 headset 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).

[0057] 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, a depth camera controller 169, 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 other input control devices 116. The 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 input controller 160 is optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing 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. The one or more buttons optionally include a push button (e.g., Figure 2 206).

[0058] A quick press of the push button optionally disengages the lock of 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.

[0059] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. 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 or all of the visual output optionally corresponds to user interface objects.

[0060] 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 (and any movement or interruption of the contact) on the touch screen 112 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.

[0061] 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 in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

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

[0063] In some embodiments, the touch-sensitive display of touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; (5) U.S. patent application No. 11 / 086,694, filed on January 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive and (9) U.S. patent application 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.

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

[0065] In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad 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 touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0066] The device 100 also includes a power system 162 for powering the various components. The 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 device.

[0067] 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 a 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 images 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 acquired for video conferencing while the user is viewing other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and 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.

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

[0069] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to force sensor controller 159 in 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 a 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 back of device 100, opposite touch screen display 112 located on the front of device 100.

[0070] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A 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: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 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 (eg, when the user is on a phone call), the proximity sensor turns off and the touch screen 112 is disabled.

[0071] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA 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 intensity 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 juxtaposition or proximity to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., back and forth 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 device 100 , opposite touch screen display 112 located on the front of device 100 .

[0072] 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 is optionally implemented as described in the following U.S. Patent Publication No. 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication No. 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. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

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

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

[0075] 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., a 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 connected to (trademark of Apple Inc.) devices.

[0076] 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 point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a trackpad.

[0077] In some embodiments, 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 device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a software setting is provided to a 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).

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

[0079] 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, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0080] 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 graphics attribute data together if necessary, and then generates screen image data to be output to the display controller 156.

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

[0082] 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).

[0083] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services, such as the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

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

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

[0086] Telephone module 138;

[0087] Video conferencing module 139;

[0088] Email client module 140;

[0089] Instant messaging (IM) module 141;

[0090] Fitness support module 142;

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

[0092] Image management module 144;

[0093] Video player module;

[0094] Music player module;

[0095] Browser module 147;

[0096] Calendar module 148;

[0097] 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 acquired by the user, and a user-created widget 149-6;

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

[0099] Search module 151;

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

[0101] Notepad module 153;

[0102] Map module 154; and / or

[0103] Online video module 155.

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

[0105] 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 phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and the like.

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

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

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

[0109] 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).

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

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

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

[0113] 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 in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

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

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

[0116] 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., converting a user-specified portion of a web page into a desktop widget).

[0117] 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, videos 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.

[0118] 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, and 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.).

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

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

[0121] 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 descriptions of online video applications 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.

[0122] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., 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, so 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.

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

[0124] A predefined set of functions that are performed exclusively through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by the 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 "menu button" is implemented using a trackpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

[0125] 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).

[0126] Event classifier 170 receives event information and determines an application 136-1 and an 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 that indicates one or more current application views 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 application view 191 to which the event information is to be delivered.

[0127] 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 that information is being displayed or is ready to be displayed by the application 136-1, 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.

[0128] 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, one or more accelerometers 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.

[0129] 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).

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

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

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

[0133] 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 for which it was identified as the hit view.

[0134] 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 therefore 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.

[0135] Event distributor module 174 distributes the 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.

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

[0137] 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 of the event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit 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 191 include one or more corresponding event handlers 190. Additionally, 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.

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

[0139] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touches or touch movements. 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 a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another orientation (e.g., from a portrait orientation to a landscape 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).

[0140] 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 definitions of events (e.g., predefined sub-event sequences), 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 touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0141] In some embodiments, event definition 187 includes definitions of events for corresponding 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.

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

[0143] When a corresponding event recognizer 180 determines that a sequence 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.

[0144] In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers 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.

[0145] 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 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

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

[0147] 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 a new user interface object or updates the position of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

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

[0149] 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 that utilize 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.

[0150] Figure 2 A portable multifunction device 100 with a touch screen 112 is shown according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of the graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of a finger that has made contact with the 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 does not select the 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.

[0151] The device 100 optionally also includes one or more physical buttons, such as a "home" or 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.

[0152] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a subscriber 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 in a depressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval has passed; 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.

[0153] Figure 3 300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuits (sometimes referred to as chipsets) that interconnect system components and control communications between system components. Device 300 includes an input / output (I / O) interface 330 having 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 touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to the above referenced device). Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1AThe memory 370 may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may optionally include 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 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores data related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores 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 portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0154] Figure 3 Each element in the above-mentioned elements is optionally stored in one or more memory devices of the previously mentioned memory devices. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as separate software programs, processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0155] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0156] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 is shown in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0157] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0158] Time 404;

[0159] Bluetooth indicator 405;

[0160] Battery status indicator 406;

[0161] A tray 408 with icons for commonly used applications, such as:

[0162] o an icon 416 of the phone module 138 labeled “Phone”, the icon 416 optionally including an indicator 414 of the number of missed calls or voicemails;

[0163] o an icon 418 of the email client module 140 labeled “Mail”, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0164] o an icon 420 labeled “Browser” of the browser module 147; and

[0165] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0166] Icons for other apps, such as:

[0167] o Icon 424 labeled “Messages” of IM module 141;

[0168] o Icon 426 labeled “Calendar” of calendar module 148;

[0169] o Icon 428 labeled “Photos” of the image management module 144;

[0170] o Icon 430 labeled “Camera” of camera module 143;

[0171] o Icon 432 labeled “Online Video” of the online video module 155;

[0172] o Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

[0173] o an icon 436 labeled “MAP” of the map module 154;

[0174] o Icon 438 labeled “Weather” of the Weather widget 149-1;

[0175] o Icon 440 labeled “Clock” of the alarm clock widget 149-4;

[0176] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0177] o Icon 444 labeled "Notepad" of the Notepad module 153; and

[0178] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .

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

[0180] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet 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 sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0181] Although some of the examples below will be 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 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4BWhen 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 to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0182] 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). For 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 the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

[0183] Figure 5A An exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) and some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, hereinafter referred to as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to the touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

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

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

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

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

[0188] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may, for example, cause the computer processors to perform the techniques described below, including processes 700, 900, and 1000 ( FIG. 7A to FIG. 7B , FIG. 9A to FIG. 9B and Fig.10 ). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0189] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0190] 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 is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4A In some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the 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 touch screen 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 touch screen 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 touch screen display) that is controlled by the user to deliver 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 trackpad or touch screen), 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).

[0191] 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 begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). 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.

[0192] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the intensity of the swipe contact to achieve the purpose of determining the characteristic strength.

[0193] The intensity of a contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0194] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0195] 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 with a corresponding contact (or contacts), wherein the corresponding press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in intensity of the corresponding contact above the press input intensity threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in intensity of the corresponding contact below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0196] 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 a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact to below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity 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, a subsequent decrease in contact intensity 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).

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

[0198] As used herein, an "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application using an installer that extracts program portions from a downloaded software package and integrates the extracted portions with the operating system of a computer system.

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

[0200] The active application currently displayed on the display of the device on which the application is being used;

[0201] Background applications (or background processes), which are not currently displayed but whose processes are being processed by one or more processors; and

[0202] Not running but stored in memory (volatile and non-volatile respectively)

[0203] A suspended or dormant application that contains status information that can be used to resume execution of the application.

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

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

[0206] FIG. 6A to FIG. 6AE Figures 1 and 2 show exemplary user interfaces for managing applications for different usage scenarios according to various embodiments presented herein. The user interfaces in these figures are used to illustrate the processes and techniques described below, including FIG. 7A to FIG. 7B The processes and techniques described.

[0207] Fig. 6A An exemplary user interface 600 for managing applications for different usage scenarios according to various embodiments presented herein is shown. In some examples, the user interface 600 is provided by an electronic device 600A in operative communication with a display screen 600B (e.g., the display screen 600B that displays the user interface 600). In some embodiments, the device 600A and the display screen 600B include some or all of the features of the device 100, device 300, or device 500 discussed above.

[0208] In some embodiments, device 600A is a mobile phone connected to display screen 600B or an external electronic device with display screen 600B in red (e.g., USB, Lightning) or wirelessly (e.g., Bluetooth, WiFi). In some embodiments, display screen 600B is set on the dashboard of the car. In some embodiments, according to various embodiments discussed herein, the mobile phone (e.g., device 600A) sends a command signal to generate a user interface 600 at display screen 600B. In addition, in some embodiments, the user interaction detected at display screen 600B is sent to the mobile phone (e.g., device 600A). In some embodiments of these embodiments, the user interface 600 described herein is provided at the display screen 600B of the electronic device (e.g., device 600A) itself.

[0209] like Fig. 6A As shown, user interface 600 includes a first portion 602 and a second portion 604. First portion 602 is disposed along a border of user interface 600 and includes a shortcut menu 606. Shortcut menu 606 includes three shortcut affordances 608, 612, and 616. Each shortcut affordance is in a corresponding shortcut position (e.g., 610, 614, and 618).

[0210] In some embodiments, shortcut affordances 608, 612, and 616 belong to different categories of applications. In some embodiments, shortcut affordance 608 belongs to an application in a map category, shortcut affordance 612 belongs to an application in a music category, and shortcut affordance 616 belongs to an application in a communication (or other) category. Each shortcut affordance launches, activates, or otherwise causes display of its corresponding application in second portion 604.

[0211] The first portion 602 provides status information. The status information includes the current time 620 and network connectivity 622 of the device 600A. The first portion also provides an icon navigation affordance 626 for navigating between applications and / or pages on the user interface 600. Although the first portion 602 is disposed along the vertical border of the user interface 600, in some embodiments, the first portion 602 is disposed along the horizontal border of the user interface 600, such as above or below the second portion 604.

[0212] like Figure 6BAs shown, device 600A causes display screen 600B to display user interface 600 as dashboard interface 624. For example, device 600A receives an input corresponding to a request to display dashboard interface 624 on display screen 600B. In some embodiments, the input corresponds to a request to turn on display screen 600B and / or connect device 600A to display screen 600B. In some embodiments of these embodiments, dashboard interface 624 is provided in the form of a startup screen of display screen 600B, so when display screen 600B is started (e.g., woken up or turned on), device 600A causes dashboard interface 624 to be displayed on display screen 600B. In some embodiments, dashboard interface 624 is not provided in the form of a startup screen or first page displayed on display screen 600B, as shown by page indicator 628.

[0213] Dashboard interface 624 includes three exemplary shortcut affordances (a map shortcut affordance 608A located in a first position (eg, Fig. 6A 610 in the figure), a music shortcut indicator 610A located at a second position (e.g., Fig. 6A 612) and a communication shortcut indicator 614A located at a third position (e.g., Fig. 6A The dashboard interface 624 also includes status information. The status information includes the current time 620 and the network connectivity 622.

[0214] Dashboard interface 624 also includes icon navigation affordance 626, map widget 630, predicted destination widget 634, music playback widget 636, and communication suggestion widget 642. Map widget 630 includes map information 632. Predicted destination widget 634 includes predicted destination. Music playback widget 636 includes media playback controls, play affordance 638, and fast forward affordance 640. And communication suggestion widget 642 performs communication functions. Communication functions are associated with applications associated with communication application 644.

[0215] Based on one or more usage scenarios of device 600A, the predicted destination desktop widget 634 and the communication suggestion desktop widget 642 are displayed (or stopped being displayed). The usage scenario may, for example, include one or more states of device 600A (e.g., the location of the electronic device). In some embodiments, the usage scenario is determined by device 600A and / or one or more other devices (e.g., one or more servers). However, for ease of explanation, the foregoing description will only refer to device 600A for determining one or more usage scenarios.

[0216] In some embodiments, device 600A causes display or cessation of display of predicted destination widget 634 and communication suggestion widget 642 based on a determination of one or more usage contexts of device 600A.

[0217] In some embodiments, based on the usage context of device 600A, communication suggestion widget 642 shows an indication of "Call Rich". The usage context determines that "Rich" is the most frequent contact associated with device 600A based on device 600A. In some embodiments, based on one or more usage contexts, one or more widgets including map widget 630 and music playback widget 636 are not displayed, so the usage context of device 600A has no effect on how map widget 630 or music playback widget 636 are displayed.

[0218] like Figure 6B As shown, while dashboard interface 624 is displayed, device 600A detects input 695A on predicted destination widget 634 .

[0219] like Figure 6C As shown, in response to detecting input 695A, device 600A causes map widget 630 to display map information 646. Map information 646 includes route information and navigation status information (e.g., "20 minutes from home"). Map information 646 is different from map information 632 because it includes route information. Route information is information that is updated based on the movement of device 600A, such as Figure 6C In other words, in response to detecting input 695A, device 600A updates map widget 630 to provide navigation information for the user of device 600A to navigate to the predicted destination.

[0220] Additionally, updating the map widget 630 to display map information 646 causes the device 600A to operate in a new use context. Prior to updating the map widget 630, the device 600A was operating in a non-navigation mode. However, when displaying route information, the device 600A is operating in a navigation mode. In response to operating in the navigation mode, 600A causes an estimated time of arrival ("ETA") widget 648 to be displayed. The ETA widget 648 includes information that displays the ETA from a location. Here, in Figure 6C , the ETA widget 648 shows that the device 600A is twenty minutes away from home (eg, a home location) and has replaced the predicted destination widget 634.

[0221] Nineteen minutes later, Fig.6DAs shown, device 600A is one minute away from home (e.g., a location associated with the name "home"). When device 600A is within a predetermined distance (e.g., 5 miles) or time (e.g., 1 minute) from home, device 600A begins operating in the new use context. Thus, based on determining that device 600A is a predetermined distance or time away from home, device 600A causes garage door widget 652 to be displayed to perform a door opening function via garage door application icon 654. Additionally, as shown Fig.6D As shown, device 600A causes an animation showing garage door widget 652 sliding upward or being placed on top of communication suggestion widget 642.

[0222] like Fig. 6E As shown, the animation is complete and device 600A causes garage door widget 652 to be displayed. While displaying garage door widget 652, device 600A detects input 695B on garage door widget 652. In response to detecting input 695B, device 600A causes the garage door to open at the home location. Here, garage door widget 652 performs the function of opening the garage door without causing display on display screen 600B, and without causing a discrete user interface of the application represented by garage door application icon 654 to be displayed.

[0223] like Fig. 6F As shown, device 600A operates in another use scenario. Device 600A leaves home and goes to work (e.g., a business location). Therefore, based on determining that device 600A is a predetermined distance or time away from home, device 600A causes garage door widget 658 to be displayed. Garage door widget 658 or a modified version of garage door widget 652 performs a door closing function.

[0224] like Figure 6G As shown, while the garage door desktop widget 658 is displayed, the device 600A detects an input 695C on the garage door desktop widget 658. In response to detecting the input 695C, the device 600A causes the garage door to close at the home location. Here, the garage door desktop widget 658 causes the garage door to close.

[0225] like Figure 6H As shown, device 600A has traveled thirty minutes away from home and is within forty-five minutes of work. During this period, device 600A has begun to operate in another use scenario because device 600A leaves home at a predetermined time (e.g., or time range). Therefore, based on determining that device 600A leaves a certain location at a predetermined time, device 600A causes restaurant desktop widget 662 to be displayed. Restaurant desktop widget 662 performs the function of ordering food from a restaurant.

[0226] exist Figure 6H When the restaurant widget 662 is displayed in the example embodiment, in some embodiments, one or more other delivery or ordering widgets associated with one or more other types of businesses (e.g., department stores) are displayed. In addition, in some other embodiments, widgets associated with activities (e.g., playing sports) or suggested events (e.g., sports games) are displayed.

[0227] like Fig.6I As shown, device 600A causes restaurant widget 662 to be displayed. In addition, while restaurant widget 662 is displayed, device 600A detects input 695D on restaurant widget 662.

[0228] like Figure 6J As shown, in response to detecting input 695D, device 600A causes restaurant interface 666 to be displayed. Here, device 600A causes restaurant interface 666 to replace dashboard interface 624. In some embodiments, in response to detecting input 607D, device 600A causes an order to be placed at the restaurant without causing restaurant interface 666 to be displayed.

[0229] like Figure 6J As shown, when displaying restaurant interface 666, device 600A causes dashboard navigation affordance 668 to be displayed. Icon navigation affordance 626 and dashboard navigation affordance 668 are different affordances. For example, icon navigation affordance 626 (e.g., Figure 6J ) includes an indication of the icon interface, while dashboard navigation affordance 668 includes an indication of dashboard interface 624. In addition, dashboard navigation affordance 668 allows navigation to dashboard interface 624, while icon navigation affordance 626 allows navigation to the icon interface.

[0230] In some embodiments, dashboard navigation affordance 668 is not displayed when dashboard interface 624 is displayed. In some embodiments, icon navigation affordance 626 is displayed only when dashboard interface 624 is displayed.

[0231] While displaying dashboard navigation affordance 668, device 600A detects input 695E on dashboard navigation affordance 668. Figure 6K As shown, in response to detecting input 695E on dashboard navigation affordance 668, device 600A causes dashboard interface 624 to be redisplayed.

[0232] like Figure 6LAs shown, after moving to the company for another 15 minutes, device 600A has traveled 45 minutes away from home and is within 30 minutes of the company. During this period, device 600A begins to operate in another use context because device 600A has identified a contact ("Jane") associated with an upcoming conference event.

[0233] like Figure 6L As shown, device 600A causes communication suggestion widget 672 to be displayed to call Jane using the application associated with communication application icon 674. Here, it is worth noting that communication application icon 674 is different from communication application icon 644. Therefore, communication suggestion widget 672 can use a different application than communication suggestion widget 642 to communicate with the contact.

[0234] Communication suggestion widget 672 is also from the same category of applications (e.g., the communication category) as shortcut affordance 616 (e.g., the instant messaging shortcut affordance). However, communication suggestion widget 672 is associated with a different application from shortcut affordance 616 in the communication category. In other words, device 600A causes widgets to be displayed that correspond to (or perform functions corresponding to) different functions of applications in the same category.

[0235] In some embodiments, when device 600A causes a function associated with a widget to be executed (e.g., via input on the widget), device 600A will cause the application associated with the widget to replace the application with a shortcut affordance in the same category of applications. In some embodiments, device 600A will not do so, and the application associated with the shortcut affordance in the same category of applications will be retained.

[0236] like Figure 6M As shown, the animation is complete and device 600A causes communication suggestions widget 672 to be displayed. Additionally, while displaying communication suggestions widget 642, device 600A detects input 695F on communication suggestions widget 672. In response to detecting input 695F, device 600A causes communication suggestions widget 672 to call a predetermined phone number to contact Jane. Here, communication suggestions widget 672 performs functionality without causing display of a communication application associated with communication suggestions widget 642 (other embodiments may also occur as discussed above with respect to the garage door widget).

[0237] Device 600A has functionality that allows access to previous desktop widgets, such as Figures 6N to 6Q As shown. Figure 6NAs shown, device 600A is moving toward home. Device 600A causes display of communication suggestions widget 672. While causing communication suggestions widget 672 to be displayed, device 600A detects input 695G on communication suggestions widget 672.

[0238] like Fig.6O As shown, in response to detecting input 695G, device 600A causes restaurant widget 662 to be displayed, which device 600A causes to be displayed before communication suggestion widget 672. While causing restaurant widget 662 to be displayed, device 600A detects input 695H on restaurant widget 662.

[0239] like Figure 6P As shown, in response to detecting input 695H, device 600A causes garage door widget 658 to be displayed, which device 600A causes to be displayed before restaurant widget 662. While causing garage door widget 658 to be displayed, device 600A detects input 695I on garage door widget 658.

[0240] like Figure 6Q As shown, in response to detecting input 695I, device 600A causes garage door widget 652 to be displayed, which device 600A causes to be displayed before garage door widget 658 .

[0241] like Figure 6R As shown, when device 600A is 1 minute away from home, the device detects input 695J. In response to detecting input 695J, device 600A causes the garage door at the home location to open.

[0242] like Figure 6S As shown, device 600A operates in another usage scenario because device 600A leaves home. In response to entering this usage scenario, device 600A causes calendar desktop widget 682 to be displayed. Calendar desktop widget 682 can be displayed when the usage scenario includes device 600A leaving the location for a predetermined time or distance.

[0243] In addition, device 600A also causes predicted destination widget 686 to be displayed because device 600A is operating in non-navigation mode. Predicted destination widget 686 indicates that device 600A is 10 minutes away from the predicted destination ("school"). While displaying predicted destination widget 684, device 600A detects input 695K on predicted destination widget 684.

[0244] like Figure 6TAs shown, in response to detecting input 695K, device 600A causes map desktop widget 630 to display map information 682. In addition, icon navigation affordance 626 is caused to be displayed. While icon navigation affordance 626 is displayed, device 600A detects input 695L on dashboard interface 624 and / or input 695M on icon navigation affordance 626. Either input may correspond to a request to navigate to another page of user interface 600.

[0245] like Figure 6U As shown, in response to detecting input 695L, device 600A causes display of icon interface 688. Icon interface 688 may include a first set of icons corresponding to different applications that device 600A may cause to be displayed on user interface 600. Additionally, in response to detecting input 695L, device 600A causes dashboard navigation affordance 668 to be displayed. While displaying the first plurality of icons, device 600A detects input 695N on icon interface 688.

[0246] like Figure 6V As shown, in response to detecting input 695N, device 600A causes a second set of icons corresponding to different applications to be displayed. The second set of icons may be different from the first set of icons. The second set of icons is displayed on the second page of icon user interface 688 or the third page of user interface 600 (as shown by page indicator 628). In some embodiments, in response to one or more additional inputs, more pages of icons may be displayed.

[0247] In addition, if Figure 6V As shown, dashboard navigation affordance 668 is maintained. While dashboard navigation affordance 668 is displayed, device 600A detects input 695O on dashboard navigation affordance 668.

[0248] like Figure 6W As shown, in response to detecting input 695O, device 600A displays dashboard interface 624. While displaying dashboard interface 624, device 600A detects input 695P on map widget 630.

[0249] like Figure 6X As shown, in response to detecting input 695P, device 600A causes display of map application 690 associated with map widget 630. Map application 690 displays map information 678 and additional map information (e.g., "Turn left in 500 FT"). While displaying map application 690, device 600A detects input 695Q on dashboard navigation affordance 668.

[0250] like Figure 6YAs shown, in response to detecting input 695Q on dashboard navigation affordance 668, device 600A causes display of dashboard interface 624. While dashboard interface 624 is displayed, device 600A detects input 695R on play affordance 638.

[0251] In response to detecting input 695R, as Figure 6Z As shown, device 600A causes the music to be played back. In addition, in response to detecting input 695R, device 600A causes pause enable indication 692 to be displayed by replacing play enable indication 638 with pause enable indication 692. While displaying the music desktop applet, device 600A detects input 695S from a location other than any playback enable indication (e.g., pause enable indication 692 or fast forward enable indication 640) on the music desktop applet.

[0252] like Figure 6AA As shown, in response to detecting input 695S, device 600A causes music application 694 to be displayed. Music application 694 includes pause affordance 692 and fast forward affordance 640, as well as other user interface elements (e.g., rewind affordance, volume control) for interacting with or executing one or more additional functions and additional information (e.g., "Track 1 Hit Mix") of music application 694. While displaying music application 694, device 600A detects input 695T on pause affordance 692.

[0253] like Figure 6AB As shown, in response to detecting input 695T, device 600A causes play enable indication 638 to be displayed by replacing pause enable indication 692 with play enable indication 638. In addition, music application 694 also includes dashboard navigation enable indication 668. While displaying dashboard navigation enable indication 668, device 600A, device 600A detects input 695U on dashboard navigation enable indication 668.

[0254] like Figure 6AC As shown, in response to detecting input 695U, device 600A causes dashboard interface 624 to be displayed. Dashboard interface 624 continues to include calendar widget 682. While calendar widget 682 is displayed, device 600A detects user input 695V on calendar widget 682.

[0255] like Figure 6AD As shown, in response to detecting input 695V, device 600A causes calendar application 696 to be displayed. Calendar application 696 includes events corresponding to the information displayed on calendar widget 682.

[0256] Figure 6AEDisplay screen 600C is shown, which includes one or more features of display screen 600B, but is larger in area / size than display screen 600C. Therefore, due to the larger area / size of 600C, more desktop widgets are displayed on display screen 600C than on display screen 600B.

[0257] In some embodiments, when dashboard interface 624 is displayed on a device having a screen size smaller than display screen 600B, dashboard interface 624 may include fewer widgets than the number of widgets displayed on display screen 600B. In some embodiments, the number of widgets displayed on display screen 600B and / or display screen 600C may be configured by the user.

[0258] In addition, if Figure 6AE As shown, device 600A enables multiple widgets from multiple categories of applications to be displayed. Device 600A enables a communication suggestion widget 642 from a class of communication applications and a calendar widget 682 from a class of calendar applications to be displayed simultaneously. In some embodiments, only a certain number of widgets (e.g., 1 or 2) may be displayed simultaneously on dashboard interface 624.

[0259] FIG. 7A to FIG. 7B 700 is a flow chart illustrating a method for managing applications for different usage scenarios using an electronic device (e.g., 600A) according to some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500) that communicates (e.g., wired connection (e.g., USB) or wireless connection (e.g., Bluetooth, WIFI, etc.)) with a display screen (e.g., 600B). In some embodiments, the display screen is electrically connected to the electronic device (e.g., physically connected to the electronic device, physically becoming part of the electronic device).

[0260] In some embodiments, the display screen (e.g., 600B) is electrically coupled to another electronic device (e.g., 600A) (e.g., a head unit installed in a car, a phone, another type of device, etc.). In some embodiments, the display screen is electrically coupled to another device rather than to the electronic device. In some embodiments, communication includes connecting the electronic device to the other device using a wired or wireless connection of an application that is operably running with the first electronic device (e.g., on the first electronic device, accessed by the first electronic device from a cloud server or some other remote server or storage location). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0261] As described below, method 700 provides an intuitive way to display a map user interface. The method reduces the cognitive burden of viewing the map user interface for the user, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to access the map user interface faster and more efficiently saves power and increases the time between battery charges.

[0262] An electronic device (e.g., 600A) receives input (702) corresponding to a request to display a user interface on a display screen (e.g., 600B) (e.g., in response to the electronic device being connected to the display via a wired or wireless connection, in response to the electronic device and / or the display being turned on).

[0263] In response to receiving an input (e.g., Figure 6B ), the electronic device causes a user interface (e.g., 624, a startup screen) to be displayed on the display screen (704). In some embodiments, the electronic device displays the user interface on the startup screen or as a startup screen (e.g., after the display screen is turned on, after the user interacts with the electronic device or the display screen, or when the electronic device and the display screen establish communication (e.g., via Bluetooth, WIFI, wired connection, etc.), the user interface is on the startup screen or as a startup screen). Based on determining that the electronic device is in the first usage context (e.g., Figure 6B ) (e.g., the state of the electronic device, including the state of an active application (e.g., recency of use) or the state of a sensor of the electronic device (e.g., a GPS sensor)), a user interface that is displayed on a display screen includes (706): a first interface element (706) (e.g., 630), a second interface element (708) (e.g., 636), and a third interface element (710) (e.g., 634, 642, 652, 662, 672, 682, 684). In some embodiments, the determination is performed on the electronic device. In other embodiments, the determination is performed outside the electronic device. In some embodiments, the determination includes the electronic device detecting context parameters (e.g., one or more parameters that define the state of the electronic device, including the state of an active application (e.g., recency of use) or the state of a sensor of the electronic device (e.g., a GPS sensor)), and determining whether one or more of the context parameters satisfy a first usage context or a second usage context. In some embodiments, the electronic device determines whether one or more context parameters satisfy the first usage context or the second usage context by comparing the one or more context parameters with predefined variables that satisfy the first usage context or the second usage context. In some embodiments, the electronic device determines whether one or more context parameters satisfy the first usage context or the second usage context by calculating a confidence score.

[0264] Based on determining that the electronic device is in the first usage context, the first interface element (e.g., 630, one or more desktop widgets (e.g., one or more applications, or one or more components of one or more user interfaces that enable a user to perform one or more functions (or services), a map desktop widget) includes a map (e.g., 630, a representation of a map) selected based on the current location of the electronic device (e.g., the location of the electronic device (e.g., captured by a GPS unit of the electronic device)) (e.g., a real-time mapping service or application) (708). In some embodiments, the first state is a representation of a map with information (such as the location of the first electronic device). In some embodiments, the desktop widget only includes some functions (e.g., user interface functions, user experience functions, and / or operations) of the complete application (e.g., 690). function); in other words, a desktop widget is a lite version of an application. In some embodiments, a desktop widget represents a portion of a graphical interface that a user can interact with to perform one or more functions provided by an application. In some embodiments, an interface element updates a state based on one or more applications that are operably running with the electronic device (e.g., an application on the device, accessed by the device from a cloud server, another type of remote server, a storage location, etc.). In some embodiments, a user selects a portion of an interface element, and in response to selecting the portion of the interface element, the electronic device displays one or more applications corresponding to the state of the interface element on the electronic device. In some embodiments, a map is retrieved from a map application for display. In some embodiments, a map is displayed as part of a map application.

[0265] Based on determining that the electronic device is in the first usage context, the second interface element (e.g., 636) includes a media playback control (e.g., 636, a music application or a video application) (710). In some embodiments, in response to detecting a selection of a representation of a music application, the electronic device causes the music application to be displayed on the display screen (e.g., 694). In some embodiments, in response to detecting a selection of a representation of a media player application, the electronic device causes the media player application to be displayed on the display screen.

[0266] Based on determining that the electronic device is in the first usage context, the third interface element (e.g., 634, 642, 652, 662, 672, 682, 684, a smartly selected widget) includes a first control that, when selected, performs a first function (712) selected based on the first usage context. In some embodiments, the third application is different from a map application (e.g., 690) and a media playback application (e.g., 694) (e.g., a restaurant application when the third interface element is a restaurant application widget). In some embodiments, the third application is the same as a map application or a media playback application (e.g., a map application when the third interface element is an estimated arrival time widget).

[0267] According to determining that the electronic device is in a second usage context different from the first usage context (for example, Fig.6D , Fig. 6F , Figure 6H , Figure 6M , Figure 6S ) (e.g., the state of the device, including the state of active applications (e.g., recency of use) or the state of a sensor of the device (e.g., a GPS sensor)), a user interface that is caused to be displayed on a display screen includes (720): a first interface element (e.g., 630) that includes a map selected based on a current location of the electronic device; a second interface element (e.g., 636) that includes media playback controls; and a third interface element (e.g., 634, 642, 652, 662, 672, 682, 684) that includes a second control without the first control, the second control, when selected, performing a second function selected based on a second usage context (e.g., Fig.6I ).

[0268] Based on determining that the electronic device is in the second usage scenario, the first interface element (e.g., 630, one or more desktop widgets (e.g., one or more applications, or one or more components of one or more user interfaces that enable a user to perform one or more functions (or services))) includes a map (e.g., 690) (e.g., a representation of a map) (722) selected based on the current location of the electronic device (e.g., the location of the electronic device (e.g., captured by a GPS unit of the electronic device)) (e.g., a real-time mapping service or application). In some embodiments, the first state is a representation of a map with information (such as the location of the first electronic device). In some embodiments, the desktop widget only includes some functions of the complete application (e.g., user interface functions, user experience functions, and / or operational functions); in other words, the desktop widget is a lite version of the application. In some embodiments, the desktop widget represents a portion of a graphical interface that a user can interact with to perform one or more functions provided by the application. In some embodiments, the interface element updates a state based on one or more applications that are operably running with the electronic device (e.g., an application on the device, accessed by the device from a cloud server, another type of remote server, a storage location, etc.). In some embodiments, a user selects a portion of an interface element, and in response to selecting the portion of the interface element, the electronic device displays one or more applications (eg, a map widget) corresponding to a state of the interface element on the electronic device.

[0269] Based on determining that the electronic device is in the second usage context, the second interface element (e.g., 636) includes (e.g., name, artist, time (e.g., remaining time, start time, end time, etc.)) media playback controls (e.g., 636, a music application or a video application) (724). In some embodiments, selecting the representation of the music application causes the music application (e.g., 696) to be displayed on the display screen.

[0270] Based on determining that the electronic device is in a second usage context, a third interface element (e.g., 634, 642, 652, 662, 672, 682, 684, a smartly selected widget) includes a second control (e.g., 634, 642, 652, 662, 672, 682, 684) but does not include (e.g., does not display) a first control, which, when selected, performs a second function selected based on the second usage context (726). In some embodiments, the third application is different from a map application and a media playback application (e.g., a restaurant application when the third interface element is a restaurant application widget (e.g., 664)). In some embodiments, the third application is the same as a map application or a media playback application (e.g., a map application when the third interface element is an estimated time of arrival widget). In some embodiments, the interface element is displayed in a fixed position on the display. In some embodiments, one or more user interface elements are displayed as one user interface element (e.g., an estimated ETA widget combined with a predicted destination).

[0271] Displaying a third interface element (e.g., a desktop widget) when the electronic device is in a specific usage context reduces the number of inputs that the user must make when operating the display screen. Reducing the number of inputs used to operate the display screen enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn further reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0272] Automatically displaying and exchanging various interface elements (e.g., desktop widgets) when a set of conditions are met (e.g., the electronic device is in a particular usage context) allows the user to operate the device and display screen under safer conditions when engaging in potentially dangerous activities by reducing the number of inputs required to perform various functions associated with the interface elements. Performing optimized operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0273] Displaying a third interface element (e.g., a desktop widget) based on the electronic device being in a specific usage context provides the user with feedback on the current state of important information relevant to the user. Providing improved feedback on the current state of important information relevant to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0274] In addition, determining the functionality of a third interface element based on the usage context in which the electronic device is in and maintaining the functionality of other interface elements allows the user to quickly identify the changed interface elements, which maintains a relatively consistent display while only changing certain portions of the display to increase the functionality and information provided to the user of the device. Performing optimization operations when a set of conditions have been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0275] According to some embodiments, a third interface element (e.g., an estimated time of arrival widget) includes (e.g., displays) a representation of an estimated time of arrival (e.g., 634). In some embodiments, the estimated time of arrival widget displays information such as an estimated time of arrival to one or more destinations via one or more different routes (e.g., when a car is predicted or expected to travel on the same route to different predicted or predetermined destinations). In some embodiments, the estimated time of arrival widget is controlled by the same application (e.g., a map application) as the first element that includes a map selected based on the current location of the electronic device. In some embodiments, the estimated time of arrival widget is controlled by a different application (e.g., a map application) than the first element that includes a map selected based on the current location of the electronic device. The ability to display an estimated time of arrival based on the electronic device being in a usage context and maintain other interface elements allows a user to quickly identify interface elements that have changed, which maintains a relatively consistent display while providing some portions of the display to be changed in order to increase the functionality and information provided to the user of the device via the widget. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0276] According to some embodiments, the third interface element (e.g., predicted destination) includes a representation of the predicted destination (e.g., 634, 684). In some embodiments, the predicted destination is controlled by the same application (e.g., a map application) as the first element including a map selected based on the current location of the electronic device. In some embodiments, the predicted destination is controlled by a different application (e.g., a predicted destination application) than the first element including a map selected based on the current location of the electronic device. In some embodiments, the predicted destination displays information such as predicted destinations for reaching one or more destinations via one or more different routes (e.g., when it is expected or predicted that a car will travel to different destinations on the same route). In some embodiments, one or more predicted destinations are determined by one or more predetermined destinations set by a user of the electronic device. In some embodiments, one or more predicted destinations are determined based on one or more usage contexts (e.g., the state of the device, including the state of an active application (e.g., recency of use) or the state of a sensor of the device (e.g., a GPS sensor). The function of displaying the predicted destination based on the electronic device being in a usage context and maintaining other interface elements allows the user to quickly identify the changed interface elements, which maintains a relatively consistent display while providing some portions of the display to be changed in order to increase the functionality and information provided to the user of the device via the desktop widget. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0277] According to some embodiments, the first use scenario includes the electronic device being within a predetermined distance of a first location (e.g., a location associated with the electronic device or a user of the electronic device (e.g., a home)), wherein the first function (e.g., 652, 658) includes transmitting a signal to a second electronic device. In some embodiments, the electronic device receives user input corresponding to a request to select a smart-selected widget (e.g., 695B, 695C), and in response to receiving the user input corresponding to the request to select the smart-selected widget, the electronic device transmits a signal to another device that causes an entry point (e.g., a garage door) to a physical structure (e.g., a house) to open or close.

[0278] According to some embodiments, the first usage scenario includes the electronic device moving away from (e.g., moving away from (or, in an alternative, moving toward)) a second location (e.g., a predetermined distance from a predetermined location (e.g., a location associated with the electronic device or a user of the electronic device (e.g., home)), and the third interface element includes a representation (e.g., a visual representation (e.g., words, images (e.g., icons), videos)) of a calendar (e.g., 682, one or more calendars and / or one or more calendar events (e.g., one or more previous, upcoming, ongoing calendar events)). In some embodiments, the electronic device receives user input corresponding to a request to select a smart-selected widget, and in response to receiving user input corresponding to a request to select a smart-selected widget (e.g., 695V), the electronic device displays an application (e.g., a calendar application) associated with a calendar (e.g., meeting, dinner, etc.) application. In some embodiments, the smart-selected widget displays one or more representations of previous, upcoming, or ongoing calendar events. In some embodiments, the widget displays one or more representations of a calendar application (e.g., 696).

[0279] According to some embodiments (e.g., Figures 6N to 6Q ), the first usage scenario includes the electronic device leaving (e.g., moving away) a third position at a predetermined time (e.g., the predetermined time includes a predetermined time range), and the third interface element includes (e.g., a smartly selected desktop widget) a representation (e.g., a visual representation (e.g., words, images (e.g., icons), videos)) of a suggested event (e.g., 662). In some embodiments, the electronic device receives user input corresponding to a request to select a smartly selected desktop widget (e.g., 695H), and in response to receiving the user input corresponding to the request to select the smartly selected desktop widget, the electronic device causes an application (e.g., a calendar application, a restaurant application, an activity-related application (e.g., ordering food, calling a taxi)) associated with the suggested event (e.g., a meeting, dinner, etc.) to open in the application.

[0280] According to some embodiments, the first function corresponds to making a call to a predetermined phone number (e.g., 672). In some embodiments, the predetermined phone number is a suggested (e.g., preferred (most frequent)) contact (e.g., the most frequent contact associated with the electronic device (e.g., set by the user of the electronic device, determined by one or more algorithms to correspond to (e.g., involve) the electronic device, predicted to correspond to the electronic device)), and the suggested contact is a contact associated with the conference event. In some embodiments, the phone number is determined when the electronic device is in a specific context (at a specific time, on a specific date, during specific conditions (e.g., weather conditions)).

[0281] According to some embodiments, when causing a third interface element including a first control to be displayed on the display screen, the electronic device detects a second input (e.g., a tap) corresponding to a selection of the first control (e.g., 695D, 695V) (714). In response to detecting the second input (e.g., a tap) corresponding to the selection of the first control, the electronic device executes a first function, wherein the first function includes causing a first application associated with the first function (e.g., an application including instructions for executing the first function in a set of executable instructions) to be displayed on the display screen (716).

[0282] According to some embodiments, while causing a third interface element including a first control to be displayed on the display screen, the electronic device detects a second input (e.g., a tap) corresponding to a selection of the first control (714). In response to detecting the second input (e.g., a tap) corresponding to a selection of the first control (e.g., 695B, 695C), the electronic device executes the first function without causing a second application associated with the first function (e.g., an application including instructions for executing the first function in a set of executable instructions) to be displayed on the display screen (718).

[0283] Executing a function without causing an application associated with the function to be displayed provides the user with more control over the device by helping the user avoid inadvertently launching an application that performs the function. Providing additional control over the device without cluttering the UI with additional displays of applications enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0284] According to some embodiments, before causing a third interface element including a first control to be displayed on a display screen, the electronic device causes a third interface element including a third control (e.g., a previously displayed desktop widget) to be displayed on the display screen. When causing the third interface element including the first control to be displayed on the display screen, the electronic device receives a third input on the third interface element (e.g., 695G-I, swipe). In response to receiving the third input on the third interface element, the electronic device causes the third interface element including the third control to be displayed on the display screen. In some embodiments, the intelligently selected desktop widget was not previously displayed. In some embodiments, displaying the desktop widget replaces the display of one or more other desktop widgets. In some embodiments, the desktop widget is displayed in a turntable or a slider. In some embodiments, the first input, the second input, and the third input on the intelligently selected desktop widget are different types of inputs.

[0285] Allowing the user to provide input to display a previously displayed smart-selected widget provides the user with more control over the device by helping the user avoid inadvertently losing the functionality of the previously displayed widget when displaying a new widget. In addition, providing the option to display a previous widget provides additional functionality without cluttering the UI with additional widgets being displayed, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0286] According to some embodiments, when causing a third interface element including a first control to be displayed on a display screen, the first control, when selected, performs a first function selected based on a first usage context, the electronic device causes a fourth interface element including a fourth control to be displayed on the display screen, the fourth control, when selected, performing a fourth function selected based on a third usage context (e.g., a state of the electronic device, including a state of an active application (e.g., recency of use) or a state of a sensor of the electronic device (e.g., a GPS sensor)). In some embodiments, the first usage context and the third usage context are the same. In some embodiments, the first usage context and the third usage context are different. In some of these embodiments, the first function of the third interface element and the fourth function of the fourth interface element change independently of each other at different times. The first function (e.g., a function of a map application (e.g., navigating to a destination)) is included in a first category of applications (e.g., a map application) (e.g., an application in the category of applications has a function that is a part of an instruction set for applications in the category of applications). The fourth function (e.g., a function of a communication application (e.g., sending an instant message to a contact)) is included in a second category of applications (e.g., a map application) (e.g., an application in the category of applications has a function that is a part of an instruction set for applications in the category of applications). The first category of applications is different from the second category of applications. In some embodiments, one or more smart-selected widgets can be displayed in different ways (e.g., one or more smart-selected widgets are displayed in a carousel and another one or more smart-selected widgets are displayed as sliders). In some embodiments, the number of selected widgets displayed depends on the size (or dimension) of the display, where more selected widgets are displayed when the size of the display is larger. In some embodiments, the functionality of one or more smart-selected widgets is based on different usage scenarios and / or performs different functions (e.g., Figure 6AE ).

[0287] According to some embodiments, the first function is included in a second application (e.g., 672) in a third category of applications (e.g., a portion is included in an instruction set for the application). The user interface also includes a shortcut enable representation (e.g., 612B) at a shortcut location (e.g., a fixed location on a display screen) corresponding to an application (e.g., a communication application) in the third category (e.g., a communication application) (e.g., the shortcut location is displayed on a second portion of the display screen that is different from the first portion, where the first portion includes a third interface element) (e.g., an enable representation of the application is displayed on the display screen when selected), the shortcut enable representation representing a third application (e.g., a phone application) in the third category of applications, and the second application is different from the third application.

[0288] According to some embodiments, the user interface is a first user interface, and causing the user interface (e.g., a startup screen) to be displayed on the display screen further includes: based on determining that the first user interface (e.g., a dashboard user interface (e.g., 624) (e.g., a user interface including a first element, a second element, and a third element)) is currently displayed on the display screen: causing a navigation enable representation (e.g., 626, 668) including a first representation (e.g., 626) (e.g., an image, video, symbol representing the first user interface) to be displayed on the display screen (e.g., an enable representation for navigating to a second user interface (e.g., an icon grid user interface)), wherein the navigation enable representation includes a fifth control that, when selected, performs a fifth function, the fifth function including causing a second user interface different from the first representation to be displayed on the display screen (e.g., navigating to an icon grid user interface (e.g., a user interface for navigating to multiple icons of multiple applications)). According to some embodiments, the user interface is a first user interface, and causing the user interface (e.g., a startup screen) to be displayed on the display screen further includes: based on determining that the first user interface (e.g., a dashboard user interface (e.g., 624) (e.g., a user interface including a first element, a second element, and a third element)) is not currently displayed on the display screen (e.g., a user interface of an application, an icon grid user interface (e.g., a user interface of multiple icons for navigating to multiple applications is displayed on the display screen): causing a navigation enable representation to be displayed on the display screen, the navigation enable representation including a second representation (e.g., 668) that is different from the first representation (e.g., an image, video, symbol representing the second user interface), wherein the navigation enable representation includes a sixth control that performs a sixth function when selected, the sixth function including causing the display screen to display a sixth function. A first user interface is displayed on the screen (e.g., navigating to a dashboard user interface (e.g., 624) (e.g., a user interface including a first element, a second element, and a third element)). Updating the visual features of the navigation (based on whether a particular user interface is displayed) to reflect the change in functionality and changing the functionality of the navigation affordance provides the user with more control over the device by helping the user avoid unintentionally performing operations while allowing the user to identify locations to which the user can quickly navigate using the navigation affordance. In addition, updating the visual features of the navigation to detect the change in functionality and changing the functionality of the navigation affordance makes the user device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0289] Note that the above description is relative to method 700 (eg, FIG. 7A to FIG. 7B) The details of the process described in the method 900 and 1000 are also applicable in a similar manner to the methods described below. For example, methods 900 and 1000 optionally include one or more of the features of the various methods described above with reference to method 700. For example, method 700 may include one or more techniques in methods 900 and 1000 to provide an interface when connected to a second device. For the sake of brevity, these details are not repeated below.

[0290] FIG. 8A to FIG. 8T An exemplary user interface and its transition for managing the connection between display screen 800B and computing devices 800A, 800C, 800D are shown. In some embodiments, each of devices 800A, 800B, 800C, and 800D includes device 100, 300, or 500 ( Figure 1A to Figure 1B , Figure 3 and FIG. 5A to FIG. 5B ) some or all of the features of ). The user interfaces in these figures are used to illustrate the processes and techniques described below, including FIG. 9A to FIG. 9B and Fig.10 The processes and techniques described.

[0291] In some embodiments, each of electronic devices 800A, 800C, and 800D is a mobile phone connected to display screen 800B or an external electronic device having display screen 800B by wire (e.g., USB, Lightning) or wirelessly (e.g., Bluetooth, WiFi). In some embodiments, display screen 800B (e.g., a device having one or more features of display screen 600B) is disposed on or in the dashboard of a car. In some embodiments, according to various embodiments discussed herein, a mobile phone (e.g., device 800A, 800D) sends a command signal to generate a user interface at display screen 800B. In addition, a user interaction detected at display screen 800B is sent to a mobile phone (e.g., device 800A). In some embodiments, the user interface 802B described herein is provided at the display screen of the electronic device (e.g., device 800A, 800D) itself.

[0292] Although devices 800A, 800C, and 800D are potentially capable of receiving and transmitting media and connected to display screen 800B, devices 800A and 800D will be described below as receiving devices. The receiving device communicates directly with display screen 800B and device 800C. Device 800C will be described as a sending device. In the following examples, the sending device communicates directly with the receiving device, but not with display screen 800B.

[0293] FIG. 8A to FIG. 8TA technique is described that allows a user of a sending device to transfer media to an accessory (e.g., display screen 800B) via an indirect wireless connection. The technique uses a receiving device as a hub between the sending device and the accessory; that is, the receiving device establishes a secure connection with the sending device and the accessory. In addition, the technique may obscure the indirect connection between the sending device and the accessory to the user of the sending device. For example, the receiving device provides identification information to the sending device that is typically associated with display screen 800B. Thus, to the user of the sending device, it may appear to be directly connected to display screen 800B when the connection is actually an indirect connection relayed through the receiving device. Details of the technique are described below.

[0294] like Fig. 8A As shown, device 800C displays a user interface 802C for controlling the output of media (including transmitting the media to one or more accessory devices). When device 800C cannot identify any available accessory devices, user interface 802C indicates that device 800C is configured to play back media (e.g., directly play back media using one or more speakers of device 800C). Here, user interface 802C indicates that device 800C is configured to play back media by including an affordance 806A, a device identifier 808A ("phone" is the device itself), and a connection indicator 810A.

[0295] like Figure 8B As shown, device 800A establishes connection 870A with display screen 800B, so that display screen 800B displays user interface 802B (e.g., dashboard interface 624). In some embodiments, connection 870A is a secure connection (e.g., Bluetooth), which indicates that device 800A and display screen 800B establish connection 870A by following a security protocol. In some embodiments, by establishing connection 870A, display screen 800B includes an indication that device 800A is a trusted device. In some embodiments, forming a connection with display screen 800B allows the connected device to transmit data to display screen 800B, even if the data is malicious. Therefore, in some embodiments, when display screen 800B allows one or more unknown devices to establish a connection similar to connection 870A, the display screen is vulnerable. In some embodiments, when device 800A is a trusted device, display screen 800B may allow device 800A to have administrative control over display screen 800B (e.g., a higher level of control than other devices with control).

[0296] In some embodiments, when device 800A is connected to display screen 800B, device 800A provides or broadcasts information to device 800C. The information broadcast by device 800A includes information having an identifier corresponding to the identity of display screen 800B. In some embodiments, device 800A determines the identifier by using the identity of display screen 800B. In some of these embodiments, if the identity of display screen 800B is "Steve's car", the identifier broadcast to device 800C includes "Steve's car". In some embodiments, device 800A determines the identifier by deriving the identifier from the identity of display screen 800B. In some of these embodiments, the identifier broadcast to device 800C includes "Steve's car car player".

[0297] In some embodiments, device 800A provides information in a format that conforms to a wireless communication protocol or standard (e.g., Bluetooth) for identifying nearby devices that can be used to receive content. In some embodiments, the communication protocol identifies nearby devices that can be used to receive specific types of content such as audio and video.

[0298] like Figure 8C As shown, based on determining that a wireless connection is available with a device broadcasting an identifier "Steve's Car Player", device 800C displays affordance 806B having identifier 808B that matches the identifier broadcast by device 800C. Here, device 800A broadcasts an identifier including "Steve's Car Player". Upon receiving the identifier, device 800C determines that a wireless connection is available with a device that may appear to be display screen 800B.

[0299] like Fig.8D As shown, when displaying affordance 806B, device 800C detects input 895A corresponding to the selection of affordance 806B with identifier 808B. It is noteworthy that displaying identifier 808B may indicate to the user that device 800C will be connected to display screen 800B. Therefore, some users may not know that selecting affordance 806B will cause device 800C to be connected to 800A. In some embodiments, not showing the identifier associated with device 800C reduces the risk of confusion (e.g., when the user's intention is to connect to display screen 800B in order to play media). In some embodiments, indirectly connecting device 800C to display screen 800B via device 800A can improve security and require less time and effort than requiring a direct connection between device 800C and display screen 800B.

[0300] like Fig. 8EAs shown, in response to detecting input 895A, device 800C establishes connection 870B with 800A and displays indication 810B. Indication 810B shows the user that device 800C is configured to transmit media to an external device that the user can perceive as display screen 800B. It is worth noting that device 800C establishes connection 870B with 800A, rather than establishing a direct connection with display screen 800B.

[0301] In some embodiments, in response to detecting input 895A, device 800C sends a request to connect to device 800A. Subsequently, device 800A receives a request to connect device 800C to display screen 800B (e.g., indirectly via device 800A). In response to receiving the request to connect device 800C to display screen 800B, Fig. 8E As shown, device 800A causes confirmation screen 812 to be displayed on display screen 800B.

[0302] In some embodiments, although device 800C is connected to 800A, confirmation must be given by a user associated with display screen 800B or device 800A in order to allow 800C media to be played via display screen 800B. Fig. 8E As further shown in FIG. 8 , confirmation screen 812 includes a rejection indication 814 and an approval indication 816. Fig. 8E As shown, device 800C displays a confirmation screen 820 including a deny enable indication 822 and an allow enable indication 824.

[0303] While confirmation screen 812 and / or confirmation screen 820 is displayed, device 800A detects input 895B on allow affordance 816 or input 895C on allow affordance 824. Fig. 8E As shown, after device 800A detects input 895B or input 895C, device 800C transmits media to device 800A via display screen 800B for playback. Subsequently, device 800A receives the media and transmits the media to display screen 800B for playback.

[0304] like Fig.8F As shown, when transmitting the media for playback to display screen 800B, device 800A causes display screen 800B to display media application 826. Media application 826 plays the media transmitted by device 800C to 800A.

[0305] like Fig.8FAs shown, device 800C is connected to device 800A, and device 800A is connected to display screen 800B. Here, device 800A acts as a hub device that receives media from 800C and transmits the media to display screen 800B. Therefore, device 800C is indirectly connected to display screen 800B via device 800A. However, it is worth noting that the user of device 800C may not know that device 800C is transmitting media to device 800A. The user of device 800C may only know that indication 810B indicates to the user that device 800C is connected to display screen 800B and that media is being played by display screen 800B via media application 826.

[0306] like Fig.8F As shown, media application 826 includes volume control 828 at a first volume level (first position). Here, display screen 800B plays back media from device 800C. Similarly, device 800C displays audio control 830 at a first volume level (first position). While audio control 830 is displayed, device 800C detects input 895D that changes the volume level from the first volume level to a second volume level.

[0307] like Figure 8G As shown, in response to detecting input 895D, device 800C displays audio control 830 at a higher volume level. Subsequently, device 800A receives an instruction from 800C to increase the volume on display screen 800B and causes display screen 800B to display volume control 828 at a higher volume level.

[0308] Additionally, the user may decide to turn off the sending device, such as device 800C, while the media is being transmitted to display screen 800B for playback. FIG. 8G to FIG. 8I Go to Figure 8G , while transferring media to display screen 800B for playback, device 800A causes display screen 800B to display information affordance 832. Information affordance 832 identifies device 800C as currently transferring media to display screen 800B. Information affordance 832 is also included in media application 826.

[0309] While displaying information enable indication 832, device 800A detects input 895E on information enable indication 832. Fig.8I As shown, in response to detecting input 895E, device 800A causes display screen 800B to display close interface 834. Close interface 834 includes close enable indication 836 and cancel enable indication 838. Close enable indication 836 indicates device 800C as a device that will disconnect if the enable indication is selected. When displaying close enable indication 836, device 800A receives input 895F corresponding to the selection of close enable indication 836.

[0310] like Fig.8I As shown, in response to receiving input 895F, device 800A stops transmitting media for playback to display screen 800B. When devices 800A and 800C are no longer connected, the user of device 800C may interpret the loss of connection 870B as a loss of connection between display screen 800B and device 800C. This is at least because, as described above, the user may have no indication that device 800C is connected to device 800A.

[0311] In addition, in response to receiving input 895F, device 800A causes display screen 800B to indicate that no media is being played back ("Not Playing") in media application 826. In addition, device 800A causes opening interface 834 and / or closing enable indication 836 to cease being displayed on display screen 800B.

[0312] Additionally, because devices 800A and 800C are no longer connected via connection 870B, device 800C updates affordance 806a to indicate that device 800C is configured to directly play back media. Device 800C also stops displaying affordance 810B. However, although device 800C stops displaying affordance 806B, device 800C continues to display affordance 806B and identifier 808B. Figure 8S , disconnecting device 800C does not disconnect device 800A from display screen 800B. Since device 800A maintains its connection to display screen 800B, device 800A continues to broadcast the identifier "Steve's Car Player".

[0313] like Figure 8J As shown, device 800A is no longer connected to display screen 800B, which is achieved by Figure 8J 870A not shown in the figure can be clearly seen. In response to not being connected to the display, such as Figure 8K As shown, device 800A stops broadcasting the identifier "Steve's Car Player".

[0314] In some embodiments, when device 800A is no longer connected to display screen 800B, device 800A removes the availability of information indicating that device 800A can be used to retransmit content from the remote device to display screen 800B. In some embodiments, removing the availability of information indicating that device 800A can be used to retransmit content from the remote device to display screen 800B also includes stopping providing information to device 800C.

[0315] Then, if Figure 8KAs shown, device 800C stops displaying affordance 806B with identifier 808B based on determining that connection 870B is unavailable. In some embodiments, when another connection with display screen 800B is available, device 800C continues to display affordance 806B with identifier 808B. Figure 8K No connection is available, so device 800C stops displaying the enable indication 806B with identifier 808B.

[0316] like Figure 8L As shown, device 800D is connected to display screen 800B via connection 870C. Device 800D is different from device 800A. In some embodiments, device 800D is connected to display screen 800B, which is different from the above description with respect to Figure 8C The techniques discussed are consistent.

[0317] In some embodiments, device 800C receives a second request to display available wireless media receiver devices. And, in response to receiving the second request, device 800C displays user interface 802C, as described above with respect to Fig. 8A discussed.

[0318] like Figure 8M As shown, based on determining that connection 870C exists between device 800D and display screen 800B, device 800C displays enable indication 806C. Enable indication 806C includes identifier 808C. Identifier 808C is the same as identifier 808B. Here, device 800D obtains or recognizes the identifier of display screen 800B that is the same as the above-mentioned device 800B. Therefore, multiple receiving devices (for example, 800A and 800D) generate the same identifier. The user of the sending device may not be able to distinguish between different receiving devices. It is worth noting that the user can only consider that device 800C can be connected to display screen 800B. As shown in FIG. Figure 8N As shown, when the enable indication 806C is displayed, the device 800C detects input 895Z on the enable indication 806C.

[0319] like Figure 8O to Figure 8P As shown, in response to detecting input 895Z, devices 800C and 800D establish connection 870C. Device 800D detects input 895G on the corresponding enable representation 842, and devices 800B, 800C, and 800D receive and / or transmit media and update user interfaces 802B, 802C, and 802D, which is consistent with FIG. 8B to FIG. 8F The discussion is consistent.

[0320] In addition, if Figure 8PAs shown, device 800D and display screen 800B are connected via connection 870C, and devices 800C and 800D are connected via connection 870D. Device 800D also displays user interface 802C. User interface 802C includes an indication 810C that indicates that device 800C is configured to transmit media via display screen 800B.

[0321] Additionally, device 800D causes media application 826 to be displayed on display screen 800B. While causing media application 826 to be displayed on display screen 800B, device 800D detects input 895H on user interface 802C.

[0322] like Figure 8Q As shown, in response to detecting input 895H, device 800D causes icon interface 850A including a first group of icons (e.g., phone map, music, etc.) to be displayed on display screen 800B. While causing icon interface 850A including a first group of icons to be displayed, device 800D detects input 895I on icon interface 850A.

[0323] like Figure 8R As shown, in response to detecting input 895I, device 800D causes icon interface 850B including a second group of icons (e.g., phone map, music) to be displayed on display screen 800B. The second group of icons includes settings icon 852. At 8R, device 800D detects input 895J on icon interface 850A.

[0324] like Figure 8S As shown, in response to detecting input 895J on setup icon 852, device 800D causes setup user interface 854 to be displayed on display screen 800B. Setup user interface 854 includes existing connection enable indication 856. Existing connection enable indication 856 includes identifier 858 ("RICH's phone") identifying device 800C as a connected device. While displaying existing connection enable indication 856 including identifier 858, device 800D detects input 895K.

[0325] like Figure 8T As shown, in response to detecting input 895K, device 800D causes display of disconnect enable indication 860 and cancel enable indication 862. While disconnect enable indication 860 is displayed, device 800D detects input 895L on disconnect enable indication 895L.

[0326] FIG. 9A to FIG. 9B900 is a flow chart illustrating a method for coordinating access to media using an electronic device according to some embodiments. Method 900 is performed at a first electronic device (e.g., 100, 300, 500) (e.g., a digital media player, a digital media playback coordination device (e.g., a phone configured to coordinate media playback)) having one or more antennas (e.g., one or more WIFI antennas, Bluetooth antennas). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0327] As described below, method 900 provides an intuitive way to coordinate access to media. The method reduces the cognitive burden on users when accessing media, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to access media faster and more efficiently saves power and increases the time between battery charges.

[0328] When a first electronic device (e.g., device 800A or device 800D) is connected (e.g., 870a) (e.g., via one or more antennas (e.g., wirelessly connected via a wireless communication protocol (e.g., Bluetooth))) to an accessory (e.g., display 800B) (e.g., an electronic device (e.g., a device including a second display device (e.g., a head unit installed in a car)) that includes one or more output devices (e.g., display, speaker), the first electronic device transmits information (e.g., FIG. 8B to FIG. 8C , Figures 8K to 8L )(e.g., data (e.g., including an identifier)) provides (e.g., FIG. 8B to FIG. 8C , Figures 8K to 8L ) to a second electronic device (e.g., 800C) (e.g., a digital media player, a digital media playback coordination device (e.g., a phone configured to coordinate media playback)), the information indicating that the first electronic device can be used to retransmit content (e.g., media) from the second electronic device to the attachment information (e.g., FIG. 8B to FIG. 8C , Figures 8K to 8L )(902). In some embodiments, the first electronic device connects (e.g., 870a) to an accessory by receiving input (e.g., turning on the electronic device, bringing the electronic device within connection range of a compatible accessory, selecting the accessory from a list of devices available for connection) via an input device (e.g., an antenna, a power circuit (e.g., a power button or switch), a proximity sensor), the input corresponding to a request to establish a connection with an accessory (e.g., a second electronic device (e.g., a device including a display device (e.g., a head unit installed in an automobile)). In some embodiments, in response to receiving the input (e.g., 950a), the device establishes a connection with the accessory via the antenna.

[0329] According to some embodiments, prior to transmitting media to the accessory for presentation via one or more output devices of the accessory (904): the first electronic device receives a request from the second electronic device to connect to the accessory as a receiving source (e.g., via input 950A, FIG. 8D to FIG. 8E )(906). In response to receiving a request to connect to an accessory as a receiving source, the first electronic device causes a user interface to be displayed on at least one of the one or more output devices of the accessory, the user interface including a confirmation screen (e.g., confirmation screen 812, 820) to allow (e.g., enable indication 816, 824) or deny (enable indication 814, 822) connection with the accessory as a receiving source (908). In some embodiments, the confirmation screen (e.g., 812) is displayed on the first electronic device simultaneously with or in lieu of displaying the confirmation screen on the display screen of the accessory. Displaying the confirmation screen in response to receiving a request to connect to the accessory helps the user of the accessory control which devices can transfer information to the accessory for playback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0330] In providing (eg, broadcasting) the information to a second electronic device (eg, Fig.8D , Fig. 8E), the first electronic device receives media (e.g., 804) (e.g., audio media (e.g., music), visual media (e.g., video)) from the second electronic device via one or more antennas (910). In some embodiments, based on determining that the first electronic device identifier broadcast criteria are met, the first electronic device provides information to the second electronic device. In some embodiments, the first electronic device identifier broadcast criteria include criteria that are met when the accessory that meets the first type of accessory (e.g., the accessory is an accessory that is compatible with the media processing standard). In some embodiments, based on determining that the first electronic device identifier broadcast criteria are met, the first electronic device broadcasts, via an antenna and using a first electronic device identifier (e.g., an identifier selected based on the accessory and / or a state of being connected to the accessory), that the electronic device is available for receiving wireless media (e.g., receiving wireless media from a second electronic device that is different from the accessory). In some embodiments, the electronic device includes a device identifier (e.g., a default device identifier; an identifier for identifying the electronic device when the electronic device is not connected to the accessory), and the first electronic device identifier is different from the device identifier. In some embodiments, before broadcasting, via an antenna and using the first electronic device identifier, that the electronic device is available for receiving wireless media, the electronic device broadcasts, via an antenna and using a second electronic device identifier that is different from the first electronic device identifier, that the electronic device is available for receiving wireless media. In some embodiments, before broadcasting, via an antenna and using the first electronic device identifier, that the electronic device is available for receiving wireless media, the electronic device does not broadcast, via an antenna and using the first electronic device identifier, that the electronic device is available for receiving wireless media.

[0331] The first electronic device transmits the media to the accessory for presentation via one or more output devices of the accessory (e.g., Fig.8F )(912).

[0332] After transmitting the media to the accessory for presentation via one or more output devices, the first electronic device detects that the first electronic device is no longer connected to the accessory (e.g., FIG. 8I to FIG. 8F )(914).

[0333] In response to detecting that the first electronic device is no longer connected to the accessory, the first electronic device removes the availability of information indicating that the first electronic device is available to retransmit content from the remote device to the accessory (e.g., FIG. 8I to FIG. 8F)(918). In some embodiments, based on determining that the first electronic device identifier broadcast criteria are not met, the first electronic device detects that the first electronic device is no longer connected to the accessory (and / or does not provide information to the electronic device). Therefore, in some embodiments, the first electronic device abandons broadcasting via the antenna and using the first electronic device identifier that the electronic device is available for receiving wireless media. In some embodiments, abandoning broadcasting via the antenna and using the first electronic device identifier that the electronic device is available for receiving wireless media includes the first electronic device broadcasting via the antenna and using a second electronic device identifier that is different from the first electronic device identifier that the electronic device is available for receiving wireless media. In some embodiments, abandoning broadcasting via the antenna and using the first electronic device identifier that the electronic device is available for receiving wireless media includes abandoning broadcasting (e.g., completely) that the electronic device is available for receiving wireless media. Controlling the availability of information indicating that the first electronic device is available for transmission based on whether the device is connected to an accessory allows the second electronic device (and the user of the electronic device) to quickly identify whether there is a connection available for the second electronic device to connect to the accessory via the first electronic device. Performing optimization operations when a set of conditions have been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0334] According to some embodiments, removing the availability of information indicating that the first electronic device is available to retransmit content from the remote device to the accessory also includes the first electronic device ceasing to provide (e.g., broadcast) the information to the second electronic device (e.g., FIG. 8I to FIG. 8F )(920).

[0335] According to some embodiments, information indicating to the second electronic device that the first electronic device can be used to retransmit content from the second electronic device to the accessory includes information identifying the first electronic device by an identifier corresponding to the accessory (e.g., as a car source (e.g., identifying that the device is connected to play audio, send and receive information, control applications such as maps)). In some embodiments, the identifier corresponding to the accessory is an identifier of the accessory (e.g., "Car Model" when the accessory is a "Car Model") or an identifier derived from the identifier of the accessory (e.g., "Car Model Stereo" when the accessory is a "Car Model"). Updating the information to reflect the information identifying the first electronic device by an identifier corresponding to the accessory (e.g., car) rather than the first electronic device (e.g., phone) provides the user with visual feedback indicating that the media transmitted to the accessory will be output by the accessory. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0336] According to some embodiments, information is provided to a second electronic device in a format that complies with a communication protocol (e.g., a wireless streaming protocol) to identify a nearby device (e.g., a wireless device) that can be used to receive content (e.g., media (e.g., audio, video)) of a predetermined content type (e.g., an audio / video file). Figure 8B ).

[0337] According to some embodiments, the media includes audio, and the one or more output devices of the accessory include speakers. In some embodiments, the one or more output devices are wired to the accessory. In some embodiments, the one or more output devices are wirelessly connected to the accessory.

[0338] Prior to detecting that the first electronic device is no longer connected to the accessory: while transmitting media to the accessory for presentation via one or more output devices of the accessory, the first electronic device causes display on at least one of the one or more output devices a user interface (e.g., 826) of an application corresponding to playback of the media (e.g., a media application corresponding to the playback media application), wherein the user interface includes an affordance (e.g., 832) (e.g., turning off the affordance (e.g., turning off the affordance includes identification information of the second electronic device)) (e.g., Figures 8G to 8HIn some embodiments, the user interface is displayed on the first electronic device concurrently with or in lieu of displaying the user interface on the display screen of the accessory. In response to receiving user input corresponding to selection of the affordance (e.g., 895E), the first electronic device stops transmitting media to the accessory for presentation via one or more output devices of the accessory (e.g., Figures 8G to 8H In some embodiments, stopping the transmission of media to the accessory for presentation via one or more output devices of the accessory disconnects the first electronic device from the second electronic device (e.g., Figures 8G to 8H In some embodiments, stopping transmitting media to the accessory for presentation via one or more output devices of the accessory does not disconnect the first electronic device from the second electronic device. In some of these embodiments, the first electronic device is able to retransmit media of a different type than the media it previously transmitted to the accessory. In some embodiments, the affordance is displayed outside of an application corresponding to playback of the media (e.g., in a settings application) (e.g., Figures 8G to 8H ).

[0339] Note that the process described above with respect to method 900 (eg, FIG. 9A to FIG. 9B ) may also be applied in a similar manner to the methods described below / above. For example, methods 700 and 1000 optionally include one or more features of the various methods described above with reference to method 900. For example, method 900 may be combined with methods 700 and 1000 to operate a display screen and multiple devices.

[0340] Fig.10 1 is a flow chart illustrating a method for coordinating access to media using an electronic device according to some embodiments. Method 1000 is performed at a first electronic device (e.g., 100, 300, 500) (e.g., a media storage device, a media sending device (e.g., a phone storing digital media)) having a display device and one or more input devices (e.g., a WIFI antenna, a Bluetooth antenna, etc.). Some operations in method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0341] As described below, method 1000 provides an intuitive way to coordinate access to media. The method reduces the cognitive burden on users when accessing media, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to access media faster and more efficiently saves power and increases the time between battery charges.

[0342] The first electronic device (e.g., 800C) receives, via one or more input devices, a display indicating an available wireless media receiver device (e.g., a digital media player, a digital media playback coordination device (e.g., Fig. 8A ) (eg, a phone configured to coordinate media playback)) request (1002).

[0343] In response to receiving the request, the first electronic device displays, via the display device, a user interface (e.g., 802C) for selecting a wireless media receiver for media (e.g., digital audio and / or video) from the first electronic device, including (1004): based on determining that a wireless connection is available with an accessory (e.g., display screen 800b) for receiving media via a wireless connection (e.g., an electronic device (e.g., a device including a second display device (e.g., a head unit installed in a car))), displaying an enabling representation (e.g., 806A, 806B, 806C) for selecting an accessory to receive wireless media, wherein the user interface for selecting the accessory to receive the media is displayed. establishing a connection (e.g., 870b, 870d) (1006) between a first electronic device and a second electronic device (e.g., 800A, 800D) connected to an accessory (e.g., a digital media player, a digital media playback coordination device (e.g., a phone configured to coordinate media playback)); and based on determining that a wireless connection with the accessory for receiving media via the wireless connection is unavailable, abandoning displaying an enablement representation for selecting an accessory to receive wireless media, wherein when no device (e.g., no digital media player or digital media playback coordination device) is connected (e.g., wirelessly connected) to the accessory (e.g., Figure 8K ), a connection to an accessory for receiving media via a wireless connection is unavailable (1014).

[0344] Based on determining that a wireless connection to the accessory is available for receiving media to quickly identify whether a connection is available to connect to the accessory, selecting to display an enable representation for selecting the accessory to receive wireless media. Performing optimization operations when a set of conditions have been met without further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0345] In accordance with some embodiments, an affordance for selecting an accessory to receive wireless media includes information (e.g., 808B) (e.g., a name) that identifies a second electronic device by an identifier (e.g., 808B) corresponding to the accessory (e.g., as a car source (e.g., identifying that the device is connected to play audio, send and receive information, control an application such as a map)) or an identifier derived from an identifier of the accessory (e.g., "Car Model Stereo" when the accessory is a "Car Model"). In some embodiments, the identifier corresponding to the accessory is an identifier of the accessory (e.g., "Car Model" when the accessory is a "Car Model"). Updating the information to reflect the information identifying the first electronic device by an identifier corresponding to the accessory (e.g., car) rather than the first electronic device (e.g., phone) provides the user with visual feedback indicating that media transmitted to the accessory will be output by the accessory. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0346] According to some embodiments, the request to display available media devices is a first request. The first electronic device receives a request to display available wireless media receiver devices (e.g., at a later time) (e.g., a digital media player, a digital media playback coordination device (e.g., a phone configured to coordinate media playback)) via one or more input devices (e.g., Figure 8K). In response to receiving the second request, the first electronic device displays, via the display device, a user interface (e.g., 802c) for selecting a wireless media receiver for media (e.g., digital audio and / or video) from the first electronic device, including: based on determining that a second wireless connection (e.g., 870B, 870D) with an accessory for receiving media via a wireless connection (e.g., a second electronic device (e.g., a device including a second display device (e.g., a head unit installed in a car)) is available, displaying an enable representation (e.g., 806B, 806C) for selecting an accessory to receive wireless media, wherein the enable representation for selecting an accessory to receive wireless media is displayed between the first electronic device and a third electronic device (e.g., a device connected to the accessory) For example, establishing a connection between an accessory (e.g., a digital media player, a digital media playback coordination device (e.g., a phone configured to coordinate media playback); an electronic device different from a second electronic device) and wherein an affordance for selecting an accessory to receive wireless media includes information (e.g., a name) identifying the second electronic device via an identifier corresponding to the accessory (e.g., 808B, 808C); abandoning displaying an affordance for selecting an accessory to receive wireless media based on determining that a wireless connection with the accessory for receiving media via the wireless connection is unavailable, wherein when no device (e.g., no digital media player or digital media playback coordination device) is connected (e.g., wirelessly connected) to the accessory (e.g., Figure 8K , relative to device 800A), a connection to the accessory for receiving media via a wireless connection is unavailable. In some embodiments, other devices connected to the accessory obtain the same name as a second electronic device connected to the same accessory. In some embodiments, the first electronic device displays multiple identical identification information (e.g., "Car" for the second electronic device and "Car" for the third electronic device) (806A, 806B).

[0347] Updating the information to reflect information identifying the accessory (e.g., the car) rather than the first electronic device (e.g., the phone) to the two or more devices provides visual feedback to the user indicating that media transferred to the accessory will be output by the accessory. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0348] According to some embodiments, while displaying an affordance for selecting an accessory to receive wireless media, the first electronic device receives user input corresponding to a selection of the affordance for selecting an accessory to receive wireless media (e.g., 895A) (1008). In response to receiving the user input corresponding to the selection of the affordance for selecting an accessory to receive wireless media: the first electronic device connects to the second electronic device (e.g., 870b, Fig. 8E )(1010). When connected to the second electronic device, the first electronic device displays an indication that the first electronic device is connected to the accessory (e.g., 810B, 810C) (1014). Selecting to display an enable indication (which is already connected to the second electronic device when user input corresponding to selection of the enable indication is received) in a certain state (e.g., connected) when connected to the second electronic device provides the user with an indication of whether the electronic device is connected to the accessory after providing the input. Performing optimization operations when a set of conditions have been met and no further user input is required enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0349] According to some embodiments, upon connecting to a second electronic device, the first electronic device transmits media (e.g., 804) to the second electronic device for presentation via one or more output devices of the accessory (e.g., 8F). While transmitting the media to the second electronic device for presentation via one or more output devices of the accessory, the first electronic device displays an indication (e.g., 804) of the media transmitted to the second electronic device for presentation via one or more output devices of the accessory.

[0350] According to some embodiments, while transmitting media to a second electronic device for presentation via one or more output devices of an accessory, the first electronic device receives a request to stop transmitting the media (e.g., FIG. 8H to FIG. 8I ). In response to receiving the request to stop media transmission, the first electronic device stops transmitting media to the second electronic device connected to the accessory. In some embodiments, the first electronic device continues to be connected to the second electronic device. In some embodiments, the first electronic device does not continue to be connected to the second electronic device.

[0351] Note that the above reference method 1000 (e.g., Fig.10) also apply in a similar manner to the methods described below / above. For example, methods 700 and 900 optionally include one or more features of the various methods described above with reference to method 1000. For example, method 1000 can be combined with methods 700 and 900 to operate a display screen and multiple devices. For the sake of brevity, these details are not repeated below.

[0352] 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. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

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

[0354] As described above, one aspect of the technology of the present invention is to collect and use data from various sources to improve the delivery of applications based on personalized scenarios. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.

[0355] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to deliver target application functions that users are more interested in through desktop applets. Therefore, the use of such personal information data enables users to control the delivery of target application functions through desktop applets within certain usage scenarios. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0356] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0357] Regardless of the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to the delivery of application functionality based on certain scenarios, the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" at any time during or after registration for a service to participate in the collection of personal information data. As another example, a user may choose not to provide personal information, such as the state of their device and / or personal information, such as their current location. As another example, a user may choose to limit the length of time to maintain the state of their device and / or personal information (such as their current location), or completely prohibit the development of a baseline emotional condition. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then reminded again just before the personal information data is accessed by the application.

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

[0359] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may also be implemented without access to such personal information data. That is, the various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, application functionality may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum of personal information (such as content requested by a device associated with the user, other non-personal information available to an application functionality delivery service, or publicly available information).

Claims

1. A method comprising: At a first electronic device having a display device and one or more input devices: receiving, via the one or more input devices, a request to display available wireless media receiver devices; as well as In response to receiving the request, displaying, via the display device, a user interface for selecting a wireless media receiver for media from the first electronic device, comprising: Based on determining that a wireless connection with an accessory for receiving media via a wireless connection is available, displaying a first enablement representation for selecting the accessory to receive wireless media without displaying a second enablement representation for selecting a second electronic device connected to the accessory, wherein the first enablement representation for selecting the accessory to receive wireless media establishes a connection between the first electronic device and the second electronic device connected to the accessory; as well as Based on determining that a wireless connection with the accessory for receiving media via the wireless connection is unavailable, forgoing displaying the affordance for selecting the accessory to receive wireless media, wherein when no device is connected to the accessory, The connection with the accessory for receiving media via the wireless connection is unavailable.

2. The method of claim 1, wherein the indication for selecting the accessory to receive wireless media includes an identifier corresponding to the accessory.

3. The method according to any one of claims 1 to 2, wherein the request to display available media devices is a first request, the method further comprising: receiving, via the one or more input devices, a second request to display available wireless media receiver devices; as well as In response to receiving the second request, displaying, via the display device, a user interface for selecting a wireless media receiver for media from the first electronic device, comprising: based on determining that a second wireless connection with an accessory for receiving media via the wireless connection is available, displaying the first affordance for selecting the accessory to receive wireless media, wherein the first affordance for selecting the accessory to receive wireless media indicates establishing a connection between the first electronic device and a third electronic device connected to the accessory, and wherein the first affordance for selecting the accessory to receive wireless media includes the identifier corresponding to the accessory; as well as Based on determining that a second wireless connection with the accessory for receiving media via the wireless connection is unavailable, abandoning display of the first enabling representation for selecting the accessory to receive wireless media, wherein the connection with the accessory for receiving media via the wireless connection is unavailable when no device is connected to the accessory.

4. The method according to any one of claims 1 to 2, further comprising: receiving, while displaying the first affordance for selecting the accessory to receive wireless media, a user input corresponding to a selection of the first affordance for selecting the accessory to receive wireless media; In response to receiving user input corresponding to the selection of the first affordance for selecting the accessory to receive wireless media: connected to the second electronic device; as well as When connected to the second electronic device, an indication is displayed that the first electronic device is connected to the accessory.

5. The method according to claim 4, further comprising: while connected to the second electronic device, transferring media to the second electronic device for presentation via one or more output devices of the accessory; as well as While the media is being transferred to the second electronic device for presentation via the one or more output devices of the accessory, an indication of the media being transferred to the second electronic device for presentation via the one or more output devices of the accessory is displayed.

6. The method according to claim 4, further comprising: receiving a request to stop transmitting the media while transmitting the media to the second electronic device for presentation via one or more output devices of the accessory; as well as In response to receiving the request to stop the media transmission: The transfer of the media to the second electronic device connected to the accessory is stopped.

7. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device having a display device and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 6.

8. An electronic device, comprising: Display devices; one or more input devices; one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 6.

9. An electronic device, comprising: Display devices; one or more input devices; and Device for carrying out the method according to any one of claims 1 to 6.

10. A computer program product comprising one or more programs configured to be executed by one or more processors of an electronic device communicating with a display device and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 6.

Images