Multi-device charging user interface

Abstract

To provide faster, more efficient methods and interfaces for charging multiple electronic devices.SOLUTION: At a first device with a display, it is detected that at least one of the first device or a second device has entered a wireless charging state. In response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, an indication of charge status for the second device is displayed on the display.SELECTED DRAWING: Figure 6I

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority to U.S. Patent Application Publication No. 62 / 514,924, titled "MULTI - DEVICE CHARGING USER INTERFACE", filed on June 4, 2017; U.S. Patent Application Publication No. 62 / 556,387, titled "MULTI - DEVICE CHARGING USER INTERFACE", filed on September 9, 2017; and Danish Patent Application No. PA201870024, titled "MULTI - DEVICE CHARGING USER INTERFACE", filed on January 12, 2018. The entire contents of these applications are hereby incorporated by reference herein.

[0002] This application is related to U.S. Patent Application Publication No. 62 / 514,875, titled "SYNCHRONIZING COMPLEMENTARY NOTIFICATIONS ACROSS RELATED COMPUTING DEVICES CONNECTED TO A WIRELESS CHARGING APPARATUS", filed on June 4, 2017. The entire contents of that application are hereby incorporated by reference herein.

[0003] [Technical Field] The present disclosure generally relates to computer user interfaces, and more particularly, to techniques for charging multiple electronic devices.

Background Art

[0004] Many modern electronic devices operate relying on rechargeable batteries. The charge level of a device's battery decreases as the device is operated, and thus, the device needs to be recharged from time to time for continued use. Further, some users have multiple electronic devices and / or devices that require charging via cables. Accordingly, techniques for wirelessly charging multiple electronic devices are desired.

Summary of the Invention

[0005] However, some techniques for charging multiple electronic devices are generally cumbersome and inefficient. For example, some existing techniques for determining the charge level of one or more devices (e.g., while one or more devices are charging) use a complex and time-consuming user interface that may include multiple key presses or key strokes. With existing technologies, more time than necessary is required, wasting the user's time and the device's power. This former consideration is particularly important in order to provide a user-friendly interface.

[0006] Accordingly, the present techniques provide an electronic device with a faster and more efficient method and interface for charging multiple electronic devices. Such a method and interface optionally complement or replace other methods for charging multiple electronic devices. Such a method and interface reduce the user's cognitive burden and implement a more efficient human-machine interface. Such a method and interface improve the user experience, conserve power, and increase the time during battery charging.

[0007] In some embodiments, a computer-implemented method executed on a first device comprising a display includes detecting that at least one of the first device or the second device has entered a wireless charging state, and in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, displaying an indication of the charge state for the second device on the display.

[0008] In some embodiments, the non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device comprising a display, the electronic device being a first device, and the one or more programs detect that at least one of the first device or the second device has entered a wireless charging state, and in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, include instructions to display an indication of the charging state for the second device on the display.

[0009] In some embodiments, the transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device comprising a display, the electronic device being a first device, and the one or more programs detect that at least one of the first device or the second device has entered a wireless charging state, and in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, include instructions to display an indication of the charging state for the second device on the display.

[0010] In some embodiments, an electronic device includes a display, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors, and the one or more programs detect that at least one of the electronic device or the second device has entered a wireless charging state, and in response to detecting that at least one of the electronic device or the second device has entered a wireless charging state, and in accordance with a determination that the electronic device and the second device are being wirelessly charged by the same wireless charging device, include instructions to display an indication of the charging state for the second device on the display.

[0011] In some embodiments, the electronic device includes a display, means for detecting that at least one of the electronic device or a second device has entered a wireless charging state, and, in response to detecting that at least one of the electronic device or the second device has entered a wireless charging state and in accordance with a determination that the electronic device and the second device are being wirelessly charged by the same wireless charging device, means for displaying an indication of the charging state for the second device on the display.

[0012] In some embodiments, a computer-implemented method, executed on a device, includes receiving a first user input expressing a request for a charging level while the device is wirelessly charging and at a first charging level, outputting a first non-visual indication of the first charging level of the device in response to receiving the first user input, receiving a second user input expressing a request for a charging level while the device is wirelessly charging and at a second charging level different from the first charging level, and outputting a second non-visual indication of the second charging level of the device in response to receiving the second user input, the second non-visual indication being different from the first non-visual indication.

[0013] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions to receive a first user input expressing a request for a charging level while the device is wirelessly charging and at a first charging level, output a first non-visual indication of the first charging level of the device in response to receiving the first user input, receive a second user input expressing a request for a charging level while the device is wirelessly charging and at a second charging level different from the first charging level, and output a second non-visual indication of the second charging level of the device in response to receiving the second user input, the second non-visual indication being different from the first non-visual indication.

[0014] A temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device. The one or more programs include instructions for receiving, while the device is wirelessly charging and at a first charging level, a first user input representing a charging level request; outputting, in response to receiving the first user input, a first non-visual indication of the first charging level of the device; receiving, while the device is wirelessly charging and at a second charging level different from the first charging level, a second user input representing a charging level request; and outputting, in response to receiving the second user input, a second non-visual indication of the second charging level of the device, the second non-visual indication being different from the first non-visual indication.

[0015] In some embodiments, an 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 programs include instructions for receiving, while the device is wirelessly charging and at a first charging level, a first user input representing a charging level request; outputting, in response to receiving the first user input, a first non-visual indication of the first charging level of the device; receiving, while the device is wirelessly charging and at a second charging level different from the first charging level, a second user input representing a charging level request; and outputting, in response to receiving the second user input, a second non-visual indication of the second charging level of the device, the second non-visual indication being different from the first non-visual indication.

[0016] In some embodiments, an electronic device includes means for receiving a first user input expressing a charging level requirement while the device is wirelessly charging and at a first charging level, means for outputting a first non-visual indication of the first charging level of the device in response to receiving the first user input, means for receiving a second user input expressing a charging level requirement while the device is wirelessly charging and at a second charging level different from the first charging level, and means for outputting a second non-visual indication of the second charging level of the device in response to receiving the second user input, the second non-visual indication being different from the first non-visual indication.

[0017] The executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. The executable instructions for performing these functions are optionally included in a transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0018] Thus, a faster and more efficient method and interface for charging an electronic device are provided to the device, thereby increasing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface can complement or replace other methods for charging an electronic device.

Brief Description of the Drawings

[0019] To better understand the various embodiments described, the following "Modes for Carrying Out the Invention" should be referred to in conjunction with the following drawings. Here, like reference numerals refer to corresponding parts throughout the drawings.

[0020]

Figure 1A

[0021]

Figure 1B

[0022]

Figure 2

[0023]

Figure 3

[0024]

Figure 4A

[0025]

Figure 4B

[0026]

Figure 5A

[0027]

Figure 5B

[0028]

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 6E

Figure 6F

Figure 6G

Figure 6H

Figure 6I

Figure 6J

Figure 6K

Figure 6L

Figure 6M

Figure 6N

Figure 6O

Figure 6P

Figure 6Q

Figure 6R

Figure 6S

Figure 6T

Figure 6U

Figure 6V

Figure 6W

Figure 6X

Figure 6Y

Figure 6Z

Figure 6AA

Figure 6AB

Figure 6AC

Figure 6AD

Figure 6AE

Figure 6AF

Figure 6AG

[0029]

Figure 7A

Figure 7B

Figure 7C

Figure 7D

Figure 7E

[0030]

Figure 8A

Figure 8B

Figure 8C

Figure 8D

Figure 8E

[0031]

Figure 9A

Figure 9B

[0032]

Figure 10

[0033]

Figure 11A

Figure 11B

Figure 11C

Figure 11D

[0034] In the following description, exemplary methods, parameters, etc. are described. However, it should be understood that the purpose of such description is not to limit the scope of the present disclosure, but to provide an explanation of exemplary embodiments.

[0035] There is a need for an electronic device that provides an efficient method and interface for charging multiple devices. In one example, when multiple devices are being charged by the same charging device, all of the charge levels of the devices being charged are simultaneously displayed on one device. In another example, a device provides a non-visual indication of its own charge level and / or the charge level of another device (e.g., another device being charged simultaneously). Such techniques can reduce the cognitive burden on a user charging multiple devices, thereby increasing productivity. Further, such technology can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0036] Hereinafter, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide an illustration of an exemplary device for performing techniques for charging an electronic device. FIGS. 6A-6AG show exemplary user interfaces for charging an electronic device. FIGS. 7A-7E are flow diagrams showing methods of charging an electronic device according to some embodiments. The user interfaces in FIGS. 6A-6AG are used to illustrate the processes described hereinafter, including the processes in FIGS. 7A-7E. FIGS. 8A-8E also show exemplary user interfaces for charging an electronic device. FIGS. 9A-9B are flow diagrams showing methods of charging an electronic device according to some embodiments. The user interfaces in FIGS. 8A-8E are used to illustrate the processes described hereinafter, including the processes in FIGS. 9A-9B.

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

[0038] The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a", "an", and "the" are intended to include the plural form as well, unless the context clearly indicates otherwise. As used herein, the term "and / or" refers to and also includes any and all possible combinations of one or more of the associated listed items. The terms "includes", "including", "comprises", and / or "comprising", when used herein, specify the presence of the stated feature, integer, step, operation, element, and / or component, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0039] Optionally, the term "if (in the case of ~)" is construed to mean "when (at the time of ~)", "upon (~ upon doing)", "in response to determining (in response to the determination that ~)", or "in response to detecting (in response to detecting ~)" depending on the context. Similarly, the phrases "if it is determined (if it is determined that ~)" or "if (a stated condition or event) is detected (if (the stated condition or event) is detected)" are optionally construed, depending on the context, to mean "upon determining (when determining ~)", "in response to determining (in response to the determination that ~)", "upon detecting (the stated condition or event) (when detecting (the stated condition or event))", or "in response to detecting (the stated condition or event) (in response to detecting (the stated condition or event))".

[0040] Embodiments of an electronic device, a user interface for such a device, and related processes for using such a device are described. In some embodiments, the device is a portable communication device such as a mobile phone that also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunctional devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices of Apple Inc. of Cupertino, California. Other portable electronic devices such as laptop or tablet computers with a touch-sensitive surface (e.g., a touch screen display and / or a touch pad) may optionally be used. It is also understood that in some embodiments, the device is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and / or a touch pad) rather than a portable communication device.

[0041] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it is understood that the electronic device may optionally include one or more other physical user interface devices such as a physical keyboard, a mouse, and / or a joystick.

[0042] This device generally supports various applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0043] 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, as well as the corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each respective application. Thus, the common (such as touch-sensitive surface) physical architecture of the device optionally supports various applications with a user interface that is intuitive and transparent to the user.

[0044] Attention is now directed to an embodiment of a portable device with a touch-sensitive display. FIG. 1A is a block diagram showing a portable multifunctional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 may be referred to as a "touch screen" for convenience, and may also be known or referred to as a "touch-sensitive display system". The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more light sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the device 100 (such as a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). The device 100 optionally includes one or more haptic output generators 167 for generating haptic output on the device 100 (such as generating haptic output on a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100 or the touch pad 355 of the device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0045] As used in this specification and the claims, the term "intensity" of a contact on a touch-sensing surface refers to the force or pressure (force per unit area) of the contact (e.g., finger contact) on the touch-sensing surface, or an alternative (substitute) for the force or pressure of the contact on the touch-sensing surface. The intensity of the contact has a range of values that includes at least four different values, and more generally, hundreds (e.g., at least 256) of different values. The intensity of the contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensing surface are optionally used to measure the force at various points on the touch-sensing surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated value of the contact force. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensing surface. Alternatively, the size and / or change thereof of the contact area detected on the touch-sensing surface, the capacitance and / or change thereof of the touch-sensing surface in proximity to the contact, and / or the resistance and / or change thereof of the touch-sensing surface in proximity to the contact are optionally used as an alternative to the force or pressure of the contact on the touch-sensing surface. In some implementations, alternative measurements of the contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the alternative measurement). In some implementations, alternative measurements of the contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of the contact as an attribute of user input, a user can gain access to additional device functions that may not otherwise be accessible to the user on a device with a limited area, reduced size (e.g., on a touch-sensing display), and / or reduced size (e.g., via a physical / mechanical control such as a touch-sensing display, touch-sensing surface, or knob or button) for displaying affordances and / or receiving user input.

[0046] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of a device relative to a position in front 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., the housing), or a displacement of a component relative to the center of mass of the device, that is to be detected by a user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of a physical actuator button associated with a touch-sensitive surface that has been physically pushed (e.g., displaced) by the user's movement. As another example, movement of a touch-sensitive surface may optionally be interpreted or felt by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. Such interpretation of touch by the user is subject to the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise specified, the generated haptic output corresponds to a physical displacement of a device, or a component of the device, that produces the described sensory perception of a typical (or average) user.

[0047] Device 100 is merely an example of a portable multifunctional device, and it should be understood that Device 100 may optionally have more or fewer components than those shown, and may optionally combine two or more components, or have different configurations or arrangements of components. The various components shown in FIG. 1A are implemented in a combination of hardware, software, or both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.

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

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

[0050] The RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, and memory. The RF circuit 108 optionally communicates wirelessly with other devices over a network such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN) and / or a metropolitan area network (MAN). The RF circuit 108 optionally includes well-known circuits for detecting a near field communication (NFC) field, such as near field wireless communication. Wireless communication optionally uses any of a plurality of communication standards, communication protocols, and communication technologies, including Global System for Mobile Communications (GSM (registered trademark)) for mobile communication, 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 divisionmultiple access, W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth (registered trademark), Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (registered trademark) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for e-mail (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed as of the filing date of this document, but not limited thereto.

[0051] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally obtained 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 further includes a headset jack (e.g., 212 in FIG. 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 an output (e.g., mono or stereo headphones) and an input (e.g., a microphone).

[0052] The I / O subsystem 106 couples the input / output peripheral devices of device 100, such as the touch screen 112 and other input control devices 116, to the peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / transmit electrical signals from / to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to (or not coupled to any of) a pointer device such as a keyboard, an infrared port, a USB port, and a mouse. One or more buttons (e.g., 208 of FIG. 2) optionally include up / down buttons for volume adjustment of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., 206 of FIG. 2).

[0053] Optionally, as described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, and issued as U.S. Patent No. 7,657,849, "Unlocking a Device by Performing Gestures on an Unlock Image" (which patent is hereby incorporated by reference in its entirety), the lock of the touch screen 112 is released by a quick press of a push button, or the process of using gestures on the touch screen to unlock the device is optionally started. By pressing a push button (e.g., 206) for a longer time, the power of the device 100 is optionally turned on or off. The functions of one or more of the buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0054] 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 transmits 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, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, optionally, some or all of the visual output corresponds to user interface objects.

