Context-Specific User Interface

Abstract

Embodiments of the present disclosure relate to context-specific user interfaces. A context-specific user interface for use with a portable multifunction device is disclosed. Methods for a context-specific user interface described herein provide an indication of time and, optionally, various additional information. Also disclosed are non-transitory computer-readable storage media, systems, and devices configured to perform the methods described herein.

Description

[0001] This application is a divisional application of the invention patent application with Chinese national application number 201510479088.4, application date August 3, 2015, and invention name “Context-Specific User Interface”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application Serial No. 62 / 032,562, filed August 2, 2014; U.S. Provisional Patent Application Serial No. 62 / 044,994, filed September 2, 2014; and U.S. Provisional Patent Application Serial No. 62 / 129,835; all of which are hereby incorporated by reference in their entireties.

[0004] This application is related to the following applications: International Patent Application Serial No. PCT / US2013 / 040087, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Moving a User Interface Object Based on an Intensity of a Press Input”; International Patent Application Serial No. PCT / US2013 / 040072, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Providing Feedback for Changing Activation States of a User Interface Object”; International Patent Application Serial No. PCT / US2013 / 040070, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface”; International Patent Application Serial No. PCT / US2013 / 040071, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface”; International Patent Application Serial No. PCT / US2013 / 040073, filed on May 8, 2013, entitled International patent application serial number PCT / US2013 / 040067, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013; and international patent application serial number PCT / US2013 / 040058, entitled “Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a User Contact,” filed on May 8, 2013;International patent application serial number PCT / US2013 / 040056, entitled “Device, Method, and Graphical User Interface for Scrolling Nested Regions,” filed on May 8, 2013; International patent application serial number PCT / US2013 / 040054, entitled “Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects,” filed on May 8, 2013; International patent application serial number PCT / US2013 / 069489, entitled “Device, Method, and Graphical UserInterface for Switching Between User Interfaces,” filed on November 11, 2013; and International patent application serial number PCT / US2013 / 069489, entitled “Device, Method, and Graphical UserInterface for Determining Whether to Scroll or Select International patent application serial number PCT / US2013 / 069486, entitled “Device, Method, and Graphical User Interface for Moving a Cursor According to a Change in an Appearance of a Control Icon with Simulated Three-Dimensional Characteristics,” filed on November 11, 2013; and international patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to DisplayOutput Relationships,” filed on November 11, 2013;International patent application serial number PCT / US2013 / 069479, entitled “Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture,” filed on November 11, 2013; International patent application serial number PCT / US2013 / 069472, entitled “Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies,” filed on November 11, 2013; International patent application serial number PCT / US2013 / 040108, entitled “Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object,” filed on May 8, 2013; International patent application serial number PCT / US2013 / 040109, entitled “Device, Method, and Graphical User Interface for Selecting User Interface Objects,” filed on May 8, 2013 and PCT / US2013 / 040053, entitled “Device, Method, and Graphical User Interface for Selecting Object within a Group of Objects”;U.S. patent application serial number 61 / 778,211, filed March 12, 2013, entitled “Device, Method, and Graphical User Interface for Facilitating User Interaction with Controls in a User Interface”; U.S. patent application serial number 61 / 778,191, filed March 12, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application”; U.S. patent application serial number 61 / 778,171, filed March 12, 2013, entitled “Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a User Contact”; U.S. patent application serial number 61 / 778,181, filed March 12, 2013, entitled “Device, Method, and Graphical User Interface for Scrolling Nested No. 61 / 778,179, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects”; No. 61 / 778,156, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies”; and No. 61 / 778,092, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Selecting Object Within a Group of Objects”.U.S. patent application serial number 61 / 778,418, filed on March 13, 2013, entitled “Device, Method, and Graphical User Interface for Switching Between User Interfaces”; U.S. patent application serial number 61 / 778,416, filed on March 13, 2013, entitled “Device, Method, and Graphical User Interface for Determining Whether to Scroll or Select Content”; U.S. patent application serial number 61 / 747,278, filed on December 29, 2012, entitled “Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and / or Haptic Feedback”; U.S. patent application serial number 61 / 747,278, filed on December 29, 2012, entitled “Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object with Visual and / or Haptic Feedback”; U.S. patent application serial number 61 / 747,278, filed on December 29, 2012, entitled “Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object with Visual and / or Haptic Feedback”; No. 61 / 778,414, filed on March 13, 2013, entitled “Device, Method, and Graphical User Interface for Selecting User Interface Objects”; No. 61 / 778,413, filed on March 13, 2013, entitled “Device, Method, and Graphical User Interface for Displaying Content Associated with a Corresponding Affordance”; No. 61 / 778,373, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Managing Activation of a Control Based on Contact Intensity”;U.S. patent application serial number 61 / 778,265, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Display States in Response to a Gesture”; U.S. patent application serial number 61 / 778,367, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Moving a User Interface Object Based on an Intensity of a Press Input”; U.S. patent application serial number 61 / 778,363, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships”; U.S. patent application serial number 61 / 778,364, filed on March 12, 2013, entitled “Device, Method, and Graphical User Interface for Providing Feedback for Changing Activation States of a User Interface No. 61 / 778,287, entitled “Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface,” filed on March 12, 2013; and No. 61 / 778,239, entitled “Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture,” filed on March 12, 2013.U.S. Patent Application Serial No. 61 / 688,227, filed May 9, 2012, entitled “Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and / or Haptic Feedback”; U.S. Provisional Patent Application Serial No. 61 / 645,033, filed May 9, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices”; U.S. Provisional Patent Application Serial No. 61 / 665,603, filed June 28, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices”; and U.S. Provisional Patent Application Serial No. 61 / 681,098, filed August 8, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices”; U.S. Provisional Patent Application Serial No. 61 / 681,098, filed August 8, 2012, entitled “Reduced-Size Interfaces for Managing No. 62 / 044,894, entitled “Stopwatch and Timer User Interfaces,” filed on September 2, 2014; No. 62 / 044,979, entitled “Stopwatch and Timer User Interfaces,” filed on September 2, 2014; No. 62 / 026,532, entitled “Raise Gesture Detection in a Device,” filed on July 18, 2014; and No. 14 / 476,700, entitled “Crown Input for a Wearable Electronic Device,” filed on September 3, 2014. The contents of these applications are hereby incorporated by reference in their entirety. Technical Field

[0005] The present disclosure relates generally to computer user interfaces, and more particularly to a context-specific user interface for indicating time. Background Art

[0006] In addition to various operations, including running software applications, users rely on portable multifunction devices for timekeeping. It would be desirable to allow users to access information through a single user interface, while making the interface simple and intuitive to use. Furthermore, users may want to access different types of information, such as various aspects of timekeeping in different contexts or different application data points. It would also be desirable to allow users to customize the user interface and the type of information provided through the user interface. Summary of the Invention

[0007] Portable multifunction devices can provide a lot of different types of information and interfaces to users, and users can wish to customize these user interfaces and the types of information they provide in different contexts. Therefore, context-specific user interfaces for counting time are increasingly desirable.

[0008] However, some techniques for managing (e.g., editing) context-specific user interfaces for indicating time using electronic devices are often cumbersome and ineffective. For example, existing techniques use complex and time-consuming user interfaces that may include multiple buttons or keystrokes. These techniques require unnecessary time, wasting user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0009] Therefore, the present invention especially provides the benefit of the portable electronic device with faster, more effective method and interface for managing situation-specific user interface.Such method and interface optionally supplement or replace other methods for managing situation-specific user interface.Such method and interface reduce the cognitive burden of the user, and produce more effective man-machine interface.Such method and interface can also reduce unnecessary, irrelevant, repeated and / or redundant input, and can reduce the number of required input, reduce processing power and reduce the time amount that needs to display user interface so that access and realize desired function.For battery-powered computing device, such method and interface save power, and increase the time between battery charging.

[0010] The above-mentioned defects and other problems are reduced or eliminated by the disclosed device, method and computer-readable medium. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (for example, a notebook computer, a tablet computer or a handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or a "touch screen display"). In some embodiments, the device has a hardware input mechanism, such as a depressible button and / or a rotatable input mechanism. In some embodiments, the device has a graphical user interface (GUI), one or more processors, a memory and one or more modules, programs or instruction sets for performing multiple functions stored in the memory. In some embodiments, the user interacts with the GUI by finger contacts and gestures on the touch-sensitive surface and / or by rotating the rotatable input mechanism and / or by pressing a depressible hardware button. In some embodiments, the functions optionally include image editing, drawing, presentation, word processing, website creation, disk production, spreadsheet production, games, phone calls, video conferencing, email, instant messaging, training support, digital video, digital photography, web browsing, digital music playback and / or digital video playback. Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0011] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device having a display: receiving data representing user input, and in response to receiving the data: displaying a user interface screen on the display, the user interface screen including a clock face indicating a first time, wherein the first time is before a current time; and updating the user interface screen by animating the clock face to transition from indicating the first time to indicating the current time, wherein the animation represents the change in time from the first time to the current time.

[0012] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: displaying a clock face indicating the current time on the touch-sensitive display, the clock face including: a user interface object including an hour hand and a minute hand, wherein the user interface object indicates the current time, one or more hour time scale indications and a stopwatch hand; receiving data representing user input; and in response to receiving the data: replacing the one or more hour time scale indications with an indication of a first time scale of the stopwatch hand; and animating the stopwatch hand to reflect the change of time.

[0013] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: displaying a user interface screen on the touch-sensitive display, the user interface screen including: a first affordance representing a simulation of a first area of the Earth illuminated by the sun at a current time; receiving user input; and in response to receiving the user input: rotating the simulation of the Earth to display a second area of the Earth illuminated by the sun at the current time.

[0014] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: displaying a user interface screen on the touch-sensitive display, the user interface screen including: a first portion of the user interface screen, the first portion indicating daytime; a second portion of the user interface screen, the second portion indicating nighttime; a user interface object, the user interface object representing a sine wave having a period representing a day, wherein the sine wave indicates a path of the sun during the day, and wherein the sine wave is displayed in one or more of the first portion and the second portion; a first affordance representing the sun, wherein the first affordance is displayed at a first position on the displayed sine wave, the first position indicating a current time of day and whether the current time of day is during daytime or nighttime; and a second affordance, the second affordance indicating the current time of day.

[0015] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: displaying a user interface screen on the display, the user interface screen comprising: an image-based background, the background comprising a plurality of pixels, wherein a subset of the pixels is modified in appearance relative to the image such that the subset of pixels represents one or more of: a first user interface object indicating a date and a second user interface object indicating a time of day.

[0016] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device with a display: accessing a folder, the folder including two or more images; selecting a first image from the folder; and displaying a user interface screen on the display, the user interface screen including: a background based on the first image, the background including a plurality of pixels, wherein a subset of the pixels is modified in appearance relative to the image such that the subset of pixels represents one or more of: a first user interface object indicating a date and a second user interface object indicating a time of day.

[0017] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: detecting user input, wherein the user input is detected at a first time, and in response to detecting the user input: displaying a user interface screen, the user interface screen including: a first user interface object indicating the first time; and a second user interface object; and animating the second user interface object, the animation presentation including a sequence of the first animation presentation, a sequence of the second animation presentation following the sequence of the first animation presentation, and a sequence of the third animation presentation following the sequence of the second animation presentation, wherein the sequence of the first animation presentation, the sequence of the second animation presentation, and the sequence of the third animation presentation are different; after animating the second user interface object, detecting a second user input, wherein the second User input is detected at a second time, where the second time is after the first time, and in response to detecting the second user input: data representing a previously displayed second animated sequence is accessed; a fourth animated sequence is selected, where the fourth animated sequence is different from the first animated sequence and the second animated sequence; a second user interface screen is displayed, the second user interface screen comprising: a first user interface object, where the first user interface object is updated to indicate the second time; and a third user interface object related to the second user interface object; and animating the third user interface object, the animation presentation comprising a sequential display of a sequence of the first animated sequence, a sequence of the fourth animated sequence following the sequence of the first animated sequence, and a sequence of the third animated sequence following the sequence of the fourth animated sequence.

[0018] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: detecting user movement of the electronic device; and in response to detecting the movement: displaying an animated presentation of a clock face, wherein the animated presentation includes: displaying an hour hand and a minute hand; displaying a first hour indication and displaying a second hour indication after displaying the first hour indication, wherein the second hour indication is displayed on the clock face at a position after the first hour indication in a clockwise direction.

[0019] In some embodiments, a method for indicating time using a character-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a character user interface object on the display, the character user interface object including representations of a first limb and a second limb, wherein the character user interface object indicates a first time by indicating a first hour using the first limb and indicating a first minute using the second limb; and updating the character user interface object to indicate a second time, wherein the character user interface object indicates the second time by indicating a second hour using the second limb and indicating a second minute using the first limb.

[0020] In some embodiments, a method for indicating time using a character-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a character user interface object on the display, the character user interface object including a representation of a limb, the limb including: a first endpoint of the limb having a first position and a second endpoint of the limb having a second position, wherein the first endpoint of the limb is the axis of rotation of the limb and the position of the second endpoint of the limb indicates a first time value; and updating the character user interface object to indicate a second time value, wherein updating the character user interface object includes moving the first endpoint of the limb to a third position and moving the second endpoint of the limb to a fourth position to indicate the second time value.

[0021] In some embodiments, a method for indicating time using a character-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a character user interface object on the display, the character user interface object including a representation of a limb, the limb including a first segment of the limb and a second segment of the limb, wherein the first segment of the limb connects a first endpoint of the limb to a joint of the limb, the first endpoint of the limb having a first position, and wherein the second segment of the limb connects a second endpoint of the limb to the joint of the limb, the second endpoint of the limb having a second position, wherein the joint of the limb is an axis of rotation for the second segment of the limb, and wherein the position of the second endpoint of the limb indicates a first time value, and updating the character user interface object to indicate a second time value, wherein the update includes moving the second endpoint of the limb to a third position along the axis of rotation of the second segment of the limb to indicate the second time.

[0022] In some embodiments, a method for indicating time using a character-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a character user interface object on the display, wherein the character user interface object indicates time; receiving first data indicating an event; determining whether the event satisfies a condition; and based on a determination that the event satisfies the condition: updating the displayed character user interface object by changing a visual aspect of the character user interface object.

[0023] In some embodiments, a method for indicating time using a character-based user interface includes: at an electronic device having a display and a touch-sensitive surface: setting the display to an inactive state; receiving first data indicating an event; in response to receiving the first data: setting the display to an active state; displaying a character user interface object on a side of the display; animating the character user interface object toward the center of the display; and displaying the character user interface object at the center of the display in a position indicating the current time.

[0024] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: a clock face and an affordance, wherein the affordance represents an application, wherein the affordance includes a set of information obtained from the application, wherein the set of information is updated based on data from the application, and wherein the affordance is displayed as a complication on the clock face; detecting contact on the displayed affordance; and in response to detecting the contact: launching the application represented by the affordance.

[0025] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device having a touch-sensitive display configured to detect contact intensity: displaying a user interface screen including a clock face on the touch-sensitive display; detecting a contact on the touch-sensitive display, the contact having a characteristic intensity, and in response to detecting the contact: determining whether the characteristic intensity is above an intensity threshold; and based on the determination that the characteristic intensity is above the intensity threshold: entering a clock face editing mode of the electronic device; visually distinguishing the displayed clock face to indicate editing mode; and detecting a second contact on the touch-sensitive display, wherein the second contact is on the visually distinguished displayed clock face, and in response to detecting the second contact: visually indicating an element of the clock face for editing.

[0026] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device having a touch-sensitive display configured to detect contact intensity: displaying a user interface screen including a clock face on the touch-sensitive display; detecting contact on the touch-sensitive display, the contact having a characteristic intensity, and in response to detecting the contact: determining whether the characteristic intensity is above an intensity threshold; and based on the determination that the characteristic intensity is above the intensity threshold: entering a clock face selection mode of the electronic device; visually distinguishing the displayed clock face to indicate a clock face selection mode, wherein the displayed clock face is centered on the display; and detecting a swipe on the touch-sensitive display, and in response to detecting the swipe: centering a second clock face on the display.

[0027] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having a touch-sensitive display and a rotatable input mechanism: displaying a user interface screen on the touch-sensitive display, the user interface screen including: a clock face; and an affordance on the clock face, the affordance indicating a first time of day; detecting contact on the touch-sensitive display; and in response to detecting the contact: entering a user interaction mode of the electronic device, detecting movement of the rotatable input mechanism while the electronic device is in the user interaction mode, and in response to detecting the movement: updating the affordance to indicate a second time of day; detecting a second contact on the touch-sensitive display at the affordance indicating the second time, and in response to detecting the second contact: setting a user reminder for the second time of day.

[0028] In some embodiments, a method for providing a context-specific user interface includes: at an electronic device with a touch-sensitive display: displaying a user interface screen on the display, the user interface screen including multiple affordances, the multiple affordances including a first affordance, wherein the first affordance indicates a clock face, the clock face including: a time indication and an outline; detecting contact on the displayed first affordance; and in response to detecting the contact: replacing display of the user interface screen with a second user interface screen, wherein the replacement includes maintaining one or more of the time indication and the outline, wherein the maintained time indication or outline is displayed on the second user interface screen at a size larger than the first user interface screen.

[0029] In some embodiments, a device includes a device for receiving data representing user input; a device for displaying a user interface screen on a display in response to receiving the data, the user interface screen including a clock face indicating a first time, wherein the first time is before a current time; and a device for updating the user interface screen by animating the clock face to transition from indicating the first time to indicating the current time, wherein the animation represents the change in time from the first time to the current time.

[0030] In some embodiments, a device includes a device for displaying a clock face indicating the current time on a touch-sensitive display, the clock face comprising: a user interface object including an hour hand and a minute hand, wherein the user interface object indicates the current time, one or more hour time scale indications and a stopwatch hand; a device for receiving data representing user input; a device for replacing the one or more hour time scale indications with an indication of a first time scale of the stopwatch hand in response to receiving the data; and a device for animating the stopwatch hand to reflect the change of time.

[0031] In some embodiments, a device includes means for displaying a user interface screen on a touch-sensitive display, the user interface screen comprising: a first available feature representing a simulation of a first area of the Earth illuminated by the sun at the current time; means for receiving user input; and means for rotating the simulation of the Earth to display a second area of the Earth illuminated by the sun at the current time in response to receiving the user input.

[0032] In some embodiments, a device includes a device for displaying a user interface screen on a touch-sensitive display, the user interface screen comprising: a first portion of the user interface screen, the first portion indicating daytime; a second portion of the user interface screen, the second portion indicating nighttime; a user interface object, the user interface object representing a sine wave having a period representing a day, wherein the sine wave indicates a path of the sun during the day, and wherein the sine wave is displayed in one or more of the first portion and the second portion; a first affordance representing the sun, wherein the first affordance is displayed at a first position on the displayed sine wave, the first position indicating a current time of day and whether the current time of day is during daytime or nighttime; and a second affordance, the second affordance indicating the current time of day.

[0033] In some embodiments, a device includes means for displaying a user interface screen on a display, the user interface screen comprising: a background based on an image, the background comprising a plurality of pixels, wherein a subset of the pixels is modified in appearance relative to the image such that the subset of pixels represents one or more of: a first user interface object indicating a date and a second user interface object indicating a time of day.

[0034] In some embodiments, a device includes a device for accessing a folder, the folder including two or more images; a device for selecting a first image from the folder; and a device for displaying a user interface screen on a display, the user interface screen including: a background based on the first image, the background including a plurality of pixels, wherein a subset of the pixels is modified in appearance relative to the image so that the subset of pixels represents one or more of: a first user interface object indicating a date and a second user interface object indicating a time of day.

[0035] In some embodiments, a device includes a device for detecting user input, wherein the user input is detected at a first time; a device for displaying a user interface screen in response to detecting the user input, the user interface screen including: a first user interface object indicating the first time; and a second user interface object; a device for animating the second user interface object, the animation presentation including a sequence of a first animation presentation, a sequence of a second animation presentation following the sequence of the first animation presentation, and a sequence of a third animation presentation following the sequence of the second animation presentation, wherein the sequence of the first animation presentation, the sequence of the second animation presentation, and the sequence of the third animation presentation are different; a device for detecting a second user input, wherein the second user input is detected at a second time, wherein the second time is at the first time. after a second time; a device for accessing data representing a previously displayed second animated sequence in response to detecting a second user input; a device for selecting a fourth animated sequence, wherein the fourth animated sequence is different from the first animated sequence and the second animated sequence; a device for displaying a second user interface screen, the second user interface screen comprising: a first user interface object, wherein the first user interface object is updated to indicate a second time; and a third user interface object related to the second user interface object; and a device for animating the third user interface object, the animation presentation comprising a sequential display of a sequence of the first animated sequence, a sequence of the fourth animated sequence following the sequence of the first animated sequence, and a sequence of the third animated sequence following the sequence of the fourth animated sequence.

