Dynamic user interface scheme for electronic devices based on detected accessory devices

Abstract

The system may include an electronic device including an enclosure with a transparent cover. The electronic device may also include a display disposed beneath the transparent cover and configured to display a first graphical user interface and a second graphical user interface different from the first graphical user interface, and a touch sensor disposed beneath the transparent cover and configured to detect touch input applied to the transparent cover. The system may also include a protective case including a shell defining a cavity and configured to at least partially cover the enclosure of the electronic device when the electronic device is positioned within the cavity, and a near field communication antenna coupled to the shell and detectable by the electronic device. In response to detecting the near field communication antenna, the electronic device may be configured to switch from the first graphical user interface to the second graphical user interface.

Description

TECHNICAL FIELD

[0001] The described embodiments relate generally to electronic devices, and more particularly, to electronic devices and accessories that use near-field wireless communication systems to dynamically change the operation of the electronic devices.

BACKGROUND ART

[0002] Handheld electronic devices such as mobile phones and tablet computers provide numerous functions and features, and use graphical user interfaces to allow users to interact with and control those functions and features. For example, a handheld electronic device displays input objects such as icons, buttons, keys, and other graphical objects that a user can interact with to control the device and its various functions. The device may also display output objects such as text or images that convey information to the user.

SUMMARY OF THE INVENTION

[0003] The system may include an electronic device having an enclosure with a transparent cover. The electronic device may also include a display disposed under the transparent cover and configured to display a first graphical output and a second graphical output different from the first graphical output, and a touch sensor disposed under the transparent cover and configured to detect touch inputs applied to the transparent cover. The system may also include a protective case that defines a cavity and includes a shell configured to at least partially cover the enclosure of the electronic device when the electronic device is positioned within the cavity, and a near-field wireless communication antenna coupled to the shell and detectable by the electronic device. In response to detecting the near-field wireless communication antenna, the electronic device may be configured to switch from the first graphical output to the second graphical output. The first graphical output may include a first background image, and the second graphical output may include a second background image different from the first background image.

[0004] The electronic device may be a mobile phone, and the protective case may have a colored exterior. The first graphical output may include a group of application icons and have a first color scheme, and the second graphical output may include application icons and have a second color scheme. The second color scheme may be different from the first color scheme and may correspond to the color of the exterior of the protective case.

[0005] The enclosure may define the rear outer surface of the electronic device, the front outer surface of the electronic device, and the periphery outer surface of the electronic device, the periphery outer surface extending from the rear outer surface to the front outer surface. The shell may further define a window area configured to allow a user to touch the front outer surface of the electronic device when the electronic device is placed in the cavity, a rear wall configured to at least partially cover the rear outer surface of the electronic device, and side walls configured to at least partially cover the periphery outer surface.

[0006] The protective case may further include an input system comprising an actuating member configured to be actuated by a user and a passive antenna. After detecting a near-field radio communication antenna, the passive antenna may become detectable by an electronic device in response to the actuating member being actuated by the user. The electronic device may be configured to perform an action in response to the detection of the passive antenna. The passive antenna may be undetectable by the electronic device when the actuating member is not actuated. The electronic device may further include a camera system, a second graphical output which may correspond to an image acquisition interface, and the actuation of the actuating member may cause the electronic device to acquire an image using the camera system.

[0007] An electronic device dock may include a support structure configured to position the electronic device in a visible orientation when the dock is on the surface of an object; a short-range wireless communication antenna configured to cause the electronic device to display a graphical user interface in response to the electronic device being positioned on the support structure; and an input system configured to wirelessly communicate with the electronic device in response to the input system being activated by a user when the electronic device is positioned on the support structure. The input system may include an actuating member and a passive antenna, and in response to the actuating member being activated by a user, the input system may wirelessly communicate with the electronic device using the passive antenna.

[0008] The graphical user interface may be a secondary graphical user interface, and the electronic device may be configured to switch from displaying a secondary graphical user interface to displaying a primary graphical user interface in response to being removed from the support structure.

[0009] The graphical user interface may correspond to the alarm clock function of the electronic device, and the operation of the input system may cause the electronic device to change the settings of the alarm clock function. The dock may further include a speaker, and the graphical user interface may correspond to the audio playback function of the electronic device, and the operation of the input system may cause the electronic device to change the operating parameters of the audio playback function. The dock may further include a wireless charging system including an output coil configured to inductively couple to the charging coil of the electronic device when the electronic device is held by the support structure.

[0010] A handheld electronic device may include an enclosure, a display, a touch sensor located within the enclosure, and a near-field communication system configured to detect when the handheld electronic device is in proximity to any one of a set of docking accessories. When the near-field communication system detects that the handheld electronic device is in proximity to a first docking accessory of the set of docking accessories, the handheld electronic device may transition from a first operating mode to a second operating mode different from the first operating mode. When the near-field communication system detects that the handheld electronic device is in proximity to a second docking accessory of the set of docking accessories, the handheld electronic device may transition from a first operating mode to a third operating mode different from both the first and second operating modes.

[0011] A first docking accessory may be located in a first location, and a second docking accessory may be located in a second location different from the first location. Transitioning from a first operating mode to a second operating mode may include transitioning from displaying a primary graphical user interface containing a set of application icons to displaying a first auxiliary graphical user interface containing a first set of graphical objects associated with the first location, and transitioning from a first operating mode to a third operating mode may include transitioning from displaying a primary graphical user interface to displaying a second auxiliary graphical user interface containing a second set of graphical objects associated with the second location, different from the first auxiliary graphical user interface.

[0012] Transitioning from a first operating mode to a second operating mode may include transitioning from displaying a primary graphical user interface to displaying a first auxiliary graphical user interface, and transitioning from a first operating mode to a third operating mode may include transitioning from displaying a primary graphical user interface to displaying a second auxiliary graphical user interface different from the first auxiliary graphical user interface. The first auxiliary graphical user interface may include a first user-defined set of graphical objects selected from a group of candidate graphical objects, and the second auxiliary graphical user interface may include a second user-defined set of graphical objects selected from a group of candidate graphical objects. The first user-defined set of graphical objects may include audio control input objects. The second user-defined set of graphical objects may lack audio control input objects. The first user-defined set of graphical objects may be arranged on the display according to a user-defined arrangement.

[0013] The disclosure will be easily understood by the following detailed description, along with the attached drawings in which similar reference numbers specify similar structural elements. [Brief explanation of the drawing]

[0014] [Figure 1A] This figure shows an exemplary system including electronic devices and associated accessories. [Figure 1B] Figure 1A shows the device and exemplary accessories used together. [Figure 2A] An exemplary wireless charging system for the device shown in Figure 1A is illustrated. [Figure 2B] An exemplary wireless charging system for the device shown in Figure 1A is illustrated. [Figure 3A] Figure 1A shows several exemplary protective cases for the device. [Figure 3B] shows the device of Figure 1A being used with an exemplary protective case. [Figure 3C] shows the device of Figure 1A being used with an exemplary protective case. [Figure 3D] shows the device of Figure 1A being used with another exemplary protective case. [Figure 3E] shows the device of Figure 1A being used with another exemplary protective case. [Figure 3F] shows the device of Figure 1A being used with another exemplary protective case. [Figure 3G] shows the device being used with an exemplary removable accessory. [Figure 3H] shows the device being used with an exemplary removable accessory. [Figure 3I] shows the device being used with an exemplary removable accessory. [Figure 3J] shows the device being used with another exemplary removable accessory. [Figure 3K] shows the device being used with another exemplary removable accessory. [Figure 3L] shows the device being used with another exemplary removable accessory. [Figure 3M] shows the device of Figure 1A being used with another exemplary protective case. [Figure 3N] shows the device of Figure 1A being used with another exemplary protective case. [Figure 3O] shows the device of Figure 1A being used with another exemplary removable accessory. [Figure 3P] shows the device of Figure 1A being used with another exemplary removable accessory. [Figure 4] depicts several additional exemplary device holders for the device of Figure 1A. [Figure 5]Depicts several additional exemplary protective cases for the device of Figure 1A. [Figure 6] Depicts an exemplary group of candidate graphical objects for creating a user-defined auxiliary graphical user interface. [Figure 7] Shows several exemplary docks for the device of Figure 1A. [Figure 8] This is a diagram showing exemplary components of an electronic device. [Detailed Description of the Invention]

[0015] Reference will now be made in detail to the representative embodiments illustrated in the accompanying drawings. It is to be understood that the following description is not intended to limit these embodiments to one preferred embodiment. On the contrary, the following description is intended to cover alternatives, modifications, and equivalents that may be included within the spirit and scope of the described embodiments as defined by the appended claims.

[0016] Embodiments herein are generally directed to systems of electronic devices and electronic device accessories that use short-range wireless communication technology to dynamically adjust or change how the device operates. For example, each of a variety of different accessories for an electronic device can include a short-range wireless communication antenna that allows the accessory to be detected and identified by the electronic device. When a particular accessory is detected near the electronic device, the electronic device can change its operation mode in a manner specific to that particular accessory or accessory type.

[0017] Various different types of accessories may be configured to affect the operating mode and / or characteristics of the device using those accessories, using a near-field communication system. For example, a protective case for a mobile phone may be configured to change the mobile phone's operating mode in one way, a charging dock may change the mobile phone's operating mode in another way, and an "alarm clock" docking accessory may change the mobile phone's operating mode in yet another way. The change in operating mode may correspond to and / or be accompanied by a change in the graphical user interface or graphical output displayed by the mobile phone. For example, when a mobile phone is placed in a sports-focused protective case, the mobile phone may replace its primary graphical user interface (or any currently active graphical user interface) with the sports-focused interface without any additional user input. As another example, when a mobile phone is placed on a speaker dock, the mobile phone may replace its primary graphical user interface with a set of audio playback controls. Thus, the graphical user interface that is activated when a device is used with an accessory may be customized to a specific function or set of functions related to the associated accessory. In some cases, these graphical user interfaces may be simpler than primary graphical user interfaces (e.g., those with fewer and / or larger graphical objects), and they may help facilitate more efficient use of the device and may be dedicated to a specific set of functions or operating modes of the device.

[0018] In some implementations described herein, one or more graphical outputs displayed on the device are modified or switched in response to the detection of a protective case. As used herein, graphical output may be used to refer to visible output from a display. Graphical output may include a graphical user interface, graphical objects, images, videos, and / or other visible outputs generated by the display. A graphical user interface may include various types of graphical objects, including graphical objects that indicate information such as icons, menu items, status bars, menus, radio signal strength, time, and battery charge level. A graphical user interface may also include graphical outputs such as background images. Graphical objects may be visually distinguishable from other graphical objects, and the boundaries of graphical objects may suggest a functional distinction between different graphical objects. For example, the boundary of a first icon (e.g., a first graphical object) may visually distinguish the first icon from a second icon, indicating to the user that the two icons define different input areas and that the device will perform different actions when selected.

[0019] As used herein, the terms “switch” or “change” a graphical output may be used to refer to a scenario in which one graphical user interface, graphical object, or other displayed item is replaced with another graphical user interface, graphical object, or other displayed item. The terms “switch” or “change” may also be used to refer to a scenario in which a graphical user interface, graphical object, or other displayed item is modified to produce a visually distinguishable or visually perceptible effect. For example, the background or color scheme of one or more graphical objects within a graphical user interface may be “switched” or “changed” so that they appear to have different colors, textures, or other visually perceptible features. For clarity, a switched or changed graphical output may be called a second graphical output, even if, aside from appearance, it represents the same item or performs the same function when the graphical output was selected.

[0020] For the purposes of this disclosure, accessories may include, but are not limited to, protective cases, game cases, camera cases, and docks (e.g., speaker docks, alarm clock docks, charging docks, wireless docks, etc.). Cases such as protective cases, game cases, and camera cases may be accessories configured to accept otherwise complete devices such as mobile phones and may provide additional functionality (e.g., physical protection, appearance, mounting mechanisms, etc.) to the device. Accessories that include a near-field radio communication antenna and cause an electronic device to change or modify the operating mode and / or characteristics of an electronic device when the device and accessory are in close proximity to each other may be referred to herein as near-field radio-enabled accessories.

[0021] The operating mode and / or characteristics of an electronic device can be changed or modified by near-field radio communication, which enables the determination of when the electronic device is being used with an accessory. For example, the accessory may include a near-field radio communication antenna, and the device may include a near-field radio communication system that can detect when the device is in close proximity to the near-field radio communication antenna (for example, the device can detect when it is installed in the accessory, coupled to the accessory, placed on the accessory, or being used with the accessory). The device may also receive information about a particular accessory from the near-field radio communication antenna, such as a unique identifier.

[0022] Near-field communication systems and antennas may be configured such that an accessory is detected by a device only when the device is sufficiently close and it is substantially certain that the device and accessory are being used together. For example, in the case of a protective case for a mobile phone, the mobile phone can only detect the presence of the case when the phone is inserted into the protective case. In the case of a docking accessory (also referred to herein as a “dock”), the mobile phone can only detect the presence of the docking accessory after the mobile phone has been physically placed on the docking accessory. Furthermore, the near-field communication antenna may be a passive antenna or a parasitic antenna, and dynamic device customization can be performed even with a parasitic accessory. As used herein, a passive antenna or a parasitic antenna refers to an antenna that is not electrically coupled to the power supply of the accessory. Thus, the protective case does not need to have a battery or an independently powered communication system (e.g., WIFI or Bluetooth®) to change the operating mode or other characteristics of the electronic device. However, in some cases, the device may include both a parasitic near-field communication antenna and a powered communication system.

[0023] By providing a range of different accessories that allow for the customization of the mobile device's operation or user interface in different ways, mobile devices can become even more dynamic and useful tools. For example, throughout the day, a user might place their mobile device in a workout case for a morning workout, a charging dock during work, a kitchen dock in the evening, and an alarm clock dock at night. The concepts described herein enable the device to automatically transition to a workout interface when placed in the workout case, a work interface when placed in the charging dock, a cooking interface when placed in the kitchen dock, and an alarm clock interface when placed in the alarm clock dock, among a number of other possible transitions. The device may also transition back to a primary or default interface when removed from those docks (or in response to a user request, regardless of its proximity to the accessory). In this way, the device continuously and automatically adapts to its intended use and provides a user interface tailored to its user.

