Context-specific user interface

Abstract

To provide a context-specific user interface for use with a portable multifunction apparatus.SOLUTION: A method comprises: detecting, at an electronic device having a display, an input corresponding to displaying a personalized user interface including an anthropomorphic character; in response to detecting the input, displaying the anthropomorphic character having a first appearance based on a first condition in accordance with determination that the input was detected while the first condition is satisfied; and displaying the anthropomorphic character having a second appearance different from the first appearance in accordance with determination that the input was detected while a second condition different from the first condition is satisfied, wherein the second appearance is based on the second condition.SELECTED DRAWING: Figure 14B

Description

[Technical Field]

[0001] [Cross-reference of related applications] This application claims priority to U.S. Provisional Patent Application No. 62 / 032,562 filed on 2 August 2014, U.S. Provisional Patent Application No. 62 / 044,994 filed on 2 September 2014, and U.S. Provisional Patent Application No. 62 / 129,835 filed on 7 March 2015. These applications are incorporated in their entirety in this application.

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

[0003] This disclosure relates in general to computer user interfaces, and more specifically to context-specific user interfaces that indicate time. [Background technology]

[0004] Users rely on portable multifunction devices, particularly for recording time, among various other operations including running software applications. It is desirable that users can access information through a single user interface while maintaining simplicity and intuitive usability. Furthermore, users may want to access various types of information, such as different aspects related to time recording or different application data points, depending on the context. Therefore, it is also desirable that users can customize the user interface and the types of information provided through it. [Overview of the project]

[0005] Portable multifunction devices can provide users with many different types of information and interfaces, and users may want to customize these user interfaces and the information they provide depending on the context. Therefore, there is a growing demand for context-specific user interfaces for recording time.

[0006] However, in most cases, some methods for managing (e.g., editing) context-specific user interfaces to indicate time using electronic devices are cumbersome and inefficient. For example, existing methods use complex and time-consuming user interfaces, sometimes involving multiple key presses or keystrokes. Existing technologies take more time than necessary, wasting both the user's time and the device's energy. The latter energy issue is particularly significant for battery-powered devices.

[0007] Accordingly, the present invention provides the advantages of portable electronic devices that have a fast and efficient method for managing context-specific user interfaces. Such methods and interfaces optionally complement or replace other methods for managing context-specific user interfaces. The methods and interfaces reduce the cognitive burden on the user and form a more efficient human-machine interface. Furthermore, by reducing the number of unnecessary, superfluous, repetitive, and / or redundant inputs and generating a faster and more efficient user interface structure, the methods and interfaces can reduce the number of inputs required, processing power, and time required to display the user interface in order to access and execute a desired function. In the case of battery-powered computing devices, the methods and interfaces conserve power and extend the time between battery charges.

[0008] The drawbacks and other problems described above are mitigated or eliminated by the disclosed apparatus, method and computer-readable medium. In some embodiments, the apparatus is a desktop computer. In some embodiments, the apparatus is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the apparatus has a touchpad. In some embodiments, the apparatus has a touch-sensitive display (also known as a “touchscreen” or “touchscreen display”). In some embodiments, the apparatus has hardware input mechanisms such as pressable buttons and / or rotatable input mechanisms. In some embodiments, the apparatus has a graphical user interface (GUI), one or more processors, memory, and one or more module programs or instruction sets stored in memory to perform multiple functions. In some embodiments, the user interacts with the GUI by touching the touch-sensitive surface and gestures and / or rotating a rotatable input mechanism and / or pressing hardware buttons. In some embodiments, the functions optionally include image editing, drawing, presentation, word processing, website creation, disk authoring, spreadsheet creation, gameplay, telephone, video conferencing, email, instant messaging, training support, digital photography, digital video recording, web browsing, digital music playback, and / or digital video playback. Executable instructions for performing these functions are optionally included in a non-temporary computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a temporary computer-readable storage medium or other computer program product configured for execution by one or more processors.

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

[0010] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display is to display a clock face indicating the current time on the touch-sensitive display, wherein the clock face comprises a user interface object having hour and minute hands, the user interface object indicating the current time, one or more time scale displays and a stopwatch hand, obtaining data representing user input, and in response to the receipt of data, replacing one or more time scale displays with a first time scale display relating to the stopwatch hand, and animating the stopwatch hand to reflect the passage of time.

[0011] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display is to display a user interface screen on the touch-sensitive display, wherein the user interface screen includes a first affordance representing a simulation of a first region of the Earth illuminated by the sun at the current time and a second affordance indicating the current time; to receive user input; and to rotate the simulation of the Earth to display a second region of the Earth illuminated by the sun at the current time in response to the receipt of user input.

[0012] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display comprises displaying a user interface screen on the touch-sensitive display, wherein the user interface screen comprises a first part of the user interface screen indicating daytime, a second part of the user interface screen indicating nighttime, a user interface object representing a sine wave having a period representing a day, the sine wave indicating the progression of the sun over the course of a day, and displayed in one or more of the first and second parts, a first affordance representing the sun, displayed at a first position on the displayed sine wave, the first position indicating the current time of day, and the current time of day being daytime or nighttime, and a second affordance indicating the current time.

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

[0014] In some embodiments, a method for providing a context-specific user interface in an electronic device having a display comprises accessing a folder containing two or more images, selecting a first image from the folder, and displaying a user interface screen on the display, wherein the user interface screen has a background comprising multiple pixels based on the first image, and the appearance of the image is modified such that a subset of pixels represents one or more of a first user interface object indicating a date and a second user interface object indicating a time zone.

[0015] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display includes detecting user input, wherein the user input is detected at a first time; displaying a user interface screen in response to the detection of the user input, which includes a first user interface object and a second user interface object indicating the first time; and animating the second user interface object, wherein the animation comprises a sequence of a first animated sequence, a second animated sequence following the first animated sequence, and a third animated sequence following the second animated sequence, wherein the first, second, and third animated sequences are different; and detecting a second user input after the animation of the second user interface object. The process includes: detecting user input 2 at a second time, the second time being after the first time; accessing data representing a previously displayed second animated sequence in response to the detection of the second user input; selecting a fourth animated sequence different from the first and second animated sequences; displaying a second user interface screen containing a first user interface object, updating the first user interface object to indicate the second time, a third user interface object relating to the second user interface object; and animating the third user interface object, wherein the animation is a sequential display of the first animated sequence, a fourth animated sequence following the first animated sequence, and a third animated sequence following the fourth animated sequence.

[0016] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display includes detecting user movement of the electronic device and displaying an animated representation of a clock face in response to the detection of user movement, wherein the animation comprises displaying hour and minute hands, displaying a first time display, and displaying a second time display after the display of the first time display, and the second time display is displayed in a position on the clock face behind the first time display in a clockwise direction.

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

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

[0019] In some embodiments, a method for indicating time in a character-based user interface, in an electronic device having a display and a touch-sensitive surface, involves displaying a character user interface object on the display, wherein the character user interface object comprises a representation of a limb, the limb includes a first segment and a second segment of the limb, 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 has a first position, 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 has a second position, the joint of the limb is the axis of rotation for the second segment of the limb, the position of the second endpoint of the limb indicates a first time value, and updating the character user interface object to indicate a second time value, wherein the updating involves moving the second endpoint of the limb to a third position along the axis of rotation of the second segment of the limb to indicate a second time value.

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

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

[0022] In some embodiments, a method for providing a context-specific user interface is an electronic device having a touch-sensitive display, comprising a watch face and affordances representing an application, wherein the affordances comprise a set of information obtained from the application, the set of information is updated according to data from the application, and the affordances are displayed on the watch face as complications, and the method comprises detecting contact with the displayed affordances and, in response to the detection of contact, launching the application represented by the affordances.

[0023] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display configured to detect contact intensity includes: displaying a user interface screen including a clock face on the touch-sensitive display; detecting contact to the touch-sensitive display, wherein the contact has a characteristic intensity; determining, in response to the detection of contact, whether the characteristic intensity exceeds an intensity threshold; in response to the determination that the characteristic intensity exceeds the intensity threshold, inputting a clock face editing mode for the electronic device; visually highlighting the displayed clock face to indicate a clock face selection mode; detecting a second contact to the touch-sensitive display, wherein the second contact is a contact to the visually highlighted clock face; and visually indicating elements of the clock face for editing in response to the detection of the second contact.

[0024] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display configured to detect contact intensity includes: displaying a user interface screen including a clock face on the touch-sensitive display; detecting contact to the touch-sensitive display, wherein the contact has a characteristic intensity; determining, in response to the detection of contact, whether the characteristic intensity exceeds an intensity threshold; inputting a clock face selection mode for the electronic device in response to the determination that the characteristic intensity exceeds the intensity threshold; indicating the clock face selection mode by visually highlighting the displayed clock face, wherein the displayed clock face is placed in the center of the display; detecting a swipe on the touch-sensitive display; and, in response to the detection of the swipe, centering a second clock face on the display.

[0025] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display and a rotatable input mechanism, comprising displaying a user interface screen including a clock face on the touch-sensitive display, wherein the affordance on the clock face indicates a first time zone; detecting contact on the touch-sensitive display; in response to the detection of contact, inputting a user interaction mode for the electronic device; detecting movement of the rotatable input mechanism while the electronic device is in user interaction mode; updating an affordance indicating a second time zone in response to the detection of movement; detecting a second contact on the touch-sensitive display with an affordance indicating the second time zone; and setting user advice for the second time zone in response to the detection of the second contact.

[0026] In some embodiments, a method for providing a context-specific user interface in an electronic device having a touch-sensitive display is to display a user interface screen on the display, wherein the user interface screen includes a plurality of affordances, the plurality of affordances include a first affordance, the first affordance indicating a clock face including a time display and an outline; to detect contact to the displayed first affordance; and in response to the detection of contact, to replace the display of the user interface screen with a second user interface screen, wherein the replacement maintains the time display and one of one or more outlines, and the maintained time display or outline is displayed on the second user interface screen in a larger size than on the first user interface screen.

[0027] In some embodiments, the apparatus comprises means for receiving data representing a user input, and means for displaying on a display a user interface screen including a clock face indicating a first time, the first time preceding the current time, and means for updating the user interface screen by animating the clock face to transition from the first time display to the current time display, the animation representing the passage of time from the first time to the current time.

[0028] In some embodiments, the apparatus comprises means for displaying a clock face on a touch-sensitive display indicating the current time, the clock face including a user interface object having an hour hand and a minute hand, the user interface object indicating the current time, one or more displays of a time scale, and a stopwatch hand, means for receiving data representing a user input, and means for, in response to the reception of the data, replacing one or more displays of the time scale with a display of a first time scale with the stopwatch hand, and means for animating the stopwatch hand to reflect the passage of time.

[0029] In some embodiments, the apparatus comprises means for displaying a user interface screen on a 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 and a second affordance representing the current time, means for receiving a user input, and means for, in response to the reception of the user input, rotating a simulation displaying a second region of the Earth illuminated by the sun at the current time.

[0030] In some embodiments, the device includes means for displaying a user interface screen on a touch-sensitive display, the user interface screen comprising: 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 progression of the sun over the course of a day, and the user interface object is displayed in one or more of the first and second portions; a first affordance representing the sun, which is displayed at a first position on the displayed sine wave, where the first position indicates the current time of day, and the current time of day is daytime or nighttime; and a second affordance indicating the current time of day.

[0031] In some embodiments, the apparatus includes means for displaying a user interface screen on a display, the user interface screen including a background comprising a plurality of pixels based on an image, and the appearance of the image is modified such that a subset of pixels represents one or more of a first user interface object indicating a date and a second user interface object indicating a time zone.

[0032] In some embodiments, the device includes means for accessing a folder containing two or more images, for selecting a first image from the folder, and for displaying a user interface screen on a display, wherein the user interface screen has a background comprising a plurality of pixels based on the first image, and the appearance of the image is modified such that a subset of pixels represents one or more of a first user interface object indicating a date and a second user interface object indicating a time zone.

[0033] In some embodiments, the device includes means for detecting user input detected at a first time; means for displaying a user interface screen in response to the detection of user input, wherein the user interface screen includes a first user interface object and a second user interface object indicating the first time; means for animating the second user interface object, wherein the animation comprises a sequential display of a first animated sequence, a second animated sequence following the first animated sequence, and a third animated sequence following the second animated sequence, wherein the first animated sequence, the second animated sequence, and the third animated sequence are different from each other; means for detecting a second user input detected at a second time after the first time; and the second user input The system includes means for accessing data representing a previously displayed second animated sequence in response to a detection; means for selecting a fourth animated sequence different from the first and second animated sequences; means for displaying a second user interface screen, wherein the second user interface screen includes a first user interface object and a third user interface object associated with the second user interface object, which are updated to indicate a second time; and means for animating the third user interface object, wherein the animation is a sequential display of the first animated sequence, a fourth animated sequence following the first animated sequence, and a third animated sequence following the fourth animated sequence.

[0034] In some embodiments, the device includes means for detecting the movement of a user of the device; means for displaying an animated representation of a clock face in response to the detection of user movement, wherein the animation includes the display of hour and minute hands and the display of a first time display; and means for displaying a second time display, wherein the second time display is displayed in a clockwise direction at a position on the clock face after the first time display.

[0035] In some embodiments, the apparatus includes means for displaying a user interface screen on a display, wherein the user interface screen includes a clock face and affordances, the affordances representing applications, the affordances comprising a set of information obtained from the applications, the set of information being updated according to data from the applications, and the affordances being displayed as complications on the clock face; means for detecting contact with the displayed affordances; and means for launching the application represented by the affordances in response to the detection of contact.

[0036] In some embodiments, the device includes means for displaying a user interface screen including a clock face on a touch-sensitive display; means for detecting contact to the touch-sensitive display, wherein the contact has a characteristic intensity; means for determining, in response to the detection of contact, whether the characteristic intensity exceeds an intensity threshold; means for inputting a clock face editing mode for the electronic device in response to the determination that the characteristic intensity exceeds an intensity threshold; means for visually highlighting the displayed clock face to indicate a clock face selection mode; means for detecting a second contact to the touch-sensitive display, wherein the second contact is a contact with the visually highlighted clock face; and means for visually indicating elements of the clock face for editing in response to the detection of the second contact.

[0037] In some embodiments, the device includes means for displaying a user interface screen including a clock face on a touch-sensitive display; means for detecting contact to the touch-sensitive display, wherein the contact has a characteristic intensity; means for determining, in response to the detection of contact, whether the characteristic intensity exceeds an intensity threshold; means for inputting a clock face editing mode for the electronic device in response to the determination that the characteristic intensity exceeds an intensity threshold; means for visually highlighting the displayed clock face to indicate a clock face selection mode, wherein the displayed clock face is placed in the center of 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 the detection of a swipe.

[0038] In some embodiments, the device includes means for displaying a user interface screen on a touch-sensitive display, wherein the user interface screen includes a clock face and an affordance indicating a first time zone on the clock face; means for detecting contact to the touch-sensitive display; means for inputting a user interaction mode for the electronic device; means for detecting movement of a rotatable input mechanism while the device is in user interaction mode; means for updating the affordance to indicate a second time zone in response to detection of movement; means for detecting a second contact to the touch-sensitive display with an affordance indicating a second time zone; and means for setting user advice for the second time zone in response to detection of the second contact.

[0039] In some embodiments, the apparatus includes means for displaying a user interface screen on a display, wherein the user interface screen includes a plurality of affordances, the plurality of affordances include a first affordance, the first affordance indicating a clock face including a time display and an outline; means for detecting contact to the displayed first affordance; and means for replacing the display of the user interface screen with a second user interface screen in response to the detection of contact, wherein the replacement includes maintaining one or more of the time display and the outline, the maintained time display or outline being displayed on the second user interface screen in a larger size than on the first user interface screen.

[0040] In some embodiments, the method comprises: an instruction to receive data relating to a first subject; an instruction to display first information relating to a first portion of the received data; an instruction to detect a first rotation of a rotatable input mechanism; and an instruction to supplement the first information with second information relating to a second portion of the received data in response to the detection of the first rotation of the rotatable input mechanism.

[0041] In some embodiments, a non-temporary computer-readable storage medium includes an instruction for receiving data relating to a first subject; an instruction for displaying first information relating to a first portion of the received data; an instruction for detecting a first rotation of a rotatable input mechanism; and an instruction for supplementing the first information with second information relating to a second portion of the received data in response to the detection of the first rotation of the rotatable input mechanism.

[0042] In some embodiments, the temporary computer-readable storage medium includes an instruction to receive data relating to a first subject; an instruction to display first information relating to a first portion of the received data; an instruction to detect a first rotation of a rotatable input mechanism; and an instruction to supplement the first information with second information relating to a second portion of the received data in response to the detection of the first rotation of the rotatable input mechanism.

[0043] In some embodiments, the device comprises a display, a rotatable input mechanism, one or more processors, and memory. In some embodiments, the memory stores, when executed by one or more processors, instructions to cause one or more processors to receive data relating to a first subject, instructions to display first information relating to a first portion of the received data, instructions to detect a first rotation of the rotatable input mechanism, and instructions to supplement the first information with second information relating to a second portion of the received data in response to the detection of the first rotation of the rotatable input mechanism.

[0044] In some embodiments, the apparatus includes means for receiving data relating to a first subject; means for displaying first information relating to a first portion of the received data; means for detecting a first rotation of a rotatable input mechanism; and means for capturing the first information with second information relating to a second portion of the received data in response to the detection of the first rotation of the rotatable input mechanism.

[0045] In some embodiments, the electronic device comprises a display unit, a rotatable input mechanism, and a processing unit connected to the display unit and the rotatable input mechanism. In some embodiments, the processing unit is configured to receive data relating to a first subject, to display first information relating to a first portion of the received data on the display unit, to detect a first rotation of the rotatable input mechanism, and in response to the detection of the first rotation of the rotatable input mechanism, to supplement the first information with second information relating to a second portion of the received data.

[0046] In some embodiments, the method comprises, in an electronic device having a display, obtaining first event data from a first application, obtaining second event data from a second application separate from the first application, determining a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and displaying a user interface on the display that includes a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0047] In some embodiments, a non-temporary computer-readable storage medium stores one or more programs, and when executed by an electronic device having a touch-sensitive display, the one or more programs include instructions to cause the device to acquire first event data from a first application, instructions to acquire second event data from a second application different from the first application, instructions to determine a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and instructions to display a user interface on the display that includes a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0048] In some embodiments, a temporary computer-readable storage medium stores one or more programs, and when executed by an electronic device having a touch-sensitive display, the one or more programs include an instruction to cause the device to acquire first event data from a first application, an instruction to acquire second event data from a second application different from the first application, an instruction to determine a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and an instruction to display a user interface on the display that includes a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0049] In some embodiments, the electronic device comprises a touch-sensitive display, one or more processors, memory, and one or more programs, the one or more programs being stored in memory and configured to be executed by one or more processors, and when the one or more programs are executed by one or more processors, the one or more programs include instructions to cause the device to obtain first event data from a first application, instructions to obtain second event data from a second application different from the first application, instructions to determine a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and instructions to display a user interface on the display that includes a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0050] In some embodiments, the electronic device includes means for obtaining first event data from a first application, means for obtaining second event data from a second application separate from the first application, means for determining a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and means for displaying a user interface on the device's touch-sensitive display that includes a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0051] In some embodiments, the electronic device comprises a display unit configured to display a graphical user interface, a touch-sensing surface unit configured to accept contact, and a processing unit connected to the display unit, the touch-sensing surface unit, a rotatable and pressable input mechanism, and a button, wherein the processing unit is configured to acquire first event data from a first application, acquire second event data from a second application separate from the first application, determine a first time value associated with the first event data, a second time value associated with the second event data, and the relative order of the first and second time values, and to display on the display a user interface including a representation of the first event data having a representation of the first time value and a representation of the second event data having 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 and second time values ​​and the values ​​of the first and second time values.

[0052] Therefore, by providing a high-speed and efficient device for managing (e.g., editing) context-specific user interfaces, effectiveness, efficiency, and user satisfaction with the device are improved. The above method and interface can complement or replace other methods for managing context-specific user interfaces. [Brief explanation of the drawing]

[0053] [Figure 1A] This is a block diagram showing a portable multifunctional device equipped with a touch-sensitive display according to several embodiments.

[0054] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0055] [Figure 2] This figure shows a portable multifunctional device having a touch-sensitive display according to several embodiments.

[0056] [Figure 3] This is a block diagram of an exemplary multifunctional device comprising a display and a touch-sensing surface according to several embodiments.

