Devices, methods, and graphical user interfaces for interacting with user interface objects corresponding to applications

Abstract

The present disclosure relates to devices, methods, and graphical user interfaces for interacting with user interface objects corresponding to applications. The electronic device displays a first home screen user interface including a first subset of application icons. When the first home screen user interface is displayed, the first home screen user interface is replaced with a second home screen user interface in response to detecting a first input that meets a second criterion and corresponds to a request to navigate to the second home screen user interface. When the second home screen user interface is displayed, in response to detecting a second input satisfying a third criterion: replacing the second home screen user interface with a corresponding user interface comprising a representation of a plurality of automatically generated packets of a plurality of applications. Activation of respective representations of respective ones of the plurality of automatically generated packets according to a first criterion causes display of a third subset of application icons.

Description

[0001] This application is a divisional application of the Chinese patent application with the application date of March 10, 2021, application number 202180006856.8, and invention name “Device, method and graphical user interface for interacting with user interface objects corresponding to an application”.

[0002] Priority claim and related applications

[0003] This application is a continuation-of-patent application of U.S. patent application 17 / 027,353, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0004] This application is also a continuation-of-patent application of U.S. patent application 17 / 027,382, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0005] This application is also a continuation-of-patent application of U.S. patent application 17 / 027,400, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0006] This application is also a continuation-of-patent application of U.S. patent application 17 / 027,416, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0007] This application is also a continuation-of-patent application of U.S. patent application 17 / 027,429, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0008] This application is also a continuation-of-patent application of U.S. patent application 17 / 027,441, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0009] This application also claims priority to Danish patent application PA 202070608, filed on September 21, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0010] This application also claims priority to Danish patent application PA 202070636, filed on September 24, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims priority to U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0011] This application also claims priority to Danish patent application PA 202070637, filed on September 24, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims priority to U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0012] This application also claims priority to Danish patent application PA 202070638, filed on September 24, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims the benefit of U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0013] This application also claims priority to Danish patent application PA 202070639, filed on September 24, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims priority to U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Patent Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020.

[0014] This application also claims priority to Danish patent application PA 202070640, filed on September 24, 2020, entitled “Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications,” which claims priority to U.S. Provisional Patent Application 63 / 041,993, filed on June 21, 2020, U.S. Provisional Patent Application 63 / 023,237, filed on May 11, 2020, U.S. Provisional Patent Application 63 / 008,656, filed on April 10, 2020; U.S. Provisional Application 62 / 987,871, filed on March 11, 2020; and U.S. Provisional Patent Application 62 / 987,870, filed on March 10, 2020. Technical Field

[0015] This document generally relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces for displaying and interacting with user interface objects corresponding to applications. Background Art

[0016] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include trackpads and touchscreen displays. Such surfaces are widely used to manipulate user interfaces and objects on displays. Exemplary user interface objects include digital images, videos, text, icons, and control elements (such as buttons), as well as other graphics.

[0017] Exemplary manipulations include adjusting the position and / or size of one or more user interface objects, or activating a button or opening a file / application represented by a user interface object, as well as associating metadata with one or more user interface objects or otherwise manipulating the user interface. Exemplary user interface objects include digital images, videos, text, icons, control elements (such as buttons), and other graphics. In some cases, a user will need to perform such manipulations on user interface objects in: a file management program (e.g., Finder from Apple Inc. (Cupertino, California)); an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc. (Cupertino, California)); a digital content (e.g., video and music) management application (e.g., iTunes from Apple Inc. (Cupertino, California)); a drawing application; a presentation application (e.g., Keynote from Apple Inc. (Cupertino, California)); a word processing application (e.g., Pages from Apple Inc. (Cupertino, California)); or a spreadsheet application (e.g., Numbers from Apple Inc. (Cupertino, California)).

[0018] However, methods for performing these manipulations are cumbersome and inefficient. For example, using a sequence of mouse-based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and places a significant cognitive burden on the user. Furthermore, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-powered devices. Summary of the Invention

[0019] Therefore, there is a need for electronic devices with improved methods and interfaces for displaying and interacting with user interface objects corresponding to different applications. Such methods and interfaces reduce the amount, extent, and / or nature of input from the user and produce a more efficient human-computer interface. For battery-powered devices, such methods and interfaces can conserve power and increase the time between battery charges.

[0020] The disclosed device can reduce or eliminate the above-mentioned defects and other problems associated with the user interface of an electronic device with a touch-sensitive surface. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger contact and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentations, word processing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, fitness support, digital photography, digital video recording, web browsing, digital music playback, note-taking, and / or digital video playback. Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0021] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes: displaying, via the display generation component, a first page of a multi-page home screen user interface, wherein the first page of the multi-page home screen user interface includes a first subset of application icons from a plurality of application icons corresponding to a plurality of applications associated with a computer system, and wherein activating a corresponding application icon from the plurality of application icons, based on a first criterion, causes display of the application corresponding to the corresponding application icon to replace display of the corresponding page of the multi-page home screen user interface on which the corresponding application is displayed. The method also includes, while displaying the first page of the multi-page home screen user interface, detecting a first input that satisfies a second criterion different from the first criterion, the second criterion including the first input indicating a request to navigate through the multi-page home screen user interface in a first direction. The method also includes, in response to detecting the first input that satisfies the second criterion: replacing display of the first page of the multi-page home screen user interface with display of the second page of the multi-page home screen user interface based on a determination that the first input corresponds to a request to navigate to the second page of the multi-page home screen user interface, wherein the second page of the multi-page home screen user interface includes a second subset of the plurality of application icons corresponding to the plurality of applications, the second subset of application icons being different from the first subset of application icons. The method also includes, when displaying a second page of the multi-page home screen user interface, detecting a second input that satisfies a third criterion, the third criterion including that the second input indicates a requirement to navigate through the multi-page home screen user interface in a first direction; in response to detecting the second input that satisfies the third criterion: replacing the display of the second page of the multi-page home screen user interface with the display of a corresponding user interface that includes representations of multiple automatically generated groups of the multiple applications, and wherein activating the corresponding representation of the corresponding automatically generated group of the multiple automatically generated groups according to the first criterion causes the display of a third subset of application icons of the multiple application icons, wherein the third subset of application icons corresponds to at least a subset of the multiple applications that belong to the corresponding automatically generated group of the multiple automatically generated groups.

[0022] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes: displaying a first page of a multi-page home screen user interface, wherein the first page of the multi-page home screen user interface includes a first subset of application icons corresponding to a plurality of applications. The method also includes, while displaying the first page of the multi-page home screen user interface, detecting a first input that satisfies a first criterion; in response to detecting the first input that satisfies the first criterion: displaying the first page of the multi-page home screen user interface in a first reconfiguration mode associated with the multi-page home screen user interface, wherein positions of application icons in the first subset of application icons are adjustable in response to user input detected during the first reconfiguration mode. The method also includes, while displaying the first page of the multi-page home screen user interface in the first reconfiguration mode, detecting a second input that satisfies a second criterion; and in response to detecting the second input, activating a second reconfiguration mode associated with the multi-page home screen user interface, including: simultaneously displaying representations of multiple pages of the multi-page home screen user interface in the first user interface, including a first representation of the first page of the multi-page home screen user interface and a second representation of a second page of the multi-page home screen user interface that is different from the first page of the multi-page home screen user interface.

[0023] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a first user interface, including displaying a plurality of application icons in the first user interface according to a first layout. The method also includes: when the first user interface including the plurality of application icons is displayed according to the first layout, detecting a first input corresponding to a request to insert a first user interface object including application content into the first user interface. The method also includes, in response to detecting the first input corresponding to a request to insert the first user interface object including application content into the first user interface: based on determining that the first input points to a first position corresponding to a first application icon group on the first user interface: moving the first application icon group from the first position to a corresponding position, wherein once the first application icon group has been moved to the corresponding position to create space for the first user interface object including application content at the first position, the first application icon group cannot be directly activated from the first user interface; and displaying the first user interface object including application content at the first position.

[0024] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a first user interface at a first time, wherein: the first user interface includes a placement location configured to spatially accommodate a corresponding user interface object from a plurality of user interface objects corresponding to different applications associated with the placement location; the plurality of user interface objects includes a first user interface object corresponding to the first application and a second user interface object corresponding to a second application different from the first application; and at the first time, displaying the first user interface object at the placement location. The method also includes, at a second time after the first time, displaying the first user interface with the second user interface object displayed at the placement location, wherein the second user interface object is automatically selected for display at the placement location at the second time based on a current context of the device. The method also includes, while displaying the second user interface object at the placement location, detecting a gesture directed at the placement location. The method also includes, in response to detecting the gesture directed at the placement location, replacing display of the second user interface object with a different user interface object from the plurality of user interface objects associated with the placement location based on determining that the gesture is a gesture of the first type.

[0025] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a first user interface, the first user interface including a first placement location associated with a plurality of user interface objects corresponding to different applications, wherein the plurality of user interface objects include a first user interface object that includes information from the first application; a second user interface object that includes information from a second application different from the first application; and a third user interface object that includes information from a third application different from the first and second applications. The method also includes, after displaying the first user interface object corresponding to the first application at the first placement location in the first user interface, detecting the occurrence of a corresponding condition. The method also includes, in response to detecting the occurrence of the corresponding condition, displaying the second user interface object at the first placement location in the first user interface. The method also includes, after displaying the second user interface object at the first placement location in the first user interface, displaying a configuration user interface corresponding to the first placement location, wherein displaying the configuration user interface includes simultaneously displaying at least a portion of a first representation of the first user interface object and at least a portion of a second representation of the second user interface object. The method also includes, while displaying the configuration user interface corresponding to the first placement location, detecting a first user input directed to the corresponding portion of the configuration user interface. The method also includes: in response to detecting a first user input pointing to a corresponding portion of the configuration user interface, based on determining that the first user input satisfies a selection criterion when pointing to a first representation of a first user interface object among the multiple user interface objects shown in the configuration user interface, and the first user input includes a movement that satisfies a first movement criterion, stopping displaying the configuration user interface corresponding to the first placement position and displaying the first user interface object at a second placement position in a second user interface based on the movement of the first user input, wherein the second user interface is different from the configuration user interface, and the second placement position is different from the first placement position.

[0026] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a first page of a multi-page home screen user interface in a first reconfiguration mode, wherein the corresponding positions of a first plurality of application icons in the first page of the multi-page home screen user interface can be adjusted according to user input in the first reconfiguration mode. The method also includes, when the first page of the multi-page home screen user interface is displayed in the first reconfiguration mode, detecting a first input corresponding to a request to enter a second reconfiguration mode from the first reconfiguration mode, wherein the availability of one or more pages in the multi-page home screen user interface can be changed according to user input in the second reconfiguration mode. The method also includes, in response to detecting the first input, replacing the display of the first page of the multi-page home screen user interface in the first reconfiguration mode with the display of corresponding representations of at least two of the multiple pages of the multi-page home screen user interface in the second reconfiguration mode, the corresponding representations including at least a first representation of the first page of the multi-page home screen user interface and a second representation of a second page of the multi-page home screen user interface that is different from the first page of the multi-page home screen user interface. The method further includes, while displaying respective representations of at least two of the plurality of pages of the multi-page home screen user interface in the second reconfiguration mode, the respective representations including a first representation of the first page and a second representation of the second page, detecting a second input. The method further includes, in response to detecting the second input, displaying a second page of the multi-page home screen user interface in the first reconfiguration mode based on a determination that the second input is directed to the second representation of the second page displayed in the second reconfiguration mode and that the second input satisfies a first criterion, wherein respective positions of the second plurality of application icons in the second page of the multi-page home screen user interface are adjustable based on the user input in the first reconfiguration mode.

[0027] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a corresponding page of a home screen user interface, wherein the corresponding page of the home screen user interface includes a first plurality of application icons in a first predefined arrangement. The method also includes detecting a sequence of one or more inputs corresponding to a request to insert a first user interface object into the corresponding page of the home screen user interface, the first user interface object containing a plurality of application icons of a plurality of applications automatically selected by a computer system. The method also includes, in response to detecting the sequence of one or more inputs, simultaneously displaying on the corresponding page of the home screen user interface: two or more application icons of the first plurality of application icons in a first predetermined arrangement, and a second plurality of application icons different from the first plurality of application icons, wherein the second plurality of application icons are automatically placed on the corresponding page of the home screen in a position aligned with the first predefined arrangement of the first plurality of application icons on the corresponding page of the home screen user interface, and the second plurality of application icons are automatically selected by the computer system for inclusion on the corresponding page of the home screen user interface.

[0028] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying a corresponding page of a home screen user interface via the display generation component, wherein the corresponding page of the home screen user interface includes a first plurality of application icons and a first user interface object containing application content corresponding to the corresponding application displayed at a first placement position. The method also includes, when the corresponding page of the home screen user interface is displayed, detecting a first user input corresponding to a request to move the first user interface object containing application content away from the first placement position. The method also includes: in response to detecting the first user input, moving the first user interface object relative to the first placement position in the corresponding page according to the first user input, and based on determining that the first criterion is met, moving the first plurality of application icons located in the first group of placement positions relative to the first placement position of the first user interface object containing application content to follow the movement direction of the first user interface object containing application content.

[0029] According to some embodiments, a method is performed at an electronic device including a display generation component and one or more input devices. The method includes displaying, via the display generation component, a first user interface for selecting a user interface object to place on a home screen user interface of a computer system, wherein the first user interface includes a first user interface object, and the first user interface object includes application content corresponding to a first application. The method also includes, when displaying the first user interface, detecting a first user input pointing to a corresponding position in the first user interface. The method also includes: in response to detecting the first user input pointing to a corresponding position in the first user interface, based on determining that the corresponding position corresponds to the position of the first user interface object, the first user interface object includes application content corresponding to the first application and is preconfigured to have one or more predetermined configuration options corresponding to the first user interface object, and the first user input is an input of a first type, displaying one or more first controls for changing one or more configuration options of the first user interface object to configuration options different from the one or more predetermined configuration options. The method also includes: in response to detecting a first user input pointing to a corresponding location in the first user interface, based on determining that the corresponding location corresponds to the location of a first user interface object, the first user interface object includes application content corresponding to the first application, and the first user input is a second type of input different from the first type of input, displaying the first user interface object in a corresponding user interface different from the first user interface, the first user interface object includes application content corresponding to the first application and one or more predetermined configuration options corresponding to the first user interface object.

[0030] According to some embodiments, an electronic device includes: a display generating component (e.g., a touch screen, a display, a display of a head-mounted device, etc.), a touch-sensitive surface, one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface, one or more optional tactile output generators, one or more processors, and a memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing or causing the execution of operations of any of the methods described herein. According to some embodiments, a non-transitory computer-readable storage medium has instructions stored therein that, when executed by an electronic device having a display generating component (e.g., a touch screen, a display, a display of a head-mounted device, etc.), a touch-sensitive surface, one or more optional sensors for detecting the intensity of contact with the touch-sensitive surface, and one or more optional tactile output generators, causes the device to perform operations of any of the methods described herein or causes operations of any of the methods described herein to be performed. According to some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, a memory, and one or more processors for executing one or more programs stored in the memory includes one or more elements displayed in any of the methods described herein, and the one or more elements are updated in response to input, as described in any of the methods described herein. According to some embodiments, an electronic device includes: a display generating component (e.g., a touch screen, a display, a display of a head-mounted device, etc.), a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators; and a device for performing or causing the operation of any of the methods described herein to be performed. According to some embodiments, an information processing device in an electronic device having a display generating component (e.g., a touch screen, a display, a display of a head-mounted device, etc.), a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators includes a device for performing the operation of any of the methods described herein or causing the operation of any of the methods described herein to be performed.

[0031] Thus, electronic devices having display generating components, a touch-sensitive surface, optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system are provided with improved methods and interfaces for navigating between user interfaces and interacting with control objects, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0033] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0034] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0035] Figure 1C is a block diagram illustrating a tactile output module according to some embodiments.

[0036] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0037] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0038] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.

[0039] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to some embodiments.

[0040] Figures 4C to 4E Examples of dynamic intensity thresholds are shown according to some embodiments.

[0041] Figures 5A1 to 5A36 An exemplary user interface for displaying and interacting with user interface objects corresponding to different applications according to some embodiments is shown.

[0042] Figures 5B1 to 5B19 An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown.

[0043] Figures 5C1 to 5C73 An exemplary user interface is shown for inserting a user interface object containing application content (e.g., a mini-application object, a desktop widget, etc.) into a page of a home screen user interface (e.g., a single page or a multi-page home screen user interface) according to some embodiments.

[0044] Figures 5D1 to 5D12An exemplary user interface is shown for selecting, displaying, and updating a user interface object (e.g., a mini-application object, a desktop widget, etc.) associated with a placement location in a page of a home screen user interface (e.g., a single page or multiple pages of a home screen user interface) containing application content according to some embodiments.

[0045] Figures 5E1 to 5E32 Exemplary user interfaces are shown for interacting with multiple user interface objects (e.g., on a page of a home screen user interface and in a stack-specific configuration user interface, etc.) that contain application content associated with a common placement location (e.g., a desktop widget or stack of mini-application objects, etc.) according to some embodiments.

[0046] Figures 5F1 to 5F30 An exemplary user interface for interacting with multiple pages of a home screen user interface according to some embodiments is shown (e.g., in icon reconfiguration mode, in page editing mode, when switching between the two modes, etc.).

[0047] Figures 5G1 to 5G31 An exemplary user interface for displaying and interacting with a user interface object (e.g., a suggested application widget, a recommended application widget, a recent application widget, etc.) according to some embodiments is shown, wherein the user interface object presents an application icon automatically selected by a computer system at a user-selected location (e.g., on a page of a home screen user interface, at a user-selected placement location on a widget screen, etc.).

[0048] Figures 5H1 to 5H76 Various ways of moving and / or rearranging existing user interface objects (e.g., application icons of various sizes, desktop applets, etc.) corresponding to different applications on a page of a home screen user interface during a reconfiguration mode are shown according to some embodiments (e.g., based on repositioning, deleting, adding, passing, removing, etc., of one or more user interface objects corresponding to different applications).

[0049] Figures 5I1 to 5I18 A user interface is shown for configuring a user interface object containing application content (e.g., a desktop widget, a mini-application object, etc.) and adding the same user interface object to another user interface (e.g., a page of a home screen) according to some embodiments.

[0050] Figures 6A to 6K is a flowchart illustrating a method of displaying and interacting with user interface objects corresponding to different applications, according to some embodiments.

[0051] Figures 7A to 7His a flowchart illustrating a method of reconfiguring a multi-page home screen user interface according to some embodiments.

[0052] Figures 8A to 8M is a flowchart illustrating a method of inserting a user interface object containing application content (e.g., a mini-application object, a desktop widget, etc.) into a page of a home screen user interface according to some embodiments.

[0053] 9A to 9H is a flowchart illustrating a method for selecting, displaying, and updating user interface objects (e.g., mini-application objects, desktop widgets, etc.) associated with a placement location in a page of a home screen user interface, according to some embodiments.

[0054] Figures 10A to 10H is a flowchart illustrating a method for interacting with multiple user interface objects (e.g., widgets or stacks of mini-application objects, etc.) containing application content associated with a common placement location (e.g., on a page of a home screen user interface, in a stack-specific configuration user interface, etc.) according to some embodiments.

[0055] 11A to 11D is a flowchart illustrating a method for interacting with multiple pages of a home screen user interface (e.g., in icon reconfiguration mode, in page editing mode, when switching between the two modes, etc.) according to some embodiments.

[0056] 12A to 12F This is a flowchart showing a method for displaying and interacting with a user interface object (e.g., a suggested application widget, a recommended application widget, a recent application widget, etc.) according to some embodiments, wherein the user interface object presents an application icon automatically selected by a computer system at a user-selected location (e.g., on a page of a home screen user interface, at a user-selected placement location on a widget screen, etc.).

[0057] 13A to 13H is a flowchart illustrating a method for moving and / or rearranging existing user interface objects (e.g., application icons of various sizes, desktop applets, etc.) corresponding to different applications on a page of a home screen user interface during a reconfiguration mode according to some embodiments (e.g., based on repositioning, deleting, adding, passing, removing, etc., of one or more user interface objects corresponding to different applications).

[0058] Figures 14A to 14GThis is a flowchart illustrating a method for configuring a user interface object (e.g., a desktop widget, a mini-application object, etc.) containing application content and adding the same user interface object to another user interface (e.g., a page of a home screen) according to some embodiments. DETAILED DESCRIPTION

[0059] Some methods for displaying and interacting with user interface objects corresponding to different applications, and in particular, for displaying and interacting with application icons corresponding to different applications, typically require multiple separate inputs for a user to manually arrange the application icons into meaningful categories or folders on a user-defined home screen. The user must search for the correct application icon among many other applications on multiple pages of the home screen user interface in order to locate the application icon for the desired application in order to activate the application icon and launch the desired application. Over time, it becomes difficult for the user to keep track of the applications installed on the device, and it becomes increasingly difficult for the user to manually categorize and arrange the application icons on the home screen user interface to allow efficient and easy access to the application icons.

