Context-Specific User Interface

Abstract

Embodiments of the present disclosure relate to context-specific user interfaces, and context-specific user interfaces for use with portable multifunction devices are disclosed. Methods for context-specific user interfaces described herein provide an indication of time and optionally provide a variety of additional information. Non-transient computer-readable storage media, systems, and devices configured to perform the methods herein are also disclosed.

Description

[0001] This application is a divisional application of Chinese national application number 201510479088.4, filed on August 3, 2015, entitled "Context-Specific User Interface".

[0002] Cross-reference to related applications

[0003] This application claims priority to the following applications: 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 incorporated herein by reference in their entirety.

[0004] This application relates to the following applications: International Patent Application Serial No. PCT / US2013 / 040087, filed 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 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 May 8, 2013, entitled "Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface"; and International Patent Application Serial No. PCT / US2013 / 040070, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Facilitating User...". International patent application serial number PCT / US2013 / 040067 entitled "Interaction with Controls in a User Interface"; International patent application serial number PCT / US2013 / 040061 entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application" filed on May 8, 2013; International patent application serial number PCT / US2013 / 040058 entitled "Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a UserContact" filed on May 8, 2013;International patent application serial number PCT / US2013 / 040056, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Scrolling Nested Regions"; International patent application serial number PCT / US2013 / 040054, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects"; International patent application serial number PCT / US2013 / 069489, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Switching Between User Interfaces"; International patent application serial number PCT / US2013 / 069489, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Determining Whether to Scroll or Select". The international patent application serial number for “Content” is PCT / US2013 / 069486; the international patent application serial number for “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 is PCT / US2013 / 069484; the international patent application serial number for “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to DisplayOutput Relationships” filed on November 11, 2013 is PCT / US2013 / 069483.International patent application serial number PCT / US2013 / 069479, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture"; International patent application serial number PCT / US2013 / 069472, filed November 11, 2013, entitled "Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies"; International patent application serial number PCT / US2013 / 040108, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object"; International patent application serial number PCT / US2013 / 040108, filed May 8, 2013, entitled "Device, Method, and Graphical User Interface for Selecting User Interface". International patent application serial number PCT / US2013 / 040101 entitled “Objects”; International patent application serial number PCT / US2013 / 040098 entitled “Device, Method, and Graphical User Interface for Displaying Content Associated with a Corresponding Affordance” filed on May 8, 2013; International patent application serial number PCT / US2013 / 040093 entitled “Device, Method, and Graphical User Interface for Transitioning Between Display States in Response to a Gesture” filed on May 8, 2013; International patent application serial number PCT / US2013 / 040053 entitled “Device, Method, and Graphical User Interface for Selecting Object within a Group of Objects” filed on May 8, 2013;U.S. Patent Application Serial No. 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 No. 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 No. 61 / 778,171, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a User Contact"; and U.S. Patent Application Serial No. 61 / 778,171, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Scrolling Nested...". U.S. Patent Application Serial No. 61 / 778,179, entitled “Regions”; U.S. Patent Application Serial No. 61 / 778,156, entitled “Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects”, filed March 12, 2013; U.S. Patent Application Serial No. 61 / 778,125, entitled “Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies”, filed March 12, 2013; and U.S. Patent Application Serial No. 61 / 778,092, entitled “Device, Method, and Graphical User Interface for Selecting Object Within a Group of Objects”, filed March 12, 2013.U.S. Patent Application Serial No. 61 / 778,418, filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Switching Between User Interfaces"; U.S. Patent Application Serial No. 61 / 778,416, filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Determining Whether to Scroll or Select Content"; U.S. Patent Application Serial No. 61 / 747,278, filed December 29, 2012, entitled "Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and / or Haptic Feedback"; and U.S. Patent Application Serial No. 61 / 747,278, filed March 13, 2013, entitled "Device, Method, and Graphical User Interface for Moving and Dropping a UserInterface". U.S. Patent Application Serial No. 61 / 778,414 entitled “Device, Method, and Graphical User Interface for Selecting User Interface Objects”, filed March 13, 2013; U.S. Patent Application Serial No. 61 / 778,413 entitled “Device, Method, and Graphical User Interface for Displaying Content Associated with a Corresponding Affordance”, filed March 13, 2013; and U.S. Patent Application Serial No. 61 / 778,373 entitled “Device, Method, and Graphical User Interface for Managing Activation of a Control Based on Contact Intensity”, filed March 12, 2013.U.S. Patent Application Serial No. 61 / 778,265, filed 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 No. 61 / 778,367, filed 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 No. 61 / 778,363, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships"; and U.S. Patent Application Serial No. 61 / 778,363, filed March 12, 2013, entitled "Device, Method, and Graphical User Interface for Providing Feedback for Changing Activation States of a User Interface". U.S. Patent Application Serial No. 61 / 778,287 entitled “Object”; U.S. Patent Application Serial No. 61 / 778,284 entitled “Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface”, filed March 12, 2013; and U.S. Patent Application Serial No. 61 / 778,239 entitled “Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture”, filed 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"; and U.S. Provisional Patent Application Serial No. 61 / 681,098, filed September 2, 2014, entitled "Reduced-Size Interfaces for Managing". U.S. Provisional Patent Application Serial No. 62 / 044,894, entitled "Alerts"; U.S. Provisional Patent Application Serial No. 62 / 044,979, entitled "Stopwatch and Timer User Interfaces", filed September 2, 2014; U.S. Provisional Patent Application Serial No. 62 / 026,532, entitled "Raise Gesture Detection in a Device", filed July 18, 2014; and U.S. Patent Application Serial No. 14 / 476,700, entitled "Crown Input for a Wearable Electronic Device", filed September 3, 2014. The contents of these applications are incorporated herein by reference in their entirety. Technical Field

[0005] This disclosure relates generally to computer user interfaces, and more particularly to context-specific user interfaces for indicating time. Background Technology

[0006] In addition to various operations involving running software applications, users rely on portable multi-functional devices for timekeeping. The goal is to allow users to access information through a single user interface, while making the interface simple and intuitive for 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. Therefore, it is also desirable to allow users to customize the user interface and the types of information provided through it. Summary of the Invention

[0007] Portable multi-functional devices can provide users with many different types of information and interfaces, and users can expect to customize these user interfaces and the types of information they provide in different contexts. Therefore, context-specific user interfaces for timekeeping are increasingly desirable.

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

[0009] Therefore, the present invention particularly provides the benefits of portable electronic devices having faster and more efficient methods and interfaces for managing context-specific user interfaces. Such methods and interfaces can optionally complement or replace other methods for managing context-specific user interfaces. These methods and interfaces reduce the cognitive burden on the user and result in a more efficient human-machine interface. They can also reduce unnecessary, irrelevant, repetitive, and / or redundant input, and can reduce the number of inputs required, reduce processing power, and reduce the amount of time required to display the user interface to access and achieve desired functions. For battery-powered computing devices, such methods and interfaces save power and reduce the time between battery charging cycles.

[0010] The aforementioned deficiencies and other problems are mitigated or eliminated by the disclosed devices, methods, and computer-readable media. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop computer, tablet computer, or 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 "touchscreen" or "touchscreen display"). In some embodiments, the device has hardware input mechanisms, such as pressable buttons and / or rotatable input mechanisms. In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in the memory for performing multiple functions. In some embodiments, a user interacts with the GUI by finger contact and gestures on a touch-sensitive surface and / or by rotating a rotatable input mechanism and / or by pressing a pressable hardware button. In some embodiments, the functions may optionally include image editing, drawing, presentation, word processing, website creation, disk creation, spreadsheet creation, games, telephone, video conferencing, email, instant messaging, training support, digital video recording, digital photography, web browsing, digital music playback, and / or digital video playback. Executable instructions for performing these functions may optionally be included in a non-transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0011] In some embodiments, a method of 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 the current time; and updating the user interface screen by animing the clock face transitioning from indicating the first time to indicating the current time, wherein the animing represents the time transition from the first time to the current time.

[0012] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: displaying a clock face on the touch-sensitive display indicating the current time, 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 one or more hour time scale indications with the indication of a first time scale of the stopwatch hand; and animate the stopwatch hand to reflect the passage of time.

[0013] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having 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 region of the Earth illuminated by the sun at the current time; receiving user input; and in response to receiving user input: rotating the simulation of the Earth to display a second region 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 having 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 indicating daytime; a second portion of the user interface screen indicating nighttime; a user interface object representing a sine wave having a period representing a day, wherein the sine wave indicates the path of the sun on that day, and wherein the sine wave is displayed in one or more of the first and second portions; a first availability representing the sun, wherein the first availability is displayed at a first position on the displayed sine wave, the first position indicating the current time of the day and whether the current time of the day is during daytime or nighttime; and a second availability indicating the current time of the day.

[0015] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: displaying a user interface screen on the display, the user interface screen including: an image-based background comprising a plurality of pixels, wherein a subset of the pixels is visually modified relative to the image such that the subset of pixels represents one or more of the following: 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 of providing a context-specific user interface includes: at an electronic device having a display: accessing a folder comprising two or more images; selecting a first image from the folder; and displaying a user interface screen on the display, the user interface screen comprising: a background based on the first image, the background comprising a plurality of pixels, wherein a subset of the pixels is visually modified relative to the image such that the subset of pixels represents one or more of the following: 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 of 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 moment; and in response to detecting the user input: displaying a user interface screen, the user interface screen including: indicating a first user interface object at the first moment; and a second user interface object; and animate rendering of the second user interface object, the animate rendering including the sequential display of a sequence of first animate renderings, a sequence of second animate renderings following the sequence of first animate renderings, and a sequence of third animate renderings following the sequence of second animate renderings, wherein the sequence of first animate renderings, the sequence of second animate renderings, and the sequence of third animate renderings are different; after animate rendering of the second user interface object, detecting a second user input, wherein the second User input is detected at a second time, which is after the first time, and in response to the detection of the second user input: accessing data representing a previously displayed sequence of second animation presentations; selecting a fourth sequence of animation presentations, wherein the fourth sequence of animation presentations is different from the first and second sequences of animation presentations; displaying a second user interface screen, the second user interface screen including: a first user interface object, wherein the first user interface object is updated to indicate the second time; and a third user interface object associated with the second user interface object; and an animation presentation of the third user interface object, the animation presentation including the sequential display of the first sequence of animation presentations, the fourth sequence of animation presentations following the first sequence of animation presentations, and the third sequence of animation presentations following the fourth sequence of animation presentations.

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

[0019] In some embodiments, a method of indicating time using a person-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a person user interface object on the display, the person user interface object including representations of a first limb and a second limb, wherein the person 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 person user interface object to indicate a second time, wherein the person 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 person-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a person user interface object on the display, the person 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 a rotation axis of the limb, and the position of the second endpoint of the limb indicates a first time value; and updating the person user interface object to indicate a second time value, wherein updating the person 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 person-based user interface includes: at an electronic device having a display and a touch-sensitive surface: displaying a person-based user interface object on the display, the person-based user interface object including a representation of a limb, the limb including a first segment 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 a joint of the limb, the second endpoint of the limb having a second position, wherein the joint of the limb is a rotation axis of 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 person-based 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 rotation axis of the second segment of the limb to indicate a second time.

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

[0023] In some embodiments, a method for indicating time using a person-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 person user interface object on the side of the display; animating the person user interface object toward the center of the display; and displaying the person user interface object at the center of the display at the location indicating the current time.

[0024] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: a clock face and an available element, wherein the available element represents an application, wherein the available element 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 available element is displayed as a complex element on the clock face; detecting a touch on the displayed available element; and in response to detecting a touch: launching the application represented by the available element.

[0025] In some embodiments, a method of 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 a 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 the 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 elements of the clock face for editing.

[0026] In some embodiments, a method of 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 a 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 the 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 a 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 a device on the clock face indicating a first time of day; detecting a touch on the touch-sensitive display; and in response to detecting a touch: entering a user interaction mode of the electronic device, while the electronic device is in the user interaction mode, detecting movement of the rotatable input mechanism, and in response to detecting movement: updating the device to indicate a second time of day; detecting a second touch on the touch-sensitive display at the device indicating the second time, and in response to detecting the second touch: setting a user reminder for the second time of day.

[0028] In some embodiments, a method of providing a context-specific user interface includes: at an electronic device having a touch-sensitive display: displaying a user interface screen on the display, the user interface screen including a plurality of available elements, the plurality of available elements including a first available element, wherein the first available element indicates a clock face, the clock face including: a time indicator and an outline; detecting a touch on the displayed first available element; and in response to detecting a touch: replacing the display of the user interface screen with a second user interface screen, wherein the replacement includes retaining one or more of the time indicator and the outline, wherein the retained time indicator or outline is displayed on the second user interface screen at a size larger than that of the first user interface screen.

[0029] In some embodiments, an apparatus includes means for receiving data representing user input; means 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 the current time; and means for updating the user interface screen by animate transition of the clock face from indicating the first time to indicating the current time, wherein the animate transition represents the time change from the first time to the current time.

[0030] In some embodiments, an apparatus includes means for displaying a clock face indicating the current time on a 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; means for receiving data representing user input; means for replacing one or more hour time scale indications with the indication of a first time scale of the stopwatch hand in response to receiving the data; and means for animate the stopwatch hand to reflect the passage of time.

[0031] In some embodiments, an apparatus includes means for displaying a user interface screen on a touch-sensitive display, the user interface screen including: a first available element representing a simulation of a first region 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 region of the Earth illuminated by the sun at the current time in response to receiving user input.

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

[0033] In some embodiments, an apparatus includes means for displaying a user interface screen on a display, the user interface screen including: an image-based background comprising a plurality of pixels, wherein a subset of the pixels is visually modified relative to the image such that the subset of pixels represents one or more of the following: 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 means for accessing a folder comprising two or more images; means for selecting a first image from the folder; and means for displaying a user interface screen on a display, the user interface screen including: a background based on the first image, the background comprising a plurality of pixels, wherein a subset of the pixels is visually modified relative to the image such that the subset of pixels represents one or more of the following: 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 means for detecting user input, wherein the user input is detected at a first time; means 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; means for animate rendering of the second user interface object, the animate rendering including the sequential display of a first animate rendering sequence, a second animate rendering sequence following the first animate rendering sequence, and a third animate rendering sequence following the second animate rendering sequence, wherein the first animate rendering sequence, the second animate rendering sequence, and the third animate rendering sequence are different; and means for detecting second user input, wherein the second user input is detected at a second time, wherein the second time is the first time. The following means are provided: in response to detecting second user input for accessing data representing a previously displayed sequence of second animation presentations; means for selecting a fourth sequence of animation presentations, wherein the fourth sequence of animation presentations differs from the first and second sequences of animation presentations; means for displaying a second user interface screen, the second user interface screen including: a first user interface object, wherein the first user interface object is updated to indicate a second time; and a third user interface object associated with the second user interface object; and means for animate presentation of the third user interface object, the animation presentation including the sequential display of the first sequence of animation presentations, the fourth sequence of animation presentations following the first sequence of animation presentations, and the third sequence of animation presentations following the fourth sequence of animation presentations.

