System and method for interacting with multiple display devices

Abstract

To allow a user to more easily connect and simultaneously operate multiple computer displays.SOLUTION: A method is performed on a first computer system having a first display generation component in communication with a second computer system having a second display generation component. The method includes a step of, in response to an input, moving a representation of content across a first display region provided by the first display generation component to a second display region provided by the second display generation component when the display generation components are in communication in a first mode or a second mode. The method includes steps of: moving an application window across the first display region to the second display region provided when the display generation components are in communication in the first mode; and preventing the movement across the first display region to the second display region when the display generation components are in communication in the second mode.SELECTED DRAWING: None

Description

[Technical Field]

[0001] (Related Applications) This application is a continuation of U.S. Patent Application No. 17 / 831,377, filed June 2, 2022, which claims priority to U.S. Provisional Patent Application No. 63 / 197,248, filed June 4, 2021, and U.S. Provisional Patent Application No. 63 / 252,114, filed October 4, 2021. (Technical field)

[0002] Disclosed embodiments relate to interacting with two or more electronic devices (e.g., a first electronic device and a second electronic device) using one or more input devices associated with only one of the two or more electronic devices, for example, the two or more electronic devices being operated in different modes, including a shared input mode (e.g., a first user interface generated by an operating system of the first electronic device and a second user interface generated by an operating system of the second electronic device are controlled with the shared input device) and a companion display mode (e.g., a first user interface generated by an operating system of the first electronic device spans both the display of the first electronic device and the display of the second electronic device). [Background technology]

[0003] Users of computing devices often use multiple computer displays to visually present content simultaneously. Using multiple connected displays often increases user efficiency by allowing users to open more user interfaces and spread those user interfaces across a larger screen area. However, connecting multiple computer displays together typically requires specialized knowledge of the computer's operating system or other display software, requires reconfiguration when a computing device or display is moved, and is otherwise a difficult, cumbersome, and wasteful process. Moreover, some computing devices or displays are not even compatible with each other and cannot be connected together to simultaneously display content. Thus, there is a need for systems and methods that more easily allow users to connect and simultaneously operate multiple computer displays.

[0004] Furthermore, human-machine interfaces for devices that operate with multiple displays are typically non-intuitive and fail to provide visual feedback when performing different functions. Therefore, there is also a need for more intuitive human-machine interfaces, especially those that allow for easier and more efficient use of multiple displays. Summary of the Invention

[0005] The embodiments described herein address the above-mentioned shortcomings by providing display devices and methods that enable users to intuitively and efficiently connect and operate the displays of multiple display devices (e.g., desktop electronic devices, laptop electronic devices, or tablet electronic devices) that are in communication with each other to share content among the multiple display devices. Such devices and methods require little or no input to establish communication between different devices, switch between different display modes (e.g., shared input mode and companion display mode), and share content among the different displays. Such display devices and methods also provide feedback to assist users in operating different display devices in different display modes. Such display devices and methods also provide an improved human-machine interface, for example, by highlighting information to make it more perceptible on a touch-sensitive display and by requiring less interaction from the user to achieve the user's desired results. For these reasons and those described below, the devices and methods described herein reduce power usage and improve battery life of electronic devices.

[0006] According to some embodiments, a method is implemented in a first computer system having a first display generating component. The first computer system is in communication with a first input device and a second computer system having a second display generating component. The method includes displaying a first user interface object in a first display area via the first display generating component. While displaying the first user interface object in the first display area provided by the first display generating component, detecting a first input including a first movement via the first input device. The input corresponds to a request to drag the first user interface object across the first display area to a second display area provided by the second display generating component. In response to detecting the first movement, and in accordance with a determination that the first user interface object is a representation of content, moving the first user interface object from the first display area to the second display area when the second display generating component is in communication with the first computer system in a first mode (e.g., extended display mode) or a second mode (e.g., shared input mode). In accordance with a determination that the first input is detected while the first user interface object is an application window and the second display generating component is communicating with the first computer system in a first mode (e.g., an extended display mode), the first user interface object is moved from the first display area to the second display area. In accordance with a determination that the first input is detected while the first user interface object is an application window and the second display generating component is communicating with the first computer system in a second mode (e.g., a shared input mode), the first user interface object is prevented from moving into the second display area provided by the second display generating component.In some embodiments, in a shared input mode, a first computer system displays a user interface controlled by the first computer system, and a second computer system displays a user interface controlled by the second computer system, and the first computer and the second computer system share an input device. In some embodiments, in an extended display mode, the first display generating component and the second display generating component both display a user interface generated by the first computer system, and the first computer and the second computer system receive input via the shared input device.

[0007] According to some embodiments, a method is implemented in a first computer system having a first display generation component. The first computer system is in communication with a first input device. The method includes detecting a first event satisfying first criteria while displaying a first user interface within a first display area provided by the first display generation component. In response to detecting the first event satisfying the first criteria, displaying a respective visual indication of a respective representative spatial position of a user interface generated by a second display generation component of a second computer system. Displaying the respective visual indication includes displaying the first visual indication in a first portion of a user interface generated by the first display generation component in accordance with a determination that the first computer system shares the first input device with a second display generation component of the second computer system and that the user interface generated by the second display generation component has a first representative spatial position that can be reached by dragging a user interface object through the first portion of the user interface generated by the first display generation component. The first computer system shares a first input device with a second computer system in communication with the second display generating component, and displays a second visual indication in a second portion of the user interface generated by the first display generating component according to a determination that the user interface generated by the second display generating component has a second representative spatial position that can be reached by dragging the user interface object through the second portion of the user interface generated by the first display generating component. While the first computer system shares the first input device with the second computer system, detects a first input via the first input device corresponding to a request to drag the first user interface object across the first display area.In response to detecting the first input, moving a first user interface object across a user interface generated by the first display generating component, and in accordance with a determination that the first input included movement across a portion of the first user interface in which the distinct visual indication was displayed when a first event satisfying a first criterion was detected while the user interface generated by the second display generating component had a distinct representative spatial position represented by the distinct visual indication, moving the first user interface object across the user interface generated by the second display generating component in accordance with the first movement detected via the first input device.

[0008] According to some embodiments, a method is implemented in a first computer system having a first display generating component, the first computer system communicating with a first input device and a second computer system having a second display generating component. The method includes displaying, via the first display generating component, a configuration user interface in a first display area, the configuration user interface including a first representation of a representative spatial position of a user interface generated by the first display generating component and a second representation of a representative spatial position of a user interface generated by the second display generating component. In accordance with determining that the first computer system and the second computer system are connected in a first mode (e.g., a shared input mode), the method includes displaying, using a first visual characteristic, the first representation of the representative spatial position of the user interface generated by the first display generating component and the second representation of the representative spatial position of the user interface generated by the second display generating component. In accordance with determining that the first computer system and the second computer system are connected in a second mode, a first representation of a representative spatial position of the user interface generated by the first display generation component and a second representation of a representative spatial position of the user interface generated by the second display generation component are displayed using second visual characteristics different from the first visual characteristics.

[0009] According to some embodiments, a method is implemented in a first computer system including a first display generating component and an input device. The method includes displaying, via the first display generating component, a visual indication of the location of a portal between a first display area associated with the first display generating component and a second display area associated with a second display generating component. The portal is a portion of the first display area through which a user interface object can be moved between the first display area and the second display area. While displaying the visual indication of the portal, the method includes detecting a first input corresponding to a first movement within the first display area. In response to detecting the first input, modifying a size and / or location of the visual indication of the portal between the first display area associated with the first display generating component and the second display area associated with the second display generating component to indicate the change to the size and / or location of the portal between the first display area associated with the first display generating component and the second display area associated with the second display generating component.

[0010] According to some embodiments, a method is implemented in a first computer system having a display generation component and one or more input devices. The method includes simultaneously displaying, in a display area provided by the display generation component, a dock including a plurality of icons corresponding to a plurality of applications, and a first region and a second region displayed in a split-screen configuration, where the first region displays a first user interface of the first application and the second region displays a placeholder interface indicating that the second region is available for placement of a user interface of an application other than the first application. While simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface in the second region, the method further includes detecting a first user input corresponding to a selection of an icon in the dock corresponding to a second application, and displaying a second user interface of the second application in the second region in response to detecting the first user input, where the second user interface of the second application is displayed together with the first user interface of the first application in the split-screen configuration.

[0011] According to some embodiments, a computer system includes a first display generating component, one or more processors, a memory, and one or more programs, the one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods described above. According to some embodiments, a computer-readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by a first computer system having a first display generating component, cause the computer system to perform any of the methods described above.

[0012] The systems and methods described herein improve how devices with multiple displays can be operated efficiently simultaneously. [Brief explanation of the drawings]

[0013] For a better understanding of the various described embodiments, reference should be made to the following Detailed Description of the Invention in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0014] [Figure 1A] 1 illustrates an exemplary system in which a first electronic device operates in communication with a second electronic device and / or a third electronic device (e.g., a combination of two or three of a desktop computer, a laptop computer, and a tablet computer), according to some embodiments. [Figure 1B] 1 illustrates an exemplary system in which a first electronic device operates in communication with a second electronic device and / or a third electronic device (e.g., a combination of two or three of a desktop computer, a laptop computer, and a tablet computer), according to some embodiments.

[0015] [Figure 2] FIG. 1 is a block diagram of an electronic device (e.g., a device running a mobile operating system) according to some embodiments.

[0016] [Figure 3A] FIG. 1 is a block diagram of an electronic device (e.g., a device running a desktop or laptop operating system) according to some embodiments.

[0017] [Figure 3B] FIG. 3B is a block diagram of components for event processing of FIG. 3A according to some embodiments.

[0018] [Figure 4A] 1A-1C illustrate exemplary user interfaces for a menu of applications on a portable multifunction device according to some embodiments.

[0019] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display, according to some embodiments.

[0020] [Figure 5A] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5B] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5C] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5D] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5E] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5F]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5G] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5H] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5I] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5J] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5K] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5L]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5M] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5N] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5O] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5P] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5Q] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5R]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5S] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 5T] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6A] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6B] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6C] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6D]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6E] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6F] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6G] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6H] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6I] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6J]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6K] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6L] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6M] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6N] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6O] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6P]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6Q] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6R] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6S] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6T] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6U] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6V]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6W] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 6X] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7A] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7B] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7C] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7D]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7E] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7F] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7G] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7H] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7I] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7J]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7K] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7L] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7M] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7N] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7O] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7P]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7Q] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7R] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7S] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7T] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7U] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7V]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7W] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7X] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7Y] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 7Z] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8A] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8B]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8C] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8D] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8E] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8F] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8G] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8H]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8I] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8J] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8K] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8L] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8M] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8N]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8O] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8P] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8Q] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8R] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8S] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8T]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8U] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8V] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8W] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8X] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8Y] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8Z]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AA] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AB] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AC] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AD] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AE] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AF]9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AG] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AH] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000. [Figure 8AI] 9A-9C are schematic diagrams of a display device used to illustrate an exemplary user interface for interacting with multiple display devices simultaneously, with additional details regarding these diagrams also provided below with reference to the descriptions of methods 9000, 10000, 11000, and 12000.

[0021] [Figure 9A] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 9B] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 9C] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 9D] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10A]1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10B] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10C] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10D] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10E] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 10F] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 11A] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 11B] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 11C] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 11D] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 11E] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12A] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12B]1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12C] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12D] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12E] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments. [Figure 12F] 1 is a flowchart of a method for initiating and interacting with a companion display mode, according to some embodiments.

[0022] [Figure 13A] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13B] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13C] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13D]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13E] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13F] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13G] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13H] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13I] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13J]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13K] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13L] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13M] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13N] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13O] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13P]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13Q] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13R] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13S] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13T] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13U] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13V]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13W] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13X] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13Y] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13Z] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AA] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AB]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AC] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AD] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AE] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AF] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AG] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AH]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AI] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AJ] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AK] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AL] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AM] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AN]14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000. [Figure 13AO] 14A-14C are schematic diagrams of a display device used to show an exemplary user interface for simultaneously displaying and interacting with multiple applications, according to some embodiments. Further details regarding these diagrams are also provided below with reference to the description of method 14000.

[0023] [Figure 14A] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14B] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14C] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14D] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14E] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14F] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. [Figure 14G] 1 is a flowchart of a method for displaying and interacting with multiple user interfaces on a display device, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0024]

[0023] Figures 1A-4B illustrate exemplary devices on which the methods described herein may be implemented and practiced. Figures 5A-8AI are schematic diagrams of displays used to illustrate exemplary user interfaces for simultaneously initiating and interacting with multiple display devices in a shared input mode or companion display mode (e.g., an extended display mode or a mirrored display mode); additional discussion regarding these user interface diagrams is also provided with reference to methods 9000, 10000, 11000, and 12000 in Figures 9A-12F. Figures 13A-13AO are schematic diagrams of display devices used to illustrate exemplary user interfaces for simultaneously displaying and interacting with multiple applications; additional discussion regarding these user interface diagrams is also provided with reference to method 14000 in Figures 14A-14G. Exemplary Devices and Systems

[0025] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0026] In this specification, terms such as "first," "second," etc. are used to describe various elements in some examples, but it will be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first contact can be referred to as a second contact, and similarly, a second contact can be referred to as a first contact, without departing from the scope of the various embodiments being described. Although a first contact and a second contact are both contacts, they are not the same contact.

[0027] The terminology used in the description of the various embodiments set forth 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 embodiments described and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include 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," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0028] As used herein, the term "if" is optionally interpreted to mean "when," "upon," "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" are optionally interpreted 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.

[0029] 1A illustrates an exemplary system in which a first display device (e.g., the illustrated laptop display device 300) operates in conjunction with a second display device (e.g., the illustrated tablet display device or desktop computer display device 100). FIG. 1B illustrates an exemplary system in which a first display device (e.g., the illustrated desktop display device 300) operates in conjunction with a second display device (e.g., the illustrated tablet display device 100) and a third display device (e.g., the illustrated laptop device 200). Devices 100, 200, and 300 are all display devices that include individual display devices 101, 201, and 301 (also referred to as display generating components). In some embodiments, the displays are touch-sensitive displays (e.g., display 101 of tablet device 100 is a touch-sensitive display or touchscreen). The first display device includes or communicates with one or more input devices (e.g., mouse input device 202, keyboard input devices 203 and 305, and touchpad 309 shown in FIG. 1B). In some embodiments, the input devices are implemented on the device (e.g., touchpad 309 and keyboard 305 are part of laptop device 300). In some embodiments, the input devices are in wireless or wired communication with the device (e.g., mouse 202 and keyboard 203 communicate wirelessly with desktop device 200 of FIG. 1B). In some embodiments, the first display device is in communication with the second and / or third display device in a shared input device mode. In the shared input device mode, the first display device shares one or more input devices (e.g., the illustrated mouse input device and / or keyboard input device) with the second and / or third display device such that the one or more input devices can be used to operate the second or third display device.In some embodiments, the first electronic device detects input through one or more input devices with which it is in wireless or wired communication and provides information about the detected input to the second computer system and / or the third computer system. In some embodiments, the first computer system and the second and / or third computer systems all communicate with and detect input through the same one or more input devices. For example, the detected input is processed by the currently active computer system (e.g., the input is directed to the keyboard, mouse, or touchpad of the currently active computer system). In some embodiments, a computer system is currently active if it displays a cursor (e.g., in a shared input mode, different computers have a common cursor). Alternatively, the first display device may be in communication with the second and / or third display device in a companion display mode. In the companion display mode, a separate display of the second or third display device displays content provided by the first display device. For example, the separate display of the second or third display device operates as a mirror display or an extended display for the display of the first display device. Additional details regarding shared input mode and companion display mode are provided below.

[0030] It should also be noted that various references are made to first, second, and third display devices. In particular instances, the first, second, and third display devices may be selected from any type of display device, i.e., an electronic device having a respective display (e.g., a mobile phone, tablet, laptop, wearable, or desktop display device). Also, references to tablet, laptop, desktop, wearable, and mobile phone display devices are merely illustrative examples. Descriptions herein regarding tablet display devices also apply to other portable display devices running mobile operating systems (e.g., smartphones such as an iPhone from APPLE INC. (Cupertino, CA) running the IOS operating system), and descriptions herein regarding laptop display devices also apply to other desktop-like devices running desktop / laptop operating systems.

[0031] Block diagrams illustrating various components of the first and second electronic devices are shown in Figures 2 and 3A-3B.

[0032] Attention is now directed to embodiments of portable electronic devices with touch-sensitive displays. Figure 2 is a block diagram illustrating portable multifunction device 100 (also referred to interchangeably herein as electronic device 100 or device 100) with touch-sensitive display 112, according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touchscreen" and may also be known or referred to as a touch-sensitive display system. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), controller 120, one or more processing units (CPU's) 122, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 that detect the intensity of a contact 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 that generate a tactile output on device 100 (e.g., generate a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or a touchpad of device 100). These components optionally communicate via one or more communication buses or signal lines 103.

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

[0034] Memory 102 optionally includes high-speed random-access memory (e.g., 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, flash memory devices, or other non-volatile solid-state storage devices. Memory 102 optionally includes one or more storage devices located remotely from processor(s) 122. Access to memory 102 by other components of device 100, such as CPU 122 and peripherals interface 118, is optionally controlled by controller 120.

[0035] A peripheral interface 118 can be used to couple input and output peripherals of the device to the CPU 122 and memory 102. The one or more processors 122 operate or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions and process data for the device 100.

[0036] In some embodiments, peripheral interface 118, processor(s) or CPU(s) 122, and controller 120 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0037] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via 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, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also called the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. Wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM)®, Enhanced Data GSM Environment (EDGE)®, High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), 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®, Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.1la, IEEE 802.1lb, IEEE 802.1lg, and / or IEEE 802.1ln).

[0038] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 further includes a headset jack. The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).

[0039] I / O subsystem 106 connects input / output peripherals of device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes one or more input controllers 160 for display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and other input or control devices. One or more input controllers 160 receive electrical signals from and send electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller 160 is optionally coupled to any or none of a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons optionally include up / down buttons for adjusting the volume of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button.

[0040] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user-interface objects.

[0041] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the area under the user's finger.

[0042] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), LED (light emitting diode), or OLED (organic light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in Apple Inc.'s (Cupertino, California) iPhone®, iPod Touch®, and iPad®.

[0043] Touchscreen 112 optionally has a video resolution greater than 400 dpi. In some embodiments, touchscreen 112 has a video resolution of at least 600 dpi. In other embodiments, touchscreen 112 has a video resolution of at least 1000 dpi. A user optionally contacts touchscreen 112 using any suitable object or digit, such as a stylus or a finger. In some embodiments, the user interface is designed to work primarily with finger-based touches and gestures. In some embodiments, the device translates finger-based input into precise pointer / cursor position or commands that perform the user's desired action.

[0044] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0045] Device 100 also includes a power system 162 that provides power to 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, power failure detection circuitry, power converters or inverters, power status indications (e.g., light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing electrical power in a portable device.

[0046] Device 100 also optionally includes one or more optical sensors 164. FIG. 1 shows an optical sensor coupled to optical sensor controller 158 in I / O subsystem 106. Optical sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Optical sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still or video images. In some embodiments, an optical sensor is located on the back of device 100, opposite touchscreen 112 on the front of the device, to enable the touch-sensitive display as a viewfinder for still and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to optionally obtain an image of the user for video conferencing while the user views other video conference participants on the touch-sensitive display.

[0047] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1 shows contact intensity sensors coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensors 165 optionally include 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 sensors 165 receive 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 juxtaposed with or proximate to the 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 touchscreen 112 located on the front of device 100.

[0048] Device 100 also optionally includes one or more proximity sensors 166. Figure 1 shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is coupled to input controller 160 in I / O subsystem 106. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call).

[0049] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1 shows tactile output generators 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 motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is located on 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 the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display 112, which is located on the front of device 100.

[0050] Device 100 also optionally includes one or more accelerometers 168. FIG. 1 shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. In some embodiments, information is displayed on the touch-sensitive display in portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the location and orientation (e.g., vertical or horizontal) of device 100.

[0051] In some embodiments, software components stored in memory 102 include operating system 126, communications module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, memory 102 stores device / global internal state 157, as shown in FIG. 1 . Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touch-sensitive display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's location and / or attitude (i.e., the device's orientation).

[0052] Operating system 126 (e.g., an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks) includes various software components and / or drivers that control and manage common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

[0053] The communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) are adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors that are the same as, similar to, and / or compatible with the 30-pin connectors used in some embodiments of APPLE Inc.'s IPOD devices. In other embodiments, the external ports are multi-pin (e.g., 8-pin) connectors that are the same as, similar to, and / or compatible with the 8-pin connectors used in APPLE Inc.'s Lightning connectors.

[0054] Contact / motion module 130 optionally detects contact with touchscreen 112 (in cooperation with display controller 156) and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether the contact has ceased (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0055] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., whether the user has selected or “clicked” on an affordance). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touch-sensitive display can be set to any of a wide range of predetermined thresholds without modifying the trackpad or touch-sensitive display hardware. Furthermore, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0056] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same position (or substantially the same position) as the finger down event (e.g., 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 drag events, and in some embodiments, then subsequently detecting a finger up (lift off) event.

[0057] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that modify the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual properties) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including softkeys), digital images, video, animation, etc.

[0058] 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 one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.

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

[0060] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts module 137, email client module 140, IM module 141, browser module 147, and any other application requiring text input).

[0061] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based calling, to the camera 143 as photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0062] Application (“app”) 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Fitness module 142, camera module 143 for still images and / or video; ● Image management module 144; ● Browser module 147, ● Calendar module 148, • A widget module 149 optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, and a user-created widget 149-6; ● Search module 151, • a video and music player module 152, optionally consisting of a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0063] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, website creation applications, disk authoring applications, spreadsheet applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, widget creator modules for creating user created widgets 149-6, and voice duplication.

[0064] In conjunction with touch screen 112, display controller 156, touch module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or contact list (e.g., stored in memory 102 or memory 302 in contacts module 137), including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), email address(es), street address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication via telephone module 138, videoconferencing module 139, email client module 140, or IM module 141, etc.

[0065] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to enter a series of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify an entered telephone number, dial each telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0066] Along 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 module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants according to the user's commands.

[0067] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user commands. In cooperation with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0068] Instant messaging module 141, together with RF circuitry 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions for entering characters corresponding to instant messages, modifying previously entered characters, sending each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and displaying received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0069] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 146, fitness module 142 includes executable instructions for creating workouts (e.g., in terms of time, distance, and / or calorie burn goals), communicating with workout sensors (such as a watch or sports device such as a pedometer), receiving workout sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0070] In cooperation with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions to capture still images or video (including video streams) and store them in memory 102, change the characteristics of the still images or video, or delete the still images or video from memory 102.

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