[0060] The following embodiments provide additional system-arranged pages or pages of a home screen user interface that include application icons that are automatically categorized and arranged into automatically generated groups. A user can easily navigate to the system-generated pages of the home screen using the same navigation gestures used to navigate between user-arranged pages of the home screen user interface, and locate the application icon of the desired application based on the characteristics of the desired application (e.g., the application storage category, the time it was installed, etc.). In some embodiments, recently installed applications, recently accessed applications, and / or context-related applications are automatically identified by the operating system and included in corresponding categories (e.g., recently installed, recently accessed, and / or context-suggested categories, etc.) in the system-generated pages of the home screen user interface. In some embodiments, the system-generated home screen also includes user interface objects that include application content, also known as mini-application objects or desktop applets, which provide a limited subset of functionality and / or information available from their corresponding applications without launching the application. In some embodiments, a system-arranged page of a multi-page home screen user interface provides a search input area that allows a user to enter search criteria (e.g., keywords, filters such as applications with recent notifications, applications published by a specific publisher, etc.) and returns applications corresponding to the search criteria (e.g., installed applications and / or applications available from an application store, etc.) as search results. In some embodiments, these search results include application icons that can be interacted with directly, such as launching the corresponding application, dragging and dropping it to a desired location on the user-arranged page of the home screen, and / or deleting it from the device, without the user having to find the application icon in its current location on the user-arranged page of the home screen user interface. In some embodiments, similar capabilities are also provided for application icons shown on the system-arranged home screen. In some embodiments, system-generated groups are represented as large folder icons on the system-arranged page of the home screen user interface, with the respective large folder icons corresponding to the respective groups, and when activated, displaying application icons (or copies or links thereof) for multiple (e.g., some or all) applications from the user-arranged page of the home screen user interface, which are assigned to the respective groups represented by the large folder icons. The system-generated representation of the group (e.g., a large folder icon) optionally includes miniature versions of application icons corresponding to at least a subset of applications included in the group (e.g., applications with unread notifications or badges, recently accessed applications, etc.) and folder launch icons. When a corresponding miniature application icon is activated (e.g., by a tap input, a double-click input, etc.), the computer system launches the corresponding application of the corresponding miniature application icon.When activated (e.g., by a tap input, a double-click input, etc.), the folder launch icon displays the folder contents, including application icons corresponding to the applications in the corresponding groupings. In some embodiments, the application icons and groups included in the system-arranged pages of the multi-page home screen user interface are not changed by the user's input, or at least are not changed in the same way that they might be changed (e.g., deleted, moved, etc.) in the user-arranged pages of the home screen user interface. In some embodiments, the system-arranged pages are presented as pages of the multi-page home screen user interface with corresponding page indicator icons, which indicate their sequential position in the sequence of pages of the multi-page home screen user interface. In some embodiments, the system-arranged pages are presented as user interface overlays or separate user interfaces (e.g., application library user interfaces) that do not have corresponding page indicator icons among the page indicator icons of the user-arranged pages of the multi-page home screen user interface. In some embodiments, regardless of the appearance of the system-arranged pages of the home screen user interface, the system-arranged pages of the home screen user interface are accessed and displayed in response to the same type of page navigation input used to navigate between the user-arranged pages of the multi-page home screen user interface.

[0061] Some methods of configuring pages of a multi-page home screen user interface involve the user laboriously moving application icons to different pages of the home screen or to a new page of the home screen, and manually deleting all application icons on a page to delete the page. There is also no simple way to arrange the different pages of a multi-page home screen as a whole, or to restore a page or group of application icons after it has been deleted from the multi-page home screen user interface. As disclosed herein, a computer system provides a two-step process for invoking a page editing mode of a multi-page home screen user interface, wherein an icon reconfiguration mode is first invoked on a corresponding page of the multi-page home screen user interface; and when the corresponding page of the multi-page home screen is displayed in the icon reconfiguration mode, user input is optionally detected to activate a page editing mode, in which entire pages of the multi-page home screen user interface can be hidden, rearranged, and / or removed from being included in the multi-page home screen user interface upon exiting the page editing mode. In some embodiments, when in page editing mode, user input is optionally detected to move a previously hidden page out of a preset save area of ​​the page editing user interface, or to mark the previously hidden page as unhidden so that when exiting the page editing mode, the previously hidden page is displayed again in the multi-page home screen user interface. In some embodiments, in page editing mode, a delete input is applied to multiple (e.g., all, some, etc.) hidden pages stored in a preset save area. In some embodiments, hidden pages are not deleted so that they can be easily restored in the future. In some embodiments, the enable indication for entering page editing mode from icon reconfiguration mode is displayed on multiple (e.g., some or all) pages (e.g., system-arranged pages and / or user-arranged pages, etc.) of the multi-page home screen user interface in icon reconfiguration mode, and is optionally displayed at the location of page navigation elements on different pages of the home screen user interface.

[0062] On some computer systems, when a user wishes to insert a widget into a home screen user interface, the insertion will fail or be blocked if the desired placement location is already occupied or if there is insufficient space on the user interface. The user first has to manually clear some space on the user interface, such as by deleting and / or moving some application icons from the user interface. In some cases, even if insertion is possible, it will cause a rearrangement of existing application icons on the user interface and sometimes push some icons at the bottom of a page to the next page, which can cause a cascading effect that undesirably changes the layout on multiple pages of the home screen user interface. As disclosed herein, a computer system automatically moves an application icon group and / or widget currently located at a desired placement location selected by the user for a new widget to a preset location (e.g., a new folder on the current page, a new page of the home screen user interface, etc.), creating the preset location for maintaining the displayed application icon group and / or widget without affecting the layout of other parts of the current page or other existing pages of the multi-page home screen user interface. In some embodiments, when a new widget is dragged around a page before being inserted into the page, only the group of application icons at the current location of the new widget is sent to the corresponding location, so that the user obtains a preview of the final state of the page before committing the change. In some embodiments, when adding a widget to a page of a multi-page home screen user interface, the user can select the widget from the widget selection and configuration user interface, or drag the widget from another location or another page of the home screen user interface and drop it into the desired placement location on the desired page of the home screen user interface. When there is enough space on a page of the home screen user interface, the application icons are offset and shifted on the page to make room for inserting the new widget. In some embodiments, the quick action menu associated with the widget includes a size selector that shows different available sizes for the widget, and the size selection is used to select different sizes of the widget, so that other application icons and / or widgets on the same page of the home screen user interface are adjusted and optionally rearranged. In some embodiments, in addition to the rearrangement of other application icons and / or widgets, some application icons and / or widgets on the page are optionally pushed to predefined locations (e.g., existing or newly created folders or new pages, etc.). In some embodiments, resizing a widget optionally causes the application icons and / or widgets on the page of the home screen user interface to be rearranged according to a block size corresponding to the new size and / or old size of the widget (and optionally, the size and position of other widgets on the same page).

[0063] On some computer systems, the desktop widget displayed at a placement location is fixed and does not automatically switch to a different desktop widget or a desktop widget for a different application. As disclosed herein, desktop widget stacking is implemented so that multiple desktop widgets share the same placement location and these multiple desktop widgets are displayed at different times at the same placement location. In some embodiments, a placement location on a page of a home screen user interface is optionally associated with desktop widgets for multiple different applications, where different subsets of desktop widgets or mini-application objects associated with the placement location are displayed at different times. In some cases, the computer system automatically updates (e.g., without user input) the selection of desktop widgets to be displayed at the placement location at the current time based on the current context. In addition, the computer system also updates which desktop widget or mini-application object is displayed at the placement location in response to user input (e.g., a swipe input). In some embodiments, different numbers of desktop widgets are optionally displayed simultaneously at the placement location, depending on whether the current context is clear enough to recommend a single mini-application object or multiple mini-application objects at the placement location. In many respects, the behavior of desktop widgets on the home screen user interface is similar to that of application icons on the home screen. For example, in response to the same input type required to trigger these functions on the application icon, the application icon launches the application, displays a quick action menu and / or triggers an icon reconfiguration mode, etc. The desktop widget on the home screen user interface behaves differently because it takes up a larger space, causing the application icon and other existing desktop widgets to shift on the home screen in a different manner than the application icon. Desktop widgets can be stacked at the same placement position and can be automatically rotated through the placement position by the computer system without user input, and provide useful functions and information from the applications corresponding to these desktop widgets without launching the application. In some embodiments, when the computer system automatically updates the currently displayed desktop widget at the placement position of the desktop widget stack, the computer system provides a visual indication of the information in the newly displayed desktop widget, which visual indication helps select the desktop widget for display at the current moment. In some embodiments, the information that helps automatically select the desktop widget for display at the placement position of the desktop widget stack is visually highlighted relative to other information of the desktop widget.

[0064] Some methods of browsing a list of applications with available widgets and selecting a widget from the list to place in a fixed location on the widget screen are rigid and cumbersome. It is difficult for users to discover useful widgets and find an easy way to add the widget to a desired location on a page of a home screen user interface. As disclosed herein, a widget stack includes multiple widgets displayed at the same placement location at different times. A stack-specific configuration user interface includes representations of multiple (e.g., some, all, each, etc.) widgets in the widget stack. In addition to providing configuration options and entry points for additional configuration options for the widgets in the stack, the stack-specific configuration user interface serves a dual purpose and provides widget selection functionality and a configuration user interface for the widgets in the stack, wherein in response to selecting one or more widgets and then a request corresponding to adding the widget to a page of the home screen user interface (e.g., tapping the Add Widget affordance, dragging the widget from the stack-specific configuration user interface, and dropping it at a desired location on a page of the home screen user interface), one or more widgets can be added to a default location or a user-selected location. In some embodiments, dragging a widget away from a stack-specific configuration user interface removes the widget from the stack (e.g., adds the widget to another user-selected location, or optionally, without adding it to another location). In some embodiments, the representations of the widgets in the stack-specific widget configuration user interface are reordered in response to user input that results in a reordering of the widgets in the stack. In some embodiments, the representations of the widgets in the stack-specific widget configuration user interface are scaled-down images of the widget and include current application data. In some embodiments, these representations visually indicate which information in the widget will facilitate automatic selection of the widget as the currently displayed widget at the placement location of the widget stack.

[0065] Some methods provide an entry point to a page editing mode, where a user can manage or delete an entire page of application icons in a home screen user interface without first launching an icon reconfiguration mode and then entering page editing mode while in icon reconfiguration mode. Some methods that provide access to page editing mode also do not provide an entry point to icon reconfiguration mode. Essentially, page editing and icon reconfiguration are decoupled from each other in some computer systems, and switching from one mode to the other involves multiple user inputs, which can be cumbersome and time-consuming. As disclosed herein, a computer system provides an entry point from page editing mode to icon reconfiguration mode, and also provides an entry point from icon reconfiguration mode to page editing mode. Specifically, in response to user input detected when a first page of a home screen user interface is displayed in icon reconfiguration mode, the computer system optionally enters page editing mode, and in response to input directed to a representation of the other page, exits page editing mode and displays another page of the home screen user interface displayed in icon reconfiguration mode. The ability to switch back and forth between page editing mode and icon reconfiguration mode in response to a single input is fast and efficient, and improves the usability of the computer system. In some embodiments, the page editing user interface displayed in the page editing mode includes representations of multiple (e.g., all, some, etc.) user-arranged pages of the main screen user interface, and optionally includes both hidden pages and currently available pages in the same sequence based on the original order of the pages before some pages became hidden. In some embodiments, the order of the pages including the hidden pages is reordered in the main screen user interface by reordering the representations of the pages including the representations of the hidden pages in the page editing user interface. In some embodiments, the layout and scaling of the representations of the pages in the fixed-size page editing user interface are adjusted based on the number of pages present in the main screen user interface. In some embodiments, when a preset number of pages is exceeded in the main screen user interface, the fixed-size page editing user interface becomes a single scrollable page or includes multiple pages.

[0066] On some computer systems, a small number of user-selected application icons may be included in a widget and placed on a page of the Home screen user interface. However, the selection is static and does not change based on the current context. Consequently, the widget's usefulness is limited and, over time, requires significant user maintenance time and effort to remain useful. Furthermore, the widget's position and size may not align with other application icons on the same page, resulting in an unorganized appearance and making the preset configuration of the Home screen user interface difficult to maintain. As disclosed herein, a computer system provides a suggested application widget that includes application icons for multiple applications automatically selected by the computer system based on criteria used to measure the likely relevance of the application to the user given the current context. The suggested application widget can be repositioned by the user during an icon reconfiguration mode and inserted into a user-specified location on a page of the Home screen user interface. When displaying the suggested application widget, the computer system displays the application icons within the suggested application widget, with their size and position matching and aligned with other application icons on the same page to create a uniform and consistent layout, even when the suggested application widgets are displayed at different user-selected placement locations on the page. In some embodiments, the suggested applications widget serves the function of the mini-application gallery and provides a convenient opportunity for the user to find a desired application icon from among the currently displayed application icons in the suggested applications widget, and select the currently displayed application icon in the suggested applications widget and drag it to another location on the same page or a different page of the home screen user interface to add the application icon to the user-selected location (optionally, by selecting and dragging input, and / or dropping input triggering icon reconfiguration mode). In some embodiments, the above-mentioned drag and drop function is only available when the page is in icon reconfiguration mode. In some embodiments, the borders and background of the suggested applications widget are visually weakened when the page is displayed in normal mode, and this becomes more obvious when the page enters icon reconfiguration mode. In some embodiments, the suggested applications widget behaves similarly to other application icons and widgets in that, in response to a preset input for triggering the display of a quick action menu for a user interface object corresponding to an application, the computer system displays a quick action menu for the suggested applications widget. The quick action menu for the suggested application widget includes widget-specific options for the suggested application widget and, optionally, if the entered location corresponds to an application icon, includes application-specific options corresponding to the application icon within the suggested application widget.In some embodiments, application-specific options for an application include an option to hide the application from the suggested application widget (e.g., temporarily, permanently, on the current page or on another page, etc.). As disclosed herein, since the application icon with the suggested application widget is aligned with other application icons on the same page, it is ensured that when the suggested application widget is displayed at different user locations, and when different groups of application icons are presented in user-selected locations, the page containing the suggested application widgets maintains a sequential and organized arrangement, so that it is less likely to cause confusion to the user when positioning the desired application icon on the page, and / or it is less likely to cause problems with rearranging application icons on the page (e.g., adding, deleting, and rearranging application icons and widgets on the page based on additional user input) when the configuration of the page is altered due to subsequent changes. This feature enhances the operability of the device (e.g., by allowing the user to select placement locations for automatically selected application icons while maintaining an organized layout on the page at user-selected locations) and makes the user device interface more efficient (e.g., by reducing user errors when operating / interacting with the device), which extends the battery life of the device (e.g., by helping the user use the device more quickly and efficiently).

[0067] On some computer systems, application icons on a home screen user interface can be arranged arbitrarily based on user input, or arranged in a fixed grid in a predetermined order. When application icons are inserted into or removed from a page of the home screen user interface, the application icons are sequentially rearranged according to the predetermined order. However, these rearrangement methods do not consider the impact on both application icons and user interface objects containing application content on the same page of the home screen user interface. If these objects were allowed to be positioned arbitrarily, the page could quickly become disorganized and difficult to use when objects of different sizes (e.g., application icons and widgets) are moved around, added, and / or removed. This sequential rearrangement of all objects of the same size is not applicable to pages containing objects of different sizes; simply continuing the same rearrangement strategy would result in disorganization and an erroneous ending in the layout of the page. As disclosed herein, various rules for providing visual feedback and rearranging application icons and / or user interface objects containing application content (e.g., widgets) on one or more pages of the home screen user interface are introduced for various situations in which application icons and / or user interface objects containing application content are inserted into, removed from, and / or moved relative to the one or more pages. In some embodiments, rules are executed to avoid clustering that is more likely to cause alignment problems and / or one or more configurations of the page that are more likely to contribute to page disorganization and user confusion over time. In some embodiments, if a user interface object containing application content is inserted into a page, and then user input ends and the user interface object containing application content is actually inserted into the page, and / or then user input selects any particular placement location on the page for the user interface object containing application content, rules are executed to provide visual feedback about how the page will be organized (e.g., by automatically organizing into blocks, reflowing and moving as blocks, etc.). In some embodiments, rules are executed to provide visual feedback about suitable and / or desired placement locations on the page, so that the user becomes aware of such recommendations or restrictions for placement locations once the user interface object containing application content is dragged onto the page, without having to make any unsuccessful attempts to drop the user interface object into an impermissible placement location. These features enhance the operability of the device (e.g., by providing appropriate visual feedback and guidance to the user when the user provides input to reorganize pages of the home screen user interface) and make the user device's interface more efficient (e.g., by reducing user errors when operating / interacting with the device), which extends the device's battery life (e.g., by helping the user use the device more quickly and efficiently).

[0068] On some computer systems, widgets can be added from a user interface to a widget screen user interface that shows a list of applications with available widgets, or a list from a dedicated application for creating a specific type of customized widget (e.g., an application that creates a home screen widget for weather forecasts, an application that creates a widget for saving bookmarks, etc.). These methods do not provide a preview of multiple preconfigured widgets corresponding to different applications in the same user interface, and do not provide an easy means for accessing both configuration options for modifying a preconfigured widget and inserting the preconfigured widget into a user-selected location. As disclosed herein, a widget selection and configuration user interface displays a collection of preconfigured widgets from multiple applications. Widget-specific configuration options for preconfigured widgets and / or widget stacks are accessible from the widget selection and configuration user interface, and preconfigured widgets and / or widget stacks can be added directly to another user interface. As disclosed herein, the widget selection and configuration user interface serves the functionality of a miniature preconfigured widget library and / or widget stack, but also allows access to widget-specific configuration options for preconfigured widgets and / or widget stacks. The widget selection and configuration user interface and the widget-specific configuration user interface optionally display widgets with currently selected configuration options, and real-time data from widgets corresponding to applications. The widget selection and configuration user interface provides a combined functionality of allowing a user to view preconfigured widgets and provide access to configuration options for widgets, and allowing a user to select one or more widgets from the widget selection and configuration user interface or the widget-specific configuration user interface and insert / move them to another user-selected location, which enhances the operability of the device (e.g., by making it easier to discover widgets and add widgets to another location) and makes the user-device interface more efficient (e.g., by helping the user utilize the required inputs to achieve the desired results and reducing user errors when operating / interacting with the device), which improves the battery life of the device (e.g., by helping the user use the device more quickly and efficiently).

[0069] under, Figures 1A to 1C 、 Figure 2 and Figure 3 A description of an exemplary apparatus is provided. Figures 4A to 4B and Figures 5A1 to 5A36 、 Figures 5B1 to 5B19 、 Figures 5C1 to 5C73 、 Figures 5D1 to 5D12 、 Figures 5E1 to 5E32 、 Figures 5F1 to 5F30 、 Figures 5G1 to 5G31 、 Figures 5H1 to 5H76 ,and Figures 5I1 to 5I18 Shown are exemplary user interfaces for displaying and interacting with user interface objects (e.g., application icons, mini-application objects, etc.) corresponding to different applications according to some embodiments, an exemplary user interface for reconfiguring a multi-page home screen user interface, an exemplary user interface for inserting user interface objects (e.g., mini-application objects, desktop widgets, etc.) containing application content into pages of a home screen user interface (e.g., a single page or multiple pages of a home screen user interface), an exemplary user interface for selecting, displaying, and updating user interface objects (e.g., mini-application objects, desktop widgets, etc.) associated with placement locations in pages of a home screen user interface (e.g., a single page or multiple pages of a home screen user interface) containing application content, an exemplary user interface for interacting with multiple user interface objects containing application content associated with a common placement location, and an exemplary user interface for interacting with a home screen user interface. An exemplary user interface for interacting with multiple pages of a home screen user interface (e.g., in icon reconfiguration mode, in page editing mode, and when switching between the two modes, etc.), an exemplary user interface for displaying and interacting with a user interface object that presents an application icon automatically selected by the computer system at a user-selected location, various ways of moving and / or rearranging existing user interface objects corresponding to different applications (e.g., application icons of various sizes, desktop widgets, etc.) on pages of a home screen user interface during a reconfiguration mode (e.g., based on repositioning, deletion, addition, passing, removal, etc. of one or more user interface objects corresponding to different applications), and an exemplary user interface for configuring user interface objects containing application content (e.g., desktop widgets, mini-application objects, etc.) and adding the same application content to another user interface. Figures 6A to 6K 、 Figures 7A to 7H 、 Figures 8A to 8M 、 9A to 9H 、 Figures 10A to 10H 、 11A to 11D 、 12A to 12F 、 13A to 13H and Figures 14A to 14GIt is a flowchart of a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments, a flowchart of a method for reconfiguring a multi-page home screen user interface, a flowchart of a method for inserting a user interface object containing application content into a page of a home screen user interface, a flowchart of a method for selecting, displaying and updating a user interface object associated with a placement location in a page of a home screen user interface containing application content, a flowchart of a method for interacting with multiple user interface objects associated with a common placement location containing application content, a flowchart of a method for interacting with multiple pages of a home screen user interface, a flowchart of a method for displaying and interacting with a user interface object that presents an application icon automatically selected by a computer system at a user-selected location, a flowchart of a method for moving and / or rearranging existing user interface objects corresponding to different applications on a page of a home screen user interface during a reconfiguration mode, and a flowchart of a method for configuring a user interface object containing application content and adding the same application content to another user interface. Figures 4A to 4B and Figures 5A1 to 5A36 、 Figures 5B1 to 5B19 、 Figures 5C1 to 5C73 、 Figures 5D1 to 5D12 、 Figures 5E1 to 5E32 、 Figures 5F1 to 5F30 、 Figures 5G1 to 5G31 、 Figures 5H1 to 5H76 and Figures 5I1 to 5I18 The user interface in Figures 6A to 6K 、 Figures 7A to 7H 、 Figures 8A to 8M 、 9A to 9H 、 Figures 10A to 10H 、 Figures 11A to 11D 、 12A to 12F 、 13A to 13H and Figures 14A to 14G in the process.