[0024] Furthermore, the device may use other inputs and / or information to determine how to change or modify its behavior when used with near-field-enabled accessories. For example, when the device detects that it has been docked on an exercise bike, it may also determine the device's location. If the location is a first location (e.g., home location), the device may take a different set of actions than if the location were a second location (e.g., a fitness center or gym). At the home location, the device may initialize a first set of user controls, such as a set of media controls for the user's home media system (e.g., the user's television, stereo equipment, etc.), and the fitness tracking interface. At the fitness center, the device may initialize a second set of user controls, such as a set of media controls for the fitness tracking interface and personal streaming services (e.g., to provide audio to the user's personal headphones). As another example, when the device detects that it has been docked in the kitchen, the device may also determine who is using the device. If the user is a first user, the device may display one set of interface elements (e.g., smoothie recipes and an editable grocery list), and if the user is a second user, the device may display a second set of interface elements (e.g., pasta sauce recipes and a set of media controls for the user's home media system).

[0025] To provide a highly customized and tailored user experience, information from any of the device's sensors and / or sensor systems may be used to provide additional contextual information about the device, its use, its user, etc. Such sensors and / or sensor systems may include, but are not limited to, an integrated camera, GPS or other navigation or positioning systems, thermal sensors, accelerometers, magnetometers, biometric identification systems (e.g., facial recognition, fingerprint recognition, voice recognition), and biometric sensors (e.g., heart rate monitors, electrocardiograms, pulse oxygen saturators). Other types of information not detected by onboard sensors may also be used to provide additional contextual information about the device, its use, its user, etc. Such information may include, but is not limited to, current or predicted weather information, date and time information, calendar entries, recently opened or closed applications, text or email messages, etc. Such information may be stored on the device or accessed via a communication network, etc. In some cases, the device may use information about accessories (from a near-field wireless connection with the accessories) together with additional contextual information (e.g., from sensor systems or other sources) to determine how to change, modify, or affect the operation of the device. For example, a device may determine which application to launch based on its near-field wireless connectivity and its location. Examples of using additional contextual information to determine how to modify or affect the operation of a device used with a near-field wireless-enabled accessory are provided herein.

[0026] Figure 1A shows an exemplary system in which the electronic device 100 (also referred to herein simply as the “device”) may be used with a variety of different accessories, which cause the device 100 to transition between operating modes when used with those accessories. The electronic device 100 is an example of an electronic device, such as the electronic device 800 described herein with respect to Figure 8. As described herein, transitions between operating modes include and / or may include the start and / or end of an application (e.g., starting or ending an application in response to the detection of an accessory), a change in the graphical user interface or graphical output displayed by the device 100 (e.g., a change in the color, content, appearance, size, icons, or information of the graphical user interface), a change in device settings (e.g., alert volume, tactile or tactile output intensity, screen brightness), etc. Transitions between operating modes (or between different graphical user interfaces or other graphical outputs) may or may not include, or may be accompanied by, visual animations, sequences, or other graphical effects that are displayed or occur during the transition.

[0027] The device 100 shown in Figure 1A is a mobile phone (e.g., a smartphone), but this is merely one representative example of a device that may be used in connection with the ideas disclosed herein. Other exemplary devices include, but are not limited to, music / media players, tablet computers, laptop computers, wearable electronic devices, and watches (e.g., mechanical, electric, or electromechanical).

[0028] Device 100 includes an enclosure 102 that defines the outer surface of Device 100. The enclosure 102 may include, for example, a housing member 103 that defines the rear outer surface of Device 100 (e.g., the rear 201 in Figure 2), the front outer surface of Device 100, and the peripheral outer surface 131 of Device 100 extending from the rear outer surface to the front outer surface. The housing member 103 may be a single piece of material (e.g., a monolithic component) or a plurality of separate components. The enclosure 102 may also include a transparent cover 105 that covers or otherwise covers the display 104 and / or touch sensor surface (e.g., a touchscreen) of Device 100, and may define the front outer surface of Device 100. The display 104 is configured to display a graphical output, which can be viewed through the transparent cover 105 or at least one area of ​​the transparent cover 105. The transparent cover 105 may also define one or more openings to allow internal components such as microphones, cameras, speakers, and sensors to access the surrounding environment of the device 100. The device 100 may also include a touch sensor configured to detect touch events or touch inputs applied to the transparent cover 105. The touch sensor may be integrated with a display or configured to provide touchscreen functionality.

[0029] Device 100 may include a near-field communication system 106 configured to wirelessly detect when an electronic device is in proximity to any one of a group of near-field communication-enabled accessories. The near-field communication system 106 can be configured for any suitable type or protocol of near-field communication, including but not limited to near-field communication (NFC) protocols, radio frequency identification (RFID) protocols, or any other suitable type or protocol. For example, the near-field communication system 106 (and in practice any near-field communication system, antenna, or other component described herein) may be configured to operate in accordance with applicable standards such as ISO / IEC 14443, FeliCa, ISO / IEC 18092, ISO / IEC 21481, ISO / IEC 13157.

[0030] In some cases, the near-field communication system 106 is configured to detect the presence or proximity of a passive or unpowered antenna incorporated into an accessory. Thus, the near-field communication system 106 may be separate from other communication systems within the device 100, such as Bluetooth®, Wi-Fi, or a cellular communication system, and may be configured to communicate over a limited range (for example, the near-field communication system 106 may only be able to detect near-field wireless antennas when they are within approximately 10 cm of each other).

[0031] Device 100 may include physical inputs, such as a button 108, which a user can interact with to control the operation of Device 100. The specific function of button 108 may be modified based on the accessory associated with Device 100 at a given time. For example, as described herein, in a primary operating mode, button 108 may function to activate or deactivate the screen of Device 100. In a second operating mode, such as when Device 100 is in a case intended for taking photographs, button 108 may function as a shutter button for taking images. Although Device 100 is shown to have one button 108, this is merely representative, and Device 100 may include more or different input mechanisms, such as separate volume control buttons, a fingerprint sensor, a rotatable input member, keys, a keyboard, etc. Device 100 may also include a wireless charging system, as described with respect to Figure 2.

[0032] Device 100 may also include various additional internal components and structures such as sensors, memory, processors, control circuits, batteries, circuit boards, frames or other support structures, and antennas. Device 100 may also include a front and / or rear camera system (e.g., the rear camera 214 in Figure 2) capable of capturing images and / or video of external subjects. The camera system may include a lens, an image sensor, a focus and zoom mechanism, a flash, and any other suitable components.

[0033] Additional or different components may be located within the enclosure 102 of device 100. Device 100 may also include various systems and / or components (e.g., touchscreens, microphones, biometric sensors, GPS systems) that can receive information from or about the user or the user's surroundings. It should be fully understood that the use of personally identifiable information (such as information from or about the user or the user's environment that is stored on or accessible by the device) should be in accordance with privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintentional or unauthorized access or use, and the nature of permitted use should be clearly indicated to the user.

[0034] The system shown in Figure 1A also includes various types of accessories that may be used with device 100. For example, Figure 1A includes a protective case 112, a dock 114, a dock 116 with an auxiliary input system 117, a speaker dock 118, and a protective case 120 with an auxiliary input system 121. As described herein, device 100 may be used with each of these accessories (as well as other accessories not shown in Figure 1A), and when a user switches from one accessory to another, device 100 may dynamically switch to different operating modes, present different graphical user interfaces or graphical outputs (e.g., presenting graphical user interfaces with different content or different appearances, colors, etc.), change device settings, or operate in a manner adjusted to the specific accessory with which device 100 is being used. Docks such as dock 114 may include standalone accessories, as well as docks integrated into other devices such as exercise equipment (e.g., bicycles, rowing machines, elliptical machines, stair climbers, etc.), vehicles, and musical instruments (e.g., guitars, amplifiers, keyboards, etc.). The dock 114 is shown with an optional ledge 115 for supporting the device 100 in a convenient observation position. In some cases, the dock 114 may be without the ledge 115, and the device 100 may be held in the dock 114 and / or maintained in a particular orientation or position using magnetic mounting features within the dock 114 and the device 100.

[0035] Each accessory may include a near-field radio communication antenna 110 (also referred to herein simply as the “antenna”) detectable by the near-field radio communication system 106 of device 100. As used herein, an antenna may be detectable insofar as the antenna or near-field radio communication circuit can produce an electrical response when probed or polled by a radio detection device or circuit. For example, an antenna may produce a distinct or recognizable interference or other response to an electromagnetic field generated by another device or circuit, thereby making the antenna detectable. Furthermore, as used herein, a detectable near-field radio communication antenna indicates that the near-field radio communication antenna may be operable to trigger, initiate, or otherwise cause a response in the near-field radio communication system of the device, the response indicating the presence and / or proximity (e.g., within threshold distance) of the device.

[0036] When device 100 is detected being used with one of the accessories in Figure 1A, for example, because it is within short distance (e.g., less than approximately 10 cm) of the accessory, the detected antenna 110 causes device 100 to change its operating mode. As used herein, changing the operating mode can mean or include changing the graphical output of the device (e.g., temporarily or permanently changing the color scheme of part or all of a graphical user interface, changing between different graphical user interfaces, initiating the display of a graphical object), changing one or more device settings, or a combination thereof. To facilitate this function, each antenna 110 may contain some identifier or other information that uniquely identifies its accessory (or an accessory of that type), or may be configured to uniquely modify the operation of device 100. In this way, the operation of device 100 can change dynamically as the user switches to a different accessory.

[0037] Antenna 110 may be any suitable type of antenna detectable by the device 100's near-field communication system 106. For example, antenna 110 may be an NFC antenna, an RFID antenna, etc. In some cases, antenna 110 may be a passive antenna or a parasitic antenna. Thus, the accessory does not need to be powered or contain a battery or other power source in order to cause the device 100 to change its operating mode. This can make the accessory smaller, thinner, lighter, and more portable than when the accessory requires a power source. In some cases, antenna 110 may be located inside the accessory or powered by a power source connected to the accessory. Also, accessories that use power for other purposes (e.g., speakers, amplifiers, etc.) may use a passive antenna or a parasitic antenna even though power is available in the accessory.

[0038] The near-field communication antenna 110 may be positioned within the accessory so as to be aligned with the accessory so as to be detectable by the near-field communication system 106 when the device 100 is used with the accessory, or otherwise appropriately positioned. For example, when the device 100 is placed in a protective case 112, the near-field communication antenna 110 of the case may be substantially aligned with the near-field communication system 106 of the device 100 (e.g., within about 2 cm or about 1 cm). The antenna and the near-field communication system 106 may be similarly aligned when the device 100 is placed on a dock 114, 116, or 118.

[0039] As described, device 100 can dynamically change its operating mode when used with different accessories. In some cases, changing the operating mode involves changing between different graphical user interfaces. Figure 1B shows device 100 displaying the primary graphical user interface 128 when it is not used with an accessory (when it is used with an accessory that causes device 100 to display the primary graphical user interface 128), and displaying a different graphical user interface 130 when it is used with accessory 129 (shown as a dock in this example).

[0040] The primary graphical user interface 128 may include selectable icons (for example, application icons that, when selected, run and / or initialize an application, or display a graphical user interface associated with an application), or other graphical objects corresponding to applications or other functions of device 100. The primary graphical user interface 128 may also include graphical objects that display information such as a status bar, menus, radio signal strength, time, and battery charge level. The primary graphical user interface 128 may be displayed automatically when device 100 is turned on and may be considered the top-level graphical user interface (or the highest level of a multi-level graphical user interface scheme) of device 100. The primary graphical user interface 128 may also be called the “home screen” and may be the primary startup interface for the device’s operating system. The primary graphical user interface 128 may also have a color scheme that can refer to one or more colors, such as a background image, borders, screen area, and icons. As used herein, a secondary graphical user interface may refer to any graphical user interface other than the primary graphical user interface.

[0041] When device 100 is placed on an accessory and positioned by the accessory so that device 100 can be seen and interacted with, device 100 can switch from a primary graphical user interface 128 to another graphical user interface. For example, as shown in Figure 1B, when device 100 is placed on accessory 129, device 100 can switch from a primary graphical user interface 128 to a second graphical user interface 130 that is different from the primary graphical user interface 128. The second graphical user interface 130, unlike the primary graphical user interface 128, is just one of many possible graphical user interfaces that device 100 can switch to in response to device 100 being used with an accessory. The switch from the primary graphical user interface to the second graphical user interface can be triggered by device 100 detecting a near-field communication antenna in accessory 129.

[0042] The second graphical user interface 130 may have a different set of icons, inputs, outputs, or other types of graphical objects compared to the primary graphical user interface 128. For example, the second graphical user interface 130 lacks the application icons of the primary graphical user interface 128 and instead includes other graphical objects such as graphical objects 132 and 134. Graphical object 132 may be a "world clock" graphical object (e.g., displaying the time in multiple time zones), and graphical object 134 may be an "audio control" graphical object (e.g., displaying information about the currently playing audio and including audio control affordances such as play, pause, skip forward, and skip backward). Thus, the second graphical user interface 130 includes different graphical content and provides different device functionality than the primary graphical user interface 128. Device 100 can be modified to automatically return from the second graphical user interface 130 to the primary graphical user interface 128 when device 100 is removed from the dock 129, or in response to user input received while device 100 is on the dock 129.

[0043] Figures 2A and 2B illustrate a wireless charging system for device 100. Figure 2A shows a rear view of, for example, device 100 and the charging dock 200, which is configured to wirelessly charge device 100 when device 100 is placed on the charging dock 200. Figure 2B shows device 100 positioned on the charging dock 200 in a charging configuration (for example, the back of device 100 resting on the top surface of the dock 200).

[0044] Device 100 includes a charging coil 206 located within the device 100 and configured to inductively couple to the output coil 210 of a charging dock 200 for charging the device 100. More specifically, the output coil 210 of the charging dock can generate an electromagnetic field, which induces a current in the charging coil 206 of the electronic device, and this induced current can be used to charge the battery of the device.

[0045] Device 100 may include a set of magnetic mounting features, such as magnets 202, configured to facilitate alignment and retention of Device 100 on the charging dock 200. The charging dock 200 may include a pair of complementary magnets (or ferromagnetic materials) 204 attracted to magnets 202 to further facilitate alignment and retention of Device 100 on the charging dock 200. For example, magnets 202 and complementary magnets (or ferromagnetic materials) 204 may be configured such that when Device 100 is brought close to the dock 200 by a user (e.g., 2 cm, 1 cm, or another suitable range), magnets 202 and complementary magnets 204 pull Device 100 toward the dock 200, aligning the output coil 210 of the dock 200 with the charging coil 206 of Device 100. The magnetic attraction force may also provide a retaining force that holds Device 100 in the aligned position and prevents Device 100 from sliding off the dock 200 during charging. Figure 2A describes the device as including a magnet 202 and the dock 200 as including a magnet or magnetic material 204, but it will be understood that any materials or combinations of materials that are magnetically attracted to each other may be used in either the device 100 or the dock 200. Furthermore, the magnet and / or magnetic material may be arranged so that the device 100 is magnetically coupled to the dock 200 in only one orientation. This can further help prevent misalignment and help ensure that the wireless charging function can operate efficiently. In some cases, other techniques may be used to align the device 100 with the dock 200, such as alignment pins and recesses, clips, or surfaces of complementary shapes, instead of or in addition to the magnet.

