A device, method, and graphical user interface for interacting with user interface objects corresponding to an application.

Abstract

To generate more efficient human-machine interfaces. [Solution] A computer system or electronic device displays a first user interface. In a first time, the first user interface object is displayed at the placement location. In a second time, the first user interface is displayed at the placement location together with a second user interface object. In the second time, the second user interface object is automatically selected for the display based on the current context of the device. In response to the detection of a first type of gesture directed at the placement location, the second user interface object is replaced with a different user interface object from the user interface objects associated with the placement location.

Description

[Technical Field]

[0001] This application generally relates to electronic devices having a touch-sensitive surface, including but not limited to electronic devices having a touch-sensitive surface for displaying and interacting with user interface objects corresponding to an application. [Background technology]

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touchscreen displays. Such surfaces are widely used to interact with user interfaces on displays and the objects within them. Exemplary user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics.

[0003] Illustrative operations include adjusting the position and / or size of one or more user interface objects, activating buttons, or opening files / applications represented by user interface objects, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Illustrative user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics. In some situations, users need to perform such operations on user interface objects in file management programs (e.g., Finder from Cupertino, California, Apple Inc.), image management applications (e.g., Aperture, iPhoto, Photos from Cupertino, California, Apple Inc.), digital content (e.g., video and music) management applications (e.g., iTunes from Cupertino, California, Apple Inc.), drawing applications, presentation applications (e.g., Keynote from Cupertino, California, Apple Inc.), word processing applications (e.g., Pages from Cupertino, California, Apple Inc.), or spreadsheet applications (e.g., Numbers from Cupertino, California, Apple Inc.).

[0004] However, the methods for performing these operations are cumbersome and inefficient. For example, using a series of mouse-based inputs to select one or more user interface objects and then performing one or more actions on the selected user interface objects is tedious and places a significant cognitive burden on the user. In addition, these methods take more time than necessary, thereby wasting energy. The latter problem is particularly serious in battery-powered devices. [Overview of the Initiative]

[0005] 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 number, range, and / or types of user input, resulting in a more efficient human-machine interface. With respect to battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0006] The above-mentioned defects and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by the devices of this disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, 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 known as a “touchscreen” or “touchscreen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger touch and gestures on the touch-sensitive surface. In some embodiments, the functions are optional and include image editing, drawing, presentation, word processing, spreadsheet creation, gameplay, making phone calls, video conferencing, sending emails, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note-taking, and / or digital video playback. The executable instructions for performing those functions are optional and may be contained in a non-temporary computer-readable storage medium or in other computer program products configured to be executed by one or more processors.

[0007] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying a first page of a multipage home screen user interface via the display generating component, wherein the first page of the multipage home screen user interface includes a first subset of application icons of a plurality of application icons corresponding to a plurality of applications associated with a computer system, and the activation of an individual application icon of the plurality of application icons, according to a first criterion, results in the display of the application corresponding to the individual application icon, replacing the display of an individual page of the multipage home screen user interface on which the individual application icon is displayed. The method further includes detecting a first input that satisfies a second criterion different from the first criterion while the first page of the multipage home screen user interface is being displayed, wherein the second criterion includes the requirement that the first input indicates navigation in a first direction via the multipage home screen user interface. The method is to replace the display of the first page of the multipage home screen user interface with the display of the second page of the multipage home screen user interface in response to the detection of a first input that satisfies a second criterion, and according to the determination that the first input corresponds to a request to navigate to a second page of the multipage home screen user interface, further comprising the second page of the multipage home screen user interface including a second subset of application icons from a plurality of application icons corresponding to a plurality of applications, wherein the second subset of application icons is different from the application icons of the first subset.The method includes detecting a second input that satisfies a third criterion while displaying a second page of a multipage home screen user interface, wherein the third criterion includes the requirement that the second input indicates navigation in a first direction through the multipage home screen user interface, and, in response to detecting a second input that satisfies the third criterion, replacing the display of the second page of the multipage home screen user interface with the display of an individual user interface that includes a representation of a plurality of auto-generated groupings of a plurality of applications, further comprising the activation of an individual representation of an individual auto-generated grouping of a plurality of auto-generated groupings according to the first criterion, which results in the display of application icons of a plurality of third subsets of application icons, the third subset of application icons corresponding to a plurality of applications of at least a subset belonging to an individual auto-generated grouping of a plurality of auto-generated groupings.

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

[0009] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying a first user interface, which includes displaying a plurality of application icons according to a first layout within the first user interface. The method further includes detecting a first input corresponding to a request to insert a first user interface object containing application content into the first user interface while displaying the first user interface including a plurality of application icons according to the first layout. The method further includes, in response to detecting a first input corresponding to a request to insert a first user interface object containing application content into the first user interface, and determining that the first input is directed to a first position corresponding to a first pair of application icons on the first user interface, moving the first pair of application icons from a first position to individual positions where, once the first pair of application icons are moved to individual positions, they cannot be directly activated from the first user interface, thereby creating space at the first position for the first user interface object containing application content, and displaying the first user interface object containing application content at the first position.

[0010] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes, in a first time, displaying a first user interface, the first user interface including a placement location configured to spatially accommodate individual user interface objects of a plurality of user interface objects corresponding to different applications associated with the placement location, the plurality of user interface objects including 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, and in the first time, the first user interface object is displayed at the placement location. The method further includes, in a second time after the first time, displaying the first user interface together with a second user interface object displayed at the placement location, the second user interface object being automatically selected for display at the placement location based on the current context of the device in the second time. The method further includes detecting a gesture directed at the placement location while the second user interface object is displayed at the placement location. The method further includes, in response to detecting a gesture directed at a placement location, replacing the display of a second user interface object with a user interface object different from the user interface objects associated with the placement location, according to the determination that the gesture is a gesture of a first type.

[0011] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying a first user interface including a first placement location associated with a plurality of user interface objects corresponding to different applications, the plurality of user interface objects including a first user interface object containing information from a first application, a second user interface object containing information from a second application different from the first application, and a third user interface object containing information from a third application different from both the first and second applications. The method further includes detecting the occurrence of a specific condition after displaying the first user interface object corresponding to the first application at a first placement location within the first user interface. The method further includes displaying the second user interface object at the first placement location within the first user interface in response to the detection of the occurrence of the specific condition. The method further includes displaying a second user interface object at a first placement location within a first user interface, and then 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 further includes detecting a first user input directed to a separate portion of the configuration user interface while displaying the configuration user interface corresponding to the first placement location.The method further includes, in response to detecting a first user input directed to a particular part of a configuration user interface, satisfying a selection criterion when the first user input is directed to a first representation of a first user interface object among a plurality of user interface objects shown in the configuration user interface, and determining that the first user input includes a move that satisfies a first move criterion, ceasing to display the configuration user interface corresponding to a first placement position in accordance with the move of the first user input, and displaying the first user interface object at a second placement position in a second user interface in accordance with the move 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.

[0012] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying a first page of a multipage home screen user interface in a first reconfiguration mode, wherein the individual positions of a first group of application icons within the first page of the multipage home screen user interface are adjustable according to user input in the first reconfiguration mode. The method further includes detecting a first input corresponding to a request to move from the first reconfiguration mode to a second reconfiguration mode while the first page of the multipage home screen user interface is displayed in the first reconfiguration mode, wherein the availability of one or more pages within the multipage home screen user interface may be changed according to user input in the second reconfiguration mode. The method further includes, in response to detecting a first input, replacing the display of a first page of the multipage home screen user interface in a first reconfiguration mode with a display of individual representations of at least two pages of a plurality of pages of the multipage home screen user interface in a second reconfiguration mode, which includes at least a first representation of the first page of the multipage home screen user interface and a second representation of a second page of the multipage home screen user interface that is different from the first page of the multipage home screen user interface. The method further includes detecting a second input while displaying individual representations of at least two pages of a plurality of pages of the multipage home screen user interface in a second reconfiguration mode, which includes a first representation of the first page and a second representation of the second page. The method is to respond to the detection of a second input by directing the second input to a second representation of a second page displayed in a second reconfiguration mode, and to display the second page of a multipage home screen user interface in a first reconfiguration mode according to the determination that the second input satisfies a first criterion, further comprising the individual positions of a second set of application icons within the second page of the multipage home screen user interface being adjustable according to user input in the first reconfiguration mode.

[0013] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying an individual page of a home screen user interface, wherein the individual page of the home screen user interface includes a first plurality of application icons in a first predetermined arrangement. The method further includes detecting a series of one or more inputs corresponding to a request to insert a first user interface object into the individual page of the home screen user interface, which includes a plurality of application icons for a plurality of applications automatically selected by a computer system. In response to detecting a series of one or more inputs, the method simultaneously displays on the individual page of the home screen user interface two or more 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, further including that the second plurality of application icons are automatically positioned on the individual page of the home screen user interface in a position aligned with the first predetermined arrangement of the first plurality of application icons on the individual page of the home screen user interface, and that the second plurality of application icons are automatically selected by a computer system to be included on the individual page of the home screen user interface.

[0014] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying an individual page of a home screen user interface via the display generating component, wherein the individual page of the home screen user interface includes a first plurality of application icons and a first user interface object that includes application content corresponding to an individual application displayed at a first placement position. The method further includes detecting a first user input corresponding to a request to move the first user interface object including the application content away from a first placement position while displaying an individual page of the home screen user interface. In response to the detection of the first user input, the method further includes moving the first user interface object to a first placement position in the individual page in accordance with the first user input, and, in accordance with the determination that a first criterion is met, moving a first plurality of application icons located at a first set of placement positions relative to the first placement position of the first user interface object including the application content, so as to follow the direction of movement of the first user interface object including the application content.

[0015] According to some embodiments, the method is performed on an electronic device including a display generating component and one or more input devices. The method includes displaying a first user interface via the display generating component for selecting a user interface object to be placed on the home screen user interface of a computer system, wherein the first user interface includes a first user interface object that includes first application content corresponding to a first application. The method further includes detecting a first user input directed to a specific location within the first user interface while displaying the first user interface. In response to detecting a first user input directed to a specific location within the first user interface, the method further includes displaying one or more first controls for changing one or more configuration options of the first user interface object to a configuration option different from one or more predetermined configuration options, according to a determination that the specific location n corresponds to a location of a first user interface object that includes application content corresponding to a first application and is pre-configured with one or more predetermined configuration options corresponding to a first user interface object, and that the first user input is an input of a first type. The method further includes, in response to detecting a first user input directed to a specific location within the first user interface, and determining that the specific location corresponds to the location of a first user interface object containing application content corresponding to a first application, and that the first user input is a second type of input different from a first type of input, displaying the first user interface object containing application content corresponding to a first application in a separate user interface different from the first user interface, using one or more predetermined configuration options corresponding to the first user interface object.