[0070] Exemplary devices

[0071] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Numerous specific details are shown in the following detailed description to provide a full understanding of the various described embodiments. However, it will be apparent to those skilled in the art that the various described embodiments may optionally be practiced without these specific details. In other cases, well-known methods, processes, components, circuits, and networks are not described in detail so as not to unnecessarily obscure various aspects of the embodiments.

[0072] It will also be understood that, although in some cases, the terms "first," "second," etc., are used herein to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first contact can be named a second contact, and similarly, a second contact can be named a first contact without departing from the scope of the various described embodiments. Both a first contact and a second contact are contacts, but they are not the same contact unless the context clearly indicates otherwise.

[0073] The terms used in the description of the various embodiments described herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a" and "the" are intended to also include plural forms unless the context clearly indicates otherwise. It will also be understood that the terms "and / or" used herein refer to and encompass any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "includes," "including," "comprises," and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements, and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and / or their groupings.

[0074] As used herein, the term "if" is optionally interpreted to mean "when" followed by "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that" or "if [stated condition or event] is detected" are optionally interpreted to mean "upon determining" or "in response to determining" or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]," depending on the context.

[0075] Embodiments of electronic devices, user interfaces for such devices, and processes associated with using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). iPod and Device. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or trackpads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or trackpads).

[0076] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0077] The device typically supports a variety of applications, such as one or more of the following: a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0078] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports the various applications with a user interface that is intuitive and clear to the user.

[0079] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display system 112 is sometimes referred to as a "touch screen" for convenience, and sometimes simply as a touch-sensitive display. The device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and external ports 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more intensity sensors 165 for detecting intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0080] As used in this specification and 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 a 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 using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" on a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such interpretation of touch by the user will be limited by the user's individualized sensory perception, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the tactile output generated corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or average) user. Providing tactile feedback to the user using tactile output enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0081] In some embodiments, the tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the motion waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0082] When a device generates tactile output with different tactile output patterns (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile output will, in some cases, induce different tactile sensations to a user holding or touching the device. While a user's senses are based on their perception of the tactile output, most users will be able to discern changes in the waveform, frequency, and amplitude of the tactile output generated by the device. Therefore, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different operations have been performed. Thus, tactile output with tactile output patterns designed, selected, and / or arranged to simulate the characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behavior (e.g., oscillation, displacement, acceleration, rotation, extension, etc.); and / or interaction (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and / or any combination thereof) can, in some cases, provide helpful feedback to the user, reducing input errors and improving the user's efficiency in operating the device. In addition, tactile output is optionally generated to correspond to feedback that is unrelated to the simulated physical properties (such as input threshold or object selection). Such tactile output will provide helpful feedback to the user in some cases, which reduces input errors and improves the efficiency of the user's operation of the device.

[0083] In some embodiments, a tactile output with a suitable tactile output pattern serves as a prompt for an event of interest in the user interface or behind the screen in the device. Examples of events of interest include activation of an affordance (e.g., a real or virtual button or toggle switch) provided on the device or in the user interface, the success or failure of a requested operation, reaching or crossing a boundary in the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detecting or recognizing a type of input or gesture, and the like. In some embodiments, a tactile output is provided to serve as a warning or prompt for an upcoming event or result that would otherwise occur unless a change in direction or interrupt input is detected in a timely manner. Tactile output is also used in other contexts to enrich the user experience, improve the accessibility of the device for users with visual or motor difficulties or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. Optionally, the tactile output is compared with audio input and / or visual user interface changes, which further enhances the user's experience when the user interacts with the user interface and / or device, and facilitates better transmission of information about the state of the user interface and / or device, and reduces input errors and improves the efficiency of the user's operation of the device.

[0084] It should be understood that device 100 is merely one example of a portable multifunction device and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown in the drawings are implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.

[0085] Memory 102 optionally includes high-speed random access memory and optionally includes 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 102 by other components of device 100 (such as CPU 120 and peripheral device interface 118) is optionally controlled by memory controller 122.

[0086] Peripherals interface 118 may be used to couple the device's input and output peripherals to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.

[0087] In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0088] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), an intranet, and / or a wireless network (such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN)). The wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), 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.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed on the date of filing of this document.

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

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

[0091] The touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch-sensitive display system 112 and / or sends electrical signals to the touch-sensitive display system. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual outputs or all of the visual outputs correspond to user interface objects. As used herein, the term "indicator" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed to a graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

[0092] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from the user based on tactile and / or haptic contact. The touch-sensitive display system 112 and the display controller 156 (together with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of that contact) on the touch-sensitive display system 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch-sensitive display system 112. In some embodiments, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0093] The touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch-sensitive display system 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch-sensitive display system 112 to detect contact and any movement or interruption thereof. In some embodiments, projected mutual capacitance sensing technology is used, such as the ATmega 2000 from Apple Inc. (Cupertino, California). iPod and Technology found in.

[0094] The touch-sensitive display system 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to contact the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the action desired by the user.

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

[0096] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0097] Device 100 optionally also includes one or more optical sensors 164 . Figure 1A An optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. One or more optical sensors 164 optionally include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The one or more optical sensors 164 receive light projected from the environment through one or more lenses and convert the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the one or more optical sensors 164 optionally capture still images and / or video. In some embodiments, the optical sensor is located on the rear portion of the device 100 opposite the touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still image and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to obtain an image of the user (e.g., for selfies, for video conferencing when the user views other video conference participants on the touch screen, etc.).

[0098] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. One or more contact force sensors 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). One or more contact force sensors 165 receive contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the rear portion of the device 100 opposite the touch-sensitive display system 112 located on the front portion of the device 100.

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

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

[0101] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripherals interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0102] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a tactile feedback module (or instruction set) 133, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 stores device / global internal state 157, as shown in Figures 1A and 1B. Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications, if any, are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch-sensitive display system 112; a sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or orientation information regarding the device's position and / or posture.

[0103] The operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0104] The communication 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 suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are compatible with some of the Apple Inc. (Cupertino, California) iPod and In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to and / or compatible with the 30-pin connector used in some Apple Inc. (Cupertino, California) iPod and A Lightning connector that is the same as, or similar to, and / or compatible with, the Lightning connector used in the device.

[0105] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection (e.g., by a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger press event), determining the strength 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 has been movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact or stylus contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touchpad.

[0106] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger press event and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event. Similarly, taps, swipes, drags, and other gestures of the stylus are optionally detected by detecting a specific contact pattern of the stylus.

[0107] In some embodiments, detecting a finger tap gesture depends on detecting the length of time between a finger press event and a finger lift event, but is independent of detecting the intensity of the finger contact between the finger press event and the finger lift event. In some embodiments, a tap gesture is detected based on determining that the length of time between the finger press event and the finger lift event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of the finger contact during the tap reaches a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can meet a specific input criterion that does not require the characteristic intensity of the contact to meet a given intensity threshold to meet the specific input criterion. For clarity, the finger contact in a tap gesture is generally required to meet a nominal contact detection intensity threshold to detect a finger press event, below which the contact is not detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting contact by a finger or stylus hovering over the touch-sensitive surface, the nominal contact detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0108] The same concepts apply in a similar manner to other types of gestures. For example, a swipe gesture, a pinch gesture, an expand gesture, and / or a long press gesture may be optionally detected based on satisfying criteria that are independent of the intensity of the contacts included in the gesture or that do not require one or more contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts; a zoom gesture is detected based on the movement of two or more contacts toward each other; a zoom gesture is detected based on the movement of two or more contacts away from each other; and a long press gesture is detected based on the duration of a contact on the touch-sensitive surface having less than a threshold amount of movement. Thus, the statement that a particular gesture recognition criterion does not require the intensity of the contacts to meet the corresponding intensity threshold in order to satisfy the particular gesture recognition criterion means that the particular gesture recognition criterion can be satisfied when the contacts in the gesture do not meet the corresponding intensity threshold, and can also be satisfied when one or more contacts in the gesture meets or exceeds the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on determining that a finger down event and a finger up event are detected within a predefined time period, regardless of whether the contact is above or below a corresponding intensity threshold during the predefined time period, and a swipe gesture is detected based on determining that the contact moves by more than a predefined amount, even if the contact is above the corresponding intensity threshold at the end of the contact movement. Even in specific implementations where detection of gestures is affected by the intensity of the contact performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold, or the device delays detection of a tap input when the intensity of the contact is higher), detection of these gestures does not require the contact to reach a particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies), as long as the criteria for recognizing the gesture can be met without the contact reaching the particular intensity threshold.

[0109] In some cases, contact intensity thresholds, duration thresholds, and movement thresholds are combined in various combinations to create heuristic algorithms that distinguish between two or more different gestures directed to the same input element or area, enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria does not require the intensity of a contact to meet the corresponding intensity threshold to meet the particular gesture recognition criteria does not preclude the simultaneous evaluation of other intensity-related gesture recognition criteria to identify other gestures whose criteria are met when the gesture includes a contact with an intensity above the corresponding intensity threshold. For example, in some cases, a first gesture recognition criterion for a first gesture (which does not require the intensity of the contact to meet the corresponding intensity threshold to meet the first gesture recognition criterion) competes with a second gesture recognition criterion for a second gesture (which depends on the contact meeting the corresponding intensity threshold). In such a competition, if the second gesture recognition criterion for the second gesture is met first, the gesture is optionally not recognized as meeting the first gesture recognition criterion for the first gesture. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predefined amount, a deep press gesture is detected instead of a swipe gesture. Conversely, if the contact moves a predefined amount before the contact reaches the corresponding intensity threshold, a swipe gesture is detected instead of a deep press gesture. Even in such cases, the first gesture recognition criterion for the first gesture still does not require the intensity of the contact to meet the corresponding intensity threshold in order to satisfy the first gesture recognition criterion because, if the contact remains below the corresponding intensity threshold until the gesture ends (e.g., a swipe gesture with an intensity that does not increase above the corresponding intensity threshold), the gesture will be recognized as a swipe gesture by the first gesture recognition criterion. Thus, a particular gesture recognition criterion that does not require the intensity of the contact to meet the corresponding intensity threshold in order to satisfy the particular gesture recognition criterion may (A) in some cases ignore the intensity of the contact relative to the intensity threshold (e.g., for a tap gesture) and / or (B) in some cases fail to satisfy the particular gesture recognition criterion (e.g., for a long press gesture) if a set of competing intensity-related gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-related gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input, and in this sense still depends on the intensity of the contact relative to the intensity threshold (e.g., for a long press gesture competing with a deep press gesture for recognition).

[0110] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) 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 soft keys), digital images, videos, animations, etc.

[0111] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying the graphics to be displayed from an application program or the like, along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 156.

[0112] Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to generate tactile output at one or more locations on device 100 using tactile output generator 167 in response to user interaction with device 100.

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

[0114] 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 location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services such as the weather widget, the local yellow pages widget, and the map / navigation widget).

[0115] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

[0116] Contacts module 137 (sometimes called address book or contact list);

[0117] Telephone module 138;

[0118] Video conferencing module 139;

[0119] Email client module 140;

[0120] Instant messaging (IM) module 141;

[0121] Fitness support module 142;

[0122] A camera module 143 for still and / or video images;

[0123] Image management module 144;

[0124] Browser module 147;

[0125] Calendar module 148;

[0126] Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets acquired by the user, and user-created widgets 149-6;

[0127] A widget creator module 150 for forming user-created widgets 149-6;

[0128] Search module 151;

[0129] A video and music player module 152, optionally consisting of a video player module and a music player module;

[0130] Notepad module 153;

[0131] Map module 154; and / or

[0132] Online video module 155.

[0133] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0134] In combination with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers and / or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing 139, email 140, or instant messaging 141; and so on.

[0135] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 includes executable instructions for entering a character sequence corresponding to a phone number, accessing one or more phone numbers in address book 137, modifying an entered phone number, dialing the corresponding phone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0136] In combination with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and phone module 138, video conferencing module 139 includes executable instructions for initiating, conducting, and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0137] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0138] In conjunction with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for phone-based instant messaging or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0139] In combination with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the fitness support module 142 includes executable instructions for creating a workout (e.g., with time, distance, and / or calorie burn goals); communicating with fitness sensors (in sports equipment and smart watches); receiving fitness sensor data; calibrating sensors for monitoring a workout; selecting and playing music for a workout; and displaying, storing, and transmitting fitness data.

[0140] In conjunction with touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, and / or deleting still images or videos from memory 102.

[0141] In conjunction with touch-sensitive display system 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 slideshow or album), and storing still images and / or video images.

[0142] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet (including searching for, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) in accordance with user instructions.

[0143] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0144] In conjunction with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget module 149 is a mini-application that is optionally downloaded and used by the user (e.g., the weather desktop widget 149-1, the stock desktop widget 149-2, the calculator desktop widget 149-3, the alarm desktop widget 149-4, and the dictionary desktop widget 149-5), or a mini-application created by the user (e.g., the user-created desktop widget 149-6). In some embodiments, the desktop widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., the Yahoo! desktop widget).

[0145] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget creator module 150 includes executable instructions for creating a desktop widget (e.g., transferring a user-specified portion of a web page into a desktop widget).

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

[0147] In conjunction with touch-sensitive display system 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 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch-sensitive display system 112 or on an external display wirelessly connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple Inc.).

[0148] In conjunction with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do lists, etc. according to user instructions.

[0149] In combination with RF circuitry 108, touch-sensitive display system 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 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with the maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

[0150] In conjunction with touch-sensitive display system 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, online video module 155 includes executable instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on touch screen 112 or on an external display connected wirelessly or via external port 124), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video.

[0151] Each module and application identified above corresponds to a set of executable instructions for performing one or more functions and methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). These modules (i.e., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-mentioned modules and data structures. In addition, memory 102 optionally stores other modules and data structures not described above.

[0152] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touchpad. By using a touch screen and / or a touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.

[0153] A predefined set of functions that are exclusively performed through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such embodiments, the trackpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

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

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

[0156] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by the application 136-1, a state queue for enabling the user to return to a previous state or view of the application 136-1, and a redo / undo queue of previous actions taken by the user.

[0157] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display system 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information received by peripherals interface 118 from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

[0158] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).

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

[0160] When the touch-sensitive display system 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

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

[0162] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (i.e., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. 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.

[0163] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of 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 an area associated with one particular view, views higher in the hierarchy will still remain actively participating views.

[0164] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue, which is retrieved by corresponding event receiver module 182.

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

[0166] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 is part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application's internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0167] A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event from the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0168] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as touches or touch movements. 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 the movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

[0170] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler that is associated with the sub-event and the object that triggered the hit test.

[0171] In some embodiments, the definition of the corresponding event 187 also includes delay actions that delay the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

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

[0173] In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery for actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0174] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating an event handler 190 is different from sending (and deferred sending) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.

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

[0176] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video or music player module 152. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the location of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

[0177] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0178] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 100, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a trackpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining the event to be recognized.

[0179] Figure 1C is a block diagram illustrating a tactile output module according to some embodiments. In some embodiments, the I / O subsystem 106 (e.g., the tactile feedback controller 161 ( Figure 1A ) and / or one or more other input controllers 160 ( Figure 1A ))include Figure 1C At least some of the example components shown. In some embodiments, the peripheral device interface 118 includes Figure 1C At least some of the example components shown.

[0180] In some embodiments, the tactile output module includes a tactile feedback module 133. In some embodiments, the tactile feedback module 133 aggregates and combines tactile outputs from software applications on the electronic device for user interface feedback (e.g., feedback in response to user input corresponding to the displayed user interface and prompts and other notifications indicating the execution of operations or the occurrence of events in the user interface of the electronic device). The tactile feedback module 133 includes one or more of a waveform module 123 (for providing waveforms for generating tactile outputs), a mixer 125 (for mixing waveforms, such as waveforms in different channels), a compressor 127 (for reducing or compressing the dynamic range of the waveform), a low-pass filter 129 (for filtering out high-frequency signal components in the waveform), and a thermal controller 131 (for adjusting the waveform according to thermal conditions). In some embodiments, the tactile feedback module 133 is included in a tactile feedback controller 161 ( Figure 1A In some embodiments, a separate unit of the tactile feedback module 133 (or a separate specific implementation of the tactile feedback module 133) is also included in the audio controller (e.g., audio circuit 110, Figure 1A ) and used to generate an audio signal. In some embodiments, a single tactile feedback module 133 is used to generate an audio signal and to generate a waveform for a tactile output.

[0181] In some embodiments, the haptic feedback module 133 also includes a trigger module 121 (e.g., a software application, operating system, or other software module that determines that a tactile output is to be generated and initiates a process for generating the corresponding tactile output). In some embodiments, the trigger module 121 generates a trigger signal for initiating (e.g., by the waveform module 123) the generation of a waveform. For example, the trigger module 121 generates the trigger signal based on a preset timing standard. In some embodiments, the trigger module 121 receives the trigger signal from outside the haptic feedback module 133 (e.g., in some embodiments, the haptic feedback module 133 receives the trigger signal from a hardware input processing module 146 located outside the haptic feedback module 133) and relays the trigger signal to other components within the haptic feedback module 133 (e.g., the waveform module 123) or a software application that triggers an operation (e.g., utilizing the trigger module 121) based on activation of a user interface element (e.g., an application icon or enable representation within an application) or a hardware input device (e.g., a primary button or an intensity-sensitive input interface, such as an intensity-sensitive touch screen). In some embodiments, the trigger module 121 also (e.g., from the haptic feedback module 133, Figure 1A and Figure 3 ) receives the tactile feedback generation instruction. In some embodiments, the trigger module 121 responds to the tactile feedback module 133 (or the trigger module 121 in the tactile feedback module 133) (e.g., from the tactile feedback module 133, Figure 1Aand Figure 3 ) receives tactile feedback instructions and generates a trigger signal.

[0182] Waveform module 123 receives a trigger signal as input (e.g., from trigger module 121) and provides a waveform for generating one or more tactile outputs (e.g., a waveform selected from a predefined set of waveforms assigned for use by waveform module 123) in response to receiving the trigger signal.

[0183] The mixer 125 receives waveforms as input (e.g., from the waveform module 123) and mixes the waveforms together. For example, when the mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform in a second channel that at least partially overlaps with the first waveform), the mixer 125 outputs a combined waveform corresponding to the sum of the two or more waveforms. In some embodiments, the mixer 125 also modifies one or more of the two or more waveforms to emphasize a particular waveform relative to the rest of the two or more waveforms (e.g., by increasing the scale of the particular waveform and / or reducing the scale of the other waveforms in the waveforms). In some cases, the mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., when waveforms from more than three sources have been requested to be output simultaneously by the tactile output generator 167, the waveform from the oldest source is discarded).