[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 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 following the first hour indication in a clockwise direction.

[0037] In some embodiments, an apparatus includes means for displaying a user interface screen on a display, the user interface screen including: a clock face and an available element, wherein the available element represents an application, wherein the available element 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 available element is displayed as a complex element on the clock face; means for detecting contact on the displayed available element; and means for activating the application represented by the available element in response to detecting contact.

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

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

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

[0041] In some embodiments, an apparatus includes means for displaying a user interface screen on a display, the user interface screen including a plurality of available elements, the plurality of available elements including a first available element, wherein the first available element indicates a clock face, the clock face including: a time indicator and an outline; means for detecting contact on the displayed first available element; and means for replacing the display of the user interface screen with a second user interface screen in response to detecting contact, wherein replacement includes retaining one or more of the time indicator and the outline, wherein the retained time indicator or outline is displayed on the second user interface screen at a size larger than that of 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-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 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.

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

[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 one or more processors, cause 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, an apparatus includes: means for receiving data related to a first subject; means for displaying first information related to a first portion of the received data; means for detecting a first rotation of a rotatable input mechanism; and means 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 the display unit to 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.

[0048] In some embodiments, a method at an electronic device having a display includes: acquiring first event data from a first application; acquiring 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-transient computer-readable storage medium storing one or more programs, the programs including instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to: acquire first event data from a first application; acquire 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 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.

[0050] In some embodiments, a transient computer-readable storage medium storing one or more programs, the programs including instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to: acquire first event data from a first application; acquire 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 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.

[0051] In some embodiments, an electronic device includes: a touch-sensitive display; one or more processors; a memory; and one or more programs, wherein the programs are stored in the memory and configured to be executed by the one or more processors, the programs including instructions that, when executed by the one or more processors, cause the device to: acquire first event data from a first application; acquire 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 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.

[0052] In some embodiments, an electronic device includes: means for acquiring first event data from a first application; means for acquiring second event data from a second application different from the first application; means 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 means 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, a rotatable and pressable input mechanism unit, and a button unit, the processing unit being configured to: acquire first event data from a first application; acquire 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 the 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.

[0054] Therefore, devices are provided with faster and more efficient methods and interfaces for managing (e.g., editing) context-specific user interfaces, thereby increasing effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace other methods for managing context-specific user interfaces. Attached Figure Description

[0055] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some embodiments.

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

[0057] Figure 2 The illustration shows a portable multi-functional device with a touch-sensitive display according to some embodiments.

[0058] Figure 3 This is a block diagram illustrating an exemplary multifunctional device having a display and a touch-sensitive surface according to some embodiments.

[0059] Figure 4A and Figure 4B An exemplary user interface for an application menu on a portable multi-functional device, according to some embodiments, is illustrated.

[0060] Figure 5A The illustration shows a portable multi-functional device with a touch-sensitive display and a rotatable, pressable input mechanism, according to some embodiments.

[0061] Figure 5B The illustration depicts a portable multi-functional device with a touch-sensitive display and a rotatable, pressable input mechanism, according to some embodiments.

[0062] Figure 6A and Figure 6B The illustration shows a user interface specific to an exemplary scenario.

[0063] Figure 7A and Figure 7B The illustration shows a user interface specific to an exemplary scenario.

[0064] Figure 8 The illustration shows a user interface specific to an exemplary scenario.

[0065] Figure 9 The illustration shows a user interface specific to an exemplary scenario.

[0066] Figure 10 The illustration shows a user interface specific to an exemplary scenario.

[0067] Figures 11A-11C The illustration shows a user interface specific to an exemplary scenario.

[0068] Figure 12 The illustration shows a user interface specific to an exemplary scenario.

[0069] Figure 13A and Figure 13B The illustration shows a user interface specific to an exemplary scenario.

[0070] Figure 14A The illustration shows a user interface specific to an exemplary scenario.

[0071] Figures 14B-14U The illustration shows a user interface specific to an exemplary scenario.

[0072] Figure 15 The illustration shows a user interface specific to an exemplary scenario.

[0073] Figures 16A-16G The illustration shows a user interface specific to an exemplary scenario.

[0074] Figure 17A and Figure 17B The illustration shows a user interface specific to an exemplary scenario.

[0075] Figures 18A-18C The illustration shows a user interface specific to an exemplary scenario.

[0076] Figure 19 The illustration shows a user interface specific to an exemplary scenario.

[0077] Figure 20 This is a flowchart illustrating a process used for a context-specific user interface.

[0078] Figure 21 This is a flowchart illustrating a process used for a context-specific user interface.

[0079] Figure 22 This is a flowchart illustrating a process used for a context-specific user interface.

[0080] Figure 23 This is a flowchart illustrating a process used for a context-specific user interface.

[0081] Figure 24 This is a flowchart illustrating a process used for a context-specific user interface.

[0082] Figure 25 This is a flowchart illustrating a process used for a context-specific user interface.

[0083] Figure 26 This is a flowchart illustrating a process used for a context-specific user interface.

[0084] Figure 27A This is a flowchart illustrating a process used for a context-specific user interface.

[0085] Figure 27B This is a flowchart illustrating a process used for a context-specific user interface.

[0086] Figure 27C This is a flowchart illustrating a process used for a context-specific user interface.

[0087] Figure 27D This is a flowchart illustrating a process used for a context-specific user interface.

[0088] Figure 27E This is a flowchart illustrating a process used for a context-specific user interface.

[0089] Figure 27F This is a flowchart illustrating a process used for a context-specific user interface.

[0090] Figure 28 This is a flowchart illustrating a process used for a context-specific user interface.

[0091] Figure 29 This is a flowchart illustrating a process used for a context-specific user interface.

[0092] Figure 30 This is a flowchart illustrating a process used for a context-specific user interface.

[0093] Figure 31 This is a flowchart illustrating a process used for a context-specific user interface.

[0094] Figure 32 This is a flowchart illustrating a process used for a context-specific user interface.

[0095] Figure 33 This is a flowchart illustrating a process used for a context-specific user interface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0115] Figures 53A-53F An exemplary user interface according to some embodiments is illustrated.

[0116] Figures 54A-54E This is a flowchart illustrating a method for activating an operation mode according to some embodiments.

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

[0118] Figures 56A-56I The illustration shows a user interface specific to an exemplary scenario.

[0119] Figure 57A This is a flowchart illustrating a process used for a context-specific user interface.

[0120] Figure 57B This is a flowchart illustrating a process used for a context-specific user interface.

[0121] Figure 57C This is a flowchart illustrating a process used for a context-specific user interface.

[0122] Figure 57D This is a flowchart illustrating a process used for a context-specific user interface.

[0123] Figure 57E This is a flowchart illustrating a process used for a context-specific user interface.

[0124] Figure 57F This is a flowchart illustrating a process used for a context-specific user interface.

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

[0126] Figures 59A-59F An exemplary user interface according to some embodiments is illustrated.

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

[0128] Figure 61 This is a functional block diagram of an electronic device according to some embodiments. Detailed Implementation

[0129] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but rather is provided as a description of exemplary embodiments.

[0130] As discussed above, users can customize an environment-specific user interface to maintain time and receive certain types of information. The challenge lies in providing users with numerous options for customizing such an interface while maintaining a highly usable interface. Furthermore, it is challenging to present these options in a user-friendly and intuitive way to customize multiple variables such as color, display density, and complexity. An environment-specific user interface, and the methods for allowing users to customize such an interface, are highly desirable for portable, multi-functional devices.

[0131] under, Figures 1A to 1B , Figure 2 , Figure 3 and Figures 4A to 4B as well as Figures 5A to 5B Description of exemplary devices for implementing technologies for providing environment-specific user interfaces. Figures 6 to 10 are provided. Figure 19 The illustration depicts an exemplary environment—a specific user interface. The user interface in the diagram is also used to illustrate the processes described below, including... Figures 20 to 33 The process in.

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

[0133] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. The singular forms “a,” “an,” and “described” as used in the description of the various embodiments and in the appended claims are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and covers any item in one or more entries of the associated listed items and all possible combinations thereof. Furthermore, it should be understood that the terms “comprising,” “having,” “including,” and / or “containing,” as used in this specification, specify the presence of a feature, integral, step, operation, element, and / or part, but do not preclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or combinations thereof.

[0134] The term "if" can be interpreted, depending on the context, as meaning "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determination" or "if [a certain condition or event] is detected" can be interpreted, depending on the context, as meaning "once determination, then," "in response to determination," "once [a certain condition or event] is detected," or "in response to the detection of [a certain condition or event]."

[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 functions such as PDA and / or music player functionality. Exemplary embodiments of portable multi-functional devices include, but are not limited to, those from Apple Inc., Cupertino, California. iPod and Devices. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), may also be used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0136] In the following discussion, an electronic device comprising 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 a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk writing applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video recorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0138] Various applications running on the device may 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 the corresponding information displayed on the device, may be optionally adjusted and / or changed from one application to the next and / or within each application. In this way, the device's common physical architecture (such as the touch-sensitive surface) may optionally support various applications through a user interface that is intuitive and transparent to the user.

[0139] We will now focus on embodiments that turn to portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” and is sometimes considered or referred to as a touch-sensitive display system. Device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the contact strength on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 may optionally include one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 335 of device 300). These components may optionally communicate via one or more communication buses or signal lines 103.

[0140] As used in the specification and claims, the term "intensity" for contact on a tactile surface refers to the force or pressure (force per unit area) of contact (e.g., finger contact) on the tactile surface, or to a substitute (proxy) for the force or pressure used for contact on the tactile surface. Contact intensity has a numerical range including at least four different values ​​and more typically including hundreds of different values ​​(e.g., at least 256). Optionally, contact intensity is determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors, located below or adjacent to the tactile surface, may optionally be used to measure force at various points on the tactile surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated force of contact. Similarly, the pressure-sensitive tip of a stylus may optionally be used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or change of the contact area detected on the touch-sensitive surface, the capacitance and / or change of the touch-sensitive surface adjacent to the contact, and the resistance and / or change of the touch-sensitive surface adjacent to the contact can optionally be used as alternatives to the force or pressure of contact on the touch-sensitive surface. In some implementations, the alternative 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 alternative measurement). In some implementations, the alternative measurement for contact force or contact pressure is converted into an estimated force or estimated pressure, and this 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 a user input attribute allows user access to additional device functionality that would otherwise be inaccessible to the user on a device with a reduced size (e.g., via a touch-sensitive display) having a limited effective area for displaying affordances and / or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0141] As used in the specification and claims, the term "haptic output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of gravity of the device, which will be detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive user surface (e.g., a finger, palm, or other part of the user's hand), the haptic output resulting from the physical displacement will be interpreted by the user as a tactile sensation corresponding to a change in the perceived physical characteristics of the device or device component. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" of a physical actuator button. In some cases, the user will feel a tactile sensation such as a "press-click" or "release-click" even when there is no movement of a physical actuator button associated with a touch-sensitive surface 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 may optionally be 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 personalized sensory perception, there are sensory perceptions of many points of touch common to most users. Therefore, when tactile output is described as corresponding to a specific sensory perception of a user (e.g., "lift-to-click", "press-to-click", "roughness"), the resulting tactile output will correspond to the physical displacement of the device or its components, which will produce the sensory perception described for a typical (or average) user, unless explicitly indicated otherwise.

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

[0143] Memory 102 may include one or more computer-readable storage media. The 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 through other components of device 100.

[0144] Peripheral interface 118 can be used to peripherally couple the device's inputs and outputs to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 may be implemented on a single chip (such as chip 104). In some other embodiments, they may 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 electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 may optionally include known circuitry for performing these functions, including but not limited to: antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, customer identity module (SIM) cards, memory, etc. RF circuitry 108 may optionally communicate wirelessly with 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), and other devices. RF circuitry 108 may optionally include known circuitry for detecting near-field communication (NFC) fields, such as via short-range communication radio. 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), Evolved 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), and Wireless High Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE...). 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Messaging Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Field Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Field Balanced Extensions (SIMPLE), Instant Messaging and Field Services (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not been developed as of the date of this document submission.

[0146] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to peripheral interface 118 for processing. Audio data can be acquired from and / or transmitted to memory 102 and / or RF circuitry 108 via peripheral interface 118. In some embodiments, audio circuitry 110 also includes a headphone jack (e.g., ...). Figure 2 (212 in the text). The headphone jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device (such as a receiver with only output or a headset that can output (e.g., a receiver with one or both ears) and input (e.g., a microphone)).

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

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

[0149] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or sends electrical signals to the touchscreen 112. The touchscreen 112 displays visual output to the user. This visual output may include graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output may correspond to a user interface object.

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

[0151] While other display technologies may be used in other embodiments, the touchscreen 112 may use LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology. The touchscreen 112 and display controller 156 may use any of a variety of touch sensing technologies now known or developed hereafter to detect contact and any movement or interruption of contact. These touch sensing technologies include, but are 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 touchscreen 112. In one exemplary embodiment, projected mutual capacitance sensing technology, such as that available at Apple Inc. in Cupertino, California, is used. and iPod The technology found there.

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

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

[0154] The touchscreen 112 may have a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users can interact with the touchscreen 112 using any suitable object or accessory, such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise compared to stylus-based input due to the larger contact area of ​​the finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-expected actions.

[0155] In some embodiments, in addition to the touchscreen, 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 differs from the touchscreen and does not display visual output. The touchpad may be a touch-sensitive surface separate from the touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0156] The device 100 also includes a power system 162 for powering various components. The power system 162 may include a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a charging system, a power failure detection circuit, 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 the portable device.

[0157] The device 100 may also include one or more optical sensors 164. Figure 1A An optical sensor 164 coupled to a controller 158 of the optical sensor in the I / O subsystem 106 is shown. The optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with an 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 a touchscreen display 112 on the front of the device, allowing the touchscreen display to 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, allowing for the acquisition of user images for video conferencing while the user views other video conferencing 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 lenses and sensors within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still and / or video image acquisition.

[0158] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength 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 strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or alternatives for pressure information) from the environment. In some embodiments, at least one contact strength sensor is juxtaposed with or near a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the back of device 100, opposite a touchscreen display 112 located on the front of device 100.