[0016] According to some embodiments, the electronic device includes a display generating component (e.g., a touchscreen, a display, a display for a head-mounted device), a touch-sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensing surface, optionally one or more tactile output generators, one or more processors, and a memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, and the one or more programs including instructions to perform or cause to perform any of the operations described herein. According to some embodiments, a non-temporary computer-readable storage medium has instructions stored therein, and when executed by an electronic device having a display generating component (e.g., a touchscreen, a display, a head-mounted device), a touch-sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensing surface, and optionally one or more tactile output generators, the instructions cause the device to perform or cause to perform any of the operations described herein. 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, memory, and one or more processors for executing one or more programs stored in memory includes one or more elements displayed in any of the methods described herein, the elements being updated in response to input as described in any of the methods described herein. According to some embodiments, the electronic device includes a display generating component (e.g., a touchscreen, a display, 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, optionally one or more tactile output generators, and means for performing or causing to perform any of the operations described herein.According to some embodiments, an information processing apparatus for use in an electronic device having a display generation component (e.g., a touch screen, a display, a head-mounted device, etc.), a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, and optionally one or more haptic output generators, includes means for performing or causing to be performed any of the operations of the methods described herein.

[0017] Thus, an electronic device having a display generation component, a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, optionally one or more haptic output generators, optionally one or more device orientation sensors, and optionally an audio system is provided with an improved method and interface for navigating between user interfaces and interacting with control objects, thereby enhancing the effectiveness, efficiency, and user satisfaction of such a device. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To better understand the various embodiments described, reference should be made to the following "DETAILED DESCRIPTION" in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the following figures.

[0019] [Figure 1A] FIG. 1 is a block diagram of a portable multifunctional device having a touch sensing display according to some embodiments.

[0020] [Figure 1B] FIG. 2 is a block diagram of exemplary components for event processing according to some embodiments.

[0021] [Figure 1C] FIG. 3 is a block diagram of a haptic output module according to some embodiments.

[0022] [Figure 2]Several embodiments of a portable multifunctional device having a touchscreen are shown.

[0023] [Figure 3] This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, according to several embodiments.

[0024] [Figure 4A] The following are exemplary user interfaces for application menus on a portable multifunction device, according to several embodiments.

[0025] [Figure 4B] This document illustrates an exemplary user interface for a multifunctional device having a touch-sensitive surface separated from a display, according to several embodiments.

[0026] [Figure 4C] Examples of dynamic intensity thresholds according to several embodiments are shown. [Figure 4D] Examples of dynamic intensity thresholds according to several embodiments are shown. [Figure 4E] Examples of dynamic intensity thresholds according to several embodiments are shown.

[0027] [Figure 5A1] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A2] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A3] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A4]This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A5] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A6] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A7] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A8] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A9] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A10] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A11] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A12] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A13] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A14]This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A15] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A16] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A17] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A18] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A19] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A20] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A21] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A22] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A23] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A24]This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A25] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A26] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A27] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A28] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A29] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A30] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A31] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A32] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A33] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A34]This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A35] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments. [Figure 5A36] This document illustrates an exemplary user interface that displays and interacts with user interface objects corresponding to different applications, according to some embodiments.

[0028] [Figure 5B1] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B2] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B3] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B4] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B5] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B6] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B7] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B8] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B9]An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B10] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B11] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B12] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B13] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B14] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B15] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B16] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B17] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B18] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown. [Figure 5B19] An exemplary user interface for reconfiguring a multi-page home screen user interface according to some embodiments is shown.

[0029] [Figure 5C1]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C2] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C3] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C4] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C5] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C6]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C7] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C8] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C9] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C10] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C11]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C12] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C13] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C14] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C15] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C16]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C17] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C18] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C19] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C20] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C21]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C22] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C23] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C24] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C25] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C26]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C27] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C28] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C29] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C30] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C31]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C32] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C33] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C34] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C35] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C36]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C37] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C38] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C39] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C40] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C41]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C42] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C43] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C44] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C45] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C46]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C47] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C48] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C49] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C50] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C51]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C52] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C53] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C54] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C55] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C56]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C57] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C58] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C59] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C60] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C61]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C62] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C63] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C64] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C65] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C66]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C67] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C68] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C69] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C70] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C71]The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C72] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5C73] The following is an exemplary user interface for inserting a user interface object containing application content (e.g., a mini-application object, a widget, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments.

[0030] [Figure 5D1] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D2] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D3]This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D4] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D5] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D6] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D7] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D8] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D9] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D10] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D11] This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. [Figure 5D12]This document illustrates an exemplary user interface for selecting and updating user interface objects, including application content (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments.

[0031] [Figure 5E1] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E2] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E3] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E4] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E5] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E6] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E7] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E8] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E9] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E10] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E11] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E12] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E13] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E14] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E15]This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E16] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E17] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E18] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E19] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E20]This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E21] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E22] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E23] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E24] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 5E25]This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E26] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E27] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E28] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E29] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E30]This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E31] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments. [Figure 5E32] This document illustrates an exemplary user interface that interacts with a user interface object (e.g., a widget or mini-application object stack) containing multiple application contents associated with common placement locations (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface) according to some embodiments.

[0032] [Figure 5F1] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F2] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F3] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F4] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F5] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F6] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F7] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F8] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F9] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F10] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F11]This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F12] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F13] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F14] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F15] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F16] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F17] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F18]This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F19] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F20] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F21] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F22] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F23] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F24] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F25]This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F26] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F27] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F28] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F29] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 5F30] This document illustrates an exemplary user interface for interacting with multiple pages of the home screen user interface, according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes).

[0033] [Figure 5G1]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G2] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G3] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G4] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G5]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G6] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G7] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G8] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G9]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G10] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G11] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G12] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G13]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G14] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G15] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G16] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G17]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G18] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G19] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G20] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G21]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G22] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G23] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G24] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G25]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G26] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G27] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G28] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G29]In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G30] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.). [Figure 5G31] In some embodiments, an exemplary user interface is shown for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.).

[0034] [Figure 5H1] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H2]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H3] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H4] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H5] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H6]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H7] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H8] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H9] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H10]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H11] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H12] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H13] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H14]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H15] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H16] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H17] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H18]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H19] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H20] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H21] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H22]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H23] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H24] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H25] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H26]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H27] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H28] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H29] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H30]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H31] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H32] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H33] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H34]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H35] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H36] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H37] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H38]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H39] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H40] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H41] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H42]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H43] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H44] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H45] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H46]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H47] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H48] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H49] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H50]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H51] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H52] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H53] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H54]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H55] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H56] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H57] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H58]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H59] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H60] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H61] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H62]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H63] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H64] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H65] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H66]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H67] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H68] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H69] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H70]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H71] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H72] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H73] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H74]This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H75] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H76] This describes various ways in which existing user interface objects corresponding to different applications on a home screen user interface page (e.g., application icons, widgets, etc. of various sizes) are moved and / or rearranged during reconfiguration mode (e.g., in response to the rearrangement, deletion, addition, passing through, or removal of one or more user interface objects corresponding to different applications), according to some embodiments.

[0035] [Figure 5I1] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I2]In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I3] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I4] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I5] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I6] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I7] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I8]In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I9] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I10] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I11] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I12] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I13] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I14]In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I15] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I16] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I17] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page). [Figure 5I18] In some embodiments, a user interface is shown for configuring a user interface object that includes application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page).

[0036] [Figure 6A] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6B] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6C] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6D] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6E] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6F] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6G] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6H] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6I] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6J] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram. [Figure 6K] This flowchart illustrates how to display and interact with user interface objects corresponding to different applications, according to one embodiment of the diagram.

[0037] [Figure 7A] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7B] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7C] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7D] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7E] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7F] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7G] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment. [Figure 7H] This flowchart illustrates a method for configuring a multi-page home screen user interface according to one embodiment.

[0038] [Figure 8A] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8B] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8C] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8D]This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8E] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8F] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8G] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8H] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8I] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8J] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8K]This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8L] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment. [Figure 8M] This flowchart illustrates a method for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a home screen user interface page, according to one embodiment.

[0039] [Figure 9A] This flowchart illustrates a method for selecting and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of the home screen user interface, according to one embodiment. [Figure 9B] This flowchart illustrates a method for selecting and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of the home screen user interface, according to one embodiment. [Figure 9C] This flowchart illustrates a method for selecting and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with their placement within a page of the home screen user interface, according to one embodiment. [Figure 9D]A flowchart showing a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with the placement positions within the page of a home screen user interface according to some embodiments. [Figure 9E] A flowchart showing a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with the placement positions within the page of a home screen user interface according to some embodiments. [Figure 9F] A flowchart showing a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with the placement positions within the page of a home screen user interface according to some embodiments. [Figure 9G] A flowchart showing a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with the placement positions within the page of a home screen user interface according to some embodiments. [Figure 9H] A flowchart showing a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with the placement positions within the page of a home screen user interface according to some embodiments.

[0040] [Figure 10A] A flowchart showing a method of interacting with a user interface object (e.g., a widget or a mini-application object stack, etc.) that includes multiple application contents associated with a common placement position (e.g., on the page of a home screen user interface and within a stack-specific configuration user interface, etc.) according to some embodiments. [Figure 10B]This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10C] This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10D] This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10E] This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10F] This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10G]This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10H] This flowchart illustrates how to interact with a user interface object (e.g., a widget or mini-application object stack) that contains multiple application contents associated with a common placement location (e.g., on a page of the home screen user interface and within a stack-specific configuration user interface), according to some embodiments.

[0041] [Figure 11A] This flowchart illustrates how to interact with multiple pages of the home screen user interface according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 11B] This flowchart illustrates how to interact with multiple pages of the home screen user interface according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 11C] This flowchart illustrates how to interact with multiple pages of the home screen user interface according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes). [Figure 11D] This flowchart illustrates how to interact with multiple pages of the home screen user interface according to some embodiments (for example, in icon reconstruction mode, page editing mode, and when transitioning between the two modes).

[0042] [Figure 12A]This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments. [Figure 12B] This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments. [Figure 12C] This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments. [Figure 12D] This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments. [Figure 12E]This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments. [Figure 12F] This flowchart illustrates a method for displaying and interacting with user interface objects (e.g., suggested application widgets, recommended application widgets, recent apps widgets, etc.) that present application icons automatically selected by the computer system at user-selected locations (e.g., user-selected placement locations on a page of the home screen user interface, on a widget screen, etc.) according to some embodiments.

[0043] [Figure 13A] This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13B] This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13C]This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13D] This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13E] This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13F] This flowchart illustrates, according to some embodiments, how to move and / or rearrange existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc.) on a home screen user interface page during a reconfiguration mode (e.g., depending on the rearrangement, deletion, addition, passing through, and removal of one or more user interface objects corresponding to different applications). [Figure 13G]A flowchart showing a method of moving and / or rearranging existing user interface objects corresponding to different applications (e.g., application icons of various sizes, widgets, etc.) on a page of a home screen user interface during a reconfiguration mode according to some embodiments (e.g., in response to rearrangement, deletion, addition, passing, removal of one or more user interface objects corresponding to different applications). [Figure 13H] A flowchart showing a method of moving and / or rearranging existing user interface objects corresponding to different applications (e.g., application icons of various sizes, widgets, etc.) on a page of a home screen user interface during a reconfiguration mode according to some embodiments (e.g., in response to rearrangement, deletion, addition, passing, removal of one or more user interface objects corresponding to different applications).

[0044] [Figure 14A] A flowchart showing a method of constructing a user interface object including application content (e.g., widgets, mini - application objects, etc.) and adding it to another user interface (e.g., a page of a home screen). [Figure 14B] A flowchart showing a method of constructing a user interface object including application content (e.g., widgets, mini - application objects, etc.) and adding it to another user interface (e.g., a page of a home screen). [Figure 14C] A flowchart showing a method of constructing a user interface object including application content (e.g., widgets, mini - application objects, etc.) and adding it to another user interface (e.g., a page of a home screen). [Figure 14D]This flowchart illustrates a method for configuring a user interface object containing application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page) according to one embodiment. [Figure 14E] This flowchart illustrates a method for configuring a user interface object containing application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page) according to one embodiment. [Figure 14F] This flowchart illustrates a method for configuring a user interface object containing application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page) according to one embodiment. [Figure 14G] This flowchart illustrates a method for configuring a user interface object containing application content (e.g., widgets, mini-application objects, etc.) and adding it to another user interface (e.g., a home screen page) according to one embodiment. [Modes for carrying out the invention]