[0055] The touch screen 112 has a touch sensing surface, sensor, or set of sensors that receive input from a user based on tactile and / or haptic contact. The touch screen 112 and the display controller 156 (along with any associated modules and / or instruction sets within the memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into an interaction with user interface objects (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 the user's finger.

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

[0057] The touch-sensing display in some embodiments of the touch screen 112 is optionally similar to a multi-touch sensing touch pad described in the following U.S. Patents: U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and / or U.S. Pat. No. 6,677,932 (Westerman), and / or U.S. Patent Application Publication No. 2002 / 0015024 (A1). Each of these documents is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, whereas the touch-sensing touch pad does not provide visual output.

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

[0059] The touch screen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally contacts the touch screen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to function primarily based on finger-based contact and gestures, and due to the large contact area of the finger on the touch screen, it may be less accurate than stylus-based input. In some embodiments, the device converts finger-based rough input into an accurate pointer / cursor position or a command to execute the user's desired action.

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

[0061] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0062] Device 100 also optionally includes one or more optical sensors 164. FIG. 1A shows an optical sensor connected to an optical sensor controller 158 within I / O subsystem 106. Optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts that light into data representing an image. In combination with imaging module 143 (also referred to as a camera module), optical sensor 164 optionally captures a still image or video. In some embodiments, the optical sensor is disposed on the back of device 100, which is opposite touch screen display 112 on the front of the device, so as to enable the touch screen display to be used as a viewfinder for still image and / or video acquisition. In some embodiments, optionally, an optical sensor is disposed on the front of the device so that a user's image can be obtained for a video conference at the same time the user views other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating lenses and sensors within the device housing), thereby enabling a single optical sensor 164 to be used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0063] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a surrogate for pressure information) from the surrounding environment. In some embodiments, at least one contact intensity sensor is disposed on or proximate to a touch sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back of device 100, which is opposite the touch screen display 112 disposed on the front of device 100.

[0064] Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to the peripheral device interface 118. Alternatively, the proximity sensor 166 is optionally connected to an input controller 160 within the I / O subsystem 106. The proximity sensor 166 may optionally be implemented as described in U.S. Patent Application Nos. 11 / 241,839, "Proximity Detector In Handheld Device", 11 / 240,788, "Proximity Detector In Handheld Device", 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output", 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices", and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals". In some embodiments, when a multifunctional device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0065] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output) on the device. The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is disposed on or proximate to a touch sensing surface (e.g., touch sensing display system 112) and optionally generates a haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or a lateral direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back of device 100, on the opposite side of touch screen display 112 disposed on the front of device 100.

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

[0067] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Further, in some embodiments, as shown in FIGS. 1A and 3, memory 102 (FIG. 1A) or memory 370 (FIG. 3) stores a device / global internal state 157. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active if there is a currently active application, a display state indicating which application, view, or other information occupies various regions of the touch screen display 112, a sensor state including information obtained from various sensors and input control devices 116 of the device, and position information regarding the position and / or orientation of the device.

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

[0069] The communication module 128 facilitates communication with other devices via 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 ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE (registered trademark), etc.) are adapted to connect to other devices either directly or indirectly through a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is the same as or similar to the 30-pin connector used on an iPod (registered trademark) device (a trademark of Apple Inc.) and / or a compatible multi-pin (e.g., 30-pin) connector.

[0070] The contact / motion module 130 optionally detects contact with the touch screen 112 and other touch sensing devices (e.g., a touch pad or a physical click wheel) (in cooperation with the display controller 156). The contact / motion module 130 includes various software components for performing various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting an event of a finger being lowered), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch sensing surface (e.g., detecting one or more events of a finger being dragged), and determining whether the contact has stopped (e.g., detecting an event of a finger being raised or an interruption of the contact). The contact / motion module 130 receives contact data from the touch sensing surface. Determining the movement of the contact point represented by a series of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., contact of one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact of multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0071] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., to determine whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of device 100). For example, the mouse "click" threshold of a trackpad or touch screen display may be set to any of a wide range of predefined thresholds without changing the hardware of the trackpad or touch screen display. Further, in some implementations, the user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level click "intensity" parameters).

[0072] The contact / motion module 130 optionally detects gesture inputs by the user. Different gestures on the touch-sensing surface have different contact patterns (e.g., different motions, timings, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture includes detecting an event of lowering a finger (e.g., at the location of an icon) and subsequently detecting an event of raising (lifting off) the finger at the same location (or substantially the same location) as the event of lowering the finger. As another example, detecting a finger swipe gesture on the touch-sensing surface includes detecting an event of lowering a finger, subsequently detecting one or more events of dragging the finger, and then subsequently detecting an event of raising (lifting off) the finger.

[0073] The graphic 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 effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). As used herein, the term "graphic" includes, but is not limited to, any object that can be displayed to the user, including text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

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

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

[0076] The text input module 134 is optionally a component of the graphic module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).

[0077] 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 calling, to the camera 143 as photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map / navigation widgets).

[0078] The application 136 optionally includes the following modules (or instruction sets), or subsets or supersets thereof. ● Contact module 137 (also sometimes referred to as an address book or contact list), ● Phone module 138, ● Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ● Training support module 142, ● Camera module 143 for still and / or video images, ● Image management module 144, ● Video player module, ● Music player module, ● Browser module 147, ● Calendar module 148, ● Widget module 149 that optionally includes one or more of weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets acquired by the user, as well as user-created widget 149-6, ● Widget creation module 150 for creating user-created widget 149-6, ● Search module 151, ● Video and music player module 152 that integrates the video player module and the music player module, ● Memo module 153, ● Map module 154, and / or ● Online video module 155.

[0079] Examples of other applications 136 optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA (registered trademark)-compatible applications, encryption, digital rights management, voice recognition, and voice replication.

[0080] Together with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the 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 the memory 102 or the memory 370), which includes adding a name (singular or plural) to the address book, deleting a name (singular or plural) from the address book, associating a phone number (singular or plural), an email address (singular or plural), an address (singular or plural), or other information with a name, associating an image with a name, classifying and sorting names, providing a phone number or email address to initiate and / or facilitate communication by phone 138, the video conferencing module 139, email 140, or IM 141, etc.

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

[0082] In cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the light sensor 164, the light sensor controller 158, the contact / motion module 130, the graphic module 132, the text input module 134, the contact module 137, and the telephone module 138, the videoconference module 139 includes executable instructions for starting, conducting, and ending a videoconference between the user and one or more other participants according to the user's instructions.

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

[0084] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering a string corresponding to an instant message, modifying an entered character, transmitting a corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for phone-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), receiving an instant message, and viewing a received instant message. In some embodiments, the instant messages transmitted and / or received optionally include graphics, photos, audio files, video files, and / or other attached files as supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0085] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and music player module, training support module 142 creates a training (e.g., having time, distance, and / or calorie consumption goals), communicates with a training sensor (sports device), receives training sensor data, calibrates sensors used to monitor the training, selects and plays music for the training, and displays, stores, and transmits training data.

[0086] In conjunction with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphic module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including video streams), store them in memory 102, modify the characteristics of the still images or video, or delete the still images or video from memory 102.

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

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

[0089] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable instructions to create, display, modify, and store a calendar and data associated with the calendar (e.g., calendar items, to do lists, etc.) according to user instructions.

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

[0091] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, the widget creation module 150 is optionally used by the user to create a widget (e.g., change a user-specified location on a web page to a widget).

[0092] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the search module 151 includes executable instructions for searching for text, music, sounds, images, videos, and / or other files within the memory 102 that match one or more search criteria (e.g., one or more user-specified search phrases) in accordance with a user's instruction.

[0093]

[0092] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, the audio circuit 110, the speaker 111, the RF circuit 108, and the browser module 147, the video and music player module 152 includes executable instructions that enable a user to download and play 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 videos (e.g., on the touch screen 112 or on an external display connected via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

[0094] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do lists, etc. in accordance with a user's instruction.

[0095] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 optionally receives, displays, modifies, and stores maps and data associated with the maps (e.g., driving directions, data on stores and other attractions near or at a particular location, and other location-based data) in accordance with a user's instructions for use.

[0096] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphic 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 that enable a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touch screen or on an external display connected via external port 124), send an email including a link to a particular online video, and otherwise manage one or more file format online videos, such as H.264. In some embodiments, an instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are hereby incorporated by reference in their entirety.

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

[0098] In some embodiments, the device 100 is a device in which the operation of a set of pre-defined functions on the device is exclusively performed through a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the main input control device for the operation of the device 100, the number of physical input control devices (push buttons, dials, etc.) on the device 100 is optionally reduced.

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

[0100] FIG. 1B is a block diagram showing exemplary components for event processing in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or memory 370 (FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and a corresponding application 136-1 (e.g., any of applications 137-151, 155, 380-390 described above).

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

[0102] In some embodiments, the application internal state 192 includes additional information such as resume information used when the application 136-1 resumes execution, user interface state information indicating information being displayed or prepared for display by the application 136-1, a state waiting queue to enable the user to return to a previous state or view of the application 136-1, and a redo / undo waiting queue for previous actions performed by the user.

[0103] The event monitor 171 receives event information from the peripheral device interface 118. The event information includes information regarding sub-events (e.g., a user touch on the touch-sensitive display 112 as part of a multi-touch gesture). The peripheral device interface 118 transmits information received from the I / O subsystem 106, or sensors such as the proximity sensor 166, the accelerometer(s) 168, and / or the microphone 113 (via the audio circuit 110). The information that the peripheral device interface 118 receives from the I / O subsystem 106 includes information from the touch-sensitive display 112 or the touch-sensitive surface.

[0104] In some embodiments, the event monitor 171 transmits requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when a significant event (e.g., receiving an input that exceeds a predetermined noise threshold and / or is longer than a predetermined duration) exists.

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

[0106] The hit view determination module 172 provides a software procedure for determining where within one or more views a sub-event has occurred when the touch-sensitive display 112 displays two or more views. A view is composed of the control unit and other elements that the user can view on the display.

[0107] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, within which information is displayed and touch-based gestures occur. The application views (for each application) where touches are detected optionally correspond to a program level within the program hierarchy or view hierarchy of the application. For example, the lowest level view where a touch is detected is optionally called the hit view, and the set of events recognized as appropriate input is optionally determined based at least in part on the hit view of the initial touch that starts a touch-based gesture.

[0108] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has a plurality of views organized in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest level view within the hierarchy in which to process the sub-events. In most situations, the hit view is the lowest level view where the first sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view generally receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0109] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-event are views that are actively involved, and thus all views that are actively involved should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely limited to a region associated with a particular view, the upper-level views in the hierarchy will still continue to be views that are actively involved.

[0110] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 distributes event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information obtained by the corresponding event receiver 182 in an event queue.

[0111] In some embodiments, the operating system 126 includes an event sorter 170. Alternatively, the application 136-1 includes an event sorter 170. In still other embodiments, the event sorter 170 is an independent module or part of another module stored in the memory 102, such as the touch / motion module 130.

[0112] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Generally, a corresponding application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other characteristics. In some embodiments, a corresponding event processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. The event processing unit 190 optionally utilizes or calls data update unit 176, object update unit 177, or GUI update unit 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event processing units 190. Also, in some embodiments, one or more of data update unit 176, object update unit 177, and GUI update unit 178 are included in a corresponding application view 191.

[0113] A corresponding event recognition unit 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).

[0114] The event receiving unit 182 receives event information from the event sorting unit 170. The event information includes sub-events, for example, information regarding a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information such as the position of the sub-event. When the sub-event is related to the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from 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 posture of the device).

[0115] The event comparison unit 184 compares the event information with a predefined event or sub-event definition, and based on the comparison, determines an event or a sub-event, or determines or updates the state of an event or a sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes, for example, definitions of events such as event 1 (187-1), event 2 (187-2), etc. (e.g., a predefined series of sub-events). In some embodiments, the sub-events in event 187 include, for example, the start of a touch, the end of a touch, the movement of a touch, the stop of a touch, and multiple touches. In one example, the definition of event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (start of the touch) on the displayed object during a predetermined period, a first lift-off (end of the touch) during a predetermined period, a second touch (start of the touch) on the displayed object during a predetermined period, and a second lift-off (end of the touch) during a predetermined period. In another example, the definition of event 2 (187-2) is a drag operation on a displayed object. The drag operation includes, for example, a touch (or contact) on the displayed object during a predetermined period, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event processing units 190.

[0116] In some embodiments, the event definition 187 includes the definition of events for each user interface object. In some embodiments, the event comparison unit 184 performs a hit test to determine the user interface object associated with the sub-event. For example, in an application view where three user interface objects are displayed on the touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparison unit 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 processing unit 190, the event comparison unit uses the result of the hit test to determine which event processing unit 190 should be activated. For example, the event comparison unit 184 selects the event processing unit associated with the sub-event and object that trigger the hit test.

[0117] In some embodiments, the definition for the corresponding event (187) also includes a delay action that delays the delivery of event information until it is determined whether a series of sub-events correspond to the event type of the event recognition unit.

[0118] When the corresponding event recognition unit 180 determines that a series of sub-events do not match any of the events in the event definition 186, the corresponding event recognition unit 180 enters a state of event impossible, event failure, or event end, and then ignores the next sub-event of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, that event recognition unit continues to track and process the sub-events of the touch-based gesture in progress.

[0119] In some embodiments, the corresponding event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event distribution system should actively participate in event recognition for sub - event distribution. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how event recognition units interact with each other or are enabled to interact. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub - events are distributed at various levels in the view hierarchy or program hierarchy.

[0120] In some embodiments, each event recognition unit 180 activates an event processing unit 190 associated with the event when one or more specific sub - events of the event are recognized. In some embodiments, each event recognition unit 180 distributes event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub - events to each hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with the flag catches the flag and executes a predefined process.

[0121] In some embodiments, the event distribution command 188 includes a sub - event distribution command that distributes event information about sub - events without activating the event processing unit. Instead, the sub - event distribution command distributes event information to an event processing unit associated with a series of sub - events or to a view actively involved. The event processing unit associated with a series of sub - events or with a view actively involved receives the event information and executes a predefined process.

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

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

[0124] The foregoing discussion regarding event processing of a user's touch on the touch-sensitive display also applies to other forms of user input for operating the multifunctional device 100 with an input device, it being understood that not all of them are initiated on the touch screen. For example, the movement of a mouse and the pressing of a mouse button optionally associated with the pressing or holding of a single or multiple keyboards, the tapping, dragging, scrolling, etc. of contact movements on a touch pad, pen stylus input, the movement of the device, spoken instructions, detected eye movements, biometric input, and / or any combination thereof are optionally utilized as input corresponding to sub-events that define events to be recognized.