[0057] [Figure 4A] This figure shows an exemplary user interface for an application menu of a portable multifunction device according to several embodiments. [Figure 4B] This figure shows an exemplary user interface for an application menu of a portable multifunction device according to several embodiments.

[0058] [Figure 5A] This is a block diagram showing a portable multifunctional device comprising a touch-sensitive display and a rotatable and pressable input mechanism according to several embodiments.

[0059] [Figure 5B] This is a block diagram showing a portable multifunctional device comprising a touch-sensitive display and a rotatable and pressable input mechanism according to several embodiments.

[0060] [Figure 6A] This diagram illustrates an exemplary context-specific user interface. [Figure 6B] This diagram illustrates an exemplary context-specific user interface.

[0061] [Figure 7A] This diagram illustrates an exemplary context-specific user interface. [Figure 7B] This diagram illustrates an exemplary context-specific user interface.

[0062] [Figure 8] This diagram illustrates an exemplary context-specific user interface.

[0063] [Figure 9] This diagram illustrates an exemplary context-specific user interface.

[0064] [Figure 10] This diagram illustrates an exemplary context-specific user interface.

[0065] [Figure 11A] This diagram illustrates an exemplary context-specific user interface. [Figure 11B] This diagram illustrates an exemplary context-specific user interface. [Figure 11C] This diagram illustrates an exemplary context-specific user interface.

[0066] [Figure 12] This diagram illustrates an exemplary context-specific user interface.

[0067] [Figure 13A] This diagram illustrates an exemplary context-specific user interface. [Figure 13B] This diagram illustrates an exemplary context-specific user interface.

[0068] [Figure 14A] This diagram illustrates an exemplary context-specific user interface.

[0069] [Figure 14B] This diagram illustrates an exemplary context-specific user interface. [Figure 14C] This diagram illustrates an exemplary context-specific user interface. [Figure 14D] This diagram illustrates an exemplary context-specific user interface. [Figure 14E] This diagram illustrates an exemplary context-specific user interface. [Figure 14F] This diagram illustrates an exemplary context-specific user interface. [Figure 14G] This diagram illustrates an exemplary context-specific user interface. [Figure 14H] This diagram illustrates an exemplary context-specific user interface. [Figure 14I] This diagram illustrates an exemplary context-specific user interface. [Figure 14J] This diagram illustrates an exemplary context-specific user interface. [Figure 14K] This diagram illustrates an exemplary context-specific user interface. [Figure 14L] This diagram illustrates an exemplary context-specific user interface. [Figure 14M] This diagram illustrates an exemplary context-specific user interface. [Figure 14N] This diagram illustrates an exemplary context-specific user interface. [Figure 14O] This diagram illustrates an exemplary context-specific user interface. [Figure 14P] This diagram illustrates an exemplary context-specific user interface. [Figure 14Q] This diagram illustrates an exemplary context-specific user interface. [Figure 14R] This diagram illustrates an exemplary context-specific user interface. [Figure 14S] This diagram illustrates an exemplary context-specific user interface. [Figure 14T] This diagram illustrates an exemplary context-specific user interface. [Figure 14U] This diagram illustrates an exemplary context-specific user interface.

[0070] [Figure 15] This diagram illustrates an exemplary context-specific user interface.

[0071] [Figure 16A] This diagram illustrates an exemplary context-specific user interface. [Figure 16B] This diagram illustrates an exemplary context-specific user interface. [Figure 16C] This diagram illustrates an exemplary context-specific user interface. [Figure 16D] This diagram illustrates an exemplary context-specific user interface. [Figure 16E] This diagram illustrates an exemplary context-specific user interface. [Figure 16F] This diagram illustrates an exemplary context-specific user interface. [Figure 16G] This diagram illustrates an exemplary context-specific user interface.

[0072] [Figure 17A]This diagram illustrates an exemplary context-specific user interface. [Figure 17B] This diagram illustrates an exemplary context-specific user interface.

[0073] [Figure 18A] This diagram illustrates an exemplary context-specific user interface. [Figure 18B] This diagram illustrates an exemplary context-specific user interface. [Figure 18C] This diagram illustrates an exemplary context-specific user interface.

[0074] [Figure 19] This diagram illustrates an exemplary context-specific user interface.

[0075] [Figure 20] This is a flowchart illustrating the processing of a context-specific user interface.

[0076] [Figure 21] This is a flowchart illustrating the processing of a context-specific user interface.

[0077] [Figure 22] This is a flowchart illustrating the processing of a context-specific user interface.

[0078] [Figure 23] This is a flowchart illustrating the processing of a context-specific user interface.

[0079] [Figure 24] This is a flowchart illustrating the processing of a context-specific user interface.

[0080] [Figure 25] This is a flowchart illustrating the processing of a context-specific user interface.

[0081] [Figure 26] This is a flowchart illustrating the processing of a context-specific user interface.

[0082] [Figure 27A] This is a flowchart illustrating the processing of a context-specific user interface.

[0083] [Figure 27B] This is a flowchart illustrating the processing of a context-specific user interface.

[0084] [Figure 27C] This is a flowchart illustrating the processing of a context-specific user interface.

[0085] [Figure 27D] This is a flowchart illustrating the processing of a context-specific user interface.

[0086] [Figure 27E] This is a flowchart illustrating the processing of a context-specific user interface.

[0087] [Figure 27F] This is a flowchart illustrating the processing of a context-specific user interface.

[0088] [Figure 28] This is a flowchart illustrating the processing of a context-specific user interface.

[0089] [Figure 29] This is a flowchart illustrating the processing of a context-specific user interface.

[0090] [Figure 30] This is a flowchart illustrating the processing of a context-specific user interface.

[0091] [Figure 31] This is a flowchart illustrating the processing of a context-specific user interface.

[0092] [Figure 32] This is a flowchart illustrating the processing of a context-specific user interface.

[0093] [Figure 33] This is a flowchart illustrating the processing of a context-specific user interface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0113] [Figure 53A] This figure shows an exemplary user interface according to several embodiments. [Figure 53B] This figure shows an exemplary user interface according to several embodiments. [Figure 53C] This figure shows an exemplary user interface according to several embodiments. [Figure 53D] This figure shows an exemplary user interface according to several embodiments. [Figure 53E] This figure shows an exemplary user interface according to several embodiments. [Figure 53F] This figure shows an exemplary user interface according to several embodiments.

[0114] [Figure 54A] This flowchart illustrates how to activate several operating modes according to different embodiments. [Figure 54B] This flowchart illustrates how to activate several operating modes according to different embodiments. [Figure 54C] This flowchart illustrates how to activate several operating modes according to different embodiments. [Figure 54D] This flowchart illustrates how to activate several operating modes according to different embodiments. [Figure 54E] This flowchart illustrates how to activate several operating modes according to different embodiments.

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

[0116] [Figure 56A] This diagram illustrates an exemplary context-specific user interface. [Figure 56B] This diagram illustrates an exemplary context-specific user interface. [Figure 56C] This diagram illustrates an exemplary context-specific user interface. [Figure 56D] This diagram illustrates an exemplary context-specific user interface. [Figure 56E] This diagram illustrates an exemplary context-specific user interface. [Figure 56F] This diagram illustrates an exemplary context-specific user interface. [Figure 56G] This diagram illustrates an exemplary context-specific user interface. [Figure 56H] This diagram illustrates an exemplary context-specific user interface. [Figure 56I] This diagram illustrates an exemplary context-specific user interface.

[0117] [Figure 57A] This is a flowchart illustrating the processing of a context-specific user interface.

[0118] [Figure 57B] This is a flowchart illustrating the processing of a context-specific user interface.

[0119] [Figure 57C] This is a flowchart illustrating the processing of a context-specific user interface.

[0120] [Figure 57D] This is a flowchart illustrating the processing of a context-specific user interface.

[0121] [Figure 57E] This is a flowchart illustrating the processing of a context-specific user interface.

[0122] [Figure 57F]This is a flowchart illustrating the processing of a context-specific user interface.

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

[0124] [Figure 59A] This figure shows an exemplary user interface according to several embodiments. [Figure 59B] This figure shows an exemplary user interface according to several embodiments. [Figure 59C] This figure shows an exemplary user interface according to several embodiments. [Figure 59D] This figure shows an exemplary user interface according to several embodiments. [Figure 59E] This figure shows an exemplary user interface according to several embodiments. [Figure 59F] This figure shows an exemplary user interface according to several embodiments.

[0125] [Figure 60A] This flowchart illustrates a process for supplementing displayed information, according to several embodiments. [Figure 60B] This flowchart illustrates a process for supplementing displayed information, according to several embodiments. [Figure 60C] This flowchart illustrates a process for supplementing displayed information, according to several embodiments. [Figure 60D] This flowchart illustrates a process for supplementing displayed information, according to several embodiments. [Figure 60E] This flowchart illustrates a process for supplementing displayed information, according to several embodiments. [Figure 60F] This flowchart illustrates a process for supplementing displayed information, according to several embodiments.

[0126] [Figure 61] This is a functional block diagram of an electronic device according to several embodiments. [Modes for carrying out the invention]

[0127] The following description outlines exemplary methods and parameters. However, it should be understood that the above description is not intended to limit the scope of the disclosure and is provided solely as a description of exemplary embodiments.

[0128] As mentioned above, users can customize a context-specific user interface to record time and receive specific types of information. Providing a highly useful interface while offering users numerous options for customizing it is challenging. Furthermore, presenting options for customizing numerous variable elements such as color, display density, and complications in a user-friendly and intuitive manner is also difficult. A context-specific user interface and an integrated method for allowing users to customize it are highly desirable for portable multifunction devices.

[0129] The following describes an exemplary apparatus for implementing a method for providing a context-specific user interface, with reference to Figures 1A, 1B, 2, 3, 4A, 4B, and 5A and 5B. Figures 6 to 19 show exemplary context-specific user interfaces. The processes described later, such as those shown in Figures 20 to 33, will be explained using the user interfaces in these figures.

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

[0131] The language used in the descriptions of the various embodiments described herein is for the purpose of describing specific embodiments and is not intended to be limiting. Where used in the various embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural form unless otherwise specified in the context. Where used herein, the phrase "and / or" is understood to refer to and encompass all possible combinations of one or more of the associated listed items. Furthermore, where used herein, the phrases "includes," "comprises," and / or "comprising" indicate the presence of the described features, integers, processes, operations, elements, and / or components, but are understood not to exclude the presence or addition of one or more other features, integers, processes, operations, elements, components, and / or groups thereof.

[0132] The word "if" can be interpreted, depending on the context, as meaning "when," "at a time," "in response to a determination," or "in response to detection." Similarly, the clauses "if determined" or "[the condition or event described] is detected" can be interpreted, depending on the context, as meaning "at the time of determination," "in response to determination," "[the condition or event described] is detected," or "[the condition or event described] is detected."

[0133] Embodiments of electronic devices, user interfaces for such devices, and related processes using such devices are described. In some embodiments, the device is a portable communication device such as a mobile phone, which also includes other functions such as a PDA and / or music player function. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices manufactured by Apple Inc. of Cupertino, California. Other portable electronic devices such as laptop computers or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad) are also optionally used. Furthermore, in some embodiments, the device should be understood not as a portable communication device, but as a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

[0134] The following description refers to electronic devices including displays and touch-sensitive surfaces. However, it should be understood that electronic devices optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0135] The device can support one or more of the following applications: drawing applications, presentation applications, word processing applications, website creation applications, disk authoring 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 camera applications, web browsing applications, digital music player applications, and / or digital video playback device applications.

[0136] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and related information displayed on the device are optionally adjusted and / or modified from one application to the next and / or within the corresponding application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with an intuitive and user-friendly interface.

[0137] Next, we will focus on embodiments of portable devices equipped with touch-sensitive displays. Figure 1A is a block diagram of a portable multifunction device 100 equipped with a touch-sensitive display system 112 according to several embodiments. The touch-sensitive display 112 may be conveniently referred to as a "touchscreen" and may be known or referred to as a "touch-sensitive display system". The device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact intensity sensors 165 for detecting contact intensity on the device 100 (for example, on a touch-sensitive surface such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output (for example, tactile output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). Optionally, these components communicate over one or more communication buses or signal lines 103.

[0138] Where used in the specification and claims, the term “contact strength” on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact (e.g., finger contact) on the touch-sensitive surface, or an alternative (substitute) for the force or pressure of contact on the touch-sensitive surface. Contact strength has a range of values ​​including at least four distinct values, and more typically includes hundreds of different values ​​(e.g., at least 256). Optionally, contact strength is determined (or measured) using various approaches and various sensors or combinations of sensors. For example, optionally, force is measured at various points on the touch-sensitive surface using one or more force sensors below or near the touch-sensitive surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact strength. Similarly, optionally, the pressure-sensitive tip of a stylus is used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, optionally, the size and / or modification of the contact area detected on the touch-sensitive surface, the capacity and / or modification of the adjacent touch-sensitive surface, and / or the resistance and / or modification of the adjacent touch-sensitive surface are used instead of the force or pressure of contact to the touch-sensitive surface. In some embodiments, the alternative measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is stated in units corresponding to the alternative measurement). In some embodiments, the alternative measurement of contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in pressure units). By using contact intensity as a characteristic of user input, the user can access additional device functions on a small device with a limited area that would otherwise be inaccessible to the user, in order to display affordances (e.g., on a touch-sensitive display) and / or to receive user input (e.g., via a physical / mechanical control device such as a touch-sensitive display, touch-sensitive surface, or knob or button).

[0139] Where used in the specification and claims, the term “tactile output” refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of gravity of the device as detected by a tactile user. For example, if the device or a component of the device is in contact with a touch-sensitive user surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or a component of the device. For example, optionally, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may experience a tactile sensation such as a “down-click” or “up-click” even if there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movement. As another example, optionally, movement of a touch-sensitive surface may be interpreted or perceived by the user as a "relief" of the touch-sensitive surface, even if there is no change in the surface's smoothness. Such user-perception of touch is influenced by the user's individual sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described to correspond to a user's specific sensory perception (e.g., "up-click," "down-click," "relief"), unless otherwise specified, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception for a typical (or average) user.

[0140] Device 100 is merely an example of a portable multifunction device, and it should be recognized that device 100 may optionally include more or fewer components than those shown, may optionally combine two or more components, or may optionally include different structures or configurations of components. The various components shown in Figure 1A are implemented in one or more signal processing and / or application-specific integrated circuits, hardware, software, or a combination of hardware and software.

[0141] Memory 102 may include one or more computer-readable storage media. The computer-readable storage media may be tangible and non-temporary. Memory 102 includes high-speed random-access memory and may further include one or more non-volatile memories such as magnetic storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory controller 122 can control access to memory 102 by other components of device 100.

[0142] The peripheral device interface 118 can be used to connect the device's input / output peripherals to the CPU 120 and memory 102. One or more processors 120 can execute various functions of the device 100 and process data by executing various software programs and / or instruction sets stored in memory 102. In some embodiments, the peripheral device interface 118, CPU 120, and memory controller 122 can be implemented on a single chip such as chip 104. In some other embodiments, they can be implemented on separate chips.

[0143] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals and electromagnetic signals to electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits that perform 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, subscriber identification module (SIM) cards, memory, etc. Optionally, the RF circuit 108 communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and other devices. The RF circuit 108 optionally includes well-known circuits, such as those used to detect a near-field communication (NFC) field by a short-range radio.Optionally, wireless communication uses one of several communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDpa), High-Speed ​​Uplink Packet Access (HSUpa), Evolution, Data Only (EV-DO), HSpa, HSpa+, and Dual-Cell. HSpa (DC-HSPDA), Long-Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth®, Bluetooth Low Energy (bTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, Protocol for Email (e.g., Internet This includes, but is not limited to, other suitable communication protocols, including the Immediate Message Access Protocol (IMAP) and / or Post Office Protocol (POP), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Event Package (SIMPLE), Instant Messaging and Presence Event Package (IMPS)), and / or Short Message Service (SMS), or communication protocols not yet developed as of the filing date of this document.

[0144] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into audible sound waves. The audio circuit 110 also receives the electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data for processing and transmits the audio data to the peripheral interface 118. The audio data can be retrieved from memory 102 and / or RF circuit 108 by the peripheral interface 118 and / or transmitted to memory 102 and / or RF circuit 108. In some embodiments, the audio circuit 110 further includes a headset jack (e.g., 212, Figure 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral device, such as an output-only headphone or a headset having both an output (e.g., a single-ear or dual-ear headphone) and an input (e.g., a microphone).

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

[0146] As described in U.S. Patent Application No. 11 / 322,549, U.S. Patent No. 7,657,849, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed December 23, 2005, a quick press of a push button can be used to unlock the touchscreen 112, or a gesture on the touchscreen can be used to initiate the process of unlocking the device, the above application being incorporated in its entirety. A long press of a push button (e.g., 206) can be used to turn the device 100 on and off. The user can customize the function of any one or more buttons. The touchscreen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

[0147] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives and / or transmits electrical signals to and from the touchscreen 112. The touchscreen 112 displays visual output to the user. Visual output may include images, characters, icons, videos, and combinations thereof (collectively referred to as “images”). In some embodiments, some or all of the visual output may correspond to user interface objects.

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

[0149] The touchscreen 112 may use LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies may be used in other embodiments. The touchscreen 112 and the display controller 156 can detect contact and its movement or interruption using any of several currently known or future-developed touch sensing technologies, including but not limited to capacitive, resistive, infrared and surface acoustic wave technologies, and other proximity sensor arrays or other elements for determining one or more contact points with the touchscreen 112. In one exemplary embodiment, projected mutual capacitive sensing technology, as seen in the iPhone® and iPod Touch® manufactured by Apple Inc. in Cupertino, California, is used.

[0150] The touch-sensitive displays in some embodiments of the touchscreen 112 may be similar to the multi-touch-sensitive touchpads described in U.S. Patent No. 6,323,846 (Westerman et al.), No. 6,570,557 (Westerman et al.) and / or No. 6,677,932 (Westerman) and / or U.S. Patent Application Publication No. 2002 / 0015024(A1). Each of these applications is incorporated in whole into this application. However, the touchscreen 112 displays visual output from the device 100, whereas the touch-sensitive touchpad does not provide visual output.

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

[0152] The touchscreen 112 may have a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user can touch the touchscreen 112 using any suitable object or attachment such as a stylus or finger. In some embodiments, the user interface is designed to function primarily with finger touch and gestures, in which case it may not be as precise as stylus-based input due to the large contact area of ​​the finger on the touchscreen. In some embodiments, the device converts coarse finger input into a precise pointer / cursor position or command in order to perform a desired action by the user.

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

[0154] The device 100 further includes a power system 162 that supplies power to 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 fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0155] The device 100 may also include one or more optical sensors 164. Figure 1A shows an optical sensor connected to an optical sensor controller 158 of the I / O subsystem 106. The optical sensor 164 may include a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses and converts that light into data representing an image. In conjunction with the imaging module 143 (also referred to as the camera module), the optical sensor 164 acquires still images or video. In some embodiments, the optical sensor is located on the back side of the device 100, opposite the front-side touchscreen display 112 of the device, so that the touchscreen display can be used as a viewfinder for acquiring still images and / or video. In some embodiments, the optical sensor is located on the front side of the device so that an image of the user can be acquired for video conferencing while viewing other video conference participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (for example, by rotating the lens and sensor within the device housing) so that the optical sensor 164 can be used as a standalone optical sensor with a touchscreen display for video conferencing and for acquiring still images and / or video.

[0156] The device 100 optionally further includes one or more contact strength sensors 165. Figure 1A shows a contact strength sensor connected to a strength sensor controller 159 of the I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, pressure-power sensors, optical force sensors, capacitive touch-sensing surfaces, or other strength sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch-sensing surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact strength sensor is connected to or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112). In some embodiments, at least one contact strength sensor is located on the back side of the device 100, opposite the touchscreen display 112 located on the front side of the device 100.

[0157] The device 100 may further include one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 connected to a peripheral device interface 118. Alternatively, the proximity sensor 166 may be connected to an input controller 160 of the I / O subsystem 106. The proximity sensor 166 can be implemented as described in U.S. Patent Application No. 11 / 241,839, “Proximity Detector In Handheld Device”, No. 11 / 240,788, “Proximity Detector In Handheld Device”, No. 11 / 620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”, No. 11 / 586,862, “Automated Response Of User Activity In Portable Devices”, and No. 11 / 638,251, “Methods And Systems For Automatic Configuration Of Peripherals”, all of which are incorporated herein by reference. In some embodiments, when the multifunction device is located near the user's ear (for example, when the user is making a phone call), the proximity sensor turns off and disables the touchscreen 112.