[0036] In some embodiments, a device includes means for detecting user movement of the device; means for displaying an animated presentation of a clock face in response to detecting the movement, wherein the animated presentation includes: displaying hour and minute hands and displaying a first hour indication; and means for displaying a second hour indication, wherein the second hour indication is displayed on the clock face at a position subsequent to the first hour indication in a clockwise direction.

[0037] In some embodiments, a device includes means for displaying a user interface screen on a display, the user interface screen comprising: a clock face and an affordance, wherein the affordance represents an application, wherein the affordance comprises a set of information obtained from the application, wherein the set of information is updated based on data from the application, and wherein the affordance is displayed as a complication on the clock face; means for detecting contact on the displayed affordance; and means for launching the application represented by the affordance in response to detecting the contact.

[0038] In some embodiments, a device includes a device for displaying a user interface screen including a clock face on a touch-sensitive display; a device for applying detection of a contact on the touch-sensitive display, the contact having a characteristic intensity; a device for determining whether the characteristic intensity is above an intensity threshold in response to detecting the contact; a device for entering a clock face editing mode of the electronic device based on the determination that the characteristic intensity is above the intensity threshold; a device for visually distinguishing the displayed clock face to indicate the editing mode; a device for detecting a second contact on the touch-sensitive display, wherein the second contact is on the visually distinguished displayed clock face; and a device for visually indicating an element of the clock face for editing in response to detecting the second contact.

[0039] In some embodiments, a device includes a device for displaying a user interface screen including a clock face on a touch-sensitive display; a device for detecting contact on the touch-sensitive display, the contact having a characteristic intensity; a device for determining whether the characteristic intensity is above an intensity threshold in response to detecting the contact; a device for entering a clock face selection mode of the electronic device based on the determination that the characteristic intensity is above the intensity threshold; a device for visually distinguishing the displayed clock face to indicate a clock face selection mode, wherein the displayed clock face is centered on the display; a device for detecting a swipe on the touch-sensitive display; and a device for centering a second clock face on the display in response to detecting the swipe.

[0040] In some embodiments, a device includes a device for displaying a user interface screen on a touch-sensitive display, the user interface screen including: a clock face; and an affordance on the clock face, the affordance indicating a first time of day; a device for detecting contact on the touch-sensitive display; a device for entering a user interaction mode of the electronic device in response to detecting contact; a device for detecting movement of a rotatable input mechanism when the electronic device is in the user interaction mode; a device for updating the affordance to indicate a second time of day in response to detecting movement; a device for detecting a second contact on the touch-sensitive display at the affordance indicating the second time; and a device for setting a user reminder for the second time of day in response to detecting the second contact.

[0041] In some embodiments, a device includes a device for displaying a user interface screen on a display, the user interface screen including a plurality of affordances, the plurality of affordances including a first affordance, wherein the first affordance indicates a clock face, the clock face comprising: a time indication and an outline; a device for detecting contact on the displayed first affordance; and a device for replacing display of the user interface screen with a second user interface screen in response to detecting the contact, wherein the replacement includes maintaining one or more of the time indication and the outline, wherein the maintained time indication or outline is displayed on the second user interface screen at a size larger than the first user interface screen.

[0042] In some embodiments, a method includes: receiving data related to a first subject; displaying first information related to a first portion of the received data; detecting a first rotation of a rotatable input mechanism; and in response to detecting the first rotation of the rotatable input mechanism, supplementing the first information with second information related to a second portion of the received data.

[0043] In some embodiments, a non-transitory computer-readable storage medium includes instructions for: receiving data related to a first subject; displaying first information related to a first portion of the received data; detecting a first rotation of a rotatable input mechanism; and in response to detecting the first rotation of the rotatable input mechanism, supplementing the first information with second information related to a second portion of the received data.

[0044] In some embodiments, a transient computer-readable storage medium includes instructions for: receiving data related to a first subject; displaying first information related to a first portion of the received data; detecting a first rotation of a rotatable input mechanism; and in response to detecting the first rotation of the rotatable input mechanism, supplementing the first information with second information related to a second portion of the received data.

[0045] In some embodiments, a device includes: a display; a rotatable input mechanism; one or more processors; and a memory. In some embodiments, the memory stores instructions that, when executed by the one or more processors, cause the one or more processors to: receive data related to a first subject; display first information related to a first portion of the received data; detect a first rotation of the rotatable input mechanism; and, in response to detecting the first rotation of the rotatable input mechanism, supplement the first information with second information related to a second portion of the received data.

[0046] In some embodiments, a device includes: a device for receiving data related to a first subject; a device for displaying first information related to a first portion of the received data; a device for detecting a first rotation of a rotatable input mechanism; and a device for supplementing the first information with second information related to a second portion of the received data in response to detecting the first rotation of the rotatable input mechanism.

[0047] In some embodiments, an electronic device includes: a display unit; a rotatable input mechanism unit; and a processing unit coupled to the display unit and the rotatable input mechanism unit. In some embodiments, the processing unit is configured to: receive data related to a first subject; enable display of first information related to a first portion of the received data on the display unit; detect a first rotation of the rotatable input mechanism; and, in response to detecting the first rotation of the rotatable input mechanism, supplement the first information with second information related to a second portion of the received data.

[0048] In some embodiments, a method at an electronic device with a display includes: obtaining first event data from a first application; obtaining second event data from a second application different from the first application; determining a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and displaying a user interface on the display, the user interface including: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the corresponding values of the first time value and the second time value.

[0049] In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by an electronic device with a touch-sensitive display, cause the device to: obtain first event data from a first application; obtain second event data from a second application different from the first application; determine a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and display a user interface on the display, the user interface comprising: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the respective values of the first time value and the second time value.

[0050] In some embodiments, a transient computer-readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by an electronic device with a touch-sensitive display, cause the device to: obtain first event data from a first application; obtain second event data from a second application different from the first application; determine a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and display a user interface on the display, the user interface comprising: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the respective values of the first time value and the second time value.

[0051] In some embodiments, an electronic device comprises: a touch-sensitive display; one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions that, when executed by the one or more processors, cause the device to: obtain first event data from a first application; obtain second event data from a second application different from the first application; determine a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and display a user interface on the display, the user interface comprising: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the corresponding values of the first time value and the second time value.

[0052] In some embodiments, an electronic device includes: a device for obtaining first event data from a first application; a device for obtaining second event data from a second application different from the first application; a device for determining a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and a device for displaying a user interface on a touch-sensitive display of the device, the user interface including: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the corresponding values of the first time value and the second time value.

[0053] In some embodiments, an electronic device includes: a display unit configured to display a graphical user interface; a touch-sensitive surface unit configured to receive contact; and a processing unit coupled to the display unit, the touch-sensitive surface unit, the rotatable and pressable input mechanism unit, and the button unit, the processing unit being configured to: obtain first event data from a first application; obtain second event data from a second application different from the first application; determine a first time value associated with the first event data and a second time value associated with the second event data and a relative order of the first time value and the second time value; and display a user interface on a display, the user interface including: a representation of the first event data accompanied by a representation of the first time value; and a representation of the second event data accompanied by a representation of the second time value, wherein the representation of the first event data and the representation of the second event data are displayed relative to each other according to the relative order of the first time value and the second time value and the corresponding values of the first time value and the second time value.

[0054] Therefore, a device with a faster, more efficient method and interface for managing (e.g., editing) context-specific user interfaces is provided, thereby increasing effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can supplement or replace other methods for managing context-specific user interfaces. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0057] Figure 2 A portable multifunction device with a touch-sensitive display is illustrated in accordance with some embodiments.

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

[0059] Figure 4A and Figure 4B Illustrated is an exemplary user interface for an applications menu on a portable multifunction device in accordance with some embodiments.

[0060] Figure 5A is an illustration of a portable multifunction device with a touch-sensitive display and a rotatable depressible input mechanism in accordance with some embodiments.

[0061] Figure 5B A portable multifunction device with a touch-sensitive display and a rotatable depressible input mechanism is illustrated in accordance with some embodiments.

[0062] Figure 6A and Figure 6B An exemplary context-specific user interface is illustrated.

[0063] Figure 7A and Figure 7B An exemplary context-specific user interface is illustrated.

[0064] Figure 8 An exemplary context-specific user interface is illustrated.

[0065] Figure 9 An exemplary context-specific user interface is illustrated.

[0066] Figure 10 An exemplary context-specific user interface is illustrated.

[0067] Figures 11A-11C An exemplary context-specific user interface is illustrated.

[0068] Figure 12 An exemplary context-specific user interface is illustrated.

[0069] Figure 13A and Figure 13B An exemplary context-specific user interface is illustrated.

[0070] Figure 14A An exemplary context-specific user interface is illustrated.

[0071] Figures 14B-14U An exemplary context-specific user interface is illustrated.

[0072] Figure 15 An exemplary context-specific user interface is illustrated.

[0073] Figures 16A-16G An exemplary context-specific user interface is illustrated.

[0074] Figure 17A and Figure 17B An exemplary context-specific user interface is illustrated.

[0075] Figures 18A-18C An exemplary context-specific user interface is illustrated.

[0076] Figure 19 An exemplary context-specific user interface is illustrated.

[0077] Figure 20 is a flow diagram illustrating a process for a context-specific user interface.

[0078] Figure 21 is a flow diagram illustrating a process for a context-specific user interface.

[0079] Figure 22 is a flow diagram illustrating a process for a context-specific user interface.

[0080] Figure 23 is a flow diagram illustrating a process for a context-specific user interface.

[0081] Figure 24 is a flow diagram illustrating a process for a context-specific user interface.

[0082] Figure 25 is a flow diagram illustrating a process for a context-specific user interface.

[0083] Figure 26 is a flow diagram illustrating a process for a context-specific user interface.

[0084] Figure 27A is a flow diagram illustrating a process for a context-specific user interface.

[0085] Figure 27B is a flow diagram illustrating a process for a context-specific user interface.

[0086] Figure 27C is a flow diagram illustrating a process for a context-specific user interface.

[0087] Figure 27D is a flow diagram illustrating a process for a context-specific user interface.

[0088] Figure 27E is a flow diagram illustrating a process for a context-specific user interface.

[0089] Figure 27F is a flow diagram illustrating a process for a context-specific user interface.

[0090] Figure 28 is a flow diagram illustrating a process for a context-specific user interface.

[0091] Figure 29 is a flow diagram illustrating a process for a context-specific user interface.

[0092] Figure 30 is a flow diagram illustrating a process for a context-specific user interface.

[0093] Figure 31 is a flow diagram illustrating a process for a context-specific user interface.

[0094] Figure 32 is a flow diagram illustrating a process for a context-specific user interface.

[0095] Figure 33 is a flow diagram illustrating a process for a context-specific user interface.

[0096] Figure 34 is a functional block diagram of an electronic device according to some embodiments.

[0097] Figure 35 is a functional block diagram of an electronic device according to some embodiments.

[0098] Figure 36 is a functional block diagram of an electronic device according to some embodiments.

[0099] Figure 37 is a functional block diagram of an electronic device according to some embodiments.

[0100] Figure 38 is a functional block diagram of an electronic device according to some embodiments.

[0101] Figure 39 is a functional block diagram of an electronic device according to some embodiments.

[0102] Figure 40 is a functional block diagram of an electronic device according to some embodiments.

[0103] Figure 41 is a functional block diagram of an electronic device according to some embodiments.

[0104] Figure 42 is a functional block diagram of an electronic device according to some embodiments.

[0105] Figure 43 is a functional block diagram of an electronic device according to some embodiments.

[0106] Figure 44 is a functional block diagram of an electronic device according to some embodiments.

[0107] Figure 45 is a functional block diagram of an electronic device according to some embodiments.

[0108] Figure 46 is a functional block diagram of an electronic device according to some embodiments.

[0109] Figure 47 is a functional block diagram of an electronic device according to some embodiments.

[0110] Figure 48 is a functional block diagram of an electronic device according to some embodiments.

[0111] Figure 49 is a functional block diagram of an electronic device according to some embodiments.

[0112] Figure 50 is a functional block diagram of an electronic device according to some embodiments.

[0113] Figure 51 is a functional block diagram of an electronic device according to some embodiments.

[0114] Figure 52 is a functional block diagram of an electronic device according to some embodiments.

[0115] Figures 53A-53F An exemplary user interface in accordance with some embodiments is illustrated.

[0116] Figures 54A-54E is a flow chart illustrating a method of activating an operating mode according to some embodiments.

[0117] Figure 55 is a functional block diagram of an electronic device according to some embodiments.

[0118] Figures 56A-56I An exemplary context-specific user interface is illustrated.

[0119] Figure 57A is a flow diagram illustrating a process for a context-specific user interface.

[0120] Figure 57B is a flow diagram illustrating a process for a context-specific user interface.

[0121] Figure 57C is a flow diagram illustrating a process for a context-specific user interface.

[0122] Figure 57D is a flow diagram illustrating a process for a context-specific user interface.

[0123] Figure 57E is a flow diagram illustrating a process for a context-specific user interface.

[0124] Figure 57F is a flow diagram illustrating a process for a context-specific user interface.

[0125] Figure 58 is a functional block diagram of an electronic device according to some embodiments.

[0126] Figures 59A-59F An exemplary user interface in accordance with some embodiments is illustrated.

[0127] Figures 60A-60F is a flow diagram illustrating a process for supplementing displayed information according to some embodiments.

[0128] Figure 61 is a functional block diagram of an electronic device according to some embodiments. DETAILED DESCRIPTION

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

[0130] As discussed above, users can customize context-specific user interfaces for keeping track of time and receiving certain types of information. The challenge is to provide users with numerous options for customizing such interfaces while also providing a highly usable interface. Furthermore, the challenge is to present these options in a manner that is easily understood and intuitive to the user, allowing customization of multiple variables such as color, display density, complexity, and the like. Context-specific user interfaces and methods for enabling user customization of such interfaces are highly desirable for portable, multi-function devices.

[0131] under, Figure 1A to Figure 1B 、 Figure 2 、 Figure 3 and Figures 4A to 4B as well as Figures 5A to 5B A description of an exemplary device for performing techniques for providing a context-specific user interface is provided. Figure 19 The user interface in the figure is also used to illustrate the process described below, including Figures 20 to 33 in the process.

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

[0133] The terms used in the description of the various described embodiments are used herein only to describe specific embodiments and are not intended to be limiting. The description of the various described embodiments and the singular forms "one", "an" and "said" used in the appended claims are intended to also include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and covers any item in one or more items of the associated listed items and all possible combinations. It should further be understood that the terms "comprises", "having", "including" and / or "containing" when used in this specification specify the presence of features, wholes, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0134] The term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [certain condition or event] is detected" may be interpreted to mean "upon determination" or "in response to determining" or "upon detecting [certain condition or event]" or "in response to detecting [certain condition or event]," depending on the context.

[0135] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device (such as a mobile phone) that also includes other functionality, such as a PDA and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. of Cupertino, California. iPod and Device. Other portable electronic devices such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) may also be used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

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

[0137] The device can support various applications, such as one or more of the following applications: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video recorder application, a web browsing application, a digital music player application, and / or a digital video player application.

[0138] Various applications executing on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed from one application to the next and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications through a user interface that is intuitive and transparent to the user.

[0139] Attention will now be turned to embodiments of portable devices having touch-sensitive displays. Figure 1Ais a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" and is sometimes considered or referred to as a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, peripheral interfaces 118, RF circuitry 108, audio circuitry 110, speakers 111, microphones 113, input / output (I / O) subsystems 106, other input or control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 335 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0140] As used in the specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). Optionally, various methods and various sensors or combinations of sensors are used to determine (or measure) the intensity of a contact. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, the force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of the contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of and / or changes to the contact area detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface in proximity to the contact and / or changes thereto, or the resistance of the touch-sensitive surface in proximity to the contact and / or changes thereto are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement for contact force or contact pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement for contact force or contact pressure is converted into an estimated force or estimated pressure, and the estimated force or estimated pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows user access to additional device functionality that would otherwise not be accessible to the user on a reduced-size device (e.g., via a touch-sensitive display) with limited real estate for displaying affordances and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0141] As used in the specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of gravity of the device, which will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a touch-sensitive user surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a change in the physical properties of the device or device component that is felt. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "lift click" of a physical actuator button. In some cases, the user will feel a tactile sensation, such as a "press click" or "lift click," even when there is no movement of a physical actuator button associated with the touch-sensitive surface being physically pressed (e.g., displaced) by the user's movement. As another example, even when the smoothness of the touch-sensitive surface does not change, the movement of the touch-sensitive surface is optionally interpreted or felt by the user as the "roughness" of the touch-sensitive surface. While this interpretation of touch by a user will be influenced by the user's individual sensory perception, there are many sensory perceptions of point touch that are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "lift-click," "press-click," "roughness"), unless explicitly indicated to the contrary, the tactile output produced will correspond to a physical displacement of the device or a component thereof that would produce the described sensory perception for a typical (or average) user.

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

[0143] Memory 102 may include one or more computer-readable storage media. Computer-readable storage media may be tangible and non-volatile. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.

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

[0145] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communications network and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as other devices. RF circuitry 108 optionally includes known circuitry for detecting near-field communication (NFC) fields, such as via a short-range radio. The wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11d). 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this document.

[0146] The audio circuit device 110, the speaker 111 and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit device 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit device 110 also receives the electrical signal converted from the sound wave by the microphone 113. The audio circuit device 110 converts the electrical signal into audio data and transmits the audio data to the peripheral interface 118 for processing. The audio data can be obtained from the memory 102 and / or the RF circuit device 108 and / or transmitted to the memory 102 and / or the RF circuit device 108 through the peripheral interface 118. In some embodiments, the audio circuit device 110 also includes a headphone jack (e.g., Figure 2 The headphone jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset capable of both output (e.g., a headset for one or both ears) and input (e.g., a microphone).

[0147] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to the peripherals interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to the other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., Figure 2 208) optionally includes up / down buttons for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206 in ).

[0148] A quick press of the push button can unlock the touch screen 112 or begin the process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application No. 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," and U.S. Patent No. 7,657,849, which are incorporated herein by reference in their entirety. A longer press of the push button (e.g., 206) can power the device 100 on or off. The user can customize the function of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0149] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, videos, and any combination of the above (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to user interface objects.

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

[0151] The touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. The touch screen 112 and display controller 156 may use any of a variety of touch sensing technologies now known or later developed to detect contact and any movement or interruption of contact, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112. In one exemplary embodiment, projected mutual capacitance sensing technology is used, such as that available from Apple Inc. of Cupertino, California. and iPod The technology found in .

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

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

[0154] The touch screen 112 can have a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user can use any suitable object or appendage, such as a stylus, finger, etc., to make contact with the touch screen 112. In some embodiments, the user interface is designed to operate primarily through finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer / cursor position or command to perform the action desired by the user.

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

[0156] The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a charging system, power failure detection circuitry, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components related to the generation, management, and distribution of power in a portable device.

[0157] Device 100 may also include one or more optical sensors 164 . Figure 1A An optical sensor is shown coupled to the optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives ambient light projected through one or more lenses and converts the light into data representing an image. In conjunction with the imaging module 143 (also referred to as a camera module), the optical sensor 164 can capture still images or video. In some embodiments, the optical sensor is located on the back of the device 100, opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be used as a viewfinder for still and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image can be captured for video conferencing while the user views other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing), so that a single optical sensor 164 can be used with the touchscreen display for both video conferencing and still and / or video image acquisition.

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

[0159] Device 100 may also include one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 can be coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 can be implemented as described in U.S. patent application Ser. No. 11 / 241,839, entitled “Proximity Detector In Handheld Device,” U.S. patent application Ser. No. 11 / 240,788, entitled “Proximity Detector In Handheld Device,” U.S. patent application Ser. No. 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output,” U.S. patent application Ser. No. 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices,” and U.S. patent application Ser. No. 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are incorporated herein by reference in their entireties. In some embodiments, when the multifunction device is near the user's ear (eg, when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112 .

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

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

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

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

[0164] The communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly to other devices via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are used in conjunction with (trademark of Apple Inc.) devices.

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

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