[0159] The device 100 may also include one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to a peripheral interface 118 is shown. Alternatively, the proximity sensor 166 may be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may function as described in U.S. Patent Application No. 11 / 241,839 entitled "Proximity Detector In Handheld Device", U.S. Patent Application No. 11 / 240,788 entitled "Proximity Detector In Handheld Device", U.S. Patent Application No. 11 / 620,702 entitled "Using Ambient Light Sensor To Augment ProximitySensor Output", U.S. Patent Application No. 11 / 586,862 entitled "Automated Response To And Sensing Of User Activity In Portable Devices", and U.S. Patent Application No. 11 / 638,251 entitled "Methods And Systems For Automatic Configuration Of Peripherals", all of which are incorporated herein by reference in their entirety. In some embodiments, when the multifunction device is near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touchscreen 112 is disabled.

[0160] The device 100 may optionally also include one or more tactile output generators 167. Figure 1A A haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices (such as speakers or other audio components) and / or electromechanical devices that convert electrical energy into linear motion (such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generation components (e.g., components that convert electrical signals into haptic outputs on the device)). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed with or near a haptic surface (e.g., a haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outside the surface of device 100) or laterally (reciprocating in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the back of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0161] The device 100 may also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may 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 entirety. In some embodiments, information is displayed on a touchscreen display in either a portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer(s)168, the device 100 may optionally include a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information relating 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. Furthermore, as... Figure 1A and Figure 3 As shown, in some embodiments, memory 102 ( Figure 1A ) or memory 370 ( Figure 3 Storage device / global internal state 157. 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 orientation.

[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 on one or more external ports 124 and also includes various software components for processing data received by the RF circuitry device 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled to other devices via a network (e.g., the Internet, Wireless LAN, etc.). In some embodiments, the external port is used in conjunction with... (A trademark of Apple Inc.) The same, similar and / or compatible multi-pin (e.g., 30-pin) connectors on Apple Inc. devices.

[0165] The contact / motion module 130 optionally detects contact with the touchscreen 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 a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to the force or pressure used for the contact), determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or a contact interruption). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the touch point (represented by a series of contact data) optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the touch point. These operations can optionally be applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contact). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

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

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

[0168] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other displays, including components for altering the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual attributes). 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 applications, etc., 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] The haptic feedback module 133 includes various software components that, in response to user interaction with the device 100, generate instructions for use by the haptic output generator(s) 167 to produce haptic output at one or more locations on the device.

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

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

[0173] Application 136 may include the following modules (or instruction sets), or subsets or supersets thereof:

[0174] • Contacts module 137 (sometimes called 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] • 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 may include one or more of the following: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 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 a video player module and a 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 can be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, applications that support JAVA features, encryption, digital access control, speech recognition, and speech duplication.

[0194] In conjunction with the touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 can be used to manage an address book or contact list (e.g., in the application internal state 192 of the contact 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 phone numbers, one or more email addresses, one or more physical addresses, or other information with a name; associating an image with a name; categorizing and sorting names; providing a phone number or email address to initiate and / or facilitate communication via telephone 138, video conferencing module 139, email 140, or instant messaging 141, etc.

[0195] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 can be used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify input telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is complete. As described above, wireless communication can use any of a variety of communication standards, protocols, and technologies.

[0196] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting, and terminating video conferences between the user and one or more other participants, based on user instructions.

[0197] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / 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 commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0198] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for inputting character sequences corresponding to instant messages, modifying previously input characters, transmitting corresponding instant messages (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, transmitted and / or received instant messages may include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, “instant message” refers to telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages using XMPP, SIMPLE, or IMPS).

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

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

[0201] Incorporating touchscreen 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), manipulating, annotating, deleting, presenting (e.g., in a digital slideshow presentation or photo album), and storing still and / or video images.

[0202] Combining the RF circuitry 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and 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, as well as attachments and other files linked to the web pages) according to user instructions.

[0203] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and calendar-related data (e.g., calendar entries, to-do lists, etc.) according to user instructions.

[0204] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / 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 the user (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widget).

[0205] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 can be used by the user to create widgets (e.g., converting user-specified portions of a webpage into widgets).

[0206] In conjunction with the touchscreen 112, display controller 156, touch / 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) according to user instructions.

[0207] Incorporating touchscreen 112, display controller 156, touch / 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 allowing users to download and play back recorded music and other sound files (such as MP3 or AAC files) stored in one or more file formats, and includes executable instructions for displaying, presenting, or additionally playing back video (e.g., on touchscreen 112 or on a display externally connected via external port 124). In some embodiments, device 100 may optionally include the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0208] Combining the touchscreen 112, display controller 156, touch / 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 conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 can be used to receive, display, modify, and store maps and map-related data (e.g., driving directions; data about shops and other points of interest in or near a specific location; and other location-based data) according to user instructions.

[0210] In conjunction with touchscreen 112, display controller 156, touch / 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 allowing users to access, browse, receive (e.g., via streaming and / or downloading), (e.g., on a touchscreen or on a display externally connected via external port 124) play back specific online videos, send emails with links to specific online videos, and manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141, instead of email client module 140, is used to send links to specific online videos. Additional descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed 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 December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the entire contents of which are incorporated herein by reference.

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

[0212] In some embodiments, device 100 is a device specifically designed to perform operations of a predetermined set of functions on the device via a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (such as push-buttons, dial pads, etc.) on device 100 can be reduced.

[0213] The predetermined set of functions, specifically performed via a touchscreen and / or touchpad, may optionally include navigation between user interfaces. In some embodiments, when a user touches the touchpad, the device 100 is navigated from any user interface on the device 100 display to the home screen, main picture, or root menu. In such embodiments, a 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 instead of a touchpad.

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

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

[0216] In some embodiments, the application internal state 192 includes additional information such as one or more of the following: recovery information to be used when the application 136-1 resumes execution, user interface state information indicating the information being displayed or ready to be displayed by the application 136-1, a state queue that allows the user to return to the 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 peripheral interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral interface 118 transmits information it receives from I / O subsystem 106 or sensors, such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

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

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

[0220] The hit view determination module 172 provides a software program for determining where a sub-event has occurred in one or more views when the touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that the 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 corresponding application) where a touch is detected can correspond to a program level in the application's program or view hierarchy. For example, the lowest-level view where a touch is detected can be called the hit view, and the set of events recognized as correct input can be determined at least in part based on the hit view of the initial touch that initiated the touch-based gesture.

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

[0223] The active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a specific sub-event sequence. In some embodiments, the active event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the 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 the specific sub-event sequence. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, higher-level views in the hierarchy will still remain as actively participating views.

[0224] Event dispatcher module 174 dispatches event information to event identifiers (e.g., event identifier 180). In embodiments that include an active event identifier determination module 173, event dispatcher module 174 delivers event information to an event identifier determined by active event identifier determination module 173. In some embodiments, event dispatcher module 174 stores event information in an event queue for retrieval by a 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 (such as contact / motion module 130) stored in memory 102.

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

[0227] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes 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. This event information includes information about sub-events (e.g., 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 touch movement, 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., rotation from portrait to landscape and vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device pose).

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

[0230] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine the user interface object associated with the sub-event. For example, in an application view where three user interface objects are displayed on a touch-sensitive display 112, when a touch is detected on the 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 the delivery of event information until it has been determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

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

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

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

[0235] In some embodiments, event delivery instruction 188 includes a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers 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 procedure.

[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 location 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 a data updater 176, an object updater 177, and a GUI updater 178. In some embodiments, the data updater 176, object updater 177, and GUI updater 178 are included in a single module of a corresponding application 136-1 or application view 191. In other embodiments, the 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 for user touch on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 with input devices, where not all user input is initiated on the touchscreen. Examples include mouse movement and mouse button presses that optionally correspond to pressing or holding one or more keyboard keys; touch movements on the touchpad (such as tapping, dragging, scrolling, etc.); stylus input; device movement; voice commands; detected eye movements; biometric input; and / or any combination of the foregoing, which may optionally be used as input corresponding to a sub-event that defines the event to be identified.

[0239] Figure 2 A portable multi-functional device 100 with a touchscreen 112 is illustrated according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over them (e.g., with one or more fingers 202 (not shown to scale) or one or more styluses (not shown to scale)). In some embodiments, selection of one or more graphics occurs when the user interrupts contact with one or more graphics. In some embodiments, gestures may optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rotation of a finger that has been in contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or situations, unintentional contact with a graphic will not select the graphic. For example, a swipe gesture over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0241] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for turning the device on / off and locking the device, and one or more volume control buttons 208, a SIM card slot 210, a headphone jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to turn the device on / off by pressing the button and holding it in the pressed state for a predetermined time interval; to lock the device by pressing the button and releasing it before the 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 via microphone 113 for activating or deactivating certain functions. Device 100 may optionally also include one or more contact strength sensors 165 for detecting contact strength on the touchscreen 112 and / or one or more haptic output generators 167 for generating haptic outputs to a user of device 100.

[0242] Figure 3 This is a block diagram of an exemplary multi-functional device having a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 may optionally include circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input / output (I / O) interface 330, which includes a display 340, typically a touchscreen display. The input / output interface 330 may also optionally include a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the one mentioned above). Figure 1A The described (multiple) tactile output generators 167 and sensors 359 (e.g., similar to those in the above reference appendix) Figure 1AThe described contact strength sensors 165 are optical, acceleration, proximity, touch-sensitive, and / or contact strength sensors. 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 disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory 370 may optionally include one or more storage devices located remotely from CPU(one or more) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to those stored in memory 102 of portable multifunction device 100 (FIG. 1), or subsets thereof. Furthermore, memory 370 may optionally store additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, the memory 370 of device 300 may optionally store a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk writing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 ( Figure 1A The memory 102 may optionally not store these modules.

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

[0244] Our attention will now turn to embodiments of user interfaces that can be implemented, for example, on a portable multifunction device 100.

[0245] Figure 4A An exemplary user interface for an application menu on a portable multifunction device 100, according to some embodiments, is illustrated. 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 indicator 402 is used for (various) wireless communications, such as cellular signals and Wi-Fi signals;

[0247] • Time 404;

[0248] Bluetooth indicator 405;

[0249] • Battery status indicator 406;

[0250] • Tray tray 408, featuring icons for frequently used applications, such as:

[0251] o An icon 416 for the telephone module 138, labeled “telephone”, optionally includes an indicator 414 for 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 for the number of unread emails;

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

[0254] o The icon 422 used for the video and music player module 152, also known as the iPod (Apple Inc. trademark) module 152, is labeled "iPod"; and

[0255] • Icons used in other applications, such as:

[0256] o Icon 424 used for IM module 141 is labeled "Message";

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

[0258] o Icon 42 for the image management module 144 is labeled "Photo";

[0259] o The icon 430 used for camera module 143 is labeled "camera";

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

[0261] o Icon 434 for the stock widget 149-2, labeled "Stock";

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

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

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

[0265] o Icon 442 used for training support module 142, labeled "training support";

[0266] o The icon 444 used for the memo module 153 is labeled "Memo";

[0267] o is the icon 446 used to set applications or modules, labeled "Settings", which provides access to the settings of device 100 and its various applications 136.

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

[0269] Figure 4B The illustration shows a touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)). Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3 An exemplary user interface on device 300. Device 300 may also optionally include one or more contact intensity sensors (e.g., one or more sensors 357) for detecting contact intensity on the touch-sensitive surface 451 and / or one or more tactile output generators 359 for generating tactile outputs to a user of device 300.

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

[0271] Furthermore, while the following examples are primarily given with reference to finger input (e.g., finger touch, finger tap, finger swipe), it should be understood that in some embodiments, one or more finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may be replaced, for instance, not a touch (followed by movement with the touch), but optionally by a mouse click (followed by movement of the cursor along the swipe path). As another example, a tap gesture may be replaced, for instance, not a touch detection (followed by cessation of touch detection), but optionally by 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 be used simultaneously, or mouse and finger touch may be used simultaneously.

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

[0273] Techniques for detecting and processing touch intensity can be found, for example, in the following related applications: International Patent Application Serial No. PCT / US2013 / 040061, filed May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application”, published under WIPO Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships”, published under WIPO Publication No. WO / 2014 / 105276, 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 may 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 may allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, watch chains, trousers, belts, shoes, handbags, backpacks, etc. These attachment mechanisms may allow device 500 to be worn by a user.

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

[0276] In some examples, the input device 508 may be a microphone. The personal electronic device 500 may include a variety of 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 may be operatively connected to the 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, which, when executed by one or more computer processors 516, may cause the computer processors to perform, for example, the techniques described above, including processes 2000-3300. Figures 20 to 33 Computer-executable instructions may also be stored and / or transmitted in 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 processor-containing system, or other system that can retrieve and execute instructions from and from the instruction execution system, apparatus, or device. For the purposes of this document, a “non-volatile computer-readable storage medium” can be any medium that tangibly contains or stores computer-executable instructions that can be used by or in conjunction with an instruction execution system, apparatus, or device. Non-volatile computer-readable storage media can include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage (such as flash memory, solid-state drives, etc.). Personal electronic devices 500 are not limited to Figure 5B The components and configurations may include other or additional components in various configuration forms.

[0278] As used herein, the term "available component" refers to components that can be supplied in device 100, device 300, and / or device 500 (Figure 1, ...). Figure 3 The user interaction graphical user interface object displayed on the screen (as shown in Figure 5). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) can each constitute an available component.

[0279] As used herein, the term "focus selector" refers to the input element of the user interface that is currently being interacted with by the user. In some implementations, this includes a cursor or other position marker that serves as the "focus selector" so that when the user is on a touch-sensitive surface (e.g., ...), the input element is selected. Figure 3 The touchpad 355 or Figure 4B When input (e.g., a press input) is detected on the touch-sensitive surface 451 and the cursor is over a specific user interface element (e.g., a button, window, slider, or other user interface element), that specific user interface element is adjusted according to the detected input. In some implementations, a touchscreen display (e.g., […]) is included, enabling direct interaction with user interface elements on the touchscreen display. Figure 1A The touch-sensitive display system 112 or Figure 4A The touchscreen 112 in the image serves as a "focus selector" to adjust a particular user interface element (e.g., a touch-sensitive input) based on the detected input when input is detected on the touchscreen display at the location of that element (e.g., a button, window, slider, or other user interface element). In some implementations, focus is moved from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these implementations, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, it is typically a user interface element (or a touch on the touchscreen display) that is user-controlled (e.g., by indicating to the device that the user intends to interact with a user interface element) to communicate the user's intended interaction with the user interface. For example, when a press input is detected on a touch-sensitive surface (such as a touchpad or touchscreen), the position of the focus selector (such as a cursor, touch, or selection box) on the corresponding button will indicate that the user intends to activate the corresponding button (relative to other user interface elements displayed on the device's display).