[0046] In some cases, the dock 200 may include a near-field radio communication antenna similar to the antenna 110 described with respect to Figure 1A. In this way, device 100 can detect when it is placed on or otherwise held in the dock 200 using the same near-field radio communication system used to detect the presence of other accessories. (In other cases, device 100 can communicate with the dock 200 using charging and output coils or via another radio protocol or technique.) When device 100 detects that it is placed on the dock 200 via the near-field radio communication system, it can change its operating mode to match the dock 200. For example, as shown in Figure 2A, device 100 can display a graphical object 211 on the display 104. The graphical object 211 may be on the blank screen of device 100 or as an overlay on the primary graphical user interface. The graphical object may include inputs and outputs that are contextually relevant to the dock 200 and / or the charging operation provided by the dock 200. For example, as shown in the figure, the graphical object 211 displays the name or description of the dock 200 (e.g., "bedroom charger"), as well as an input 212 that can control one or more modes of charging operation. For example, the input 212 may allow the user to select different charging modes or different power consumption modes for the device 100.

[0047] Other inputs and outputs may also be included instead of, or in addition to, those shown in Figure 2B. For example, the graphical object may include inputs and outputs related to the room in which the dock 200 is located. As used herein, a graphical object or graphical user interface may be considered related to a location, room, accessory, etc., if the graphical object or graphical user interface provides access to a function or information that is closely related to the context of the location. Thus, for example, if the dock 200 is in a bedroom, the graphical object may include inputs for activating or deactivating an alarm. If the dock 200 is in a living room, the graphical object may include inputs for controlling audio playback of device 100 or a connected audio system (e.g., a home stereo or other device). If the dock 200 is in a kitchen, the graphical object may include a recipe interface and one or more timers. If the dock 200 is in a music room, the graphical object may include audio control and a score interface. In some implementations, the association of an accessory (e.g., a dock) with a particular room is based on the assignment of the accessory to a virtual room within the smart home platform. A smart home platform may include a number of virtual rooms or environments, and devices and / or smart accessories may be associated with specific rooms and / or environments among them. For example, devices such as a television, audio system, and wirelessly controllable lighting may be assigned to a “living room” environment. In some implementations, a dock (e.g., dock 200) is also associated with or assigned to a “living room” environment within the smart home platform. Thus, in some implementations, in response to being placed on the living room dock, a device detects that the dock is associated with a “living room” environment and displays a graphical object configured to control devices assigned to the “living room” environment (e.g., a television, audio system, and lighting located in the living room).

[0048] Figures 2A and 2B show a wireless charging system integrated into a dedicated charging dock, but wireless charging systems similar to those described with respect to Figures 2A and 2B can be integrated into other accessories described herein. For example, a protective case may include an auxiliary battery and an output coil to charge the device 100 when the device 100 is inserted into the case. Similarly, an output coil and alignment magnets may be integrated into a speaker dock or alarm clock dock to enable the device 100 to charge when the device 100 is positioned on the dock. Furthermore, a wireless charging system may be integrated into a standalone battery accessory that is attached to a device and configured to wirelessly charge the device from a battery. Exemplary battery accessories are described herein with reference to Figures 3J and 3L.

[0049] As described above, device 100 can use a near-field communication system to detect when it is being used with an accessory and to identify that particular accessory. Furthermore, since the near-field communication antenna does not need to be powered to communicate with the device's near-field communication system, or does not need to be detectable by the device's near-field communication system, even simple accessories such as protective cases and simple device stands can trigger the device to change its operating mode or otherwise modify its behavior. Figure 3A shows some examples of protective cases for devices such as device 100. The protective cases shown in Figure 3A may be embodiments of the protective case 112 in Figure 1A. Each protective case in Figure 3A may include a near-field communication antenna 110, but may lack other circuits or components that interact with device 100. Thus, even a simple protective case that looks like nothing more than a piece of plastic or rubber can cause device 100 to change its behavior in different or unique ways.

[0050] Referring to Figure 1A, each protective case in Figure 3A may include a shell 124 defining a cavity 125 in which a device 100 can be placed. The shell 124 may be configured to at least partially cover the enclosure of the device 100 when the device 100 is placed inside the cavity 125. The shell 124 may further define a rear wall 122 configured to at least partially cover the rear outer side of the electronic device (e.g., side 201 in Figure 2A) and a side wall 127 configured to at least partially cover the periphery outer side 131 of the device 100. The shell 124 may also define a window area 126 configured to allow a user to touch the front outer side of the electronic device (e.g., transparent cover 105) when the device 100 is placed inside the cavity 125. The window area 126 may be an open area such that the protective case covers all or substantially all of the back and sides of the device 100, but leaves the transparent cover 105 substantially uncovered (for example, so that more than 50%, 60%, 70%, 80%, 90%, 95%, or 99% of the front of the transparent cover 105 is not covered).

[0051] The walls of the shell 124 (e.g., the back wall 122 and the side walls 127) may be relatively thin. For example, in some cases, each wall of the shell 124 may have a thickness of about 4 mm, about 3 mm, about 2 mm, about 1.5 mm, less than about 1 mm, or any other preferred dimension. The shell 124 may increase the overall size of the device (e.g., the combined size of the shell with the installed device) by a sufficiently small amount so that the main functions of the device 100 are not fundamentally altered as a result of the device 100 being placed in the protective case. For example, if the device 100 is a mobile phone that can be held and operated by a user's hand (e.g., one hand), then when the device 100 is in the protective case, the device 100 may retain the same or substantially the same use and / or handling characteristics (e.g., it can still be held and operated with one hand). If the device 100 is a tablet that can be held and operated with one hand or both hands, then the device 100 may be held and operated in the same or similar manner even when inserted into the protective case.

[0052] Each protective case in Figure 3A may also include a near-field radio communication antenna 110 coupled to its shell and configured to cause device 100 to switch from displaying a first graphical user interface (or graphical output) to displaying a different graphical user interface (or graphical output) in response to an electronic device being placed inside the cavity. Figure 3A illustrates how various different examples of protective cases may switch the graphical user interface of device 100. For example, device 100 in Figure 3A, not inside a protective case, is shown displaying the first graphical user interface 310. The first graphical user interface 310 may be a default or primary graphical user interface, such as the primary graphical user interface 128 in Figure 1B. In some cases, this graphical user interface 310 may display selectable icons (e.g., application icons that, when selected, run and / or initialize an application, or display a graphical user interface associated with an application), or other graphical objects corresponding to applications or other functions of device 100. The first graphical user interface 310 may also have a background image 311. The background image 311, sometimes called a wallpaper, may be an image that graphically appears behind the application icons of a graphical user interface. In some cases, the first graphical user interface 310 may primarily function as an application selection screen. (Device 100 may also have a "lock screen" or "wake screen" that is displayed when the display is active but Device 100 is locked. The lock screen may also have a background image that may also be called a wallpaper.)

[0053] Case 300 may be configured to cause device 100 to stop displaying a first graphical output (e.g., a first graphical user interface 310) and instead display a second graphical output 312 that is different from the first graphical output. As used herein, the second graphical user interface or graphical output may refer to any graphical user interface or graphical output that is different from the first graphical user interface or graphical output.

[0054] When device 100 is placed inside case 300, the device 100's near-field communication system 106 detects the near-field communication antenna of case 300 that is close to device 100 (for example, within a range of about 10 cm, 5 cm, 2 cm, etc.) and receives information from the antenna, from or about case 300. The antenna can communicate executable commands to device 100, or it can communicate data that the device uses to select or retrieve commands or routines, or to determine how to modify their operation.

[0055] The graphical output 312 initiated by case 300 may include the same application icons and provide the same functionality as the first graphical user interface 310, but may have a different background image 313. Therefore, when a user places device 100 inside case 300, device 100 may automatically switch to the different background image. In some cases, the different background image 313 is a modified version of background image 311. For example, the hue, saturation, color balance, or other image characteristics of background image 311 can be modified to generate the different background image 313.

[0056] Different background images 313 may relate to the case 300 in some way. For example, if the case 300 is blue, the background image 313 may be blue, and if the case 300 has a rainbow decoration, the background image 313 may be rainbow. Thus, the graphical user interface 310 may be modified or transformed to graphically match or adjust to the case 300. In this way, the user can switch between cases having different colors, designs, appearances, etc., and the appearance of the graphical output of device 100 changes automatically based on the case it is coupled to.

[0057] In addition to, or instead of, changing the background image, device 100 may display a second graphical output that includes the same icons and background image as the primary graphical user interface, but has a different color scheme. The color scheme for the graphical user interface may include specific colors for the background, application icons, status bar, information icons, etc. The color scheme of the second graphical output may match or otherwise correspond to the color of the outer surface of the accessory (e.g., case 300) in which device 100 is installed. For example, if the accessory is yellow, the second graphical output may include graphic elements that have the same or a similar shade of yellow as the case. In particular, these elements may have different colors when device 100 is not installed in the case. In some cases, at least one graphic element of the second graphical output may have the same color as the accessory.

[0058] Other changes to the graphical user interface 310 (or other graphical output displayed by device 100) are also contemplated. For example, instead of switching to a different background image, or in addition to that, device 100 may change the arrangement of its icons, or the content or appearance of the lock screen, or change the overall color scheme of the graphical user interface and / or background image.

[0059] Another case, such as case 302, may have an antenna that moves device 100 from the first graphical user interface 310 to yet another graphical user interface 314 (e.g., a second graphical user interface). The graphical user interface 314 may be a restricted environment, which may reduce or change the number or type of available application icons, optionally change the size of the icons, and lock the interface so that the user cannot leave the restricted environment without a password or other type of authentication. In addition to changing the graphical user interface, other aspects of device operation may be modified or changed. For example, notifications (e.g., ringtones, message previews, etc.) may be turned off or changed to a different mode (e.g., message content previews are not displayed). As another example, access to media stored on device 100 may be restricted or limited, such as limiting movies or songs based on their rating. Thus, case 302 may be particularly suitable for use when device 100 is given to a child or friend for temporary use, where the owner of device 100 may want to restrict access to certain applications or features.

[0060] If case 302 is intended to function as a child-friendly case, case 302 itself may include physical features that may be useful for a device being used by a child. For example, case 302 may have additional padding or other protection to prevent damage in case of drops, a seal to prevent damage from spills, a clear screen cover to prevent damage to or soiling of the clear cover, a grip or other features to facilitate holding by smaller hands.

[0061] Another exemplary case 304 may have an antenna that causes device 100 to display a graphical user interface or other graphical object coordinated with physical features within the case itself, such as an opening in the case. For example, case 304 includes a front cover 316 that allows the user to open and close the front of device 100. The front cover 316 may include a window 318 that allows a portion of the display of device 100 to be seen when the front cover 316 is closed. When device 100 detects that it is being used with case 304 and that the front cover 316 is closed, device 100 may transition from the first user interface 310 to another graphical user interface 320 that includes a graphical object 322 that is aligned with and / or positioned to be visible through the window 318. The illustrated graphical object 322 includes the current time and weather, but may include any other information or images instead of, or in addition to, those shown. Furthermore, the graphical object 322 may remain displayed even when the front cover 316 is closed, or even after the display of device 100 has been turned off (for example, to save power). Device 100 can detect that the front cover 316 of case 304 is closed using any suitable technique. For example, device 100 can detect that the front cover 316 is closed by detecting that the front camera is obscured using a second near-field wireless communication antenna inside the front cover 316, or any other preferred technique.

[0062] Since case 304 has a front cover 316, device 100 may be more shielded or covered when inside case 304 than when inside other open-front cases (e.g., case 300). Therefore, when device 100 detects that it is inside case 304, device 100 may also change other settings or functions of the device. For example, the alert volume may be increased to account for the silencing or volume attenuation of case 304. As another example, since device 100 may use case 304 when the user intentionally wants to silence device 100, the alert volume may be reduced or the alert may be turned off completely. Device 100 may also change how it provides graphical or visual notifications, such as by displaying graphical or visual notifications in the area of ​​window 318 so that they are visible when the front cover 316 is closed. In fact, as with any other accessories described herein, the user can customize how device 100 changes in operation when used with the accessory. For example, a user may choose which graphical user interface should replace the primary user interface (e.g., an array of application icons), or which device settings should be changed. Case 304 is shown as having an openable front cover, but other types of cases may have windows and function similarly to case 304 (e.g., a sleeve-type case with a window on one side of the sleeve).