[0125] Figure 2 shows a portable multifunctional device 100 having a touch screen 112, according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this and the embodiments described hereinafter, the user can select one or more of the graphics by performing gestures on the graphics, for example, using one or more fingers 202 (not drawn to an exact scale in the figure) or one or more styli 203 (not drawn to an exact scale in the figure). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, upward, and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, from left to right, upward, and / or downward). In some implementations or situations, an unexpected contact with a graphic does not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon does not optionally select the corresponding application.

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

[0127] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume adjustment button(s) 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 power on / off on the device by pressing the button and holding it in the pressed state for a predetermined time, to lock the device by pressing the button and releasing the button before a predetermined time has elapsed, and / or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also receives verbal input through microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on touch screen 112, and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

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

[0129] Each of the elements of FIG. 3 identified above is optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., sets of instructions) identified above need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules may be combined or otherwise reorganized. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Further, memory 370 optionally stores additional modules and data structures not described above.

[0130] Next, for example, attention is directed to embodiments of a user interface optionally implemented on portable multifunctional device 100.

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

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

[0133] FIG. 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) that includes a touch sensing surface 451 (e.g., the tablet or touch pad 355 of FIG. 3) separate from the display 450 (e.g., touch screen display 112). The device 300 may also optionally include one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of contact on the touch sensing surface 451 and / or one or more haptic output generators 357 for generating haptic output to the user of the device 300.

[0134] Some of the following examples are described with reference to input on the touch screen display 112 (when the touch sensing surface and the display are combined), but in some embodiments, the device detects input on a touch sensing surface separate from the display, as shown in FIG. 4B. In some embodiments, this touch sensing surface (e.g., 451 of FIG. 4B) has a major axis (e.g., 452 of FIG. 4B) corresponding to the major axis (e.g., 453 of FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with the touch sensing surface 451 (e.g., 460 and 462 of FIG. 4B) at locations corresponding to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). Thus, when the touch sensing surface is separate from the display, user input (e.g., contacts 460 and 462 and their movement) detected by the device on the touch sensing surface (e.g., 451 of FIG. 4B) is used by the device to operate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunctional device. It should be understood that a similar approach is optionally used for other user interfaces described herein.

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

[0136] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as the touch screen 504. Instead of or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally has one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of the device 500 can respond to the touch based on the intensity of the touch, which means that touches of different intensities can call different user interface operations on the device 500.

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

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

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

[0140] Input mechanism 508 can optionally be a microphone in some embodiments. Personal electronic device 500 can optionally include various sensors such as a GPS sensor 532, an accelerometer 534, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which can be operably connected to I / O section 514.

[0141] The memory 518 of the personal electronic device 500 can include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, can cause, for example, the computer processor to execute the techniques described below, including process 700 and process 900 (FIGS. 7A-7E and FIGS. 9A-9B). A computer-readable storage media can be any media that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage media is a transitory computer-readable storage media. In some examples, the storage media is a non-transitory computer-readable storage media. Non-transitory computer-readable storage media can 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 (registered trademark) technology, and persistent solid-state memories such as flash, solid-state drives. The personal electronic device 500 is not limited to the components and configurations of FIG. 5B and can include other components or additional components in a plurality of configurations.

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

[0143] As used herein, the term "focus selector" refers to an input element that indicates the current part of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3, or touch-sensitive surface 451 of FIG. 4B), and the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor functions as a "focus selector" and the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A, or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, when a contact detected on the touch screen serves as a "focus selector", 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, and that particular user interface element is adjusted according to the detected input. In some embodiments, the focus is moved from one area of the user interface to another area of the user interface (e.g., by using a tab key or arrow keys to move the focus from one button to another button) without a corresponding movement of the cursor or movement of the contact on the touch screen display, and in those embodiments, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intends to interact).For example, when a pressing input is detected on a touch sensing surface (e.g., a touch pad or a touch screen), the position of a focus selector (e.g., a cursor, a contact, or a selection box) over the corresponding button indicates that the user is attempting to activate the corresponding button (as opposed to other user interface elements shown on the device's display).

[0144] As used in this specification and the claims, the term "characteristic strength" of a contact refers to a characteristic of the contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on a plurality of strength samples. The characteristic strength is optionally based on a set of strength samples collected during a predefined number of strength samples, or during a predefined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predefined event (e.g., after detecting the contact, before detecting the lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the strength of the contact, and / or before or after detecting a decrease in the strength of the contact). The characteristic strength of the contact is optionally based on one or more of the maximum value of the strength of the contact, the mean value of the strength of the contact, the average value of the strength of the contact, the top 10% value of the strength of the contact, a value that is half of the maximum value of the strength of the contact, a value that is 90% of the maximum value of the strength of the contact, etc. In some embodiments, the duration of the contact is used (e.g., when the characteristic strength is the average of the strength of the contact over time) to determine the characteristic strength. In some embodiments, the characteristic strength is compared to a set of one or more strength thresholds to determine whether an operation has been performed by a user. 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 first operation is performed as a result of a contact having a characteristic strength that does not exceed the first threshold, a second operation is performed as a result of a contact having a characteristic strength that exceeds the first threshold and does not exceed the second threshold, and a third operation is performed as a result of a contact having a characteristic strength that exceeds the second threshold. In some embodiments, the comparison between the characteristic strength and one or more thresholds is used not to determine which of the first or second operations to perform, but to determine whether to perform one or more operations (e.g., whether to perform each operation, or to defer the execution of each operation).

[0145] In some embodiments, for the purpose of determining the characteristic intensity, a portion of the gesture is specified. For example, the touch sensing surface optionally receives a continuous swipe contact that transitions from a starting position to an ending position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending position is optionally based on only a portion of the swipe contact (e.g., only the portion of the swipe contact at the ending position) rather than the entire continuous swipe contact. In some embodiments, optionally, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of a non - weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms remove minor increases or decreases in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

[0146] The intensity of a contact on the touch sensing 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 the intensity at which the device performs an operation generally associated with clicking a button or trackpad of a physical mouse. In some embodiments, the deep press intensity threshold corresponds to the intensity at which the device performs an operation different from the operation typically associated with clicking a button or trackpad of a physical mouse. In some embodiments, if a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a slight contact detection intensity threshold below which the contact is no longer detected), the device moves the focus selector in accordance with the movement of the contact on the touch sensing surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface figures.

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

[0148] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding pressing input, or in response to detecting a corresponding pressing input performed with a corresponding contact (or contacts), and the corresponding pressing input is detected based at least in part on detecting an increase in the strength of a contact (or contacts) that exceeds a pressing input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the strength of the corresponding contact (e.g., the "downstroke" of the corresponding pressing input) that exceeds the pressing input strength threshold. In some embodiments, the pressing input includes an increase in the strength of each contact that exceeds the pressing input strength threshold and a subsequent decrease in the strength of the contact that is below the pressing input strength threshold, and each operation is performed in response to detecting a decrease in the strength of each contact (e.g., the "upstroke" of each pressing input) that is below the subsequent pressing input threshold.

[0149] In some embodiments, the device employs intensity hysteresis to avoid unpredictable inputs sometimes referred to as "jitter", and the device defines or selects a hysteresis intensity threshold having a predefined relationship with the pressing input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the pressing input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable ratio of the pressing input intensity threshold). Thus, in some embodiments, the pressing input includes an increase in the intensity of each contact above the pressing input intensity threshold and a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the subsequent pressing input intensity threshold, and each operation is performed in response to the detection of a decrease in the intensity of each subsequent contact below its hysteresis intensity threshold (e.g., the "upstroke" of each pressing input). Similarly, in some embodiments, the pressing input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressing input intensity threshold and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and each operation is performed in response to the detection of that pressing input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the situation).

[0150] For ease of explanation, the description of operations performed in response to a pressing input associated with a pressing input intensity threshold or in response to a gesture including a pressing input is optionally triggered by the detection of any of an increase in the intensity of the contact above the pressing input intensity threshold, an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressing input intensity threshold, a decrease in the intensity of the contact below the pressing input intensity threshold, and / or a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the pressing input intensity threshold. Additionally, in embodiments described as having an operation performed in response to the detection of a decrease in the intensity of the contact below the pressing input intensity threshold, the operation is optionally performed in response to the detection of a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressing input intensity threshold.

[0151] 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., opened) on that device. In some embodiments, a downloaded application becomes an installed application by an installation program that extracts program portions from the downloaded package and integrates the extracted portions with the operating system of the computer system.

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