[0072] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0073] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) according to user instructions.

[0074] In conjunction with RF circuitry 108, touchscreen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application (e.g., weather widget 149-1, stock quotes widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is optionally downloaded and used by a user, or a mini-application (e.g., user-created widget 149-6) created by a user. 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).

[0075] In conjunction with the RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, a widget creator module (not shown) is optionally used by a user to create widgets (e.g., turn user-specified portions of a web page into widgets).

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

[0077] In conjunction with touchscreen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play pre-recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an IPOD® from APPLE Inc.

[0078] In conjunction with the touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0079] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may optionally be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about businesses and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0080] Online video module 155, along with touchscreen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, contains instructions that enable a user to access, browse, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails containing links to particular online videos. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0081] 2, portable multifunction device 100 also includes a companion display module 180 for managing operations associated with companion display mode multitasking on device 100. Companion display module 180 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: an arrangement module 182 for determining the arrangement of displays for a laptop and a tablet device adjacent to each other in association with the companion display mode described herein; a UI generator module 184 for generating user interfaces and sharing data related to those user interfaces across different devices along with companion display and annotation modes; and • A secure criteria module 186 for monitoring whether a device has met a set of secure connection criteria used to determine when a companion display mode is available for use between different devices (e.g., laptop and tablet devices).

[0082] In cooperation with touch screen 112, display controller 156, contact module 130, graphics module 132, and contact intensity sensor(s) 165, PIP module 186 includes executable instructions for determining a reduced size of the video content and for determining an appropriate location on touch screen 112 for displaying the reduced-size video content (e.g., a location that avoids important content in an active application that may be overlaid by the reduced-size video content).

[0083] Each of the above-identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0084] 3A is a block diagram of an electronic device 300, according to some embodiments. In some embodiments, the electronic device 300 is a laptop or desktop computer running a desktop operating system that is different from a mobile operating system.

[0085] The electronic device 300 typically supports a variety of applications, such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a video conferencing application, an email application, an instant messaging application, a picture management application, a digital camera application, a digital video camera application, a web browser application, and / or a media player application.

[0086] Various applications running on electronic device 300 optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed by electronic device 300 are optionally adjusted and / or changed for each application and / or within an application. In this way, the common physical architecture (such as the touch-sensitive surface) of electronic device 300 optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0087] Electronic device 300 includes memory 302 (optionally including one or more computer-readable storage media), a memory controller 322, one or more processing units (CPUs) 320, a peripherals interface 318, RF circuitry 308, audio circuitry 310, a speaker 311, a microphone 313, an input / output (I / O) subsystem 306, other input or control devices 316, and an external port 324. Electronic device 300 optionally includes a display system 312, which may be a touch-sensitive display (sometimes referred to herein as a “touchscreen” or “touchscreen display”). Electronic device 300 optionally includes one or more optical sensors 364. Electronic device 300 optionally includes one or more intensity sensors 365 that detect the intensity of a contact on a touch-sensitive surface, such as a touch-sensitive display or touchpad. Electronic device 300 optionally includes one or more tactile output generators 367 for generating a tactile output on a touch-sensitive surface, such as a touch-sensitive display or touchpad. These components optionally communicate via one or more communication buses or signal lines 303 .

[0088] As used herein, 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 a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under 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., weighted averaged) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).

[0089] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touch / trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” 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's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even if there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0090] It should be understood that electronic device 300 is only one example, and that electronic device 300 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in Figure 3A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.

[0091] Memory 302 optionally includes high-speed random-access memory and, optionally, non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 302 by other components of electronic device 300, such as CPU(s) 320 and peripheral interface 318, is optionally controlled by memory controller 322. Peripheral interface 318 may be used to couple input and output peripherals to CPU(s) 320 and memory 302. One or more processing units 320 operate or execute various software programs and / or instruction sets stored in memory 302 to perform various functions and process data for electronic device 300. In some embodiments, peripheral interface 318, CPU(s) 320, and memory controller 322 are optionally implemented on a single chip, such as chip 305. In some other embodiments, they are optionally implemented on separate chips.

[0092] RF (radio frequency) circuitry 308 transmits and receives RF signals, also referred to as electromagnetic signals. RF circuitry 308 converts electrical signals to and from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 308 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, etc. RF circuitry 308 optionally communicates via wireless communication with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. The wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (WDMA), and the like.Wireless communication technologies include, but are not limited to, wireless (wireless) and wireless (wireless network) technologies, such as wireless code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX®, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP)), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), and Instant Messaging and Presence Event Package (IMP). This includes, but is not limited to, Intermediate Message 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.

[0093] The audio circuit 310, speaker 311, and microphone 313 provide an audio interface between a user and the electronic device 300. The audio circuit 310 receives audio data from the peripherals interface 318, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 311. The speaker 311 converts the electrical signals into sound waves audible to humans. The audio circuit 310 also receives electrical signals converted from sound waves by the microphone 313. The audio circuit 310 converts the electrical signals into audio data and transmits the audio data to the peripherals interface 318 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 302 and / or the RF circuit 308 by the peripherals interface 318. In some embodiments, the audio circuit 310 further includes a headset jack. The headset jack provides an interface between the audio circuitry 310 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., single or double ear headphones) and an input (e.g., a microphone).

[0094] I / O subsystem 306 couples input / output peripherals of electronic device 300, such as display system 312 and other input or output devices 316, to peripheral interface 318. I / O subsystem 306 optionally includes a display controller 356, an optical sensor controller 358, an intensity sensor controller 359, a haptic feedback controller 361, and one or more other input controllers 360 for other input or control devices. One or more other input controllers 360 receive electrical signals from and send electrical signals to other input or control devices 316. Other input or control devices 316 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, other input controller(s) 360 are optionally coupled to any (or none) of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more physical buttons optionally include up / down buttons for volume control of the speaker 311 and / or microphone 313.

[0095] Display system 312 provides an output interface (and, optionally, an input interface, in the case of a touch-sensitive display) between electronic device 300 and a user. Display controller 356 receives and / or sends electrical signals to display system 312. Display system 312 displays visual output to the user. This visual output optionally includes graphics, text, icons, animation, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects / elements.

[0096] In some embodiments, display system 312 is a touch-sensitive display having a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Thus, display system 312 and display controller 356 (along with any associated modules and / or instruction sets in memory 302) detect contact (and any movement or disruption of contact) on display system 312 and translate the detected contact into interaction with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on display system 312. In one exemplary embodiment, the point of contact between display system 312 and the user corresponds to the area under the user's finger.

[0097] Display system 312 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), LED (light emitting diode), or OLED (organic light emitting diode) technology, although other display technologies are used in other embodiments. In some embodiments, when display system 312 is a touch-sensitive display, display system 312 and display controller 356 optionally use any of a number of now-known or later-developed touch-sensing technologies to detect contact and any movement or disruption of that contact, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with display system 312. In one exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPHONE®, iPODTOUCH®, and iPAD® from Apple Inc. of Cupertino, California.

[0098] Display system 312 optionally has a video resolution greater than 400 dpi (e.g., 500 dpi, 800 dpi, or higher). In some embodiments, display system 312 is a touch-sensitive display to which a user optionally makes contact using a stylus, finger, or the like. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures. In some embodiments, electronic device 300 translates coarse finger input into precise pointer / cursor position or commands to perform actions desired by the user.

[0099] In some embodiments, in addition to display system 312, electronic device 300 optionally includes a touchpad for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​electronic device 300 that, unlike display system 312, does not display visual output. In some embodiments, when display system 312 is a touch-sensitive display, the touchpad is optionally a touch-sensitive surface that is separate from display system 312 or an extension of the touch-sensitive surface formed by display system 312.

[0100] Electronic device 300 also includes a power system 362 that provides power to the various components. Power system 362 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC), etc.), a recharging system, power failure detection circuitry, power converters or inverters, power status indications (e.g., light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing electrical power in a portable device.

[0101] Electronic device 300 also optionally includes one or more optical sensors 364 coupled to optical sensor controller 358 in I / O subsystem 306. Optical sensor(s) 364 optionally include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor(s) 364 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In cooperation with imaging module 343, optical sensor(s) 364 optionally capture still images or video. In some embodiments, optical sensors are located on the front of electronic device 300 to optionally obtain an image of the user for video conferencing while the user views other video conference participants on display system 312.

[0102] Electronic device 300 also optionally includes one or more contact intensity sensors 365 coupled to intensity sensor controller 359 in I / O subsystem 306. Contact intensity sensor(s) 365 optionally include 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 the touch-sensitive surface). Contact intensity sensor(s) 365 receive 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 the touch-sensitive surface.

[0103] Electronic device 300 also optionally includes one or more tactile output generators 367 coupled to haptic feedback controller 361 in I / O subsystem 306. Tactile output generator(s) 367 optionally include one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor(s) 365 receive tactile feedback generation instructions from haptic feedback module 333 and generate a tactile output that can be sensed by a user of electronic device 300. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to the touch-sensitive surface and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in / out of the surface of electronic device 300) or laterally (e.g., back and forth in the same plane as the surface of electronic device 300).

[0104] Electronic device 300 also optionally includes one or more proximity sensors 366 coupled to peripheral interface 318. Alternatively, proximity sensor(s) 366 are coupled to other input controller(s) 360 in I / O subsystem 306. Electronic device 300 also optionally includes one or more accelerometers 368 coupled to peripheral interface 318. Alternatively, accelerometer(s) 368 are coupled to other input controller(s) 360 in I / O subsystem 306.

[0105] In some embodiments, the software components stored in memory 302 include an operating system 326, a communications module 328 (or instruction set), a contact / motion module 330 (or instruction set), a graphics module 332 (or instruction set), applications 340 (or instruction set), and a touch bar management module 350 (or instruction set). Additionally, in some embodiments, as shown in FIG. 3A , memory 302 stores device / global internal state 357 (or instruction set). Device / global internal state 357 includes one or more of: an active application state indicating which application, if any, is currently active and / or in focus; a display state indicating which applications, views, or other information occupy various areas of display system 312 and / or peripheral display systems; a sensor state including information obtained from various sensors and input or control devices 316 of electronic device 300; and location information regarding the location and / or orientation of electronic device 300.

[0106] Operating system 326 (e.g., an embedded operating system such as DARWIN®, RTXC®, LINUX®, UNIX®, OS X®, WINDOWS®, or VXWorks®) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

[0107] Communications module 328 facilitates communication with other devices via one or more external ports 324 and / or RF circuitry 308, and includes various software components for sending / receiving data via RF circuitry 308 and / or external port 324. External port 324 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, external port 324 is a multi-pin (e.g., 30-pin) connector the same as, similar to, and / or compatible with the 30-pin connector used on iPod® devices.

[0108] Contact / motion module 330 optionally detects contact with display system 312 when it is a touch-sensitive display (in cooperation with display controller 356) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 330 includes various software components for performing various operations related to contact detection, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether the contact has ceased (e.g., detecting a finger-up event or an interruption of contact). Contact / motion module 330 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are optionally applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 330 also detects contacts on a touchpad.

[0109] In some embodiments, the contact / motion module 330 uses one or more sets of intensity thresholds to determine whether an action has been performed by the user (e.g., whether the user has selected or “clicked” on an affordance). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and may be adjusted without modifying the physical hardware of the electronic device 300). For example, the mouse “click” threshold of a trackpad or touchscreen display may be set to any of a wide range of pre-defined thresholds without modifying the hardware of the trackpad or touchscreen display. Furthermore, in some implementations, a user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-level click “intensity” parameter).

[0110] Contact / motion module 330 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap contact includes detecting a finger down event, followed by detecting a finger lift (lift-off) 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 one or more finger drag events, and in some embodiments also followed by detecting a finger lift (lift-off) event.

[0111] Graphics module 332 includes various known software components for rendering and displaying graphics on primary display 301 or other displays, including components for modifying the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual properties) of the displayed graphics. As used herein, the term “graphic” includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (e.g., user interface objects including soft keys), digital images, videos, and animations. In some embodiments, graphics module 332 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 332 receives, from an application or the like, one or more codes specifying the graphics to be displayed, along with coordinate data and other graphic property data, as necessary, and then generates screen image data to output to display controller 356.

[0112] The haptic feedback module 333 includes various software components that generate instructions used by the tactile output generator(s) 367 to generate tactile outputs at one or more locations on the electronic device 300 in response to user interactions with the electronic device 300.

[0113] Application 340 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: an email client module 341 for receiving, sending, composing, and viewing emails (sometimes referred to herein as a “mail app” or “email app”); an imaging module 342 for capturing still and / or video images; an image management module 343 for editing and viewing still and / or video images (sometimes referred to herein as the “photo app”); a media player module 344 (sometimes referred to herein as a “media player app”) that plays audio and / or video; and • A web browsing module 345 for connecting to and browsing the Internet (sometimes referred to herein as a "web browser").

[0114] Examples of other applications 340 optionally stored in memory 302 include messaging and communication applications, word processing applications, other image editing applications, drawing applications, presentation applications, JAVA®-enabled applications, encryption applications, digital rights management applications, voice recognition applications, and voice duplication applications.

[0115] In cooperation with RF circuitry 308, display system 312, display controller 356, and one or more of contact module 330 and graphics module 332, email client module 341 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. In cooperation with image management module 343, email client module 341 greatly facilitates creating and sending emails with still or video images captured by imaging module 342.

[0116] In cooperation with one or more of the display system 312, the display controller 356, the optical sensor(s) 364, the optical sensor controller 358, the contact module 330, the graphics module 332, and the image management module 343, the imaging module 342 includes executable instructions to capture still images or video (including video streams), store them in the memory 302, change the characteristics of the still images or video, or delete the still images or video from the memory 302.

[0117] In conjunction with one or more of the display system 312, display controller 356, contact module 330, graphics module 332, and imaging module 342, image management module 343 includes executable instructions for arranging, modifying (e.g., editing), or possibly manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0118] In conjunction with one or more of the display system 312, display controller 356, contact module 330, graphics module 332, audio circuitry 310, speaker 311, RF circuitry 308, and web browsing module 345, media player module 344 includes executable instructions that enable a user to download and play recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, and otherwise playing video.

[0119] In conjunction with one or more of the RF circuitry 308, the display system 312, the display controller 356, the contact module 330, and the graphics module 332, the web browsing module 345 contains executable instructions for browsing the Internet based on user commands, including searching for, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0120] 3A , device 300 may also include a companion display module 350 for managing operations associated with companion display mode multitasking on device 100. Companion display module 350 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: an arrangement module 351 for determining the arrangement of displays for a laptop and a tablet device adjacent to each other in association with the companion display mode described herein; a UI generator module 352 for generating user interfaces and sharing data related to those user interfaces across different devices along with companion display and annotation modes; and • A secure criteria module 353 for monitoring whether a device has met a set of secure connection criteria used to determine when a companion display mode is available for use between different devices (e.g., laptop and tablet devices).

[0121] Each of the above-identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 302 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 302 optionally stores additional modules and data structures not described above.

[0122] 3B is a block diagram of components for event processing of FIG. 3A, in some embodiments. In some embodiments, memory 302 (FIG. 3A) includes event sorter 370 (e.g., in operating system 326) and application 340-1 (e.g., any of applications 341, 342, 343, 344, or 345 described above).

[0123] Event sorter 370 receives the event information and determines application 340-1 and application view 391 for application 340-1 to deliver the event information to. Event sorter 370 includes event monitor 371 and event dispatcher module 374. In some embodiments, application 340-1 includes application internal state 392 that indicates the current application view(s) that are displayed on display system 312 when the application is active or running. In some embodiments, device / global internal state 357 is used by event sorter 370 to determine which application(s) are currently active or in focus, and application internal state 392 is used by event sorter 370 to determine application view 391 to deliver the event information to.

[0124] In some embodiments, application internal state 392 includes additional information such as one or more of resume information used when application 340-1 resumes execution, user interface state information indicating information being displayed or ready to be displayed by application 340-1, state cues to enable the user to return to a previous state or view of application 340-1, and redo / undo cues for previous actions taken by the user.

[0125] Event monitor 371 receives event information from peripherals interface 318. The event information includes information about sub-events (e.g., a user touch on display system 312 when it is a touch-sensitive display, as part of a multi-touch gesture). Peripherals interface 318 transmits information it receives from I / O subsystem 306 or sensors such as proximity sensor(s) 366, accelerometer(s) 368, and / or microphone 313 (via audio circuitry 310). Information that peripherals interface 318 receives from I / O subsystem 306 includes information from display system 312 when it is a touch-sensitive display or another touch-sensitive surface.

[0126] In some embodiments, event monitor 371 sends requests to peripherals interface 318 at predetermined intervals. In response, peripherals interface 318 transmits event information. In other embodiments, peripherals interface 318 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined duration).

[0127] In some embodiments, event sorter 370 also includes a hit view determination module 372 and / or an active event recognizer determination module 373 .

[0128] The hit view determination module 372 provides software procedures that determine where a sub-event occurred within one or more views, when the display system 312 displays two or more views, and where the views are composed from the controls and other elements visible to the user on the display.

[0129] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of an application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0130] The hit view determination module 372 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, the hit view determination module 372 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). Once a hit view is identified by the hit view determination module, 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.

[0131] The active event recognizer determination module 373 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 373 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 373 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0132] Event dispatcher module 374 dispatches event information to event recognizers (e.g., event recognizer 380). In embodiments that include active event recognizer determination module 373, event dispatcher module 374 delivers event information to the event recognizers determined by active event recognizer determination module 373. In some embodiments, event dispatcher module 374 stores event information in an event queue, which is retrieved by individual event receivers 382.

[0133] In some embodiments, operating system 326 includes event sorter 370. Alternatively, application 340-1 includes event sorter 370. In still other embodiments, event sorter 370 is a stand-alone module or is part of another module stored in memory 302, such as contact / motion module 330.

[0134] In some embodiments, application 340-1 includes multiple event handlers 390 and one or more application views 391, each containing instructions for processing touch events that occur within a separate view of the application's user interface. Each application view 391 of application 340-1 includes one or more event recognizers 380. Typically, an application view 391 includes multiple event recognizers 380. In other embodiments, one or more of the event recognizers 380 are part of a separate module, such as a user interface kit or a higher-level object from which application 340-1 inherits methods and other properties. In some embodiments, a separate event handler 390 includes one or more of a data updater 376, an object updater 377, a GUI updater 378, and / or event data 379 received from event sorter 370. Event handler 390 optionally utilizes or invokes data updater 376, object updater 377, or GUI updater 378 to update application internal state 392. Alternatively, one or more of the application views 391 include one or more separate event handlers 390. Also, in some embodiments, one or more of the data updater 376, object updater 377, and GUI updater 378 are included in the application view 391.

[0135] A separate event recognizer 380 receives event information (e.g., event data 379) from event sorter 370 and identifies events from the event information. Event recognizer 380 includes an event receiver 382 and an event comparator 384. In some embodiments, event recognizer 380 also includes at least a subset of metadata 383 and event delivery instructions 388 (optionally including sub-event delivery instructions).

[0136] Event receiver 382 receives event information from event sorter 370. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves a movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's posture).

[0137] The event comparator 384 compares the event information to predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 384 includes an event definition 386. The event definition 386 includes definitions of events (e.g., a predefined set of sub-events), such as Event 1 (387-1) and Event 2 (387-2). In some embodiments, sub-events in Event 387 include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one example, the definition for Event 1 (387-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a predetermined phase on the displayed object, a first lift-off (touch end) for a predetermined phase, a second touch (touch start) for a predetermined phase on the displayed object, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for Event 2 (387-2) is a drag on the displayed object. Dragging includes, for example, a touch (or contact) to a predetermined stage on a displayed object, a movement of the touch across the display system 312 when it is a touch-sensitive display, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information for one or more associated event handlers 390.

[0138] In some embodiments, event definition 387 includes definitions of events for individual user interface objects. In some embodiments, event comparator 384 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 display system 312, when a touch is detected on display system 312 when it is a touch-sensitive display, event comparator 384 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each display object is associated with a separate event handler 390, the event comparator uses the results of the hit test to determine which event handler 390 should be activated. For example, event comparator 384 selects the event handler associated with the sub-event and object that triggers the hit test.

[0139] In some embodiments, the definition of an individual event 387 also includes a delay action that delays delivery of the event information until it is determined whether a set of sub-events corresponds to the event type of the event recognizer.

[0140] When the individual event recognizer 380 determines that the sequence of sub-events does not match any of the events in the event definition 386, the individual event recognizer 380 enters an event disabled, event failed, or event finished state and then ignores subsequent sub-events of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0141] In some embodiments, individual event recognizers 380 include metadata 383 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 383 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are allowed to interact with each other. In some embodiments, metadata 383 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0142] In some embodiments, an individual event recognizer 380 activates an event handler 390 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, the individual event recognizer 380 delivers event information associated with the event to the event handler 390. Activating the event handler 390 is distinct from sending (and postponing) the sub-events to the individual hit view. In some embodiments, the event recognizer 380 pops a flag associated with the recognized event, and the event handler 390 associated with the flag captures the flag and performs a predetermined process.

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

[0144] In some embodiments, data updater 376 creates and updates data used by application 340-1. For example, data updater 376 stores video files used by media player module 344. In some embodiments, object updater 377 creates and updates objects used by application 340-1. For example, object updater 376 creates new user interface objects or updates the positions of user interface objects. GUI updater 378 updates the GUI. For example, GUI updater 378 prepares display information and sends it to graphics module 332 for display on display system 312.

[0145] In some embodiments, event handler(s) 390 include or have access to data updater 376, object updater 377, and GUI updater 378. In some embodiments, data updater 376, object updater 377, and GUI updater 378 are included in a single module of application 340-1 or application view 391. In other embodiments, they are included in two or more software modules.

[0146] It should be understood that the foregoing discussion regarding event processing of user touches on a touch-sensitive display also applies to other forms of user input for operating electronic device 300 using input devices, not all of which are initiated on a touchscreen. For example, mouse movements and mouse button presses, touch movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, optionally utilize as inputs corresponding to sub-events that define the event to be recognized.

[0147] As used herein, the term “focus selector” refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other location marker, the cursor functions as a “focus selector” such that when 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 according to the detected input. In some implementations involving a touchscreen display that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen operates as a “focus selector” such that when input (e.g., a press input by contact) is detected on the touchscreen display at the 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 according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab key or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user intends to interact with).For example, the position of a focus selector (e.g., cursor, touch, or selection box) over an individual button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (and not other user interface elements shown on the device's display).

[0148] As used herein and in the 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 or a stylus contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under 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., weighted average or sum) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).Using the intensity of contact as an attribute of user input allows a user to access additional device functionality that may not otherwise be easily accessible by the user on devices of reduced size with limited assets for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0149] In some embodiments, contact / motion module 130 uses one or more sets of intensity thresholds to determine whether an action 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 according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without modifying the physical hardware of portable computing device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. Furthermore, in some implementations, a user of the device is provided with software settings to adjust one or more of the sets of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-level click “intensity” parameter).