[0280] As used in the specification and claims, the term "characteristic intensity" of contact refers to a characteristic of contact based on one or more intensities of contact. In some embodiments, characteristic intensity is based on a plurality of intensity samples. Characteristic intensity may optionally be based on a predetermined number of intensity samples or a set of intensity samples collected over 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 contact is detected, before contact is detected to lift, before or after contact is detected to begin moving, before contact is detected to end, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of contact may optionally be based on one or more of the following: the maximum value of contact intensity, the median value of contact intensity, the average value of contact intensity, the highest 10% value of contact intensity, the half-maximum value of contact intensity, the 90% maximum value of contact intensity, etc. In some embodiments, the duration of contact is used to determine characteristic intensity (e.g., when characteristic intensity is the average of contact intensity over time). In some embodiments, characteristic intensity is compared to one or more sets of intensity thresholds to determine whether an action has been performed by a user. For example, one or more intensity threshold sets may include a first intensity threshold and a second intensity threshold. In this example, contact with a characteristic intensity not exceeding the first threshold results in a first operation, contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second operation, and contact with a characteristic intensity exceeding the second threshold results in a third operation. In some embodiments, comparisons between the characteristic intensity and one or more thresholds are used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or abandon the performance of the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

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

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

[0283] The intensity of a contact increasing from below a light pressure threshold to between a light pressure threshold and a deep pressure threshold is sometimes referred to as a "light pressure" input. The intensity of a contact increasing from below a deep pressure threshold to above a deep pressure threshold is sometimes referred to as a "deep pressure" input. The intensity of a contact increasing from below a contact detection intensity threshold to between a contact detection intensity threshold and a light pressure threshold is sometimes referred to as detecting contact on a touch surface. The intensity of a contact decreasing from above a contact detection intensity threshold to below a contact detection intensity threshold is sometimes referred to as detecting contact lifting off 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 including a corresponding press input, or in response to detecting a corresponding press input performed by a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the contact (or multiple contacts) intensity increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the corresponding contact intensity increases to above a press input intensity threshold (e.g., a "press-to-slap" of the corresponding press input). In some embodiments, the press input includes a corresponding contact intensity increasing to above a press input intensity threshold, and the contact intensity subsequently decreasing to below a press input intensity threshold, and the corresponding operation is performed in response to detecting that the corresponding contact intensity subsequently decreases to below a press input threshold (e.g., a "lift-to-slap" of the corresponding press input).

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

[0286] For ease of illustration, the description of an operation optionally triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided, in response to detecting any of the following: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below a hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example, an operation is described in response to detecting a decrease in contact strength to below the press input strength threshold, which may optionally be executed in response to detecting a decrease in contact strength to below a hysteresis strength threshold corresponding to the press input strength threshold, or a decrease to a hysteresis strength threshold less than the press input strength threshold.

[0287] As used herein, "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 on the device (e.g., become open). In some embodiments, a downloaded application becomes an installed application through an installer that extracts program portions from the downloaded package and integrates the extracted portions with the computer system's operating system.

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

[0289] • Active application: The application currently in use and displayed on the device's screen;

[0290] • Background applications (or background processes) that are not currently displayed, but one or more processes used by the application are being handled by one or more processors; and

[0291] • Pause or hibernate the application, which is not running but has state information stored in memory (either volatile or non-volatile, respectively) that can be used to resume the 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 the application process of stopping and / or removing the application, as well as removing the application's state information from the device's memory. Typically, 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 now turns to context-specific user interface (“UI”) embodiments and associated processes that can be implemented in devices such as 100, 300 and / or 500 having a display and a touch-sensitive surface. Figure 1A , Figure 3 and / or Figure 5A This can be achieved on multi-functional devices such as )

[0295] The following examples illustrate exemplary embodiments of a context-specific user interface. The general concepts described herein relate to customizable context-specific user interfaces. Note that the context-specific user interface described herein can be edited in a variety of ways. The user interface can display or otherwise indicate various types of time-related information, and the type of information can be customizable by the user. The user interface may include customizable aspects such as color, display density, and complication (or lack thereof). 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 hours and minutes (e.g., clock hands or hour / minute indicators). Complications can provide the user with different types of information, such as data obtained from the application, and the information conveyed to the user by the complication is also customizable, as described below.

[0296] These combined features result in thousands (if no more) of available context-specific user interfaces. Since describing each of these permutations is impractical, the use of specific context-specific user interfaces emphasizes specific aspects, but these exemplary descriptions are by no means intended to limit such aspects to such context-specific user interfaces, as 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 concept presented, but those skilled in the art will recognize that many other embodiments are possible within the scope of the techniques described herein.

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

[0298] Users who track the time of day may want to get a sense of how much time has passed since a specific event. For example, a user might want to know how much time has passed since they last checked the time, or since a specific time of day such as morning. In addition to looking at the clock face, users may want to receive additional visual cues that reinforce their perception of the passage of time.

[0299] Animated clock face transitions from indicating a first time to indicating the current time, updating 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 time transition from the first time to the current time. In some embodiments, screen 604 and / or screen 610 may also include a date indication.

[0300] As described above, in Figure 6A The scenario-specific user interface, as exemplified in the example, first displays a clock face indicating a first time. This first time can be determined based on different criteria. In some embodiments, the device receives second data indicating previous user movement toward the electronic device (e.g., movement toward the device such as lowering the user's wrist in the case of a wearable device, or other movements indicating that the user no longer actively looks at the display). The time of the previous user movement toward the device could be the last time the user viewed the device, or the last time the device's display was turned off before receiving data indicating user input 602. The time of the previous user movement toward the electronic device can then be displayed as the first time indicated by the clock face. For example, in... Figure 6AIn this context, 10:05 depicted on clock face 606 could be the previous time the user moved to 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 user viewed the previous time on device 600).

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

[0302] In some embodiments, the predetermined duration is 5 hours. In response to user input, the clock face can depict the time 5 hours prior to the current time, and then the clock face is animated to transition from indicating the first time to indicating the current time. For example, if the current time is 6:00, the device can respond to user input by displaying a clock face showing 1:00, which is then animated to transition from 1:00 to 6:00.

[0303] In other embodiments, the first time can be based on a predetermined time of day. In this case, the device can begin the animation 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 could be morning (e.g., 8:00 AM). In this example, if the current time is 6:00 AM, the device can respond to user input by displaying a clock face showing 8:00 AM, which is then animated to transition from 8:00 AM to 6:00 AM.

[0304] Regardless of how the first time is determined, in some embodiments, the clock face can be animated for a period of time indicating the duration between the first time and the current time. That is, the length of the animation can be approximately proportional to the length of that duration. The length of the animation does not have to be precisely proportional to the first duration, but rather it can convey a basic indication of the approximate length of time to the user. To illustrate using the example described above, if the transition is from 8:00 to 6:00, the clock face can be animated for a longer period of time than if it transitions from 3:00 to 6:00. This can be particularly useful in cases 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, the time elapsed between interactions is longer, or if the clock face animation is shorter, the time elapsed between interactions is shorter.

[0305] In other embodiments, the clock face is animated for a period of time 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 may be the same for each animation. To illustrate using the example described above, the clock face may be animated for the same period of time regardless of whether it is transitioning from 8:00 to 6:00 or from 3:00 to 6:00. This can help reduce the time it takes for the user to see the transition. Alternatively, if the transition is from 8:00 to 6:00, the clock face may be animated for a different period of time than if it is transitioning from 3:00 to 6:00, but the period of time may not be related to the first duration.

[0306] Figure 6B The illustration shows optional features of a user interface specific to this scenario. In response to data representing user input 620, device 600 displays a user interface screen 622, which includes a clock face 624. In this example, the current time is 10:25. Clock face 624 indicates the first time (10:05 in this example). As a background, clock face 624 also displays an image of a mountain view representing the first time. For example, as... Figure 6B As shown, clock face 624 presents a morning view of the mountains (see, for example, the position of the sun 626 in the sky). Therefore, a user viewing clock face 624 interprets 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 the user with additional information, as the user understands the indicated time as 10:05 AM, not 10:05 PM, through the displayed scene.

[0307] In some embodiments, the device accesses a scene image representing the time indicated by a clock face. The scene image representing the time, along with the time indicated by the clock face, can suggest to the user a similar time of day. The scene image does not need to suggest a precise time indicated by the clock face, nor does it need to be strictly linked to the time of day at the scene location (this will be discussed in detail below). In some embodiments, the scene image is an image captured at a time of day 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 scene image is an image captured at a time of day different from the current time.

[0308] In some embodiments, the scene image may depict, for example, a city, seaside, desert, park, lake, mountain, or valley. In some embodiments, the scene may 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 indicating the time between a first time and the current time. This intermediate time is further represented on clock face 632 by a background (see, for example, sunset 634). Screen 640 includes clock face 642 depicting the current time. Clock face 642 also displays a background indicating the current time (see, for example, moon 644).

[0310] Therefore, in some embodiments, and in response to receiving data representing user input 620, the device accesses a first image of the scene representing a first time (e.g., the background of clock face 624), accesses a second image of the scene representing 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 continuous display indicates the passage of time from a first time to the current time. The device may include a series of images of a particular scene (e.g., a time-lapse image), each image 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, a first image and a 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 a scene, including a first image representing the 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 the 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 scene by animate presentation of the sequence of images to indicate the passage of time from the first time to the current time (e.g., like a flipbook). In some embodiments, the scene is specified by the user (e.g., the device may store a collection of time-passage images for different scenes, and the user can select the scene to display).

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

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