[0158] The device 100 optionally further includes one or more tactile output generators 167. Figure 1A shows a tactile output generator connected to a tactile feedback controller 161 of the I / O subsystem 106. The tactile output generators 167 optionally include one or more speakers or audio components and / or electromechanical devices such as electroacoustic devices that convert energy into linear motion, e.g., motors, solenoids, electrically active polymers, piezoelectric actuators, electrostatic actuators, or other components that generate tactile outputs (e.g., components that convert electrical signals into tactile outputs on the device). A contact intensity sensor 165 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on the device 100 that can be detected by a user of the device 100. In some embodiments, at least one tactile output generator is connected to or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., in and out of the surface of the device 100) or horizontally (e.g., back and forth in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generating sensor is located on the back side of the device 100, opposite the touchscreen display 112 which is located on the front side of the device 100.

[0159] The device 100 may further include one or more accelerometers 168. Figure 1A shows an accelerometer 168 connected to a peripheral device interface 118. Alternatively, the accelerometer 168 may be connected to an input controller 160 of the I / O subsystem 106. The accelerometer 168 can be operated as described in U.S. Patent Application Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Application Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated in their entirety. In some embodiments, information is displayed on a touchscreen display in person view or landscape view based on an analysis of data received from one or more accelerometers. The device 100 optionally includes, in addition to the accelerometer 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) to acquire information about the location and orientation of the device 100 (for example, a person or a landscape).

[0160] 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, in some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) stores device / global internal state 157 as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: active application state, indicating which applications are currently active, if any; display state, indicating which applications, views, or other information occupy various areas of the touchscreen display 112; sensor state, indicating information obtained from the device's various sensors and input control devices 116; and location information, relating to the device's location and / or orientation.

[0161] Operating Systems 126 (e.g., Darwin, RTXC, LINUX) (trademark) Unix (trademark) OS X, iOS, Windows (Registered trademark) Or VxWorks (trademark) Embedded operating systems (such as) include various software components and / or drivers that control and manage common system tasks (e.g., memory management, storage device control, power management, etc.), and simplify communication between various hardware and software components.