[0150] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., 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) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the median intensity of the contact, the average intensity of the contact, the top 10 percent of the intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. 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 action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold would be a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not exceeding a second intensity threshold would be a second action, and a contact having a characteristic intensity that exceeds the second intensity threshold would be a third action. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform the first action or the second action, but rather to determine whether to perform one or more actions (e.g., perform a respective option or refrain from performing a respective action).

[0151] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact (e.g., a drag gesture) that transitions from a start location to 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 may be based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the swipe contact intensity for purposes of determining the characteristic intensity.

[0152] In some embodiments, one or more predefined intensity thresholds are used to determine whether a particular input meets the intensity-based criteria. For example, the one or more predefined intensity thresholds may include: (i) a touch-detection intensity threshold IT0; (ii) a light pressure intensity threshold IT10; L , (iii) (e.g., at least initially I L Higher) deep pressure intensity threshold IT D , and / or (iv) one or more other intensity thresholds (e.g., I L Lower Intensity Threshold I H) In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light pressure intensity threshold (e.g., above a nominal contact-detection intensity threshold IT0 below which contact is no longer detected), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing an action associated with the light or deep pressure intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across various sets of user interface values.

[0153] In some embodiments, the device's response to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact during the input that exceeds a first intensity threshold triggers a first response. In some embodiments, the device's response to an input detected by the device depends on criteria that include both the intensity of the contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input that exceeds a second intensity threshold that is greater than the first intensity threshold for a light press triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 milliseconds in duration (e.g., 40 milliseconds, 100 milliseconds, or 120 milliseconds, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the first intensity threshold is met. During the period of decreased sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. For other deep pressure inputs, the response to the detection of a deep pressure input does not depend on a time-based criterion.

[0154] In some embodiments, one or more of the input intensity threshold and / or corresponding output vary based on one or more factors, such as user settings, contact movement, input timing, running application, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, etc. Exemplary factors are described in U.S. Patent Application Publication Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0155] For ease of explanation, descriptions of actions performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including a pressure input are, optionally, triggered in response to detecting an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Further, in examples where an action is described as being performed in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the action is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold. As noted above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time elapsed between the first intensity threshold being met and the second intensity threshold being met).

[0156] 4A shows an exemplary user interface 400 for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0157] signal strength indication(s) for wireless communication(s), such as cellular and Wi-Fi signals;

[0158] time,

[0159] Bluetooth indication,

[0160] Battery status indication,

[0161] A tray 408 containing icons for frequently used applications, such as:

[0162] an icon 416 for the phone module 138 labeled "Phone," which optionally includes an indication 414 of the number of missed calls or voicemail messages;

[0163] an icon 418 for the email client module 140, labeled "Mail," which optionally includes an indication 410 of the number of unread emails;

[0164] an icon 420 for the browser module 147, labeled "Browser"; and

[0165] an icon 422 for the video and music player module 152, labeled "Music"; and

[0166] Icons for other applications, such as:

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

[0168] an icon 426 for the calendar module 148, labeled "Calendar";

[0169] an icon 428 for the image management module 144, labeled "Photos";

[0170] an icon 430 for the camera module 143, labeled "camera";

[0171] Icon 432 for online video module 155, labeled "Online Video";

[0172] Icon 434 for stock widget 149-2, labeled "Stock Prices"

[0173] Icon 436 for map module 154, labeled "Map";

[0174] Icon 438 for weather widget 149-1, labeled "Weather"

[0175] Icon 440 for alarm clock widget 149-4, labeled "Clock"

[0176] icon 442 for training support module 142, labeled "Training Support";

[0177] an icon 444 for the notes module 153, labeled "Notes"; and

[0178] An icon 446 for a settings application or module that provides access to settings for the device 100 and its various applications 136.

[0179] 4A are merely examples. For example, other labels are optionally used for various application icons. In some embodiments, the label for an individual application icon includes the name of the application corresponding to the individual application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to the particular application icon.

[0180] FIG. 4B shows an example user interface on a device (e.g., device 300, FIG. 3) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from display 450. While many of the following examples are given with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a major axis (e.g., 452 in FIG. 4B ) that corresponds to a major axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) 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 manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It should be understood that similar methods are optionally used for the other user interfaces described herein.

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

[0182] As used herein, the term “focus selector” refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other location marker, the cursor functions as a “focus selector” such that when 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 according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen in FIG. 4A ) that enables direct interaction with user interface elements on the touchscreen display, a contact detected on the touchscreen functions as a “focus selector” such that when input (e.g., a press input by contact) is detected on the touchscreen display at the 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 according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface through which the user intends to interact).For example, the position of a focus selector (e.g., cursor, touch, or selection box) over an individual button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that individual button (and not other user interface elements shown on the device's display).

[0183] As used herein and in the 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 or a stylus contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under 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., weighted average or sum) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).Using the intensity of contact as an attribute of user input allows a user to access additional device functionality that may not otherwise be easily accessible by the user on devices of reduced size with limited assets for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0184] In some embodiments, contact / motion module 130 uses one or more sets of intensity thresholds to determine whether an action 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 according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and may be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display may be set to any of a wide range of pre-defined thresholds without modifying the hardware of the trackpad or touchscreen display. Furthermore, in some implementations, a user of the device is provided with software settings to adjust one or more of the sets of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-level click “intensity” parameter).

[0185] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% of the maximum intensity of the contact, a value generated by low-pass filtering the intensity of the contact starting over a predefined period or at a predefined time, etc. 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 action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity not exceeding the first threshold results in a first action being performed, a contact having a characteristic intensity above the first intensity threshold but not above the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity above the second intensity threshold results in a third action being performed. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform a first operation or a second operation, but rather to determine whether to perform one or more operations (e.g., whether to perform a respective option or refrain from performing a respective operation).

[0186] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact (e.g., a drag gesture) that transitions from a start location to 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 may be based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the swipe contact intensity for purposes of determining the characteristic intensity.

[0187] The user interface diagrams described herein may optionally be configured with one or more intensity thresholds (e.g., a touch-detection intensity threshold IT0, a light press intensity threshold IT1, and a light press intensity threshold IT2). L , deep pressure intensity threshold IT D (e.g., IT, at least initially L higher than 0.15), and / or one or more other intensity thresholds (e.g., IT L An intensity threshold lower than IT H), showing the current intensity of the contact on the touch-sensitive surface relative to the intensity of the contact. This intensity diagram is typically not part of the displayed user interface, but is provided to aid in interpretation of the diagram. In some embodiments, the light pressure intensity threshold corresponds to the intensity at which the device performs an action normally associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to the intensity at which the device performs an action different from the action normally associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light pressure intensity threshold (e.g., above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing the action associated with the light or deep intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent among the various sets of values ​​for the user interface.

[0188] In some embodiments, the device's response to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact during the input that exceeds a first intensity threshold triggers a first response. In some embodiments, the device's response to an input detected by the device depends on criteria including both the intensity of the contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input that exceeds a second intensity threshold that is greater than the first intensity threshold for a light press triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps avoid accidental recognition of deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the first intensity threshold is met. During the period of decreased sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. For other deep pressure inputs, the response to the detection of a deep pressure input does not depend on a time-based criterion.

[0189] In some embodiments, one or more of the input intensity threshold and / or corresponding output vary based on one or more factors, such as user settings, contact movement, input timing, running application, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, etc. Exemplary factors are described in U.S. Patent Application Publication Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties. User Interface and Related Processes

[0190] Attention is now directed to embodiments of user interfaces (“UIs”) and associated processes that may be implemented on a system including a laptop device 300 (FIG. 1A), a tablet device 100 (FIGS. 2A-2B), and / or a desktop device 200 (e.g., FIG. 1B). The system can operate in different modes, including a shared input mode and a companion display mode. In the shared input mode, the user interface generated by each device (e.g., laptop device 300, tablet device 100, or desktop device 200) is presented on the devices' respective displays (e.g., displays 301, 101, and 201 of laptop device 300, tablet device 100, or desktop device 200, respectively) such that the devices share the same input devices (e.g., mouse 202 and keyboard 203, or keyboard 305 and / or touchpad 309). In the companion display mode, the user interface generated by one device (e.g., laptop device 300 of FIG. 1A) is presented on another device (e.g., tablet device 100 of FIG. 1A). The devices described herein (e.g., desktop, laptop, tablet, mobile phone) are used as illustrative examples in the following description, and one of ordinary skill in the art will readily understand that the techniques described herein are equally applicable to any device running a desktop / laptop / tablet operating system, or that in some cases, operations described as being performed on a laptop may also be performed by a tablet device or desktop, and vice versa. The following examples illustrate one or more embodiments.

[0191] 1A shows that laptop device 300 has connection 194 (e.g., a wired or wireless connection), is associated with (e.g., logged into) the same user account as tablet device 100, and has established a trusted connection with the tablet device (e.g., a trust prompt as described below has been accepted by the device's user). The laptop includes a display 301, which may be a touch-sensitive display. Additionally, in some embodiments, the laptop may also include a dynamic function row 304 for displaying additional information (additional details regarding such dynamic function row 304 are provided in U.S. patent application Ser. No. 15 / 655,707, which is incorporated herein by reference in its entirety). Furthermore, the laptop also includes a keyboard 305 and a touchpad 309. With respect to tablet device 100, tablet device 100 includes a touch-sensitive display 101, which may be capacitively sensitive, and device 100 may also receive input from an input device such as a stylus or a user's finger. FIG. 1A also illustrates performing a selection action with the cursor (e.g., by hovering or right-clicking) on ​​maximize button 196 of photo application window 189 (e.g., a button that appears between two other buttons in a corner of the user interface window, and that maximize button may also be presented in green).

[0192] In some embodiments, when in shared input mode, both devices 100 and 300 run their own respective operating systems while sharing input devices (e.g., keyboard 305 and touchpad 309) implemented on device 300. In some embodiments, when in companion display mode, device 100 continues to run its operating system but then receives information from device 300 that enables device 100 to display a user interface generated by device 300 (in some cases, device 100 also ceases displaying any user interface elements associated with its operating system when companion display mode is initiated). Companion display modes include extended display mode and mirrored display mode. In extended display mode, the displays of devices 100 and 300 display a continuous view of content generated by device 300 (e.g., the display of device 100 extends the display of device 300). In mirrored display mode, the display of device 100 displays a mirror image of the display of device 300, and the content on the display is generated by device 300. In some embodiments, two or more devices (e.g., two tablet devices running a mobile operating system or two laptop devices running a desktop operating system) can run the same operating system. For example, in FIG. 1B , device 200 is in a trusted (195) connection 194 with device 300 and device 100, and shares the same user account 193. Device 200 can be in shared input mode or companion display mode with either or both of devices 300 and 100.

[0193] FIG. 1A illustrates two devices, a laptop device 300 and a tablet device 100, both signed in to the same user account 193 (e.g., the same ICLOUD account for APPLE INC., Cupertino, CA) on both displays of the two devices) and having an established connection 194 (e.g., a wired or wireless connection). When the two devices are logged in to the same user account and have an established connection, companion display mode or shared input mode may not yet be available until the devices have a trusted connection (e.g., 195). The laptop device 300 and the tablet device 100 are both connected to the same Wi-Fi wireless network, indicating that the devices have an established connection 194. In some embodiments, the users may not need to be on the same Wi-Fi network, and other forms of connection between the two devices may be possible, such as near-field communication (NFC), Bluetooth, or other short-range communication protocols.

[0194] 5A-8A-I are schematic diagrams of a laptop display 301, a desktop display 201, and a touch-sensitive display 101 of a tablet device, used to illustrate exemplary user interfaces according to some embodiments. The user interfaces in these figures are used to illustrate the methods and / or processes described below. Those skilled in the art will understand that the following user interfaces are merely examples, and that the user interfaces shown in each figure can be invoked in any particular order. Furthermore, those skilled in the art will understand that different layouts having additional or fewer affordances, user interface elements, or graphics can be used in various situations. It should also be understood that any one of the following exemplary user interfaces can correspond to a separate embodiment and need not follow any particular order. The user interfaces in these figures are used to illustrate the processes described below, including the processes of FIGS. 9A-12F.

[0195] 5A-5E illustrate user inputs that move objects (e.g., user interface objects) from a first display of a first device to a second display of a second device when the first and second devices are in extended display mode, according to some embodiments. In FIG. 5A, device 200 (e.g., a desktop device) displays a first user interface 5010 (e.g., a home screen user interface), a menu bar (e.g., menu bar 5008), and a dock (e.g., dock 5006). As referred to herein, the menu bar includes multiple affordances for invoking commands, performing system-level or application-level tasks, and / or status indications (e.g., time, signal strength). As referred to herein, the dock includes multiple application icons (e.g., icons for engaging or launching applications). In some embodiments, at least some of the application icons in the dock correspond to recently viewed applications, frequently used applications, and / or applications based on user preferences or selections. Device 200 further displays a user interface object (e.g., photo object 5004) and a cursor (e.g., cursor 5002) positioned over the object. Movement of the cursor is controlled by an input device (e.g., mouse 202 and / or keyboard 203 in communication with device 200). In FIGS. 5A-5E, desktop device 200 is communicating with tablet device 100 in extended display mode. In some embodiments, desktop device 200 is communicating with tablet device 100 when both desktop device 200 and tablet device 100 are signed in to the same user account 193 and have established a trusted (e.g., 195) connection 194 (e.g., wired or wireless connection), as described with respect to FIG. 1A.In some embodiments, when desktop device 200 is communicating with tablet device 100, both desktop device 200 and tablet device 100 are connected to the same Wi-Fi wireless network or other form of connection (e.g., near field communication (NFC), Bluetooth, or other short-range communication protocol). Specifically, device 200 is positioned next to device 100 such that a first edge (e.g., edge 201-1) of display 201 of device 200 is substantially parallel to and close to (e.g., within 1 or 2 feet of) a first edge (e.g., edge 101-1) of display 101 of device 100. In some embodiments, the edge of the display refers to the location on the device (e.g., the touch-sensitive display or touch screen 112 or display system 312 described above) where the display area ends and the edge of the display device's frame begins (or, in the case of a borderless display, the side of the device). In extended display mode, the displays of devices 100 and 200 display a continuous view of the display content generated by device 200 (e.g., the desktop of device 100's display extends across the display of device 300), as shown along with the corresponding horizontal desktop wallpaper (e.g., background image of user interface 5010) displayed on displays 201 and 101. In some embodiments, device 100 also displays menu bar 5008, which corresponds to the menu bar displayed on device 200, as shown. Note that some aspects of user interface features, such as the menu bar, may appear differently or include different selections of indications and / or affordances, for example, based on different display sizes and orientations. Edges 201-1 and 101-1 of each device include portals for moving particular objects (e.g., a cursor or user interface object) from display 201 across edge 201-1 onto display 101.For example, the portal corresponds to a first portion of the respective edge that allows a particular object to be moved from display 201 to display 101. Portions of the respective edge outside the first portion do not allow movement of the particular object. In some embodiments, the portal extends along a portion of the respective edge of edges 201-1 and 101-1 (e.g., a portion corresponding to about 25%, about 50%, or about 75%) or along the entire length of the respective edge of edges 201-1 and 101-1. For example, the portal extends along about 50% of the width of the respective display.

[0196] 5A , device 200 detects input via mouse 202 (e.g., input including press 5011-A (e.g., a gray dot) on mouse 202 followed by movement 5012-A of mouse 202 in the direction indicated by the arrow in FIG. 5A ) while cursor 5002 is displayed over photo object 5004. In some embodiments, the input corresponds to a request to select and move photo object 5004. In some embodiments, the input corresponds to a request to select and drag photo object 5004 in accordance with movement of mouse 202 (e.g., movement 5012-A). For example, user input includes press 5011-A (e.g., indicated by a gray dot on mouse 202) and drag input performed via mouse 202 to select photo object 5004 and move the photo object in accordance with the drag input. In FIG. 5B , device 200 displays photo object 5004 moving in accordance with movement 5012-A of mouse 202 toward edge 201-1 of display 201. In some embodiments, photo object 5004 is moved in a direction corresponding to movement 5012-A and at a velocity and / or acceleration corresponding to movement 5012-A. For example, the movement of photo object 5004 may increase, decrease, or halt in accordance with movement 5012-A. As long as photo object 5004 remains selected, the object follows the movement of mouse 202. In some embodiments, in response to detecting that photo object 5004 is being moved toward edge 201-1 of device 100 that includes a portal for moving the object to display 201, device 200 displays an indication (e.g., indication 5014-A) indicating the position of the portal that allows the object to be moved from display 101 to display 101. In some embodiments, the length of indication 5014-A corresponds to the size of the portal. In some embodiments, the length of indication 5014-A corresponds to the length of edge 101-1 of device 100 (e.g., extended display).In some embodiments, concurrently with displaying indication 5014-A by display 101, display 201 displays corresponding indication 5014-B. Indication 5014-B extends along edge 101-1 of display 101 facing edge 201-1 of display 201. In some embodiments, indication 5014-A and / or indication 5014-B are displayed pursuant to a determination that an object (or set of one or more objects) being moved toward edge 201-1 is a representation of content that can be moved from display 201 to display 101. In some embodiments, the content that can be moved from display 101 to display 201 corresponds to textual content (e.g., one or more text files or a selection of text), a photo object (e.g., one or more photos), video content, audio content, or presentation content. 5C , in accordance with a determination that photo object 5004 can be moved from display 201 to display 101, photo object 5004 moves across edges 201-1 and 101-1 and through a portal when devices 200 and 100 are in extended display mode. In FIG. 5C , the user input further includes movement 5012-B to move photo object 5004 to a desired position on display 101. In some embodiments, movements 5012-A and 5012-B are part of a continuous drag input. In some embodiments, the appearance (e.g., size, shape, color, pattern) of cursor 5002 changes according to the device on which it is displayed. As shown, the appearance of cursor 5002 changes as the cursor moves from display 201 (e.g., a desktop display) to display 101 (e.g., a tablet touchscreen). In some embodiments, the appearance of the moved object also changes. For example, device 200 with a smaller display size may display an object that is reduced in size compared to device 100 with a larger display size.5D , the photo object 5004 is moved to a central portion of the display 201. In FIG. 5D , the device 200 further detects an end of the gesture for moving the photo object (e.g., the press gesture on the mouse 202 is released). In some embodiments, the release of the input corresponds to a request to drop the photo object 5004 at the position of the cursor 5002. As shown in FIG. 5E , the photo object 5004 is positioned (e.g., dropped) at a position corresponding to the position of the cursor 5002 when the press on the mouse 202 was released. As shown, the photo object 5004 remains in the same position while the cursor 5002 is moved away from the object. Selecting, moving, and releasing an object using input detected on a mouse, as described with respect to FIGS. 5A-5F , is applicable to other user interfaces described below. It is also understood that moving a user interface object (e.g., the photo object 5004) from the display 201 to the display 101 is exemplary. It will be appreciated that user interface objects can also be moved from display 101 to display 101 in a similar manner.

[0197] 5F-5J illustrate user inputs that move an object from a first display of a first device to a second display of a second device when the first and second devices are in shared input mode, according to some embodiments. In FIG. 5A, device 200 displays an application user interface (e.g., photo application 5016) over a first user interface 5010. Photo application 5016 includes a photo object 5004 displayed on user interface 5010 of FIG. 5A. Device 200 is positioned adjacent to device 100 such that a first edge (e.g., edge 201-1) of display 201 of device 200 is substantially parallel to and proximate to a first edge (e.g., edge 101-1) of display 101 of device 100. In FIGS. 5F-5J, desktop device 200 and tablet device 100 are in shared input mode. As described above, in shared input mode, devices 100 and 200 share one or more input devices (e.g., keyboard 203 and mouse 202). However, device 100 and device 200 operate their respective operating systems while receiving input via the same input device (e.g., keyboard 203 and mouse 202 in communication with device 200). In some embodiments, device 200 receives the input and communicates the input to device 100 pursuant to a determination that a cursor is displayed on display 101 of device 100. Device 100 thereby receives information regarding the input from device 200 and performs an action accordingly. As shown in FIG. 5F , display 101 of device 100 displays a user interface (e.g., email user interface 5018) that is different from the user interfaces (e.g., user interface 5010 and application user interface 5016) displayed on display 201 of device 200.

[0198] 5F , device 200 detects input via mouse 202 (e.g., a press on mouse 202 followed by a drag movement in the direction indicated by the illustrated arrow) corresponding to a request to select and move photo object 5004. As described above, the input corresponds to a request to drag photo object 5004 in accordance with movement of mouse 202. In FIG. 5G , device 200 displays photo object 5004 moving in accordance with movement of mouse 202 toward edge 201-1 of display 201 (e.g., in accordance with the direction, speed, acceleration, etc. of mouse 202 movement). In some embodiments, in response to detecting that photo object 5004 is being moved toward edge 201-1 that includes a portal for moving objects to display 201 of device 100, device 200 displays an indication (e.g., indication 5014-A) indicating the position of the portal that enables the object to be moved from display 101 to display 101. In FIG. 5H , in accordance with a determination that photo object 5004 can be moved from display 201 to display 101, when devices 200 and 100 are in shared input mode, photo object 5004 is moved from display 201 to display 101 through the portal, across edges 201-1 and 101-1. In FIG. 5I , photo object 5004 is moved to a central portion of display 201 and positioned on application user interface 5018. In FIG. 5I , device 200 further detects the end of the gesture for moving the photo object (e.g., the press gesture on mouse 202 is released). In some embodiments, the release of the input corresponds to a request to drop photo object 5004 at the position of cursor 5002. As shown in FIG. 5J , photo object 5004 is positioned (e.g., dropped) at a position corresponding to the position of cursor 5002 when the press on mouse 202 was released. As shown, the photo object 5004 remains in the same position while the cursor 5002 is moved away from the object.5F-5J, in addition to moving user interface objects between system-level user interfaces (e.g., user interface 5010, such as the home screen user interface of FIGS. 5A-5F), user interface objects can be moved from a first application window displayed on a first display of a first device (e.g., photo application user interface 5016 on display 201 of device 200) to a second application window displayed on a second display of a second device (e.g., email application 5018 on display 101 of device 100). The first application and second application can be user interfaces of the same application or different applications.