[0153] As used herein, the term "closed application" refers to a software application for which state information is not retained (e.g., state information regarding the closed application is not stored in the device's memory). Thus, closing an application includes stopping and / or removing the application process associated with that application, and removing the state information regarding that application from the device's memory. Generally, even if a second application is opened while a first application is open, the first application is not closed. When the second application is displayed and the display of the first application is stopped, the first application becomes a background application.

[0154] Next, attention is paid to embodiments of a user interface ("UI") and related processes implemented on an electronic device such as the portable multifunctional device 100, device 300, or device 500.

[0155] Figures 6A - 6AG show exemplary user interfaces for charging a plurality of electronic devices, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 7A - 7E.

[0156] FIG. 6A shows a primary device 610 (e.g., a smartphone), a secondary device 620 (e.g., a smartwatch), and a charging device 600. In some embodiments, the primary device 610 is a portable multifunctional device 100, device 300, device 500, or other electronic device (e.g., an electronic watch, a tablet computer) that includes a display. In some embodiments, the secondary device 620 is a portable multifunctional device 100, device 300, device 500, or other electronic device (e.g., a smartphone, an electronic watch, a tablet computer, battery-operated earphones (e.g., AirPods™, etc.)) that may or may not include a display. In some embodiments, the secondary device 620 includes a case, dock, or the like through which the secondary device 620 interfaces with the charging device 600.

[0157] In some embodiments, the primary device 610 and the secondary device 620 are paired in the sense that they are configured to exchange information (e.g., via a wireless communication link such as Bluetooth™, or via pulses transmitted by the charging coil of the charging device 600 as a backup communication method). In some embodiments, the primary device 610 and / or the secondary device 620 are included within a set of devices that are associated with each other (e.g., associated with the same iCloud™ account or paired with each other). In some embodiments, the set of devices associated with each other includes one or more of a device paired with at least one other device in the set and a device associated with the same user account (e.g., iCloud™). In some embodiments, the devices are configured to exchange data in another manner. For example, the devices are logged onto the same WiFi network.

[0158] The charging device 600 is configured to charge a primary device 610 and a secondary device 620. Optionally, the charging device 600 is configured to wirelessly charge the primary device 610 and / or the secondary device 620. In some embodiments, the charging device 600 includes a substantially flat surface (e.g., a mat) on which the primary device 610 and the secondary device 620 can be placed for wireless charging. The primary device 610 and the secondary device 620 are configured to enter a wireless charging state when placed on the charging device 600. Optionally, the charging device 600 has the ability for wireless and / or wired communication. In one example, the charging device 600 has the ability for wireless communication with the primary device 610, the secondary device 620, and / or other electronic devices via the Bluetooth® and / or near-field communication (NFC) protocol, or through a wireless network. In some embodiments, the charging device 600 is the wireless charging device 1002 (described below), or includes one or more features or elements of the wireless charging device 1002.

[0159] Figures 6B - 6F show one embodiment of a user interface in which the primary device 610 is placed on the charging device 600 for charging. Figure 6B shows the primary device 610 placed on the charging device 600. When the primary device 610 is placed on the charging device 600, the primary device 610 detects that it has entered a wireless charging state (e.g., that it has just started charging in response to being placed on the charging mat). In response to detecting that the primary device 610 has entered a wireless charging state, the primary device 610 provides an indication of the charging state (e.g., a visual or other type of indication that the charging state of the primary device 610 has changed).

[0160] In the illustrated embodiment, the indication of the charge state for the primary device 610 includes a haptic output (e.g., the primary device 610 provides a haptic output when placed on the charging device 600), as shown in FIG. 6B. The primary device 610 also displays a visual indication (e.g., an animation or a graphical interface object(s)) that the primary device 610 has entered the wireless charging state. FIG. 6C shows an exemplary animation in which a graphic representation of the primary device 610 (e.g., iPhone (registered trademark)) spins, flips, twists, and / or twirls to indicate that the primary device 610 has entered the charging state. In another embodiment, the primary device 610 displays a charge state indicator 644 (described in more detail below), as shown in FIG. 6F, and / or pulsates or blinks a battery icon 644-2 within the charge state indicator 644 or the settings state indicator 645 to indicate that the primary device 610 has entered the charging state.

[0161] Following the animation shown in FIG. 6C, the primary device 610 displays a charge state interface 640 having a charge state indicator 641, as shown in FIG. 6D. The charge state indicator 641 includes a charge state platter indicating the charge level of the primary device 610.

[0162] In the embodiment shown in FIG. 6D, the charge state indicator 641 includes a battery indicator 641-1 that includes a text indication 641-1A (68%) of the charge level of the battery of the primary device 610 as a percentage, a graphical indication 641-1B of the charge level (a battery icon partially filled in proportion to the charge level of the primary device 610), and a current state indication 641-1C (lightning bolt) that the primary device 610 is currently charging. The charge state indicator 641 also includes a graphical identifier 641-2 of the primary device 610 that includes the name (Device 1) associated with the primary device 610 and a representative image of the primary device 610 (a thumbnail image of an iPhone (registered trademark)). In some embodiments, the charge state indicator 641 includes one or more of the features included within the battery indicator 641-1 and the graphical identifier 641-2.

[0163] In some embodiments, displaying the charge state indicator 641 includes a fly-in animation of the charge state platter. In some embodiments, the graphical indication of the charge level includes a partially filled ring. In some embodiments, the indication of the charge level includes an animation representing the charge level (e.g., a ripple and / or impact effect that indicates the charge level (e.g., varying based on the charge level) and is referred to herein as a "ripple" effect), or a color-based indication representing the charge level (e.g., green for full charge, yellow for partial charge, and red for low / no charge).

[0164] Optionally, the charge state indicator 641 is displayed as long as the primary device 610 is charging and is removed (e.g., stopped being displayed) after the primary device 610 is no longer charging (e.g., after being removed from the charging device 600). Optionally, the charge state interface 640 includes a setting state indicator 645 that indicates the state of various device settings (e.g., do not disturb, GPS, Bluetooth (registered trademark), etc.).

[0165] After the charging state interface 640 is displayed (e.g., over a predetermined time), the primary device 610 animates a transition to another more compact charging state indicator 644 shown in FIG. 6F. FIG. 6E shows an exemplary transition where the charging state indicator 641 is scaled down and the settings state indicator 645 is translated out of the right edge of the display 612. The charging state indicator 644 includes the same features as the battery indicator 641-1 described above and indicates the charging state of the primary device 610. In some embodiments, the charging state indicator 644 includes one or more items from the settings state indicator 645 (e.g., Bluetooth® state), as well as one or more charge level indicators (e.g., text indication 641-1A and battery icon 641-1B).

[0166] Next, as shown in FIG. 6G, the secondary device 620 is placed on the charging device 600 together with the primary device 610 and enters the wireless charging state. In response to the secondary device 620 being placed on the charging device 600, the primary device 610 detects that the secondary device 620 has entered the wireless charging state. Optionally, the primary device 610 receives data from the secondary device 620 via a communication link (e.g., Bluetooth®, or a pulse transmitted through the charging coil of the charging device 600), where the data indicates that the secondary device 620 has entered the wireless charging state and / or represents the charging state of the secondary device 620. In some embodiments, the secondary device 620 is placed on the charging device 600 prior to the primary device 610 being placed on the charging device 600.

[0167] When at least one of the primary device 610 or the secondary device 620 enters a wireless charging state (e.g., is placed on the charging device 600), and in response to determining that both the primary device 610 and the secondary device 620 are being wirelessly charged by the same charging device 600, the primary device 610 displays an indication of the charging state for the secondary device 620. In the illustrated embodiment, the primary device 610 displays an animation in which the graphic representation of the secondary device 620 rotates, flips, turns, and / or spins, as indicated in FIG. 6H, to indicate that the charging state of the secondary device 620 has changed (e.g., the secondary device 620 has entered a charging state).

[0168] Following the animation, the primary device 610 displays a charging state interface 640 having a charging state indicator 641 for the primary device 610 and a charging state indicator 642 for the secondary device 620, as shown in FIG. 6I. Similar to the charging state indicator 641 for the primary device 610, the charging state indicator for the secondary device 620 includes an identifier of the secondary device 620 (representation image and name), the charging level of the secondary device 620 (in both text and graphical forms), and an indication that the secondary device 620 is currently charging (lightning bolt). In some embodiments, the secondary device 620 also outputs (e.g., displays) an indication of its charging level (e.g., a visual or non-visual indication of the charging level).

[0169] In some embodiments, displaying an indication of the charging state for the secondary device 620 includes a fly-in animation of the charging state indicator 641 and / or the charging state indicator 642. In some embodiments, the primary device 610 displays a charging state indicator 644 and / or pulsates or blinks a battery icon 644-2 within the charging state indicator 644 or the setting state indicator 645 to indicate that the secondary device 620 has entered a charging state.

[0170] In some embodiments, when the primary device 610 enters a wireless charging state or another device detects that the primary device 610 has entered a wireless charging state while being placed on the charging device 600, the primary device 610 displays an indication of the charging state (e.g., a platter) for each device being wirelessly charged by the charging device 600. In this sense, the primary device 610 is the "host device" that displays a multi-device charging state interface including a charging state platter for each device currently being charged on the charging device 600.

[0171] In some embodiments, the primary device 610 displays the charging state indicators (e.g., 641 and 642) in a specific order. In FIG. 6I, the charging state indicator 641 and the charging state indicator 642 are displayed on the display 612 in an ordered array (e.g., a vertical list). In some embodiments, the charging state indicators are displayed in a horizontal list. In some embodiments, the ordered array is a predetermined array based on the type of device associated with each corresponding charging state indicator (e.g., the phone is always first, then the watch, then the earphones (e.g., iPhone (registered trademark), then Apple Watch (registered trademark), then AirPods (registered trademark))). In some embodiments, the ordered array is at least partially based on the order in which each corresponding device entered the wireless charging state (e.g., a first-in, first-out (FIFO) list of charging state indicators for each device). In some embodiments, the charging state indicator of the device (e.g., the primary device 610) that displays the charging state interface is always displayed first (e.g., at the top or leftmost), followed by the indicators listed in first-in, first-out order.

[0172] In some embodiments, the charging state interface 640 is state - dependent (e.g., the primary device 610 displays different charging state interfaces based on a particular state). In one example, the primary device 610 determines whether the primary device 610 is in a low - interference condition (e.g., whether it is in a do - not - disturb mode or in a dark room). In accordance with a determination that the primary device 610 is not in a low - interference condition, the primary device 610 displays an indication of the charging state for the secondary device 620 as described above (e.g., displays the indication as normal). Alternatively, in accordance with a determination that the primary device 610 is in a low - interference condition, the primary device 610 displays a low - interference indication of the charging state for the secondary device 620 (e.g., a charging state indicator 642 or 644 that moves red and / or has a lower light output).

[0173] As described above, in some embodiments, the primary device 610 is included within a set of devices associated with each other. In one such example, the primary device 610 determines whether the secondary device 620 is included within a set of devices associated with each other. In accordance with a determination that the secondary device 620 is included within a set of devices associated with each other, the primary device 610 displays an indication of the charging state for the secondary device 620 as described above. Alternatively, in accordance with a determination that the secondary device 620 is not included within a set of devices associated with each other, the primary device 610 refrains from displaying an indication of the charging state for the secondary device 620 (e.g., the charging state indicator 642).

[0174] Next, referring to FIGS. 6J - 6K, after displaying the charging state indicators 641 and 642, the primary device 610 displays an animated transition from the charging state interface 640 to the charging state indicator 644 of the primary device 610, similar to the transitions described above with reference to FIGS. 6D - 6F.

[0175] Next, as shown in FIG. 6K, a user input 650 (e.g., a tap) is detected on the battery icon 644-2 within the charge status indicator 644 (e.g., the battery icon 644-2 and / or the charge status indicator 644 are selectable affordances). In response, the primary device 610 displays a charge status interface 640 having charge status indicators 641 and 642 (e.g., having charge status indicators for all devices currently charging on the charging device 600). In the illustrated embodiment, displaying the charge status interface 640 in response to the user input 650 includes an animation in which the charge status indicator 644 (including the battery icon 644-2) is removed from the display 612 and the charge status interface 640 transitions onto the display 612. As shown in FIGS. 6K-6M, the animation is the reverse of the animation shown by FIGS. 6I-6K.

[0176] Next, referring to FIG. 6N, the device 600 ceases to display the charge status interface 640, which includes an indication of the charge status (e.g., the charge status indicator 642) for the secondary device 620. In the illustrated embodiment, the display 612 of the primary device 610 enters a mode (e.g., sleep mode) in which the display 612 is inactive (e.g., turned off or not currently displaying any content). In some embodiments, the display 612 becomes inactive if no input or alert (e.g., an email, text message, phone call, etc.) is received or detected over a predetermined period of time.

[0177] While the display 612 is inactive, the primary device 610 receives a user input 651 (e.g., a touch input such as a tap). In response to receiving the user input 651, the primary device 610 displays a charge state indication for the primary device 610 and / or a charge state indication for the secondary device 620. In the illustrated embodiment, in response to receiving the user input 651, the primary device 610 determines whether the user input 651 has been detected for a threshold time (e.g., determines whether the user input 651 is a tap and hold). In accordance with the determination that the user input 651 has been detected for a threshold time, the primary device 610 displays a charge state interface 640 that includes a charge state indicator 641 associated with the primary device 610 and a charge state indicator 642 associated with the secondary device 620. FIGS. 6N - 6P show an exemplary transition from the inactive display 612 to the charge state interface 640 in which the charge state indicators 641 and 642 gradually appear on the interface 640 in response to the user input 651. In some embodiments, the primary device 610 displays a charge state indicator 644 and / or blinks a battery icon 644-2 in response to the user input 651. Thus, the primary device 610 enables the user to "check" the state of the devices being charged on the charging device 600. In some embodiments, the primary device 610 periodically provides charge state information by lighting the display 612 at regular intervals to indicate charge information (e.g., the display is activated at predetermined time intervals to display the charge state interface 640).

[0178] When the user input 651 is removed from the display 612, the primary device 610 stops displaying the charge state interface 640 (e.g., the display 612 returns to an inactive state). Alternatively, in accordance with the determination that the user input 651 has not been detected for a threshold time, the primary device 610 defers displaying the charge state interface 640.

[0179] Next, referring to FIG. 6Q, the primary device 610 and the secondary device 620 are being charged on the charging device 600, and the primary device 610 is displaying a charging interface 640. While the primary device 610 and the secondary device 620 are being charged on the charging device 600 and the primary device 610 is displaying the charging interface 640, as shown in FIG. 6R, a third device 630A (e.g., a tablet computer) is added to the charging device 600 and enters a wireless charging state.

[0180] In response to the third device 630A entering the wireless charging state, a determination is made (e.g., by the primary device 610, the third device 630A, and / or the charging device 600) as to whether the third device 630A is a preferred device (e.g., a new primary device or a protagonist device). In the illustrated embodiment, whether the third device 630A is a preferred device is based on the display size of the third device 630A (e.g., the display size of the third device 630A relative to the display size of the primary device 610). Since the third device 630A has a larger display than the primary device 610 and the secondary device 620, the third device 630A is a preferred device. Accordingly, the charging state interface 640 stops being displayed on the primary device 610 and is instead displayed on the preferred device, the third device 630A.

[0181] As shown in FIG. 6R, the charging state interface 640 on the third device 630A includes a charging state indicator 643 for the third device 630A. Since the third device 630A is a preferred device, the charging state indicator 643 is displayed above the charging state indicators 641 and 642 for the primary and secondary devices 610 and 620.

[0182] In some embodiments, the primary device 610 detects that the third device 630A has entered a wireless charging state and determines the display size of the third device 630A (e.g., the primary device 610 receives display size information from the third device 630A or accesses information regarding the display size of the third device 630A in another manner). In accordance with a determination that the display size of the third device 630A is larger than the display size of the primary device 610, the primary device 610 determines that the third device 630A is a preferred device and transmits the charging level of the primary device 610 to the third device 630A (e.g., for display on the third device 630A). In some embodiments, transmitting the charging level to the third device 630A includes transmitting the charging state directly (e.g., via the charging device 600 or Bluetooth® communication) or indirectly (e.g., via an external network or server such as via iCloud®).

[0183] In some embodiments, the preferred device is determined based on a predetermined hierarchy of devices. For example, the primary device 610 can maintain a list indicating the hierarchy of devices (from most preferred to least preferred): the third device 630A, the primary device 610, and the secondary device 620. Therefore, determining whether a device is a preferred device includes determining whether the device is higher in the hierarchy - in this example, the third device 630 is a preferred device relative to the primary device 610.

[0184] Next, referring to FIG. 6S, an alternative embodiment is shown where a different third device (e.g., third device 630B) is added to charging device 600 in place of the third device 630A described above. In response to detecting that the third device 630B has entered a wireless charging state, the primary device 610 determines that the third device 630B is not a preferred device (e.g., the display size of the third device 630B is not larger than the display size of the primary device 610), and displays an indication of the charging state (e.g., charging state indicator 643) for the third device 630B on display 612. In some embodiments, displaying an indication of the charging state for the third device 630B includes displaying charging state indicator 644 and / or pulsating a battery icon (e.g., 644-2).

[0185] While devices 600, 610, 620, and 630B are configured as shown in FIG. 6S, secondary device 620 is removed from charging device 600. The primary device 610 detects that the secondary device 620 has exited the wireless charging state (e.g., by receiving data from the secondary device 620), and in response, displays an indication that the secondary device 620 is no longer being charged. In some embodiments, the primary device 610 blinks the battery icon within charging state indicator 644. In the embodiments shown in FIGS. 6T - 6V, the primary device 610 removes the charging state indicator 642 for the secondary device 620 and continues to display charging state indicator 641 and charging state indicator 643, indicating that the primary device 610 and the third device 630 are still charging. FIGS. 6T - 6U show an exemplary animation for removing the charging state indicator 642 that provides a visual effect of highlighting (e.g., blinking) the charging state indicator 642 (FIG. 6T) and then the charging state indicator 642 disappearing (FIG. 6U).

[0186] Next, transitioning from the configuration shown in FIG. 6V, the primary device 610 is removed from the charging device 600. In response to being removed from the charging device 600, the primary device 610 exits the wireless charging state and ceases to display the charging state interface 640 as shown in FIG. 6W. Additionally, the primary device 610 displays the interface 660 of the active application (e.g., the interface for the inbox of the email application) in response to (e.g., user selection of the email application icon). In FIG. 6X, while the primary device 610 is displaying the interface 660, it is repositioned onto the charging device 600, and in response, while also displaying the interface 660 of the active application, it provides an indication of the charging state (e.g., by displaying, enlarging, and / or pulsing the charging state indicator 644 and / or the battery icon 644-2). In this way, the primary device 610 provides an indication of the charging state (e.g., that the primary device 610 has entered the wireless charging state) while minimizing interference with the interface 660 of the active application (e.g., without displaying the charging state indicator 641 over the interface 660 of the active application). In some embodiments, the primary device 610 then ceases to display the charging state indicator 644 but maintains the display of the battery icon 644-2 as shown in FIG. 6Y. In some embodiments, in response to the secondary device 620 being placed on the charging device 600 while an active application is being displayed, the primary device 610 also displays the interface 660 of the active application while displaying an indication of the charging state of the secondary device 620 (e.g., the charging state indicator 644 instead of the charging state indicator 642).

[0187] Next, in FIG. 6Z, the primary device 610 detects an input 652 on the battery icon 644-2. In response, the primary device 610 displays a charge status indicator 641 and a charge status indicator 643 corresponding to the primary device 610 and the third device 630B, respectively. As shown in the embodiment shown in FIG. 6AA, the charge status indicator 641 and the charge status indicator 643 are visually superimposed on the interface 660 of the active application. In some embodiments, the primary device 610, in response to being placed in the charging device 600 together with the third device 630B, (instead of displaying the charge status indicator 644 as described with reference to FIG. 6X, for example) displays the charge status indicator 641 and the charge status indicator 643 directly superimposed on the interface 660 of the active application.

[0188] Next, referring to FIGS. 6AB - 6AG, some embodiments of the multi-device charge status interface and charge status indicators are described. In FIG. 6AB, the primary device 610 indicates the physical position of the devices on the charging device 600 by displaying visual representations of the devices (e.g., charge status indicators 641A, 642A, and 643A) positioned relative to a visual representation of the charging device (e.g., 646). The positioning of the visual representations reflects the actual physical positioning of the devices on the charging device 600. The indication of the physical position includes identifying information about the devices (D1, D2, D3). Therefore, the user can look at the display 612 of the primary device 610 and recognize the identification and positioning of each device currently being wirelessly charged. In addition, the charge status indicators 641A, 642A, and 643A indicate the charge level of the corresponding devices using rings filled in proportion to the percentage charge. FIG. 6AC shows an embodiment of the multi-device charge status interface when four devices are being charged by the charging device 600.

[0189] In FIG. 6AD, the charge status indicator 647 includes a lightning icon and a ring that is filled in proportion to the percentage charge. The charge status indicator 648 in FIG. 6AE includes text indicating the percentage charge and a ring that is filled in proportion to the percentage charge. The charge status indicators 649 in FIGS. 6AF - 6AG include a ring that is filled in proportion to the percentage charge and an animated ripple effect (e.g., a wavy effect), and the size of the animated ripple effect is proportional to the percentage charge. In FIG. 6AF, the device is only partially charged, as indicated by the ring being partially filled and a relatively small ripple effect partially surrounding the ring. In contrast, in FIG. 6AG, the device is fully charged, as indicated by the ring being fully filled and a relatively large ripple effect fully surrounding the ring.

[0190] FIGS. 7A - 7E are flowcharts showing methods for charging an electronic device according to some embodiments. Method 700 is executed on a first device (e.g., 100, 300, 500, or 610) having a display (e.g., 612). Optionally, the first device includes a touch - sensitive surface (e.g., a touch - sensitive display). Some operations in method 700 may optionally be combined, the order of some operations may optionally be changed, and some operations may optionally be omitted.

[0191] As described below, method 700 provides an intuitive way (e.g., for determining the charge level of one or more devices) to charge an electronic device. This method reduces the user's cognitive burden for charging an electronic device, thereby creating a more efficient human - machine interface. In the case of battery - operated computing devices, it improves the user experience, saves power, and increases the battery charging interval by enabling the user to charge the electronic device faster and more efficiently.

[0192] In block 702, the first device detects that at least one of the first device (e.g., 610) or the second device (e.g., 620) has entered a wireless charging state. In some embodiments, in response to detecting that the first device has entered a wireless charging state, the first device provides a haptic output (e.g., 800). Providing a haptic output in response to detecting that the first device has entered a wireless charging state provides feedback to the user that the first device has successfully started charging, and reduces the number of inputs by providing charging information without the user having to activate or look at the display. By providing improved feedback to the user and reducing the number of inputs required to perform an operation, the usability of the device is enhanced, and the user-device interface becomes more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device). This additionally reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0193] In block 704, in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device (e.g., 600), the first device displays an indication of the charging state (e.g., 642) for the second device on a display. In some embodiments, displaying an indication of the charging state for the second device includes displaying a visual indication (e.g., 642) that at least one of the first device or the second device has entered a wireless charging state. In some embodiments, the first device displays a charging state indicator on the display, and the indication of the charging state for the second device is an animation associated with the charging state indicator (e.g., FIG. 6H). Displaying an indication of the charging state for the second device on the display of the first device enables the charging state to be provided on a more suitable device to provide charging state information, particularly when the second device (e.g., a pair of earphones) does not include a display or has limited means for providing the charging state, thereby providing improved feedback to the user about the charging state of the second device. It also reduces the number of inputs required to obtain the charging state of the second device by reducing or eliminating the need to provide a separate input on the second device to obtain the charging level of the second device. The benefits of providing improved feedback to the user and reducing the number of inputs required to perform an operation are described above.

