PATENT DOCUMENT

Publication Number: US-11372659-B2
Application Number: US-202017078896-A
Country: US
Kind Code: B2

Title: User interfaces for managing user interface sharing

Abstract:
The present disclosure generally relates to managing user interface sharing. A computer system receives a representation of a first user interface template that specifies an arrangement of user interface elements. The computer system receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications. The computer system initiates a process for creating a user interface for the respective computer system using the first user interface template. The process includes, in accordance with a determination that a first application is not available on the respective computer system, displaying an alert indicating that the first application needs to be installed on the respective computer system. The process includes, in accordance with a determination that the first application is available on the respective computer system, forgoing displaying the alert.

Claims:
What is claimed is: 
     
       1. A computer system, comprising:
 a display generation component; 
 one or more processors; and 
 memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:
 receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; 
 subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and 
 in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the first application is not available on the respective computer system, concurrently displaying, via the display generation component:
 a representation of the first user interface template, wherein displaying the representation of the first user interface template includes concurrently displaying a plurality of user interface elements including one or more user interface elements that indicate a location at which the first user interface element would be displayed relative to other user interface elements of the first user interface template; and 
 an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and 
 
 in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
 
 
 
     
     
       2. The computer system of  claim 1 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, via the display generation component, an affordance that, when activated, initiates a process for installing the first application on the respective computer system. 
 
     
     
       3. The computer system of  claim 2 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the affordance was not activated, continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template is configured to not include the first user interface element corresponding to the first application. 
 
     
     
       4. The computer system of  claim 2 , further comprising during the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the affordance:
 detecting an activation of the affordance; and 
 in response to detecting the activation of the affordance, initiating the process for installing the first application on the respective computer system. 
 
 
     
     
       5. The computer system of  claim 1 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 in accordance with a determination that the second application is available on the respective computer system, forgoing displaying, via the display generation component, the second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template. 
 
     
     
       6. The computer system of  claim 1 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application and a third user interface element corresponding to a third application different from the first application and the second application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 subsequent to displaying the alert:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 subsequent to displaying the second alert:
 in accordance with a determination that the third application is not available on the respective computer system, displaying, via the display generation component, a third alert indicating that the third application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the third user interface element from the first user interface template. 
 
 
 
     
     
       7. The computer system of  claim 1 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system and a second application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, a user interface for the first user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the first user interface element, wherein the representation of the first user interface template includes the first user interface element corresponding to the first application; and 
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the first application available, receiving an input corresponding to a request to display a user interface for a second user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the second user interface element; and 
 in response to receiving the request to display a user interface for the second user interface element:
 in accordance with a determination that the first application was selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying a representation of the first user interface element; and 
 in accordance with a determination that the first application was not selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying the representation of the first user interface template without displaying the first user interface element. 
 
 
     
     
       8. The computer system of  claim 7 , wherein the representation of the user interface specifies elements for a third application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the second application available, receiving an input corresponding to a request to display a user interface for a third user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the third user interface element; and 
 in response to receiving the request to display a user interface for the third user interface element:
 in accordance with a determination that the second application was selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying a representation of the second user interface element; and 
 in accordance with a determination that the second application was not selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying the representation of the first user interface template without displaying the second user interface element. 
 
 
     
     
       9. The computer system of  claim 1 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, the representation of the first user interface template; and 
 while displaying the representation of the first user interface template:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a first visual characteristic; and 
 in accordance with the determination that the first application is available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a second visual characteristic different from the first visual characteristic. 
 
 
     
     
       10. The computer system of  claim 1 , wherein receiving the representation of the first user interface template comprises receiving the representation of the first user interface template via a messaging application. 
     
     
       11. The computer system of  claim 1 , wherein receiving the representation of the first user interface template includes:
 displaying, via the display generation component, a messaging user interface of a messaging application; and 
 displaying, in the messaging user interface, a first message corresponding to the representation of the first user interface template, wherein the first message includes an image showing the representation of the first user interface template. 
 
     
     
       12. The computer system of  claim 1 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 initiating a communication to a second computer system that is coupled to the computer system, wherein the communication includes instructions to continue the process for creating the user interface for the respective computer system using the first user interface template on the second computer system. 
 
 
     
     
       13. The computer system of  claim 1 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template no longer includes the first user interface element corresponding to the first application. 
 
 
     
     
       14. The computer system of  claim 1 , the one or more programs further including instructions for:
 adding the user interface created using the first user interface template to a user interface library for the respective computer system. 
 
     
     
       15. The computer system of  claim 1 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system, the process for creating the user interface for the respective computer system includes:
 in accordance with a determination that the first application is to be made available on the respective computer system:
 initiating a process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system with the first user interface element corresponding to the first application; and 
 
 in accordance with a determination that the first application is not to be made available on the respective computer system:
 forgoing initiating the process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system without the first user interface element. 
 
 
     
     
       16. The computer system of  claim 1 , the one or more programs further including instructions for:
 causing display of the user interface created using the first user interface template, wherein the first user interface element displayed in the user interface includes information obtained from the first application. 
 
     
     
       17. The computer system of  claim 16 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a current location of the respective computer system. 
 
     
     
       18. The computer system of  claim 16 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a designated location different from a current location of the respective computer system. 
 
     
     
       19. The computer system of  claim 16 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to calendar information, and 
 the information is determined based on application information from the first application accessed via the respective computer system, wherein the first application corresponds to a calendar application. 
 
     
     
       20. The computer system of  claim 16 , wherein the first user interface template, when received, is configured to include a visual characteristic that is selected based on context information accessible by the respective computer system. 
     
     
       21. The computer system of  claim 1 , the one or more programs further including instructions for:
 in accordance with the determination that the first application is not available on the respective computer system:
 detecting a request to install the first application on the respective computer system; and 
 in response to detecting the request to install the first application on the respective computer system:
 in accordance with a determination that the first application cannot be installed on the respective computer system, displaying, via the display generation component, an indication that the first application cannot be installed on the respective computer system. 
 
 
 
     
     
       22. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of computer system that is in communication with a display generation component, the one or more programs including instructions for:
 receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; 
 subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and 
 in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the first application is not available on the respective computer system, concurrently displaying, via the display generation component:
 a representation of the first user interface template, wherein displaying the representation of the first user interface template includes concurrently displaying a plurality of user interface elements including one or more user interface elements that indicate a location at which the first user interface element would be displayed relative to other user interface elements of the first user interface template; and 
 an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and 
 
 in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
 
 
     
     
       23. A method, comprising:
 at a computer system that is in communication with a display generation component:
 receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; 
 subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and 
 in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the first application is not available on the respective computer system, concurrently displaying, via the display generation component:
 a representation of the first user interface template, wherein displaying the representation of the first user interface template includes concurrently displaying a plurality of user interface elements including one or more user interface elements that indicate a location at which the first user interface element would be displayed relative to other user interface elements of the first user interface template; and 
 an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and 
 
 in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
 
 
 
     
     
       24. The non-transitory computer-readable storage medium of  claim 22 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, via the display generation component, an affordance that, when activated, initiates a process for installing the first application on the respective computer system. 
 
     
     
       25. The non-transitory computer-readable storage medium of  claim 24 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the affordance was not activated, continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template is configured to not include the first user interface element corresponding to the first application. 
 
     
     
       26. The non-transitory computer-readable storage medium of  claim 24 , further comprising during the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the affordance:
 detecting an activation of the affordance; and 
 in response to detecting the activation of the affordance, initiating the process for installing the first application on the respective computer system. 
 
 
     
     
       27. The non-transitory computer-readable storage medium of  claim 22 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 in accordance with a determination that the second application is available on the respective computer system, forgoing displaying, via the display generation component, the second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template. 
 
     
     
       28. The non-transitory computer-readable storage medium of  claim 22 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application and a third user interface element corresponding to a third application different from the first application and the second application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 subsequent to displaying the alert:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 subsequent to displaying the second alert:
 in accordance with a determination that the third application is not available on the respective computer system, displaying, via the display generation component, a third alert indicating that the third application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the third user interface element from the first user interface template. 
 
 
 
     
     
       29. The non-transitory computer-readable storage medium of  claim 22 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system and a second application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, a user interface for the first user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the first user interface element, wherein the representation of the first user interface template includes the first user interface element corresponding to the first application; and 
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the first application available, receiving an input corresponding to a request to display a user interface for a second user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the second user interface element; and 
 in response to receiving the request to display a user interface for the second user interface element:
 in accordance with a determination that the first application was selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying a representation of the first user interface element; and 
 in accordance with a determination that the first application was not selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying the representation of the first user interface template without displaying the first user interface element. 
 
 
     
     
       30. The non-transitory computer-readable storage medium of  claim 29 , wherein the representation of the user interface specifies elements for a third application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the second application available, receiving an input corresponding to a request to display a user interface for a third user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the third user interface element; and 
 in response to receiving the request to display a user interface for the third user interface element:
 in accordance with a determination that the second application was selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying a representation of the second user interface element; and 
 in accordance with a determination that the second application was not selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying the representation of the first user interface template without displaying the second user interface element. 
 
 
     
     
       31. The non-transitory computer-readable storage medium of  claim 22 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, the representation of the first user interface template; and 
 while displaying the representation of the first user interface template:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a first visual characteristic; and 
 in accordance with the determination that the first application is available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a second visual characteristic different from the first visual characteristic. 
 
 
     
     
       32. The non-transitory computer-readable storage medium of  claim 22 , wherein receiving the representation of the first user interface template comprises receiving the representation of the first user interface template via a messaging application. 
     
     
       33. The non-transitory computer-readable storage medium of  claim 22 , wherein receiving the representation of the first user interface template includes:
 displaying, via the display generation component, a messaging user interface of a messaging application; and 
 displaying, in the messaging user interface, a first message corresponding to the representation of the first user interface template, wherein the first message includes an image showing the representation of the first user interface template. 
 
     
     
       34. The non-transitory computer-readable storage medium of  claim 22 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 initiating a communication to a second computer system that is coupled to the computer system, wherein the communication includes instructions to continue the process for creating the user interface for the respective computer system using the first user interface template on the second computer system. 
 
 
     
     
       35. The non-transitory computer-readable storage medium of  claim 22 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template no longer includes the first user interface element corresponding to the first application. 
 
 
     
     
       36. The non-transitory computer-readable storage medium of  claim 22 , the one or more programs further including instructions for:
 adding the user interface created using the first user interface template to a user interface library for the respective computer system. 
 
     
     
       37. The non-transitory computer-readable storage medium of  claim 22 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system, the process for creating the user interface for the respective computer system includes:
 in accordance with a determination that the first application is to be made available on the respective computer system:
 initiating a process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system with the first user interface element corresponding to the first application; and 
 
 in accordance with a determination that the first application is not to be made available on the respective computer system:
 forgoing initiating the process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system without the first user interface element. 
 
 
     
     
       38. The non-transitory computer-readable storage medium of  claim 22 , the one or more programs further including instructions for:
 causing display of the user interface created using the first user interface template, wherein the first user interface element displayed in the user interface includes information obtained from the first application. 
 
     
     
       39. The non-transitory computer-readable storage medium of  claim 38 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a current location of the respective computer system. 
 
     
     
       40. The non-transitory computer-readable storage medium of  claim 38 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a designated location different from a current location of the respective computer system. 
 
     
     
       41. The non-transitory computer-readable storage medium of  claim 38 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to calendar information, and 
 the information is determined based on application information from the first application accessed via the respective computer system, wherein the first application corresponds to a calendar application. 
 
     
     
       42. The non-transitory computer-readable storage medium of  claim 38 , wherein the first user interface template, when received, is configured to include a visual characteristic that is selected based on context information accessible by the respective computer system. 
     
     
       43. The non-transitory computer-readable storage medium of  claim 22 , the one or more programs further including instructions for:
 in accordance with the determination that the first application is not available on the respective computer system:
 detecting a request to install the first application on the respective computer system; and 
 in response to detecting the request to install the first application on the respective computer system:
 in accordance with a determination that the first application cannot be installed on the respective computer system, displaying, via the display generation component, an indication that the first application cannot be installed on the respective computer system. 
 
 
 
     
     
       44. The method of  claim 23 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, via the display generation component, an affordance that, when activated, initiates a process for installing the first application on the respective computer system. 
 
     
     
       45. The method of  claim 44 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the affordance was not activated, continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template is configured to not include the first user interface element corresponding to the first application. 
 
     
     
       46. The method of  claim 44 , further comprising during the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the affordance:
 detecting an activation of the affordance; and 
 in response to detecting the activation of the affordance, initiating the process for installing the first application on the respective computer system. 
 
 
     
     
       47. The method of  claim 23 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 in accordance with a determination that the second application is available on the respective computer system, forgoing displaying, via the display generation component, the second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template. 
 
     
     
       48. The method of  claim 23 , wherein the one or more other user interface elements include a second user interface element corresponding to a second application different from the first application and a third user interface element corresponding to a third application different from the first application and the second application, and wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 subsequent to displaying the alert:
 in accordance with a determination that the second application is not available on the respective computer system, displaying, via the display generation component, a second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template; and 
 subsequent to displaying the second alert:
 in accordance with a determination that the third application is not available on the respective computer system, displaying, via the display generation component, a third alert indicating that the third application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the third user interface element from the first user interface template. 
 
 
 
     
     
       49. The method of  claim 23 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system and a second application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, a user interface for the first user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the first user interface element, wherein the representation of the first user interface template includes the first user interface element corresponding to the first application; and 
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the first application available, receiving an input corresponding to a request to display a user interface for a second user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the second user interface element; and 
 in response to receiving the request to display a user interface for the second user interface element:
 in accordance with a determination that the first application was selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying a representation of the first user interface element; and 
 in accordance with a determination that the first application was not selected for installation on the respective computer system, displaying the user interface for the second user interface element includes displaying the representation of the first user interface template without displaying the first user interface element. 
 
 
     
     
       50. The method of  claim 49 , wherein the representation of the user interface specifies elements for a third application that is not available on the respective computer system and the process for creating the user interface for the respective computer system using the first user interface template includes:
 while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the second application available, receiving an input corresponding to a request to display a user interface for a third user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the third user interface element; and 
 in response to receiving the request to display a user interface for the third user interface element:
 in accordance with a determination that the second application was selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying a representation of the second user interface element; and 
 in accordance with a determination that the second application was not selected for installation on the respective computer system, displaying the user interface for the third user interface element includes displaying the representation of the first user interface template without displaying the second user interface element. 
 
 
     
     
       51. The method of  claim 23 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 displaying, via the display generation component, the representation of the first user interface template; and 
 while displaying the representation of the first user interface template:
 in accordance with the determination that the first application is not available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a first visual characteristic; and 
 in accordance with the determination that the first application is available on the respective computer system, displaying, in the representation of the first user interface template, the first user interface element with a second visual characteristic different from the first visual characteristic. 
 
 
     
     
       52. The method of  claim 23 , wherein receiving the representation of the first user interface template comprises receiving the representation of the first user interface template via a messaging application. 
     
     
       53. The method of  claim 23 , wherein receiving the representation of the first user interface template includes:
 displaying, via the display generation component, a messaging user interface of a messaging application; and 
 displaying, in the messaging user interface, a first message corresponding to the representation of the first user interface template, wherein the first message includes an image showing the representation of the first user interface template. 
 
     
     
       54. The method of  claim 23 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 initiating a communication to a second computer system that is coupled to the computer system, wherein the communication includes instructions to continue the process for creating the user interface for the respective computer system using the first user interface template on the second computer system. 
 
 
     
     
       55. The method of  claim 23 , wherein the process for creating the user interface for the respective computer system using the first user interface template includes:
 in accordance with the determination that the first application is not available on the respective computer system:
 continuing the process for creating the user interface for the respective computer system using the first user interface template without installing the first application on the respective computer system, wherein the first user interface template no longer includes the first user interface element corresponding to the first application. 
 
 
     
     
       56. The method of  claim 23 , further comprising:
 adding the user interface created using the first user interface template to a user interface library for the respective computer system. 
 
     
     
       57. The method of  claim 23 , wherein the representation of the user interface specifies elements for the first application that is not available on the respective computer system, the process for creating the user interface for the respective computer system includes:
 in accordance with a determination that the first application is to be made available on the respective computer system:
 initiating a process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system with the first user interface element corresponding to the first application; and 
 
 in accordance with a determination that the first application is not to be made available on the respective computer system:
 forgoing initiating the process for making the first application available on the respective computer system, wherein, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system without the first user interface element. 
 
 
     
     
       58. The method of  claim 23 , further comprising:
 causing display of the user interface created using the first user interface template, wherein the first user interface element displayed in the user interface includes information obtained from the first application. 
 
     
     
       59. The method of  claim 58 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a current location of the respective computer system. 
 
     
     
       60. The method of  claim 58 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to location information, and 
 the information is determined based on a location setting from the first user interface template, wherein the location setting is configured to be a designated location different from a current location of the respective computer system. 
 
     
     
       61. The method of  claim 58 , wherein:
 the information included in the first user interface element displayed in the user interface corresponds to calendar information, and 
 the information is determined based on application information from the first application accessed via the respective computer system, wherein the first application corresponds to a calendar application. 
 
     
     
       62. The method of  claim 58 , wherein the first user interface template, when received, is configured to include a visual characteristic that is selected based on context information accessible by the respective computer system. 
     
     
       63. The method of  claim 23 , further comprising:
 in accordance with the determination that the first application is not available on the respective computer system:
 detecting a request to install the first application on the respective computer system; and 
 in response to detecting the request to install the first application on the respective computer system:
 in accordance with a determination that the first application cannot be installed on the respective computer system, displaying, via the display generation component, an indication that the first application cannot be installed on the respective computer system.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims the benefit of U.S. Provisional Patent Application Ser. No. 63/023,149, entitled “USER INTERFACES FOR MANAGING USER INTERFACE SHARING”, filed May 11, 2020, the content of which is hereby incorporated by reference in its entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing user interface sharing. 
     BACKGROUND 
     An electronic device can display user interfaces that include one or more features. The one or more features of a respective user interface that can be customized before being enabled for use on the electronic device. 
     BRIEF SUMMARY 
     Some techniques for managing user interface sharing using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated systems or devices. 
     Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for managing user interface sharing. Such methods and interfaces optionally complement or replace other methods for managing user interface sharing. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component is described. The method comprises: receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes: in accordance with a determination that the first application is not available on the respective computer system, displaying, via the display generation component, an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
     In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of computer system that is in communication with a display generation component is described. The one or more programs include instructions for: receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes: in accordance with a determination that the first application is not available on the respective computer system, displaying, via the display generation component, an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
     In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of computer system that is in communication with a display generation component is described. The one or more programs include instructions for: receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes: in accordance with a determination that the first application is not available on the respective computer system, displaying, via the display generation component, an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
     In accordance with some embodiments, a computer system comprising a display generation component, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors is described. The one or more programs including instructions for: receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes: in accordance with a determination that the first application is not available on the respective computer system, displaying, via the display generation component, an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
     In accordance with some embodiments, a computer system is described. The computer system comprises: a display generation component; means for receiving a representation of a first user interface template that specifies an arrangement of user interface elements including a first user interface element corresponding to a first application and one or more other user interface elements corresponding to software that is different from the first application; means for, subsequent to receiving the representation of the first user interface template, receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications; and means for, in response to receiving the request to use the first user interface template for the respective computer system, initiating a process for creating a user interface for the respective computer system using the first user interface template, wherein the process for creating the user interface for the respective computer system using the first user interface template includes: in accordance with a determination that the first application is not available on the respective computer system, displaying, via the display generation component, an alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on the respective computer system, forgoing displaying, via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. 
     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 managing user interface sharing, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing user interface sharing. 
    
    
     
       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-6AB  illustrate exemplary user interfaces for managing user interface sharing using a computer system, in accordance with some embodiments. 
         FIGS. 7A-7F  is a flow diagram illustrating methods of managing user interface sharing, 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 managing user interface sharing. For example, there is a need for user interfaces that enable quick and easy setup of a user interface that has been shared via a user interface template. For another example, there is a need for user interfaces that enable convenient downloading of an application(s) for which installation may be needed to complete the setup of a user interface that has been shared via a user interface template. For another example, there is a need for user interfaces that enable the completion of the setup of a user interface that has been shared via a user interface template without installing one or more applications that enable respective features of the user interface template. Such techniques can reduce the cognitive burden on a user who accesses user interface sharing, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. 
     Below,  FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B  provide a description of exemplary devices for performing the techniques for managing event notifications.  FIGS. 6A-6AB  illustrate exemplary user interfaces for managing user interface sharing using a computer system, in accordance with some embodiments.  FIGS. 7A-7F  is a flow diagram illustrating methods of managing user interface sharing, in accordance with some embodiments. The user interfaces in  FIGS. 6A-6AB  are used to illustrate the processes described below, including the processes in  FIGS. 7A-7F . 
     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 some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller  156 ) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content. 
     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 , depth camera controller  169 , 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 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 ). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with one or more input devices. In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a trackpad, as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors  164  and/or one or more depth camera sensors  175 ), such as for tracking a user&#39;s gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. 
     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 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 depth camera sensors  175 .  FIG. 1A  shows a depth camera sensor coupled to depth camera controller  169  in I/O subsystem  106 . Depth camera sensor  175  receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module  143  (also called a camera module), depth camera sensor  175  is optionally used to determine a depth map of different portions of an image captured by the imaging module  143 . In some embodiments, a depth camera sensor is located on the front of device  100  so that the user&#39;s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor  175  is located on the back of device, or on the back and the front of the device  100 . In some embodiments, the position of depth camera sensor  175  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor  175  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 and a GPS (or GLONASS or other global navigation system) receiver 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 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 process  700  ( FIGS. 7A-7F ). 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. 1A, 3, and 5A-5B ). 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 
     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. 
     Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIGS. 6A-6AB  illustrate exemplary user interfaces for managing user interface sharing using a computer system (e.g.,  600 A,  600 B,  600 C,  600 D; an electronic device, such as a smartphone or smartwatch), in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS. 7A-7F . 
       FIG. 6A  illustrates a computer system  600 A (e.g., a smartphone) and a computer system  600 B (e.g., a smartwatch). In some embodiments, computer system  600 A is paired with computer system  600 B. In some embodiments, computer system  600 A can be used to control and/or manage configurations and settings on computer system  600 B (e.g., via a companion application for computer system  600 B that is accessible on computer system  600 A). 
       FIG. 6A  illustrates a method for downloading the first user interface template on a computer system (e.g., computer system  600 A or  600 B) from a link (e.g., a hyperlink). 
     In  FIG. 6A , computer system  600 A displays, via a display generation component  602 A, a user interface  604 A of a browser application (e.g., a web browser), where user interface  604 A is showing a webpage  606 A for downloading a first user interface template onto a respective computer system (e.g., a respective electronic device). In some embodiments, the first user interface template corresponds to a user interface that includes one or more user interface elements that correspond to one or more respective applications. In some embodiments, the first user interface template corresponds to a user interface that can be used as a watch user interface (e.g., a watch face) on an electronic device (e.g., a smartwatch), where the watch user interface includes one or more watch complications (e.g., also referred to as “complications”) that correspond to one or more respective applications, as will be described in greater detail below with reference to  FIG. 6F . 
     In some embodiments, 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). In some embodiments, complications provide data obtained from an application. In some embodiments, a complication includes an affordance that when selected launches a corresponding application. In some embodiments, a complication is displayed at a fixed, predefined location on the display. In some embodiments, complications occupy respective locations at particular regions of a watch face (e.g., lower-right, lower-left, upper-right, and/or upper-left). 
     In some embodiments, the first user interface template corresponds to a user interface that can be used as a background user interface on an electronic device (e.g., a mobile device; a smartwatch; a smartphone; a tablet). 
     In  FIG. 6A , webpage  606 A includes a representation  608 A (e.g., a preview) of the first user interface template and an affordance  610 A (e.g., a hyperlink; a selectable user interface object; an activatable user interface object) for initiating the downloading of the first user interface template onto the respective computer system (e.g., onto computer system  600 B). 
     Similarly, in  FIG. 6A , computer system  600 B displays, via a display generation component  602 B, a user interface  604 B of a browser application (e.g., a web browser), where user interface  604 B is displaying webpage  606 B that corresponds to webpage  606 A displayed on computer system  600 A, and where webpage  606 B includes a representation  608 B (e.g., a preview) of the first user interface template and an affordance  610 B (e.g., a hyperlink; a selectable user interface object; an activatable user interface object) for initiating the downloading of the first user interface template onto computer system  600 B. 
     In  FIG. 6A , while displaying webpage  606 A, computer system  600 A receives (e.g., detects) an input  601 A directed to affordance  601 A. In some embodiments, input  601 S is a touch input on display generation component  602 A. In response to detecting input  601 A on affordance  610 A, computer system  600 A displays, via display generation component  602 A, a user interface  632 A for customizing the user interface corresponding to the downloaded first user interface template, as shown in  FIG. 6F  (e.g., such that the first user interface template can be used to create a user interface that can be used (e.g., as a watch user interface). 
     Similarly, while displaying webpage  606 B, computer system  600 B receives (e.g., detects) an input  601 B on affordance  610 B. In some embodiments, input  601 B is a touch input on display generation component  602 B. In response to detecting input  601 B on affordance  610 B, computer system  600 B displays, via display generation component  602 B, a user interface  632 B for customizing the user interface corresponding to the first user interface template downloaded on computer system  600 B, as shown in  FIG. 6F . 
       FIG. 6B  illustrates a method for downloading the first user interface template on a computer system (e.g., computer system  600 A or  600 B) from an application store. 
     In  FIG. 6B , computer system  600 A displays, via display generation component  602 A, a user interface  6100 A of an application store. In some embodiments, the application store includes a page (e.g., a “TODAY” page; a tab) that shows one or more user interface templates that are available for download. In some embodiments, the first user interface template can be downloaded from the application store. In  FIG. 6B , user interface  6100 A of the application store includes a user interface element  6102 A (e.g., a platter) (e.g., including a representation of the first user interface template) indicating that the first user interface template can be downloaded, and an affordance  6104 A corresponding to user interface element  6102 A for downloading the first user interface template. 
     While displaying affordance  6104 A, computer system  600 A receives (e.g., detects) an input  6101 A on affordance  6104 A. In response to detecting input  6101 A on affordance  6104 A, computer system  600 A initiates a process for downloading the first user interface template. In some embodiments, in response to (e.g., or while) downloading the first user interface template, computer system  600 A displays, via display generation component  602 A, user interface  632 A for customizing the user interface corresponding to the downloaded first user interface template, as shown in  FIG. 6F . 
     Similarly, in  FIG. 6B , computer system  600 B displays, via display generation component  602 B, a user interface  6100 B of the application store, where user interface  6100 A of the application store includes a user interface element  6102 B (e.g., a platter) indicating that the first user interface template can be downloaded, and an affordance  6104 B for downloading the first user interface template on computer system  600 B. 
     While displaying affordance  6104 B, computer system  600 B receives (e.g., detects) an input  6101 B on affordance  6104 B. In response to detecting input  6101 B on affordance  6104 B, computer system  600 B initiates a process for downloading the first user interface template. In some embodiments, in response to (e.g., or while) downloading the first user interface template, computer system  600 B displays, via display generation component  602 B, user interface  632 B for customizing the user interface corresponding to the first user interface template downloaded on computer system  600 B, as shown in  FIG. 6F . 
     In some embodiments, prior to initiating the process for downloading the first user interface template, the computer system (e.g., computer system  600 A or  600 B) requests authorization to download the first user interface template. In some embodiments, the authorization includes biometric authentication (e.g., facial recognition authentication; fingerprint authentication; iris/retina scan authentication). In some embodiments, the authorization includes password or passcode authentication. In some embodiments, the authorization includes confirmation via a user input on a mechanical input device (e.g., a hardware button) of the computer system. 
     As discussed in greater detail below with reference to  FIGS. 6F-6G , first user interface template includes one or more complications that require corresponding applications to be installed on a respective computer system for a user interface (e.g., a watch user interface) created from first user interface template for use on the respective computer system. In some embodiments, if one or more of the required applications is not installed on the respective computer when the first user interface template is downloaded from the application store as in  FIG. 6B , the computer system (e.g., computer system  600 A or  600 B) downloads the missing application(s) with the first user interface template (e.g., concurrently downloads the missing application(s) with and/or immediately after downloading the first user interface template). In some embodiments, the authorization requested to download the first user interface template also authorizes the downloading of the missing application(s) (e.g., thus, the computer system requests a single authorization (e.g., biometric authentication; password or passcode authentication) to download the first use interface template and the missing application(s)). 
       FIG. 6C  illustrates a method for receiving the first user interface template from a contactless wireless terminal (e.g., a NFC terminal) to be stored on a computer system (e.g., computer system  600 A or  600 B). 
     In  FIG. 6C , computer system  600 A receives (e.g., via NFC), from a contactless wireless terminal  612  (e.g., also referred to as a NFC terminal  612 ), the first user interface template. In some embodiments, in response to receiving the first user interface template from NFC terminal  612 , computer system  600 A displays, via display generation component  602 A, a preview  614 A of the first user interface template and an affordance  616 A for storing the first user interface template on computer system  600 A and/or causing the first user interface template to be stored on the respective computer system (e.g., computer system  600 B). 
     Similarly, in  FIG. 6C , computer system  600 B receives (e.g., via NFC), from NFC terminal  612 , the first user interface template. In some embodiments, in response to receiving the first user interface template from NFC terminal  612 , computer system  600 B displays, via display generation component  602 B, a preview  614 B (of the first user interface template and an affordance  616 B for storing the first user interface template on computer system  600 B. 
     In  FIG. 6C , while displaying affordance  616 A, computer system  600 A receives (e.g., detects) an input  603 A on affordance  616 A. In some embodiments, input  603 A is a touch input on display generation component  602 A. In response to receiving input  603 A on affordance  616 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A for creating a user interface (e.g., a watch user interface) from the first user interface template for use on the respective computer system (e.g., on computer system  600 B), as shown in  FIG. 6F . 
     Similarly, in  FIG. 6C , while displaying affordance  616 B, computer system  600 B receives (e.g., detects) an input  603 B on affordance  616 B. In some embodiments, input  603 B is a touch input on display generation component  602 B. In response to receiving input  603 B on affordance  616 B, computer system  600 B displays, via display generation component  602 B, user interface  632 B for creating a user interface (e.g., a watch user interface) from the first user interface template for use on computer system  600 B, as shown in  FIG. 6F . 
       FIG. 6D  illustrates a method for receiving (e.g., detecting) the first user interface template via a QR code to be stored on a computer system (e.g., on computer system  600 A or  600 B). 
     In  FIG. 6D , computer system  600 A detects (e.g., via one or more cameras of computer system  600 A) a QR code  618 . In some embodiments, in response to detecting QR code  618 , computer system  600 A displays, via display generation component  602 A, a preview  620 A of the first user interface template that has been detected from QR code  618  and an affordance  622 A for storing the first user interface template on computer system  600 A and/or causing the detected first user interface template to be stored on the respective computer system (e.g., on computer system  600 B). 
     Similarly, in  FIG. 6D , computer system  600 B detects (e.g., via one or more cameras of computer system  600 B) QR code  618 . In some embodiments, in response to detecting QR code  618 , computer system  600 B displays, via display generation component  602 B, a preview  620 B of the first user interface template that has been detected from QR code  618  and an affordance  622 B for storing the first user interface template on computer system  600 B. 
     In  FIG. 6D , while displaying affordance  622 A, computer system  600 A receives (e.g., detects) an input  605 A on affordance  622 A. In some embodiments, input  605 A is a touch input on display generation component  602 A. In response to receiving input  605 A on affordance  622 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A for creating a user interface (e.g., a watch user interface) from the first user interface template for use on the respective computer system (e.g., on computer system  600 B), as shown in  FIG. 6F . 
     Similarly, in  FIG. 6D , while displaying affordance  622 B, computer system  600 B receives (e.g., detects) an input  605 B on affordance  622 B. In response to detecting input  605 B on affordance  622 B, computer system  600 B displays, via display generation component  602 B, user interface  632 B for creating a user interface (e.g., a watch user interface) from the first user interface template to be used on computer system  600 B, as shown in  FIG. 6F . 
       FIG. 6E  illustrates a method for receiving the first user interface template via a messaging application. 
     In  FIG. 6E , computer system  600 A displays, via display generation component  602 A, a user interface  624 A of a messaging application (e.g., a text messaging application; a chat application; an electronic mail application), where user interface  624 A of the messaging application is displaying a message conversation  626 A with a message participant (e.g., “Jane Appleseed”), and where message conversation  626 A includes a received electronic communication that includes (e.g., as an attachment) the first user interface template (e.g., shown as preview  628 A in message conversation  626 A) and a message  630 A associated with the first user interface template (e.g., a message from the message participant that was received as part of the electronic communication that includes the first user interface template). 
     Similarly, in  FIG. 6E , computer system  600 A displays, via display generation component  602 A, a user interface  624 B of the messaging application, where user interface  624 A of the messaging application is displaying a message conversation  626 B with the message participant (e.g., “Jane Appleseed”), and where message conversation  626 A includes a received electronic communication that includes (e.g., as an attachment) the first user interface template (e.g., shown as preview  628 B in message conversation  626 B) and a message  630 B associated with the first user interface template (e.g., a message from the message participant that was received as part of the electronic communication that includes the first user interface template). 
     In  FIG. 6E , while displaying message conversation  626 A, computer system  600 A receives (e.g., detects) an input  607 A directed to downloading and storing the first user interface template. In some embodiments, input  607 A is a touch input (e.g., or a press-and-hold input) on preview  628 A, as in  FIG. 6E . In some embodiments, input  607 A is a touch input on a download affordance associated with the electronic communication. In response to (e.g., or subsequent to) receiving input  607 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A for creating a user interface (e.g., a watch user interface) from the first user interface template to be used on the respective computer system (e.g., on computer system  600 B), as shown in  FIG. 6F . 
     Similarly, in  FIG. 6E , while displaying message conversation  626 B, computer system  600 B receives (e.g., detects) an input  607 B directed to downloading and storing the first user interface template on computer system  600 B. In some embodiments, input  607 B is a touch input (e.g., or a press-and-hold input) on preview  628 B, as in  FIG. 6E . In some embodiments, input  607 B is a touch input on a download affordance associated with the electronic communication. In response to (e.g., or subsequent to) receiving input  607 B, computer system  600 B displays, via display generation component  602 B, user interface  632 B for creating a user interface (e.g., a watch user interface) from the first user interface template to be used on computer system  600 B, as shown in  FIG. 6F . 
       FIG. 6F  illustrates computer system  600 A displaying user interface  632 A for creating a user interface (e.g., a watch user interface) from the first user interface template to be used on the respective computer system (e.g., on computer system  600 B) and computer system  600 B displaying the corresponding user interface  632 B for creating a user interface (e.g., a watch user interface) from the first user interface template to be used on computer system  600 B. In some embodiments, as is the case in  FIGS. 6A-6AB , the first user interface template is a watch user interface (e.g., a watch face) that can be used on a type of computer system (e.g., a smartwatch), where the watch user interface includes one or more complications that correspond to respective applications, and where a respective application needs to be installed on the respective computer system in order for a corresponding complication to be used in the computer system through the watch user interface. 
     In  FIG. 6F , in response to (e.g., or subsequent to) downloading, receiving, and/or detecting the first user interface template (e.g., as described above with reference to  FIGS. 6A-6E ), computer system  600 A displays, via display generation component  602 A, user interface  632 A, where user interface  632 A includes a preview  634 A of the first user interface template. 
     In  FIG. 6F , the respective computer system for which the user interface corresponding to the first user interface template will be used (e.g., computer system  600 B) includes (e.g., has already installed) respective applications corresponding to all of the complications that are included with the first user interface template (e.g., all of the respective applications are already installed on and thus available on computer system  600 B). Thus, no additional applications need to be downloaded and installed on the respective computer system (e.g., computer system  600 B) for all complications of the first user interface template to be used. 
     As shown in  FIG. 6F , user interface  632 A includes a plurality of complication previews  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A, and  650 A. Because all of the respective applications are already installed on, and thus are available on, the respective computer system (e.g., computer system  600 B), all of complication previews  636 A- 650 A correspond to respective complications for available applications, and computer system  600 A does not visually indicate (e.g., does not highlight) any of complication previews  636 A- 650 A (e.g., as computer system  600 A (e.g., only) visually indicates (e.g., highlights) a complication preview corresponding to a complication for which the application is not available). 
     In  FIG. 6F , in response to (e.g., or subsequent to) downloading, receiving, and/or detecting the first user interface template (e.g., as described above with reference to  FIGS. 6A-6E ), computer system  600 B displays, via display generation component  602 B, user interface  632 B, where user interface  632 B includes a preview  634 B of the first user interface template, and where computer system  600 B already includes (e.g., has already installed) all respective applications corresponding to all complications that are included with the first user interface template. 
     As shown in  FIG. 6F , user interface  632 B includes a plurality of complication previews  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and  650 B. Because all of the respective applications are already installed on, and thus are available on, computer system  600 B, all of complication previews  636 B- 650 B correspond to respective complications for available applications, and computer system  600 B does not visually indicate (e.g., does not highlight) any of complication previews  636 B- 650 B (e.g., as computer system  600 B (e.g., only) visually indicates (e.g., highlights) a complication preview corresponding to a complication for which the application is not available). 
     In  FIG. 6F , because all of the respective applications are already installed on, and thus available on, the respective computer system (e.g., on computer system  600 B), computer system  600 A displays, in user interface  632 A, an affordance  652 A for adding the user interface corresponding to the first user interface template to a user interface library for the respective computer system (e.g., a collection of user interfaces (e.g., watch user interfaces; watch faces) that can be used on computer system  600 B). While displaying affordance  652 A, computer system  600 A receives (e.g., detects) an input  609 A on affordance  652 A. In some embodiments, input  609 A is a touch input on display generation component  602 A. In response to receiving input  609 A, computer system  600 A displays, via display generation component  602 A, a companion application (e.g., an application that can be used to edit or configure features and settings of a paired computer system) for the respective computer system (e.g., a companion application for computer system  600 B), as shown in  FIG. 6G . 
     Similarly, in  FIG. 6F , because all of the respective applications are already installed on, and thus available on, computer system  600 B, computer system  600 B displays, in user interface  632 B, an affordance  652 B for adding the user interface corresponding to the first user interface template to the user interface library for computer system  600 B. While displaying affordance  652 B, computer system  600 B receives (e.g., detects) an input  609 B on affordance  652 B. In some embodiments, input  609 B is a touch input on display generation component  602 B. In response to receiving input  609 B, computer system  600 B displays, via display generation component  602 B, a watch user interface corresponding to the first user interface template configured in  FIG. 6F , as shown in  FIG. 6G . 
     In  FIG. 6G , user interface  654  of the companion application includes a plurality of watch user interface previews that can be used as a watch user interface on the respective computer system (e.g., on computer system  600 B), including a watch user interface preview  656 A (including complication previews  636 A- 650 A) corresponding to the watch user interface configured in  FIG. 6F  and shown as watch user interface  656 B on computer system  600 B in  FIG. 6G . As shown by computer system  600 B, watch user interface  656 B includes complications  658 ,  660 ,  662 ,  664 ,  666 ,  668 ,  670 , and  672 , corresponding to complication previews  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and  650 B from  FIG. 6F , respectively, where complications  658 ,  660 ,  662 ,  664 ,  666 ,  668 ,  670 , and  672  can be used to perform operations on computer system  600 B corresponding to the respective applications. 
     In some embodiments, for certain types of complications of a watch user interface that is created from a received user interface template (e.g., watch user interface  656 B created from the first user interface template), how one or more settings of a respective compilation of the watch user interface are set depends (e.g., at least partially) on the type of the respective complications and/or a logic-based (e.g., a smart) algorithm. 
     For example, watch user interface  656 B includes calendar complication  660  corresponding to a calendar application of computer system  600 B. In some embodiments (e.g., upon completing the configuration/setup of watch user interface  656 B in  FIG. 6F ), settings of calendar complication  660  are automatically (e.g., without user input) set to settings of the calendar application that is installed on computer system  600 B and calendar complication  660  retrieves information (e.g., schedule information) from a user account that is associated with the calendar application that is installed on computer system  600 B, as opposed to maintaining the calendar complication settings and/or information that had originally been associated with the first user interface template (e.g., based on a respective computer system of the sender/creator of the first user interface template) when the first user interface template was initially downloaded, received, and/or detected on computer system  600 . 
     For another example, watch user interface  656 B includes weather complication  668  corresponding to a weather application of computer system  600 B. In some embodiments (e.g., upon completing the configuration/setup of watch user interface  656 B in  FIG. 6F ), settings of weather complication  668  are automatically (e.g., without user input) set to the settings of the weather application that is installed on computer system  600 B, as opposed to maintaining the weather complication settings and/or information that had originally been associated with the first user interface template (e.g., based on a respective computer system of the sender/creator of the first user interface template) when the first user interface template was initially downloaded, received, and/or detected on computer system  600 . 
     For another example, watch user interface  656 B includes world clock complication  672  corresponding to a world clock application of computer system  600 B. In some embodiments (e.g., upon completing the configuration/setup of watch user interface  656 B in  FIG. 6F ), settings of world clock complication  672  are automatically (e.g., without user input) transferred over from the world clock complication settings that had originally been associated with the first user interface template (e.g., based on a respective computer system of the sender/creator of the first user interface template) when the first user interface template was initially downloaded, received, and/or detected on computer system  600 B. For example, if the world clock complication had been, prior to being configured/setup for use on computer system  600 B, set to a current location of its respective computer system, the location of the world clock complication  672  is automatically (e.g., without user input) set to the current location of computer system  600 B upon completion of the configuration/setup of watch user interface  656 B for use on computer system  600 B. For another example, if the world clock compilation had been, prior to being configured/setup for use on computer system  600 B, set to a predetermined location (e.g., a set location; a selected location; a particular location), the location setting of the world clock complication  672  is automatically (e.g., without user input) maintained to be the same predetermined location upon completion of the configuration/setup of watch user interface  656 B for use on computer system  600 B (e.g., instead of being modified to be the current location of computer system  600 B). 
       FIGS. 6H-6K  illustrates a method for configuring the first user interface template for use on the respective computer system (e.g., computer system  600 B), where the first user interface template corresponds to a photo watch user interface (e.g., a photo watch face). 
     In some embodiments, a respective photo watch user interface includes an indication of a current time and is associated with a plurality of selected photos that are displayed (e.g., one-by-one) as a background of the respective photo watch user interface. In some embodiments, the plurality of selected photos (e.g., up to a predetermined maximum number of photos, such as 6 photos, 12 photos, or 24 photos) are selected to be included in the respective photo watch user interface. In some embodiments, the currently-displayed photo of the respective photo watch user interface changes automatically (e.g., based on time; randomly). In some embodiments, the currently-displayed photo of the respective photo watch user interface changes based on predetermined criteria (e.g., in response to detecting a predefined movement of the respective computer system, such as, e.g., a wrist raise). In some embodiments, a user interface template corresponding to the respective photo watch user interface, when downloaded, received, and/or detected by computer system  600 A or computer system  600 B, includes the plurality of selected photos that are included with (e.g., shared with, and thus downloaded, received, and/or detected by computer system  600 A or computer system  600 B together with) the respective user interface template. In some embodiments, the plurality of photos corresponds to photos that were designated for the respective photo watch user interface on a source computer system/source device of the respective user interface template corresponding to the respective photo watch user interface (e.g., selected by a user that created the respective user interface template on the source computer system/source device), and are shared together with the respective user interface template from the source computer system/source device. In some embodiments, a photo watch user interface includes complications, and the processes described in  FIGS. 6A-6G and 6L-6AB  with respect to watch user interfaces also apply to photo watch user interfaces. 
     In  FIG. 6H , computer system  600 A displays, via display generation component  602 A, user interface  624 A of the messaging application, where user interface  624 A of the messaging application is displaying message conversation  626 A with a message participant (e.g., “Jane Appleseed”). Message conversation  626 A includes a received electronic communication that includes (e.g., as an attachment) the first user interface template (e.g., shown as preview  6106 A in message conversation  626 A) interface, the plurality of selected photos associated with the first user interface template, including photo  6108 A, and a message  630 A associated with the received electronic communication. While displaying preview  6106 A corresponding to the photo watch user interface, computer system  600 A receives (e.g., detects) an input  6103 A directed to preview  6106 A. In some embodiments, input  6103 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6H , computer system  600 B displays, via display generation component  602 B, user interface  624 B of the messaging application, where user interface  624 B of the messaging application is displaying message conversation  626 B with the message participant (e.g., “Jane Appleseed”). Message conversation  626 A includes a received electronic communication that includes (e.g., as an attachment) the first user interface template (e.g., shown as preview  6106 B in message conversation  626 B), the plurality of selected photos associated with the first user interface template, including photo  6108 A, and a message  630 B associated with the received electronic communication. While displaying preview  6106 B corresponding to the photo watch user interface, computer system  600 B receives (e.g., detects) an input  6103 B directed to preview  6106 B. In some embodiments, input  6103 B is a touch input on display generation component  602 B. 
     In response to (e.g., or subsequent to) receiving input  6103 A, computer device  600 A displays, via displays, via display generation component  602 A, user interface  632 A for creating a watch user interface based on the first user interface template, as shown in  FIG. 6I . Similarly, in response to (e.g., or subsequent to) receiving input  6103 B, computer device  600 B displays, via displays, via display generation component  602 B, user interface  632 B for creating a watch user interface based on the first user interface template, as shown in  FIG. 6I . 
     In  FIG. 6I , computer device  600 A displays, concurrently with preview  6106 A (showing photo  6108 A) of the photo watch user interface in user interface  632 A, an affordance  652 A for initiating a process for creating a photo watch user interface for the respective computer system (e.g., for computer system  600 B) based on the photo watch user interface corresponding to preview  6106 A. While displaying user interface  632 A with preview  6106 A and affordance  652 A, computer system  600 A receives (e.g., detects) an input  6105 A on affordance  652 A. In some embodiments, input  6105 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6I , computer device  600 B displays, concurrently with preview  6106 B (showing photo  6108 A) of the photo watch user interface in user interface  632 B, an affordance  652 B for initiating a process for creating a photo watch user interface for the respective computer system (e.g., for computer system  600 B) based on the photo watch user interface corresponding to preview  6106 B. While displaying user interface  632 B with preview  6106 B and affordance  652 B, computer system  600 B receives (e.g., detects) an input  6105 B on affordance  652 B. In some embodiments, input  6105 B is a touch input on display generation component  602 B. 
     In response to receiving input  6105 A, computer system  600 A displays, via display generation component  602 A, a user interface  6110 A (e.g., a photo-picker user interface) that includes the plurality of photos associated with (and received with) the photo watch user interface, including photo  6108 A, as shown in  FIG. 6J . Similarly, in response to receiving input  6105 B, computer system  600 B displays, via display generation component  602 B, a user interface  6110 B (e.g., a photo-picker user interface) that includes the plurality of photos associated with (and received with) the photo watch user interface, including photo  6108 A, as shown in  FIG. 6J . 
     In  FIG. 6J , user interface  6110 A includes the plurality of associated photos (e.g., where a user can navigate (e.g., scroll) through the photos), including photo  6108 A and  6114 A, where all of the plurality of photos (e.g., 24 of 24 photos) are currently selected to be included with the photo watch user interface corresponding to preview  6106 A. In some embodiments, all associated photos are initially (e.g., when user interface  6110 A is launched) selected to be used in the photo watch user interface, and one or more of the plurality of associated photos can be de-selected (by the user) via user interface  6110 A such that the remaining selected photos will be displayed as the background in the photo watch user interface if the photo watch user interface is used as the current watch user interface on the respective computer system (e.g., on computer system  600 B). In some embodiments, one or more of the plurality of associated photos that are selected (e.g., remains selected) are stored on computer system  600 A and/or on the respective computer system (e.g., on computer system  600 B). In some embodiments, one or more of the plurality of associated photos that are not selected (e.g., were de-selected by the user) are not stored on computer system  600 A and/or the respective computer system (e.g., on computer system  600 B) (e.g., and are instead removed/deleted). 
     While displaying the plurality of photos in user interface  6110 A, computer system  600 A concurrently displays an affordance  6112 A for completing the configuration/setup of the photo watch user interface with the currently-selected photos. While displaying user interface  6110 A with all of the plurality of associated photos selected (e.g., because none of the photos were de-selected by the user), computer system  600 A receives (e.g., detects) an input  6107 A directed to affordance  6112 A. In some embodiments, input  6107 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6J , corresponding user interface  6110 B includes the plurality of associated photos, including photo  6108 A and  6114 A, where all of the plurality of photos (e.g., 24 of 24 photos) are currently selected to be included with the photo watch user interface corresponding to preview  6106 A. In some embodiments, one or more of the plurality of associated photos that are selected (e.g., remains selected) are stored on computer system  600 B. In some embodiments, one or more of the plurality of associated photos that are not selected (e.g., were de-selected by the user) are not stored on computer system  600 B (e.g., and are instead removed/deleted). While displaying the plurality of photos in user interface  6110 B, computer system  600 B concurrently displays an affordance  6112 B for completing the configuration/setup of the photo watch user interface with the currently-selected photos. While displaying user interface  6110 B with all of the plurality of associated photos selected (e.g., because none of the photos were de-selected by the user), computer system  600 B receives (e.g., detects) an input  6107 B directed to affordance  6112 B. In some embodiments, input  6107 B is a touch input on display generation component  602 B. 
     In response to receiving input  6107 A on affordance  6112 A, computer system  600 A displays, via display generation component  602 A, user interface  654  of the companion application, as shown in  FIG. 6K . Similarly, in response to receiving input  6107 B on affordance  6112 B, computer system displays, via display generation component  602 B, a photo watch user interface  6116 B corresponding to the photo watch user interface configured in  FIG. 6J  set as the current watch user interface, as shown in  FIG. 6K . 
     In  FIG. 6K , user interface  654  of the companion application includes, as one of the plurality of watch user interface previews that can be used as a watch user interface on the respective computer system (e.g., on computer system  600 B), photo watch user interface preview  6106 A corresponding to the photo watch user interface configured in  FIG. 6J , and corresponding to photo watch user interface  6116 B displayed in computer system  600 B as the current watch user interface. 
       FIG. 6L  illustrates computer system  600 A displaying, via display generation component  602 A, user interface  632 A where two of the respective eight applications—the first application corresponding to complication preview  636 A and the fifth application corresponding to the complication preview  644 A—are not available on (e.g., not downloaded on; not installed on) the respective computer system (e.g., computer system  600 B). In some embodiments, the unavailable applications correspond to third-party applications (e.g., as opposed to first-party applications developed and published by the same entity controlling the operating system of computer system  600 B), where the third-party applications are available for download onto the respective computer system (e.g., onto computer system  600 B) via a source (e.g., a website or an application store) that is accessible on computer system  600 A and/or the respective computer system (e.g., computer system  600 B). 
     In  FIG. 6L , because the first application and the fifth application are not available on the respective computer system (e.g., on computer system  600 B), computer system  600 A visually indicates (e.g., dims; highlights) complication previews  636 A and  644 A, thereby indicating that the first and fifth applications are currently not available on the respective computer system (e.g., computer system  600 B). In some embodiments, visually indicating complication previews  636 A and  644 A includes visually highlighting complication previews  636 A and  644 A while not visually highlighting the other complication previews. In some embodiments, visually indicating complication previews  636 A and  644 A includes dimming (e.g., darkening; shading) complication previews  636 A and  644 A while not dimming the other complication previews. visually indicating complication previews  636 A and  644 A includes not dimming complication previews  636 A and  644 A while dimming the other complication previews. 
       FIG. 6L  similarly illustrates computer system  600 B displaying, via display generation component  602 B, user interface  632 B where the first application corresponding to complication preview  636 B and the fifth application corresponding to the complication preview  644 B are not available on computer system  600 B. In  FIG. 6L , because the first application and the fifth application are not available on computer system  600 B, computer system  600 B visually indicates (e.g., dims; highlights) complication previews  636 B and  644 B, thereby indicating that the first and fifth applications are currently not available on computer system  600 B. 
     In  FIG. 6L , computer system  600 A displays, in user interface  632 A, an affordance  674 A for continuing with the configuration/setup process for enabling the user interface corresponding to preview  634 A to be used on the respective computer system (e.g., on computer system  600 B). While displaying affordance  674 A, computer system  600 A receives (e.g., detects) an input  611 A on affordance  674 A. In some embodiments, input  611 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6L , computer system  600 B displays, in user interface  632 B, an affordance  674 B for continuing with the configuration/setup process for enabling the user interface corresponding to preview  634 B to be used on computer system  600 B. While displaying affordance  674 B, computer system  600 B receives (e.g., detects) an input  611 B on affordance  674 B. In some embodiments, input  611 B is a touch input on display generation component  602 B. 
     In some embodiments, if the computer system (computer system  600 A or  600 B) does not receive an input on the affordance (affordance  674 A or  674 B) for continuing with the configuration/setup process for a predetermined time period (e.g., 10 seconds; 15 seconds; 30 seconds), the computer system automatically (e.g., without any further user input) completes the configuration/setup process, where a new watch user interface generated from the first user interface template becomes available for use on the respective computer system (e.g., on computer system  600 B) without including complications that correspond to the unavailable applications. 
     In response to receiving input  611 A on affordance  674 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A as shown in  FIG. 6M . Similarly, in response to receiving input  611 B on affordance  674 B, computer system  600 B displays, via display generation component  620 B, user interface  632 B as shown in  FIG. 6M . 
     In  FIG. 6M , computer system  600 A visually highlights complication preview  636 A corresponding to the first application without visually highlighting the other complication previews (including not visually highlighting complication preview  644 A corresponding to the unavailable fifth application), thereby indicating that the current step in the configuration/setup process relates to first application corresponding to complication preview  636 A. In some embodiments, computer system  600 A concurrently displays, in user interface  632 A, an indication  676 A (e.g., text information) that the current step in the configuration/setup process relates to one of the complications of the first user interface template for which the respective application is not available on the respective computer system (e.g., on computer system  600 B), and of the current stage within the configuration/setup process (e.g., “1 of 2”). 
     While visually highlighting complication preview  636 A, computer system  600 A displays, in user interface  632 A, an affordance  678 A for downloading (e.g., via an application store) the first application corresponding to complication preview  636 A, and an affordance  680 A for continuing the configuration/setup process without downloading the first application. While displaying affordances  678 A and  680 A, computer system  600 A receives (e.g., detects) an input  613 A on affordance  680 A. 
     Similarly, in  FIG. 6M , computer system  600 B visually highlights complication preview  636 B corresponding to the first application without visually highlighting the other complication previews (including not visually highlighting complication preview  644 B corresponding to the unavailable fifth application). In some embodiments, computer system  600 B concurrently displays, in user interface  632 B, an indication  676 B (e.g., text information) that the current step in the configuration/setup process relates to one of the complications of the first user interface template for which the respective application is not available on computer system  600 B, and of the current stage within the configuration/setup process (e.g., “1 of 2”). 
     While visually highlighting complication preview  636 B, computer system  600 B displays, in user interface  632 B, an affordance  678 B for downloading (e.g., via an application store) the first application corresponding to complication preview  636 B, and an affordance  680 B for continuing the configuration/setup process without downloading the first application. While displaying affordances  678 B and  680 B, computer system  600 B receives (e.g., detects) an input  613 B on affordance  680 B. 
     In response to receiving input  613 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A as in  FIG. 6N . Similarly, in response to receiving input  613 B, computer system  600 B displays, via display generation component  602 B, user interface  632 B as in  FIG. 6N . 
     In  FIG. 6N , because the first application was not downloaded, preview  634 A does not (e.g., no longer) include complication preview  636 A corresponding to the first application that was not downloaded. 
     In  FIG. 6N , computer system  600 A visually highlights complication preview  644 A corresponding to the fifth application without visually highlighting the other complication previews in preview  634 A, thereby indicating that the current step in the configuration/setup process relates to the fifth application. In some embodiments, computer system  600 A updates display of, in user interface  632 A, indication  676 A (e.g., text information) of the current step in the configuration/setup process to indicate the current stage within the configuration/setup process (e.g., “2 of 2”). 
     While visually highlighting complication preview  644 A, computer system  600 A displays, in user interface  632 A, an affordance  682 A for downloading (e.g., via an application store) the fifth application, and an affordance  684 A for continuing the configuration/setup process without downloading the fifth application. While displaying affordances  682 A and  684 A, computer system  600 A receives (e.g., detects) an input  615 A on affordance  682 A. 
     Similarly, in  FIG. 6N , because the first application was not downloaded, preview  634 B does not (e.g., no longer) include complication preview  636 B corresponding to the first application that was not downloaded. 
     In  FIG. 6N , computer system  600 B visually highlights complication preview  644 B corresponding to the fifth application without visually highlighting the other complication previews in preview  634 B, thereby indicating that the current step in the configuration/setup process relates to the fifth application. In some embodiments, computer system  600 B updates display of, in user interface  632 B, indication  676 B (e.g., text information) of the current step in the configuration/setup process to indicate the current stage within the configuration/setup process (e.g., “2 of 2”). 
     While visually highlighting complication preview  644 B, computer system  600 B displays, in user interface  632 B, an affordance  682 B for downloading (e.g., via an application store) the fifth application, and an affordance  684 B for continuing the configuration/setup process without downloading the fifth application. While displaying affordances  682 B and  684 B, computer system  600 B receives (e.g., detects) an input  615 B on affordance  682 B. 
     In some embodiments, the fifth application corresponding to complication preview  644 A/ 644 B is installed on computer system  600 A but is not installed on computer system  600 B. In some embodiments, in accordance with a determination that the fifth application is installed on computer system  600 A but is not installed on computer system  600 B (e.g., and where computer system  600 A (e.g., a smartphone) and computer system  600 B (e.g., a smartwatch) are paired systems), computer system  600 B does not visually highlight complication preview  644 B corresponding to the fifth application, forgoes displaying affordance  682 B for downloading the fifth application and affordance  684 B for continuing the configuration/setup process without downloading the fifth application, and instead automatically downloads (e.g., without user input) the fifth application (directly) from computer system  600 A (e.g., via a short-range connection (e.g., Bluetooth)). 
     In some embodiments, in accordance with a determination that the fifth application corresponding to complication preview  644 A/ 644 B is installed on computer system  600 A but is not installed on computer system  600 B (e.g., and where computer system  600 A (e.g., a smartphone) and computer system  600 B (e.g., a smartwatch) are paired systems), computer system  600 B still visually highlights representation  644 B corresponding to the fifth application and displays affordance  682 B and affordance  684 B as in  FIG. 6N . In some embodiments, in accordance with (e.g., in response to) an input on affordance  682 B, computer system  600 B downloads the fifth application (directly) from computer system  600 A (e.g., via a short-range connection (e.g., Bluetooth)) (e.g., instead of downloading the fifth application via the Internet). 
     In some embodiments, while displaying user interface  632 A as in  FIG. 6N , if computer system  600 A does not detect an input on affordance  682 A for a predetermined time period (e.g., 10 seconds; 15 seconds; 30 seconds), computer system  600 A automatically (e.g., without any user input) proceeds with the configuration/setup process without downloading the fifth application corresponding to complication preview  644 A. Similarly, in some embodiments, while displaying user interface  632 B as in  FIG. 6N , if computer system  600 B does not detect an input on affordance  682 B for the predetermined time period (e.g., 10 seconds; 15 seconds; 30 seconds), computer system  600 B automatically (e.g., without any user input) proceeds with the configuration/setup process without downloading the fifth application corresponding to complication preview  644 B on computer system  600 B. 
     In response to receiving input  615 A, computer system  600 A displays, via display generation component  602 A, user interface  632 A as in  FIG. 6O . Similarly, in response to receiving input  615 B, computer system  600 B displays, via display generation component  602 B, user interface  632 B as in  FIG. 6O . 
     In  FIG. 6O , computer system  600 A displays, via display generation component  602 A, a user interface  686 A of an application store, where user interface  686 A corresponds to a page of the application store relating to the fifth application, and where user interface  686 A includes an affordance  688 A for downloading the fifth application onto computer system  600 A. In some embodiments, the application store is a first-party application developed and controlled by the same entity controlling the operating system of computer system  600 A, and from which first-party and/or third-party applications can be downloaded onto computer system  600 A. In some embodiments, applications that are downloaded onto computer system  600 A can also be installed on the respective computer system (e.g., on computer system  600 B) (e.g., directly from computer system  600 A to computer system  600 B via a companion application on computer system  600 A). While displaying user interface  686 A, computer system  600 A receives (e.g., detects) an input  617 A on affordance  688 A. In some embodiments, input  617 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6O , computer system  600 B displays, via display generation component  602 B, a user interface  686 A of the application store, where user interface  686 A corresponds to the page of the application store relating to the fifth application, and where user interface  686 B includes an affordance  688 B for downloading the fifth application onto computer system  600 B. While displaying user interface  686 B, computer system  600 B receives (e.g., detects) an input  617 B on affordance  688 B. In some embodiments, input  617 B is a touch input on display generation component  602 B. 
     In response to receiving input  617 A on affordance  688 A, computer system  600 A initiates a process for downloading the fifth application onto computer system  600 A, as in  FIG. 6P . Similarly, in response to receiving input  617 B on affordance  688 B, computer system  600 B initiates a process for downloading the fifth application onto computer system  600 B, as in  FIG. 6P . 
     In  FIG. 6P , computer system  600 A displays, overlaid on a portion of user interface  686 A, an authorization user interface  690  for authorizing the downloading (and installing) of the fifth application onto computer system  600 A. In some embodiments, authorization user interface  690  includes instructions  692 A for how to authorize and/or initiate the downloading (and installing) of the fifth application onto computer system  600 A. In some embodiments, while displaying authorization user interface  690 , computer system  600 A receives, via an input device  694 A, an input  619 A (e.g., a double-press input on a mechanical input button of computer system  600 A) in accordance with instructions  692 A. 
     Similarly, in  FIG. 6P , computer system  600 B displays, overlaid on user interface  686 B, instructions  692 B for how to authorize and/or initiate the downloading (and installing) of the fifth application onto computer system  600 B. In some embodiments, while displaying instructions  692 B, computer system  600 B receives, via an input device  694 B, an input  619 B (e.g., a double-press input on a mechanical input button of computer system  600 B) in accordance with instructions  692 B. 
     In response to receiving input  619 A while displaying authorization user interface  690 , computer system  600 A downloads and installs the fifth application on computer system  600 A (e.g., and, after having downloaded (and installed) the fifth application onto computer system  600 A, causes the fifth application to be installed on the respective computer system (e.g., on computer system  600 B)). Similarly, in response to receiving input  619 B while displaying instructions  692 B, computer system  600 B downloads and installs the fifth application on computer system  600 B. 
       FIG. 6Q  illustrates computer system  600 A displaying, via display generation component  602 A, user interface  623 A showing preview  634 A after (e.g., in response to) downloading and installing the fifth application on the respective computer system (e.g., on computer system  600 B). In  FIG. 6Q , preview  634 A includes complication preview  644 A corresponding to the fifth application that is not visually highlighted, thereby indicating that the respective complication corresponding to complication preview  644 A can be used on the watch user interface corresponding to preview  634 A once the configuration/setup process has been completed. As also shown in  FIG. 6Q , preview  634 A still includes display of the other complication previews corresponding to respective complications that can be used (e.g., because their respective applications were already available on (e.g., installed on) the respective computer system (e.g., on computer system  600 B)) on the watch user interface corresponding to preview  634 A once the configuration/setup process has been completed. 
     While displaying user interface  623 A showing preview  634 A as in  FIG. 6Q , computer system  600 A concurrently displays, in user interface  632 A, an affordance  696 A for completing the configuration/setup process for enabling the user interface corresponding to the first user interface template for use on the respective computer system (e.g., on computer system  600 B) without the first watch complication, and an affordance  698 A for continuing the configuration/setup process to initiate the downloading of one or more applications that had not been downloaded (e.g., the first application). 
     While displaying affordances  696 A and  698 A, computer system  600 A receives (e.g., detects) an input  621 A on affordance  696 A for completing the configuration/setup process. In some embodiments, input  621 A is a touch input on display generation component  602 A. In response to detecting input  621 A on affordance  696 A, computer system  600 A completes the configuration/setup process. In some embodiments, in response to (e.g., or subsequent to) completing the configuration/setup process, computer system  600 A displays, via display generation component  602 A, user interface  654  of the companion application (first described above with reference to  FIG. 6K ), where user interface  654  includes a watch user interface preview corresponding to the new watch user interface created in  FIG. 6Q . 
     Similarly,  FIG. 6Q  also illustrates computer system  600 B displaying, via display generation component  602 B, user interface  623 B showing preview  634 B after (e.g., in response to) downloading and installing the fifth application on computer system  600 B. In  FIG. 6Q , preview  634 B includes complication preview  644 B corresponding to the fifth application that is not visually highlighted, thereby indicating that the respective complication corresponding to complication preview  644 B can be used on the watch user interface corresponding to preview  634 B once the configuration/setup process has been completed. As also shown in  FIG. 6Q , preview  634 B still includes display of the other complication previews corresponding to respective complications that can be used (e.g., because their respective applications were already available on (e.g., installed on) computer system  600 B) on the watch user interface corresponding to preview  634 A once the configuration/setup process has been completed. 
     While displaying user interface  623 B showing preview  634 B as in  FIG. 6Q , computer system  600 B concurrently displays, in user interface  632 B, an affordance  696 B for completing the configuration/setup process for enabling the user interface corresponding to the first user interface template for use on computer system  600 B without the first watch complication, and an affordance  698 B for continuing the configuration/setup process to initiate the downloading of one or more applications that had not been downloaded (e.g., the first application). 
     While displaying affordances  696 B and  698 B, computer system  600 B receives (e.g., detects) an input  621 A on affordance  696 B for completing the configuration/setup process. In some embodiments, input  621 B is a touch input on display generation component  602 B. In response to detecting input  621 B on affordance  696 B, computer system  600 B completes the configuration/setup process. In some embodiments, in response to (e.g., or subsequent to) completing the configuration/setup process, computer system  600 B displays, via display generation component  602 B, the new watch user interface created in  FIG. 6Q  as the current watch user interface. 
     As described above with reference to  FIG. 6B , in some embodiments, the first user interface template can be downloaded and/or received via the application store on the computer (computer system  600 A or computer system  600 B). In some embodiments, in response to receiving (e.g., detecting) a request to download/receive the first user interface template via the application store, in accordance with a determination that one or more respective applications corresponding to the first user interface template is not installed on (e.g., is not available on) the respective computer system (e.g., on computer system  600 B), the computer system displays an indication (e.g., a notification; a prompt; a request) indicating that that the one or more respective applications (e.g., the first application and the fifth application) are not installed, and requesting authorization to download the one or more respective applications (e.g., the first application and the fifth application) that are not installed (e.g., via the application store; concurrently as part of the process of downloading the first user interface template from the application store). In some embodiments, in response to receiving (e.g., detecting) a request to download/receive the first user interface template via the application store, the computer system downloads the first user interface template via the application store. In some embodiments, after (e.g., immediately after, in response to) downloading (e.g., and installing) the first user interface template and in accordance with a determination that one or more respective applications corresponding to the first user interface template is not installed on (e.g., is not available on) the respective computer system (e.g., on computer system  600 B), the computer system displays an indication (e.g., a notification; a prompt; a request) indicating that that the one or more respective applications (e.g., the first application and the fifth application) are not installed, and requests authorization to download the one or more respective applications that are not installed. 
       FIG. 6R  illustrates computer system  600 A displaying, via display generation component  602 A, user interface  632 A, where user interface  632 A includes preview  634 A corresponding to the first user interface template if the fifth application corresponding to complication preview  644 A had not been downloaded onto computer system  600 A (e.g., because affordance  684 A, instead of affordance  682 A, had been activated in  FIG. 6N ). 
     In  FIG. 6R , because the fifth application had not been downloaded, preview  634 A does not include complication preview  636 A corresponding to the first application and does not include complication preview  644 A corresponding to the fifth application. As in  FIG. 6Q , because a decision has been made (as to whether to download each of the respective applications that were not available on the respective computer system (e.g., on computer system  600 B)) for each of the respective applications that were not available on the respective computer system (e.g., on computer system  600 B), computer system  600 A displays, in user interface  632 A, affordance  696 A for completing the configuration/setup process for enabling the user interface corresponding to the first user interface template for use on the respective computer system (e.g., on computer system  600 B) without the complications corresponding to the first and fifth applications, and affordance  698 A for returning to the configuration/setup process to initiate the downloading of one or more applications that had not been downloaded. 
     Similarly, in  FIG. 6R , because the fifth application had not been downloaded, preview  634 B does not include complication preview  636 B corresponding to the first application and does not include complication preview  644 B corresponding to the fifth application. As in  FIG. 6Q , because a decision has been made (as to whether to download each of the respective applications that were not available on computer system  600 B) for each of the respective applications that were not available on computer system  600 B, computer system  600 B displays, in user interface  632 B, affordance  696 B for completing the configuration/setup process for enabling the user interface corresponding to the first user interface template for use on computer system  600 B without the complications corresponding to the first and fifth applications, and affordance  698 B for returning to the configuration/setup process to initiate the downloading of one or more applications that had not been downloaded. 
     In response to receiving input  621 A on affordance  696 A in  FIG. 6Q , computer system  600 A displays, via display generation component  602 A, user interface  654  that includes watch user interface preview  699 A as in  FIG. 6S . Similarly, in response to receiving input  621 B on affordance  696 B in  FIG. 6Q , computer system  600 B displays, via display generation component  602 B, a watch user interface  699 B (corresponding to watch user interface preview  699 A) as in  FIG. 6S . 
     In  FIG. 6S , user interface  654  includes watch user interface preview  699 A (including complication previews  638 A- 650 A) corresponding to the user interface for which configuration/setup was completed in  FIG. 6Q , thereby indicating that the watch user interface corresponding to preview  699 A is available for use on the respective computer system (e.g., on computer system  600 B). Computer system  600 B shows the corresponding watch user interface (watch user interface  699 B) being used on computer system  600 B as the current watch user interface, where watch user interface  699 B includes complications  697 - 685  corresponding to complication previews  638 A- 650 A, respectively. 
       FIG. 6T  illustrates a computer system  600 C (e.g., a smartphone) and a computer system  600 D (e.g., a smartwatch). In some embodiments, computer system  600 C is paired with computer system  600 D. In some embodiments, computer system  600 C can be used to control and/or manage configurations and settings on computer system  600 D (e.g., via a companion application for computer system  600 D that is accessible on computer system  600 C). 
     In  FIG. 6T , computer system  600 C displays, via a display generation component  602 C, a user interface  683  (e.g., similar to user interface  654  first described above with reference to  FIG. 6F ) for setting and/or editing user interface settings for a respective computer system (e.g., for computer system  600 D), including selecting a watch user interface for use on the respective computer system (e.g., on computer system  600 D). In some embodiments, user interface  683  includes a watch user interface preview  681  corresponding to watch user interface  679  displayed by computer system  600 B in  FIG. 6T . 
     While displaying user interface  683 , computer system  600 C receives (e.g., detects) an input  623 A on watch user interface preview  681  corresponding to watch user interface  679 . In some embodiments, input  623 A is a touch input on display generation component  602 A. While displaying watch user interface  679 , computer system  600 D receives (e.g., detects) an input  623 B on watch user interface  679 . In some embodiments, input  623 B is a touch input on display generation component  602 B. In some embodiments, input  623 B is a press input (e.g., a press-and-hold input) on display generation component  602 B. 
     In response to receiving input  623 A, computer system  600 C displays, via display generation component  602 C, a user interface  677  for managing settings associated with watch user interface  679 , as shown in  FIG. 6U . In response to receiving input  623 B, computer system  600 D displays, via display generation component  602 D, a user interface  655  for editing one or more features (e.g., complication types) of watch user interface  679 . 
     In  FIG. 6U , user interface  677  displayed in computer system  600 A includes a watch user interface preview  675  of watch user interface  679 . In some embodiments, user interface  677  includes user interface elements  673 - 659  for setting a complication type for a respective complication included in watch user interface  679 . In some embodiments, user interface  677  includes an affordance  657 A for initiating a sharing of watch user interface  679  (e.g., initiating a process for sending/transmitting watch user interface  679 , as a user interface template, to a different computer system). While displaying user interface  677 , computer system  600 C receives (e.g., detects) an input  625 A on affordance  657 A. In some embodiments, input  625 A is a touch input on affordance  657 A. 
     In  FIG. 6U , user interface  655  displayed in computer system  600 B includes a watch user interface preview  653  of watch user interface  679  an affordance  657 B (corresponding to affordance  657 A) for initiating a sharing of watch user interface  679  (e.g., initiating a process for sending/transmitting watch user interface  679 , as a user interface template, to a different computer system). While displaying user interface  655 , computer system  600 D receives (e.g., detects) an input  625 B on affordance  657 B. In some embodiments, input  625 B is a touch input on affordance  657 B. 
     In response to receiving input  625 A on affordance  657 A, computer system  600 C displays, via display generation component  602 C, a user interface  651 A for selecting a recipient (e.g., from a contactable users list) of the user interface template corresponding to watch user interface  679  being shared and/or for selecting a type of communication channel to transmit the user interface template, as shown in  FIG. 6V . Similarly, in response to receiving input  625 B on affordance  657 B, computer system  600 D displays, via display generation component  602 D, a user interface  651 B for selecting a recipient (e.g., from a contactable users list) of the user interface template corresponding to watch user interface  679  being shared and/or for selecting a type of communication channel to transmit the user interface template, as shown in  FIG. 6V . 
     In some embodiments, the user interface template (corresponding to watch user interface  679 ) being shared can be transmitted from computer system  600 C to a computer system (e.g., an electronic device, such as a smartphone or a smartphone) of the recipient (e.g., an electronic device logged into an account associated with the recipient) via a messaging application (e.g., as an attachment of a message). In some embodiments, the user interface template being shared can be transmitted via a chat application. In some embodiments, the user interface template being shared can be transmitted via an electronic mail application (e.g., as an attachment). In some embodiments, the user interface template being shared can be transmitted via short-range communication (e.g., via NFC; via Bluetooth). In some embodiments, the user interface template being shared can be transmitted by uploading the user interface template to the Internet, from which the template is available for download by the recipient (e.g., by selecting a hyperlink corresponding to the uploaded template). 
     In  FIG. 6V , user interface  651 A includes a plurality of contactable users that can be selected as the recipient, including contactable users  649 A,  647 A, and  645 A. While displaying the plurality of contactable users, computer system  600 C receives (e.g., detects) an input  627 A directed to selecting contactable user  649 A. In some embodiments, input  627 A is a touch input on display generation component  602 A. 
     Similarly, in  FIG. 6V , user interface  651 B includes corresponding contactable users available for selection as the recipient, including a contactable users  649 B,  647 B, and  645 B. While displaying the plurality of contactable users, computer system  600 D receives (e.g., detects) an input  627 B directed to selecting contactable user  649 B. In some embodiments, input  627 B is a touch input on display generation component  602 B. 
     In response to receiving input  627 A, computer device  600 C displays, via display generation component  602 C, a user interface  643 A of a messaging application, where user interface  643 A includes a message conversation  641 A with contactable user  649 A, as shown in  FIG. 6W . Similarly, in response to receiving input  627 B, computer system  600 D displays, via display generation component  602 D, a user interface  643 B of a messaging application, where user interface  643 B includes a message conversation  641 B with contactable user  649 B, as shown in  FIG. 6W . As mentioned, sharing a watch user interface via a messaging application is one of several different communication channels through which the watch user interface can be shared with a different user. 
     In  FIG. 6W , computer system  600 C displays, in message conversation  641 A, a preview  639 A of the user interface template (corresponding to watch user interface  679 ) being shared and an affordance  637 A for initiating the transmittal of a message that includes the user interface template to the recipient&#39;s computer system. While displaying message conversation  641 A, computer system  600 C receives (e.g., detects) an input  629 A on affordance  637 A. In some embodiments, input  629 A is a touch input on display generation component  602 A. In response to receiving input  629 A on affordance  637 A, computer system  600 C transmits the message that includes the user interface template corresponding to watch user interface  679  to the recipient&#39;s computer system (e.g., similar to how computer system  600 A received the first user interface template in  FIG. 6E ). Once received, the recipient can go through a process corresponding to the process described above with reference to  FIGS. 6F-6S  to configure/setup a new watch user interface based on the shared user interface template for use on the recipient&#39;s computer system. 
     Similarly, in  FIG. 6W , computer system  600 D displays, in message conversation  641 B, a preview  639 B of the user interface template (corresponding to watch user interface  679 ) being shared and an affordance  637 B for initiating the transmittal of a message that includes the user interface template to the recipient&#39;s computer system. While displaying message conversation  641 B, computer system  600 D receives (e.g., detects) an input  629 B on affordance  637 B. In some embodiments, input  629 B is a touch input on display generation component  602 B. In response to receiving input  629 B on affordance  637 B, computer system  600 D transmits the message that includes the user interface template corresponding to watch user interface  679  to the recipient&#39;s computer system for use by the recipient. 
       FIG. 6X  illustrates computer system  600 B displaying, via display generation component  602 B, a first type of notification  635 A (e.g., a prompt) concerning the configuration/setup process for a downloaded, received, and/or detected user interface template. In some embodiments, computer system  600 B is not capable of directly downloading applications (e.g., from an application store or a website) onto computer system  600 B (e.g., because computer system  600 B does not have direct access to the Internet). In some embodiments, in accordance with a determination that computer system  600 B is not capable of directly downloading applications onto computer system  600 B (e.g., and upon detecting a request to initiate the process for configuring/setting up a new user interface template using computer system  600 B), computer system  600 B displays notification  635 A indicating that that the process should be initiated on a different computer system (e.g., a computer system that is paired with computer system  600 B, such as computer system  600 A (e.g., a smartphone)) and/or indicating that one or more applications associated with the user interface template that are not currently available on computer system  600 B should first be downloaded onto the different computer system (e.g., a computer system that is paired with computer system  600 B, such as computer system  600 A). 
       FIG. 6Y  illustrates computer system  600 B displaying, via display generation component  602 B, a second type of notification  635 B (e.g., a prompt) concerning the configuration/setup process for the downloaded, received, and/or detected user interface template. In some embodiments, computer system  600 B is not capable of directly downloading applications (e.g., from a website or an application store) onto computer system  600 B (e.g., because computer system  600 B does not have direct access to the Internet). In some embodiments, in accordance with a determination that computer system  600 B is not capable of directly downloading applications from an application store onto computer system  600 B (e.g., and upon detecting a request to initiate the process for configuring/setting up a user interface template using computer system  600 B), computer system  600 B displays notification  635 B indicating that one or more applications associated with the user interface template that are not currently available on computer system  600 B should first be downloaded via an application store accessed on the different computer system (e.g., a computer system that is paired with computer system  600 B, such as computer system  600 A). In some embodiments, notification  635 B also includes an affordance  633  (e.g., a selectable user interface object; an activatable user interface object) which, when activated (e.g., when selected), (e.g., immediately) completes the configuration/setup process and adds the user interface corresponding to the new user interface template to a user interface library of computer system  600 B. 
       FIG. 6Z  illustrates computer system  600 A displaying, via display generation component  602 A, a third type of notification  635 C (e.g., a notification user interface) indicating that the type of user interface corresponding to the downloaded, received, and/or detected user interface template can only be used on certain types (e.g., certain models) of computer systems, and that the type of user interface corresponding to the user interface template cannot be used on (e.g., the new user interface template is not compatible with) the respective computer system (e.g., computer system  600 B). 
       FIG. 6AA  illustrates computer system  600 A displaying, via display generation component  602 A, a fourth type of notification  635 D (e.g., a notification user interface) indicating that software (e.g., operating system software; operating system version) on the respective computer system (e.g., computer system  600 B) for which the user interface corresponding to the downloaded, received, and/or detected user interface template is to be used needs to be updated in order for the user interface corresponding to the user interface template to be able to be used on the respective computer system (e.g., on computer system  600 B). In some embodiments, notification  635 D includes an affordance  631  (e.g., a selectable user interface object; an activatable user interface object) that, when activated, initiates a process for updating the software (e.g., operating system software; operating system version) on the respective computer system (e.g., on computer system  600 B). 
       FIG. 6AB  illustrates computer system  600 A displaying, via display generation component  602 A, a fifth type of notification  635 E (e.g., a notification user interface) indicating that (e.g., for a miscellaneous reason) the user interface (e.g., or the type of user interface) corresponding to the downloaded, received, and/or detected user interface template cannot be used on the respective computer system (e.g., on computer system  600 B). 
       FIGS. 7A-7F  are a flow diagram illustrating a method for managing user interface sharing using a computer system (e.g., an electronic device), in accordance with some embodiments. Method  700  is performed at a computer system (e.g., an electronic device (e.g.,  100 ,  300 ,  500 ,  600 A,  600 B)) that is in communication with a display generation component (e.g., a display, a touch-sensitive display (e.g.,  112 )). Some operations in method  700  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  700  provides an intuitive way for managing user interface sharing. The method reduces the cognitive burden on a user for managing user interface sharing, thereby creating a more efficient human-machine interface. For battery-operated computer systems (e.g., computing devices; electronic devices), enabling a user to manage user interface sharing faster and more efficiently conserves power and increases the time between battery charges. 
     The computer system (e.g.,  600 A;  600 B) receives ( 702 ) (e.g., from a second computer system (e.g., a second electronic device; a second smart device, such as a second smartphone or a second smartwatch; an external server)), a representation (e.g.,  634 A;  634 B) of a first user interface template (e.g., a template of a watch face or clock user interface created by and/or shared by another user; a template of a watch face or clock user interface created on a different computer system or electronic device and received from the different computer system or electronic device) that specifies an arrangement of user interface elements (e.g., previews/images of watch complications; where the user interface elements can include one or more of  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and/or  650 B) including a first user interface element (e.g., a first watch complication) corresponding to a first application (e.g., the application that controls the corresponding first watch complication) and one or more other user interface elements (e.g., one or more other/different watch complications corresponding to other/different applications; an indication of a time and/or date; or one or more other watch complications corresponding to a system feature) corresponding to software that is different from the first application. Receiving a representation of a first user interface template that specifies an arrangement of user interface elements (e.g., as opposed to creating a user interface with the first user interface template on the computer system) enables convenient creation of user interfaces and reduces the number of inputs needed to create a user interface. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the representation (e.g.,  634 A;  634 B) of the first user interface template is received via a message in a message conversation (e.g.,  626 A;  626 B; as an attachment file). In some embodiments, the representation of the first user interface template is received via NFC from a second computer system (e.g.,  612 ; a second electronic device). In some embodiments, the representation of the first user interface template is received via a QR code scan (e.g., via  618 ). In some embodiments, the representation of the first user interface template is downloaded via a link (e.g.,  610 A;  610 B) from a webpage (e.g.,  606 A;  606 B). Providing various different methods to receive/access to a user interface template enables convenient access to the various different user interface templates. Providing additional control options/access to different operations for accessing the user interface templates enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     Subsequent to receiving the representation (e.g.,  634 A,  634 B) of the first user interface template (e.g., and while displaying the representation of the first user interface template (or an indication or preview of the first user interface template)), the computer system (e.g.,  600 A;  600 B) receives ( 708 ) a request (e.g.,  609 A;  609 B;  611 A;  611 B) to use the first user interface template for a respective computer system (e.g.,  600 B; the current computer system (e.g., the current electronic device), a different computer system (e.g.,  600 B; a different electronic device) that is paired with the current computer system (e.g., the current electronic device)) that includes a plurality of installed applications. 
     In response to receiving ( 710 ) the request (e.g.,  609 A;  609 B;  611 A;  611 B) to use the first user interface template for the respective computer system (e.g.,  600 B), the computer system (e.g.,  600 A;  600 B) initiates ( 712 ) a process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating a user interface for the respective computer system using the first user interface template. Initiating the process for creating a user interface for the respective computer system using the first user interface template provides quick and easy access to the process for creating the user interface. In some embodiments, the process for creating the user interface is initiated automatically without user input. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     The process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes ( 714 ), in accordance with a determination that the first application is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system, the computer system (e.g.,  600 A;  600 B) displaying ( 716 ), via the display generation component (e.g.,  602 A;  602 B), an alert (e.g., user interface  632 A of  FIG. 6M ; user interface  632 B of  FIG. 6M ; user interface  632 A of  FIG. 6N ; user interface  632 B of  FIG. 6N ; a notification; a prompt; a message; an affordance) indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template; and in accordance with a determination that the first application is available on (e.g., downloaded onto; installed on; locally accessible on) the respective computer system, the computer system forgoing displaying ( 718 ), via the display generation component, the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. Displaying the alert indicating that the first application needs to be installed on the respective computer system in accordance with the determination that the first application is not available on the respective computer system enables a user to quickly and easily recognize that further action must be taken to enable use of the user interface on the computer system. Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes ( 714 ), in accordance with the determination ( 724 ) that the first application is not available on the respective computer system, the computer system (e.g.,  600 A;  600 B) displaying ( 724 ), via the display generation component (e.g.,  602 A;  602 B), an affordance (e.g.,  678 A;  678 B;  682 A;  682 B; an install affordance or an install prompt that can be selected to initiate the download and/or installing of the first application on the computer system) that, when activated, initiates a process (e.g., displays an application store) for installing the first application on the respective computer system (e.g., downloading the first application (e.g., from the application store; from an external server) onto the respective computer system and installing the first application on the respective computer system). Displaying the affordance that, when activated, initiates the process for installing the first application on the respective computer system enables a user to easily control, during the configuration/setup process, whether or not the first application should be installed on the respective computer. Providing easily accessible control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the affordance (e.g.,  678 A;  678 B;  682 A;  682 B) is displayed after (e.g., in response to) receiving the request to use the first user interface template for the respective computer system (e.g.,  600 B). In some embodiments, the affordance is displayed concurrently with the alert (e.g., user interface  632 A of  FIG. 6M ; user interface  632 B of  FIG. 6M ; user interface  632 A of  FIG. 6N ; user interface  632 B of  FIG. 6N ) indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template. Displaying the affordance concurrently with the alert enables a user to quickly and easily recognize that the affordance relates to the first user interface element that is indicated (e.g., highlighted) via the alert. Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes, in accordance with a determination that the affordance (e.g.,  678 A;  678 B;  682 A;  682 B) was not activated (e.g., the user affirmatively chooses to proceed without installing the first application (e.g., by selecting an affordance to continue without installing the first application on the respective computer system or by selecting an affordance to dismiss the affordance for installing the first application on the respective computer system), the user does not select the affordance for a predetermined time period (e.g., 5 seconds; 10 seconds) while the affordance was displayed), the computer system (e.g.,  600 A;  600 B) continuing ( 728 ) the process for creating the user interface for the respective computer system using the first user interface template without installing (e.g., without downloading and installing) the first application on the respective computer system, where the first user interface template is configured to (e.g., set to; modified to) not include the first user interface element (e.g., the first watch complication) corresponding to the first application. Continuing (e.g., automatically, without further user input) the process for creating the user interface for the respective computer system if the user does not select the affordance for a predetermined time period optimizes the configuration/setup process by enabling the process to proceed if a user input is not detected for a prolonged period of time. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, during the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template, while displaying the affordance (e.g.,  678 A;  678 B;  682 A;  682 B), the computer system (e.g.,  600 A;  600 B) detects (e.g., via one or more input devices of the computer system, such as a touch-sensitive surface that is integrated with the display generation component (e.g.,  602 A;  602 B)) an activation (e.g.,  615 A;  615 B) of (e.g., user selection of) the affordance, and in response to detecting the activation of the affordance, initiates ( 730 ) the process for installing the first application on the respective computer system. Enabling the initiation of the process for installing the first application via the affordance provided during the configuration/setup process enables a user to quickly and easily install the first application. Providing easily accessible control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the process for (e.g., as shown in  6 N- 6 O) installing the first application on the respective computer system (e.g.,  600 B) includes displaying (e.g., on the computer system (e.g.,  600 A;  600 B) and/or on the respective computer system) an application store (e.g.,  6100 A;  6100 B;  686 A;  686 B) for downloading the first application onto the respective computer system and/or downloading (e.g., automatically, without displaying the application store) the first application onto the respective computer system. 
     In some embodiments, the one or more other user interface elements (e.g., where the user interface elements can include one or more of  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and/or  650 B) include ( 704 ) a second user interface element (different from the first user interface element and arranged at a different location/position within the first user interface template than the first user interface element) (e.g., a second watch complication) corresponding to a second application different from the first application, where the process for creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes (e.g., after displaying the alert ( 732 ) indicating that the first application needs to be installed on the respective computer system or forgoing displaying the alert): in accordance with a determination that the second application (e.g., that controls the second user interface element) is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system, the computer system (e.g.,  600 A;  600 B) displaying ( 720 ), via the display generation component (e.g.,  602 A;  602 B), a second alert (e.g., user interface  632 A of  FIG. 6H ; user interface  632 B of  FIG. 6H ; user interface  732 A of  FIG. 6I ; user interface  632 B of  FIG. 6I ; a notification; a prompt; a message) indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template (e.g., the second alert is displayed after the computer system has displayed and is no longer displaying the alert); and in accordance with a determination that the second application is available on (e.g., downloaded onto; installed on; locally accessible on) the respective computer system, the computer system forgoing displaying ( 722 ), via the display generation component, the second alert indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template. 
     In some embodiments, the one or more other user interface elements (e.g., where the user interface elements can include one or more of  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and/or  650 B) include a second user interface element (different from the first user interface element and arranged at a different location/position within the first user interface template than the first user interface element) (e.g., a second watch complication) corresponding to a second application different from the first application and a third user interface element (different from the first and second user interface elements and arranged at a different location/position within the first user interface template than the first and second user interface elements) (e.g., a third watch complication) corresponding to a third application different from the first application and the second application, where the process for creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes subsequent to (e.g., after) displaying the alert (e.g., user interface  632 A of  FIG. 6H ; user interface  632 B of  FIG. 6H ; user interface  732 A of  FIG. 6I ; user interface  632 B of  FIG. 6I ) (e.g., and while no longer displaying the alert), in accordance with a determination that the second application (e.g., that corresponds to the second user interface element) is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system, the computer system (e.g.,  600 A;  600 B) displaying ( 734 ), via the display generation component (e.g.,  602 A;  602 B), a second alert ( 736 ) (e.g., user interface  632 A of  FIG. 6H ; user interface  632 B of  FIG. 6H ; user interface  732 A of  FIG. 6I ; user interface  632 B of  FIG. 6I ; a notification; a prompt; a message) indicating that the second application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the second user interface element from the first user interface template (e.g., the second alert is displayed after the computer system has displayed and is no longer displaying the alert), and subsequent to (e.g., after) displaying the second alert (e.g., and while no longer displaying the second alert), in accordance with a determination that the third application (e.g., that controls the second user interface element) is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system, the computer system displaying ( 738 ), via the display generation component, a third alert (e.g., user interface  632 A of  FIG. 6H ; user interface  632 B of  FIG. 6H ; user interface  732 A of  FIG. 6I ; user interface  632 B of  FIG. 6I ; a notification; a prompt; a message) indicating that the third application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the third user interface element from the first user interface template (e.g., the third alert is displayed after the computer system has displayed and is no longer displaying the second alert). Displaying the alert, second alert, and third alert sequentially during the configuration/setup process enables the user to quickly and easily recognize a missing application for each respective stage, and therefore make an informed decision on whether or not to download the missing application. Providing improved control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the representation (e.g.,  634 A;  634 B) of the user interface specifies ( 706 ) elements for the first application that is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system and a second application that is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system (e.g.,  600 B). In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system using the first user interface template includes the computer system (e.g.,  600 A;  600 B) displaying ( 740 ), via the display generation component (e.g.,  602 A;  602 B), a user interface for the first user interface element that includes a representation (e.g.,  634 A;  634 B) of the first user interface template and one or more selectable user interface objects associated with the first user interface element, where the representation of the first user interface template includes the first user interface element corresponding to the first application (e.g., the representation of the first user interface template optionally includes a second user interface element (different from the first user interface element) corresponding to the second application). Displaying the user interface for the first user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the first user interface element during the configuration/setup process enables a user to quickly and easily recognize which, if any, applications may need to be installed on the computer system, and also recognize updates to the user interface as the user is making decisions for each of the user interface objects for which user action is needed. Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the representation (e.g.,  634 A;  634 B) of the first user interface template is displayed in a setup user interface (e.g.,  623 A;  623 B) for configuring different user interface templates to be used to create different user interfaces for use (e.g., for use as a watch face user interface) on the respective computer system (e.g.,  600 B). 
     In some embodiments, while displaying the representation (e.g.,  634 A;  634 B) of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the first application available (e.g., install the first application), the computer system (e.g.,  600 A;  600 B) receives ( 742 ) an input corresponding to a request to display a user interface for a second user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the second user interface element. 
     In some embodiments, in response to receiving ( 744 ) the request to display a user interface for the second user interface element, in accordance with a determination that (e.g., in accordance with receiving a request (e.g., detecting a user input)) the first application was selected for installation (e.g., based on the one or more inputs corresponding to the decision as to whether to install the first application) on the respective computer system (e.g.,  600 B), the computer system displaying ( 746 ) the user interface for the second user interface element includes displaying a representation of the first user interface element (e.g., as shown by watch user interface preview  634 A in  FIG. 6Q  and watch user interface preview  634 B in  FIG. 6Q ); and in accordance with a determination that (e.g., in accordance with receiving a request (e.g., detecting a user input); in accordance with a predetermined time period having passed) the first application was not selected for installation (e.g., based on the one or more inputs corresponding to the decision as to whether to install the first application) on the respective computer system, the computer system displaying ( 748 ) the user interface for the second user interface element includes displaying the representation of the first user interface template without displaying the first user interface element (e.g., as shown by watch user interface preview  634 A and watch user interface preview  634 B in  FIG. 6N ). Displaying the representation of the first user interface element in accordance with a determination that the first application was selected for installation and displaying the representation of the first user interface template without displaying the first user interface element in accordance with a determination that the first application was not selected for installation provides improved visual feedback about user action taken during the configuration/setup process, which in turn enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the representation (e.g.,  634 A;  634 B) of the user interface specifies elements for a third application that is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system (e.g., the representation of the first user interface template includes a third user interface element (different from the first user interface element and from the second user interface element) corresponding to the third application). In some embodiments, the process for creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes, while displaying the representation of the first user interface template, and after receiving one or more inputs corresponding to a decision as to whether to make the second application available (e.g., install the first application), the computer system (e.g.,  600 A;  600 B) receiving ( 750 ) an input corresponding to a request to display a user interface for a third user interface element that includes a representation of the first user interface template and one or more selectable user interface objects associated with the third user interface element. 
     In some embodiments, in response to receiving ( 752 ) the request to display a user interface for the third user interface element, in accordance with a determination that (e.g., in accordance with receiving a request (e.g., detecting a user input)) the second application was selected for installation (e.g., based on the one or more inputs corresponding to the decision as to whether to install the first application) on the respective computer system (e.g., to be downloaded and installed on the respective computer system; to be made available on the respective computer system), the computer system displaying ( 754 ) the user interface for the third user interface element includes displaying a representation of the second user interface element (e.g., no longer highlighting; dimming; blurring) (e.g., as shown by watch user interface preview  634 A in  FIG. 6Q  and watch user interface preview  634 B in  FIG. 6Q ); and in accordance with a determination that (e.g., in accordance with receiving a request (e.g., detecting a user input); in accordance with a predetermined time period having passed) the second application was not selected for installation (e.g., based on the one or more inputs corresponding to the decision as to whether to install the first application) on the respective computer system (e.g., to not be downloaded and/or not be installed on the respective computer system), the computer system displaying ( 756 ) the user interface for the third user interface element includes displaying the representation of the first user interface template without displaying the second user interface element (e.g., as shown by watch user interface preview  634 A and watch user interface preview  634 B in  FIG. 6N ). Displaying the representation of the second user interface element in accordance with a determination that the second application was selected for installation and displaying the representation of the first user interface template without displaying the second user interface element in accordance with a determination that the second application was not selected for installation provides improved visual feedback about user action taken during the configuration/setup process, which in turn enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes the computer system (e.g.,  600 A;  600 B) displaying, via the display generation component (e.g.,  602 A;  602 B), the representation (e.g.,  634 A;  634 B) of the first user interface template. In some embodiments, the representation of the first user interface template is displayed in a setup user interface (e.g.,  632 A;  632 B) for configuring different user interface templates to be used to create different user interfaces for use (e.g., for use as a watch face user interface) on the respective computer system. In some embodiments, while displaying the representation of the first user interface template, in accordance with the determination that the first application is not available on the respective computer system, the computer system displays, in the representation of the first user interface template, the first user interface element with a first visual characteristic (e.g., highlighted, brightened, and/or otherwise visually indicated such that the first user interface element is more visible/recognizable within the representation of the first user interface template) (e.g., as shown via complication previews  636 A and  636 B in  FIG. 6M  and complication previews  644 A and  644 B in  FIG. 6N ); and in accordance with the determination that the first application is available on the respective computer system, the computer system displays, in the representation of the first user interface template, the first user interface element with a second visual characteristic (e.g., not highlighted; dimmed; blurred) different from the first visual characteristic (e.g., as shown via complication previews in  FIG. 6L  other than complication previews  636 A,  644 A and  636 B,  644 B). Displaying the first user interface element with the first visual characteristic in accordance with the determination that the first application is not available on the respective computer system enables a user to quickly and easily recognize that the first application is not available (e.g., is not installed). Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, if the representation (e.g.,  634 A;  634 B) of the first user interface template includes a plurality of respective user interface elements (e.g.,  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B,  650 B) corresponding to respective applications that are unavailable on the respective computer system (e.g.,  600 B), the computer system (e.g.,  600 A;  600 B) displays, in the representation of the first user interface template, the plurality of respective user interface elements with the first visual characteristic (e.g., highlighted; brightened). 
     In some embodiments, receiving the representation (e.g.,  634 A;  634 B) of the first user interface template comprises receiving (e.g., as an attachment; as a download link) the representation of the first user interface template via a messaging application (e.g.,  624 A;  624 B; a text messaging application; a chat application; an electronic mail application). Receiving the representation of the first user interface template via the messaging application enables a user to conveniently receive the first user interface template from a different user. Providing convenient control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, receiving the representation (e.g.,  634 A;  634 B) of the first user interface template includes the computer system (e.g.,  600 A;  600 B) displaying, via the display generation component (e.g.,  602 A;  602 B), a messaging user interface (e.g.,  624 A;  624 B) showing a messaging conversation (e.g.,  626 A;  626 B) with one or more other participants of a messaging application (e.g., a text messaging application; a chat application; an email application). In some embodiments, the computer system (e.g.,  600 A;  600 B) displays, in the messaging user interface, a first message (e.g.,  628 A;  628 B) corresponding to the representation of the first user interface template, where the first message includes an image (e.g., a preview image) showing the representation of the first user interface template. Displaying the first message where the message includes the image showing the representation of the first user interface template enables a user to quickly and easily view the first user interface template without needing to first download/store the first user interface template. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, receiving the request (e.g.,  609 A;  609 B;  6105 A;  6105 B;  621 A;  621 B) to use the first user interface template for the respective computer system (e.g.,  600 B) includes detecting (e.g., via one or more input devices of the computer system, such as a touch-sensitive surface that is in communication with the device generation component) user selection of the image showing the representation (e.g.,  628 A;  628 B) of the first user interface template in the first message. In some embodiments, receiving the request to use the first user interface template for the respective computer system includes detecting (e.g., via one or more input devices of the computer system, such as a touch-sensitive surface that is in communication with the device generation component) user selection of a link corresponding to the representation of the first user interface template. 
     In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes, in accordance with the determination that the first application is not available on (e.g., not downloaded on; not installed on; not accessible on) the respective computer system (e.g., as shown in  632 B in  FIG. 6M and 632B  in  FIG. 6N ) (e.g., where the respective computer system is the same system as the computer system) (e.g., in response to receiving the request to use the first user interface template for the respective computer system), the computer system (e.g.,  600 A;  600 B) initiating (e.g., via a short-range communication radio that is in communication with the computer system) a communication to a second computer system (e.g.,  600 B;  600 A; a second electronic device (e.g., a smartphone)) that is coupled to (e.g., paired with) the computer system (e.g., an electronic device), where the communication includes instructions to continue the process for creating the user interface for the respective computer system using the first user interface template on the second computer system (instead of on the computer system). Enabling the process for creating the user interface to continue on the second computer system enables a user to conveniently complete the process on a different computer system if, for example, the process cannot be completed on the current computer system (e.g., because the current computer system does not have access to the Internet to download applications). Providing convenient control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the respective computer system (e.g.,  600 B) is the same system as the computer system (e.g., the respective computer system is the same device as the electronic device). In some embodiments, the computer system (e.g.,  600 B) is a wearable electronic device (e.g., a smartwatch). In some embodiments, the computer system does not have a direct connection with or direct access to the Internet. In some embodiments, the computer system is paired with (e.g., via a Bluetooth connection) a second computer system (e.g.,  600 A; a smartphone). 
     In some embodiments, the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template includes, in accordance with the determination that the first application is not available on (e.g., not downloaded on; not installed on; not accessible on) the respective computer system (e.g., as shown in  632 B in  FIG. 6M and 632B  in  FIG. 6N ) (e.g., where the respective computer system is the same system as the computer system) (e.g., in response to receiving the request to use the first user interface template for the respective computer system), the computer system (e.g.,  600 A;  600 B) continuing the process for creating the user interface for the respective computer system using the first user interface template without installing (e.g., without downloading and installing) the first application on the respective computer system (e.g., as shown via  632 A and  632 B in  FIG. 6M ), where the first user interface template no longer includes the first user interface element corresponding to the first application (e.g., as shown in  632 A and  632 B in  FIG. 6M ). Enabling the process creating the user interface for the respective computer system using the first user interface template to continue without installing the first application provides user control over which applications should be installed and used for the user interface, and enables completion of the process even if not all unavailable (e.g., not installed) applications are installed. Providing improved control options enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, if the process for creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template is continued without installing the first application on the respective computer system, the first user interface, once used on the respective computer system (e.g., as a watch face user interface), does not include the first user interface element (e.g., where the user interface elements can include one or more of  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and/or  650 B) corresponding to the first application. In some embodiments, if the process for creating the user interface for the respective computer system using the first user interface template is continued without installing the first application on the respective computer system but with installing a second application on the respective computer system, where the second application corresponds to a second user interface element (e.g., where the user interface elements can include one or more of  636 A,  638 A,  640 A,  642 A,  644 A,  646 A,  648 A,  650 A;  636 B,  638 B,  640 B,  642 B,  644 B,  646 B,  648 B, and/or  650 B) of the first user interface template, then the first user interface, once used on the respective computer system (e.g., as a watch face user interface), does not include the first user interface element corresponding to the first application but includes the second user interface element corresponding to the second application. Not including the first user interface element if the process for creating the user interface for the respective computer system using the first user interface template is continued without installing the first application on the respective computer system prevents the user interface from being created with a feature that may not properly function (e.g., because the corresponding first application is not installed), thereby enhancing the operability of the computer system and making the user-system interface more efficient. 
     In some embodiments, in accordance with the determination that the first application is not available on (e.g., not downloaded on; not installed on; not accessible on) the respective computer system (e.g.,  600 B) (e.g., as shown in  FIG. 6N ), the computer system (e.g.,  600 A;  600 B) continues the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system using the first user interface template, where continuing the process includes installing (e.g., by downloading and/or purchasing the respective application (e.g., from an app store)) the first application on the respective computer system (e.g., as shown in  FIGS. 6N-6P ). In some embodiments, the first user interface template maintains the first user interface element corresponding to the first application. 
     In some embodiments, in response to completing the process (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) for creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template, the computer system (e.g.,  600 A;  600 B) adds (e.g., initiating a process for adding) the user interface created using the first user interface template to a user interface library (e.g., a watch face library; a library of available watch faces that can be set as the current watch face for the respective computer system) for the respective computer system (e.g., a smartwatch). In some embodiments, in response to completing the process for creating the user interface and/or upon determining that the process for creating the user interface has been completed, the respective computer system automatically sets the user interface created using the first user interface template as a currently selected user interface (e.g., as shown by  656 B in  FIG. 6G, 6114B  in  FIG. 6K, and 699B  in  FIG. 6S ) from the user interface library for the respective computer system (e.g., as the current watch face of the computer system). In some embodiments, in response to completing the process for creating the user interface for the respective computer system using the first user interface template, the computer system also displays (or causes display of), via the display generation component, an option to install one or more applications on the respective computer system corresponding to applications that were not available on the respective computer system and were, during the process for creating the user interface for the respective computer system using the first user interface template, not selected to be made available on the respective computer system. Providing the option to install one or more applications on the respective computer system corresponding to applications that are still not available on the respective computer system in response to completing the process for creating the user interface enables a user to quickly and easily download the unavailable applications even after the process has been completed. Providing improved control options enhances the operability of the computer system and makes the user-system interface more efficient 
     In some embodiments, the representation (e.g.,  600 A;  600 B) of the user interface specifies elements (e.g.,  636 A;  636 B;  644 A;  644 B) for the first application that is not available on (e.g., not installed on; not downloaded onto; not locally accessible on) the respective computer system (e.g.,  600 B). In some embodiments, the process for creating the user interface for the respective computer system includes, in accordance with a determination that the first application is to be made available (e.g., installed) on (e.g., to be downloaded and installed on) the respective computer system (e.g., based on receiving a user indication or detecting one or more user inputs to install the first application on the respective computer system), the computer system initiating a process for making the first application available (e.g., installing) on the respective computer system, where, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system with the first user interface element (e.g., the first watch complication) corresponding to the first application; and in accordance with a determination that the first application is not to be made available on (e.g., not to be downloaded and/or installed on) the respective computer system (e.g., based on receiving a user indication or detecting one or more user inputs to not install the first application on the respective computer system), the computer system forgoing initiating the process for making the first application available (e.g., installing) on the respective computer system, where, after completing the process for creating the user interface for the respective computer system using the first user interface template, the user interface created using the first user interface template is displayed on the respective computer system without the first user interface element. 
     In some embodiments, the computer system (e.g.,  600 A;  600 B) displays (or causes display of) the representation (e.g.,  634 A;  634 B) of the first user interface template during the process for creating the user interface for the respective computer system using the first user interface template. In some embodiments, the first user interface template includes the first user interface element (e.g., the first watch complication) corresponding to the first application at a first location within the first user interface template. In some embodiments, the first user interface template includes one or more additional user interface elements (e.g., corresponding to different watch complication previews). In some embodiments, the one or more additional user interface elements are displayed at particular defined locations within the first user interface template. 
     In some embodiments, after creating the user interface using the first user interface template, the respective computer system (e.g.,  600 B) displays the user interface (e.g.,  697 ;  679 ; as a watch face) created using the first user interface template, where the user interface includes the first user interface element (e.g., the first watch complication) corresponding to the first application at the first location (e.g., at the same location within the user interface that the first user interface element was displayed within the first user interface template). In some embodiments, other user interface elements are also displayed at corresponding locations within the user interface displayed on the respective computer system. 
     In some embodiments, if the first application was not available on the respective computer system (e.g.,  600 B) and the first application was not subsequently installed on the respective computer system, the respective computer system displays the user interface (e.g.,  697 ;  679 ; as a watch face) created using the first user interface template, where the user interface does not include the first user interface element (e.g., the first watch complication) corresponding to the first user interface element and the first application at the first location (e.g., the same location within the user interface that the first user interface element was located in the first user interface template). In some embodiments, the other user interface elements (e.g., if their corresponding applications had been or were made available on the respective computer system) are still displayed at their corresponding locations within the user interface displayed on the respective computer system. 
     In some embodiments, after completing the process for (e.g., as shown in  FIGS. 6F-6G, 6I-6J , and/or  6 L- 6 R) creating the user interface for the respective computer system (e.g.,  600 B) using the first user interface template (e.g., and thus the user interface created using the first user interface template is ready to be displayed or used as a watch face), the computer system (e.g.,  600 A;  600 B) causes display of (e.g., on the respective computer system; if the computer system is the same system as the respective computer system, on the computer system) the user interface created using the first user interface template (e.g., as shown by  656 A and  656 B in  FIG. 6G, 6106A and 6114B  in  FIG. 6K, and 699A and 699B  in  FIG. 6S ), where the first user interface element displayed in the user interface includes information (e.g., location information; date/time information; weather information; calendar information) obtained from the first application (e.g., related to a feature of the first application). In some embodiments, prior to causing display of the user interface created using the first user interface template, the computer system (e.g.,  600 ) completes the process for creating the user interface for the respective computer system using the first user interface template. Displaying information obtained from the first application in the first user interface element displayed in the user interface provides a user with quick and easy access to the information without requiring an input to launch the application to obtain the information. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the information (e.g., location information; time/date information) included in the first user interface element displayed in the user interface (e.g.,  697 ;  679 ) corresponds to location information (e.g., and the first application corresponds to a map application or a GPS-based application), and the information is determined (e.g., selected) based on a location setting (e.g., a pre-set location configuration or setting) from the first user interface template, where the location setting is configured to be a current location of the respective computer system (e.g.,  600 B). Configuring (e.g., automatically) the location setting to be a current location of the respective computer system enables a user to not have to provide additional inputs to manually set the location setting to the current location. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the first user interface template, when received, was configured/setup for location information to be based on a current location of its source computer system or source device; in some embodiments in which this is the case, in the user interface created using the first user interface template, the information is automatically set to include location information that is based on the current location of the respective computer system (e.g.,  600 B). 
     In some embodiments, the information (e.g., location information; time/date information) included in the first user interface element displayed in the user interface (e.g.,  697 ;  679 ) corresponds to location information (e.g., and the first application corresponds to a map application or a GPS-based application), and the information is determined (e.g., selected) based on a location setting (e.g., a pre-set location configuration or setting) from the first user interface template, where the location setting is configured to be a designated location different from a current location of the respective computer system (e.g.,  600 B). In some embodiments, the first user interface template, when received, was configured/setup for location information to be based on a location different from the current location of its source computer system or source device; in some embodiments in which this is the case, in the user interface created using the first user interface template, the information is automatically set to include location information that corresponds to that same different location from the source computer system or source device. Automatically (e.g., without user input) setting the information to include location information that corresponds to that same different location from the source computer system or source device results in the user interface maintaining a setting from the first user interface template, as may have been the user&#39;s preference, thereby enhancing the operability of the computer system and making the user-system interface more efficient. 
     In some embodiments, the information included in the first user interface element displayed in the user interface (e.g.,  697 ;  679 ) corresponds to calendar information (e.g., schedule information; meeting information), and the information is determined based on application information from the first application accessed via the respective computer system (e.g.,  600 B), where the first application corresponds to a calendar application. In some embodiments, in the user interface created using the first user interface template, the information is automatically set to include schedule information that is based on a calendar application that is accessible on or by the respective computer system. Automatically setting the information to include schedule information that is based on the calendar application that is accessible on or by the respective computer system enables a user to not have to provide additional inputs to manually set the calendar settings for the user interface. Reducing the number of inputs needed to perform an operation enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. 
     In some embodiments, the first user interface template, when received, is configured to (e.g., set to) include (e.g., automatically include) a visual characteristic (e.g., a color, such as a background color and/or color scheme) that is selected based on context information accessible by (e.g., determinable by; detectable by) the respective computer system (e.g.,  600 B). In some embodiments, the visual characteristic includes a background color or background color scheme for the user interface, and the context information includes a color or color scheme of a housing of the computer system (e.g., an electronic device) or of a device accessory (e.g., case; cover) detected by (e.g., using one or more image sensors) the respective computer system. 
     In some embodiments, the respective computer system (e.g.,  600 B; a respective device) is a particular type or model within a device type category (e.g., a particular type or model of smartwatch). In some embodiments, in accordance with the determination that the first application is not available on the respective computer system, the computer system (e.g.,  600 A;  600 B) detects (e.g., via one or more input devices that are in communication with the computer system) a request (e.g., user selection of the alert or an affordance in the alert indicating that the first application needs to be installed on the respective computer system in order for the first user interface template to be used to create a user interface for the respective computer system that includes the first user interface element from the first user interface template) to install (e.g., download and install) the first application on the respective computer system. In some embodiments, in response to detecting the request to install the first application on the respective computer system, in accordance with a determination that the first application cannot be installed on the respective computer system (e.g., because the first application cannot be downloaded on the respective computer system; because the first application is not compatible with the respective computer system), the computer system displays, via the display generation component, an indication (e.g.,  635 C;  635 D;  635 E; a notification; an error message) that the first application cannot be installed on the respective computer system. Displaying the indication that the first application cannot be installed on the respective computer system enables a user to quickly and easily recognize that the operation cannot be performed on the computer system. Providing improved visual feedback enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently. In some embodiments, in accordance with a determination that the first application can be installed on the respective computer system (e.g.,  600 B), the computer system (e.g.,  600 A;  600 B) (if the computer system is the respective computer system) automatically downloads and installs the first application or causes (if the computer system is different from the respective computer system) the respective computer system to download and install the first application. 
     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 invention 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 drawings, 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 claims.

Metadata:
Filing Date: 20201023
Publication Date: 20220628
Grant Date: 20220628
Priority Date: 20200511
Inventors: GUZMAN, Aurelio
CHAO, EDWARD
CHEN, KEVIN WILL
WILSON, CHRISTOPHER
DYE, ALAN C.
LYNCH, KEVIN
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F9/452", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F8/61", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/542", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/452", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F8/38", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L67/10", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F8/36", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/542", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/452", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04L67/10", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 78412623