[0162] The communication module 128 further includes various software components that simplify communication with other devices via one or more external ports 124 and handle data received by the RF circuit 108 and / or external ports 124. (External ports 124 (e.g., Universal Serial Bus (USB), FireWire) (Registered trademark)These can be adapted for direct connection to other devices or indirect connection via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is identical, similar to, and / or compatible with the 30-pin connector used in iPod® (a trademark of Apple Inc.) devices.

[0163] 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 that perform various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the contact strength (e.g., the force or pressure of the contact or an alternative to the force or pressure of the contact), determining the movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether contact has been terminated (e.g., detecting a finger up event or interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by a series of contact data optionally includes determining the velocity (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions can be optionally applied to a single contact (e.g., one finger touch) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger touches). In some embodiments, the contact / motion module 130 and the display controller 156 detect touch on the touchpad.

[0164] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action was performed by a user (for example, whether a user "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds is determined according to software parameters (for example, the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without changing the physical hardware of the device 100). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to any value within a wide range of defined thresholds without changing the trackpad or touchscreen display hardware. Also in some embodiments, the user of the device is provided with software settings to adjust one or more of the intensity threshold sets (for example, by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-level click "intensity" parameter).

[0165] The contact / motion module 130 selectively detects gestures input by the user. Different gestures on the touch-sensitive surface result in different contact patterns (e.g., different actions, timing, and / or detected contact strengths). Therefore, gestures are selectively detected by detecting specific contact patterns. For example, detecting a finger tap gesture involves detecting a finger up (lift) event at the same (or nearly the same) location as a finger down event (e.g., the position of an icon). Another example is detecting a finger swipe gesture on the touch-sensitive surface, which involves detecting a finger down event, followed by the detection of one or more subsequent finger drag events and subsequent finger up (lift-off) events.

[0166] The graphics module 132 includes various known software components for rendering and displaying images on the touchscreen 112 or other display, including components that modify the visual effects of the displayed image (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used in this document, the term "image" includes, without limitation, objects that can be displayed to the user, such as text, web pages, icons (e.g., user interface objects including soft keys), digital images, videos, animations, etc.

[0167] In some embodiments, the graphics module 132 stores data representing the image to be used. Each image is optionally assigned a corresponding code. After receiving one or more codes from an application or the like that specify the image to be displayed, along with coordinate data and other image characteristic data as needed, the graphics module 132 generates screen image data and outputs it to the display controller 156.

[0168] The haptic feedback module 133 is used by a haptic output generator 167 that generates haptic outputs at one or more locations on the device 100 in response to user interaction with the device 100, and includes various software components for generating commands.

[0169] The text input module 134 may be a component of the graphics module 132 and provides a soft keyboard for inputting characters into various applications (for example, contacts 137, email 140, IM 141, browser 147, and any other applications that require character input).

[0170] The GPS module 135 determines the location of the device and provides this information for use in various applications (for example, to a telephone 138 used for location-based dial-up, to a camera 143 as photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0171] Application 136 may include the following modules (or instruction sets), or subsets or supersets thereof: ● Contact Module 137 (sometimes called the address book or contact list) ● Telecommunications module 138 ● Video conferencing module 139 ● Email client module 140 ● Instant messaging (IM) module 141 ●Training support module 142 ● Camera module 143 for still images and / or video. ●Image management module 144 ●Video playback device module ● Music player module ● Browser Module 147 ● Calendar Module 148 ● A widget module 149 that 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. ● Widget creator module 150 for creating user-created widget 149-6 ● Search Module 151 ●Video and music player module 152 that integrates a video playback module and a music player module. ●Memo Module 153 ●Map module 154 and / or ● Online video module 155

[0172] Other applications 136 that can be stored in memory 102 include, for example, other word processing applications, other image editing applications, drawing applications, presentation applications, and JAVA. (Registered trademark) Supported applications include encryption, digital rights management, speech recognition, and speech reproduction.

[0173] In conjunction with the touchscreen 112, display controller 156, contact / 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 (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), and can, for example, add names to the address book, remove names from the address book, associate names with phone numbers, email addresses, physical addresses or other information, associate names with images, categorize and sort names, and provide phone numbers or email addresses to initiate and / or simplify communication via telephone 138, video conferencing module 139, email 140 or IM 141, etc.

[0174] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the telecommunications module 138 can be used to input a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the contact module 137, modify the entered telephone number, dial the corresponding telephone number, conduct a conversation, and interrupt or disconnect the call when the conversation is finished. As described above, wireless communication may use any of multiple communication standards, protocols, and technologies.

[0175] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telecommunications module 138, the video conferencing module 139 includes executable commands to start, run, and end a video conference between the user and one or more other participants in response to user commands.

[0176] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the email client module 140 includes executable commands for creating, receiving, and managing emails in response to user commands. In conjunction with the image management module 144, the email client module 140 simplifies the creation and sending of emails accompanied by still images or videos captured by the camera module 143.

[0177] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions for modifying a sequence of input strings corresponding to an instant message, sending the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for telephone-based instant messaging or XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages may include images, photographs, audio files, video files, and / or other attachments supported by MMS and / or Enhanced Messaging Services (EMS). As used herein, “instant messaging” refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0178] In conjunction with the RF circuit 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 commands for creating exercise training (e.g., having time, distance, and / or calorie burn targets), communicating with exercise training sensors (sports equipment), receiving exercise training sensor data, calibrating sensors used to monitor exercise training, selecting and playing music for exercise training, and displaying, storing, and transmitting exercise training data.

[0179] In conjunction with the touchscreen 112, display controller 156, optical sensor 164, light sensor controller 158, contact / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable commands for capturing still images or videos (including video footage of limbs), storing them in memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from memory 102.

[0180] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable commands for arranging, modifying (e.g., editing), otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or videos.

[0181] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the browser module 147 includes executable commands for browsing the internet in response to user commands, including searching, linking, receiving, and displaying web pages or parts thereof, as well as attachments and other files linked to web pages.

[0182] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable commands that create, display, modify, and store a calendar and data associated with the calendar (e.g., calendar entries, task lists, etc.) in response to user commands.

[0183] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, the widget module 149 is a mini-application that can be downloaded and used by the 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 mini-application that can be created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widget).

[0184] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 allows the user to create widgets (for example, by converting a user-specified portion of a web page into a widget).

[0185] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the search module 151 includes executable instructions that, in response to user commands, search for characters, music, sounds, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specific search terms).

[0186] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music player module 152 includes executable commands that cause the user to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable commands that cause video to be displayed, presented, or otherwise played (for example, on the touchscreen 112 or on an externally connected display via the external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

[0187] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the memo module 153 includes executable commands for creating and managing memos, task lists, etc., in response to user commands.

[0188] In conjunction with the RF circuit 108, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 can be used to receive, display, modify, and store maps and map-associated data (e.g., discharge direction, data on stores and locations in a specific place or its vicinity, and other location-based data) in response to user commands.

[0189] In conjunction with the touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes commands that cause the user to access, browse, receive (e.g., by streaming and / or downloading), transmit (e.g., on an externally connected display via the touchscreen or external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Online video applications are further described in U.S. Patent Provisional Application No. 60 / 936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed on 20 June 2007, and U.S. Patent Application No. 11 / 968,067, “Portable Multifunction Device, Method, Graphical User Interface for Playing Online Videos,” filed on 31 December 2007, the contents of which are incorporated herein by reference in their entirety.

[0190] Each of the above modules and applications corresponds to a set of executable instructions that perform one or more of the above-described functions and methods of the Application (e.g., methods performed by a computer and other information processing methods described herein). These modules (e.g., instruction sets) do not need to be implemented as separate software programs, procedures, or modules, and various subsets of these modules can be combined or otherwise reconfigured in various embodiments. For example, a video playback device module and a music player module can be combined into a single module (e.g., a video and music player module 152, Figure 1A). In some embodiments, memory 102 can store a subset of the above-described modules and data structures. Furthermore, memory 102 can also store additional modules and data structures not described above.

[0191] In some embodiments, the device 100 is a device in which the operation of a predetermined set of functions on the device is performed exclusively via a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for the operation of the device 100, the number of physical input control devices (push buttons, dials, etc.) on the device 100 can be reduced.

[0192] A predetermined set of functions, exclusively performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, when a user touches the touchpad, the touchpad navigates the device 100 from any user interface displayed on the device 100 to the main, home, or root menu. In such embodiments, a “menu button” is implemented using the touchpad. In some other embodiments, the menu button is not a touchpad but a physical push button or other physical input control device.

[0193] Figure 1B is a block diagram showing components for exemplary event handling according to several embodiments. In some embodiments, memory 102 (Figure 1A) or 370 (Figure 3) includes either an event sorter 170 (e.g., within the operating system 126) and the respective applications 136-1 (e.g., the aforementioned applications 137-151, 155, 380-390).

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

[0195] In some embodiments, the application internal state 192 includes one or more of the following application information: resume information used when application 136-1 resumes execution; user interface state information indicating information displayed or ready to be displayed by application 136-1; a state queue for allowing the user to return to a previous state or view of application 136-1; and a redo / undo queue for previous actions performed by the user.

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

[0197] In some embodiments, the event monitor 171 transmits requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there is a significant event (e.g., an input exceeding a predetermined noise threshold and / or received for a predetermined period of time).

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

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

[0200] Other aspects of the user interface related to an application are a set of views in which information is displayed and touch-based gestures occur, which in this specification is sometimes referred to as an application view or a user interface window. The application view in which a touch is detected (for each application) may correspond to a program level within the program hierarchy or view hierarchy of the application. For example, the bottommost view in which a touch is detected may optionally be called the "hit view", and a set of events recognized as appropriate input may be determined based at least on the hit view of the first touch that initiates a touch-based gesture.

[0201] The hit view determination module 172 receives information regarding sub-events of a touch-based gesture. When an application has a plurality of hierarchically organized views, the hit view determination module 172 identifies a hit view as the bottommost view within the hierarchy in which the sub-events are to be processed. In most situations, the hit view is the bottommost view in which a start sub-event (e.g., the first sub-event within a series of sub-events that form an event or potential event) occurs. Typically, once the hit view is identified by the hit view determination module 172, it will receive all sub-events related to the same touch or input source that caused it to be identified as the hit view.

[0202] The active event recognition determination module 173 determines which views in the view hierarchy should receive a particular sub-event sequence. In some embodiments, the active event recognition determination module 173 determines that only the hit view should receive a particular sub-event sequence. In other embodiments, the active event recognition determination module 173 determines that all views, including the physical location of the sub-event, are actively involved views, and all actively involved views should receive a particular sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to an area associated with one particular view, higher-level views in the hierarchy remain actively involved views.

[0203] The event dispatcher module 174 dispatches event information to an event recognition unit (for example, an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes this event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information acquired by each event receiving unit 182 in an event queue.

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

[0205] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within each view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more event recognition units 180 are part of separate modules, such as an interface kit (not shown) or part of a higher-level object from which application 136-1 inherits methods or other properties. In some embodiments, each event handler 190 includes one or more event data 179 received from a data update unit 176, an object update unit 177, a GUI update unit 178, and / or an event sorter 170. The event handler 190 may optionally utilize or call the data update unit 176, the object update unit 177, or the GUI update unit 178 to update the application's internal state 192. Alternatively, one or more application views 191 include one or more respective event handlers 190. Furthermore, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included within each application view 191.

[0206] Each event recognition unit 180 receives event information (e.g., event data 179) from the event sorter 170 and identifies an event from this event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparison unit 184. In some embodiments, the event recognition unit 180 further includes at least one subset of metadata 183 and event transmission instructions 188 (optionally including sub-event transmission instructions).

[0207] The event receiver 182 receives event information from the event sorter 170. The event information includes information about sub-events (e.g., touches or movement of touches). Depending on the sub-event, the event information may further include additional information such as the location of the sub-event. If the sub-event relates to the movement of a touch, the event information may further include the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes information about the corresponding current orientation of the device (also called the device orientation).

[0208] The event comparison unit 184 compares event information with a predetermined event or sub-event definition and, based on this comparison, determines an event or sub-event or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 holds an event definition (e.g., a predetermined sub-event sequence), e.g., event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events within event (187) include, for example, touch start, touch end, touch move, touch cancel, and multiple touches. In one embodiment, the definition of event 1 (187-1) is a double tap on a displayed object. A double tap comprises, for example, a first touch (touch start) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch start) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In other embodiments, the definition of event 2 (187-2) is a drag on a displayed object. A drag includes, for example, touching (or contacting) a displayed object for a predetermined phase, moving the touch across the touch-sensitive display 112, and lifting off the touch (ending the touch). In some embodiments, the event also includes information about one or more associated event handlers 190.

[0209] In some embodiments, the event definition 187 includes an event definition for each user interface object. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with a 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, the event comparison unit 184 performs a hit test to determine which of the three user interface objects is associated with this touch (sub-event). If each display object is associated with a corresponding event handler 190, the event comparison unit uses the results of the hit test to determine which event handler 190 should be invoked. For example, the event comparison unit 184 selects an event handler associated with a sub-event and the object that triggers the hit test.

[0210] In some embodiments, the definition of each event (187) includes a delay action that delays the transmission of event information until it is determined whether the sub-event sequence corresponds to the event type of the event recognition unit.

[0211] Each event recognition unit 180, if it determines that a series of sub-events does not match any event in the event definition 186, inputs an event unavailable, event failed, or event ended state, and then ignores subsequent sub-events of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, those event recognition units continue to track and process the sub-events of the ongoing touch-based gesture.

[0212] In some embodiments, each event recognition unit 180 includes metadata 183 with configurable properties, flags, and / or a list indicating how the event transmission system should perform sub-event transmission to event recognition units in which it actively participates. In some embodiments, the metadata 183 includes configurable properties, flags, and / or a list indicating how event recognition units can or can become able to interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or a list indicating whether sub-events have been transmitted to various levels in a view or program hierarchy.

[0213] In some embodiments, each event recognition unit 180 activates an event handler 190 associated with an event when it recognizes a specific sub-event of one or more events. In some embodiments, each event recognition unit 180 transmits event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and delaying) the sub-events to their respective hit views. In some embodiments, the event recognition unit 180 throws a flag associated with the recognized event, and the event handler 190 associated with this flag catches this flag and performs predetermined processing.

[0214] In some embodiments, the event transmission command 188 includes a sub-event transmission command that transmits event information about a sub-event without invoking an event handler. Rather, the sub-event transmission command transmits the event information to an event handler associated with a set of sub-events or an actively involved view. The event handler associated with the set of sub-events or the actively involved view receives the event information and performs predetermined processing.

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

[0216] In some embodiments, the event handler 190 includes, or has access to, a data update unit 176, an object update unit 177, and a GUI update unit 178. In some embodiments, the data update unit 176, the object update unit 177, and the GUI update unit 178 are contained within a single module of application 136-1 or application view 191. In other embodiments, they are contained within two or more software modules.

[0217] The description above regarding the processing of user touch events on a touch-sensitive display should be understood to also apply to other forms of user input (not all of which begin on the touchscreen) for operating the multi-functional device 100 that implements the input device. For example, mouse movements and mouse button presses are optionally used as inputs corresponding to sub-events that define the event to be recognized, in optional conjunction with one or more keyboard presses or grips, touch actions such as tapping, dragging, and scrolling on a touchpad, stylus pen input, device movements, verbal commands, detected eye movements, biometric input, and / or any combination thereof.

[0218] Figure 2 shows a portable multifunction device 100 implementing a touchscreen 112 according to several embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as with other embodiments described later, the user can select one or more graphics by making gestures on the graphics, for example, with one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, the gesture optionally includes a tap, one or more swipes (left to right, right to left, up and / or down), and / or rotations of the finger in contact with the device 100 (right to left, left to right, up and / or down). In some embodiments or situations, graphics are not selected by unintentional contact with them. For example, if the optional gesture for selection is a tap, then a swipe gesture across the application icon will not select the corresponding application.

[0219] The device 100 may further include one or more physical buttons, such as a "Home" or menu button 204. As previously mentioned, the menu button 204 can be used to navigate to any application 136 from a set of applications that can be run on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touchscreen 112.

[0220] In one embodiment, the device 100 includes a touchscreen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume control buttons 208, a subscriber identification module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding it down 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, the device 100 further accepts verbal input via a microphone 113 to activate or deactivate several functions. The device 100 optionally further includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more tactile output generators 167 for generating tactile output to the user of the device 100.

[0221] Figure 3 is a block diagram of an exemplary multifunctional device implementing a display and touch-sensitive surface according to several embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop computer, desktop computer, tablet computer, multimedia player, navigation device, educational device (such as a children's learning toy), game system, or control device (e.g., a home or industrial controller). Typically, the device 300 includes one or more processing units (CPUs) 310, one or more network or communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 optionally include circuits (sometimes called chipsets) that interconnect system components and control communication between system components. The device 300 includes an input / output (I / O) interface 330 implementing a display 340, typically a touchscreen display. The I / O interface 330 optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 that generates tactile output on the device 300 (for example, similar to the tactile output generator 167 described above with reference to Figure 1A), and a sensor 359 (for example, an optical, accelerometer, proximity, touch-sensitive sensor, and / or a contact intensity sensor similar to the contact intensity sensor 165 described above with reference to Figure 1A). The memory 370 includes high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, or optionally includes one or more non-volatile memories such as magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores programs, modules, data structures, or subsets thereof that are similar to the programs, modules, and data structures stored in the memory 102 of the portable multifunction device 100 (Figure 1A).Furthermore, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while the memory 102 of the portable multifunctional device 10C (FIG. 1A) does not store any of these modules.

[0222] Each of the elements in FIG. 3 above can be stored in one or more of the memory devices described above. Each of the above modules corresponds to one set of instructions for performing the functions described above. Since these modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, modules, it is possible to optionally combine or rearrange various subsets of these modules in various embodiments. In some embodiments, the memory 370 optionally stores a subset of the above modules and data structures. Furthermore, the memory 370 can optionally store additional modules and data structures not described above.

[0223] Here, attention is paid to embodiments of a user interface that can be optionally implemented on, for example, the portable multifunctional device 100.

[0224] FIG. 4A shows an exemplary user interface of an application menu on the portable multifunctional device 100 according to some embodiments. A user interface similar to this can be implemented on the device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. ● A signal strength indicator 402 for wireless communication such as cellular and WiFi signals, ● Time 404, ● A Bluetooth indicator 405, ●Battery status indicator 406, ●Tray 408 contains frequently used icons such as the following: ○ Icon 416 for telephone module 138. Label: "Telephone". Optionally includes an indicator 414 showing the number of missed calls or voicemail messages. ○ Icon 418 for email client module 140. Label display: "Mail". Optionally includes an indicator 410 showing the number of unread emails. ○Icon 420 for browser module 147. Label: "Browser". Icon 422 for video and music player module 152. Also known as iPod (trademark of Apple Inc.) module 152. Labeled "iPod". ● Icons for other applications, ○Icon 424 for IM module 141. Label display: "Message". ○ Icon 426 for Calendar Module 148. Label: "Calendar". ○Icon 428 for image management module 144. Label: "Photo". ○ Icon 430 for camera module 143. Label: "Camera". ○Icon 432 for online video module 155. Label: "Online Video". ○Icon 434 for stock widget 149-2. Label: "Stocks". ○Icon 436 for map module 154. Label: "Map". ○Icon 438 for weather widget 149-1. Label: "Weather". ○ Icon 440 for alarm clock widget 149-4. Label: "Clock". ○Icon 442 for Training Support Module 142. Label: "Training Support". ○ Icon 444 for memo module 153. Label: "Memo". ○ Icon 446 for the configuration application or module. Labeled "Configuration". Provides access to the configuration of the device 100 and various applications 136.

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

[0226] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) that implements a touch-sensitive surface 451 (e.g., a tablet or touchpad 355 in Figure 3) separated from a display 450 (e.g., a touchscreen display 112). The device 300 optionally includes one or more contact intensity sensors (e.g., one or more sensors 357) for detecting the intensity of contact on the touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating tactile output to the user of the device 300.

[0227] Some embodiments described below refer to input on a touchscreen display 112 (a combination of a touch-sensitive surface and a display), but in some embodiments, as shown in Figure 4B, the device detects input on a touch-sensitive surface that is separated from the display. In some embodiments, the touch-sensitive surface (e.g., 451 in 4B) has a principal axis (e.g., 452 in Figure 4B) corresponding to a principal axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to these embodiments, the device detects contact with the touch-sensitive surface 451 (e.g., 460, 462 in Figure 4B) at locations corresponding to their respective locations on the display (e.g., 460 in Figure 4B corresponds to 468, and 462 corresponds to 470). In this way, when the touch-sensitive surface is separated from the display, the device uses the user input (e.g., contacts 460, 462, and their movement) detected on the touch-sensitive surface (e.g., 451 in Figure 4B) to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B). It should be understood that similar methods may be used selectively for other user interfaces described herein.

[0228] In addition, while the following embodiments are provided primarily with reference to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, input from one or more other input devices (e.g., mouse-based input or stylus input) may be used instead. For example, a swipe gesture may be optionally replaced with a mouse click (e.g., as a substitute for touch), and then the cursor may be moved along the swipe path (e.g., as a substitute for the touch movement). In other embodiments, the tap gesture may be optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (e.g., as a substitute for stopping touch detection after touch detection). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may be used simultaneously, or a mouse and finger touch may be used simultaneously.

[0229] Figure 5A shows an exemplary personal electronic device 500. The device 500 includes a main body 502. In some embodiments, the device 500 may include some or all of the characteristics described in relation to devices 100 and 300 (for example, Figures 1A to 4B). In some embodiments, the device 500 is provided with a touch-sensitive display screen 504 (hereinafter referred to as the touchscreen 504). Alternatively, in addition to the touchscreen 504, the device 500 is provided with a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touchscreen 504 (or touch-sensitive surface) may optionally include one or more intensity sensors for detecting the intensity of contact being made (e.g., a touch). One or more intensity sensors on the touchscreen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of the device 500 may respond to touches based on the intensity of the touch, that is, different touches of different intensity may invoke different user interface operations on the device 500.

[0230] Techniques for detecting and processing touch intensity can be found, for example, in the following related applications: International Patent Application PCT / US2013 / 040061, “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on 8 May 2013 and published as International Publication No. WO / 2013 / 169849; and International Patent Application PCT / US2013 / 069483, filed on 11 November 2013 and published as International Publication No. WO / 2014 / 105276. Each of these applications is incorporated herein by reference in its entirety.

[0231] In some embodiments, the device 500 is provided with one or more input mechanisms 506, 508. The input mechanisms 506, 508 may be physical (if included). Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 is provided with one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, a hat, eyewear, earrings, necklace, shirt, jacket, bracelet, watch band, chain, trousers, belt, shoes, bag, backpack, or the like. These attachment mechanisms allow the user to wear the device 500.

[0232] Figure 5B shows an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described in relation to Figures 1A, 1B, and 3. The device 500 has a bus 512 that operably connects an I / O section 514 to one or more computer processors 516 and memory 518. The I / O section 514 can be connected to a display 504 which may have a touch-sensing component 522 and optionally an intensity sensor 524. In addition, the I / O section 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies. The device 500 may include input mechanisms 506 and / or 508. The input mechanism 506 may be a rotatable input device or a pressable and rotatable input device. In some embodiments, the input mechanism 508 may be a button.

[0233] In some embodiments, the input mechanism 508 may be a microphone. The personal electronic device 500 may optionally include a variety of sensors such as a GPS sensor 532, an accelerometer 534, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or a combination thereof, all of which can be operably connected to the I / O section 514.

[0234] The memory 518 of the personal electronic device 500 may be a non-temporary computer-readable storage medium that stores computer-executable instructions, which, when executed by, for example, one or more computer processors 516, cause the computer processors to perform the techniques described above, including processes 2000 to 3300 (Figures 20 to 33). The computer-executable instructions may be further stored and / or transferred to any non-temporary computer-readable storage medium for use by or in connection with instruction execution systems, devices, or other instruction execution systems, devices, or systems that can fetch and execute instructions from such systems. For the purposes of this document, “non-temporary computer-readable storage medium” may be any medium that can tangibly hold or store computer-executable instructions for use by or in connection with instruction execution systems, devices, or other devices. Non-temporary computer-readable storage medium may, not limited to, include magnetic, optical, and / or semiconductor memory devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical discs based on Blu-ray technology, as well as persistent solid-state memory (flash, solid-state drives, etc.). The personal electronic device 500 is not limited to the components and configurations shown in Figure 5B and may include other or additional components with multiple configurations.

[0235] As used herein, the term "affordance" means a user-interactive graphical user interface object that can be displayed on the display screen of the devices 100, 300, and / or 500 (Figures 1, 3, and 5). For example, an image (e.g., an icon), a button, or text (e.g., a hyperlink) may each constitute an affordance.

[0236] As used herein, the term “focus selector” means an input element that indicates the current portion of a user interface that the user is interacting with. In some embodiments, including a cursor or other position marker, the cursor functions as a “focus selector,” so that when input is detected on a touch-sensitive surface (e.g., the touchpad 355 in Figure 3, or the touch-sensitive surface 451 in Figure 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to this detected input. In some embodiments, including a touchscreen display that allows direct interaction with user interface elements on the touchscreen display (e.g., the touch-sensitive display system 112 in Figure 1A, or the touchscreen 112 in Figure 4A), detected contact functions as a “focus selector,” so when input (e.g., a press input by touch) is detected at the location of a particular user interface element on the touchscreen display (e.g., a button, window, slider, or other user interface element), the particular user interface is adjusted according to this detected input. In some implementations, focus moves from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (e.g., by moving focus from one button to another using the tab key or arrow keys), and in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. The focus selector is generally a user interface element (or touch on the touchscreen display) controlled by the user to communicate the user's intended interaction within the user interface (e.g., by indicating to the device the element of the user interface that the user intends to interact with).For example, the position of a focus selector (e.g., cursor, touch, or selection box) on each button while pressure input is detected on a touch-sensitive surface (e.g., touchpad or touchscreen) indicates that the user wants to activate that button (in contrast to other user interface elements displayed on the device's display).

[0237] As used herein and in the claims, “characteristic intensity” of a contact means a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is arbitrarily based on a predetermined number of intensity samples, or on a set of intensity samples collected in connection with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of contact movement, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity) during a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds). The characteristic intensity of a contact is arbitrarily based on one or more of the following: the maximum intensity of the contact, the mean value of the contact intensity, the average value of the contact intensity, the top 10 percentile value of the contact intensity, the maximum half-value of the contact intensity, the 90% value of the maximum intensity of the contact intensity, and others. In some embodiments, the duration of contact is used to determine the characteristic intensity (for example, if the characteristic intensity is the average value of the contact intensity over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user performed an action. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this embodiment, a first action is obtained as a result of contact at a characteristic intensity not exceeding the first threshold, a second action is obtained as a result of contact at a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold, and a third action is obtained as a result of contact at a characteristic intensity exceeding the second threshold. In some embodiments, the comparison of the characteristic intensity with one or more thresholds is not used to determine whether to perform the first or second action, but rather to determine whether to perform one or more actions (for example, whether to perform each action or refrain from performing each action).

[0238] In some embodiments, a portion of the gesture is identified for the purpose of determining characteristic intensity. For example, a touch-sensitive surface can receive a series of swipe contacts transitioning from a starting location and read an ending location where the contact intensity increases. In this embodiment, the characteristic intensity of the contact at the ending location may be based only on a portion of the series of swipe contacts (e.g., only the portion of the swipe contact at the ending location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm can be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms remove sharp spikes and dips in the intensity of the swipe contact in order to determine characteristic intensity.

[0239] The intensity of contact on a touch-sensitive surface may be characterized in relation to one or more intensity thresholds, e.g., a contact detection intensity threshold, a light pressure intensity threshold, a hard 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 performs an operation typically associated with clicking a physical mouse or trackpad button. In some embodiments, the hard pressure intensity threshold corresponds to the operation at which the device performs an action typically associated with clicking a physical mouse or trackpad button. In some embodiments, when a contact with a characteristic intensity below the light pressure intensity threshold (for example, above a nominal contact detection intensity threshold below which contact is no longer detected) is detected, the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an operation associated with the light pressure intensity threshold or the hard pressure intensity threshold. Generally, unless otherwise described, these intensity thresholds are consistent across various user interface diagrams.

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

[0241] In some embodiments described herein, one or more operations are performed in response to the detection of a gesture including each pressing input, or in response to the detection of each pressing input performed with each (or more) contact, in which case each pressing input is detected at least in part on detecting an increase in the intensity of the contact (or more) above a pressing input intensity threshold. In some embodiments, each operation is performed in response to the detection of an increase in the intensity of each contact above a pressing input intensity threshold (e.g., a "downstroke" of each pressing input). In some embodiments, the pressing input includes an increase in the intensity of each contact above a pressing input intensity threshold and a subsequent decrease in the intensity of the contact below the pressing input intensity threshold, and each operation is performed in response to the detection of a subsequent decrease in the intensity of each contact below a pressing input threshold (e.g., an "upstroke" of each pressing input).

[0242] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes referred to as "jitter," in which case the device defines or selects a hysteresis intensity threshold using a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of each contact above the press input intensity threshold, followed by a decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, with each operation performed in response to the detection of a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., an "upstroke" of each press input). Similarly, in some embodiments, a pressing input is detected only when the device detects an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a pressing input intensity threshold, and optionally a subsequent decrease in contact intensity to an intensity below the hysteresis intensity, and each operation is performed in response to the detection of a pressing input (for example, an increase in contact intensity or a decrease in contact intensity, depending on the situation).

[0243] For simplicity of explanation, descriptions of actions performed in response to a press input or a gesture involving a press input related to a press input are optionally triggered in response to the detection of any of the following: an increase in contact intensity above a press input intensity threshold; an increase in contact intensity from below a hysteresis intensity threshold to above a press input intensity threshold; a decrease in contact intensity below a press input intensity threshold; and / or a decrease in contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold. In addition, in embodiments described as being performed in response to the detection of a decrease in contact intensity below a press input intensity threshold, the operation is optionally performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold corresponding to and below the press input intensity threshold.

[0244] The term "installed application" as used herein means a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched (e.g., opened). In some embodiments, a downloaded application becomes an installed application by an installation program that extracts a program portion from a downloaded package and integrates this extracted portion with the operating system of the computer system.

[0245] The terms "open application" or "running application" used herein refer to a software application that holds state information (for example, as part of the device / global internal state 157 and / or application internal state 192). An open or running application may be any of the following types of applications: ●The active application currently displayed on the display screen of the device using the application, ● Background applications (or background processes) that are not currently displayed but are being processed by one or more processors, ● An application that is not currently running but has state information stored in memory (both volatile and non-volatile) that can be used to resume application execution; this is an application that is suspended or suspended.

[0246] The term "closed application" used here refers to a software application that does not retain state information (for example, a closed application whose state information is not stored in the device's memory). Therefore, closing an application includes stopping and / or removing the application's processing and removing the application's state information from the device's memory. Generally, if a second application is opened while the first application is not closed, the first application will not be closed. When the second application is displayed and the display of the first application is stopped, the first application becomes a background application. 1. Context-specific user interface

[0247] Next, we focus on embodiments of context-specific user interfaces ("UI") and related processing that can be implemented on multifunctional devices equipped with displays and touch-sensitive surfaces, such as devices 100, 300, and / or 500 (Figures 1A, 3A, and / or 5A).

[0248] The following examples illustrate exemplary embodiments of context-specific user interfaces. Here, we discuss the overall concepts related to customized context-specific user interfaces. Note that the context-specific user interfaces described here can be edited in numerous ways. The user interface can display or indicate various types of time-related information, and the type of information can be customized by the user. The user interface includes aspects such as color, display density, complexity (or lack thereof), which are also customizable. As used here without contradicting the technically accepted meaning, "complexity" refers to any clock face features other than those used to indicate hours and minutes (e.g., clock hands or hour / minute displays). Complexity can provide the user with different types of information, such as data obtained from applications, and the information conveyed to the user through complexity is also customizable.

[0249] The combination of these features generates at least several thousand usable context-specific user interfaces. Since it is impractical to describe each of these permutations, we will emphasize embodiments with specific context-specific user interfaces. However, specific embodiments can be used for other context-specific user interfaces, and specific context-specific user interfaces can have other embodiments; therefore, such illustrative descriptions are not intended to limit such embodiments to the context-specific user interfaces described herein. These embodiments are intended to illustrate the overall concept presented, but those skilled in the art will recognize that numerous other embodiments are possible within the scope of the technology described herein.

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

[0251] Users who track their time may want some sense of how much time has passed since a particular event. For example, a user might want to know how much time has passed since they last looked at the time, or how much time has passed since a particular time of day (e.g., morning). In addition to looking at the clock face, users may want to receive additional visual cues to reinforce their perception of the elapsed time.

[0252] As shown in Figure 6A, the device receives data representing user input 602. In response to receiving this data, the device displays a user interface screen 604 on the display. Screen 604 includes a clock face 606. In the embodiment shown in Figure 6A, the current time is 7:00. The clock face 606 displays a first time (10:05 as shown in Figure 6A) before showing the current time. The device 600 transitions from displaying the first time to displaying the current time by updating screen 604 with an animated clock face. The updated screen 604 is shown as screen 610, displaying the clock face 612. The clock face 612 is now updated to show the current time. The animation of screens 604-610 represents the passage of time from the first time to the current time. In some embodiments, screens 604 and / or 610 may further include a date display.

[0253] As described above, the context-specific user interface illustrated in Figure 6A initially displays a clock face showing a first time. The first time can be determined based on different criteria. In some embodiments, the device receives second data representing the time the user last moved the electronic device (e.g., the time of device movement, such as the user lowering their wrist if the device is wearable, or other movement indicating that the user is no longer actively looking at the display). The time the user last moved the electronic device may be the time the user last looked at the device, or the time the device's display was last turned off, before receiving data representing user input 602. Next, the time the user last moved the electronic device is indicated by the clock face as the first time. For example, in Figure 6A, the 10:05 shown on the clock face 606 may be the time the user last moved the device (i.e., the time of the last user interaction). In these embodiments, when the user interface screen is updated, the user is provided with a display indicating how much time has passed since the last user interaction (e.g., the time the user last looked at the device 600).

[0254] In other embodiments, the first time can 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 prior to the current time. That is, the first time displayed on the clock face may be based on a predetermined or fixed duration prior to the current time, rather than on user interaction.

[0255] In some embodiments, the predetermined duration is 5 hours. In response to user input, the clock face can display a time 5 hours prior to the current time, and then animate the clock face to transition from the display of the first time to the display of the current time. For example, if the current time is 6:00, the device can, in response to user input, display an animated clock face showing 1:00 to transition from 1:00 to 6:00.

[0256] In other embodiments, the first time zone may be based on a predetermined time. In this case, the device can start the animation by showing the same time zone (i.e., the first time zone) regardless of the current time, and then continue animating the clock face until it reaches the current time. For example, the first time zone may be in the morning (e.g., 8:00 AM). In this embodiment, if the current time is 6:00 AM, the device can respond to user input to display an animated clock face showing 8:00 AM in order to transition from 8:00 AM to 6:00 AM.

[0257] 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, regardless of how the first time was determined. That is, the length of the animation is roughly proportional to the length of this duration. The length of the animation does not have to be exactly proportional to the first duration, but it may convey an approximate length of time to the user. To illustrate using the embodiments described above, the clock face can be animated for a longer period when transitioning from 8:00 to 6:00 than when transitioning from 3:00 to 6:00. This is particularly useful when the duration is variable, such as when the duration is based on the time between user interactions. In this case, the user will immediately understand that a longer clock face animation indicates a longer elapsed time between interactions, and a shorter clock face animation indicates a shorter time between interactions.

[0258] In other embodiments, the clock face is animated for a certain period, regardless of the first period. 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 all animations. To illustrate using the embodiments described above, the clock face can be animated for the same period, regardless of whether it is transitioning from 3:00 to 6:00 or from 8:00 to 6:00. This helps reduce the time the user has to view the transition. Alternatively, the clock face can be animated for a different period when transitioning from 8:00 to 6:00 than when transitioning from 3:00 to 6:00, but these periods do not have to be related to the first period.

[0259] Figure 6B illustrates an optional feature of this context-specific user interface. In response to data representing user input 620, the device 600 displays a user interface screen 622 including a clock face 624. In this embodiment, the current time is 10:25. The clock face 624 shows a first time (10:05 in this embodiment). The clock face 624 further displays an image of a mountain scene representing the first time as a background. For example, as shown in Figure 6B, the clock face 624 shows a view of a mountain scene in the morning (see, for example, the position of the sun 626 in the sky). Thus, a user looking at the clock face 624 understands the time based on the clock face itself and the background, which also represents the time indicated by the clock face. Note that this provides the user with additional information, as the user understands from the scene display that the displayed time is 10:05 AM and not 10:05 PM.

[0260] In some embodiments, the device accesses an image of a scene representing the time shown on a clock face. The image of the scene representing the time can also imply to the user a similar time period, along with the time shown on the clock face. The image of the scene does not need to imply the exact time shown on the clock face, nor does it need to be strictly related to the time period of the location in the scene (this will be discussed in more detail later). In some embodiments, the image of the scene is an image captured at substantially the same time as the current time (i.e., the time when the image was taken at the scene location). In other embodiments, the image of the scene is an image captured at a different time period than the current time.

[0261] In some embodiments, the scene image may depict, for example, a city, a beach, a desert, a park, a lake, a mountain, or a canyon. In some embodiments, the scene may be a user-recognizable location such as Yosemite Valley or Big Ben.

[0262] Next, the device 600 displays screens 630 and 640. Screen 630 is optional, as described below, and includes a clock face 632 showing the time between the first time and the current time. This intermediate time is further represented on the clock face 632 by a background (see, for example, a setting sun 634). Screen 640 includes a clock face 642 showing the current time. The clock face 642 further displays a background representing the current time (see, for example, the moon 644).

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

[0264] The continuous display shows the passage of time from the first time to the current time. The device may include a series of images of specific scenes (e.g., time progression images), each representing a different time period, so that any first time or current time shown on the clock face has a scene image representing the displayed time. In some embodiments, the first scene image and the second scene image are displayed as a background on the user interface screen.

[0265] In some embodiments, the device accesses a set of scene images, including a first scene image representing a first time (e.g., a clock face background 624), one or more second scene images representing one or more time intervals between the first time and the current time (e.g., a clock face background 632), and a third scene image representing the current time (e.g., a clock face background 642). In response to receiving data representing user input 620, the device displays this set of scene images (e.g., like a flipbook) by animating the sequence of scene images showing the passage of time from the first time to the current time. In some embodiments, the scenes are specified by the user (e.g., the device stores a set of time-lapse images for different scenes, and the user can select which scenes to display).

[0266] As shown in Figure 6B, the device 600 displays screens 622, 630, and 640 in sequence to animate each displayed background, thereby animating the scene images like a flipbook showing the passage of time. In some embodiments, the transition from screen 620 to 630 and further to 640 can also be animated by animating the hands of a clock face to rotate clockwise, and / or animating the display of the scene images like a flipbook. If the clock face alternatively or additionally displays a digital clock representation, the numerical display of hours and minutes can be animated in some way to indicate the elapsed time. By displaying an animated clock face and animated scene images, the device provides the user with a clear display that allows for easy distinction between the first time and the current time.

[0267] In some embodiments, the 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. The first scene image represents the first time at the current location, and the second or third scene image (e.g., either representing the current time) represents the current time at the current location. That is, the shown passage of time reflects the daytime / nighttime at the current location. For example, if the user is in a location near the Arctic Circle, the daytime may be close to 24 hours. In this embodiment, even if the first time and the current time are far apart, all images representing the first time and the current time can be daytime scene images (e.g., Yosemite Valley). Thus, a scene image can represent the time shown at the current location, but not the time shown at the location of the scene. Because the animation is based on the user's experience at the current location (e.g., perception of time), this concept allows the device to display a context-specific user interface that shows the passage of time at the current location, thereby extending the interaction between the user and the device.

[0268] In some embodiments, the device displays a user interface object at a first position on the user interface screen based on a first time. In some embodiments, this position may be based on a position along a clock face, such as the hour marker (e.g., the 6 o'clock position at the bottom center of the display). In some embodiments, this position may be based on a position that intersects the horizon, such as the position of the sun or moon. For example, in Figure 6B, the position of the sun 626 represents the sun 626 in the east of the scene, just before noon, thus indicating the first time.

[0269] In some embodiments, the device animates a user interface object by moving it from a first position on the user interface screen to a second position based on the current time. Moving the user interface object from the first position to the second position indicates the passage of time from a first time to the current time. As shown in Figure 6B, the sun 626 moves across the sky in a series of scene images (see sun 626 and sun 634). Next, the user interface object shows the moon 644 at a position in the night sky representing the current time. In some embodiments, the user interface object is a graphic representation of the sun (e.g., 626, 634). In some embodiments, the user interface object is a graphic representation of the moon (e.g., 644).

[0270] In any of the embodiments described above, user input may include movement of the device. For example, movement of the device may be a wrist raise (if the device is wearable), or other movement indicating that the user has raised the device to view it. These movements can be detected using, for example, an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or a combination thereof. In any context-dependent aspect described herein, movement of the device may constitute user input for activating the display.

[0271] Furthermore, in any of the context-dependent aspects described here, device movement such as the user lowering their wrist (if the device is wearable) or other movements indicating the user is no longer actively looking at the device, or the absence of device movement such as the user raising their wrist (if the device is wearable) or other movements indicating the user has raised the device to view the display, can serve as user input to turn off the display on the device.

[0272] In other embodiments, the device may have a touch-sensitive display or touch-sensitive surface (for example, the touchpad 355 in Figure 3, the touch-sensitive surface 451 in Figure 4B, and / or a touchscreen 504).

[0273] Next, we consider the context-specific user interface shown in Figure 7A. Figure 7A shows an exemplary context-specific user interface that can operate on the device 700. The device 700 may be the device 100, 300, or 500 in some embodiments. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0274] Users might want to access stopwatch functionality while tracking time. For example, in contexts such as "running" or "cycle," users might want to operate the stopwatch and record laps while tracking time.

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

[0276] As illustrated in Figure 7A, the device 700 receives user input, in this case a touch 712 on the start affordance 710. In response, the device replaces the 12 o'clock indicator 706 with the stopwatch timescale indicator 724, as shown on screen 720. The stopwatch indicator 724 indicates that the stopwatch timescale is a 60-second timescale. The stopwatch hand's timescale means the amount of time required for the stopwatch hand to complete one rotation around the displayed clock face. 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.

[0277] Furthermore, in response to touch 712, the device 700 animates the stopwatch hand 726 to reflect the passage of time by comparing screens 720 and 730. As shown on screen 730, the stopwatch hand moves to the seconds position on the clock face (note the position of stopwatch hand 736), indicating the passage of time. If indicator 734 shows a 60-second stopwatch timescale, the position of stopwatch hand 736 indicates that 25 seconds have elapsed. As shown in Figure 7A, the user accesses this information by touching 740 on the wrap affordance 738, which displays the 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 their positions in the past 25 seconds. In this embodiment, through screens 702, 720, and 730, the hour and minute hands show the same time (e.g., 10:10).

[0278] Alternatively, the device indicates the time with hour and minute hands, and also with a stopwatch hand. In response to the reception of data representing user input, the hour display is replaced with the first timescale display on the first stopwatch hand, but the hour and minute hands continue to display the time even after the hour display is replaced. This allows the user to view the stop and time simultaneously while the stopwatch is running and displaying the stopwatch's timescale. In response to the reception of data, the device animates the stopwatch hand to reflect the passage of time.

[0279] In some embodiments, the device can animate the stopwatch hands to reflect the passage of time, receive second data representing a second user input, and stop animating the stopwatch hands in response to the receipt of this second data. For example, this can function similarly to the "stop" function of a stopwatch.

[0280] In some embodiments, the device may display a first affordance (e.g., affordance 710) representing a start / stop function on a touch-sensitive display. Both first data representing a first user input (e.g., touch 712) and second data representing a second user input indicate contact with the displayed first affordance. In other embodiments, the device displays separate affordances for a stopwatch start function and a stopwatch stop function.

[0281] In some embodiments, the device may display a second affordance (e.g., affordance 738) representing a lap function on a touch-sensitive display. The device receives third data representing a touch on the displayed second affordance after receiving first data (e.g., after calling the start function) and before receiving second data (e.g., before calling the stop function). In response to the receipt of this third data, the device displays a third digit display representing the elapsed time between the receipt of the first data and the receipt of the third data. For example, this can function similarly to the “lap” function of a stopwatch to display the elapsed time since the start function call. As described above, this feature is shown on screen 730.

[0282] In some embodiments, the device can display a third affordance (shown as affordance 714 on screen 702) representing a stopwatch application on a touch-sensitive display. The device receives fourth data representing a touch of the displayed third affordance and, in response to the receipt of this fourth data, launches the stopwatch application. This allows the user to directly access additional information and / or functions related to the stopwatch feature from this context-specific user interface. In one embodiment, the stopwatch application is the application described in the following related application: U.S. Provisional Patent Application No. 62 / 044,979, “Stopwatch and Timer User Interfaces,” filed 2 September 2014.

[0283] In some embodiments, the first timescale of the stopwatch hand may be 60 seconds, 30 seconds, 6 seconds, or 3 seconds. In some embodiments, the movement of the stopwatch hand is animated at a speed based on the first timescale of the stopwatch hand. For example, the stopwatch hand can move faster when the timescale is 3 seconds than when the timescale is 60 seconds. This allows the stopwatch hand to complete one rotation around the clock face within the time amount indicated by the first timescale.

[0284] In some embodiments, the device can replace one or more hourly indicators with indicators for the first time scale of the stopwatch hand by removing one or more hourly indicators, displaying a first time scale indicator for the stopwatch hand, and converting the displayed first time scale indicator for the stopwatch hand into a clockwise rotation. In an exemplary embodiment, if the display includes twelve digits for the hourly time scale and the first time scale for the stopwatch hand is a 6-second time scale, the device replaces the twelve digits with a single digit 6. In some embodiments, this may be the same digit 6 that was previously used to indicate "6 o'clock" so that the user does not perceive the replacement and display. The device can display the digit 6 indicating the first time scale of the stopwatch hand at the 6 o'clock position on the clock face and translate this digit 6 clockwise around the clock face until it reaches the top of the clock face, at which point the translation stops. This enhances the context-specific interface by emphasizing to the user that the clock face has transitioned from displaying hours and minutes to displaying the first time scale of the stopwatch hand.

[0285] As shown in Figure 7B, in some embodiments, the device has a rotatable input mechanism (e.g., 506) used as an optional input for changing the stopwatch timescale. Figure 7B shows a screen 750 with a clock face 752, which includes hour and minute hands 754 and a stopwatch timescale indicator 756 (showing a 60-second timescale). In response to the reception of a fifth data representing a movement of the rotatable input mechanism (e.g., movement 758), the device 700 changes the stopwatch timescale to a second timescale such that a portion of the clock face 772 on the screen 770 is shown by the stopwatch timescale indicator 776. Note that the screen 770 continues to display the hour and minute hands 774. The second stopwatch timescale is different from the first stopwatch timescale. This allows the user to customize the timescale of the stopwatch hands by rotating the rotatable input mechanism, resulting in a context-specific user interface that corresponds to the user's desired stopwatch timescale.

[0286] In some embodiments, the device replaces the display of the first time scale on the stopwatch hand with the display of the second time scale on the stopwatch hand by removing the display of the first time scale on the stopwatch hand, displaying the display of the second time scale on the stopwatch hand, and translating the displayed display of the second time scale on the stopwatch hand by rotating it to the right.

[0287] As shown in Figure 7B, the indicator 760 of the second time scale of the stopwatch hand is displayed on the clock face at a position indicating its relative position on the first time scale. For example, the indicator 760 of the 30-second time scale is displayed on the clock face 752 at a position based on the 60-second time scale indicated by 756. In response to the reception of data representing movement 758, the device removes 756, displays 760, and then translates 760 to the right in a rotational motion until it reaches the original position of the indicator of the first time scale of the stopwatch hand (for example, the original position of 756 indicated by position 776 on the clock face 772).

[0288] In some embodiments, after receiving first data representing a first user input, the device animates a stopwatch hand to represent rotation around a base point, and then stops the animation to display the stopwatch hand at a position of π / 2 radians relative to the rotation around the base point (e.g., the 12 o'clock position). For example, prior to receiving the first data, the stopwatch hand can function as the second hand of a clock face. Upon receiving the first data, the second hand is animate to represent rotation around the clock face (e.g., by rotating around the center point of the clock face) until it reaches the 12 o'clock position. This informs the user that the second hand has become a stopwatch hand.

[0289] Next, we consider the context-specific user interface shown in Figure 8. Figure 8 shows an exemplary context-specific user interface that can operate on device 800. Device 800 may be device 100, 300, or 500 in some embodiments. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0290] Figures 8-10 provide a context-sensitive user interface that allows users to view the passage of time while accessing a wealth 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 currently experiencing daytime or nighttime. Another user might be interested in the lunar phase and want to know what the moon will look like tomorrow, next week, and next month. Yet another user might be interested in astronomy and want to know how the planets will align at a specific time (which could be today).

[0291] In Figure 8, the device 800 displays a user interface screen 802 that includes a first affordance 804. The first affordance 804 represents a simulation of the regions of the Earth that are illuminated by the sun at the current time. For example, the first affordance 804 indicates that it is currently daytime in North, Central, and South America, and nighttime in the Pacific region, thereby simulating the regions of the Earth that are illuminated by the sun at the current time.

[0292] Screen 802 further displays the second affordance 806, which indicates the current time. The second affordance 806 shows the current time (10:09) and optionally displays the day of the week (Wednesday) and the date (25th). Screen 802 further displays the lunar affordance 808 and solar system affordance 810, which are used to invoke additional context-specific user interfaces accessible from this screen, and are described in more detail below.

[0293] In some embodiments, the simulation of a first region of the Earth illuminated by the sun at the current time is a photorealistic rendering of the Earth at the current time. For example, the simulation of the Earth may include specific geographical features. In some embodiments, the simulation of the Earth is updated to reflect the weather pattern at the current time (by indicating cloud cover or other weather phenomena such as tropical storms). The device updates the Earth to reflect the global scale by obtaining data from weather services such as Weather Channel, Accuweather, the National Weather Service, Yahoo! Weather, Weather Underground, the U.S. Naval Observatory, the National Oceanic and Atmospheric Administration, or external servers. In some embodiments, the simulation of a first region of the Earth illuminated by the sun at the current time can display other global events such as real-time positioning of the International Space Station (obtained from a service such as one provided by NASA or from an external server).

[0294] The device 800 receives user input (a swipe 812 in this embodiment) and, in response to receiving this user input, rotates the Earth simulation to display a second region of the Earth that is illuminated by the sun at the current time. This is shown on screen 820, which displays a first affordance 822 indicating the second region of the Earth that is illuminated by the sun at the current time, indicated by a second affordance 824. This feature allows the user to access additional information beyond the current time from this context-specific user interface. For example, the user can rotate the Earth simulation to display regions that are currently daytime and regions that are currently nighttime. By linking this information with the Earth simulation, the user can access complex geographical and time-related data in an instant, intuitive, and understandable way.

[0295] In some embodiments, a first affordance representing a simulation of a first region of the Earth that is illuminated by the sun at the present time includes a representation of a solar terminator (e.g., the day-night boundary at the present time). As shown by affordances 804, 822, the simulation of the Earth may include a region of the Earth that is currently daytime, a region of the Earth that is currently nighttime, and / or a solar terminator dividing the two regions.

[0296] In some embodiments, user input includes a swipe in a first swipe direction on a touch-sensitive display, indicated by swipe 812. This allows the user to swipe the display to rotate the simulation of the Earth. In some embodiments, the direction of rotation of the Earth is the same as the swipe direction. In some embodiments, the direction of rotation of the Earth is opposite to the swipe direction.

[0297] In some embodiments, the user can rotate the Earth simulation in two or more directions using swipes in different directions. For example, swiping in one direction rotates the image of the Earth in that direction, while swiping in the opposite or different direction rotates the representation of the Earth in the opposite direction. This allows the user to swipe in various directions to guide the rotation of the Earth simulation.

[0298] In some embodiments, as shown in Figure 8, the device has a rotatable input mechanism (e.g., 506). Device 800 receives user input representing the movement of the rotatable input mechanism (e.g., movement 830) and, in response, updates a first affordance 822 representing 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 affordance 842 and a second affordance 844. Comparing screens 820 and 840, the simulation of the Earth has been updated from showing a region of the Earth at the current time (10:09, shown in 824) to showing the same region of the Earth at a non-current time (12:09, shown in 844) (see 822, 842). This feature provides further user access to geographical and time-related information by allowing the user to view the sunlit Earth multiple times a day.

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

[0300] In some embodiments, the device (e.g., device 800) visually marks the device's current location on a representation of the Earth (e.g., by displaying a symbol at an appropriate location on the image of the Earth, and / or by displaying the current location in text). In some embodiments, the visual mark may be temporary, for example, the visual mark may disappear or fade out after being displayed for a short time. In some embodiments, the device does not repeatedly display the visual mark 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 representation of the Earth as described above when the user first looks at the display after changing location. In some embodiments, the device detects movement of the device by the user (e.g., movement of the device such as the user raising their wrist if the device is wearable, or other movement indicating that the user is viewing the display), and in response, obtains the current location of the electronic device from a location sensor. The device then determines whether the current location is the same as the device location when the user last moved the device. According to the determination that the current location has changed since the user last moved the device, the device may visually mark the current location on the representation of the Earth.

[0301] In some embodiments, the device visually marks a contact location (e.g., current location) corresponding to the contact's location on a representation of the Earth (e.g., the location of the contact's electronic device) (e.g., displaying a symbol at the appropriate location on the image of the Earth, and / or displaying the contact's location in text). This contact can be stored, for example, in the device or in an external device connected to the device via wireless communication (Wi-Fi, Bluetooth®, Near Field Communication ("NFC"), or any of the cellular and / or other wireless communication technologies described herein). In some embodiments, the contact may be a contact associated with a user who has agreed to provide location data to the user of the device 800 via a "Find My Friends" application, and data indicating the location of the contact's electronic device may be provided from a server that provides the locations of contacts stored in the device 800. This provides the user of the device 800 with a readily understandable visual query to inform them of the contact's current location. In some embodiments, the user can further input travel information for the contact (e.g., flight data, train data, sea voyage or ship data for contacts traveling by plane, etc.). The device can obtain data representing the contact's current or predicted location (for example, provided by the airline's server in the case of flight data) and update the visual marker of the contact's location based on this obtained data.

[0302] In some embodiments, the device detects movement of the device by the user (for example, movement of the device such as the user raising their wrist if the device is wearable, or other movement indicating that the user is viewing the display). Upon detecting this movement, the device animates the first affordance representing the Earth simulation by translating the first affordance on the screen toward the center of the displayed user interface screen. For example, upon detecting user movement, the device animates the Earth simulation rotating from the side or edge of the display toward the center of the display.

[0303] In some embodiments, the device displays a third affordance representing the moon (indicated by affordances 808, 826, and 846) on the user interface screen. In some embodiments, the third affordance may be a graphic or stylized representation of the moon, such as a moon icon, symbol, or character representation. In some embodiments, the third affordance may be a realistic rendering of the moon as seen from Earth at the current time, depicting actual lunar features.

[0304] The device detects contact with the displayed third affordance and, in response to this detection, updates the user interface screen display by showing a fourth affordance representing a simulation of the Moon as seen from Earth at the current time, and a fifth affordance indicating the current time. In some embodiments, updating the user interface screen display includes animating a zoom-out of the first affordance representing a simulation of a first region of the Earth illuminated by the sun. This animation allows the user to recognize that the astronomical scale and / or perspective has been changed.

[0305] This shifts the user interface from providing information about the current time within the day using a simulation of the Earth to providing information about the current time within the month using a simulation of the Moon. While the context-specific user interface described in Figure 8 provides globally customizable geographical information about daytime / nighttime conditions, Figure 9 shows a context-specific user interface that provides the user with customizable information about the lunar phase and other lunar features.

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

[0307] As described above, device 900 is device 800 with an updated display. Device 900 displays screen 902 which includes affordance 904. Affordance 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 affordance 904 is a realistic rendering of the moon as seen from Earth at the current time, depicting the actual lunar features. As shown by the fourth affordance 904, the current lunar phase is an inverted crescent. Figure 9 shows a stylized crescent for representing the moon, but this is a schematic diagram for illustrative purposes only. The fourth affordance 904 can show a realistic rendering of the moon that is similar to how the moon actually appears in the night sky. Screen 904 further includes a fifth affordance 906 which indicates the current time by showing the current date, day of the week, and month. In some embodiments, 906 shows the current date.

[0308] The device 900 receives user input (e.g., movement 912 of the rotatable input mechanism) and, in response to receiving this user input, rotates the lunar simulation to display the moon as seen from Earth at the current time, as shown by affordance 922 on the screen 920 (representing the moon at a non-current time as shown by the updated fifth affordance 924). The non-current time may be the time of the current month or another month.

[0309] This is somewhat similar to the user interaction with the Earth simulation described in Figure 8. The context-specific user interface illustrated in Figure 9 allows the user to access information about the appearance of the Moon at various times (e.g., lunar phase, or which regions of the Moon are visible from Earth). In some embodiments, the size of the displayed Moon simulation may represent the relative distance between Earth and the Moon at the indicated current or non-current time, or the visual size of the Moon as perceived from Earth at the indicated current or non-current time. The device can obtain such information from services such as those provided by NASA or from external servers.

[0310] In some embodiments, a user can rotate a representation of the moon and view the corresponding time by swiping on a touch-sensitive display. In some embodiments, user input may include swiping in a first swipe direction on the touch-sensitive display. In some embodiments, in response to receiving user input, the simulation of the moon as seen from Earth is rotated in a first rotation direction. In some embodiments, the first rotation direction may be based at least in part on the first swipe direction. The term "moon rotation" as used herein includes the rotation of the moon to represent 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 based on the rotation of the relative positions of the moon, Earth, and sun (e.g., updating the displayed lunar phase).

[0311] In some embodiments, the device receives a second user input and, in response to receiving this second user input, rotates a simulation of the Moon as seen from Earth in a second direction different from the first direction. This user input includes, for example, a swipe in a second swipe direction different from the first direction on a touch-sensitive display.

[0312] This allows users to be guided by swiping to both the direction of the moon's rotation and the time indicated by the fifth affordance. For example, by swiping in one direction, a user can rotate the moon in a specific direction to see the moon at a later time within the current month, and by swiping in another direction, they can rotate the moon in the opposite direction to see the moon at an earlier time within the current month.

[0313] In some embodiments, as shown in Figure 9, the user can rotate the representation of the moon and view the corresponding time by rotating a 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 rotational 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 rotational direction. In some embodiments, the first rotational direction may be based at least in part on the direction of movement of the rotatable input mechanism.

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

[0315] This allows the user to guide both the direction of the moon's rotation and the time indicated by the fifth affordance in response to the rotation of the rotatable input mechanism. For example, by moving the rotatable input mechanism in one direction, the user can rotate the moon in a specific direction to view the moon at a later time within the current month, and by moving the rotatable input mechanism in another direction, the user can rotate the moon in the opposite direction to view the moon at an earlier time within the current month.

[0316] In any of the embodiments described herein, the displayed lunar simulation may indicate one or more additional lunar attributes, such as special lunar events (e.g., blue moon, black moon, red moon, lunar eclipse, and others), the distance between the moon and the Earth (as described above, e.g., in the case of a supermoon). In some embodiments, additional lunar attributes can be indicated by changing the appearance of the displayed lunar simulation (e.g., changing the color, size, and / or tilt of the displayed lunar simulation). In some embodiments, additional lunar attributes may be indicated by text. In some embodiments, additional lunar attributes may correspond to the current lunar attribute. In some embodiments, additional lunar attributes may correspond to the lunar attribute at the currently displayed date (e.g., if the user rotates the moon to see the moon at an earlier or later time within the current month, as described above). For example, in some embodiments, while the lunar simulation is rotated to show the moon at a different time in that month or year, the lunar simulation may be updated to reflect one or more additional lunar attributes at the time currently shown by the displayed lunar simulation.

[0317] In some embodiments, the device may display additional lunar information in response to user input. This additional lunar information may be displayed, for example, as part of screen 902 or 920, or on a user interface screen (such as a lunar information application) in place of screen 902 or 920. The additional lunar information may, but not necessarily, include the names of lunar phases, the distance from the Earth to the Moon, and the moonrise and / or moonset times (e.g., today's and / or the user's current location). In some embodiments, the additional lunar information may correspond to current lunar information (e.g., current lunar phase, distance to the Moon, moonrise / moonset times, etc.). In some embodiments, as described above, if the user rotates the Moon to view the Moon at earlier or later times within the current month, the additional lunar information may correspond to the information for the currently displayed date.

[0318] For example, in some embodiments, the device can detect user input (e.g., a user double-tap on a touch-sensitive display, including a first touch and a second touch on the touch-sensitive display). In exemplary embodiments, in response to a user double-tap, the device can also determine whether the first and second touches were received within a predetermined time interval. In response to the detection of a user double-tap, and in accordance with the determination that the first and second touches were received within a predetermined time interval, the device can display additional month information.

[0319] In some embodiments, the user interface screen displays an affordance representing the Earth (e.g., 910 or 928) after updating the display to show a simulation of the Moon. When the user interacts with this Earth affordance, they can return to the context-specific user interface described with reference to Figure 8. In some embodiments, the Earth affordance may be a graphic or stylized representation of the Earth, such as an icon, symbol, or character representation of the Earth. In some embodiments, the Earth affordance may be a photorealistic rendering of the Earth.

[0320] In some embodiments, the device 900 displays six affordances representing the solar system (indicated by affordances 810, 828, 848, 908, and 926) on the user interface screen. In some embodiments, the sixth affordance may be a graphic or stylized representation of the solar system, such as an icon, symbol, or character representation of the solar system. In some embodiments, the sixth affordance may be a realistic rendering of the solar system.

[0321] The device 900 detects contact with the displayed sixth affordance and, in response to this detection, updates the user interface screen display by showing a seventh affordance representing the sun, Earth, and one or more non-Earth planets aligned at their respective positions at the current time, and an eighth affordance indicating the current time. In some embodiments, updating the user interface screen display includes animating a first affordance representing a simulation of a first region of the Earth illuminated by the sun, or an animation of a fourth affordance representing a simulation of the Moon as seen from Earth. This animation allows the user to recognize that the astronomical scale and / or perspective has been changed.

[0322] This shifts the user from viewing information about the current time within this month using a lunar simulation to viewing information about the current time within this year using a solar system simulation. While the context-specific user interface described with reference to Figure 9 provides user-customizable information about the state of the moon, Figure 10 illustrates a context-specific user interface that provides user-customizable information about the solar system and the relative positions of Earth and other planets.

[0323] Figure 10 shows a typical context-specific user interface that can operate on device 1000. Device 1000 may be device 100, 300, or 500 in some embodiments. The electronic device has a touch-sensitive display (touchscreen 504, etc.).

[0324] As described above, device 1000 is device 800 and / or device 900, which have an updated display. Device 1000 displays screen 1002 including a seventh affordance 1004. The seventh affordance 1004 includes representations of the sun 1006, the earth 1008, and the planets Mercury, Venus, and Saturn (for example, Saturn is represented by planet 1010). 1006, 1008, and 1010 are indicated by their respective positions at the current date (in this example, May 25, 2014) as indicated by the eighth affordance 1012. In some embodiments, the eighth affordance 1012 further indicates the current time.

[0325] 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 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, and other astronomical features.

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

[0327] This context-specific user interface allows the user to access information about the positions of Earth and one or more non-terrestrial planets on dates other than the current date, which may be within the current year or a different year. In some embodiments, the sun, Earth, and one or more non-terrestrial planets are depicted as photorealistic renderings. In some embodiments, the sun, Earth, and one or more non-terrestrial planets are depicted as stylized or abstract renderings.

[0328] In some embodiments, the user can rotate a representation of the solar system by swiping on a touch-sensitive display. Thus, in some embodiments, user input may include swiping on a touch-sensitive display. In some embodiments, in response to the detection of a swipe, Earth and one or more non-terrestrial planets are rotated around the sun in a first rotation direction. In some embodiments, the first rotation direction may be based at least in part on a first swipe direction.

[0329] In some embodiments, in response to the detection of a swipe on a touch-sensitive display in a different direction, the device rotates the Earth and one or more non-terrestrial planets around the sun in a second rotational direction different from the first direction. This allows the user to deduce both the rotational direction of the Earth and one or more non-terrestrial planets and the time indicated by the eighth affordance in response to the swipe. For example, the user may swipe in one direction to rotate the Earth and one or more non-terrestrial planets in a predetermined direction and view the Earth and one or more non-terrestrial planets at a later date within (or a different year) of that year, or the user may swipe in another direction to rotate the Earth and one or more non-terrestrial planets in the opposite direction and view the Earth and one or more non-terrestrial planets at an earlier date within (or a different year) of that year.

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

[0331] In some embodiments, the device receives a second user input, and in response to receiving the second user input, the device rotates the Earth and one or more non-Earth planets around the Sun in a second rotational direction different from the first direction. This user input may include, for example, the movement of a rotatable input mechanism in the second rotational direction different from the first rotational direction.

[0332] This allows the user to derive both the rotation direction of Earth and one or more other planets, and the time indicated by the eighth affordance, in accordance with the rotation of the rotatable input mechanism. For example, the user can move the rotatable input mechanism in one direction to rotate Earth and one or more other planets in a predetermined direction and view Earth and one or more other planets at a later time in that year, or the user can move the rotatable input mechanism in another direction to rotate Earth and one or more other planets in the opposite direction and view Earth and one or more other planets at an earlier time in that year.

[0333] 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 representations of the orbits of one or more non-Earth planets around the Sun. The orbital representations may be graphic representations such as lines or rings. In some embodiments, the orbital representations may be stylized. In some embodiments, the orbital representations may be based on the actual dimensions of the planetary orbits around the Sun.

[0334] In some embodiments, a user can contact a touch-sensitive display at a location related to a representation of Earth and one or more non-Earth planets. For example, contact may be in or near a displayed representation of the planet itself, or in or near a displayed representation of the planet's orbit. In some embodiments, the device can determine a selected planet based on the determination of the displayed representation of the planet or the displayed representation of the planet's orbit closest to the contact location. In some embodiments, contact may be a press-and-hold type contact on the display. Upon detection of contact, the device can visually distinguish the representation of the selected planet and / or the representation of the selected planet's orbit (e.g., by changing the color and / or brightness of the displayed planet and / or orbit, by displaying the outline or other visual boundary of the planet and / or orbit, by animating the planet and / or orbit, etc.). In some embodiments, while continuing to receive contact, the device may also determine whether the duration of contact exceeds a predetermined threshold, and according to the determination that the contact has exceeded the predetermined threshold, the device can visually distinguish the representation of the selected planet and / or the representation of the selected planet's orbit. When the user releases contact, the device can display information about the given planet. Such information may include, without limitation, the size of the planet, the distance between the planet and the sun (e.g., current distance, average distance, etc.), the distance between the planet and Earth (if the selected planet is not Earth) (e.g., current distance, average distance, etc.), the time and / or position in the sky when the planet is visible from Earth (if the selected planet is not Earth), the surface temperature of the planet, the number of satellites orbiting the planet, the number and / or identifiers of spacecraft currently orbiting or near the planet, details about the planet (e.g., whether the planet is terrestrial or gaseous, the date of discovery, information about the planet's name, etc.), the time (past, present, or future) of a particular alignment of the planet with other objects in the solar system, etc.

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

[0336] In some embodiments, the user interface screen updates its display to show a simulation of the solar system and then displays affordances indicating the Moon (e.g., 10¹⁶ or 10³⁴) and / or the Earth (e.g., 10¹⁴ or 10³⁐). In some embodiments, the affordances for the Moon and / or Earth may be graphic or stylized representations of the Earth or Moon, such as icons, symbols, or text. In some embodiments, the affordances for the Moon and / or Earth may be photorealistic renderings of the Moon or Earth. When the user interacts with the Earth's affordance, they can return to the context-specific user interface described with reference to Figure 8. When the user interacts with the Moon's affordance, they can return to the context-specific user interface described with reference to Figure 9.

[0337] In some embodiments of the context-specific user interfaces shown in Figures 8 to 10, the user can move (e.g., rotate) a rotatable input mechanism to scroll the displayed time indication forward or backward in time. Naturally, such functionality may be applied to any of the context-specific user interfaces described herein, but for the sake of brevity, this functionality will be described with reference to Figures 8 to 10. Any model is used to map the movement of the rotatable input mechanism to the scrolling distance or speed, such as that described in U.S. Patent Application No. 14 / 476,700, “Crown Input for a Wearable Electronic Device,” filed September 3, 2014, which is incorporated hereby by reference as a whole. For example, acceleration, velocity, etc., can be used to determine the amount of scaling speed of the displayed time indication.

[0338] In some embodiments, the user can move a rotatable input mechanism to scroll the time indications displayed on screens 802, 820, and / or 840. In response to the detection of movement of the rotatable input mechanism (e.g., movement 830), the device can update the displayed representation of the Earth by, for example, simulating the rotation of the Earth, to show the Earth as illuminated by the sun at different times (compare 822 and 842). In some embodiments, the device can update the displayed time indications to show different times (compare 824 and 844). Similarly, as shown in Figure 9, in response to the detection of movement of the input mechanism (e.g., movement 912), the device can also update the displayed simulation of the Moon to show different lunar phases at different times of month (e.g., compare 904 and 922), and / or update the displayed time indications to show different times (e.g., compare 906 and 924). Similarly, as shown in Figure 10, in response to the detection of movement of the rotatable input mechanism (e.g., movement 1018), the device may also update the displayed positions of the Earth and one or more non-terrestrial planets to display different positions relative to the Sun at different time of year (e.g., comparing 1008 and 1010 with 1026 and 1028), or update the displayed time indication to show a different time (e.g., comparing 1012 and 1030). In some embodiments, the representations of the Earth and Moon, and / or the positions of the Earth and one or more non-terrestrial planets, can rotate in one direction based on the direction of movement of the rotatable input mechanism. In some embodiments, the representations of the Earth and Moon, and / or the positions of the Earth and one or more non-terrestrial planets, can rotate at a predetermined speed based on the speed and / or amount of movement of the rotatable input mechanism, for example, according to one of the models referenced above. Naturally, depending on the displayed context-specific user interface, movement of the rotatable input mechanism may cause the displayed time indication to update at different timescales. For example, the context-specific user interface shown in Figure 8 may be updated hourly at the same rate and / or speed, the context-specific user interface shown in Figure 9 may be updated daily or weekly, and the context-specific user interface shown in Figure 10 may be updated monthly or yearly.

[0339] In some embodiments of the context-specific user interface shown in Figures 8 to 10, the device can indicate other global or astronomical features or objects, such as the real-time position of the International Space Station, as described above. In some embodiments, the user can also tap on the display (e.g., a location corresponding to space), and in response to the detection of the tap, the device can provide additional information about other global or astronomical features or objects, such as the number of people currently in space, the number of spacecraft currently in space, and / or their names.

[0340] Figure 11A shows a typical context-specific user interface that can operate on device 1100. In some embodiments, device 1100 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0341] Users may want to observe a given time within the context of daytime and nighttime. For example, a user might want to know the time of dawn or dusk, or access a simple visual indicator of how much time is left until sunset.

[0342] As shown in Figure 11A, the device 1100 displays a user interface screen 1102. The user interface screen 1102 has two parts: a first part 1104 indicating daytime and a second part 1106 indicating nighttime. Furthermore, the screen 1102 displays a user interface object representing a sine wave 1108. The sine wave 1108 may 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 that day. As shown in Figure 11A, the trough of 1108 represents the primes (corresponding to two primes separated by 24 hours), and the peak of 1108 represents noon on that day. The screen 1102 also displays a first affordance 1110, which is displayed along the sine wave 1108 at a position indicating the current time. Furthermore, screen 1102 displays a horizontal line 1112, an optional feature that divides the display into daytime and nighttime sections. As shown in the diagram, the horizontal line 1112 intersects the sine wave 1108 at two points, representing sunrise and sunset. Finally, screen 1102 displays a second affordance 1114 that indicates the current time.

[0343] Throughout the day, 1114 displays the current time (5:30 AM in this example), and the first affordance 1110 progresses along a sine wave. When 1110 is in the daytime portion 1104, the current time is daytime. When 1110 is in the nighttime portion 1106, the current time is nighttime. At 5:30 AM, the first affordance 1110 is still in the nighttime portion of screen 1102, so it is just before dawn. The functionality of this context-specific user interface provides the user with a simple and intuitive way to track the current time and understand, for example, how much time is left until sunset or sunrise. In some embodiments, when the position representing the sun is entirely within the nighttime portion of the display (e.g., 1106), as indicated by the first affordance 1110, the affordance representing the sun appears hollow (ring-shaped, etc.). This further reinforces the user's awareness that it is currently before dawn.

[0344] For example, screen 1120 indicates a second time and includes a first affordance 1122, a sine wave 1124, and a second affordance 1126. As indicated by the second affordance 1126, it is now sunrise at 7:00 AM. The position of the first affordance 1122 along wave 1124 lies between the first and second parts, indicating a transition from night to day. This is further shown on screen 1120 by aligning affordance 1122 with line 1128 that divides the two parts of the display. This is further shown by the appearance of affordance 1122 itself, which is optionally filled in half when the affordance is at a position where it intersects with the first and second parts of the display.

[0345] Screen 1130 displays a third time and includes a first affordance 1132, a sine wave 1134, and a second affordance 1136. As indicated by the second affordance 1136, it is now 2:00 PM. The position of the first affordance 1132 along wave 1134 is in the first part of the display and indicates daytime. This is further depicted by the appearance of affordance 1132 itself, which is optionally filled in when its affordance is entirely in the position of the first part.

[0346] In some embodiments, the colors of the first and / or second parts can indicate daytime (e.g., warm or bright colors) or nighttime (e.g., dark or cool colors). In some embodiments, the first and second parts may be the same color and can represent the current light state. In these embodiments, the user can further indicate the current light state by the sine wave, an optional horizontal line, and / or an optional appearance of the sun's affordance (e.g., filled, half-filled, or hollow). In some embodiments, the sine wave may contain two or more colors, which can indicate the daytime and nighttime parts (e.g., part of the wave in the daytime part may be one color, and part of the wave in the nighttime part may be another color). Furthermore, the two parts may be of any shape (not limited to rectangles). For example, the daytime part may appear as a brightened circle surrounding the sine wave, and the nighttime part may appear as everything around the circle.

[0347] In some embodiments, the device 1100 may have a position sensor (e.g., a GPS sensor 532 and / or a GPS module 135). In these embodiments, the device 1100 can obtain the device's current position from the position sensor and indicate the daytime and nighttime hours at the current position and time by the proportion of the displayed first and second portions. That is, the size of the daytime and nighttime portions of the display is adjusted for the daytime hours at the current position and date. As an example in the figure, if the current position is near the Arctic Circle during summer, the daytime portion may encompass all or almost all of the screen, and all or almost all of the displayed sine waves are in the daytime portion. As another example, if the user moves the Earth in the latitudinal direction, the position of affordances 1110, 1122, or 1132 does not change (e.g.), but the ratio of the daytime and nighttime portions, and the relative amount of sine waves within each, are adjusted to reflect the current position. This provides the user with a more realistic depiction of the time and improves the user interface.

[0348] 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 wave can be flat or have a reduced amplitude to reflect the sun's lower path in the sky at that location and current date (e.g., closer to the winter pole).

[0349] Now, turning our attention to Figure 11B, it shows an example of this context-specific user interface that provides user-interactive functionality and allows the user to view additional day / night information. Figure 11B shows the user interface screen 1140 displayed on the device 1100. Screen 1140 includes a first affordance 1142, which represents the position of the sun at the current time along a sine wave 1144. Screen 1140 further displays a second affordance 1146, which further indicates the current time (10:09 AM). The device 1100 receives user contact indicated by touch 1148 in the displayed first affordance 1142.

[0350] As detected by device 1100, the user touches the first affordance 1142 and drags it along the sine wave to a second position with a continuous gesture (as indicated by touch 1166). Accordingly, as shown on screen 1160, device 1100 displays the first affordance 1162 at the second position along the sine wave 1164. Device 1100 further updates the second affordance 1168 to indicate a time other than the current time. This new time (12:09) corresponds to the time indicated by the second position of affordance 1162. Thus, the user can see the time represented at any position along the sine wave simply by moving affordances 1148 and / or 1166.

[0351] Naturally, contact movement can begin and end at positions on a sine wave, but the movement itself does not need to precisely track the sine wave. In other words, the user does not need to precisely track the contact along the sine wave. The device may simply receive user contact at the first affordance displayed, and while continuing to receive user contact, detect the movement of contact from the first position to the second position without interrupting the user contact on the touch-sensitive display (for example, the user does not lift their finger from the touch-sensitive display).

[0352] In response to the detection of contact at the second position, the device can translate the first affordance on the screen to the second position while tracking the sine wave. Thus, user contact does not need to track the sine wave, but the device still translates the first affordance from the first position to the second position by tracking the first affordance along the sine wave. In some embodiments, the device can continuously update the time as indicated by the second affordance. Alternatively, the device can update the time indicated by the second affordance when continuous contact stops at the second position. In alternative embodiments, after the detection of contact at the first position, the device can translate the first affordance on the screen to the second position on the sine wave in response to the rotation of the rotatable input mechanism.

[0353] Figure 11B illustrates the optional features of this context-specific user interface. As shown on screen 1140, in response to a user touch 1148 on affordance 1142, the device 1100 displays affordances 1150 and 1152, which depict sunrise and sunset, respectively. Affordances 1150 and 1152 are displayed along wave 1144 at two points where the wave intersects the boundary between a first position indicating daytime and a second position indicating nighttime. This boundary, along with an optional horizontal line 1154, defines the boundary on screen 1140. When the horizontal line 1154 is displayed, affordances 1150 and 1152 are displayed at two points where the line 1154 intersects wave 1144. In some embodiments, affordances 1150 and 1152 may further include numerical representations of the sunrise and sunset times for the current day, respectively. In some embodiments, these affordances are displayed even while the device 1100 receives user contact at a second position.

[0354] In response to receiving user contact 1148 at affordance 1142, affordances 1156 and 1158 are also displayed on screen 1140. Affordances 1156 and 1158 are displayed along wave 1144 at positions corresponding to dawn and dusk, respectively. In some embodiments, these affordances are also displayed while the device 1100 receives user contact at a second position. These displayed affordances indicate to the user when the first and last lights occur, and the user can visually assess when they occur or how long ago they occurred by their distance from affordance 1142. In some embodiments, the time of dawn may be astronomical twilight, nautical twilight, or civil twilight. In some embodiments, the time of dusk may be astronomical twilight, nautical twilight, or civil twilight.

[0355] In some embodiments, the device 1100 detects contact, movement of contact, and interruption of contact in the displayed first affordance. In response to detection of interruption of contact, the device may translate the first affordance back to a position indicating the current time, update the second affordance, and indicate the current time. This allows the user to drag the affordance to a predetermined position, see the time indicated for that position, release the contact, and "snap back" to the current position.

[0356] Figure 11C shows another optional feature of this context-specific user interface. In some embodiments, it is desirable to display each element as large as possible for visibility, especially when the user interface screen is displayed on a small-sized display. Screen 1170 displays a first affordance 1172, a sine wave 1174, and a second affordance 1176. As shown in the figure, affordance 1176 intersects with wave 1174. When the current time reaches 2:00, the position of affordance 1182 indicating 2:00 along wave 1184 intersects with the second affordance, as shown in screen 1180. The device 1100 can determine whether the position of the first affordance intersects with the second affordance (e.g., a position where it overlaps with, is obscured by, or appears close to the second affordance). Depending on the decision that the affordances intersect, the device can display the second affordance at a different position on the display where they do not intersect. As shown in screen 1180, the position of affordance 1186 is different from that of 1176 because the relative position of 1176 on the screen intersects with the first affordance 1182. This adjustment allows the device to display an information-rich screen without visual interference between the displayed elements.

[0357] The user can also contact a touch-sensitive display equipped with a touch 1188 on screen 1180. This contact may be anywhere on the display other than, for example, the position of a first affordance representing the sun at the current time. In response to detection of contact, the device 1100 displays screen 1190, which includes sunrise time 1192, sunset time 1194, and affordance 1196, providing non-textual indications of daytime and nighttime. This allows the user to access sunrise and sunset times from any user interface screen.

[0358] The user can also set time reminders through this 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 the detection of movement of the rotatable input mechanism, the device can translate the first affordance to a third position indicating that it is not the current time. The user can contact the first affordance displayed at the third position, and in response to the detection of the contact, the device can set a user reminder for the indicated time.

[0359] For example, the device may display another affordance representing a user prompt and set an alert at the indicated time. The reminder may also be a visual alert. In this example, the device may display a visual alert that appears as the time approaches. Alternatively, the device may continuously display a visual affordance indicating a third position along a sine wave, helping the user understand how far away the indicated time is from the current time. In some embodiments, the user reminder may include an audio alert that notifies the user audibly when the indicated time has been reached or is about to be reached. In some embodiments, the user reminder may include a haptic alert. The device may generate a haptic signal to the user as the indicated time approaches (for example, using a haptic feedback module 133 and a haptic output generator 167).

[0360] These features allow users to further customize this context-specific user interface. Naturally, this feature does not generate specific alerts at predetermined times, but rather allows setting common alerts at times not tied to a specific date. For example, a user might want to be notified of a certain lighting effect, such as sunlight shining through a window, and set a reminder so they can see this effect at the time it occurs. Within the context of daytime / nighttime information, this allows users to customize the user interface to include not only sunrise, sunset, dawn, and dusk, but also any time they wish to specify.

[0361] Figure 12 shows a typical context-specific user interface that can operate on device 1200. In some embodiments, device 1200 may be device 100, 300, or 500. In some embodiments, the electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0362] Users may want to view a specific background image on the user interface screen while preserving the original image as much as possible. Therefore, it is desirable to provide a context-specific user interface that displays the time and / or date not only as an interface object displayed on the image, but also as an interface object that appears to arise from the image itself, maximizing the user's view of the image while still providing visual indication of the time and date. This is especially true when the user interface is displayed on a small-sized display.

[0363] As shown in Figure 12, the device 1200 displays a user interface screen 1202 including a background 1204. The background 1204 is based on an image of a beach. In some embodiments, the image may be a photograph.

[0364] As used herein, according to its technically accepted meaning, the term "background" refers to the background of a user interface screen that is visually distinguishable from text and user interface objects also displayed on the user interface screen. To base a background on an image simply means to display an image as the background of the screen being displayed. In some cases, the image and background may be identical. In other cases, displaying an image as a background may involve modifying one or more aspects of the image to suit the display, such as image size, image cropping, image resolution, etc.

[0365] Furthermore, screen 1202 includes user interface objects 1206 and 1208. 1206 indicates the date (23rd), while 1208 indicates the time (10:09). In some embodiments, the device can indicate the current date and / or current time.

[0366] The displayed background 1204 contains multiple pixels. A subset of these pixels modifies the appearance of the image so that the subset represents one or more of the user interface objects 1206 and 1208. In other words, at least one of these user interface objects is displayed by modifying the background. For example, a subset of pixels can be modified by changing its color and / or intensity.

[0367] In some embodiments, a subset of pixels can be modified by color mixing. In some embodiments, a subset of pixels can be modified by color blurring. In some embodiments, a subset of pixels can be modified by applying a gradient. Importantly, these examples demonstrate that the appearance of a subset of pixels is influenced by both the background image at the location of the user interface object and the user interface object itself. This allows the user to see the image more clearly while maintaining the visibility of the user interface object (since the user interface object is not simply displayed on top of the image and does not obstruct the image).

[0368] In some embodiments, one of the user interface objects 1206 and 1208 is displayed by modifying the background, while the other is displayed independently of the background (e.g., a fixed color and / or intensity not produced by modifying a subset of background pixels). In these embodiments, the device may also 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 this 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 common color at that location. This feature ensures that if one of the user interface objects is a given color, it will be clearly displayed on the background regardless of the appearance of the background color.

[0369] In some embodiments, the background-based image is stored in the device 1200.

[0370] In other embodiments, the background image is stored in an external device, which is coupled to the device 1200 via wireless communication (e.g., Wi-Fi, Bluetooth®, Near Field Communication (NFC), or any other cellular and / or other wireless communication technologies described herein). In these embodiments, before displaying the screen 1202, the device 1200 can receive data representing the background from the external device (via wireless communication). Using this data, the device 1200 can then display the background.

[0371] Optionally, if the image is stored in an external device, the device 1200 can display a background based on the current background of the external device. For example, the device receives data representing the current background from the external device (via wireless communication) and displays a user interface screen containing a background corresponding to the current background of the external device. The device then modifies a subset of background pixels from the external device to represent one or more user interface objects indicating the date and one or more user interface objects indicating the time. In some embodiments, the device 1200 can further modify the background from the external device, particularly if the external device and the device 1200 have different display dimensions and / or resolutions, for example, by changing one or more of the image size, image cropping, image resolution, etc.

[0372] Referring to Figure 12, a user may want to select an image from an image folder and use it as a background. Therefore, the device 1200 can access a folder containing two or more images (e.g., the images shown in screens 1202 and 1210), select a first image, and display a user interface screen that includes a background based on the first image (e.g., background 1204). As described above, this background includes a subset of pixels that are visually modified from the image and represents a user interface object indicating the date (e.g., 1206) and a user interface object indicating the time (e.g., 1208).

[0373] Optionally, as shown in Figure 12, after displaying screen 1202, the device 1200 can receive data representing user input. Accordingly, the 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 containing background 1212 based on the second image. As shown in Figure 12, backgrounds 1204 and 1212 are based on different images, a beach scene and a mountain scene, respectively. This function ensures that when the user decides to change the background being displayed, the device displays a different image than the one displayed before user input.

[0374] As shown in Figure 12, the screen 1210 further includes a user interface object 1214 that indicates the date and a user interface object 1216 that indicates the time. At least one of these user interface objects is displayed by modifying a subset of pixels of the background 1212 at the position of the user interface object to be displayed, as described above. This subset is modified in one of the above ways, such as color mixing, blurring, or gradient. In some embodiments, one of the user interface objects may have a background-independent color, and the device 1200 may modify this color to fit the background as described above. The image on which the background is based may be stored in the device 1200 or in an external device as described above.

[0375] Various user inputs may function as user inputs for changing the background. In some embodiments, user input may be a touch on the display, rotation of a rotatable input mechanism, pressing down and pressing down of a rotatable input mechanism, or a swipe on the display. In some embodiments, user input may be user movement of the electronic device (e.g., if the device is wearable, movement of the device such as raising the user's wrist, or other movement indicating that the user is looking at the display). Preferably, this function allows the device to display a different image each time the display is looked at, providing the user with a customized display each time and improving user interaction with the device. As described above, user movement of the device is detected by using, for example, an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor (e.g., 538), and / or a combination thereof.

[0376] In some embodiments, the user can choose to exclude an image from a folder so that it can no longer be selected as a background. In these examples, the device can receive data representing the user's prohibition of an image from a folder. Such prohibitions can be received via the user interface shown in Figure 12 or via a folder containing two or more images (for example, the folder may include functionality that allows the user to select more images, drag images into the folder, delete images from the folder, and / or prohibit the use of images as a background). In response to the receipt of data, the device can prevent the display of an image as a background in accordance with subsequent user input.

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

[0378] Users may want to see animations displayed on electronic devices in response to their input. Since users may look at electronic devices multiple times a day, especially if they rely on the device for timekeeping, it is desirable to provide a different experience each time they look at the display. This helps maintain the user's interest in and engagement with the electronic device.

[0379] As shown in Figure 13A, at 10:09, in response to the detection of user input 1304, the device 1300 displays the user interface screen 1302. Screen 1302 includes a user interface object 1306 that indicates the time, and a user interface object 1308 that depicts a butterfly. After displaying screen 1302, the device 1300 animates the butterfly 1308 by sequentially displaying three completely different animation sequences. The first animation sequence, shown by the butterfly 1308, depicts a butterfly with its wings open. Next, screen 1310 displays the second animation sequence, depicting a butterfly 1314 flying from right to left across the display. Screen 1310 also displays the user interface object 1312 that indicates the time. Finally, screen 1320 displays the third animation sequence, depicting a butterfly 1324 with its wings closed. Screen 1320 again displays a user interface object 1322 that indicates the time.

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

[0381] The device 1300 then animates the butterfly 1336 by displaying three animation sequences in sequence. The butterfly 1336 on screen 1330 is animated using the same sequence as the butterfly 1308 on screen 1302, showing a butterfly with its wings open. Next, screen 1340 shows the butterfly 1334, which is animated to fly from left to right across the display. The animation sequence for the butterfly 1334 is different from the animation sequence for the butterfly 1314 on screen 1310 (the data representing the sequence for the butterfly 1314 has already been accessed). This ensures that the user sees a different animation compared to the last user input. This variation gives the animated user interface object a random and lively quality, making the animation more realistic and / or engaging for the user.

[0382] Finally, screen 1350 displays a butterfly 1354, which is animated using the same sequence (a butterfly with its wings closed) as butterfly 1324 on screen 1320. Screens 1340 and 1350 further display user interface objects 1342 and 1342 that indicate the time.

[0383] Figures 13A and 13B show two butterflies (1336 and 1308) that are displayed in response to user input. Butterfly 1336 is related to 1308, but they do not need to be identical. 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 related to user interface object 1308, but they may not be identical. 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.).

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

[0385] As can be seen by comparing butterfly 1308 with butterfly 1324, or butterfly 1336 with butterfly 1354, the third animation sequence may be based on the inverse of the first animation sequence. For example, if the first sequence depicts a butterfly with its wings open, the third sequence may depict a butterfly with its wings closed. Since these sequences flank the entire animation sequence from both sides, this feature gives the overall sequence a cohesive feel. In some embodiments, the state of the user interface object at the beginning of the first animation sequence (e.g., butterfly 1308 has its wings closed and is then animated to open them) corresponds to the state of the user interface object at the end of the third animation sequence (e.g., butterfly 1324 is animated to end with its wings closed), giving the user the impression of one seamless animation.

[0386] Various user inputs can function as user inputs for displaying the screen illustrated in Figure 13. In some embodiments, user input may be a touch on the display, rotation of a rotatable input mechanism, pressing down and pressing down of a rotatable input mechanism, or a swipe on the display. In some embodiments, user input may be a user movement of the electronic device (for example, if the device is wearable, a movement of the device such as the user raising their wrist, or other movement indicating that the user is looking at the display). Preferably, this function allows the device to appear to display different animations each time the display is viewed.

[0387] In some embodiments, the user interface objects displayed in response to user input may be the same after each input. In some embodiments, the user interface objects may be different each time. For example, a user interface object can be reflected (e.g., around the horizontal and / or vertical axis), flipped, and / or rotated to generate a new user interface object. This provides a source of variety for the displayed user interface objects and animation sequences. For example, generating four new objects by rotating a single object horizontally, vertically, and horizontally and vertically, and combining these with animations that guide the movement of the objects, generates even more variations. These aspects add possibilities for combination, significantly increasing the number of animations available for a single object and reducing the number of pre-programmed animation sequences. This is further useful for animating objects with less inherent shape and / or movement, such as jellyfish.

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

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

[0390] Figure 14A shows a typical context-specific user interface that can operate on device 1400. In some embodiments, device 1400 may be device 100, 300, or 500. The electronic device has a touch-sensitive display (e.g., touchscreen 504).

[0391] Users may want to manage the time with an interactive clock face. For example, they might want to see animations each time they look at the display, or see a clock face that changes color, in order to maintain their interest in interacting with the device. Users may also want to customize the clock face to include individual complications such as monograms, or individual widgets that display application data.

[0392] As shown in Figure 14A, the device 1400 has a turned-off display 1402. In response to detection of user movement (e.g., motion 1404) of the device 1400, the device 1400 displays an animated indicator of the clock face. On screen 1410, the device 1400 displays the outer perimeter 1412 of the clock face, which is animated to be filled or drawn clockwise. On screen 1420, the device 1400 displays the full outer perimeter 1422 of the clock face and the hour and minute hands 1424. On screen 1430, the device 1400 displays the full outer perimeter 1432 of the clock face, the hour and minute hands 1434, and the time indicators 1436 and 1438 (indicating 12 o'clock and 1 o'clock, respectively). These time indicators are displayed gradually clockwise, as shown by comparing screens 1430 and 1440.

[0393] On screen 1440, the device 1400 displays a 12-hour indicator, as shown by the outer edge of the clock face 1442, the hour and minute hands 1444, and the 12 o'clock indicator 1446. On screen 1450, the device 1400 displays the outer edge of the clock face 1452, the hour and minute hands 1454, the 12-hour indicator (as shown by the 12 o'clock indicator 1456), the minute indicator 1458, and the monogram 1460, which will be described in more detail later. Thus, as illustrated in Figure 14, the clock face is animated to gradually reveal its shape.

[0394] Figure 14A depicts two types of time indications: numerical time indications (e.g., 3, 6, 9, and 12, as shown in time indications 1436, 1446, and 1456) and symbolic time indications (e.g., the displayed markings between the numerical indications on screens 1440 and 1450). Both types of indications can be used individually or in combination. Both types of symbols are used as time indications, but it is not the symbol itself, but its position around the clock face that tells the user what time it indicates. The numbers (or lack thereof) of the hour and / or minute indications can be further customized by the user, which will be discussed in more detail later.

[0395] Figure 14A shows that one or more time indicators appear progressively in a clockwise direction (for example, they can appear continuously in a clockwise direction, as depicted on screens 1430 and 1440). Similarly, the outer edge of the clock can optionally appear in a clockwise direction. This helps to define the user's orientation. Optionally, minute indicators can appear progressively in a clockwise direction. The hour and minute hands (and optionally, the second hand) can be animated radially, etc. (for example, appearing starting from the center of the clock face and extending outward toward the outer edge). In some embodiments, the hour and minute hands can appear first, followed by the hour indicator, and then the minute indicator. In some embodiments, the clock face displays the current time.

[0396] In some embodiments, the clock face may include color. Functions such as the background of the clock face, the outer edge of the clock face, the second hand, hour indicators, minute indicators, hour hand, and minute hand may be displayed in any color. In some embodiments, the device 1400 updates the colors displayed on the clock face over time by continuously changing the colors, and the user recognizes the passage of time by the color changes. These colors may be, for example, the background color, the color of the clock face itself, and / or the color of the second hand (e.g., the entire second hand, or a part of the second hand such as a pointer, dot, or other optional function). As an example, the colors may be repeating color gradients, and the entire cycle may last for one minute, one hour, one day, etc.

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

[0398] In some embodiments, the device 1400 can display complications on the clock face (for example, within the clock face itself or adjacent to the clock face on the display). As used herein, according to its technically permissible meaning, a complication refers to any function of the clock face, rather than something used to indicate the hours and minutes of a given time (e.g., the hands of a clock or hour / minute indicators). For example, affordances are displayed as clock faces. As will be described in more detail below, affordances can also represent applications, and in response to the detection of contact on an affordance, the device 1400 can also activate the application represented by that affordance.

[0399] Referring here to Figure 14A, in some embodiments, the monogram is displayed as a complication. Screen 1450 shows the monogram affordance 1460 displayed as a watch face complication. The device 1400 can receive data representing a name, and in response to receiving that data, generate a monogram and display the monogram as affordance 1460 (in this example, "MJ"). The device 1400 can receive this data from one or more sources, such as stored contact entries, V cards, or images containing monograms (e.g., images taken or uploaded by the user). In some embodiments, the device 1400 has a user interface for monogram editing, which may be the functionality of the user interface described in Figure 14, a separate user interface on the device 1400, or a user interface on an external device communicating wirelessly with the device 1400. Naturally, these aspects (e.g., complications, monograms, and / or colors) may be applied to any of the other context-specific user interfaces described herein. These features enhance the user interface by providing customizable elements that users may want to include to personalize one or more watch faces, thereby improving user interactivity.

[0400] Figure 14B shows a typical user interface screen 14602 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The electronic device has a touch-sensitive display (e.g., a touchscreen 504).

[0401] Users rely on electronic devices to manage time throughout the day. It is increasingly desirable to provide users with interactive user interfaces that facilitate user interaction with personal electronic devices. Character-based user interfaces can improve user interaction with devices by indicating the time. Increasing the level of character interactivity and enhancing the impression of natural movement displayed by the characters improves the characters' lifelike appearance, thereby improving and extending user interaction with the device. Character-based interfaces can improve user interaction with devices by conveying a more lifelike user interface by providing information related to other events in addition to managing the time.

[0402] Accordingly, this specification provides context-specific user interfaces that include character user interface objects. Users may want to give such character-based user interface objects a more natural and lifelike appearance. Furthermore, users may want character-based user interface objects to behave more dynamically, interact with the user, and provide the user with event-related information.

[0403] The device 14000 can display character user interface objects such as character user interface object 14604 on the display. Character user interface object 14604 has representations of limbs 14606 and 14608. As shown in the user interface screen 14602, character user interface object 14604 can indicate a time, such as 7:50, by the positions of limbs 14606 and 14608.

[0404] A character user interface object may include any representation of a character, such as a human or an anthropomorphic character. In some embodiments, the character may be a cartoon character. In some embodiments, the character may be a realistic human being. In some embodiments, the character may be a human, animal, plant, other living thing, or other object. In some embodiments, the character may be a general character such as a cartoon character.

[0405] The character user interface object 14604 can indicate the time of day by indicating the hour with a first limb (e.g., limb 14606) and the minute with a second limb (e.g., limb 14608). In some embodiments, the character user interface object may be a still image that can be updated to different times of day. In some embodiments, the character user interface object may be animated to depict movement. For example, the character user interface object may be animated to express blinking, weight shifts, and / or changes in facial expression (e.g., facial expressions).

[0406] As described herein, character user interface objects can indicate the time by varying the precision. As shown in Figure 14B, a user interface screen may include one or more numerical indications of time values, i.e., numbers indicating the value of hours, minutes, or seconds on a clock face. However, numerical indications of time values ​​are optional, as users are accustomed to recognizing clock faces, and the relative positions of two objects resembling clock hands can indicate the approximate time even without such numerical indications.

[0407] Any user interface screen described herein may include one or more complications, such as a date indicator, stopwatch, chronograph, or alarm.

[0408] Furthermore, the limbs of a character user interface object can indicate the time to the user in various ways. For example, a limb (such as an arm or leg) can indicate the time by its relative position on the display, or by "pointing" to a position on the display along a vector. A limb can also indicate the time by displaying a direction indicator, such as a finger, which indicates the position on the display corresponding to the time by its relative position, or, as described above, by pointing along a vector. The limb does not need to be precise in indicating the time.

[0409] The device 14000 may indicate a second time by updating the character user interface object and reversing the roles of the first and second limbs, that is, by having the second limb indicate a second hour and the first limb indicate a second minute. For example, Figure 14B shows a user interface screen 14610 that the device 14000 can display. 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 it represents a different time.

[0410] As shown in user interface screen 14610, the character user interface object 14612 indicates a time, such as 8:20, by the positions of its limbs 14614 and 14616. Comparing character user interface objects 14604 and 14612, both have first limbs (limbs 14606 and 14614, respectively) and second limbs (limbs 14608 and 14616). However, the first limb (limb 14606) of character user interface object 14604 indicates the hour, while the first limb (limb 14614) of character user interface object 14612 indicates the minute. Similarly, the second limb (limbs 14608) of character user interface object 14604 indicates minutes, and the second limb (limbs 14616) of character user interface object 14612 indicates hours.

[0411] In some embodiments, the device 14000 can display a second time by updating a user interface object, extending a first limb and retracting a second limb. Since users may be accustomed to standard clock faces where the hour hand is shorter than the minute hand, changing the expansion / contraction of the limbs when their roles are reversed makes it easier for the user to follow the indicated time.

[0412] Allowing a character user interface object to indicate the time using limbs with opposite roles improves the flexibility of displaying the character user interface object by ensuring the character always maintains a natural appearance. Alternatively, if the roles of the limbs are fixed, the character may be awkwardly twisted between predetermined times, for example, 12:30 and 12:40. By allowing the character to switch the roles of its limbs, more options are given to the character's posture and position, allowing for a more natural appearance and thereby improving user interaction with the device by depicting a more lifelike character user interface object.

[0413] Referring to Figure 14C, users may want to interact with character user interface objects that appear more naturally. If a character user interface object indicates time using limbs that are constantly moving from a fixed position or role, this detracts from the character's natural appearance because it limits the range of the character's movement and / or posture. This can result in awkward postures and / or a monotonous character appearance. Limbs can indicate time through animation that represents free movement from both ends of the limbs, rather than rotation around an axis, so that one endpoint is always fixed and the character user interface object appears more naturally at different times.

[0414] Naturally, the mechanical movements used herein (e.g., limb movements) include the display of representations or simulations of mechanical movements.

[0415] Figure 14C shows a typical user interface screen 14702 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5).

