PATENT DOCUMENT

Publication Number: US-11073799-B2
Application Number: US-202016918855-A
Country: US
Kind Code: B2

Title: Configuring context-specific user interfaces

Abstract:
Techniques for configuring context-specific user interfaces for use with a portable multifunction device are disclosed. The context-specific user interfaces provide indications of time and, optionally, a variety of additional information. The methods provided herein allow for configuring such user interfaces, e.g., at a first electronic device coupled via wireless communication to a second electronic device. Further disclosed are non-transitory computer-readable storage media, systems, and devices configured to perform the methods described herein.

Claims:
What is claimed is: 
     
       1. A first electronic device, comprising:
 a touch-sensitive display; 
 one or more processors; 
 memory storing one or more programs configured to be executed by the one or more processors, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, and memory, and wherein a library of two or more user interfaces for display on the second electronic device is stored in the memory of the second electronic device, the one or more programs including instructions for:
 displaying on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; 
 receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; 
 in response to receiving the first user input:
 ceasing to display the first user interface screen; and 
 displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; 
 receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and 
 in response to receiving the second user input:
 sending instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
 
 
 
 
     
     
       2. The first electronic device of  claim 1 , the one or more programs further including instructions for, in response to receiving the second user input:
 re-displaying the second user interface screen, wherein the relative positions of the first user interface preview image and the second user interface preview image on the re-displayed second user interface screen reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
     
     
       3. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying an affordance for editing the stored library of user interfaces as part of the first user interface screen, wherein receiving the first user input comprises detecting a contact at the displayed affordance for editing the stored library of user interfaces. 
 
     
     
       4. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after receiving the second user input, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; and 
 re-displaying the first user interface screen, wherein the position of the second user interface preview image on the first user interface screen has shifted relative to the position of the first user interface preview image. 
 
 
     
     
       5. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying a re-ordering affordance in association with the second user interface preview image as part of the second user interface screen. 
 
     
     
       6. The first electronic device of  claim 5 , wherein receiving the second user input corresponding to a user request to order the second user interface before the first user interface comprises:
 detecting a contact at a first position on the display at the re-ordering affordance; 
 while continuing to detect the contact, detecting movement of the contact from the first position to a second position on the display without a break in the contact on the display, wherein the second position on the display is on an opposite side of the displayed first user interface preview image relative to the first position; and 
 in response to detecting the contact at the second position:
 translating the second user interface preview image on-screen in a direction of the movement of the contact; and 
 translating the first user interface preview image on-screen in a direction opposite the movement of the contact, wherein after the translation of the first and the second user interface preview images, the relative positions of the first and the second user interface preview images reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
 
     
     
       7. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
     
     
       8. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying an affordance for revealing an edit option, the affordance for revealing an edit option being displayed in association with the first user interface preview image as part of the second user interface screen; 
 detecting a contact on the display at the affordance for revealing an edit option; and 
 in response to detecting the contact at the affordance for revealing an edit option:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
 
     
     
       9. The first electronic device of  claim 8 , wherein displaying the delete affordance comprises translating the first user interface preview image on-screen. 
     
     
       10. The first electronic device of  claim 7 , the one or more programs further including instructions for, after displaying the delete affordance as part of the second user interface screen:
 detecting a contact on the display at the delete affordance displayed in association with the first user interface preview image; and 
 in response to detecting the contact at the delete affordance:
 removing the displayed first user interface preview image from the second user interface screen; and 
 sending instructions to the second electronic device for removing the first user interface from the stored library. 
 
 
     
     
       11. The first electronic device of  claim 10 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after detecting the contact at the delete affordance, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; 
 re-displaying the first user interface screen, wherein the first user interface screen comprises the first and the second user interface preview images; 
 animating the first user interface preview image to disappear from the display; and 
 after animating the first user interface preview image to disappear from the display, translating the second user interface preview image on-screen to occupy the position of the first user interface preview image before the animation. 
 
 
     
     
       12. The first electronic device of  claim 1 , the one or more programs further including instructions for, while displaying the first user interface screen:
 detecting a swipe on the display at the first or the second user interface preview image; and 
 in response to detecting the swipe:
 scrolling the first and the second user interface preview images to reveal a third user interface preview image, wherein the third user interface preview image represents a third user interface for display on the second electronic device, and wherein the third user interface is part of the stored library. 
 
 
     
     
       13. The first electronic device of  claim 12 , the one or more programs further including instructions for, prior to revealing the third user interface preview image:
 displaying as part of the first user interface screen a partial view of the third user interface preview image. 
 
     
     
       14. The first electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying, as part of the second user interface screen, text indications of the watch face types of the first and the second user interfaces, wherein the indications are displayed in association with the first and the second user interface preview images. 
 
     
     
       15. A non-transitory computer-readable storage medium comprising one or more programs configured to be executed by the one or more processors of a first electronic device with a touch-sensitive display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second electronic device, the one or more programs including instructions for:
 displaying on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; 
 receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; 
 in response to receiving the first user input:
 ceasing to display the first user interface screen; and 
 displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; 
 receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and 
 in response to receiving the second user input:
 sending instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
 
 
 
     
     
       16. A method, comprising:
 at a first electronic device with a touch-sensitive display, one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, and memory, and wherein a library of two or more user interfaces for display on the second electronic device is stored in the memory of the second electronic device: 
 displaying on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; 
 receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; 
 in response to receiving the first user input:
 ceasing to display the first user interface screen; and 
 displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; 
 receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and 
 in response to receiving the second user input:
 sending instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
 
 
 
     
     
       17. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for, in response to receiving the second user input:
 re-displaying the second user interface screen, wherein the relative positions of the first user interface preview image and the second user interface preview image on the re-displayed second user interface screen reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
     
     
       18. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying an affordance for editing the stored library of user interfaces as part of the first user interface screen, wherein receiving the first user input comprises detecting a contact at the displayed affordance for editing the stored library of user interfaces. 
 
     
     
       19. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after receiving the second user input, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; and 
 re-displaying the first user interface screen, wherein the position of the second user interface preview image on the first user interface screen has shifted relative to the position of the first user interface preview image. 
 
 
     
     
       20. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying a re-ordering affordance in association with the second user interface preview image as part of the second user interface screen. 
 
     
     
       21. The non-transitory computer-readable storage medium of  claim 20 , wherein receiving the second user input corresponding to a user request to order the second user interface before the first user interface comprises:
 detecting a contact at a first position on the display at the re-ordering affordance; 
 while continuing to detect the contact, detecting movement of the contact from the first position to a second position on the display without a break in the contact on the display, wherein the second position on the display is on an opposite side of the displayed first user interface preview image relative to the first position; and 
 in response to detecting the contact at the second position:
 translating the second user interface preview image on-screen in a direction of the movement of the contact; and 
 translating the first user interface preview image on-screen in a direction opposite the movement of the contact, wherein after the translation of the first and the second user interface preview images, the relative positions of the first and the second user interface preview images reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
 
     
     
       22. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
     
     
       23. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying an affordance for revealing an edit option, the affordance for revealing an edit option being displayed in association with the first user interface preview image as part of the second user interface screen; 
 detecting a contact on the display at the affordance for revealing an edit option; and 
 in response to detecting the contact at the affordance for revealing an edit option:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
 
     
     
       24. The non-transitory computer-readable storage medium of  claim 23 , wherein displaying the delete affordance comprises translating the first user interface preview image on- screen. 
     
     
       25. The non-transitory computer-readable storage medium of  claim 22 , the one or more programs further including instructions for, after displaying the delete affordance as part of the second user interface screen:
 detecting a contact on the display at the delete affordance displayed in association with the first user interface preview image; and 
 in response to detecting the contact at the delete affordance:
 removing the displayed first user interface preview image from the second user interface screen; and 
 sending instructions to the second electronic device for removing the first user interface from the stored library. 
 
 
     
     
       26. The non-transitory computer-readable storage medium of  claim 25 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after detecting the contact at the delete affordance, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; 
 re-displaying the first user interface screen, wherein the first user interface screen comprises the first and the second user interface preview images; 
 animating the first user interface preview image to disappear from the display; and 
 after animating the first user interface preview image to disappear from the display, translating the second user interface preview image on-screen to occupy the position of the first user interface preview image before the animation. 
 
 
     
     
       27. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for, while displaying the first user interface screen:
 detecting a swipe on the display at the first or the second user interface preview image; and 
 in response to detecting the swipe:
 scrolling the first and the second user interface preview images to reveal a third user interface preview image, wherein the third user interface preview image represents a third user interface for display on the second electronic device, and wherein the third user interface is part of the stored library. 
 
 
     
     
       28. The non-transitory computer-readable storage medium of  claim 27 , the one or more programs further including instructions for, prior to revealing the third user interface preview image:
 displaying as part of the first user interface screen a partial view of the third user interface preview image. 
 
     
     
       29. The non-transitory computer-readable storage medium of  claim 15 , the one or more programs further including instructions for:
 displaying, as part of the second user interface screen, text indications of the watch face types of the first and the second user interfaces, wherein the indications are displayed in association with the first and the second user interface preview images. 
 
     
     
       30. The method of  claim 16 , the one or more programs further including instructions for, in response to receiving the second user input:
 re-displaying the second user interface screen, wherein the relative positions of the first user interface preview image and the second user interface preview image on the re-displayed second user interface screen reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
     
     
       31. The method of  claim 16 , the one or more programs further including instructions for:
 displaying an affordance for editing the stored library of user interfaces as part of the first user interface screen, wherein receiving the first user input comprises detecting a contact at the displayed affordance for editing the stored library of user interfaces. 
 
     
     
       32. The method of  claim 16 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after receiving the second user input, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; and 
 re-displaying the first user interface screen, wherein the position of the second user interface preview image on the first user interface screen has shifted relative to the position of the first user interface preview image. 
 
 
     
     
       33. The method of  claim 16 , the one or more programs further including instructions for:
 displaying a re-ordering affordance in association with the second user interface preview image as part of the second user interface screen. 
 
     
     
       34. The method of  claim 33 , wherein receiving the second user input corresponding to a user request to order the second user interface before the first user interface comprises:
 detecting a contact at a first position on the display at the re-ordering affordance; 
 while continuing to detect the contact, detecting movement of the contact from the first position to a second position on the display without a break in the contact on the display, wherein the second position on the display is on an opposite side of the displayed first user interface preview image relative to the first position; and 
 in response to detecting the contact at the second position:
 translating the second user interface preview image on-screen in a direction of the movement of the contact; and 
 translating the first user interface preview image on-screen in a direction opposite the movement of the contact, wherein after the translation of the first and the second user interface preview images, the relative positions of the first and the second user interface preview images reflect the re-ordering of the second user interface before the first user interface in the stored library. 
 
 
     
     
       35. The method of  claim 16 , the one or more programs further including instructions for:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
     
     
       36. The method of  claim 16 , the one or more programs further including instructions for:
 displaying an affordance for revealing an edit option, the affordance for revealing an edit option being displayed in association with the first user interface preview image as part of the second user interface screen; 
 detecting a contact on the display at the affordance for revealing an edit option; and 
 in response to detecting the contact at the affordance for revealing an edit option:
 displaying a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
 
 
     
     
       37. The method of  claim 36 , wherein displaying the delete affordance comprises translating the first user interface preview image on-screen. 
     
     
       38. The method of  claim 35 , the one or more programs further including instructions for, after displaying the delete affordance as part of the second user interface screen:
 detecting a contact on the display at the delete affordance displayed in association with the first user interface preview image; and 
 in response to detecting the contact at the delete affordance:
 removing the displayed first user interface preview image from the second user interface screen; and 
 sending instructions to the second electronic device for removing the first user interface from the stored library. 
 
 
     
     
       39. The method of  claim 38 , the one or more programs further including instructions for:
 displaying an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; 
 after detecting the contact at the delete affordance, detecting a contact on the display at the affordance for completing editing of the stored library of user interfaces; and 
 in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces:
 ceasing to display the second user interface screen; 
 re-displaying the first user interface screen, wherein the first user interface screen comprises the first and the second user interface preview images; 
 animating the first user interface preview image to disappear from the display; and 
 after animating the first user interface preview image to disappear from the display, translating the second user interface preview image on-screen to occupy the position of the first user interface preview image before the animation. 
 
 
     
     
       40. The method of  claim 16 , the one or more programs further including instructions for, while displaying the first user interface screen:
 detecting a swipe on the display at the first or the second user interface preview image; and 
 in response to detecting the swipe:
 scrolling the first and the second user interface preview images to reveal a third user interface preview image, wherein the third user interface preview image represents a third user interface for display on the second electronic device, and wherein the third user interface is part of the stored library. 
 
 
     
     
       41. The method of  claim 40 , the one or more programs further including instructions for, prior to revealing the third user interface preview image:
 displaying as part of the first user interface screen a partial view of the third user interface preview image. 
 
     
     
       42. The method of  claim 16 , the one or more programs further including instructions for:
 displaying, as part of the second user interface screen, text indications of the watch face types of the first and the second user interfaces, wherein the indications are displayed in association with the first and the second user interface preview images.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 15/418,537, entitled “Configuring Context-Specific User Interfaces,” filed Jan. 27, 2017, which claims priority to U.S. provisional patent application 62/348,902, entitled “Configuring Context-Specific User Interfaces,” filed Jun. 11, 2016, the contents of each of which are hereby incorporated by reference in their entirety. 
     This application relates to the following applications: International Patent Application Serial No. PCT/US2015/034604, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022203; International Patent Application Serial No. PCT/US2015/034606, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022204; International Patent Application Serial No. PCT/US2015/034607, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205; International Patent Application Serial No. PCT/US2015/055165, titled “Device Configuration User Interface,” filed Oct. 12, 2015; International Patent Application Serial No. PCT/US2015/053353, titled “Sharing User-Configurable Graphical Constructs,” filed Sep. 30, 2015; and International Patent Application Serial No. PCT/US2016/021403, titled “Sharing User-Configurable Graphical Constructs,” filed Mar. 8, 2016. The content of these applications is hereby incorporated by reference in their entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to configuring context-specific user interfaces for indicating time, e.g., via wireless communication. 
     BACKGROUND 
     Users rely on portable multifunction devices for keeping time, among a variety of other operations including running software applications. It is desirable to allow the user to access an array of information through a single user interface while keeping the interface simple and intuitive to use. Further, a user may want to access different types of information, such as various aspects related to keeping time, or different application data points, in different contexts. Moreover, different users may find it beneficial to have information (e.g., the same information) presented in different formats and/or arrangements. Modern electronic devices often have many customizable features that can be set by a user according to the user&#39;s preferences. It is therefore also desirable to allow the user to customize the user interface and the types of information provided through the user interface. Modern electronic devices are also capable of communicating with other electronic devices via, for example, wireless communication. The ability to communicate with other devices may allow devices to share information and interact with each other. Thus, there is also an opportunity to provide techniques for establishing communication between devices and to use the communication to improve a configuration process, e.g., for context-specific user interfaces that indicate time. 
     SUMMARY 
     Portable multifunction devices are able to provide many different types of information and interfaces to a user, and a user may wish to configure these user interfaces, and the types of information they provide, in different contexts. Therefore, context-specific user interfaces for keeping time are increasingly desirable. Since some portable multifunction devices have a reduced size display and/or different input modalities as compared to other electronic devices, techniques for configuring user interfaces of a portable multifunction device at another electronic device (e.g., via wireless communication) are also desirable. 
     Some techniques for managing (e.g., editing) context-specific user interfaces for indicating time using electronic devices, however, are generally cumbersome and inefficient. For example, existing techniques use a complex and time-consuming user interface, which may not be suitable for configuring a device with a reduced display size. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices. 
     Accordingly, the present disclosure provides, inter alia, the benefit of portable electronic devices with faster, more efficient methods and interfaces for configuring context-specific user interfaces. Such methods and interfaces optionally complement or replace other methods for configuring context-specific user interfaces. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. Such methods and interfaces may also reduce the number of unnecessary, extraneous, repetitive, and/or redundant inputs, and may create a faster and more efficient user interface arrangement, which may reduce the number of required inputs, reduce processing power, and reduce the amount of time for which user interface(s) need to be displayed in order for desired functions to be accessed and carried out. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In some embodiments, a method of configuring a context-specific user interface comprises, at a first electronic device with a display, one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, a memory, and access to a library of one or more user interfaces for display on the second electronic device: displaying on the display of the first electronic device a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory of the first electronic device. 
     In some embodiments, a method of configuring a context-specific user interface comprises, at a first electronic device with a touch-sensitive display, one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, a memory, and access to a library of one or more user interfaces for display on the second electronic device: displaying on the display of the first electronic device a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second electronic device; detecting a first contact at the displayed first user interface preview image; in response to detecting the first contact: ceasing to display the first user interface screen; and displaying on the display of the first electronic device a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; detecting a second contact at the selection affordance; and in response to detecting the second contact: sending instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     In some embodiments, a method of configuring a context-specific user interface comprises, at a first electronic device with a touch-sensitive display, one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, and memory, and wherein a library of two or more user interfaces for display on the second electronic device is stored in the memory of the second electronic device: displaying on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; in response to receiving the first user input: ceasing to display the first user interface screen; and displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and in response to receiving the second user input: sending instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, a non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory of the first electronic device. 
     In some embodiments, a non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second electronic device; detect a first contact at the displayed first user interface preview image; in response to detecting the first contact: cease to display the first user interface screen; and display on the display of the first electronic device a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; detect a second contact at the selection affordance; and in response to detecting the second contact: send instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     In some embodiments, a non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, and memory, wherein a library of two or more user interfaces for display on the second electronic device is stored in the memory of the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; receive a first user input corresponding to a user request to reorder the stored library of user interfaces; in response to receiving the first user input: cease to display the first user interface screen; and display a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; receive a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and in response to receiving the second user input: send instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, a transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory of the first electronic device. 
     In some embodiments, a transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second electronic device; detect a first contact at the displayed first user interface preview image; in response to detecting the first contact: cease to display the first user interface screen; and display on the display of the first electronic device a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; detect a second contact at the selection affordance; and in response to detecting the second contact: send instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     In some embodiments, a transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device with a display, the one or more processors, and memory, wherein the first electronic device is coupled via wireless communication to a second electronic device with a display, one or more processors, and memory, wherein a library of two or more user interfaces for display on the second electronic device is stored in the memory of the second electronic device, the one or more programs including instructions which, when executed by the one or more processors of the first electronic device, cause the first electronic device to: display on the display of the first electronic device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; receive a first user input corresponding to a user request to reorder the stored library of user interfaces; in response to receiving the first user input: cease to display the first user interface screen; and display a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; receive a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and in response to receiving the second user input: send instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, a device comprises: a display; one or more processors; a memory; and one or more programs, wherein the device is coupled via wireless communication to a second device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second device, and wherein the one or more programs are stored in the memory of the device and configured to be executed by the one or more processors of the device, the one or more programs including instructions for: displaying on the display of the device a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second device that corresponds with an application installed in the memory of the device. 
     In some embodiments, a device comprises: a display; one or more processors; a memory; and one or more programs, wherein the device is coupled via wireless communication to a second device with a display, one or more processors, memory, and access to a library of one or more user interfaces for display on the second device, and wherein the one or more programs are stored in the memory of the device and configured to be executed by the one or more processors of the device, the one or more programs including instructions for: displaying on the display of the device a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second device; detecting a first contact at the displayed first user interface preview image; in response to detecting the first contact: ceasing to display the first user interface screen; and displaying on the display of the first electronic device a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; detecting a second contact at the selection affordance; and in response to detecting the second contact: sending instructions to the second device for displaying the first user interface on the display of the second device. 
     In some embodiments, a device comprises: a display; one or more processors; a memory; and one or more programs, wherein the device is coupled via wireless communication to a second device with a display, one or more processors, and memory, wherein a library of two or more user interfaces for display on the second device is stored in the memory of the second device, and wherein the one or more programs are stored in the memory of the device and configured to be executed by the one or more processors of the device, the one or more programs including instructions for: displaying on the display of the device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second device; receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; in response to receiving the first user input: ceasing to display the first user interface screen; and displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and in response to receiving the second user input: sending instructions to the second device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, a device comprises: means for displaying on a display of the device a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on a second device coupled via wireless communication to the device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second device that corresponds with an application installed in a memory of the device. 
     In some embodiments, a device comprises: means for displaying on a display of the device a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on a second device coupled via wireless communication to the device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in a library of user interfaces for display on the second device, the second device having access to the library; means for detecting a first contact at the displayed first user interface preview image; means responsive at least in part to detecting the first contact for ceasing to display the first user interface screen; means responsive at least in part to detecting the first contact for displaying on the display of the first electronic device a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; means for detecting a second contact at the selection affordance; and means responsive at least in part to detecting the second contact for sending instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     In some embodiments, a device comprises: means for displaying on a display of a first device a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on a second device, wherein the device is coupled via wireless communication to the second device, wherein a library of two or more user interfaces for display on the second device is stored in the memory of the second device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device; means for receiving a first user input corresponding to a user request to reorder the stored library of user interfaces; means responsive at least in part to receiving the first user input for ceasing to display the first user interface screen; and means responsive at least in part to receiving the first user input for displaying a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; means for receiving a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and means responsive at least in part to receiving the second user input for sending instructions to the second device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, an electronic device comprises: a display unit; a memory unit; a wireless communications unit, wherein the wireless communications unit couples via wireless communication the electronic device to a second electronic device with a second display unit, a second memory unit, a second processing unit, and an accessing unit configured to provide access to a library of one or more user interfaces for display on the second display unit of the second electronic device; and a processing unit coupled to the display unit, the memory unit, and the wireless communications unit of the electronic device, the processing unit comprising: a display enabling unit configured to enable display, on the display unit, of a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second display unit of the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory unit of the electronic device. 
     In some embodiments, an electronic device comprises: a display unit; a touch-sensitive surface unit; a wireless communications unit, wherein the wireless communications unit couples via wireless communication the electronic device to a second electronic device with a second display unit, a second memory unit, a second processing unit, and an accessing unit configured to provide access to a library of one or more user interfaces for display on the second display unit of the second electronic device; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the wireless communications unit of the electronic device, the processing unit comprising: a display enabling unit configured to enable display, on the display unit, of a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second display unit of the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second display unit of the second electronic device; a detecting unit configured to detect a first contact on the touch-sensitive surface unit at the displayed first user interface preview image; wherein the display enabling unit is further configured to, in response to detecting the first contact, enable ceasing of the display, on the display unit, of the first user interface screen; wherein the display enabling unit is further configured to, in response to detecting the first contact, enable display, on the display unit, of a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; wherein the detecting unit is further configured to detect a second contact on the touch-sensitive surface unit at the selection affordance; and a sending unit configured to send, via the wireless communications unit and in response to detecting the second contact, instructions to the second electronic device for displaying the first user interface on the second display unit of the second electronic device. 
     In some embodiments, an electronic device comprises: a display unit; a touch-sensitive surface unit; a wireless communications unit, wherein the wireless communications unit couples via wireless communication the electronic device to a second electronic device with a second display unit, a second memory unit, and a second processing unit, wherein a library of one or more user interfaces for display on the second display unit of the second electronic device is stored in the second memory unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the wireless communications unit of the electronic device, the processing unit comprising: a display enabling unit configured to enable display, on the display unit, of a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second display unit of the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second display unit of the second electronic device; a receiving unit configured to receive a first user input corresponding to a user request to reorder the stored library of user interfaces; wherein the display enabling unit is further configured to enable ceasing of the display, on the display unit, of the first user interface screen in response to receiving the first user input; wherein the display enabling unit is further configured to enable display, on the display unit, of a second user interface screen in response to receiving the first user input, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; wherein the receiving unit is further configured to receive a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and a sending unit configured to send, via the wireless communications unit and in response to receiving the second user input, instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. 
     Thus, devices are provided with faster, more efficient methods and interfaces for configuring context-specific user interfaces, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing and/or providing context-specific user interfaces. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG. 1A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. 
         FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. 
         FIG. 2  illustrates a portable multifunction device having a touch screen in accordance with some embodiments. 
         FIG. 3  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. 
         FIG. 4A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG. 4B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG. 5A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG. 5B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIGS. 6A and 6B  illustrate exemplary context-specific user interfaces. 
         FIGS. 7A-7C  illustrate exemplary context-specific user interfaces. 
         FIGS. 8A and 8B  illustrate exemplary context-specific user interfaces. 
         FIGS. 9A and 9B  illustrate exemplary context-specific user interfaces. 
         FIG. 10  illustrates exemplary context-specific user interfaces. 
         FIG. 11  illustrates exemplary electronic devices in accordance with some embodiments. 
         FIG. 12  illustrates exemplary user interfaces for sharing context-specific user interfaces. 
         FIG. 13  illustrates exemplary user interfaces in accordance with some embodiments. 
         FIGS. 14A-14F  illustrate exemplary user interfaces in accordance with some embodiments. 
         FIGS. 15A-15C  illustrate exemplary user interfaces in accordance with some embodiments. 
         FIGS. 16A-16C  illustrate exemplary user interfaces in accordance with some embodiments. 
         FIG. 17  illustrates exemplary user interfaces in accordance with some embodiments. 
         FIG. 18  illustrates exemplary user interfaces in accordance with some embodiments. 
         FIG. 19  illustrates exemplary user interfaces in accordance with some embodiments. 
         FIGS. 20A-20I  illustrate a flow diagram depicting a process for configuring context-specific user interfaces. 
         FIGS. 21A-21D  illustrate a flow diagram depicting a process for configuring context-specific user interfaces. 
         FIGS. 22A-22F  illustrate a flow diagram depicting a process for configuring context-specific user interfaces. 
         FIG. 23  is a functional block diagram of an electronic device in accordance with some embodiments. 
         FIG. 24  is a functional block diagram of an electronic device in accordance with some embodiments. 
         FIG. 25  is a functional block diagram of an electronic device in accordance with some embodiments. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments. 
     There is a need for electronic devices that provide efficient methods and interfaces for providing context-specific user interfaces, e.g., that display the time along with additional information. This is particularly true for portable multifunction devices with reduced-size displays. Providing techniques for configuring context-specific user interfaces for use on such devices at another device conserves display time, processor resources, and battery life for the portable multifunction devices themselves, which are important considerations for these smaller devices. If the other electronic device is a device with a larger display than the reduced-size portable multifunction device, allowing the user to configure a context-specific user interface for use on the smaller device at the larger device allows for larger display sizes, additional input mechanisms, and conserves battery life and processor usage at the smaller device. Such techniques can also reduce the cognitive burden on a user who accesses such interfaces, thereby enhancing productivity. 
     Below,  FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B  provide a description of exemplary devices for performing the techniques for configuring context-specific user interfaces.  FIGS. 6A-19  illustrate exemplary user interfaces for configuring context-specific user interfaces. The user interfaces in the figures are also used to illustrate the processes described below, including the processes in  FIGS. 20A-22F . 
     Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch. 
     The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. 
     The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. 
     The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application. 
     The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user. 
     Attention is now directed toward embodiments of portable devices with touch-sensitive displays.  FIG. 1A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive display system  112  in accordance with some embodiments. Touch-sensitive display  112  is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device  100  includes memory  102  (which optionally includes one or more computer-readable storage mediums), memory controller  122 , one or more processing units (CPUs)  120 , peripherals interface  118 , RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , input/output (I/O) subsystem  106 , other input control devices  116 , and external port  124 . Device  100  optionally includes one or more optical sensors  164 . Device  100  optionally includes one or more contact intensity sensors  165  for detecting intensity of contacts on device  100  (e.g., a touch-sensitive surface such as touch-sensitive display system  112  of device  100 ). Device  100  optionally includes one or more tactile output generators  167  for generating tactile outputs on device  100  (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system  112  of device  100  or touchpad  355  of device  300 ). These components optionally communicate over one or more communication buses or signal lines  103 . 
     As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are 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 units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  100  is only one example of a portable multifunction device, and that device  100  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG. 1A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  102  optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller  122  optionally controls access to memory  102  by other components of device  100 . 
     Peripherals interface  118  can be used to couple input and output peripherals of the device to CPU  120  and memory  102 . The one or more processors  120  run or execute various software programs and/or sets of instructions stored in memory  102  to perform various functions for device  100  and to process data. In some embodiments, peripherals interface  118 , CPU  120 , and memory controller  122  are, optionally, implemented on a single chip, such as chip  104 . In some other embodiments, they are, optionally, implemented on separate chips. 
     RF (radio frequency) circuitry  108  receives and sends RF signals, also called electromagnetic signals. RF circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  108  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  108  optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data is, optionally, retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG. 2 ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input control devices  116 . The other input control devices  116  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG. 2 ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG. 2 ). 
     A quick press of the push button optionally disengages a lock of touch screen  112  or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) optionally turns power to device  100  on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  112 . In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen  112  and display controller  156  optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif. 
     A touch-sensitive display in some embodiments of touch screen  112  is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  112  displays visual output from device  100 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  112  is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  112  optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  optionally also includes one or more optical sensors  164 .  FIG. 1A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical sensor  164  optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device  100 , opposite touch screen display  112  on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  164  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  164  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG. 1A  shows a contact intensity sensor coupled to intensity sensor controller  159  in I/O subsystem  106 . Contact intensity sensor  165  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  165  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ). In some embodiments, at least one contact intensity sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more proximity sensors  166 .  FIG. 1A  shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  is, optionally, coupled to input controller  160  in I/O subsystem  106 . Proximity sensor  166  optionally performs as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen  112  when the multifunction device is placed near the user&#39;s ear (e.g., when the user is making a phone call). 
     Device  100  optionally also includes one or more tactile output generators  167 .  FIG. 1A  shows a tactile output generator coupled to haptic feedback controller  161  in I/O subsystem  106 . Tactile output generator  167  optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  165  receives tactile feedback generation instructions from haptic feedback module  133  and generates tactile outputs on device  100  that are capable of being sensed by a user of device  100 . In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device  100 ) or laterally (e.g., back and forth in the same plane as a surface of device  100 ). In some embodiments, at least one tactile output generator sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more accelerometers  168 .  FIG. 1A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  is, optionally, coupled to an input controller  160  in I/O subsystem  106 . Accelerometer  168  optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  100  optionally includes, in addition to accelerometer(s)  168 , a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) stores device/global internal state  157 , as shown in  FIGS. 1A and 3 . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  126  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/motion module  130  optionally detects contact with touch screen  112  (in conjunction with display controller  156 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  130  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  130  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some embodiments, contact/motion module  130  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  100 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  130  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which is, optionally, a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , IM  141 , browser  147 , and any other application that needs text input). 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  138  for use in location-based dialing; to camera  143  as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Applications  136  optionally include the following modules (or sets of instructions), or a subset or superset thereof:
         Contacts module  137  (sometimes called an address book or contact list);   Telephone module  138 ;   Video conference module  139 ;   E-mail client module  140 ;   Instant messaging (IM) module  141 ;   Workout support module  142 ;   Camera module  143  for still and/or video images;   Image management module  144 ;   Video player module;   Music player module;   Browser module  147 ;   Calendar module  148 ;   Widget modules  149 , which optionally include one or more of: weather widget  149 - 1 , stocks 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 making user-created widgets  149 - 6 ;   Search module  151 ;   Video and music player module  152 , which merges video player module and music player module;   Notes module  153 ;   Map module  154 ; and/or   Online video module  155 .       

     Examples of other applications  136  that are, optionally, stored in memory  102  include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , contacts module  137  are, optionally, used to manage an address book or contact list (e.g., stored in application internal state  192  of contacts module  137  in memory  102  or memory  370 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  138 , video conference module  139 , e-mail  140 , or IM  141 ; and so forth. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , telephone module  138  are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module  137 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , optical sensor  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , text input module  134 , contacts module  137 , and telephone module  138 , video conference module  139  includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , e-mail client module  140  includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module  144 , e-mail client module  140  makes it very easy to create and send e-mails with still or video images taken with camera module  143 . 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , the instant messaging module  141  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 
     In conjunction with RF circuitry  108 , touch screen  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, workout support module  142  includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 
     In conjunction with touch screen  112 , display controller  156 , optical sensor(s)  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , and image management module  144 , camera module  143  includes executable instructions to capture still images or video (including a video stream) and store them into memory  102 , modify characteristics of a still image or video, or delete a still image or video from memory  102 . 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and camera module  143 , image management module  144  includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , browser module  147  includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , e-mail client module  140 , and browser module  147 , calendar module  148  includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , widget modules  149  are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , and dictionary widget  149 - 5 ) or created by the user (e.g., user-created widget  149 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , the widget creator module  150  are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , search module  151  includes executable instructions to search for text, music, sound, image, video, and/or other files in memory  102  that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , and browser module  147 , video and music player module  152  includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen  112  or on an external, connected display via external port  124 ). In some embodiments, device  100  optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , notes module  153  includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , and browser module  147 , map module  154  are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , text input module  134 , e-mail client module  140 , and browser module  147 , online video module  155  includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port  124 ), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module  141 , rather than e-mail client module  140 , is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 
     Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module  152 ,  FIG. 1A ). In some embodiments, memory  102  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  102  optionally stores additional modules and data structures not described above. 
     In some embodiments, device  100  is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  100 , the number of physical input control devices (such as push buttons, dials, and the like) on device  100  is, optionally, reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  100  to a main, home, or root menu from any user interface that is displayed on device  100 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) includes event sorter  170  (e.g., in operating system  126 ) and a respective application  136 - 1  (e.g., any of the aforementioned applications  137 - 151 ,  155 ,  380 - 390 ). 
     Event sorter  170  receives event information and determines the application  136 - 1  and application view  191  of application  136 - 1  to which to deliver the event information. Event sorter  170  includes event monitor  171  and event dispatcher module  174 . In some embodiments, application  136 - 1  includes application internal state  192 , which indicates the current application view(s) displayed on touch-sensitive display  112  when the application is active or executing. In some embodiments, device/global internal state  157  is used by event sorter  170  to determine which application(s) is (are) currently active, and application internal state  192  is used by event sorter  170  to determine application views  191  to which to deliver event information. 
     In some embodiments, application internal state  192  includes additional information, such as one or more of: resume information to be used when application  136 - 1  resumes execution, user interface state information that indicates information being displayed or that is ready for display by application  136 - 1 , a state queue for enabling the user to go back to a prior state or view of application  136 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  171  receives event information from peripherals interface  118 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  112 , as part of a multi-touch gesture). Peripherals interface  118  transmits information it receives from I/O subsystem  106  or a sensor, such as proximity sensor  166 , accelerometer(s)  168 , and/or microphone  113  (through audio circuitry  110 ). Information that peripherals interface  118  receives from I/O subsystem  106  includes information from touch-sensitive display  112  or a touch-sensitive surface. 
     In some embodiments, event monitor  171  sends requests to the peripherals interface  118  at predetermined intervals. In response, peripherals interface  118  transmits event information. In other embodiments, peripherals interface  118  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     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 that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of event recognizers  180 . In other embodiments, one or more of event recognizers  180  are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  optionally utilizes or calls data updater  176 , object updater  177 , or GUI updater  178  to update the application internal state  192 . Alternatively, one or more of the application views  191  include one or more respective event handlers  190 . Also, in some embodiments, one or more of data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective event recognizer  180  receives event information (e.g., event data  179 ) from event sorter  170  and identifies an event from the event information. Event recognizer  180  includes event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which optionally include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event  1  ( 187 - 1 ), event  2  ( 187 - 2 ), and others. In some embodiments, sub-events in an event ( 187 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event  1  ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event  2  ( 187 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  112 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event definition  187  includes a definition of an event for a respective user-interface object. In some embodiments, event comparator  184  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 187 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  188  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module. In some embodiments, object updater  177  creates and updates objects used in application  136 - 1 . For example, object updater  177  creates a new user-interface object or updates the position of a user-interface object. GUI updater  178  updates the GUI. For example, GUI updater  178  prepares display information and sends it to graphics module  132  for display on a touch-sensitive display. 
     In some embodiments, event handler(s)  190  includes or has access to data updater  176 , object updater  177 , and GUI updater  178 . In some embodiments, data updater  176 , object updater  177 , and GUI updater  178  are included in a single module of a respective application  136 - 1  or application view  191 . In other embodiments, they are included in two or more software modules. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  100  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG. 2  illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  optionally also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  is, optionally, used to navigate to any application  136  in a set of applications that are, optionally, executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In some embodiments, device  100  includes touch screen  112 , menu button  204 , push button  206  for powering the device on/off and locking the device, volume adjustment button(s)  208 , subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       FIG. 3  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device  300  need not be portable. In some embodiments, device  300  is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device  300  typically includes one or more processing units (CPUs)  310 , one or more network or other communications interfaces  360 , memory  370 , and one or more communication buses  320  for interconnecting these components. Communication buses  320  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  300  includes input/output (I/O) interface  330  comprising display  340 , which is typically a touch screen display. I/O interface  330  also optionally includes a keyboard and/or mouse (or other pointing device)  350  and touchpad  355 , tactile output generator  357  for generating tactile outputs on device  300  (e.g., similar to tactile output generator(s)  167  described above with reference to  FIG. 1A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG. 1A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 . In some embodiments, memory  370  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  102  of portable multifunction device  100  ( FIG. 1A ), or a subset thereof. Furthermore, memory  370  optionally stores additional programs, modules, and data structures not present in memory  102  of portable multifunction device  100 . For example, memory  370  of device  300  optionally stores drawing module  380 , presentation module  382 , word processing module  384 , website creation module  386 , disk authoring module  388 , and/or spreadsheet module  390 , while memory  102  of portable multifunction device  100  ( FIG. 1A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG. 3  is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory  370  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  370  optionally stores additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device  100 . 
       FIG. 4A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device  300 . In some embodiments, user interface  400  includes the following elements, or a subset or superset thereof:
         Signal strength indicator(s)  402  for wireless communication(s), such as cellular and Wi-Fi signals;   Time  404 ;   Bluetooth indicator  405 ;   Battery status indicator  406 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Messages;”   Icon  426  for calendar module  148 , labeled “Calendar;”   Icon  428  for image management module  144 , labeled “Photos;”   Icon  430  for camera module  143 , labeled “Camera;”   Icon  432  for online video module  155 , labeled “Online Video;”   Icon  434  for stocks widget  149 - 2 , labeled “Stocks;”   Icon  436  for map module  154 , labeled “Maps;”   Icon  438  for weather widget  149 - 1 , labeled “Weather;”   Icon  440  for alarm clock widget  149 - 4 , labeled “Clock;”   Icon  442  for workout support module  142 , labeled “Workout Support;”   Icon  444  for notes module  153 , labeled “Notes;” and   Icon  446  for a settings application or module, labeled “Settings,” which provides access to settings for device  100  and its various applications  136 .   
               

     It should be noted that the icon labels illustrated in  FIG. 4A  are merely exemplary. For example, icon  422  for video and music player module  152  is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG. 4B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG. 3 ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG. 3 ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples that follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG. 4B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) has a primary axis (e.g.,  452  in  FIG. 4B ) that corresponds to a primary axis (e.g.,  453  in  FIG. 4B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG. 4B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG. 4B, 460  corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG. 5A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some embodiments, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS. 1A-4B ). In some embodiments, device  500  has touch-sensitive display screen  504 , hereafter touch screen  504 . Alternatively, or in addition to touch screen  504 , device  500  has a display and a touch-sensitive surface. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  500  has one or more input mechanisms  506  and  508 . Input mechanisms  506  and  508 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  500  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device  500  to be worn by a user. 
       FIG. 5B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS. 1A, 1B, and 3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, intensity sensor  524  (e.g., contact intensity sensor). In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  is, optionally, a button, in some examples. 
     Input mechanism  508  is, optionally, a microphone, in some examples. Personal electronic device  500  optionally includes various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including the processes in  FIGS. 20A-22F . A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG. 5B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS. 1, 3, and 5 ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG. 3  or touch-sensitive surface  451  in  FIG. 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 in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG. 1A  or touch screen  112  in  FIG. 4A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact 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. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices  100 ,  300 , and/or  500 ) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system. 
     As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state  157  and/or application internal state  192 ). An open or executing application is, optionally, any one of the following types of applications:
         an active application, which is currently displayed on a display screen of the device that the application is being used on;   a background application (or background processes), which is not currently displayed, but one or more processes for the application are being processed by one or more processors; and   a suspended or hibernated application, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.       

     As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application. 
     Attention is now directed towards embodiments of configuring context-specific user interfaces and associated processes that may be implemented on a multifunction device with a display and a touch-sensitive surface, such as devices  100 ,  300 , and/or  500  ( FIGS. 1A, 3A , and/or  5 A). 
     The following examples illustrate exemplary embodiments of context-specific user interfaces. Described herein are overall concepts related to customizable context-specific user interfaces. It is noted that the context-specific user interfaces described herein are editable in a number of ways. A user interface may display or otherwise indicate various types of information related to time, and the type(s) of information may be customizable by the user. A user interface may include aspects such as colors, density of display, and complications (or lack of complications) that are also customizable. As used here, consistent with its accepted meaning in art, a complication refers to any clock face feature other than those used to indicate the hours and minutes of a time (e.g., clock hands or hour/minute indications). Complications may provide different types of information to a user, such as data obtained from an application, and the information conveyed to a user by a complication is also customizable, as described below. In some embodiments, a complication may also serve as an affordance for launching an application. 
     While  FIGS. 6A-10  display particular context-specific user interfaces configured according to particular watch face types, these examples are not intended to limit the scope of the present disclosure. Additional descriptions of context-specific user interfaces, as well as features thereof and techniques related thereto, suitable for use in the techniques described herein may be found in International Patent Application Serial No. PCT/US2015/034604, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022203; International Patent Application Serial No. PCT/US2015/034606, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022204; and International Patent Application Serial No. PCT/US2015/034607, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205; each of which is incorporated by reference herein in its entirety. 
     These combinatorial features result in many thousands, if not more, of available context-specific user interfaces. Since describing each of these permutations is not practical, particular aspects are highlighted with particular context-specific user interfaces, but these exemplary descriptions are in no way intended to limit such aspects to such context-specific user interfaces, as specific aspects may be used in other context-specific user interfaces, and specific context-specific user interfaces may have other aspects. These embodiments are meant to illustrate the overall concepts presented, but a skilled artisan will recognize that numerous other embodiments are possible within the scope of the techniques described herein. 
       FIGS. 6A &amp; 6B  show exemplary context-specific user interfaces that may be operated on device  600 . Device  600  may be device  100 ,  300 , or  500  in some embodiments. The electronic device has a display  602  (e.g.,  504 ). In some embodiments, device  600  includes rotatable input mechanism  604  (e.g.,  506 ) and/or input mechanism or button  606  (e.g.,  508 ). 
     In  FIG. 6A , device  600  displays a context-specific user interface on display  602 . This exemplary context-specific user interface includes analog clock  608 . Clock  608  may optionally include a variety of features or aspects that are independently editable or configurable by the user. For example, the user may independently configure an appearance and/or number of indications of hours or minutes, a color (e.g., a color of the seconds hand), and so on. In some embodiments, a complication may be displayed within clock  608  (e.g., a complication that displays data obtained from a calendar application, such as the current date, or a complication that displays a monogram or other customizable text and/or image(s)). 
     In addition, the context-specific user interface also includes four complications,  610 ,  612 ,  614 , and  616 , which are displayed as associated with clock  608 . In some embodiments, one or more of these complications may obtain data and display information from an application. In some embodiments, the displayed information may be updated, e.g., in accordance with updates to data obtained from the application. For example, complication  610  obtains data and displays information from a weather application (e.g., data identifying a sunny weather condition). Similarly, complication  614  obtains data and displays information from a calendar application (e.g., data identifying the date). Complication  612  obtains data and displays information from a social networking application (e.g., a logo or other data obtained from the social networking application, such as a text element), and complication  616  obtains data and displays information from a fitness application for cycling (e.g., a logo or other data obtained from the cycling application, such as fitness data, or a previous or future scheduled ride or workout). 
       FIG. 6B  illustrates another exemplary context-specific user interface displayed on display  602  of device  600 . This screen includes digital clock  624 . It also includes five complications:  626 ,  628 ,  630 ,  632 , and  634 . Like complication  610 , complication  626  obtains data and displays information from a weather application (e.g., data identifying a temperature). Similarly, complication  628  obtains data and displays information from a calendar application (e.g., data identifying the day of the week and date). Complication  630  obtains data and displays information from a social networking application (e.g., a logo or other data obtained from the social networking application, such as a text element), and complication  632  obtains data and displays information from a fitness application for cycling (e.g., a logo or other data obtained from the cycling application, such as fitness data, or a previous or future scheduled ride or workout). Complication  634  also obtains data and displays information from a fitness application for cycling, but, compared to  632 ,  634  displays a different set of information (e.g., a different type and/or amount of content) from the fitness application, including a name of the application and a time, date, and length of a previous cycling workout. 
     The context-specific user interfaces illustrated in  FIGS. 6A &amp; 6B  include a clock, such as analog clock  608  or digital clock  624 . They also include one or more complications (e.g.,  610 ,  612 ,  614 , and  616  in  FIG. 6A or 626, 628, 630, 632, and 634  in  FIG. 6B ). In addition, each of these context-specific user interfaces is configured according to a watch face type. For example, the watch face type illustrated in  FIG. 6A  includes an analog clock and four slots or platters that may be configured by the user to display a complication (e.g., as an affordance representing an application, which in some embodiments may be independently selected by the user). In some embodiments, one or more of these slots or platters may be configured by the user not to display a complication (e.g., to display a blank area or the same content as the background of the user interface). Similarly, the watch face type illustrated in  FIG. 6B  includes a digital clock and five slots or platters that may be configured by the user to display a complication (e.g., as an affordance representing an application, which in some embodiments may be independently selected by the user). In some embodiments, one or more of these slots or platters may be configured by the user not to display a complication (e.g., to display a blank area or the same content as the background of the user interface). In  FIG. 6B , the watch face type includes two different types of complication slots or platters: those illustrated by  626 ,  628 ,  630 , and  632  (e.g., smaller slots that display a first set, type, or amount of application information), and that illustrated by  634  (e.g., a larger slot that displays a second set, type, or amount of application information). As illustrated in  FIG. 6B , a complication representing an application may display a different type or amount of information from the application depending upon whether it is displayed in a small or large complication slot or platter. 
     Turning now to  FIG. 7A , any or all of the context-specific user interfaces described herein may include one or more complications. One type of complication a user may wish to use is a complication for launching an application. For example, the complication may be an affordance representing an application that displays a set of information from the corresponding application. However, a user may wish to view additional information from the application, or launch the full application itself. 
       FIG. 7A  shows exemplary context-specific user interfaces that may be operated on device  700 . Device  700  may be device  100 ,  300 , or  500  in some embodiments. In some embodiments, the electronic device has a touch-sensitive display (e.g., touchscreen  504 ). 
     Device  700  displays user interface screen  702 . Screen  702  includes clock face  704  and affordances  706  and  708 , which are displayed as complications. Affordances  706  and  708  represent applications and include a set of information obtained from the corresponding application. In this example, affordance  706  represents a weather application and displays weather conditions obtained from the weather application. Affordance  708  represents a calendar application and displays the current date obtained from the calendar application. Affordance  706  and affordance  708  are updated in accordance with data from the corresponding application. For example, affordance  706  is updated to display current weather conditions obtained from the weather application. Affordance  708  is updated to display the current date obtained from the calendar application. For example, these complications may be application widgets updated based on application data. 
     To launch the weather application, a user contacts the display at affordance  706  (e.g., touch  710 ). In response, device  700  launches the weather application, which is depicted on screen  720 , and ceases to display screen  702 . Screen  720  shows further weather information, including current weather conditions (e.g., user interface object  722 ), an indication of the current location (e.g., user interface object  724 ), and an indication of the current temperature (e.g., user interface object  726 ). 
       FIG. 7B  also depicts device  700  displaying screen  702 . As depicted in  FIG. 7A , screen  702  includes clock face  704  and affordances  706  and  708 , which are displayed as complications. 
     If a user wishes to launch the calendar application instead of the weather application, the user contacts the display at affordance  708  (e.g., touch  712 ). In response, device  700  launches the calendar application, which is depicted on screen  730 , and ceases to display screen  702 . Screen  730  shows further calendar information, including user interface object  732 , which depicts the full date, and user interface object  734 , which represents a calendar event (in this case, a meeting at 1). 
     In some embodiments, a user interface screen may display a complication that represents an application and includes a set of information obtained from the corresponding application. In some embodiments, as illustrated by  FIGS. 7A and 7B , a user interface screen may display a plurality of complications that represent applications and include sets of information obtained from a plurality of applications, or a plurality of sets of information obtained from a single application. 
     In some embodiments, as described above, a user may move a rotatable input mechanism (e.g.,  604  or  506 ) to scroll a displayed indication of time forward or backward. In some embodiments, the device may display two or more indications of time, and in response to detecting a movement of the rotatable input mechanism, the device may update one or more of the displayed indications of time and keep another indication of time constant. To illustrate using screen  702  in  FIGS. 7A  and B as an example, if affordance  708  represents an indication of current time (e.g., a digital display), the device may update the displayed clock face in response to detecting the movement of the rotatable input mechanism while continuing to display the current time with affordance  708 . The displayed clock face may be updated, for example, by animating a clockwise or counter-clockwise movement of one or more clock hands, depending on whether the displayed time is scrolled forward or backward. 
     In some embodiments, the device updates other displayed complications (e.g., those that do not indicate a time per se) in response to detecting the movement of the rotatable input mechanism. For example, in addition to updating the time displayed by clock face  704 , the device also updates the forecasted or historical weather condition displayed by affordance  706  to correspond with the time indicated by clock face  704 . In these embodiments, the device can forego updating another displayed complication in response to scrolling the displayed time. For example, a displayed stopwatch complication may remain the same while the displayed clock face is updated. In some embodiments, a displayed complication that is not updated in response to detecting the movement of the rotatable input mechanism is visually distinguished, such as by changing a hue, saturation, and/or lightness of the displayed complication. This allows the user to distinguish which complications are updated and which remain constant. 
     Advantageously, these context-specific user interface methods, which may be applied to any of the context-user interfaces described herein simply by including an application complication, allow the user to view updated information from a particular application while also presenting a quick way to launch the corresponding application in the same user interface object. Moreover, the application and/or application information depicted by the complication may further be customized using the editing methods described in reference to  FIG. 10  (see, e.g., screen  1060  and  1070 ). 
     A user may navigate screens on, e.g., a portable multifunction device, that include many affordances. These affordances may represent, for example, applications that may be launched on the device. One such affordance may activate a context-specific user interface, such as those described herein. In order to help the user recognize that a particular affordance corresponds to launching a context-specific user interface, an animation that visually connects the affordance to the interface may be desirable. 
       FIG. 7C  shows an exemplary user interface for editing a clock face that includes more than one complication, such as the ones depicted in  FIGS. 7A and 7B .  FIG. 7C  again depicts device  700  displaying screen  702 , which includes clock face  704 , affordance  706  representing a weather application, and affordance  708  representing a calendar application. 
     As discussed herein in reference to  FIG. 10 , a user customizes the complications displayed on screen  702  by entering clock face edit mode. The user contacts the touch-sensitive display of device  700  with touch  714 . Touch  714  has a characteristic intensity above an intensity threshold, which prompts device  700  to enter a clock face edit mode, shown on screen  740 . Device  700  indicates that the user has entered clock face edit mode by visually distinguishing the clock face. In this example, screen  740  shows a smaller version of the display of screen  702  (e.g.,  742 ), which includes a reduced size clock face, reduced size complication  744 , which is based on complication  706 , and reduced size complication  746 , which is based on complication  708 . 
     A user selects this clock face for editing by contacting displayed clock face  742  (e.g., touch  750 ). In some embodiments, touch  750  is a contact on the touch-sensitive display. In some embodiments, touch  750  is a contact on the touch-sensitive display with a characteristic intensity above an intensity threshold. This causes device  700  to enter into clock face edit mode and display screen  760 . Screen  760  displays clock face  762  for editing. Currently, affordance  764  representing the weather application is selected for editing, as highlighted by outline  766 . Also displayed is positional indicator  768 , which indicates the position of the displayed complication in a series of complication options using line  770 . Positional indicator  768  further indicates to the user that a rotatable input mechanism may be used to cycle through options available for editing affordance  764  (e.g., which set of information from the weather application to display, or another application from which a set of information may be displayed). Paging affordance  772  also displays the position of the aspect of clock face  762  currently selected for editing (i.e., complication  764 ) in a series of editable aspects. 
     Screen  760  also displays affordance  774 , which represents the calendar application. To select this complication for editing, the user contacts displayed affordance  774  (e.g., touch  776 ). In response, device  700  displays screen  780 . Like screen  760 , screen  780  displays clock face  762 , affordance  764  (which represents the weather application), positional indicator  768 , and affordance  774  (which represents the weather application). Affordance  774  is now highlighted for editing, as shown by outline  782 . The position of this complication option is depicted by line  784  in positional indicator  768 . Finally, paging affordance  786  has been updated to display the position of affordance complication  774  in a series of editable aspects of clock face  762 . The user may now edit the set of information displayed by affordance  774  using the rotatable input mechanism (e.g., which set of information from the calendar application to display, or another application from which a set of information may be displayed). In summary, while in clock face edit mode, a user may select a complication for editing when more than one complication is displayed by contacting the displayed complication. In some embodiments, this causes the affordance to be highlighted (e.g., by a visible outline or other means for visibly distinguishing the affordance described herein). 
       FIGS. 8A &amp; 8B  illustrate a different context-specific user interface configured according to a different watch face type.  FIG. 8A  shows exemplary context-specific user interfaces that may be operated 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 ). 
     A user may wish to keep track of the time of day while also accessing a stopwatch function. For example, in contexts such as running or cycling, a user may wish to operate a stopwatch, record laps, and still maintain a view of the time of day. 
     As shown in  FIG. 8A , device  800  displays a clock face that indicates current time, as depicted on user interface screen  802 , on the touch-sensitive display. The clock face includes hour hand and minute hand  804 . The clock face also includes one or more indications of an hourly timescale (e.g., numbers 12, 1, 2, 3, and/or tick marks or other visual indicators displayed at the corresponding positions on the clock face), such as 12 o&#39;clock indicator  806 . The clock face further includes stopwatch hand  808  (which, in some embodiments described below, also serves as a seconds hand. Note that, as used herein, the term seconds hand refers to a hand on a clock face that indicates seconds, not a second hand of two hands on a clock face). 
     As exemplified in  FIG. 8A , device  800  receives user input, which in this case is touch  812  on start affordance  810 . In response, the device replaces the 12 o&#39;clock indicator  806  with stopwatch timescale indicator  824 , as shown on screen  820 . Stopwatch indicator  824  shows that the stopwatch timescale is a 60 second timescale. A timescale for the stopwatch hand may refer to the amount of time needed for the stopwatch hand to complete one full revolution around the displayed clock face. Note that the clock face on screen  820  includes hour hand and minute hand  822  and stopwatch hand  826 , which are the same as hour hand and minute hand  804  and stopwatch hand  808 . 
     Further in response to touch  812 , device  800  animates stopwatch hand  826  to reflect passage of time, as shown by comparing screen  820  and  830 . As shown on screen  830 , the stopwatch hand has moved to a second position on the clock face (note the position of stopwatch hand  836 ), indicating the passage of time. Given that indicator  834  shows that the stopwatch timescale is 60 seconds, the position of stopwatch hand  836  indicates that 25 seconds have passed. As shown in  FIG. 8A , the user accesses this information by touch  840  on lap affordance  838 , which causes the display of time  842 , indicating the time elapsed since touch  812 . Note that hour hand and minute hand  832  are the same as  822  and  804 , and these two hands have not changed position in the last 25 seconds. In this example, the hour hand and minute hand are indicating the same time of day (e.g., 10:10) throughout screens  802 ,  820 , and  830 . 
     Stated another way, the device displays the time of day with the hour hand and the minute hand, and it additionally displays a stopwatch hand. In response to receiving data representing user input, the indication(s) of the hour are replaced with indication(s) of a first timescale of the stopwatch hand, but the hour hand and the minute hand continue to indicate the time of day, even though the hour indication(s) have been replaced. This allows the user to view a stopwatch and the time of day simultaneously, while showing that the stopwatch has started and indicating the timescale for the stopwatch. Also in response to receiving the data, the device animates the stopwatch hand to reflect passage of time. 
     In some embodiments, while animating the stopwatch hand to reflect the passage of time, the device receives second data representing a second user input, and in response to receiving the second data, the device may cease the animation of the stopwatch hand. For example, this may function similar to a “stop” function for the stopwatch. 
     In some embodiments, the device may display on the touch-sensitive display a first affordance representing a start/stop function (e.g., affordance  810 ). The first data representing the first user input (e.g., touch  812 ) and the second data representing the second user input both represent contacts on the displayed first affordance. In other embodiments, the device may display separate affordances for the stopwatch start and stopwatch stop functions. 
     In some embodiments, the device may display on the touch-sensitive display a second affordance representing a lap function (e.g., affordance  838 ). The devices receives third data representing a contact on the displayed second affordance after receiving the first data (e.g., after invoking the start function) and before receiving the second data (e.g., before invoking the stop function). In response to receiving the third data, the device displays a third numerical indication of elapsed time between receiving the first data and receiving the third data. For example, this may function similar to a “lap” function for the stopwatch that causes a display of the time elapsed since invoking the start function. As described above, this feature is illustrated on screen  830 . 
     In some embodiments, the device may display on the touch-sensitive display a third affordance representing a stopwatch application, which is depicted as affordance  814  on screen  802 . The device receives fourth data representing a contact on the displayed third affordance, and in response to receiving the fourth data, the device launches the stopwatch application. This allows the user to access additional information and/or functionality related to the stopwatch feature directly from this context-specific user interface. In one embodiment, the stopwatch application is an application as described in related application: U.S. Provisional Patent Application Ser. No. 62/044,979, filed on Sep. 2, 2014, entitled “Stopwatch and Timer User Interfaces.” 
     In some embodiments, the first timescale for 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 rate based on the first timescale for the stopwatch hand. For example, the stopwatch hand may move faster if the timescale is 3 seconds than if the timescale is 60 seconds. This allows the stopwatch hand to complete a full revolution around the clock face in the amount of time depicted by the first timescale. 
     In some embodiments, the device may substitute the one or more indications of an hourly timescale with an indication of a first timescale for the stopwatch hand by removing the one or more indications of the hourly timescale, displaying the indication of the first timescale for the stopwatch hand, and translating the displayed indication of the first timescale for the stopwatch hand in a rotational motion in a clockwise direction. As an illustrative example, if the display includes 12 numerical indications of hourly timescale, and the first timescale for the stopwatch hand is a 6 second timescale, the device may substitute the 12 numerals with a single 6 numeral. In some embodiments, this may be the same 6 numeral that was previously the indicator for the 6 o&#39;clock hour, such that the substitute and display are not perceptible to the user. The device may display the 6 numerical indicating the first timescale for the stopwatch hand at the 6 o&#39;clock position on the clock face, then translate the 6 in a clockwise motion around the clock face until it arrives at the top of the clock face (formerly the 12 o&#39;clock position), at which point the translation stops. This improves the context-specific interface by reinforcing to the user that the clock face has transitioned from indicating hours and minutes to indicating the first timescale for the stopwatch hand. 
     As illustrated in  FIG. 8B , in some embodiments, the device has a rotatable input mechanism (e.g.,  506 ), which may be used as an optional input to change the stopwatch timescale.  FIG. 8B  shows screen  850  with clock face  852 , which includes hour hand and minute hand  854 , and stopwatch timescale indicator  856  (showing a 60 second timescale). In response to receiving fifth data representing movement of the rotatable input mechanism (e.g., movement  858 ), the device  800  changes the stopwatch timescale to a second timescale, as shown by stopwatch timescale indicator  886 , part of clock face  882  on screen  880 . Note that screen  880  continues to display hour hand and minute hand  884 . The second stopwatch timescale is different from the first stopwatch timescale. This allows the user to customize the timescale for the stopwatch hand through rotating the rotatable input mechanism, allowing for a context-specific user interface depending on the user&#39;s desired stopwatch timescale. 
     In some embodiments, the device substitutes the indication of the first timescale for the stopwatch hand with the indication of the second timescale for the stopwatch hand by removing the indication of the first timescale for the stopwatch hand, displaying the indication of the second timescale for the stopwatch hand, and translating the displayed indication of the second timescale for the stopwatch hand in a rotational motion in a clockwise direction. 
     As shown in  FIG. 8B , indicator of the second timescale for the stopwatch hand  860  is displayed at a position on the clock face that indicates its relative position in the first timescale For example, indicator of a 30 second timescale  860  is displayed on clock face  852  at a position based on the sixty second timescale indicated by  856 . In response to receiving data representing movement  858 , the device removes  856 , displays  860 , and translates  860  in a rotational motion in a clockwise direction until it reaches the former position of the indicator of the first timescale for the stopwatch hand (e.g., (e.g., the former position of 856, as depicted by the position of  886  on clock face  882 ). 
     In some embodiments, after receiving the first data representing the first user input, the device animates the stopwatch hand to represent a rotational motion about an origin and ceases the animation to display the stopwatch hand at a position at π/2 radians (e.g., the 12 o&#39;clock position) relative to the rotational motion about the origin. For example, the stopwatch hand may function as a seconds hand of the clock face before the first data is received. When the first data is received, the seconds hand may be animated to depict a rotation around the clock face (e.g., by rotating about the center point of the clock face) until it resets at the 12 o&#39;clock position. This signals to the user that the seconds hand has now become the stopwatch hand. 
       FIGS. 9A-9B  illustrate yet another context-specific user interface configured according to a different watch face type. 
       FIG. 9A  shows exemplary context-specific user interfaces that may be operated on device  900 . Device  900  may be device  100 ,  300 , or  500  in some embodiments. The electronic device has a touch-sensitive display (e.g., touchscreen  504 ). 
     A user may wish to view a displayed animation on an electronic device in response to an input. Because a user may look at an electronic device many times per day, particularly if the user relies on the device for timekeeping, it may be advantageous to provide the user a different experience each time the display is viewed. This keeps the user interested and engaged with the electronic device. 
     As shown in  FIG. 9A , device  900  displays user interface screen  902  in response to detecting user input  904  at 10:09. Screen  902  includes user interface object  906 , which indicates the time, as well as user interface object  909 , which depicts a butterfly. After displaying screen  902 , device  900  animates butterfly  909  by sequentially displaying three animated sequences that are all different from each other. The first animated sequence is shown by butterfly  909 , which depicts the butterfly opening its wings. Next, screen  910  displays the second animated sequence, which depicts butterfly  914  flying from right to left on the display. Note that screen  910  also displays user interface object  912 , which indicates the time. Finally, screen  920  displays the third animated sequence, which depicts butterfly  924  closing its wings. Screen  920  again displays user interface object  922  indicating the time. 
     Later in the day, as shown in  FIG. 9B , device  930  detects a second user input  932 . In response, device  900  accesses data representing the previously displayed animated sequence (i.e., the sequence shown by butterfly  914 ). Device  900  displays screen  930 . Screen  930  includes user interface object  934 , which indicates the time is now 2:09, and user interface object  936 , which depicts a butterfly. 
     Device  900  then animates butterfly  936  by sequentially displaying three animated sequences. Butterfly  936  on screen  930  is animated using the same sequence as butterfly  909  on screen  902 , showing the butterfly opening its wings. Next, screen  940  shows butterfly  934 , which is animated to fly from left to right on the display. The animated sequence of butterfly  934  is different from the animated sequence of butterfly  914  on screen  910  (data representing the sequence of butterfly  914  had previously been accessed). This ensures that the user will view a different animation, as compared to the last user input. This makes the animation appear more realistic and/or engaging to the user, as this variation imparts a more random, lifelike quality to the animated user interface object. 
     Finally, screen  950  shows butterfly  954 , which is animated using the same sequence (a butterfly closing its wings) as butterfly  924  on screen  920 . Screens  940  and  950  also include user interface objects  942  and  942 , respectively, which indicate the time. 
       FIGS. 9A and 9B  show two butterflies ( 936  and  909 ) that are displayed in response to user inputs. Butterfly  936  is related to  909 , but it need not be identical. In some embodiments, user interface object  936  may be the same as user interface object  909 . In other embodiments, user interface object  936  may be an object related, but not identical, user interface object  909 . 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, and so forth). 
     The animated user interface object may be an animal, such as a butterfly or jellyfish, or it may be a plant, like a flower. In some embodiments, it may be a non-living object, single-celled organism, cartoon, human, and so forth. This context-specific user interface is not limited by the particular animated user interface object. The animated sequences may be specific to the displayed objects. For example, a jellyfish may swim across the screen in various directions, a flower may open, close, or be blown about the wind, and so on. In some embodiments, the animated user interface object may be an emoji, e.g., that wakes up and changes facial expression or one or more facial features upon animation. 
     As illustrated by comparing butterfly  909  to butterfly  924 , or butterfly  936  to butterfly  954 , the third animated sequence may be based on a reverse of the first animated sequence. For example, if the first sequence depicts a butterfly opening its wings, the third sequence may depict a butterfly closing its wings. Since these sequences bookend the full animated sequence, this feature imparts a cohesive feel to the entire sequence. In some embodiments, the state of the user interface object at the beginning of the first animated sequence (e.g., butterfly  909  has closed wings, which are then animated to open) corresponds with the state of the user interface object at the end of the third animated sequence (e.g., butterfly  924  is animated to end on closed wings), thereby providing the user with the impression of one seamless animation. 
     A variety of user inputs may serve as the user input to display the screens exemplified in  FIGS. 9A and 9B  In some embodiments, the user input may be a touch on the display, a rotation of a rotatable input mechanism, a depression of a depressible and rotatable input mechanism, or a swipe on the display. In some embodiments, the user input may be a user movement of the electronic device (e.g., a movement of the device such as raising of the user&#39;s wrist, if the device is wearable, or other movement indicative that the user is viewing the display). Advantageously, this feature enables the device to seemingly display a different animation each time the display is viewed. 
     In some embodiments, the user interface object displayed in response to user input may be the same after each input. In some embodiments, the user interface object could be different each time. For example, a user interface object may be reflected (e.g., about a horizontal and/or a vertical axis), flipped, and/or rotated to create a new user interface object. This is a source of variety for the displayed user interface object and the animated sequences. For example, rotating a single object horizontally, vertically, and horizontally and vertically creates four new objects, which when coupled with an animation that directs the movement of the object creates even more variations. These aspects add combinatorial possibilities which greatly increase the number of available animations for a single object, thus reducing the number of pre-programmed animated sequences. It also helps animate objects with fewer intrinsic features and/or movements, such as a jellyfish. 
     The user may also change the displayed user interface object. For example, device  900  may detect a contact on the touch-sensitive display, and in response, device  900  may substitute the displayed user interface object with a second user interface object. This second user interface object may be related to the first (e.g., the user could select an orange butterfly if the previous one was blue). 
     In some embodiments, as shown in  FIGS. 9A and 9B , the user interface object indicating time may be a representation of a digital clock with numerical indications of an hour and a minute (see, e.g., objects  906 ,  912 ,  922 ,  934 ,  942 , and  952 ). In some embodiments, the user interface object may display the current time in response to user input. 
     The context-specific user interfaces described and illustrated herein provide numerous elements and features that a user may customize, depending upon a particular context. As described, these customizable elements enhance the user interfaces, making them more personal and interactive to the user. 
     At the same time, a user also wants a device that is easy and intuitive to use. Providing a multitude of features only serves to frustrate the user if the user interface does not provide comprehensible ways to edit these features. Described below are user interfaces for editing context-specific user interfaces that provide easy and intuitive methods that facilitate user customization. 
     Importantly, it is to be appreciated that, while particular embodiments such as clock faces may be described with respect to particular editing features, these editing features may also apply to one or more of the other user interfaces described herein. For example, a method for customizing a color of a clock face may be used to change the color of a seconds hand, change an animated object (e.g., a butterfly), or change a clock face background (e.g., a photo or image of a scene). Similarly, methods for customizing complications may be used to add and/or edit various complications on any clock face, regardless of whether an embodiment of that clock face bearing a particular complication was described herein. A skilled artisan will recognize that the methods described below provide user interface functionalities that may be applied to elements and aspects of various context-specific user interfaces in numerous combinations, such that each possible combination would be impossible to elaborate individually. 
     It is to be further appreciated that references to a “clock face” with respect to clock face editing and/or selection as described herein are not in any way limited to a traditional notion of a “clock face,” e.g., a circular display with hour indications and one or more hands to indicate time, or a representation of a digital clock. Any context-specific user interface with an indication of time described herein may properly be termed a clock face. 
     Attention is now directed to  FIG. 10 .  FIG. 10  shows exemplary context-specific user interfaces that may be operated on device  1000 . Device  1000  may be device  100 ,  300 , or  500  in some embodiments. The electronic device has a touch-sensitive display (e.g., touchscreen  504 ) configured to detect the intensity of contacts. Exemplary components for detecting the intensity of contacts, as well as techniques for their detection, have been referenced and described in greater detail above. 
     Device  1000  displays user interface screen  1002 , which includes clock face  1004 . Clock face  1004  also includes complication  1006  that displays a set of information from a weather application (e.g., current weather conditions). In this example, the user wishes to change multiple aspects of clock face  1004 . Specifically, the user decides to change the hour indications on clock face  1004  and complication  1006 . 
     The user contacts the touch-sensitive display of device  1000  with touch  1008 . In some embodiments, touch  1008  is a touch gesture that prompts device  100  to enter a clock face edit mode, such as a touch with a characteristic intensity above an intensity threshold, a touch with a duration above a threshold duration (e.g., a long press or “press and hold”-type user input), and so forth. Touch  1008  has a characteristic intensity above an intensity threshold, which prompts device  1000  to enter a clock face edit mode, shown on screen  1010 . Clock face edit mode allows the user to edit one or more aspects of a clock face. Device  1000  indicates that the user has entered clock face edit mode by visually distinguishing the clock face. In this example, screen  1010  shows a smaller version of the display of screen  1002  (e.g.,  1012 ), which includes reduced size clock face  1014  based on clock face  1004 . Reduced size complication  1016 , which is based on complication  1006 , is also displayed. This display indicates to the user that the user is in clock face edit mode while giving the user an indication of what the edited clock face will look like on the display. In some embodiments, a user may be able to select a different clock face by swiping displayed screen  1010 . In some embodiments, the user may access clock face edit mode and a clock face selection mode through a shared interface. Exemplary descriptions of clock face selection mode are provided in International Patent Application Serial No. PCT/US2015/034607, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205. 
     Screen  1010  also displays paging affordance  1018 . Paging affordances may indicate where the user is within a sequence of options, as well as how many options are available in the sequence. In clock face edit mode, paging affordances may indicate which editable aspect of the clock face a user is editing, where this aspect falls within a sequence of editable aspects, and the total number of editable aspects in the sequence (if clock face selection is available on this screen, paging affordance  1018  may depict the currently selected clock face within a sequence of selectable clock faces and/or clock face options, as described below). A paging affordance may be advantageous in clock face edit mode to help the user navigate the interface and explore all of the editable options available within each type of clock face. 
     The user selects the displayed clock face for editing by contacting  1012  through touch  1020 . In response to detecting touch  1020 , device  1000  visually indicates an element of the clock face for editing. As shown on screen  1030 , the hour indications have been selected for editing, as indicated by outline  1034  around the position of the hour indications. The other elements of the clock face are still retained, as shown by hour hand and minute hand  1032  and complication  1036 . 
     In this example, three aspects of the clock face are available for user editing. This is depicted by paging affordance  1038 . The first editable aspect is the hour indications (e.g., their number and/or appearance). This is relayed to the user by paging affordance  1038 . By viewing outline  1034  in combination with paging affordance  1038 , the user recognizes that the hour indications are the first of three editable aspects of this clock face. 
     Device  1000  also has rotatable input mechanism  1040 . The user may move rotatable input mechanism  1040  to cycle through different options for editing different aspects of the clock face. On screen  1030 , the user may select different options for the hour indications (which are currently editable, as depicted by outline  1034 ) through movement  1042 . Advantageously, using a rotatable input mechanism to cycle through editing options (rather than using, e.g., a touch interaction) frees up touch interactions with the screen to instead provide other functionalities, thus expanding the interactability of the device. Using a rotatable input mechanism is also helpful in cases where smaller elements of the display are being edited, as finer-scale touch gestures may be difficult on a reduced-size display for users with large fingers. 
     Also displayed on screen  1030  is positional indicator  1044 , shown as a column of 9 lines. Positional indicator  1044  is an indicator of a current position along a series of positions. This is may be used, for example, in combination with rotatable input mechanism  1040 . On screen  1030 , positional indicator  1044  indicates to the user the position of the currently selected option (e.g., by line  1046 ) within a series of all selectable options. 
     Upon detecting movement  1042 , device  1000  displays screen  1050 . In response to detecting movement  1042 , device  1000  edits the hour indications, in this case by increasing the number of indications and adding numerals. This is shown by indications  1052 , still highlighted by outline  1034 . The other elements of the clock face, hour hand and minute hand  1032  and complication  1036 , remain the same. Positional indicator  1044  has been updated to indicate the position of this hour indication option, highlighted by line  1054 , within a series of positions of hour indication options. 
     As indicated by paging affordance  1038 , the hour indications are the first editable aspect of this clock face within a sequence of editable aspects. The user may select a second editable aspect by swiping the touch-sensitive display (e.g., swipe  1056 ). In response to detecting the swipe, device  1000  displays screen  1060 . Screen  1060  includes clock face  1062 , which now has 12 hour indications, including 4 numerical indications, as depicted by hour indications  1052 . Note that these hour indications are the hour indications that were selected by the user on the previous screen (see indications  1052 ). Paging affordance  1038  has now been updated to indicate that editing complications is the second editable aspect within the sequence of editable aspects in this clock face. 
     On screen  1060 , complication  1036  is currently editable, as indicated to the user by outline  1064 . Currently, complication  1036  is displaying current weather conditions using information from a weather application. This option is option  3  in a series of options, as indicated by updated positional indicator  1044  and line  1066 . Positional indicator  1044  lets the user know that the currently selected feature (i.e., complication  1036 ) is editable by the rotatable input mechanism. 
     While screen  1060  depicts a single complication, it should be understood that multiple complications may be displayed. When multiple complications are displayed, a user may select a particular complication for editing by contacting the corresponding position of the complication. Outline  1064  then transitions from the previously selected complication or element to the currently selected complication or element and rotatable input mechanism may then be used to edit the complication or element at the selected location. This concept is described in greater detail in reference to  FIGS. 7A-7C . 
     It is to be noted that positional indicator  1044  is displayed on screens  1030 ,  1050 , and  1060 , even though the available options depicted by the indicators are different. A positional indicator may be a universal indicator of options available through a particular type of user input, such as a movement of the rotatable input mechanism. Rather than displaying positions within a particular context, such as editing a certain feature or displaying data from a particular application, a positional indicator shows the user positions available through a type of user input, no matter the particular context in which the user input is being used. This better indicates to the user which user input should be used for this functionality. In some embodiments, a positional indicator is displayed on the display at a position adjacent to the user input for which it is used (e.g., next to the rotatable input mechanism to indicate positions accessible by moving the rotatable input mechanism). 
     A positional indicator (e.g., positional indicator  1044 ) may be responsive to one or more inputs. For example, as shown in  FIG. 10 , the positional indicator  1044  may indicate options available through a movement of the rotatable input mechanism. As described above, the user may scroll through the available options using movement of the rotatable input mechanism. However, a user may also wish to scroll through the available options using a second type of input, such as a contact (e.g., a swipe) on the touch-sensitive display. In some embodiments, a user viewing screen  1030  may swipe the touch-sensitive display in a different direction than the swipe used for removing a visual indication of a first element of the clock face for editing and visually indicating a second element of the clock face for editing (e.g., a downward swipe on the display). For example, to scroll through the available options shown in  FIG. 10 , the user may swipe in a substantially horizontal direction (e.g., swipe  1056 ) to scroll through editable aspects (e.g., with swipes moving left-to-right resulting in scrolling through the sequence of editable aspects in one direction, and swipes moving right-to-left resulting in scrolling through the sequence of editable aspects in a different direction, as depicted by updating the paging affordance  1038 ). In this example, the user may swipe in a substantially vertical direction (e.g., perpendicular to swipe  1056 ) to scroll through available options (e.g., with swipes moving downwards resulting in scrolling through the sequence of available options in one direction, and swipes moving upwards resulting in scrolling through the sequence of available options in a different direction, as depicted by updating the positional indicator  1044 ). In some embodiments, the user may swipe the display at or near the location of the displayed positional indicator to scroll through the sequence of available options. 
     In some embodiments, upon detecting the swipe, the device may update an indicator of position (e.g., an indicator of position along a series of positions that indicates a position of a currently selected option for the editable aspect along a series of selectable options for the editable aspect of the visually indicated element of the clock face) to indicate a second position along the series. In some embodiments, upon detecting the swipe, the device may edit an aspect of the visually indicated element of the clock face. In some embodiments, the device may visually distinguish the positional indicator (e.g., by changing a color, size, shape, animation, or other visual aspect) based on the type of input used to scroll the indicator. For example, in some embodiments, in response to detecting a movement of the rotatable input mechanism, the device may display the positional indicator in a first color (e.g., green), and in some embodiments, in response to detecting a swipe, the device may display the positional indicator in a second color different from the first color (e.g., white). 
     In clock face edit mode depicted on screen  1060 , the user may be able to cycle through different types of information from the weather application, or change the application from which the information is drawn. In this case, the user moves rotatable input mechanism using movement  1068 , which causes device  1000  to display screen  1070 . This updates complication  1036  to display the current date, which is obtained from a calendar application. This option is indicated within positional indicator  1044  by line  1072 . Note that paging affordance  1038  still indicates the second position because the user is still engaged in editing complications, the second editable aspect of this clock face. A determination that the contact has a characteristic intensity above a predetermined threshold may be user to distinguish the contact from other gestures, such as a tap or the beginning of a swipe. 
     Having finished editing the clock face, the user may now exit clock face selection mode and display the edited clock face on the display. In some embodiments, this may be done by detecting a user contact with a characteristic intensity above an intensity threshold. In accordance with a determination that the characteristic intensity is above the intensity threshold, the device may exit clock face edit mode and cease to visually distinguish the displayed clock face for editing (e.g., by increasing the size of the displayed clock face). In some embodiments, in accordance with a determination that the characteristic intensity is above the intensity threshold, the device may save this edited clock face as a new clock face that is accessible through clock face selection mode (described below). In accordance with a determination that the characteristic intensity is not above the intensity threshold (where the clock face includes an affordance representing an application, and where the contact is on the affordance representing the application), the device may launch the application represented by the affordance. 
     In some embodiments, the device may have a rotatable and depressible input mechanism (e.g.,  506 ), and in response to detecting a depression of the rotatable and depressible input mechanism, the device may exit clock face edit mode, display the currently edited clock face, and/or save the currently edited clock face for later user selection, as described above. 
       FIG. 10  illustrates an exemplary embodiment of clock face edit mode, but a number of other potential embodiments are possible within the scope of the techniques described herein. For example, in  FIG. 10 , an element was indicated for editing by visibly distinguishing an outline around the element (e.g., by displaying a visible outline, or by distinguishing a pre-existing outline already visible around the element), as illustrated by outlines  1034  and  1064 . In some embodiments, the outline may be animated to depict a rhythmic expansion and contraction (e.g., animation similar to pulsing or breathing). In some embodiments, the element indicated for editing itself may be animated to depict a rhythmic expansion and contraction. In some embodiments, the element may be animated to depict flashing. In some embodiments, a color of the element may be changed (e.g., a change in color and/or intensity). Any or all of these indications may be used to visually indicate the element that is currently editable. 
     As shown in  FIG. 10 , movement of a rotatable input mechanism may be employed as the user input for editing an aspect of the element indicated for editing. In some embodiments, if an outline is used to indicate the currently editable element, the outline may disappear when the rotatable input mechanism is being moved, and reappear when the movement stops. In this way, the user is able to see what the edited element will look like on the clock face as a whole, without any possible obstruction or distraction from the outline. 
     In some embodiments, in response to detecting the movement, the device may change a color of the element. This could include, e.g., changing a color of a clock face background (e.g., substituting a color if the clock face background is a particular color, or selecting a different image if the clock face background includes an image), changing a color of part or all of a seconds hand (if included on the clock face), changing a color of an hour and/or minute indication, and/or changing a color of a number or colon in the display of a representation of a digital clock. Since a seconds hand is a smaller element than a background (and therefore may be more difficult for the user to perceive), changing the color of the seconds hand may include an animated color change. For example, the seconds hand could first change a color of a particular point (e.g., a dot depicted along the seconds hand), then propagate this color change in either direction along the seconds hand. Alternatively, the color change could begin at the origin of the clock face and propagate outward. Animating a color change, particularly a change of a smaller element of the clock face, may be helpful to draw the user&#39;s attention to the color change. 
     In other embodiments, in response to detecting movement of the rotatable input mechanism, the device may change an aspect of a complication. For example, this could be used to change application data displayed by an application complication. In some embodiments, the complication may indicate a first set of information obtained by an application (e.g., application data. For example, if the application is a weather application, a set of information could be a forecasted weather condition, a current temperature, etc.), and upon editing, the complication could be updated to indicate a second set of information from the same application (e.g., if the application is a weather application, the display could be edited from showing a current temperature to showing current precipitation). In other embodiments, upon editing, the complication could be updated to indicate a set of information from a different application (e.g., if the application is a weather application, the display could be edited from showing weather to showing data from a calendar application, as illustrated by complication  1036 ). 
     In other embodiments, in response to detecting movement of the rotatable input mechanism, the device may change an aspect of display density. For example, as illustrated in  FIG. 10 , this could be used to edit the number of visible divisions of time (e.g., the number of displayed hour and/or minute indications, such as numbers 1-12 or other marks/symbols positioned along the clock face at the hour positions). In response to detecting movement of the rotatable input mechanism, the device may increase or decrease the number of visible divisions of time. As illustrated on screens  1030 ,  1050 , and  1060 , this could involve changing the number of visible divisions (e.g., from 4 to 12) and/or changing the number of numerical/symbolic hour indications (e.g., from 0 to 4). 
     In some embodiments, as illustrated in  FIG. 10 , an indicator of positions along a series of positions may be displayed (e.g., positional indicator  1044 ). In response to detecting movement of the rotatable input mechanism, the device may update the indicator from indicating a first to indicating a second position along the series of positions. In some embodiments, the indicated position may reflect a currently selected option for the currently editable aspect along a series of selectable options for the currently editable aspect. As described above, in some embodiments, the indicator is displayed on the display at a position adjacent to the rotatable input mechanism, thereby strengthening the user&#39;s association between the indicator and the input. In some embodiments, if the currently editable aspect is color, the device may display a positional indicator that includes a series of colors, such that the currently selected color option matches the color of the position currently indicated by the positional indicator (e.g., the color could be a similar or identical color). In some embodiments, the number of positions displayed in a position indicator increases or decreases depending on the number of options for the currently selected editable aspect. 
     In some embodiments, upon reaching the last position indicated by the positional indicator, the device may provide an indication to the user that the last option has been displayed. For example, the device may depict a dimming of one or more of the selected element, an outline around the selected element, and the positional indicator. In some embodiments, the device may animate one or more of the selected element, an outline around the selected element, and the positional indicator to expand and contract (e.g., like a rubber band). In some embodiments, the device may animate one or more of the selected element, an outline around the selected element, and the positional indicator to move on the display (e.g., by bouncing). These features may be advantageous to provide an indication to the user that the last option in the series of options has been reached. 
     In some embodiments, a user may select the element on the clock face for editing by contacting the touch-sensitive display at the position of the displayed element. In other embodiments, the element may be selected by swiping the touch-sensitive display, or rotating the rotatable input mechanism. Regardless of the input, selecting a second element for editing may involve removing a visual indication from the previous element and visually indicating a second element for editing (visually indicating may include any or all of the techniques described above). 
     In some embodiments, if the element selected for editing is indicated by an outline around the element, changing an element for editing could involve translating the outline on-screen away from the first element and/or translating a visible on-screen in a continuous on-screen movement towards the second element until the outline is displayed around the second element. 
     As illustrated in  FIG. 10 , clock face edit mode allows the user to alter multiple editable aspects of the clock faces described herein. In some embodiments, in response to detecting a swipe on the touch-sensitive display (e.g., swipe  1056 ), the device may select a second element of the clock face for editing, which in response to detecting another user input (e.g., a movement of the rotatable input mechanism), may be edited. This allows the user to cycle through different editable aspects of the displayed clock face, such as colors, number and/or type of complications, and display density. 
     A user may wish to match a color of a displayed clock face to an image. In some embodiments, the device may receive a user input, and in response to receiving the user input, the device may enter a color selection mode. While in the color selection mode, the device may receive data representing an image, and in response to receiving the data, the device may select a color of the image and update a displayed clock face by changing a color on the clock face (e.g., a clock face background, hour and/or minute indication, and/or seconds hand) to match the color of the image. In some embodiments, the color selected may have the greatest prevalence of the colors in the image. This allows the user to further customize a clock face to display a designated color. For example, if the user is wearing a blue shirt, the user could take an image of the blue shirt and match the color of the clock face to the shirt. In some embodiments, the data representing the image may be obtained from an image stored on the device, an image stored on an external device in wireless communication with the device (e.g., Wi-Fi, Bluetooth™, near field communication (“NFC”), or any of the other cellular and/or other wireless communication techniques described herein), or an image taken using a camera on the device, such as camera module  143  or optical sensor  164 . 
     As described above, the techniques illustrated and described in reference to  FIGS. 7C and 10  may be used to edit or configure various aspects of context-specific user interfaces on portable multifunction device. However, it may be advantageous to allow the user to use an electronic device (e.g., a first device) to configure a context-specific user interface for a different portable multifunction device (e.g., a second device). In some embodiments, the first device has a larger display than the second device, thereby making it easier for the user to see and/or provide touch gestures on the first device. The user may wish to configure a user interface for the second device while operating the first device without switching over to the second device. For example, the user may download an application on the first device and wish to install a corresponding application configured for use on the second device. The user may then wish to configure the second device to display a user interface with a complication representing the newly installed corresponding application. 
       FIG. 11  illustrates an exemplary first electronic device  1100  and an exemplary second electronic device  1110 . In some embodiments, device  1100  may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1100  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a touch-sensitive display  1102 . In some embodiments, second device  1110  may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, external device  1110  is a personal electronic device, similar to device  500  as depicted in  FIG. 5A , with a touch-sensitive display  1112  and a rotatable input mechanism  1114 . 
     As depicted in  FIG. 11 , device  1100  is capable of receiving information over a wireless network. In some embodiments, device  1100  is coupled via wireless communication to device  1110 .  FIG. 11  also indicates that device  1100  is capable of operating in a paired relationship with external device  1110  to exchange data between the two devices. In a paired relationship, device  1100  and device  1110  are registered with one another and can perform two-way wireless communication. In some embodiments, wireless communication, for purposes of a paired relationship, occurs over a peer-to-peer wireless communication protocol such as Bluetooth and/or Bluetooth Low Energy (BTLE). In some embodiments, the wireless communication uses more than one wireless communication protocol. For example, WiFi may be used in addition to BTLE. In these embodiments, an initial communication between two devices may occur over a lower powered protocol, such as BTLE, even if the protocol yields a slower data transfer speed. Subsequent communications may occur over a secondary network that is relatively faster, such as WiFi. Additional exemplary techniques related to initiating and operating in a paired relationship are described in the following co-pending applications: International Patent Application Serial No. PCT/US2015/023699, titled “Companion Application for Activity Cooperation,” filed Mar. 31, 2015 published as WIPO Publication No. WO/2015/0183403; U.S. patent application Ser. No. 14/474,466, titled “Predefined Wireless Pairing,” filed Sep. 2, 2014, published as US PG Pub. No. 20150350865; International Patent Application Serial No. PCT/US2015/047507, titled “Reduced-size Configuration Interface,” filed Aug. 28, 2015 published as WIPO Publication No. WO/2016/036603; and U.S. Provisional Patent Application titled “Reduced-size Configuration Interface,” filed Mar. 8, 2015, naming Lawrence Y. Yang et al. as inventors. 
     A user may wish for data representing a context-specific user interface to be transmitted between devices. For example, users may wish to share context-specific user interfaces they have configured or customized with another user. Referring to  FIG. 11 , a user may wish to configure a context specific user interface using device for display on device  1110  using device  1100 . As such, it is desirable to provide techniques for transmitting data representing a context specific user interface. 
     Context-specific user interfaces may be thought of as user-configurable graphical constructs. User-configurable graphical constructs (e.g., context-specific user interfaces) may be broken down into modular constituents. A user-configurable graphical construct may include one or more graphical elements, which may themselves be independently configurable. Examples of graphical elements include without limitation aspects of the user interface, such as a clock, display density, color, and one or more optional complications. Each graphical element, as displayed to the user, may be thought to contain two dimensions of relevant information: what particular graphical asset(s) make up the graphical element (e.g., graphical assets selected from a discrete set of graphical assets stored in memory of device  1100  and/or  1110 ), and how the graphical asset(s) are arranged within the user-configurable graphical construct (e.g., where they are displayed). Stated another way, the graphical asset(s) and their arrangement make up a graphical element, and a plurality of graphical elements makes up a user-configurable graphical construct. Graphical assets need not themselves be graphical (they are assets making up a graphical element, rather than strictly “graphical” assets). In some embodiments, a clock may contain a graphical element or a set of graphical elements. Examples of graphical assets may include, for example, images or icons, text elements, animations, sound files, data obtained from an application, and so forth. 
     Returning to  FIGS. 6A and 6B , the user interface screen on display  602  may be thought of as a user-configurable graphical construct (in this instance, a context-specific user interface). This exemplary user-configurable graphical construct includes clock  608  (e.g., a graphical element or set of graphical elements). In some embodiments, clock  608  may be independently configurable by the user, e.g., using one or more of the concepts described in reference to  FIG. 10 . For example, the user may independently configure an appearance and/or number of indications of hours or minutes, a color (e.g., a color of the seconds hand), and so on. In some embodiments, a complication may be displayed within clock  608  (e.g., a complication that displays data obtained from a calendar application, such as the current date, or a complication that displays a monogram or other customizable text and/or image(s)). 
     Complications  610 ,  612 ,  614 , and  616  may be thought of as graphical elements. Each of these graphical elements is rendered on the displayed user-configurable graphical construct using one or more graphical assets (e.g., icons, application data, colors, text, and the like) and using an arrangement of the one or more graphical assets in the user-configurable graphical construct. For example, graphical element  610  is rendered using data obtained from a weather application (e.g., data identifying a sunny weather condition), a graphical asset representing a sun, and an indication that graphical element  610  is to be displayed in the upper left corner of the user interface screen. Similarly, graphical element  614  is rendered using data obtained from a calendar application (e.g., data identifying the date), a graphical asset representing a numerical date indication (e.g., a text element), and an indication that graphical element  614  is to be displayed in the lower left corner of the user interface screen. 
     If a user wishes to share a user-configurable graphical construct with a second user, and each user&#39;s device stores in memory a discrete set of graphical assets from which the graphical elements may be generated, the methods, devices, systems, and computer-readable storage media described herein need only transmit and receive data representing a user-configurable graphical construct, rather than transmitting or receiving the full user-configurable graphical construct, e.g., as an asset. Similarly, if a user wishes to configure a user-configurable graphical construct (e.g., a context-specific user interface) for display on device  1110  using device  1100 , and each device stores in memory a discrete set of graphical assets from which the graphical elements may be generated, the methods, devices, systems, and computer-readable storage media described herein need only transmit and receive data representing a user-configurable graphical construct, rather than transmitting or receiving the full user-configurable graphical construct, e.g., as an asset. Advantageously, such methods, devices, systems, and computer-readable storage media described herein may reduce bandwidth requirements, thus conserving processor, memory, and/or battery usage, which are particularly relevant for portable multifunction devices. 
     The concept of sharing data representing a user-configurable graphical construct with graphical assets and elements is illustrated in  FIG. 12 . This exemplary user-configurable graphical construct is optionally operated on device  1200  and/or  1230 , each of which may optionally be devices  100 ,  300 ,  500 , or  3200 , in accordance with some embodiments. The electronic devices have a display (e.g.,  504 ). It will be appreciated that similar techniques may be adapted for transmitting data representing a context-specific user interface between devices  1100  and  1110  in  FIG. 11 , e.g., via wireless communication. 
     Device  1200  displays user interface screen  1202 , which includes clock  1204  and complications  1206  and  1208 , representing a weather application and a calendar application, respectively. Each of graphical elements  1204 ,  1206 , and  1208  is made of graphical assets. In this example, the user of device  1200  wants to share data representing this user-configurable graphical construct with the user of device  1230 . 
     In order to share these data, device  1200  transmits data  1220 , which represents the user-configurable graphical construct. Data  1220  includes metadata or information  1222  representing each graphical element. For example, metadata  1222  contains data indicating each graphical asset of clock  1204  (e.g., a style of clock, a density of the clock, and a color scheme of the clock) as well as data indicating the arrangement of the graphical assets in the user-configurable graphical construct (e.g., display the clock in the middle of screen  1202 ). Metadata  1222  further contains data for each of the two complications, indicating which graphical assets to use (e.g., which application data to display, and which icon, image or text element to display) and how they are arranged (e.g., which corner of screen  1202 ). 
     As shown on screen  1232  of device  1230 , data  1220  includes all of the information necessary to compile the graphical assets required for the user-configurable graphical construct. Data  1220  does not include the graphical assets themselves; it merely contains metadata or information  1222  that device  1230  then uses to select the relevant graphical assets from the discrete set stored in memory and display them in the indicated arrangement. 
     Upon receiving data  1220 , device  1230  displays screen  1232 , which includes complications  1236  and  1238 , which are based on complications  1206  and  1208 . In some embodiments, graphical elements  1206  and  1236 , and/or graphical elements  1208  and  1238 , may be the same as those sent by device  1200 . In some embodiments, the complications as displayed on the sender and recipient devices may differ, since they may obtain and display local application data. For example, a sender in Alaska may send to a friend in Hawaii data representing a user-configurable graphical construct with a complication showing data from a weather application (e.g.,  1206 ). As viewed from on the sender&#39;s device, complication  1206  shows Alaskan weather data, but when displayed by the recipient device  1230 , complication  1236  shows local weather data from Hawaii. 
       FIG. 13  illustrates exemplary electronic device  1300  and an exemplary electronic device  1320 . In some embodiments, device  1300  may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a touch-sensitive display  1302 . In some embodiments, second device  1320  may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, external device  1320  is a personal electronic device, similar to device  500  as depicted in  FIG. 5A , with a touch-sensitive display  1322  and a rotatable input mechanism  1324 . Devices  1300  and  1320  are coupled via wireless communication. In some embodiments, devices  1300  and  1320  are in a paired relationship, e.g., as described in reference to  FIG. 11 . 
     Device  1320  has access to a library of context-specific user interfaces for display on display  1322 . For example, the library can be stored in memory of device  1320 , stored in memory of device  1300  and accessible to device  1320 , and/or stored at an external server accessible to devices  1300  and  1320 . In some embodiments, context-specific user interfaces are stored in the library as unique or complete assets. In some embodiments, the library stores context-specific user interfaces as configurations that are rendered for display by device  1320  (e.g., by rendering a set of graphical assets stored in memory according to the configuration, which specifies the particular graphical asset(s) used and their arrangement within the user interface). 
     In some embodiments, device  1320  enters a user interface or clock face selection mode that allows the user to select a user interface for display. Further descriptions of clock face selection mode may be found in International Patent Application Serial No. PCT/US2015/034607, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205. This selection mode is illustrated on screen  1322 , which includes preview image or representation  1330  that represents a context-specific user interface from the library for display by device  1320 . As represented by preview image  1330 , the context-specific user interface includes indications of the current time, date, a sinusoidal wave that indicates the path of the Sun through the day, and an affordance representing the current position of the Sun along the path. Preview images  1332  and  1334  from the library are displayed in partial view, indicating to the user that the library contains additional user interfaces. Paging affordance  1336  indicates the total number of user interfaces in the stored library as well as the position of the currently selected user interface (e.g., the user interface represented by  1330 ) within the library. 
       FIG. 13  also illustrates a user interface, at device  1300 , for selecting, reordering, and/or editing context-specific user interfaces from the stored library for display on device  1320 . The user interface screen shown on display  1302  includes depiction  1304  of device  1320 , which optionally includes a depiction of device name, size, and/or other device features. In some embodiments, depiction  1304  serves as an affordance that, when contacted by the user, displays additional information and/or functionality related to device  1320 , such as options for pairing or de-pairing device  1320  with another electronic device. The user interface screen shown on display  1302  includes complications bar  1306 . In some embodiments, complications bar  1306  allows the user to view a list of complications that can be configured for display as part of a context-specific user interface from the library, as well as optional affordances for selecting and/or editing particular complications. In some embodiments, the user scrolls on the depicted user interface screen (e.g., with a horizontal swipe) to view particular complication options. Screen  1302  further includes affordance  1308  for viewing one or more user interfaces from the library. In some embodiments, the user touches affordance  1308 , and in response device  1300  displays the user interface illustrated on screen  1302 . 
     Also shown on the user interface screen of display  1302  are preview images  1310 ,  1312 , and  1314 . Preview images  1310 ,  1312 , and  1314  represent context-specific user interfaces from the library for display on device  1320 . As represented by preview images  1310  and  1312 , both corresponding user interfaces include a clock. In addition, the user interface represented by  1312  includes a complication, as described herein. In some embodiments, the preview image(s) are displayed with an associated text element indicating the type of watch face for the corresponding context-specific user interface (e.g., “sun” for the user interface represented by  1310 , “utility” for the user interface represented by  1312 , etc.). The user interface screens shown on displays  1302  and  1322  indicate to the user what user interfaces are stored in the library and the order or sequence of the user interfaces within the library. 
     In some embodiments, the preview image includes a representation of one or more complications of the user interface. For example, preview image  1312  includes representation  1316 , which represents a complication of the user interface represented by  1312 . In this example, representation  1316  represents a complication that displays an affordance representing a weather application. As discussed above, complications can obtain data and display information obtained from an associated application (optionally, the information is updated in accordance with updates to the data). In some embodiments, device  1300  obtains “live” data from the weather application and displays information updated according to updates to the data in representation  1316  (e.g., the sun depicted in  1316  indicates current weather conditions, representing live data obtained from the weather application). Advantageously, this allows the user to visualize how the user interface looks when displayed on device  1320  at the current time. In other embodiments, device  1300  displays a “placeholder” representation of application data. For example, the sun depicted in  1316  can be an icon or affordance that represents to the user the content of the live data that would be displayed in the complication. For example, the placeholder may be installed as part of the app and/or designated as part of a software development kit used to develop the application. Advantageously, this allows the user to understand the function of the complication within the user interface but does not require processor resources and/or communication bandwidth to obtain live data to generate the preview image. 
     Preview image  1314  is shown in partial view. This alerts the user to the fact that additional preview images representing the rest of the stored library are viewable in this interface, e.g., by scrolling. In some embodiments, the user swipes the display at one or more of preview images  1310 ,  1312 , and  1314  (e.g., a horizontal swipe), and in response to detecting the swipe, device  1300  scrolls the displayed preview images to reveal one or more additional preview images representing user interfaces from the library. 
     In some embodiments, information in one or more preview images shown on display  1302  and/or  1322  is updated live, e.g., while the user is in face selection mode of device  1320  or viewing preview images at display  1302 . For example, in some embodiments, a representation of a clock on one or more of  1310 ,  1312 ,  1314 ,  1330 ,  1332 , and/or  1334  is rendered live, e.g., such that the preview image displays current time. In some embodiments, a representation of one or more complications on one or more of  1310 ,  1312 ,  1314 ,  1330 ,  1332 , and/or  1334  is rendered live, e.g., such that the preview image displays current complication data (e.g., information from an application updated in accordance with updates to application data). In some embodiments, a representation of one or more complications on a currently centered preview image (e.g., displayed in complete view, such as  1310  or  1330 ) is rendered live, while a representation of one or more complications on a currently non-centered preview image (e.g., displayed in partial view, such as  1312 ,  1314 ,  1332  or  1334 ) is not rendered live (e.g., it displays placeholder data, or data obtained at a previous refresh, such as the last time the represented user interface was displayed, or the last time the preview image was centered on the display). In some embodiments, a representation of one or more complications on a currently centered preview image (e.g., displayed in complete view, such as  1310  or  1330 ) and representation(s) on preview images immediately adjacent to the currently centered preview image are rendered live (e.g.,  1312 ,  1314 ,  1332  or  1334 ), while a representation of one or more complications on a preview image that is not currently centered and not adjacent to a currently centered preview image is not rendered live (e.g., it displays placeholder data, or data obtained at a previous refresh, such as the last time the represented user interface was displayed, or the last time the preview image was centered on the display). In some embodiments, a representation that is not rendered live may be rendered using data updated at a longer interval than a representation that is rendered live. In some embodiments, one or more elements or user interface objects represented in a preview image other than those representing a clock or a complication may be shown as a static element (e.g., not rendered according to updated data). 
       FIGS. 14A-14D  illustrate exemplary electronic device  1300 . In some embodiments, device  1300  is one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a touch-sensitive display  1302 . In some embodiments, device  1300  is coupled to a second device (e.g.,  1320 ; not shown), which may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For example, device  1300  can be coupled via wireless communication to a personal electronic device similar to device  1320  or device  500  as depicted in  FIG. 5A , with a touch-sensitive display and a rotatable input mechanism. 
     The techniques illustrated in  FIGS. 14A-14F  provide user interfaces that allow a user to manage the stored library of context-specific user interfaces for display at another device, e.g., as described above. These techniques allow the user to conserve battery life of the second device by providing an interface for library management at device  1300 . In some embodiments, e.g., where device  1300  has a larger display than the second device on which the user interface(s) are displayed (e.g.,  1320 ), these techniques provide enhanced visibility and screen “real estate” for additional functionalities and/or inputs. In some embodiments, they also provide an alternative interface for users with large hands or fine motor skill deficits, who may prefer to use a larger touch-sensitive display and surface for inputs than a smaller screen and/or rotatable input mechanism. 
       FIG. 14A  at (A) illustrates a user interface screen similar to the one shown on display  1302  in  FIG. 13 . Device  1300  receives a user input corresponding to a user request to reorder the stored library of context-specific user interfaces for display on a second device (e.g.,  1320 ). In this example, the user input is touch  1400  on edit affordance  1318 . In response to detecting touch  1400 , device  1300  displays the user interface screen shown in  FIG. 14A  at (B). 
     The user interface screen shown in  FIG. 14A  at (B) includes user interface objects  1404 ,  1410 ,  1412 ,  1414 , and  1416 , representing context-specific user interfaces from the stored library. In some embodiments, each context-specific user interface from the library is represented on the user interface screen, e.g., by a corresponding user interface object (in some embodiments, the user interface screen may be scrollable, e.g., to reveal additional user interface representations). In some embodiments, the order of the user interface objects reflects the order of the represented context-specific user interfaces in the stored library. For example, the order of user interface objects  1404 ,  1410 , and  1412  from top to bottom in  FIG. 14A  at (B) reflects the order of user interface preview images  1312 ,  1310 , and  1314  from left to right in  FIG. 14A  at (A), as well as the order of  1332 ,  1330 , and  1334  on device  1320  in  FIG. 13 . The configuration of the user interface screen shown in  FIG. 14A  at (B) allows for a larger number of user interfaces from the library to be represented (e.g., all 5 are represented at (B), as compared to 2 full user interface preview images and a partial view of another at (A)), thereby allowing the user to view a larger portion of the stored library for managing. 
     User interface objects can contain various affordances for identifying and/or modifying the corresponding user interface, and/or its position in the sequence of the stored library. In some embodiments, the user interface screen displays one or more user interface preview images, e.g.,  1310 ,  1312 , and  1314 , corresponding to user interfaces from the library. In some embodiments, the user interface preview images displayed on the user interface screens shown in  FIG. 14A  at (A) and (B) are similar, related, or identical. In some embodiments, the user interface preview images shown in  FIG. 14A  at (B) are modified as compared to those displayed on the user interface screen shown in  FIG. 14A  at (A), e.g., displayed at a smaller size and/or level of detail. In some embodiments, the user interface screen displays one or more text indications, e.g., such as text element  1408 , that indicate the watch face type according to which one or more user interfaces from the library is configured. In some embodiments, the user interface screen includes an indication, e.g.,  1418 , of the currently selected and/or currently displayed (e.g., on device  1320 ) user interface. 
     As shown in  FIG. 14B  at (A), the user provides a user input corresponding to a user request to re-order the stored library. For example, user interface object  1414  (representing the “astro” user interface) includes a re-ordering affordance  1418  displayed in association with (e.g., adjacent to, or in a common, demarcated area of the display with) the corresponding user interface preview image and/or watch face type indication. In some embodiments, the user input is a touch gesture on display  1302 , such as touch-and-drag gesture  1420 . Device  1300  detects a contact on display  1302  at re-ordering affordance  1418  and, while continuing to detect the contact, detects movement of the contact without a break to a position on display  1302  above user interface object  1410 , representing the “sun” user interface of the library. During and/or after the movement of the contact (e.g., touch and drag  1420 ), device  1300  translates user interface objects  1410 ,  1412 , and  1416  downward on display  1302  to accommodate a concomitant upward movement of  1414 . In some embodiments, during touch and drag  1420 , user interface object  1414  is displayed as semi-transparent, allowing the user to see the on-screen translation of the other user interface objects, portions of which can be displayed “behind”  1414 . During touch and drag  1420 , device  1300  translates user interface object  1414  in a direction of the gesture (in this example, upward on-screen; cf.  FIG. 14B  at (A) and (B)). 
     In response to detecting a break in the contact of gesture  1420 , device  1300  places user interface object  1414  at a position in the ordered list according to the position of the break of contact and re-orders the subsequent user interface objects accordingly. This is illustrated in  FIG. 14C  at (A), which shows user interface object  1414  at a re-ordered position between user interface objects  1404  and  1410  on the displayed user interface screen. In some embodiments, the user provides an input for completing editing of the stored library. In this example, the user provides touch  1422  on display  1302  at the location of “done” affordance  1424 . 
     In response to detecting touch  1422 , device  1300  displays the user interface screen shown in  FIG. 14C  at (B). The user interface screen shown in  FIG. 14C  at (B) is similar to the user interface screen shown in  FIG. 14A  at (A). However, in  FIG. 14C  at (B), the user interface screen displays user interface preview image  1426 , representing the same user interface from the library as that represented by user interface object  1414 . As compared to  FIG. 14A  at (A), preview image  1426  is now shown between user interface preview image  1312  and a partial view of  1310  at a position that reflects the re-ordering of the library. This position indicates to the user that the user interface represented by  1426  has been re-ordered in the stored library. Device  1300  also sends instructions to the second electronic device (e.g.,  1320 ) for re-ordering the second user interface before the first user interface in the stored library. In some embodiments, device  1300  sends the instructions directly to device  1320 . In other embodiments, e.g., if the library is stored at an external server, device  1300  sends the instructions indirectly to device  1320  through the external server or other intermediary device. 
     The user can also use the interface to delete a context-specific user interface from the library.  FIG. 14D  at (A) illustrates a similar user interface screen as compared to  FIG. 14A  at (B). User interface object  1414  includes affordance  1432  for revealing an edit option displayed in association with (e.g., adjacent to, or in a common, demarcated area of the display with) the corresponding user interface preview image and/or text element. In this example, the user contacts display  1302  with touch  1430  at affordance  1432 . 
     In response to detecting touch  1430 , device  1300  displays delete affordance  1434 , as shown in  FIG. 14D  at (B). In some embodiments, one or more components of user interface  1414 , such as the associated user interface preview image, text element, and/or re-ordering affordance, as translated on-screen to accommodate the appearance of delete affordance  1434 . In this example, the corresponding user interface preview image (e.g.,  1414 ) is translated on-screen such that it is shown in a partial view, aiding the user&#39;s understanding that the delete affordance functions to remove the user interface object from the user interface screen and the represented user interface from the library. 
     The user provides touch  1436  on the displayed affordance  1434 . In response to detecting touch  1436 , as shown in  FIG. 14E , device  1300  removes user interface object  1414  from the display. In some embodiments, one or more other user interface object(s) (e.g.,  1416 ) are translated on-screen accordingly, e.g., to occupy the former position of  1414 . In some embodiments, device  1300  sends instructions to device  1320 , as described above, to remove the user interface represented by  1414  from the stored library. In some embodiments, device  1300  sends the instructions after detecting a user touch on a displayed affordance, such as “done” affordance  1424 . 
     In some embodiments, the user interface screen displays a user prompt to add a new user interface to the stored library, e.g., if the user scrolls to the end of the list of user interface images. For example, the user contacts display  1302  at “new” affordance  1438 , and in response to detecting the contact, device  1300  displays a new user interface screen that includes a user interface preview image representing a new user interface, optionally with affordances for customizing the watch face type, complications, and other options for the new user interface, as well as an affordance for saving the new user interface as part of the stored library. 
     In some embodiments, after detecting the user touch on “done affordance”  1424 , device  1300  displays the user interface screen shown on display  1302  in  FIG. 14F  at (D). This user interface screen includes user interface preview images  1440 ,  1426 , and  1444  in the same order as user interface objects  1410 ,  1414 , and  1416  shown in  FIG. 14D  at (A), e.g., before the user input to delete the user interface represented by user interface object  1414 . Device  1300  animates user interface preview image  1426  to disappear from display  1302 , e.g., by animating  1426  to translate away from the row of preview images  1440  and  1444 , as depicted by arrow  1442 . In some embodiments, device  1300  animates another preview image (in this example,  1444 ) to translate on-screen, e.g., to occupy the former position of 1426, as depicted by arrow  1446 . 
     Subsequently, as shown in  FIG. 14F  at (E), device displays a row of user interface preview images that includes  1440  and  1444  (which occupies the former position of  1426 ) but lacks  1426 . 
     In addition to re-ordering, deleting, and adding user interfaces to the library, it is advantageous to allow the user to edit or customize user interfaces for display on device  1320  at device  1300 . These techniques allow the user to conserve battery life of the second device by providing an interface for library management at device  1300 . In some embodiments, e.g., where device  1300  has a larger display than the second device on which the user interface(s) are displayed (e.g.,  1320 ), these techniques provide enhanced visibility and screen “real estate” for additional functionalities and/or inputs. They may also provide an easier user interface for users with large hands or fine motor skill deficits, who may prefer a larger touch-sensitive display and surface for inputs than a smaller screen and/or rotatable input mechanism. 
     As shown in  FIG. 15A  at (A), device  1300  displays a user interface screen on display  1302  that includes depiction  1304  of device  1320 , complications bar  1306 , and affordance  1308  for viewing one or more user interfaces from the library. The user interface screen also includes preview images  1310 ,  1312 , and  1314 . The user is able to select a user interface for editing at device  1300  by contacting display  1302  at the corresponding user interface preview image, such as touch  1500  on user interface preview image  1312 . In some embodiments, a preview image representing a context-specific user interface that was recently stored in the library (e.g., within the previous day, week, or in the previous user editing session) is indicated by a user interface object, such as dot  1502  displayed in association with preview image  1310 . 
     In response to detecting touch  1500 , device  1300  displays the user interface screen shown in  FIG. 15A  at (B). This user interface allows the user to edit or customize various aspects of user interface(s) from the stored library. For example, the user may customize one or more editable aspects or options described herein in reference to  FIG. 10 . However, in  FIG. 10 , the user provides at device  1320  a swipe (e.g., swipe  1056 ) or other input to view different editable aspects, and movement  1042  of rotatable input mechanism  1040  to view different options for each editable aspect. In the user interface for device  1300  illustrated in  FIG. 15A  at (B), multiple editable aspects, and their associated options, are presented to the user simultaneously on the same display, thereby promoting the user&#39;s understanding of the full scope of available customization options. 
     The user interface displays one or more editable aspects of the represented user interface, along with one or more options for the one or more editable aspects. As shown in  FIG. 15A  at (B), display  1302  shows bar  1504  for editing a color of the user interface, along with affordances such as  1506  that indicate options for this editable aspect (e.g., color) of the user interface. Affordance  1506  represents a color option for the represented user interface. In some embodiments, the affordance(s) are displayed in the corresponding color. In some embodiments, the display further includes a text element indicating the currently selected color option, such as indicator  1508 . In some embodiments, the number of affordances shown in association with an editable aspect corresponds with the number of available options for each respective aspect (unless the options are too numerous to display at once, in which case the affordances are scrollable to allow the user to navigate through the options). 
     Display  1302  in  FIG. 15A  at (B) also shows bar  1510  for editing an amount of detail or display density of the corresponding user interface. Displayed in association with bar  1510  are affordances such as affordance  1512 , each representing a detail option for the corresponding user interface. In some embodiments, affordance  1512  displays a representation of the user interface configured according to the corresponding detail option. In some embodiments, affordance  1512  displays a representation of an aspect of the user interface configured according to the corresponding detail option, such as a clock face with a certain number or type of hour indicators. 
     Display  1302  in  FIG. 15A  at (B) also shows bar  1520  for editing one or more complications of the user interface. For example, affordances  1522 ,  1524 ,  1526 , and  1528  represent available complication slots or platters of the user interface and indicate the currently selected complication option for each slot or platter (which may include not displaying a complication at the slot or platter). These indicate to the user how many complication slots or platters are configurable for display on the user interface according to the corresponding watch face type, as well as the currently selected options for each slot or platter. Affordance  1522  indicates the position of the corresponding complication on the user interface (e.g., “top left”) and an application represented by the complication (e.g., “Weather” application). 
     In some embodiments, the user contacts display  1302  at affordance  1522  to edit the indicated complication slot or platter (e.g., as illustrated in  FIG. 16B  with touch  1660 ). In response to detecting the contact, device  1300  expands a scrollable menu on display  1302  in which the user swipes horizontally to scroll through the available applications, and optionally contacts a “done” affordance to select a particular option. In some embodiments, the scrollable menu includes one or more applications installed on device  1320  for which a complication is available. 
     Display  1302  in  FIG. 15A  at (B) also shows affordance  1530  for setting the presently selected and configured user interface as the current user interface, e.g., of device  1320 . In some embodiments, in response to detecting a contact at affordance  1530 , device  1300  sends instructions to device  1320  for displaying the represented user interface, e.g., as configured on display  1302 . In some embodiments, device  1320  displays the user interface after receiving the instructions. In some embodiments, device  1320  displays the user interface the next time display  1322  is activated. In some embodiments, e.g., if a context-specific user interface is currently displayed on display  1322 , device  1320  animates a transition from the previous user interface to the presently selected and configured user interface. In some embodiments, device  1300  sends instructions to device  1320  for providing a haptic output, thereby indicating to the user that the context-specific user interface has changed. 
     Display  1302  in  FIG. 15A  at (B) also shows affordance  1532  for removing the selected user interface from the library. In some embodiments, in response to detecting a contact at affordance  1532 , device  1300  sends instructions to device  1320  for removing the user interface from the stored library. In some embodiments, in response to detecting a contact at affordance  1532 , device  1300  displays a customization page corresponding to a different user interface, e.g., one adjacent to the removed user interface in the library. In some embodiments, in response to detecting a contact at affordance  1532 , device  1300  re-displays the user interface screen as illustrated in  FIG. 15A  at (A), with the re-displayed user interface screen lacking preview image  1312  representing the deleted user interface. 
     As shown in  FIG. 15A  at (B), the display includes a preview image of the context-specific user interface currently selected for editing, e.g.,  1312 . In some embodiments, the preview image visually distinguishes a current aspect for editing, e.g., by highlighting, outlining, or animating the selected element; or dimming one or more non-selected elements. In some embodiments, the preview image is a “live” representation of the user interface that is updated in response to user customization. In some embodiments, user selection of a different option for an editable aspect of the represented user interface causes an animated transition on the preview image from the former option to the currently selected option. For example, a color change of a seconds hand can be animated as a color change originating from the center of the clock face outwards. In some embodiments, the animated transition appears on display  1302  in a different manner than an animated transition between the same options on display  1322 . In some embodiments, the user swipes the display (e.g., a lateral swipe, or in some embodiments a lateral swipe originating at a bezel of display  1302 ) to view and/or edit a different context-specific user interface from the library. 
     Preview image  1312  also includes representation  1316 , which represents a complication on the corresponding user interface. In some embodiments, representation  1316  is updated in response to user customization. For example, the user can change the application represented by the complication, which in turn leads to update of representation  1316  to represent the currently selected application (e.g., by displaying “live” application data or a placeholder representation of application data, as described herein). In some embodiments, the transition of representation  1316  from one application to another is animated as a slot machine-style rollover of displayed content. 
       FIGS. 15B and 15C  display user interface screens for editing context-specific user interfaces configured according to other watch types at device  1300 . The user interface shown in  FIG. 15B  on display  1302  shows an editing interface for customizing a user interface that displays animated video segments, e.g., as described in reference to  FIGS. 9A and 9B . User interface preview image  1540  shows a representation of a user interface with displays of the time, date, and an animated flower. Bar  1542  indicates to the user various selectable options for the theme or animated item of the user interface. Displayed in association with bar  1542  are affordances including affordance  1544  that indicate options for editing the theme or animated object (in this example, a flower, jellyfish, or butterfly). In this example, the option represented by affordance  1544  is highlighted, e.g., by a displayed outline, indicating that this option is the currently selected option for this aspect. 
     The user interface shown in  FIG. 15C  on display  1302  shows an editing interface for customizing a user interface that displays astronomical information. User interface preview image  1550  shows a preview image representing a user interface that displays the time, date, a representation of the Earth, and affordances representing the Moon (for accessing lunar data) and the Solar System (for accessing data related to other planets in the Solar System). Text element  1552  provides a brief description of the functionalities for this watch face type. In this example, text element  1552  indicates that the “astro” watch face type displays information about the Earth, Moon, and Solar System, thereby informing the user about the available functionalities of the user interface. 
     While  FIGS. 15A-15C  show exemplary editable aspects for context-specific user interfaces, other editable aspects are contemplated. For example, the user can edit a timescale of a displayed stopwatch affordance, e.g., on the user interfaces described in reference to  FIGS. 8A and 8B , a displayed image or designated folder or album from which displayed images are obtained (e.g., for display as a user interface background), the type and/or appearance of a character user interface object, and so forth. In some embodiments, the user is able to crop an image, e.g. for display as a user interface background. 
     In addition to allowing the user to configure, add, delete, and/or reorder user interfaces already stored in the library of context-specific user interfaces, it is also advantageous to provide suggestions to the user for new user interfaces and/or complications for display on a second device (e.g., device  1320 ) that are not already represented in the library. For example, if the user frequently uses an application configured for use on device  1300 , they may wish to use a corresponding version of the application configured for use on device  1320 . A user may be unaware of particular watch face types or configurations thereof that are available for use on device  1320 . Techniques for suggesting new user interfaces (e.g., not already represented in the stored library) are therefore desirable and provide for more convenient user access to the full range of available applications and/or functionalities at an electronic device (e.g.,  1320 ). 
       FIG. 16A  illustrates exemplary electronic device  1300 . In some embodiments, device  1300  is one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a display  1302  (e.g., a touch-sensitive display). In some embodiments, device  1300  is coupled to a second device (e.g.,  1320 ), which may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For example, device  1300  can be coupled via wireless communication to a personal electronic device similar to device  1320  or device  500  as depicted in  FIG. 5A , with a touch-sensitive display and a rotatable input mechanism. 
     In  FIG. 16A , device  1300  displays an exemplary user interface screen on display  1302 . The user interface screen includes indicator  1600 , which indicates to the user that the user interface screen represents a gallery of potential context-specific user interfaces for display on device  1320 . The user interface screen also displays affordance  1608 , which the user can contact to access the user interface screen illustrated in  FIG. 16A  (e.g., by contacting the displayed affordance  1608 ). Bar  1602  indicates one or more context-specific user interfaces that are “new,” or configured according to one or more watch face types that were recently installed in memory of device  1320 . For example, in some embodiments, these watch face types were installed in the previous day, week, or other predetermined period of time; and/or in the latest operating system update installed at device  1320 . Displayed as associated with bar  1602  are one or more user interface preview images (e.g., preview image  1604 ) representing user interfaces configured according to the one or more new watch face types. Importantly, in some embodiments, the preview images represent context-specific user interfaces that are not already stored in the library of context-specific user interfaces for display on device  1320 . In some embodiments, the user interface in  FIG. 16A  is accessible on device  1300  even if it is not paired or coupled via wireless communication to device  1320 . Thus, the user interface displays options that inform the user about the available functionalities of device  1320  even if the user does not own device  1320  or has not yet paired device  1320  with device  1300 . 
     The user interface screen also displays bar  1606 , which indicates to the user that the represented user interfaces include featured complications. This provides an opportunity to introduce to the user new, or not currently used or configured, complications for use on device  1320 , e.g., through inclusion in one or more context-specific user interfaces. This user interface serves to introduce the user to new or not currently used (e.g., represented in the stored library of context-specific user interfaces) complications, watch face types, and/or combinations thereof. 
     Displayed in association with bar  1606  are user interface preview images  1610  and  1620 . Preview images  1610  and  1620  represent context-specific user interfaces for display on device  1320 . Importantly, in some embodiments, the preview images represent context-specific user interfaces that are not already stored in the library of context-specific user interfaces for display on device  1320 . 
     The user interfaces represented by  1610  and  1620  both include a clock. This is depicted by representation  1616  of a digital clock as part of preview image  1610  and representation  1624  of an analog clock as part of preview image  1620 . The user interfaces represented by  1610  and  1620  are both configured according to a watch face type, which includes, e.g., the type of available clock options; a number, size, position, and/or content of available complication slot(s) or platter(s); and/or other optional, configurable elements (e.g., character user interface objects, animated objects, astronomical information, etc.). 
     The user interfaces represented by  1610  and  1620  both include one or more complications. This is depicted by complication representations  1612  and  1614  as part of preview image  1610  and complication representation  1622  as part of preview image  1620 . As described above, in some embodiments, the preview image represents the same features that would be displayed as part of the represented context-specific user interface on device  1320 . For example, if a complication obtains live application data and displays information updated in accordance with updates to the data, the complication representation also displays the information. In other embodiments, the preview image schematically represents the features that would be displayed as part of the represented context-specific user interface on device  1320  without using the same features. For example, if a complication obtains live application data and displays information updated in accordance with updates to the data, the complication representation displays placeholder data that indicates to the user the type of data that would be displayed without requiring use of wireless bandwidth and/or processor resources to obtain live data. 
     In some embodiments, the user swipes display  1302  at user interface preview image  1610  and/or  1620 , and in response device  1300  scrolls  1610  and/or  1620  on-screen to reveal additional preview images representing context-specific user interfaces for display  1320 , e.g., selected according to one or more criteria described herein. 
     User interface preview images  1610  and  1620  represent respective context-specific user interfaces that are selected by device  1300  for display based at least in part on one or more criteria described herein. It is contemplated that various criteria described herein may be combined and/or weighted according to various algorithm(s) and/or weighting schema using the guidance provided by the present disclosure. Exemplary criteria for selection are described infra. 
     In some embodiments, a selected user interface is configured according to a watch face type not currently represented in the library. For example, preview image  1610  represents a user interface configured according to a modular watch face type, and the user does not have a context-specific user interface configured according to the modular watch face type saved in the library. 
     In some embodiments, a selected user interface is configured with a complication that is not currently represented in a user interface saved in the library. For example, preview image  1610  represents a user interface configured with two complications associated with a news application (e.g., as depicted by representations  1612  and  1614 ), and the user does not have a user interface with a news complication saved in the library. 
     In some embodiments, a selected user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 . For example, corresponding versions of the news application may be configured for use on a desktop or laptop, tablet, phone, or smartwatch. A user may use the application on one type of device and be unaware that a corresponding version of the application is configured for use and available for another type of device. In this example, preview image  1610  represents a user interface configured with two complications associated with a news application (e.g., as depicted by representations  1612  and  1614 ). The user has installed on device  1300  a version of the application configured for use on device  1300 , but has not installed a corresponding version on device  1320  configured for use on device  1320 . 
     In some embodiments, one or both of the user interfaces represented by preview images  1610  and  1620  are selected according to the criteria described herein. In some embodiments, the user interfaces represented by preview images  1610  and  1620  are independently selected according to criteria described herein. In some embodiments, the user interfaces represented by preview images  1610  and  1620  include representations of different complications, such as complications associated with different applications (e.g., news and pace). In some embodiments, the user interfaces represented by preview images  1610  and  1620  are configured according to different watch face types (e.g., modular and utility). 
     In some embodiments, a selected user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 , but the application for use on device  1320  is not currently installed on device  1320 . In this example, the user has installed a version of the news application configured for use on device  1300 , but not the version configured for use on device  1320 . 
     In some embodiments, a selected user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 , and the application for use on device  1320  was installed on device  1320  within a predetermined period of time. In this example, the user has installed the version of the news application configured for use on device  1300  and recently installed on device  1320  the version configured for use on device  1320 . In another example, a new complication for use on device  1320  representing an application with a corresponding application installed at device  1300  has recently been installed as part of an operating system or application update on device  1320 . 
     In some embodiments, a selected user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 , and the corresponding application on device  1300  was installed within a predetermined period of time. In this example, the user has recently installed the version of the news application configured for use on device  1300 . 
     In some embodiments, a selected user interface is configured with a complication associated with a designated application for use on device  1320 . In this example, the news application is part of a curated or sponsored list of applications for use on device  1320 , e.g., as designated by an application store, website, or other external server from which the corresponding application is downloaded. 
     In some embodiments, a selected user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 , and the corresponding application is used above a predetermined frequency on device  1300 . In this example, the user frequently uses the version of the news application configured for use on device  1300 . 
     In some embodiments, device  1300  selects a prioritized list of user interfaces to present to the user (e.g., via user interface preview images). For example, the row of user interface preview images shown by  1610  and  1620  can be part of the list. Optionally, the order in which preview images are displayed reflects an order of prioritization. In some embodiments, a user interface of the list is prioritized, e.g., moved up within the prioritized list, based at least in part on one or more of the criteria described herein. 
     In some embodiments, a user interface of the list is de-prioritized, e.g., moved down within the prioritized list, based on one or more de-prioritization criteria in any combination and/or according to any weighting schema and/or algorithm. For example, in some embodiments, a user interface of the list is de-prioritized because the user interface is already represented in the stored library. In some embodiments, a user interface of the list is de-prioritized because it includes a complication that is already represented in a user interface of the library. In some embodiments, the complication is already represented in a user interface configured according to the same watch face type as the de-prioritized user interface. In some embodiments, a user interface of the list is de-prioritized because a user interface of the same watch face type is adjacent to the de-prioritized user interface in the list (e.g., to avoid presenting to the user two preview images representing two watch faces of the same type adjacent on the display). Advantageously, these criteria prioritize the presentation of user interfaces with newer and/or unused features to the user. 
     The user interface selected by device  1300  and represented by preview image  1610  contains a complication associated with the news application. The user interface is also configured according to a watch face type (in this example, a “modular” watch face with a digital clock and 5 complication slots or platters that has editable aspects including color and application(s) associated with the complications). In some embodiments, device  1300  selects the watch face type of a user interface (e.g., the user interfaces represented by preview images  1610  and  1620 , and/or one or more user interfaces that are part of a prioritized list) based at least in part on one or more watch face type criteria, e.g., as described infra. It will be appreciated that such criteria may be combined or weighted according to various algorithm(s) and/or weighting schema. Inter alia, these criteria help to present to the user new complications as part of context-specific user interface(s) configured according to watch face types in which the user has already demonstrated interest, thus improving the potential for user satisfaction. 
     In some embodiments, a watch face type is selected because the application (e.g., configured for use on device  1320 ) associated with a complication of the user interface is supported for use in the selected watch face type. An application can be supported and/or configured for use in a particular complication slot or platter, but not another. For example, a complication can have certain constraints related to the type or amount of displayed data, and an application can be supported for use in association with a complication according to certain complication configuration(s). 
     In some embodiments, a watch face type is selected because the watch face type is represented in one or more user interfaces already in the library. In some embodiments, a watch face type is selected because one or more user interfaces configured according to the selected watch face type are displayed by device  1320  (e.g., on display  1322 ) above a predetermined frequency. For example, the user frequently uses one or more context-specific user interfaces configured according to a “modular” watch face type, so device  1300  presents a featured complication as part of a user interface configured according to that watch face type. In some embodiments, a watch face type is selected because one or more user interfaces configured according to the selected watch face type were displayed by device  1320  (e.g., on display  1322 ) within a predetermined period of time. For example, the user has used one or more context-specific user interfaces configured according to a “modular” watch face type recently, so device  1300  presents a featured complication as part of a user interface configured according to that watch face type. 
     In some embodiments, a watch face type is selected because one or more user interfaces in the library of the same watch type have been edited by the user (e.g., at device  1300  and/or device  1320  as described herein). For example, the user has edited a complication of a user interface of the same watch type, thereby indicating interest in that watch face type and/or awareness that the watch face type can be edited as described herein. 
     In some embodiments, a watch face type is selected because the library does not already include a user interface configured according to the same watch face type with the same complication. Alternatively, the presence in the library of a user interface configured according to the same watch face type with the same complication may serve as a de-prioritization criterion for selection of a watch face type. For example, the user has already stored a user interface with a news complication configured according to a “modular” watch face type. 
     The user selects the user interface represented by preview image  1610  with touch  1626  on display  1302 . In response to detecting touch  1626 , device  1300  displays the user interface screen illustrated on display  1302  in  FIG. 16B . This user interface screen provides the user with information about the editable aspects, selectable options for the editable aspects, watch face type, and other characteristics of the represented user interface. This provides a platform for educating the user about the selected user interface, which in some embodiments is not already stored in the library, and for editing a new context specific user interface before storing it in the library. In some embodiments, in response to detecting touch  1626 , device  1300  sends instructions to device  1320  to add the context-specific user interface represented by  1610  to the library and/or display the context-specific user interface represented by  1610  on display  1322 . 
     The user interface screen shown in  FIG. 16B  includes preview image  1610  with representations  1612 ,  1614 ,  1616 , and  1618 . In some embodiments, as described above in reference to  FIG. 15A  at (B), one or more of preview image  1610  and/or representations  1612 ,  1614 ,  1616 , and  1618  is updated in response to user selection of an option for one or more editable aspects of the represented user interface. 
     The user interface screen shown in  FIG. 16B  also includes indication  1630 , which indicates the watch face type of the user interface represented by  1610  (in this example, “modular”). The user interface screen also includes selection affordance  1632 . In some embodiments, the user contacts display  1302  at selection affordance  1632  to select the user interface represented by  1610 . In some embodiments, in response to detecting the contact at selection affordance  1632 , device  1300  sends instructions to device  1320  to display the context-specific user interface represented by  1610  (e.g., as configured on the user interface screen illustrated in  FIG. 16B ) on display  1322 . In some embodiments, in response to detecting the contact at selection affordance  1632 , device  1300  sends instructions to device  1320  to add the context-specific user interface represented by  1610  (e.g., as configured on the user interface screen illustrated in  FIG. 16B ) to the library. In some embodiments, the context-specific user interface represented by  1610  (e.g., as configured on the user interface screen illustrated in  FIG. 16B ) is added to the library at a first position in the sequence of the library. In some embodiments, in response to detecting the contact at selection affordance  1632 , device  1300  animates preview image  1610  to move on-screen toward affordance  1308  for viewing one or more user interfaces from the library. This indicates to the user that the selected user interface has been added to the stored library (representations of which are accessible for viewing by contacting affordance  1308 , which in some embodiments leads to the display of a user interface screen similar to that shown in  FIG. 14A  at (A)). 
     In some embodiments, in response to detecting the contact at selection affordance  1632 , device  1300  determines whether the represented user interface includes a complication associated with an application that is not currently installed on device  1320 . For example, the user interface may have been selected at least in part based on a criterion that the user interface is configured with a complication associated with an application for use on device  1320  that corresponds with an application installed on device  1300 , but the application for use on device  1320  is not currently installed on device  1320 . In some embodiments, in accordance with a determination that the represented user interface does not include a complication associated with an application that is not currently installed on device  1320 , device  1300  sends instructions to device  1320  to store the user interface in the library and/or display the user interface on display  1322 . 
     In some embodiments, device  1300  has a setting that allows the user to select whether to automatically install the application or first display a prompt to install the application. In some embodiments, in accordance with a determination that the represented user interface includes a complication associated with an application that is not currently installed on device  1320 , device  1300  sends instructions to device  1320  for installing the application in the memory of device  1320  (e.g., from an external server). In some embodiments, this means that device  1320  installs the application automatically in the background, e.g., without alerting the user. In some embodiments, in accordance with a determination that the represented user interface includes a complication associated with an application that is not currently installed on device  1320 , device  1300  displays a user prompt on display  1302  for installing the application configured for use on device  1320  (e.g., a displayed “install” affordance). In some embodiments, in response to detecting a contact on the displayed “install” affordance, device  1300  sends instructions to device  1320  for installing the application in the memory of device  1320  (e.g., from an external server). In some embodiments, this means that device  1320  installs the application automatically in the background, e.g., without alerting the user. In some embodiments, the application is installed directly by device  1320 , by instructing device  1320  to install the application via device  1300 , or by device  1300  obtaining the application configured for use on device  1320  and then sending the application to device  1320  for installation. 
     The user interface screen shown in  FIG. 16B  also includes description bar  1634  and text element  1636 . In some embodiments, text element  1636  includes a description of the watch face type according to which the user interface represented by preview image  1610  is configured. Text element  1636  includes description(s) that help the user understand the functionalities of the corresponding watch face type, e.g., in the event that the watch face type has not been used previously on device  1320 . 
     The user interface screen shown in  FIG. 16B  also includes editable aspect bar  1504  (in this case, the aspect is a color of the user interface), one or more affordances (e.g.,  1506 ) indicating options for the editable aspect (in this case, color options), and text element  1508  that provides a text description of an available option (e.g., a currently selected option). In some embodiments, the news application has a designated color associated with the complication when displayed as part of the context-specific user interface (e.g., on display  1322  of device  1320 ). For example, the designated color may be a “hero” or predominant color designated during development of the application as part of a software development kit. In some embodiments, device  1300  selects a color for the selected watch face type (e.g., a color indicated by  1506  and/or  1508 ) based at least in part on the designated color. For example, the selected color may be part of the discrete set of graphical assets used in configuration of the context-specific user interface. In some embodiments, the selected color matches the designated color. In some embodiments, the selected color is the closest color, e.g., as part of the discrete set of graphical assets in memory of device  1320 , to the designated color. 
     The user interface screen shown in  FIG. 16B  also includes complications bar  1520  and associated affordances  1640 ,  1642 ,  1644 ,  1646 , and  1648  that represent available complication slots or platters of the user interface and indicate the currently selected complication option for each slot or platter (which may include not displaying a complication at the slot or platter). Affordance  1640 , as represented by representation  1618 , indicates that the top left complication slot or platter is currently configured to display a complication that shows information obtained from a calendar application. 
     Affordances  1642  and  1644 , as represented by representations  1612  and  1614  (respectively), indicate that the middle complication slot or platter is currently configured to display a complication that shows information obtained from the news application and that the lower right complication slot or platter is currently configured to display a complication that shows information obtained from the news application. Since the user accessed this user interface by selecting a preview image that was presented as having a news-associated complication, and/or the corresponding user interface was selected based on one or more criteria related to surfacing the news complication to the user, at least one of the complications shown in this user interface is associated with the news application. 
     In this case, the complications represented by  1612  and  1614  are both associated with the news application but display a different type and/or amount of information (e.g., a different set of application information) from the news application. As such, the news application supports two different complication configurations for use on the context-specific user interface. In some embodiments, device  1300  determines whether the news application supports multiple complication configurations, and in accordance with a determination that the application supports multiple complication configurations, displays a preview image (e.g.,  1610 ) that contains a representation of a complication configured according to the first complication configuration (e.g.,  1612 ) and a representation of a complication configured according to the second complication configuration (e.g.,  1614 ). This lets the user know that the selected watch face type supports multiple complication configurations for the associated application, thereby introducing another functionality of the user interface. In some embodiments, in accordance with a determination that the application does not support multiple complication configurations, displays a preview image that contains a representation of a complication configured according to a complication configuration. 
     The user can edit select an option for one or more editable aspects of the user interface represented by  1610 . For example, the user changes the application associated with the complication in the lower right slot or platter (as represented by  1644 ) by contacting the display with touch  1660  at affordance  1644 . In some embodiments, in response to detecting touch  1660 , the user interface screen expands a scrollable menu on display  1302  in which the user swipes horizontally to scroll through the available applications, and optionally contacts a “done” affordance to select a particular option. In some embodiments, the scrollable menu includes one or more applications installed on device  1320  for which a complication is available. 
     In this example, the user contacts the “done” affordance, and in response device  1300  displays the user interface screen shown on display  1302  in  FIG. 16C . Comparing the user interface screens shown in  FIGS. 16B and 16C , the application indicated by affordance has been updated to “weather” from “news” as a result of the user editing. In addition, representation  1614  has been updated to display a temperature obtained from the weather application (e.g., either in accordance with updated data from the weather application, or a placeholder). In some embodiments, device  1300  animates a transition of representation  1614  on preview image  1610 , e.g., as a slot machine-style rollover from news data to weather data. 
     In some embodiments, representations  1612  and/or  1614 , as part of preview image  1610 , display live application data obtained from the news application (e.g., a version of the news application installed on device  1300 ). In some embodiments, representations  1612  and/or  1614 , as part of preview image  1610 , display placeholder data that represents information from the news application. 
     In some aspects, it is advantageous to present to the user different watch face types configured with a particular complication. For example, the user may wish to view a complication as part of a particular configuration, or in combination with a different set of user interface aspects, options, and/or functionalities. It is desirable to present the user with multiple contexts (e.g., context-specific user interfaces) in which a particular complication is available for use in order to demonstrate a greater range of the complication&#39;s potential functionalities and/or display styles. 
       FIG. 17  illustrates exemplary electronic device  1300 . In some embodiments, device  1300  is one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a display  1302  (e.g., a touch-sensitive display). In some embodiments, device  1300  is coupled to a second device (e.g.,  1320 ), which may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For example, device  1300  can be coupled via wireless communication to a personal electronic device similar to device  1320  or device  500  as depicted in  FIG. 5A , with a touch-sensitive display and a rotatable input mechanism. 
     In  FIG. 17  at (A), device  1300  displays an exemplary user interface screen on display  1302 . The user interface screen includes preview image  1610 , among other features in common with  FIG. 16A . The user touches preview image  1610  with touch  1626  to select the corresponding user interface for viewing, editing, and/or addition to the library. 
     In response to detecting touch  1626 , device  1300  displays an exemplary user interface screen on display  1302 , as shown in  FIG. 17  at (B). The user interface screen includes preview image  1610 , affordances representing complication slots or platters  1640 ,  1642 ,  1644 ,  1646 , and  1648 , among other features in common with  FIG. 16B . The user interface screen in  FIG. 17  at (B) also includes bar  1650  and associated user interface preview images  1700  and  1710 . 
     User interface preview image  1700  represents a context-specific user interface that, like the user interface represented by  1610 , includes a news complication. This complication is represented in user interface preview image  1700  by representation  1702 . Preview image  1700  also includes representation  1704  of an analog clock. Compared to the user interface represented by  1610 , the user interface represented by preview image  1700  is configured according to a different watch face type (e.g., “utility” instead of “modular”). Similarly, preview image  1710  represents a user interface configured according to a third watch face type (e.g., “color”) that includes a news complication, as represented in  1710  by representation  1712 . Thus, bar  1650  and its associated preview images provide the user with additional watch face configurations that feature the news complication. 
     In some embodiments, in response to detecting a contact on display  1302  at preview image  1700  or  1710 , device  1300  displays a user interface screen similar to that shown in  FIG. 17  at (B), but with the corresponding preview image and one or more editable aspects and options for the corresponding user interface (e.g., a list of one or more complication slots or platters and associated locations and/or applications for each). 
       FIG. 18  illustrates exemplary electronic device  1300 . In some embodiments, device  1300  is one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a display  1302  (e.g., a touch-sensitive display). In some embodiments, device  1300  is coupled to a second device (e.g.,  1320 ), which may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For example, device  1300  can be coupled via wireless communication to a personal electronic device similar to device  1320  or device  500  as depicted in  FIG. 5A , with a touch-sensitive display and a rotatable input mechanism. 
     In  FIG. 18  at (A), device  1300  displays an exemplary user interface screen on display  1302 . The user interface screen includes featured complications bar  1606  displayed in association with user interface preview images  1610  and  1620 . In this instance, the user wishes to view more types of featured complications. The user provides touch  1800  on display  1302  at “see all” affordance  1802 . 
     In response to detecting touch  1800 , device  1300  displays the user interface screen shown in  FIG. 18  at (B). This user interface includes user interface objects  1804 ,  1806 , and  1808 . Each user interface object indicates a group of user interface preview images, viewable on display  1302 , that represent user interfaces containing a complication associated with an application. In this example, preview images associated with affordance  1804  represent user interfaces with one or more news complications, preview images associated with affordance  1806  represent user interfaces with one or more pace complications, and preview images associated with affordance  1808  represent user interfaces with one or more sports complications. 
     User interface preview images  1610  and  1820  represent user interfaces that include one or more news complications, as shown by representations  1612  and  1614  in preview image  1610  and representation  1822  in preview image  1820 . User interface preview images  1610  and  1820  represent user interfaces that include a clock (e.g., as shown by representation  1616  of a digital clock in preview image  1610  and representation  1824  of an analog clock in preview image  1820 ). Thus, a plurality of preview images representing a plurality of user interfaces, configured according to different watch face types but including the same complication, are presented to the user. 
     Similarly, user interface preview images  1810  and  1620  represent user interfaces that include one or more pace complications, as shown by representations  1812  and  1814  in preview image  1810  and representation  1622  in preview image  1620 . User interface preview images  1810  and  1620  represent user interfaces that include a clock (e.g., as shown by representation  1816  of a digital clock in preview image  1810  and representation  1624  of an analog clock in preview image  1620 ). 
     This user interface screen provides the user with an expanded menu of potential clock faces configured with a variety of complications. In some embodiments, the user can scroll through various user interface preview images within a complication type by swiping horizontally on the display. In some embodiments, the user can scroll through various complication types, e.g., grouped by associated application, and through corresponding user interface preview images within each complication type by swiping vertically on the display. For example, the partial view of preview images shown in association with affordance  1808  indicates to the user that additional preview images containing the sports complication are viewable by scrolling the user interface screen. 
     In some embodiments, as shown by preview images  1610 ,  1820 ,  1810 , and  1620 , multiple supported watch face types are shown for one or more complications. In other words, this user interface screen indicates to the user that the news complication is supported for use on the modular and utility watch face types, as is the pace complication. In some embodiments, preview images for multiple complications are displayed in the same order according to watch face type (in this example, modular then utility). These features allow the user to understand which complications are supported for use in which particular watch face types. Thus, this user interface presents watch face types for each complication to the user in a predictable manner (by virtue of a common order), such that the user can immediately understand which, and/or how many, watch face types support a complication of interest. 
     The user interface screen also includes information affordance  1830 . In some embodiments, device  1300  detects a contact on display  1302 , and in response to detecting the contact the device provides a set of information about the corresponding application; or a hyperlink or other navigation to an application store, website, or other external server from which the corresponding application may be downloaded. Thus, the user is sent to an external site that can provide additional information and/or purchase details for an application corresponding to one or more complications of the user interface. 
     While the user interface screen shown in  FIG. 16A  features new complications to a user, a user may also wish to view new and/or unused watch face types.  FIG. 19  illustrates exemplary electronic device  1300 . In some embodiments, device  1300  is one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For purposes of illustration, first device  1300  is a personal electronic device, similar to portable multifunction device  100  as depicted in  FIG. 4A , with a display  1302  (e.g., a touch-sensitive display). In some embodiments, device  1300  is coupled to a second device (e.g.,  1320 ), which may be one or more of devices  100  ( FIG. 1 ),  300  ( FIG. 3 ), and/or  500  ( FIG. 5 ). For example, device  1300  can be coupled via wireless communication to a personal electronic device similar to device  1320  or device  500  as depicted in  FIG. 5A , with a touch-sensitive display and a rotatable input mechanism. 
     In  FIG. 19 , device  1300  displays an exemplary user interface screen on display  1302 . The user interface screen includes header  1900 , indicating that the user interface screen is a gallery for context-specific user interfaces. Bar  1902  indicates one or more context-specific user interfaces that are “new,” or configured according to one or more watch face types that were recently installed in memory of device  1320  (e.g., within a predetermined period of time, or installed in the latest operating system update). Displayed as associated with bar  1902  are one or more user interface preview images (e.g., preview image  1904 ) representing user interfaces configured according to the one or more new watch face types. The user interface screen also displays affordance  1908 , which the user can contact to access the user interface screen illustrated in  FIG. 16A  (e.g., by contacting the displayed affordance  1908 ). 
     Bar  1906  indicates one or more context-specific user interfaces configured according to featured watch face types. Displayed as associated with bar  1906  are user interface preview images  1620  and  1910 . User interface preview image  1620  represents a context-specific user interface that includes a complication (as represented by representation  1622 ) and an analog clock (as represented by representation  1624 ). User interface preview image  1910  represents a context-specific user interface that includes two complications (as represented by representations  1912  and  1914 ) and an analog clock (as represented by representation  1916 ). 
     The user interfaces represented by  1620  and  1910  include different types of complications (e.g., a pace complication represented by  1622 , a calendar complication represented by  1912 , and a battery monitoring complication represented by  1914 ). However, the user interfaces represented by  1620  and  1910  are both configured according to a “utility” watch face type. Thus, the user interface illustrated in  FIG. 19  introduces the user to different configurations or customizations that are possible within a particular watch face type. In some embodiments, other editable aspects such as color, display density, or any of the other editable aspects described herein may be varied in the series of user interface preview images. In some embodiments, the user can swipe horizontally on display  1302  to view additional user interface preview images of the “utility” type or swipe vertically on display  1302  to view additional user interface preview images of another watch face type. 
       FIGS. 20A-20I  are flow diagrams illustrating process  2000  for configuring context-specific user interfaces. In some embodiments, process  2000  can be performed at an electronic device with a display, one or more processors, and memory, such as  100  ( FIG. 4A ) or  1300  ( FIGS. 13-19 ). Some operations in process  2000  can be combined, the order of some operations may be changed, and some operations may be omitted. Process  2000  provides for configuring, at a first device, context-specific user interfaces for display at a second device, potentially conserving battery usage at the second device, enhancing the user visibility of the display, and making user recognition of the information more efficient, potentially reducing display time and improving battery life. 
     In  FIG. 20A , at block  2002 , process  2000  is performed at a first electronic device, having a display, memory, and one or more processors, coupled via wireless communication to a second electronic device having a display, memory, one or more processors, and access to a library of one or more user interfaces for display on the second electronic device. For example, in some embodiments, the library of one or more user interfaces for display on the second electronic device is stored in the memory of the first and/or the second electronic device(s). Exemplary first and second devices are device  1300  of  FIGS. 13-19  and device  1320  of  FIG. 13 , respectively. 
     At block  2004 , the first device displays a first user interface screen comprising at least a first user interface preview image. The first user interface preview image represents a first user interface for display on the second electronic device, is configured according to a first watch face type, and comprises a clock and at least a first complication. The first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication. Exemplary user interface preview images are illustrated throughout  FIGS. 13-19 , including, inter alia, preview image  1610  with a representation of digital clock  1616  and representations  1612 ,  1614 , and  1616  of complications. The first user interface is selected based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory of the first electronic device. 
     In accordance with some embodiments, at block  2006 , the first device displays, as part of the first user interface screen, a second user interface preview image. The second user interface preview image represents a second user interface for display on the second electronic device, is configured according to a second watch face type, and comprises a clock and at least a second complication. The second user interface preview image comprises representations of the second watch face type, the clock, and the at least second complication of the second user interface. The second user interface is independently selected based at least in part on the one or more criterion. In some embodiments, the second watch face type is different from the first watch face type. In some embodiments, the second complication is different from the first complication. Exemplary user interface preview images are illustrated throughout  FIGS. 13-19 , including, inter alia, preview image  1620  with a representation of analog clock  1624  and representation  1622  of a complication. 
     Turning now to  FIG. 20B  at block  2008 , in accordance with some embodiments, the first user interface is selected based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application currently installed in the memory of the first electronic device (the application for use on the second electronic device is not currently installed in the memory of the second electronic device). For example, in some embodiments, the user interface represented by  1610  includes the complications, represented by  1612  and  1614 , associated with a news application, for which the version configured for use on device  1320  is not currently installed on device  1320 , but the version configured for use on device  1300  is currently installed on device  1300 . 
     In accordance with some embodiments, at block  2010 , the first user interface is selected based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application currently installed in the memory of the first electronic device (the application for use on the second electronic device was installed in the memory of the second electronic device within a predetermined period of time). For example, in some embodiments, the user interface represented by  1610  includes the complications, represented by  1612  and  1614 , associated with a news application, for which the version configured for use on device  1320  was installed within a predetermined period of time on device  1320 , and the version configured for use on device  1300  is currently installed on device  1300 . 
     In accordance with some embodiments, at block  2012 , the first user interface is selected based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory of the first electronic device within a predetermined period of time. For example, in some embodiments, the user interface represented by  1610  includes the complications, represented by  1612  and  1614 , associated with a news application, for which the version configured for use on device  1300  was installed within a predetermined period of time on device  1300 . 
     In accordance with some embodiments, at block  2014 , the first user interface is selected based at least in part on a determination that the first user interface has a complication associated with a designated (e.g., sponsored, or curated) application. For example, in some embodiments, the user interface represented by  1610  includes the complications, represented by  1612  and  1614 , associated with a news application, which is part of a curated or sponsored list of applications. 
     Turning now to  FIG. 20C  at block  2016 , in accordance with some embodiments, the first user interface is selected based at least in part on a determination that the first user interface has a complication associated with an application that is used above a predetermined frequency of use on the first electronic device. For example, in some embodiments, the user interface represented by  1610  includes the complications, represented by  1612  and  1614 , associated with a news application, which is used above a predetermined frequency of use on device  1300 . 
     In accordance with some embodiments, at block  2018 , the first device receives a user input corresponding to a selection of the first user interface preview image. An exemplary user input is illustrated in  FIG. 17  as touch  1626 . 
     In accordance with some embodiments, at block  2020 , in response to receiving the user input, the first device ceases to display the first user interface screen; and displays a second user interface screen. The second user interface screen comprises the first user interface preview image (e.g.,  1610  in  FIG. 17  at (B)), a list of one or more complications of the first user interface (the list comprises at least the first complication; e.g.,  1520 ,  1640 ,  1642 ,  1644 ,  1646 , and  1648  in  FIG. 17  at (B)), and a selection affordance for selecting the first user interface (e.g.,  1632  in  FIG. 17  at (B)). 
     In accordance with some embodiments, at block  2022 , the first device receives a user input corresponding to a selection of the selection affordance. For example, the user input may be a touch on displayed affordance  1632 . 
     In accordance with some embodiments, at block  2024 , in response to receiving the user input, the first device sends instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     Turning now to  FIG. 20D  at block  2026 , in accordance with some embodiments, in response to receiving the user input, the first device stores the first user interface as part of the library of one or more user interfaces for display on the second electronic device (e.g., by storing directly on the memory of the first device, or by sending instructions to the second device for storing). 
     In accordance with some embodiments, at block  2028 , the first device displays, as part of the first user interface screen, an affordance for viewing a user interface from the library. 
     In accordance with some embodiments, at block  2030 , the first device, in response to receiving the user input, displays an animation depicting a movement of the first user interface preview image toward the affordance for viewing the user interface from the library. In some embodiments, device  1300  animates preview image  1610  to move on-screen toward affordance  1308  for viewing one or more user interfaces from the library. 
     In accordance with some embodiments, at block  2032 , the display of the first electronic device is a touch-sensitive display, and receiving the user input corresponding to a selection of the first user interface preview image comprises detecting a contact on the display at the first user interface preview image (e.g., touch  1626  in  FIG. 17  at (A)). 
     In accordance with some embodiments, at block  2034 , in response to receiving the user input, the first device determines whether the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device. 
     Turning now to  FIG. 20E  at block  2036 , in accordance with some embodiments, and in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device, the first device sends instructions to the second electronic device for installing the application associated with the complication of the first user interface in the memory of the second electronic device. 
     In accordance with some embodiments, at block  2038 , and in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device, the first device displays a user prompt to install the application associated with the complication of the first user interface in the memory of the second electronic device. 
     In accordance with some embodiments, at block  2040 , and in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is currently installed on the second electronic device, the first device sends to the second electronic device the instructions for displaying the first user interface on the display of the second electronic device (e.g., as depicted in block  2024 ). 
     In accordance with some embodiments, at block  2042 , the first device has a touch-sensitive display, and after displaying the first user interface screen, the first device detects a user swipe on the display at a location of the first user interface preview image. For example, in some embodiments the user swipes display  1302  at  1312  as shown in  FIG. 15A  at (A). 
     In accordance with some embodiments, at block  2044 , in response to detecting the swipe, the first device scrolls the first user interface preview image to reveal a third user interface preview image representing a third user interface for display on the display of the second electronic device. 
     In accordance with some embodiments, at block  2046 , prior to scrolling the first user interface preview image, the first device displays a partial view of the third user interface preview image (the scrolling reveals a complete view of the third user interface preview image). For example,  1314  is shown in partial view in  FIG. 15A  at (A). 
     Turning now to  FIG. 20F  at block  2048 , in accordance with some embodiments, the first and the second user interfaces are part of a prioritized list of user interfaces, and two or more user interfaces of the list are prioritized at least in part based on the one or more criteria. Optionally, the first device de-prioritizes a user interface of the prioritized list. The user interface is de-prioritized based at least in part on one or more criteria selected from: the user interface is already represented in the library; the user interface has a complication that is already represented in a user interface in the library; and the prioritized list comprises a user interface of the same watch face type as the de-prioritized user interface that is adjacent to the de-prioritized user interface in the prioritized list. 
     In accordance with some embodiments, at block  2050 , the first device displays, as part of the first user interface screen, an affordance for viewing additional user interface preview images. An exemplary affordance is shown as affordance  1802  in  FIG. 18  at (A). 
     In accordance with some embodiments, at block  2052 , the first device receives a user input corresponding to a selection of the affordance for viewing additional user interface preview images (e.g., touch  1800  at affordance  1802 ). 
     In accordance with some embodiments, at block  2054 , in response to receiving the user input, the first device ceases to display the first user interface screen; and displays a third user interface screen (e.g., as shown in  FIG. 18  at (B)) comprising a plurality of user interface preview images representing a plurality of user interfaces for display on the second electronic device. The plurality of user interfaces comprises a fourth user interface that comprises the first complication, and the fourth user interface is configured according to a watch face type other than the first watch face type. For example,  FIG. 18  at (B) illustrates preview images  1610  and  1820  that include a news complication. 
     Turning now to  FIG. 20G  at block  2056 , in accordance with some embodiments, and in response to receiving the user input, the first device displays as part of the third user interface screen a second plurality of user interface preview images representing a second plurality of user interfaces for display on the second electronic device. The second plurality of user interfaces comprises a fifth user interface that comprises a second complication different from the first complication. For example,  FIG. 18  at (B) illustrates preview images  1810  and  1620  that include a pace complication. Optionally, the first plurality of user interface preview images are displayed in order according to watch face type, and the second plurality of user interface preview images are displayed in the same order according to watch face type (cf. preview images  1610  and  1820  with  1810  and  1620 ). 
     In accordance with some embodiments, at block  2058 , the first complication of the first user interface displays a set of data obtained from an application when displayed on the display of the second electronic device, and the representation of the first complication in the first user interface preview image displays the set of data obtained from the application (e.g., live application data). In some embodiments, representation  1612  in  FIG. 17  at (B) shows a live headline from the news application. 
     In accordance with some embodiments, at block  2060 , the first complication of the first user interface displays a set of data obtained from an application when displayed on the display of the second electronic device, and the representation of the first complication in the first user interface preview image displays a placeholder representation of the set of data obtained from the application. For example, the placeholder may be part of the application data obtained during installation, and/or it may be designated as part of the development of the application, e.g., as part of a software development kit. In some embodiments, representation  1612  in  FIG. 17  at (B) shows a placeholder headline from the news application. 
     In accordance with some embodiments, at block  2062 , the first device displays, as part of the first user interface screen, a fourth user interface preview image that represents a fourth user interface configured according to a fourth watch face type. In some embodiments, the fourth watch face type was installed in the memory of the second electronic device within a predetermined period of time. 
     Turning now to  FIG. 20H  at block  2064 , in accordance with some embodiments, the first device, prior to displaying the first user interface screen, selects the first watch face type of the first user interface. The first watch face type is selected based at least in part on a criterion that the application with which the first complication of the first user interface is associated is supported for use in the selected first watch face type. Optionally, the first watch face type is selected based at least in part on a criterion that the selected first watch face type is represented in one or more user interfaces that are displayed on the display of the second electronic device above a predetermined frequency of display. Optionally, the first watch face type is selected based at least in part on a criterion that the selected first watch face type is represented in one or more user interfaces that were displayed on the display of the second electronic device within a fourth predetermined period of time. Optionally, the first watch face type is selected based at least in part on a criterion that the library comprises a user interface configured according to the first watch face type that comprises a complication that has been edited by the user. Optionally, the first watch face type is selected based at least in part on a criterion that the library does not already comprise a user interface that is configured according to the first watch face type and further comprises the first complication. Optionally, selecting the first watch face type further comprises selecting a color of the first watch face type, and the color of the first watch face type is selected based at least in part on a designated color of the application associated with the first complication (e.g., a “hero” or predominant color designated during development of the application as part of a software development kit). 
     Turning now to  FIG. 20I  at block  2066 , in accordance with some embodiments, prior to displaying the first user interface screen, the first device determines whether the first complication of the first user interface is associated with an application that supports a first and a second complication configuration (the first and the second complication configurations are different). 
     In accordance with some embodiments, at block  2068 , and in accordance with a determination that the first complication of the first user interface is associated with an application that supports the first and the second complication configurations, the first device displays, as part of the first user interface preview image, a first representation of the complication according to the first complication configuration and a second representation of the complication according to the second complication configuration. For example, the user interface represented by preview image  1610  supports multiple complication configurations, as depicted by representations  1612  and  1614  of the news application. 
     In accordance with some embodiments, at block  2070 , and in accordance with a determination that the first complication of the first user interface is associated with an application that does not support a second complication configuration, the first device displays, as part of the first user interface preview image, the first representation of the complication according to the first complication configuration. 
     It should be understood that the particular order in which the operations in  FIGS. 20A-20I  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. 
     Note that details of the processes described above with respect to method  2000  (e.g.,  FIGS. 20A-20I ) are also applicable in an analogous manner to the methods described elsewhere in this application. For example, other methods described in this application may include one or more of the characteristics of method  2000 . For example, the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described above with respect to method  2000  may share one or more of the characteristics of the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described elsewhere in this application with respect to other methods. Moreover, the techniques described above with respect to method  2000  may be used in combination with any of the interfaces, faces, or complications described elsewhere in this application. 
       FIGS. 21A-21D  are flow diagrams illustrating process  2100  for configuring context-specific user interfaces. In some embodiments, process  2100  can be performed at an electronic device with a display, one or more processors, and memory, such as  100  ( FIG. 4A ) or  1300  ( FIGS. 13-19 ). Some operations in process  2100  can be combined, the order of some operations may be changed, and some operations may be omitted. Process  2000  provides for configuring, at a first device, context-specific user interfaces for display at a second device, potentially conserving battery usage at the second device, enhancing the user visibility of the display, and making user recognition of the information more efficient, potentially reducing display time and improving battery life. 
     In  FIG. 21A , at block  2102 , process  2100  is performed at a first electronic device, having a touch-sensitive display, memory, and one or more processors, coupled via wireless communication to a second electronic device having a display, memory, one or more processors, and access to a library of one or more user interfaces for display on the second electronic device. For example, in some embodiments, the library of one or more user interfaces for display on the second electronic device is stored in the memory of the first and/or the second electronic device(s). Exemplary first and second devices are device  1300  of  FIGS. 13-19  and device  1320  of  FIG. 13 , respectively. 
     At block  2104 , the first device displays a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second electronic device. The first user interface is configured according to a first watch face type and comprises a clock and at least a first complication. The first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication. The first user interface is not already in the library of user interfaces for display on the second electronic device. Exemplary preview images are illustrated throughout  FIGS. 13-19 ; see, e.g.,  1610  in  FIG. 17  at (A). 
     At block  2106 , the first device detects a first contact at the displayed first user interface preview image (e.g., touch  1626 ). 
     At block  2108 , in response to detecting the first contact, the first device ceases to display the first user interface screen and displays a second user interface screen comprising: the first user interface preview image (e.g.,  1610  in  FIG. 17  at (B)); a list of one or more complications of the first user interface (the list comprises at least the first complication; e.g.,  1520 ,  1640 ,  1642 ,  1644 ,  1646 , and  1648  in  FIG. 17  at (B)); a selection affordance for selecting the first user interface (e.g.,  1632  in  FIG. 17  at (B)); and a second user interface preview image. The second user interface preview image represents a second user interface, is configured according to a second watch face type, and comprises a clock and the first complication. The second watch face type is different from the first watch face type. For example, preview images  1700  and  1710  represent user interfaces configured according to different watch face types as compared to that represented by  1610 , but also include a clock (e.g., as represented by  1704  and  1714 ) and the news complications (e.g., as represented by  1702  and  1712 ). 
     At block  2110 , the first device detects a second contact at the selection affordance (e.g., a contact at  1632 ). 
     At block  2112 , in response to detecting the second contact, the first device sends instructions to the second electronic device for displaying the first user interface on the display of the second electronic device. 
     Turning now to  FIG. 21B  at block  2114 , in accordance with some embodiments, the second user interface screen further comprises: a first editing affordance indicating a first option for an editable aspect of the first user interface; and a second editing affordance indicating a second option for the editable aspect of the first user interface. For example,  FIG. 15A  at (B) displays a number of different affordances (e.g.,  1506 ) for the color aspect of the user interface represented by  1312 . Optionally, the editable aspect is selected from a color of the first user interface, a density of the first user interface, a background of the first user interface, and a font of the first user interface. Optionally the first complication is a stopwatch affordance, and the editable aspect is a stopwatch timescale. Optionally, the first complication is an affordance that is associated with an application. Optionally, the editable aspect is the application associated with the first affordance. Optionally, the affordance displays a set of information obtained from the application, and the editable aspect is the set of information that is obtained from the application and displayed. Additional editable aspects are illustrated in  FIGS. 15B and 15C . 
     In accordance with some embodiments, at block  2116 , the second user interface screen further comprises a description of the first watch face type of the first user interface (e.g.,  1552 ). 
     In accordance with some embodiments, at block  2118 , the first device detects a third contact at the second user interface preview image. 
     Turning now to  FIG. 21C  at block  2120 , in accordance with some embodiments, and in response to detecting the third contact, the first device ceases to display the second user interface screen and displays a third user interface screen comprising: the second user interface preview image; a list of one or more complications of the second user interface (the list comprises at least the first complication); and a selection affordance for selecting the second user interface. For example, the user can contact preview image  1700  to display a user interface screen similar to that shown in  FIG. 17  at (B) for configuring the represented user interface. 
     In accordance with some embodiments, at block  2122 , the first option is a currently selected option for the editable aspect of the first user interface, the first user interface preview image represents the first option for the editable aspect, and the first device detects a fourth contact at the second editing affordance. 
     In accordance with some embodiments, at block  2124 , and in response to detecting the fourth contact, the first device updates the first user interface preview image to represent the second option for the editable aspect. Optionally, updating the first user interface preview image comprises animating a transition from the first option of the editable aspect to the second option. For example, representation  1614  in preview image  1610  may be animated to transition from the news information in  FIG. 16B  to the weather information in  FIG. 16C . 
     In accordance with some embodiments, at block  2126 , and in response to detecting the second contact at the affordance for selecting the first user interface (e.g., a touch at affordance  1632 ), the first device sends instructions to the second electronic device to add the first user interface to the library. 
     Turning now to  FIG. 21D  at block  2128 , in accordance with some embodiments, the second user interface screen further comprises an affordance for viewing the library of user interfaces for display on the second electronic device. In some embodiments, the first device, in response to detecting the second contact at the selection affordance, animates the first user interface preview image to translate on-screen toward the affordance for viewing the library of user interfaces. In some embodiments, device  1300  animates preview image  1610  to move on-screen toward affordance  1308  for viewing one or more user interfaces from the library. 
     In accordance with some embodiments, at block  2130 , after adding the first user interface to the stored library of user interfaces for display on the second electronic device, the first device detects a fifth contact at the affordance for viewing the library of user interfaces. 
     In accordance with some embodiments, at block  2132 , in response to detecting the fifth contact, the first device ceases to display the second user interface screen and displays a fourth user interface screen comprising the first user interface preview image; and a fourth user interface preview image (the fourth user interface preview image represents a fourth user interface that is part of the library of user interfaces for display on the second electronic device). 
     In accordance with some embodiments, at block  2134 , the first device visually distinguishes the first user interface preview image on the fourth user interface screen to indicate that the first user interface is newly added to the library. For example, a user interface object such as dot  1502  is displayed associated with preview image  1310  to indicate that the user interface is newly added to the library. 
     In accordance with some embodiments, at block  2136 , the first device displays a plurality of user interface preview images representing a plurality of user interfaces for display on the second electronic device. The plurality of user interfaces comprises two or more user interfaces that represent the same watch face type (see, e.g., preview images  1620  and  1910  in  FIG. 19 ). 
     It should be understood that the particular order in which the operations in  FIGS. 21A-21D  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. 
     Note that details of the processes described above with respect to method  2100  (e.g.,  FIGS. 21A-21D ) are also applicable in an analogous manner to the methods described elsewhere in this application. For example, other methods described in this application may include one or more of the characteristics of method  2100 . For example, the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described above with respect to method  2100  may share one or more of the characteristics of the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described elsewhere in this application with respect to other methods. Moreover, the techniques described above with respect to method  2100  may be used in combination with any of the interfaces, faces, or complications described elsewhere in this application. 
       FIGS. 22A-22F  are flow diagrams illustrating process  2200  for configuring context-specific user interfaces. In some embodiments, process  2200  can be performed at an electronic device with a display, one or more processors, and memory, such as  100  ( FIG. 4A ) or  1300  ( FIGS. 13-19 ). Some operations in process  2200  can be combined, the order of some operations may be changed, and some operations may be omitted. Process  2200  provides for configuring, at a first device, context-specific user interfaces for display at a second device, potentially conserving battery usage at the second device, enhancing the user visibility of the display, and making user recognition of the information more efficient, potentially reducing display time and improving battery life. 
     In  FIG. 22A , at block  2202 , process  2200  is performed at a first electronic device having a touch-sensitive display, memory, and one or more processors, coupled via wireless communication to a second electronic device having a display, one or more processors, and memory in which a library of one or more user interfaces for display on the second electronic device is stored. Exemplary first and second devices are device  1300  of  FIGS. 13-19  and device  1320  of  FIG. 13 , respectively. 
     At block  2204 , the first device displays a first user interface screen comprising at least a first and a second user interface preview image. The first and the second user interface preview images represent a first and a second user interface for display on the second electronic device, the first and the second user interfaces are configured according to a watch face type and comprise a clock, and the first and the second user interfaces are part of the stored library of user interfaces for display on the second electronic device. Exemplary preview images are described and illustrated through the present disclosure; see, e.g.,  1310  and  1312  in  FIG. 14A . 
     At block  2206 , the first device receives a first user input corresponding to a user request to reorder the stored library of user interfaces. For example,  FIG. 14A  shows touch  1400  on edit affordance  1318 . 
     At block  2208 , in response to receiving the first user input, the first device ceases to display the first user interface screen and displays a second user interface screen (e.g., as shown in  FIG. 14A  at (B)) comprising the first and the second user interface preview images. The relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library. 
     At block  2210 , the first device receives a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library. An exemplary user input is illustrated as touch and drag  1420  on affordance  1418 . 
     At block  2212 , in response to receiving the second user input, the first device sends instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     Turning now to  FIG. 22B  at block  2214 , in accordance with some embodiments, and in response to receiving the second user input, the first device re-displays the second user interface screen. The relative positions of the first user interface preview image and the second user interface preview image on the re-displayed second user interface screen reflect the re-ordering of the second user interface before the first user interface in the stored library (cf.  1410  and  1414  in  FIG. 14B  at (A) and  FIG. 14C  at (A)). 
     In accordance with some embodiments, at block  2216 , the first device displays an affordance for editing the stored library of user interfaces as part of the first user interface screen, and receiving the first user input comprises detecting a contact at the displayed affordance for editing the stored library of user interfaces (e.g., touch  1400  at affordance  1318 ). 
     In accordance with some embodiments, at block  2218 , the first device displays an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen. 
     In accordance with some embodiments, at block  2220 , after receiving the second user input, the first device detects a contact on the display at the affordance for completing editing of the stored library of user interfaces (e.g., touch  1422  at affordance  1424 ). 
     In accordance with some embodiments, at block  2222 , and in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces, the first device ceases to display the second user interface screen and re-displays the first user interface screen (the position of the second user interface preview image on the first user interface screen has shifted relative to the position of the first user interface preview image). This is illustrated in  FIG. 14C  at (B). 
     In accordance with some embodiments, at block  2224 , the first device displays a re-ordering affordance in association with the second user interface preview image as part of the second user interface screen (e.g.,  1418 ). 
     Turning now to  FIG. 22C  at block  2226 , in accordance with some embodiments, receiving the second user input corresponding to a user request to order the second user interface before the first user interface comprises: detecting a contact at a first position on the display at the re-ordering affordance; while continuing to detect the contact, detecting movement of the contact from the first position to a second position on the display without a break in the contact on the display (the second position on the display is on an opposite side of the displayed first user interface preview image relative to the first position); and in response to detecting the contact at the second position: translating the second user interface preview image on-screen in a direction of the movement of the contact; and translating the first user interface preview image on-screen in a direction opposite the movement of the contact. After translation of the first and the second user interface preview images, the relative positions of the first and the second user interface preview images reflect the re-ordering of the second user interface before the first user interface in the stored library. This is illustrated and described in reference to touch and drag  1420 . 
     In accordance with some embodiments, at block  2228 , the first device displays a delete affordance in association with the first user interface preview image as part of the second user interface screen. An exemplary affordance is shown as  1434  in  FIG. 14D  at (B). 
     In accordance with some embodiments, at block  2230 , the first device displays an affordance for revealing an edit option (the affordance for revealing an edit option is displayed in association with the first user interface preview image as part of the second user interface screen). An exemplary affordance is shown as  1432  in  FIG. 14D  at (A). 
     In accordance with some embodiments, at block  2232 , the first device detects a contact on the display at the affordance for revealing an edit option (e.g., touch  1430 ). 
     Turning now to  FIG. 22D  at block  2234 , in accordance with some embodiments, and in response to detecting the contact at the affordance for revealing an edit option, the first device displays a delete affordance in association with the first user interface preview image as part of the second user interface screen. An exemplary affordance is shown as  1434  in  FIG. 14D  at (B). Optionally, displaying the delete affordance comprises translating the first user interface preview image on-screen. This is shown in  FIG. 14D  at (B). 
     In accordance with some embodiments, at block  2236 , after displaying the delete affordance as part of the second user interface screen, the first device detects a contact on the display at the delete affordance displayed in association with the first user interface preview image (e.g., touch  1436 ). 
     In accordance with some embodiments, at block  2238 , in response to detecting the contact at the delete affordance, the first device removes the displayed first user interface preview image from the second user interface screen and sends instructions to the second electronic device for removing the first user interface from the stored library (see, e.g.,  FIG. 14E ). 
     In accordance with some embodiments, at block  2240 , the first device displays an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen. An exemplary affordance is shown as  1424 . 
     In accordance with some embodiments, at block  2242 , after detecting the contact at the delete affordance, the first device detects a contact on the display at the affordance for completing editing of the stored library of user interfaces (e.g., touch  1422 ). 
     Turning now to  FIG. 22E  at block  2244 , in accordance with some embodiments, and in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces, the first device ceases to display the second user interface screen; re-displays the first user interface screen (the first user interface screen comprises the first and the second user interface preview images); and animates the first user interface preview image to disappear from the display. This concept is illustrated in  FIG. 14F  with respect to preview image  1426 . 
     In accordance with some embodiments, at block  2246 , after animating the first user interface preview image to disappear from the display, the first device translates the second user interface preview image on-screen to occupy the position of the first user interface preview image before the animation. An exemplary translation is depicted by arrow  1446  and preview image  1444 . 
     In accordance with some embodiments, at block  2248 , while displaying the first user interface screen, the first device detects a swipe on the display at the first or the second user interface preview image. 
     In accordance with some embodiments, at block  2250 , in response to detecting the swipe, the first device scrolls the first and the second user interface preview images to reveal a third user interface preview image. The third user interface preview image represents a third user interface for display on the second electronic device and is part of the stored library. 
     Turning now to  FIG. 22F  at block  2254 , in accordance with some embodiments, prior to revealing the third user interface preview image, the first device displays as part of the first user interface screen a partial view of the third user interface preview image, such as the partial view of preview image  1314  in  FIG. 14A  at (A). 
     In accordance with some embodiments, at block  2256 , the first device displays, as part of the second user interface screen, text indications of the watch face types of the first and the second user interfaces. In some embodiments, the indications are displayed in association with the first and the second user interface preview images. Exemplary indications include 1408 in  FIG. 14A  at (B). 
     It should be understood that the particular order in which the operations in  FIGS. 22A-22F  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. 
     Note that details of the processes described above with respect to method  2200  (e.g.,  FIGS. 22A-22F ) are also applicable in an analogous manner to the methods described elsewhere in this application. For example, other methods described in this application may include one or more of the characteristics of method  2200 . For example, the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described above with respect to method  2200  may share one or more of the characteristics of the devices, hardware elements, inputs, interfaces, modes of operation, faces, time indicators, and complications described elsewhere in this application with respect to other methods. Moreover, the techniques described above with respect to method  2200  may be used in combination with any of the interfaces, faces, or complications described elsewhere in this application. 
     In accordance with some embodiments,  FIG. 23  shows an exemplary functional block diagram of an electronic device  2300  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  2300  are configured to perform the techniques described above. The functional blocks of the device  2300  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 23  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 23 , an electronic device  2300  includes a display unit  2302  configured to display a graphic user interface, a wireless communications unit  2304  configured to send and/or receive wireless communications, a memory unit  2310  configured to store data, optionally, a touch-sensitive surface unit  2312  configured to receive contacts, and a processing unit  2306  coupled to the display unit  2302 , wireless communications unit  2304 , memory unit  2310 , and optionally, touch-sensitive surface unit  2312 . In some embodiments, the processing unit  2306  includes a display enabling unit  2308 , a receiving unit  2314 , a sending unit  2316 , a storing unit  2318 , a selecting unit  2320 , a determining unit  2322 , a detecting unit  2324 , a scrolling enabling unit  2326 , and a de-prioritizing unit  2328 . In some embodiments, display unit  2302  is a touch-sensitive display unit that serves as touch-sensitive surface unit  2312 . In this example, electronic device  2300  is coupled via wireless communication (e.g., using wireless communications unit  2304 ) to a second electronic device (e.g., device  500  described herein) with a second display unit, a second memory unit, a second processing unit, and an accessing unit configured to provide access to a library of one or more user interfaces for display on the second display unit of the second electronic device. 
     The processing unit  2306  is configured to enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a first user interface screen comprising at least a first user interface preview image, the first user interface preview image representing a first user interface for display on the second display unit of the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on one or more criterion selected from the group consisting of: the first user interface is configured according to a watch face type not currently represented in a user interface in the library; the first user interface has a first complication not currently represented in a user interface in the library; and the first user interface has a first complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory unit of device  2300  (e.g., memory unit  2310 ). 
     In some embodiments, the processing unit  2306  is configured to enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a second user interface preview image, wherein the second user interface preview image is displayed as part of the first user interface screen, wherein the second user interface preview image represents a second user interface for display on the second display unit of the second electronic device, wherein the second user interface is configured according to a second watch face type and comprises a clock and at least a second complication, wherein the second user interface preview image comprises representations of the second watch face type, the clock, and the at least second complication of the second user interface, and wherein the second user interface is independently selected (e.g., using selecting unit  2320 ) based at least in part on the one or more criterion. 
     In some embodiments, the second watch face type is different from the first watch face type. 
     In some embodiments, the second complication is different from the first complication. 
     In some embodiments, the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application currently installed in the memory unit of device  2300  (e.g., memory unit  2310 ), and wherein the application for use on the second electronic device is not currently installed in the second memory unit of the second electronic device. 
     In some embodiments, the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application currently installed in the memory unit of device  2300  (e.g., memory unit  2310 ), and wherein the application for use on the second electronic device was installed in the second memory unit of the second electronic device within a first predetermined period of time. 
     In some embodiments, the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on a criterion that the first user interface has a complication associated with an application for use on the second electronic device that corresponds with an application installed in the memory unit of device  2300  (e.g., memory unit  2310 ) within a second predetermined period of time. 
     In some embodiments, the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on a determination that the first user interface has a complication associated with a designated application. 
     In some embodiments, the first user interface is selected (e.g., using selecting unit  2320 ) based at least in part on a determination that the first user interface has a complication associated with an application that is used above a predetermined frequency of use on device  2300 . 
     In some embodiments, the processing unit  2306  is configured to: receive (e.g., using receiving unit  2314 ) a user input corresponding to a selection of the first user interface preview image; in response to receiving the user input, enable ceasing of the display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of the first user interface screen; and in response to receiving the user input, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a second user interface screen, wherein the second user interface screen comprises the first user interface preview image, a list of one or more complications of the first user interface, wherein the list comprises at least the first complication, and a selection affordance for selecting the first user interface. 
     In some embodiments, the processing unit  2306  is configured to: receive (e.g., using receiving unit  2314 ) a user input corresponding to a selection of the selection affordance; and, in response to receiving the user input, send (e.g., using sending unit  2316 ) via the wireless communications unit (e.g., wireless communications unit  2304 ) instructions to the second electronic device for displaying the first user interface on the second display unit of the second electronic device. 
     In some embodiments, the processing unit  2306  is configured to: store (e.g., using storing unit  2318 ) on the memory unit (e.g., memory unit  2310 ) the first user interface as part of the library of one or more user interfaces for display on the second display unit of the second electronic device. 
     In some embodiments, the processing unit  2306  is configured to: enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of an affordance for viewing a user interface from the library as part of the first user interface screen; and, in response to receiving the user input, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of an animation depicting a movement of the first user interface preview image toward the affordance for viewing the user interface from the library. 
     In some embodiments, device  2300  further comprises a touch-sensitive surface unit (e.g., touch-sensitive surface unit  2312 ), and receiving the user input corresponding to a selection of the first user interface preview image comprises detecting (e.g., using detecting unit  2324 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2312 ) at the first user interface preview image. 
     In some embodiments, the processing unit  2306  is configured to: in response to receiving the user input, determine (e.g., using determining unit  2322 ) whether the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device; and in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device, and in response to receiving the user input, send (e.g., with sending unit  2316 ) via the wireless communications unit (e.g., wireless communications unit  2304 ) instructions to the second electronic device for installing the application associated with the complication of the first user interface in the second memory unit of the second electronic device. 
     In some embodiments, the processing unit  2306  is configured to: in response to receiving the user input, determine (e.g., using determining unit  2322 ) whether the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device; and in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is not currently installed on the second electronic device, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a user prompt to install the application associated with the complication of the first user interface in the second memory unit of the second electronic device. 
     In some embodiments, the instructions for displaying the first user interface on the second display unit of the second electronic device are sent to the second electronic device in accordance with a determination that the first user interface represented by the first user interface preview image comprises a complication associated with an application that is currently installed on the second electronic device. 
     In some embodiments, device  2300  further comprises a touch-sensitive surface unit (e.g., touch-sensitive surface unit  2312 ), and the processing unit  2306  is configured to: after displaying the first user interface screen, detect (e.g., with detecting unit  2324 ) a user swipe on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2312 ) at a location of the first user interface preview image; and in response to detecting the swipe, enable scrolling (e.g., with scrolling enabling unit  2326 ), on the display unit (e.g., display unit  2302 ), of the first user interface preview image to reveal a third user interface preview image representing a third user interface for display on the second display unit of the second electronic device. 
     In some embodiments, the processing unit  2306  is configured to: prior to scrolling the first user interface preview image, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a partial view of the third user interface preview image, wherein the scrolling reveals a complete view of the third user interface preview image. 
     In some embodiments, the first and the second user interfaces are part of a prioritized list of user interfaces, and wherein two or more user interfaces of the list are prioritized at least in part based on the one or more criteria. 
     In some embodiments, the processing unit  2306  is configured to: de-prioritize (e.g., with de-prioritizing unit  2328 ) a user interface of the prioritized list, wherein the user interface is de-prioritized based at least in part on one or more criteria selected from the group consisting of: the user interface is already represented in the library; the user interface has a complication that is already represented in a user interface in the library; and the prioritized list comprises a user interface of the same watch face type as the de-prioritized user interface that is adjacent to the de-prioritized user interface in the prioritized list. 
     In some embodiments, the processing unit  2306  is configured to: enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of an affordance for viewing additional user interface preview images as part of the first user interface screen; receive (e.g., using receiving unit  2314 ) a user input corresponding to a selection of the affordance for viewing additional user interface preview images; and in response to receiving the user input, enable ceasing of the display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of the first user interface screen; and in response to receiving the user input, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a third user interface screen comprising a plurality of user interface preview images representing a plurality of user interfaces for display on the second display unit of the second electronic device, wherein the plurality of user interfaces comprises a fourth user interface that comprises the first complication, and wherein the fourth user interface is configured according to a watch face type other than the first watch face type. 
     In some embodiments, the processing unit  2306  is configured to: in response to receiving the user input, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a second plurality of user interface preview images representing a second plurality of user interfaces for display on the second display unit of the second electronic device, wherein the second plurality of user interfaces comprises a fifth user interface that comprises a second complication, wherein the second complication is different from the first complication, and wherein the second plurality of user interface preview images is displayed as part of the third user interface screen. 
     In some embodiments, the first plurality of user interface preview images are displayed in order according to watch face type, and wherein the second plurality of user interface preview images are displayed in the same order according to watch face type. 
     In some embodiments, the first complication of the first user interface displays a set of data obtained from an application when displayed on the display of the second electronic device, and wherein the representation of the first complication in the first user interface preview image displays the set of data obtained from the application. 
     In some embodiments, the first complication of the first user interface displays a set of data obtained from an application when displayed on the display of the second electronic device, and wherein the representation of the first complication in the first user interface preview image displays a placeholder representation of the set of data obtained from the application. 
     In some embodiments, the processing unit  2306  is configured to: in response to receiving the user input, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), of a fourth user interface preview image as part of the first user interface screen, wherein the fourth user interface preview image represents a fourth user interface configured according to a fourth watch face type, wherein the fourth watch face type that was installed in the second memory unit of the second electronic device within a third predetermined period of time. 
     In some embodiments, the processing unit  2306  is configured to: prior to displaying the first user interface screen, select (e.g., with selecting unit  2320 ) the first watch face type of the first user interface, wherein the first watch face type is selected based at least in part on a criterion that the application with which the first complication of the first user interface is associated is supported for use in the selected first watch face type. 
     In some embodiments, the first watch face type is selected (e.g., with selecting unit  2320 ) based at least in part on a criterion that the selected first watch face type is represented in one or more user interfaces that are displayed on the second display unit of the second electronic device above a predetermined frequency of display. 
     In some embodiments, the first watch face type is selected (e.g., with selecting unit  2320 ) based at least in part on a criterion that the selected first watch face type is represented in one or more user interfaces that were displayed on the second display unit of the second electronic device within a fourth predetermined period of time. 
     In some embodiments, the first watch face type is selected (e.g., with selecting unit  2320 ) based at least in part on a criterion that the library comprises a user interface configured according to the first watch face type that comprises a complication that has been edited by the user. 
     In some embodiments, the first watch face type is selected (e.g., with selecting unit  2320 ) based at least in part on a criterion that the library does not already comprise a user interface that is configured according to the first watch face type and further comprises the first complication. 
     In some embodiments, selecting the first watch face type (e.g., with selecting unit  2320 ) further comprises selecting a color of the first watch face type, and wherein the color of the first watch face type is selected (e.g., with selecting unit  2320 ) based at least in part on a designated color of the application associated with the first complication. 
     In some embodiments, the processing unit  2306  is configured to: prior to displaying the first user interface screen, determine (e.g., with determining unit  2322 ) whether the first complication of the first user interface is associated with an application that supports a first and a second complication configuration, wherein the first and the second complication configurations are different; and in accordance with a determination that the first complication of the first user interface is associated with an application that supports the first and the second complication configurations, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), as part of the first user interface preview image, of a first representation of the complication according to the first complication configuration and a second representation of the complication according to the second complication configuration; and in accordance with a determination that the first complication of the first user interface is associated with an application that does not support a second complication configuration, enable display (e.g., with display enabling unit  2308 ), on the display unit (e.g., display unit  2302 ), as part of the first user interface preview image, of the first representation of the complication according to the first complication configuration. 
     The operations described above with reference to  FIGS. 20A-20I  are, optionally, implemented by components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  6 A- 19 . For example, displaying operation  2004  and displaying operation  2006  may be implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch-sensitive display  112 , and event dispatcher module  174  delivers the event information to application  136 - 1 . A respective event recognizer  180  of application  136 - 1  compares the event information to respective event definitions  186 , and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer  180  activates an event handler  190  associated with the detection of the event or sub-event. Event handler  190  may utilize or call data updater  176  or object updater  177  to update the application internal state  192 . In some embodiments, event handler  190  accesses a respective GUI updater  178  to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  6 A- 19 . 
     In accordance with some embodiments,  FIG. 24  shows an exemplary functional block diagram of an electronic device  2400  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  2400  are configured to perform the techniques described above. The functional blocks of the device  2400  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 24  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 24 , an electronic device  2400  includes a display unit  2402  configured to display a graphic user interface, a wireless communications unit  2404  configured to send and/or receive wireless communications, a touch-sensitive surface unit  2410  configured to receive contacts, optionally, a memory unit  2420  configured to store data, and a processing unit  2406  coupled to the display unit  2402 , wireless communications unit  2404 , touch-sensitive surface unit  2410 , and optionally, memory unit  2420 . In some embodiments, the processing unit  2406  includes a display enabling unit  2408 , a detecting unit  2412 , a sending unit  2414 , an updating unit  2416 , and an animation enabling unit  2418 . In some embodiments, display unit  2402  is a touch-sensitive display unit that serves as touch-sensitive surface unit  2410 . In this example, electronic device  2400  is coupled via wireless communication (e.g., using wireless communications unit  2404 ) to a second electronic device (e.g., device  500  described herein) with a second display unit, a second memory unit, a second processing unit, and an accessing unit configured to provide access to a library of one or more user interfaces for display on the second display unit of the second electronic device. 
     The processing unit  2406  is configured to enable display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of a first user interface screen comprising a first user interface preview image, the first user interface preview image representing a first user interface for display on the second display unit of the second electronic device, wherein the first user interface is configured according to a first watch face type and comprises a clock and at least a first complication, wherein the first user interface preview image comprises representations of the first watch face type, the clock, and the at least first complication, and wherein the first user interface is not already in the library of user interfaces for display on the second display unit of the second electronic device; detect (e.g., with detecting unit  2412 ) a first contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2410 ) at the displayed first user interface preview image; in response to detecting the first contact, enable ceasing of the display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of the first user interface screen; in response to detecting the first contact, enable display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of a second user interface screen comprising: the first user interface preview image; a list of one or more complications of the first user interface, wherein the list comprises at least the first complication; a selection affordance for selecting the first user interface; and a second user interface preview image, wherein the second user interface preview image represents a second user interface, wherein the second user interface is configured according to a second watch face type and comprises a clock and the first complication, and wherein the second watch face type is different from the first watch face type; detect (e.g., with detecting unit  2412 ) a second contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2410 ) at the selection affordance; and in response to detecting the second contact, send (e.g., with sending unit  2414 ) via the wireless communications unit (e.g., wireless communications unit  2404 ) instructions to the second electronic device for displaying the first user interface on the second display unit of the second electronic device. 
     In some embodiments, the second user interface screen further comprises: a first editing affordance, wherein the first editing affordance indicates a first option for an editable aspect of the first user interface; and a second editing affordance, wherein the second editing affordance indicates a second option for the editable aspect of the first user interface. 
     In some embodiments, the editable aspect is selected from the group consisting of a color of the first user interface, a density of the first user interface, a background of the first user interface, and a font of the first user interface. 
     In some embodiments, the first complication is a stopwatch affordance, wherein the editable aspect is a stopwatch timescale. 
     In some embodiments, the first complication is an affordance that is associated with an application. 
     In some embodiments, the editable aspect is the application associated with the first affordance. 
     In some embodiments, the affordance displays a set of information obtained from the application, and wherein the editable aspect is the set of information that is obtained from the application and displayed. 
     In some embodiments, the second user interface screen further comprises: a description of the first watch face type of the first user interface. 
     In some embodiments, the processing unit  2406  is further configured to: detect (e.g., with detecting unit  2412 ) a third contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2410 ) at the second user interface preview image; in response to detecting the third contact, enable ceasing of the display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of the second user interface screen; in response to detecting the third contact, enable display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of a third user interface screen comprising: the second user interface preview image; a list of one or more complications of the second user interface, wherein the list comprises at least the first complication; and a selection affordance for selecting the second user interface. 
     In some embodiments, the first option is a currently selected option for the editable aspect of the first user interface, wherein the first user interface preview image represents the first option for the editable aspect, and the processing unit  2406  is further configured to: detect (e.g., with detecting unit  2412 ) a fourth contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2410 ) at the second editing affordance; and in response to detecting the fourth contact, enable update (e.g., with updating unit  2416 ), on the display unit (e.g., display unit  2402 ), of the first user interface preview image to represent the second option for the editable aspect. 
     In some embodiments, updating the first user interface preview image comprises animating a transition from the first option of the editable aspect to the second option. 
     In some embodiments, the processing unit  2406  is further configured to: in response to detecting the second contact at the affordance for selecting the first user interface, send (e.g., with sending unit  2414 ) via the wireless communications unit (e.g., wireless communications unit  2404 ) instructions to the second electronic device to add the first user interface to the library. 
     In some embodiments, the second user interface screen further comprises an affordance for viewing (e.g., on display unit  2402 ) the library of user interfaces for display on the second display unit of the second electronic device, and the processing unit  2406  is further configured to: enable animation (e.g., with animation enabling unit  2418 ), on the display unit (e.g., display unit  2402 ), of the first user interface preview image to translate on-screen toward the viewing affordance in response to detecting the second contact at the selection affordance. 
     In some embodiments, the processing unit  2406  is further configured to: detect (e.g., with detecting unit  2412 ) a fifth contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2410 ) at the viewing affordance after adding the first user interface to the stored library of user interfaces for display on the second electronic device; in response to detecting the fifth contact, enable ceasing of the display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of the second user interface screen; and in response to detecting the fifth contact, enable display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of a fourth user interface screen comprising: the first user interface preview image; and a fourth user interface preview image, wherein the fourth user interface preview image represents a fourth user interface that is part of the library of user interfaces for display on the second display unit of the second electronic device. 
     In some embodiments, the processing unit  2406  is further configured to: enable visually distinguishing (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of the first user interface preview image on the fourth user interface screen to indicate that the first user interface is newly added to the library. 
     In some embodiments, the processing unit  2406  is further configured to: enable display (e.g., with display enabling unit  2408 ), on the display unit (e.g., display unit  2402 ), of a plurality of user interface preview images representing a plurality of user interfaces for display on the second display unit of the second electronic device, wherein the plurality of user interfaces comprises two or more user interfaces that represent the same watch face type. 
     In some embodiments, the library of one or more user interfaces for display on the second electronic device is stored in the second memory unit of the second electronic device. 
     In some embodiments, the library of one or more user interfaces for display on the second electronic device is stored the memory unit (e.g., memory unit  2420 ) of device  2400 . 
     The operations described above with reference to  FIG. 24  are, optionally, implemented by components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  21 A- 21 D. For example, displaying operation  2104 , detecting operation  2106 , and ceasing/displaying operation  2108  may be implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch-sensitive display  112 , and event dispatcher module  174  delivers the event information to application  136 - 1 . A respective event recognizer  180  of application  136 - 1  compares the event information to respective event definitions  186 , and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer  180  activates an event handler  190  associated with the detection of the event or sub-event. Event handler  190  may utilize or call data updater  176  or object updater  177  to update the application internal state  192 . In some embodiments, event handler  190  accesses a respective GUI updater  178  to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  6 A- 19 . 
     In accordance with some embodiments,  FIG. 25  shows an exemplary functional block diagram of an electronic device  2500  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  2500  are configured to perform the techniques described above. The functional blocks of the device  2500  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 25  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 25 , an electronic device  2500  includes a display unit  2502  configured to display a graphic user interface, a wireless communications unit  2504  configured to send and/or receive wireless communications, a touch-sensitive surface unit  2510  configured to receive contacts, and a processing unit  2506  coupled to the display unit  2502 , wireless communications unit  2504 , and touch-sensitive surface unit  2510 . In some embodiments, the processing unit  2506  includes a display enabling unit  2508 , a receiving unit  2512 , a sending unit  2514 , a detecting unit  2516 , and a scrolling enabling unit  2518 . In some embodiments, display unit  2502  is a touch-sensitive display unit that serves as touch-sensitive surface unit  2510 . In this example, electronic device  2500  is coupled via wireless communication (e.g., using wireless communications unit  2504 ) to a second electronic device (e.g., device  500  described herein) with a second display unit, a second memory unit, a second processing unit, and an accessing unit configured to provide access to a library of one or more user interfaces for display on the second display unit of the second electronic device. 
     The processing unit  2506  is configured to enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a first user interface screen comprising at least a first and a second user interface preview image, the first and the second user interface preview images representing a first and a second user interface for display on the second display unit of the second electronic device, wherein the first and the second user interfaces are configured according to a watch face type and comprise a clock, and wherein the first and the second user interfaces are part of the stored library of user interfaces for display on the second display unit of the second electronic device; receive (e.g., with receiving unit  2512 ) a first user input corresponding to a user request to reorder the stored library of user interfaces; in response to receiving the first user input, enable ceasing of the display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the first user interface screen; in response to receiving the first user input, enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a second user interface screen, wherein the second user interface screen comprises the first and the second user interface preview images, and wherein the relative positions of the first and the second user interface preview images on the second user interface screen reflect an order of the first and the second user interfaces in the stored library; receive (e.g., with receiving unit  2512 ) a second user input corresponding to a user request to re-order the second user interface before the first user interface in the stored library; and in response to receiving the second user input, send (e.g., with sending unit  2514 ) via the wireless communications unit (e.g., wireless communications unit  2504 ) instructions to the second electronic device for re-ordering the second user interface before the first user interface in the stored library. 
     In some embodiments, the processing unit  2506  is further configured to: in response to receiving the second user input, enable re-display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the second user interface screen, wherein the relative positions of the first user interface preview image and the second user interface preview image on the re-displayed second user interface screen reflect the re-ordering of the second user interface before the first user interface in the stored library. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of an affordance for editing the stored library of user interfaces as part of the first user interface screen, and receiving the first user input comprises detecting (e.g., with detecting unit  2516 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the displayed affordance for editing the stored library of user interfaces. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; detect (e.g., with detecting unit  2516 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the affordance for completing editing of the stored library of user interfaces; in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces, enable ceasing of the display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the second user interface screen; and in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces, enable re-display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the first user interface screen, wherein the position of the second user interface preview image on the first user interface screen has shifted relative to the position of the first user interface preview image. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a re-ordering affordance in association with the second user interface preview image as part of the second user interface screen. 
     In some embodiments, the processing unit  2506  is further configured to: detect (e.g., with detecting unit  2516 ) a contact at a first position on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the re-ordering affordance; while continuing to detect the contact, detect (e.g., with detecting unit  2516 ) movement of the contact from the first position to a second position on the touch-sensitive surface unit without a break in the contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ), wherein the second position on the (e.g., touch-sensitive surface unit  2510 ) is on an opposite side of the displayed first user interface preview image relative to the first position; enable translating (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the second user interface preview image on-screen in a direction of the movement of the contact in response to detecting the contact at the second position; and enable translating (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the first user interface preview image on-screen in a direction opposite the movement of the contact in response to detecting the contact at the second position, wherein after the translation of the first and the second user interface preview images, the relative positions of the first and the second user interface preview images reflect the re-ordering of the second user interface before the first user interface in the stored library. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of an affordance for revealing an edit option, the affordance for revealing an edit option being displayed in association with the first user interface preview image as part of the second user interface screen; detect (e.g., with detecting unit  2516 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the affordance for revealing an edit option; and in response to detecting the contact at the affordance for revealing an edit option, enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a delete affordance in association with the first user interface preview image as part of the second user interface screen. 
     In some embodiments, displaying the delete affordance comprises translating the first user interface preview image on-screen. 
     In some embodiments, the processing unit  2506  is further configured to: after displaying the delete affordance as part of the second user interface screen, detect (e.g., with detecting unit  2516 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the delete affordance displayed in association with the first user interface preview image; in response to detecting the contact at the delete affordance, enable removal (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the displayed first user interface preview image from the second user interface screen; and in response to detecting the contact at the delete affordance, send (e.g., with sending unit  2514 ) via the wireless communications unit (e.g., wireless communications unit  2504 ) instructions to the second electronic device for removing the first user interface from the stored library. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of an affordance for completing editing of the stored library of user interfaces as part of the second user interface screen; after detecting the contact at the delete affordance, detect (e.g., with detecting unit  2516 ) a contact on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the affordance for completing editing of the stored library of user interfaces; and in response to detecting the contact at the affordance for completing editing of the stored library of user interfaces: enable ceasing of the display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the second user interface screen; enable re-display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the first user interface screen, wherein the first user interface screen comprises the first and the second user interface preview images; enable animation (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the first user interface preview image to disappear from the display unit; and after animating the first user interface preview image to disappear from the display, enable translation (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of the second user interface preview image on-screen to occupy the position of the first user interface preview image before the animation. 
     In some embodiments, the processing unit  2506  is further configured to: detect (e.g., with detecting unit  2516 ) a swipe on the touch-sensitive surface unit (e.g., touch-sensitive surface unit  2510 ) at the first or the second user interface preview image; and in response to detecting the swipe, enable scrolling (e.g., with scrolling enabling unit  2518 ), on the display unit (e.g., display unit  2502 ), of the first and the second user interface preview images to reveal a third user interface preview image, wherein the third user interface preview image represents a third user interface for display on the second display unit of the second electronic device, and wherein the third user interface is part of the stored library. 
     In some embodiments, the processing unit  2506  is further configured to: prior to revealing the third user interface preview image, enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of a partial view of the third user interface preview image as part of the first user interface screen. 
     In some embodiments, the processing unit  2506  is further configured to: enable display (e.g., with display enabling unit  2508 ), on the display unit (e.g., display unit  2502 ), of text indications of the watch face types of the first and the second user interfaces as part of the second user interface screen, wherein the indications are displayed in association with the first and the second user interface preview images. 
     The operations described above with reference to  FIGS. 22A-22F  are, optionally, implemented by components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  6 A- 19 . For example, displaying operation  2204 , receiving operation  2206 , and ceasing/displaying operation  2208  may be implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch-sensitive display  112 , and event dispatcher module  174  delivers the event information to application  136 - 1 . A respective event recognizer  180  of application  136 - 1  compares the event information to respective event definitions  186 , and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer  180  activates an event handler  190  associated with the detection of the event or sub-event. Event handler  190  may utilize or call data updater  176  or object updater  177  to update the application internal state  192 . In some embodiments, event handler  190  accesses a respective GUI updater  178  to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIG. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B , or  6 A- 19 . 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the scope of the disclosure to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying figures, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the appended claims.

Metadata:
Filing Date: 20200701
Publication Date: 20210727
Grant Date: 20210727
Priority Date: 20160611
Inventors: WILSON, ERIC LANCE
BROUGHTON, LEE S.
WILSON, CHRISTOPHER
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F9/451", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G04G21/04", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/904", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T13/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04808", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/451", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/016", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04804", "inventive": false, "first": false, "tree": "[]"}, {"code": "G04G21/08", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/016", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/904", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G04G21/04", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04808", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04812", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G04G21/08", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04804", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04812", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0414", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G04G21/04", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/451", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T13/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/904", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/016", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04808", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04804", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04812", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0414", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G04G21/08", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04812", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/016", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/904", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04804", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04808", "inventive": false, "first": false, "tree": "[]"}]
Family ID: 60572669