[0194] Optionally, in block 706, displaying an indication of the charge state for the second device includes displaying a charge state interface (e.g., 640) that includes a first charge state indicator (e.g., 641) associated with the first device and a second charge state indicator (e.g., 642) associated with the second device. Displaying the charge state indicators for both the first device and the second device provides improved feedback by enabling the charge states of multiple devices to be displayed on a single device. Displaying an indication of the charge states of multiple devices on a single display reduces the number of inputs required to obtain the charge state of each device by reducing or eliminating the need to provide separate inputs at each device to obtain the individual charge levels. The benefits of providing improved feedback to the user and reducing the number of inputs required to perform an operation have been described above.

[0195] In some embodiments, displaying the charge state interface includes displaying the first charge state indicator and the second charge state indicator on the display in an ordered array (e.g., vertically). In some embodiments, the ordered array is a predetermined array based on the type of device associated with each corresponding charge state indicator. In some embodiments, the ordered array is at least partially based on the order in which each corresponding device entered a wireless charging state. Ordering the array based on the order in which each corresponding device entered a wireless charging state improves feedback to the user by placing the most important information (e.g., the charge level of the most recently charged device) in a more prominent position. The benefits of providing improved visual feedback to the user have been described above.

[0196] In some embodiments, displaying a charging state interface includes displaying on a display a first charging state indicator (e.g., 641-1A or 641-1B) that includes a charging level for a first device, and an indication that the first device is currently charging (e.g., 641-1C). In some embodiments, displaying a charging state interface includes displaying on a display a second charging state indicator that includes a charging level for a second device, and an indication that the second device is currently charging. In some embodiments, displaying a charging level for a device includes displaying one or more of a text indication of the charging level (e.g., 644-1), a graphical indication of the charging level (e.g., 644-2), an animation representing the charging level (e.g., 649), and a color-based indication representing the charging level.

[0197] Optionally, in block 708, the first device displays on the display an animation of the charging state interface transitioning to an icon (e.g., 644-2), and then the charging state interface ceases to be displayed (e.g., FIGS. 6I-6K). Optionally, in block 710, after the charging state interface ceases to be displayed, the first device receives a user input selection of an icon (e.g., 650). Optionally, in block 712, in response to receiving the user input selection of the icon, the first device displays the charging state interface on the display (e.g., FIGS. 6K-6M). Ceasing to display the charging state interface and then redisplaying the charging state interface in response to an icon selection allows the user to easily access the charging state information without cluttering the user interface with persistent charging state information that could interfere with other information on the display. By providing additional control options without cluttering the interface with additional displayed controls, the operability of the device is enhanced, and the user-device interface becomes more efficient (e.g., by assisting the user in providing appropriate inputs and reducing user errors when operating / interacting with the device). This additionally allows the user to use the device more quickly and efficiently, thereby reducing power usage and improving the battery life of the device.

[0198] In some embodiments, before detecting that at least one of the first device or the second device has entered a wireless charging state, the first device displays on the display an interface of an active application (e.g., 660), and displaying an indication of the charging state includes simultaneously displaying on the display an indication of the charging state (e.g., 644) and an interface of the active application. Optionally, the indication of the charging state is visually overlaid on the interface of the active application (e.g., FIG. 6AA).

[0199] In some embodiments, the indication of the charging state is a selectable affordance (e.g., 644-2). Optionally, at block 714, the first device receives a user input selection of the indication of the charging state (e.g., 652). Optionally, at block 716, in response to receiving the user input selection of the indication of the charging state, the first device displays on the display a charging state interface that includes a first charging state indicator (e.g., 641) associated with the first device and a second charging state indicator (e.g., 642) associated with the second device.

[0200] Optionally, at block 718, the first device detects that a third device (e.g., 630A or 630B) has entered a wireless charging state. In some embodiments, in response to detecting that the third device has entered a wireless charging state and in accordance with a determination that the first device and the third device are being wirelessly charged by the same wireless charging device, the first device displays on the display an indication of the charging state (e.g., 643) for the third device. Optionally, at block 720, in response to detecting that the third device has entered a wireless charging state, the first device determines whether the third device is a preferred device. In some embodiments, determining whether the third device is a preferred device includes determining whether the third device is a device that includes a display larger than the display of the first device. Optionally, at block 722, in accordance with a determination that the third device is a preferred device, the first device defers displaying an indication of the charging state for the third device (e.g., FIG. 6R) and transmits the charging level of the first device to the third device (e.g., for display on the third device). Optionally, at block 724, in accordance with a determination that the third device is not a preferred device, the first device displays on the display an indication of the charging state for the third device (e.g., FIG. 6S).

[0201] Determining whether the third device is the preferred device (e.g., based on display size) and transmitting the charge level of the first device to the third device enables the charge states of at least these two devices to be provided on a more suitable (e.g., preferred) device (e.g., the third device) for providing charge state information, thereby providing the user with improved feedback regarding the charge states of the first and third devices. It also reduces the number of inputs required to obtain the charge states of both the first device and the third device by reducing or eliminating the need to provide separate inputs at each device to obtain their respective charge levels. The benefits of providing the user with improved feedback and reducing the number of inputs required to perform an operation are described above.

[0202] In some embodiments, after displaying an indication of the charge state for the second device and while the first device and the second device are being wirelessly charged by the same wireless charging device, the first device ceases to display the indication of the charge state for the second device (e.g., FIG. 6N). Optionally, at block 726, while the display is inactive, the first device receives a user input (e.g., 651) associated with the device. In some embodiments, in response to receiving a user input associated with the device, the first device displays an indication of the charge state for the second device on the display (e.g., FIG. 6P). In some embodiments, the indication of the charge state for the second device is a visual indication (e.g., blinking or magnification) associated with a charge state indicator (e.g., 644). In some embodiments, the first device receives a user input selection (e.g., 650) of the charge state indicator. In some embodiments, in response to receiving a user input selection of the charge state indicator, the first device displays on the display a charge state interface (e.g., 640) including a first charge state indicator (e.g., 641) associated with the first device and a second charge state indicator (e.g., 642) associated with the second device.

[0203] Optionally, at block 728, in response to receiving user input associated with the device, the first device determines whether the user input associated with the device has been detected over a threshold time. Optionally, at block 730, in accordance with the determination that the user input associated with the device has been detected over a threshold time, and while the user input associated with the device continues to be detected, the first device displays on the display a charge state interface including a first charge state indicator associated with the first device and a second charge state indicator associated with the second device (e.g., FIG. 6P). Optionally, at block 732, in accordance with the determination that the user input associated with the device has not been detected over a threshold time, the first device defers displaying the charge state interface on the display. Optionally, at block 734, in accordance with the determination that the user input associated with the device has not been detected over a threshold time, the first device stops detecting the user input associated with the device. Optionally, at block 736, in response to stopping detecting the user input associated with the device, the first device stops displaying the charge state interface.

[0204] Optionally, at block 738, the first device detects that the second device has exited the wireless charging state (e.g., FIG. 6T). Optionally, at block 740, in response to detecting that the second device has exited the wireless charging state, and in accordance with the determination that the first device and the second device are no longer being wirelessly charged by the same wireless charging device, the first device displays on the display a second indication of the charge state for the second device (e.g., the highlighting of 642 in FIG. 6T). In some embodiments, displaying the second indication of the charge state for the second device includes displaying a visual indication that the second device has exited the wireless charging state (e.g., the removal of 642 in FIGS. 6U - 6V).

[0205] Optionally, in block 742, in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, the first device determines whether the first device is in a low interference condition. Optionally, in block 744, in accordance with a determination that the first device is in a low interference condition, the first device displays on a display a low interference indication of the charging state for the second device (e.g., a moving red color and / or 642 or 644 having a lower light output). Optionally, in block 746, in accordance with a determination that the first device is not in a low interference condition, the first device displays on a display an indication of the charging state for the second device (e.g., 642).

[0206] In some embodiments, the first device and the second device are included within a set of devices that are associated with each other. In some embodiments, the set of devices that are associated with each other includes one or more of a device paired with at least one other device within the set, and a device associated with the same user account. Optionally, at block 748, the first device detects that the fourth device has entered a wireless charging state. Optionally, at block 750, the first device determines whether the fourth device is included within the set of devices that are associated with each other. Optionally, in response to detecting that the fourth device has entered a wireless charging state, in accordance with a determination that the first device and the fourth device are being wirelessly charged by the same wireless charging device, and in accordance with a determination that the fourth device is included within the set of devices that are associated with each other, at block 752, the first device displays an indication of the charging state (e.g., 642, 643, or 644) for the fourth device on a display. Optionally, in response to detecting that the fourth device has entered a wireless charging state, in accordance with a determination that the first device and the fourth device are being wirelessly charged by the same wireless charging device, and in accordance with a determination that the fourth device is not included within the set of devices that are associated with each other, at block 754, the first device refrains from displaying an indication of the charging state for the fourth device on a display.

[0207] In some embodiments, while the first device and the second device are being wirelessly charged by the same wireless charging device, the first device displays an indication of the charging state for the second device on a display at predetermined time intervals.

[0208] In some embodiments, the first device and the second device are connected via a communication link. In some embodiments, the first device receives, from the second device via the communication link, data representing the charging state of the second device.

[0209] In some embodiments, further, in response to detecting that at least one of the first device or the second device has entered a wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, the first device displays, on a display, an indication of the physical position of the second device on the wireless charging device (e.g., 642A in FIGS. 6AB).

[0210] Note that the details of the processes described above with respect to method 700 (e.g., FIGS. 7A - 7E) should also be noted as being applicable in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, the display of an indication of the charging state for the second device as described above with reference to block 704 of method 700 can be provided in addition to the non - visual indication(s) described in method 900. Similarly, the non - visual indication(s) described in method 900 can be provided in addition to the display of an indication of the charging state for the second device as described above with reference to block 704 of method 700. For the sake of brevity, these details will not be repeated below.

[0211] Next, with reference to FIGS. 8A-8E, techniques and non-visual interfaces for communicating the charge level of an electronic device are described. FIG. 8A shows the charging device 600 and the primary device 610 described above with reference to FIGS. 6A-6AG. The primary device 610 is charging on the device 610 and displays a charge status indicator 644 indicating that the primary device 610 has a first charge level of 50%. While charging at the first charge level on the charging device 600, the primary device 610 receives a user input 850 (e.g., a tap on the display 612) that represents a request for the charge level (e.g., the charge level of the primary device 610). In response to receiving the user input 850, the primary device 610 outputs a first non-visual indication 800 (e.g., an audible sound and / or a tactile vibration) of the first charge level of the primary device 610. The type (e.g., audible or tactile) or characteristics (e.g., amplitude, frequency, duration, modulation pattern) of the first non-visual indication 800 are represented by the number of curves (e.g., two curves) adjacent to each corner of the primary device 610. In some embodiments, the first non-visual indication 800 is output in response to a transition in the wireless charging state of the primary device 610 (e.g., placing the primary device 610 on the charging device 600 or removing the primary device 610 from the charging device 600).

[0212] FIG. 8B shows the primary device 610 charging at a second charge level of 100% on the charging device 600 (e.g., after the device has been charging for some length of time since user input 850). While the primary device 610 is charging at the second charge level on the charging device 600, the primary device 610 receives a user input 851 (e.g., a tap on the display 612) that represents another request for a charge level. In response to receiving the user input 851, the primary device 610 outputs a second non-visual indication 802 (e.g., an audible sound and / or a tactile vibration) of the second charge level of the primary device 610. The type or characteristic of the second non-visual indication 802 is again represented by the number of curves adjacent to each corner of the primary device 610 (e.g., four curves). In some embodiments, the second non-visual indication 802 is output in response to a transition in the wireless charging state of the primary device 610 (e.g., placing the primary device 610 on the charging device 600 or removing the primary device 610 from the charging device 600).