[0416] The device 14000 can display character user interface objects, such as character user interface object 14704, on the display. The character user interface object 14704 has a representation of limbs 14706. As shown in the user interface screen 14702, the character user interface object 14704 can indicate a time, such as 12, by the position of the limbs 14706. In some embodiments, the character user interface object may be a still image that can be updated to different times. In some embodiments, the character user interface object can be animated to depict movement.

[0417] The limb portion 14706 has a first endpoint 14708 at a first position, which functions as a representation of the axis of rotation of the limb portion 14706. That is, the position of the limb portion 14706 is displayed or animated to represent rotation around the endpoint 14708 and can display different times. The limb portion 14706 further has a second endpoint 14710 at a second position, which indicates a time value. In some embodiments, the time value may be hours, minutes, and / or seconds.

[0418] 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. Importantly, the first endpoint 14708 functions as the axis of rotation for the limb 14706, but the first endpoint 14708 itself can also be moved to indicate the time. Thus, more flexibility is given to its positioning, allowing the limb 14706 to adopt a more natural posture. This can improve the character's lifelike appearance.

[0419] As an example, user interface screen 14720 shows a character user interface object 14722 comprising a limb 14724 having a first endpoint 14726 and a second endpoint 14728. Character user interface object 14722 may be an updated display of character user interface object 14704. Comparing user interface screens 14702 and 14720, the position of the first endpoint is updated, particularly in limbs 14706 and 14724, so as to be 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, indicating a second time. As shown in user interface screens 14702 and 14720, limb 14706 is updated to limb 14724 by (i) moving the position of the first endpoint and (ii) rotating the limb on the axis of rotation.

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