[0199] 5K-5N illustrate user inputs that move an application window from a first display of a first device to a second display of a second device when the first and second devices are in extended display mode, according to some embodiments. In FIGS. 5K-5N, devices 200 and 100 are in extended display mode, as described above with respect to FIG. 5A. In FIG. 5K, device 200 displays an application user interface (also referred to as an application window) (e.g., photo application 5016). In FIG. 5K, device 200 detects input (e.g., a press followed by movement in the direction indicated by the arrow) via mouse 202. In FIG. 5K, cursor 5001 is positioned in a predefined region of the application window associated with a user interface selection instead of a user interface object (e.g., an area corresponding to the menu bar of the application user interface). In some embodiments, a press input received on the mouse 202 while the cursor 5002 is positioned over a predetermined area of ​​the application user interface 5016 corresponds to a request to select the application user interface 5016 and move the application user interface 5016 according to the movement of the mouse.

[0200] 5L , in accordance with a determination that application user interface 5016 can be moved from display 201 to display 101, when device 200 and device 100 are in extended display mode, device 200 displays application user interface 5016 that moves across edge 201-1 of display 201 to display 101 in accordance with movement of mouse 202. As shown, in some embodiments, indication 5014-A and / or indication 5014-B are displayed in accordance with a determination that application user interface 5016 has been moved toward edge 201-1. In FIG. 5M , application user interface 5016 is moved to a central portion of display 201. In FIG. 5M , device 200 further detects the end of the gesture for moving the photo object (e.g., the press gesture on mouse 202 is released). In some embodiments, the release of the input corresponds to a request to drop application user interface 5016 at the position of cursor 5002. 5N, application user interface 5016 is positioned (e.g., dropped) at a position corresponding to the position of cursor 5002 when the pressure on mouse 202 is released. As shown, application user interface 5016 remains in the same position while cursor 5002 is moved away from the application user interface (e.g., via movement of mouse 202).

[0201] 5O-5P illustrate user inputs for attempting to move an application window from a first display of a first device to a second display of a second device when the first and second devices are in extended display mode and the first display provides an indication that moving the application window to the second display is prevented, according to some embodiments. In FIGS. 5O-5P, devices 200 and 100 are in shared input mode, as described above with respect to FIG. 5F. In FIG. 5P, device 100 displays a system-level user interface (e.g., home screen 5020) that differs from the system-level user interface (e.g., home screen user interface 5010) displayed by device 200 (e.g., as indicated by device 100's diagonally striped wallpaper, which differs from device 200's horizontally striped wallpaper). Additionally, device 200 displays a status bar 5009 (e.g., including indications of signal strength, battery, and Wi-Fi signal) that differs from the menu bar 5008 displayed by device 200. In Figure 5O, device 200 displays application user interface 5016. In Figure 5K, device 200 detects input (e.g., a press followed by movement in the direction indicated by the arrow) via mouse 202 while cursor 5001 is positioned within a predefined region of an application window associated with selecting a user interface instead of a user interface object (e.g., a region corresponding to a menu bar of the application user interface). In some embodiments, a press input received on mouse 202 while cursor 5002 is positioned over a predefined region of application user interface 5016 corresponds to a request to select application user interface 5016 and move application user interface 5016 according to the movement of the mouse.

[0202] 5P , application user interface 5016 is moved to edge 201-1 of display 201 (e.g., application user interface 5016 has reached edge 201-1 of display 201 or is within a threshold distance from edge 201-1). When devices 200 and 100 are in shared display mode, in accordance with a determination that the moved object is an application user interface that cannot be moved from display 201 to display 101, device 200 halts the movement of application user interface 5016 even though mouse movement continues in the projection direction. In some embodiments, in accordance with a determination that the moved object is an application user interface and cannot be moved between displays, device 200 displays an indication (e.g., indication 5014-C) indicating that moving the object between displays is not permitted. In some embodiments, the indication corresponds to a bar extending along edge 201-1 (e.g., similar to indication 5014-A described with respect to FIG. 5B ), but indication 5014-C has a different appearance than indication 5014-A indicating that it is possible to move an object between displays. For example, indication 5014-C has a different color, size, or pattern than the color, size, or pattern of indication 5014-A. In some embodiments, device 200 provides another visual indication that moving application user interface 5016 from display 201 to display 101 is not permitted. In some embodiments, device 200 displays an animation indicating that application user interface 5016 appears to bounce off edge 201-1. In some embodiments, device 200 displays an animation indicating that application user interface 5016 appears to bounce back to its original position on display 201 (e.g., the position when the select and drag user input was initiated).In some embodiments, device 200 displays an animation indicating that edge 201-1 is resisting movement of application user interface 5016. For example, cursor 5002 continues to move toward edge 201-1 as mouse 202 moves, but application user interface 5016 stops moving when it reaches edge 201-1.

[0203] 5Q-5T illustrate user inputs that move selected text from a first display of a first device to a third display of a third device when the first device and a third device are in extended display mode and the first device is also communicating with a second device, according to some embodiments. In FIG. 5Q, a desktop device 200 communicates with a tablet device 100 and a laptop device 300. Specifically, the device 300 is positioned next to the device 300 such that a first edge (e.g., edge 301-1) of the display 201 of the device 200 is substantially parallel to and proximate to a second edge (e.g., edge 201-2) of the display 301 of the device 200. The device 200 is communicating with the device 300 in a shared input mode (e.g., the device 300 is running its own operating system while receiving commands from the input device communicating with the device 200). As shown, device 300 displays a system-level user interface (e.g., home screen user interface 5024) that includes a menu bar (e.g., menu bar 5028). Home screen 5025 and menu bar 5028 are different from home screen user interface 5010 and menu bar 5008, respectively, displayed by device 200. Device 200 can communicate with device 100 in shared input mode, extended display mode, or mirrored display mode. In FIG. 5Q , device 200 displays an application user interface (e.g., notes application 5030) that includes text arranged on two lines. As shown, text line 5032 is selected, as indicated by highlighting. For example, device 200 has detected user input corresponding to a request to select text. In some embodiments, the user input corresponding to the request to select text line 5032 includes a press and hold while cursor 5002 is positioned over the text to be selected, and then dragging cursor 5002 to expand the selection to a desired size.In FIG. 5Q, device 200 detects user input via mouse 202 (e.g., a press followed by movement in the direction indicated by the arrow) while cursor 5001 is over selected text line 5032. In some embodiments, text line 5032 is moved in accordance with the movement of the mouse. In FIG. 5R, text line 5034 is moved to edge 201-2 of display 201. In some embodiments, in accordance with a determination that the movement of text line 5034 is toward edge 201-2, indication 5014-C is displayed along edge 201-2 to indicate the position of a portal that allows the object to be moved from display 201 to display 301. In some embodiments, in accordance with a determination that the movement of text line 5034 is toward edge 201-2 (and not toward edge 201-1), device 200 ceases displaying an indication along edge 201-1 (e.g., indication 5014-A of FIG. 5B). When devices 200 and 100 are in shared input mode, in accordance with a determination that the moved object is a text line that can be moved from display 201 to display 301, device 200 displays text line 5034 that moves across edge 201-2 of display 201 to display 101 in accordance with the movement of mouse 202. In FIG. 5S, text line 5032 is moved to email application 5026. In FIG. 5S, device 200 further detects the end of the gesture for text line 5032 (e.g., the press input on mouse 202 is released). In some embodiments, the release of the input corresponds to a request to drop text line 5034 at the position of cursor 5002 on email application 5026. As shown in FIG. 5T, text line 5034 is positioned (e.g., dropped) at a position corresponding to the position of cursor 5002 when mouse 202 was released. As shown, the text line 5034 remains in the same position while the cursor 5002 is moved away from the text line 5034 (eg, via movement of the mouse 202).Based on a request to copy or move an object, such as text line 5032, the object may be copied or moved to a new position on a different display. As shown in FIG. 5T, text line 5032 is copied from notes application 5030 on display 201 to an email application such that text line 5034 remains displayed on notes application 5030. Alternatively, text line 5034 is moved from notes application 5030 on display 201 to an email application, such that text line 5034 is no longer displayed on notes application 5030.

[0204] 6A-6D illustrate displaying an indication on a first display of a first device when the second display of the second device is available to move content from the first display to the second display, according to some embodiments. In FIG. 6A, tablet device 100 is positioned near desktop device 200. Display device 100 is in sleep mode 6006 (e.g., a power-saving mode or low-power mode). In some embodiments, when in sleep mode, the device turns off touchscreen display 101, thereby reducing power consumption of device 100. For example, the device turns off any display by display generation components (e.g., display controller 156 associated with display 101). In some embodiments, the device turns on sleep mode pursuant to a determination that user interaction device 100 has been absent for a predetermined period of time. In some embodiments, device 100 turns on sleep mode in response to detecting a user input to turn on sleep mode. In some embodiments, device 100 turns off sleep mode (e.g., wakes display 101) in response to detecting a user input. In some embodiments, the user input is a gesture (e.g., a tap or swipe gesture with contact 6002-2 on touch-sensitive display 101) or a button press (e.g., press 6002-1 on button 6004 (e.g., the Start button)). In some embodiments, the device turns off the low power mode in response to detecting a change in the orientation of device 100. For example, the orientation of device 100 changes from a horizontal orientation (e.g., lying on its side) to a vertical position. When the device exits sleep mode, display 101 displays a wake screen user interface (e.g., wake screen user interface 6008), as shown in FIG. 6B.In some embodiments, the wake screen user interface is initially displayed in a locked state and then transitions to an unlocked state after authentication information is obtained (e.g., through passcode entry or biometric verification). In some embodiments, the wake screen user interface and the lock screen user interface have similar appearances. In some embodiments, the wake screen user interface includes a time element (e.g., time element 6010) that displays the current time and optionally the date. In some embodiments, the wake screen usage interface includes a status bar 5009. When device 100 is in sleep mode 6006 or displaying wake screen user interface 6008, display 101 is not available to receive objects moved from display 201 of device 200 to display 101 of device 200 (e.g., as described with respect to FIGS. 5A-5T). In some embodiments, no communication is established between devices 200 and 100 (e.g., the devices operate independently without any communication between each other, or the devices do not share a user account 193 and / or do not have a trusted (195) connection 194). In some embodiments, device 100 exits the wake screen and / or the lock screen in response to detecting user input and / or receiving authentication information. For example, device 100 detects user input (e.g., a tap or swipe gesture with contact 6002-3 on touch-sensitive display 101 shown in FIG. 6B , or a user input on a button).

[0205] 6C , device 100 displays a system-level user interface (e.g., home screen 5020) after exiting the wake screen and / or lock screen in response to detecting user input (e.g., via contact 6002-3). Home screen 5020 includes a plurality of application icons 6012 (e.g., application launch icons). In some embodiments, application icons 6012 correspond to the application icons described with respect to FIG. 4A . When device 100 begins displaying home screen 5020 or an application user interface (e.g., email user interface 5018 of FIG. 5F ), after exiting sleep mode and / or wake screen / lock screen user interface 6008, device 100 may be available to receive one or more user interface objects moved (e.g., dragged) from device display 201 to display 101 of device 100. In response to detecting an event (e.g., starting to display home screen 5020 and / or application user interface 5018 after exiting sleep mode and / or wake screen or lock screen user interface 6008), device 200 determines whether display 101 meets a first set of criteria for being available to receive one or more user interface objects moved between display 101 and display 201. In some embodiments, the first set of criteria includes the devices sharing a user account 193 and / or having a trusted (195) connection 194 or being able to establish such a trusted connection. In some embodiments, the first set of criteria includes the devices having established communication in a shared display mode, as described above. In some embodiments, the first set of criteria includes the devices having established communication in an extended display mode.In some embodiments, the first set of criteria includes the distance between device 200 and device 100 being below a threshold distance (e.g., as determined based on Bluetooth range or based on ultra-wideband (UWB) positioning technology). In some embodiments, the first set of criteria includes both display 101 of device 100 and display 201 of device 200 displaying a user interface that allows for the display of movable user interface objects (e.g., devices 100 and 200 are not in sleep mode or display a wake screen user interface or a lock screen user interface). In response to determining that the first set of criteria for allowing user interface objects to be moved between devices is met, device 200 displays an indication (e.g., indication 6014-A) on a first region of display 201. In some embodiments, indication 6014-A is displayed adjacent to edge 201-1 of display 201. In some embodiments, indication 6014-A has an appearance similar to indication 5014-A described with respect to FIG. 5B . In some embodiments, indication 6014-A corresponds to indication 5014-A. For example, indication 6014-A indicates the position of a portal that allows an object to be moved from display 201 to display 101. In some embodiments, in response to determining that a first set of criteria for allowing a user interface object to be moved between devices is met, display 101 displays indication 6014-B in a first region of display 101. In some embodiments, indication 6014-B is displayed adjacent to edge 101-1 of display 101 (e.g., edge 101-1 opposite edge 201-1 of display 201). In some embodiments, indication 6014-B has a similar appearance to indication 5014-B described with respect to FIG. 5B . In some embodiments, indication 6014-B corresponds to indication 5014-B.For example, indication 6014-B indicates the position of a portal that allows an object to be moved from display 201 to display 101. As shown in Figure 6C, indication 6014 is displayed at a position corresponding to the portion of each of displays 201 and 101 that corresponds to the portal that allows user interface objects to be moved between the displays.

[0206] 6D , device 100 has been moved to a different side of device 200 (e.g., device 100 is facing edge 201-2 of display 201, opposite edge 201-1). In some embodiments, the relative positions of devices 100 and 200 are determined based on Bluetooth, Wi-Fi, or UWB signals. In some embodiments, the relative positions of devices 100 and 200 are determined based on user input (e.g., while displaying a display preference user interface described with respect to FIGS. 7A-7G ). As shown in FIG. 6D , device 200 displays indication 6014-D on a second portion of display 201 (e.g., along edge 201-2 facing device 100). In some embodiments, device 100 displays indication 6014-C on a second portion of display 101 (e.g., along edge 101-2 facing device 200). As shown in Figures 6C-6D, device 200 and optionally device 100 display an indication in the area of ​​each display corresponding to the portal (e.g., the portion of each edge that can be used to drag a user interface object between displays) to indicate that the user interface object can be moved between devices.

[0207] 6E-6F illustrate switching display modes of a first device and a second device communicating with each other in a display settings user interface of the first device, according to some embodiments. In FIG. 6E, device 200 displays display settings user interface 6016. In some embodiments, display settings user interface 6016 is displayed in response to a user input to an affordance or keystroke combination corresponding to a request to display settings user interface 6016. Display settings user interface 6016 includes a representation of device 200 (e.g., representation 6018-A) and a representation of device 100 (e.g., representation 6018-B). In some embodiments, the representations include a text identifier (e.g., "Joe's tablet and Joe's desktop computer"). In some embodiments, the representations display a pattern and / or graphic corresponding to the wallpaper of the respective devices. In FIG. 6E, device 200 and device 100 are in shared input mode. In some embodiments, the mode is indicated by a text indication (e.g., "Shared Input Mode") on display settings user interface 6016. Also shown in FIG. 6E , representation 6018-A has a horizontal stripe pattern corresponding to the wallpaper displayed on home screen user interface 5010 of device 200, and representation 6018-B has a diagonal stripe pattern corresponding to the wallpaper displayed on home screen user interface 5020 of device 100. In FIG. 6E , representations 6018-A and 6018-B are displayed separately from one another. In some embodiments, representation 6018-B is separated from representation 6018-A by a distance greater than a predetermined distance. In FIG. 6E , device 200 detects user input (e.g., pressing down mouse 202 followed by moving mouse 202 in the direction of the arrow) while cursor 5002 is displayed over representation 6018-B. In some embodiments, the user input in FIG. 6E corresponds to a request to select representation 6018-B and move representation 6018-B according to the movement of mouse 202. In FIG. 6F, representation 6018-B is moved adjacent to (eg, directly touching) representation 6018-A.In some embodiments, device 200 displays an animation of the representations "snapping" together (e.g., sliding together) when representation 6018-B reaches a predetermined distance from representation 6018-A. In some embodiments, the user input to move the representations adjacent to each other corresponds to a request to change mode from shared input mode to extended display mode, as shown in FIG. 6F. In FIG. 6F, in response to changing mode to extended display mode, display 101 displays home screen user interface 5010 and menu bar 5008 corresponding to the home screen user interface and menu bar displayed on display 201. At the same time, the appearance of representation 6018-B has changed to reflect the appearance of display 101 (e.g., representation 6018-B has a horizontal stripe pattern corresponding to the wallpaper of home screen user interface 5010).

[0208] 6G-6H illustrate displaying an indication on a first display of a first device when the third display of the first device is available to move content from the first display to the third display while the first device is also communicating with a second device, according to some embodiments. In FIG. 6G, laptop device 300 is positioned away from desktop device 200 by a distance greater than the threshold distance (e.g., distance D) for establishing communication between devices 200 and 300 (e.g., in shared input mode or extended display mode). Thus, in FIG. 6G, device 300 is not communicating with device 200 in shared input mode or extended display mode. Instead, device 300 runs its own operating system. As shown, device 300 displays a system-level user interface (e.g., home screen user interface 5024), a dock (e.g., dock 5022), and a menu bar (e.g., menu bar 5028) that are distinct from the home screen user interface, dock, and menu bar displayed by display 201 of device 200. In FIG. 6H , device 300 is moved closer to device 100 such that the distance between the devices is less than threshold distance D for establishing communication between devices 200 and 300 (e.g., in shared input mode or extended display mode). Pursuant to a determination that device 300 is within threshold distance D for establishing communication, and in accordance with a determination that any other criteria of the first set of criteria for moving user interface objects between device 200 and device 300 are met, device 200 displays indication 6014-D within a second region of display 201 (e.g., along edge 201-1 of display 201). In some embodiments, display 201 of device 200 also displays an indication in a first region of display 301 (eg, indication 6014-E along edge 301-1 facing device 200).

[0209] 6I-6K illustrate user inputs that move objects (e.g., user interface objects) from a first display of a first device to a second display of a second device when the first and second devices are in shared input mode, according to some embodiments. In FIG. 6I, the display 201 of the device 200 displays a photo application user interface 5016 including photo objects 5004-A and 5004-B. The display 201 of the device 100 displays a notes application user interface 6020. The devices 200 and 100 are in shared input mode. In FIG. 6I, the photo objects 5004-A and 5004-B are selected, as indicated by gray highlighting, and the cursor 5002 is positioned over the selected photo object 5004-B. For example, multiple user interface objects may be selected with a user input corresponding to dragging (e.g., moving the mouse 202 while holding a press on the mouse 202) over an area that includes the multiple user interface objects. In Figure 6I, while displaying cursor 5002 over selected photo objects 5004-A and 5004-B, device 200 detects user input (e.g., a press on mouse 202 followed by movement in the direction indicated by the arrow). In some embodiments, the user input in Figure 6I corresponds to a request to move selected photo objects 5004-A and 5004-B in accordance with movement of mouse 202. In some embodiments, indication 6014-A is displayed along edge 201-1 of display 201 to indicate that a user interface object may be moved from display 201 to display 101 of device 100 across the portal indicated by indication 6014-A. In Figure 6J, selected photo objects 5004-A and 5004-B have been moved toward edge 201-1 of display 201 in accordance with movement of mouse 202.In Figure 6K, selected photo objects 5004-A and 5004-B have been moved to a central portion of display 101 on notes application user interface 602. In Figure 6K, the device also detects a release of the user input (e.g., a lift-off of a press gesture on mouse 202). In response to this release, photo objects 5004-A and 5004-B are positioned at positions corresponding to the position of cursor 5002 when the user input was released.

[0210] 6L-6M illustrate user inputs for attempting to move an object from a first display of a first device to a second display of a second device across a location outside the portal indicated by the indication, according to some embodiments. As noted above, in some embodiments, indications such as 6014-A described with respect to FIG. 6C indicate the location of individual edge portions that enable the dragging of user interface objects between displays of different devices. As a result, in some embodiments, user interface objects cannot be dragged between displays of different devices at locations outside of these indications. In FIG. 6L, display 201 of device 200 displays photo application user interface 5016, including photo objects 5004-A and 5004-B, and display 201 of device 100 displays note application user interface 6020. Devices 200 and 100 are in shared input mode. In Figure 6I, device 200 detects user input (e.g., a press of mouse 202 followed by movement in the direction indicated by the arrow) while displaying cursor 5002 over photo object 5004-B in Figure 6L. In some embodiments, the user input in Figure 6L corresponds to a request to select and move photo object 5004-B in accordance with movement of mouse 202. In some embodiments, indication 6014-A is displayed along edge 201-1 of display 201 to indicate that a user interface object may be moved from display 201 to display 101 of device 100 across the inter-display portal indicated by indication 6014-A. However, in Figure 6L, movement of mouse 202 in the direction indicated by the arrow has a projection direction toward an edge region of display 201 that is outside of indication 6014-A (e.g., an upper region of edge 201-1). In FIG. 6M, photo object 5004-B has been moved toward the upper region of edge 201-1 of display 201 in accordance with the movement of mouse 202.As shown in FIG. 6M, photo object 5004-B has reached the outer edge 201-1 of the inter-display portal, as indicated by indication 6014-A, and therefore photo object 5004-B cannot be dragged across edge 201-1 onto display 101 of device 100.

[0211] 6N-6O illustrate user input on a touchpad of a third device moving an object from a first display of a first device to a second display of a second device when the first device is in a shared input mode with the second and third devices, according to some embodiments. As described above, two or more display devices may be operated in communication with each other (e.g., in a shared input mode or a companion display mode) while sharing one or more input devices. In some embodiments, one or more input devices communicate with a single display device. For example, keyboard 203 and mouse 202 communicating with desktop device 200 are shared between desktop device 200, tablet device 100, and laptop device 300. In some embodiments, one or more input devices communicate with two or more display devices. For example, in addition to keyboard 203 and mouse 202, desktop device 200, tablet device 100, and laptop device 300 may also be operated with touchpad 309 and keyboard 305 of laptop device 300, as shown in FIG. 6N. 6N , device 200 is communicating with devices 100 and 300 in shared input mode. In some embodiments, device 200 is communicating with devices 100 and 300 in extended display mode (e.g., displays 201, 101, and 301 all display an extended view of the user interface provided by device 200). In any of these embodiments, devices 200, 300, and 100 may all be input devices (e.g., mouse 202, keyboard 203, keyboard 305, and touchpad 309). In some other embodiments, device 200 communicates with device 100 in shared input mode and with device 300 in extended display mode, or vice versa.