[0213] As shown in FIGS. 8A-8B, since the second charge level (100%) is different from the first charge level (50%), the second non-visual indication 802 is different from the first non-visual indication 800 (e.g., includes a different type of indication or different characteristics). In some embodiments, the second non-visual indication 802 and the first non-visual indication 800 include the same type of indication (e.g., both include a tactile output or both include an audio output) but differ with respect to one or more characteristics (e.g., they have different amplitudes, frequencies, durations, and / or modulation patterns). In some embodiments, the second non-visual indication 802 and the first non-visual indication 800 include different types of indications.

[0214] Although user inputs 850 and 851 have been described above as taps on display 612, in some embodiments, the request for a charge level includes placing a hand on the display 612 and holding it, a tap-and-hold on the display 612, or a user input voice command (e.g., "Hey, Siri, what's the charge level of my device?"). In some embodiments, before outputting a non-visual indication, the primary device 610 determines whether the user input includes a touch input that has been continuously detected over a threshold time duration, and then outputs an indication in accordance with the determination that the touch input has been continuously detected over the threshold time duration. In some embodiments, the primary device 610 responds to a request for the charge level of the primary device 610 when not charging on the charging device 600.

[0215] In some embodiments, the non-visual indication includes a haptic output that represents the current charge level of the primary device 610. Optionally, one or more output characteristics of the haptic output depend on the charge level of the primary device 610. Exemplary output characteristics of the haptic output include the duration of the haptic output, the number of discrete haptic pulses of the haptic output, and the frequency between the discrete haptic pulses of the haptic output. In some embodiments, the haptic length indicates (e.g., is directly proportional to) the level of charge. In an example applicable to the charge levels described in FIGS. 8A-8B, since the second charge level is greater than the first charge level, the first non-visual indication 800 includes a first haptic output over a first duration, and the second non-visual indication 802 includes a second haptic output over a second duration that is longer than the first duration. In some embodiments, the primary device 610 provides a series of decaying haptic taps for indicating a relatively low charge level and a series of haptic buzzes with an increasing frequency for indicating a relatively higher charge level. In an example applicable to the charge levels described in FIGS. 8A-8B, the first non-visual indication 800 includes a first plurality of discrete haptic pulses given a decaying frequency between the pulses, and the second non-visual indication 802 includes a second plurality of discrete haptic pulses given an increasing frequency between the pulses.

[0216] In some embodiments, the non-visual indication includes an audible output that represents the current charge level of the primary device 610. Optionally, one or more output characteristics of the audible output depend on the charge level of the primary device 610. Exemplary output characteristics of the audible output include the duration of the audible output, the number of discrete audible signals of the audible output, the volume of the audible output, the modulation pattern, and the frequency of the audible output. In some embodiments, the primary device 610 provides a short audible tone to indicate a relatively low charge level and a longer audible tone to indicate a relatively higher charge level (e.g., the length of the tone is proportional to the charge or the discrete lengths of multiple tones are based on charge level threshold(s)). In one example applicable to the charge levels described in FIGS. 8A-8B, the first non-visual indication 800 includes a first audible output having a first duration, and the second non-visual indication 802 includes a second audible output having a second duration that is longer than the first duration. In some embodiments, the frequency of the audible tone indicates the charge level (e.g., the frequency of the tone is directly proportional to the charge level). In one example applicable to the charge levels described in FIGS. 8A-8B, the first non-visual indication 800 includes an audio signal having a first characteristic frequency, and the second non-visual indication 802 includes an audio signal having a second characteristic frequency that is higher than the first characteristic frequency.

[0217] Referring now to FIG. 8C, while the primary device 610 is charging on the charging device 600, the secondary device 620 is placed on the charging device 600. The secondary device 620 has a charge level of 75%. The primary device 610 receives a user input 852 (e.g., a tap on the display 612) that represents a request for the charge level of the secondary device 620. In some embodiments, the user input 852 includes placing and holding a hand on the display 612, a tap-and-hold on the display 612, or a user input voice command (e.g., "Hey Siri, how's my Apple Watch charging?").

[0218] In response to receiving the user input 852, the primary device 610 outputs a non-visual indication 804 of the charge level of the secondary device 620. In some embodiments, one or more of the techniques, features, and / or characteristics described above with respect to the first and second non-visual indications 800 and 802 are applied to the non-visual indication 804 to represent the charge level of the secondary device 620. In some embodiments, in response to a transition in the wireless charging state of the secondary device 620 (e.g., placing the secondary device 620 on the charging device 600 or removing the secondary device 620 from the charging device 600), a non-visual indication 804 of the charge level of the secondary device 620 is output.

[0219] Next, with reference to FIGS. 8D - 8E, techniques for providing a low charge warning are described. FIG. 8D shows a primary device 610 that is charging on the charging device 600 and displaying a calendar application. The primary device 610 indicates the time of 9:55, and the calendar application indicates that there is a meeting scheduled between 10:00 AM and 11:00 AM. The charge status indicator 644 indicates that the primary device 610 has a charge level of 15%.