[0167] The contact / motion module 130 optionally detects gestures input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or detected contact intensities). Thus, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event followed by detecting a finger up (e.g., lift) event at the same location (or substantially the same location) as the finger press event (e.g., at an icon location). As another example, detecting a finger drag gesture on the touch surface includes detecting a finger press event followed by detecting one or more finger drag events followed by detecting a finger up (lift) event.

[0168] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual effects (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to: text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

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

[0171] Text input module 134 (which may be a component of graphics module 132) provides a soft keyboard for entering text into various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

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

[0173] Application 136 may include the following modules (or instruction sets), or a subset or superset thereof:

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

[0175] Telephone module 138;

[0176] Video conferencing module 139;

[0177] Email client module 140

[0178] Instant messaging (IM) module 141;

[0179] Training support module 142;

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

[0181] Image management module 144;

[0182] Video player module;

[0183] Music player module;

[0184] Browser module 147;

[0185] Calendar module 148;

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

[0187] Widget creator module 150, used to create user-created widgets 149-6;

[0188] Search module 151;

[0189] Video and music player module 152, which combines the video player module and the music player module;

[0190] Memo module 153;

[0191] Map module 154; and / or

[0192] Online video module 155.

[0193] Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

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

[0195] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 can be used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an already entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication can use any of a variety of communication standards, protocols, and technologies.

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

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

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

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

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

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

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

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

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

[0205] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 may be used by a user to create widgets (e.g., convert a user-specified portion of a web page into a widget).

[0206] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

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

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

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

[0210] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back a particular online video (e.g., on the touch screen or on a display connected externally via external port 124), send an email with a link to a particular online video, and manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141, rather than email client module 140, is used to send a link to a particular online video. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the entireties of which are hereby incorporated by reference in their entirety.

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

[0212] In some embodiments, the device 100 is a device that is dedicated to performing operations of a predetermined set of functions on the device through a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the primary input control device for operating the device 100, the number of physical input control devices (such as push buttons, dials, etc.) on the device 100 can be reduced.

[0213] The predetermined set of functions performed exclusively via the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, when the user touches the touchpad, the device 100 is navigated from any user interface on the device 100 display to the home screen, main screen, or root menu. In such embodiments, the touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

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

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

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

[0217] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (through audio circuitry 110). The information peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

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

[0220] Hit view determination module 172 provides software routines for determining where a sub-event has occurred in one or more views when touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that a user can see on the display.

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

[0222] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the lowest-level view in the hierarchy that should handle the sub-event as the hit view. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that forms an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source that caused it to be identified as the hit view.

[0223] Active event recognizer determination module 173 determines which view or views in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views, including the physical location of the sub-event, are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with a particular view, views higher in the hierarchy will still remain as actively participating views.

[0224] Event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue for retrieval by corresponding event receiver 182.

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

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

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

[0228] Event receiver 182 receives event information from event classifier 170. The event information includes information about a sub-event (e.g., a touch or touch movement). Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

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

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

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

[0233] In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers may or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or program hierarchy.

[0234] In some embodiments, a corresponding event recognizer 180 activates an event handler 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, a corresponding event recognizer 180 delivers event information associated with the event to event handler 190. Activating event handler 190 is distinct from sending (or delaying sending) the sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predetermined process.

[0235] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a series of sub-events or an actively participating view. The event handler associated with the series of sub-events or the actively participating view receives the event information and executes a predetermined process.

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

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

[0238] It should be understood that the foregoing discussion of event handling regarding user touches on a touch-sensitive display also applies to other forms of user input for operating a multifunction device 100 having an input device, where not all user input is initiated on the touch screen, for example, mouse movements and mouse button presses, optionally combined with single or multiple keyboard presses or holds; contact motions on a touchpad (such as taps, drags, scrolls, etc.); stylus input, movement of the device; voice commands; detected eye movements, biometric input; and / or any combination of the above, optionally used as input corresponding to sub-events defining the event to be recognized.

[0239] Figure 2 A portable multifunction device 100 with a touch screen 112 is illustrated in accordance with some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more graphics by making gestures (e.g., with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses (not drawn to scale in the figure)) directed to the graphics. In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, upward, and / or downward), and / or rotation of a finger that has made contact with the device 100 (from right to left, from left to right, upward, and / or downward). In some implementations or circumstances, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture across an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

[0240] The device 100 may also include one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 may be used to navigate to any application 136 in the application collection that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0241] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, and volume adjustment buttons (or buttons) 208, a subscriber identity module (SIM) card slot 210, a headphone jack 212, and a docking / charging external port 124. Push button 206 is optionally used to turn the device on / off by pressing and holding the button for a predetermined time interval; to lock the device by pressing and releasing the button before a predetermined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also accepts voice input for activating or deactivating certain functions via microphone 113. Device 100 optionally also includes one or more contact force sensors 165 for detecting contact force on touch screen 112 and / or one or more tactile output generators 167 for generating tactile output for a user of device 100.

[0242] Figure 3 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. The device 300 includes an input / output (I / O) interface 330, which includes a display 340, which is typically a touch screen display. The input / output interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above referenced appendix). Figure 1A (a) tactile output generator(s) 167 as described above), sensor 359 (e.g., similar to the ... Figure 1A1 ). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 may optionally include one or more storage devices remote from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 ( FIG. 1 ). In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0243] Figure 3 Each element of the above-mentioned elements in can be stored in one or more of the aforementioned memory devices. Each module in the above-mentioned modules corresponds to an instruction set for performing the functions described above. The above-mentioned modules or programs (e.g., instruction sets) do not need to be implemented as separate software programs, processes or modules, so in various embodiments, various subsets of these modules can be combined or otherwise rearranged. In some embodiments, memory 370 can store subsets of the above-mentioned modules and data structures. In addition, memory 370 can store additional modules and data structures not described above.

[0244] Attention now turns to embodiments of a user interface that may be implemented on, for example, portable multifunction device 100 .

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

[0246] Signal strength indicators 402 for wireless communication(s), such as cellular and Wi-Fi signals;

[0247] Time 404;

[0248] Bluetooth indicator 405;

[0249] Battery status indicator 406;

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

[0251] o An icon 416 for the phone module 138, labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voice messages;

[0252] o An icon 418 for the email client module 140 , labeled “Mail,” which optionally includes an indicator 410 of the number of unread emails;

[0253] o Icon 420 for the browser module 147, labeled "Browser"; and

[0254] o Icon 422 for the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled “iPod”; and

[0255] Icons for other applications, such as:

[0256] o Icon 424 for IM module 141, labeled "Messages";

[0257] o Icon 426 for calendar module 148, labeled "Calendar";

[0258] o Icon 42 for image management module 144, labeled "Photos";

[0259] o Icon 430 for camera module 143, labeled "Camera";

[0260] o Icon 432 for the online video module 155, labeled "Online Video";

[0261] o Icon 434 for the stock widget 149 - 2 , labeled “Stocks”;

[0262] o Icon 436 for the map module 154, labeled "Map";

[0263] o Icon 438 for the weather widget 149 - 1 , labeled “Weather”;

[0264] o Icon 440 for the alarm clock widget 149 - 4 , labeled “Clock”;

[0265] o Icon 442 for the training support module 142, labeled "Training Support";

[0266] o Icon 444 for the memo module 153, labeled "Memo";

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

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

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

[0270] Although some examples will be given with reference to input on a touch screen display 112 (where the touch sensitive surface is combined with the display), in some embodiments, as Figure 4B As shown, the device detects input on a touch-sensitive surface that is separate from the display. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a coordinate system corresponding to the main coordinate axis (eg, Figure 4B 453) of the principal axis (e.g., Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., at 452). Figure 4B , 460 corresponds to 468 and 462 corresponds to 470 ) at contact with touch-sensitive surface 451 (eg, Figure 4B In this way, when the touch-sensitive surface is in contact with the display of the multifunction device (e.g., Figure 4B 450) when separated by the device on the touch-sensitive surface (e.g., Figure 4B The user input detected on 451 in (for example, contact 460 and contact 462 and its movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

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

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

[0274] In some embodiments, device 500 has one or more input mechanisms 506 and 508. If included, input mechanisms 506 and 508 can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. If included, these attachment mechanisms can allow device 500 to be attached to, for example, a hat, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, fobs, pants, belts, shoes, handbags, backpacks, etc. These attachment mechanisms can allow device 500 to be worn by a user.

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

[0276] In some examples, input mechanism 508 can be a microphone. Personal electronic device 500 can include various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which can be operatively connected to I / O component 514.

[0277] The memory 518 of the personal electronic device 500 may be a non-volatile computer-readable storage medium for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described above, including processes 2000-3300 ( Figures 20 to 33 ). Computer-executable instructions may also be stored and / or transmitted within any non-volatile computer-readable storage medium for use by or in conjunction with an instruction execution system, apparatus, or device, such as a computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, apparatus, or device and execute the instructions. For the purposes of this document, a "non-volatile computer-readable storage medium" may be any medium that tangibly contains or stores computer-executable instructions for use by or in conjunction with an instruction execution system, apparatus, or device. Non-volatile computer-readable storage media may include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory (such as flash memory, solid-state drives, etc.). The personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other or additional components in various configurations.

[0278] As used herein, the term "affordance" refers to an item that can be present on device 100, device 300, and / or device 500 (FIG. 1, Figure 3 5 ). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) can each constitute an affordance.

[0279] As used herein, the term "focus selector" refers to an input element of a user interface that is currently interacting with a user. In some implementations, a cursor or other position marker is included that serves as a "focus selector" to facilitate focusing on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 in FIG. 4 and a cursor is over a particular user interface element (e.g., a button, a window, a slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations, a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display is included. Figure 1A touch-sensitive display system 112 or Figure 4A In some implementations, focus is moved from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user (e.g., by indicating to the device the user interface element with which the user intends to interact) to communicate the user's intended interaction with the user interface. For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) on the corresponding button will indicate that the user is intending to activate the corresponding button (as opposed to other user interface elements displayed on the device's display).

[0280] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predetermined event (e.g., after detecting the contact, before detecting the contact is lifted, before or after detecting the contact starts moving, before detecting the contact ends, before or after detecting an increase in contact intensity, and / or before or after detecting a decrease in contact intensity). The characteristic intensity of the contact is optionally based on one or more of the following: a maximum contact intensity, a median contact intensity, an average contact intensity, a top 10% contact intensity value, a contact intensity value at half-height, a contact intensity value at 90% of maximum, and the like. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the contact intensity over time). In some embodiments, the characteristic intensity is compared to one or more sets of intensity thresholds to determine whether an action has been performed by the user. For example, one or more intensity threshold sets may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or abstain from performing the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0281] In some embodiments, a portion of a gesture is recognized for the purpose of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact that transitions from a starting position and reaches an ending position where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only a portion of the swipe contact at the ending position). In some embodiments, a smoothing algorithm may be applied to the swipe contact intensity before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms may eliminate narrow spikes or dips in the swipe contact intensity for the purpose of determining the characteristic intensity.

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

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

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

[0285] In some embodiments, the device employs intensity hysteresis to avoid unintended input, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable fraction of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding action is performed in response to detecting the subsequent decrease in the intensity of the corresponding contact to below the hysteresis intensity threshold (e.g., a "lift-and-tap" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to at or below the hysteresis intensity, and a corresponding action is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on various circumstances).

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

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

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

[0289] Active applications, which are applications currently being used and displayed on the device's display;

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

[0291] • Suspended or hibernated applications, not running but having state information stored in memory (volatile or non-volatile, respectively) that can be used to resume execution of the application.

[0292] As used herein, the term "closed application" refers to a software application that does not retain state information. For example, the state information of a closed application is not stored in the device's memory. Therefore, closing an application includes stopping and / or removing the application's application process, as well as removing the application's state information from the device's memory. Generally, opening a second application within a first application does not close the first application. When the second application is displayed and the first application stops displaying, the first application becomes a background application.

[0293] 1. Context-Specific User Interface

[0294] Attention is now directed to embodiments of a context-specific user interface ("UI") and associated processes that may be used on a device having a display and a touch-sensitive surface such as devices 100, 300, and / or 500 ( Figure 1A 、 Figure 3 and / or Figure 5A ) and other multi-function devices.

[0295] The following examples illustrate exemplary embodiments of context-specific user interfaces. Described herein are overall concepts relating to customizable context-specific user interfaces. Note that the context-specific user interfaces described herein can be edited in a variety of ways. The user interface can display or otherwise indicate various types of information related to time, and the type of information can be customizable by the user. The user interface can include aspects such as color, display density, and complications (or the lack thereof) that can also be customizable. As used herein, consistent with its accepted meaning in the art, complications refer to any clock face features other than those used to indicate the hours and minutes of time (e.g., clock hands or hour / minute indications). Complications can provide different types of information to the user, such as data obtained from an application, and the information conveyed to the user by the complications is also customizable, as described below.

[0296] These combined features result in thousands (if not more) of available context-specific user interfaces. Since it is impractical to describe each of these permutations, specific context-specific user interfaces are utilized to emphasize specific aspects, but these exemplary descriptions are by no means intended to limit such aspects to such context-specific user interfaces, because specific aspects can be used for other context-specific user interfaces, and specific context-specific user interfaces can have other aspects. These embodiments are intended to illustrate the overall concepts presented, but those skilled in the art will recognize that multiple other embodiments within the scope of the technology described herein are possible.

[0297] Figure 6A An exemplary context-specific user interface is shown that may operate on device 600. In some embodiments, device 600 may be device 100, 300, or 500. The electronic device has a display (eg, 504).

[0298] A user who tracks the time of day may wish to gain some sense of how much time has passed since a specific event. For example, a user may wish to know how much time has passed since the user last checked the time, or how much time has passed since a specific time of day, such as morning. In addition to viewing a clock face, a user may wish to receive additional visual cues that enhance the perception of elapsed time.

[0299] Animating a clock face transitioning from indicating a first time to indicating the current time updates screen 604. The updated screen 604 is depicted as screen 610, which displays clock face 612. Clock face 612 has been updated to indicate the current time. The animation from screen 604 to screen 610 represents the transition from the first time to the current time. In some embodiments, screen 604 and / or screen 610 may also include an indication of the date.