[0212] 6N, device 200 displays a notes application user interface 6022 including text arranged on two lines, and device 100 displays a notes application user interface 6020. As shown, text line 5032 is selected, as indicated by a highlight. In FIG. 6N, device 300 detects user input (e.g., contact 6026) on touchpad 309 while cursor 5002 is displayed over selected text line 5032. For example, the user input corresponds to a press of contact 6026 followed by movement in the direction indicated by the arrow. In some embodiments, the user input corresponds to a request to move (e.g., drag) selected text line 5032 in accordance with the movement of contact 6026 on touchpad 309 (e.g., in the direction indicated by the arrow). In some embodiments, indication 6014-A is displayed along edge 6014-1 of display 201 to indicate that a user interface object may be moved from display 201 to display 101 of device 100 across the portal indicated by indication 201-A. In some embodiments, device 200 displays indication 6014-A along edge 201-1 in response to device 300 detecting that movement of contact 6026 for dragging text line 5032 is toward edge 201-1. In some embodiments, simultaneously with displaying indication 6014-A, device 100 displays indication 6014-B along edge 101-1. In FIG. 6O , text line 5032 is moved to a central portion of display 101 on notes application 6020 in accordance with movement of contact 6026. As described above, in response to device 300 detecting the end of user input (e.g., liftoff of contact 6026), text line 5032 is dropped at the location of cursor 5002 at the time the end of user input was detected.

[0213] FIG. 6P illustrates user input in a predetermined manner on the touchpad of a third device that highlights a second display of the second display when a cursor is displayed on the second display, according to some embodiments. In some instances, when operating multiple display devices simultaneously, a user may find it difficult to recognize which display is currently displaying cursor 5002, and a method for providing an indication of such a display to the user is useful. In FIG. 6P, device 300 detects user input (e.g., contact 6028) on touchpad 309. The user input includes moving contact 6028 on touchpad 309 in a predetermined motion. For example, the movement includes a circular movement that moves cursor 5002 in a circular motion (e.g., cursor 5002 is hovering over an area on display 101). In response to identifying that the user input includes movement in the predetermined motion and that cursor 5002 is displayed on display 101 of device 100, display 101 displays an indication that cursor 5002 is located on that display. In some embodiments, the indication includes increasing the brightness of display 101 or a portion of display 101. In Figure 6P, the indication includes a brightened rim 6032 of display 101.

[0214] 6Q-6T illustrate user input on a touchpad of a third device that causes actions on the second display and the first display based on where the cursor appears when the user input is received, according to some embodiments. In FIGS. 6Q-6T, device 300 is communicating with devices 100 and 200 in shared input mode. In FIG. 6Q, device 200 displays home screen user interface 5010, and device 100 displays home screen user interface 5020. In FIG. 6Q, device 300 detects user input (e.g., contact 6030) on touchpad 309 while cursor 5002 is displayed on application icon 6012-1 (e.g., a photos application icon) of application icon 6012 of home screen 5020 on display 101. For example, the user input corresponds to a press of contact 6030 followed by movement in the direction indicated by the arrow. In some embodiments, the user input corresponds to a request to select and move (e.g., drag) application icon 6012-1 in accordance with the movement of contact 6030 on touchpad 309 (e.g., in the direction indicated by the arrow). In Figure 6R, device 100 has moved application icon 6012-1 to a central portion of display 101 in accordance with the movement of contact 6030. As described above, in response to device 300 detecting the end of user input (e.g., liftoff of contact 6030), application icon 6012-1 is dropped at the location of cursor 5002 at the time the end of user input was detected.

[0215] In FIG. 6S, device 200 displays photo application user interface 5016 over home screen user interface 5010. Photo application user interface 5016 includes multiple representations corresponding to photos (e.g., photo objects 5004). In FIG. 6S, device 300 detects user input (e.g., contact 6031) on touchpad 309 while cursor 5002 is displayed over photo object 5004 on photo application user interface 5016. For example, the user input corresponds to a tap on contact 6031 (e.g., a quick touch and lift-off at a location corresponding to contact 6031). In some embodiments, the tap user input corresponds to a request to select and view (e.g., open) photo object 5004. In FIG. 6T, in response to detecting the tap user input, device 200 displays photo 5004 on display 201.

[0216] 6U-6V illustrate user input for displaying a control panel on a first display of a first device, the control panel including multiple affordances for controlling display settings, according to some embodiments. In FIG. 6U, device 200 displays a home screen user interface 5010 including a menu bar 5008. Menu bar 5008 includes multiple indications (e.g., status indications) and multiple affordances, including affordance 5008-1 for the control panel user interface. As used herein, the control panel user interface (also referred to as a control center user interface or control user interface) is used to control multiple system-level operations. The control panel user interface includes multiple controls (e.g., affordances) corresponding to multiple system functions of the device. In FIG. 6U, device 200 detects user input via mouse 202 (e.g., press 6034 on mouse 202) while cursor 5002 is displayed over affordance 5008-1. In some embodiments, the user input corresponds to a request to display a control panel user interface (e.g., control panel user interface 5036 of FIG. 6V). In response to detecting user input via mouse 202, device 200 displays control panel user interface 5036, as shown in FIG. 6V. The control panel user interface includes affordance 5036-1 for controlling wireless networks, affordance 5036-2 for controlling call and notification muting, affordance 5036-3 for controlling keyboard brightness, affordance 5036-4 for display preferences, and affordance 5036-5 for controlling display brightness. It should be understood that these affordances are exemplary and that control panel 5036 may also include a different set of affordances.Affordance 5036-4 for display preferences includes a selectable affordance 5038 for opening a display preferences user interface (e.g., as described with respect to FIG. 7A). Affordance 5036-4 further includes multiple slide affordances (e.g., affordance 5039) for toggling different display modes on and off. For example, in FIG. 6V, the affordance associated with shared input mode (e.g., "Share mouse and keyboard") is turned on, and the affordances associated with extended and mirrored display modes (e.g., "View as Extended Display" and "View as Mirror Display," respectively) are turned off.

[0217] 6W-6X illustrate updating a touchscreen bar of a third device in response to user input on a touchpad of the third device based on where a cursor is displayed when the user input is received, according to some embodiments. In some embodiments, tablet device 300 includes a touchscreen bar (also referred to as a touch bar) (e.g., touchscreen bar 6040 positioned adjacent keyboard 305). As referred to herein, a touchscreen bar is an input device capable of displaying multiple, changing affordances for causing actions on device 300 and / or devices 100 and 200 communicating with device 300. User input on the multiple, changing affordances can be touch gestures, including, for example, taps, swipes, flicks, and drag gestures. In some embodiments, the multiple affordances (e.g., selectable icons) are displayed according to a currently active user interface. For example, if the currently active user interface is an application user interface, the touch screen bar displays a first plurality of affordances for manipulating the application user interface, and if the currently active user interface is a home screen user interface, the touch screen bar displays a second plurality of affordances different from the first set of affordances for manipulating the home screen user interface. In some embodiments, a user interface is determined to be active when a cursor is displayed over the user interface.

[0218] 6W, cursor 5002 is displayed on home screen user interface 5024 of device 300, and touchscreen bar 6040 displays a first set of one or more affordances (e.g., affordance 6040-1 for performing actions on home screen user interface 5024 of device 300). Device 300 detects user input (e.g., contact 6042) on touchpad 309. For example, the user input corresponds to a press by contact 6042 followed by movement in the direction indicated by the arrow. In some embodiments, the user input corresponds to a request to move cursor 5002 in accordance with the movement of contact 6042. In FIG. 6X, cursor 5002 is moved to home screen user interface 5020 of display 101. In response to moving cursor 5002 to a different user interface, touchscreen bar 6040 is updated to display a second set of one or more affordances (e.g., affordance 6040-2 for performing an action on home screen 5020 of device 100).

[0219] 7A-7G illustrate changing the display mode of a first device and a second device communicating with each other by changing the position of the respective representations of the first device and the second device in a display preferences user interface, according to some embodiments. In FIG. 7A, display 201 of desktop device 200 displays a display preferences user interface (e.g., display preferences user interface 7002). In some embodiments, display preferences user interface 7002 is displayed in response to a user input on an affordance in a control panel user interface (e.g., affordance 5038 in control panel user interface 5036 of FIG. 6V). Display preferences user interface 7002 provides affordances for adjusting properties and settings related to the display. In some embodiments, display preferences user interface 7002 includes multiple tabs for adjusting different aspects of the display. For example, tab 7002-1 is for adjusting different aspects of an individual display, tab 7002-2 is for adjusting the placement of the display when the individual display is in communication with one or more displays, and tab 7002-3 is for adjusting the color settings of the individual display.

[0220] FIG. 7A illustrates the contents of tab 7002-2 for adjusting the arrangement of multiple displays. Tab 7002-2 includes representation 7004-A corresponding to desktop device 200 (e.g., named “Joe's Desktop Computer”) and representation 7004-B corresponding to tablet device 100 (e.g., named “Joe's Tablet”). In FIG. 7A, device 200 is communicating with device 100 in shared input mode. Representation 7004-A has a highlighted rim to indicate that representation 7004-A corresponds to display 201 on which display preferences user interface 7002 is currently displayed (e.g., display 201 is the currently active display). Device 200 displays home screen user interface 5010, and device 100 displays home screen user interface 5020. In display preferences user interface 7002, representation 7004-A has a first appearance (e.g., size, shape, picture, or pattern) and representation 7004-B has a second appearance different from the first appearance to indicate that device 200 and device 100 are in shared input mode. In some embodiments, the sizes of representations 7004-A and 7004-B correspond to the relative sizes of displays 200 and 100, respectively. For example, representation 7004-A has a larger size than representation 7004-B because display 201 has a larger size than display 101. In some embodiments, the shapes of representations 7004-A and 7004-B correspond to the shapes of displays 200 and 100, respectively. For example, representation 7004-B has a rectangular shape with a portrait orientation corresponding to the orientation of display 101, and representation 7004-A has a rectangular shape with a landscape orientation corresponding to the orientation of display 201. In some embodiments, the pictures or wallpapers in representations 7004-A and 7004-B correspond to the pictures or wallpapers in displays 200 and 100, respectively.For example, representation 7004-A has a horizontally striped wallpaper that corresponds to the horizontally striped wallpaper of home screen user interface 5010 of device 200, and representation 7004-B has a diagonally striped wallpaper that corresponds to the diagonally striped wallpaper of home screen user interface 5020 of device 100. When in shared input mode, representation 7004-B is separated from representation 7004-B by a distance (e.g., a distance greater than the threshold distance for changing between shared input mode and extended display mode).

[0221] In Figure 7B, device 200 is communicating with device 100 in extended display mode. In contrast to the shared input mode of Figure 7A, both displays 101 and 201 display home screen user interface 5010, including menu bar 5008, provided by device 200. As a result, representation 7004-B has changed its appearance to correspond to the wallpaper of home screen user interface 5010. As shown, representation 7004-B has the same horizontally striped wallpaper as representation 7004-A. Furthermore, in Figure 7B, representation 7004-B is adjacent to (e.g., directly touching) representation 7004-A (e.g., a gap between the representations is not shown).

[0222] 7C , device 200 is communicating with device 100 in mirror display mode. As shown, display 101 of device 100 displays a mirror image or replica of what is displayed on display 201 of device 200. It is understood that because display 101 has a smaller size than display 201, some of the affordances and / or features are displayed at a smaller scale or are excluded. As a result, when in mirror display mode, representations 7004-A and 7004-B are displayed overlapping (e.g., as a stack) in display preferences user interface 7002 (e.g., representation 7004-B is displayed behind representation 7004-A). Representations 7004-A and 7004-B have corresponding appearances to indicate that representation 7004-B is, in fact, a mirror image of representation 7004-A. For example, representations 7004-A and 7004-B have the same size, shape, and include the same horizontally striped wallpaper. 7D-7E illustrate changing the display mode from shared input mode to extended display mode by moving (e.g., dragging) representation 7004-A adjacent to representation 7004-B. In FIG. 7D, device 200 is communicating with device 100 in shared input mode, and display preference user interface 7002 is as described above with respect to FIG. 7A. In FIG. 7D, device 200 detects user input on mouse 202 while cursor 5002 is displayed over representation 7004-B. In some embodiments, the user input corresponds to a press on mouse 202 (e.g., as indicated by a gray dot on mouse 202) followed by movement of mouse 202 in the direction indicated by arrow 7005-A. In some embodiments, the user input corresponds to a request to select and move representation 7004-B according to the mouse movement. In FIG. 7E, device 200 has moved representation 7004-B adjacent to (e.g., directly contacting) representation 7004-A. As a result, device 200 has changed its display mode from shared input mode to extended display mode (eg, as described with respect to FIG. 7B).Additionally, representation 7004-B and display 101 have changed their wallpaper to correspond to the horizontally striped wallpaper of device 200's home screen user interface 5010. In some embodiments, device 200 displays an animation in which representations that are touching each other "snap" (e.g., representation 7004-B slides into contact with representation 7004-A) when representation 7004-B moves a predetermined distance from representation 7004-A. It will be appreciated that the display mode may be changed from extended display mode back to shared input mode following a user input requesting that representations 7004-A and 7004-B be displayed separately from each other (e.g., a user input corresponding to a request to drag representation 7004-B away from representation 7004-A). In FIGS. 7D-7E, changing the display mode is indicated by moving representation 7004-B relative to representation 7004-A while representation 7004-B remains in its original position. However, it should be understood that the display mode may be changed by moving either or both of representations 7004-A and 7004-B.

[0223] In FIG. 7E, device 200 further detects user input on mouse 202 while cursor 5002 is displayed over representation 7004-B. In some embodiments, the user input corresponds to a press on mouse 202 (e.g., as indicated by a gray dot on mouse 202) followed by movement of mouse 202 in the direction indicated by arrow 7005-B. In some embodiments, the user input corresponds to a request to select and move representation 7004-B in accordance with the mouse movement. In FIG. 7F, device 200 continues to detect user input. In FIG. 7F, the user input includes movement of mouse 202 in the direction indicated by arrow 7005-B. While representation 7004-B is being moved and is not in contact with representation 7004-A, devices 200 and 100 are in a shared input mode (e.g., displaying their respective home screen user interfaces). 7G, device 200 has moved representation 7004-B to the opposite side of representation 7004-A in response to movement of mouse 202. In addition, the user has positioned device 100 opposite device 200. As indicated by the positioning and appearance of representations 7004-A and 7004-B, device 200 is now communicating with device 100 in shared input mode.

[0224] 7H-7I illustrate changing the display mode of a first device and a second device communicating with each other using an affordance displayed on a representation of the second device in a display preferences user interface, according to some embodiments. FIGS. 7H-7I illustrate yet another method for changing the display mode of devices 200 and 100 communicating with each other. In FIG. 7H, device 200 displays affordance 7006 for changing the display mode. In FIG. 7H, affordance 7006 for adjusting display preferences corresponding to display 101 of device 100 is displayed over representation 7004-B. Similarly, affordance 7006 may alternatively or additionally be displayed over representation 7004-A for adjusting display preferences corresponding to display 201 of device 100. It will be understood that the display mode may be changed by adjusting the display preferences of either of the displays. In FIG. 7H, device 200 detects user input (e.g., a click) on mouse 202 while cursor 5002 is over affordance 7006. In some embodiments, the user input corresponds to a request to display a drop-down menu containing a set of selectable affordances for selecting a display mode (e.g., "Share Mouse and Keyboard," "Use as External Display," and "Use as Mirror Display"). For example, user input on "Share Mouse and Keyboard" (e.g., clicking on mouse 202 while cursor 5002 is over the desired option) changes the display mode of devices 200 and 100 to shared input mode. User input on "Use as External Display" changes the display mode of devices 200 and 100 to extended display mode, such that display 101 operates as an extended display for displaying a user interface provided by device 200. User input on "Use as Mirror Display" changes the display mode of devices 200 and 100 to mirror display mode, such that display 101 displays a mirror image of display 201.

[0225] 7J-7K illustrate user input on a representation of a device within a display preferences user interface, causing the display of the respective device to provide an indication, according to some embodiments. In some instances, when operating multiple display devices simultaneously, a user may find it difficult to recognize which display is currently displaying cursor 5002, and a method of providing an indication of such a display to the user is useful. In FIG. 7J, device 200 is communicating with devices 300 and 200 in shared input mode. Display preferences user interface 7002 includes representations 7004-A, 7004-B, and 7004-C corresponding to devices 200, 100, and 300, respectively. In FIG. 7J, device 200 detects user input via mouse 202 while cursor 5002 is displayed over representation 7004-B. The user input includes moving mouse 202 in a predetermined motion. For example, the movement includes a circular movement that causes cursor 5002 to move in a circular motion (e.g., cursor 5002 is hovering over representation 7004-B). In response to identifying that the user input includes movement in a predetermined motion and that cursor 5002 is displayed on representation 7004-B, display 101 displays an indication that cursor 5002 is located on display 101. In FIG. 7K, the indication includes a highlighted bezel region 7008 of display 101 (e.g., an area of ​​the display adjacent to a bezel of device 100). In some embodiments, the indication includes increasing the brightness of display 101, a portion of display 101, or a rim of display 101. In some embodiments, the indication is a text notification (e.g., a pop-up window).

[0226] 7L illustrates adjusting the display of different features of a display in a display preferences user interface, according to some embodiments. In FIG. 7L, device 200 displays tab 7002-1 of display preferences user interface 7002 for adjusting different aspects of display 201 of device 200. Tab 7002-1 includes multiple affordances for disabling and enabling certain actions or features available on device 200, such as affordance 7010-1 for displaying a control strip (e.g., as shown in FIG. 7R) for accessing frequently used modifier keys on the touchscreen display, affordance 7010-2 for enabling and disabling a touchscreen bar (e.g., touchscreen bar 6040 shown in FIGS. 6W-6X), affordance 7010-3 for enabling and disabling the use of wireless stylus penwork as an input device (e.g., as shown in FIG. 7R), and affordance 7010-4 for enabling and disabling content casting (e.g., enabling and disabling nearby devices that play content currently playing on the device).

[0227] 7M-7Q illustrate streaming content (e.g., displaying video content) from a display of a second device to a display of a first device when the devices are in shared input mode, according to some embodiments. In FIG. 7M, device 200 is communicating with device 200 in shared input mode. Device 100 is playing video content in video user interface 7012. Video user interface 7012 includes a set of controls, such as affordance 7012-1 for turning off the video content, affordance 7014-2 for playing the video content, affordance 7014-3 for pausing the video content, and affordance 7014-4 for casting the currently playing video content to a different device in communication with device 100. In FIG. 7M, device 100 detects user input (e.g., a tap gesture) on affordance 7014-4 to enable casting the video content to the different device. In response to a tap gesture on affordance 7014-4, device 100 displays a user interface including affordance 7016 for selecting a device to which content will be cast. In FIG. 7N , device 100 detects that device 200 identified as “Joe's Desktop Computer” has been selected. In response to the selection, device 200 streams the video content displayed by device 100 (e.g., displays 101 and 201 simultaneously play the same video content). Such streaming allows the user to enjoy watching the video content from device 100 on the larger-sized display of device 200. While device 200 is streaming video content, other operations of device 200 are set to a locked mode. For example, when in locked mode, performing any operation on device 200 other than streaming video content requires obtaining authentication information from the user (e.g., through passcode entry or biometric verification).7O, device 200 detects user input (e.g., a keystroke via contact 7018) corresponding to a request to unlock device 200. In response to detecting the user input, device 200 ceases displaying video content on video user interface 7012. Instead, device 200 displays a lock screen user interface (e.g., lock screen user interface 7020) that includes an affordance for entering a passcode (e.g., passcode entry affordance 7022). In some embodiments, the device obtains biometric information from the user (e.g., fingerprint or facial recognition) to unlock device 100. In response to obtaining the passcode (e.g., by entering the passcode via user input on keyboard 203), device 200 dismisses lock screen user interface 7020 and displays home screen user interface 5010, as shown in FIG. 7Q.