[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 may be based on the position along a clock face, such as an hour indicator (e.g., 6 o'clock is positioned at the lower center of the display). In some embodiments, the location may be based on the position across the horizon, such as the position of the sun or moon. For example, Figure 6B In the scene, the position of the sun 626 indicates the first moment, as it represents the sun in the east, almost at noon.

[0316] In some embodiments, the device animates a user interface object by moving it from a first position to a second position on the user interface screen, where the second position is based on the current time. Moving the user interface object from the first position to the second position indicates a time transition from the first time to the current time. Figure 6B As shown, the sun 626 moves across the sky in a sequence of scene images (see sun 626 and sun 634). Subsequently, the 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, user input may include movement of the device. For example, movement of the device might be raising the user's wrist (if the device is wearable), or other movements instructing the user to raise the device to view the display. These movements may be detected, for example, by using an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or combinations thereof. In any of the context-dependent clock faces described herein, movement of the device may be user input that activates the display.

[0318] Furthermore, in any of the context-dependent clock faces described herein, the absence of movement of the device, such as lowering the user's wrist (if the device is wearable) or other movement instructing the user to stop actively looking at the display, or the absence of movement of the device, such as raising the user's wrist (if the device is wearable) or instructing the user to raise the device to look at other movements of the display, can 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 a touch-sensitive surface (e.g., Figure 3 The touchpad 355 in the middle Figure 4B The touch-sensitive surface 451 and / or touch screen 504 are used, and user input can be a touch on the touch-sensitive display.

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

[0321] Users might want to track the time of day while also accessing the stopwatch function. For example, in scenarios such as running or cycling, users might want to operate the stopwatch, record laps, and still keep track of the time of day.

[0322] like Figure 7A As shown in the illustration, 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., numbers 12, 1, 2, 3 and / or scale lines 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 second hand in some embodiments described below. Note that, as used herein, the term second hand refers to the hand on the clock face that indicates seconds, and not the second of two hands on the clock face).

[0323] like Figure 7A As illustrated, device 700 receives user input, in this case, via touch 712 on a start-available element 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 a stopwatch time scale with 60-second intervals. The stopwatch hand's time scale indicates the amount of time required 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 a stopwatch hand 726, which are identical to the hour and minute hands 704 and the stopwatch hand 708.

[0324] Further responding to touch 712, as shown by comparing screens 720 and 730, device 700 animatedly presents 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 indicator 734 shows a stopwatch time scale of 60 seconds, the position of stopwatch hand 736 indicates that 25 seconds have elapsed. Figure 7A As shown, the user accesses this information by touching 740 on the lap (available element) 738, which causes the display of time 742, indicating the elapsed time since touch 712. Note that the hour and minute hands 732 are the same as 722 and 704, and these two hands have not changed position in the past 25 seconds. In this example, the hour and minute hands across screens 702, 720, and 730 indicate the same time of day (e.g., 10:10).

[0325] To put it another way, the device uses hour and minute hands to display the time of day, and it additionally displays a stopwatch hand. In response to receiving data representing user input, the hour indication is replaced by the indication of the first time mark on the stopwatch hand, but the hour and minute hands continue to indicate the time of day, even though the hour indication has been replaced. This allows the user to view both the stopwatch and the time of day simultaneously, while simultaneously showing that the stopwatch has started and indicating its 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 the stopwatch hands are animated 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 stop the animation of the stopwatch hands. For example, this can function similarly to a "stop" function for a stopwatch.

[0327] In some embodiments, the device may display a first availability (e.g., availability 710) representing a start / stop function on a touch-sensitive display. 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 availability. In other embodiments, the device may display separate availability for stopwatch start and stopwatch stop functions.

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

[0329] Additional information and / or functions related to the stopwatch features are accessed directly from a context-specific user interface. In one embodiment, the stopwatch application is as described in the following related application: U.S. Provisional Patent Application No. 62 / 044,979, filed 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. For example, the stopwatch hand can move faster at a time scale of 3 seconds than at a time scale of 60 seconds. This allows 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 a first time scale indication of a stopwatch hand by removing one or more hour time scale indications, displaying a 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 numerical indications of a 12-hour time scale and the first time scale indication of the stopwatch hand is a 6-second time scale, the device can replace 12 numerical values ​​with a single value of 6. In some embodiments, this can be the same value 6 as the previous hour indicator at 6 o'clock, so that the replacement and display are imperceptible to the user. The device can display the value 6 indicating the first time scale indication of the stopwatch hand at the 6 o'clock position on the clock face, and then translate 6 around the clock face in a clockwise motion until it reaches the top of the clock face (the previous 12 o'clock position), where 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 a first time scale.

[0332] like Figure 7B As shown, in some embodiments, the device has a rotatable input mechanism (e.g., 506) that can be used as an optional input to change the stopwatch time scale. Figure 7B A 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 movement (e.g., movement 758) of a rotatable input mechanism, the device 700 changes the stopwatch time scale to a second time scale, as shown in the portion of the clock face 772 on the screen 770, indicated by the stopwatch time scale indicator 776. Note that the screen 770 continues to display the hour and minute hands 774. The second stopwatch time scale differs from the first stopwatch time scale. This allows the user to customize the stopwatch hands' time scale 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 pointer with the second time scale indication of the stopwatch pointer by removing the first time scale indication of the stopwatch pointer, displaying the second time scale indication of the stopwatch pointer, and translating the displayed second time scale indication of the stopwatch pointer in a clockwise rotational motion.

[0334] like Figure 7B As shown, the second time scale indicator 760 of the stopwatch hand is displayed at a position on the clock face relative to its position on 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 60-second time scale indicated by 756. In response to receiving data indicating movement 758, the device removes 756, displays 760, and translates 760 in a clockwise rotational movement 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 first data representing first user input, the device animates a stopwatch hand to represent rotational movement around the origin, and stops the animation at a position relative to π / 2 radians of rotational movement around the origin (e.g., the 12 o'clock position). For example, the stopwatch hand could function as the second hand of a clock face before receiving the first data. When the first data is received, the second hand can be animate to depict rotation around the clock face (e.g., by rotating around the center point of the clock face) until it resets at the 12 o'clock position. This signals to the user that the second hand has now become the stopwatch hand.

[0336] Now turn attention to Figure 8 The example shown is a context-specific user interface. Figure 8 An exemplary context-specific user interface for operation on device 800 is shown. In some embodiments, device 800 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

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

[0338] exist Figure 8In the device 800, a user interface screen 802 is displayed, including a first available element 804. The first available element 804 represents a simulation of regions of the Earth illuminated by the sun at the current time. For example, the first available element 804 shows that North America, Central America, and South America are currently in daylight, and parts of the Pacific Ocean are currently in night, thus simulating regions of the Earth illuminated by the sun at the current time.

[0339] Screen 802 also displays a second availability 806 indicating the current time. The second availability 806 indicates the current time (10:09) and optionally includes indications of a day of the week (Wednesday) and a day of the month (the 25th). Screen 802 further displays a moon availability 808 and a solar system availability 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 region 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 weather conditions at the current time (e.g., by depicting cloud cover or other weather phenomena such as tropical storms). The device can access this data from weather services or external servers (such as The Weather Channel, Accuweather, The National Weather Service, Yahoo!). TM Weather, Weather Underground, the United States Naval Observatory, or the National Oceanic and Atmospheric Administration (NOAA) are used to update the Earth to reflect a global scale. In some embodiments, a simulation of a first region of the Earth illuminated by the sun at the current time can indicate other global events such as the real-time location of the International Space Station, which can be obtained from an external server or service such as NASA.

[0341] Device 800 receives user input (in this example, a swipe 812), and in response to receiving user input, device 800 rotates a 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 available element 822 depicting the second region of the Earth illuminated by the sun at the current time, indicated by a second available element 824. This feature allows the user to access additional information beyond the current time from a context-specific user interface. For example, the user can rotate the simulation of the Earth and see which regions are currently in daylight and which are currently in nightlight. Tying this information to the simulation of the Earth allows the user to access complex geographic and time-related data in an instant, intuitive, and easy-to-understand manner.

[0342] In some embodiments, a first available element 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 available elements 804 and 822, the simulation of the Earth may include a depiction of a region of the Earth currently in daylight, a region of the Earth currently in nightlight, and / or a terminator dividing the two regions.

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

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

[0345] In some embodiments, such as Figure 8As illustrated, the device has a rotatable input mechanism (e.g., 506). Device 800 receives user input indicating movement of the rotatable input mechanism (e.g., movement 830), and in response, device 800 updates a first available element 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, which has a first available element 842 and a second available element 844. Comparing screens 820 and 840, the simulation of the Earth has been updated from the region indicating the Earth at the current time (10:09, indicated by 824) to (compare 822 and 842) the same region indicating 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 position 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 position sensor and displays a first region of the Earth represented by a first available element to indicate the current location of the electronic device. This allows the device to display the Earth in a manner where the current location is a part of the visible portion of the Earth simulation (e.g., as a default or user-selectable country). In some embodiments, the first available element 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, the device (e.g., device 800) visually marks its current location on a globe display (e.g., by displaying a symbol and / or text indicating the current location at an appropriate location on the globe). In some embodiments, this visual marking may be transient; for example, the visual marking may be briefly displayed and then disappear or fade out. In some embodiments, the device does not repeat the visual marking of the current location while the user is at the current location. However, if the user changes location, the device visually marks the new current location on the globe display the first time the user views the display after the change of location, as described above. In some embodiments, the device detects user movement relative to the device (e.g., in the case of a wearable device, movement relative to the device such as raising the user's wrist, or other movements indicating that the user is viewing the display) and, in response, acquires 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 location when the user moved on the previous pair of devices, and based on the determination that the current location has changed since the user moved on the previous pair of devices, the device can visually mark the current location on the globe display.

[0348] In some embodiments, the device may visibly (e.g., by displaying a symbol and / or text indicating the contact's location at an appropriate location on a globe display) mark a location (e.g., the location of the contact's electronic device) corresponding to the contact's location on the globe display. The contact may be stored on the device or communicated with the device wirelessly (e.g., via Wi-Fi, Bluetooth). TM This device is coupled to an external device using 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 a user who has consented to providing their current location to the user of device 800, such as through the Find MyFriend app, and may be provided by a server with data indicating the location of the contact’s electronic device, which may provide the location of the contact stored on device 800. This provides the user of device 800 with a quickly visible reference to alert them to the contact’s current location. In some embodiments, the user may further input the contact’s travel information (e.g., flight data, train data, cruise or ship data, etc. for a contact traveling by air). The device may acquire (in the example of flight data, for example, provided by an airline’s server) data representing the contact’s current or predicted location and update the visible marker of the contact’s location based on the acquired data.

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

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

[0351] The device detects contact on the displayed third available element, and in response to the detection of contact, updates the user interface screen display by displaying a fourth available element representing a simulation of the moon as seen from Earth at the current time and a fifth available element indicating the current time. In some embodiments, updating the user interface screen display includes animate presentation of the first available element representing a simulation of a first region of Earth illuminated by the sun by zooming out. This 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 within the day to using a simulation of the Moon to provide information about the current time within the current month. (Based on reference...) Figure 8 The described context-specific user interface provides users with worldwide, customizable geographic information about day / night conditions. Figure 9 The diagram illustrates a context-specific user interface that provides users with customizable information about the phases of the moon and other lunar features.

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

[0354] As described above, device 900 is device 800 with an updated display. Device 900 is displaying a screen 902 including an offer 904. Offer 904 represents a simulation of the moon as seen from Earth at the current time (e.g., the current lunar phase). In some embodiments, the fourth offer 904 is a realistic representation of the moon as seen from Earth at the current time, having depicted actual lunar features. As shown in the fourth offer 904, the current lunar 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 available element 904 can depict a realistic representation of the moon, similar to how it actually appears in the night sky. Screen 904 also includes a fifth available element 906, which 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 912 of a rotatable input mechanism), and in response to receiving user input, the device rotates a simulation of the moon to display the moon as seen from Earth at a non-current time, as shown on screen 920 by available element 922, which indicates the moon at a non-current time, indicated by an updated fifth available element 924. The non-current time can be within the current month or in a different month.

[0356] This is somewhat similar to the relationship between users and targets. Figure 8 The described interactive simulation of Earth. Figure 9 The scenario-specific user interface illustrated herein allows users to access information about the appearance of the moon at various times (e.g., lunar phases or which areas of the moon are visible from Earth). In some embodiments, the size of the simulated moon shown 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 an external server such as NASA.

[0357] In some embodiments, a user can rotate a representation of the moon and view the corresponding time by swiping the touch-sensitive display. In some embodiments, user input may include a swipe in a first swipe direction on the touch-sensitive display. In some embodiments, in response to receiving user input, a simulation of the moon as seen from Earth is rotated in a first rotation direction. In some embodiments, the first rotation direction may be at least partially based on the first swipe direction. As used herein, the rotation of the moon may include rotation of the moon on its axis to depict different regions of the moon (e.g., regions of the moon not visible from Earth) and / or updating the appearance of the moon as seen from Earth at a particular time of interest (e.g., updating the displayed lunar phase) based on rotation of the relative positions of the moon, Earth, and 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 Earth in a second rotation direction different from the first rotation direction. The user input may include, for example, a swipe on a touch-sensitive display in a second swipe direction different from the first swipe direction.

[0359] This allows users to guide both the direction of the moon's rotation and the time indicated by the fifth available element in response to a swipe. For example, a user can swipe in one direction to rotate the moon in that direction and view the moon at a later time in that month, and a user can swipe in another direction to rotate the moon in the opposite direction and view the moon at an earlier time in that month.

[0360] In some embodiments, such as Figure 9As shown, a user can rotate the representation of the moon and view the corresponding time by rotating the rotatable input mechanism. Therefore, in some embodiments, the device has a rotatable input mechanism (e.g., 506), and user input may include movement of the rotatable input mechanism in a first rotation direction (e.g., rotation 912). In some embodiments, in response to receiving user input, the simulation of the moon as seen from Earth is rotated in the first rotation direction. In some embodiments, the first rotation direction may be at least partially based 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 a 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 guide both the direction of the moon's rotation and the time indicated by the fifth available element 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 that direction and view the moon at a later time 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 at an earlier time in the month.

[0363] In any embodiment of the embodiments described herein, the displayed moon simulation may indicate one or more additional moon attributes, such as a special moon (e.g., blue moon, black moon, or red moon, lunar eclipse, etc.), the distance between the moon and the earth (as described above, for example, for a supermoon), and / or lunar tremors. In some embodiments, additional moon attributes may 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, additional moon attributes may be indicated by text. In some embodiments, additional moon attributes may correspond to current moon attributes. In some embodiments, additional moon attributes may correspond to the moon attributes of the currently displayed date (e.g., as described above, in the case where the user has rotated the moon to view the moon at a time before or after the month). For example, in some embodiments, when the moon simulation is being rotated to depict the moon at different times in a month or year, the moon simulation may be updated to reflect one or more additional moon attributes at the time currently indicated by the displayed moon simulation.

[0364] In some embodiments, the device may display additional moon information in response to user input. This additional moon information may be displayed as a portion 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 may 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., on the current day and / or at the user's current location), etc. In some embodiments, the additional moon information may 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 may correspond to the moon information for the currently displayed date, as described above, for example, in cases where the user has rotated the moon to view the moon at a time earlier or later in the month.

[0365] For example, in some embodiments, the device may detect user input (e.g., a double tap on a touch-sensitive display, including a first contact 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 were 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 were 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 available element indicating the Earth (e.g., 910 or 928). Upon accessing the Earth available element, the user can return to the reference. Figure 8 The described context-specific user interface. In some embodiments, the Earth available element can be a graphical or stylized representation of the Earth, such as an icon, symbol, or text indicating the Earth. In some embodiments, the Earth available element can be a realistic representation of the Earth.

[0367] In some embodiments, device 900 displays a sixth available element (as depicted by available elements 810, 828, 848, 908, and 926) representing the solar system on a user interface screen. In some embodiments, the sixth available element may 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 available element may be a realistic representation of the solar system.

[0368] Device 900 detects contact on the displayed sixth available element, and in response to the detection of contact, updates the display of the user interface screen by displaying a seventh available element and an eighth available element. The seventh available element has a representation of the Sun, Earth, and one or more non-Earth planets at their respective locations at the current time, and the eighth available element indicates the current time. In some embodiments, updating the display of the user interface screen includes animate presentation of a first available element representing a simulation of a first area of ​​Earth illuminated by the Sun by zooming out, or animate presentation of a fourth available element representing a simulation of the Moon as seen from Earth. This animation allows the user to recognize that the astronomical scale and / or angle has changed.

[0369] This transitions users from using a simulation of the moon to view information about the current time within the current month to using a simulation of the solar system to view information about the current time within the current year. (Based on reference...) Figure 9 The described context-specific user interface provides users with customizable information about the moon's condition. Figure 10 The diagram illustrates a context-specific user interface that provides users with customizable information about the solar system and the relative positions of Earth and other planets.

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

[0371] As described above, device 1000 is device 800 and / or device 900 with an updated display. Device 1000 displays a screen 1002 including a seventh available element 1004. The seventh available element 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 as planet 1010). 1006, 1008, and 1010 are depicted at their respective locations under the current date indicated by an eighth available element 1012 (May 25, 2014 in this example). In some embodiments, the eighth available element 1012 also indicates the current time of day.

[0372] Optionally, in some embodiments, the solar system depicts all eight planets. In some embodiments, the solar system depicts four inner planets. In some embodiments, the solar system depicts other astronomical features, such as asteroids or asteroid belts, one or more moons of one or more planets (e.g., the Moon), 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 the seventh available element 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 the seventh available element 1022 on screen 1020. The seventh available element 1022 includes a representation 1024 of the Sun, a representation 1026 of the Earth, and representations of Mercury, Venus, and Saturn (e.g., Saturn depicted by planet 1028) at their respective positions on a non-current date indicated by the eighth available element 1030 (November 25, 2014). In some embodiments, the eighth available element 1030 also indicates the current time of day.

[0374] This context-specific user interface allows users to access information about the relative positions of Earth and one or more non-Earth planets on a date other than the current date, which may be within the current year or in a different year. In some embodiments, the Sun, Earth, and one or more non-Earth planets are depicted as realistically rendered. 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 a representation of the solar system by swiping on a touch-sensitive display. Therefore, in some embodiments, user input may include a swipe on a touch-sensitive display. In some embodiments, in response to detecting a swipe, the Earth and one or more non-Earth planets are rotated around the Sun in a first rotation direction. In some embodiments, the first rotation direction may be at least partially based on the first swipe direction.

[0376] In some embodiments, in response to detecting a swipe in different directions on a touch-sensitive display, the device causes the Earth and one or more non-Earth planets to rotate around the Sun in a second rotation direction different from a first rotation direction. This allows the user to guide both the rotation direction of the Earth and one or more non-Earth planets and the time indicated by an eighth available element in response to a swipe. For example, a user can swipe in one direction to rotate the Earth and one or more non-Earth planets in that particular direction and view the Earth and one or more non-Earth planets on later dates during that year (or in different years), and a user can swipe 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 on earlier dates during that year (or in different years).

[0377] In some embodiments, such as Figure 10As shown, a user can rotate a representation of the solar system by rotating a rotatable input mechanism (e.g., 506). In these embodiments, user input may include movement of the rotatable input mechanism in a first rotation direction (e.g., movement 1018). In some embodiments, in response to receiving user input, the Earth and one or more non-Earth planets are rotated around the Sun in the first rotation direction. In some embodiments, the first rotation direction may be at least partially based 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 around 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 guide the rotation direction of the Earth and one or more non-Earth planets, as well as the time indicated by an eighth available element, 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 that specific direction and view the Earth and one or more non-Earth planets at a later time during that 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 that 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 loop. 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] A contact is made at a location associated with the representation of a non-Earth planet on a touch-sensitive display. For example, the contact may be located at or near the representation of the displayed planet itself, or at or near the representation of the planet's orbit. In some embodiments, the device may determine the selected planet based on identifying the representation of the displayed planet or the representation of the planet's orbit closest to the contact location. In some embodiments, the contact may be a press-and-hold type contact on the display. Upon detection of a contact, the device may (e.g., by changing the color and / or brightness of the displayed planet and / or orbit, by displaying the outline or other visual demarcation of the planet and / or orbit, by animing the planet and / or orbit, etc.) visually distinguish the representation of the selected planet and / or the representation of the selected planet's orbit. In some embodiments, while receiving contact, the device may determine whether the duration of the contact exceeds a predetermined threshold, and based on the determination 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. This type of 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.), (in the case that the selected planet is not Earth) the distance between the planet and Earth (e.g., current distance, average distance, etc.), the time when the planet will become visible from Earth and its position in the sky (in the case 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 the planet's discovery, information about the planet's name, etc.), and the time (past, present, or future) when the planet is specifically aligned with another object in the solar system.

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

[0383] In some embodiments, after updating the display to show a simulation of the solar system, the user interface screen displays an availability indicating the Moon (e.g., 1016 or 1034) and / or an availability indicating the Earth (e.g., 1014 or 1032). In some embodiments, the Moon and / or Earth availability may be a graphical or stylized representation of the Earth or Moon, such as an icon, symbol, or text. In some embodiments, the Moon and / or Earth availability may be a realistic representation of the Moon or Earth. When the Earth availability is accessed, the user can return to the reference. Figure 8 This describes a context-specific user interface. When the user interacts with the moon-related component, they can return to the reference. Figure 9 The context-specific user interface described.

[0384] exist Figures 8 to 10 In some embodiments of any context-specific user interface illustrated in the figure, the user can move (e.g., rotate) a rotatable input mechanism to scroll forward or backward in time toward the displayed time indication. It should be appreciated that such a feature can be applied to any context-specific user interface described herein; however, for ease of explanation, reference may be made to… Figures 8 to 10 This feature can be described using any model for mapping the movement of a rotatable input mechanism to a rolling distance or speed, such as the model described in U.S. Patent Application No. 14 / 476,700, filed September 3, 2014, entitled "Crown Input for a Wearable Electronic Device," which is incorporated herein by reference in its entirety. For example, acceleration, velocity, etc., can be used to determine the amount of speed at which the displayed time indication is adjusted.

[0385] In some embodiments, a user can move a 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 Earth's rotation, to show the Earth illuminated by the sun at different times of 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 moon simulation to show different lunar phases at different times of the month (e.g., comparing 904 and 922), and / or update the displayed time indication to show different times (e.g., comparing 906 and 924). Similarly, as Figure 10 As shown, in response to detecting movement of the rotatable input mechanism (e.g., movement 1018), the device can update the displayed positions 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., comparing 1008 and 1010 with 1026 and 1028), and / or update the displayed time indication to show different times (e.g., comparing 1012 and 1030). In some embodiments, the representation of the positions of the Earth, Moon, and / or Earth and one or more non-Earth planets can be rotated based on the direction of movement of the rotatable input mechanism. In some embodiments, the representation of the positions of the Earth, Moon, and / or Earth and one or more non-Earth planets can be rotated at a certain rate based on the rate and / or amount of movement of the rotatable input mechanism, such as 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 can cause the displayed time indication to be updated at different time scales. For example, the same rotation angle and / or rate can cause... Figure 8 The scenario-specific user interface shown is updated hourly, while Figure 9 The scenario-specific user interface shown can be updated daily or weekly, or Figure 10 The scenario-specific user interface shown can be updated by month or year.

[0386] exist Figures 8 to 10 In some embodiments of any context-specific user interface illustrated in the diagram, the device may 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, a user may tap on the display (e.g., at a location corresponding to space), and in response to detecting a tap, the device may 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 that can operate on device 1100 is shown. In some embodiments, device 1100 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0388] Users may want to view the time of day in the context of day and night hours. For example, users may want 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 wave 1108. The sine wave 1108 can represent the general appearance of a sine wave without mathematical precision or accuracy. However, importantly, the sine wave 1108 has a period of approximately one day and indicates the path of the sun throughout the day. Figure 11A As shown, the trough of wave 1108 represents solar midnight (corresponding to a 24-hour interval between two solar midnights), and the peak of wave 1108 represents solar noon. Also displayed on screen 1102 is a first available element 1110, shown along the sine wave 1108 at a position indicating the current time of day. Screen 1102 also displays a horizon 1112 (an optional feature that divides the display into day and night sections). As shown, the horizon 1112 intersects the sine wave 1108 at two points, representing sunrise and sunset. Finally, screen 1102 displays a second available element 1114, indicating the current time of day.

[0390] Throughout the day, 1114 displays the current time (5:30 AM in this example), and the first available element 1110 follows a sine wave track. When 1110 is in the daytime portion 1104, the current time is during 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 the first available element 1110 is still within the nighttime portion of screen 1102. This context-specific user interface 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 the first available element 1110, when the position is entirely within the nighttime portion of the display (e.g., 1106), the available element representing the sun is presented as hollow (e.g., like a ring). This further emphasizes to the user that it is just before dawn.

[0391] For example, screen 1120 shows a second time of day and includes a first available element 1122, a sine wave 1124, and a second available element 1126. As indicated by the second available element 1126, it is currently sunrise time at 7:00 AM. The position of the first available element 1122 along the waveform 1124 between the first and second portions indicates the transition from night to day. This is further depicted on screen 1120 by positioning the available element 1122 on line 1128, which separates the two portions of the display. This is further indicated by the appearance of the available element 1122 itself; optionally, the available element may be partially filled when it is located at the intersection of the first and second portions of the display.

[0392] Screen 1130 displays the third time of day and includes a first available element 1132, a sine wave 1134, and a second available element 1136. As indicated by the second available element 1136, it is now 2:00 PM. The first available element 1132, positioned along the waveform 1134 within a first portion of the display, indicates daytime. This is further depicted by the appearance of the available element 1132 itself; optionally, the available element can be fully filled when it is fully positioned within the first portion.

[0393] In some embodiments, the colors of the first and / or second portions can indicate daytime (e.g., using warm or light colors) or nighttime (e.g., using dark or cool colors). In some embodiments, the first and second portions 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 sine wave, an optional horizon, and / or an optional sun-viewing element (e.g., fully filled, partially filled, or hollow). In some embodiments, the sine wave can include two or more colors, and these colors can indicate daytime and nighttime portions (e.g., portions of the waveform in the daytime portion can be one color, and portions of the waveform in the nighttime portion can be another color). Furthermore, the two portions can have any shape (not limited to rectangles). For example, the daytime portion can appear as an illuminated circle containing the sine wave, while the nighttime portion appears entirely around the circle.

[0394] In some embodiments, device 1100 may have a location sensor (e.g., GPS sensor 532 and / or GPS module 135). In these embodiments, device 1100 can obtain the current location of the device from the location sensor and indicate the number of day and night hours at the current location and time by the ratio of the first and second portions displayed. That is, the size of the daytime and nighttime portions of the display can be adjusted relative to the number of daytime hours at the current location and date. As an illustrative example, if the current location is near the Arctic Circle during summer, the daytime portion may include all or almost all of the screen such that all or almost all of the displayed sine wave is within the daytime portion. As another example, if the user will be traveling globally along latitudes, the location of available components 1110, 1112, or 1132 (e.g.) will not change, but the ratio of the daytime portion to the nighttime portion and the relative amount of the sine wave within each portion will be adjusted to reflect the current location. This provides the user with a more realistic depiction of the time of day, thus enhancing the user interface.

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

[0396] Attention shift Figure 11B , Figure 11B The illustration shows an example of a context-specific user interface that provides interactive features for users to view additional day / night information. Figure 11B A user interface screen 1140, which can be displayed on device 1100, is shown. Screen 1140 includes a first availability 1142 indicating the position of the sun along a sine wave 1144 at the current time. Screen 1140 also displays a second availability 1146, which also indicates the current time (10:09 AM). Device 1100 receives user contact at the displayed first availability 1142, indicated by touch 1148.

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

[0398] It should be noted that the movement of the contact can begin and end at a position on a sine wave, but the movement itself does not need to precisely track the trajectory of the sine wave. That is, the user is not required to precisely follow the trajectory of the sine wave with the contact. The device can receive only user contact at the first available position displayed, and while continuously receiving user contact, detect the movement of the contact from the first position to the second position in the absence of interruptions 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 can translate the first available element on the screen to the second position while simultaneously following the trajectory of a sine wave. Therefore, even when user contact does not require following the trajectory of a sine wave, the device still translates the first available element from the first position to the second position by causing it to follow the trajectory of the sine wave. In some embodiments, the device can continuously update the time as indicated by the second available element. Alternatively, the device can update the time indicated by the second available element 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 can translate the first available element on the screen to the second position on the sine wave.

[0400] Figure 11BThe illustration shows optional features of the context-specific user interface. As shown on screen 1140, in response to receiving a user touch 1148 at availability 1142, device 1100 displays availability 1150 and 1152 depicting sunrise and sunset, respectively. Availability 1150 and 1152 are displayed along waveform 1144 at two points where the waveform intersects with the boundary between a first portion indicating daytime and a second portion indicating nighttime. This boundary is defined on screen 1140 using an optional horizon 1154. When horizon 1154 is displayed, availability 1150 and 1152 are displayed at the two points where line 1154 intersects with waveform 1144. In some embodiments, availability 1150 and 1152 may further include numerical displays of sunrise and sunset times, respectively. In some embodiments, these availability elements are also displayed simultaneously with device 1100 receiving a user touch at a second location.

[0401] In response to a user touch 1148 at the available element 1142, available elements 1156 and 1158 are also displayed on the screen 1140. Available elements 1156 and 1158 are displayed along waveform 1144 at positions corresponding to dawn and dusk, respectively. In some embodiments, these available elements are also displayed simultaneously with a user touch at a second position received by the device 1100. These displayed available elements 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 before they will occur based on their distance from the available element 1142. In some embodiments, the time of dawn can be astronomical dawn, maritime dawn, or civil dawn. In some embodiments, the time of dusk can be astronomical dusk, maritime dusk, or civil dusk.

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

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

[0404] Users can also contact the touch-sensitive display using touch 1188 on screen 1180. This contact can be, for example, anywhere on the display except for the location of the first available element indicating the current time of the sun. In response to a detected contact, device 1100 displays screen 1190, which includes sunrise time 1192, sunset time 1194, and available elements 1196 providing non-textual indications of day and night. This allows the user to access sunrise and sunset times from any user interface screen.

[0405] Users can also set reminders for specific times of day through a 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 a first available element to a third position indicating a time outside the current day. The user can then touch the first available element displayed at the third position, and in response to detected contact, the device can set a user reminder for the specified time of day.

[0406] For example, the device may display another available element indicating a user prompt for setting an alarm for a specified time of day. This prompt may be a visual alarm. In this example, the device may display a visual alarm that appears as the time of day approaches. Alternatively, the device may display a visual available element at any time, showing a third position along a sine wave to help the user understand how far the specified time of day is from the current time. In some embodiments, the user prompt may include an audible alarm that notifies the user when the specified time of day has arrived or is about to arrive. In some embodiments, the user prompt may include a haptic alarm. The device may (e.g., using haptic feedback module 133 and haptic output generator 167) create a haptic signal to the user as the specified time of day approaches.

[0407] These features allow users to further customize the context-specific user interface. It should be understood that this feature does not create specific alerts for time and date; rather, it allows users to set general alerts for a time of day that is not tied to a specific date. For example, a user might notice a specific lighting effect, such as sunlight streaming through a window in their home, and want to set an alert so that they observe this effect at that 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 that can operate on device 1200 is shown. In some embodiments, device 1200 may be device 100, 300, or 500. In some embodiments, the electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0409] Users may want to view a specific background image on the user interface screen while retaining as much of the original image as possible. Therefore, it can be advantageous to provide a context-specific user interface that, instead of simply displaying the time and / or date as interface objects displayed on top of the image, presents them as interface objects that appear to originate from the image itself. This maximizes the user's view of the image while still providing a visual indication of the time and date. This may be particularly true when the user interface is displayed on a smaller screen.

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

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

[0412] Screen 1202 also includes user interface objects 1206 and 1208. 1206 indicates the date (23rd), while 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 comprises multiple pixels. A subset of these pixels is modified in an image-related manner so that the subset represents one or more user interface objects 1206 and 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 the color and / or intensity.

[0414] In some embodiments, a subset of pixels can be modified through color blending. In some embodiments, a subset of pixels can be modified through color blurring. In some embodiments, a subset of pixels can be modified by applying a gradient. Importantly, these examples illustrate that the appearance of a subset of pixels can be affected by both the background image at the location 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 top of and obscuring the image), while also maintaining the legibility of the user interface object.