[0045] Several methods for displaying and interacting with user interface objects corresponding to different applications, particularly for displaying and interacting with application icons corresponding to different applications, often require multiple separate inputs for the user to manually place application icons into meaningful categories or folders on a user-defined home screen. To activate an application icon and launch the desired application, the user must locate the application icon for the desired application among many other applications on multiple pages of the home screen user interface. Over time, it becomes increasingly difficult for users to keep track of applications installed on their devices, and it also becomes increasingly difficult for users to manually categorize and place application icons on the home screen user interface to enable efficient and easy access to application icons.

[0046] The following embodiments provide one or more additional system-placed pages of the home screen user interface, which include application icons that are automatically categorized and placed within automatically generated groups. Users can easily navigate to one or more system-placed pages of the home screen and locate the application icons of desired applications based on their characteristics (e.g., when installed, app store category, features, etc.) using the same navigation gestures used to navigate between user-placed pages of the home screen user interface. In some embodiments, recently installed applications, recently accessed applications, and / or contextually relevant applications are automatically identified by the operating system and included in corresponding categories (e.g., recently installed, recently accessed, and / or contextually suggested categories, etc.) within the system-placed pages of the home screen user interface. In some embodiments, the system-placed home screen also includes user interface objects containing application content, also called mini-application objects or widgets, which provide a limited subset of features and / or information available from their corresponding applications without requiring the application to be launched. In some embodiments, the system placement page(s) of the multipage home screen user interface allows the user to enter search criteria (e.g., keywords, filters such as recently notified apps, apps originating from a specific caller, etc.) and provides a search input area that returns applications corresponding to the search criteria (e.g., installed applications and / or applications available from the app store, etc.) as search results.In some embodiments, search results include application icons that can be directly interacted with to launch the corresponding application, for example, and can be dragged and dropped to a desired location on the user placement page of the home screen, and / or removed from the device without the user needing to find the application icon at their current location on the user placement page of the home screen user interface. In some embodiments, similar functionality is provided for application icons displayed on the system-placed home screen. In some embodiments, system-generated groupings are represented on the system placement page of the home screen user interface as large folder icons, and individual large folder icons correspond to individual groupings and, when activated, display application icons (or copies or links thereof) for multiple (e.g., some or all) applications from the user placement page of the home screen user interface designated for the individual grouping represented by the large folder icon. The representation of a system-generated grouping (e.g., a large folder icon) optionally includes smaller versions of application icons and folder launch 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.). When an individual mini-application icon is activated (for example, by tap input, double-tap input, etc.), the computer system launches the application corresponding to that individual mini-application icon. When a folder launch icon is activated (for example, by tap input, double-tap input, etc.), it displays the contents of a folder containing application icons corresponding to applications within an individual group. In some embodiments, application icons and groupings included in the system placement page of a multi-page home screen user interface are not modified by user input, or at least not in the same way that they can be modified (for example, deleted, moved, etc.) within the user placement page of the home screen user interface.In some embodiments, system placement pages are presented as pages of the multi-page home screen user interface, along with a corresponding page indicator icon indicating their normal position within a set of pages of the multi-page home screen user interface. In some embodiments, system placement pages are presented as user interface overlays or separate user interfaces (e.g., application library user interfaces) that do not have a corresponding page indicator icon among the page indicator icons of user placement pages in the multi-page home screen user interface. In some embodiments, regardless of their appearance, system placement 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 user placement pages of the multi-page home screen user interface.

[0047] Several methods for configuring pages in a multipage home screen user interface include the user painstakingly moving application icons onto different pages of the home screen or onto new pages of the home screen, and manually deleting all application icons on a page to delete the page. Furthermore, there is no easy way to arrange different pages of a multipage home screen as a whole, or to restore a page or a set of application icons after they have been deleted from the multipage home screen user interface. As disclosed herein, a computer system provides a two-step process for invoking a page editing mode for a multipage home screen user interface, where an icon reconfiguration mode is first invoked on an individual page of the multipage home screen user interface, and while displaying an individual page of the multipage home screen in icon reconfiguration mode, user input is optionally detected to activate the page editing mode, which can hide, rearrange, and / or remove all pages of the multipage home screen user interface from within the multipage home screen user interface when the page editing mode is exited. In some embodiments, while in page editing mode, user input is optionally detected to move previously hidden pages from a pre-configured hold area in the page editing user interface or to mark them as not hidden, resulting in them reappearing in the multi-page home screen user interface when page editing mode is exited. In some embodiments, in page editing mode, delete input is applied to multiple (e.g., all, some, etc.) hidden pages stored in a pre-configured hold area. In some embodiments, hidden pages are not deleted and can be easily restored in the future.In some embodiments, affordances for transitioning from icon reconstruction mode to page editing mode are displayed on multiple (e.g., some or all) pages of the multi-page home screen user interface in icon reconstruction mode (e.g., system-placed pages and / or user-placed pages), and optionally, at the location of page navigation elements on different pages of the home screen user interface.

[0048] On some computer systems, when a user attempts to insert a widget into the home screen user interface, the insertion fails or is blocked if the desired drop location is already occupied or if there is insufficient space on the user interface. The user must first manually clear some space on the user interface, for example, by deleting and / or moving some application icons from the user interface. In some cases, even if insertion is possible, it may cause a reflow of existing application icons on the user interface, sometimes pushing some icons at the bottom of a page onto the next page, which can cause a cascading effect that unnecessarily alters the layout on multi-page home screen user interfaces. As disclosed herein, a computer system moves a set of application icons and / or widgets currently located at a desired placement location selected by the user for a new widget to a pre-configured location (e.g., a new folder or new page on the current page of the home screen user interface) that is created to hold the displayed set of application icons and / or widgets and does not affect the layout of the current page or other parts of other existing pages of a multi-page home screen user interface. In some embodiments, if a new widget is dragged around the page before it is inserted into the page, only a set of application icons at the current position of the new widget are sent to a separate position, and as a result, the user gets a preview of the final state of the page before completing the changes. 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 a widget selection and configuration user interface, or drag it from another location or from another page of the home screen user interface and drop it at a desired position on the desired page of the home screen user interface.If there is sufficient space on the page of the home screen user interface, application icons are transposed and shifted on the page to make room for the insertion of new widgets. In some embodiments, a quick action menu associated with a widget includes a size selector that shows different available sizes for the widget, and by using the size selector to choose a different size for the widget, the widget is resized, and optionally, other application icons and / or widgets are reflowed on the same page of the home screen user interface. In some embodiments, in addition to the reflow of other application icons and / or widgets, some application icons and / or widgets on the page are optionally pushed to a predetermined location (e.g., an existing or newly created folder, or a new page). In some embodiments, resizing a widget optionally causes the application icons and / or widgets on the page of the home screen user interface to rearrange with respect to the block size corresponding to the new and / or old size of the widget (and optionally, the size and position of other widgets on the same page).

[0049] On some computer systems, widgets displayed at a placement location are fixed and do not automatically switch to different widgets or widgets for different applications. As disclosed herein, a widget stack is implemented such that multiple widgets share the same placement location and are displayed at the same location at different times. In some embodiments, a placement location on a page of a home screen user interface is optionally associated with widgets for multiple different applications, and different subsets of widgets or mini-application objects associated with the placement location are displayed at different times. In some examples, the computer system automatically updates the selection of widgets to be displayed at the placement location at the current time based on the current context (e.g., without user input). In addition, the computer system also updates which widgets or mini-application objects are displayed at the placement location in response to user input (e.g., swipe input). In some embodiments, different numbers of widgets are optionally displayed simultaneously at the placement location, depending on whether the current context is sufficiently clear to recommend a single or multiple mini-application objects at the placement location. In many ways, widgets on a home screen user interface behave similarly to application icons on the home screen. For example, it triggers an icon reconfiguration mode in response to the same type of input required to launch an application, display a quick action menu, and / or trigger these functions on the application icon. Widgets on the home screen user interface behave differently in that they occupy more space and, in a different way than application icons, reposition application icons and other existing widgets on the home screen. Widgets can be stacked in the same position, automatically rotated by the computer system without user input, and provide useful functions and information from the corresponding application without launching the application.In some embodiments, when the currently displayed widgets at a widget stack location are automatically updated by the computer system, the computer system provides visual indications of the information within the newly displayed widgets that contributed to the selection of the widgets to be displayed. In some embodiments, the information that contributes to the automatic selection of widgets to be displayed at a widget stack location is visually highlighted against other information on the widgets.

[0050] Some methods of browsing a list of applications with available widgets, selecting a widget from the list, and placing it in a fixed position within the widget screen are rigid and cumbersome. It is difficult for users to find an easy opportunity to discover useful widgets and add them to a desired location on a page of the home screen user interface. A widget stack, as disclosed herein, includes multiple widgets that appear at the same position at different times. A stack-specific configuration user interface includes representations of multiple (e.g., some or all, each of) widgets within the widget stack. In addition to providing configuration options and entry points for additional configuration options for widgets within the stack, the stack-specific configuration user interface also serves a dual purpose, providing widget selection and configuration user interface functionality for widgets within the stack, allowing, in response to the selection of one or more widgets, to add one or more widgets to a default or user-selected position, and then continuing to provide input in response to requests to add the widgets to a page of the home screen user interface (e.g., tapping an add widget affordance, dragging a widget(s) from the stack-specific configuration user interface, and dropping it to a desired location on a page of the home screen user interface). In some embodiments, dragging a widget from the stack-specific configuration user interface removes the widget from the stack (e.g., by adding it to another user-selected position, or optionally, without adding it to another position). In some embodiments, the representation of a widget in the stack-specific widget configuration user interface is rearranged in response to user input, resulting in a rearrangement of widgets in the stack. In some embodiments, the representation of a widget in the stack-specific widget configuration user interface is a scaled-down image of the widget containing current application data.In some embodiments, the representation visually indicates which information within the widget contributes to the automatic selection of the widget as the widget currently displayed at its placement in the widget stack.

[0051] Several methods of providing an entry point to a page editing mode, which allows a user to manage or delete all pages of application icons within the home screen user interface, do not involve first entering icon reconfiguration mode and then entering page editing mode while in icon reconfiguration mode. Similarly, some methods of providing page editing mode do not provide an entry point to icon reconfiguration mode. Essentially, page editing and icon reconfiguration are separated from each other in some computer systems, and transitions from one mode to the other involve multiple user inputs, making the process cumbersome and time-consuming. As disclosed herein, a computer system provides an entry point from page editing mode to icon reconfiguration mode, and an entry point from icon reconfiguration mode to page editing mode. Specifically, the computer system enters page editing mode in response to user input detected while a first page of the home screen user interface is displayed in icon reconfiguration mode, and then exits page editing mode to display another page of the home screen user interface displayed in icon reconfiguration mode in response to input directed towards a representation of another page. The ability to transition back and forth between page editing mode and icon reconfiguration mode in response to a single input is fast and efficient, improving the usability of the computer system. In some embodiments, the page editing user interface displayed in page editing mode includes representations of multiple (e.g., all, some, etc.) user-placed pages of the home screen user interface, and optionally includes both hidden and currently available pages in the same order as the original order before some pages are hidden. In some embodiments, the order of pages including hidden pages is reordered within the home screen user interface by reordering the representations of pages including the representations of hidden pages in the page editing user interface. In some embodiments, the layout and scaling of page representations within the fixed-size page editing user interface are adjusted based on the number of pages present in the home screen user interface.In some embodiments, if the number of pages exceeds a pre-set number within the home screen user interface, the fixed-size page editing user interface may consist of a single scrollable page or multiple pages.