[0421] As described above, the first and second limbs of the character user interface object may each have two endpoints whose positions can be changed. 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 by each shoulder, so that the position of one shoulder affects the position of the other. This feature adds a lively and natural appearance to the character by coordinating or relating the movement of both limbs, similar to the human body.

[0422] Figure 14D shows a typical user interface screen 14802 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5).

[0423] The device 14000 can display character user interface objects such as character user interface object 14804 on the display. The character user interface object 14804 has a representation of limbs 14806. As shown in the user interface screen 14802, the character user interface object 14804 can indicate the time, for example, 12, by the position of the limbs 14806.

[0424] The limb portion 14806 has a first segment 14808 having a first endpoint 14810 at one end and a joint 14812 at the other. The first endpoint 14810 has a first position. Furthermore, the limb portion 14806 has a second segment 14814 having a second endpoint 14816 at one end and a joint 14812 at the other. Thus, the first segment 14808 and the second segment 14814 are connected by 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 one end of the limb portion 14806) has a second position and indicates a first time value, for example, a time of 12.

[0425] Device 14000 can indicate a second time value by updating the character user interface object 14804 and moving the second endpoint 14814 to a third position along the axis of rotation in order to indicate a second time. In anthropomorphic terms, the limb 14806 has a representation of an upper arm 14808 and a forearm 14814 joined at the elbow 14812. The forearm 14814 can rotate at the elbow 14812 to indicate different times. Adding joints to a limb that indicates time is analogous to the hands of a clock, however, because it includes joints, the arm appears more naturally than the hands of a clock. Furthermore, the joints expand the potential range of movement that can be depicted by the limb.