[0415] In some embodiments, one of the user interface objects 1206 and 1208 is displayed by modifying the background, and the other user interface object is displayed independently of the background (e.g., without a set of colors and / or intensities produced by modifying a subset of background pixels). In these embodiments, the device may receive data representing the background color at the location of the displayed user interface object (e.g., 1206 or 1208), and the color of the displayed user interface object may differ from that background color (e.g., a different color and / or intensity). For example, the background color at the location of the displayed user interface object may include the most prevalent color at that location. This feature ensures that, regardless of the appearance of the background, if one of the user interface objects is a preset color, it will be distinguishably displayed on the background.

[0416] In some embodiments, a background-based image may be stored on device 1200.

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

[0418] Optionally, 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 from the background of the external device to represent one or more user interface objects, such as a user interface object indicating a date and a user interface object indicating the time of day. In some embodiments, device 1200 can further modify the background from the external device, for example, by changing one or more of the following: 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 A user may wish to select an image from a folder of images to use as a background. Therefore, device 1200 can 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 including a background based on the first image (e.g., background 1204). As described above, this background includes a subset of pixels whose appearance has been modified in relation to the image to represent one or more user interface objects, such as a user interface object indicating a date (e.g., 1206) and a user interface object indicating a time (e.g., 1208).

[0420] Optionally, such as Figure 12 As shown, after displaying screen 1202, device 1200 can receive data representing user input. In response, device 1200 acquires data representing background 1204, selects a second image from a folder that is different from the first image, and displays screen 1210 including a background 1212 based on the second image. Figure 12As shown, 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 compared to the image shown before the user's input.