[0052] On some computer systems, a small number of user-selected application icons may be included in a widget and placed on the home screen user interface page. However, the selection is static and does not change based on the current context. As a result, the widget's usefulness is limited, requiring significant user maintenance time and considerable effort to maintain its usefulness. In addition, the widget's position and size are not aligned with the positions of other application icons on the same page, resulting in a chaotic appearance and making it difficult to maintain a pre-configured home screen user interface. As disclosed herein, a computer system provides a proposed application widget containing application icons for multiple applications automatically selected by the computer system based on criteria for measuring the potential relevance of the applications to the user, taking into account the current context. The proposed application widget is repositionable by the user during icon reconfiguration mode and can be inserted at a user-specified position on the home screen user interface page. When displaying the proposed application widget, the computer system displays application icons within the proposed application widget that have a size and position aligned with and consistent with other application icons on the same page, creating a uniform and consistent layout even when the proposed application widget is displayed at different user-selected placement positions on the page.In some embodiments, the proposed application widget functions as a mini-application library, providing the user with a convenient opportunity to discover a desired application icon from among the currently displayed application icons within the proposed application widget, select the currently displayed application icon within the proposed application widget, and drag it to another location on the same page or on a different page of the home screen user interface to add the application icon at the user-selected location (optionally, select and drag inputs and / or drop inputs trigger icon reconfiguration mode). In some embodiments, the drag and drop functionality described above is only available when the page is in icon reconfiguration mode. In some embodiments, when the page is displayed in normal mode, the borders and background of the proposed application widget are visually suppressed, and become more prominent when the page enters icon reconfiguration mode. In some embodiments, the proposed application widget behaves similarly to other application icons and widgets, in that, in response to a pre-configured input to trigger the display of a quick action menu for the user interface object corresponding to the application, the computer system also displays a quick action menu for the proposed application widget. The quick action menu for the proposed application widget includes widget-specific options for the proposed application widget, and optionally, application-specific options corresponding to the application icon within the proposed application widget, if the input location corresponds to that application icon. In some embodiments, the application-specific options for the application include options to hide the application within the proposed application widget (e.g., temporarily, permanently, on the current page, or on another page).As disclosed herein, with alignment between application icons containing the proposed application widget and other application icons on the same page, and with the proposed application widget appearing at different user positions and different sets of application icons presented within user-selected positions, the page containing the proposed application widget maintains a regularly organized layout, resulting in a lower likelihood of user confusion when placing desired application icons on the page and / or causing problems by reflowing application icons on the page when the page configuration is changed by subsequent modifications (e.g., adding, removing, and rearranging application icons and widgets in accordance with additional user input). This feature enhances device usability (e.g., by allowing the user to select the placement of automatically selected application icons while maintaining an organized layout on the page at user-selected positions), makes the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device), and thereby improves device battery life (e.g., by helping users use the device more quickly and efficiently).

[0053] On some computer systems, application icons on the home screen user interface may be arbitrarily placed according to user input, or they may be 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, they are sequentially reflowed in a predetermined order. However, these reflow methods do not take into account the effects of having both application icons and user interface objects containing application content on the same page of the home screen user interface. If arbitrary positioning of objects is allowed, the page can quickly become chaotic and difficult to use as objects of different sizes (e.g., application icons and widgets) are moved around, added, and / or removed. Such sequential reflow of objects that are all the same size is not suitable for pages containing objects of various sizes, and simply continuing with the same reflow method will result in chaos and an incorrect page layout. As disclosed herein, various rules for providing visual feedback on one or more pages of a home screen user interface and for reflowing user interface objects, including application icons and / or application content (e.g., widgets), are introduced for use in various situations when user interface objects, including application icons and / or application content, are inserted into, removed from, and / or moved between one or more pages. In some embodiments, the rules are implemented to avoid one or more page configurations that are likely to result in an aggregation of alignment problems and / or contribute to page disorder and user confusion over time.In some embodiments, rules are enforced to provide visual feedback on how the page will be organized (e.g., via automatic organization into blocks, reflow and move as blocks, etc.) when a user interface object containing application content is inserted into a page, either before user input is completed and the user interface object containing application content is actually inserted into the page, and / or before user input selects any particular placement location for the user interface object containing application content on the page. In some embodiments, rules are enforced to provide visual feedback on preferred and / or required placement locations on the page as soon as a user interface object containing application content is dragged onto the page, so that the user is aware of such recommendations or restrictions on placement locations without failing to drop the user interface object in an unapproved placement location. These features enhance the usability of the device (e.g., by providing the user with preferred visual feedback and guidance when the user gives input to reorganize the pages of the home screen user interface), make the user-device interface more efficient (e.g., by reducing user errors when operating / interacting with the device), and thereby improve the battery life of the device (e.g., by helping the user use the device more quickly and efficiently).

[0054] On some computer systems, widgets can be added to a widget screen user interface from a user interface that displays a list of applications with available widgets, or from a dedicated application for creating specific types of customized widgets (e.g., an application to create a home screen widget for weather forecasts, an application to create a widget for saving bookmarks, etc.). These methods do not provide previews of multiple pre-configured widgets corresponding to different applications within the same user interface, nor do they provide easy means to both modify pre-configured widgets and to insert widgets as pre-configured at user-selected locations. As disclosed herein, a widget selection and configuration user interface displays a collection of pre-configured widgets from multiple applications. From the widget selection and configuration user interface, widget-specific configuration options for pre-configured widgets and / or widget stacks can be accessed, and pre-configured widgets and / or widget stacks can be added directly to another user interface. As disclosed herein, a widget selection and configuration user interface functions as a minilibrary of pre-configured widgets and / or widget stacks, but also provides access to widget-specific configuration options for pre-configured widgets and / or widget stacks. The widget selection and configuration user interface, as well as the widget-specific configuration user interface, optionally display the widget with the currently selected configuration option and real-time data from the widget(s) corresponding to the application(s).A combined widget selection and configuration user interface that allows users to view pre-configured widgets, provides access to widget configuration options, and enables users to select and insert / move one or more widgets from the widget selection and configuration user interface or a widget-specific configuration user interface to another user-selected location, thereby improving and enhancing device usability (e.g., by making it easier to discover widgets and add them to different locations), making the user-device interface more efficient (e.g., by helping users achieve intended results with the necessary inputs and by reducing user errors when operating / interacting with the device), and improving device battery life (e.g., by helping users use the device more quickly and efficiently).

[0055] Figures 1A to 1C, 2, and 3 below provide a description of exemplary devices. Figures 4A to 4B, as well as Figures 5A1 to 5A36, 5B1 to 5B19, 5C1 to 5C73, 5D1 to 5D12, 5E1 to 5E32, 5F1 to 5F30, 5G1 to 5G31, 5H1 to 5H76, and 5I1 to 5I18 illustrate 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 several embodiments; exemplary user interfaces for reconfiguring a multi-page home screen user interface; exemplary user interfaces for inserting user interface objects containing application content (e.g., mini-application objects, widgets, etc.) into a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface); and applications associated with placement locations within a page of a home screen user interface (e.g., a single-page or multi-page home screen user interface). An exemplary user interface for selecting to display and update user interface objects containing application content (e.g., mini-application objects, widgets, etc.), an exemplary user interface for interacting with multiple user interface objects (e.g., widgets or mini-application object stacks, etc.) containing application content associated with a common placement location, an exemplary user interface for interacting with multiple pages of the home screen user interface (e.g., in icon reconfiguration mode, page editing mode, and when transitioning between the two modes), an exemplary user interface for displaying and interacting with user interface objects that present application icons automatically selected by the computer system at a user-selected location, and existing user interface objects corresponding to different applications (e.g., application icons, widgets, etc. of various sizes) on the pages of the home screen user interface,Figures 6A-6K, 7A-7H, 8A-8M, 9A-9H, 10A-10H, 11A-11D, 12A-12F, 13A-13H, and 14A-14G illustrate various ways in which user interface objects are moved and / or rearranged during reconfiguration mode (for example, in response to the rearrangement, deletion, addition, passage, and removal of one or more user interface objects corresponding to different applications), and user interfaces for configuring user interface objects containing application content (e.g., widgets, mini-application objects, etc.) and adding them to another user interface. This flowchart illustrates a method for interacting with multiple user interface objects, including application content associated with their placement location; interacting with multiple pages of a home screen user interface; displaying and interacting with a user interface object that presents an application icon automatically selected by the computer system at a user-selected location; configuring a user interface object containing application content, where existing user interface objects corresponding to different applications on a page of the home screen user interface are moved and / or rearranged during reconfiguration mode; and adding this to another user interface. Using the user interfaces in Figures 4A-4B, 5A1-5A36, 5B1-5B19, 5C1-5C73, 5D1-5D12, 5E1-5E32, 5F1-5F30, 5G1-5G31, 5H1-5H76, and 5I1-5I18, Figures 6A-6K, 7A-7H, 8A-8M, 9A-9H, and 10A-10H,The processes shown in Figures 11A-11D, 12A-12F, 13A-13H, and 14A-14G are illustrated. Example device

[0056] Herein, a detailed reference is made to embodiments shown in the accompanying drawings. The following detailed description includes numerous specific details to provide a complete understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various embodiments described are optional and can be implemented without their specific details. In other examples, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the embodiments.

[0057] In this specification, terms such as "first," "second," etc., are used to describe various elements in several embodiments, but it will be understood that these elements should not be limited by those terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact. Both the first and second contacts are contacts, but they are not the same contact unless the context explicitly indicates otherwise.

[0058] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and is not intended to be limiting. In the descriptions of the various embodiments and the accompanying claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless otherwise explicitly stated in the context. Furthermore, it should be understood that, as used herein, the term “and / or” refers to and includes any and all possible combinations of one or more of the enumerated items relating to the description. It will be further understood that, as used herein, the terms “includes,” “comprises,” and / or “comprising” specify the presence of the described features, integers, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof.

[0059] Where used herein, the term "if" is interpreted, at its discretion and in context, to mean "when," "upon," "in response to determining," or "in response to detecting." Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are interpreted, at its discretion and in context, to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]."

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

[0061] The following discussion describes electronic devices including displays and touch-sensitive surfaces. However, please understand that the definition of an electronic device is optional and may include one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.

[0062] The device generally supports a variety of applications, including one or more of the following: note-taking applications, drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0063] Various applications running on this device optionally utilize at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or modified on an application-by-application basis and / or within individual applications. In this way, the device's common physical architecture (such as the touch-sensitive surface) optionally supports a variety of applications with intuitive and transparent user interfaces for the user.

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