[0184] Mixer 127 receives waveforms (e.g., combined waveforms from mixer 125) as input and modifies these waveforms. In some embodiments, compressor 127 reduces these waveforms (e.g., based on the tactile output generator 167 ( Figure 1A ) or 357( Figure 3 ) such that the tactile output corresponding to these waveforms is reduced. In some embodiments, compressor 127 limits the waveforms, such as by imposing a predefined maximum amplitude on the waveforms. For example, compressor 127 reduces the amplitude of the waveform portions that exceed a predefined amplitude threshold, while maintaining the amplitude of the waveform portions that do not exceed the predefined amplitude threshold. In some embodiments, compressor 127 reduces the dynamic range of the waveforms. In some embodiments, compressor 127 dynamically reduces the dynamic range of the waveforms such that the combined waveform remains within the performance specifications of tactile output generator 167 (e.g., force and / or movable mass displacement limits).

[0185] Low-pass filter 129 receives a waveform (e.g., a compressed waveform from compressor 127) as input and filters (e.g., smoothes) the waveform (e.g., removes or reduces high-frequency signal components in the waveform). For example, in some cases, compressor 127 may include extraneous signals (e.g., high-frequency signal components) in the compressed waveform that interfere with generating tactile output and / or exceed the performance specifications of tactile output generator 167 when generating tactile output based on the compressed waveform. Low-pass filter 129 reduces or removes such extraneous signals in the waveform.

[0186] Thermal controller 131 receives a waveform (e.g., a filtered waveform from low-pass filter 129) as input and adjusts the waveform based on the thermal condition of device 100 (e.g., based on an internal temperature detected within device 100, such as the temperature of haptic feedback controller 161, and / or an external temperature detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies based on temperature (e.g., in response to receiving the same waveform, haptic feedback controller 161 generates a first tactile output when haptic feedback controller 161 is at a first temperature and generates a second tactile output when haptic feedback controller 161 is at a second temperature different from the first temperature). For example, the magnitude (or amplitude) of the tactile output may vary based on temperature. To reduce the effects of temperature changes, the waveform is modified (e.g., the amplitude of the waveform is increased or decreased based on temperature).

[0187] In some embodiments, the tactile feedback module 133 (e.g., trigger module 121) is coupled to the hardware input processing module 146. In some embodiments, Figure 1A The one or more other input controllers 160 include a hardware input processing module 146. In some embodiments, the hardware input processing module 146 receives input from a hardware input device 145 (e.g., Figure 1A In some embodiments, the hardware input device 145 is any input device described herein, such as a touch-sensitive display system 112 ( Figure 1A )、Keyboard / Mouse 350( Figure 3 )、Touchpad 355( Figure 3 ), one of the other input or control devices 116 ( Figure 1A ) or intensity-sensitive primary buttons. In some embodiments, the hardware input device 145 consists of intensity-sensitive primary buttons rather than touch-sensitive display system 112 ( Figure 1A )、Keyboard / Mouse 350( Figure 3 ) or touchpad 355( Figure 3). In some embodiments, in response to input from a hardware input device 145 (e.g., an intensity-sensitive home button or a touch screen), the hardware input processing module 146 provides one or more trigger signals to the haptic feedback module 133 to indicate that user input that meets predefined input criteria has been detected, such as input corresponding to a home button "click" (e.g., "press click" or "release click"). In some embodiments, the haptic feedback module 133 provides a waveform corresponding to a home button "click" in response to input corresponding to a home button "click", thereby simulating the haptic feedback of pressing a physical home button.

[0188] In some embodiments, the tactile output module includes a tactile feedback controller 161 (e.g. Figure 1A 145 ). In some embodiments, the tactile feedback controller 161 is coupled to a plurality of tactile output generators and selects one or more tactile output generators from the plurality of tactile output generators and sends a waveform to the selected one or more tactile output generators for generating a tactile output. In some embodiments, the tactile feedback controller 161 coordinates a tactile output request corresponding to activation of the hardware input device 145 and a tactile output request corresponding to a software event (e.g., a tactile output request from the tactile feedback module 133), and modifies one or more of the two or more waveforms to emphasize a particular waveform relative to the remaining waveforms of the two or more waveforms (e.g., by increasing the scale of the particular waveform and / or reducing the scale of the remaining waveforms of the waveforms to prioritize the tactile output corresponding to the activation of the hardware input device 145 over the tactile output corresponding to the software event).

[0189] In some embodiments, as Figure 1C As shown, the output of the tactile feedback controller 161 is coupled to the audio circuit of the device 100 (eg, the audio circuit 110, Figure 1A ) and provides the audio signal to the audio circuit of device 100. In some embodiments, haptic feedback controller 161 provides both a waveform for generating a tactile output and an audio signal for providing an audio output along with generating the tactile output. In some embodiments, haptic feedback controller 161 modifies the audio signal and / or the waveform (for generating the tactile output) so that the audio output and the tactile output are synchronized (e.g., by delaying the audio signal and / or the waveform). In some embodiments, haptic feedback controller 161 includes a digital-to-analog converter for converting the digital waveform into an analog signal, which is received by amplifier 163 and / or tactile output generator 167.

[0190] In some embodiments, the tactile output module includes an amplifier 163. In some embodiments, the amplifier 163 receives a waveform (e.g., from the tactile feedback controller 161), amplifies the waveform, and then sends the amplified waveform to the tactile output generator 167 (e.g., the tactile output generator 167 ( Figure 1A ) or 357( Figure 3 )). For example, amplifier 163 amplifies the received waveform to a signal level that meets the physical specifications of tactile output generator 167 (e.g., to a voltage and / or current required by tactile output generator 167 to generate a tactile output such that the signal sent to tactile output generator 167 generates a tactile output corresponding to the waveform received from haptic feedback controller 161) and sends the amplified waveform to tactile output generator 167. In response, tactile output generator 167 generates a tactile output (e.g., by displacing the movable mass back and forth in one or more dimensions relative to the neutral position of the movable mass).

[0191] In some embodiments, the tactile output module includes a sensor 169 coupled to the tactile output generator 167. The sensor 169 detects the state or state change (e.g., mechanical position, physical displacement, and / or movement) of the tactile output generator 167 or one or more components of the tactile output generator 167 (e.g., one or more moving components for generating a tactile output, such as a membrane). In some embodiments, the sensor 169 is a magnetic field sensor (e.g., a Hall effect sensor) or other displacement and / or motion sensor. In some embodiments, the sensor 169 provides information (e.g., the position, displacement, and / or movement of one or more components in the tactile output generator 167) to the tactile feedback controller 161, and based on the information about the state of the tactile output generator 167 provided by the sensor 169, the tactile feedback controller 161 adjusts the waveform output from the tactile feedback controller 161 (e.g., the waveform optionally sent to the tactile output generator 167 via the amplifier 163).

[0192] Figure 2 A device with a touch screen (e.g., Figure 1AIn some embodiments, the portable multifunction device 100 includes a touch-sensitive display system 112 (e.g., a touch screen). The touch screen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, and in other embodiments described below, a user can select one or more of the graphics by, for example, making a gesture on the graphics using one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of a finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0193] The device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen display.

[0194] In some embodiments, the device 100 includes a touch screen display, a menu button 204 (sometimes referred to as a home button 204), a push button 206 for powering the device on / off and for locking the device, a volume adjustment button 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding the button in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing the button before the predefined time interval has passed; and / or to unlock the device or initiate an unlocking process. In some embodiments, the device 100 also accepts voice input for activating or deactivating certain functions through the microphone 113. The device 100 also optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the touch-sensitive display system 112, and / or one or more tactile output generators 167 for generating tactile output for the user of the device 100.

[0195] Figure 3is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above referenced devices). Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or sensors similar to those described above) Figure 1A Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ), or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100( Figure 1A )'s memory 102 optionally does not store these modules.

[0196] Figure 3Each element in the above-mentioned identified element is optionally stored in one or more memory devices in the previously mentioned memory device.Each module in the above-mentioned identified module corresponds to the instruction set for performing the above-mentioned functions.The above-mentioned identified module or program (that is, instruction set) need not be implemented as independent software program, process or module, so the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments.In some embodiments, memory 370 optionally stores the subset of above-mentioned modules and data structure.In addition, memory 370 optionally stores additional modules and data structure not described above.

[0197] Attention is now turned to an embodiment of a user interface (“UI”) that is optionally implemented on portable multifunction device 100 .

[0198] Figure 4A An exemplary user interface for an application menu on portable multifunction device 100 is shown 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:

[0199] One or more signal strength indicators of one or more wireless communications, such as cellular signals and Wi-Fi signals;

[0200] ·time;

[0201] Bluetooth indicator;

[0202] Battery status indicator;

[0203] A tray 408 with icons for commonly used applications, such as:

[0204] o An icon 416 labeled “Phone” for the phone module 138 , which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0205] o An icon 418 of the email client module 140 labeled “Mail,” which optionally includes an indicator 410 of the number of unread emails;

[0206] o An icon 420 labeled "Browser" of the browser module 147; and

[0207] o Icon 422 labeled “Music” of the video and music player module 152;

[0208] as well as

[0209] Icons for other applications, such as:

[0210] o Icon 424 labeled “Messages” of IM module 141;

[0211] o Icon 426 labeled “Calendar” of calendar module 148;

[0212] o Icon 428 labeled “Photos” of the image management module 144;

[0213] o An icon 430 labeled “Camera” of the camera module 143;

[0214] o Icon 432 labeled “Online Video” of the online video module 155;

[0215] o Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

[0216] o Icon 436 labeled “Map” of the map module 154;

[0217] o Icon 438 labeled “Weather” of the weather widget 149-1;

[0218] o Icon 440 labeled “Clock” of the alarm clock widget 149-4;

[0219] o An icon 442 labeled “Fitness Support” of the fitness support module 142 ;

[0220] o Icon 444 labeled "Notepad" of the Notepad module 153; and

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

[0222] It should be noted that Figure 4A The icon labels shown in the are merely exemplary. For example, other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0223] Figure 4B A touch-sensitive surface 451 (e.g., Figure 3 a device (e.g., a tablet or touchpad 355) Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 359 for generating tactile output for a user of device 300.

[0224] Although many of the examples that follow will be given with reference to input on a touch screen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the main axis (for example, Figure 4B According to these embodiments, the device detects contact with the touch-sensitive surface 451 at a location that corresponds to a corresponding location on the display (e.g., Figure 4B 460 and 462 in (e.g., in Figure 4B , 460 corresponds to 468 and 462 corresponds to 470). Thus, on a touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user interface 450 in FIG. 4 is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0225] Additionally, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures, etc.), it should be understood that in some embodiments, one or more of these finger inputs are replaced by 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 contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). For another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

[0226] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that the touch-sensitive surface 451 in the display is included, the touch-sensitive surface 451 can be used to directly interact with the user interface elements on the touch-screen display. Figure 1A touch-sensitive display system 112 or Figure 4A In some implementations (such as touch screens in a touchscreen display), a contact detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by a 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 based on the detected input. In some implementations, focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touchscreen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in these implementations, the focus selector moves based on the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touchscreen display) that is controlled by the user to convey the user's desired interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user desires to activate the corresponding button (rather than other user interface elements shown on the device display).

[0227] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a surrogate (surrogate) 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 different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, the force measurements from multiple force sensors are combined (e.g., weighted averaged or summed) to determine an estimated contact force. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in pressure units). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that the user may not otherwise be able to access on a smaller device in some cases, which has a limited real estate for displaying indications (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical controls / mechanical controls, such as knobs or buttons).

[0228] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen display can be set to any one of a large range of predefined thresholds. In addition, in some embodiments, the user of the device is provided with a software setting for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0229] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, a value generated by low-pass filtering the contact intensity over a predefined time period or starting from a predefined time, etc. In some embodiments, the duration of the contact is used in determining the feature strength (e.g., when the feature strength is the average of the strength of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more strength thresholds is used to determine whether to perform one or more operations (e.g., whether to execute the corresponding option or give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0230] In some embodiments, a portion of a gesture is identified for determining the characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position (e.g., a drag gesture) where the strength of the contact increases. In this example, the characteristic strength of the contact at the end position is, in some cases, based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic strength.

[0231] The user interface diagrams described herein optionally include various intensity diagrams (e.g., 5530) that illustrate the intensity of contacts on the touch-sensitive surface relative to one or more intensity thresholds (e.g., contact detection intensity threshold IT0, light press intensity threshold IT1, and contact detection intensity threshold IT2). L , deep press intensity threshold IT D (For example, it is initially at least above 1 L ) and / or one or more other intensity thresholds (e.g., L Lower intensity threshold IT H )). This intensity graph is not typically part of the displayed user interface, but is provided to help explain the graph. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold IT0, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface figures.

[0232] 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 exceeding a first intensity threshold during the input 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 a time-based criterion. For example, for some "deep press" inputs, the intensity of the contact exceeding a second intensity threshold, which is greater than the first intensity threshold for a light press, during the input triggers a second response, as long as a delay time elapses between the first intensity threshold being met and the second intensity threshold being met. The duration of 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, where the delay time increases as the second intensity threshold increases). This delay time helps avoid accidentally identifying a deep press input. As another example, for some "deep press" inputs, a period of reduced sensitivity occurs after the first intensity threshold is reached. During this period of reduced sensitivity, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps avoid accidental deep press inputs.For other deep press inputs, the response to detecting the deep press input does not depend on time-based criteria.

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

[0234] For example, Figure 4C A dynamic intensity threshold 480 is shown that varies over time based in part on the intensity of the touch input 476 over time. The dynamic intensity threshold 480 is the sum of two components: a first component 474 that decays over time after a predefined delay time p1 from when the touch input 476 is initially detected, and a second component 478 that tracks the intensity of the touch input 476 over time. The initial high intensity threshold of the first component 474 reduces accidental triggering of a "deep press" response while still allowing an immediate "deep press" response if the touch input 476 provides sufficient intensity. The second component 478 reduces the unintentional triggering of a "deep press" response through gradual intensity fluctuations of the touch input. In some embodiments, when the touch input 476 satisfies the dynamic intensity threshold 480 (e.g., at Figure 4C ), triggering a “deep press” response.