[0421] like Figure 12 As shown above, screen 1210 also includes a user interface object 1214 indicating the date and a user interface object 1216 indicating the time of day. As described above, at least one of these user interface objects is displayed by modifying a subset of pixels of the background 1212 at the location of the displayed user interface object. This subset can be modified in any of the ways described above, such as color blending, blurring, gradients, etc. In some embodiments, as described above, one of the user interface objects can be a color independent of the background, and device 1200 can modify this color to fit the background. As described above, the image on which the background is based can be stored on device 1200 or on an external device.

[0422] Multiple user inputs can be used to change the background. In some embodiments, user input can be a touch on the display, rotation of a rotatable input mechanism, pressing down on a rotatable input mechanism, or a swipe on the display. In some embodiments, user input can be user movement on the electronic device (e.g., movement on the device such as raising the user's wrist in the case of a wearable device, or other movements indicating that the user is viewing the display). Advantageously, this feature allows the device to display different images each time the display is viewed, thereby providing the user with a customized display each time and enhancing user interaction with the device. As described above, user movement on 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 combinations thereof.

[0423] In some embodiments, a user can choose to exclude images from a folder so that they are no longer selected as backgrounds. In these examples, the device can receive data indicating that the user has excluded images from the folder. This can be achieved by... Figure 12 The user interface shown can receive this prohibition, or it can receive it through a folder containing two or more images (for example, the folder may include features that allow users to select more images, drag images into the folder, delete images from the folder, and / or prohibit images from being used as a background). In response to receiving this data, the device can prevent the image from being displayed as a background in response to future user input.

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

[0425] Users may want to see the displayed animations on their electronic devices in response to input. Since users may look at their electronic devices many times a day, especially if they rely on devices for timing, providing a different experience each time they view the screen can be advantageous. This maintains user interest and engagement with the electronic device.

[0426] like Figure 13A As shown, in response to the detection of 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, shown by butterfly 1308, depicts a butterfly with its wings open. Next, screen 1310 displays a second animated sequence depicting butterfly 1314 flying from the right side of the display to the left. Note that screen 1310 also displays user interface object 1312 indicating the time. Finally, screen 1320 displays a third animated sequence depicting butterfly 1324 closing its wings. Screen 1320 again displays user interface object 1322 indicating the time.

[0427] Later in the day, such as Figure 13B As shown, device 1330 detects a second user input 1332. In response, device 1300 accesses data representing the sequence of animations previously displayed (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 displaying three animated sequences. Butterfly 1336 on screen 1330 is animated using the same sequence as butterfly 1308 on screen 1302, showing a butterfly with its wings open. Next, screen 1340 displays butterfly 1334, animated as if flying from the left to the right of the display. The sequence of animated butterfly 1334 differs from the sequence of animated butterfly 1314 on screen 1310 (data representing the sequence of butterfly 1314 has been accessed previously). This ensures that the user will see an animated presentation different from the previous user input. This makes the animated presentation appear more realistic and / or engaging to the user, as this variation gives the animated user interface object a more random and lifelike quality.

[0429] Finally, screen 1350 displays butterfly 1354, which is animated using the same sequence as butterfly 1324 on screen 1320 (a butterfly with its wings closed). Screens 1340 and 1350 also include user interface objects 1342 and 1352, respectively, indicating the 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 not necessarily the same. In some embodiments, user interface object 1336 may be the same as user interface object 1308. In other embodiments, user interface object 1336 may be an object related to but not the same as user interface object 1338. For example, these user interface objects may be animals of the same general type but with different appearances (e.g., different colors, different postures, different species, etc.).

[0431] The user interface object presented in the simulated animation can be an animal, such as a butterfly or 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 character, a human, etc. The context-specific user interface is not limited to a specific animated user interface object. The sequence of animations can be specific to the displayed object. For example, a jellyfish can swim across the screen in various directions, and 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 sequence of third animation presentations can be based on the reverse of the sequence of first animation presentations. For example, if the first sequence depicts a butterfly with its wings open, the third sequence could depict a butterfly with its wings closed. Since these sequences run throughout the entire animation presentation sequence, this feature gives the whole sequence a unified feel. In some embodiments, the state of the user interface object at the beginning of the first animation presentation sequence (e.g., butterfly 1308 has closed its wings, which are then animated to open) corresponds to the state of the user interface object at the end of the third animation presentation sequence (e.g., butterfly 1324 is animated to end with its wings closed), thereby giving the user the impression of a seamless animation presentation.

[0433] Various user inputs can be used to display the screen illustrated in Figure 13. In some embodiments, user input can be a touch on the display, rotation of a rotatable input mechanism, pressing down on a rotatable input mechanism, or a swipe on the display. In some embodiments, user input can be user movement of the electronic device (e.g., movement of the device such as raising the user's wrist in the case of a wearable device, or other movements indicating that the user is viewing the display). Advantageously, this feature allows the device to appear to display a different animation presentation each time the display is viewed.

[0434] In some embodiments, the user interface object displayed in response to user input can be the same after each input. In other embodiments, the user interface object can be different each time. For example, the user interface object can be reflected (e.g., around a horizontal and / or vertical axis), flipped, and / or rotated to create new user interface objects. This is a source of diversity in the sequence of displayed user interface objects and animated renderings. For example, horizontally, vertically, and horizontally and vertically rotating a single object creates four new objects, which create even more variations when coupled with animated renderings that guide the object's movement. These aspects add the possibility of combination, which significantly increases the number of animated renderings available for a single object, thus reducing the number of pre-programmed sequences of animated renderings. It also helps to animate objects such as jellyfish using fewer inherently characteristic and / or movement elements.

[0435] Users can also change the displayed user interface object. For example, device 1300 can detect touch on a touch-sensitive display, and in response, device 1300 can replace the displayed user interface object with a second user interface object. This second user interface object can be associated with the first user interface object (e.g., if the previous butterfly was blue, the user can select an orange-red butterfly).

[0436] In some embodiments, such as Figure 13A and Figure 13B As shown, the user interface object indicating 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 that can operate on device 1400 is shown. In some embodiments, device 1400 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0438] Users may want to keep the time connected to an interactive clock face. For example, users might want to see animated presentations or a clock face that changes color each time they look at the display, keeping interaction with the device fun. Users may also want to customize the clock face using personalized complications such as monograms or personalized widgets to display application data.

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

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

[0441] Figure 14ATwo types of hour indicators are depicted: numerical hour indicators (e.g., 3, 6, 9, and 12 as indicated by hour indicators 1436, 1446, and 1456) and symbolic hour indicators (e.g., scale markings displayed between the numerical indicators on screens 1440 and 1450). Either type of indicator can be used alone or in combination. Any type of symbol can be used as an hour indicator; its position around the clock face, rather than the symbol itself, conveys to the user which hour is indicated. The numbers (or omissions) of the hour and / or minute indicators can be further customized by the user, as will be discussed in more detail below.

[0442] Figure 14A One or more hour indicators can be displayed progressively in a clockwise direction (e.g., as depicted on screens 1430 and 1440, they can appear sequentially in a clockwise direction). Similarly, the clock outline can optionally appear in a clockwise direction. This helps orient the user. Optionally, the minute indicators can appear progressively in a clockwise direction. The hour and minute hands (and optionally, the second hand) can also be animated, such as radially (e.g., starting from the center of the clock face and appearing to extend outwards toward the outline). In some embodiments, the hour and minute hands appear first, followed by the hour indicators, and then the minute indicators. In some embodiments, the clock face displays the current time.

[0443] In some embodiments, the clock face may include color. Features such as the clock face background, clock face outline, second hand, hour indicator, minute indicator, hour hand, minute hand, etc., can 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 passage of time through color changes. The color can 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 the hand, dot, or other optional features). As an illustrative example, the color can cycle through color gradients, and a complete cycle can last for one minute, one hour, one day, etc.

[0444] In some embodiments, device 1400 may detect user movement toward the device. As described above, user movement toward the device may be detected, for example, by using an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or combinations thereof. User movement toward the electronic device may include movements 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 may 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 may be used to allow a user to change a static color displayed on the clock face. In other embodiments, as illustrated above, this feature may be used to allow a user to change a continuously changing color.

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

[0446] Now return to Figure 14A In some embodiments, the letter combination can be displayed as a complication. Screen 1450 shows a letter combination available 1460 displayed as a clock face complication. Device 1400 can receive data representing a name and, in response to receiving the data, generate the letter combination and display it as available 1460 (in this example, "MJ"). Device 1400 can receive this data from one or more sources such as saved contact entries, V-cards, images containing the letter combination (e.g., images taken or uploaded by the user), etc. In some embodiments, device 1400 has a user interface for editing the letter combination, which can be a feature of the user interface described in FIG. 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., complication, letter combination, and / or color) 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 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300) Figure 3 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 a growing demand for interactive user interfaces that enhance user interaction with these devices. Indicating time through a character-based user interface can enhance this interaction. Increasing the level of character interactivity and improving the impression of natural movements displayed by the character enhances its lifelike appearance, thereby strengthening and extending user interaction. By delivering a more realistic and interactive character-based user interface, which not only ensures timekeeping but also provides information related to other events, user interaction is further enhanced.

[0449] Therefore, this paper provides context-specific user interfaces that include person-based user interface objects. For such person-based user interface objects, users may desire a more natural and realistic appearance. Furthermore, for person-based user interface objects, users may want more dynamic actions to interact with them and / or provide them with event-related information.

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

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

[0452] The character user interface object 14604 can indicate 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, shifting its center of gravity, and / or changing its behavior (e.g., facial expressions).

[0453] As described in this article, a character user interface object can indicate time by varying the precision. Figure 14B As shown, a character user interface object can include one or more numerical indications of time values, i.e., numbers indicating the hours, minutes, or seconds on a clock face. However, since users are accustomed to perceiving a clock face, numerical indications of time values ​​are optional, as the relative positioning of two objects resembling clock hands can indicate approximate time without such numerical indications.

[0454] Any user interface screen described herein may further include one or more complex components, such as indications of date, stopwatch, timer, alarm, etc.

[0455] Additionally, the limbs 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 its "pointing" position along a vector on the display. A limb can also indicate time by displaying directional indicators, such as a finger indicating a position corresponding to a time on the display, as described above, by its relative position or by showing a direction along a vector. Limbs do not need to indicate time precisely.

[0456] Device 14000 can update the character user interface object to indicate a second time by reversing the roles of the first and second limbs; that is, by using the second limb to indicate the second hour and by using the first limb to indicate the second minute. For example, Figure 14B The device 14000 shows a user interface screen 14610 that can be displayed. The user interface screen 14610 includes a character user interface object 14612. The character user interface object 14612 may be the same character user interface object as the character user interface object 14604, but represents a different time.

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

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

[0459] Because allowing the character to maintain a natural appearance, the character user interface object can use limbs with reversible roles to indicate time, increasing the flexibility for displaying the character user interface object. Otherwise, if the limb roles were fixed, the character might awkwardly distort at specific times of day (e.g., between 12:30 and 12:40). Allowing the character to swap limb roles provides more options for character poses and positions that can represent a more natural appearance, thereby enhancing user interaction with the device by depicting more realistic character user interface objects.

[0460] Now turning Figure 14C Users may prefer to interact with a more natural-looking character user interface object. If a character user interface object uses limbs that always move from a fixed position or the character itself to indicate time, this diminishes the character's natural appearance by limiting the character's pose and / or range of movement. This can result in awkward poses and / or a monotonous character appearance. Limbs can indicate time by animating free movement from both ends of the limb, rather than a representation of rotation around an axis that is always fixed at one end, making the character user interface object appear more natural at different times of the day.

[0461] It should be understood that the descriptions of mechanical motion (e.g., limb movement) used in this document include representations or simulations of mechanical motion.

[0462] Figure 14C An exemplary user interface screen 14702 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300), etc. Figure 3 ) and / or one or more of the 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 a representation of limbs 14706. As shown on user interface screen 14702, character user interface object 14704 can indicate time, such as hours like 12, through 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, which serves as a representation of the axis of rotation of limb 14706. That is, the position of limb 14706 can be displayed or animated such that the representation rotates around endpoint 14708 to show different times of day. Limb 14706 also has a second endpoint 14710 at a second position indicating a time value. In some embodiments, the time value may be an hour, minute, and / or second.

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

[0466] As an example, user interface screen 14720 shows a character user interface object 14722, which has limbs 14724, with a first endpoint 14726 and a second endpoint 14728. Character user interface object 14722 may be a display of an updated character user interface object 14704. Compared to user interface screens 14702 and 14720, particularly limbs 14706 and 14724, the positions of the first endpoints have been updated, as reflected by the positions of the first endpoints 14708 and 14726. The first endpoint 14726 is in a third position, and the 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 at the axis of rotation.

[0467] In some embodiments, the 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, the first endpoint 14714 being the axis of rotation of 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 the first endpoint 14714 of second limb 14712 to a third position, and to indicate a second time value by moving the second endpoint 14716 to a fourth position. This is depicted on user interface screen 14720, which depicts second limb 14730 having a first endpoint 14732 at a third position and a second endpoint 14734 at a fourth position.

[0468] As described above, the first and second limbs 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 connects the movement of each limb through each shoulder, such 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, like an active human body, by coordinating or otherwise associating the movement of the two limbs.

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

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

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

[0472] Device 14000 can update the character interface object 14804 to indicate a second time value by moving the second endpoint 14814 along the rotation axis to a third position to indicate a second time. In anthropomorphic terms, limb 14806 has a representation of an upper arm 14808 joined at the elbow 14812 and a forearm 14814. The forearm 14814 can rotate at the elbow 14812 to indicate different times. Adding joints to the limb indicating time is similar to the hands of a clock, except that the arm appears more natural than a clock hand due to its joints. Furthermore, joints increase the possible range of movements that can be depicted by the limb.

[0473] User interface screen 14820 illustrates this by displaying a character user interface object 14822 having limbs 14824. In some embodiments, the character user interface object may be the same 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, the second endpoint 14834 is in a different position than the second endpoint 14816, thus 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 static images depicting the second endpoint at a first and a third position. In some embodiments, moving the second endpoint may include animate a human user interface object to translate the movement of the second endpoint on the screen.

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