[0065] As used herein and in the claims, the term “tactile output” refers to the physical displacement of a device relative to its previous position, the 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 the displacement of a component relative to the center of mass of a device, which will be detected by the user through the user’s sense of touch. For example, in a situation where a device or component of a device is in contact with a touch-sensitive user’s surface (e.g., the user’s fingers, palm, or other part of their hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or component of the device. For example, the movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user’s action. As another example, movement of a touch-sensitive surface may be interpreted or perceived by the user as "roughness" of that surface, even if there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the user's personal sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.Providing haptic feedback to the user using tactile output improves device usability and makes the user-device interface more efficient (for example, by helping the user provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, reduces power consumption and improves the device's battery life by enabling the user to use the device more quickly and efficiently.

[0066] 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.

[0067] When a device generates tactile outputs with different tactile output patterns (for example, via one or more tactile output generators that move a movable mass to generate tactile outputs), the tactile outputs will, in some situations, evoke different tactile sensations when the user holds or touches the device. Since the user's sensation is based on the user's perception of the tactile output, most users are able to identify 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 actions have been performed. Therefore, in some situations, tactile outputs having tactile output patterns designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behavior (e.g., vibration, displacement, acceleration, rotation, expansion, etc.), and / or interactions (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 of the above), provide the user with useful feedback that reduces input errors and increases the efficiency of the user's operation of the device. In addition, tactile outputs are optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile outputs provide the user with useful feedback that reduces input errors and increases the efficiency of the user's operation of the device.

[0068] In some embodiments, tactile output having a suitable tactile output pattern acts as a signal for the occurrence of a target event behind a scene in the user interface or device. Examples of target events include the activation of affordances provided on the device or within the user interface (e.g., physical buttons, virtual buttons, or toggle switches), the success or failure of a requested action, reaching or crossing a boundary within the user interface, entering a new state, switching the focus of input between objects, activating a new mode, reaching or exceeding an input threshold, and detecting or recognizing the type of input or gesture. In some embodiments, tactile output is provided to serve as a warning or alert for an upcoming event or result that will occur unless a redirection or interruption input is detected in a timely manner. Tactile output is also used in other contexts to improve the user experience, improve the accessibility of the device for users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. Tactile output, optionally accompanied by audio output and / or visible user interface changes, further enhances the user experience when the user interacts with the user interface and / or device, facilitates better communication of information regarding the state of the user interface and / or device, reduces input errors, and increases the efficiency of user operation of the device.

[0069] It should be understood that device 100 is merely an example of a portable multifunction device, and that device 100 may optionally have more or fewer components than those shown, may optionally be a combination of two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in Figure 1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing circuits and / or application-specific integrated circuits.

[0070] 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 CPU(s) 120 and other components of device 100 such as peripheral interface 118 is optionally controlled by memory controller 122.

[0071] A peripheral device interface 118 is used to connect the device's input and output peripherals to the CPU(s) 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data.

[0072] In some embodiments, the peripheral interface 118, the CPU(s) 120, and the 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.

[0073] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals, or electromagnetic signals to electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, which include, but are not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, and memory. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the World Wide Web (WWW), intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs), as well as with other devices. Wireless communication is optional and includes 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), and Code Division Multiple Access (W-CDMA).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, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), Instant Messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)), Instant Messaging and Presence Services Using any of several communication standards, communication protocols, and communication technologies, including, but not limited to, a Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including a communication protocol not yet developed as of the filing date of this document.

[0074] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives the electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits this audio data to the peripheral interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or RF circuit 108 by the peripheral interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212, Figure 2). The headset jack provides an interface between the audio circuit 110 and detachable audio input / output peripherals such as output-only headphones or headsets that have both output (e.g., headphones for one or both ears) and input (e.g., a microphone).

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

[0076] The touch-sensitive display system 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or transmits electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays a visual output to the user. This visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively, “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (for example, a graphical user interface object configured to respond to input directed toward the 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.

[0077] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accept user input 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 memory 102) detect contact on the touch-sensitive display system 112 (and any movement or interruption of contact) and translate the detected contact into interaction with user interface objects (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.

[0078] 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, but other display technologies are used in other embodiments. The touch-sensitive display system 112 and the display controller 156 optionally use any of several currently known or future-developed touch-sensing technologies, including but not limited to capacitive technology, resistive technology, infrared technology, and surface acoustic wave technology, as well as other proximity sensor arrays or other elements for determining one or more contact points 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 that found in iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

[0079] The touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the video resolution of the touch screen is greater than 400 dpi (e.g., 500 dpi, 800 dpi, or higher). The user optionally touches the touch-sensitive display system 112 using any suitable object or attachment such as a stylus or finger. In some embodiments, the user interface is designed to function with finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen than that of a stylus. In some embodiments, the device translates coarse finger input into a precise pointer / cursor position or command to perform an action desired by the user.

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

[0081] Device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with generating, managing, and distributing power within the portable device.

[0082] The device 100 also optionally includes one or more optical sensors 164. Figure 1A shows an optical sensor coupled with an optical sensor controller 158 in the I / O subsystem 106. The optical sensor(s) 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor(s) 164 receives light from the environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with the imaging module 143 (also called the camera module), the optical sensor(s) 164 optionally captures still images and / or video. In some embodiments, the optical sensors are located on the back of the device 100, opposite the touch-sensitive display system 112 on the front of the device, so that the touchscreen can be used as a viewfinder for acquiring still images and / or video images. In some embodiments, a separate light sensor is positioned on the front of the device so that an image of the user can be captured (for example, for selfies, or for video conferencing while the user is viewing other video conference participants on the touchscreen).

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

[0084] The device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 coupled to a peripheral interface 118. Alternatively, the proximity sensor 166 is coupled to an input controller 160 in the I / O subsystem 106. In some embodiments, when the multifunction device is positioned near the user's ear (for example, when the user is making a phone call), the proximity sensor turns off and disables the touch-sensitive display system 112.

[0085] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator coupled with a tactile feedback controller 161 in the I / O subsystem 106. In some embodiments, the tactile output generator(s) 167 includes one or more electroacoustic devices such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile outputs on the device). The tactile output generator(s) 167 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on Device 100 that can be sensed by the user of Device 100. In some embodiments, at least one tactile output generator is positioned alongside or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or horizontally (e.g., forward / backward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is positioned on the back of device 100, opposite the touch-sensing display system 112 which is located on the front of device 100.

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

[0087] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic 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. Furthermore, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. The device / global internal state 157 includes one or more of the following: an active application state indicating which application is active, if there is an application currently active; a display state indicating which application, view, or other information occupies various areas of the touch-sensitive display system 112; a sensor state including information obtained from various sensors and other input or control devices 116 of the device; and position and / or orientation information relating to the position and / or orientation of the device.

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

[0089] 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 circuit 108 and / or external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) are adapted to connect to other devices directly or indirectly via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical or similar to and / or compatible with the 30-pin connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external ports are Lightning connectors identical or similar to and / or compatible with the Lightning connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

[0090] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 112 (in cooperation with the display controller 156) and contact with other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes 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 down event), determining the intensity of contact (e.g., the force or pressure of contact, or an alternative to the force or pressure of contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting a drag event of one or more fingers), and determining whether contact has stopped (e.g., detecting a finger up event or interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, represented by a series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions can optionally be applied to a single contact (e.g., a single finger or stylus contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0091] The contact / motion module 130 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motion, timing, and / or intensity of the detected contact). Therefore, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture involves detecting a finger down event, followed by a finger up (lift-off) event at the same location (or substantially the same location) as the finger down event (e.g., at the icon's position). In another embodiment, detecting a finger swipe gesture on the touch-sensitive surface involves detecting a finger down event, followed by a drag event of one or more fingers, and then a finger up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected with respect to the stylus by detecting a specific contact pattern with respect to the stylus.

[0092] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger down event and detecting a finger up event, but not on the intensity of finger contact between the two events. In some embodiments, a tap gesture is detected according to the determination that the length of time between a finger down event and a finger up event is shorter than a predetermined value (e.g., shorter than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of finger contact between taps meets a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light or deep pressure intensity threshold. Thus, a finger tap gesture can satisfy certain input criteria that do not require the characteristic intensity of contact to meet a given intensity threshold in order for certain input criteria to be met. To clarify, finger contact in a tap gesture generally needs to meet a nominal contact detection intensity threshold below which contact is not detected in order to detect a finger down event. A similar analysis applies to detecting tap gestures or other contacts by a stylus. In cases where the device can detect contact from a finger or stylus hovering over the touch-sensitive surface, the nominal contact detection intensity threshold is optional and does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0093] In a similar manner, the same concept applies to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts involved in the gesture, or do not require the contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, swipe gestures are detected based on the amount of movement of one or more contacts, pinch gestures are detected based on the movement of two or more contacts toward each other, de-pinch gestures are detected based on the movement of two or more contacts away from each other, and long press gestures are detected based on the duration of contact on the touch-sensitive surface that is less than a threshold amount of movement. Therefore, the statement that a particular gesture recognition criterion does not require the intensity of a contact(s) to meet a corresponding intensity threshold for that criterion to be satisfied means that the particular gesture recognition criterion can be satisfied when the contact(s) in the gesture do not reach the corresponding intensity threshold, and can also be satisfied when one or more of the contacts in the gesture reach or exceed the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on the determination that a finger-down event and a finger-up event were detected within a given time period, regardless of whether the contact exceeds or falls below an individual intensity threshold during a given time period, and a swipe gesture is detected based on the determination that the movement of the contact is greater than a predetermined magnitude, even if the contact exceeds an individual intensity threshold at the end of the movement of the contact. Even in embodiments where gesture detection is influenced by the intensity of the contact performing the gesture (for example, the device detects longer presses more quickly when the contact intensity exceeds an intensity threshold, or the device is slower to detect tap inputs when the contact intensity is higher), the detection of those gestures does not require the contact to reach a specific intensity threshold, as long as the criteria for recognizing the gesture can be met in situations where the contact does not reach a specific intensity threshold (for example, even if the amount of time required to recognize the gesture changes).

[0094] Contact intensity thresholds, duration thresholds, and movement thresholds are combined in various different combinations to create heuristics for distinguishing two or more different gestures directed towards the same input element or region in certain situations, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A description that a particular set of gesture recognition criteria does not require that the intensity of a contact(s) meets a corresponding intensity threshold for a particular gesture recognition criterion to be satisfied does not preclude the simultaneous evaluation of other intensity-dependent gesture recognition criteria for identifying other gestures whose criteria are satisfied when the gesture includes a contact with an intensity exceeding a corresponding intensity threshold. For example, in some situations, a first gesture recognition criterion for a first gesture that does not require that the intensity of a contact(s) meet a corresponding intensity threshold for the first gesture recognition criterion to be satisfied is in competition with a second gesture recognition criterion for a second gesture that depends on the contact(s) reaching a corresponding intensity threshold. In such competition, a gesture is optional and will not be recognized as satisfying the first gesture recognition criterion for the first gesture if the second gesture recognition criterion for the second gesture is first satisfied. For example, if a contact reaches the corresponding intensity threshold before it moves a predetermined amount, a deep press gesture will be detected instead of a swipe gesture. Conversely, if a contact moves a predetermined amount before it reaches the corresponding intensity threshold, a swipe gesture will be detected instead of a deep press gesture. Even in such situations, the first gesture recognition criterion for the first gesture still does not require the intensity of the contact(s) to meet the corresponding intensity threshold for the first gesture recognition criterion to be satisfied, because if the contact remains below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the corresponding intensity threshold), the gesture is recognized as a swipe gesture by the first gesture recognition criterion.In this way, a particular gesture recognition criterion that does not require the intensity of a contact(s) to meet a corresponding intensity threshold for that particular gesture recognition criterion to be satisfied still depends on the intensity of the contact(s) with respect to the intensity threshold in some situations, and / or (B) in some situations, the particular gesture recognition criterion (e.g., for a long press gesture) does not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input (e.g., for a long press gesture competing with a deep press gesture for recognition).