[0220] As shown in FIG. 8E, in response to being removed from the charging device 600 (e.g., the primary device 610 transitioning from a wireless charging state to a state where the primary device 610 is not wirelessly charging), the primary device 610 estimates whether the current charge level of the primary device 610 (15%) is sufficient to provide battery charging to the primary device 610 over a period of time before the charge level of the primary device 610 reaches a depleted charge level (e.g., 0%, 5%, 10%, etc.). In the illustrated example, the primary device 610 determines the period based on calendar data associated with the primary device 610 (e.g., a calendar application, events on the user's calendar linked to the primary device 610, or data from the user account logged in on the primary device 610). Thus, the primary device 610 estimates whether 15% charge of the primary device 610 is sufficient to provide battery charging to the primary device 610 through the meetings on the calendar (e.g., over 1 hour and 5 minutes) before the charge level reaches the depleted charge level.

[0221] In accordance with the estimation that the charge level is sufficient, the primary device 610 outputs a non-visual indication of the charge level of the primary device 610 according to one of the techniques described above (e.g., normal audible or tactile output). In accordance with the estimation that the current charge level is not sufficient, the primary device 610 outputs a non-visual indication 806 (e.g., an audible or tactile low charge alert) representing the low charge level of the primary device 610. In one example, the non-visual indication 806 includes an audible voice output such as "You may want to charge your phone if you want to make it through the next meeting." In some embodiments, (e.g., even if the current charge is 50% and the charge of the primary device 610 is not expected to make it through the user's meetings for the day,) the primary device 610 sends a low charge alert regardless of the current charge level.

[0222] Figures 9A-9B are flow diagrams showing a method for charging an electronic device, according to some embodiments. Method 900 is executed on a device (e.g., 100, 300, 500, or 610) that includes a display. Optionally, the device includes a touch-sensing surface (e.g., a touch-sensing display). Some operations in method 900 may optionally be combined, the order of some operations may optionally be changed, and some operations may optionally be omitted.

[0223] As described below, method 900 provides an intuitive way to charge an electronic device. This method reduces the user's cognitive burden for charging the electronic device, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, the user experience is improved, power is conserved, and the battery charging interval is increased by enabling the user to charge the electronic device faster and more efficiently.

[0224] In block 902, while the device is wirelessly charging and at a first charge level, the device receives a first user input (e.g., 850) that represents a request for a charge level.

[0225] In block 904, in response to receiving a first user input, the device outputs a first non-visual indication (e.g., 800) of a first charge level of the device. Outputting a non-visual indication of the first charge level of the device provides the user with feedback on the charging status of the device and the charge level, reducing the number of inputs required by the user to view or activate the display or select another interface object. The benefits of providing improved feedback to the user and reducing the number of inputs required to perform an operation have been described above. Outputting a non-visual indication also improves the operability of the device by enabling the charge level of the device to be conveyed in a subtle or unobtrusive manner (e.g., without activating the display and illuminating the surrounding environment at night). The benefits of improving the operability of the device are similar to those described above for providing improved feedback to the user and reducing the number of inputs required to perform an operation.

[0226] In block 906, while the device is wirelessly charging and at a second charge level different from the first charge level, the device receives a second user input (e.g., 851) that represents a request for a charge level.

[0227] In block 908, in response to receiving a second user input, the device outputs a second non-visual indication (e.g., 802) of a second charge level of the device. The second non-visual indication is different from the first non-visual indication. Again, outputting a non-visual indication of the charge level of the device enables the device to provide the user with information that the device is charging and unobtrusive feedback about the charge level of the device, reducing the number of inputs by providing charge information without the user having to look at or activate a display or select another interface object. Additionally, outputting a second non-visual indication different from the first non-visual indication provides the user with improved feedback by communicating information about the charge level of the device not only by the second output itself but also by the difference between the first output and the second output. The difference in the outputs can indicate a change in the charge level between the first charge level and the second charge level. The benefits of these effects have been described above.

[0228] In some embodiments, one or more of the first user input and the second user input is a transition in the wireless charging state of the device. In some embodiments, the transition in the wireless charging state is a transition from a state where the device is not wirelessly charging to a state where the device is wirelessly charging on a wireless charging device. In some embodiments, the transition in the wireless charging state is a transition from a state where the device is wirelessly charging on a wireless charging device to a state where the device is not wirelessly charging.

[0229] In some embodiments, one or more of the first user input and the second user input is a user input voice command.

[0230] In some embodiments, one or more of the first user input and the second user input is a touch input on a touch-sensitive surface (e.g., 612) of the device. In some embodiments, in accordance with a determination that a touch input has been continuously detected over a threshold time duration, the device outputs a non-visual indication (e.g., 800) of the charge level of the device.

[0231] In some embodiments, outputting a non-visual indication of the charging level of a device includes providing a haptic output representative of the charging level of the device, the haptic output having output characteristics that depend on the charging level of the device. In some embodiments, the output characteristics are one or more of a duration of the haptic output, a number of discrete haptic pulses of the haptic output, and a frequency between the discrete haptic pulses of the haptic output. In some embodiments, in response to a first user input, the device provides a first haptic output representative of a first charging level, the first haptic output being provided over a first duration, and in response to a second user input, the device provides a second haptic output representative of a second charging level, the second haptic output being provided over a second duration, the second user input being received after the first user input, and the second duration being longer than the first duration.

[0232] In some embodiments, in response to a first user input, the device provides a third haptic output representative of a first charging level, the third haptic output including a first plurality of discrete haptic pulses provided with a decreasing frequency between the pulses, and in response to a second user input, the device provides a fourth haptic output representative of a second charging level, the fourth haptic output including a second plurality of discrete haptic pulses provided with an increasing frequency between the pulses, the second user input being received after the first user input.

[0233] In some embodiments, outputting a non-visual indication of the charging level of a device includes providing an audible output representative of the charging level of the device, the audible output having output characteristics that depend on the charging level of the device. In some embodiments, the output characteristics are one or more of a duration of the audible output, a number of discrete audible signals of the audible output, a volume of the audible output, a modulation pattern, and a frequency of the audible output.

[0234] In some embodiments, in response to a first user input, a first audible output representing a first charge level is provided, the first audible output being provided over a first duration of time. In response to a second user input, the device provides a second audible output representing a second charge level, the second audible output being provided over a second duration of time. The second user input is received after the first user input, and the second duration of time is longer than the first duration of time. In some embodiments, in response to a first user input, the device provides a third audible output representing a first charge level, the third audible output including an audio signal having a first characteristic frequency. In response to a second user input, the device provides a fourth audible output representing a second charge level, the fourth audible output including an audio signal having a second characteristic frequency. The second user input is received after the first user input, and the second characteristic frequency is higher than the first characteristic frequency.

[0235] Optionally, at block 910, while the device is wirelessly charging, the device receives a third user input (e.g., 852) that represents a request for the charge level of a second device (e.g., 620). The second device is wirelessly charging at a third charge level. Optionally, at block 912, in response to receiving the third user input, the device outputs a third non-visual indication (e.g., 804) of the third charge level of the second device. In some embodiments, the second device is wirelessly charging on the same wireless charging device (e.g., 600) as the first device. In some embodiments, the third user input is a transition in the wireless charging state of the second device. Outputting a non-visual indication of the charge level of the second device on the first device enables the charge state to be provided on a device that is more suitable for providing charge state information, particularly when the second device does not include means for providing a non-visual (e.g., unobtrusive) output or has limited means for providing the charge state, thereby providing improved feedback to the user about the charge state of the second device. It also reduces the number of inputs required to obtain the charge state of the second device by reducing or eliminating the need for a separate input in the second device to obtain the charge level of the second device. The benefits of providing improved feedback to the user and reducing the number of inputs required to perform an operation are described above.

[0236] Optionally, in block 914, while the device is wirelessly charging and at a fourth charge level, the device receives a fourth user input that represents a transition of the device's wireless charging state from a state where the device is wirelessly charging on a wireless charging device to a state where the device is not wirelessly charging. Optionally, in block 916, in response to receiving the fourth user input, the device estimates whether the fourth charge level is sufficient to provide battery charging to the device over a period of time before the device's charge level reaches the depleted charge level. Optionally, in block 918, in accordance with an estimation that the fourth charge level is not sufficient, the device outputs a fourth non-visual indication (e.g., 806) of the fourth charge level of the device. Optionally, in block 920, in accordance with an estimation that the fourth charge level is sufficient, the device outputs a fifth non-visual indication of the fourth charge level of the device, and the fourth non-visual indication is different from the fifth non-visual indication. Providing a different output when the device's charge level is considered insufficient to sustain over a period of time compared to the output when it is determined that the device's charge level is sufficient helps to provide improved feedback to the user by warning the user that the device's charge is being stopped despite the relatively low charge of the device, and helps to prevent the device from unexpectedly running out of charge. The alert gives the user an opportunity to take measures (e.g., by setting the device to a low power mode to extend battery life or by charging the device in another location) to ensure that the device does not run out of charge. The benefit of providing improved user feedback is explained above.

[0237] In some embodiments, determining whether a fourth charge level is sufficient to provide battery charging to a device over a period of time before the device's charge level reaches a depleted charge level includes determining the period based on calendar data associated with the device, and determining whether the fourth charge level is sufficient to provide battery charging to the device until the end of the period before the device's charge level reaches a depleted charge level. In some embodiments, a fourth non-visual indication of the fourth charge level of the device is an audible or tactile output that indicates a low charge level of the device. In some embodiments, a fourth non-visual indication of the fourth charge level of the device is an audible voice output that indicates a low charge level of the device.

[0238] Note that the details of the processes described above with respect to method 900 (e.g., FIGS. 9A-9B) are also applicable in a similar manner to other methods (FIGS. 7A-7E) described above with respect to method 700. For example, method 700 optionally includes one or more of the various method characteristics described above with reference to method 900.

[0239] The embodiments described herein explain techniques for synchronizing information among one or more devices on a wireless charging device (also referred to as a "wireless charger"). According to some embodiments, a wireless charger can be configured to receive information from each computing device disposed on the wireless charger. This information can include, for example, a unique identifier (ID) associated with the computing device, one or more unique IDs of other computing devices known to the computing device (e.g., previously / actively paired computing devices, a set of devices associated with each other or with a common user account), and the battery state (also referred to as the "charge state") of the computing device. Thus, when a new computing device is placed on the wireless charger, the wireless charger can refer to the unique ID for identification when at least two related computing devices are present. For example, when the wireless charger determines that a first computing device and a second computing device are (1) disposed on the wireless charger (e.g., being wirelessly charged by the wireless charger, which is also referred to as each device being in a "wireless charging state") and (2) related to each other, the wireless charger can cause the first computing device to display information about the second computing device instead of and / or in addition to the information displayed by the second computing device.

[0240] For example, consider a scenario where the first computing device is a smartphone device and the second computing device is a smaller device related to the smartphone device (e.g., a smartwatch device paired with the smartphone). In this scenario, when the smartwatch device is placed on the wireless charging device (with the smartphone device already present), the wireless charging device can (1) identify the relationship between the devices and (2) notify the smartphone device of the presence / battery state of the smartwatch device. As a result, the smartphone device can generate a notification associated with the battery state of the smartwatch device, for example, through one or more animations / sounds that provide a pleasant user experience. As described above, the smartwatch device can also be configured to generate a notification (e.g., a complementary notification) that is coordinated with the notification generated by the smartphone device. Specifically, the smartphone device can be configured to instruct the wireless charging device of a time delay that will be fulfilled by the smartphone device before generating a notification associated with the battery state of the smartwatch device. As a result, the wireless charging device provides the time delay to the smartwatch device. In this way, the smartwatch device can display a notification that includes one or more animations / sounds that complement the animations / sounds included in the notification generated by the smartphone device, in accordance with the time delay.

[0241] Additionally, it should be noted that smartphone devices and smartwatch devices can periodically / responsively issue relevant updates to the wireless charging device while they remain connected to the wireless charging device. For example, a smartphone device can instruct the wireless charging device whether it is appropriate for the smartphone device to display notifications associated with the smartwatch device. The appropriateness can be based on, for example, whether the smartphone device is locked / unlocked, in use / not in use, etc. For example, when the smartphone device is in an unlocked state / in use, the smartphone device can refuse to display any notifications associated with the smartwatch device. In some examples, the smartphone device can display a notification of the battery status of the smartwatch device (e.g., a pop-up or other visual indication) to continue providing information to the user. Additionally, each of the smartphone device and the smartwatch device can provide battery status updates to the wireless charging device to enable various useful features to be implemented as they are charged. This can, for example, enable the smartphone device to display the latest battery status of the smartwatch device when the smartwatch device is removed from the wireless charging surface, thereby improving the user experience.

[0242] A more detailed consideration of these techniques is described below and explained in conjunction with FIGS. 10 and 11A - 11D. These figures show detailed diagrams of systems and methods that can be used to implement these techniques.

[0243] FIG. 10 shows a block diagram 1000 of different computing devices that can be configured to implement various aspects of the techniques described herein, according to some embodiments. Specifically, FIG. 10 shows a high-level overview of a wireless charging device 1002 configured to communicate with and provide electrical charge to different computing devices 1020. Although not shown in FIG. 10, it is understood that the wireless charging device 1002 (also referred to as device 1002) and the computing devices 1020 can each include at least one processor, at least one memory, and at least one storage device that collectively enable these devices to operate in accordance with the present disclosure. For example, in a given device, instructions can be stored in at least one storage device and loaded into at least one memory for execution by at least one processor to enable the techniques described herein to be implemented. In some embodiments, each of devices 1002 and 1020 includes one or more features of device 100, 300, or 500. In some embodiments, device 600 includes one or more features of device 100, 300, 500, or 1002.

[0244] As shown in FIG. 10, the wireless charging device 1002 can include a power supply mechanism 1004, one or more indicators 1006, a memory (not shown in FIG. 10) for storing device information 1010, one or more communication components 1008, and at least one wireless charging surface 1012. According to some embodiments, the wireless charging surface 1012 enables one or more computing devices 1020 to receive charging when disposed in proximity to the wireless charging surface 1012 (e.g., directly on the wireless charging surface 1012 or otherwise within the functional range of the wireless charging technology of the wireless charging surface 1012). For example, the wireless charging surface 1012 can implement any form of wireless (e.g., inductive) charging technology. For example, the wireless charging surface 1012 can implement Qi wireless charging technology, Power Matters Alliance (PMA) technology, or any other form of wireless charging technology. However, note that the wireless charging technique is not essential for implementing the techniques described herein. In some embodiments, the wireless charging surface 1012 can be replaced or supplemented by any component (e.g., a conductor-based charging component) that enables the computing device 1020 to receive charging and communicate with the wireless charging device 1002.

[0245] According to some embodiments, the indicator 1006 included within the wireless charging device 1002 can include, for example, a light emitting diode (LED) that indicates various information to the end user of the wireless charging device 1002. For example, the LED can indicate whether the power supply mechanism 1004 is receiving power from a power source, whether at least one computing device 1020 is properly connected to the wireless charging surface 1012 and being charged there through, and so on. According to some embodiments, the communication component 1008 can enable the wireless charging device 1002 to transmit information to and receive information from the computing device 1020 (e.g., via Bluetooth®, Near Field Communication (NFC), WiFi, or any suitable communication technology). According to some embodiments, the computing devices 1020 communicate directly. For example, when the computing devices 1020-1 and 1020-2 are paired by Bluetooth®, they can directly exchange information regarding battery status via their Bluetooth® communication link. According to some embodiments, the information described above can be transmitted between the wireless charging device 1002 and the computing device 1020 using "in-band" communication that is consistent with any wireless charging technology implemented by the wireless charging device 1002. For example, data signals can be transmitted through the wireless charging technology medium (e.g., one or more communication signal pulses are transmitted through an induction coil). Thus, existing relationships - such as Bluetooth® pairing, NFC pairing, WiFi pairing, or the like - are not required for the wireless charging device 1002 to effectively communicate with the computing device 1020.Furthermore, implementing in-band communication can enable the wireless charging device 1002 to communicate with a given computing device 1020 even when the computing device 1020 is operating in a minimal mode where the primary communication components (e.g., cellular, Bluetooth®, NFC, WiFi, etc.) within the computing device 1020 are disabled - for example, in-flight mode.

[0246] Note that the internal components of the wireless charging device 1002 shown in FIG. 10 and described herein do not represent an exhaustive list of what may be included within the wireless charging device 1002. In some embodiments, the wireless charging device 1002 can include any number of components that contribute to or supplement the embodiments described herein. In some examples, the wireless charging device 1002 can include a display device / speaker that can be used to inform an end user of information associated with the wireless charging device 1002 and / or the computing device 1020. In some examples, the wireless charging device 1002 can include any form of input device, such as a touch screen, a biometric sensor, buttons, a dial, a slider, etc., to enable interaction with the wireless charging device 1002. In some examples, the wireless charging device 1002 can include any communication component (e.g., providing communication capabilities via technologies such as cellular, Bluetooth®, NFC, WiFi, or the like) to enable the wireless charging device 1002 to communicate with the computing device 1020.

[0247] According to some embodiments, the device information 1010 can be used by the wireless charging device 1002 to manage the flow of information between computing devices 1020 according to the techniques described herein. For example, when a computing device 1020 is placed on the wireless charging device 1002, the computing device 1020 can transmit one or more packets 1028 containing related information to enable the techniques described herein to be effectively implemented, via, for example, in-band communication techniques or other communication techniques described herein. For example, as shown in FIG. 10, the packet 1028 transmitted by the computing device 1020 can include a unique identifier (ID) 1022 for the computing device 1020, one or more known unique IDs 1022 of other computing devices 1020 known to the computing device 1020, and other information 1026 associated with the computing device 1020, the purpose of which will be described in more detail below.

[0248] According to some embodiments, the unique ID 1022 can take any form that enables the computing device 1020 to be uniquely identifiable. For example, the unique ID 1022 can be based on hardware / software properties (e.g., identifiers) associated with the computing device 1020. However, in some cases, especially for privacy protection, it may be desirable to separate the unique ID 1022 from the properties of the computing device 1020. For example, the unique ID 1022 can be a randomly generated string that has no relation to the hardware / software properties of the computing device 1020. In this way, nearby malicious devices attempting to probe the information transmitted between the computing device 1020 and the wireless charging device 1002 can only collect harmless data. Further, the embodiments described herein can include periodically refreshing the unique ID 1022 of the computing device 1020 to further prevent any malicious activities that may be attempted.

[0249] As described above, the packet(s) 1028 transmitted by computing device 1020 can also include one or more known unique IDs 1024 that represent the unique ID 1022 of other computing devices 1020 associated with computing device 1020. According to some embodiments, these other computing devices 1020 can represent computing devices 1020 that are actively paired or previously paired with computing device 1020 and can communicate directly with computing device 1020 (e.g., via Bluetooth® or NFC), such as wearable devices, headphones, speakers, sensors, etc. Thus, and as described in more detail herein, wireless charging device 1002 can utilize the unique ID 1022 and known unique IDs 1024 provided by various computing devices 1020 for identification when an interaction is to occur between specific ones of computing devices 1020.

[0250] Additionally, and as described above, the packet(s) 1028 transmitted by computing device 1020 can include other information 1026 regarding computing device 1020 that can be utilized by wireless charging device 1002 to implement the techniques described herein. For example, the other information 1026 can include an indication of the type of computing device 1020, including model information associated with computing device 1020 (e.g., device name, model, color, display characteristics (e.g., size, dimensions, area), etc.), status information associated with computing device 1020 (e.g., locked / unlocked), battery information associated with computing device 1020, etc.

[0251] Additionally, although not shown in FIG. 10, it will be understood that the various computing devices 1020 described herein may include hardware / software components that enable the computing devices 1020 to interface with a wireless charging device 1002, including, for example, receiving energy from the wireless charging device 1002 (e.g., via the wireless charging surface 1012) (e.g., for charging one or more batteries of a power receiving device), communicating with the wireless charging device 1002, and the like. It will further be understood that the various computing devices 1020 may include hardware / software elements that enable the computing devices 1020 to implement the techniques described herein at various levels. For example, a computing device 1020 having a larger display device (e.g., a laptop, tablet, smartphone, etc.) may be designated as a primary / high-priority device that displays information regarding known computing devices 1020 when they are placed on / removed from the wireless charging device 1002. Continuing with this example, a computing device 1020 having a smaller display (e.g., a smartwatch) may be designated as a secondary / low-priority device that should only display information when a primary / high-priority device is not present on the wireless charging device 1002. For example, if only a smartwatch computing device 1020 is present on the wireless charging device 1002 and a pair of wireless headphones is placed on the wireless charging device 1002, the smartwatch computing device 1020 may undertake to display information regarding the wireless headphones in conjunction with / instead of the wireless headphones. It should be noted that the above examples are not intended to be exhaustive, and the computing devices 1020 described herein may be configured in any way to achieve different variations of the techniques described herein.

[0252] Accordingly, FIG. 10 illustrates an overview of different configurations of a wireless charging device 1002 / computing device 1020 that can be utilized to enable the implementation of the embodiments described herein. As will be described in more detail below, these components can be utilized to provide a rich user experience, e.g., through synchronized / complementary notifications, when two or more related computing devices 1020 are placed on the wireless charging device 1002 for charging.

[0253] FIGS. 11A-11D show conceptual diagrams of an exemplary computing device 1020, in accordance with some embodiments, displaying complementary notifications in a synchronized manner as it is placed on and removed from a wireless charging device 1002. In some embodiments, fewer devices than all those placed on or removed from the wireless charging device provide notifications according to the techniques described herein (e.g., a primary device displays a charging state and other device(s) do not provide notifications in response to placement / removal from the wireless charging device). As shown in FIG. 11A, a first step 1110 can include a computing device 1020-1 being placed on the wireless charging device 1002. This can represent, for example, when a user places the computing device 1020-1 on the wireless charging device 1002 with the intention of charging the computing device 1020-1 via the wireless charging technique described herein. As shown in FIG. 11A, step 1110 can include the computing device 1020-1 transmitting one or more packets 1028 to the wireless charging device 1002. As previously described above, these packets 1028 can include information associated with the computing device 1020-1, e.g., a unique ID 1022, a known unique ID 1024, and other information 1026.

[0254] As shown in FIG. 11A, exemplary information transmitted by packet 1028 is placed within device information 1010 by wireless charging device 1002. For example, the value "device_1" can be specified as the unique ID 1022, the values "device_2" and "device_3" can be specified as known unique IDs 1024, and the value "smartphone, 52% BAT" can be specified as other information 1026. In this example, computing device 1020-1 has the specified unique ID 1022 of "device_1", and computing device 1020-1 has previously been paired with two other computing devices 1020 - computing device 1020-2 having the unique ID 1022 of "device_2", and computing device 1020-3 having the unique ID 1022 of "device_3". Further, in this example, computing device 1020-1 is a smartphone device with a battery level of 52% when computing device 1020-1 is placed on wireless charging device 1002. Additionally, as shown in FIG. 11A, wireless charging device 1002 can specify a "status information" property 1100 within device information 1010 for computing device 1020-1 to identify whether computing device 1020-1 is present on wireless charging device 1002 or not. The "status information" property 1100 can also identify whether computing device 1020-1 is designated as a high-priority device / low-priority device for displaying complementary notifications associated with other related computing devices 1020 (as previously described above) placed on wireless charging device 1002. As will be described in more detail herein, the "status information" property 1100 can enable wireless charging device 1002 to appropriately respond to and command other computing devices 1020-2 and 1020-3 when / after other computing devices 1020-2 and 1020-3 are placed on / removed from wireless charging device 1002.In some examples, the "status information" is at least partially input with information received from the computing device 1020 (e.g., via the received packet(s) 1028).

[0255] In the example shown in FIG. 11A, the computing device 1020-1 is the first and only computing device 1020 present on the wireless charging device 1002. In this regard, and according to some embodiments, the computing device 1020-1 can undertake to display its own battery state, shown as notification 1102 in FIG. 11A. As shown in FIG. 11A, the notification 1102 can indicate, by means of one or more animations / acoustics, (1) the type of the computing device 1020-1 (e.g., "smartphone"), and (2) the battery state for the computing device 1020-1. It should be noted that the content associated with the notification 1102 shown in FIG. 11A is merely exemplary, and any content in any format, order, manner, etc. can be utilized when generating the notification 1102.

[0256] Accordingly, at the end of the first step 1110 shown in FIG. 11A, the first computing device 1020-1 provides useful information via the notification 1102 and receives power from the wireless charging device 1002 to charge any internal battery included within the computing device 1020-1. At this point, the computing device 1020-1 can now function as an auxiliary device to display complementary notifications associated with the computing devices 1020-2 and 1020-3 when the computing devices 1020-2 and 1020-3 are placed on the wireless charging device 1002. For example, the second step 1120 shown in FIG. 11B can include the state where the second computing device, the computing device 1020-2, is placed on the wireless charging device 1002. As shown in FIG. 11B and according to the techniques described herein, the computing device 1020-2 can provide information regarding the computing device 1020-2 to the wireless charging device 1002 via one or more packets 1028. For example, the computing device 1020-2 can provide the value "device_2" as the unique ID 1022, provide the values "device_1" and "device_3" as the known unique IDs 1024, and provide the value "wearable, 17% BAT" as the other information 1026. For example, in FIG. 11A, the computing device 1020-2 can represent a smartwatch, a fitness tracker, an augmented reality device, a sensor, and the like.

[0257] Although it is slightly offset, note that each computing device 1020 disposed on the wireless charging device 1002 can periodically / responsively issue a packet 1028 for providing related updates to the wireless charging device 1002. For example, the device information 1010 can be updated to manage a status property for each computing device 1020 indicating whether the computing device 1020 has the ability to display complementary notifications. In this case as well, this can be based on, for example, whether the computing device 1020 is locked / unlocked, in use / not in use, etc. In another example, the device information 1010 can be updated to reflect the battery state of the computing device 1020 as the computing device 1020 is charged via the wireless charging device 1002, as indicated by the battery state of the computing device 1020-1 advancing from 52% to 60% during the time when steps 1110 of FIG. 11A and 1120 of FIG. 11B occur. In particular, various useful features can be implemented by keeping the battery state up-to-date within the device information 1010. For example, when a pair of headphones is removed from the wireless charging device 1002 and a related device having a display (e.g., laptop, tablet, smartphone, smartwatch) remains on the wireless charging device 1002, the related device can display an indication of the latest battery state of the headphones. In this way, a user who has removed the headphones from the wireless charging device 1002 can immediately receive an easy-to-read indication of the battery state of the headphones (via the display of the related device), thereby improving the user experience. Accordingly, in some embodiments, a wireless charging device (e.g., 1002) receives one or more packets transmitted by a computing device (e.g., 1020).

[0258] In some embodiments, a computing device (e.g., 1020) receives one or more packets transmitted by a wireless charging device (e.g., 1002). For example, a smartphone device (e.g., device 1020-1 in FIG. 11B) can receive a packet 1028 that includes information regarding the battery state (e.g., battery charge level) of a wearable device (e.g., device 1020-2 in FIG. 11B). In this example, the smartphone device then displays an indication of its own battery state and the battery state of the wearable device.

[0259] Additionally, by updating device information, one or more of the computing devices 1020 can immediately display an overview of information regarding associated devices placed on the wireless charging device 1002. This can occur, for example, when a trigger occurs in a given computing device 1020, such as when the home / power button is pressed on the computing device 1020, when the computing device 1020 is moved while placed on the wireless charging device 1002 (e.g., gently nudged by the user), when the computing device 1020 detects that the user is in proximity to the computing device 1020, etc. For example, when a smartphone, smartwatch, and pair of headphones are charging on the wireless charging device 1002, the smartphone can be configured to display an up-to-date overview of its own battery state, the battery state of the smartwatch, and the battery state of the headphones in response to any of the above triggers. According to some embodiments, the smartphone can also be configured to cause one or more of the smartwatch / headphones to present information in a synchronized manner (or, if desired, an asynchronous manner) through complementary notifications.

[0260] Next, returning to FIG. 11B, it should be noted that according to some embodiments, computing devices 1002 and 1020 can be configured to omit the known unique ID 1024 from packet 1028 whenever the known unique ID 1024 represents redundant information. For example, consider a first computing device 1020 that is only paired with a second computing device 1020 (and vice versa). In this example, if the first computing device 1020 is placed on the wireless charging device 1002 and provides a known unique ID 1024 corresponding to the unique ID 1022 of the second computing device, it would be redundant for the second computing device 1020 to provide a known unique ID 1024 corresponding to the unique ID 1022 of the first computing device 1020. Instead, the wireless charging device 1002 can easily identify the relationship by comparing the unique ID 1022 of the second computing device 1020 with the known unique ID 1024 of the first computing device 1020 (managed within the device information 1010) and identifying the relationship, and can perform the same techniques described herein according to the identified relationship.

[0261] In any case, if the information associated with computing device 1020-2 is incorporated within device information 1010, wireless charging device 1002 can identify that computing device 1020-1 and computing device 1020-2 are related to each other (e.g., in a paired relationship, or associated with a set of devices or a common user account). As a result, wireless charging device 1002 can query computing device 1020-1 (e.g., via one or more packets 1028) to determine whether computing device 1020-1 should proceed to display a notification 1106 related to computing device 1020-2 (e.g., whether it is available or capable of being displayed). According to some embodiments, the query can include other information 1026 provided by computing device 1020-2 to minimize the number of messages transmitted between computing device 1020-1, wireless charging device 1002, and computing device 1020-2, thereby reducing the overall latency and improving the overall user experience. In particular, this approach enables computing device 1020-1 to assume the responsibility of holding the information necessary for display within notification 1106 if computing device 1020-1 accepts such responsibility. For example, when computing device 1020-1 remains on wireless charging device 1002, locked, and / or in an inactive state, computing device 1020-1 can instruct acceptance of the display of notification 1106. Alternatively, when computing device 1020-1 is in an unlocked state and / or actively utilized by the user, computing device 1020-1 can instruct rejection of the display of notification 1106.

[0262] In the example shown in FIG. 11B, computing device 1020-1 instructs wireless charging device 1002 to accept to display a notification 1106 related to the fact that computing device 1020-2 is placed on wireless charging device 1002. According to some embodiments, computing device 1020-1 can instruct acceptance by transmitting one or more packets 1028 to wireless charging device 1002. According to some embodiments, packet 1028 can instruct a time delay at which computing device 1020-1 plans to display notification 1106. In this way, wireless charging device 1002 can transfer the time delay to computing device 1020-2. The time delay also indirectly instructs computing device 1020-2 by computing device 1020-1 to accept to display notification 1106. Optionally, computing device 1020-2 can prepare to display a complementary notification 1108 (e.g., a notification that complements the notification by the primary device) according to the time delay provided by computing device 1020-1.

[0263] As shown in FIG. 11B, when the time delay is satisfied, notification 1106 is displayed by computing device 1020-1 and can instruct information regarding computing device 1020-2 through one or more animations / acoustics. For example, the animation / acoustics can communicate the state of "Wearable Battery 17%". Further, in accordance with the satisfaction of the time delay and in relation to notification 1106, notification 1108 generated by computing device 1020-2 can include other information presented through one or more animations / acoustics, for example, when computing device 1020-2 includes a display device (such as a smartwatch). In another example, when computing device 1020-2 does not include a display device but includes one or more LEDs, the LED(s) can be utilized to communicate to the user a pulsating animation that matches the animation / acoustics displayed by computing device 1020-1, for example, the information. In another example, the LED(s) can display continuous light of a first color (such as orange) indicating that computing device 1020-2 is being charged, continuous light of a second color (such as green) indicating that computing device 1020-2 is fully charged, and so on. In any case, even if computing device 1020-2 includes only a small display device or no display device at all, useful information regarding computing device 1020-2 is presented in an aesthetically pleasing manner between computing device 1020-1 and computing device 1020-2, thus improving the user experience.

[0264] As described herein, computing device 1020 is expected to be periodically placed on wireless charging device 1002 in an expected use case environment. To capture how the various embodiments described herein manage such an event, FIG. 11C shows a third step 1130 in which a third computing device 1020-3 is placed on wireless charging device 1002 (while computing device 1020-1 and computing device 1020-2 remain on wireless charging device 1002). As shown in FIG. 11C and according to the techniques described herein, computing device 1020-3 can provide information regarding computing device 1020-3 to wireless charging device 1002 via one or more packets 1028. For example, computing device 1020-3 can provide the value "device_3" as a unique ID 1022, the values "device_1" and "device_2" as known unique IDs 1024, and the value "headphones, 23% BAT" as other information 1026. For example, in FIG. 11C, computing device 1020-3 can represent a pair of wireless headphones associated with both computing device 1020-1 and computing device 1020-2.

[0265] As shown in FIG. 11C and as previously described, the wireless charging device 1002 can receive the packet 1028 and add information regarding the computing device 1020-3 to the device information 1010. As a result, the wireless charging device 1002 can identify that the computing device 1020-1 and the computing device 1020-2 are known to the computing device 1020-3, and issue a message (e.g., via the packet 1028) that includes information regarding the computing device 1020-3. Also in this case, similar to the previous case, such information can include the type of the computing device 1020-3, the battery state of the computing device 1020-3, and the like. As a result, the computing device 1020-1 and the computing device 1020-2 can instruct whether they should proceed to display a notification related to the appearance of the computing device 1020-3 (as described herein). According to some embodiments, when two or more computing devices 1020 are involved in the display of a notification, the primary computing device (e.g., the computing device 1020-1) can instruct a time delay at which the notification should be displayed, and the other computing devices 1020 operate according to the time delay.

[0266] For example, in FIG. 11C, computing device 1020-1 can instruct wireless charging device 1002 of the time delay at which notification 1114 will be displayed at computing device 1020-1. As a result, wireless charging device 1002 can provide the time delay to both computing device 1020-2 and computing device 1020-3, and then computing device 1020-2 and computing device 1020-3 can each prepare to display notifications 1118 and 1122. As shown in FIG. 11C, notification 1114 displayed by computing device 1020-1 can present the information "headphone battery 23%" by one or more animations / acoustics. Additionally, notification 1118 generated by computing device 1020-2 can communicate other information regarding computing device 1020-3 by one or more animations / acoustics. For example, continuing with the above-described exemplary scenario where computing device 1020-2 represents a smartwatch, computing device 1020-2 can display other information in conjunction with notification 1114 displayed by computing device 1020-1. Additionally, in this exemplary scenario, notification 1122 generated by computing device 1020-3 can be optional and used to communicate other information by one or more animations / acoustics according to the time delay and one or more of notifications 1114 and 1118. For example, computing device 1020-3 - which can represent a pair of wireless headphones within FIG. 11C - can include an LED that operates in conjunction with the animation / acoustics. In another example, one or more of the speakers included within the pair of wireless headphones can be used to reproduce an audible sound that operates in conjunction with the animation / acoustics.

[0267] Additionally, it should be noted that computing device 1020 will be periodically removed from wireless charging device 1002 under the expected use case scenarios. To capture how the embodiments described herein manage such events, FIG. 11D shows a fourth step 1140 in which computing device 1020-2 is removed from wireless charging device 1002 (device 1020-2 is shown crossed out by an "X", while computing device 1020-1 and computing device 1020-3 remain on wireless charging device 1002). As shown in FIG. 11D and according to the techniques described herein, device information 1010 can be updated to reflect that computing device 1020-2 is now not on wireless charging device 1002. As a result, wireless charging device 1002 can be configured to notify related computing devices 1020 - for example, computing device 1020-1 and computing device 1020-3 - that computing device 1020-2 is no longer present. At this point, computing device 1020-1 can optionally display a notification 1126 providing the most recent battery state of computing device 1020-2 (e.g., if locked / in use as described herein) by, for example, one or more animations / acoustics. Additionally, computing device 1020-3 can optionally display a notification 1132 providing other information regarding computing device 1020-2 (as previously described herein) by one or more animations / acoustics.

[0268] Accordingly, FIGS. 11A-11D illustrate scenarios in which computing device 1020 can provide information and notifications in accordance with (1) the placement / removal of computing device 1020 onto / from wireless charging device 1002, and (2) the presence of other known computing devices 1020. One or more of the features described above with respect to FIGS. 10 and 11A-11D can be used to perform the techniques described with respect to FIGS. 6A-6AG, 7A-7E, 8A-8E, and 9A-9B.

[0269] The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Embodiments were chosen and described in order to best explain the principles of the technology and its practical application, thereby enabling others skilled in the art to best utilize the technology and various embodiments with various modifications as are suited to the particular use contemplated.

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

Claims

1. A first device having a display, Detecting a first input while the first device associated with a first user account is in a first device presentation state; In response to detecting the first input, transitioning the first device to a second device display state; and simultaneously displaying a first visual indication of a battery level of the first device and a second visual indication of a battery level of a second device different from the first device; the second device is associated with the first user account; the first visual indication is different from the second visual indication; method.

2. The method of claim 1, wherein at least one of the first visual indication and the second visual indication is not displayed prior to detecting the first input.

3. A method as described in claim 1 or 2, wherein the first device display state is an inactive display state and the second device display state is an active display state.

4. The second device is in the first device display state before detecting the first input, and the method further comprises: The method of claim 1 , further comprising: in response to detecting the first input, maintaining the second device in the first device display state.

5. failing to detect communication between the first device and the second device while simultaneously displaying the first visual indication of the battery level of the first device and the second visual indication of the battery level of the second device different from the first device; subsequent to not detecting communication between the first device and the second device, ceasing to display the second visual indication of the battery level of the second device while continuing to display the first visual indication of the battery level of the first device while the first device and the second device are not communicating; The method of claim 1 , further comprising:

6. Simultaneously displaying the first visual indication of the battery level of the first device and the second visual indication of the battery level of the second device different from the first device, displaying the first visual indication concurrently with a first charging status indication in response to determining that the first device is in a charging state; 6. The method of claim 1, further comprising: displaying the second visual indication simultaneously with a second charging status indication in accordance with determining that the second device is in a charging state, the second charging status indication being different from the first charging status indication.

7. A method according to any one of claims 1 to 6, wherein the first visual indication and the second visual indication include at least one of a graphical indication and a textual indication.

8. A method for detecting a battery level of a first device, comprising: displaying a first visual indication of the battery level of the first device and a second visual indication of the battery level of the second device that is different from the first device; detecting a third device in communication with the first device; and in response to detecting the third device, displaying a third visual indication of a battery level of the third device, the third visual indication being different from the first visual indication and the second visual indication.

8. The method according to any one of claims 1 to 7. Detecting that the second device is no longer charging while simultaneously displaying the first visual indication of the battery level of the first device and the second visual indication of the battery level of the second device different from the first device; following detecting that the second device is no longer in the charging state, continuing to display the first visual indication of the battery level of the first device simultaneously with the second visual indication of the battery level of the second device while the second device is not in the charging state; 9. The method of claim 1 , further comprising:

10. A method according to any one of claims 1 to 9, wherein the first device and the second device are logged in to the same service.

11. A computer program causing a computer to carry out a method according to any one of claims 1 to 10.

12. A first device, comprising: A memory for storing the computer program according to claim 11; and one or more processors capable of executing the computer programs stored in the memory, the first device including a display.

13. A first device having a display, the first device comprising means for executing a method according to any one of claims 1 to 10.

Images