[0235] Figure 4D Another dynamic intensity threshold 486 (eg, intensity threshold I D ). Figure 4D Two other intensity thresholds are also shown: a first intensity threshold IT H and the second intensity threshold I L .exist Figure 4D Although the touch input 484 meets the first intensity threshold IT before time p2 H and the second intensity threshold IT L , but no response is provided until a delay time p2 has elapsed at time 482. Additionally, Figure 4D In the example, the dynamic intensity threshold 486 decays over time, wherein the decay is from time 482 (when the trigger is connected to the intensity threshold IT L This type of dynamic intensity threshold reduction begins immediately after the trigger is triggered with a lower threshold intensity (such as the first intensity threshold IT H Or the second intensity threshold I L ) is triggered after or simultaneously with the unexpected triggering of the dynamic intensity threshold IT D The associated response.

[0236] Figure 4E Another dynamic intensity threshold 492 (eg, intensity threshold I D ).exist Figure 4E In the example, after a delay time p2 has passed since the touch input 490 was initially detected, the trigger is triggered with the intensity threshold IT L At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 has passed since the touch input 490 was initially detected. L The associated response then reduces the intensity of the touch input 490, and then increases the intensity of the touch input 490 without releasing the touch input 490, which may trigger an action that is consistent with the intensity threshold I. D The associated response (e.g., at time 494) is performed even when the intensity of touch input 490 is below another intensity threshold (e.g., intensity threshold I L ) is also the case.

[0237] The contact characteristic strength is lower than the light press strength threshold IT L The intensity increases to between the light press intensity threshold IT L and deep press intensity threshold IT D The intensity between the deep press intensity threshold IT is sometimes referred to as a "light press" input. D The intensity of the deep press increases to above the deep press intensity threshold IT DThe intensity of the contact feature increases from an intensity below the contact detection intensity threshold IT0 to an intensity between the contact detection intensity threshold IT0 and the light press intensity threshold IT0. L A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold IT0 to an intensity below the contact detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some examples, shaded circles or ellipses are used to represent the intensity of a contact on the touch-sensitive surface. In some examples, unshaded circles or ellipses are used to represent corresponding contacts on the touch-sensitive surface without specifying the intensity of the corresponding contacts.

[0238] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting an increase in the strength of the contact (or multiple contacts) to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the strength of the corresponding contact to above the press input strength threshold (e.g., the corresponding operation is performed on a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and a subsequent decrease in the strength of the contact to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., the corresponding operation is performed on an "up stroke" of the corresponding press input).

[0239] In some embodiments, the device employs intensity hysteresis to avoid unintended input, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., performing the corresponding operation on an "up stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact strength increases from an strength equal to or less than a hysteresis strength threshold to an strength equal to or greater than a press input strength threshold and, optionally, the contact strength subsequently decreases to an strength equal to or less than the hysteresis strength, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact strength or a decrease in contact strength, depending on the circumstances).

[0240] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold, or in response to a gesture including a press input, are optionally triggered in response to detecting: the intensity of the contact increasing above the press input intensity threshold, the intensity of the contact increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreasing below the press input intensity threshold, or the intensity of the contact decreasing below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where operations are described as being performed in response to detecting a decrease in the intensity of the contact below the press input intensity threshold, the operations are optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold. As described above, in some embodiments, triggering of these operations is also dependent on satisfying a time-based criterion (e.g., a delay time having elapsed between satisfying the first intensity threshold and satisfying the second intensity threshold).

[0241] User interface and associated processes

[0242] Attention now turns to an embodiment of a user interface (“UI”) and associated processes, optionally implemented on an electronic device such as portable multifunction device 100 or device 300, having a display, a touch-sensitive surface, and (optionally) one or more sensors for detecting intensity of contacts with the touch-sensitive surface.

[0243] Figures 5A1 to 5A361 shows exemplary user interfaces for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figures 6A to 6K For ease of explanation, some embodiments in the implementation scheme will be discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on touch-sensitive display system 112. However, in response to detecting a contact on touch-sensitive surface 451 when the user interface shown in the figure is displayed on display 450 together with the focus selector, similar operations are optionally performed on a device with display 450 and a separate touch-sensitive surface 451.

[0244] For ease of explanation, some of the embodiments will be discussed with reference to operations performed on a device that does not have a home button, and uses a gesture that meets predefined criteria to dismiss the currently displayed user interface and display the home screen user interface. Figures 5A1 to 5A36 Not shown, but in some embodiments, a home button (e.g., a mechanical button, a solid-state button, or a virtual button) is included on the device and is used to cause the dismissal of a currently displayed user interface and the display of a home screen user interface (e.g., the last displayed page or a default page of the home screen user interface is displayed in response to a single press input).

[0245] Figures 5A1 to 5A36 An exemplary user interface for displaying and interacting with user interface objects corresponding to different applications on a multi-page home screen user interface according to some embodiments is shown (e.g., including two or more user-arranged home screens and system-arranged home screens arranged in a predefined sequence in a first page navigation direction (e.g., from left to right)). According to some embodiments, the user interface objects corresponding to different applications include application icons and, optionally, user interface objects that include application content from the corresponding applications (e.g., desktop widgets, mini-application objects, etc.). In some embodiments, both the application icon and the user interface object that includes application content are configured to launch their corresponding application when activated by a first type of input (e.g., a tap input at the location of the application icon or the user interface object containing application content). In some embodiments, the user interface object that includes application content is updated according to content and / or instructions provided by its corresponding application (e.g., by an operating system or by an application) while the application remains dormant or operates in the background.

[0246] Figures 5A1 to 5A4 Examples of navigating between different home screen user interfaces are shown according to some embodiments.

[0247] Figure 5A1 A first user-arranged page 5050 of a multi-page home screen user interface (also referred to as a "user-arranged home screen 5050") is shown. The user-arranged home screen 5050 includes a plurality of application icons (application icons 5008a-5008m) arranged in a preset layout (e.g., on a 5×4 grid). In some embodiments, the plurality of application icons are user-selected and placed at corresponding positions on the user-arranged home screen 5050 based on user input. In some embodiments, the user-arranged home screen 5050 includes a page navigation element 5004 that indicates both the total number of pages in the multi-page home screen user interface and the position of the currently displayed page in the sequence of pages of the multi-page home screen user interface. For example, as Figure 5A1 As shown, the navigation element 5004 includes a sequence of page dots or page indicator icons corresponding to respective pages in the page sequence. The page indicator icon 5004a is highlighted relative to the other page indicator icons in the page navigation element 5004, which indicates that the page 5050 of the multi-page home screen user interface currently displayed is the third page of a total of five pages of the multi-page home screen user interface. In some embodiments, the multi-page home screen user interface includes a desktop widget page and a system-arranged page at the beginning and end of the page sequence. In some embodiments, the multi-page home screen user interface includes a desktop widget page and a system-arranged page as an overlay displayed above the user-arranged page of the multi-page home screen user interface (e.g., above the beginning page and the ending page of the sequence of user-arranged pages). In this example, the desktop widget page and the system-arranged page are the beginning page and the ending page, respectively, of the page sequence of the multi-page home screen user interface. In Figure 5A1, at the bottom of a user-arranged page 5050 of a multi-page home screen user interface, a plurality of preconfigured application icons (application icons 5008n-5008q) are displayed in a dock. In some embodiments, the plurality of preconfigured icons in the dock are for the most frequently used applications. In some embodiments, the application icons may be displayed with corner marks (e.g., corner mark 5010b for a phone application and corner mark 5010a for a calendar application, etc.) that indicate the number of notifications received from the application icon's corresponding application. In some embodiments, the dock shown in the bottom portion of the user-arranged page 5050 is shown at the same location on the display 112 as other pages of the multi-page home screen user interface (e.g., some or all user-arranged pages, all pages except the desktop widget screen and the system-arranged home screen, etc.). In some embodiments, the page navigation element 5004 displayed on the user-arranged page 5050 is also shown at the same location on the display 112 on other pages of the multi-page home screen user interface (e.g., all user-arranged pages, all pages including desktop widget screens and system-arranged home screens, etc.), in addition to highlighting different page indicator icons to show which page is currently being displayed.

[0248] Figures 5A1 to 5A3 Navigation is shown from a user-arranged page 5050 to another user-arranged page 5052 in a first navigation direction (e.g., a forward direction of a sequence of pages through a multi-page home screen user interface), where the first navigation direction is specified by a navigation input (e.g., a left swipe gesture on the user-arranged page 5050, a tap input on the page indicator icon 5004b for the user-arranged page 5052, etc.). Figure 5A1 500 and swipe input by contact 5502 are shown, which are separate inputs and are not detected simultaneously. The tap input by contact 5500 is detected at a position on the touch screen corresponding to the page indicator icon 5004b. In response to the tap input by contact 5500, the device displays a different home screen user interface corresponding to the page indicator icon 5004b, namely, Figure 5A35052 shown on the top. In some embodiments, to detect a tap input, the device detects lift-off of contact 5500 within a first threshold amount of time of pressure of contact 5500 (e.g., the amount of time required to detect a touch hold input), without detecting substantial movement of the contact 5500 since the pressure of contact 5500 (e.g., the contact being substantially stationary). A swipe input by contact 5502 is detected after contact 5502 is pressed at a location corresponding to application icon 5008a. In some embodiments, the device detects a swipe input by contact 5502 when the device detects substantial movement (e.g., more than a nominal amount of movement within a nominal threshold amount of time) after the pressure of contact 5502 but before contact 5502 has remained substantially stationary for a threshold amount of time (e.g., before a touch hold is detected). In some embodiments, the swipe input by contact 5502 need not be detected on any particular application icon, and the swipe input by the contact is optionally detected at an unoccupied area of ​​the currently displayed page 5050. In some embodiments, a swipe input that starts at page indicator icon 5004a and ends at page indicator icon 5004b also causes navigation from page 5050 to page 5052. In some embodiments, if a swipe input is used to specify a navigation direction through pages of a multi-page home screen user interface, the computer system does not need to start the swipe input from an edge of the input. Instead, the computer system detects a swipe input that starts at a corresponding location on the currently displayed page, and in response to detecting the swipe input: based on determining that the swipe input is in a first direction, the computer system navigates from the current page through the sequence of pages in a first navigation direction (e.g., a forward direction) to the next page; and based on determining that the swipe input is in a second direction, the computer system navigates from the current page through the sequence of pages in a second navigation direction (e.g., a backward direction) to the next page.

[0249] exist Figure 5A2 , a user-arranged page 5050 of a multi-page home screen user interface including application icons 5008a-5008m and other simultaneously displayed user interface elements is shown moving in response to movement of contact 5502 to the left, thereby dragging a previously undisplayed user-arranged page of the home screen onto the display (e.g., past the next user-arranged page in the page sequence in a forward direction). In some embodiments, the user-arranged page 5050 moves in response to a tap input 5500 on the page indicator icon 5004b.

[0250] exist Figure 5A3, the next user-arranged page 5052 of the multi-page home screen user interface (e.g., a user-arranged home screen 5052 that was not previously displayed) is displayed due to a swipe input made through contact 5502, replacing the previously displayed user-arranged page 5050. User-arranged page 5052 of the multi-page home screen user interface includes an additional plurality of application icons 5008r-5008w (e.g., a user-selected group of application icons that is different from the plurality of application icons on user-arranged page 5050). Figure 5A3 , due to a change in the displayed user arranged home screen, navigation element 5004 is updated to de-highlight page indicator icon 5004a and highlight page indicator icon 5004b.

[0251] Figure 5A4 exist Figure 5A3 after. Figures 5A3 to 5A4 Continuous navigation from a user-arranged page 5052 to a system-arranged user interface (e.g., a system-arranged home screen 5054 or another user interface including automatically generated application groupings, etc.) is shown according to some embodiments.

[0252] Similar to Figure 5A1 , Figure 5A3 A left swipe input by contact 5506 is shown. The swipe input by contact 5506 is detected after contact 5506 is pressed at a corresponding location in user-arranged page 5052 of the multi-page home screen user interface (e.g., optionally, not at the location of application icon 5008). In some embodiments, the device detects a swipe input by contact 5506 when the device detects substantial movement (e.g., more than a nominal amount of movement within a nominal threshold amount of time) after the press of contact 5506 but before contact 5506 has remained substantially stationary for a threshold amount of time (e.g., before the touch is detected to be maintained). In response to the swipe input by contact 5506 and based on determining that the movement of contact 5506 has exceeded a predefined threshold amount of movement (e.g., half the width of the display) to complete the page navigation operation, system-arranged page 5054 of the multi-page home screen user interface is displayed as a result of the swipe input by contact 5506, replacing the previously displayed user-arranged page 5052, as shown. Figure 5A4In some embodiments, the system-arranged page 5054 is part of a sequence of pages of a multi-page home screen user interface and is represented by a corresponding page indicator icon (e.g., page indicator icon 5004c) in the page navigation element 5004. In some embodiments, a tap input by contact 5504 is detected at a location on the touch screen corresponding to the page indicator icon 5004c. In response to the tap input by contact 5504, the device displays the system-arranged page 5054 (e.g., page indicator icon 5004c) of the multi-page home screen user interface corresponding to the page indicator icon 5004c. Figure 5A4 In some embodiments, upon swiping input from page indicator icon 5004b to page indicator icon 5004c on page navigation element 5004, the device displays Figure 5A4 5054 is shown in FIG. 506 . In some embodiments, the system-arranged home screen 5054 is replaced with an application library user interface 5054′ that overlays the last user-arranged page of the home screen user interface. In some embodiments, another system-arranged user interface that includes a similar automatic grouping of application icons is displayed instead of the system-arranged page 5054.

[0253] Figure 5A4 A system-arranged home screen 5054 of a multi-page home screen user interface according to some embodiments is shown. System-arranged home screen 5054 is different from user-arranged home screens 5050 and 5052, wherein system-arranged home screen 5054 has a layout (e.g., position and grouping) for application icons and user interface objects containing application content that is automatically generated without user input, wherein user-arranged home screens 5052 and 5050 have a user-configured layout (e.g., position and grouping) for application icons and user interface objects containing application content. In some embodiments, the device generates system-arranged home screen 5054 by assigning (e.g., categorizing, clustering, grouping, etc.) application icons that share one or more characteristics under the same automatically generated application grouping. For example, Figure 5A4Home screen 5054, showing a system arrangement, includes an application grouping corresponding to "Communication" (e.g., represented by grouping icon 5020a), an application grouping corresponding to "Recently Added" (e.g., represented by grouping icon 5020b), an application grouping corresponding to "Utilities" (e.g., represented by grouping icon 5020c), and an application grouping corresponding to "Productivity" (e.g., represented by grouping icon 5020d), among others. In some embodiments, the same application icon may be included in more than one application grouping. For example, application icon 5008o (representing an "Email" application) is included in application groups corresponding to grouping icons 5020a, 5020b, and 5020c. In some embodiments, the "Recently Added" application grouping represented by grouping icon 5020b includes applications that were most recently added to device 100 by a user. In some embodiments, the "Recently Added" application grouping includes applications that were added (e.g., automatically installed) by the device.

[0254] In some embodiments, a search input area 5030 is displayed at the top of the system-arranged home screen 5054. The search input area 5030 can be used to search for applications and optional desktop widgets available on the device (e.g., available on user-arranged pages of a multi-page home screen user interface). In some embodiments, the search input area 5030 displayed on the system-arranged home screen automatically applies a filter so that only applications and optional desktop widgets that meet the search criteria received via the search input area are returned as search results. In some embodiments, a search is performed on applications and optional desktop widgets that are currently installed on the device (e.g., excluding deleted applications and desktop widgets, or applications that are available in an application store but not installed). In some embodiments, a search is performed on installed applications and optional desktop widgets, regardless of whether they are currently available via visible user-arranged home screens of the home screen user interface (e.g., including applications and optional desktop widgets on hidden pages or previously deleted pages of the multi-page home screen user interface, as well as applications and optional desktop widgets on visible pages of the multi-page home screen user interface). In some embodiments, a corresponding search input area is available on a start page of a multi-page home screen user interface, which is a widget screen that displays a list of widgets corresponding to different applications installed on the device. In some embodiments, the search input area available on the widget screen returns search results including applications and optional widgets, as well as other types of information, such as content from installed applications (e.g., messages, emails, contacts, logs, game history, web pages, photos, etc.). In some embodiments, a corresponding search input area is optionally available on multiple (e.g., some, all, each, etc.) pages of a user-arranged page of a multi-page home screen user interface (e.g., in response to a downward swipe detected on the page (e.g., from the top edge of the user interface, or from any area within the user interface, etc.)). In some embodiments, the search input area on the user-arranged page has the same functionality as the search input area on the system-arranged page of the multi-page home screen user interface. In some embodiments, the search input area on the user-arranged page has the same functionality as the search input area on the widget screen. Figures 5A15 to 5A20 and additional features of the search input area are described in the accompanying instructions.

[0255] In some embodiments, the system-arranged home screen 5054 optionally includes one or more widgets (e.g., widgets 5022a and 5022b) (e.g., also referred to as user interface objects that include application content, or mini-application objects) (e.g., including widgets that are also available on the user-arranged home screen, and optional widgets that are automatically selected by the system). Unlike application icons, widgets are mini-application objects that display information or provide functionality of the corresponding application without displaying the application itself. For example, the system-arranged home screen 5054 includes a widget 5022a for a weather application that displays weather information for a selected city and a widget 5022b for a clock application that displays time information worldwide (e.g., time information for multiple locations around the world). In some embodiments, the system-arranged home screen 5054 includes a recommended application widget 5055 that displays corresponding application icons of multiple recommended applications automatically identified from applications installed on the device based on the user's individual usage patterns and, optionally, the average usage patterns of a large number of users.

[0256] Figure 5A4 Various contacts and touch inputs detected on the main screen 5054 of the system arrangement in different example scenarios are shown, including a swipe input made by contact 5508, and corresponding tap inputs made by contacts 5110, 5112, and 5114. In some embodiments, in response to detecting a contact on the touch screen 112, the device determines the type of input, the starting position of the input, the movement direction and movement distance (if any) of the input, the current position and movement characteristics of the input and / or the termination of the input, etc., and performs a corresponding operation based on the type, position, movement direction, movement distance, termination state, etc.

[0257] Figures 5A4 to 5A6 An example of navigating system-arranged home screens 5054 in response to swipe inputs according to some embodiments is shown. For example, in response to an upward swipe input made by contact 5508 (e.g., starting on an application icon or on an unoccupied area of ​​a home screen), the system-arranged home screens 5054, or portions thereof, scroll upward to show previously undisplayed portions of the system-arranged home screens 5054. For example, in Figure 5A5, the application groupings represented by grouping icons 5020a-5020d move upward in accordance with the upward swipe input made through contact 5508. Due to the upward movement of the swipe input made through contact 5508, the application grouping corresponding to "Entertainment" (e.g., represented by grouping icon 5020e) and the application grouping corresponding to "System" (e.g., represented by grouping icon 5020f) that were not previously displayed are shown below the desktop widget 5022b. In some embodiments, there may be an unlimited number of user-arranged home screens and only a single system-arranged home screen in a multi-page home screen user interface, and the system-arranged home screen extends infinitely in one dimension and is scrollable (e.g., scrollable in the vertical direction), while the user-arranged home screen is a fixed-size page and is not scrollable. As Figure 5A6 As shown, as the swipe input performed through contact 5508 continues to move upward, more user interface elements are revealed on the system arrangement home screen 5054, including an application grouping corresponding to "Games" (e.g., represented by grouping icon 5020g) and an application grouping corresponding to "Finance" (e.g., represented by grouping icon 5020h).

[0258] exist Figure 5A4, the corresponding group icon includes multiple different parts, including multiple parts occupied by application icons (or scaled-down versions thereof) for a subset of applications included in the automatically generated group represented by the group icon, and optionally a folder launch icon corresponding to the folder containing the application icons of the applications included in the group. In some embodiments, only a limited number of applications (e.g., three) included in the group have their application icons shown on the group icon. In some embodiments, the folder launch icon includes miniature images of the application icons for the applications included in the group represented by the group icon. For example, group icon 5020a for the "Communication" group includes application icons for the phone application, email application, and messaging application included in the "Communication" group. In some embodiments, the "Communication" group includes additional applications that are not represented by their application icons on the group icon 5020a. In some embodiments, the applications represented by their application icons on the group icon are automatically selected by the system based on various criteria (such as frequency of use, recency, whether the application requests user attention (e.g., has a badge, has unread notifications, etc.), etc.) without user input. Folder launch icon 5014a on group icon 5020a shows miniature images of application icons for the seven applications currently included in the "Communications" group. In some embodiments, if there are more than a threshold number of applications included in the group (e.g., nine), only nine miniature images of application icons will be shown on folder launch icon 5014a. In some embodiments, a folder launch icon is not used, and a tap input on an empty area of ​​a group icon also causes the contents of the group to be displayed in a folder window.

[0259] Figure 5A4 and Figures 5A7 to 5A9 An example of navigation from a system arranged home screen 5054 in response to user tap input on application icons and folder launch icons shown on grouped icons is shown according to some embodiments.

[0260] Figure 5A4 After Figure 5A7 Shown in response to contact 5510 on the main screen 5054 of the system arrangement corresponding to the group icon 5020a ( Figure 5A4 5020a (or a scaled-down version thereof), the device 100 launches an application (e.g., a messaging application) corresponding to the application icon 5020a and displays a corresponding Figure 5A7 The application user interface 5056 for the selected application in Figure 5A7, the messaging application also includes a virtual keyboard 5042 at the bottom of the application user interface 5056. Figure 5A7 , upon detecting a home desktop gesture or input (e.g., an upward edge swipe input (e.g., swiping upward from the bottom edge area of ​​the display) via contact 5516), the device returns to displaying the system-arranged home screen 5054 (e.g., as shown in FIG. Figure 5A4 ) (e.g., exiting the messaging application and dismissing the application user interface 5056). Figure 5A4 After Figure 5A8 In response to the Figure 5A4 Another tap input by contact 5512 is detected at the location of application icon 5008o within the grouped icon 5020a shown, launching a different application (e.g., an email application), and the device displays a corresponding Figure 5A8 The application user interface 5058 of the selected application in the Figure 5A8 , upon detecting an upward edge swipe input via contact 5518, the device returns to displaying the system-arranged home screen 5054.

[0261] Figure 5A4 After Figure 5A9 5022c for the phone application).

[0262] exist Figure 5A9 In some embodiments, in response to detecting a tap input by contact 5526 at any location in the user interface 5054' outside of the pop-up window 5080, the device returns to displaying the system-arranged home screen 5054 (e.g., Figure 5A4 or Figure 5A10In some embodiments, in response to detecting a tap by contact 5520 at a location corresponding to an application icon 5008o within folder window 5080, the corresponding application (e.g., a messaging application) is launched, and the device displays an application user interface 5056 corresponding to the selected application (e.g., as shown in FIG. Figure 5A7 In some embodiments, in response to detecting a tap input by contact 5522 at a location corresponding to application icon 5008o within folder window 5080, a different application (e.g., an email application) is launched, and the device displays an application user interface 5058 corresponding to the selected application (e.g., as shown in FIG. 5B ). Figure 5A8 In some embodiments, in response to detecting a tap input by contact 5524 at a location corresponding to the avatar "Neil" corresponding to the user contact within the "mCall" desktop widget 5022c, the device executes the functionality of the application "mCall" to call the user contact "Neil" using the phone application "mCall". In some embodiments, other operations that can be triggered by interacting with an application icon on a user-arranged home screen may also be triggered by interacting with the application icon when the application icon is shown on a system-arranged home screen, such as displaying a quick action menu, triggering an icon reconfiguration mode, deleting the corresponding application, moving the application icon to a different location on the user-arranged home screen after the icon reconfiguration mode begins, and the like.

[0263] Figures 5A10 to 5A14 An example of performing a search in response to user input in the search input area 5030 is shown according to some embodiments.

[0264] exist Figure 5A10 , a tap input by contact 5528 is detected on the search input area 5030 at the top of the main screen 5054 of the system arrangement. In response to the tap input by contact 5528, the main screen 5054 of the system arrangement is transformed into a user interface 5054″, in which a search filter selector 5032 is displayed below the search input area 5030, and a virtual keyboard 5042 appears at the bottom of the user interface 5054″, as shown in FIG. Figure 5A11 The search filter selector 5032 (eg, a toggle option) has options to show “all” applications or only “badged” applications that satisfy the search keyword received in the search input area 5030 .

[0265] exist Figure 5A12In FIG. 5 , the user enters the search keyword “ca” in the search input area 5030, and the “badged” filter is enabled. In response to detecting the search input, application icons (e.g., application icons with badges) for applications that match the search keyword “ca” (e.g., the phone application (with “missed call information”), the calendar application, and the “(Cal Today)” news application) and have unread notifications as indicated by badges 5010a-c are returned and displayed. Figure 5A12 In some embodiments, only application icons (and optional desktop widgets) are returned in response to search input (e.g., search results are user interface objects that can be repositioned in a multi-page home screen user interface in icon reconfiguration mode).

[0266] exist Figure 5A12 In response to the tap input by contact 5530 to change the search condition from "with badge" to "all", the search results are updated. Figure 5A13 In some embodiments, widgets for related applications (e.g., widget 5022c for the mCall application) are also displayed as search results.

[0267] In some embodiments, the application icons and optional desktop widgets returned in the search results have the same functionality as the applications displayed on the user-arranged pages of the home screen user interface. Figure 5A13, contact 5532 is detected at a location corresponding to application icon 5008n. In some embodiments, based on determining that liftoff of contact 5532 is detected within a first threshold amount of time (e.g., the amount of time required to detect a touch hold input) without detecting substantial movement of the contact since the application of contact 5532 (e.g., the contact remains substantially stationary and has moved less than a threshold amount) since the application of contact 5532 was pressed, the device launches the corresponding phone application and displays an application user interface for the corresponding phone application. In some embodiments, based on determining that liftoff of contact 5532 is detected within a second threshold amount of time (e.g., the amount of time required to detect a tap and hold input) without detecting substantial movement of the contact since the application of contact 5532 (the contact remains substantially stationary and has moved less than a threshold amount), the device begins icon reconfiguration mode and displays delete enable representations for multiple (e.g., some, all, each, etc.) application icons (e.g., delete badges 5012a-d). The search results user interface 5054 in icon reconfiguration mode is labeled “ Figure 5A14 5060 in the user interface. In some embodiments, the second threshold amount of time is greater than the first second threshold amount of time.

[0268] Figure 5A14 Both a tap input by contact 5534 or a drag and drop input by contact 5536 are shown at the location of an application icon on search results user interface 5060 in icon reconfiguration mode. In response to a tap input by contact 5534 at a location corresponding to a delete affordance for application icon 5008w (e.g., delete badge 5012e), the device removes application icon 5008w from user interface 5060 (e.g., deletes the “Calculator” application associated with application icon 5008 from the search results and from the device (e.g., from a user-arranged home screen and a system-arranged home screen)), as shown. Figure 5A19 In some embodiments, in response to a tap input on the cancel button via contact 5540, the device redisplays the system-placed home screen 5054. At this point, the device has moved from the original position of the application icon 5008w in the user-placed home screen 5052 and the system-placed home screen 5054 (as shown in FIG. Figure 5A20 In response to detecting a drag-and-drop input by contact 5536 after touching contact 5536 downward at a location corresponding to application 5008w, based on determining that movement of contact 5536 has reached an edge of user interface 5060 in the first reconfiguration mode, the device navigates to an adjacent user-arranged home screen 5052 while application icon 5008w is being dragged by contact 5036. Figures 5A15 to 5A18An exemplary repositioning process for application icon 5008w in a first reconfiguration mode is shown after application icon 5008w is dragged from search results user interface 5060 in accordance with some embodiments.

[0269] exist Figure 5A15 In response to Figure 5A14 5008r-5008v and other simultaneously displayed user interface elements are displayed in the icon reconfiguration mode. For example, the home screen interface arranged by the previous user where the application icon 5008w is located, or the adjacent home screen of the system arranged home screen interface. The page indicator icon 5004b corresponding to the page 5052 is highlighted in the page navigation element 5004. When the moving icon of the contact 5536 continues to the edge of the page 5052' in the reconfiguration mode, another page 5050' of the home screen user interface in the icon reconfiguration mode is displayed, as shown in FIG. Figure 5A16 As shown. Figure 5A16 In the first reconfiguration mode, a user arranged home screen 5050' is displayed, which includes application icons 5008a-5008m and other user interface elements displayed simultaneously. Figure 5A16 , as a result of the page navigation, page navigation element 5004 is updated to de-highlight page indicator icon 5004b and highlight page indicator icon 5004a. Application icon 5008w is shown moving on user-arranged page 5050' of the home screen user interface in accordance with movement of contact 5536 to the left.

[0270] like Figure 5A17 As shown, the drag input by contact 5536 is terminated (e.g., via lift-off) and application icon 5008w is dropped into user-arranged home screen 5050' in the first reconfiguration mode. Figure 5A17 5050 ', the device terminates the first reconfiguration mode and displays the home screen 5050 arranged by the user, as shown in FIG. Figure 5A18 shown.

[0271] Figures 5A19 to 5A20 An example of exiting the first reconfiguration mode according to some embodiments is shown. Figure 5A19, a tap input by contact 5540 is received at a position corresponding to an option (e.g., a “Cancel” option) for exiting the search results user interface 5060 in the first reconfiguration mode. In response to the tap input by contact 5540 at “Cancel,” the device exits the search results user interface 5060 and returns to the main screen 5054 of the system arrangement in the normal operation mode, as shown in FIG. Figure 5A20 In some embodiments, the home screen 5054 of the system arrangement in normal operating mode is redisplayed, regardless of whether the icon reconfiguration mode was triggered before the cancel button was selected and regardless of whether the application icon has been deleted from the search results user interface 5060 or 5054".

[0272] Figures 5A21 to 5A36 An example is shown in which the widget screen and the system-placed page of a multi-page home screen user interface are not represented as pages in a sequence of pages of the multi-page home screen user interface, but are instead separately displayed user interfaces that overlay the beginning and ending pages of the user-placed sequence of pages of the multi-page home screen user interface. In some embodiments, when the system-placed page is not one of the pages in the sequence of pages represented by the page indicator icon in the page navigation element 5004, the system-placed page is also referred to as an application library user interface 5054'.

[0273] like Figure 5A21 As shown, the multi-page home screen user interface includes four user-arranged pages represented by four page indicator icons 5004a-5004b and 5004d-5004e in the page navigation element 5004. The currently displayed page is the user-arranged page 5064, which is the starting page of the user-arranged page sequence in the multi-page home screen user interface. Figures 5A21 to 5A23, in response to a right swipe input made through contact 5531 (e.g., specifying a navigation direction from an end page to a start page through a page sequence (e.g., a left navigation direction through pages)), the widget screen user interface 5053 slides on the user-arranged home screen 5064 as the user-arranged home screen gradually moves away from the user and the user-arranged home screen becomes darker and blurred behind the widget screen user interface 5053. In some embodiments, the widget screen user interface 5053 includes a plurality of user-selected desktop widgets 5022, which are optionally categorized according to relevant metrics determined by the system (e.g., a message widget 5022f, a weather widget 5022a, a map widget 5022d, and a calendar widget 5022e). In some embodiments, various widgets of different sizes and various widgets for different applications are included in the widget screen (e.g., widgets 5022e and 5022f are 2×2 in size, while widgets 5022a and 5022d are 2×4 in size). In some embodiments, the widget screen user interface 5053 also includes a recommended applications widget that displays application icons for multiple applications automatically selected by the device based on various recommendation criteria (e.g., individual usage patterns, average usage patterns across a large number of users, recent usage behavior, long-term usage behavior, etc.). Figures 5A24 to 5A26 In response to a left swipe input made through contact 5529 (e.g., specifying a navigation direction from a start page to an end page through a page sequence (e.g., a right navigation direction through pages), the desktop widget screen user interface 5053 slides away from the user-arranged home screen 5064, and the user-arranged home screen 5064 is restored to the foreground of the display (e.g., Figure 5A26 shown).

[0274] Figures 5A26 to 5A32A swipe input by contact 5527 is shown passing through different portions of a cross-page navigation element 5004 through pages of a multi-page home screen user interface in a left navigation direction (e.g., a direction from the start page to the end page of a sequence of pages of the multi-page home screen user interface). In response to detecting that contact 5527 reaches the corresponding page indicator icon for the next page in the page navigation direction, the device highlights the corresponding page indicator icon and displays the corresponding page of the multi-page home screen user interface. In some embodiments, in response to detecting that contact 5527 reaches the corresponding page indicator icon for the next page in the page navigation direction, the device generates corresponding tactile output 5525 (e.g., 5525a, 5525b, 5525c). In some embodiments, various characteristics of the movement of contact 5527 (e.g., speed, acceleration, distance, starting position, lift-off position, etc.) are used to calculate various movement metrics for determining the destination page displayed after detecting the end of the swipe input. For example, a quick swipe without intentionally locating a lift-off position may cause the device to land on the same page of the home screen user interface, while a slow and more intentional swipe lands on a specific page indicator icon in a page navigation element if both inputs meet preset criteria for navigating to the pages. In some embodiments, tactile output is optionally generated even after lift-off of contact has been detected, for example in conjunction with display of a separate page of a sequence of pages leading to a final destination page displayed in response to the swipe input.

[0275] exist Figure 5A32 , a page navigation input by contact 5523 (e.g., a left swipe input anywhere on user-arranged page 5052) is detected on user-arranged home screen 5052, which is currently the last page in a sequence of pages of a multi-page home screen user interface. When the last user-arranged page of the multi-page home screen user interface has been reached, the page navigation input specifies a rightward navigation direction through the pages. Figures 5A33 to 5A34 , in response to navigation input through contact 5523, the application library user interface 5054' slides onto the display from the right edge of the display, with the last user-arranged page 5052 gradually moving away from the user and becoming a blurred and / or dimmed background for the application library user interface 5054'.

[0276] exist Figures 5A35 to 5A36, another page navigation input (e.g., a right swipe input anywhere on application library user interface 5054') is detected on application library user interface 5054' via contact 5521. The page navigation input specifies a left navigation direction through the pages of the multi-page home screen user interface. In response to the navigation input via contact 5521, application library user interface 5054' slides off the display again, and the last user-placed page 5052 is restored to the foreground of the display.

[0277] Figures 5B1 to 5B19 An exemplary user interface for reconfiguring and interacting with a multi-page home screen user interface according to some embodiments is shown.

[0278] Figures 5B1 to 5B6 An exemplary user interface is shown for configuring and interacting with a multi-page home screen user interface in a first reconfiguration mode (e.g., icon reconfiguration mode) according to some embodiments. Figure 5B1A user-arranged page 5050 of a multi-page home screen user interface is shown, including a plurality of application icons (e.g., application icons 5008a-5008m) and a plurality of pre-configured application icons (application icons 5008n-5008q) at the bottom of the user-arranged home screen 5050. A page navigation element 5004 is displayed on the user-arranged home screen 5050, with page indicator icon 5004a highlighted, indicating that the user-arranged home screen 5050 is the third page in a sequence of five pages of the multi-page home screen user interface. In this illustrative example, the desktop widget screen and the system-arranged home screen are not included in the sequence of pages of the multi-page home screen user interface, but are displayed as overlays on the beginning and end pages of the user-arranged pages of the multi-page home screen user interface, respectively, and are therefore not represented in the page navigation element 5004. In some embodiments, when a system-arranged page of the home screen user interface is not included in the sequence of pages represented by the page indicator icon in the page navigation element, the system-arranged page is also referred to as an application library user interface (e.g., application library user interface 5054'). In some embodiments, regardless of whether the system-arranged pages are represented by page indicator icons in page navigation elements of the sequence of pages of the multi-page home screen user interface, the system-arranged pages are accessed by input specifying a navigation direction that is the same as the navigation direction through the sequence of pages of the multi-page home screen user interface. In some embodiments, a swipe input in another direction (e.g., a downward edge swipe on the left corner of a user-arranged home screen) optionally also causes the application library user interface to be displayed, overlaying any one of the user-arranged home screens. In some embodiments, the examples shown herein are not limited to embodiments in which the system-arranged home screen or the application library is represented by a page indicator icon as a page of the sequence of pages in the multi-page home screen user interface.

[0279] exist Figure 5B1 , the detection of multiple inputs through various contacts in various scenarios is shown, which, in some embodiments, individually meet the requirements for triggering the first reconfiguration mode. When a contact is detected, the device evaluates the input against various criteria to determine which action, if any, should be performed. Figure 5B1 to Figure 5B2 As shown, in response to detecting a touch hold and drag input by contact 5542 at a location on the touch screen corresponding to application icon 5008a, the device enters a first reconfiguration mode (e.g., icon reconfiguration mode). Figure 5B1 After Figure 5B3As shown, a longer touch hold input detected without movement on another application icon 5008k (or any application icon (e.g., application icon 5008a) or desktop widget displayed on the user-arranged home screen 5050) by contact 5541 also triggers the first reconfiguration mode. Figure 5B1 After Figure 5B3 As shown, a touch-and-hold input detected by contact 5543 on an unoccupied area of ​​the user-arranged home screen 5050 and meeting a shorter time threshold than a touch-and-hold input detected on the application icon 5008a also triggers the first reconfiguration mode. Figure 5B2 to Figure 5B3 It is shown that in response to entering the first reconfiguration mode, the device optionally generates non-visual output (e.g., tactile output 5092) and provides visual feedback (e.g., animating an application icon in home screen 5050') to indicate activation of the user interface reconfiguration mode (e.g., the first reconfiguration mode).

[0280] Figures 5B4 to 5B5 It is shown that in a first reconfiguration mode, a user can drag a target (e.g., selected) application icon to reposition it in a multi-page home screen user interface, for example, by dropping it to a different location on a currently displayed page or placing it at a desired location on a newly displayed page. Figures 5B4 to 5B5 , application icon 5008a is dragged to a different location in the home screen 5050' arranged by the user via a drag input provided by contact 5544 (or a continuation of the drag input made by contact 5442). Other application icons on the home screen 5050' are automatically shifted and moved into the position vacated by application icon 5008a, or space is left to accommodate application icon 5008a at the drop location. When termination of the input is detected (e.g., detection of lift-off of contact 5544), application icon 5008a is inserted into the nearest insertion location in the home screen user interface 5050', and the home screen user interface 5050' is reconfigured. In some embodiments, in conjunction with the placement of application icon 5008a (and detection of termination of input made by contact 5544), the device generates a non-visual output (e.g., a tactile output).

[0281] In some embodiments, upon entering the first reconfiguration mode, the page navigation element 5004 changes its appearance (e.g., becomes highlighted or is replaced with another affordance in the same location) to indicate that an additional home screen reconfiguration (e.g., a second reconfiguration mode) is available by tapping the highlighted page navigation element 5004. In some embodiments, a user interface object 5094 (e.g., an add widget button) appears in the user-arranged home screen 5050' in the first reconfiguration mode to indicate that one or more widgets can be configured in the first reconfiguration mode and added to the home screen user interface. In some embodiments, the page navigation element 5004 with the changed appearance still provides the same navigation functionality as in the normal operating mode (e.g., outside of the reconfiguration mode), as well as a swipe input from one page indicator icon to another page indicator icon in the page navigation element 5004, where the changed appearance still causes navigation to the page corresponding to the page indicator icon at the current contact location. However, in some embodiments, page navigation functionality based on tap inputs on a single page indicator icon is disabled for the page navigation element 5004, and a tap input on any portion of the page navigation element 5004 causes a transition from the first reconfiguration mode to a second reconfiguration mode (e.g., page editing mode). In some embodiments, the page navigation element 5004 with the changed appearance still functions the same as in the normal operating mode with respect to page navigation (e.g., swiping or tapping to navigate to different pages still works), and performs additional functionality that triggers a transition to the second reconfiguration mode in response to different types of input (e.g., touch input on any portion of the page navigation element 5004 by contact, tap input on a portion of the page navigation element 5004 not occupied by a page indicator icon, etc.).

[0282] Figures 5B6 to 5B19 An exemplary user interface for configuring and interacting with a home screen in a second reconfiguration mode is shown according to some embodiments.

[0283] Figures 5B6 to 5B7 5050 'on the home screen 5050 ', a user arranges a highlighted page navigation element 5004, and a tap input is detected by contact 5548 (e.g., when in the first reconfiguration mode). In response to the tap input, the device transitions from the first reconfiguration mode to the second reconfiguration mode and Figure 5B7 Another home screen reconfiguration user interface (eg, page editing user interface 5062) is displayed in (eg, entering a second reconfiguration mode). Figure 5B7In some embodiments, scaled-down representations (e.g., representation 5064", representation 5066", representation 5050", and representation 5052) of multiple (e.g., some, all, each, etc.) user-arranged pages for a multi-page home screen user interface (e.g., home screen 5064, home screen 5066, home screen 5050, and home screen 5052) are displayed in an activation area of ​​page editing user interface 5062 (e.g., visible after scrolling). In some embodiments, representations of all user-arranged pages are at least partially visible from the outset. In some embodiments, representations of only a subset of all user-arranged pages are initially visible, and representations of additional user-arranged pages are displayed in response to scrolling input (e.g., a swipe input in a navigation direction through a sequence of pages of the multi-page home screen user interface, a tap input on a portion of a navigation element closer to one end of a navigation element, etc.). In some embodiments, the order of the representations of the pages is the same as the order of the pages in the multi-page home screen user interface. In some embodiments, a representation of the home screen of the system arrangement (e.g., home screen 5054) is not displayed in the page editing user interface 5062. Similarly, a representation of the desktop widget screen is not displayed in the page editing user interface. Figure 5B7 As shown, the representation of the home screen arranged by the corresponding user is displayed with an enable representation (e.g., a "close" icon 5104) that is used to remove or hide the home screen arranged by the corresponding user, so that when the device exits the second reconfiguration mode and returns to the first reconfiguration mode and then returns to the normal operation mode, the home screen arranged by the corresponding user will not be displayed in the multi-page home screen user interface. In some embodiments, when a tap input is detected on the enable representation associated with the page representation, the appearance of the page representation changes (e.g., switching between a normal visibility state and a reduced visibility state, switching between an unmarked state and a marked state, etc.), and the state of the page represented by the page representation also changes accordingly (e.g., switching between an unhidden state and a hidden or deleted state). In some embodiments, a tap input on the page representation (e.g., in a normal visibility state or a reduced visibility state, a marked state or an unmarked state, etc.) causes a view of the page to be displayed to the user to view the application icons on the page. When the view of the page is released, the page editing user interface is redisplayed. This allows the user to view the page before deleting / hiding or restoring a previously deleted / hidden page.

[0284] In some embodiments, the page editing user interface 5062 includes a preset save area 5100 (e.g., visible simultaneously with the page representations of unhidden pages, or in another portion of the page editing user interface that is not visible simultaneously with the page representations). The preset save area 5100 displays the currently hidden pages. Figure 5B7, which is empty in the previously deleted / hidden user-arranged home screen. In some embodiments, the preset save area 5100 includes a delete enable indication 5102, which permanently deletes the hidden home screen in the preset save area when activated. In some embodiments, such a holding area 5100 and / or delete button 5102 is not provided in the page editing user interface. The hidden page is visually marked as hidden and retained in the page sequence of the multi-page home screen user interface. A restore enable indication is displayed for the corresponding hidden page, and when the restore enable indication is activated, the state of the page is changed from hidden / deleted to unhidden, and once the device exits the second reconfiguration mode, the restored page is displayed in other pages of the multi-page home screen user interface. In some embodiments, the search function provided on the system-arranged home screen returns search results that include application icons on the hidden pages of the home screen user interface and application icons from unhidden pages. In some embodiments, a filter selector for enabling search results including application icons on hidden pages is provided in the search input area on the system-arranged home screen.

[0285] Figure 5B7 、 Figure 5B8 and Figure 5B11 Five different inputs are shown through various contacts 5550, 5552, 5558, 5560 and 5562, which will cause the multi-page home screen user interface to be configured differently, as shown below.

[0286] exist Figure 5B7 , a drag input by contact 5550 is detected at a position on the touch screen corresponding to page representation 5064" for the user-arranged home screen 5064. In response to the movement of contact 5550 into the preset saving area 5100 after the contact 5550 is lifted off, page representation 5064" is dropped into the preset saving area 5100, and the user-arranged home screen 5064 is hidden (e.g., temporarily removed from the page sequence of the multi-page home screen user interface), so that once the device exits the second reconfiguration mode, the user-arranged home screen 5064 will not be displayed as part of the multi-page home screen user interface. Figure 5B8 , page representation 5064″ of the previously deleted home screen 5064 is displayed in the preset saving area 5100. Another drag input by contact 5552 is detected at the position of page representation 5066″ of the user-arranged home screen 5066 and the drag input ends in the preset saving area 5100. Therefore, page representation 5066″ is moved to the preset saving area 5100 and once the device exits the second reconfiguration mode, the user-arranged home screen 5066 is also hidden so that it will not be displayed in the page sequence of the multi-page home screen user interface.

[0287] exist Figure 5B9 , page representations 5064" and 5066" of the previously deleted / hidden home screens 5064 and 5066 are displayed in the preset saving area 5100. Figure 5B9 , upon detecting a gesture for exiting the second reconfiguration mode (e.g., an upward edge swipe input through contact 5554, a tap input through contact 5555 in an unoccupied area of ​​page editing user interface 5062, etc.), the device exits the second reconfiguration mode and returns to displaying the multi-page home screen user interface in the first reconfiguration mode, as shown in FIG. Figure 5B10 In some embodiments, the page that was used to enter the second reconfiguration mode (e.g., page 5050') is redisplayed. In some embodiments, the newly restored page is displayed upon exiting the second reconfiguration mode. In some embodiments, the system selects the page that is displayed upon exiting the second reconfiguration mode based on a variety of factors. Figure 5B10 , the first reconfiguration mode remains active, wherein the user may rearrange application icons or re-enter the second reconfiguration mode by selecting the highlighted page navigation element 5004. Since the two user-arranged home screens have been deleted / hidden, the number of page indicator icons in the page navigation element 5004 has been reduced to represent only those user interfaces that remain (e.g., user-arranged pages 5050 and 5052 represented by page indicator icons 5004a and 5004b).

[0288] exist Figure 5B10 , a tap input by contact 5556 is detected in the touch screen at a location corresponding to the highlighted page indicator 5004. In some embodiments, based on determining that a lift-off of contact 5556 is detected within a second threshold amount of time (e.g., the amount of time required to detect a press or tap and hold input), without detecting substantial movement of contact 5556 since the press of contact 5556 (e.g., the contact is substantially stationary), the device re-enters the second reconfiguration mode, such as Figure 5B11 shown.

[0289] Figure 5B11Multiple inputs through various contacts are shown according to some embodiments, which illustrate different interactions with the page editing user interface 5062. In some embodiments, in response to a tap input through contact 5560 selecting the delete enable 5102, the page representations 5064" and 5066" of the previously hidden / deleted home screens 5064 and 5066 are removed from the preset save area 5100 and the pages 5064 and 5066, along with the applications represented by the application icons on those pages, are permanently deleted from the device. Thus, the deleted applications are removed from their assigned groupings on the user interface arranged by the system. In some embodiments, when there are no hidden pages in the preset save area, the delete enable 5102 is grayed out, as shown in FIG. Figure 5B12 In some embodiments, a page deleted in this manner is not recoverable (e.g., permanently removed from device 100). In some embodiments, permanent deletion of an entire page is disabled on the device, and a page is permanently deleted only if most or all of the application icons on the page are individually manually deleted or moved to another page.

[0290] exist Figure 5B11 Then in Figure 5B13 , a drag input is made by contact 5562, which selects page representation 5064" of the user-arranged home screen 5064 in the preset saving area 5100 and moves page representation 5064" back to the sequence of page representations for the currently unhidden pages (e.g., page representations 5050" and 5052"). The position of page representation 5064" is determined based on the lift-off position of contact 5562. For example, page representation 5064" is optionally displayed on the right side of page representation 5052" (e.g., Figure 5B13 ), in the center or on the left side of the page indicating 5050". In addition, Figure 5B11 Then in Figure 5B13 , the input by contact 5558 drags the page representation 5050 from the first position in the sequence of page representations to the second position in the sequence of page representations to adjust the position of the corresponding page 5050 in the sequence of pages of the multi-page home screen user interface. When the drag input by contact 5558 and the drag input by contact 5562 end, the sequence of page representations is as follows Figure 5B13 as shown (e.g., page representation 5052", followed by page representation 5050", followed by page representation 5064").

[0291] Figure 5B13 After Figure 5B145566, a tap input in an unoccupied area of ​​page editing user interface 5062 through contact 5567, etc., is detected, and in response, the device exits the second reconfiguration mode and displays a page of the multi-page home screen user interface in the first reconfiguration mode (e.g., in Figure 5B14 User-arranged pages 5052').

[0292] Figures 5B14 to 5B16 In response to a sequence of navigation inputs specifying a navigation direction through the multi-page home screen user interface, a sequence of unhidden pages of the multi-page home screen user interface is shown. Figure 5B14 As shown, when the device returns to the first reconfiguration mode, there are three unhidden pages in the sequence of user-arranged page 5052, user-arranged page 5050, and user-arranged page 5064 in the multi-page home screen user interface. The three user-arranged pages have their respective page indicator icons 5004b, 5004a, and 5004d in the highlighted page navigation element 5004 in a sequence corresponding to the order of the pages in the multi-page home screen user interface. In response to a swipe input sequence through contacts 5565 and 5567, the device switches from user-arranged page 5052′ ( Figure 5B14 ) Navigate to the user-configured page 5050'( Figure 5B15 ), then from the user-placed page 5050'( Figure 5B15 ) Navigate to the user-configured page 5064'( Figure 5B16 ).

[0293] exist Figure 5B16 In the first reconfiguration mode, when an input for exiting the first reconfiguration mode is detected (for example, an upward edge swipe input through contact 5566 on an unoccupied area of ​​the page 5064' arranged by the user in the first reconfiguration mode or a tap input through contact 5569, etc.), the device terminates the first reconfiguration mode and the page 5064 arranged by the user is displayed in the normal operation mode.

[0294] In some embodiments, after at least one page has been hidden, when the device exits the second reconfiguration mode and returns to the first reconfiguration mode or normal operating mode, the device displays a warning after the pages of the home screen are hidden that the new application will not be shown on the home screen arranged by the user. Figure 5B17 As shown, the device responds to an input for exiting the first reconfiguration mode (e.g., Figure 5B16After entering normal mode (as shown in the first reconfiguration mode), the device displays an alert 5553 informing the user of the change. In some embodiments, after at least one page is hidden, the new application will be shown only on the system-arranged home screen, and the user has the option of adding an application icon for the new application to a user-arranged page that is not currently hidden (e.g., by dragging and dropping the application icon from a system-arranged page to a user-arranged page in the first reconfiguration mode).

[0295] exist Figure 5B17 In the embodiment, a tap input is detected by 5551 at a position in the touch screen corresponding to the enable indication to return to the first reconfiguration mode or the normal operation mode. Figure 5B18 As shown, after the warning 5553 is dismissed, the user-arranged page 5064 is displayed in normal operating mode.

[0296] exist Figure 5B17 , another page navigation input (e.g., a left swipe input via contact 5571) has been detected on user-arranged page 5064, and in response, application library user interface 5054' (e.g., an alternative form of system-arranged page 5054 represented by page navigation element 5004 as one of a sequence of pages in a multi-page home screen user interface) is displayed, thereby overlaying the background user interface (e.g., a blurred and dimmed version of user-arranged home screen 5064, as shown in FIG. Figure 5B18 In some embodiments, the application library user interface 5054' has features similar to the system layout home screen 5054 and application library user interface 5054', as previously described with respect to Figures 5A1 to 5A36 In some embodiments, the grouping of application icons (e.g., application groups 5020a-5020d) is updated to remove any application icons from the delete / hide page of the home screen user interface.

[0297] Figures 5C1 to 5C73 An exemplary user interface is shown for inserting a user interface object containing application content (e.g., a mini-application object, a desktop widget, etc.) into a page of a home screen user interface (e.g., a single page or a multi-page home screen user interface) according to some embodiments.

[0298] Figure 5C110. User-arranged page 5302' of a multi-page home screen user interface in a first reconfiguration mode (e.g., icon reconfiguration mode) is shown. Application icons 5008aa-5008ao on user-arranged page 5302 (e.g., 5302' in normal mode) are shown as jittering to indicate that the placement of the application icons can be adjusted based on user input. User-arranged page 5302' in the first reconfiguration mode is shown with page navigation element 5004 highlighted, compared to the appearance of page navigation elements on user-arranged page 5302 in normal mode (e.g., non-reconfiguration mode). First page indicator icon 5004a is visually distinguished from the other three page indicator icons 5004b-500d in page navigation element 5004 to indicate that user-arranged page 5302 is the first in a sequence of four user-arranged pages of the multi-page home screen user interface. In the first reconfiguration mode, an add widget button 5094 is displayed at the top of page 5302'. A tap input is detected by contact 5568 at the location of the add widget button 5094. In response, the device displays a widget selection and configuration user interface 5304, such as Figure 5C2As shown. The widget selection and configuration user interface 5304 displays one or more recommended widgets (widgets 5310a, 5310b, 5310c, etc.) in the recommended widget area 5038, which are configured to occupy placement locations of different sizes and / or correspond to different applications. For example, "Application 17 - Widget 1" is a 2×4 sized widget, while "Application 22 - Widget 1" and "Application 22 - Widget 2" are 2×2 sized widgets. In some embodiments, additional widget sizes (e.g., 4×4, 1×4, etc.) are also optionally available for selection. In some embodiments, one or more preconfigured widget stacks are also displayed in the recommended widget area 5038. The widget stack includes multiple system-selected widgets, which optionally have the same size, and the multiple system-selected widgets can be placed in a single placement location of that size in a corresponding user-arranged page of the home screen user interface. In some embodiments, stacks of preconfigured widgets of different sizes (e.g., 2×2, 2×4, 4×4, etc.) are included in the recommended widget area 5038. In some embodiments, a tap on a preconfigured widget stack causes a stack-specific configuration user interface to be displayed, in which a user can view the widgets included in the stack and adjust the order of the widgets in the stack, reconfigure some of the widgets in the stack, and / or delete some widgets from the stack. In some embodiments, the widget stack displayed in the recommended widget area 5038 is, optionally, a functional stack that is automatically switched from time to time (e.g., due to the passage of time or due to a changing context, etc.) when displayed in the recommended widget area 5038 in the widget selection and configuration user interface 5304. In some embodiments, in response to detecting a swipe input (e.g., a vertical swipe input or a horizontal swipe input, etc.) on the recommended widget stack shown in the recommended widget area 5038, the computer system scrolls through the widgets in the recommended widget stack for the user to view which widget is included in the widget stack. In some embodiments, the application content included in the widgets and the recommended widget stack shown in the recommended widget area 5038 are real-time application content and are updated from time to time based on updates that occur in their corresponding applications. The size of the placement location and the size of the widget are specified based on the grid size of the layout used to display application icons. In some embodiments, recommended widgets are based on global popularity and individual usage patterns at the device. The corresponding widget is associated with a widget selection indicator 5312 that indicates the selected / unselected state of the corresponding widget. In Figure 5C2, the top widget 5310a (e.g., the first widget of application 17) has been selected (e.g., by a tap input provided by the user). In some embodiments, the widget selection and configuration user interface 5304 also includes a list of applications 5316 for which widgets are available for selection and configuration.

[0299] exist Figure 5C2 In the embodiment of the present invention, after at least one widget (e.g., widget 5310a) has been selected, a tap input by contact 5570 is detected on touch screen 112 at a position corresponding to add button 5318 on widget selection and configuration user interface 5304. In response to detecting the tap input by contact 5570, display of widget selection and configuration user interface 5304 is stopped and page 5302′ in the first reconfiguration mode is redisplayed, as shown in FIG. Figure 5C3 As shown. Figure 5C3 In some embodiments, the selected widget (e.g., widget 5310a that is relabeled as widget 5322 when shown on the home screen) is automatically inserted into the redisplayed page 5302' at the corresponding placement location (e.g., at the top of the redisplayed page 5302') in the first reconfiguration mode. In some embodiments, if the selected widget is dragged away from its original location in the widget selection and configuration user interface 5304 to the edge of the desktop widget selection and configuration user interface 5304, the selected widget is inserted into another location (e.g., a user-selected location) in the currently displayed home screen page. In some embodiments, the user can drag the widget 5322 to another location after it has been inserted into the home screen page 5302' in the first reconfiguration mode (e.g., to reposition it in the same manner as an application icon that is dragged or dropped into the home screen page 5302' or onto different pages of a multi-page home screen user interface).

[0300] like Figure 5C3 shown, and with Figure 5C1 Compared to page 5302′ shown prior to the insertion of widget 5322, there is insufficient space on page 5302′ to accommodate all of the application icons already present on page 5302′ and widget 5322 in a conventional manner (e.g., individually and / or on the layout grid of the page, etc.). Consequently, the insertion of widget 5322 causes the existing application icons (e.g., icons 5008aa-5008ao) on page 5302′ to move rightward and downward toward the bottom of page 5302′ and stops some of the application icons in the bottom row of page 5302′ from being displayed on page 5302′.

[0301] In some embodiments, as Figures 5C3 to 5C4 As shown, application icons (e.g., application icons 5008am, 5008an, and 5008ao) that are not suitable for the current user arrangement on home screen 5302' are moved to adjacent pages (e.g., as shown in FIG. Figure 5C4 2'). In some embodiments, adjacent page 5324' is a new page created by the device to accommodate the displaced application icons from page 5302'. For example, as indicated by the addition of page indicator icon 5004e between page indicators 5004a and 5004b, a new page corresponding to page indicator 500e has been created and inserted after page 5302'. Figure 5C3 , a left swipe input by contact 5572 is detected on the current user-arranged home screen 5302'. In response to detecting the swipe input by contact 5572, a newly created user-arranged home screen 5324' containing overflowing application icons 5008am-5008ao is displayed. Page indicator icon 5004e in page navigation element 5004 is highlighted to indicate that the location of newly created page 5324' (e.g., page 5324 in normal mode) is immediately after page 5302' from which application icons 5008am-5008ao were received.

[0302] exist Figure 5C4 In FIG, a right swipe input by contact 5574 is detected on the newly created user-arranged page 5324′. In response to detecting the swipe input by contact 5574, the device returns to the previous user-arranged page 5302′, which includes the repositioned application icons 5008aa-5008al and the newly inserted desktop widget 5322, as shown in FIG. Figure 5C5 shown.

[0303] exist Figure 5C5 In the example, a tap input by contact 5576 is again detected on the add widget button 5094 in page 5302′. In response to detecting the tap input by contact 5576, the device again displays the widget selection and configuration user interface 5304, as shown in FIG. Figure 5C6 As shown. Figure 5C6 In the example, the recommended desktop widget area 5308 is updated and a new desktop widget 5310d is displayed to replace the desktop widget 5310a that has been inserted into the home screen page. In this example, the desktop widget 5310d has the same size as the desktop widget 5310a.

[0304] exist Figure 5C5, contact 5578 is detected on the desktop widget 5310d, and based on determining that the selection criteria are met (for example, contact 5578 has not moved more than a threshold amount within a threshold amount of time that satisfies the touch hold requirement, or the strength of contact 5578 satisfies a first strength threshold, etc.), the selection indicator 5312d is updated to indicate the selected state of the desktop widget 5310d before the contact 5578 is lifted. In some embodiments, while contact 5578 is maintained, the desktop widget 5310d is shown as being lifted away from its original position on the desktop widget selection and configuration user interface 5304. While the desktop widget 5310d remains selected, movement of contact 5578 is detected, and in response to detecting that the movement of the contact exceeds a threshold distance away from the original position of the desktop widget 5310d, the desktop widget selection and configuration user interface 5304 is stopped from being displayed, and the user-arranged page 5302' in the first reconfiguration mode is redisplayed, as shown. Figure 5C7 shown.

[0305] like Figure 5C7 As shown, when the user arranged page 5302' is redisplayed, the widget 5310d (now relabeled as widget 5326 outside of the widget selection and configuration user interface 5304) remains under contact 5578. As contact 5578 continues to move on the touch screen 112, the widget 5326 is dragged around the user arranged page 5302' in accordance with the movement of contact 5578, as shown in FIG. Figure 5C8 As shown. Figure 5C8 5302h) is moved directly to a newly created page 5324′ (e.g., Figure 5C4 and Figure 5C13 As shown)), because there is no space on page 5302' to flow the existing application icons to accommodate the desktop widget 5326. Figure 5C8 In , application icons outside of their drop locations are not moved on page 5302'. Figure 5C8 , after the application icon group 5302a-5302h is moved to the newly created page 5324' (e.g., connected to the previously shifted application icons 5008am-5008ao), the desktop widget 5326 is shown at the drop location to provide the user with a preview of what the page 5302' would look like if the desktop widget 5326 were dropped at the current drop location.

[0306] exist Figure 5C9 and 5C11 , it is shown that the contact 5578 is maintained and the desktop widget 5326 is continued to be moved downward to a different placement location, which is currently occupied by the application icon group 5008ai-5008al. Figure 5C10 As shown, contact 5578 dragging widget 5326 has paused over a placement location partially occupied by application icons 5302i-5302l, and in response to detecting that contact 5578 has remained at the same placement location for at least a threshold amount of time, application icons 5302i-5302l cease to be displayed at their original locations and move to the newly created page 5324'. In addition, previously displayed application icons 5008aa-5008ad are returned from the newly created page 5324' to the user-arranged page 5302' after widget 5326 has vacated the original placement location for the application icons. In some embodiments, during the same reconfiguration session, the displaced application icons are moved to the same newly created page 5324' across one or more user-arranged home screens (e.g., without exiting the currently activated first reconfiguration mode and returning to a normal, non-reconfiguration mode). In some embodiments, a new page is created for multiple groups of application icons that are displaced from the same existing page due to the insertion of multiple widgets. In some embodiments, due to the insertion of multiple desktop widgets in multiple existing pages, a new page is created for multiple groups of application icons displayed from those multiple existing pages.

[0307] Figure 5C12 Shown in contact 5578 in Figure 5C11 After lifting from the position shown, the widget is placed at the new placement location at the bottom of page 5302', along with widget 5322 and restored application icons 5008aa-5008ad at the top of page 5302'.

[0308] exist Figure 5C12 In the example, a left swipe input by contact 5580 is detected by the device (e.g., at a location in the touch screen that does not correspond to any widget icon or application icon, or at a location occupied by a widget or application icon, etc.). In response to the swipe input by contact 5580 and based on determining that contact 5580 has exceeded a predefined threshold movement amount (e.g., half the width of the display) to complete the page navigation operation, the newly created page 5324' of the home screen user interface is displayed again. Figure 5C13As shown, the user-arranged home screen 5324′ now includes a plurality of application icons, including application icons 5008am-5008ao that were previously displaced due to the insertion of the desktop widget 5322 and application icons 5008ae-5008al that were previously displaced due to the insertion of the desktop widget 5326.

[0309] exist Figure 5C13 In response to the swipe input through contact 5582 and based on determining that contact 5582 has exceeded a predefined threshold movement amount (e.g., half the width of the display) to complete the page navigation operation, page 5302' is redisplayed, as shown in FIG. Figure 5C14 shown.

[0310] exist Figure 5C14 In the first reconfiguration mode, a tap input by contact 5584 is detected at a location corresponding to the delete badge 5328 associated with the desktop widget 5326 in the first reconfiguration mode. In response to detecting the tap input by contact 5584, the desktop widget 5326 is removed from the page 5302'. Based on determining that the desktop widget 5326 has been inserted into the current placement location during the current session of the first reconfiguration mode, the device restores the application icons that were displaced due to the insertion of the desktop widget 5326 to their original placement locations on the page 5302'. Figure 5C15 As shown, after deleting the newly added desktop widget 5326, the plurality of displaced application icons 5508ae-5508al are restored to their original positions. As a result of the restoration, the page 5324' will also include only the application icons 5008am-5008ao (e.g., in the form of Figure 5C4 shown).

[0311] Figure 5C14 Another scenario is also shown in which a tap input by contact 5586 is detected at a location corresponding to the desktop widget 5326. Figures 5C16 to 5C17 As shown, the widget 5326 is lifted from its placement position in the page 5302' by the touch hold input and is dragged upward away from the placement position in accordance with the movement of the contact 5586. Figures 5C17 to 5C18 In FIG, widget 5326 is dragged by contact 5586 over widget 5322 and is dropped onto widget 5322 after contact 5586 is lifted from the location above widget 5322. Based on determining that widget 5326 and widget 5322 have the same size, as shown in FIG. Figure 5C18As shown, a widget stack 5328 is created at the placement location of widget 5322, with widget 5326 shown at the top. The plurality of application icons 5008aa-5008al that were displaced by the insertion of widget 5326 in the lower portion of page 5302' are restored from page 5324' to their original placement locations on page 5302', as shown in FIG. Figure 5C18 shown.

[0312] In some embodiments, as Figure 5C18 As shown, the newly created widget stack 5328 is displayed with widget indicator icons 5330a and 5330b. The newly added widget 5326 is added to the top of the stack and corresponds to widget indicator icon 5330a, and therefore, widget indicator icon 5330a is highlighted relative to widget indicator icon 5330b to illustrate the order of the currently displayed widget 5326 in the widget stack (e.g., relative to the currently hidden widget 5322).

[0313] In addition, Figure 5C18 In response to detecting the upward edge swipe input by contact 5590, the first reconfiguration mode is terminated and the device returns to the user-arranged home screen 5302 in the normal non-reconfiguration mode, as shown in FIG. Figure 5C19 shown.

[0314] exist Figure 5C19 , an upward swipe input by contact 5592 is detected at a location corresponding to the drop location occupied by widget stack 5328, while widget 5326 is displayed at the drop location. In response to the upward swipe input by contact 5592, the device switches to the next widget in stack 5328 and displays widget 5322 at the drop location, as shown in FIG. Figure 5C20 As shown. Figure 5C20 , the device also updates widget indicator icon 5330 to show that widget indicator icon 5330a for widget 5326 is now highlighted over widget indicator icon 5330b for widget 5322.

[0315] exist Figures 5C20 to 5C22 , a touch-and-hold input by contact 5594 followed by a lift-off of contact 5594 without movement causes display of a quick action menu 5332 for the widget stack 5328 associated with the placement location where the touch-and-hold input was detected. Figure 5C20, contact 5594 is detected at a location corresponding to the currently displayed desktop widget 5322 in the desktop widget stack 5328. Based on determining that contact 5594 remains substantially stationary for at least a threshold amount of time (e.g., an amount of time that is shorter than the time required to trigger the first reconfiguration mode using a touch hold input, and is equal to or greater than the time required to trigger using a touch hold, then drag input, etc.), the device displays a quick action menu for the desktop widget stack 5328. In some embodiments, lift-off of contact 5594 is required before displaying the quick action menu 5332, and the quick action menu is maintained until the quick action menu is dismissed due to another tap input outside of the quick action menu, or due to selection of a menu option in the quick action menu. In some embodiments, lift-off of contact 5594 is not required for display of the quick action menu 5332, and contact 5594 can be moved to a menu option in the quick action menu 5332 to select the menu option by lifting off over the menu option.

[0316] In some embodiments, as Figure 5C21 As shown, quick action menu 5332 includes menu options 5334-5344 for performing actions associated with currently displayed widget 5326 and widget stack 5328. For example, quick action menu 5332 includes option 5334 for sharing the currently displayed widget using one or more sharing devices provided by the device, option 5336 for displaying a widget-specific configuration user interface for configuring the currently displayed widget, option 5338 for deleting the currently displayed widget from the widget stack, option 5342 for deleting the stack-specific configuration user interface for editing the widget stack, option 5344 for deleting all or substantially all of the entire widget stack including its widgets, and option 5345 for entering a first reconfiguration mode of the home screen user interface (e.g., in which the position of the widget in the widget stack, as well as the positions of other application icons and widgets of the home screen user interface, are adjustable).

[0317] Figure 5C22 Two different exemplary scenarios are shown in which tap inputs are performed by two contacts 5596 and 5598, respectively, on different options (e.g., options 5336 and 5340) of the quick action menu 5332. In response to the tap input on option 5336 for editing the currently displayed widget performed by contact 5596, a widget-specific configuration palette 5336' for editing the currently displayed widget 5326 is displayed with widget options 5348 specific to the currently displayed widget 5326 (e.g., size, content update frequency, available application functions, whether user input is enabled, etc.), as shown. Figure 5C23In other instances, in response to a tap input on option 5340 via contact 5598 to edit widget stack 5328, stack-specific options (e.g., option 5356a to open widget options for widget 5326, option 5356b to open widget options for widget 5322, option 5358a to delete widget 5326 from widget stack 5328, option 5358b to delete widget 5322 from widget stack 5328, etc.) are displayed in stack configuration tray 5340′ along with options applicable to the widget stack (e.g., control 5360, which, when activated, enables and / or disables wildcard widgets for widget stack 5328, control 5362, which, when activated, enables and / or disables automatic widget switching for placement of widget stack 5328, control 5347 for deleting the entire stack, etc.). In some embodiments, the wildcard widget occupies a slot in the widget stack and serves as a placeholder in the widget stack for another widget that is not currently included in the widget stack but is determined to be relevant to the user based on the current context. In some embodiments, automatic switching allows the device to automatically (e.g., without user input) select a widget from the widgets included in the widget stack (e.g., optionally including the wildcard widget) to display at the placement location of the widget stack, for example, based on the current context and / or based on a rotation schedule. Figure 5C24 Controls 5360 and 5362 are shown activated by contacts 5604 and 5608, respectively, to enable the universal widget and the auto-switching widget stack 5328 in this example. Figure 5C23 and Figure 5C24 , a completion button 5351 is displayed along with configuration disks 5336' and 5340', respectively. A tap input on the completion button 5351 by contact 5600 or 5602 releases the configuration disks 5336' and 5340', respectively, and the device redisplays page 5302, as shown. Figure 5C25 As shown. Figure 5C25 , because the wildcard widget has been enabled for widget stack 5328, widget indicator icon 5330c is added to the sequence of widget indicator icons 5330. According to some embodiments, the position of widget indicator icon 5330c in the sequence of widget indicator icons 5330 indicates that the widget indicator icon is added at the bottom of widget stack 5328.

[0318] exist Figure 5C25, an upward swipe input by contact 5610 is detected at the placement location occupied by widget stack 5328 while widget 5326 is the currently displayed widget, and in response to the swipe input by contact 5610, the device displays the next widget in the widget stack, which in this example is wildcard widget 5366, according to the navigation direction specified by the swipe input. Figure 5C26 As shown, the device automatically selects a widget that is not currently included in the widget stack 5366 (and optionally not included in any widget stack shown on the same page) and is determined to be relevant to the user given the current context, and displays the automatically selected widget instead of the wildcard widget 5366. In some embodiments, if multiple widgets are determined to be equally relevant given the current context, multiple widgets may be displayed simultaneously instead of the wildcard widget 5366, provided that the overall size and arrangement of the multiple widgets will fit within the placement of the widget stack 5328. Figure 5C26 In some embodiments, the widget indicator icon 5330 is updated so that the widget indicator icon 5330c is highlighted relative to the other widget indicator icons 5330a and 5330b in the sequence of widget indicator icons, and the user is notified that the currently displayed widget is the last one in the widget stack. In some embodiments, when a wildcard widget is displayed at a placement location (e.g., already filled with automatically selected widgets that are not included in the widget stack), the wildcard indicator (e.g., a red edge or glowing appearance) is displayed to notify the user that the wildcard widget is being displayed. In some embodiments, the wildcard widget is always inserted at the bottom of the widget stack and is represented by the last widget indicator icon in the sequence of widget indicator icons for the widget stack. In some embodiments, the widget indicator icon is continuously displayed next to the corresponding widget stack. In some embodiments, when the currently displayed widget in the widget stack is updated (e.g., by automatic switching or rotation and / or by user request), the widget indicator icon is displayed.

[0319] exist Figure 5C26, a reconfiguration input is detected on page 5302 (e.g., a touch hold input of contact 5614 on an unoccupied area of ​​page 5302 for less than a threshold movement amount for a first threshold time amount t1, a touch hold input of contact 5612 on a placement location occupied by widget stack 5328 for at least a second threshold time amount t2 followed by movement of contact 5612 exceeding a threshold movement amount, etc., in some embodiments t1=t2, in some embodiments t1 is greater than t2, in some embodiments t1 is less than t2), and in response to the reconfiguration input, the device enters a first reconfiguration mode (e.g., icon reconfiguration mode), as Figure 5C27 shown.

[0320] Figures 5C27 to 5C32 An example is shown of adding another 4×4 sized widget to the top of page 5302 where a 2×4 sized widget stack 5328 already exists. Figure 5C27 In FIG. 5 , a tap input by contact 5616 is detected at a position corresponding to the add widget button 5094. In response to detecting the tap input by contact 5616, the device displays the widget selection and configuration user interface 5304, as shown in FIG. Figure 5C28 As shown. Figure 5C28 , a new widget 5310e has been presented in the recommended widget area and has been selected (e.g., as indicated by selection indicator 5312e) by contact 5618 (e.g., by a touch-and-hold input or by an earlier tap input on widget 5310e) and dragged away from its original position in widget selection and configuration user interface 5304. In response to detecting the drag input by contact 5618, display of widget selection and configuration user interface 5304 is stopped and page 5302′ in the first reconfiguration mode is displayed, as shown. Figure 5C29 shown. Figures 5C29 to 5C30Widget 5310e (now labeled as widget 5368 on page 5302') is shown being dragged to a placement location occupied by a widget stack and application icon group 5008aa-5008ad and dropped into that placement location. Due to dropping widget 5368, based on determining that the placement location of widget stack 5328 is not large enough to accommodate widget 5368 (or in some embodiments does not have the same dimensions; or in some embodiments is a different group dimension, etc.), widget 5368 is not added to the widget stack 5328 at that placement location. Instead, widget stack 5328 is moved out of the previously occupied placement location (e.g., down, and / or to the right if it is narrower than the width of the page layout) to make room for widget 5368. Thus, the existing application icons 5008aa-5008al are displaced from the current page 5302' and a new page 5370' is optionally created to hold these displaced application icons, as shown in FIG. Figure 5C31 shown.

[0321] exist Figure 5C31 , newly created page 5370′ includes application icon group 5008aa-5008al, which has been displaced from page 5302′ due to the insertion of widget 5368 and the rearrangement movement of widget stack 5328. In some embodiments, if a single widget occupies the placement location occupied by widget stack 5328, then the single widget is optionally sent to the newly created page 5370′ with application icons 5008aa-5008ad, and application icons outside the space required to accommodate widget 5368 5C29-5C30 are not moved on page 5302′.

[0322] Figures 5C29 to 5C30 A sequence of page navigation inputs from page 5302' is shown toward the end of the sequence of pages of the multi-page home screen user interface (e.g., two consecutive left swipe inputs anywhere on the currently displayed page made by contacts 5620 and 5622, two consecutive tap inputs on page indicators 5004f and 5004e, a quick and short swipe input toward the right along page indicator 5004, a longer and slower swipe input toward the right along page indicator 5004, etc.) such that the device navigates first to page 5370' and then to page 5324'. Figure 5C31, page 5370′ is a newly created page for accommodating the shifted application icons 5008aa-5008al, and a new page indicator icon 5004f is added after page indicator icon 5004a and before page indicator icon 5004e, and the page is highlighted relative to the other page indicator icons in the sequence of page indicator icons in page indicator 5004. Figure 5C32 , page 5324' is created in a previous reconfiguration session that is different from the current reconfiguration session (e.g., the previous reconfiguration session ends when the home screen user interface exits the first reconfiguration mode and returns to normal mode, such as Figures 5C18 to 5C25 ), and the page includes application icons 5008am-5008ao that were displaced from page 5302' during a previous reconfiguration session.

[0323] Figures 5C33 to 5C46 Examples of adding a widget to a user-arranged page of a multi-page home screen user interface and simultaneously reconfiguring the user-arranged page of the multi-page home screen user interface are shown according to some embodiments. Figures 5C33 to 5C46 In the example shown in FIG, according to some embodiments, an application icon that is displaced from a page of a multi-page home screen user interface is automatically sent to a folder (e.g., in a new folder created on the page or in a preconfigured folder in a different page) in response to a desktop widget inserted at the location of the application icon in the page. Figures 5C1 to 5C32 In contrast to the example shown in , where the displaced application icons and / or widgets are moved to a newly created user-arranged page of the multi-page home screen user interface. According to various embodiments, with respect to Figures 5C1 to 5C32 and Figures 5C33 to 5C46 The other aspects described in one example shown in Figures 5C1 to 5C32 and Figures 5C33 to 5C46 The aspects of another example shown in combination are described in detail, and optionally are independent of whether the displaced application icon / desktop widget is placed in a folder or a new page.

[0324] Figure 5C33 A first user-arranged page 5302' of a multi-page home screen user interface is shown. The user-arranged page 5302' includes a plurality of application icons 5008aa-5008as arranged in a first reconfiguration mode (e.g., icon reconfiguration mode) according to a preset layout (e.g., on a 5×4 grid). In some embodiments, the user-arranged home screen 5302' includes a page indicator 5004 that indicates both the total number of pages and the position of the currently displayed page in the sequence of pages of the multi-page home screen user interface. For example, as shown in FIG. Figure 5C33 As shown, page indicator icon 5004c is highlighted, which indicates that the currently displayed page 5302' is the fourth page of the five total pages of the multi-page home screen user interface. In some embodiments, multiple pages (e.g., all pages) of the multi-page home screen user interface are user-arranged pages (e.g., there are no system-arranged pages or desktop widget screens, or system-arranged pages and desktop widget screens are displayed as overlays instead of pages of the home screen user interface, etc.). In some embodiments, the first page of the multi-page home screen user interface is a desktop widget screen, and the last page of the multi-page home screen user interface is a system-arranged home screen.

[0325] exist Figure 5C33 In the first reconfiguration mode, the user arranged page 5302' includes an add widget button 5094. Figure 5C33 , a tap input by contact 5624 is detected at a corresponding position on touch screen 112 corresponding to add widget button 5094. In response to the tap input by contact 5624, the device displays widget selection and configuration user interface 5304, as shown in FIG. Figure 5C34 As shown. Figure 5C34 As shown, the desktop widget selection and configuration user interface 5304 includes a set of recommended desktop widgets 5310 corresponding to different applications and having different preconfigured sizes. In some embodiments, the display size of the desktop widget is equivalent to the display size of a predefined number of application icons (e.g., 2, 4, or 8 application icons arranged in a grid). In some embodiments, the desktop widget optionally includes more information and functionality than the corresponding application available in the application icon. The desktop widget selection and configuration user interface also includes a representation of multiple applications 5316 for which the desktop widget can be used to configure. In some embodiments, corresponding desktop widgets in the multiple desktop widgets 5310 have corresponding selection indicators 5312. For example, in Figure 5C34 , a touch hold input by contact 5626 is detected at a corresponding position in the touch screen corresponding to the desktop widget 5310h, so the desktop widget 5310h is selected and the selection indicator 5312h associated with the desktop widget 5310h indicates the selected state of the desktop widget 5310h. Figure 5C3553. The diagram shows that after selecting widget 5310h, movement of contact 5626 is detected. In response to the movement of contact 5626 dragging widget 5310h away from its original position in widget selection and configuration user interface 5304, widget selection and configuration user interface 5304 begins to become darker and translucent and eventually disappears, while the user-arranged page 5302′ transitions to a view below widget 5310h that was dragged by contact 5626, as shown in FIG. Figure 5C36 shown.

[0326] exist Figure 5C36 and Figure 5C37 In FIG, according to the movement of contact 5626, the desktop widget 5310h moves from one position to another position on the page 5302' arranged by the user. Figures 5C37 to 5C39 , movement of contact 5626 is paused for at least a threshold amount of time without termination over a first position on user-arranged page 5302'. The first position currently accommodates a group of two application icons (e.g., application icons 5008ai and 5008aj). In some embodiments, the group of application icons includes a plurality of application icons corresponding to the size of widget 5310h. Figure 5C38 and Figure 5C39 In some embodiments, based on determining that the user-arranged page 5302' cannot accommodate all existing application icons and the new desktop widget 5310h in the usual manner (e.g., individually and / or on a preset layout grid on the page, etc.), the device generates a folder 5390a on the page 5302' and moves the application icon group 5008ai-5008aj at the first location to the newly created folder 5390a to make room for the desktop widget 5310h at the first location. In some embodiments, the application icon group is not directly activatable from the user-arranged home screen 5302' after being moved to the folder 5390a. In some embodiments, the folder 5390a is created at a predefined location on the currently displayed page of the home screen user interface (e.g., the user-arranged page 5302') (e.g., at a corresponding placement location after all or a predetermined remaining application icon group in the currently displayed page of the home screen user interface). In some embodiments, an animated transition is displayed showing the creation of a folder on the currently displayed page and the shifted application icons 5008ai-5008aj flying from the first position to the folder 5390a. Figure 5C39 The state shown in gives the user a preview of the layout of the page 5302' arranged by the user.

[0327] exist Figures 5C39 to 5C41In FIG, movement of contact 5626 is detected and widget 5310h is moved from a first position to a second position occupied by widget group 5008o-5008p in accordance with the movement of contact 5626. Figure 5C40 and Figure 5C41 In the embodiment of the present invention, based on determining that the contact is maintained over the second position for more than a threshold amount of time without termination, the application icon group 5008ao and 5008ap at the second position are moved from the second position to the folder 5390a to make room for the desktop widget 5310h. While the desktop widget 5310h is being moved to the second position in the page 5302' (e.g., to make room for the first position), the application icon groups 5008ai and 5008j are moved from the folder 5390a back to the first position, as shown in FIG. Figure 5C41 As shown. Figure 5C42 5302 ′, and application icon group 5008ao-5008ap remains in folder 5390a.

[0328] Figures 5C43 to 5C44 It is shown that after widget 5310h is inserted into page 5302', repositioning the widget within page 5302' does not cause the additional application icons to be moved to folder 5390a. Figure 5C43 , an additional drag input is detected on the touch screen via contact 5636 from the second position to a third position occupied by application icon group 5008ae-5008af. Based on a determination that there is sufficient space on the currently displayed page to accommodate all or a predetermined number of existing application icon groups and widget 5310h (e.g., individually and / or on a preset layout grid on the page), the application icons on page 5302' (e.g., application icons between the third position and the second position, application icons 5008ae-5008ap, etc.) are rearranged (shifted rightward and downward in sequence) within page 5302' to accommodate widget 5310h at the third position. Due to the movement of widget 5310h, no additional application icons are moved to folder 5390a. The application icons currently within folder 5390a (e.g., application icons 5008ao-5008ap) remain within folder 5390a.

[0329] exist Figures 5C45 to 5C46, a tap input by contact 5638 is detected at a corresponding position corresponding to delete-enable representation 5392 associated with application icon 5008as. In response to the tap input by contact 5638, the device removes application icon 5008as from user-arranged page 5302′ (e.g., and deletes the application associated with application icon 5008as from the device (e.g., from the user-arranged home screen and the system-arranged home screen)), as shown. Figure 5C46...

Claims

1. A method comprising: At a computer system in communication with a display generating component: The first user interface is displayed, wherein: The first user interface includes a placement location configured to spatially accommodate a corresponding user interface object of a plurality of user interface objects corresponding to different applications; The plurality of user interface objects include a first user interface object corresponding to a first application and a second user interface object corresponding to a second application different from the first application; displaying the first user interface object corresponding to the first application at the placement location; detecting an occurrence of an event associated with a change in a state of the second application corresponding to the second user interface object; and In response to detecting the occurrence of the event associated with the change in state of the second application: ceasing to display the first user interface object corresponding to the first application at the drop location, and displaying the first user interface with the second user interface object corresponding to the second application displayed at the drop location; and Automatically updating content displayed at the placement location based on determining that a corresponding amount of time has elapsed since displaying the second user interface object at the placement location includes: removing the second user interface object corresponding to the second application from the display in the first user interface; and The first user interface is redisplayed with the first user interface object corresponding to the first application displayed at the drop location.

2. The method according to claim 1, further comprising: detecting a context change at the computer system while displaying the first user interface with a third user interface object corresponding to a third application displayed at the drop location; as well as In response to detecting the context change at the computer system: ceasing to display the third user interface object corresponding to the third application at the placement location, and The first user interface is displayed with a fourth user interface object of the plurality of user interface objects at the drop location, wherein the fourth user interface object corresponds to a fourth application different from the third application.

3. The method according to claim 2, wherein: Detecting a context change at the computer system includes detecting a change in a current location of the computer system; and The fourth user interface object is selected for display at the drop location based on the current location of the computer system. The method of claim 2 , wherein the fourth user interface object is selected to be displayed at the drop location based on a current time.

5. The method according to claim 1, further comprising: While displaying the first user interface with a third user interface object corresponding to a third application displayed at the drop location, and based on determining that a predetermined amount of time has elapsed: ceasing to display the third user interface object corresponding to the third application at the placement location, and The first user interface is displayed with a fifth user interface object from among the plurality of user interface objects at the drop location, wherein the fifth user interface object corresponds to a fifth application different from the third application.

6. The method according to claim 1, further comprising: detecting a context change indicating that the computer system is placed proximate to a second computer system different from the computer system while displaying the first user interface with a third user interface object displayed at the placement location, the third user interface object corresponding to a third application; as well as In response to detecting the context change indicating that the computer system is placed in proximity to the second computer system: ceasing to display the third user interface object corresponding to the third application at the placement location, and The first user interface is displayed with a sixth user interface object from among the plurality of user interface objects at the drop location, wherein the sixth user interface object corresponds to a digital wallet application.

7. The method according to claim 1, further comprising: receiving an incoming communication at the computer system while displaying the first user interface with a third user interface object corresponding to a third application displayed at the drop location; as well as In response to receiving the incoming communication at the computer system: ceasing to display the third user interface object corresponding to the third application at the placement location, and The first user interface is displayed with a seventh user interface object of the plurality of user interface objects at the drop location, wherein the seventh user interface object corresponds to a communication application.

8. The method of claim 1, wherein: The second application is a calendar application; and Detecting the occurrence of the event associated with the change in state of the second application corresponds to detecting an upcoming event in the calendar application.

9. The method according to claim 1, further comprising: detecting, while displaying the second user interface object corresponding to the second application at the placement location, an occurrence of an event associated with a change in a state of the first application corresponding to the first user interface object; as well as In response to detecting the occurrence of the event associated with the change in state of the first application: ceasing to display the second user interface object corresponding to the second application at the drop location, and The first user interface is displayed with the first user interface object corresponding to the first application displayed at the drop location.

10. The method according to claim 1, further comprising: while displaying the first user interface with the second user interface object displayed at the placement location, detecting input directed to the second user interface object; as well as In response to detecting the input directed to the second user interface object: The first user interface is redisplayed with the first user interface object corresponding to the first application at the dropped location.

11. The method according to claim 1, comprising: while displaying a corresponding user interface object of the plurality of user interface objects at the placement location, detecting an input directed to the corresponding user interface object displayed at the placement location; as well as In response to detecting the input pointing to the corresponding user interface object displayed at the drop location, a user interface of an application corresponding to the corresponding user interface object is displayed.

12. The method of claim 11, comprising, in response to detecting the input pointing to the corresponding user interface object displayed at the drop location, ceasing to display the corresponding user interface object at the drop location.

13. The method according to claim 1, wherein: The first user interface includes multiple placement locations, and wherein a corresponding user interface object currently displayed at a first placement location among the multiple placement locations is updated independently from a corresponding user interface object currently displayed at a second placement location among the multiple placement locations.

14. The method according to claim 13, wherein: The corresponding user interface object currently displayed at the first placement location includes content of a first corresponding application, and the corresponding user interface object currently displayed at the second placement location includes content of a second corresponding application different from the first corresponding application.

15. A computer system comprising: Display generated components; one or more processors; as well as A memory storing one or more programs, wherein the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for the following operations: The first user interface is displayed, wherein: The first user interface includes a placement location configured to spatially accommodate a corresponding user interface object of a plurality of user interface objects corresponding to different applications; The plurality of user interface objects include a first user interface object corresponding to a first application and a second user interface object corresponding to a second application different from the first application; displaying the first user interface object corresponding to the first application at the placement location; detecting an occurrence of an event associated with a change in a state of the second application corresponding to the second user interface object; and In response to detecting the occurrence of the event associated with the change in state of the second application: ceasing to display the first user interface object corresponding to the first application at the drop location, and displaying the first user interface with the second user interface object corresponding to the second application displayed at the drop location; and Automatically updating content displayed at the placement location based on determining that a corresponding amount of time has elapsed since displaying the second user interface object at the placement location includes: removing the second user interface object corresponding to the second application from the display in the first user interface; and The first user interface is redisplayed with the first user interface object corresponding to the first application displayed at the drop location.

16. The computer system of claim 15, wherein: The one or more programs include instructions for executing the method according to any one of claims 2 to 14.

17. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a computer system in communication with a display generation component, cause the computer system to: The first user interface is displayed, wherein: The first user interface includes a placement location configured to spatially accommodate a corresponding user interface object of a plurality of user interface objects corresponding to different applications; The plurality of user interface objects include a first user interface object corresponding to a first application and a second user interface object corresponding to a second application different from the first application; as well as displaying the first user interface object corresponding to the first application at the placement location; detecting an occurrence of an event associated with a change in a state of the second application corresponding to the second user interface object; as well as In response to detecting the occurrence of the event associated with the change in state of the second application: ceasing to display the first user interface object corresponding to the first application at the drop location, and displaying the first user interface with the second user interface object corresponding to the second application displayed at the drop location; as well as Automatically updating content displayed at the placement location based on determining that a corresponding amount of time has elapsed since displaying the second user interface object at the placement location includes: removing the second user interface object corresponding to the second application from the display in the first user interface; as well as The first user interface is redisplayed with the first user interface object corresponding to the first application displayed at the drop location.

18. The computer-readable storage medium of claim 17, wherein: The one or more programs include instructions that, when executed by the electronic device, cause the electronic device to perform the method according to any one of claims 2 to 14.

Images