[0095] 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 modifying the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). As used herein, the term “graphics” includes, but is not limited to, any object that can be displayed to a user, including, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, and animations.

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

[0097] The haptic feedback module 133 includes various software components that generate commands (for example, commands used by the haptic feedback controller 161) that create haptic outputs at one or more locations on the device 100 using a haptic output generator(s) 167, in response to user interaction with the device 100.

[0098] The text input module 134 is optionally a component of the graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other applications that require text input).

[0099] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the phone 138 for location-based phone calls, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0100] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof: ●Contact module 137 (sometimes called address book or contact list), ●Telephone module 138, ●Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ●Training support module 142, ● Camera module 143 for still images and / or video images, ●Image management module 144, ● Browser module 147, ● Calendar module 148, ● A widget module 149 that optionally includes one or more of the following: weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, other widgets obtained by the user, and user-created widgets 149-6. ●Widget creation module 150 for creating user-created widget 149-6, ●Search module 151, ●Optionally, a video and music player module 152 consisting of a video player module and a music player module, ●Memo Module 153, ●Map module 154, and / or ● Online video module 155.

[0101] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, Java®-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0102] Together with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contact module 137 includes executable instructions for managing an address book or contact list (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), which include adding names(s) to the address book, removing names(s) from the address book, associating telephone numbers(s) to names, email addresses(s) to names, physical addresses(s) to names, or other information, associating images to names, categorizing and sorting names, providing telephone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conferencing 139, email 140, or IM 141, and so on.

[0103] In conjunction with the RF circuit 108, voice circuit 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the telephone module 138 includes executable commands for inputting a series of characters corresponding to a telephone number, accessing one or more telephone numbers in the address book 137, changing an entered telephone number, dialing an individual telephone number, conducting a conversation, and disconnecting or ending the call when the conversation is complete. As described above, the wireless communication may optionally use any of several communication standards, protocols, and technologies.

[0104] In conjunction with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the video conferencing module 139 includes executable commands to start, conduct, and end a video conference between the user and one or more other participants, in accordance with the user's commands.

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

[0106] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the instant messaging module 141 includes executable instructions for inputting a series of characters corresponding to an instant message, modifying previously entered characters, sending individual instant messages (for example, using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol 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, transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0107] In conjunction with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, the training support module 142 includes executable commands for creating training (e.g., having time, distance, and / or calorie consumption targets), communicating with training sensors (in sports devices and smartwatches), receiving training sensor data, calibrating sensors used to monitor training, selecting and playing music for training, and displaying, storing, and transmitting training data.

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

[0109] Together with the touch-sensitive display system 112, display controller 156, contact module 130, graphic module 132, text input module 134, and camera module 143, the image management module 144 includes executable commands 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.

[0110] Together with the RF circuit 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 includes executable commands for browsing the internet in accordance with user commands, including searching, linking, receiving, and displaying web pages or parts thereof, as well as attachments and other files linked to web pages.

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

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

[0113] In conjunction with the RF circuit 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creation module 150 includes executable commands for creating widgets (for example, converting user-specified portions of a web page into widgets).

[0114] 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 to search for text, music, sounds, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to user commands.

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

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

[0117] In conjunction with the RF circuit 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 may be used to receive, display, modify, and store maps and map-associated data (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 commands.

[0118] In conjunction with the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the audio circuit 110, the speaker 111, the RF circuit 108, the text input module 134, the email client module 140, and the browser module 147, the online video module 155 includes executable instructions that enable the user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen 112, or on an external display connected wirelessly or via the external port 124), send emails containing links to specific online videos, and otherwise manage them. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos.

[0119] Each of the modules and applications identified above corresponds to one or more of the functions described above, as well as an executable instruction set for performing the methods described in this application (e.g., methods performed by a computer and other information processing methods described herein). These modules (i.e., instruction sets) do not need to be implemented as separate software programs, procedures, or modules; therefore, various subsets of these modules can be optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores the modules and data structures of the subsets identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

[0120] In some embodiments, device 100 is a device in which the operation of a default set of functions in the device is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

[0121] A default set of functions, which are performed only through the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu. In such embodiments, a “menu button” is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

[0122] Figure 1B is a block diagram showing exemplary components for event processing according to several embodiments. In some embodiments, memory 102 (in Figure 1A) or 370 (in Figure 3) includes an event sorting unit 170 (e.g., within the operating system 126) and individual applications 136-1 (e.g., any of the applications 136, 137-155, 380-390 described above).

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

[0124] In some embodiments, the application internal state 192 includes additional information such as resume information to be used when the application 136-1 resumes execution, user interface state information that indicates or is ready to display information displayed by the application 136-1, a state queue that allows the user to return to a previous state or view of the application 136-1, and one or more redo / undo queues of previous actions performed by the user.

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

[0126] In some embodiments, the event monitor 171 sends requests to the peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only when a significant event occurs (e.g., receiving input that exceeds a predetermined noise threshold and / or for a longer period than predetermined).

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

[0128] The hit view determination module 172 provides software procedures for determining where in one or more views a sub-event occurred when the touch-sensitive display system 112 displays two or more views. A view consists of control devices and other elements that the user can see on the display.

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

[0130] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views arranged in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy from which sub-events should be processed. In most situations, the hit view is the lowest-level view from which the initiating sub-event (i.e., the first sub-event in a series 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 from which it was identified as the hit view.

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

[0132] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes the event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores event information acquired by individual event receiving unit modules 182 in an event queue.

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

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

[0135] Each individual event recognition unit 180 receives event information (e.g., event data 179) from the event sorting unit 170 and identifies an event from the event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparison unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution commands 188 (optionally including sub-event distribution commands).

[0136] The event receiving unit 182 receives event information from the event sorter 170. The event information includes information about sub-events, such as touches or the movement of touches. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, an event includes the rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device's orientation).

[0137] The event comparison unit 184 compares event information with a predefined definition of an event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a default sequence of sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events in event 187 include, for example, the start of a touch, the end of a touch, a move of a touch, a stop of a touch, and multiple touches. In one embodiment, the definition for event 1 (187-1) is a double tap on a displayed object. A double tap includes, for example, a first touch (start of touch) for a predetermined stage on the displayed object, a first lift-off (end of touch) for a predetermined stage, a second touch (start of touch) for a predetermined stage on the displayed object, and a second lift-off (end of touch) for a predetermined stage. In another embodiment, event 2(187-2) is defined as a drag on a displayed object. The drag includes, for example, touching (or contacting) a predetermined number of stages on the displayed object, moving the touch across the touch-sensitive display system 112, and lifting off the touch (end of the touch). In some embodiments, the event also includes information about one or more associated event processing units 190.

[0138] In some embodiments, the event definition 187 includes event definitions for individual user interface objects. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view where three user interface objects are displayed on the touch-sensitive display system 112, when a touch is detected on the touch-sensitive display system 112, the event comparison unit 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 an individual event processing unit 190, the event comparison unit uses the results of the hit test to determine which event processing unit 190 should be activated. For example, the event comparison unit 184 selects the sub-event and the event processing unit associated with the object that triggers the hit test.

[0139] In some embodiments, the definition of an individual event 187 also includes a delay action that delays the delivery of event information until it is determined whether a series of sub-events correspond to an event type in the event recognition unit.

[0140] If an individual event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, the individual event recognition unit 180 enters an event impossible, event failed, or event terminated state, and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, if there are other event recognition units that remain active for the hit view, those event recognition units continue to track and process the sub-events of the ongoing touch-based gesture.

[0141] In some embodiments, an individual event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate to the actively involved event recognition unit how the event distribution system should perform sub-event distribution. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognition units interact with each other, or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are distributed to various levels in the view hierarchy or program hierarchy.

[0142] In some embodiments, an individual event recognition unit 180 activates an event processing unit 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, the individual event recognition unit 180 delivers event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and delaying the sending of) sub-events to individual hit views. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with that flag captures the flag and executes a default process.

[0143] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event processing unit. Instead, the sub-event distribution command distributes event information to an event processing unit associated with a set of sub-events, or to a view that is actively involved. The event processing unit associated with the set of sub-events or the view that is actively involved receives the event information and performs predetermined processing.

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

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

[0146] The foregoing description regarding the handling of user touch events on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it should be understood that not all of these begin on the touchscreen. For example, mouse movement and mouse button presses, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the events to be recognized.

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

[0148] 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 to user interface feedback from software applications on an electronic device (e.g., user input corresponding to a display user interface, and feedback in response to alarms and other notifications indicating the execution of actions or the occurrence of events in the user interface of the electronic device). The tactile feedback module 133 includes one or more of the following: a waveform module 123 (which provides waveforms used to generate tactile outputs), a mixer 125 (which mixes waveforms, such as waveforms of different channels), a compressor 127 (which reduces or compresses the dynamic range of the waveform), a low-pass filter 129 (which filters out high-frequency signal components in the waveform), and a thermal controller 131 (which modulates the waveform according to the thermal state). In some embodiments, the tactile feedback controller 161 (Figure 1A) includes the tactile feedback module 133. In some embodiments, separate units of the haptic feedback module 133 (or separate implementations of the haptic feedback module 133) are also included in an audio controller (e.g., the audio circuit 110 in Figure 1A) and used to generate an audio signal. In some embodiments, a single haptic feedback module 133 is used to generate the audio signal and the waveform for the tactile output.

[0149] In some embodiments, the haptic feedback module 133 also includes a trigger module 121 (e.g., a software application, an operating system, or another software module that determines the tactile output to be generated and initiates a process to generate the corresponding tactile output). In some embodiments, the trigger module 121 generates a trigger signal to initiate the generation of a waveform (e.g., by a waveform module 123). For example, the trigger module 121 generates a trigger signal based on a pre-configured timing criterion. In some embodiments, the trigger module 121 receives trigger signals from outside the haptic feedback module 133 based on the activation of a user interface element (e.g., an application icon or affordance within an application) or a hardware input device (e.g., a home button or an intensity-sensitive input surface such as an intensity-sensitive touchscreen) (e.g., in some embodiments, the haptic feedback module 133 receives trigger signals from a hardware input processing module 146 located outside the haptic feedback module 133), and relays those trigger signals to other components within the haptic feedback module 133 (e.g., a waveform module 123) or a software application that triggers an action (e.g., by the trigger module 121). In some embodiments, the trigger module 121 also receives a tactile feedback generation command (e.g., from the tactile feedback module 133, Figures 1A and 3). In some embodiments, the trigger module 121 generates a trigger signal in response to the tactile feedback module 133 (or the trigger module 121 within the tactile feedback module 133) receiving a tactile feedback command (e.g., from the tactile feedback module 133 in Figures 1A and 3).

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

[0151] Mixer 125 receives waveforms (e.g., from waveform module 123) as input and mixes these waveforms together. For example, when mixer 125 receives two or more waveforms (e.g., a first waveform on a first channel and a second waveform on a second channel that at least partially overlaps with the first waveform), mixer 125 outputs a combined waveform corresponding to the sum of the two or more waveforms. In some embodiments, mixer 125 also modifies one or more of the two or more waveforms, emphasizing a particular waveform over the rest of the two or more waveforms (e.g., by increasing the scale of a particular waveform and / or decreasing the scale of the rest of the waveforms). In some situations, mixer 125 selects one or more waveforms to be removed from the combined waveform (e.g., when there are waveforms from four or more sources that are required to be output simultaneously by tactile output generator 167, the waveform from the oldest source is dropped).