[0476] These features allow character user interface objects to assume a wider range of natural and realistic postures and utilize them to indicate time. When these features are animated on screen, this allows characters to simulate movements similar to those of a human. This significantly improves user interaction and connection with the device by more accurately simulating human-like movement. It allows for subtle and dynamic movements, providing characters with a wider range of expressive qualities that help to simulate personality. Therefore, the character is no longer simply an aggregation of two character-like clock hands that merely indicate time, but becomes more like a real person capable of expressing personality, thereby enhancing the user experience with the device.

[0477] In some embodiments, the character user interface object (e.g., character user interface objects 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 may include a first segment connecting a 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 may be in a first position, and the second endpoint of the second segment may be in a second position. The joint may serve as a rotation axis for the second segment, which may indicate a third time value. The device 14000 may update the character user interface object by moving the second endpoint of the second limb along the rotation axis 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. The first and second limbs may differ in length from those of conventional clock hands, for example. The first and second limbs may be distinguished, for example, by the distance between the first and second endpoints. For example, one limb may be bent or the shoulder may be positioned such that, although the limb may not be shorter than the other limb, it appears as a shorter limb or is otherwise different from the other limb. For example, the first and second limbs may be distinguished by the distance between the second endpoint and another object on the display, such as a numerical time indication.

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

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

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

[0482] Figure 14E An exemplary user interface screen 14902 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300), etc. Figure 3 Device 14000 can display a character user interface object, such as character user interface object 14904, on the display. User interface screen 14902 demonstrates the translation of the character by sequentially displaying character user interface object 14904 at two different locations, 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 The movement shown is in a right-to-left direction. For example, when a user initiates interaction with the device or looks at the device, a movement like this can be used, which prompts a figure to move toward the center of the display and indicate the time.

[0483] In some embodiments, translating a character user interface object may include animate 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 with legs and a torso. Walking is represented by 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 user interaction with the device, the character may be animate to walk naturally onto the screen and then assume a position corresponding to the current time. User interaction may include activating the screen, raising the device to a viewing position, pressing a button on the device corresponding to activating a clock face, etc.

[0484] Figure 14F An exemplary user interface screen 15002 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300), etc. Figure 3 Device 14000 may display a human user interface object, such as human user interface object 15004, on a display. Device 14000 may change the visualization aspects of the displayed user interface screen to highlight the human user interface object. Figure 14F An exemplary embodiment of the 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, altering the visualization aspects of the display may include one or more of the following: changing the color and / or brightness of the user interface screen around the character user interface object, displaying the character user interface object such as a spotlight, etc.

[0486] In some embodiments, device 14000 can animate a character user interface object to represent the character user interface object's response to changes in visualization. For example, in Figure 14F In the exemplary embodiment shown, the character user interface object 15004 can be animated to simulate looking at the spotlight 15006.

[0487] Figure 14G An exemplary user interface screen 15102 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300) Figure 3Device 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 feet 15106. In some embodiments, character user interface object 15104 includes two limbs and two legs indicating time values, at least one of the legs may include a foot.

[0488] In some embodiments, device 14000 can animate feet to indicate the passage of time. As shown on user interface screens 15102 and 15110, character user interface objects 15104 and 15112 include feet (15106 and 15114, respectively). The different positions of feet 15106 and 15114 (different in terms of their position on the display and / or their posture within the character user interface object) depict this animation. For example, the character can be animate to simulate foot movements, such as tapping. This can have regular or irregular timing. In some embodiments, the feet are animate to move at regular intervals (e.g., once per second). When coupled with two limbs, this allows the character user interface object to depict time values ​​such as 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 move by shifting 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 circular clock face representation, where a human user interface object is positioned at the center surrounded by numerical indicators, like a clock.

[0491] The features described above make the persona user interface object appear more natural and realistic by employing a wider range of natural movements while indicating time. Users may want to see the persona user interface object's representation of other events. Allowing the persona user interface object to react to external stimuli or internal system events depicts a more interactive persona, thus portraying a more realistic personality. Enhanced persona interactivity further improves user interaction with the device by providing additional notifications that events have occurred, even if the occurrence of the event is not as obvious as in other cases. The persona user interface object can be used to provide notifications, reminders, and / or other information that users may wish to access from their personal electronic devices, but the use of the persona provides personalization for the device to provide interactions for these items. Furthermore, making the persona responsive to internal system events (e.g., calendar events, etc.) means that the persona is not strictly limited to responding to external user input. In other words, the persona appears more realistically personalized because it responds to events that are not directly driven by the user's immediate actions.

[0492] Figure 14H An exemplary user interface screen 15202 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 300), etc. Figure 3 Device 14000 may display a character user interface object, such as character user interface object 15204, on a display. Character user interface object 15204 indicates time as described above.

[0493] Device 14000 can receive initial data indicating an event. Device 14000 can determine whether the event meets certain conditions. Based on the determination that the event meets certain conditions, device 14000 can update the user interface object 15204 by changing the visual aspects of the user interface object.

[0494] In some embodiments, the character user interface object still indicates the time after the displayed character user interface object is updated. For example, the character's appearance or pose 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 limbs 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 the 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 the duration of the calendar event. Determining whether an event meets 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 person user interface object may include animate rendering of the person user interface object to display a birthday greeting. The person user interface object 15204 is animate to display a holiday hat 15206 and a birthday message 15208. This animation serves to notify the user of their birthday while simultaneously making the person more interactive. Importantly, the person can change aspects of the visualization, such as by displaying a birthday greeting without immediate user input, thus giving the impression that the person can act more autonomously, as if possessing a personality. In some embodiments, the modification of the person is an indication of some significant event (such as their birthday, anniversary, etc.) related to one of 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, the character user interface object 15212 is depicted with a Santa hat 15214. This animation serves to notify the user of the holiday while simultaneously making the character more interactive and reducing the monotony of the character's appearance. Other examples of holidays besides 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 may receive data indicating user preferences, such as the user's favorite sports teams. Based on the received data, device 14000 may update the person user interface object 15204 by changing the visual aspects of the person user interface object to reflect the sports team. For example, the appearance of the person user interface object may be updated to depict the person user interface object wearing uniforms or other equipment representing the sports team (e.g., hats, jerseys, uniforms, or other representations including logos, icons, or text representing the sports team). The display may also be updated to include a second user interface object along with the person user interface object, which represents a sports object associated with the team's sport (e.g., baseball bat and / or baseball, rugby, basketball, football, hockey stick and / or hockey, checkered flag, etc.). The person may 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 will attend an event characterized by that team. The user's attendance at an event characterized by that team may be determined by analyzing the user's calendar events or by determining that an event e-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 example of user preference, and other user preferences, such as the representation of flags or countries, are also envisioned.

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

[0501] Device 14000 can receive data indicating a notification. The notification may include, for example, emails, text messages, alerts, virtual assistance requests, or other such notifications. As depicted by notification 15306, device 14000 may further display a notification or available item or user interface object indicating receipt and / or content of the notification on user interface screen 15302. Device 14000 may animate the character user interface object 15304 in response to notification 15306. For example, as shown on user interface screen 15302, the character user interface object 15304 may appear to be looking at notification 15306. This may include, for example, a change in posture to make the character face the notification, or a change in the character's appearance, such as a face, to indicate that they are looking in the direction of the notification. Similarly, by providing this change in posture or the character's focus, the user can be notified of other incoming alerts or events that may have been less obvious.

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

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

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

[0505] Device 14000 can receive data indicating the current time. Device 14000 can determine whether the current time corresponds to an hour (e.g., 1:00, 2:00, etc.). If device 14000 determines whether the current time corresponds to an hour, a character user interface object is animated to announce 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 notes 15506. In some embodiments, the announcement of the hour may include a visual depiction of the announcement, such as by displaying a user interface object. In some embodiments, the announcement of the hour may include sounds such as whistling, buzzing, one or more read words, or bells.

[0506] Figure 14L An exemplary user interface screen 15602 that device 14000 may display on its display is shown. In some embodiments, device 14000 may be device 100 (FIG. 1), 300 (FIG. 3), etc. Figure 3 Device 14000 may display a character user interface object, such as character user interface object 15604, on a display. Character user interface object 15604 indicates the time as described above.

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

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

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

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

[0511] In some embodiments, a device (such as device 14000) displaying a person 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...

Claims

1. A method comprising: At an electronic device having a display: Detect input; as well as In response to detecting the input: A presentation showing an animation of a clock face, wherein the animation comprises: Displays hour and minute hands; and displays the first hour indication; and After the first hour indication is displayed, a second hour indication is displayed, wherein the second hour indication is displayed on the clock face at a position after the first hour indication in the clockwise direction.

2. The method according to claim 1, further comprising: After displaying the second hour indication, displaying the first minute indication; as well as A second minute indication is displayed, wherein the second minute indication is displayed on the clock face at a position subsequent to the first minute indication in a clockwise direction.

3. The method according to any one of claims 1 to 2, wherein the hour hand and the minute hand are displayed before the first hour indication.

4. The method according to any one of claims 1 to 2, further comprising: An animated presentation of an outline of the clock face is displayed, wherein the outline of the clock face is animated to be displayed progressively in a clockwise direction.

5. The method according to any one of claims 1 to 2, wherein after the animation is presented, the clock face indicates the current time.

6. The method according to any one of claims 1 to 2, further comprising: displaying an affordance as a complication on the clock face, wherein the affordance represents an application; detecting a contact on the affordance, and in response to detecting the contact: The application represented by the affordance is launched.

7. The method according to any one of claims 1 to 2, further comprising: A first color of the clock face is updated, wherein updating the first color includes continuously changing the first color of the clock face over time. The method of claim 7 , wherein the first color of the clock face is a background color of the clock face.

9. The method of claim 7, wherein the clock face includes a second hand, and wherein the first color of the clock face is the color of the second hand.

10. The method according to claim 7, further comprising: detecting a second input; as well as In response to detecting the second input: displaying a second color of the clock face, wherein the second color is different from the first color; and The second color of the clock face is updated, wherein updating the second color includes continuously changing the second color of the clock face over time.

11. The method according to any one of claims 1 to 2, further comprising: receiving data representing a name; as well as In response to receiving the data: Generate combined patterns; as well as The combined pattern is displayed as a second affordance on the clock face.

12. A computer-readable storage medium comprising one or more programs for execution by one or more processors of an electronic device having a touch-sensitive display, the one or more programs comprising instructions for: Detect input; as well as In response to detecting the input: A presentation showing an animation of a clock face, wherein the animation comprises: Displays hour and minute hands; and displays the first hour indication; and After the first hour indication is displayed, a second hour indication is displayed, wherein the second hour indication is displayed on the clock face at a position after the first hour indication in the clockwise direction.

13. The computer-readable storage medium of claim 12, wherein the one or more programs further comprise instructions for: After displaying the second hour indication, displaying the first minute indication; and A second minute indication is displayed, wherein the second minute indication is displayed on the clock face at a position subsequent to the first minute indication in a clockwise direction.

14. The computer-readable storage medium of any one of claims 12 to 13, wherein the hour hand and the minute hand are displayed before the first hour indication.

15. The computer-readable storage medium according to any one of claims 12 to 13, wherein the one or more programs further comprise instructions for: An animated presentation of an outline of the clock face is displayed, wherein the outline of the clock face is animated to be displayed progressively in a clockwise direction.

16. The computer-readable storage medium according to any one of claims 12 to 13, wherein after the animation is presented, the clock face indicates a current time.

17. The computer-readable storage medium according to any one of claims 12 to 13, wherein the one or more programs further comprise instructions for: displaying an affordance as a complication on the clock face, wherein the affordance represents an application; detecting a contact on the affordance, and in response to detecting the contact: The application represented by the affordance is launched.

18. The computer-readable storage medium according to any one of claims 12 to 13, wherein the one or more programs further include instructions for: A first color of the clock face is updated, wherein updating the first color includes continuously changing the first color of the clock face over time.

19. The computer-readable storage medium of claim 18, wherein the first color of the clock face is a background color of the clock face.

20. The computer-readable storage medium of claim 18, wherein the clock face includes a second hand, and wherein the first color of the clock face is a color of the second hand.

21. The computer-readable storage medium of claim 18, wherein the one or more programs further comprise instructions for: detecting a second input; and In response to detecting the second input: displaying a second color of the clock face, wherein the second color is different from the first color; and The second color of the clock face is updated, wherein updating the second color includes continuously changing the second color of the clock face over time.

22. The computer-readable storage medium of any one of claims 12 to 13, wherein the one or more programs further comprise instructions for: receiving data representing a name; and In response to receiving the data: generating a combined pattern; and The combined pattern is displayed as a second affordance on the clock face.

23. An electronic device, comprising: monitor; 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: Detect input; as well as In response to detecting the input: A presentation showing an animation of a clock face, wherein the animation comprises: Displays hour and minute hands; and displays the first hour indication; and After the first hour indication is displayed, a second hour indication is displayed, wherein the second hour indication is displayed on the clock face at a position after the first hour indication in the clockwise direction.

24. The electronic device of claim 23, wherein the one or more programs further comprise instructions for: After displaying the second hour indication, displaying the first minute indication; and A second minute indication is displayed, wherein the second minute indication is displayed on the clock face at a position subsequent to the first minute indication in a clockwise direction.

25. The electronic device according to any one of claims 23 to 24, wherein the hour hand and the minute hand are displayed before the first hour indication.

26. The electronic device according to any one of claims 23 to 24, wherein the one or more programs further comprise instructions for: An animated presentation of an outline of the clock face is displayed, wherein the outline of the clock face is animated to be displayed progressively in a clockwise direction.

27. The electronic device according to any one of claims 23 to 24, wherein after the animation is presented, the clock face indicates the current time.

28. The electronic device according to any one of claims 23 to 24, wherein the one or more programs further comprise instructions for: displaying an affordance as a complication on the clock face, wherein the affordance represents an application; detecting a contact on the affordance, and in response to detecting the contact: The application represented by the affordance is launched.

29. The electronic device according to any one of claims 23 to 24, wherein the one or more programs further comprise instructions for: A first color of the clock face is updated, wherein updating the first color includes continuously changing the first color of the clock face over time.

30. The electronic device of claim 29, wherein the first color of the clock face is a background color of the clock face.

31. The electronic device of claim 29, wherein the clock face includes a second hand, and wherein the first color of the clock face is the color of the second hand.

32. The electronic device of claim 29, wherein the one or more programs further comprise instructions for: detecting a second input; and In response to detecting the second input: displaying a second color of the clock face, wherein the second color is different from the first color; and The second color of the clock face is updated, wherein updating the second color includes continuously changing the second color of the clock face over time.

33. The electronic device according to any one of claims 23 to 24, wherein the one or more programs further comprise instructions for: receiving data representing a name; and In response to receiving the data: generating a combined pattern; and The combined pattern is displayed as a second affordance on the clock face.

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

35. 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 11.

Images