[0063] Another exemplary case 306 may be designed to hold the device 100 during exercise or other physical activity. The case 306 includes, for example, a strap 326 for attaching the case 306 and the device 100 to a user (e.g., on the user's arm or wrist). When the device 100 is detected to be inserted into the case 306 (e.g., when the device 100 is detected to be close to the antenna of the case 306), the device 100 may transition to a graphical user interface 324 adapted for use during exercise. For example, since devices such as smartphones are often used as audio players during exercise, the graphical user interface 324 may include large audio control buttons that are easy to see and press even during exercise (e.g., buttons that respond to touch input within an area of ​​approximately 1 square inch or more). The device 100 may also suggest music or audio (e.g., a workout playlist) in response to detection by the case 306. The device 100 may also be able to change its settings to accept or respond to different types of input than it does in its normal operating mode. For example, device 100 may be configured to skip a song when the user knocks on or bumps device 100, and to change the volume of the audio output when the user swipes their palm up or down along the front of the device. Device 100 can also be configured to respond to other types of input.

[0064] Figure 3A shows four exemplary cases in which a short-range wireless communication antenna can be used to trigger device changes, but other types of cases may also be provided. For example, a case of use during camping, hiking, or other outdoor activities may be configured to put device 100 into a power-saving mode or to change device settings to help conserve power (e.g., reducing screen brightness, turning off cellular and Wi-Fi radio). In such cases, the conventional lock screen or primary graphical user interface may also be replaced with a set of icons for features or applications related to the outdoor activity. For example, device 100 may display large buttons to activate a flashlight function, a compass function, a map or positioning application, and a weather application. As mentioned above, the specific buttons displayed may be selected by the user based on user preference when using that particular case.

[0065] As another example, when device 100 is being used in a work environment or during outdoor activities such as hiking, camping, fishing, boating, skiing, or rock climbing, a rugged case may be provided. Such a case may be hardened or otherwise configured to provide a greater degree of physical protection to the device, and may be configured to replace the conventional lock screen or primary graphical user interface of device 100 with a set of icons for features or applications related to a particular activity or work environment. For example, device 100 may display buttons for activating a flashlight function, a level function, a camera application, and a radio function. As described above, the specific buttons displayed may be selected by the user based on their preference when using that particular case.

[0066] As another example, a case may cause the device to change its background image or wallpaper to match or coordinate with a separate object. For example, a case may change its background image or wallpaper to match or coordinate with the fabric of a handbag, backpack, wallet, or other object in which the device and case are used together. If the case is intended to be used when the device is carried in a bag, backpack, or wallet, the case may also increase the ringing volume and / or haptic notification amplitude of the device to help the user hear or feel device notifications through the bag.

[0067] Figures 3B and 3C show an example of device 100 used with accessory case 330, where device 100 displays color effects on its display 104 in response to being placed inside the cavity 331 of protective case 330. In particular, as described herein, device 100 uses its near-field communication system to detect when device 100 is in close proximity to case 330 and to receive information about the case in order to determine which color effect to display.

[0068] Figure 3C shows an exemplary color effect 333 that may be generated in response to the detection that device 100 is being used with case 330. The color effect shown in Figure 3C may appear as a wash of color that sweeps across display 104. The color effect 333 may also be any visible change in the characteristics of the graphical output of display 104. For example, if display 104 is displaying a background image, the color effect 333 may be a change in the hue, tint, shading, tone, saturation, etc., of the background image. The color effect may also be an image, a pattern, etc. The color effect 333 may be visually related to the color or use of the protective case 330. For example, the color effect 333 may match or be similar to the color of case 330. As another example, the color effect 333 may be contextually relevant to the use of the case, such as a rugged case for outdoor use, so that the color effect 333 has a camouflage appearance.

[0069] Returning to Figure 3C, at time t0, the color effect 333 may appear on the display 104. At time t1, the color effect 333 (the boundary of the color change) has moved a certain distance across the display 104, and at time t2, the color effect 333 has moved completely across the display 104. This may be the end of the color effect 333 (for example, the color change persists until device 100 is removed from the case or another event occurs), or the color effect 333 may continue to change further. For example, the color "wash" may gradually disappear until it is gone and the original unaltered graphical output (e.g., before time t0) is displayed again by the display 104, or it may continue to move across the display 104. If the color effect 333 (e.g., a change in the color of the graphical output) persists until device 100 is removed from case 330, the color effect animation shown in Figure 3C can be reversed to return the graphical output to its original, unchanged color (for example, the color effect may be animated from t2 to t0 instead of from t0 to t2).

[0070] The color effect 333 shown in Figure 3C may be displayed while other graphical objects or graphical user interfaces are being displayed by the display 104. For example, the display 104 may display icons associated with the main, or primary, user interface of the device's operating system. The icons may appear to be in front of (or on top of) the background image. The color effect 333 may affect any part or segment of the graphical output on the display 104. For example, the color effect 333 may cause a visual change in both the background image and the graphical user interface icons, or it may cause a visual change in the background image but not in the graphical user interface icons, or it may cause a visual change in the icons but not in the background image. The color effect 333 may be displayed in conjunction with user interfaces other than the main or primary user interface. For example, the color effect 333 may be displayed while the graphical user interface of an application (e.g., a program run by or on the operating system) is being displayed.

[0071] The graphical user output displayed when color effect 333 is absent may be considered a different graphical output from the graphical output displayed when color effect 333 is present. In other words, when color effect 333 is absent, the device may be considered to be displaying a first graphical output, and when color effect 333 is present (even temporarily), the device may be considered to be displaying a second graphical output. These are merely examples of how color effect 333 may affect the appearance of the graphical output on display 104, and other possibilities are also conceivable.

[0072] Figure 3D shows an example of device 100 used with accessory case 334, where device 100 displays a graphical output aligned with the physical features of case 334 itself, such as an opening in the case. For example, similar to case 304, case 334 defines a window 336 that allows device 100 to view a portion of the display 104 of device 100 when it is inside case 334. When device 100 detects that it is being used with case 334 (for example, using the near-field wireless technology described herein), device 100 may transition from displaying a first graphical output 337 (which may be a primary or primary graphical user interface, a graphical user interface for an application, etc.) to displaying another graphical output, such as a graphical object aligned with and / or visible through window 336.

[0073] The case 334 may have an opening 335 defined along its side so that the device 100 can be slid into the case 334. The opening 335 may be the only opening configured to allow the device to be placed inside the case 334. The opening 335 is shown on the side of the case 334 having the smallest area, but in other implementations of the case 334, the opening 335 may be along a different side of the case 334 (e.g., the long side 377).

[0074] Figure 3E shows device 100 inserted into case 334. When device 100 detects that it has been inserted into case 334 or is being used with case 334 in any other way (e.g., using near-field wireless technology), device 100 transitions from displaying a first graphical output 337 (e.g., a primary graphical user interface) to displaying a second graphical output 344. The second graphical output 344 differs from the first graphical output 337 in that it includes graphical objects having a size, shape, and position on display 104 that coordinates with window 336, as shown. In particular, if device 100 is not inside case 334, the graphical objects of the second graphical output 344 may appear out of place or interfere with the display of the primary graphical user interface. The second graphical output 344 shown includes the current time 376, a message notification icon 338, and an incoming call notification icon 339, but may include any other type of icons or information. Message and incoming call notification icons may also include several unread or recent messages or calls, thus enabling the user to quickly access information that may be useful to view without having to remove device 100 from case 334.

[0075] Figure 3F shows device 100 inserted into case 334, which displays a third graphical output 345. The third graphical output 345 may include graphical objects used in place of the second graphical output 344. The specific content, arrangement, appearance, or other characteristics of the graphical object(s) displayed in window 336 may be user-selectable or configurable. For example, the user of device 100 can choose whether the second or third graphical output 344, 345 is displayed when device 100 is inserted into case 334. The third graphical output 345 may include the current time 340, a weather indicator 393 (which may display a graphical representation of the current weather), a day / date indicator 342, and a notification indicator. The notification indicator may signal that new notifications are available to the user. Notifications may indicate, for example, that an event has occurred on device 100 (e.g., that a voice message has been received, that an incoming call has been missed, that an application has issued a notification or message, or that a text or email message has been received). The content of the third graphical output 345 may be configured to convey information more concisely and efficiently than a conventional graphical user interface. For example, instead of indicators that distinguish different types and quantities of recently received messages, graphical output 345 may include notification indicators 341 related to multiple different types of messages. This type of streamlined graphical output can improve the functionality of device 100 by allowing the user to interact with the device in different ways under different circumstances or use cases. For example, instead of requiring the user to remove device 100 to check messages or to see the time, the user can simply look at device 100 through window 336 to see the desired information. Furthermore, the same information may be displayed in the main or primary user interface, although the main or primary interface may display the information in a smaller or less visually appealing form.In this way, by displaying information in a more efficient and readable format, the overall usefulness of the device and the usefulness of device 100 when it is inside case 334 are improved.

[0076] As described above, various types of accessories may be configured to affect the operating mode and / or characteristics of the device using those accessories, using a short-range wireless communication system. For example, Figures 3A to 3F show an example where the accessory is a protective case for a device. Another type of accessory may be configured to be attached to the device and / or the protective case of the device (for example, on the back of the device or case). Figures 3G to 3I show one such exemplary accessory.

[0077] Figure 3G shows device 346 (which may be in a protective case) and a card wallet accessory 347 configured to be detachably attached to the surface 351 (e.g., the back) of device 346. Device 346 may be device 100, or an embodiment of device 100, or may be the same as or similar to device 100.

[0078] The card wallet accessory 347 may include a near-field communication antenna 348 detectable by the near-field communication system of device 346. The card wallet accessory 347 may define a first opening 358 configured to allow an object (e.g., a bank card 350) to be placed into and removed from the internal cavity of the card wallet accessory 347. The card wallet accessory 347 may also define a second opening 349 which may allow the contents of the card wallet accessory 347 to be visible to the user, and may also allow the user to touch the contents of the card wallet accessory 347 and slide the contents out of the card wallet accessory 347. The card wallet accessory 347 may also include a magnetic mounting feature 359 configured to detachably attach the card wallet accessory 347 to device 346 via a complementary magnetic mounting feature 360 ​​of device 346. The magnetic mounting features 359, 360 may include magnets, ferromagnetic materials, and the like. In some cases, device 346 may include a metal plate or sheet so that the card wallet accessory 347 can be placed at any location along the surface 351.

[0079] Figure 3H shows a card wallet accessory 347 detachably attached to the surface 351 of device 346. As described for other near-field radio-enabled accessories, in response to detecting that the card wallet accessory 347 has been attached to device 346, device 346 may take action or change its operating mode. When attaching the card wallet accessory 347, device 346 may record the location of the device when the card wallet accessory 347 was attached, or it may display a graphical object (e.g., a notification object overlapping part of a graphical user interface) confirming that the card wallet accessory 347 has been attached. In some cases, instead of detecting the card wallet accessory 347, or in addition to detecting it, device 346 may detect the content of the card wallet accessory 347. For example, a bank card may include a near-field radio communication antenna that device 346 can detect. In such a case, in response to detecting that the card wallet accessory 347 has been attached, device 346 may determine the identification of any near-field radio-enabled card in the card wallet accessory 347 and provide the user with content indication. As a specific example, the name, icon, or other indicator of each card in the card wallet accessory 347 may be displayed on the device's display so that the user can easily see which cards are available simply by looking at the display.

[0080] If device 346 can detect the presence or proximity of a card or other object within the card wallet accessory 347, it can also take certain actions in response to the detection that a card has been removed from the card wallet accessory 347. Figure 3I shows an example where a bank card 350 has been removed from the card wallet accessory 347. In response to the detection of removal, device 346 displays one or more graphical objects related to the removed card 350. For example, device 346 may display a first graphical object 352 which may be an image of the specific bank card 350 that was removed. Device 346 may also display a second graphical object 353 which may be recent purchase history associated with the bank card 350. Other types of information and / or graphical objects may be displayed instead of, or in addition to, those shown in Figure 3I.

[0081] In other cases, device 346 may take other actions, launch other applications, or display other types of graphical objects in response to detecting that a card (or card wallet accessory 347) has been removed from device 346. For example, device 346 may launch a wallet application or a financial application. Another example is that device 346 may open an application based on device 346's location when the card is removed. More specifically, since the removal of the bank card 350 may indicate that the user is about to make a purchase, device 346 may determine whether its location at that time corresponds to a store and open an application associated with that store. Yet another example is that when the card is removed, device 346 may determine whether there are any available coupons, deals, rewards, or other offers associated with a store near the user. Yet another example is that device 346 may associate a geographical location with the removal event, as described herein with respect to Figures 3O-3P.

[0082] Figures 3J–3L show other exemplary accessories configured to be attached to the device and / or a protective case for the device (e.g., on the back of the device or case). In particular, Figures 3J–3L show device 354 (which may be inside a protective case) and a battery accessory 355 configured to be detachably attached to the surface 357 of device 354 (e.g., the back). Device 354 may be device 100, or an embodiment of device 100, or may be the same as or similar to device 100.

[0083] The battery accessory 355 may include a near-field radio communication antenna 356 detectable by the near-field radio communication system of device 354. The battery accessory 355 may be configured to charge the battery of device 354 and / or to power device 354 in other ways. The battery accessory 355 may power device 354 via a cable, or it may include a wireless charging system with an output coil configured to inductively couple to the charging coil of electronic device 354 when the battery accessory 355 is detachably attached to device 354.

[0084] The battery accessory 355 may also include a magnetic mounting feature 362 configured to removably attach the battery accessory 355 to the device 354 via a complementary magnetic mounting feature 363 of the device 354. The magnetic mounting features 362, 363 may include magnets, ferromagnetic materials, and the like. The battery accessory 355 and the magnetic mounting features 362, 363 of the device 354 and the charging coil may be embodiments of the corresponding components described with respect to Figures 2A and 2B.

[0085] Figure 3K shows a battery accessory 355 detachably attached to the surface 357 of device 354. As described for other near-field wireless-enabled accessories, in response to detecting that the battery accessory 355 has been attached to device 354, device 354 may take action or change its operating mode. When the battery accessory 355 is attached, device 354 displays a graphical object (e.g., a notification object) that provides information to device 354 about the battery accessory 355 and / or its operation.

[0086] Figure 3L shows an exemplary graphical object 364 that may be displayed by device 354 in response to device 354 detecting, for example, that a battery accessory 355 has been attached to device 354. The graphical object 364 may be displayed as a box superimposed on another graphical user interface, application, etc., may disappear after a certain period of time, or may be dismissed by the user. The graphical object 364 may display information such as the battery charge level of the battery accessory 355 and the estimated time it will take for the battery accessory 355 to fully charge device 354 (as shown in Figure 3L). Other information may also be displayed, such as the battery's name or nickname, the name of the battery's owner, the battery status of the battery accessory 355, the predicted charge level of device 354 if the battery accessory 355 remains on device 354 for a certain period of time (e.g., 1 hour = 60% charge, 2 hours = 100%), or any other appropriate information.

[0087] Device 354 may also initiate an action in response to the detection of the removal of the battery accessory 355. For example, device 354 may display a graphical object (which may be similar in appearance and function to graphical object 364 and may include the remaining charge of the battery accessory 355 and the amount of charging time required for the battery accessory 355 to be fully charged). As another example, device 354 may associate a geographical location with the removal event, as described herein with respect to Figures 3O to 3P.

[0088] Figures 3M to 3N illustrate an example in which a device that detects a particular type of case may cause the device to display information related to that case. For example, as shown in Figures 3M to 3N, case 365 may include several parts or components that need to be assembled in a particular way to secure the case to the device. Thus, case 365 may include a near-field communication antenna so that the device can detect when case 365 is in use and provide assembly instructions and / or other information to the user.

[0089] As shown in Figure 3M, the case 365 includes a rear member 367 and a perimeter member 366. The rear member 367 is configured to cover and protect the rear of the device 100, and the perimeter member 366 protects the sides of the device and holds the rear member 367, the device 100, and the perimeter member 366 together. The rear member 367 may include a short-range radio antenna 368 detectable by the device 100, as described herein. The perimeter member 366 may have seams or discontinuities to allow the perimeter member 366 to expand to accommodate the device 100 and the rear member 367. To secure the case 365, the perimeter member 366 may be closed by closing the seams or discontinuities as indicated by arrow 370. The perimeter member 366 may also include a latch member 369 for securing the perimeter member 366 in a closed configuration.

[0090] Figure 3N shows case 365 in the initial stages of assembly. In particular, device 100 may be positioned on a rear member 367, which may result in the near-field communication antenna 368 on the rear member 367 being detected by the near-field communication system of device 100, which then causes a graphical output 371 to be displayed on the display 104 of device 100. The graphical output 371 may contain any appropriate text and / or graphical content. In some implementations, the graphical output 371 contains assembly instructions for case 365. For example, the graphical output 371 may show how to close the seams and secure the latch member 369 to lock the surrounding member 366 around the rear member 367 and device 100. In some cases, the latch member 369 may include a near-field communication antenna, and device 100 may be able to detect when the latch member 369 is in the latched or locked position. In response to detection that the latch member 369 is in the latched or fixed position, the device 100 may display a graphical object to indicate to the user that the case has been properly and / or completely assembled.

[0091] Instead of displaying assembly instructions, device 100 may, in response to detecting that it is being used with case 365, also display other graphical objects or graphical user interfaces, or otherwise change its operating mode. For example, case 365 may be a ruggedized case intended for use during outdoor recreational activities. Thus, device 100 may initialize a fitness application, a GPS application, or other application that reflects the user's estimated future activities. As described above, device 100 may use other sensors or information to determine which application or operating mode (if any) should be started while device 100 is inside case 365. For example, if device 100 detects that ruggedized case 365 is mounted close to the trail head of device 100, device 100 may start a hiking-related application (e.g., a GPS application, a fitness tracking application, etc.). If device 100 detects that the Ruggedise Case 365 is attached to device 100 in close proximity to a downhill ski facility, device 100 can start a ski-related application (e.g., a ski tracking application, a map of ski facilities, etc.).

[0092] As described above with respect to card wallet accessories and battery accessories, the device can take certain actions when it detects that an accessory has been removed from the device (or when the device is removed from a case, dock, or any other accessory). For example, the device can record the location of the device when the accessory was removed. This information can be useful in warning the user of unintentional removal of an accessory and in finding a lost accessory. Figures 3O to 3P show device 100 in use with accessory 372 (which may represent card wallet accessory 347, battery accessory 355, or any other near-field wireless-enabled accessory).

[0093] Figure 3O shows the accessory 372 and the attached device 100. When the accessory 372 is removed from the device 100 (or when the device 100 and the accessory 372 are separated), the device 100 can detect the removal by detecting the absence of the accessory 372's near-field radio antenna. In response to detecting the removal of the accessory 372, the device 100 can store information about the removal event. For example, the device 100 can determine the location of the device at the time of the removal of the accessory 372 and the time of the removal of the accessory 372. In some cases, the device 100 displays this (or other) information to the user at the time of removal. For example, as shown in Figure 3P, the device 100 can display a map 373 with a graphical indicator 375 representing the location where the accessory 372 and the device 100 were separated. The device 100 can also display text information 374. In some implementations, the text information 374 provides text indicating the location (e.g., address, latitude / longitude coordinates, etc.), the time of removal, and optionally other information.

[0094] Information regarding the removal of accessory 372 may be displayed to the user substantially immediately after the removal event is detected, or it may not be displayed and instead be recorded for later retrieval and / or viewing by the user. In either case, the information may be stored so that the user can retrieve and view it as needed.

[0095] Figures 3A to 3P show examples of protective cases and other accessories that use a passive antenna to change the operating mode of an electronic device when used with the electronic device. A similar principle may be applied to a device holder configured to hold or support a device during activity. Figure 4 shows two examples of a device holder or dock that may include a short-range radio communication antenna for changing the operating mode of device 100.

[0096] Figure 4 shows device 100 while displaying a first graphical user interface 404, which may be the primary graphical user interface of device 100, such as graphical user interface 128 (Figure 1B). Figure 4 also shows device 100 mounted on a dock 400 inside a vehicle. The dock 400 may include a short-range radio communication antenna that causes device 100 to switch from displaying the first graphical user interface 404 to displaying a second graphical user interface 401 that is adjusted for use while driving (for example, the device may stop displaying the first graphical user interface and start displaying the second graphical user interface). As with other accessories described herein, the transition may be automatic and seamless for the user, and the user may transition device 100 to a vehicle-specific graphical user interface by simply placing the device in the dock 400 (for example, so that the device is positioned on the dock or held by the dock).

[0097] The graphical user interface 401 may include large, easily viewable audio controls that are easy for the user to see and touch while driving. The graphical user interface 401 may also include a map or navigation view. In some cases, the graphical user interface 401 may include large, easy-to-read icons for various different applications or functions (e.g., radio, phone, maps, messages, etc.). Device 100 may also change other device settings as a result of detecting that it has been docked in 400. For example, device 100 may enter a “do not disturb” mode that can reduce the possibility of distraction while driving. This can turn off message notifications (e.g., text messages, emails, application notifications, etc.) so that the user is not inclined to type replies or read text-based messages while driving.

[0098] Figure 4 also shows the device 100 mounted on a bicycle dock 402. The dock 402 may include a short-range wireless communication antenna that causes the device 100 to stop displaying a first graphical user interface 404 and instead display a second graphical user interface 403 that is adapted for use during cycling. For example, the graphical user interface 403 displays speed, heart rate, and distance traveled. In some cases, placing the device 100 in the bike-mounted dock 402 may cause the device 100 to launch applications such as activity tracking applications, biometric monitoring applications (e.g., heart rate monitors), or map or positioning applications (e.g., GPS applications). In one case, placing device 100 in a bike-mounted dock 402 (or other exercise-related docks or accessories, such as a dock on a moving stroller or stationary bike, or an arm-mounted carrying case) causes device 100 to display affordances, which, when selected by the user, cause the device to start recording a workout associated with the exercise equipment associated with the dock (e.g., outdoor cycling, running, indoor cycling). In another example, by placing device 100 in a bike-mounted dock 402 (or other exercise-related docks or accessories), device 100 displays a list of several affordances (e.g., outdoor cycling, indoor cycling, outdoor running, etc.) that the user can select to start recording a workout.

[0099] Therefore, the graphical user interface 403 may be the graphical user interface for a particular application. In some cases, the graphical user interface 403 does not correspond to any single application, but instead displays output from various different applications or functions running on the device. For example, speed output and distance traveled may be provided by GPS or a cycling-specific application, and heart rate output may be provided by a biometric monitoring function or application. The graphical user interface 403 can use data from these applications without running or displaying dedicated graphical user interfaces for these applications.

[0100] Although the graphical user interface 403 is shown as having only outputs, it may also include, or instead of, selectable inputs such as large, easily visible and touchable audio controls, or large icons for various different applications or functions (e.g., radio, phone, maps, messaging, etc.). Device 100 may also change other device settings as a result of detecting that it has been docked in dock 402. For example, device 100 may enter a “do not disturb” mode that can reduce the possibility of distraction while cycling. This can turn off (or mute) message notifications (e.g., text messages, emails, application notifications, etc.) so that the user is not inclined to type replies or read text-based messages while cycling. In some implementations, when device 100 is used with other docks and / or accessories such as a home dock, protective case, charging dock, wallet accessory, or auxiliary battery accessory, message notifications are not turned off or muted (e.g., message notifications are displayed to the user or provided in other ways).

[0101] Device 100 may be attached to other types of docks. For example, device 100 may be integrated with exercise equipment such as stationary bikes, rowing machines, elliptical machines, or stair climbers, or attached to docks associated in other ways. When attached to exercise equipment, device 100 can detect the type of exercise equipment to which it is attached and initiate a coaching application or service associated with that particular equipment. Device 100 may also use additional information to determine which type of coaching application or service should be used, or whether a user interface that does not include a coaching service or interface should be displayed. For example, device 100 can use the device's location to determine whether it is attached to a stationary bike at the user's home or to a stationary bike at a fitness studio. If device 100 is attached to a home stationary bike, it may initiate a coaching application or service, but if it is attached to a bike at a fitness studio, it may not initiate a coaching application (for example, reflecting the fact that a fitness studio may have a live coach).

[0102] The accessories shown in Figures 3A to 4 may have features and physical properties that make them suitable for specific applications. For example, a rugged case may be designed for rough work environments, and a sports case may have straps to allow the case to be worn during training. These accessories may use a short-range wireless communication system to modify the device's operation, but they do not communicate or interact with device 100 in any other way. However, accessories using a short-range wireless communication system may have other components, systems, or mechanisms that interact or communicate with device 100 to extend the functionality of the accessory and / or device 100.

[0103] Figure 5 shows two examples of protective cases that include an input system that uses near-field wireless communication to cause device 100 to change its operating mode, communicates wirelessly with device 100, and provides auxiliary input to the user. For example, Figure 5 shows device 100 not attached to an accessory or inserted into a case, displaying a first graphical user interface 501 which may be the primary graphical user interface of device 100, such as graphical user interface 128 (Figure 1B). Figure 5 also shows device 100 after being inserted into camera case 500. As with other protective cases described herein, camera case 500 may include a near-field wireless communication antenna that causes device 100 to stop displaying its first graphical user interface and replace it with a second graphical user interface. In this case, since case 500 is configured to facilitate the use of the device's camera function, the second graphical user interface may be an image acquisition interface 508. The image capture interface 508 may include a preview of the scene to which the device's camera is pointed, as well as other selectable areas or input areas for controlling the manner of camera functions (e.g., flash settings, aperture, shutter speed, white balance, image capture type (e.g., video mode, still image mode, slow motion mode), self-timer settings, shutter button, front / rear camera selector, etc.). When the device 100 is inserted into the camera case 500, the device 100 may transition from the first graphical user interface 501 to the media capture interface 508 (e.g., a still image capture user interface or a video capture user interface), or, if the device's display is off when the device 100 is inserted into the camera case 500, the display may automatically turn on and immediately display the image capture interface 508.

[0104] The camera case 500 may also include an auxiliary input system, such as buttons 502, configured to control the image acquisition functions of device 100. For example, one of the buttons 502 may function as a shutter button to acquire an image or to start or stop video recording. As another example, buttons 502 may control zoom functions, aperture settings, shutter speed, or any other image acquisition functions. The camera case 500 may also have a button mechanism 506 that allows the user to activate buttons on device 100 itself. For example, the button mechanism 506 may include a movable button member (or membrane or material) that transmits force from the user's finger to button 108 on device 100 (Figure 1A) to mechanically activate button 108. In some cases, when device 100 is inserted into the camera case 500, detection of the camera case 500's near-field communication antenna causes device 100 to remap the input from button 108 from a first function, such as locking the phone and / or stopping the display, to a second function, such as a shutter button. This remapping can be performed whenever device 100 is inside the camera case 500 and device 100 is in image acquisition mode. That is, the user may leave image acquisition mode (and therefore leave the image acquisition interface 508) and use device 100 in other modes (for example, using the primary graphical user interface 501) while device 100 remains inside the camera case 500. In such circumstances, the device can revert button 108 to its default function and remap button 502 to other functions. When the user reinitializes the image acquisition interface, device 100 can use buttons 108 and 502 again to control the mode of image acquisition function of device 100.

[0105] An actuation signal from button 502 can be detected by device 100 in various ways. In some cases, button 502 uses near-field communication technology to provide input to device 100. For example, button 502 (or any other type of input system) may include an actuation member configured to be actuated by a user. The actuation member may be any component actuated by the user, such as a rigid button member or a membrane. Button 502 may further include a passive antenna, such as a near-field communication antenna. When the actuation member is actuated by a user (e.g., pressed), button 502 can make the near-field communication antenna detectable by an electronic device. For example, when button 502 is in a non-actuated state, the near-field communication antenna may be in a state or configuration that prevents the antenna from being detected by device 100. This may be caused by the antenna being electrically isolated from other circuit elements, grounded, electrically coupled to other circuit elements, or otherwise placed in a state where the near-field communication system of device 100 does not detect (and / or cannot detect) the antenna. In response to an actuation member being activated by a user, a passive antenna can become detectable by an electronic device. More specifically, a user activating the actuation member (e.g., by pressing the actuation member with a finger or other object) can change the electrical configuration of the antenna and / or associated circuitry to make the antenna detectable by the device. For example, pressing the actuation member closes an electrical contact, thereby connecting the antenna to a circuit element (e.g., a capacitor, inductor, resistor, etc.) and making the antenna detectable by the short-range wireless communication system of device 100. In another example, pressing the actuation member can open an electrical contact, thereby disconnecting the antenna to electrical ground. Other techniques can also be used to switch the antenna between a detectable and undetectable state.Furthermore, an operating signal may be wirelessly transmitted from the button 502 to the device 100 using other wireless communication protocols (e.g., Bluetooth®, Wi-Fi), acoustic signals (e.g., audible, ultrasonic), light, or other technologies.

[0106] Device 100 may be configured to perform an action in response to the detection of a passive antenna by the device's near-field communication system. For example, when a user presses or activates one of the buttons 502, the antenna associated with the button may be detected by the device 100's near-field communication system. The antenna may communicate information to device 100 that causes the device to perform functions such as capturing an image, zooming in or out on a scene or subject, or changing camera settings (e.g., aperture, shutter speed). The information communicated to device 100 by the antenna may be a command to perform a specific function, an identifier that device 100 uses to look up associated functions or commands, or any other suitable information.

[0107] Because the camera case 500 may include auxiliary inputs (or otherwise allow the user to operate camera functions differently than when the device 100 is not in the camera case 500), the image capture interface 508 may differ from the image capture interface displayed when the device 100 is not used with the camera case 500. For example, the default image capture interface for use without the camera case 500 may include a selectable shutter button object and other setting controls on the device's display. Because the camera case 500 may include physical buttons to control these functions, in some implementations, separate display-based controls for the functions are omitted from the image capture interface 508 (while in other implementations, display-based controls for the functions are displayed on the image capture interface 508 so that the user can use the display-based controls and / or physical buttons). The image capture interface 508 may also differ from the default image capture interface in other respects. An image capture interface 508 that displays shapes is shown, where the shapes represent a live preview of the camera (e.g., the image the camera captures when an image capture command (e.g., the shutter button) is received).

[0108] Game case 510 is another exemplary case in which a near-field wireless communication antenna may be used to change the device to an operating mode contextually relevant to the intended use of the case, and a near-field wireless communication system may be used to provide auxiliary inputs contextually relevant to the intended use of the case. For example, game case 510 may have a near-field wireless communication antenna that puts device 100 into game mode, which may include transitioning from a first graphical user interface to a game graphical user interface 516. In some implementations, the game graphical user interface 516 is a selection screen of game applications (represented by application icons having triangular, circular, and square shapes) that the user can select, but the game graphical user interface 516 may be any other type of interface. For example, attaching game case 510 to device 100 may cause device 100 to launch a single game application (which can be selected by the user), thereby bringing forth a dedicated graphical user interface for that game.

[0109] Similar to the camera case 500, the game case 510 may include auxiliary inputs 512, 514 that signal input events to device 100 using a near-field communication antenna. In some implementations, auxiliary input 512 is a directional pad (e.g., a generally plus-shaped input member that can be used to provide directional input), a joystick, an analog controller, etc. In some implementations, auxiliary input 514 is a button. Auxiliary inputs 512, 514 may use the same or similar techniques as button 502 to activate and / or deactivate the near-field communication antenna.

[0110] Device 100 may be configured to dynamically remap auxiliary inputs 512, 514 based on the active game, application, operating mode, or graphical user interface on Device 100. For example, when a user places Device 100 into the game case 510, Device 100 may enter a game mode or a graphical user interface, and auxiliary inputs 512, 514 may be mapped to game inputs (e.g., to control game characters or other aspects). If the user exits game mode while Device 100 is still inside the game case 510, auxiliary inputs 512, 514 may be remapped to other functions. For example, the directional pad 512 may control the position of a cursor on the display or change a selected object, and the buttons 514 may select items, launch applications, or switch the device between different applications or user interfaces. When the user returns to game mode, auxiliary inputs 512, 514 may be remapped to game functions.

[0111] While several examples of protective cases have been described above, these are only a few of the many types of accessories that can use near-field communication technology to automatically customize the operation of the device, and the associated changes to the operating mode of the device. As another example of an accessory, a protective case may include a keyboard that communicates wirelessly with the device. When device 100 is placed in a case with a keyboard, device 100 can be configured so that the on-screen keyboard does not appear when a text input field is selected or available, and so that input from the case's keyboard is used for text input. Device 100 may change its operating mode in other ways, including changing the autocorrection model and / or algorithm (e.g., from one adapted for touchscreen-based input to one adapted for physical key input from a keyboard), or changing the sound and / or tactile output associated with key presses. Device 100 may also, upon detecting a keyboard case, initiate a pairing sequence or otherwise initialize wireless communication with the keyboard. The keyboard can communicate with the device using any suitable communication technology or protocol, including wireless communication such as Wi-Fi, Bluetooth®, and near-field communication. In some implementations, the keyboard communicates with the device via a direct physical connection (e.g., a wired connection). In some cases, the keyboard may be associated with a keyboard dock or a standalone keyboard instead of a protective case. In such cases, the device 100's near-field communication system can detect when the device 100 is docked on the keyboard or otherwise in close proximity to the keyboard.

[0112] Another exemplary protective case may include a battery that can recharge the device 100 (either via a physical connector or wirelessly) while the device 100 is inside the case. When the device 100 is inserted into the case or used with the battery in any other way, the device 100 may display a notification indicating that the battery is installed and optionally provide selectable inputs for controlling the mode of charging (as shown with respect to Figure 2A). The device 100 may also record the location of the device 100 when the battery-compatible protective case is attached to or removed from the device 100.

[0113] The accessory does not need to be a protective case that surrounds or covers device 100. For example, a cardholder or wallet-type accessory may be configured to attach to the device (or protective case), and device 100 may use its near-field communication system to detect when the cardholder accessory is attached to and removed from the device. In response to detecting that the cardholder accessory has been attached, device 100 may customize the graphical user interface (for example, by changing the background color or image of the primary graphical user interface to match the color of the accessory, or by changing the color scheme or background of the graphical user interface of the digital wallet application to match the cardholder accessory). Device 100 may also use its near-field communication system to help the user identify when and where the cardholder accessory was removed from the device. For example, when device 100 detects that the cardholder accessory has been removed from device 100, device 100 may record the current time and the location of device 100 (for example, from GPS or another positioning system). Next, this information can be provided to the user to help them find the card holder accessory, or at least to know when and where the card holder accessory was lost or removed. For example, a notification showing the time and location (e.g., on a map) when the accessory was removed from device 100 may be provided on the device's display.

[0114] Some accessories, such as some of the cases described above, may be configured to cause device 100 to enter a specific operating mode or to start a specific application tailored for use in that case. For example, a camera case 500 may cause the device to start a camera application. In some cases, the user may be able to customize how the device behaves, such as what is presented on its graphical user interface when the device is used with different accessories. For example, device 100 may allow the user to create several different auxiliary graphical user interfaces, each containing desired interface components. The user can also associate the auxiliary graphical user interfaces with their respective accessories. For example, the user may create one auxiliary graphical user interface that is activated when the device is placed in a bedroom dock (e.g., displayed instead of the primary graphical user interface) and a second different graphical user interface that is activated when the device is placed in a kitchen dock. In some cases, the user may create many different auxiliary graphical user interfaces for many different use cases and accessories.

[0115] An auxiliary graphical user interface may be created by allowing the user to select from a group of candidate graphical objects. Figure 6 shows an exemplary group of candidate graphical objects, including, for example, an audio control object 600, a home automation object 602, a recipe object 604, a timer object 606, a calendar object 608, a channel guide and selection object 610, a clock object 612, a weather object 614, and a news distribution object 616. To create an auxiliary graphical user interface, the user may select graphical objects from the group of candidate graphical objects, associate them with specific locations on the display 104 of device 100 (e.g., define a user-defined arrangement), and associate the auxiliary graphical user interface with specific accessories. Graphical objects may have input objects, output objects, or both. In particular, the user may define a number of auxiliary graphical user interfaces, each having different objects or different combinations of objects (or having the same objects in different user-defined arrangements). For example, one auxiliary graphical user interface may include an audio control object, while another auxiliary graphical user interface may not have an audio control object. By providing such flexibility, users can generate highly customized and relevant auxiliary user interfaces for use with a wide variety of docks and accessories.

[0116] In some implementations, an auxiliary graphical user interface (AGUI) is associated with a specific dock or other accessory. For example, in some implementations, the user creates an AGUI (for example, by selecting a set of graphical objects from candidate graphical objects) and associates the created AGUI (for example, by creating the AGUI while the device is on the dock, by placing the device on the dock after creating the AGUI (for example, by manually associating the dock with the created AGUI (for example, by creating the AGUI while the device is on the dock, by placing the device on the dock after creating the AGUI (for example)). The user-created AGUI (for GUI) is then displayed when the device is placed on the dock. The same process can be used to create other customized AGUI (for GUI) interfaces associated with other docks.

[0117] The audio control object 600 may include an audio control input object ("Audio Control Input") for controlling the audio playback function of device 100 or any other device that device 100 can control. For example, the audio control input of the audio control object 600 may be configured to control the audio of a network-connected audio system that device 100 can control using network communication. The audio control object 600 may also have output objects such as indicators, such as media currently being played or queued, or album art.

[0118] The home automation object 602 may include input objects that allow a user to control networked home automation systems such as alarms, lighting, audio systems, and HVAC systems. The home automation object 602 may also include output objects that indicate the status of interconnected systems such as lighting, door sensors, and window sensors. As described above, in some implementations, a dock may be associated with a specific virtual room or environment within the home automation platform. Therefore, when a device is placed on a dock associated with a specific virtual room or environment, the home automation object 602 may display controls for the device that is also associated with that specific room or environment. For example, when a device is placed on a dock associated with and / or assigned to the "dining room" environment within the home automation platform, the home automation object 602 displayed may display controls for operating the dining room lighting, and when a device is placed on a dock associated with and / or assigned to the "living room" environment within the home automation platform, the home automation object 602 displayed may display controls for operating the living room lighting, as well as the television and audio systems. Therefore, users do not need to manually select individual devices (e.g., televisions, lighting sets, etc.) to associate with home automation objects (although in some cases this is also optional). In some implementations, home automation objects within an auxiliary graphical user interface include different controls based on the time of day. For example, a home automation object within an auxiliary graphical user interface for a bedroom dock might display controls for an audio system when the device is placed on the dock during the day, and controls for bedroom lighting and a home alarm system when the device is placed on the dock in the evening.

[0119] The recipe object 604 may display a cooking recipe or a list of recipes. The recipe object 604 may also provide a search interface for searching for recipes. The timer object 606 may provide inputs for setting a timer and selecting timer settings (e.g., alert tone, volume, etc.) and may display timer progress. The calendar object 608 may show a snapshot of the user's calendar items. The channel guide and selection object 610 may display a list of channels, shows, showtimes, or other television program information. The channel guide and selection object 610 may also provide input objects for controlling a television, DVR, DVD player, etc. The clock object 612 may display the current time. The weather object 614 may display the current weather conditions and / or weather forecast. The news distribution object 616 may display news headlines or articles.

[0120] The above represents only some of the possible graphical objects that may be provided to the user to create an auxiliary graphical user interface. In some cases, more, fewer, or additional graphical objects may be provided as well. Graphical objects may be associated with, or use, the functionality of other applications run by device 100. For example, a timer application (which may have its own separate graphical user interface) may provide timing functionality for timer object 606. In some cases, the functionality of multiple different applications may be included in a single graphical object. For example, a home automation graphical object 602 may control lighting using functionality provided by a lighting application (on device 100) and control an HVAC system using functionality from a separate thermostat application (on device 100).

[0121] Associating an auxiliary graphical user interface with a specific accessory may include associating the auxiliary graphical user interface with the identifier of the accessory's near-field communication antenna. For example, when a device is first placed on or used with an accessory, the device may prompt the user to create an auxiliary graphical user interface for use with that accessory. The device may then remember the association between the auxiliary graphical user interface and the accessory, and as a result, when the device detects the accessory in the future (for example, using the near-field communication described herein), the device will transition from displaying the first graphical user interface (whatever the graphical user interface is currently active) to displaying the auxiliary graphical user interface associated with that accessory.

[0122] In some cases, instead of an auxiliary graphical user interface that includes a set of graphical objects selected by the user, the user may associate a specific accessory or dock with a specific application. For example, a device may include dedicated applications for social networks, telephones, video phones, music players, etc. The user may select any given application that runs and / or is initialized when the device is placed in a particular dock. Thus, as an example, a user may associate a video phone application with a dock on their desk. Whenever the user places the device in that dock, the video phone application may be initialized (including, for example, displaying the graphical user interface of the video phone application on the device). In some cases, a telephone or video phone application may be configured to initiate a call or audio and / or video stream with another device in response to the device being placed in a particular dock. For example, when a user places a device in a dock on their work desk, a live video stream from the user's home security camera (or any other electronic device) may be displayed on the device. As another example, when a user places a device in a dock on their desk at home, a video call with another person may be initiated. As described above, in some implementations, specific applications, controls, and / or graphical objects that run and / or are displayed in response to a device located on or used with a dock or other accessory are based on the assignment of the dock or other accessory to a room within the home automation platform. Therefore, for example, if a device detects that it is located on a dock associated with or assigned to an "office" environment within the home automation platform, the device may run an application or similarly display controls associated with the "office" environment. In some cases, multiple docks or accessories may be associated with the same room or environment within the home automation platform.In such cases, different docks may cause the device to run or display different applications, controls, and / or graphical objects, even when associated with the same room or environment. In some implementations, the specific applications, controls, and / or graphical objects displayed and / or executed may be based on the characteristics or type of dock (e.g., an alarm clock dock in a bedroom may display alarm controls, and a charging dock in a bedroom may display lighting and audio controls), or on user selection (e.g., the user may specify that a first bedroom dock displays and / or runs a first set of applications, controls, and / or graphical objects, and a second bedroom dock displays and / or runs a second set of applications, controls, and / or graphical objects).

[0123] In some cases, multiple individuals may configure their devices and docks to initiate a video call or video conference whenever two or more of their devices are placed on a particular dock. For example, two users may configure their devices so that a video call (e.g., a live or streaming video feed) automatically (e.g., without further user input) starts when one user places their device on a specific dock and the other user's device is also on a dock. The video call may automatically end when either device is removed from its respective dock. This can provide an easy and efficient way for family, friends, and colleagues to communicate with each other. While the above example describes a communication link between two people, similar technology may be used for two or more users. For example, a group of colleagues could each configure their devices to initiate a video conference when their device is placed on a workplace dock. In this way, they can instantly collaborate with anyone else in their company or workgroup who is also available at that time. When a user no longer needs or wishes to communicate with the group, they can simply remove their phone from the dock. Users can even configure their devices to participate in different video conferences when they are docked in different locations. Thus, users can communicate with different groups simply by moving their devices to different docks. While the above examples primarily describe video conferences or video calls initiated by placing a device on a docking accessory, the same principle can be applied to audio-only communications (instead of video), and to other types of accessories such as protective cases, charging docks, charging mats, vehicle-mounted docks, or holders.

[0124] Figure 7 illustrates how various different auxiliary graphical user interfaces may be displayed on device 100, depending on which accessory or dock device 100 is placed on. Each dock shown in Figure 7 may include a near-field communication antenna that enables device 100 to detect when device 100 is placed on a support structure. Furthermore, each dock may include a support structure (e.g., structure 701 of dock 700) configured to hold the device in a visible orientation when the dock is on the surface of an object. The surface of the object may correspond to, for example, a table, counter, desk, nightstand, dresser, or any other suitable object surface. In this way, the device can be seen and interacted with, including enabling the user to touch and provide input to the device (such as by pressing a button or providing touch or stylus input on a touch sensor surface). Furthermore, the support structure can allow the user to simply place the device on and remove it from the support structure (and thus initiate different operating modes and / or graphical user interfaces) without additional steps such as pairing the device for communication, mechanically securing the device to or within the dock, or aligning and connecting electrical connectors.

[0125] Returning to Figure 7, when device 100 is placed on the first dock 700, device 100 can use its near-field communication system to detect the antenna of the first dock 700 and thereby determine that it is in proximity to (e.g., located on) the first dock 700. Then, based on its proximity to the first dock 700, device 100 can determine which operating mode to operate in (e.g., which auxiliary graphical user interface to display) and begin operating in the operating mode corresponding to the first dock 700 (e.g., display the graphical user interface associated with that dock). In the example shown in Figure 7, device 100 may display a first auxiliary graphical user interface 710 which may include channel guides and selection objects (e.g., enabling the user to view and select channels to watch on the television) and home automation objects (e.g., enabling the user to control home automation systems such as lighting, security systems, door locks, and thermostats). These graphical objects may be selected by the user to be displayed when device 100 is in this particular dock. For example, the first dock 700 may be located in the user's living room or entertainment room, where TV channel selection and home automation control are particularly useful to the user. Of course, the user can customize the graphical user interface for any dock in any location, so the content of the first auxiliary graphical user interface 710 is merely an example and may be customized by the user to suit the user's specific needs for a particular dock location.

[0126] The first auxiliary graphical user interface 710 may be displayed when device 100 is placed on the dock 700, regardless of what was displayed immediately before. For example, if device 100 is not displaying anything (e.g., display 104 is blank), display 104 may turn on and immediately display the first auxiliary graphical user interface 710. If device 100 is currently displaying the primary graphical user interface (e.g., the primary graphical user interface 128 in Figure 1B), the device may stop displaying the primary graphical user interface and instead display the first auxiliary graphical user interface 710.

[0127] When device 100 is placed in the second dock 702, device 100 may use its near-field communication system to detect the antenna of the second dock 702 and thereby determine that device 100 is in close proximity to the second dock 702 (e.g., placed on top of it). Then, based on its proximity to the second dock 702, device 100 may determine which operating mode to operate in (e.g., which auxiliary graphical user interface to display) and begin operating in the operating mode corresponding to the second dock 702 (e.g., displaying the graphical user interface associated with that dock). In the example shown in Figure 7, device 100 may display a second auxiliary graphical user interface 712 that can correspond to a live video stream captured by a remote electronic device and transmitted to device 100. More specifically, when device 100 is placed on the second dock 702, a live video link with another device may be automatically initiated. The live video link may be with another similar device enabling two-way audio and video communication (e.g., a mobile phone, tablet computer, laptop computer), or with a camera such as a security camera or webcam. Therefore, the second auxiliary graphical user interface 712 may accommodate video streaming from another camera. As another example, instead of automatically starting the live video link, placing device 100 on the second dock 702 may cause device 100 to display a list of contacts that the user can select, and then start live video or audio streaming with the selected contact. Device 100 may also activate a microphone or voice recognition scheme to accept verbal commands (e.g., "Call my mother"). As described above, the second auxiliary graphical user interface 712 may be displayed when device 100 is placed on the second dock 702, regardless of what was previously displayed on device 100.For example, device 100 may transition from a blank screen to a second auxiliary graphical user interface 712, or from another graphical user interface (e.g., a primary graphical user interface) to the second auxiliary graphical user interface 712.

[0128] When device 100 is placed in the third dock 704, device 100 may use its near-field communication system to detect the antenna of the third dock 704 and thereby determine that device 100 is in close proximity to the third dock 704 (e.g., placed on top of it). Then, based on its proximity to the third dock 704, device 100 may determine which operating mode to operate in (e.g., which auxiliary graphical user interface to display) and start operating in the operating mode corresponding to the third dock 704 (e.g., displaying the graphical user interface associated with that dock). In the example shown in Figure 7, device 100 may display a third auxiliary graphical user interface 714 which may include graphical objects related to the kitchen environment. For example, in some implementations, the third auxiliary graphical user interface 714 may include a recipe object that may allow the user to search for recipes, select from saved recipes, and read recipes. The third auxiliary graphical user interface 714 may also include a timer object and / or a measurement conversion object.

[0129] The activation of the third auxiliary graphical user interface 714 may also configure the device to respond to verbal commands (e.g., scrolling through or changing recipes, controlling a timer, etc.) so that the user does not need to touch the device 100 to operate the user interface during cooking, which could be unsanitary and could damage the device 100. Furthermore, automatic display stop can be disabled so that the display (and therefore recipes, timers, etc.) does not disappear without warning. Of course, other user-selectable graphical objects may be used instead of, or in addition to, those shown in the third auxiliary graphical user interface 714.

[0130] In some cases, a dock including a support structure for holding a device in a visible orientation may also include an input system configured to communicate wirelessly with the device in response to an input system activated by a user when the electronic device is placed on the support structure. For example, Figure 7 shows an exemplary alarm clock dock 706 including an input system such as a button 720. The button 720 may be similar to the one described with respect to Figure 5. For example, an activation signal from the button 720 can be detected by the device 100 in various ways. In some cases, the button 720 uses near-field communication technology to provide input to the device 100. For example, the button 720 (or any other type of input system) may include an activation member configured to be activated by a user, as well as a passive antenna such as a near-field communication antenna. When the activation member is activated by a user (e.g., pressed), the button 720 can make the near-field communication antenna detectable by the electronic device. For example, when the button 720 is in a non-activating state, the near-field communication antenna may be in a state or configuration that is not detectable by the device 100. This can be caused by the antenna being electrically isolated from other circuit elements, being grounded, being electrically coupled to other circuit elements, or otherwise being in a state where the device 100's short-range wireless communication system does not detect the antenna. In response to the actuation member being activated by the user, the passive antenna may become detectable by the electronic device. (An actuation signal may be wirelessly transmitted from button 502 to device 100 using other wireless communication protocols (e.g., Bluetooth®, Wi-Fi), acoustic signals (e.g., audible, ultrasonic), light, or other technologies.)

[0131] Similar to the other docks shown in Figure 7, placing device 100 on dock 706 may cause device 100 to display a fourth auxiliary graphical user interface 716. In some implementations, the fourth auxiliary graphical user interface 716 includes a clock and / or alarm clock graphical object. Thus, dock 706 may be suitable for placement in a user's bedroom. Button 720 may be configured to control or change settings of the clock and / or alarm clock graphical object, such as setting the alarm time, snoozing the alarm, or changing the display brightness (for example, temporarily activating the display so that the user can see the time at night). This can improve the experience of using the alarm function of device 100 by eliminating the need for the user to look at the device's display to find the location of a touch-sensitive snooze button or to control the alarm function in any other way.

[0132] In addition to transitioning to the fourth auxiliary graphical user interface 716 in response to being placed on the dock 706, device 100 may also change other device settings. For example, if the dock 706 is in a bedroom and is being used as an alarm clock, the device may also change notification settings (e.g., turn off audible, visible, and / or haptic notifications such as messages and events) and display settings (e.g., display brightness and display color content). Other device customizations are also possible when device 100 detects that it is on the dock 706.

[0133] Figure 7 shows several exemplary docks and associated auxiliary user interfaces, but other types of docks are also possible, including docks with different form factors, different target applications and / or locations, different configurations and types of auxiliary input systems, etc. For example, a dock may include a speaker (as dock 118 in Figure 1A) and allow device 100 to be directed to an auxiliary graphical user interface that includes music or audio control objects. As another example, a dock without a speaker may allow device 100 to be directed to an auxiliary graphical user interface that includes music or audio control objects and configures the device to control or connect to a wireless speaker system.

[0134] Another exemplary dock could transition device 100 to an auxiliary graphical user interface configured as a shared family device. This may include displaying objects for controlling shared calendars, task lists, reminder lists, etc. (e.g., among family members), as well as home functions such as security systems, thermostats, lighting, and music. In some implementations, shared information (e.g., among family members) corresponds to information shared between accounts, linked to a shared family account, which shares access to information and / or content (e.g., calendars, photos, contacts, etc.) and / or payment methods. In addition to transitioning to an auxiliary graphical user interface, the device may also have its settings modified, such as restricting access to a single user's personal content (e.g., messaging applications and features, etc.) or changing notification settings (e.g., turning off notifications or removing visible message previews).

[0135] Another exemplary dock may transition device 100 to an auxiliary graphical user interface configured as a voice-based digital assistant interface. This may include dynamically displaying the conversion of voice input, displaying content or graphical objects related to voice-based commands issued to device 100, etc. A dock configured to customize the device for use as a digital assistant may also include a microphone and / or speaker that can communicate with device 100 to enhance the device's audio capabilities.

[0136] Another exemplary dock could move device 100 to an auxiliary graphical user interface configured to control equipment wirelessly coupled to device 100, or otherwise configured to receive and / or respond to commands from device 100. For example, an auxiliary graphical user interface for controlling a washing machine could include control objects tailored to the washing machine's functions (e.g., water temperature, rotation cycle level, cycle time, dirt level). As another example, a user interface configured to control a coffee maker could include control objects tailored to the coffee maker's functions (e.g., brew start time, coffee concentration, grind size, water temperature). Naturally, the auxiliary user interface may be adapted for use with other equipment and devices.

[0137] Docks may also be provided in public places, businesses, or other locations where they may be used by many different users. Such docks may direct devices to auxiliary graphical user interfaces relevant to those locations and / or environments. For example, a restaurant may provide docks on tables that display a menu and / or ordering interface to the device when it is placed on the dock. Another example is an airport, which may have a dock at each gate that displays flight information for that gate to the device. Another example is a park, which may have docks at points of interest that display information or interactive applications relevant to those points of interest to the device. Shared docks as described above (in fact, any docks described herein) may also include wireless charging systems as described above with respect to Figures 2A and 2B.

[0138] As described above, the auxiliary user interface may be customized by the user and associated with a particular dock. In some cases, the dock may be configured to trigger a pre-popular auxiliary graphical user interface. For example, the dock may be sold as a “kitchen” dock, and the dock and / or devices usable with the dock may be configured to trigger an auxiliary graphical user interface including recipe objects and timer objects. The user may use the default auxiliary graphical user interface, or may modify and / or change the auxiliary graphical user interface in any way (e.g., with different cooking or kitchen-related objects, or so that the dock can be used in an entirely different context, such as on the user’s nightstand). Other types of “default” docks may also be provided, which can similarly trigger a tailored auxiliary graphical user interface. For example, the “bedroom” dock may, by default, trigger an interface with an alarm clock object, and the “living room” dock may, by default, trigger a television control object. Of course, these default auxiliary graphical user interfaces may be replaced or modified by the user using the modular user interface scheme described herein.

[0139] The docks, cases, and other accessories described herein can transition a device from one operating mode to another (including, for example, from one graphical user interface to another different graphical user interface), but the user can selectively return to the previous or different operating mode (and associated graphical user interface) while the device is still associated with the accessory. For example, when a device is placed on a kitchen dock, thus triggering a transition to a cooking-based user interface, the user can control the device to leave the cooking-based user interface and return to the primary graphical user interface while the device remains on the dock. As another example, the user can control the device to leave the cooking-based user interface and start a music playback interface instead. The user may also be able to choose whether or not a particular graphical user interface can be freely changed. For example, if a user places a device in a childproof case, the user may not want a child to be able to freely return to the primary user interface. Thus, the user may be able to choose which auxiliary graphical user interfaces (if any) may be freely available when the device is used with a particular accessory. A password or other authentication may be required to transition between auxiliary user interfaces.

[0140] In some cases, device 100 may transition from an auxiliary graphical user interface to a primary graphical user interface when device 100 is removed from the dock. For example, the near-field wireless communication system of device 100 may determine that the device is no longer close to the dock based on the fact that it no longer detects the dock's near-field wireless antenna. Once detection of the dock's near-field wireless antenna is stopped, device 100 may stop displaying the auxiliary graphical user interface (or any other graphical user interface associated with that dock) and start displaying the primary graphical user interface.

[0141] Figure 8 shows an exemplary schematic diagram of electronic device 800. For example, device 800 in Figure 8 may correspond to electronic device 100 (or any other electronic device described herein) shown in Figures 1A to 7. It should be understood that, insofar as multiple functions, operations, and structures are disclosed as being part of, incorporated into, or performed by device 800, various embodiments may omit some or all of the functions, operations, and structures described above. Therefore, various embodiments of device 800 may have, or may not have, some or all of the various capabilities, devices, physical features, modes, and operating parameters described herein. Furthermore, it should be understood that the details of electronic device 100 illustrated and / or described herein apply equally to electronic device 800. For example, device components (e.g., mounting mechanisms, housings, antennas, etc.), application software, graphical user interfaces, etc., can all be embodied by device 800. Furthermore, any of the components, hardware, software, or other systems or components described with respect to the electronic device 800 may be equally included in the electronic device 100.

[0142] As shown in Figure 8, device 800 includes a processing unit 802 operably connected to computer memory 804 and computer-readable medium 806. The processing unit 802 may be operably connected to the components of memory 804 and computer-readable medium 806 via an electronic bus or bridge. The processing unit 802 may include one or more computer processors or microcontrollers configured to perform operations in response to computer-readable instructions. The processing unit 802 may include the device's central processing unit (CPU). Additionally or alternatively, the processing unit 802 may include other processors within the device, including application-specific integrated chips (ASICs) and other microcontroller devices.

[0143] Memory 804 may include various types of non-temporary computer-readable storage media, such as read-access memory (RAM), read-only memory (ROM), erasable programmable memory (e.g., EPROM and EEPROM), or flash memory. Memory 804 is configured to store computer-readable instructions, sensor values, and other persistent software elements. Computer-readable media 806 also includes various types of non-temporary computer-readable storage media, such as hard drive storage devices, solid-state storage devices, portable magnetic storage devices, or other similar devices. Computer-readable media 806 may be configured to store computer-readable instructions, sensor values, and other persistent software elements.

[0144] In this embodiment, the processing unit 802 is operable to read computer-readable instructions stored in memory 804 and / or computer-readable medium 806. The computer-readable instructions may be provided as a computer program product, a software application, or the like.

[0145] As shown in Figure 8, device 800 also includes a display 808. Display 808 may include a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, a light-emitting diode (LED) display, or the same. If display 808 is an LCD, display 808 may also include a controllable backlight component to provide a variable display brightness level. If display 808 is an OLED or LED type display, the brightness of display 808 may be controlled by changing the electrical signals supplied to the display elements. Display 808 may correspond to any of the displays illustrated or described herein, such as display 104 (Figure 1A).

[0146] Device 800 may also include a battery 809 configured to supply power to the components of device 800. Battery 809 may include one or more energy storage cells linked together to provide an internal power supply. Battery 809 may be operably coupled to a power management circuit configured to supply appropriate voltage and power levels to individual components or groups of components within device 800. Battery 809 may be configured to receive power from an external source via the power management circuit, such as an AC power outlet, a charging dock (e.g., the wireless charging dock 200 in Figures 2A-2B), an auxiliary battery, or a battery-compatible protective case. Battery 809 can store the power it receives so that device 800 can operate for extended periods, ranging from several hours to several days, without connection to an external power source. The power management circuit may include wireless charging components, such as a charging coil that inductively couples to the output coil of a wireless charger to charge battery 809.

[0147] In some embodiments, device 800 includes one or more input devices 810. An input device 810 is a device configured to receive user input. One or more input devices 810 may include, for example, a rotatable input system, a push button, a touch-activated button, a keyboard, a keypad, etc. (including any combination of these or other components). In some embodiments, the input device 810 may provide dedicated or primary functions, including, for example, a power button, volume buttons, a home button, a scroll wheel, and a camera button.

[0148] Device 800 may also include a sensor 824. Sensor 824 may detect input provided by the user to one or more of the input devices 810 of device 800. Sensor 824 may also be a biometric sensor such as a heart rate sensor, an electrocardiogram sensor, a temperature sensor, or any other type of sensor. If sensor 824 is a biometric sensor, it may include a biometric sensing circuit, as well as a crown portion that conductively connects the user's body to the biometric sensing circuit. The biometric sensing circuit may include components such as a processor, capacitors, inductors, transistors, and analog-to-digital converters.

[0149] Device 800 may also include a touch sensor 820 configured to determine the location of a touch on the touch-sensitive surface of Device 800 (e.g., the input surface defined by the transparent cover 105). The touch sensor 820 may use or include capacitive sensors, resistive sensors, surface acoustic wave sensors, piezoelectric sensors, strain gauges, and the like. In some cases, the touch sensor 820 associated with the touch-sensitive surface of Device 800 may include a capacitive array of electrodes or nodes operating according to a mutual capacitance scheme or a self-capacitance scheme. The touch sensor 820 may be integrated with one or more layers of a display stack (e.g., the display 104 in Figure 1A) to provide touch-sensitive functionality for a touchscreen.

[0150] Device 800 may also include a force sensor 822 configured to receive and / or detect force inputs applied to the user input surface of Device 800 (e.g., the surface of the transparent cover 105). The force sensor 822 may use or include capacitive sensors, resistance sensors, surface acoustic wave sensors, piezoelectric sensors, strain gauges, and the like. In some cases, the force sensor 822 may include or be coupled to a capacitive sensing element that facilitates the detection of changes in the relative position of the force sensor components (e.g., deflection caused by force input). The force sensor 822 may be integrated with one or more layers of the display stack (e.g., display 104) to provide force sensing functionality for the touchscreen.

[0151] Device 800 may also include a communication port 828 configured to send and / or receive signals or electrical communications from an external or separate device. The communication port 828 may be configured to connect to an external device via a cable, adapter, or other type of electrical connector. In some embodiments, the communication port 828 may be used to connect Device 800 to an accessory including a dock or case, a stylus or other input device, a smart cover, a smart stand, a keyboard, or other devices configured to transmit and / or receive electrical signals.

[0152] Device 800 may also include a near-field communication system 812 (which may correspond to the near-field communication system 106 in Figure 1A). The near-field communication system may include one or more antennas and associated circuitry for detecting the presence of a near-field communication antenna. The near-field communication system 812 may be configured to operate using any suitable type or protocol of near-field communication, including but not limited to the Near Field Communication (NFC) protocol, the Radio Frequency Identification (RFID) protocol, or any other suitable type or protocol. The near-field communication system 812 may be configured to detect the near-field communication antenna through a single side of the device (e.g., the back) or through multiple sides (e.g., any combination of sides, including all sides).

[0153] Device 800 is described as having a specific set of components, but device 800 is not limited to the components described herein. For example, the device may include two or more components described with respect to Figure 8 or elsewhere in this application, and in fact may include other components not described herein.

[0154] The above description illustrates and describes various types of graphical objects that a device may display in response to detecting that it is being used with a short-range wireless-enabled accessory. Graphical objects may take the form of icons, graphical user interfaces, background images, notification objects (e.g., for temporary notifications), or include these. Graphical objects may be programmatically associated with any suitable application, program, or operating system of the device, and / or may arise from any suitable layer of the Open Systems Interconnection Model (OSI model). For example, if a device detects an accessory and, in response, temporarily displays a notification object on top of a primary graphical user interface of the operating system, the notification object may be programmatically associated with the operating system or may arise from the operating system. As another example, if a device detects an accessory and, in response, starts an application, the graphical user interface of the application may be programmatically associated with the application or may arise from the application (the application may be defined by or as a software program running on the operating system).

[0155] As described above, one aspect of the technology involves collecting and using data available from various sources to improve the usability of the devices described herein. This disclosure considers that in some cases, such collected data may include personal data that uniquely identifies a particular person, or personal data that can be used to contact a particular person or locate them. Such personal data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), birth dates, or any other identifying or personal information.

[0156] This disclosure acknowledges that such use of personal data in the technology may be for the benefit of the user. For example, personal data can be used for the benefit of the user. For example, personal data can be used to provide a customized graphical user interface and user experience. Furthermore, other uses of personal data that benefit the user are also intended by this disclosure. For example, health data and fitness data can be used to provide insights into the user's overall wellness, or as positive feedback to individuals using the technology to pursue wellness goals.

[0157] This disclosure assumes that entities involved in the collection, analysis, disclosure, transmission, storage, or other use of such personal data will adhere to a robust privacy policy and / or privacy practice. Specifically, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for the strict confidentiality of personal data. Such policies should be readily accessible to users and should be updated as data collection and / or use changes. Personal data from users should be collected for the lawful and legitimate use of the entity and should not be shared or sold for any other purpose. Furthermore, such collection / sharing should be carried out only after informing and obtaining the user's consent. In addition, such entities should consider taking all necessary steps to protect and secure access to such personal data and to ensure that others with access to the personal data faithfully adhere to those privacy policies and procedures. Furthermore, such entities may undergo third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal data collected and / or accessed, and should comply with applicable laws and standards, including jurisdiction-specific considerations. For example, in the United States, the collection or access to certain health data may be subject to federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA). On the other hand, health data in other countries may be subject to other regulations and policies and should be addressed accordingly. Therefore, different privacy practices should be maintained in each country with respect to different types of personal data.

[0158] Notwithstanding the foregoing, the Disclosure also envisions embodiments that allow users to selectively prevent the use of or access to personal data. Specifically, the Disclosure intends that hardware and / or software elements may be provided to prevent or prevent access to such personal data. For example, in the case of an advertising service, the technology could be configured to allow users to choose to "opt in" or "opt out" of participating in the collection of personal data during or at any time thereafter when registering for the service. In addition to providing "opt-in" and "opt-out" options, the Disclosure intends to provide notices regarding the access to or use of personal data. For example, users may be notified when downloading an app that will access their personal data, and then again immediately before the app accesses their personal data.

[0159] Furthermore, the intent of this disclosure is that personal data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data when it is no longer needed. In addition, and where applicable in certain health-related applications, data anonymization can be used to protect user privacy. De-identification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth), controlling the amount or specificity of data stored (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data across all users), and / or by other means.

[0160] Therefore, while this disclosure broadly covers the use of personal data to implement one or more of the disclosed embodiments, it is conceivable that these embodiments can also be implemented without requiring access to such personal data. That is, the various embodiments of the technology are not rendered inoperable by the absence of all or part of such personal data. For example, content can be selectively delivered to a user by inferring preferences based on only a minimal amount of non-personal data or personal information, such as content requested by the user's associated device, other non-personal data available in the content delivery service, or publicly available information.

[0161] When used herein, the phrase “at least one” preceding a set of items, along with the terms “and” or “or” separating any of the items, qualifies the list as a whole, rather than each individual element of the list. The phrase “at least one” does not require the selection of at least one of each item listed; rather, it allows for the meaning of including at least one of any of the items, and / or at least one of any combination of items, and / or at least one of each of the items. For example, the phrases “at least one of A, B, and C” or “at least one of A, B, or C” refer, respectively, to A only, B only, or C only, any combination of A, B, and C, and / or one or more of each of A, B, and C. Similarly, it should be understood that the order of elements presented for combined or separated lists provided herein should not be construed as limiting this disclosure to only that order.

[0162] In the preceding description, certain technical terms have been used for illustrative purposes to provide a complete understanding of the described embodiments. However, it will be apparent to those skilled in the art that specific details are not required to practice the described embodiments. Accordingly, the preceding descriptions of the specific embodiments described herein are presented for illustrative and explanatory purposes only. They are not intended to be exhaustive or to limit embodiments to the exact form disclosed. It will be apparent to those skilled in the art that many modifications and variations are possible considering the above teachings. Furthermore, where used herein to refer to the location of components, the above and below terms, or their synonyms, refer to the relative location of the components with reference to the drawings, not necessarily to an absolute location relative to an external reference.

Claims

1. It is a system, It is an electronic device, The enclosure includes a transparent cover, A display disposed beneath the transparent cover and configured to display a first graphical output, a second graphical output different from the first graphical output, and a third graphical output different from the first and second graphical outputs, An electronic device including a touch sensor disposed beneath the transparent cover and configured to detect touch input applied to the transparent cover, It is a protective case, A shell that defines a cavity and is configured to at least partially cover the enclosure of the electronic device when the electronic device is placed within the cavity, A protective case comprising: a first short-range wireless communication antenna coupled to the shell and detectable by the electronic device; A charging accessory including a second short-range wireless communication antenna detectable by the aforementioned electronic device, The aforementioned electronic device When the electronic device is placed in the cavity of the protective case, the first short-range wireless communication antenna is detected. The system is configured to initiate a first animation in response to the detection of the first short-range wireless communication antenna. The first animation is, Switching from the first graphical output to the second graphical output, This includes switching from the second graphical output to the first graphical output while the electronic device is located within the cavity of the protective case, The aforementioned electronic device The electronic device is placed in the cavity of the protective case, and the second near-field wireless communication antenna is detected when the charging accessory is coupled to the protective case. The system is configured to initiate a second animation in response to the detection of the second near-field wireless communication antenna when the electronic device is placed within the cavity of the protective case. The second animation described above is Switching from the first graphical output to the third graphical output, This includes switching the third graphical output to the first graphical output while the electronic device is still located within the cavity of the protective case and the charging accessory is still coupled to the protective case, system.

2. The aforementioned electronic device is a mobile phone. The protective case has an outer surface that has a color, The first graphical output includes a group of application icons and has a first color scheme. The second graphical output includes the group of application icons and has a second color scheme. The second color scheme differs from the first color scheme in that it corresponds to the color of the outer surface of the protective case. The system according to claim 1.

3. The aforementioned enclosure is The outer back surface of the aforementioned electronic device, The front outer surface of the aforementioned electronic device, The outer periphery of the electronic device, wherein the outer periphery extends from the outer back to the outer front, defines the outer periphery, The aforementioned shell is A window area configured to allow a user to touch the front outer surface of the electronic device when the electronic device is placed in the cavity, A back wall configured to at least partially cover the outer back surface of the electronic device, Further defining the side wall configured to at least partially cover the outer periphery of the electronic device, The system according to claim 1.

4. The aforementioned protective case is An operating member configured to be operated by the user, It further includes an input system including a passive antenna, After the short-range wireless communication antenna is detected, in response to the operating member being activated by the user, the passive antenna becomes detectable by the electronic device. The electronic device is configured to control the image acquisition function in response to the detection of the passive antenna. The system according to claim 1.

5. The system according to claim 4, wherein the passive antenna is undetectable by the electronic device when the operating member is not operating.

6. The aforementioned electronic device further includes a camera system, Controlling the image acquisition function includes causing the electronic device to acquire an image using the camera system. The system according to claim 4.

7. The first graphical output described above includes a first background image, The second graphical output includes a second background image that is different from the first background image. The system according to claim 1.

8. The second graphical output is displayed for a predetermined period of time. The system according to claim 1.

9. It is a system, The enclosure includes a transparent cover, A display positioned beneath the transparent cover and configured to display a first graphical output, a second graphical output different from the first graphical output, and a third graphical output different from the first and second graphical outputs, An electronic device including a touch sensor disposed beneath the transparent cover and configured to detect touch input applied to the transparent cover, A protective case comprising a cavity defined and a first short-range wireless communication antenna detectable by the electronic device, A charging accessory including a second short-range wireless communication antenna detectable by the aforementioned electronic device, The aforementioned electronic device When the electronic device is placed in the cavity of the protective case, the first short-range wireless communication antenna is detected. In response to the detection of the first short-range wireless communication antenna, the animation starts, The aforementioned animation is Switching from the first graphical output to the second graphical output, The process includes gradually fading out the second graphical output and displaying the first graphical output while the electronic device is located within the cavity of the protective case, The electronic device is placed in the cavity of the protective case, and the second near-field wireless communication antenna is detected when the charging accessory is coupled to the protective case. In response to the detection of the second short-range wireless communication antenna, the system switches from the first graphical output to the third graphical output. A system in which the electronic device is located within the cavity of the protective case, and the charging accessory is configured to switch from the third graphical output to the first graphical output while the protective case is coupled to the electronic device.

10. The second graphical output includes a color that matches the color of the protective case. The system according to claim 9.

11. The third graphical output includes a graphical object that includes the battery charge level of the electronic device. The system according to claim 9.

12. The electronic device is configured to be magnetically attracted to the protective case and the charging accessory. The system according to claim 9.

13. It is a system, The enclosure includes a transparent cover, A display positioned beneath the transparent cover and configured to display a graphical user interface, A mobile phone including a touch sensor positioned beneath the transparent cover and configured to detect touch input applied to the transparent cover, A shell that defines a cavity and is configured to at least partially cover the enclosure of the mobile phone when the mobile phone is placed inside the cavity, A protective case including a first short-range wireless communication antenna coupled to the shell and detectable by the mobile phone, A charging accessory including a second short-range wireless communication antenna detectable by the aforementioned mobile phone, The aforementioned mobile phone is When the mobile phone is placed inside the cavity of the protective case, the first short-range wireless communication antenna is detected. In response to the detection of the first near-field wireless communication antenna, the system is configured to display a first temporary graphical output while the mobile phone is placed in the cavity of the protective case, and after displaying the first temporary graphical output, to automatically return to the graphical user interface display while the mobile phone is still placed in the cavity of the protective case. The aforementioned mobile phone is The second near-field wireless communication antenna is detected when the mobile phone is placed in the cavity of the protective case and the charging accessory is coupled to the protective case. A system configured to display a second temporary graphical output in response to the detection of the second near-field wireless communication antenna when the electronic device is placed in the cavity of the protective case, and to automatically return to the display of the graphical user interface after displaying the second temporary graphical output, while the mobile phone is still placed in the cavity of the protective case and the charging accessory is still coupled to the protective case.

14. The protective case has an outer surface that has a color, The graphical output has a first color scheme, The first temporary graphical output is a second color scheme different from the first color scheme, and has a second color scheme corresponding to the color of the outer surface of the protective case. The system according to claim 13.

15. The graphical user interface includes a group of application icons, and the first temporary graphical output includes the group of application icons. The system according to claim 14.

16. The first temporary graphical output includes animated color effects, The system according to claim 13.

17. The animated color effect starts from one position on the display and moves to a second position on the display. The system according to claim 16.

18. The animated color effect moves across the display. The system according to claim 16.

19. The second temporary graphical output includes information on the battery charge status of the mobile phone. The system according to claim 13.

20. The first temporary graphical output is displayed for a predetermined period of time. The system according to claim 13.

Images