[0152] The compressor 127 receives a waveform (e.g., a synthesized waveform from the mixer 125) as input and modifies the waveform. In some embodiments, the compressor 127 reduces the waveform (e.g., according to the physical specifications of the tactile output generator 167 (Figure 1A) or 357 (Figure 3)) so that the tactile output corresponding to the waveform is reduced. In some embodiments, the compressor 127 limits the waveform, for example, by forcing a predetermined maximum amplitude on the waveform. For example, the compressor 127 reduces the amplitude of the portion of the waveform that exceeds a predetermined amplitude threshold, while maintaining the amplitude of the portion of the waveform that does not exceed the predetermined amplitude threshold. In some embodiments, the compressor 127 reduces the dynamic range of the waveform. In some embodiments, the compressor 127 dynamically reduces the dynamic range of the waveform so that the combined waveform remains within the performance specifications of the tactile output generator 167 (e.g., force and / or movable mass displacement limits).

[0153] The low-pass filter 129 receives a waveform (e.g., a compressed waveform from the compressor 127) as input and filters (e.g., smooths) these waveforms (e.g., removes or reduces high-frequency signal components in the waveform). For example, in some cases, when the tactile output is generated according to a compressed waveform, the compressor 127 includes exogenous signals (e.g., high-frequency signal components) in the compressed waveform that interfere with the generation of the tactile output and / or exceed the performance specifications of the tactile output generator 167. The low-pass filter 129 reduces or removes such exogenous signals in the waveform.

[0154] The thermal controller 131 receives waveforms (e.g., filtered waveforms from the low-pass filter 129) as input and adjusts these waveforms according to the thermal state of device 100 (e.g., based on internal temperatures detected within device 100, such as the temperature of the haptic feedback controller 161, and / or external temperatures detected by device 100). For example, in some cases, the output of the haptic feedback controller 161 varies with temperature (e.g., depending on the reception of the same waveform, the haptic feedback controller 161 generates a first tactile output when the haptic feedback controller 161 is at a first temperature, and generates a second tactile output when the 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 with temperature. To reduce the effects of temperature fluctuations, the waveform is modified (e.g., the amplitude of the waveform is increased or decreased based on temperature).

[0155] In some embodiments, a haptic feedback module 133 (e.g., a trigger module 121) is coupled to a hardware input processing module 146. In some embodiments, one or more other input controllers 160 in Figure 1A include the hardware input processing module 146. In some embodiments, the hardware input processing module 146 receives input from a hardware input device 145 (e.g., another input or control device 116 in Figure 1A, such as a home button or an intensity-sensitive input surface such as an intensity-sensitive touchscreen). In some embodiments, the hardware input device 145 is one of the following: a touch-sensitive display system 112 (Figure 1A), a keyboard / mouse 350 (Figure 3), a touchpad 355 (Figure 3), another input or control device 116 (Figure 1A), or an input device such as an intensity-sensitive home button. In some embodiments, the hardware input device 145 consists of an intensity-sensitive home button and is not the 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., intensity-sensitive home button or touchscreen), the hardware input processing module 146 provides one or more trigger signals to the haptic feedback module 133 to indicate that user input has been detected that satisfies predetermined input criteria, such as an input corresponding to a home button "click" (e.g., a "down click" or "up click"). In some embodiments, the haptic feedback module 133 provides a waveform corresponding to a home button "click" in response to an input corresponding to a home button "click," simulating haptic feedback of pressing a physical home button.

[0156] In some embodiments, the tactile output module includes a tactile feedback controller 161 (tactile feedback controller 161 in Figure 1A) that controls the generation of tactile outputs. In some embodiments, the tactile feedback controller 161 is coupled to a plurality of tactile output generators, selects one or more of the plurality of tactile output generators, and transmits waveforms to the selected one or more tactile output generators that generate tactile outputs. In some embodiments, the tactile feedback controller 161 integrates tactile output requests corresponding to the activation of a hardware input device 145 and tactile output requests corresponding to software events (e.g., tactile output requests from the tactile feedback module 133), modifies one or more waveforms out of two or more waveforms, and emphasizes a particular waveform over the rest of the two or more waveforms (e.g., by increasing the scale of a particular waveform and / or decreasing the scale of the rest of the waveforms, for example, to prioritize the tactile output corresponding to the activation of a hardware input device 145 over the tactile output corresponding to a software event).

[0157] In some embodiments, as shown in Figure 1C, the output of the haptic feedback controller 161 is coupled to the audio circuit of device 100 (e.g., audio circuit 110, Figure 1A) to provide an audio signal to the audio circuit of device 100. In some embodiments, the haptic feedback controller 161 provides both a waveform used to generate a tactile output and an audio signal used to provide an audio output in conjunction with the generation of the tactile output. In some embodiments, the haptic feedback controller 161 modifies the audio signal and / or waveform (used to generate the tactile output) so that the audio output and the tactile output are synchronized (e.g., by delaying the audio signal and / or waveform). In some embodiments, the haptic feedback controller 161 includes a digital-to-analog converter used to convert the digital waveform to an analog signal, which is received by an amplifier 163 and / or a tactile output generator 167.

[0158] In some embodiments, the tactile output module includes an amplifier 163. In some embodiments, the amplifier 163 receives a waveform (e.g., from a tactile feedback controller 161) and amplifies the waveform before transmitting the amplified waveform to a tactile output generator 167 (e.g., either tactile output generator 167 (Figure 1A) or 357 (Figure 3)). For example, the amplifier 163 amplifies the received waveform to a signal level according to the physical specifications of the tactile output generator 167 (e.g., the voltage and / or current required by the tactile output generator 167 to generate a tactile output so that the signal transmitted to the tactile output generator 167 generates a tactile output corresponding to the waveform received from the tactile feedback controller 161), and transmits the amplified waveform to the tactile output generator 167. Accordingly, the tactile output generator 167 generates a tactile output (e.g., by shifting the movable mass forward or backward in one or more dimensions relative to the neutral position of the movable mass).

[0159] In some embodiments, the tactile output module includes a sensor 169 coupled to a tactile output generator 167. The sensor 169 detects the state or state change (e.g., mechanical position, physical displacement, and / or motion) of the tactile output generator 167 or one or more components of the tactile output generator 167 (e.g., one or more moving parts, such as a membrane used to generate tactile output). 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 motion of one or more parts in the tactile output generator 167) to a tactile feedback controller 161, and the tactile feedback controller 161 adjusts the waveform output from the tactile feedback controller 161 (e.g., a waveform optionally transmitted to the tactile output generator 167 via an amplifier 163) according to the information provided by the sensor 169 regarding the state of the tactile output generator 167.

[0160] Figure 2 shows a portable multifunctional device 100 having a touchscreen (e.g., a touch-sensitive display system 112, Figure 1A) according to several embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, and in embodiments described later, the user can select one or more of the graphics by making gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with that one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not constitute a selection of that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon does not arbitrarily select the corresponding application.

[0161] Device 100 optionally also includes one or more physical buttons, such as a "Home" or menu button 204. As previously mentioned, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally run on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on a touchscreen display.

[0162] In some embodiments, device 100 includes a touchscreen display, a menu button 204 (sometimes referred to as a home button 204), a push button 206 for turning the device on / off and locking the device, one or more volume buttons 208, a subscriber identification module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. The push button 206 is optionally used to turn the device on / off by pressing down and holding the button down for a predetermined period of time, to lock the device by pressing down and releasing the button before a predetermined period of time has elapsed, and / or to unlock the device or initiate an unlocking process. In some embodiments, device 100 also accepts verbal input through a microphone 113 to activate or deactivate certain functions. Device 100 also optionally includes one or more contact intensity 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 to the user of device 100.

[0163] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), game system, or control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 typically includes an input / output (I / O) interface 330, which includes a display 340, which is a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, as well as a touchpad 355, a tactile output generator 357 for generating tactile output on a device 300 (similar to the tactile output generator(s) 167 described above with reference to Figure 1A), and a sensor 359 (e.g., an optical sensor, an accelerometer, a proximity sensor, a touch sensor, and / or a contact intensity sensor (similar to the contact intensity sensor(s) 165 described above with reference to Figure 1A). The memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, 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 memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, that are stored in memory 102 of the portable multifunction device 100 (Figure 1A). Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of the 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 authoring module 388, and / or a spreadsheet module 390, while memory 102 of the portable multifunction device 100 (Figure 1A) optionally does not store those modules.

[0164] Each of the elements identified in Figure 3 above is optionally stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to an instruction set that performs the function described above. The modules or programs (i.e., instruction sets) identified above do not need to be implemented as separate software programs, procedures, or modules; therefore, various subsets of those modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0165] Here, we focus on embodiments of a user interface ("UI") that are optionally implemented on the portable multi-functional device 100.

[0166] Figure 4A shows an exemplary user interface for an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. ● Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular signals and Wi-Fi signals. ●Time, ●Bluetooth (registered trademark) indicator, ●Battery status indicator, ●Tray 408 containing icons for frequently used applications such as the following: ○Optionally including an indicator 414 of the number of missed calls or voicemail messages, an icon 416 for the telephone module 138 labeled "Telephone", ○Optionally including an indicator 410 of the number of unread emails, an icon 418 labeled "Mail" for the email client module 140, ○ Icon 420 for browser module 147, labeled as "Browser", and ○ Icon 422 of the video and music player module 152 labeled "Music", and ● Icons for other applications such as the following: ○ Icon 424 for IM module 141, labeled as "Message", ○ Icon 426 for calendar module 148, labeled "Calendar", ○ Icon 428 for image management module 144, labeled as "Photo" ○ Icon 430 for camera module 143, labeled "Camera" ○ Icon 432 of online video module 155, labeled "online video" ○ Icon 434 for stock widget 149-2, labeled "Stocks" ○ Icon 436 of map module 154, labeled "Map" ○ Icon 438 for weather widget 149-1, labeled "Weather" ○ Icon 440 for alarm clock widget 149-4, labeled as "Clock" ○ Icon 442 for training support module 142, labeled "Training Support" ○ Icon 444 for memo module 153, which is labeled as "Memo", and ○ An icon 446 for a configuration application or module that provides access to settings related to device 100 and its various applications 136.

[0167] Please note that the icon labels shown in Figure 4A are merely examples. For example, other labels may be used selectively for various application icons. In some embodiments, the labels for individual application icons include the name of the application to which that individual application icon corresponds. In some embodiments, the label for a particular application icon is different from the name of the application to which that particular application icon corresponds.

[0168] Figure 4B shows an exemplary user interface on a device (e.g., device 300, Figure 3) having a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, Figure 3) separate from the display 450. Device 300 optionally also includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of contact on the touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating tactile output for the user of device 300.

[0169] Many of the following embodiments are given by referring to input on a touchscreen display 112 (when the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface separated from the display, as shown in Figure 4B. In some embodiments, the touch-sensing surface (e.g., 451 in Figure 4B) has a principal axis (e.g., 452 in Figure 4B) corresponding to a principal axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to those embodiments, the device detects contact (e.g., 460 and 462 in Figure 4B) with the touch-sensing surface 451 at positions corresponding to each of the positions on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). Thus, when the touch-sensing surface is separated from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensing surface (e.g., 451 in Figure 4B) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B). Please understand that similar methods may be optionally used in other user interfaces described herein.

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

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