[0426] The user interface screen 14820 demonstrates this by displaying a character user interface object 14822 comprising a limb portion 14824. In some embodiments, the character user interface object is the same object as the character user interface object 14804, but may be in a different orientation. The limb portion 14824 has a first endpoint 14826, a first segment 14828, and a joint portion 14830. The joint portion 14830 is connected to a second segment 14832, which has a second endpoint 14824. As can be seen by comparing the features of character user interface objects 14804 and 14822, the second endpoint 14834 is in a different position from the second endpoint 14816 and therefore indicates a different time. This change in position is achieved by the rotation of the second segment at the joint portion.

[0427] In some embodiments, moving the second endpoint may include drawing still images of the second endpoint at the first and third positions. In some embodiments, moving the second endpoint may include animating a character user interface object to translate the movement of the second endpoint on the screen.

[0428] In some embodiments, updating a character user interface object may include moving a first endpoint. The first endpoint 14810 may be moved as shown in user interface screen 14802 relative to user interface screen 14820, and the time display may be changed, for example, as shown in first endpoint 14826. Thus, if a character user interface object has limbs, and in the case of an arm as described above, the upper arm may be rotated at the shoulder, the shoulder itself may be moved, or the forearm may be rotated at the elbow.

[0429] These features allow character user interface objects to adopt a wider range of natural and lifelike postures to indicate the time. Animating these features on screen allows the characters to simulate the movement of moving shapes such as humans. This significantly improves user interaction and connection with the device by more accurately simulating the movement of moving shapes such as humans. This enables both subtle and large movements, giving the characters a wide range of expressions and helping to simulate the characters' personalities. Thus, the characters cease to be a simple collection of two character-like hour hands that can only tell the time, and become more practical characters that can express personalities, improving the user experience with the device.