[0228] FIG. 7R shows a second display displaying a control strip and receiving input via a stylus input device, according to some embodiments. In some embodiments, the control strip and stylus input device are enabled using affordances on the display preferences user interface (e.g., as described above with respect to FIG. 7L). In FIG. 7R, device 100 displays control strip 7028 on display 101. In FIG. 7R, control strip 7028 is a bar positioned along edge 101-1 of display 101. In some embodiments, control strip 7028 may be positioned on any other edge of display 101. Control strip 7028 includes multiple icons corresponding to frequently used modifier controls (e.g., command, option, control, shift, undo, redo). By displaying these frequently used modifier controls on control strip 7029, users can access such controls when operating multiple displays without having to navigate embedded menus to access these controls. 7R, device 100 also displays photo application user interface 7024 and detects user input via stylus 7026. In some embodiments, stylus 7026 operates as an input device (e.g., as a wireless pen). When the stylus is in physical contact with display 101 and is dragged along display 101 or moved a predetermined distance above the display (e.g., a hover movement where the cursor is above the display but not touching the display), cursor 5002 follows the movement of stylus 7026. In some embodiments, stylus 7026 is used to control the movement of cursor 5002 (e.g., instead of a mouse or touch contact with the user's finger controlling the movement of cursor 5002).

[0229] 7S-7T illustrate user input on a second display (e.g., a touchscreen) of a second device causing an action on a first display of a first device, according to some embodiments. In some embodiments, when a mobile device is communicating with a desktop or laptop device in shared input mode, the action on the desktop or laptop device can be implemented by touch gesture input received on a touch-sensitive display of the mobile device (e.g., a tablet device or a mobile phone device). In FIG. 7S, device 200 is communicating with device 100 in shared input mode. In FIG. 7S, cursor 5002 is displayed over an application icon (e.g., photo application icon 5006-1) on dock 5006. While cursor 5002 is displayed over photo application icon 5006-1, device 100 detects touch input (e.g., contact 7030) on display 101 (e.g., a touch-sensitive display). For example, the touch input of contact 7030 corresponds to a tap gesture. In some embodiments, the touch input of contact 7030 corresponds to a request to select and display an application corresponding to application icon 5006-1 over which cursor 5002 is displayed. In FIG. 7T , in response to detecting the touch input on display 101 of device 100, device 200 displays photo application 5016. It is understood that, similar to displaying an application user interface in response to a tap gesture while cursor 5002 is over a respective application icon, other operations of device 200 can also be performed in response to gesture input received on display 101 of device 100. For example, gesture input received on display 101 of device 100 can be used to provide a selection on an affordance or to move a user interface object. The operation to be performed is selected based on the gesture input and the location of the cursor when the gesture input was received.

[0230] 7U-7Z illustrate user input on a keyboard that causes a search user interface to be displayed on the first display of the first device or the second display of the second device based on the position of the cursor when the first device and the second device are in shared input mode, according to some embodiments. Generally, a user can conveniently display frequently used user interfaces by providing user input including a keystroke combination. When operating sharing in multi-device input mode, the same user input can be used to display the same frequently used user interface on the device displaying the cursor when receiving the user input. In some embodiments, a keystroke combination (e.g., command+space) causes the device to display a search user interface (e.g., for searching content from the device and / or network). In FIG. 7U, device 200 is communicating with device 100 in shared input mode. In FIG. 7U, device 200 detects user input corresponding to the keystroke combination (e.g., contact 7032 corresponding to simultaneously pressing command and space keystrokes). User input is detected while cursor 5002 is displayed on display 101 of device 100. In some embodiments, user input including contact 7032 simultaneously pressing command and space keystrokes corresponds to a request to display a search user interface. In response to detecting user input, device 100 displays corresponding text.

[0231] 7U, device 100 displays a search user interface 7034 (e.g., a search input area or search bar) above home screen user interface 5020. While cursor 5002 is displayed on search user interface 7034, device 200 further detects user input (e.g., text user input) corresponding to a text string (e.g., "APPL"). For example, the user input includes multiple keystrokes (e.g., keystroke presses via contacts 7036) corresponding to the search term "APPL," as shown in FIG. 7V. In response to detecting the user input, the corresponding text string is displayed on search user interface 7034.

[0232] In response to receiving the text input at the search user interface 7034, device 100 (e.g., search module 151 of device 100) conducts a search using the text input as search criteria (e.g., optionally together with other contextual information (e.g., time, location, previous searches, past user interactions, etc.) as supplemental search criteria and / or search filters) to identify relevant content that corresponds to the search criteria. In some embodiments, the search is conducted in search corpora corresponding to different sources of content, including content associated with applications installed on the device (e.g., content and / or data within the applications (e.g., files generated or stored within the applications, messages), metadata associated with the applications (e.g., application name, application icon, etc.)), content from external sources (e.g., the Internet, on other associated devices connected to the device, etc.), files stored on the device and / or on a user account associated with the device, etc. In some embodiments, the search is performed in a search corpus corresponding to different categories or content types for search results, including images, photos, videos, media files, contacts with contact information (e.g., names, addresses, usernames, aliases, web addresses, social media handles, etc.), applications, actions or operations that can be performed on the device, etc. In some embodiments, the search is updated as the user types input (e.g., without the user having to select "search" or "back"). In response to detecting a search input (e.g., partial or complete), the search user interface 7034 updates (e.g., refreshes or replaces) with search results (e.g., search results 7038) that correspond to the detected search input, as shown in FIG. 7W. The search results may include content from various applications on device 100 that is identified as relevant to the received search input. In FIG. 7W, the search results include photo objects (e.g., search result 7038 including the photo object "apple.jpeg"). 7X-7Z illustrate a search operation similar to that described with respect to FIGS. 7U-7W, except that in FIG. 7X, while cursor 5002 is displayed on display 201 of device 200, user input (e.g., contact 7032 corresponding to simultaneous pressing of command and space keystrokes) received via keyboard 203 to display a search user interface is detected. In response to the user input detected in FIG. 7X, device 200 displays search user interface 7043 (e.g., a search input area) on display 201, as shown in FIG. 7Y. In some embodiments, search user interface 7034 is displayed over any simultaneously displayed user interface (e.g., photo application user interface 5016 of FIG. 7Y). In FIG. 7Y, device 200 detects the same textual user input (e.g., the text string "APPL") as in FIG. 7V. In response to receiving the textual input at search user interface 7034, device 200 (e.g., search module 151 of device 200) performs a search using the textual input as search criteria, as described above with respect to searches performed by device 100. In response to detecting the search input, search user interface 7034 updates with search results (e.g., search results 7040) corresponding to the detected search input, as shown in Figure 7Z. In Figure 7Z, the search results include content from various applications on device 200 that are identified as relevant to the received search input. In Figure 7Z, the search results include a presentation ("Apple Presentation.key") and a text file ("Apples.txt").

[0233] 8A-8C illustrate user inputs for displaying cursor movement from a middle portion of a first display area of ​​a first computer system to an edge area of ​​the first display area and displaying an indication of the location of a portal for moving user interface objects between the first display area and a second display area of ​​a second computer system, according to some embodiments. In FIG. 8E, desktop device 200 communicates with tablet device 100 and tablet device 100-1. Tablet devices 100 and 100-1 are positioned on opposite sides of display 201 (e.g., device 100 faces edge 201-1 of display 201, and device 100-1 faces edge 201-2 of display 201). As shown, device 200 displays home screen user interface 5010. Device 200 is in sleep mode 6006 (e.g., a power-saving mode or low-power mode). In some embodiments, when in sleep mode, the device turns off (e.g., does not light up) the display, thereby reducing the device's power consumption. In FIG. 8A , device 200 detects user input including movement (e.g., pressing and dragging on mouse 202) in the direction indicated by the illustrated arrow. In some embodiments, the user input corresponds to a request to move cursor 5002 according to movement of mouse 202. In FIG. 8B , device 200 moves cursor 5002 according to movement of mouse 202 toward edge 201-1 (e.g., an edge region corresponding to an area near edge 201-1). In response to movement toward edge 201-1, device 200 facilitates waking up one of the devices with which device 200 is communicating from sleep mode 6006 and begins displaying a lock screen user interface (e.g., lock screen user interface 7020 on display 101) according to a determination of which device is the most recently opened file device.In some embodiments, in accordance with determining the recently opened file device, device 200 provides the recently opened file device with information to wake the recently opened file device from sleep mode 6006 and display lock screen user interface 7020. In some embodiments, the recently opened file device includes a device that most recently detected input from a user or that most recently displayed a cursor. In some embodiments, the recently opened file device is not determined based on receiving or generating a notification (e.g., associated with an application). In FIG. 8B , device 100 is determined to be the most recently active device of devices 100-1 and 100-1, but it is understood that the device could have been device 100-1 (e.g., the relative positions of the devices are not a determining factor for waking up the recently opened file device). In some embodiments, device 100 dismisses lock screen user interface 7020 in response to detecting user input and / or in response to receiving authentication information (e.g., a passcode or biometric information on passcode entry affordance 7022).

[0234] 8C , device 100 has exited speed mode user interface 6006 and is displaying home screen user interface 5020. As described above, when device 100 is displaying home screen user interface 5020 and devices 100 and 200 are communicating directly or indirectly with each other (e.g., in shared input mode or extended display mode), user interface objects can be moved (e.g., dragged) between displays 101 and 201 via portals on the edges of displays 101 and 201. A portal refers to a portion of the edge of each of displays 101 and 201 that enables moving a user interface object between displays 101 and 201 (e.g., any of the operations described above with respect to FIGS. 5A-5T). Following a determination that a user interface object can be moved between displays 101 and 201 via a portal, device 200 displays an indication (e.g., an indication user interface) indicating the location of such portal on display 201 and / or display 101. In some embodiments, the portal indication includes indication 8002-A (e.g., a first portion of the portal indication) displayed along an edge of display 201 (e.g., edge 201-1 of FIG. 8C ) that may be crossed to move a user interface object from display 201 to display 101. In some embodiments, indications 8002-A and 8002-B are displayed while device 100 is in a locked mode. For example, indication 8002-B is displayed on lock screen user interface 7020 of device 100 of FIG. 8B . In some embodiments, indication 8002-A corresponds to indication 5014-A described above with respect to FIGS. 5A-5C .In some embodiments, the indication of the portal includes indication 8002-B (e.g., a second portion of the indication of the portal) displayed along an edge of display 101 (e.g., edge 101-1) that can be traversed to move user interface objects from display 101 to display 101. In some embodiments, indications 8002-A and 8002-B optionally include representations of devices to which the respective portals may be used to drag user interface objects (e.g., representation 8004-A in indication 8002-A corresponding to a photograph representing device 100, and representation 8004-B in indication 8002-B corresponding to a photograph representing device 200). In some embodiments, representation 8004-A is displayed in indication 8002-A, but representation 8004-B is not displayed. In some embodiments, representation 8004-B is displayed in indication 8002-B, but representation 8004-A is not displayed. In some embodiments, indications 8002-A and 8002-B include names of devices to which user interface objects can be dragged using the respective portals. In some embodiments, indications 8002-A and 8002-B have lengths along the edges that correspond to the length of edge 101-1 of display 101, the smaller of the two displays. In some embodiments, indication 8002-A has a first length and indication 8002-B has a second length that is different from the first length. For example, indications 8002-A and 8002-B have lengths that are preset when communication between the devices is established. In some embodiments, indications 8002-A and 8002-B have preset locations along their respective edges when communication between the devices is established. However, as seen in FIG. 8C , in some instances, the locations and / or sizes of indications 8002-A and 8002-B do not match (e.g., are not aligned).In such cases, a cursor or user interface object being dragged between different displays does not move smoothly as projected by the movement of mouse 202. For example, when a cursor moves from a first location on display 201 to a first location on display 201 in accordance with a linear, continuous movement mouse 202, instead of transitioning linearly from the first location on display 201 to the first location on display 101, the cursor jumps between displays. Such behavior can degrade a user's experience operating two displays simultaneously. The operations described with respect to FIGS. 8E-8AJ illustrate means for adjusting the position of a portal to indicate continuous movement of an object between different displays.

[0235] FIG. 8D illustrates an edge region that a cursor can reach to initiate display of an indication of a portal's location, according to some embodiments. In some embodiments, displaying indication 7002-A and / or indication 7002-B is initiated pursuant to a determination that cursor 5002 has been moved to an edge region of the display pursuant to input movement. In FIG. 8D, device 200 detects input on mouse 202 corresponding to a request to move cursor 5002 pursuant to mouse movement. In FIG. 8D, cursor 5002 is being moved from a central portion of display 201 toward edge 201-1 of display 201. In some embodiments, device 200 initiates display of indication 7002-A pursuant to a determination that cursor 5002 has reached edge 201-1 (e.g., cursor 5002 appears to be displayed adjacent to or touching edge 201-1). In some embodiments, device 200 begins displaying indication 7002-A pursuant to a determination that cursor 5002 has reached a threshold distance (e.g., threshold distance T in FIG. 8D ) (e.g., cursor 5002 is at least partially displayed within an edge region extending from edge 201-1 toward the center of display 201 by distance T). In some embodiments, device 200 begins displaying indication 7002-A pursuant to a determination that cursor 5002 has reached a location on edge 201-1 (or an edge region extending from edge 201-1) and remained at that location (e.g., movement of cursor 5002 has been paused) for a duration longer than the threshold duration for initiating display of indication 7002-A. In some embodiments, indication 7002-B is displayed simultaneously with indication 7002-A (e.g., display of indication 7002-B begins simultaneously with the start of display of indication 7002-A). In some embodiments, device 200 generates indications 7002-A and 7002-B.In some embodiments, device 200 provides information to device 100 that causes device 100 to display indication 8002-B at the same time that display 201 displays indication 8002-A.

[0236] 8E-8L illustrate user inputs that change the size and / or location of a portal indication to move a user interface object between different displays, according to some embodiments. In FIG. 8E, device 200 displays indication 8002-A along edge 201-1 of display 201 and indication 8002-B along edge 101-1 of display 101. In FIG. 8E, while displaying cursor 5002 on indication 8002-A, device 200 detects input on mouse 202. In some embodiments, the input includes movement 8006-A in the direction indicated by the arrow. In some embodiments, the input corresponds to a request to move and / or resize indication 5002-A in accordance with movement of mouse 202. In some embodiments, the input corresponds to a request to move and / or resize indication 5002-B in accordance with movement of mouse 202. In some embodiments, the input corresponds to a request to move and / or resize indications 5002-A and 5002-B simultaneously. In some embodiments, the input corresponds to a request to move and / or resize an indication displayed on display 201 or display 101 having a larger size (e.g., display 201 of device 200 has a larger size than display 101 of device 100 in FIG. 8E ). In FIG. 8E , indication 8002-A has size L1 (e.g., size L1 refers to the length of indication 8002-A along edge 201-1), and indication 8002-B has size L2 (e.g., size L2 refers to the length of indication 8002-B along edge 101-1). In some embodiments, size L1 corresponds to size L2 (e.g., L2 corresponds to the overall length of edge 101-1 of device 100). In some embodiments, size L1 is different from size L2 (eg, L1 and L2 are based on a preset length).

[0237] In FIG. 8F, device 200 detects movement 8006-A of mouse 202. In accordance with this movement, cursor 5002 and indication 8002-A are moved downward along edge 201-1 (e.g., the relative position of cursor 5002 on indication 8002-A is maintained). In FIG. 8G, device 200 detects further movement 8006-A of the mouse. In accordance with this movement, cursor 5002 and indication 8002-A are downward along edge 201-1. As shown, indication 8002-A has reached the bottom edge of display 201-1. In response to reaching the bottom edge, device 200 reduces the size of indication 8002-A (e.g., the length along edge 201-1) so that the size of indication 8002-A in FIG. 8G is smaller than size L1 shown in FIG. 8E. 8G , the top edge of indication 8002-A has reached a location that substantially corresponds to the location of the top edge of indication 8002-B in the vertical direction. In some embodiments, in response to determining that the top edge of indication 8002-A has reached the location of the top edge of indication 8002-B in the vertical direction, device 200 retains the top edge of indication 8002-A and the location of the top edge of indication 8002-A (e.g., the location of the top edge is “locked”) unless device 200 detects user input requesting that the location not be retained. For example, device 200 retains the location of the top edge and continues to move the bottom edge of each indication if device 200 continues to detect movement 8006-A of mouse 202. However, in response to detecting movement of the mouse 202 in the opposite direction to movement 8006-A (e.g., the user desires to move cursor 5002 upward), device 200 releases its hold on the location of the top edges of indications 8002-A and 8002-B.

[0238] Even after indication 8002-A reaches the bottom edge of display 201, device 200 detects movement 8006-A (e.g., user input continues in the direction indicated by the arrow). In response, device 200 continues to reduce the size of indication 8002-A while simultaneously providing information to device 100 that causes device 100 to reduce the size of indication 8002-B (e.g., in FIG. 8G , the bottom edge of indication 8002-B is moved up). In some embodiments, device 200 further detects movement of mouse 202 in a direction opposite to the direction of movement 8006-A. In accordance with the movement of mouse 202 in the direction opposite to movement 8006-A, device 200 facilitates resizing and / or changing the location of one or both of indications 8002-A and 8002-B. For example, following movement of mouse 202 in a direction opposite to movement 8006-A, device 200 facilitates increasing the size of indication 8002-A and / or moving indication 8002-A upward along edge 201-1. In some embodiments, the device continues to change the size and / or location of one or both of indications 8002-A and 5002-B following user input, including movement in a direction corresponding to movement of cursor 5002 moving up or down within indication 8002-A. In some embodiments, after an individual indication reaches the top or bottom edge of the display, device 200 increases the size of the individual indication in response to device 200 detecting continued movement of mouse 202 toward or past the reached edge. For example, as shown in FIG. 8G, if indication 8002-A reaches the bottom edge of display 201 and device 200 detects continued movement 8006-A (e.g., the user is attempting to drag indication 8002-A beyond the bottom edge of display 201), device 200 increases the size of indication 8002-A.In some embodiments, displays 201 and 101 display the movement of indications 8002-A and 8002-B as an animation, as described with respect to Figures 8D-8G. For example, the change in size and / or location of indications 8002-A and 8002-B is displayed as a continuous animation.

[0239] In Figure 8H, indications 8002-A and 8002-B have reached corresponding sizes and locations. For example, indication 8002-A has substantially the same size and substantially the same vertical location (e.g., vertical location along parallel edges 201-1 and 101-1) as indication 8002-B. In some embodiments, the location and / or size are maintained by device 200 unless a user interface corresponding to a request not to maintain the location and / or size is detected. In Figure 8H, device 200 detects user input including movement 8006-B having a direction substantially perpendicular to the direction of movement 8006-A. In some embodiments, movement 8006-B corresponds to a request to move cursor 5002 from indication 8002-A to indication 8002-B (e.g., traversing a portal between displays 201 and 101). In accordance with movement 8006-B, device 200 facilitates displaying moving cursor 5002 from indication 8002-A to indication 8002-B, as shown in FIG. 8I. In some embodiments, cursor 5002 has a first appearance on display 201 (e.g., cursor 5002 is an arrow in FIG. 8H) and cursor 5002 has a second appearance on display 101 (e.g., cursor 5002 is a dot in FIG. 8I). In FIG. 8J, device 100 (or alternatively, device 200) detects user input including movement 8006-C. In some embodiments, device 200 and device 100 both communicate with input devices (e.g., mouse 202 and keyboard 203). In some embodiments, input received via the input devices is detected by the respective device that is currently active (e.g., currently displaying cursor 5002). In some embodiments, input received via the input device is detected by device 200, which provides information about the detected input to device 100 and causes device 100 to perform an action on display 101 in accordance with the detected input when cursor 5002 is displayed on display 101.In some embodiments, user input with movement 8006-C corresponds to a request to move cursor 5002 in the direction of movement 8006-C (e.g., upward along indication 8002-C). In FIG. 8K, device 100 detects user input including movement 8006-D. In some embodiments, user input with movement 8006-D corresponds to a request to move cursor 5002 in the direction of movement 8006-D (e.g., downward along indication 8002-C). In some embodiments, moving cursor 5002 up or down within indication 8002-A or indication 8002-B has a first movement resistance (e.g., an obstruction or slowing of movement), and moving cursor 5002 from left to right or right to left so that cursor 5002 exits the respective indication has a second movement resistance. In some embodiments, the second movement resistance is greater than the first movement resistance. In some embodiments, movement resistance refers to slowing or impeding proportional movement of the cursor in response to input movement. For example, the cursor moves proportionally less for a given amount of input movement (e.g., movement of a touch on a touchpad or movement of a mouse) when the resistance is higher than when the resistance is slower. In some embodiments, normal resistance when the mouse 202 moves a distance corresponding to distance X causes the cursor 5002 to move a distance Y on the display. At higher resistance, when the mouse 202 moves distance X, the cursor 5002 moves a distance Z, where distance Z is less than distance Y.

[0240] 8L illustrates providing an indication of the location of the cursor while being displayed within a separate indication for a portal, according to some embodiments. In FIG. 8L, device 100 detects a pause in mouse movement for a duration greater than a threshold duration for display of an indication of an indicator (e.g., indicator 8008) to show the location of cursor 5002. In response to detecting the pause, display 101 displays indication 8008.

[0241] 8M-8Q illustrate user input that causes an animated exit of a cursor from a respective indication for a portal to be displayed, according to some embodiments. In FIG. 8M, device 100 detects user input including movement of mouse 202 in the direction indicated by the arrow (e.g., movement 8006-E). In some embodiments, the user input corresponds to a request to move cursor 5002 away from edge 101-1 of display 101 (e.g., toward the center of display 101). In accordance with mouse 202 movement 8006-E, display 101 displays cursor 5002 moving toward the center of display 101 such that cursor 5002 exits indication 8002-B, as shown in FIGS. 8N-8Q. In some embodiments, display 101 displays an animation that includes enlarging a portion (e.g., portion 8010) as cursor 5002 exits indication 8002-B. 8N and 8O, portion 8010 of indication 8002-B that corresponds to the location of cursor 5002 stretches or expands as cursor 5002 moves toward a central portion of display 101. In FIG. 8P, display 101 displays an instance in which cursor 5002 has left indication 8002-B while portion 8010 of indication 8002-B is still stretched. In FIG. 8, portion 8010 of indication 8002-B does not stretch (e.g., begins to return to its original size) while cursor 5002 is displayed outside of indication 8002-B on home screen user interface 5020 of device 100.

[0242] Following cursor 5002 exiting indication 5002-B, devices 100 and 200 maintain the size and location of the portals corresponding to indications 8002-A and 8002-B. In some embodiments, following a determination that cursor 5002 is no longer displayed over indications 8002-A and 8002-B, displays 201 and 101 cease displaying indications 8002-A and 8002-B while maintaining the size and location of the corresponding portals. As shown in FIG. 8R , displays 201 and 101 may cease displaying indications 8002-A and 8002-B (as indicated by dashed lines) while device 100 detects user input via mouse 202 corresponding to a movement of the location of an application icon on home screen user interface 5020 (e.g., a selection by pressing and dragging with movement 8006-E in the direction indicated by the arrow).

[0243] 8S-8T illustrate moving a user interface object according to input movement from a first display area to a second display area after the display areas are aligned, according to some embodiments. In FIG. 8S, while devices 100 and 200 maintain the size and location of portals corresponding to indications 8002-A and 8002-B and cursor 5002 is displayed over photo object 5004, device 200 detects user input via mouse 202 including movement 8006-F (e.g., a press followed by movement 8006-F of mouse 202 in the direction indicated by the arrow). In some embodiments, the user input corresponds to a request to select and move (e.g., drag) photo object 5004 according to device movement (e.g., as described above with respect to FIGS. 5A-5J). Arrow 8007 in Figures 8S-8T corresponds to the projected movement of cursor 5002 along with photo object 5004 when the positions of the portals on display 101 and display 201 are consistent (e.g., aligned) (e.g., the movement of cursor 5002 and photo object 5004 must be continuous according to continuous movement 8006-F). In Figure 8T, displays 201 and 101 show the movement of cursor 5002 along with photo object 5004 from display 201 to display 101 according to the projected movement indicated by arrow 8007.

[0244] 8U-8V illustrate maintaining a portal after a first display region transitions from a locked state to an unlocked state, according to some embodiments. As described above, devices 200 and 100 maintain the location of a portal for moving user interface objects between displays 201 and 101 after cursor 5002 exits indications 5008-A and 5008-B. In some embodiments, devices 200 and 100 maintain the location of the portal while causing device 200 and / or device 100 to change status. For example, device 200 and / or device 100 can be powered off and back on, or device 200 and / or device 100 can enter a sleep mode (e.g., a power saving mode) or a lock mode and exit the sleep mode or lock mode by beginning to display a home screen user interface or an application user interface. In FIG. 8U, device 200 has entered a lock screen mode (e.g., device 200 requires authentication for an unlock operation of device 200). For example, device 200 may obtain passcode authentication via user input (e.g., contact 8009 providing a passcode on passcode entry affordance 7022 via keyboard 203). In response to obtaining the passcode, device 200 unlocks and displays home screen user interface 5010, as shown in FIG. 8V. In some embodiments, devices 200 and 100 maintain portal positions for moving user interface objects between displays 201 and 101. In some embodiments, displays 201 and 101 display indications 8002-A and 8002-B to indicate the location of the portal (e.g., as shown by dashed line indications 8002-A and 8002-B). In some embodiments, displays 201 and 101 cease displaying indications 8002-A and 8002-B.

[0245] 8W-8AE illustrate changing the position of a second computer system relative to a second computer system and readjusting the portal's indication after changing the relative position, according to some embodiments. In FIG. 8W, device 100 has entered sleep mode 6006. In some embodiments, device 100 enters sleep mode 6006 pursuant to a determination that an event has been detected to trigger entry into sleep mode 6006. In some embodiments, the event is a user input (e.g., a gesture or button press corresponding to a request to transition device 100 into sleep mode 6006). In some embodiments, the event corresponds to a determination that device 100 is not being actively used (e.g., based on the orientation of device 100 (e.g., display 101 facing down or up)) or that device 100 has not detected user input or motion for a duration longer than a threshold duration for entering sleep mode 6006. In some embodiments, while device 100 is in sleep mode 6006, devices 200 and 100 are no longer communicating with each other, either in shared display mode or extended or mirrored display mode. In some embodiments, when an event corresponding to a request to transition device 100 into sleep mode 6006 and the device's display 101 is displaying cursor 5002 (e.g., as shown in FIG. 8T ), cursor 5002 is automatically moved on display 101 of device 200 (e.g., as shown in FIG. 8W ).

[0246] In FIG. 8X, device 100 has been moved to the opposite side of device 100 and rotated approximately 90 degrees. As shown in FIG. 8X, edge 101-3 of display 101 is positioned adjacent to and substantially parallel to edge 201-2 of display 201. Also shown in FIG. 8X is an input unit including a keyboard 8012 and a touchpad 8014 connected (e.g., wired or wirelessly) to device 100. In FIG. 8Y, devices 200 and 100 are in a shared input mode such that devices 200 and 100 share input devices associated with both devices (e.g., touchpad 8014, keyboard 8012, keyboard 203, and mouse 202). In FIG. 8Y, device 100 detects input on touchpad 8014 (e.g., a tap gesture with contact 8016). In some embodiments, the input corresponds to a request to wake device 100 from sleep mode 6006. In response to detecting the input, device 100 displays lock screen user interface 7020 on display 101. In FIG. 8Y, device 100 further detects user input (e.g., a series of keystrokes on keyboard 8012) while cursor 5002 is displayed over passcode entry affordance 7022 to obtain the passcode necessary to unlock device 100. In response to receiving the passcode, device 100 displays home screen user interface 5020 on display 101, as shown in FIG. 8Z.

[0247] In some embodiments, after moving device 100 to a new position relative to device 200 and / or after a status change of device 100 (e.g., transitioning to sleep mode, lock screen mode, and back to displaying home screen user interface 5020), the position of the portal has changed compared to the setting described in FIGS. 8E-8K. Thus, the user may wish to readjust the location of the portal by repeating the actions described above with respect to FIGS. 8E-8L. In FIG. 8Z, device 100 detects user input on touchpad 8014 (e.g., a drag gesture of a contact with movement 8015-A in the direction indicated by the arrow). In some embodiments, the user input corresponds to a request to move cursor 5002, displayed in a central portion of display 101 of device 100, toward edge 101-3. In FIG. 8AA, cursor 5002 has been moved to edge 101-3 (e.g., or within an edge region extending a threshold distance from edge 101-3, as described with respect to FIG. 8E). In some embodiments, cursor 5002 was paused on edge 101-3 for a duration longer than the threshold duration for initiating the display of a portal indication. Thu...

Claims

1. 1. A method comprising: A first computer system having a first display generating component, the first computer system in communication with a first input device and a second computer system having a second display generating component different from the first display generating component, displaying, via the first display generating component, a first user interface in the first display area provided by the first display generating component, the first user interface including displaying a first user interface object at a first location in the first display area; detecting, while displaying the first user interface in the first display area provided by the first display generation component, a first input via the first input device, the first input including a first movement and corresponding to a request to drag the first user interface object across the first display area provided by the first display generation component according to a first portion of the first movement, followed by a request to drag the first user interface object beyond the first display area provided by the first display generation component towards a second display area provided by the second display generation component according to a second portion of the first movement; In response to detecting the first movement, responsive to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component was in communication with the first computer system in a first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; In response to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component is communicating with the first computer system in a second mode different from the first mode, moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; responsive to a determination that the first user interface object is an application window and the first input was detected while the second display generation component was communicating with the first computer system in the first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; the first user interface object is an application window, and in accordance with a determination that the first input was detected while the second display generating component was communicating with the first computer system in the second mode, preventing movement of the first user interface object into the second display area provided by the second display generating component.

2. moving the first user interface object across the second display area includes moving the first user interface object from a first location on the second display area to a second location on the second display area; the method further comprising detecting a second input via the first input device, the second input corresponding to a request to position the first user interface object at the second location, the second location on the second display area being determined according to a location determination of receiving the second input. The method of claim 1.

3. maintaining a display of the first user interface object while the first user interface object is moved across the first display area and the second display area, when the first user interface object is a representation of content; The method of claim 1 or 2, further comprising:

4. when the first user interface object is an application window, maintaining a display of the application window as an open application window while the first user interface object is being moved; The method of any one of claims 1 to 3, further comprising:

5. 5. The method of claim 1, wherein preventing movement of the first user interface object into the second display area comprises automatically moving the first user interface object from the second location back to the first location across the first display area provided by the first display generating component.

6. 6. The method of claim 1, wherein preventing movement of the first user interface object into the second display area comprises pausing the movement of the first user interface object at the second location.

7. The method of any one of claims 1 to 6, wherein the first computer system communicates with the second computer system via a wired connection.

8. The method of any one of claims 1 to 7, wherein the first computer system communicates with the second computer system via a wireless connection.

9. 9. The method of claim 1, wherein the first computer system having the first display generating component is further in communication with a third computer system having a third display generating component different from the first display generating component and the second display generating component.

10. displaying a first visual indication in accordance with a determination that the first user interface object can be moved from the first display area onto the second display area while moving the first user interface object across the first display area provided by the first display generation component; The method of any one of claims 1 to 9, further comprising:

11. displaying a second visual indication different from the first visual indication in accordance with determining that the first user interface object cannot be moved from the first display area onto the second display area; The method of claim 10 further comprising:

12. displaying a third visual indication at a first position in the first display area while moving the first user interface object across the first display area according to the first portion of the first movement in accordance with a determination that a first criterion for moving the first user interface object onto the second display area provided by the second display generation component or onto a third display area provided by a third display generation component is satisfied, the third visual indication indicating that the first user interface object may be moved onto the second display area or the third display area; The method of any one of claims 1 to 11, further comprising:

13. displaying the third visual indication indicating that the first user interface object may be moved onto the second display region at the first position in the first display region and ceasing to display the fourth visual indication indicating that the first user interface object may be moved onto the third display region at the second position in the first display region in accordance with a determination that the first user interface object has a location at a discrete time during the first portion of the first movement that is spatially closer to the second display region provided by the second display generation component than to the third display region provided by a third display generation component; The method of claim 12 further comprising:

14. moving the first user interface object across the second display area provided by the second display generation component in accordance with the determination that the first input was detected while the second display generation component is communicating with the first computer system in the second mode moves the first user interface object to a location on a native user interface of the second computer system; The method according to any one of claims 1 to 13, comprising:

15. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising:

1. A first computer system having the first display generating component, the first computer system in communication with a second computer system having a first input device and a second display generating component different from the first display generating component, displaying, via the first display generating component, a first user interface in the first display area provided by the first display generating component, including displaying a first user interface object at a first location within the first display area; while displaying the first user interface in the first display area provided by the first display generation component, detecting a first input via the first input device, the first input including a first movement and corresponding to a request to drag the first user interface object across the first display area provided by the first display generation component according to a first portion of the first movement, followed by a request to drag the first user interface object beyond the first display area provided by the first display generation component towards a second display area provided by the second display generation component according to a second portion of the first movement; In response to detecting the first movement, responsive to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component was in communication with the first computer system in a first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; In response to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component is communicating with the first computer system in a second mode different from the first mode, moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; responsive to a determination that the first user interface object is an application window and the first input was detected while the second display generation component was communicating with the first computer system in the first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; a first computer system including instructions for preventing movement of the first user interface object into the second display area provided by the second display generation component in accordance with a determination that the first input is detected while the second display generation component is communicating with the first computer system in the second mode, the first user interface object being an application window;

16. 1. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to:

1. A first computer system having the first display generating component, the first computer system in communication with a second computer system having a first input device and a second display generating component different from the first display generating component, displaying, via the first display generating component, a first user interface object in the first display area provided by the first display generating component, including displaying a first user interface object at a first location in the first display area; while displaying the first user interface in the first display area provided by the first display generation component, detecting a first input via the first input device, the first input including a first movement, the first input corresponding to a request to drag the first user interface object across the first display area provided by the first display generation component according to a first portion of the first movement, followed by a request to drag the first user interface object beyond the first display area provided by the first display generation component towards a second display area provided by the second display generation component according to a second portion of the first movement; In response to detecting the first movement, responsive to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component was in communication with the first computer system in a first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; In response to a determination that the first user interface object is a representation of content and the first input was detected while the second display generation component is communicating with the first computer system in a second mode different from the first mode, moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; responsive to a determination that the first user interface object is an application window and the first input was detected while the second display generation component was communicating with the first computer system in the first mode; moving the first user interface object from the first location across the first display area provided by the first display generating component to a second location within the first display area according to the first portion of the first movement; moving the first user interface object across the second display area provided by the second display generation component according to the second portion of the first movement; and preventing movement of the first user interface object into the second display area provided by the second display generation component in accordance with a determination that the first input is detected while the second display generation component is communicating with the first computer system in the second mode, the first user interface object being an application window.

17. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 1 to 14.

18. 15. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to perform the method of any one of claims 1 to 14.

19. 1. A method comprising: A first computer system having a first display generation component, the first computer system in communication with a first input device, displaying, via the first display generation component, a first user interface within a first display area provided by the first display generation component; Detecting a first event that satisfies a first criterion while displaying the first user interface in the first display area provided by the first display generation component; In response to detecting the first event satisfying the first criteria, displaying a respective visual indication of a respective representative spatial position of a user interface generated by a second display generation component of a second computer system; displaying a first visual indication in a first portion of a user interface generated by a first display generation component in accordance with a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a first representative spatial position that can be reached by dragging a user interface object through a first portion of the user interface generated by the first display generation component; displaying a second visual indication in the second portion of the user interface generated by the first display generation component without displaying the first visual indication in the first portion of the user interface generated by the first display generation component in accordance with a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a second representative spatial position that can be reached by dragging a user interface object through a second portion of the user interface generated by the first display generation component; detecting, while the first computer system is sharing the first input device with the second computer system, a first input via the first input device, the first input including a first movement and corresponding to a request to drag a first user interface object across the first display area; In response to detecting the first input, moving the first user interface object across the user interface generated by the first display generation component; and when the first event satisfying the first criteria is detected while the user interface generated by the second display generation component has the respective representative spatial position represented by the respective visual indication, in accordance with a determination that the first input included movement across the first portion of the user interface where the respective visual indication was displayed, moving the first user interface object across the user interface generated by the second display generation component in accordance with the first movement detected via the first input device.

20. 20. The method of claim 19, further comprising: in response to detecting the first event that satisfies the first criterion, ceasing to display the first visual indication in the first portion of the user interface generated by the first display generation component in accordance with a determination that the first computer system does not share the first input device with the second computer system.

21. in response to detecting the first input, when the first event satisfying the first criterion is detected while the user interface generated by the second display generation component has the respective representative spatial position represented by the respective visual indication, canceling movement of the first user interface object across the user interface generated by the second display generation component in accordance with the first movement detected via the first input device in accordance with a determination that the first input did not include movement across the first portion of the user interface where the respective visual indication was displayed; 21. The method of claim 20, further comprising:

22. 22. The method of claim 19, wherein the first visual indication has a first size that indicates a size of an area within which a user interface object may be dragged from the user interface generated by the first display generating component to the user interface generated by the second display generating component.

23. The method of any one of claims 19 to 22, wherein the second computer system is in communication with the first input device.

24. continuing to display the distinct visual indication while moving the first user interface object across the user interface generated by the first display generation component and the user interface generated by the second display generation component; The method of any one of claims 19 to 23, comprising:

25. 25. The method of any one of claims 19 to 24, further comprising a third computer system different from the first computer system and the second computer system, the third computer system in communication with the first computer system and the second computer system, and the first input device connected to the third computer system.

26. displaying a third visual indication in a third portion of the user interface generated by a third display generation component in accordance with a determination that the first computer system shares the first input device with the third computer system and that a user interface generated by a third display generation component of the third computer system has a third representative spatial position that can be reached by dragging a user interface object through a third portion of the user interface generated by the first display generation component; The method of any one of claims 19 to 25, further comprising:

27. 27. The method of any one of claims 19 to 26, wherein the first visual indication is displayed on a portion of a first edge of the first indication generating component and the second visual indication is displayed on a portion of a second edge of the first indication generating component.

28. 28. The method of any one of claims 19 to 27, wherein the first event that satisfies the first criterion comprises the second computer system transitioning from a low power state to an active state.

29. detecting a second input via the first input device, the second input including a second movement corresponding to a request to indicate a location of input focus; In response to detecting the second movement, modifying an appearance of at least a portion of a separate display generating component currently containing the input focus; The method of any one of claims 19 to 28, further comprising:

30. automatically establishing a wireless connection between the first computer system and the second computer system in accordance with a determination that a physical distance between the first computer system and the second computer system is less than a threshold distance; The method of any one of claims 19 to 29, further comprising:

31. the second computer system is in communication with a second input device, the second computer system sharing the second input device with the first computer system; detecting a third input via the first input device or the second input device while displaying a first input focus on a respective one of the first and second display generating components; in response to detecting the third input, performing the first operation on the respective display generation component in accordance with a determination that the third input corresponds to a request to perform a first operation. The method according to any one of claims 19 to 30.

32. Detecting a second event satisfying a second criterion while displaying the first user interface in the first display area provided by the first display generation component; In response to detecting the second event that satisfies the second criteria, displaying, by the first display generation component, a distinct visual indication that the second event has been detected; The method of any one of claims 19 to 31, further comprising:

33. 33. The method of any one of claims 19 to 32, wherein the first user interface in the first display area provided by the first display generation component includes an area for displaying a control user interface, the control user interface including a plurality of affordances for controlling device functions of the first computer system, the control user interface including one or more affordances for controlling whether the first computer system shares the first input device with the second computer system.

34. 34. The method of any one of claims 19 to 33, wherein the first user interface in the first display area provided by the first display generation component includes one or more affordances for enabling and disabling sharing of the first input device with any computer systems physically located within a threshold distance from the first computer system.

35. Detecting a termination of communication between the first input device and the second computer system while displaying the input focus in a second display area provided by the second display generation component; In response to detecting the end of communication, moving the input focus to the first display area provided by the first display generation component in accordance with detecting that the first computer system remains in communication with the first input device; The method of any one of claims 19 to 34, further comprising:

36. the first input device includes a display generating component including a touch-sensitive display screen; displaying, on the touch-sensitive display screen, a first plurality of affordances for controlling the first computer system in accordance with determining that user input provided via the first input device is directed to the first computer system; displaying, on the touch-sensitive display screen, a second plurality of affordances for controlling the second computer system in accordance with determining that user input provided via the first input device is directed to the second computer system. The method according to any one of claims 19 to 35.

37. 37. The method of claim 19, wherein the first user interface in the first display area provided by the first display generation component includes an affordance for display configuration, and the respective representative spatial positions of the user interfaces generated by the second display generation component are determined based on user input on the affordance for display configuration.

38. 38. The method of any one of claims 19 to 37, wherein the respective representative spatial positions of the user interface generated by the second display generation component are determined based on wireless signals between the second computer system and the first input device.

39. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising:

1. The first computer system having the first display generation component, the first computer system being in communication with a first input device, displaying, via the first display generation component, a first user interface within a first display area provided by the first display generation component; Detecting a first event that satisfies a first criterion while displaying the first user interface in the first display area provided by the first display generation component; In response to detecting the first event satisfying the first criteria, displaying a respective visual indication of a respective representative spatial position of a user interface generated by a second display generation component of a second computer system; displaying a first visual indication in a first portion of a user interface generated by a first display generation component in accordance with a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a first representative spatial position that can be reached by dragging a user interface object through a first portion of the user interface generated by the first display generation component; and displaying, in accordance with a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a second representative spatial position that can be reached by dragging a user interface object through a second portion of the user interface generated by the first display generation component, a second visual indication in the second portion of the user interface generated by the first display generation component without displaying the first visual indication in the first portion of the user interface generated by the first display generation component; detecting a first input via the first input device while the first computer system is sharing the first input device with the second computer system, the first input including a first movement and corresponding to a request to drag a first user interface object across the first display area; In response to detecting the first input, moving the first user interface object across the user interface generated by the first display generation component; and, when the first event satisfying the first criteria is detected while the user interface generated by the second display generation component has the respective representative spatial position represented by the respective visual indication, in accordance with a determination that the first input included movement across the first portion of the user interface where the respective visual indication was displayed, moving the first user interface object across the user interface generated by the second display generation component in accordance with the first movement detected via the first input device.

40. 1. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to:

1. The first computer system having the first display generation component, the first computer system being in communication with a first input device, displaying, via the first display generation component, a first user interface within a first display area provided by the first display generation component; detecting a first event satisfying a first criterion while displaying the first user interface in the first display area provided by the first display generation component; In response to detecting the first event satisfying the first criterion, displaying a respective visual indication of a respective representative spatial position of a user interface generated by a second display generation component of a second computer system; pursuant to a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a first representative spatial position that can be reached by dragging a user interface object through a first portion of the user interface generated by the first display generation component, causing a first visual indication to be displayed in the first portion of the user interface generated by the first display generation component; and displaying a second visual indication in the second portion of the user interface generated by the first display generation component without displaying the first visual indication in the first portion of the user interface generated by the first display generation component in accordance with a determination that the first computer system shares the first input device with the second computer system and that the user interface generated by the second display generation component has a second representative spatial position that can be reached by dragging a user interface object through a second portion of the user interface generated by the first display generation component; detecting, while the first computer system is sharing the first input device with the second computer system, a first input via the first input device, the first input including a first movement and corresponding to a request to drag a first user interface object across the first display area; In response to detecting the first input, moving the first user interface object across the user interface generated by the first display generation component; and, when the first event satisfying the first criteria is detected while the user interface generated by the second display generation component has the respective representative spatial position represented by the respective visual indication, moving the first user interface object across the user interface generated by the second display generation component in accordance with the first movement detected via the first input device in accordance with a determination that the first input included movement across the first portion of the user interface where the respective visual indication was displayed.

41. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 19 to 38.

42. 39. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to perform the method of any one of claims 19 to 38.

43. 1. A method comprising: A first computer system having a first display generating component, the first computer system in communication with a first input device and a second computer system having a second display generating component, and displaying, via the first display generation component, within a first display area provided by the first display generation component, a configuration user interface including a first representation of a representative spatial position of a user interface generated by the first display generation component and a second representation of a representative spatial position of a user interface generated by the second display generation component, wherein displaying the configuration user interface includes: displaying, using first visual characteristics, the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component in accordance with a determination that the first computer system and the second computer system are connected in a first mode in which the first display generation component displays a user interface controlled by the first computer system and the second display generation component displays a user interface controlled by the second computer system while the first computer system and the second computer system share the first input device; and displaying, in accordance with a determination that the first computer system and the second computer system are connected in a second mode in which both the first display generation component and the second display generation component display a user interface controlled by the first computer system, the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component using second visual characteristics different from the first visual characteristics.

44. the first representation of the representative spatial position of the user interface generated by the first display generation component corresponds to a first virtual wallpaper, and the second representation of the representative spatial position of the user interface generated by the second display generation component corresponds to a second virtual wallpaper different from the first virtual wallpaper.

44. The method of claim 43.

45. the first virtual wallpaper of the first representation corresponds to wallpaper displayed on the first display generation component, and the second virtual wallpaper of the second representation corresponds to wallpaper displayed on the second display generation component.

45. The method of any one of claims 43 and 44.

46. Detecting a first user input via the first input device; In response to detecting the first user input, displaying an indication on a second display area of ​​a user interface generated by the second display generating component in accordance with a determination that the first user input is over the second representation and that the first user input corresponds to a request to identify a display generating component associated with the second representation; 46. ​​The method of any one of claims 43 to 45, further comprising:

47. 47. The method of claim 46, wherein displaying the indication on the second display area provided by the second display generating component comprises modifying an appearance of a portion of an edge of the second display generating component.

48. displaying, on the first display area provided by the first display generation component, one or more selectable affordances for selecting whether the first computer system and the second computer system are connected in the first mode or the second mode; 48. The method of any one of claims 43 to 47, further comprising:

49. pursuant to a determination that the first display generation component and the second display generation component are connected in the second mode and that the second display generation component is displaying a copy of the user interface generated by the first display generation component, the first representation and the second representation are displayed overlapping one another.

49. The method of claim 48.

50. the second display generation component operates as an extended display for the first display generation component when the first display generation component and the second display generation component are connected in the second mode, and the first display generation component and the second display generation component display content provided by the first computer system.

50. The method of any one of claims 43 to 49.

51. the first computer system communicates with a second input device different from the first input device, and the first computer system and the second computer system share the second input device when connected in the first mode; 51. The method of any one of claims 43 to 50.

52. the second computer system communicates with a third input device different from the first input device, and the first computer system and the second computer system share the first input device and the third input device when connected in the first mode; 52. The method of any one of claims 43 to 51.

53. displaying one or more affordances for controlling functionality of one or more input devices and / or one or more displays in the first display area provided by the first display generation component; 53. The method of any one of claims 43 to 52, further comprising:

54. displaying media content on the first display generation component provided by the first computer system; streaming the media content from the first computer system to the second display generation component provided by the second computer system while the second computer system is in an unlocked access mode; In response to detecting a user input corresponding to a request to operate the second computer system, locking access to the second computer system such that authentication information is required to unlock access to the second computer system; 54. The method of any one of claims 43 to 53, further comprising:

55. detecting a second user input on the configuration user interface via the first input device while displaying the configuration user interface; In response to detecting the second user input, displaying, by the first display generation component, a first notification in accordance with a determination that the second user input corresponds to a request to change the position of the first representation on the configuration user interface; displaying, by the second display generation component, a second notification in accordance with determining that the second user input corresponds to a request to change the position of the second representation on the configuration user interface; and 55. The method of any one of claims 43 to 54, further comprising:

56. In response to detecting the second user input, displaying the first notification by the first display generation component and the second notification by the second display generation component in accordance with the determination that the second user input corresponds to the request to change the position of the first representation or the request to change the position of the second representation on the configuration user interface; 56. The method of any one of claims 43 to 55, further comprising:

57. according to a determination that the second user input corresponds to a request to reduce a space between the first representation and the second representation on the configuration user interface, connecting the first computer system and the second computer system to each other in the second mode such that the space between the first representation and the second representation after reducing the space satisfies a first threshold distance.

57. The method of any one of claims 43 to 56.

58. the second user input corresponds to a request to change the position of the first representation or the second representation; In response to the second user input: connecting the first computer system and the second computer system to each other in the first mode in accordance with a determination that the relative spatial location of the first representation and the second representation satisfies a first criterion after changing the position of the first representation or the second representation; connecting the first computer system and the second computer system to each other in the second mode in accordance with a determination that the relative spatial location of the first representation and the second representation satisfies a second criterion after changing the position of the first representation or the second representation.

58. The method of any one of claims 43 to 57.

59. the second criterion is met when changing the position of the first representation or the second representation reduces the distance between the first representation and the second representation.

59. The method of claim 58.

60. the first criterion is met when moving the first representation or the second representation reduces the distance between the first representations to less than a first threshold distance; 60. The method of claim 59.

61. the first criterion is met when moving the first representation or the second representation increases the distance between the first representation and the second representation; 61. The method of any one of claims 58 to 60.

62. the second criterion is met when moving the first representation or the second representation reduces the distance between the first representations to less than a second threshold distance.

62. The method of claim 61.

63. the second user input corresponds to a combination of a key press and a drag movement via the first input device; 63. The method of any one of claims 43 to 62.

64. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising:

1. A first computer system having the first display generating component, the first computer system in communication with a first input device and a second computer system having a second display generating component, and instructions for displaying, via the first display generation component, a configuration user interface within a first display area provided by the first display generation component, the configuration user interface including a first representation of a representative spatial position of a user interface generated by the first display generation component and a second representation of a representative spatial position of a user interface generated by the second display generation component, wherein displaying the configuration user interface includes: displaying, using first visual characteristics, the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component in accordance with a determination that the first computer system and the second computer system are connected in a first mode in which the first display generation component displays a user interface controlled by the first computer system and the second display generation component displays a user interface controlled by the second computer system while the first computer system and the second computer system share the first input device; a first computer system, comprising: in accordance with a determination that the first computer system and the second computer system are connected in a second mode in which both the first display generation component and the second display generation component display a user interface controlled by the first computer system, displaying the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component using second visual characteristics different from the first visual characteristics.

65. 1. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to:

1. A first computer system having the first display generating component, the first computer system in communication with a first input device and a second computer system having a second display generating component, and displaying, via the first display generation component, within a first display area provided by the first display generation component, a composed user interface including a first representation of a representative spatial position of a user interface generated by the first display generation component and a second representation of a representative spatial position of a user interface generated by the second display generation component; and displaying the composed user interface; displaying, using first visual characteristics, the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component in accordance with a determination that the first computer system and the second computer system are connected in a first mode in which the first display generation component displays a user interface controlled by the first computer system and the second display generation component displays a user interface controlled by the second computer system while the first computer system and the second computer system share the first input device; and displaying, in accordance with a determination that the first computer system and the second computer system are connected in a second mode in which both the first display generation component and the second display generation component display a user interface controlled by the first computer system, the first representation of the representative spatial position of the user interface generated by the first display generation component and the second representation of the representative spatial position of the user interface generated by the second display generation component using second visual characteristics different from the first visual characteristics.

66. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 43 to 63.

67. 64. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to perform the method of any one of claims 43 to 63.

68. 1. A method comprising: A first computer system having a first display generating component and an input device, displaying, via the first display generating component, a visual indication of the location of a portal between a first display area associated with the first display generating component and a second display area associated with a second display generating component, the portal including a portion of the first display area through which user interface objects can be moved between the first display area and the second display area; detecting a first input corresponding to a first movement within the first display area while displaying the visual indication of the portal; In response to detecting the first input, changing a size and / or location of the visual indication of the portal between the first display area associated with the first display generating component and the second display area associated with the second display generating component to indicate a change to the size and / or location of the portal between the first display area associated with the first display generating component and the second display area associated with the second display generating component.

69. detecting, via the input device, a second input in the first display area generated by the first display generation component in communication with the second display generation component prior to displaying the visual indication of the portal; displaying, via the first display generation component, the visual indication of the portal in response to detecting the second input; 69. The method of claim 68, further comprising:

70. 70. The method of claim 69, comprising displaying a first portion of the visual indication of the location of the portal in the first edge region of the first display area in accordance with a determination that the second input comprises a second movement toward the first edge region of the first display area.

71. 71. The method of claim 70, comprising: in accordance with a determination that the second input includes the second movement toward the first edge region of the first display area, a second portion of the visual indication of the portal is displayed in a separate edge region of the second display area selected based on a direction of the second movement.

72. the first computer system in communication with a plurality of candidate devices in communication with corresponding display generation components, including a first candidate device in communication with a first candidate display generation component and a second candidate device in communication with a second candidate display generation component; displaying a visual indication of the portal in the second display area in response to detecting the second input; using the first candidate display generation component to display the second display area in accordance with a determination that the first candidate device is a most recently active candidate device of the plurality of candidate devices; using the second candidate display generation component to display the second display area in accordance with a determination that the second candidate device is a most recently active candidate device of the plurality of candidate devices; 72. The method of claim 70 or 71, comprising:

73. 73. The method of any one of claims 70 to 72, wherein in response to detecting the second input, a display generation component previously in a low power state transitions to an active state to display the second display area.

74. 74. The method of any one of claims 70 to 73, wherein in response to the second input, a visual indication of the portal is displayed in the second display area along with a lock screen of a device associated with the second display area.

75. 75. The method of any one of claims 70 to 74, wherein the visual indication of the portal is displayed in response to detecting a pause in the second movement of the second input having a duration greater than a threshold duration.

76. A method according to any one of claims 70 to 75, wherein the visual indication of a portal is an indicator of where a cursor will move when moved from the first display area to the second display area.

77. 77. The method of any one of claims 68 to 76, wherein a first portion of the visual indication of the location of the portal is displayed in the first display area associated with the first display generation component.

78. 78. The method of claim 77, wherein a second portion of the visual indication of the portal is displayed in the second display area associated with the second display generation component.

79. detecting an additional input comprising movement in a direction from the first display area towards the second display area; In response to detecting the additional input, displaying a cursor moving out of the first display area, where after the cursor is moved out of the first display area based on the additional input from a separate input device, a corresponding cursor moves onto the second display area based on the continuation of the additional input from the separate input device; 79. The method of any one of claims 68 to 78, further comprising:

80. 80. The method of claim 79, wherein the corresponding cursor is displayed at a predetermined position within a second portion of the visual indication of the portal in the second display area.

81. 81. The method of claim 79 or 80, wherein the cursor displayed in the first display area associated with the first display generating component has a first appearance, and the corresponding cursor displayed in the second display area has a second appearance different from the first appearance.

82. 82. A method according to any one of claims 79 to 81, wherein in response to determining that the first movement of the first input has not been detected for a duration longer than a threshold duration, displaying a cursor location indication to indicate a location of the corresponding cursor within the second display area.

83. A method according to any one of claims 79 to 82, wherein the corresponding cursor is displayed within a second portion of the visual indication for the portal in the second display area.

84. 84. The method of any one of claims 79 to 83, wherein movement of the corresponding cursor on the second display area includes a first portion of movement of the corresponding cursor on the second display area within the visual indication of the portal on the second display area having a first resistance to movement, and a second portion of movement of the corresponding cursor on the second display area from within the visual indication of the portal to outside the visual indication of the portal having a second resistance to movement greater than the first resistance to movement.

85. 85. A method according to any one of claims 79 to 84, wherein displaying movement of the cursor from the first display area to the second display area comprises moving the cursor to an edge of the first display area and then ceasing to display the cursor in the first display area.

86. displaying a configuration user interface in the first display region provided by the first display generation component, the configuration user interface including a first representation of a representative spatial position of the first display region generated by the first display generation component and a second representation of a representative spatial position of the second display region generated by the second display generation component; detecting an input corresponding to a request to move the first representation or the second representation while displaying the configuration user interface; displaying the visual indication of the portal in response to detecting the input corresponding to the request to move the first representation or the second representation; 86. The method of any one of claims 68 to 85, comprising:

87. 87. The method of any one of claims 68 to 86, wherein changing the size and / or location of the visual indication of the portal comprises reducing the size of the visual indication of the portal in response to detecting that the visual indication of the portal has moved in accordance with the first movement of the first input, the first movement of the first input being an upward or downward movement that reaches an upper or lower edge of the first display area.

88. 88. The method of any one of claims 68 to 87, wherein changing the size and / or location of the visual indication of the portal comprises changing the location of the visual indication of the portal, including moving the visual indication of the portal along a first edge of the first display area.

89. 89. The method of any one of claims 68 to 88, wherein altering the size and / or location of the visual indication of the portal comprises increasing the size of the visual indication of the portal in response to detecting that the first input corresponds to a request to move the visual indication toward a second edge of the first display area that is non-parallel to the first edge, and wherein the first input continues to attempt to move the visual indication toward the second edge.

90. 90. The method of any one of claims 68 to 89, wherein altering the size and / or location of the visual indication of the portal comprises altering the size of the visual indication of the portal, including displaying a stretching animation of the visual indication of the portal.

91. the first display generation component displays a first portion of the visual indication of the portal in the first display area; a second portion of the visual indication of the portal is displayed in the second display area; changing the size and / or location of the visual indication of the portal includes changing the size and / or location of the first portion or the second portion of the visual indication of the portal.

91. The method of any one of claims 68 to 90.

92. 92. The method of claim 91 , wherein changing the size and / or location of the visual indication of the portal includes changing the location of an individual portion of the first and second portions of the visual indication of the portal, the individual portion of the visual indication of the portal being displayed by a larger display area of ​​the first display area and the second display area.

93. 93. A method according to any one of claims 68 to 92, wherein the first portion of the visual indication of the portal displayed in the first display area and the second portion of the visual indication of the portal displayed in the second display area have a size determined based on the size of the individual display areas of the first display area and the second display area, the smaller of which has a smaller size measured along an individual edge along which the visual indication of the portal is displayed.

94. Detecting a user input corresponding to a first request to move a cursor from the first display area to the second display area via the visual indication of the portal; ceasing to display the visual indication of the portal in response to detecting the user input corresponding to the first request to move the cursor from the first display area to the second display area via the visual indication of the portal; detecting a user input corresponding to a second request to move the cursor between the first display area and the second display area after ceasing to display the visual indication of the portal; in response to detecting the user input corresponding to the second request to move the cursor between the first display area and the second display area, and in accordance with a determination that the user input corresponding to the second request is at a location selected for the portal based on the user input corresponding to a request to move the cursor from within the visual indication of the portal to the second display area, moving the cursor between the first display area and the second display area in accordance with the user input corresponding to the second request; 94. The method of any one of claims 68 to 93, comprising:

95. disconnecting the first display generating component from the second display generating component after determining a location of a portal between the first display area and the second display area; disconnecting the first display generating component and the second display generating component, and then reconnecting the first display generating component and the second display generating component; detecting a request to move a cursor from a display area associated with the first display generating component to a display area associated with the second display generating component after reconnecting the first display generating component and the second display generating component; In response to detecting the request to move the cursor from the display area associated with the first display generation component to the display area associated with the second display generation component, resetting a location of the portal between the display area associated with the first display generating component and the display area associated with the second display generating component in accordance with a determination that the first display generating component and / or the second display generating component satisfy a portal reset criterion; pursuant to a determination that the first display generating component and / or the second display generating component does not satisfy the portal reset criteria, maintaining the portal between the display area associated with the first display generating component and the display area associated with the second display generating component at a location established for the portal before the first display generating component and the second display generating component were disconnected; 95. The method of any one of claims 68 to 94, comprising:

96. a first computer system, a first display generation component; An input device; one or more processors; Memory and and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: displaying, via the first display generating component, a visual indication of the location of a portal between a first display area associated with the first display generating component and a second display area associated with a second display generating component, the portal including a portion of the first display area through which user interface objects can be moved between the first display area and the second display area; detecting a first input corresponding to a first movement within the first display area while displaying the visual indication of the portal; a first computer system including instructions for, in response to detecting the first input, changing a size and / or location of the visual indication of the portal between the first display area associated with the first display generation component and the second display area associated with the second display generation component to indicate a change to the size and / or location of the portal between the first display area associated with the first display generation component and the second display area associated with the second display generation component.

97. 1. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component and an input device, cause the first computer system to: displaying, via the first display generating component, a visual indication of the location of a portal between a first display area associated with the first display generating component and a second display area associated with a second display generating component, the portal comprising a portion of the first display area through which user interface objects can be moved between the first display area and the second display area; detecting a first input corresponding to a first movement within the first display area while displaying the visual indication of the portal; A computer-readable storage medium that, in response to detecting the first input, changes a size and / or location of the visual indication of the portal between the first display area associated with the first display generation component and the second display area associated with the second display generation component to indicate a change to the size and / or location of the portal between the first display area associated with the first display generation component and the second display area associated with the second display generation component.

98. a first computer system, a first display generation component; An input device; one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 68 to 95.

99. 100. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component and an input device, cause the first computer system to perform the method of any one of claims 68 to 95.

100. 1. A method comprising: A first computer system having a display generation component and one or more input devices, In a display area provided by the display generation component, a dock containing multiple icons corresponding to multiple applications; simultaneously displaying a first area and a second area displayed in a split-screen configuration, the first area displaying a first user interface of a first application and the second area displaying a placeholder interface indicating that the second area is available for placement of a user interface of an application other than the first application; detecting a first user input corresponding to a selection of an icon in the dock corresponding to a second application while simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface in the second region; and in response to detecting the first user input, displaying a second user interface of the second application in the second area, wherein the second user interface of the second application is displayed together with the first user interface of the first application in the split screen configuration.

101. displaying the first region and the second region in the split screen configuration includes dividing the display region provided by the display generation component into a first portion and a second portion separated by a divider, the first region filling the first portion on a first side of the divider and the second region filling the second portion on a second side of the divider; Displaying the first user interface of the first application and the second user interface of the second application in the split screen configuration includes filling the first portion of the first side of the divider with the first user interface of the first application and filling the second portion of the second side of the divider with the second user interface of the second application; 101. The method of claim 100, comprising:

102. 102. The method of any one of claims 100 and 101, wherein the placeholder interface includes one or more representations of a user interface of an application other than the first application.

103. 103. The method of claim 102, wherein displaying the second user interface of the second application in the second area includes ceasing to display the one or more representations of a user interface of an application other than the first application in the area of ​​the display area in which the second user interface is displayed.

104. detecting a second user input corresponding to a selection of an icon in the dock corresponding to a third application while simultaneously displaying the dock, the first user interface of the first application in the first region, and the second user interface of the second application in the second region; In response to detecting the second user input, replacing the second user interface of the second application in the second region with a third user interface of the third application, wherein the third user interface of the third application is displayed together with the first user interface of the first application in the split-screen configuration; The method of any one of claims 100 to 103, further comprising:

105. The method of any one of claims 100 to 104, wherein displaying the second user interface of the second application comprises opening the second application from a closed state.

106. 102. The method of claim 100 or 101, further comprising, in accordance with a determination that a third application cannot be displayed in the split screen configuration while simultaneously displaying the dock, the first user interface of the first application in the first region, and either the placeholder interface or the second user interface of the second application in the second region, modifying an appearance of an icon in the dock corresponding to the third application to indicate that the third application cannot be displayed in the split screen configuration.

107. 107. The method of claim 100, wherein displaying the second user interface of the second application in the second area comprises displaying two or more windows associated with the second application, wherein a first window of the two or more windows associated with the second application corresponds to a first user interface for the second application, and a second window of the two or more windows associated with the second application corresponds to a second user interface for the second application, the second user interface for the second application being different from the first user interface for the first application.

108. displaying an additional window affordance in the second region while displaying the two or more windows associated with the second application in the second region; Detecting a user input corresponding to a selection of the additional window affordance; In response to detecting the user input corresponding to a selection of the additional window affordance, displaying an additional window associated with the second application in addition to the two or more windows associated with the second application; and 108. The method of claim 107, further comprising:

109. 109. The method of claim 107 or 108, wherein the two or more windows associated with the second application displayed in the second area include at least one window from a first virtual workspace and at least one window from a second virtual workspace different from the first virtual workspace.

110. 110. The method of claim 100, wherein the placeholder interface in the second region includes a first representation of two user interfaces, the first representation including a fourth user interface of a fourth application and a fifth user interface of a fifth application, the fourth user interface and the fifth user interface being displayed adjacent to one another in the second region in a split-view arrangement within the first representation.

111. detecting a fourth user input corresponding to a selection of a portion of the first representation corresponding to a respective user interface corresponding to a respective application while simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface including the first representations of the two user interfaces in the second region; In response to detecting the fourth user input, displaying in the second area a representation of the individual application, the representation of the individual application being displayed together with the first user interface of the first application in the split-screen configuration; and 111. The method of claim 110, further comprising:

112. Displaying the representation of the individual application together with the first user interface of the first application includes: in accordance with a determination that the fourth user input corresponds to a selection of the fourth user interface of the fourth application, the representation of the respective application being the fourth user interface of the fourth application; and and wherein the representation of the individual application is the fifth user interface of the fifth application in accordance with a determination that the fourth user input corresponds to a selection of the fifth user interface of the fifth application.

113. prior to simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface in the second region; displaying a first window of the first application in a portion of a user interface displayed in at least a portion of the first region and at least a portion of the second region, the first window including a window control affordance that presents a plurality of display configuration option affordances for the first window, the plurality of display configuration option affordances including: a first split screen configuration option affordance corresponding to displaying the first application in the first region in the split screen configuration; a second split screen configuration option affordance corresponding to displaying the first application in the second region in the split screen configuration; and a full screen configuration option affordance corresponding to displaying the first application in at least a portion of the first region and at least a portion of the second region in the full screen configuration; detecting a user input corresponding to a selection of the first split screen configuration option affordance corresponding to displaying the first application in the first region; displaying the first user interface of the first application in the first region and the placeholder interface in the second region in the split screen configuration in response to the detection of the user input corresponding to the selection of the first split screen configuration option affordance.

113. The method of any one of claims 100 to 112.

114. the second user interface of the second application includes a window control affordance corresponding to replacing the second user interface with the placeholder interface in the second region; The method comprises: detecting, in the split-screen configuration, while simultaneously displaying the first user interface of the first application in the first region and the second user interface of the second application in the second region, a fifth user input corresponding to a selection of the window control affordance corresponding to replacing the second user interface in the second region with the placeholder interface; 114. The method of any one of claims 100 to 113, further comprising: in response to detecting the fifth user input, replacing at least a portion of the second user interface in the second region with the placeholder interface.

115. the second user interface of the second application includes a window control affordance corresponding to displaying a window of the second application in at least a portion of the first area and at least a portion of the second area; The method comprises: detecting, in the split-screen configuration, while simultaneously displaying the first user interface of the first application in the first region and the second user interface of the second application in the second region, a sixth user input corresponding to a selection of the window control affordance corresponding to displaying a window of the second application in at least a portion of the first region and at least a portion of the second region; 115. The method of claim 100, further comprising: in response to detecting the sixth user input, displaying a window of the second application in at least a portion of the first area and at least a portion of the second area.

116. the second user interface of the second application includes a window control affordance corresponding to displaying a full-screen user interface of the second application in a full-screen configuration displayed on at least a portion of the first region and at least a portion of the second region; The method comprises: detecting a seventh user input corresponding to a selection of the window control affordance corresponding to displaying a full-screen user interface of the second application in a full-screen configuration displayed in at least a portion of the first region and at least a portion of the second region while simultaneously displaying, in the split-screen configuration, the first user interface of the first application in the first region and the second user interface of the second application in the second region; 116. The method of any one of claims 100 to 115, further comprising: in response to detecting the seventh user input, displaying a full-screen user interface of the second application in a full-screen configuration displayed on at least a portion of the first area and at least a portion of the second area.

117. the full-screen user interface of the second application includes a window control affordance corresponding to displaying the second user interface of the second application in the first region or the second region in the split-screen configuration; The method comprises: detecting an eighth user input corresponding to a selection of the window control affordance corresponding to displaying the second user interface of the second application in the first region or the second region in the split-screen configuration while displaying the full-screen user interface of the second application in the full-screen configuration displayed in at least a portion of the first region and at least a portion of the second region; 117. The method of claim 100, further comprising: in response to detecting the eighth user input, displaying the second user interface of the second application in the first area or the second area in the split screen configuration.

118. detecting a ninth user input corresponding to a search command while simultaneously displaying the first region and the second region in the split screen configuration; In response to detecting the ninth user input, displaying a search field simultaneously with the first area and / or the second area; 118. The method of any one of claims 100 to 117, further comprising:

119. detecting a tenth user input corresponding to a selection of a search result associated with a sixth application while displaying the search field; In response to detecting the tenth user input, displaying a sixth user interface of the sixth application in the second area and displaying the first user interface of the first application in the first area in the split screen configuration; 119. The method of claim 118, further comprising:

120. the second application is a file manager or an application launcher; the second user interface of the second application includes a plurality of application icons; The method comprises: detecting an eleventh user input corresponding to a selection of a first application icon among the plurality of application icons while simultaneously displaying, in the split-screen configuration, the first user interface of the first application in the first region and the second user interface of the second application in the second region; and in response to detecting the eleventh user input, displaying, in the split screen configuration, a seventh user interface of a seventh application corresponding to the first application icon in the second area and displaying the first user interface of the first application in the first area.

120. The method of any one of claims 100 to 119.

121. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: A first computer system having a display generation component and one or more input devices, In a display area provided by the display generation component, a dock containing multiple icons corresponding to multiple applications; simultaneously displaying a first area and a second area displayed in a split-screen configuration, the first area displaying a first user interface of a first application and the second area displaying a placeholder interface indicating that the second area is available for placement of a user interface of an application other than the first application; detecting a first user input corresponding to a selection of an icon in the dock corresponding to a second application while simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface in the second region; a first computer system including instructions for, in response to detecting the first user input, displaying a second user interface of the second application in the second area, the second user interface of the second application being displayed together with the first user interface of the first application in the split-screen configuration.

122. 1. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to: The first computer system having a display generation component and one or more input devices, In a display area provided by the display generation component, a dock containing multiple icons corresponding to multiple applications; simultaneously displaying a first area and a second area displayed in a split-screen configuration, the first area displaying a first user interface of a first application and the second area displaying a placeholder interface indicating that the second area is available for placement of a user interface of an application other than the first application; detecting a first user input corresponding to a selection of an icon in the dock corresponding to a second application while simultaneously displaying the dock, the first user interface of the first application in the first region, and the placeholder interface in the second region; a computer-readable storage medium that, in response to detecting the first user input, causes a second user interface of the second application to be displayed in the second area, the second user interface of the second application being displayed together with the first user interface of the first application in the split-screen configuration.

123. a first computer system, a first display generation component; one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 100 to 120.

124. 121. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a first computer system having a first display generating component, cause the first computer system to perform the method of any one of claims 100 to 120.

Images