[0172] As used herein and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact on a touch-sensitive surface (e.g., finger contact or stylus contact), or a proxy for the force or pressure of contact on a touch-sensitive surface. The strength of contact has a range of values, including at least four distinct values, and more typically, hundreds (e.g., at least 256) distinct values. The strength of 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 forces at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average or sum) to determine an estimated force of contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change in the touch-sensitive surface adjacent to the contact may optionally be used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurement for the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).Using the intensity of contact as an attribute of user input allows the user to access additional functions, which in some situations are not readily accessible to the user separately on a reduced-size device with a limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical control such as a knob or button).

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

[0174] As used herein and in the claims, the term “characteristic intensity” of a contact refers to the characteristics of that 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 set of intensity samples collected over a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). 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 top 10% value of the contact intensity, half of the maximum value of the contact intensity, 90% of the maximum value of the contact intensity, or a value generated by low-pass filtering of the contact intensity over a predetermined period or at a predetermined time. In some embodiments, the duration of the contact is used when determining the characteristic intensity (for example, when the characteristic intensity is the average of the contact intensity over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action has been performed by the user. For example, the set of one or more intensity thresholds is optionally based on a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity not exceeding the first threshold is a first operation, a contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold is a second operation, and a contact with a characteristic intensity exceeding the second intensity threshold is a third operation. In some embodiments, the comparison between characteristic intensity and one or more intensity thresholds is not used to determine whether to perform a first operation or a second operation, but rather to determine whether to perform one or more operations (for example, whether to perform individual options or refrain from performing individual operations).

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

[0176] The user interface diagrams described herein are optional and may include one or more intensity thresholds...

Claims

1. In a computer system that communicates with display generation components, The first time period is to display the first user interface, The first user interface includes a placement location configured to spatially accommodate individual user interface objects of a plurality of user interface objects corresponding to different applications associated with the placement location, 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, In the first time period, the first user interface object is displayed at the placement location, In a second time period following the first time period, the first user interface is displayed together 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 based on the current context of the computer system in the second time period. While the second user interface object is displayed at the placement location, a gesture directed towards the placement location is detected. In response to detecting the gesture directed towards the placement position, and in accordance with the determination that the gesture is a first type of gesture, the display of the second user interface object is replaced with a user interface object different from the plurality of user interface objects associated with the placement position. Methods that include...

2. The method according to claim 1, wherein the different user interface object is the first user interface object.

3. The method according to claim 1, wherein the different user interface object is a user interface object different from the first user interface object and the second user interface object.

4. The method according to claim 1, wherein the second user interface object is displayed at the placement location on the first user interface in response to the detection of a context change in the computer system, and the first user interface is displayed at the placement location together with the first user interface object.

5. The method according to claim 1, wherein the second user interface object is displayed on the first user interface at the placement position in response to the computer system detecting a request to redisplay the first user interface after it has stopped displaying the first user interface object together with the first user interface object at the placement position.

6. The method according to any one of claims 1 to 5, wherein the placement position is further associated with a third user interface object that displays application icons for a set of contextually selected applications, the activation of individual application icons for individual applications of the set of contextually selected applications triggers the display of the individual applications corresponding to the activated application icons, the third user interface object is displayed at the placement position in the first user interface at a third time different from the first and second times, the third user interface object is automatically selected for display at the placement position based on the current context of the computer system in proximity to the third time, and the set of contextually selected applications is selected based on the current context of the computer system in proximity to the third time.

7. In the fourth time, based on a first value for a pre-configured metric of the current context, a first number of user interface objects for the application are simultaneously displayed at the placement location, In the fifth time, based on a second value for the pre-configured metric of the current context, a second number of user interface objects for the application are simultaneously displayed at the placement location, wherein the first value is different from the second value, and the first number is different from the second number. The method according to any one of claims 1 to 6, including

8. The method according to claim 7, wherein the size of each of the user interface objects displayed at the placement position is adjusted based on the total number of each of the user interface objects displayed simultaneously at the placement position.

9. The method according to any one of claims 1 to 8, wherein the plurality of user interface objects corresponding to the different applications associated with the placement location are selected according to a user configuration input previously received.

10. The method according to any one of claims 1 to 9, wherein the placement location is further associated with a placeholder user interface object which is automatically replaced by a system selection user interface object containing application content from a system selection application, and the system selection user interface object containing application content is dynamically selected from a group of available user interface objects outside of the plurality of user interface objects associated with the placement location.

11. The method according to claim 10, wherein the computer system dynamically selects the system selection user interface object, which includes application content for replacing the placeholder user interface object at the placement location, based on the current context.

12. The plurality of user interface objects corresponding to the different applications associated with the placement location are placed on a stack, and the method is, To detect a series of one or more first inputs, which include one or more first movement inputs directed toward the aforementioned placement position and in a first direction, In response to detecting a corresponding one or more of the aforementioned series of first inputs, the next user interface object is switched to be displayed in the stack at the placement location. The method according to any one of claims 1 to 11, including the method described in any one of claims 1 to 11.

13. At the aforementioned placement location, while displaying individual user interface objects of the plurality of user interface objects corresponding to the different applications associated with the placement location, the system detects tap input directed at the individual user interface objects displayed at the placement location. In response to detecting the tap input directed at the individual user interface object displayed at the aforementioned placement position, the display of the first user interface is stopped, and the user interface of the application corresponding to the individual user interface object displayed at the aforementioned placement position is displayed. The method according to any one of claims 1 to 12, including the method described in any one of claims 1 to 12.

14. The first user interface is a multi-page home screen user interface for a first page, and the multi-page home screen user interface further includes a second page adjacent to the first page. The method described above is At the aforementioned placement location, while displaying individual user interface objects of the plurality of user interface objects corresponding to the different applications associated with the placement location, a swipe input directed towards the individual user interface object displayed at the placement location is detected. In response to detecting the swipe input directed towards the individual user interface object displayed at the aforementioned placement position, the display of the first user interface is stopped according to the determination that the swipe input is in a second direction, and the second page of the multi-page home screen user interface is displayed without displaying the user interface of the application corresponding to the individual user interface object displayed at the aforementioned placement position. The method according to claim 13, including the method described in claim 13.

15. The method according to any one of claims 1 to 14, wherein the plurality of user interface objects corresponding to different applications associated with the placement location are arranged in a stack according to priority estimated based on the current context.

16. The individual user interface object displayed at the aforementioned placement location is automatically modified according to the changed context, and in accordance with this determination, an instruction is displayed at a location close to the aforementioned placement location. The method according to any one of claims 1 to 15, including the method described in any one of claims 1 to 15.

17. The method according to any one of claims 1 to 16, wherein the first user interface includes a plurality of placement locations, each of the plurality of placement locations is associated with a separate set of user interface objects, each containing application content from a different application, and the user interface object currently displayed at the first placement location of the plurality of placement locations is updated independently of the user interface object currently displayed at the second placement location of the plurality of placement locations.

18. The method according to any one of claims 1 to 17, wherein the computer system automatically selects an individual user interface object to be displayed at the placement location from among the plurality of user interface objects associated with the placement location, in accordance with the closing of an application on the computer system, before displaying the first user interface.

19. The method according to any one of claims 1 to 18, wherein the computer system automatically selects, in response to navigating from the screen lock user interface to the first user interface, an individual user interface object to be displayed at the placement location from among the plurality of user interface objects associated with the placement location.

20. The method according to any one of claims 1 to 19, wherein the first user interface includes a plurality of placement locations, each of the plurality of placement locations is associated with a separate set of user interface objects, each containing application content from a different application, and the computer system considers which user interface object is currently displayed at the first placement location of the plurality of placement locations when the user interface object currently displayed at a second placement location of the plurality of placement locations is updated or when switching to a different user interface object for display at the second placement location.

21. While displaying individual user interface objects of the plurality of user interface objects at the placement location on the first user interface, the system detects input corresponding to a request to display a plurality of selectable options associated with the placement location. Displaying the multiple selectable options associated with the placement location in response to detecting the input corresponding to the request to display the multiple selectable options associated with the placement location, including a first selectable option that, when activated, enables the automatic switching of the display of user interface objects via the multiple user interface objects at the placement location. The method according to any one of claims 1 to 20, including the method described in any one of claims 1 to 20.

22. The method according to claim 21, wherein displaying the plurality of selectable options includes, when activated, displaying a second selectable option that enables a placeholder user interface object at the placement location, and when the placeholder user interface object is selected to be displayed at the placement location, the placeholder user interface object is automatically replaced by a system selection user interface object containing application content from a system selection application, and the system selection user interface object containing application content is dynamically selected from a group of available user interface objects outside of the plurality of user interface objects associated with the placement location.

23. While displaying individual user interface objects of the plurality of user interface objects at the placement location on the first user interface, an input directed to the placement location and satisfying a pre-set criterion is detected. In response to detecting the input directed to the placement position and satisfying the pre-set criteria, display one or more selectable options from a first set associated with the placement position and one or more selectable options from a second set associated with the individual user interface object. The method according to any one of claims 1 to 22, including the method described in any one of claims 1 to 22.

24. Displaying the first user interface having the second user interface object displayed at the aforementioned placement position is: The second user interface object simultaneously displays the first application content from the second application and the second application content from the second application, Based on the correlation between the first application content and the current context of the computer system in the second time period, the second user interface object is automatically selected for display at the placement location, and in accordance with this determination, the first application content is visually highlighted in relation to the second application content in the second user interface object. The method according to any one of claims 1 to 23, including the method described in any one of claims 1 to 23.

25. The method according to claim 24, wherein visually highlighting the first application content relative to the second application content includes applying the visual marking to the first application content within the second user interface object without applying the visual marking to the second application content within the second user interface object.

26. The display and Input elements and, One or more processors, A computer system comprising, A memory that stores one or more programs, and the one or more programs are configured to be executed by the one or more processors, During the first time period, the first user interface is displayed. The first user interface includes a placement location configured to spatially accommodate individual user interface objects of a plurality of user interface objects corresponding to different applications associated with the placement location, 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, During the first time period, the first user interface object is displayed at the placement location. In a second time period following the first time period, the first user interface is displayed together with the second user interface object displayed at the placement location, and the second user interface object is automatically selected to be displayed at the placement location based on the current context of the computer system in the second time period. While the second user interface object is displayed at the placement location, a gesture directed towards the placement location is detected. A computer system including an instruction to replace the display of the second user interface object with a user interface object different from the plurality of user interface objects associated with the placement location, in response to detecting the gesture directed toward the placement location, and according to the determination that the gesture is a first type of gesture.

27. The computer system according to claim 26, wherein one or more programs include instructions for performing the method described in any one of claims 2 to 25.

28. A program that includes instructions, wherein when the instructions are executed by a computer system, the computer system, In the first time period, the first user interface is displayed. The first user interface includes a placement location configured to spatially accommodate individual user interface objects of a plurality of user interface objects corresponding to different applications associated with the placement location, 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, During the first time period, the first user interface object is displayed at the placement location. In a second time period following the first time period, the first user interface is displayed together with the second user interface object displayed at the placement location, and the second user interface object is automatically selected to be displayed at the placement location based on the current context of the computer system in the second time period. While the second user interface object is displayed at the placement location, a gesture directed towards the placement location is detected. A program that, in response to detecting the gesture directed towards the placement position, determines that the gesture is of a first type, and replaces the display of the second user interface object with a user interface object different from the plurality of user interface objects associated with the placement position.

29. The program according to claim 28, further comprising, when executed by the computer system, instructions causing the computer system to perform the method according to any one of claims 2 to 25.

Images