[0430] In some embodiments, the character user interface objects (e.g., character user interface objects 14804 and / or 14822) further include a representation of a second limb, such as a second limb 14818 as shown in user interface screen 14802, or a second limb 14836 as shown in user interface screen 14820. As described above with reference to the first limb, the second limb may include a first segment connecting the first endpoint of the second limb to a joint, and a second segment connecting the second segment 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 functions as the axis of rotation of the second segment and can indicate a third time value. The device 14000 can update the character user interface object by moving the second endpoint of the second limb along the rotation axis at the joint to indicate a fourth time value.

[0431] In some embodiments, the first limb indicates the hours and the second limb indicates the minutes. The first and second limbs are distinguished by length, for example, as with existing hour hands. The first and second limbs are distinguished by distance, for example, between the first endpoint and the second endpoint. For example, one limb may be curved or its shoulder positioned so that it appears shorter or is distinguishable from the other limb, even if it is not shorter than the other limb. The first and second limbs are distinguished by distance, for example, between the second endpoint and another object on the display, such as a numerical indication of the time.

[0432] In some embodiments, updating a character user interface object to indicate a second time point may involve animating the character user interface object by translating the first endpoint on the screen. For example, the character may appear to move one or the other shoulder. In some embodiments, the movement or position of one shoulder may affect the movement or position of the other shoulder, simulating the connected movement of a real shape such as a human.

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

[0434] In some embodiments, the character user interface object may be translated across the screen, for example, toward the center of the display.

[0435] Figure 14E shows a typical user interface screen 14902 that device 14000 can display on its display. In some embodiments, device 14000 may be one or more of devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). Device 14000 can display character user interface objects such as character user interface object 14904 on its display. User interface screen 14902 shows the translation of a character by successively displaying the character user interface object 14904 at two different positions, first at position 14906 and then at 14908. At position 14908, the character user interface object 14904 moves closer to the center of the display, simulating movement from right to left, as shown in Figure 14E. Such movement is used, for example, when a user initiates interaction with the device or looks at the device, to move the character to the center of the display and indicate the time.

[0436] In some embodiments, translating a character user interface object may include animating the character user interface object to represent, for example, walking to the center of the display. Character user interface object 14904 is represented by depicting a character having legs and a torso. Different positions and postures at positions 14906 and 14908 represented by the legs and torso of character user interface object 14904 represent walking. For example, in response to user interaction with the device, the character may be animated to walk naturally on the screen and take a position corresponding to the current time. User interaction may include activating the screen, raising the device to an observation position, pressing a button on the device corresponding to activating the clock face, etc.

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

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

[0439] In some embodiments, the device 14000 can animate character user interface objects to represent the responses of the character user interface objects to changes in visual aspect. As shown in a typical embodiment in Figure 14F, the character user interface object 15004 may be animated to simulate looking at the spotlight 15006.

[0440] Figure 14G shows a typical user interface screen 15102 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects such as character user interface object 15104 on its display. The character user interface object 15104 may include a representation of a foot 15106. In some embodiments, the character user interface object 15104 includes two limbs indicating time values ​​and two legs, at least one of which may include a foot.

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

[0442] In some embodiments, the first and second times 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 shift its posture without changing the indicated time.

[0443] In some embodiments, the display may include one or more numerical indicators of the time. For example, the display may include a representation of a circular clock face, and the central character user interface object may be surrounded by numerical indicators, similar to a clock.

[0444] The features described above allow character user interface objects to appear more natural and lifelike by incorporating a wider range of natural movements while indicating the time. Users may want to see other events represented by character user interface objects. Making character user interface objects responsive to external stimuli or internal system events results in more interactive characters and a more personal portrayal. The improved interactivity of characters further enhances user interaction with the device by providing additional notifications that events have occurred that would otherwise not be apparent. While character user interface objects are useful for providing notifications, reminders, and / or other information that users may want to access from their personal electronic devices, the use of characters provides an interactive personality that the device can use to deliver these items. Furthermore, making characters respond to internal system events (e.g., calendar events) means that characters are not strictly limited to responding to external user input. In other words, characters appear to have a more lifelike personality because they respond to events that are not directly prompted by immediate user actions.

[0445] Figure 14H shows a typical user interface screen 15202 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects on its display, such as character user interface object 15204. The character user interface object 15204 indicates the time as described above.

[0446] Device 14000 can receive first data indicating an event. Device 14000 can determine whether the event meets the conditions. In accordance with the determination that the event meets the conditions, device 14000 can update the character user interface object 15204 by displaying the character user interface object.

[0447] In some embodiments, after updating the displayed character user interface object, the character user interface object still indicates the time. For example, the character's appearance or posture may be changed, but the character still indicates the time.

[0448] In some embodiments, after updating the displayed character user interface object, the character user interface object no longer only indicates the time. For example, the character may adopt a posture, make facial expressions, or use its limbs for functions other than indicating the time, such as conveying meaning related to events and / or conditions.

[0449] In some embodiments, the first data indicates a calendar event. Device 14000 can receive data indicating a calendar event, for example, by obtaining data representing the event from a calendar application on Device 14000. In this example, the condition may correspond to 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 can 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 concurrent with the calendar event, but slightly preceding or slightly following).

[0450] A typical embodiment is shown in user interface screen 15202. In some embodiments, the calendar event is a birthday. In some embodiments, the birthday is the user's birthday. In some embodiments, updating the displayed character user interface object may include animating the character user interface object to display a birthday greeting. The character user interface object 15204 is animated to display a festive hat 15206 and a birthday banner 15208. This animation serves to make the character more interactive while notifying the user of the birthday. Importantly, the character changes its visual aspect, such as displaying a birthday greeting without immediate input from the user, giving the impression that the character can act more autonomously, along with its personality. In some embodiments, the character modification is a directive for several important events related to one of the user's contacts, such as a birthday or anniversary.

[0451] A typical embodiment is shown in user interface screen 15210. In some embodiments, the calendar event is a holiday. In some embodiments, updating the displayed character user interface object may include changing the visual aspect of the character user interface object to reflect the holiday. In this example, the character user interface object 15212 depicts this with a Santa Claus hat 15214. This animation serves to make the character more interactive and reduce the monotony of the character's appearance while informing the user of the holiday. Other examples of holidays besides Christmas may include New Year's Eve, New Year's Day, Thanksgiving, Hanukkah, Independence Day, St. Patrick's Day, Valentine's Day, etc.

[0452] In some embodiments, the device 14000 can receive data indicating user preferences, such as the user's favorite sports team. Upon receiving this data, the device 14000 can update the character user interface object 15204 by changing the visual aspect of the character user interface object to reflect the sports team. For example, the appearance of the character user interface object can be updated to depict the character user interface object wearing a uniform or other personal belongings representing the sports team (e.g., a hat, jersey, uniform, or other representation including a logo, icon, or text representing the sports team). Furthermore, the display may include a second user interface object that updates to represent sports objects related to the team's sport (e.g., a baseball bat and / or ball, football, basketball, soccer ball, hockey stick and puck, checkered flag, etc.). The character can be updated according to a decision that the team is playing on that day or at that time, or according to a decision that the user is participating in an event featuring the team. The determination that a user is participating in an event featuring their team is made by analyzing the user's calendar events or by determining whether an electronic ticket for the event exists on an electronic device or a pair of electronic devices. Naturally, a user's favorite sports team is just a typical user preference, and other user preferences such as the representation of a flag or country are also expected.

[0453] Figure 14I shows a typical user interface screen 15302 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects on its display, such as character user interface object 15304. The character user interface object 15304 indicates the time as described above.

[0454] Device 14000 can receive data that instructs a notification. The notification may include, for example, an email, text message, reminder, virtual assistant request, or other such notification. Device 14000 can further display a user interface object on the user interface screen 15302 that represents the notification, or affordance, or the receipt and / or content of the notification, as depicted by notification 15306. Device 14000 can animate a character user interface object 15304 to react to notification 15306. For example, as shown on the user interface screen 15302, the character user interface screen 15304 may appear to look at notification 15306. This can include, for example, a change in posture or a change in the character's appearance, such as its face, to indicate that it is looking in the direction of the notification. Again, by providing this change in posture or change in the character's focus, incoming alerts or events that would otherwise be less obvious can be notified to the user.

[0455] Figure 14J shows a typical user interface screen 15402 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects on its display, such as character user interface object 15404. The character user interface object 15404 indicates the time as described above.

[0456] Device 14000 can receive first data indicating a time-off day. The time may include the current time. Device 14000 can determine if the time meets the criteria, for example, by determining whether the time is in the nighttime portion of the day. Device 14000 may change the visual aspect of the character user interface object 15404 to represent nighttime. As shown in the user interface screen 15402, the character user interface object 15404 represents nighttime by depicting a yawn and a candle 15406 being held. In some embodiments, the character user interface object 15404 may be modified to depict wearing nighttime-related clothing, such as pajamas. In some embodiments, the character user interface object is modified to yawn or wear pajamas according to a decision that the user should go to sleep. This decision may be based on, for example, a predetermined time for a person, a recognition of the user's sleep pattern, an indication of an early morning event on the calendar for the next day, or a recognition that the user has been active longer than a predetermined time.

[0457] Figure 14K shows a typical user interface screen 15502 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects on its display, such as character user interface object 15504. The character user interface object 15504 indicates the time as described above.

[0458] The device 14000 can receive data indicating the current time. The device 14000 can determine whether the current time corresponds to a specific hour (e.g., 1:00, 2:00, etc.). The device 14000 determines whether the current time is a specific hour, and if so, can animate a character user interface object to announce the hour in one or more increments. As shown in user interface screen 15502, the character user interface object 15504 announces the current time by drawing a musical note 15506. In some embodiments, the time announcement may include a visual representation of the announcement, such as displaying a user interface object. In some embodiments, the time announcement may include sounds, such as a whistle, chimes, one or more spoken words, or the ringing of a bell.

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

[0460] The device 14000 can receive data indicating the current or forecasted weather. To receive data indicating the current or forecasted weather, the device 14000 can retrieve weather information from an external server. In some embodiments, the device 14000 can retrieve weather information from weather services such as The Weather Channel, Accuweather, The National Weather Service, Yahoo!® Weather, and Weather Underground.

[0461] The device 14000 can determine whether the current or forecasted weather corresponds to one or more predetermined weather conditions. These predetermined weather conditions may be system-defined and may be sunny, or stormy weather such as rain, thunderstorms, wind, or snow. If the device 14000 determines that the current or forecasted weather corresponds to one or more predetermined weather conditions, it can update a character user interface object to reflect the current or forecasted weather. For example, as shown in Figure 14L, the user interface screen 15602 includes a character user interface object 15604 comprising an umbrella 15606 and raindrops 15608. In some embodiments, the device 14000 can display user interface objects to reflect predetermined weather conditions. In some embodiments, the character user interface objects can be animated and react to user interface objects reflecting predetermined weather conditions. As another example, the user interface screen 15610 displays a character user interface object 15612 comprising sunglasses 15614 and a surfboard 15616, as well as a sun 15618.

[0462] Figure 14M shows a typical user interface screen 15702 that the device 14000 can display on its display. In some embodiments, the device 14000 may be one or more of the devices 100 (Figure 1), 300 (Figure 3), and / or 500 (Figure 5). The device 14000 can display character user interface objects on its display, such as character user interface object 15704. The character user interface object 15704 indicates the time as described above.

[0463] The device 14000 can receive data indicating a second electronic device. The device 14000 can determine whether the data corresponds to a threshold proximity between the device 14000 and the secon...

Claims

1. It is a method, In an electronic device having a display, Detecting inputs that correspond to displaying individual user interfaces, including anthropomorphic characters, In response to detecting the aforementioned input, Displaying a first animation representing the first condition, in accordance with the determination that the input is detected while the first condition is met, wherein the first animation includes the anthropomorphic character having a first appearance based on the first condition. A method comprising: displaying a second animation that represents the second condition, different from the first animation, in accordance with the determination that the input is detected while the second condition, different from the first condition, is met, wherein the second animation displays the anthropomorphic character having a second appearance different from the first appearance, and the second appearance is based on the second condition.

2. A method according to claim 1, wherein the first appearance includes a first garment, and the second appearance includes a second garment different from the first garment.

3. A method according to claim 1 or 2, wherein the first appearance includes a first visual aspect relating to a first activity, and the second appearance includes a second visual aspect relating to a second activity that is different from the first visual aspect relating to the first activity.

4. A method according to any one of claims 1 to 3, wherein the first appearance includes a first animation, and the second appearance includes a second animation different from the first animation.

5. A method according to any one of claims 1 to 4, wherein the first appearance includes a first expression, and the second appearance includes a second expression different from the first expression.

6. A method according to any one of claims 1 to 5, wherein the first condition is that the current time is within the duration of a first calendar event.

7. A method according to any one of claims 1 to 6, wherein the first condition includes detecting a notification.

8. A method according to any one of claims 1 to 7, wherein the first condition includes the current weather corresponding to a specified weather condition.

9. A method according to any one of claims 1 to 8, wherein the first condition corresponds to current user activity and the first appearance includes a depiction related to the current user activity.

10. A computer program that causes a computer to perform the method described in any one of claims 1 to 9.

11. It is an electronic device, A memory for storing the computer program described in claim 10, An electronic device comprising one or more processors capable of executing the computer program stored in the memory, wherein the electronic device is configured to communicate with a display.

12. An electronic device configured to communicate with a display, An electronic device comprising means for performing the method described in any one of claims 1 to 9.

Images