[0300] As described above, in Figure 6A The context-specific user interface exemplified in first displays a clock face indicating a first time. The first time can be determined based on different criteria. In some embodiments, the device receives second data representing a previous user movement of the electronic device (e.g., movement of the device such as a lowering of the user's wrist in the case where the device is wearable or other movement indicating that the user is no longer actively viewing the display). The time of the previous user movement of the device can be the last time the user viewed the device, or the last time the display of the device was turned off before receiving the data representing the user input 602. The time of the previous user movement of the electronic device can then be shown as the first time indicated by the clock face. For example, in Figure 6A6, 10:05 depicted by clock face 606 may be the time of the previous user movement on the device, indicating the time of the previous user interaction. In these examples, when the user interface screen updates, it provides the user with an indication of how much time has elapsed since the previous user interaction (e.g., the last time the user viewed device 600).

[0301] In other embodiments, the first time may be based on a predetermined interval of time. For example, the first time may precede the current time by a first duration, and the first duration may be a predetermined duration before the current time. That is, the first time indicated by the clock face may be based on a predetermined or fixed duration before the current time, rather than based on user interaction.

[0302] In some embodiments, the predetermined duration is 5 hours. In response to the user input, the clock face may depict a time 5 hours before the current time and then animate the clock face from indicating the first time to indicating the current time. For example, if the current time is 6:00, the device may display a clock face showing 1:00 in response to the user input, and the clock face may be animated to transition from 1:00 to 6:00.

[0303] In other embodiments, the first time may be based on a predetermined time of day. In this case, the device may begin animating by indicating the same time of day (i.e., the first time) regardless of the current time, and then animate the clock face until it reaches the current time. For example, the first time may be morning (e.g., 8:00 a.m.). In this example, if the current time is 6:00 a.m., the device may display a clock face showing 8:00 in response to the user input, with the clock face animated from 8:00 to 6:00.

[0304] Regardless of how the first time is determined, in some embodiments, the clock face can be animated for a time period that indicates the duration between the first time and the current time. That is, the length of the animation can be roughly proportional to the length of the duration. The length of the animation may not be exactly proportional to the first duration, but it can provide the user with a general indication of the approximate length of time. To illustrate, using the example described above, if the clock face transitions from 8:00 to 6:00, it can be animated for a longer time period than if it transitions from 3:00 to 6:00. This can be particularly useful in situations where the duration is variable, such as if the duration is based on the time between user interactions. In this case, the user will immediately understand that if the clock face animation is longer, then more time has elapsed between interactions, or if the clock face animation is shorter, then less time has elapsed between interactions.

[0305] In other embodiments, the clock face is animated for a time period that is independent of the first duration. That is, the length of the animation is not proportional to the duration between the first time and the current time. In some embodiments, the length of the animation can be the same for each animation. To illustrate using the example described above, the clock face can be animated for the same time period regardless of whether the transition is from 8:00 to 6:00 or from 3:00 to 6:00. This can help reduce the time it takes the user to view the transition. Alternatively, if the transition is from 8:00 to 6:00, the clock face is animated for a different time period than if it was from 3:00 to 6:00, but the time period may not be related to the first duration.

[0306] Figure 6B Optional features of the context-specific user interface are illustrated. In response to data representing user input 620, device 600 displays user interface screen 622, which includes clock face 624. In this example, the current time is 10:25. Clock face 624 indicates a first time (in this instance, 10:05). As a background, clock face 624 also displays an image of a mountain scene representing the first time. For example, Figure 6B As shown in FIG, clock face 624 shows a morning view of a mountain scene (see, for example, the position of sun 626 in the sky). Thus, a user viewing clock face 624 understands the time based on the clock face itself and the background, which also represents the time indicated by the clock face. Note that this provides additional information to the user because the user understands that the indicated time is 10:05 AM, not 10:05 PM, based on the display of the scene.

[0307] In some embodiments, the device accesses an image of a scene that represents the time indicated by a clock face. The image of the scene that represents the time can, along with the time indicated by the clock face, suggest a similar time of day to the user. The image of the scene need not suggest the exact time indicated by the clock face, nor need it be strictly linked to the time of day at the scene location (which will be discussed in detail below). In some embodiments, the image of the scene is an image captured at a time of day that is substantially the same as the current time (i.e., the time of day when the image was taken at the scene). In other embodiments, the image of the scene is an image captured at a different time of day than the current time.

[0308] In some embodiments, the image of the scene can depict, for example, a city, a seaside, a desert, a park, a lake, a mountain, or a valley. In some embodiments, the scene can be recognizable to the user, such as a scene of Yosemite Valley or Big Ben.

[0309] Subsequently, device 600 displays screens 630 and 640. As described below, screen 630 is optional and includes a clock face 632 that indicates a time between the first time and the current time. This intermediate time is further represented on clock face 632 by a background (see, for example, a setting sun 634). Screen 640 includes a clock face 642 that depicts the current time. Clock face 642 also displays a background representing the current time (see, for example, a moon 644).

[0310] Thus, in some embodiments, and in response to receiving data representing user input 620, the device accesses a first image representing a scene at a first time (e.g., the background of clock face 624), accesses a second image representing a scene at the current time (e.g., the background of clock face 642), and in response to receiving data representing user input, continuously displays the first image of the scene and the second image of the scene.

[0311] The display continuously indicates the passage of time from a first time to a current time. The device may include a series of images of a particular scene (e.g., a time lapse image), each depicting a different time of day, such that any first time or current time depicted by the clock face has a corresponding scene image representing the depicted time. In some embodiments, the first image of the scene and the second image of the scene are displayed as a background on the user interface screen.

[0312] In some embodiments, the device accesses a sequence of images of scenes, the sequence including a first image representing a scene at a first time (e.g., the background of clock face 624), a second image representing one or more scenes at one or more times between the first time and the current time (e.g., the background of clock face 632), and a third image representing a scene at the current time (e.g., the background of clock face 642). In response to receiving data representing user input 620, the device displays the sequence of images of the scenes by animating the sequence of images to indicate the transition of time from the first time to the current time (e.g., like a flip book). In some embodiments, the scene is specified by the user (e.g., the device can store a collection of time lapse images for different scenes, and the user can select a scene to display).

[0313] like Figure 6BAs shown in , device 600 sequentially displays screens 622, 630, and 640 to animate the displayed, respective backgrounds, thereby animating an image of the scene like a flip book to indicate the passage of time. In some embodiments, the transition from screen 620 to 630 to 640 can also be animated, for example, by animating the hands of a clock face to rotate clockwise, and / or by animating the display of an image of the scene like a flip book. If the clock face otherwise or additionally depicts the representation of a digital clock, the numerical indication of the hours and minutes can be animated in some form to depict the passage of time. By displaying both the animated clock face and the animated scene image, the device provides the user with a clearer and more easily distinguishable indication of the time between the first time and the current time.

[0314] In some embodiments, the device 600 has a location sensor (e.g., GPS sensor 532 and / or GPS module 135), and the device obtains the device's current location from the location sensor. The first image of the scene represents the first time at the current location, and the second or third image of the scene (whichever represents the current time) represents the current time at the current location. That is, the transition of the indicated time reflects the daytime / nighttime at the current location. For example, if the user is located near the Arctic Circle, there may be nearly 24 hours of daylight on that day (e.g., the sun at midnight). In this example, the images indicating the first time and the current time may all be images of a scene during the day (e.g., Yosemite Valley), even if the first time and the current time are separated by a long period of time. Therefore, the images of the scene can represent the time depicted at the current location, but they may not represent the time depicted at the location of the scene. This concept allows the device to display a context-specific user interface for depicting the transition of time at the current location and enhances the user's interaction with the device because the animation is based on the user experience at the current location (e.g., the perception of time).

[0315] In some embodiments, the device displays a user interface object on a user interface screen at a first location based on a first time. In some embodiments, the location can be based on a position along a clock face, such as an hour indicator (e.g., 6 o'clock is located at the lower center of the display). In some embodiments, the location can be based on a position across the horizon, such as the position of the sun or moon. For example, Figure 6B , the position of the sun 626 indicates a first time, as it represents the sun at a position in the east at almost noon in the scene.

[0316] In some embodiments, the device animates a user interface object by moving the user interface object from a first position to a second position on the user interface screen, where the second position is based on a current time. Moving the user interface object from the first position to the second position indicates a transition in time from the first time to the current time. Figure 6B , the sun 626 moves across the sky in a sequence of images of a scene (see sun 626 and sun 634). Subsequently, a user interface object depicts the moon 644 at a location in the night sky indicating the current time. In some embodiments, the user interface object is a graphical representation of the sun (e.g., 626 and 634). In some embodiments, the user interface object is a graphical representation of the moon (e.g., 644).

[0317] In any of the embodiments described above, the user input can include movement of the device. For example, the movement of the device can be a raise of the user's wrist (if the device is wearable), or other movement that instructs the user to raise the device to view the display. These movements can be detected, for example, using an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or a combination thereof. In any of the context-dependent clock faces described herein, movement of the device can be the user input that activates the display.

[0318] Additionally, in any of the context-dependent clock faces described herein, movement of the device, such as lowering of the user's wrist (if the device is wearable) or other movement indicating that the user is no longer actively viewing the display, or lack of movement of the device, such as raising of the user's wrist (if the device is wearable) or other movement indicating that the user is raising the device to view the display, may be user input that causes the device to turn off the display.

[0319] In other embodiments, the device may have a touch-sensitive display or touch-sensitive surface (e.g., Figure 3 Touchpad 355, Figure 4B 45, and / or touch screen 504), and the user input may be contact on the touch-sensitive display.

[0320] Now turn your attention to Figure 7A The context-specific user interface shown in . Figure 7A An exemplary context-specific user interface is shown that may operate on device 700. In some embodiments, device 700 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0321] A user may wish to track the time of day while also accessing the stopwatch function. For example, in a context such as running or cycling, a user may wish to operate the stopwatch, record laps, and still maintain a view of the time of day.

[0322] like Figure 7A , as depicted on user interface screen 702, device 700 displays a clock face indicating the current time on a touch-sensitive display. The clock face includes hour and minute hands 704. The clock face also includes one or more hour time scale indications (e.g., the numbers 12, 1, 2, 3 and / or tick marks or other visual indicators displayed at corresponding positions on the clock face), such as a 12 o'clock indicator 706. The clock face further includes a stopwatch hand 708 (which also serves as a seconds hand in some embodiments described below. Note that, as used herein, the term seconds hand refers to the hand on the clock face that indicates seconds, not the second of the two hands on the clock face).

[0323] like Figure 7A , device 700 receives user input, in this case a touch 712 on a start affordance 710. In response, as shown on screen 720, the device replaces the 12 o'clock indicator 706 with a stopwatch time scale indicator 724. Stopwatch indicator 724 shows that the stopwatch time scale is a 60-second time scale. The time scale of the stopwatch hand can refer to the amount of time it takes for the stopwatch hand to complete one full rotation around the displayed clock face. Note that the clock face on screen 720 includes hour and minute hands 722 and stopwatch hand 726, which are the same as hour and minute hands 704 and stopwatch hand 708.

[0324] In further response to touch 712, as shown by comparing screens 720 and 730, device 700 animates stopwatch hand 726 to reflect the passage of time. As shown on screen 730, the stopwatch hand has moved to the second position on the clock face (note the position of stopwatch hand 736), indicating the passage of time. Assuming that indicator 734 shows that the stopwatch time scale is 60 seconds, the position of stopwatch hand 736 indicates that 25 seconds have passed. Figure 7A , the user accesses this information by touching 740 on lap affordance 738, which causes the display of time 742, indicating the time that has elapsed since touch 712. Note that the hour and minute hands 732 are identical to 722 and 704, and that neither hand has changed position in the past 25 seconds. In this example, the hour and minute hands indicate the same time of day (e.g., 10:10) throughout screens 702, 720, and 730.

[0325] Stated another way, the device displays the time of day using hour and minute hands and additionally displays a stopwatch hand. In response to receiving data representing user input, the hour indication is replaced by an indication of a first time mark of the stopwatch hand, but the hour and minute hands continue to indicate the time of day despite the replacement of the hour indication. This allows the user to view the stopwatch and the time of day simultaneously, while simultaneously showing that the stopwatch has started and indicating the stopwatch time mark. Also in response to receiving data, the device animates the stopwatch hand to reflect the passage of time.

[0326] In some embodiments, while animating the stopwatch hands to reflect the passage of time, the device receives second data representing a second user input, and in response to receiving the second data, the device can suspend the animation of the stopwatch hands. For example, this can function similarly to a "stop" function on a stopwatch.

[0327] In some embodiments, the device can display a first affordance (e.g., affordance 710) on the touch-sensitive display that represents a start / stop function. First data representing a first user input (e.g., touch 712) and second data representing a second user input both represent contact on the displayed first affordance. In other embodiments, the device can display separate affordances for stopwatch start and stopwatch stop functions.

[0328] In some embodiments, the device may display a second affordance (e.g., affordance 738) on the touch-sensitive display that represents a lap function. After receiving the first data (e.g., after invoking the start function) and before receiving the second data (e.g., before invoking the stop function), the device receives third data representing a contact on the displayed second affordance. In response to receiving the third data, the device displays a third numerical indication of the elapsed time between receiving the first data and receiving the third data. For example, this can function similarly to a stopwatch "lap" function that causes the display of the time that has elapsed since the start function was invoked. This feature is illustrated on screen 730, as described above.

[0329] Additional information and / or functionality related to the stopwatch feature is accessed directly from the context-specific user interface. In one embodiment, the stopwatch application is an application as described in the following related application: U.S. Provisional Patent Application No. 62 / 044,979, filed on September 2, 2014, entitled "Stopwatch and Timer User Interfaces."

[0330] In some embodiments, the first time scale of the stopwatch hand can be 60 seconds, 30 seconds, 6 seconds, or 3 seconds. In some embodiments, the movement of the stopwatch hand is animated at a rate based on the first time scale of the stopwatch hand. For example, the stopwatch hand can move faster when the time scale is 3 seconds than when the time scale is 60 seconds. This causes the stopwatch hand to complete a full rotation around the clock face in the amount of time depicted by the first time scale.

[0331] In some embodiments, the device can replace one or more hour time scale indications with the first time scale indication of the stopwatch hand by removing one or more hour time scale indications, displaying the first time scale indication of the stopwatch hand, and translating the displayed first time scale indication of the stopwatch hand in a clockwise rotational motion. As an illustrative example, if the display includes a numerical indication of 12 hour time scales, and the first time scale of the stopwatch hand is a 6-second time scale, the device can replace the 12 numerical values with a single numerical value of 6. In some embodiments, this can be the same numerical value 6 as the hour indicator that was previously 6 o'clock, so that the replacement and display are imperceptible to the user. The device can display the numerical value 6 indicating the first time scale of the stopwatch hand at the 6 o'clock position on the clock face, and then translate the 6 around the clock face in a clockwise motion until it reaches the top of the clock face (the previous 12 o'clock position), at which point the translation stops. This improves the context-specific interface by reinforcing to the user that the clock face has transitioned from indicating hours and minutes to indicating the first time scale.

[0332] like Figure 7B As shown in , in some embodiments, the device has a rotatable input mechanism (eg, 506) that can be used as an optional input to change the stopwatch time scale. Figure 7B Screen 750 is shown with a clock face 752 including hour and minute hands 754, and a stopwatch time scale indicator 756 (showing a 60-second time scale). In response to receiving fifth data representing the movement of a rotatable input mechanism (e.g., movement 758), device 700 changes the stopwatch time scale to a second time scale, as shown by the portion of clock face 772 on screen 770, indicated by stopwatch time scale indicator 776. Note that screen 770 continues to display hour and minute hands 774. The second stopwatch time scale is different from the first stopwatch time scale. This allows the user to customize the time scale of the stopwatch hands by rotating the rotatable input mechanism, allowing a context-specific user interface to depend on the stopwatch time scale desired by the user.

[0333] In some embodiments, the device replaces the first time scale indication of the stopwatch hand with the second time scale indication of the stopwatch hand by removing the first time scale indication of the stopwatch hand, displaying the second time scale indication of the stopwatch hand, and translating the displayed second time scale indication of the stopwatch hand in a clockwise rotational motion.

[0334] like Figure 7B As shown in , the second time scale indicator 760 of the stopwatch hand is displayed at a position on the clock face that indicates its relative position in the first time scale. For example, the 30-second time scale indicator 760 is displayed on the clock face 752 at a position based on the sixty-second time scale indicated by 756. In response to receiving data representing movement 758, the device removes 756, displays 760, and translates 760 in a rotational motion in a clockwise direction until it reaches the previous position of the first time scale indicator of the stopwatch hand (e.g., the previous position of 756 as depicted by position 776 on the clock face 772).

[0335] In some embodiments, after receiving the first data representing the first user input, the device animates the stopwatch hand to represent the rotational motion around the origin and stops animating the stopwatch hand at a position of π / 2 radians relative to the rotational motion around the origin (e.g., at 12 o'clock). For example, the stopwatch hand may function as the second hand of a clock face before receiving the first data. When the first data is received, the second hand may be animated to depict the rotation around the clock face (e.g., by rotating around the center point of the clock face) until it resets at 12 o'clock. This signals to the user that the second hand has now become the stopwatch hand.

[0336] Now turn your attention to Figure 8 The context-specific user interface shown in . Figure 8 An exemplary context-specific user interface is shown operating on device 800. In some embodiments, device 800 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0337] Figures 8 to 10 A context-specific user interface is provided that allows the user to view the passage of time while accessing a rich array of geographical, lunar, and astronomical information. For example, a user may have acquaintances throughout the world and wish to know which parts of the world are in daylight or nighttime at the current time. A user may be interested in the phases of the moon and wish to know what the moon will look like tomorrow, next week, or next month. A user may be interested in astronomy and wish to know how the planets align at a particular time of interest, which may be that day.

[0338] exist Figure 8, device 800 displays a user interface screen 802 including a first affordance 804. First affordance 804 represents a simulation of a region of the Earth illuminated by the sun at the current time. For example, first affordance 804 illustrates that it is currently daytime in North America, Central America, and South America, and that a portion of the Pacific Ocean is currently nighttime, thereby simulating a region of the Earth illuminated by the sun at the current time.

[0339] Screen 802 also displays a second affordance 806 indicating the current time. Second affordance 806 indicates the current time (10:09) and optionally includes an indication of the day of the week (Wednesday) and the day of the month (25th). Screen 802 further displays a moon affordance 808 and a solar system affordance 810, which are used to invoke additional context-specific user interfaces accessible from this screen, as described in detail below.

[0340] In some embodiments, the simulation of a first area of the Earth illuminated by the sun at the current time is an actual representation of the Earth at the current time. For example, the simulation of the Earth may include specific geographical features. In some embodiments, the simulation of the Earth is updated to reflect the weather conditions at the current time (e.g., by depicting cloud cover or other weather phenomena such as tropical storms). The device can update the simulation of the Earth by downloading data from a weather service or external server (such as The Weather Channel, Accuweather, The National Weather Service, Yahoo! TM In some embodiments, the simulation of a first region of the Earth illuminated by the sun at the current time may indicate other global events such as the real-time location of the International Space Station, which may be obtained from an external server or service such as NASA.

[0341] Device 800 receives user input (in this example, swipe 812), and in response to receiving the user input, device 800 rotates the simulation of the Earth to display a second region of the Earth illuminated by the sun at the current time. This is depicted on screen 820, which displays a first affordance 822 depicting the second region of the Earth illuminated by the sun at the current time, the current time being indicated by a second affordance 824. This feature allows the user to access additional information in addition to the current time from this context-specific user interface. For example, the user can rotate the simulation of the Earth and display which regions are currently in daylight and which regions are currently in nighttime. Tying this information to the simulation of the Earth allows the user to access complex geographic and time-related data in an instantly intuitive and understandable manner.

[0342] In some embodiments, a first affordance representing a simulation of a first region of the Earth illuminated by the Sun at the current time includes a representation of a terminator (e.g., a day / night line at the current time). As illustrated by affordances 804 and 822, the simulation of the Earth can include a depiction of a region of the Earth that is currently in daylight, a region of the Earth that is currently in nighttime, and / or a terminator that divides the two regions.

[0343] In some embodiments, the user input includes a swipe in a first swipe direction on the touch-sensitive display, as illustrated by swipe 812. This allows the user to swipe the display to rotate the simulation of the globe. In some embodiments, the globe rotates in the same direction as the swipe direction. In some embodiments, the globe rotates in the opposite direction to the swipe direction.

[0344] In some embodiments, the user can rotate the simulation of the Earth in more than one direction using swipes in different directions. For example, a swipe in one direction can cause the representation of the Earth to rotate in one direction, and a swipe in the opposite direction or in a different direction can cause the representation of the Earth to rotate in the opposite direction. This allows the user to swipe in different directions to direct the rotation of the simulation of the Earth.

[0345] In some embodiments, as Figure 8, the device has a rotatable input mechanism (e.g., 506). Device 800 receives user input representing movement of the rotatable input mechanism (e.g., movement 830), and in response, device 800 updates first affordance 822 to represent a simulation of a first region of the Earth illuminated by the sun at a non-current time. This is shown on screen 840 having first affordance 842 and second affordance 844. Comparing screens 820 and 840, the simulation of the Earth has been updated from indicating a region of the Earth at the current time (10:09, indicated by 824) to (compare 822 and 842) indicating the same region of the Earth at a non-current time (12:09, indicated by 844). This feature provides the user with access to further geographical and time-related information by allowing the user to view the Earth illuminated by the sun at various times throughout the day.

[0346] In some embodiments, the device has a location sensor (e.g., GPS sensor 532 and / or GPS module 135), and before displaying the user interface screen, the device obtains the current location of the electronic device from the location sensor and displays a first area of the earth represented by a first affordance to indicate the current location of the electronic device. This allows the device to display the earth in such a way that the current location is part of the visible portion of the earth simulation (e.g., as a default or user-selectable country). In some embodiments, the first affordance includes a visible marker of the current location on the earth representation. This allows the user to easily identify the current location on the earth simulation.

[0347] In some embodiments, a device (e.g., device 800) visibly marks the device's current location on the globe representation (e.g., by displaying a symbol and / or text indicating the current location at an appropriate location on the globe representation). In some embodiments, this visible marking can be transient, e.g., the visible marking can be displayed briefly and then disappear or fade out. In some embodiments, the device does not repeat the visible marking of the current location while the user is at the current location. However, if the user changes location, the first time the user views the display after changing location, the device visibly marks the new current location on the globe representation, as described above. In some embodiments, the device detects user movement of the device (e.g., if the device is wearable, movement of the device such as raising the user's wrist, or other movement indicating that the user is viewing the display) and, in response, obtains the current location of the electronic device from a position sensor. The device can then determine whether the current location is the same as the device's location at the last time the user moved the device. Based on determining that the current location has changed since the last time the user moved the device, the device can visibly mark the current location on the globe representation.

[0348] In some embodiments, the device visibly marks a location (e.g., the current location) corresponding to the contact's location (e.g., the location of the contact's electronic device) on the globe representation (e.g., by displaying a symbol and / or text indicating the contact's location at an appropriate location on the globe representation). The contact may be, for example, stored on the device or communicated with the device via wireless communications (e.g., Wi-Fi, Bluetooth TM , near field communication ("NFC"), or any other cellular and / or other wireless communication technologies described herein. In some embodiments, the contact may be a contact associated with the user who has consented to provide their current location to the user of device 800, such as through a Find My Friend application, and data indicating the location of the contact's electronic device may be provided by a server, which may provide the location of the contact stored on device 800. This provides the user of device 800 with a quick visible reference to remind them of the contact's current location. In some embodiments, the user may further input travel information for the contact (e.g., flight data for contacts traveling by air, train data, cruise or ship data, etc.). The device may retrieve data representing the contact's current or predicted location (e.g., provided by an airline's server, in the example of flight data) and update a visible marker of the contact's location based on the retrieved data.

[0349] In some embodiments, the device detects user movement of the device (e.g., if the device is wearable, movement of the device such as raising of the user's wrist, or other movement indicating that the user is viewing a display). In response to detecting the movement, the device animates a first affordance representing a simulation of the Earth by translating the first affordance on the screen toward the center of the displayed user interface screen. For example, when user movement is detected, the device animates the simulation of the Earth to rotate it from the side or edge of the display to the center of the display.

[0350] In some embodiments, the device displays a third affordance on the user interface screen representing the moon (as depicted by affordances 808, 826, and 846). In some embodiments, the third affordance can be a graphical or stylized representation of the moon, such as an icon, symbol, or text indicating the moon. In some embodiments, the third affordance can be a realistic rendering of the moon as seen from Earth at the current time, with actual lunar features depicted.

[0351] The device detects a contact on the displayed third affordance, and in response to detecting the contact, the device updates the display of the user interface screen by displaying a fourth affordance representing a simulation of the moon as seen from Earth at the current time and a fifth affordance indicating the current time. In some embodiments, updating the display of the user interface screen includes animating the first affordance representing a simulation of a first region of Earth illuminated by the sun by zooming out of the display. The animation allows the user to recognize that the astronomical scale and / or angle has changed.

[0352] This transitions the user interface from using a simulation of the Earth to provide information about the current time of day to using a simulation of the Moon to provide information about the current time of month. Figure 8 The described context-specific user interface provides users with worldwide, customizable geographic information about daytime / nighttime conditions. Figure 9 , a context-specific user interface that provides a user with customizable information about moon phases and other moon characteristics is illustrated in FIG.

[0353] Figure 9 An exemplary context-specific user interface is shown that may operate on device 900. In some embodiments, device 900 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0354] As described above, device 900 is device 800 with an updated display. Device 900 is displaying screen 902 including affordance 904. Affordance 904 represents a simulation of the moon as seen from Earth at the current time (e.g., the current moon phase). In some embodiments, fourth affordance 904 is a realistic representation of the moon as seen from Earth at the current time, with actual moon features depicted. As shown in fourth affordance 904, the current moon phase is a waxing crescent. Although Figure 9 A stylized waxing moon is shown to represent the moon, but this is for illustrative purposes only. A fourth affordance 904 can depict a realistic rendering of the moon similar to how it actually appears in the night sky. Screen 904 also includes a fifth affordance 906 that illustrates the current time by showing the current date, day of the week, and month. In some embodiments, 906 indicates the current time of day.

[0355] Device 900 receives user input (e.g., movement of rotatable input mechanism 912), and in response to receiving the user input, the device rotates the simulation of the moon to display the moon as seen from Earth at a non-current time, as shown on screen 920 by affordance 922, which represents the moon at the non-current time indicated by updated fifth affordance 924. The non-current time can be within the current month or in a different month.

[0356] This is somewhat similar to the Figure 8 Interaction of the described Earth simulation. Figure 9 The context-specific user interface exemplified in

[0015] allows a user to access information about the appearance of the moon (e.g., the phase of the moon or which areas of the moon are visible from Earth) at various times. In some embodiments, the size of the simulated moon displayed may represent the relative distance between the Earth and the moon at the depicted current or non-current time, or it may represent the visible size of the moon as perceived from Earth at the depicted current or non-current time. The device may obtain such information from, for example, a service or external server, such as from NASA.

[0357] In some embodiments, a user can rotate the representation of the moon and view the corresponding time by swiping the touch-sensitive display. In some embodiments, the user input can include a swipe in a first swipe direction on the touch-sensitive display. In some embodiments, in response to receiving the user input, the simulation of the moon as seen from the earth is rotated in the first rotational direction. In some embodiments, the first rotational direction can be based at least in part on the first swipe direction. As used herein, the rotation of the moon can include the rotation of the moon on its axis to depict different areas of the moon (e.g., areas of the moon that are not visible from the earth) and / or to update the appearance of the moon as viewed from the earth at a particular time of interest (e.g., to update the displayed moon phase) based on the rotation of the relative positions of the moon, the earth, and the sun.

[0358] In some embodiments, the device receives a second user input, and in response to receiving the second user input, the device rotates the simulation of the moon as seen from the earth in a second rotational direction different from the first rotational direction. The user input can include, for example, a swipe on the touch-sensitive display in the second swipe direction different from the first swipe direction.

[0359] This allows the user to direct both the direction of rotation of the moon and the time indicated by the fifth affordance in response to a swipe. For example, the user can swipe in one direction to rotate the moon in a particular direction and view the moon later in the month, and the user can swipe in another direction to rotate the moon in the opposite direction and view the moon earlier in the month.

[0360] In some embodiments, as Figure 9As shown in , a user can rotate the representation of the moon and view the corresponding time by rotating the rotatable input mechanism. Thus, in some embodiments, the device has a rotatable input mechanism (e.g., 506), and the user input can include movement of the rotatable input mechanism in a first rotational direction (e.g., rotation 912). In some embodiments, in response to receiving the user input, the simulation of the moon as seen from the earth is rotated in the first rotational direction. In some embodiments, the first rotational direction can be based at least in part on the direction of movement of the rotatable input mechanism.

[0361] In some embodiments, the device receives a second user input, and in response to receiving the second user input, the device rotates the simulation of the moon as seen from Earth in a second rotational direction different from the first rotational direction. The user input may include, for example, movement of a rotatable input mechanism in the second rotational direction different from the first rotational direction.

[0362] This allows the user to direct both the direction of rotation of the moon and the time indicated by the fifth affordance in response to rotating the rotatable input mechanism. For example, the user can move the rotatable input mechanism in one direction to rotate the moon in a particular direction and view the moon later in the month, and the user can move the rotatable mechanism in another direction to rotate the moon in the opposite direction and view the moon earlier in the month.

[0363] In any of the embodiments described herein, the displayed moon simulation can indicate one or more additional moon attributes, such as special moons (e.g., blue moons, black moons, or red moons, lunar eclipses, etc.), the distance between the moon and the Earth (as described above, e.g., for supermoons), and / or moon quiver. In some embodiments, the additional moon attributes can be indicated by changing the appearance of the displayed moon simulation (e.g., by changing the color, size, and / or tilt of the displayed moon simulation). In some embodiments, the additional moon attributes can be indicated by text. In some embodiments, the additional moon attributes can correspond to the current moon attributes. In some embodiments, the additional moon attributes can correspond to the moon attributes for the currently displayed date (e.g., as described above, if the user has rotated the moon to view the moon at an earlier or later time in the month). For example, in some embodiments, when the moon simulation is being rotated to depict the moon at a different time in the month or year, the moon simulation can be updated to reflect the one or more additional moon attributes for the time currently indicated by the displayed moon simulation.

[0364] In some embodiments, the device can display additional moon information in response to user input. The additional moon information can be displayed, for example, as part of screen 902 or 920, or on a user interface screen that replaces screen 902 or 920 (such as a moon information application). The additional moon information can include, but is not limited to, the name of the moon phase, the distance from the Earth to the moon, the time of moonrise and / or moonset (e.g., for the current day and / or at the user's current location), etc. In some embodiments, the additional moon information can correspond to the current moon information (e.g., the current moon phase, distance to the moon, time of moonrise and / or moonset, etc.). In some embodiments, the additional moon information can correspond to the moon information for the currently displayed date, as described above, for example, if the user has rotated the moon to view the moon earlier or later in the month.

[0365] For example, in some embodiments, the device may detect user input (e.g., a double tap by a user on a touch-sensitive display, including a first contact on the touch-sensitive display and a second contact on the touch-sensitive display). In an exemplary embodiment, and in response to the user's double tap, the device may determine whether the first contact and the second contact are received within a predetermined interval. In response to detecting the user's double tap, and based on determining that the first contact and the second contact are received within the predetermined interval, the device may display additional moon information.

[0366] In some embodiments, after updating the display to show a simulation of the moon, the user interface screen displays an affordance indicating the earth (e.g., 910 or 928). Upon touching the earth affordance, the user can return to the reference Figure 8 In some embodiments, the earth affordance may be a graphical or stylized representation of the earth, such as an icon, symbol, or text indicating the earth. In some embodiments, the earth affordance may be a realistic representation of the earth.

[0367] In some embodiments, device 900 displays a sixth affordance on the user interface screen that represents the solar system (as depicted by affordances 810, 828, 848, 908, and 926). In some embodiments, the sixth affordance can be a graphical or stylized representation of the solar system, such as an icon, symbol, or text indicating the solar system. In some embodiments, the sixth affordance can be a realistic representation of the solar system.

[0368] Device 900 detects a contact on the displayed sixth affordance, and in response to detecting the contact, the device updates the display of the user interface screen by displaying a seventh affordance having representations of the sun, the earth, and one or more non-Earth planets at their respective positions at the current time, and an eighth affordance indicating the current time. In some embodiments, updating the display of the user interface screen includes animating the first affordance representing a simulation of a first area of the earth illuminated by the sun by zooming out of the display, or animating the fourth affordance representing a simulation of the moon as seen from the earth. The animation allows the user to recognize that the astronomical scale and / or angle has changed.

[0369] This transitions the user from viewing information about the current time in the current month using a simulation of the moon to viewing information about the current time in the current year using a simulation of the solar system. Figure 9 The described context-specific user interface provides the user with customizable information about the moon's conditions. Figure 10 , a context-specific user interface that provides a user with customizable information about the solar system and the relative positions of the Earth and other planets is illustrated in .

[0370] Figure 10 An exemplary context-specific user interface is shown that may be operated on device 1000. In some embodiments, device 1000 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0371] As described above, device 1000 is device 800 and / or device 900 with an updated display. Device 1000 displays screen 1002 including seventh affordance 1004. Seventh affordance 1004 includes a representation of the sun 1006, a representation of the earth 1008, and representations of Mercury, Venus, and Saturn (e.g., Saturn is depicted by planet 1010). 1006, 1008, and 1010 are depicted below the current date (in this example, May 25, 2014) indicated by eighth affordance 1012 at their respective locations. In some embodiments, eighth affordance 1012 also indicates the current time of day.

[0372] Alternatively, in some embodiments, the solar system depicts all eight planets. In some embodiments, the solar system depicts the four inner planets. In some embodiments, the solar system depicts other astronomical features, such as an asteroid or asteroid belt, one or more satellites (e.g., moons) of one or more planets, artificial satellites or other space probes, comets, Pluto, etc.

[0373] Device 1000 receives a seventh user input (e.g., movement 1018 of a rotatable input mechanism). In response, device 1000 updates a seventh affordance to depict the respective positions of the Sun, Earth, and one or more non-Earth planets for a non-current date. This is depicted by seventh affordance 1022 on screen 1020. Seventh affordance 1022 includes a representation 1024 of the Sun, a representation 1026 of Earth, and representations of Mercury, Venus, and Saturn (e.g., Saturn is depicted by planet 1028) at their respective positions for the non-current date indicated by eighth affordance 1030 (which is November 25, 2014). In some embodiments, eighth affordance 1030 also indicates the current time of day.

[0374] The context-specific user interface allows a user to access information about the relative positions of the Earth and one or more non-Earth planets for a non-current date, which can be within the current year or a different year. In some embodiments, the Sun, Earth, and one or more non-Earth planets are depicted as realistic representations. In some embodiments, the Sun, Earth, and one or more non-Earth planets are depicted as stylized or symbolic representations.

[0375] In some embodiments, a user can rotate the representation of the solar system by swiping on the touch-sensitive display. Thus, in some embodiments, the user input can include a swipe on the touch-sensitive display. In some embodiments, in response to detecting the swipe, the Earth and one or more non-Earth planets are caused to rotate about the Sun in a first rotational direction. In some embodiments, the first rotational direction can be based at least in part on the first swipe direction.

[0376] In some embodiments, in response to detecting a swipe in a different direction on the touch-sensitive display, the device causes Earth and one or more non-Earth planets to rotate about the sun in a second rotational direction that is different from the first rotational direction. This allows the user to direct both the rotational direction of Earth and one or more non-Earth planets and the time indicated by the eighth affordance in response to a swipe. For example, the user can swipe in one direction to rotate Earth and one or more non-Earth planets in a particular direction and view Earth and one or more non-Earth planets for a later date during that year (or in a different year), and the user can swipe in another direction to rotate Earth and one or more non-Earth planets in the opposite direction and view Earth and one or more non-Earth planets for an earlier date during that year (or in a different year).

[0377] In some embodiments, as Figure 10As shown, a user can rotate the representation of the solar system by rotating a rotatable input mechanism (e.g., 506). In these embodiments, the user input can include movement of the rotatable input mechanism in a first rotational direction (e.g., movement 1018). In some embodiments, in response to receiving the user input, the Earth and one or more non-Earth planets are rotated about the Sun in the first rotational direction. In some embodiments, the first rotational direction can be based at least in part on the direction of movement of the rotatable input mechanism.

[0378] In some embodiments, the device receives a second user input, and in response to receiving the second user input, the device causes the Earth and one or more non-Earth planets to rotate about the sun in a second rotational direction different from the first rotational direction. The user input may include, for example, movement of a rotatable input mechanism in the second rotational direction different from the first rotational direction.

[0379] This allows the user to direct both the direction of rotation of the Earth and one or more non-Earth planets and the time indicated by the eighth affordance in response to rotating the rotatable input mechanism. For example, the user can move the rotatable input mechanism in one direction to rotate the Earth and one or more non-Earth planets in a particular direction and view the Earth and one or more non-Earth planets at a later time during the year, and the user can move the rotatable input mechanism in another direction to rotate the Earth and one or more non-Earth planets in the opposite direction and view the Earth and one or more non-Earth planets at an earlier time during the year.

[0380] In some embodiments, the representation of Earth may further include a representation of Earth's orbit around the Sun. In some embodiments, the representation of one or more non-Earth planets may further include a representation of the orbits of one or more non-Earth planets around the Sun. The representation of the orbits may be a graphical representation, such as a line or a ring. In some embodiments, the representation of the orbits may be stylized. In some embodiments, the representation of the orbits may be based on the actual dimensions of the planetary orbits around the Sun.

[0381] The touch-sensitive display is contacted at a location associated with a representation of a non-Earth planet. For example, the contact may be at or near the displayed representation of the planet itself, or the contact may be at or near a representation of the displayed planet's orbit. In some embodiments, the device may determine the selected planet based on determining the displayed representation of the planet or the representation of the displayed planet's orbit that is closest to the contact location. In some embodiments, the contact may be a press-and-hold type contact on the display. Upon detecting the contact, the device may visually distinguish the representation of the selected planet and / or the representation of the selected planet's orbit (e.g., by changing the color and / or brightness of the displayed planet and / or orbit, by displaying an outline or other visual delineation of the planet and / or orbit, by animating the planet and / or orbit, etc.). In some embodiments, while continuing to receive the contact, the device may determine whether the duration of the contact exceeds a predetermined threshold, and upon determining that the duration of the contact exceeds the predetermined threshold, the device may visually distinguish the representation of the selected planet and / or the representation of the selected planet's orbit. When the user releases the contact, the device may display information about the selected planet. Such information may include, but is not limited to, the size of the planet, the distance between the planet and the Sun (e.g., current distance, average distance, etc.), the distance between the planet and Earth (e.g., current distance, average distance, etc.) (in the event that the selected planet is not Earth), the time and position in the sky when the planet will be visible from Earth (in the event that the selected planet is not Earth), the temperature of the planet's surface, the number of satellites orbiting the planet, the number and / or identification of any spacecraft currently orbiting or near the planet, a description of the planet (e.g., whether the planet is terrestrial or gaseous, the date of discovery of the planet, information about the name of the planet, etc.), a time (past, present, or future) when the planet will be specifically aligned with another object in the solar system, etc.

[0382] After viewing information about a planet, the user may wish to dismiss the information or view information about another planet. In some embodiments, the user can tap to dismiss the information or swipe to select another planet. For example, a swipe in a first direction may select the next planet whose orbit is farther from the sun than the previous planet, and a swipe in the opposite direction may select the next planet whose orbit is closer to the sun than the previous planet. In some embodiments, after displaying information about Earth or one or more non-Earth planets associated with a contact, the device may receive user input and determine (e.g., by detecting a user gesture using contact / motion module 130) whether the user input represents a tap or a swipe on the touch-sensitive display. Based on determining that the user input represents a tap, the device may remove the displayed information about the planet. Based on determining that the user input represents a swipe, the device may replace the displayed information about the planet with information about a second planet different from the first planet (e.g., a planet not associated with the user contact).

[0383] In some embodiments, after updating the display to show a simulation of the solar system, the user interface screen displays an affordance indicating the moon (e.g., 1016 or 1034) and / or an affordance indicating the earth (e.g., 1014 or 1032). In some embodiments, the moon and / or earth affordances may be graphical or stylized representations of the earth or moon, such as icons, symbols, or text. In some embodiments, the moon and / or earth affordances may be realistic renderings of the moon or earth. Upon touching the earth affordance, the user may return to the reference Figure 8 Describes a context-specific user interface. When touching the moon affordance, the user can return to the reference Figure 9 Describes a context-specific user interface.

[0384] exist Figures 8 to 10 In some embodiments of any of the context-specific user interfaces illustrated in , a user can move (e.g., rotate) a rotatable input mechanism to scroll a displayed time indication forward or backward in time. It should be appreciated that such a feature can be applied to any of the context-specific user interfaces described herein; however, for ease of illustration, reference may be made to Figures 8 to 10 to describe this feature. Any model for mapping movement of a rotatable input mechanism to scrolling distance or speed may be used, such as the model described in U.S. patent application Ser. No. 14 / 476,700, filed Sep. 3, 2014, “Crown Input for a Wearable Electronic Device,” which is incorporated herein by reference in its entirety. For example, acceleration, velocity, etc. may be used to determine the amount of speed at which the displayed time indication is adjusted.

[0385] In some embodiments, the user can move the rotatable input mechanism to scroll the time indication displayed on screens 802, 820, and / or 840. In response to detecting movement of the rotatable input mechanism (e.g., movement 830), the device can update the displayed representation of the Earth, for example by simulating the rotation of the Earth, to show the Earth illuminated by the sun at different times of the day (compare 822 and 842). In some embodiments, the device can update the displayed time indication to show different times (compare 822 and 844). Similarly, as Figure 9 As shown, in response to detecting movement of the rotatable input mechanism (e.g., movement 912), the device can update the displayed simulation of the moon to show different moon phases at different times of the month (e.g., compare 904 and 922), and / or update the displayed time indication to show different times (e.g., compare 906 and 924). Figure 10 As shown, in response to detecting movement of the rotatable input mechanism (e.g., movement 1018), the device may update the displayed position of the Earth and one or more non-Earth planets to show different positions relative to the Sun at different times of the year (e.g., compare 1008 and 1010 with 1026 and 1028), and / or update the displayed time indication to show different times (e.g., compare 1012 and 1030). In some embodiments, the representations of the position of the Earth, Moon, and / or Earth and one or more non-Earth planets may be rotated based on the direction of the movement of the rotatable input mechanism. In some embodiments, the representations of the position of the Earth, Moon, and / or Earth and one or more non-Earth planets may be rotated at a certain rate based on the rate and / or amount of movement of the rotatable input mechanism, for example, according to any of the models mentioned above. It should be appreciated that depending on the context-specific user interface displayed, movement of the rotatable input mechanism may cause the displayed time indication to be updated at different time scales. For example, the same rotation angle and / or rate may cause the displayed time indication to be updated at different time scales. Figure 8 The context-specific user interface shown in the is updated hourly, while Figure 9 The context-specific user interface shown in can be updated daily or weekly, or Figure 10 The context-specific user interface shown in can be updated by month or year.

[0386] exist Figures 8 to 10 In some embodiments of any of the context-specific user interfaces illustrated in , the device can indicate other global or astronomical features or objects, such as the real-time location of the International Space Station as described above. In some embodiments, the user can tap on the display (e.g., at a location corresponding to space), and in response to detecting the tap, the device can provide further information about the global or astronomical feature or object, such as the number of people currently in space, the number and / or names of spacecraft currently in space, etc.

[0387] Figure 11A An exemplary context-specific user interface is shown that may operate on device 1100. In some embodiments, device 1100 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0388] A user may wish to view the time of day in the context of daylight and nighttime hours. For example, a user may wish to know the time of dawn or dusk, or access a simple visual indication of how much time is left before sunset.

[0389] like Figure 11AAs shown, device 1100 displays a user interface screen 1102. User interface screen 1102 has two parts: a first part 1104 indicating daytime, and a second part 1106 indicating nighttime. Screen 1102 also displays a user interface object representing a sine waveform 1108. Sine waveform 1108 may represent the general appearance of a sine waveform without being mathematically accurate or precise. However, importantly, sine waveform 1108 has a period of approximately one day and indicates the path of the sun during the day. Figure 11A As shown, the trough of 1108 represents solar midnight (corresponding to two solar midnights being 24 hours apart), and the peak of 1108 represents solar noon of the day. Also displayed on screen 1102 is a first affordance 1110, which is displayed at a location along sine wave 1108, at a location indicating the current time of day. Screen 1102 also displays a horizon 1112 (an optional feature that separates the daytime and nighttime portions of the display). As shown, horizon 1112 intersects sine wave 1108 at two points, which represent sunrise and sunset. Finally, screen 1102 displays a second affordance 1114, which indicates the current time of day.

[0390] Throughout the course of a day, 1114 displays the current time (in this example, 5:30 AM), and first affordance 1110 tracks along a sine wave. When 1110 is in the daytime portion 1104, the current time is during the daytime. When 1110 is in the nighttime portion 1106, the current time is at night. At 5:30 AM, it is just before dawn because first affordance 1110 is still in the nighttime portion of screen 1102. This context-specific user interface feature provides the user with a simple and intuitive way to track the current time and understand, for example, how long until sunset or sunrise. In some embodiments, as shown by first affordance 1110, when the position is completely within the nighttime portion of the display (e.g., 1106), the affordance representing the sun appears hollow (e.g., like a ring). This further emphasizes to the user that it is currently before dawn.

[0391] For example, screen 1120 shows a second time of day and includes first affordance 1122, sine wave 1124, and second affordance 1126. As indicated by second affordance 1126, it is now sunrise time 7:00 AM. The position of first affordance 1122 along waveform 1124 is between the first portion and the second portion, indicating the transition from nighttime to daytime. This is further depicted on screen 1120 by positioning affordance 1122 on line 1128, which separates the two portions of the display. This is further indicated by the appearance of affordance 1122 itself, which can optionally be half-filled when located at the intersection of the first portion and the second portion of the display.

[0392] Screen 1130 shows a third time of day and includes a first affordance 1132, a sinusoidal waveform 1134, and a second affordance 1136. As indicated by second affordance 1136, it is currently 2:00 PM. The position of first affordance 1132 along waveform 1134 is within the first portion of the display, indicating daytime. This is further depicted by the appearance of affordance 1132 itself, which can optionally be fully filled when the affordance is in a position completely within the first portion.

[0393] In some embodiments, the color of the first portion and / or the second portion can indicate daytime (e.g., using warm or light colors) or nighttime (e.g., using dark or cool colors). In some embodiments, the first portion and the second portion can be the same color, which can represent the current lighting conditions. In these embodiments, the user can still be informed of the current lighting conditions by the appearance of the sinusoidal waveform, the optional horizon, and / or the optional sun display (e.g., fully filled, half-filled, or hollow). In some embodiments, the sinusoidal waveform can include two or more colors, and these colors can indicate the daytime and nighttime portions (e.g., portions of the waveform for the daytime portion can be one color, and portions of the waveform for the nighttime portion can be another color). In addition, the two portions can have arbitrary shapes (not limited to rectangles). For example, the daytime portion can appear as an illuminated circle containing the sinusoidal waveform, while the nighttime portion appears entirely around the circle.

[0394] In some embodiments, the device 1100 may have a location sensor (e.g., GPS sensor 532 and / or GPS module 135). In these embodiments, the device 1100 may obtain the current location of the device from the location sensor and indicate the daytime and nighttime hours at the current location and time by the ratio of the displayed first and second parts. That is, the size of the daytime and nighttime portions of the display may be adjusted relative to the daytime hours at the current location and date. As an illustrative example, if the current location is near the Arctic Circle during the summer, the daytime portion may include all or nearly all of the screen so that all or nearly all of the displayed sine waves are within the daytime portion. As another example, if the user were to travel around the globe along a latitude, the position of affordances 1110, 1112, or 1132 (for example) would not change, but the ratio of the daytime portion to the nighttime portion and the relative amount of the sine wave within each portion would be adjusted to reflect the current location. This provides the user with a more realistic depiction of the time of day, thereby enhancing the user interface.

[0395] In some embodiments, the amplitude of the displayed sine wave is based on the height of the sun relative to the horizon at the current location and time. For example, the waveform may be flattened or otherwise reduced in amplitude to reflect that the sun has a lower path across the sky at the current location (e.g., closer to the poles in winter).

[0396] Attention shifts Figure 11B , Figure 11B An example of such a context-specific user interface is illustrated that provides features with which a user can interact to view additional day / night information. Figure 11B 10:09 AM ...

[0397] When detected by device 1100, the user touches first affordance 1142 and drags the affordance in a continuous gesture along the sine wave to a second position (as indicated by touch 1166). In response, as shown on screen 1160, device 1100 displays first affordance 1162 at a second position along sine wave 1164. Device 1100 also updates second affordance 1168 to indicate a non-current time. This new time (12:09) corresponds to the time of day indicated by the second position of affordance 1162. Thus, the user is able to view the time of day represented by any position along the sine wave by simply moving affordances 1148 and / or 1166.

[0398] It should be noted that movement of the contact can start and end at a location on the sine wave, but the movement itself need not precisely track the trajectory of the sine wave. That is, the user is not required to precisely cause the contact to track along the sine wave. The device can receive user contact only at the displayed first affordance and, while continuously receiving user contact, detect movement of the contact from the first location to the second location without a break in user contact on the touch display (e.g., the user does not lift their finger from the touch-sensitive display).

[0399] In response to detecting contact at the second position, the device may translate the first affordance on the screen to the second position while following the trajectory of the sine wave. Thus, while the user contact does not need to follow the trajectory of the sine wave, the device nonetheless translates the first affordance from the first position to the second position by causing the first affordance to follow the trajectory along the sine wave. In some embodiments, the device may continuously update the time as indicated by the second affordance. Alternatively, the device may update the time indicated by the second affordance when continuous contact has ceased at the second position. In an alternative embodiment, after contact is detected at the first position, in response to rotation of the rotatable input mechanism, the device may translate the first affordance on the screen to the second position on the sine wave.

[0400] Figure 11BThe optional features of this context-specific user interface are illustrated. As shown on screen 1140, in response to receiving a user touch 1148 at affordance 1142, device 1100 displays affordances 1150 and 1152 that depict sunrise and sunset, respectively. Affordances 1150 and 1152 are displayed along waveform 1144 at two points where the waveform intersects the boundary between the first portion indicating daytime and the second portion indicating nighttime. This boundary is delimited on screen 1140 using an optional horizon line 1154. When horizon line 1154 is displayed, affordances 1150 and 1152 are displayed at two points where line 1154 intersects waveform 1144. In some embodiments, affordances 1150 and 1152 can further include numerical displays for sunrise and sunset times, respectively. In some embodiments, these affordances are also displayed while device 1100 receives a user touch at a second location.

[0401] Also displayed on screen 1140 in response to receiving user touch 1148 at affordance 1142 are affordances 1156 and 1158. Affordances 1156 and 1158 are displayed along waveform 1144 at positions corresponding to dawn and dusk, respectively. In some embodiments, these affordances are also displayed while device 1100 receives user contact at a second position. These displayed affordances indicate to the user when the first and last rays of light will occur, allowing the user to visually estimate when they will occur or how long ago they occurred by distance from affordance 1142. In some embodiments, the time of dawn can be astronomical dawn, maritime twilight, or civil twilight. In some embodiments, the time of dusk can be astronomical twilight, maritime twilight, or civil twilight.

[0402] In some embodiments, device 1100 detects contact, movement of contact, and interruption of contact at a displayed first affordance. In response to detecting the interruption of contact, the device can translate the first affordance back to a position indicating the current time and update the second affordance to indicate the current time. This allows the user to drag the affordance to a location of interest, view the time indicated for that location, and "snap back" to the current location by releasing contact.

[0403] Figure 11CIllustrated is another optional feature of this context-specific user interface. In some embodiments, particularly when the user interface screen is displayed on a display of reduced size, it may be desirable to display each element as large as possible for visibility. Screen 1170 displays a first available component 1172, a sine wave 1174, and a second available component 1176. As shown, available component 1176 intersects with waveform 1174. When the current time reaches 2:00, as shown on screen 1180, the position of available component 1182 indicating 2:00 intersects with the position of the second available component along waveform 1184. Device 1100 can determine whether the position of the first available component intersects with the second available component (for example, a position that overlaps with the second available component, is covered by the second available component, or otherwise appears close to the second available component). In response to determining that the available components intersect, the device can display the second available component at another non-intersecting position on the display. As illustrated on screen 1180, the position of affordance 1186 differs from the position of 1176 because the relative position of 1176 on the screen would intersect with first affordance 1182. This adjustment allows the device to display an information-rich screen without visual interference between displayed elements.

[0404] The user can also contact the touch-sensitive display using touch 1188 on screen 1180. This contact can, for example, be anywhere on the display other than the location of the first affordance representing the sun at the current time. In response to detecting the contact, device 1100 displays screen 1190, which includes sunrise time 1192, sunset time 1194, and affordance 1196 that provides a non-textual indication of daytime and nighttime. This allows the user to access sunrise and sunset times from any user interface screen.

[0405] The user can also set a reminder for a time of day through the context-specific user interface. For example, if the device has a rotatable input mechanism (e.g., 506), the user can rotate the rotatable input mechanism to set a reminder. In response to detecting movement of the rotatable input mechanism, the device can translate the first affordance to a third position indicating a non-current time of day. The user can contact the first affordance displayed at the third position, and in response to detecting the contact, the device can set a user reminder for the specified time of day.

[0406] For example, the device can display another affordance that indicates a user prompt for setting an alarm for a specified time of day. The reminder can be a visual alarm. In this example, the device can display a visual alarm displayed when approaching the time of day. Alternatively, the device can display a visual affordance at any time that shows a third position along the sine wave to help the user understand how far the specified time of day is from the current time. In some embodiments, the user reminder can include an audible alarm that notifies the user in an audible manner when the specified time of day has arrived or is about to arrive. In some embodiments, the user reminder can include a tactile alarm. The device can (e.g., using tactile feedback module 133 and tactile output generator 167) create a tactile signal to the user when the specified time of day approaches.

[0407] These features allow users to further customize this context-specific user interface. It should be appreciated that this feature does not create a specific alarm at a time and date; rather, it allows users to set a general alarm for a time of day that is not tied to a specific date. For example, a user may notice a specific lighting effect, such as sunlight shining through the windows of their home, and wish to set a reminder so that they observe this effect at the time of day when it occurs. In the context of day / night information, this allows users to customize the user interface to include not only sunrise, sunset, dawn, dusk, etc., but also the time of day they wish to specify.

[0408] Figure 12 An exemplary context-specific user interface is shown that may operate on device 1200. In some embodiments, device 1200 may be device 100, 300, or 500. In some embodiments, the electronic device has a touch-sensitive display (eg, touch screen 504).

[0409] A user may wish to view a particular background image on a user interface screen while retaining as much of the original image as possible. Therefore, it may be advantageous to provide a context-specific user interface that does not simply display the time and / or date as interface objects displayed over the image, but rather displays the time and / or date as interface objects that appear to be generated from the image itself, thereby maximizing the user's viewing of the image while still providing a visual indication of the time and date. This may be particularly true where the user interface is displayed on a display of reduced size.

[0410] like Figure 12 As shown, device 1200 is displaying user interface screen 1202, which includes background 1204. Background 1204 is based on an image of a seaside. In some embodiments, the image can be a photograph.

[0411] As used herein, consistent with accepted prior art meanings, the phrase "background" refers to the background of a user interface screen that is visually distinguishable from user interface objects and text also displayed in the user interface screen. An image-based background simply means displaying an image as the background of a displayed screen. In some cases, the image and background may be the same. In other cases, displaying an image as a background may involve modifying one or more aspects of the image to accommodate the display, such as image size, image cropping, image resolution, and the like.

[0412] Screen 1202 also includes user interface objects 1206 and 1208. 1206 indicates the date (23rd) and 1208 indicates the time of day (10:09). In some embodiments, the device may indicate the current date and / or the current time of day.

[0413] The displayed background 1204 includes a plurality of pixels. A subset of these pixels is modified in appearance relative to the image so that the subset represents one or more of user interface object 1206 and user interface object 1208. That is, at least one of these user interface objects is displayed by modifying the background. For example, the subset of pixels can be modified by changing color and / or intensity.

[0414] In certain embodiments, the subset of pixels can be modified by color mixing. In certain embodiments, the subset of pixels can be modified by color blur. In certain embodiments, the subset of pixels can be modified by applying a gradual change. Importantly, these illustrations can affect the outward appearance of the subset of pixels by the background image at the position of the user interface object and the user interface object itself. This allows the user to view the image more clearly (because the user interface object is not simply displayed on the top of the image and blocks the image), while also keeping the discernibility of the user interface object.

[0415] In some embodiments, one of user interface objects 1206 and 1208 is displayed by modifying the background, and another user interface object is displayed independently of the background (e.g., without the color and / or intensity set produced by modifying the background pixel subset). In these embodiments, device can receive the data representing background color at the position of displayed user interface object (e.g., 1206 or 1208), and the color of displayed user interface object can be different from this background color (e.g., different colors and / or intensity). For example, the background color at the position of displayed user interface object can be included in the color that is most prevalent at that position. This feature ensures that no matter how the outward appearance of background is, if one of the user interface objects is a preset color, it will be discernibly displayed on the background.

[0416] In some embodiments, the image on which the background is based may be stored on device 1200 .

[0417] In other embodiments, the image based on the background can be stored on an external device that is connected to the external device via wireless communication (e.g., Wi-Fi, Bluetooth TM , near field communication ("NFC"), or any other cellular and / or other wireless communication technologies described herein) is coupled to device 1200. In these embodiments, before displaying screen 1202, device 1200 may receive data representing the background from the external device (via wireless communication). Using this data, device 1200 may then display the background.

[0418] Alternatively, when an image is stored on an external device, device 1200 can display a background based on the current background of the external device. For example, the device can receive data representing the current background from the external device (via wireless communication) and display a user interface screen including a background corresponding to the current background of the external device. The device then modifies a subset of pixels of the background from the external device to represent one or more user interface objects in the user interface object indicating a date and the user interface object indicating the time of day. In some embodiments, device 1200 can, for example, further change the background from the external device by changing one or more of image size, image cropping, image resolution, etc., particularly when the external device and device 1200 have different display sizes and / or resolutions.

[0419] Return to Figure 12 , the user may wish to select an image from a folder of images to serve as a background. Thus, device 1200 may access a folder containing two or more images (e.g., the images shown on screens 1202 and 1210), select a first image, and display a user interface screen that includes a background (e.g., background 1204) based on the first image. As described above, the background includes a subset of pixels that are altered in appearance relative to the image to represent one or more of a user interface object indicating a date (e.g., 1206) and a user interface object indicating a time (e.g., 1208).

[0420] Alternatively, as Figure 12 As shown in , after displaying screen 1202, device 1200 may receive data representing user input. In response, device 1200 obtains data representing background 1204, selects a second image different from the first image from the folder, and displays screen 1210 including background 1212 based on the second image. Figure 12As shown in , backgrounds 1204 and 1212 are based on different images: a seaside scene and a mountain scene, respectively. This feature ensures that when the user decides to change the displayed background, the device displays a different background than the image displayed before the user input.

[0421] like Figure 12 As shown in the figure, screen 1210 also comprises the user interface object 1214 of indication date and the user interface object 1216 of indication time in one day.As described above, by revising the subset of the pixel of background 1212 at the position of shown user interface object, show at least one user interface object in these user interface objects.Can revise this subset in any way in the mode described above, such as color mixing, blurring, gradual change etc.In certain embodiments, as mentioned above, one in the user interface object can be the color independent of background, and equipment 1200 can revise this color to adapt to background.As described above, the image based on background can be stored on the equipment 1200 or on the external device.

[0422] A variety of user inputs can be used as user input to change the background. In some embodiments, the user input can be a touch on the display, rotation of a rotatable input mechanism, depression of a depressible and rotatable input mechanism, or a swipe on the display. In some embodiments, the user input can be a user movement of the electronic device (e.g., movement of the device such as raising the user's wrist when the device is wearable, or other movement indicating that the user is viewing the display). Advantageously, this feature enables the device to display a different image each time the display is viewed, thereby providing the user with a customized display each time the display is viewed, and enhancing the user's interaction with the device. As described above, user movement of the device can be detected, for example, by using an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or a combination thereof.

[0423] In some embodiments, the user may choose to exclude an image from a folder so that it is no longer selected as a background. In these examples, the device may receive data indicating that the user has excluded the image from the folder. Figure 12 In response to receiving this data, the device may prevent the image from being displayed as a background in response to future user input.

[0424] Figure 13AAn exemplary context-specific user interface is shown that may operate on device 1300. In some embodiments, device 1300 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0425] A user may wish to view an animation displayed on an electronic device in response to an input. Because a user may view an electronic device many times a day, especially if the user relies on a device for timekeeping, it may be advantageous to provide the user with a different experience each time the display is viewed. This keeps the user interested and engaged in the electronic device.

[0426] like Figure 13A As shown in FIG, in response to detecting a user input 1304 at 10:09, device 1300 displays user interface screen 1302. Screen 1302 includes a user interface object 1306 indicating the time and a user interface object 1308 depicting a butterfly. After displaying screen 1302, device 1300 animates butterfly 1308 by sequentially displaying three completely different animated sequences. The first animated sequence is illustrated by butterfly 1308, which depicts a butterfly opening its wings. Next, screen 1310 displays a second animated sequence, which depicts a butterfly 1314 flying from the right side of the display to the left side. Note that screen 1310 also displays a user interface object 1312 indicating the time. Finally, screen 1320 displays a third animated sequence, which depicts a butterfly 1324 closing its wings. Screen 1320 again displays user interface object 1322 indicating the time.

[0427] Later in the day, e.g. Figure 13B As shown in FIG, device 1330 detects a second user input 1332. In response, device 1300 accesses data representing the sequence of the previously displayed animated presentation (i.e., the sequence shown by butterfly 1314). Device 1300 displays screen 1330. Screen 1330 includes a user interface object 1334 indicating that the time is now 2:09 and a user interface object 1336 depicting a butterfly.

[0428] Device 1300 then animates butterfly 1336 by sequentially showing the sequence of three animations. Use the sequence identical with the butterfly 1308 on screen 1302 to animate butterfly 1336 on screen 1330, illustrate the butterfly that opens its wings. Next, screen 1340 illustrates butterfly 1334, and it is animated to fly from the left side of display to the right side. The sequence of the butterfly 1334 of animation is different from the sequence of the butterfly 1314 of animation on screen 1310 (having previously accessed the data of the sequence of expression butterfly 1314). This guarantees that the user will see that the animations compared with the previous user input are different. This makes the animation appear more real and / or attracts the user, because this variation gives the user interface object that is animated to be more random, lifelike quality.

[0429] Finally, screen 1350 shows butterfly 1354, which is animated using the same sequence (the butterfly closing its wings) as butterfly 1324 on screen 1320. Screens 1340 and 1350 also include user interface objects 1342 and 1352, respectively, that indicate time.

[0430] Figure 13A and Figure 13B Two butterflies (1336 and 1308) are shown displayed in response to user input. Butterfly 1330 is related to 1308, but is not necessarily the same. In some embodiments, user interface object 1336 can be the same as user interface object 1308. In other embodiments, user interface object 1336 can be an object related to, but not identical to, user interface object 1338. For example, these user interface objects can be animals of the same general type but with different appearances (e.g., different colors, different poses, different species, etc.).

[0431] The user interface object presented by the simulated animation can be an animal, such as a butterfly or a jellyfish, or it can be a plant like a flower. In some embodiments, it can be an inanimate object, a single-celled organism, a cartoon, a human being, etc. This context-specific user interface is not limited to a specific animated user interface object. The sequence of animation presentation can be specific to the displayed object. For example, a jellyfish can swim across the screen in various directions, a flower can open, close, or be blown by the wind, etc.

[0432] As illustrated by comparing butterfly 1308 with butterfly 1324, or butterfly 1336 with butterfly 1354, the third animated sequence can be based on the reverse of the first animated sequence. For example, if the first sequence depicts a butterfly with its wings open, the third sequence can depict a butterfly with its wings closed. Because these sequences run throughout the entire animated sequence, this feature gives the entire sequence a unified feel. In some embodiments, the state of the user interface object at the beginning of the first animated sequence (e.g., butterfly 1308 has its wings closed, which are then animated open) corresponds to the state of the user interface object at the end of the third animated sequence (e.g., butterfly 1324 is animated to end with its wings closed), thereby providing the user with the impression of a seamless animation.

[0433] Various user inputs can be used as user input to display the screen illustrated in FIG13 . In some embodiments, the user input can be a touch on the display, rotation of a rotatable input mechanism, depression of a depressible and rotatable input mechanism, or a swipe on the display. In some embodiments, the user input can be a user movement of the electronic device (e.g., movement of the device such as raising the user's wrist if the device is wearable, or other movement indicating that the user is viewing the display). Advantageously, this feature enables the device to appear to display a different animated presentation each time the display is viewed.

[0434] In some embodiments, the user interface object displayed in response to user input can be identical after each input.In some embodiments, user interface object can be different at each time.For example, user interface object can be reflected (for example, around horizontal and / or vertical axis), flipped and / or rotated, to create new user interface object.This is the source of the sequence diversity for displayed user interface object and animation presentation.For example, horizontally, vertically and horizontally and vertically rotating a single object creates four new objects, which creates even more variations when presenting coupling with the animation that guides the object to move.These aspects have added the possibility of combination, which has significantly increased the number that the available animation for a single object presents, therefore reducing the number of the sequence that preprogrammed animation presents.It also helps to utilize less features in nature and / or move to animate an object such as a jellyfish.

[0435] The user can also change the displayed user interface object. For example, device 1300 can detect a contact on the touch-sensitive display, and in response, device 1300 can replace the displayed user interface object with a second user interface object. The second user interface object can be related to the first user interface object (for example, if the previous butterfly was blue, the user can select an orange butterfly).

[0436] In some embodiments, as Figure 13A and Figure 13B As shown, the user interface object indicating the time can be a representation of a digital clock with numerical indications of hours and minutes (see, for example, objects 1306, 1312, 1322, 1334, 1342, and 1352). In some embodiments, the user interface object can display the current time in response to user input.

[0437] Figure 14A An exemplary context-specific user interface is shown that may be operated on device 1400. In some embodiments, device 1400 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (eg, touch screen 504).

[0438] A user may wish to keep track of the time with an interactive clock face. For example, a user may wish to see an animated presentation or a clock face that changes color each time the user views the display to keep interacting with the device interesting. A user may wish to customize the clock face with personalized complications such as a monogram or personalized widgets for displaying application data.

[0439] like Figure 14A As shown in , device 1400 turns off display 1402. In response to detecting user movement of device 1400 (e.g., motion 1404), device 1400 displays an animated clock face presentation. On screen 1410, device 1400 displays a clock face outline 1412 that is animated to appear to be filled or drawn in a clockwise manner. On screen 1420, device 1400 displays a complete clock face outline 1422 and hour and minute hands 1424. On screen 1430, device 1400 displays a complete clock face outline 1432, hour and minute hands 1434, and hour indications 1436 and 1438 (indicating 12 o'clock and 1 o'clock, respectively). As shown by comparing screens 1430 and 1440, these hour indications are displayed progressively in a clockwise direction.

[0440] On screen 1440, device 1400 displays a clock face outline 1442, hour and minute hands 1444, and a twelve-hour indication, as represented by 12 o'clock indication 1446. On screen 1450, device 1400 displays a clock face outline 1452, hour and minute hands 1454, a twelve-hour indication (as represented by 12 o'clock indication 1456), a minute indication 1458, and a letter combination 1460, which will be described in more detail below. Thus, as illustrated in FIG. 14 , the clock face is animated to gradually reveal its features.

[0441] Figure 14ATwo types of hour indications are depicted: a numerical hour indication (e.g., 3, 6, 9, and 12 as indicated by hour indications 1436, 1446, and 1456) and a symbolic hour indication (e.g., tick marks displayed between the numerical indications on screens 1440 and 1450). Either indication may be used alone or in combination. Any type of symbol may be used as the hour indication; the position around the clock face, rather than the symbol itself, conveys to the user which hour is being indicated. The numerals (or lack thereof) of the hour indication and / or minute indication may be further customized by the user, as will be discussed in greater detail below.

[0442] Figure 14A It is shown that one or more hour indications can be displayed in a clockwise manner (e.g., as depicted on screens 1430 and 1440, they can appear in a clockwise order). Similarly, the clock outline can optionally appear in a clockwise direction. This helps to orient the user. Optionally, the minute indication can appear in a clockwise manner. The hour and minute hands (and optionally the second hand) can also be animated, such as in a radial direction (e.g., starting from the center of the clock face and appearing to extend outward toward the outline). In some embodiments, the hour and minute hands appear first, followed by the hour indication, and then the minute indication. In some embodiments, the clock face shows the current time.

[0443] In some embodiments, the clock face may include color. Features such as the clock face background, the clock face outline, the second hand, the hour indicator, the minute indicator, the hour hand, the minute hand, etc. may be displayed in any color. In some embodiments, the device 1400 updates the color displayed on the clock face over time by continuously changing the color so that the user perceives the changes in time through the color changes. The color may be, for example, the background color, the color of the clock face itself, and / or the color of the second hand (e.g., the entire second hand, or a portion of the second hand, such as a pointer, a dot, or other optional feature). As an illustrative example, the color may be cycled through a gradual change of color, and the complete cycle may last for one minute, one hour, one day, etc.

[0444] In some embodiments, device 1400 can detect user movement of the device. As described above, user movement of the device can be detected, for example, by using an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or a combination thereof. User movement of the electronic device can include movements such as: movement of the device such as raising the user's wrist when the device is wearable, or other movements indicating that the user is viewing the display. In response to detecting user movement, device 1400 can display different colors (e.g., background color, the color of the clock face itself, and / or the color of the second hand). In some embodiments, this feature can be used to allow the user to change the static color displayed on the clock face. In other embodiments, as illustrated above, this feature can be used to allow the user to change a continuously changing color.

[0445] In some embodiments, device 1400 can display a complication on a clock face (e.g., within the clock face itself, or adjacent to the clock face on a display). As used herein, consistent with its accepted meaning in the art, a complication refers to any clock face feature other than those used to indicate the hours and minutes of the time (e.g., clock hands or hour / minute indication). For example, an affordance can be displayed as a clock face. As will be described in more detail below, an affordance can represent an application, and in response to detecting contact on the affordance, device 1400 can launch the application represented by the affordance.

[0446] Now return to Figure 14A In some embodiments, the monogram can be displayed as a complication. Screen 1450 shows a monogram offering 1460 displayed as a clock face complication. Device 1400 can receive data representing a name and, in response to receiving the data, generate a monogram and display the monogram as an offering 1460 (in this example, "MJ"). Device 1400 can receive the data from one or more sources such as a saved contact entry, a V-card, an image containing the monogram (e.g., an image taken or uploaded by a user), etc. In some embodiments, device 1400 has a user interface for monogram editing, which can be a feature of the user interface described in Figure 14, a separate user interface on device 1400, or a user interface on an external device that wirelessly communicates with device 400. It should be appreciated that these aspects (e.g., complications, monograms, and / or colors) can also be applied to any of the other context-specific user interfaces described herein. These features provide customizable elements that a user may wish to include to personalize one or more clock faces, thereby improving the user interface by increasing user interactivity.

[0447] Figure 14BAn exemplary user interface screen 14602 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices of 500 (Figure 5). The electronic device has a touch-sensitive display (e.g., touch screen 504).

[0448] Users rely on personal electronic devices to keep track of time throughout the day. There is an increasing desire to present users with interactive user interfaces that enhance their interaction with personal electronic devices. Indicating time through a character-based user interface can enhance user interaction with a device. Increasing the level of character interactivity and improving the impression of natural movement displayed by the character enhances the lifelike appearance of the character, thereby enhancing and extending the user's interaction with the device. By delivering a more realistic and interactive character-based user interface, the character-based interface is enabled to not only keep track of time but also provide information related to other events, further enhancing user interaction with the device.

[0449] Therefore, provided herein is a context-specific user interface comprising a character user interface object. For such a character-based user interface object, a user may wish to adopt a more natural and realistic appearance. In addition, for a character-based user interface object, a user may wish to act in a more dynamic manner to interact with the user and / or provide event-related information to the user.

[0450] Device 14000 may display a character user interface object on the display, such as character user interface object 14604. Character user interface object 14604 has representations of limbs 14606 and 14608. As shown on user interface screen 14602, character user interface object 14604 may indicate a time, e.g., 7:50, through the positions of limbs 14606 and 14608.

[0451] The character user interface object can include any representation of a character, for example, a human or an anthropomorphic character. In some embodiments, the character can be a cartoon image. In some embodiments, the character can be a real image. In some embodiments, the character can be a human, an animal, a plant, other organisms or other objects. In some embodiments, the character can be a popular character, such as a cartoon character.

[0452] Character user interface object 14604 can indicate the time by using a first limb (e.g., limb 14606) to indicate the hour and a second limb (e.g., limb 14608) to indicate the minute. In some embodiments, the character user interface object can be a static image that can be updated for different times. In some embodiments, the character user interface object can be animated and can depict movement. For example, the character user interface object can be animated to represent blinking, moving its center of gravity, and / or changing expression (e.g., facial expression).

[0453] As described herein, a character user interface object can indicate time with varying degrees of precision. Figure 14B As shown, the character user interface object can include one or more numerical indications of time values, i.e., digits indicating the hours, minutes, or seconds on a clock face. However, since users are accustomed to perceiving a clock face, the numerical indication of the time value is optional, as the relative positioning of two objects, like the hands of a clock, can indicate the approximate time without such a numerical indication.

[0454] Any of the user interface screens described herein may further include one or more complications, such as an indication of a date, a stopwatch, a chronograph, an alarm, or the like.

[0455] Additionally, a limb of a character user interface object can indicate time to the user in various ways. For example, a limb (e.g., an arm or leg) can indicate time by its relative position on the display, or by "pointing" to a location along a vector on the display. A limb can also indicate time by its relative position as described above, or by pointing along a vector to show an indicator of direction, such as a finger indicating a location on the display corresponding to the time. A limb need not indicate time precisely.

[0456] Device 14000 may update the character user interface object to indicate a second time by reversing the roles of the first limb and the second limb, i.e., indicating a second hour by using the second limb and indicating a second minute by using the first limb. Figure 14B 14600. A user interface screen 14610 is shown that may be displayed by device 14000. User interface screen 14610 includes a character user interface object 14612. Character user interface object 14612 may be the same character user interface object as character user interface object 14604, but may represent a different time.

[0457] As shown on user interface screen 14610, character user interface object 14612 is indicating the time, e.g., 8:20, via the positions of limbs 14614 and 14616. Comparing character user interface objects 14604 and 14612, both have a first limb (limbs 14606 and limb 14614, respectively) and a second limb (limbs 14608 and limb 14616, respectively). However, the first limb (limb 14606) of character user interface object 14604 is indicating the hours, while the first limb (limb 14614) of character user interface object 14612 is indicating the minutes. Similarly, the second limb (limb 14608) of character user interface object 14604 is indicating the minutes, while the second limb (limb 14616) of character user interface object 14612 is indicating the hours.

[0458] In some embodiments, the device 14000 can update the user interface object to indicate the second time by extending a first limb and retracting a second limb. Because the user may be accustomed to a standard clock face in which the hour hand is shorter than the minute hand, changing the extension and / or retraction of the limbs makes it easier for the user to keep track of the indicated time when their roles are reversed.

[0459] Since the character is allowed to maintain a natural appearance at all times, the character user interface object is allowed to use limbs with reversible roles to indicate time, thereby increasing the flexibility of displaying the character user interface object by allowing the character to maintain a natural appearance at all times. Otherwise, if the roles of the limbs are fixed, the character may be distorted in an awkward manner at a specific time of day (for example, between 12:30 and 12:40). Allowing the character to swap limbs gives more options for representing more natural-looking character poses and positions, thereby enhancing the user's interaction with the device by depicting more realistic character user interface objects.

[0460] Now turn Figure 14C In some embodiments, the user may wish to interact with a more natural-looking character user interface object. If a character user interface object indicates time using a limb that is always moving from a fixed position or character, this weakens the natural appearance of the character because the character's posture and / or range of motion are limited. This can result in awkward postures and / or a monotonous character appearance. Limbs can indicate time by representing animations that move freely from both endpoints of the limb, rather than by a representation of rotation around an axis that is always fixed by one endpoint, so that the character user interface object appears more natural at different times of the day.

[0461] It should be understood that descriptions of mechanical motion (eg, limb movement) used herein include showing representations or simulations of the mechanical motion.

[0462] Figure 14C An exemplary user interface screen 14702 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5).

[0463] Device 14000 can display a character user interface object, such as character user interface object 14704, on a display. Character user interface object 14704 has representations of limbs 14706. As shown on user interface screen 14702, character user interface object 14704 can indicate the time, such as the hour, such as 12, by the position of limbs 14706. In some embodiments, the character user interface object can be a static image that can be updated for different times. In some embodiments, the character user interface object can be animated and can depict movement.

[0464] Limb 14706 has a first endpoint 14708 at a first position that represents the axis of rotation of limb 14706. That is, the position of limb 14706 can be displayed or animated so as to represent rotation about endpoint 14708 to indicate different times of day. Limb 14706 also has a second endpoint 14710 at a second position that indicates a time value. In some embodiments, the time value can be hours, minutes, and / or seconds.

[0465] Device 14000 can update character user interface object 14704 to indicate the second time value by moving first endpoint 14708 to the third position and second endpoint 14710 to the fourth position to indicate the second time value. Importantly, while first endpoint 14708 serves as the axis of rotation for limb 14706, first endpoint 14708 itself can also be moved to indicate time. Consequently, limb 14706 can adopt more natural poses because its positioning is given greater flexibility. This enhances the realistic appearance of the character.

[0466] As an example, user interface screen 14720 shows a character user interface object 14722 having a limb 14724 with a first endpoint 14726 and a second endpoint 14728. Character user interface object 14722 may be a display of updated character user interface object 14704. Compared to user interface screens 14702 and 14720, specifically limbs 14706 and 14724, the position of the first endpoint has been updated, as reflected by the positions of first endpoints 14708 and 14726. First endpoint 14726 is in a third position, and second endpoint 14728 is in a fourth position to indicate a second time. As shown on user interface screens 14702 and 14720, limb 14706 has been updated to limb 14724 by (i) moving the position of the first endpoint and (ii) rotating the limb about the rotation axis.

[0467] In some embodiments, a character user interface object may include a representation of a second limb, such as second limb 14712. Like the first limb, second limb 14712 also has a first endpoint 14714 and a second endpoint 14716, with first endpoint 14714 being the axis of rotation for second limb 14712. The position of second endpoint 14716 may indicate a third time value. For example, limb 14706 may indicate an hour value, and limb 14712 may indicate a minute value. Device 14000 may update character user interface object 14704 to indicate a fourth time value by moving first endpoint 14714 of second limb 14712 to a third position, and to indicate the second time value by moving second endpoint 14716 to a fourth position. This is depicted on user interface screen 14720, which depicts second limb 14730 with first endpoint 14732 at a third position and second endpoint 14734 at a fourth position.

[0468] As described above, the first limb and the second limb of the character user interface object can each have two endpoints, each of which can change their position. In some embodiments, the first limb is connected to the torso at a first shoulder, and the second limb is connected to the torso at a second shoulder. In some embodiments, the torso is connected to the movement of each limb through each shoulder so that the position of one shoulder can affect the position of the other shoulder. This feature adds to the realistic and natural appearance of the character by coordinating or otherwise relating the movement of the two limbs, just like a moving human body.

[0469] Figure 14D An exemplary user interface screen 14802 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices of 500 (Figure 5).

[0470] Device 14000 may display a character user interface object on the display, such as character user interface object 14804. Character user interface object 14804 has representations of limbs 14806. As shown on user interface screen 14802, character user interface object 14804 may indicate a time, such as the hour, such as 12, through the position of limbs 14806.

[0471] Limb 14806 has a first segment 14808 having a first endpoint 14810 at one end and a joint 14812 at the other end. First endpoint 14810 has a first position. Limb 14806 also has a second segment 14814 having a second endpoint 14816 at one end and a joint 14812 at the other end. Thus, first segment 14808 and second segment 14814 are connected at joint 14812, which serves as the axis of rotation for second segment 14814. Second endpoint 14816 at the end of second segment 14814 (and therefore at one end of limb 14806) has a second position and indicates a first time value, for example, hours, such as 12.

[0472] Device 14000 can update character interface object 14804 to indicate a second time value by moving second endpoint 14814 along the rotational axis to a third position to indicate the second time. Described in anthropomorphic terms, limb 14806 has a representation of an upper arm 14808 joined at an elbow 14812 and a forearm 14814. Forearm 14814 can rotate at elbow 14812 to indicate different times. Adding joints to a limb that indicates time is similar to the hand of a clock, except that the arm appears more natural than a clock hand because it includes joints. Furthermore, joints increase the possible range of motion that can be depicted by the limb.

[0473] User interface screen 14820 illustrates this by displaying a character user interface object 14822 having a limb 14824. In some embodiments, the character user interface object can be the same object as character user interface object 14804 but in a different pose. Limb 14824 has a first endpoint 14826, a first segment 14828, and a joint 14830. Joint 14830 is connected to a second segment 14832 having a second endpoint 14824. As shown by comparing the features of character user interface objects 14804 and 14822, second endpoint 14834 is in a different position than second endpoint 14816, thereby indicating a different time. This change in position is achieved by rotating the second segment at the joint.

[0474] In some embodiments, moving the second endpoint may include a static image depicting the second endpoint at the first position and the third position. In some embodiments, moving the second endpoint may include animating a character user interface object to translate the motion of the second endpoint on the screen.

[0475] In some embodiments, updating the character user interface object may include moving a first endpoint. As shown in the transition from user interface screen 14802 to user interface screen 14820, first endpoint 14810 may be moved to change the display of time, for example, as shown by first endpoint 14826. Thus, the character user interface object may have a limb that, in the arm analogy above, may rotate the upper arm at the shoulder, move the shoulder itself, and rotate the forearm at the elbow.

[0476] These features allow the character user interface object to assume a wider range of natural and realistic poses and use them to indicate time. If these features are animated on the screen, this allows the character to simulate the movements of a moving image such as a person. This significantly improves the user's interaction with and connection to the device by more accurately simulating a moving image that behaves like a person. It allows for subtle and dynamic movements, which gives the character a wider range of expression, which helps to simulate the character's personality. As a result, the character is no longer a simple aggregation of two clock hands that can only tell the time, but becomes more like a real person with personality, thereby improving the user's experience with the device.

[0477] In some embodiments, the character user interface object (e.g., character user interface object 14804 and / or 14822) also includes a representation of a second limb, such as second limb 14818 shown on user interface screen 14802 or second limb 14836 shown on user interface screen 14820. As described above with reference to the first limb, the second limb can include a first segment connecting the first endpoint of the second limb to a joint, and a second segment connecting the second endpoint to the joint. The first endpoint of the second limb can be at a first position, and the second endpoint of the second segment can be at a second position. The joint can serve as an axis of rotation for the second segment, which can indicate a third time value. The device 14000 can update the character user interface object by moving the second endpoint of the second limb along the axis of rotation at the joint to indicate a fourth time value.

[0478] In some embodiments, the first limb indicates the hour and the second limb indicates the minute. In some embodiments, the first limb indicates the minute and the second limb indicates the hour. The first limb and the second limb can be distinguished, for example, by their length, from the length of conventional clock hands. The first limb and the second limb can be distinguished, for example, by the distance between the first endpoint and the second endpoint. For example, a limb can be bent or the shoulder can be positioned so that, although the limb may not be shorter than the other limb, it appears shorter or otherwise different from the other limb. For example, the first limb and the second limb can be distinguished by the distance between the second endpoint and another object on the display, such as a numerical time indicator.

[0479] In some embodiments, updating the character user interface object to indicate the second time can include animating the character user interface object by translating the first endpoint on the screen. For example, the character can appear to move one or both shoulders. In some embodiments, the position or movement of one shoulder can affect the position or movement of another shoulder, simulating the movement of a connected real-life figure, such as a human.

[0480] In some embodiments, updating the character user interface object to indicate the second time may include animating the character user interface object by rotating the second segment at the joint on the screen. For example, the second segment may rotate at the joint like a forearm.

[0481] In some embodiments, the character user interface object may also translate on the screen, for example, towards the center of the display.

[0482] Figure 14E An exemplary user interface screen 14902 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 14904 on the display. User interface screen 14902 shows the translation of the character by sequentially displaying character user interface object 14904 at two different positions, first at position 14906 and then at position 14908. Character user interface object 14904 is closer to the center of the display at position 14908, thus simulating the translation of the character. Figure 14E A motion such as this one may be used, for example, when a user initiates interaction with a device or looks at the device, causing a character to move toward the center of the display and indicate the time.

[0483] In some embodiments, translating the character user interface object can include animating the character user interface object to represent, for example, walking toward the center of the display. The character user interface object 14904 is illustrated by depicting a character having legs and a torso. Walking is represented by the different positions and postures represented by the legs and torso of the character user interface object 14904 at positions 14906 and 14908. For example, in response to the interaction of the user with the device, the character can be animated to naturally walk onto the screen and then assume a position corresponding to the current time. User interaction can include activating the screen, raising the device to a viewing position, pressing a button corresponding to an activating clock face on the device, etc.

[0484] Figure 14F 1 shows an exemplary user interface screen 15002 that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15004 on the display. Device 14000 can change the visual aspects of the displayed user interface screen to highlight the character user interface object. Figure 14F An exemplary embodiment of this concept is illustrated. The character user interface object 15002 includes a spotlight 15006 that highlights the character user interface object 15004 .

[0485] In some embodiments, changing a visual aspect of the display may include one or more of: changing the color and / or brightness of the user interface screen around a character user interface object, displaying a character user interface object such as a spotlight, and the like.

[0486] In some embodiments, the device 14000 may animate the character user interface object to represent a response by the character user interface object to a change in the visualization aspect. Figure 14F As shown in the exemplary embodiment of FIG, the character user interface object 15004 can be animated to simulate looking at the spotlight 15006.

[0487] Figure 14G 1, 2, and 3. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 ( Figure 3) and / or one or more devices in 500 ( FIG. 5 ). Device 14000 may display a character user interface object, such as character user interface object 15104, on a display. Character user interface object 15104 may include a representation of a foot 15106. In some embodiments, character user interface object 15104 includes two limbs and two legs indicating a time value, at least one of the legs may include a foot.

[0488] In some embodiments, device 14000 can animate a foot to indicate the passage of time. As shown on user interface screens 15102 and 15110, character user interface objects 15104 and 15112 include feet (respectively 15106 and 15114). The different positions (different in the position on the display and / or in the character user interface object, their posture) of feet 15106 and 15114 depict this animation. For example, the character can be animated to simulate the movement of a foot, such as tapping. This can have regular or irregular timing. In some embodiments, the foot is animated to move at regular intervals (such as, once per second). When coupled with two limbs, this allows the character user interface object to depict the time value of, for example, hours, minutes, and seconds.

[0489] In some embodiments, the first time and the second time depicted by the character user interface object are the same. In other words, the character user interface object can be moved by displacing a limb or any endpoint of a limb without depicting a different time. This allows the character to change poses without changing the indicated time.

[0490] In some embodiments, the display may include one or more numerical indications of time. For example, the display may include a representation of a circular clock face with a character user interface object in the center surrounded by numerical indicators, like a clock.

[0491] The features described above make the character user interface object appear more natural and realistic by adopting a wider range of natural motion while indicating time. The user may wish to view the representation of other events by the character user interface object. Allowing the character user interface object to react to external incentives or internal system events, depicting more interactive characters, therefore depicting a closer personality representation. The interactivity of the enhanced character further improves the interaction between the user and the device by providing additional notifications that an event has occurred, and the occurrence of the event may not be as obvious as in other cases. The character user interface object can be used as providing notifications, reminders and / or other information that the user may wish to access from a personal electronic device, but the use of the character provides that the device can be used to provide the interactive personalization of these items. In addition, making the character respond to internal system events (e.g., calendar events, etc.) means that the character is not strictly limited to responding to external user input. In other words, the character appears to have a more realistic personalization because it responds to events that are not directly driven by the user's immediate action.

[0492] Figure 14H An exemplary user interface screen 15202 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15204 on the display. Character user interface object 15204 indicates time as described above.

[0493] Device 14000 may receive first data indicating an event. Device 14000 may determine whether the event satisfies a condition. Based on determining that the event satisfies the condition, device 14000 may update character user interface object 15204 by changing a visual aspect of the character user interface object.

[0494] In some embodiments, after updating the displayed character user interface object, the character user interface object still indicates the time. For example, the appearance or posture of the character can be changed, but the character still indicates the time.

[0495] In some embodiments, after the displayed character user interface object is updated, the character user interface object no longer simply indicates the time. For example, the character may adopt gestures, assume facial expressions, or use its body parts for functions other than indicating the time (such as conveying meaning related to events and / or conditions).

[0496] In some embodiments, the first data indicates a calendar event. Device 14000 may receive data indicating a calendar event, for example, by obtaining data representing the event from a calendar application on device 14000. In this example, the condition may correspond to a duration of the calendar event. Determining whether the event satisfies the condition may include determining whether the current time is within the duration of the calendar event. For example, device 14000 may obtain the current time and determine whether the current time is within the duration of the calendar event (e.g., during the calendar event, or substantially synchronized with the calendar event but slightly ahead or slightly behind).

[0497] An exemplary embodiment is shown on user interface screen 15202. In some embodiments, the calendar event is a birthday. In some embodiments, the birthday is the user's birthday. In some embodiments, updating the displayed character user interface object may include animating the character user interface object to display birthday greetings. Animating the character user interface object 15204 to display a holiday hat 15206 and a birthday slogan 15208. This animation serves to notify the user of the birthday while making the character more interactive. Importantly, the character can change the visual aspect, such as by displaying birthday greetings without the user's immediate input, thereby giving the impression that the character can act more autonomously, as if with personality. In some embodiments, the modification of the character is an indication of some important events (such as their birthdays, anniversaries, etc.) relevant to a contact in the user's contacts.

[0498] An exemplary embodiment is shown on user interface screen 15202. In some embodiments, the calendar event is a holiday. In some embodiments, updating the displayed character user interface object may include changing the visual aspects of the character user interface object to reflect the holiday. In this example, character user interface object 15212 is depicted by a Santa Claus hat 15214. This animation serves to inform the user of the holiday while making the character more interactive and reducing the monotony of the character's appearance. Other examples of holidays other than Christmas may include New Year's Eve or New Year's Day, Thanksgiving, Hanukkah, Independence Day, St. Patrick's Day, Valentine's Day, etc.

[0499] In some embodiments, device 14000 can receive data indicating user preferences, such as a user's favorite sports team. Based on the received data, device 14000 can update character user interface object 15204 by changing the visual aspects of the character user interface object to reflect the sports team. For example, the appearance of the character user interface object can be updated to depict a character user interface object wearing a uniform or other equipment representing a sports team (e.g., a hat, a jersey, a uniform, or other representations including a logo, an icon, or text representing a sports team). The display can also be updated to include a second user interface object together with the character user interface object, which represents a sports object associated with the team's sport (e.g., a baseball bat and / or baseball, rugby, basketball, soccer, hockey stick and / or hockey puck, a checkered flag, etc.). The character can also be updated based on determining that the team is playing on that day or at that time, or based on determining that the user is about to attend an event featuring the team. The user can be determined to attend an event featuring the team by analyzing the user's calendar events or by determining that an event electronic ticket is presented on an electronic device or a paired electronic device. It should be understood that a user's favorite sports team is merely an exemplary user preference, and that other user preferences, such as representations of flags or countries, are also contemplated.

[0500] Figure 14I An exemplary user interface screen 15302 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15304 on the display. Character user interface object 15304 indicates time as described above.

[0501] Device 14000 may receive data indicating a notification. The notification may include, for example, an email, text message, reminder, virtual assistance request, or other such notification. As depicted by notification 15306, device 14000 may further display a notification or affordance or user interface object on user interface screen 15302 indicating the receipt and / or content of the notification. Device 14000 may animate a character user interface object 15304 in response to notification 15306. For example, as shown on user interface screen 15302, character user interface object 15304 may appear to be looking at notification 15306. This may include, for example, a change in posture so that the character is facing the notification, or a change in the character's appearance, such as a face, to indicate that the character is looking in the direction of the notification. Similarly, by providing this change in posture or a change in the character's focus, the user may be notified of an incoming alert or event that might otherwise have been less apparent.

[0502] Figure 14J An exemplary user interface screen 15402 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15404 on the display. Character user interface object 15404 indicates time as described above.

[0503] Device 14000 may receive first data indicating a time of day. The time of day may include the current time. Device 14000 may determine that the time of day satisfies a condition, such as by determining whether the time of day falls within the nighttime portion of the day. Device 14000 may change the visual aspects of a character user interface object 15404 to indicate nighttime. As shown in user interface screen 15402, character user interface object 15404 represents nighttime by depicting a person yawning and holding a candle 15406. In some embodiments, character user interface object 15404 may be altered to depict the person wearing clothing associated with nighttime, such as pajamas. In some embodiments, the character user interface object is modified to depict the person yawning or wearing pajamas based on a determination that the user should be going to bed. This determination may be based on any of the following: a preset time, identification of the user's sleep patterns, an indication of an early event on the next day's calendar, identification that the user has been active for longer than a predetermined time, etc.

[0504] Figure 14K An exemplary user interface screen 15502 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15504 on the display. Character user interface object 15504 indicates time as described above.

[0505] Device 14000 can receive the data indicating the current time. Device 14000 can determine whether the current time corresponds to the hour on the hour (e.g., 1:00, 2:00, etc.). Device 14000 can determine whether the current time corresponds to the hour on the hour, if so, then animation presents a character user interface object to announce the hour on the hour for one or more hours. As shown in user interface screen 15502, character user interface object 15504 announces the current hour by depicting musical note 15506. In certain embodiments, the announcement of the hour can include such as by displaying a user interface object to the visual depiction of the announcement. In certain embodiments, the announcement of the hour can include sounds such as whistles, buzzers, one or more read-aloud words or bells.

[0506] Figure 14L 15602 shows an exemplary user interface screen that device 14000 may display on its display. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15604 on the display. Character user interface object 15604 indicates time as described above.

[0507] Device 14000 can receive data indicating current or forecast weather. To receive data indicating current or forecast weather, device 14000 can retrieve weather information from an external server. In some embodiments, device 14000 can retrieve weather information from a weather service, such as The Weather Channel, Accuweather, The National Weather Service, Yahoo! TM Weather, Weather Underground, etc.

[0508] The device 14000 may determine whether the current or forecast weather corresponds to one or more specified weather conditions. The specified weather conditions may be system specified and may include favorable weather conditions such as sunny days, or inclement weather conditions such as rain, thunderstorms, wind, snow, etc. If the device 14000 determines that the current or forecast weather corresponds to one or more specified weather conditions, the device 14000 may update the character user interface object to reflect the current or forecast weather. For example, Figure 14L, user interface screen 15602 includes a human user interface object 15604 with an umbrella 15606, and raindrops 15608. In some embodiments, device 14000 can display human user interface objects to reflect specified weather conditions. In some embodiments, human user interface objects can be animated to react to human user interface objects reflecting specified weather conditions. As another example, user interface screen 15610 displays human user interface objects 15612 with sunglasses 15614 and a surfboard 15616, and a sun 15618.

[0509] Figure 14M An exemplary user interface screen 15702 is shown that the device 14000 may display on its display. In some embodiments, the device 14000 may be the device 100 (FIG. 1), 300 ( Figure 3 ) and / or one or more devices in 500 (Figure 5). Device 14000 can display a character user interface object such as character user interface object 15704 on the display. Character user interface object 15704 indicates time as described above.

[0510] Device 14000 may receive data indicating a second electronic device. Device 14000 may determine whether the data corresponds to a threshold proximity of the second electronic device to device 14000. If so, device 14000 may update character user interface object 15704 by animating a character user interface object to react to the second electronic device. As shown in user interface screen 15702, character user interface object 15704 may depict a thumbs-up 15706 or a smile 15708. In some embodiments, the character user interface object's posture may be updated to reflect the proximity and / or direction of the second device. For example, the character user interface object may react to the device's direction or may be reflected on a display. In some embodiments, the data indicating the second electronic device may be provided by a server, such as Find My Friends, which may provide the location of user contacts who have agreed to provide their location data. The data indicating the second electronic device may also be provided via a local network (e.g., identifying that one of the user contacts has joined the same WiFi network). The data indicating the second electronic device may also be provided by the second electronic device itself (e.g., a second electronic device that announces itself via Bluetooth, near-field communication, etc.).

[0511] In some embodiments, a device (such as device 14000) that displays a character user interface object indicating time can receive data indicating user activity. For example, the device may include a user activity monitor (such as a workout monitor), an accelerometer, a gyroscope, a motion sensor, and / or a combination thereof. The device can determine whether data indicating user activity ...

Claims

1. A method comprising: At a device having a display, a rotatable input mechanism, and one or more processors: receiving first data related to a first topic and second data different from the first data, wherein the second data is related to a second topic different from the first topic; displaying first information related to the first portion of the received first data; displaying third information related to the received first part of the second data; detecting a first rotation of the rotatable input mechanism; as well as In response to detecting the first rotation of the rotatable input mechanism: supplementing the first information with second information associated with a second portion of the received first data; as well as The third information is supplemented with fourth information related to the received second portion of the second data. 2 . The method of claim 1 , wherein displaying the first information comprises displaying the first information in a first predetermined portion of a user interface. 3 . The method of claim 2 , wherein supplementing the first information with second information comprises displaying the second information in the first predetermined portion of the user interface.

4. The method of any one of claims 1 to 3, wherein supplementing the first information with second information comprises maintaining display of the first information at a position of the display where the first information was displayed prior to detection of the rotatable input mechanism.

5. The method according to any one of claims 1 to 3, wherein: The first portion of the data corresponds to a first privacy level, and The second portion of the data corresponds to a second privacy level.

6. The method according to any one of claims 1 to 3, wherein: The first information is displayed in a first font size; and The second information is displayed in a second font size that is smaller than the first font size.

7. The method according to any one of claims 1 to 3, wherein: The first information comprises a single line of text; and The second information includes two or more text lines.

8. The method according to claim 1, further comprising: displaying a first editing interface for editing a first display setting corresponding to the first information and the third information, When the first editing interface is displayed: detecting a first touch input at a position corresponding to the first information, in response to detecting the first touch input at the position corresponding to the first information, highlighting the first information; detecting a second rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the second rotation of the rotatable input mechanism, a first color setting corresponding to the first information is edited.

9. The method according to claim 8, further comprising: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, maintaining a second color setting corresponding to the third information.

10. The method according to claim 8, further comprising: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, a second color setting corresponding to the third information is edited.

11. The method according to claim 8, further comprising: When the first editing interface is displayed, detecting a horizontal swipe gesture; as well as In response to detecting the horizontal swipe gesture, a second editing interface is displayed for editing a second display setting corresponding to the first information and the third information.

12. The method according to claim 1, further comprising: displaying a third editing interface for editing a third display setting corresponding to the first information and the third information; When the third editing interface is displayed: detecting a second touch input at a position corresponding to the first information; in response to detecting the second touch input at the position corresponding to the first information, highlighting the first information; detecting a third rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the third rotation of the rotatable input mechanism, the first information is replaced with fourth information corresponding to a subject different from the first subject.

13. The method according to claim 12, further comprising: When the third editing interface is displayed: In response to detecting the third rotation of the rotatable input mechanism, display of the third information is maintained.

14. The method according to any one of claims 1 to 3, further comprising: detecting a fourth rotation of the rotatable input mechanism; as well as In response to detecting the fourth rotation of the rotatable input mechanism, the first and second information are supplemented with fourth information associated with a third portion of the received data.

15. The method according to any one of claims 1 to 3, wherein the first information and the second information do not include icons, images, glyphs or logos.

16. The method according to any one of claims 1 to 3, wherein displaying the first information related to the first portion of the received data occurs when the device is in a first state and the second information related to the second portion of the received data is not displayed, the method further comprising: In response to detecting the first rotation of the rotatable input mechanism, changing from the first state to a second state. The method of claim 16 , wherein the first state is a first privacy state and the second state is a second privacy state.

18. A computer-readable storage medium comprising one or more programs for execution by one or more processors of an electronic device having a display and a rotatable input mechanism, the one or more programs comprising instructions for: receiving first data related to a first topic and second data different from the first data, wherein the second data is related to a second topic different from the first topic; displaying first information related to the first portion of the received first data; displaying third information related to the received first part of the second data; detecting a first rotation of the rotatable input mechanism; as well as In response to detecting the first rotation of the rotatable input mechanism: supplementing the first information with second information associated with a second portion of the received first data; as well as The third information is supplemented with fourth information related to the received second portion of the second data.

19. The computer-readable storage medium of claim 18, wherein displaying the first information comprises displaying the first information in a first predetermined portion of a user interface.

20. The computer-readable storage medium of claim 19, wherein supplementing the first information with second information comprises displaying the second information in the first predetermined portion of the user interface.

21. The computer-readable storage medium of any one of claims 18 to 20, wherein supplementing the first information with second information comprises maintaining display of the first information at a location of the display where the first information was displayed prior to detection of the rotatable input mechanism.

22. The computer-readable storage medium according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: the first portion of the data corresponds to a first privacy level, and The second portion of the data corresponds to a second privacy level.

23. The computer-readable storage medium according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: The first information is displayed in a first font size; and The second information is displayed in a second font size that is smaller than the first font size.

24. The computer-readable storage medium according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: The first information comprises a single line of text; and The second information includes two or more text lines.

25. The computer-readable storage medium of claim 18, wherein the one or more programs further comprise instructions for: displaying a first editing interface for editing a first display setting corresponding to the first information and the third information, When the first editing interface is displayed: detecting a first touch input at a position corresponding to the first information, in response to detecting the first touch input at the position corresponding to the first information, highlighting the first information; detecting a second rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the second rotation of the rotatable input mechanism, a first color setting corresponding to the first information is edited.

26. The computer-readable storage medium of claim 25, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, maintaining a second color setting corresponding to the third information.

27. The computer-readable storage medium of claim 25, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, a second color setting corresponding to the third information is edited.

28. The computer-readable storage medium of claim 25, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed, detecting a horizontal swipe gesture; and In response to detecting the horizontal swipe gesture, a second editing interface is displayed for editing a second display setting corresponding to the first information and the third information.

29. The computer-readable storage medium of claim 18, wherein the one or more programs further comprise instructions for: displaying a third editing interface for editing a third display setting corresponding to the first information and the third information; When the third editing interface is displayed: detecting a second touch input at a position corresponding to the first information; in response to detecting the second touch input at the position corresponding to the first information, highlighting the first information; detecting a third rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the third rotation of the rotatable input mechanism, the first information is replaced with fourth information corresponding to a subject different from the first subject.

30. The computer-readable storage medium of claim 29, wherein the one or more programs further comprise instructions for: When the third editing interface is displayed: In response to detecting the third rotation of the rotatable input mechanism, display of the third information is maintained.

31. The computer-readable storage medium of any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: detecting a fourth rotation of the rotatable input mechanism; and In response to detecting the fourth rotation of the rotatable input mechanism, the first and second information are supplemented with fourth information associated with a third portion of the received data.

32. The computer-readable storage medium of any one of claims 18 to 20, wherein the first information and the second information do not include icons, images, glyphs, or logos.

33. The computer-readable storage medium of any one of claims 18 to 20, wherein displaying the first information associated with the first portion of the received data occurs when the device is in a first state and the second information associated with the second portion of the received data is not displayed, the one or more programs further comprising instructions for: In response to detecting the first rotation of the rotatable input mechanism, changing from the first state to a second state.

34. The computer-readable storage medium of claim 33, wherein the first state is a first privacy state and the second state is a second privacy state.

35. An electronic device comprising: monitor; a rotatable input mechanism; one or more processors; as well as A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: receiving first data related to a first topic and second data different from the first data, wherein the second data is related to a second topic different from the first topic; displaying first information related to the first portion of the received first data; displaying third information related to the received first part of the second data; detecting a first rotation of the rotatable input mechanism; as well as In response to detecting the first rotation of the rotatable input mechanism: supplementing the first information with second information associated with a second portion of the received first data; as well as The third information is supplemented with fourth information related to the received second portion of the second data.

36. The electronic device of claim 35, wherein displaying the first information comprises displaying the first information in a first predetermined portion of a user interface.

37. The electronic device of claim 36, wherein supplementing the first information with second information comprises displaying the second information in the first predetermined portion of the user interface.

38. The electronic device of any of claims 35-37, wherein supplementing the first information with second information comprises maintaining display of the first information at a location of the display where the first information was displayed prior to detection of the rotatable input mechanism.

39. The electronic device according to any one of claims 35 to 37, wherein the one or more programs further comprise instructions for: the first portion of the data corresponds to a first privacy level, and The second portion of the data corresponds to a second privacy level.

40. The electronic device according to any one of claims 35 to 37, wherein the one or more programs further comprise instructions for: The first information is displayed in a first font size; and The second information is displayed in a second font size that is smaller than the first font size.

41. The electronic device according to any one of claims 35 to 37, wherein the one or more programs further comprise instructions for: The first information comprises a single line of text; and The second information includes two or more text lines.

42. The electronic device of claim 35, wherein the one or more programs further comprise instructions for: displaying a first editing interface for editing a first display setting corresponding to the first information and the third information, When the first editing interface is displayed: detecting a first touch input at a position corresponding to the first information, in response to detecting the first touch input at the position corresponding to the first information, highlighting the first information; detecting a second rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the second rotation of the rotatable input mechanism, a first color setting corresponding to the first information is edited.

43. The electronic device of claim 42, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, maintaining a second color setting corresponding to the third information.

44. The electronic device of claim 42, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed: In response to detecting the second rotation of the rotatable input mechanism, a second color setting corresponding to the third information is edited.

45. The electronic device of claim 42, wherein the one or more programs further comprise instructions for: When the first editing interface is displayed, detecting a horizontal swipe gesture; and In response to detecting the horizontal swipe gesture, a second editing interface is displayed for editing a second display setting corresponding to the first information and the third information.

46. The electronic device of claim 35, wherein the one or more programs further comprise instructions for: displaying a third editing interface for editing a third display setting corresponding to the first information and the third information; When the third editing interface is displayed: detecting a second touch input at a position corresponding to the first information; in response to detecting the second touch input at the position corresponding to the first information, highlighting the first information; detecting a third rotation of the rotatable input mechanism while the first information is highlighted; as well as In response to detecting the third rotation of the rotatable input mechanism, the first information is replaced with fourth information corresponding to a subject different from the first subject.

47. The electronic device of claim 46, wherein the one or more programs further comprise instructions for: When the third editing interface is displayed: In response to detecting the third rotation of the rotatable input mechanism, display of the third information is maintained.

48. The electronic device according to any one of claims 35 to 37, wherein the one or more programs further comprise instructions for: detecting a fourth rotation of the rotatable input mechanism; and In response to detecting the fourth rotation of the rotatable input mechanism, the first and second information are supplemented with fourth information associated with a third portion of the received data.

49. The electronic device of any one of claims 35-37, wherein the first information and the second information do not include icons, images, glyphs, or logos.

50. The electronic device of any one of claims 35 to 37, wherein displaying the first information associated with the first portion of the received data occurs when the device is in a first state and the second information associated with the second portion of the received data is not displayed, and the one or more programs further comprise instructions for: In response to detecting the first rotation of the rotatable input mechanism, changing from the first state to a second state.

51. The electronic device of claim 50, wherein the first state is a first privacy state and the second state is a second privacy state.

52. An electronic device comprising: Components for carrying out the method according to any one of claims 1 to 17.

53. A computer program product comprising computer instructions which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 17.

Images